Home > HP > Printer > HP 5500 Ei 5500 Si Switch Series Configuration Guide

HP 5500 Ei 5500 Si Switch Series Configuration Guide

Add to Favourites
    Download as PDF Print this page Share this page

    Have a look at the manual HP 5500 Ei 5500 Si Switch Series Configuration Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 1114 HP manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.

    View all the pages
    Page
    of 2513
    Add page 1351 to Favourites
    image text
    Enable zoom 
    							 215 
# Display PIM routing information on Switch B. 
[SwitchB] display pim routing-table 
No information is output on Switch B. 
# Display PIM routing information on Switch D. 
[SwitchD] display pim routing-table 
 VPN-Instance: public net 
 Total 1 (*, G) entry; 1 (S, G) entry 
 
 (*, 225.1.1.1) 
     RP: 10.1.1.1 (local) 
     Protocol: pim-sm, Flag: WC 
     UpTime: 00:12:07 
     Upstream interface: Register 
         Upstream neighbor: NULL 
         RPF prime neighbor: NULL 
     Downstream interface(s) information: 
     Total number of downstreams: 1 
         1: Vlan-interface200 
             Protocol: igmp, UpTime: 00:12:07, Expires: - 
 
 (10.110.6.100, 225.1.1.1) 
     RP: 10.1.1.1 (local) 
     Protocol: pim-sm, Flag: SPT 2MSDP ACT 
     UpTime: 00:40:22 
     Upstream interface: Vlan-interface104 
         Upstream neighbor: 10.110.4.2 
         RPF prime neighbor: 10.110.4.2 
     Downstream interface(s) information: 
     Total number of downstreams: 1 
         1: Vlan-interface200 
             Protocol: pim-sm, UpTime:  - , Expires:  - 
SA message filtering configuration 
Network requirements 
As shown in Figure 63, three PIM-SM domains exist in the network, and OSPF runs within and among the 
domains to provide unicast routing.  
Loopback 0 is configured as a C-BSR and a C-RP in th e related PIM-SM domains on Switch A, Switch C, 
and Switch D, respectively.  
An MSDP peering relationship is set up between  Switch A and Switch C and between Switch C and 
Switch D.  
Source 1 sends multicast data to multicast groups 225.1.1.0/30 and 226.1.1.0/30, and Source 2 sends 
multicast data to multicast group 227.1.1.0/30.  
Configure SA message filtering rules so that receivers Host A and Host B can receive only the multicast 
data addressed to multicast groups 225.1.1.0/30 and 226.1.1.0/30, and Host can receive only the 
multicast data addressed to multicast groups 226.1.1.0/30 and 227.1.1.0/30.
    Add page 1352 to Favourites
    image text
    Enable zoom 
    							 216 
Figure 63 Network diagram 
 
Device Interface  IP address Device Interface IP address 
Source 1  — 10.110.3.100/24  Switch C  Vlan-int300  10.110.4.1/24 
Source 2  — 10.110.6.100/24  Vlan-int104 10.110.5.1/24 
Switch A  Vlan-int100  10.110.1.1/24  Vlan-int101 192.168.1.2/24 
 Vlan-int102 10.110.2.1/24  Vlan-int103 192.168.2.2/24 
 Vlan-int101 192.168.1.1/24  Loop0 2.2.2.2/32 
 Loop0 1.1.1.1/32 Switch D Vlan-int400 10.110.6.1/24 
Switch B  Vlan-int200  10.110.3.1/24    Vlan-int500  10.110.7.1/24 
 Vlan-int102 10.110.2.2/24  Vlan-int104 10.110.5.2/24 
 Vlan-int103 192.168.2.1/24  Loop0 3.3.3.3/32  
Configuration Procedure 
1. Configure IP addresses and unicast routing: 
Configure the IP address  and subnet mask for each interface as per  Figure 63. (Details not sh
own.) 
Configure OSPF for interoperation among the swit ches. Ensure the network-layer interoperation 
within and between the PIM-SM domains and en sure dynamic update of routing information 
among the switches by leveraging unicast routing. (Details not shown.) 
2.  Enable IP multicast routing, PIM-SM and IGMP, and configure a PIM domain border: 
# On Switch A, enable IP multicast routing, en able PIM-SM on each interface, and enable IGMP 
on the host-side interface, VLAN-interface 100. 
 system-view 
[SwitchA] multicast routing-enable 
[SwitchA] interface vlan-interface 100 
[SwitchA-Vlan-interface100] igmp enable 
[SwitchA-Vlan-interface100] pim sm 
[SwitchA-Vlan-interface100] quit 
[SwitchA] interface vlan-interface 101 
[SwitchA-Vlan-interface101] pim sm 
[SwitchA-Vlan-interface101] quit 
MSDP peers
PIM-SM 1
PIM-SM 2PIM-SM 3
Loop0
Loop0
Source 1 Source 2
Receiver Host B Receiver
Host C
Receiver
Host A
Vlan-int100
Vlan-int200
Switch A
Switch C
Switch D
Switch B
V la
n -
in t
1 0 3
Vla
n
-i
n
t1 0
3
V la n
-in
t1 0
1
Vla n
-i
n
t1 0
1
Vlan-int300 Vlan-int104
Vlan-int104
Vlan-int500 Vlan-int400
    Add page 1353 to Favourites
    image text
    Enable zoom 
    							 217 
[SwitchA] interface vlan-interface 102 
[SwitchA-Vlan-interface102] pim sm 
[SwitchA-Vlan-interface102] quit 
[SwitchA] interface loopback 0 
[SwitchA-LoopBack0] pim sm 
[SwitchA-LoopBack0] quit 
The configuration on Switch B, Switch C and Switch D is similar to the configuration on Switch A. 
(Details not shown.)  
# Configure a PIM domain border on Switch C. 
[SwitchC] interface vlan-interface 101 
[SwitchC-Vlan-interface101] pim bsr-boundary 
[SwitchC-Vlan-interface101] quit 
[SwitchC] interface vlan-interface 103 
[SwitchC-Vlan-interface103] pim bsr-boundary 
[SwitchC-Vlan-interface103] quit 
[SwitchC] interface vlan-interface 104 
[SwitchC-Vlan-interface104] pim bsr-boundary 
[SwitchC-Vlan-interface104] quit 
The configuration on Switch A, Switch B and Switch  D is similar to the configuration on Switch C. 
(Details not shown.) 
3.  Configure C-BSRs and C-RPs: 
# Configure Loopback 0 as a C-BSR and a C-RP on Switch A.  
[SwitchA] pim 
[SwitchA-pim] c-bsr loopback 0 
[SwitchA-pim] c-rp loopback 0 
[SwitchA-pim] quit 
The configuration on Switch C and Switch D is similar to the configuration on Switch A. (Details not 
shown.)  
4. Configure MSDP peers: 
# Configure an MSDP peer on Switch A. 
[SwitchA] msdp 
[SwitchA-msdp] peer 192.168.1.2 connect-interface vlan-interface 101 
[SwitchA-msdp] quit 
# Configure MSDP peers on Switch C. 
[SwitchC] msdp 
[SwitchC-msdp] peer 192.168.1.1 connect-interface vlan-interface 101 
[SwitchC-msdp] peer 10.110.5.2 connect-interface vlan-interface 104 
[SwitchC-msdp] quit 
# Configure an MSDP peer on Switch D. 
[SwitchD] msdp 
[SwitchD-msdp] peer 10.110.5.1 connect-interface vlan-interface 104 
[SwitchD-msdp] quit 
5. Configure SA message filtering rules: 
# Configure an SA message rule on Switch C so  that Switch C will not forward SA messages for 
(Source 1, 225.1.1.0/30) to Switch D.  
[SwitchC] acl number 3001
    Add page 1354 to Favourites
    image text
    Enable zoom 
    							 218 
[SwitchC-acl-adv-3001] rule deny ip source 10.110.3.100 0 destination 225.1.1.0 
0.0.0.3 
[SwitchC-acl-adv-3001] rule permit ip source any destination any 
[SwitchC-acl-adv-3001] quit 
[SwitchC] msdp 
[SwitchC-msdp] peer 10.110.5.2 sa-policy export acl 3001 
[SwitchC-msdp] quit 
# Configure an SA message rule on Switch D so that Switch D will not create SA messages for 
Source 2.  
[SwitchD] acl number 2001 
[SwitchD-acl-basic-2001] rule deny source 10.110.6.100 0 
[SwitchD-acl-basic-2001] quit 
[SwitchD] msdp 
[SwitchD-msdp] import-source acl 2001 
[SwitchD-msdp] quit 
6.  Verify the configuration: 
View the (S, G) entries cached in the SA cache on the switches using the  display msdp sa-cache 
command. For example:  
# Display the (S, G) entries cached in the SA cache on Switch C.  
[SwitchC] display msdp sa-cache 
MSDP Source-Active Cache Information of VPN-Instance: public net 
 MSDP Total Source-Active Cache - 8 entries 
 MSDP matched 8 entries 
 
(Source, Group)              Origin RP       Pro  AS     Uptime   Expi\
res 
(10.110.3.100, 225.1.1.0)    1.1.1.1         ?    ?      02:03:30 00:0\
5:31 
(10.110.3.100, 225.1.1.1)    1.1.1.1         ?    ?      02:03:30 00:0\
5:31 
(10.110.3.100, 225.1.1.2)    1.1.1.1         ?    ?      02:03:30 00:0\
5:31 
(10.110.3.100, 225.1.1.3)    1.1.1.1         ?    ?      02:03:30 00:0\
5:31 
(10.110.3.100, 226.1.1.0)    1.1.1.1         ?    ?      02:03:30 00:0\
5:31 
(10.110.3.100, 226.1.1.1)    1.1.1.1         ?    ?      02:03:30 00:0\
5:31 
(10.110.3.100, 226.1.1.2)    1.1.1.1         ?    ?      02:03:30 00:0\
5:31 
(10.110.3.100, 226.1.1.3)    1.1.1.1         ?    ?      02:03:30 00:0\
5:31 
# Display the (S, G) entries cached in the SA cache on Switch D.  
[SwitchD] display msdp sa-cache 
MSDP Source-Active Cache Information of VPN-Instance: public net 
 MSDP Total Source-Active Cache - 4 entries 
 MSDP matched 4 entries 
 
(Source, Group)              Origin RP       Pro  AS     Uptime   Expi\
res 
(10.110.3.100, 226.1.1.0)    1.1.1.1         ?    ?      00:32:53 00:0\
5:07 
(10.110.3.100, 226.1.1.1)    1.1.1.1         ?    ?      00:32:53 00:0\
5:07 
(10.110.3.100, 226.1.1.2)    1.1.1.1         ?    ?      00:32:53 00:0\
5:07 
(10.110.3.100, 226.1.1.3)    1.1.1.1         ?    ?      00:32:53 00:0\
5:07
    Add page 1355 to Favourites
    image text
    Enable zoom 
    							 219 
Troubleshooting MSDP 
MSDP peers stay in down state 
Symptom 
The configured MSDP peers stay in the down state.  
Analysis 
•  A TCP connection–based MSDP peering relationship is established between the local interface 
address and the MSDP peer after the configuration.  
•   The TCP connection setup will fail if the local inte rface address is not consistent with the MSDP peer 
address configured on the peer router.  
•   If no route is available between the MSDP peers, the TCP connection setup will fail.  
Solution 
1. Verify that a route is available between the routers. Use the  display ip routing-table command to 
determine whether the unicast route between the routers is correct.  
2.  Verify that a unicast route is available between  the two routers that will become MSDP peers to 
each other.  
3.  Verify the interface addres s consistency between the MSDP peers. Use the  display 
current-configuration  command to verify that the local interface address and the MSDP peer 
address of the remote router are the same.  
No SA entries in the switch’s SA cache 
Symptom 
MSDP fails to send (S, G) entries through SA messages.  
Analysis 
•   The  import-source  command controls sending (S, G) entries through SA messages to MSDP peers. 
If this command is executed without the  acl-number argument, all the (S, G) entries are filtered out. 
That is, no (S, G) entries of the local domain is advertised.  
•   If the  import-source  command is not executed, the system will advertise all the (S, G) entries of the 
local domain. If MSDP fails to send (S, G) entries through SA messages, verify that the 
import-source  command has been correctly configured.  
Solution 
1. Use the  display ip routing-table  command to verify that the unicast route between the routers is 
correct.  
2.  Verify that a unicast route is available between  the two routers that will become MSDP peers to 
each other.  
3.  Verify the configuration of the  import-source command and its acl-number  argument and be sure 
that ACL rule can filter appropriate (S, G) entries.
    Add page 1356 to Favourites
    image text
    Enable zoom 
    							 220 
Inter-RP communication faults in Anycast RP application 
Symptom 
RPs fail to exchange their locally registered (S, G) entries with one another in the Anycast RP application.   
Analysis 
•  I n  t h e  A nyc a s t  R P  a p p l i c a t i o n,  R Ps  i n  t h e  s a m e  P I M - S M  d o m a i n  a re  c o n fi g u re d  t o  b e  M S D P  p e e r s  t o  
achieve load balancing among the RPs.  
•   An MSDP peer address must be different from the Anycast RP address, and the C-BSR and C-RP must 
be configured on different devices or interfaces.  
•   If the  originating-rp command is executed, MSDP will replace the RP address in the SA messages 
with the address of the interface specified in the command.  
•   When an MSDP peer receives an SA message, it per forms RPF check on the message. If the MSDP 
peer finds that the remote RP address is the same  as the local RP address, it will discard the SA 
message.  
Solution 
1.  Use the  display ip routing-table  command to verify that the unicast route between the routers is 
correct.  
2.  Verify that a unicast route is available between  the two routers that will become MSDP peer to 
each other.  
3.  Verify the configuration of the  originating-rp command. In the Anycast RP application environment, 
b e  s u r e  to  u s e  t h e   originating-rp command to configure the RP addr ess in the SA messages, which 
must be the local interface address.  
4.  Verify that the C-BSR address is diffe rent from the Anycast RP address.
    Add page 1357 to Favourites
    image text
    Enable zoom 
    							 221 
Configuring MBGP (available only on the HP 
5500 EI) 
MBGP overview 
This chapter covers configuration tasks related to multiprotocol BGP for IP multicast only. For more 
information about BGP, see Layer 3—IP Routing Configuration Guide . The term router in this chapter 
refers to both routers and Layer 3 switches. 
BGP-4 can carry routing information for IPv4 only. IETF defined Multiprotocol Border Gateway Protocol 
(MP-BGP) to extend BGP-4 so that BGP can carry routing information for multiple network-layer protocols.   
For a network, the topology for multicast might be different from that for unicast. To distinguish them, the 
MP-BGP enables BGP to carry the unicast Network Layer Reachability Information (NLRI) and multicast 
NLRI separately. The multicast NLRI performs reverse pat h forwarding (RPF) exclusively. In this way, route 
selection for a destination through the unicast routing table and through the multicast routing table have 
different results, ensuring consistent unicast forw arding and normal multicast between domains. For 
more information about RPF, see  Configuring multicast routing and forwarding (available only on the 
HP 5

500 EI) . 
MP-BGP is defined in RFC 2858 (Multiprotocol Extensions for BGP-4). The application of MP-BGP on 
multicast is called Multicast BGP (MBGP). 
Protocols and standards 
•   RFC 2858,  Multiprotocol Extensions for BGP-4  
•   RFC 3392,  Capabilities Advertisement with BGP-4 
•   draft-ietf-idmr-bgp-mcast-attr-00,  BGP Attributes for Multicast Tree Construction  
•   RFC 4271,  A Border Gateway Protocol 4 (BGP-4) 
•   RFC 5291,  Outbound Route Filtering Capability for BGP-4  
•   RFC 5292,  Address-Prefix-Based Outbound Route Filter for BGP-4 
MBGP configuration task list 
 
Task  Remarks 
Configuring basic MBGP functions  Required 
Controlling route 
advertisement and 
reception Configuring MBGP route redistribution 
Required Configuring default route redistribution into MBGP  Optional 
Configuring MBGP route summarization  Optional 
Advertising a default route to an IPv4 MBGP peer or peer group Optional 
Configuring outbound MBGP route filtering Optional
    Add page 1358 to Favourites
    image text
    Enable zoom 
    							 222 
Task  Remarks 
Configuring inbound MBGP route filtering Optional 
Configuring MBGP route dampening Optional 
Configuring MBGP 
route attributes Configuring MBGP route preferences 
Optional 
Configuring the default local preference 
Configuring the MED attribute 
Configuring the next hop attribute 
Configuring the AS-PATH attributes 
Tuning and 
optimizing MBGP 
networks Configuring MBGP soft reset 
Optional Enabling the MBGP ORF capability Optional 
Configuring the maximum number of MBGP routes for load 
balancing Optional 
Configuring a large 
scale MBGP network Configuring IPv4 MBGP peer groups 
Optional Configuring MBGP community  Optional 
Configuring an MBGP route reflector Optional 
 
Configuring basic MBGP functions 
Configuration prerequisites 
Before you configure MBGP, be sure that neighboring nodes can access each other at the network layer. 
Configuration procedure 
To configure basic MBGP functions:  
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter BGP view. 
bgp as-number   N/A 
3.  Specify a peer or peer group 
and its AS number.  peer { group-name
 | ip-address } 
as-number  as-number  Not specified by default. 
4.
  Enter IPv4 MBGP address 
family view.  ipv4-family multicast 
N/A 
5.  Enable a peer or peer group 
created in IPv4 unicast view.  peer 
{ group-name  | ip-address } 
enable  Not enabled by default. 
6.
  Specify a preferred value for 
routes from an IPv4 MBGP 
peer or peer group.  peer 
{ group-name  | ip-address } 
preferred-value  value  Optional. 
The default preferred value is 0.
    Add page 1359 to Favourites
    image text
    Enable zoom 
    							 223 
Controlling route advertisement and reception 
Configuration prerequisites 
You need to configure basic MBGP functions before configuring this task.  
Configuring MBGP route redistribution 
MBGP can advertise routing information in the local AS to neighboring ASs. It redistributes such routing 
information from IGP into its routing table rather than learning the information by itself.  
To configure MBGP route redistribution: 
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter BGP view. 
bgp as-number   N/A 
3.  Enter IPv4 MBGP address 
family view.  ipv4-family multicast 
N/A 
4.  Configure MBGP route 
redistribution.   Enable route redistribution from 
another routing protocol: 
import-route 
protocol [ { process-id  
|  all-processes  } [ allow-direct  | 
med  med-value  |  route-policy 
route-policy-name  ] * ] 
Inject a network into the MBGP 
routing table: 
network  ip-address [ mask  | 
mask-length ] [  short-cut | 
route-policy  route-policy-name  ]  Use either command 
No route redistribution is 
configured by default. 
The 
allow-direct  keyword is 
available only when the specified 
routing protocol is OSPF. 
The Origin attribute of routes 
redistributed into the MBGP routing 
table with the  import-route 
command is Incomplete.  
The Origin attribute of routes 
injected into the MBGP routing 
table with the  network command is 
IGP. 
 
  NOTE: 
The networks to be injected must exist in the local IP routin
g table, and using a routing policy makes route
control more flexible. 
 
Configuring default route redistribution into MBGP 
You cannot use the  import-route command to redistribute any default route into the MBGP routing table. 
This task allows you to redistribute default routes in another way. 
To configure MBGP to redistribute a  default route from another protocol: 
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter BGP view. 
bgp as-number   N/A
    Add page 1360 to Favourites
    image text
    Enable zoom 
    							 224 
Step Command Remarks 
3.  Enter MBGP address family 
view.  ipv4-family multicast 
N/A 
4.  Enable route redistribution 
from another routing protocol.  import-route protocol 
[ { process-id 
|  all-processes  } [ allow-direct  | 
med  med-value  |  route-policy 
route-policy-name  ] * ]  No route redistribution is 
configured by default. 
The 
allow-direct  keyword is 
available only when the specified 
routing protocol is OSPF. 
5.   Enable default route 
redistribution into the MBGP 
routing table.  default-route imported 
Not enabled by default. 
 
Configuring MBGP route summarization 
To reduce the routing table size on medium and large MBGP networks, you need to configure route 
summarization on peers. MBGP supports automatic and manual summarization modes: 
•  Automatic summarization —Summarizes subnets redistributed from IGP. With the feature 
configured, MBGP advertises only summary natural networks rather than subnets. The default 
routes and routes injected with the  network command are not summarized. 
•   Manual summarization —Summarizes MBGP local routes. A manual summary route has a higher 
priority than an automatic one. 
To configure MBGP route summarization: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter BGP view. 
bgp as-number   N/A 
3.  Enter IPv4 MBGP address 
family view.  ipv4-family multicast 
N/A 
4.  Configure MBGP route 
summarization.  Enable automatic route 
summarization: 
summary automatic 
Configure manual route 
summarization: 
aggregate 
ip-address {  mask | 
mask-length }  [  as-set  | 
attribute-policy  route-policy-name  
|  detail-suppressed  | origin-policy 
route-policy-name  | 
suppress-policy  
route-policy-name  ] *  Use either command 
No route summarization is 
configured by default. 
If the two commands are both 
configured, the manual route 
summarization takes effect. 
 
Advertising a default route to an IPv4 MBGP peer or peer 
group
    All HP manuals Comments (0)

    Related Manuals for HP 5500 Ei 5500 Si Switch Series Configuration Guide