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 1321 to Favourites
    image text
    Enable zoom 
    							 185 
[SwitchA-Vlan-interface101] pim sm 
[SwitchA-Vlan-interface101] quit 
[SwitchA] interface vlan-interface 102 
[SwitchA-Vlan-interface102] pim sm 
[SwitchA-Vlan-interface102] quit 
The configuration on Switch B and Switch C is similar to that on Switch A. The configuration on 
Switch D and Switch E is also similar to that on Switch A except that it is not necessary to enable 
IGMP on the corresponding interfaces on these two switches. 
3. Configure the SSM group range: 
# Configure the SSM group range to be 232.1.1.0/24 on Switch A. 
[SwitchA] acl number 2000 
[SwitchA-acl-basic-2000] rule permit source 232.1.1.0 0.0.0.255 
[SwitchA-acl-basic-2000] quit 
[SwitchA] pim 
[SwitchA-pim] ssm-policy 2000 
[SwitchA-pim] quit 
The configuration on Switch B, Switch C, Switch D and Switch E is similar to that on Switch A. 
4. Verify the configuration: 
# Display PIM configuration information on Switch A. 
[SwitchA] display pim interface 
 VPN-Instance: public net 
 Interface           NbrCnt HelloInt   DR-Pri     DR-Address 
 Vlan100             0      30         1          10.110.1.1     (local\
) 
 Vlan101             1      30         1          192.168.1.2 
 Vlan102             1      30         1          192.168.9.2 
Assume that Host A needs to receive the information a specific multicast source S 
(10.110.5.100/24) sends to multicast group G (232 .1.1.1). Switch A builds an SPT toward the 
multicast source. Switches on the  SPT path (Switch A and Switch D) have generated an (S, G) entry, 
but Switch E, which is not on the SPT path, does  not have multicast routing entries. You can use the 
display pim routing-table  command to view the PIM routing table information on each switch. For 
example:  
# Display PIM routing table information on Switch A. 
[SwitchA] display pim routing-table 
 VPN-Instance: public net 
 Total 0 (*, G) entry; 1 (S, G) entry 
 
 (10.110.5.100, 232.1.1.1) 
     Protocol: pim-ssm, Flag: 
     UpTime: 00:13:25 
     Upstream interface: Vlan-interface101 
         Upstream neighbor: 192.168.1.2 
         RPF prime neighbor: 192.168.1.2 
     Downstream interface(s) information: 
     Total number of downstreams: 1 
         1: Vlan-interface100 
             Protocol: igmp, UpTime: 00:13:25, Expires: 00:03:25 
# Display PIM routing table information on Switch D.
    Add page 1322 to Favourites
    image text
    Enable zoom 
    							 186 
[SwitchD] display pim routing-table 
 VPN-Instance: public net 
 Total 0 (*, G) entry; 1 (S, G) entry 
 
 (10.110.5.100, 232.1.1.1) 
     Protocol: pim-ssm, Flag: LOC 
     UpTime: 00:12:05 
     Upstream interface: Vlan-interface300 
         Upstream neighbor: NULL 
         RPF prime neighbor: NULL 
     Downstream interface(s) information: 
     Total number of downstreams: 1 
         1: Vlan-interface105 
             Protocol: pim-ssm, UpTime: 00:12:05, Expires: 00:03:25 
Troubleshooting PIM 
A multicast distribution tree cannot be built correctly 
Symptom 
None of the routers in the network (including routers directly connected with multicast sources and 
receivers) have multicast forwarding entries. That is, a multicast distribution tree cannot be built correctly 
and clients cannot receive multicast data. 
Analysis 
•  When PIM-DM runs on the entire network, mult icast data is flooded from the first hop router 
connected with the multicast source to the last hop router connected with the clients. When the 
multicast data is flooded to a router, regardless of wh ich router it is, the router creates (S, G) entries 
only if it has a route to the multicast source. If the router does not have a route to the multicast source, 
or if PIM-DM is not enabled on the router’s RPF interface to the multicast source, the router cannot 
create (S, G) entries. 
•   When PIM-SM runs on the entire network and when  a router will join the SPT, the router creates (S, 
G) entries only if it has a route to the multicast source. If the router does not have a route to the 
multicast source, or if PIM-DM is not enabled on th e router’s RPF interface to the multicast source, the 
router cannot create (S, G) entries. 
•   When a multicast router receives a multicast packet, it searches the existing unicast routing table for 
the optimal route to the RPF check object. The outgoing interface of this route will act as the RPF 
interface and the next hop will be taken as the RPF  neighbor. The RPF interface completely relies on 
the existing unicast route, and is independent of  PIM. The RPF interface must be PIM-enabled, and 
the RPF neighbor must also be a PIM neighbor. If PIM is not enabled on the router where the RPF 
interface or the RPF neighbor resides, the establishment of a multicast distribution tree will surely fail, 
causing abnormal multicast forwarding. 
•   Because a hello message does not carry the PIM mo de information, a router that is running PIM 
cannot identify what PIM mode its PIM neighbor is running. If different PIM modes are enabled on 
the RPF interface and on the corresponding interface of the RPF neighbor router, the establishment 
of a multicast distribution tree will fail, causing abnormal multicast forwarding. 
•   The same PIM mode must run on the entire network. Otherwise, the establishment of a multicast 
distribution tree will fail, causing abnormal multicast forwarding.
    Add page 1323 to Favourites
    image text
    Enable zoom 
    							 187 
Solution 
1. Use the  display ip routing-table  command to verify that a unicast ro ute exists from the receiver host 
to the multicast source. 
2.  Use the  display pim interface  command to verify that PIM is enabl ed on the interfaces, especially 
on the RPF interface. If PIM is not enabled on the interface, use the  pim dm or pim sm command to 
enable PIM-DM or PIM-SM. 
3.  Use the  display pim neighbor  command to verify that the RPF neighbor is a PIM neighbor. 
4. Verify that PIM and IGMP are enabled on the interf aces directly connecting to the multicast source 
and to the receivers. 
5.  Use the  display pim interface verbose  command to verify that the same PIM mode is enabled on 
the RPF interface and the corresponding interface of the RPF neighbor router. 
6.  Verify that the same PIM mode is enabled on all th e routers in the entire network. Make sure that 
the same PIM mode is enabled on all the routers: PIM-SM on all routers, or PIM-DM on all routers. 
In the case of PIM-SM, also check that th e BSR and RP configurations are correct.  
Multicast data abnormally terminated on an intermediate 
router 
Symptom 
An intermediate router can receive multicast data su ccessfully, but the data cannot reach the last hop 
router. An interface on the intermediate router receiv es data but no corresponding (S, G) entry is created 
in the PIM routing table. 
Analysis 
•   If a multicast forwarding boundary has been configured through the  multicast boundary command, 
any multicast packet will be kept from crossing th e boundary, and no routing entry can be created 
in the PIM routing table. 
•   In addition, the  source-policy command filters received multicast packets. If the multicast data fails 
to pass the ACL rule defined in this command, PIM cannot create the route entry either. 
Solution 
1.  Use the  display current-configuration  command to verify the multicast forwarding boundary 
settings. Use the  multicast boundary  command to change the multicast forwarding boundary 
settings. 
2.  Use the  display current-configuration  command to verify the multicas t filter configuration. Change 
the ACL rule defined in the  source-policy command so that the source/group address of the 
multicast data can pass ACL filtering. 
RPs cannot join SPT in PIM-SM 
Symptom 
An RPT cannot be established correctly, or the  RPs cannot join the SPT to the multicast source.
    Add page 1324 to Favourites
    image text
    Enable zoom 
    							 188 
Analysis 
•  As the core of a PIM-SM domain, the RPs serve specific multicast groups. Multiple RPs can coexist 
in a network. Make sure that the RP information on all routers is exactly the same and that a specific 
group is mapped to the same RP. Otherwise, multicast forwarding will fail. 
•   If the static RP mechanism is used, the same static RP command must be executed on all the routers 
in the entire network. Otherwise, multicast forwarding will fail. 
Solution 
1. Use the  display ip routing-table command to verify that a route is available on each router to the 
RP. 
2.  Use the  display pim rp-info  command to verify that the RP inform ation is consistent on all routers. 
3. Use the  display pim rp-info  command to verify that the same static RP address has been configured 
on all the routers in the entire network. 
RPT establishment failure or source registration failure in 
PIM-SM 
Symptom 
C-RPs cannot unicast advertise messages to the BS R. The BSR does not advertise bootstrap messages 
containing C-RP information and has no unicast route to  any C-RP. An RPT cannot be established correctly, 
or the DR cannot perform source registration with the RP. 
Analysis 
•   The C-RPs periodically send C-RP-Adv messages to th e BSR by unicast. If a C-RP has no unicast route 
to the BSR, the BSR cannot receive C-RP-Adv messages from that C-RP and the bootstrap message 
of the BSR will not contain the information of that C-RP.  
•   In addition, if the BSR does not have a unicast route to a C-RP, it will discard the C-RP-Adv messages 
from that C-RP, and therefore the bootstrap messag es of the BSR will not contain the information of 
that C-RP. 
•   The RP is the core of a PIM-SM domain. Make sure that the RP information on all routers is exactly 
the same, a specific group G is mapped to the same RP, and unicast routes are available to the RP. 
Solution 
1. Use the  display ip routing-table  command to verify that routes are available on each router to the 
RP and the BSR and whether a route is available between the RP and the BSR. Make sure that each 
C-RP has a unicast route to the BSR, the BSR has  a unicast route to each C-RP, and all the routers 
in the entire network have a unicast route to the RP. 
2.  PIM-SM needs the support of the RP and BSR. Use the  display pim bsr-info command to verify that 
the BSR information is available on each router, and then use the  display pim rp-info command to 
verify that the RP information is correct. 
3.  Use the  display pim neighbor  command to verify that the norm al PIM neighboring relationships 
have been established among the routers.
    Add page 1325 to Favourites
    image text
    Enable zoom 
    							 189 
Configuring MSDP (available only on the HP 
5500 EI) 
Overview 
Multicast source discovery protocol (MSDP) is an inter-domain multicast solution that addresses the 
interconnection of protocol independent multicast s parse mode (PIM-SM) domains. You can use it to 
discover multicast source information in other PIM-SM domains. 
In the basic PIM-SM mode, a multicast source registers only with the RP in the local PIM-SM domain, and 
the multicast source information about a domain is isol ated from that of another domain. As a result, the 
RP obtains the source information only within the loca l domain, and a multicast distribution tree is built 
only within the local domain to deliver multicast data from a local multicast source to local receivers. 
MSDP enables the RPs of different PIM-SM domains to share their multicast source information, so that the 
local RP can join multicast sources in other domains, and multicast data can be transmitted among 
different domains.  
With MSDP peer relationships established between  appropriate routers in the network, the RPs of 
different PIM-SM domains are interconnected with  one another. These MSDP peers exchange source 
active (SA) messages, so that the multicast source information is shared among these different domains.  
 
  NOTE: 
•  MSDP is applicable only if the intra-domain multicast protocol is PIM-SM. 
•   MSDP is meaningful only for the any-source multicast (ASM) model. 
 
For more information about the concepts of desi gnated router (DR), bootstrap router (BSR), 
candidate-BSR (C-BSR), rendezvous point (RP), candidate-RP (C-RP), shortest path tree (SPT) and 
rendezvous point tree (RPT) mentioned in this document, see  Configuring PIM (available only on the HP 
5

500 EI)  
The term router in this document refers to both routers and Layer 3 switches. 
The term interface in the MSDP features refers to Layer 3 interfaces, including VLAN interfaces and 
route-mode (or Layer 3) Ethernet ports. You can set an  Ethernet port to operate in route mode by using the 
port  link-mode  route  command (see  Layer 2—LAN Switching Configuration Guide ). 
How MSDP works 
MSDP peers 
Configuring one or more pairs of MSDP peers in the network forms an MSDP interconnection map, 
where the RPs of different PIM-SM domains are intercon nected in series. An SA message that an RP sends 
and that these MSDP peers relay can be delivered to all other RPs.
    Add page 1326 to Favourites
    image text
    Enable zoom 
    							 190 
Figure 56 Where MSDP peers are in the network 
 
 
As shown in Figure 56, an M SDP peer can be created on any PIM-SM router. MSDP peers created on 
PIM-SM routers that assume different roles function differently.  
1.  MSDP peers on RPs include the following types: 
{  Source-side MSDP peer —The MSDP peer nearest to the multicast source (Source), typically the 
source-side RP, like RP 1. The source-side RP creates SA messages and sends the messages to 
its remote MSDP peer to notify the MSDP peer of the locally registered multicast source 
information. A source-side MSDP peer must be created on the source-side RP. Otherwise it will 
not be able to advertise the multicast source information out of the PIM-SM domain.  
{  Receiver-side  MSDP peer —The MSDP peer nearest to the receivers, typically the receiver-side 
R P,  l i k e  R P  3.  A f t e r  r e c e i vi n g  a n  SA  m e s s a g e ,  t h e  r e c e i v e r - s i d e  M S D P  p e e r  r e s o l ve s  t h e  m u l t i c a s t  
source information carried in the message and jo ins the SPT rooted at the source across the 
PIM-SM domain. When multicast data from the multicast source arrives, the receiver-side MSDP 
peer forwards the data to the receivers along the RPT.  
{  Intermediate  MSDP  peer —An MSDP peer with multicast remote MSDP peers, like RP 2. An 
i n t e rm e d i a t e  MS D P  p e e r  fo r wa rd s  SA  m e s s a g e s  re c eive d  f ro m  o n e  re m o t e  MS D P  p e e r  t o  o t h e r  
remote MSDP peers, functioning as a relay of multicast source information.  
2.  MSDP peers created on common PIM-SM routers (other than RPs)  
Router A and Router B are MSDP peers on commo n multicast routers. Such MSDP peers just 
forward received SA messages.  
In a PIM-SM network running the BSR mechanism, the RP is dynamically elected from C-RPs. To enhance 
network robustness, a PIM-SM network typically has mo re than one C-RP. As the RP election result is 
unpredictable, MSDP peering relationships must be  built among all C-RPs so that the winner C-RP is 
always on the MSDP interconnection map, and lo ser C-RPs will assume the role of common PIM-SM 
routers on the MSDP interconnection map.  
Inter-domain multicast delivery through MSDP 
As shown in Figure 57 , an active source (Source) exists in the domain PIM-SM 1, and RP 1 has learned 
the existence of Source through multicast source registration. If RPs in PIM-SM 2 and PIM-SM 3 also seek 
the specific location of Source so that receiver hosts can receive multicast traffic that the source sends, HP 
recommends you to establish MSDP  peering relationships between RP 1 and RP 3 and between RP 3 and 
RP 2, respectively.
    Add page 1327 to Favourites
    image text
    Enable zoom 
    							 191 
Figure 57 Inter-domain multicast delivery through MSDP 
 
 
The process of implementing PIM-SM inter-domain multicast delivery by leveraging MSDP peers is as 
follows:  
1. When the multicast source in PIM-SM 1 sends the first multicast packet to  multicast group G, DR 1 
encapsulates the multicast data within a register  message and sends the register message to RP 1. 
Then, RP 1 identifies the information related to the multicast source.  
2.  As the source-side RP, RP 1 creates SA messages  and periodically sends the SA messages to its 
MSDP peer. An SA message contai ns the source address (S), the multicast group address (G), and 
the address of the RP that has create d this SA message (namely, RP 1). 
3. On MSDP peers, each SA message undergoe s a reverse path forwarding (RPF) check and 
multicast policy–based filtering, so that only SA  messages that have arrived along the correct path 
and passed the filtering are received and forwarded.  This avoids delivery loops of SA messages. 
In addition, you can configure MSDP peers into an  MSDP mesh group so as to avoid flooding of 
SA messages between MSDP peers.  
An MSDP mesh group refers to a group of MSDP  peers that have MSDP peering relationships 
among one another and share the same group name.  
4.  SA messages are forwarded from one MSDP peer to  another, and finally the information about the 
multicast source traverses all PIM-SM domains with  MSDP peers (PIM-SM 2 and PIM-SM 3, in this 
example).  
5.  After receiving the SA message that RP 1 create d, RP 2 in PIM-SM 2 determines whether any 
receivers for the multicast gr oup exist in the domain.  
{ If receivers for the multicast group exist in the domain, the RPT for the multicast group G is 
maintained between RP 2 and the receivers. RP  2 creates an (S, G) entry and sends an (S, G) 
join message hop by hop toward DR 1 at the multicast source side, so that it can directly join 
the SPT rooted at the source over other PIM- SM domains. Then, the multicast data can flow 
along the SPT to RP 2 and RP 2 can forward the data to the receivers along the RPT. After 
receiving the multicast traffic, the DR at the receiver side (DR 2) determines whether to initiate 
an RPT-to-SPT switchover process.
    Add page 1328 to Favourites
    image text
    Enable zoom 
    							 192 
{ If no receivers for the group exist in the domain, RP 2 neither creates an (S, G) entry nor joins 
the SPT rooted at the source.  
 
  NOTE: 
When using MSDP for inter-domain multicasting, once an RP receives information form a multicast source,
it no longer relies on RPs in other PIM-SM domains.  The receivers can override the RPs in other domains
and directly join the multicast source-based SPT.  
 
RPF check rules for SA messages 
As shown in Figure 58 , the autonomous systems in the network are AS 1 through AS 5, with IGP enabled 
on routers within each AS and BGP or MBGP as the interoperation protocol among different ASs. Each 
AS contains at least one PIM-SM domain, and each  PIM-SM domain contains one or more RPs. MSDP 
peering relationships have been established among different RPs. RP 3, RP 4, and RP 5 are in an MSDP 
mesh group. On RP 7, RP 6 is configured as its static RPF peer.  
 
  NOTE: 
When an RP receives an SA message from a static RPF peer, the RP accepts the SA message and forwards
it to other peers without performing an RPF check. 
 
Figure 58  Diagram for RPF check for SA messages 
 
 
As shown in Figure 58, these MSDP peers dispose of SA messages according to the following RPF check 
rules:  
1.  When RP 2 receives an SA message from RP 1:  
Because the source-side RP address carried in th e SA message is the same as the MSDP peer 
address, which means that the MSDP peer where the SA is from is the RP that has created the SA 
message, RP 2 accepts the SA message and forw ards it to its other MSDP peer (RP 3).  
2. When RP 3 receives the SA message from RP 2:  
Because the SA message is from an MSDP peer (RP 2) in the same AS, and the MSDP peer is the 
next hop on the optimal path to the source-side RP , RP 3 accepts the message and forwards it to 
other peers (RP 4 and RP 5).  
3.  When RP 4 and RP 5 receive the SA message from RP 3:
    Add page 1329 to Favourites
    image text
    Enable zoom 
    							 193 
B e c a u s e  t h e  S A  m e s s a g e  i s  f r o m  a n  M S D P  p e e r  ( R P  3 )  i n  t h e  s a m e  m e s h  g r o u p ,  R P  4  a n d  R P  5  b o t h  
accept the SA message, but they do not forward the message to other members in the mesh group. 
Instead, they forward it to other MSDP peers (R P 6 in this example) out of the mesh group.  
4. When RP 6 receives the SA messages from RP 4  and RP 5 (suppose RP 5 has a higher IP address): 
Although RP 4 and RP 5 are in the same AS (AS 3) and both are MSDP peers of RP 6, because RP 
5 has a higher IP address, RP 6 accepts only the SA message from RP 5.  
5.  When RP 7 receives the SA message from RP 6:  
Because the SA message is from a static RPF peer (RP 6), RP 7 accepts the SA message and 
forwards it to other peer (RP 8).  
6. When RP 8 receives the SA message from RP 7:  
A BGP or MBGP route exists between two MSDP peers in different ASs. Because the SA message 
is from an MSDP peer (RP 7) in a different AS,  and the MSDP peer is the next hop on the BGP or 
MBGP route to the source-side RP, RP 8 accepts the message and forwards it to its other peer (RP 
9).  
7.  When RP 9 receives the SA message from RP 8:  
Because RP 9 has only one MSDP peer, RP 9 accepts the SA message.  
SA messages from paths other than those described  previously are not accepted or forwarded by MSDP 
peers.  
Intra-domain Anycast RP through MSDP 
Anycast RP refers to an application that enables load balancing and redundancy backup between two 
or more RPs within a PIM-SM domain by configuring the same IP address for, and establishing MSDP 
peering relationships between, these RPs.  
Usually an Anycast RP address is configured on a lo gic interface, like a loopback interface. An MSDP 
peer address must be different from the Anycast RP address. 
Be sure to configure a 32-bit subnet mask (255.255.255.255) for the Anycast RP address sure, which 
means configure the Anycast RP address into a host address. 
As shown in  Figure 59, w
 ithin a PIM-SM domain, a multicast source sends multicast data to multicast 
group G, and Receiver is a member of the multicast group. To implement Anycast RP, configure the same 
IP address (known as Anycast RP address, typically a private address) on Router A and Router B, 
configure these interfaces as C-RPs, and establish an MSDP peering relationship between Router A and 
Router B.  
Figure 59  Intra-domain Anycast RP through MSDP
    Add page 1330 to Favourites
    image text
    Enable zoom 
    							 194 
The work process of Anycast RP is as follows: 
1. The multicast source registers with the nearest RP. In  this example, Source registers with RP 1, with 
its multicast data encapsulated in the register me ssage. When the register message arrives at RP 
1, RP 1 de-encapsul ates the message.  
2. Receivers send join messages to the nearest RP to join  i n  t h e  R P T  r o o t e d  a s  t h i s  R P .  I n  t h i s  e x a m p l e ,  
Receiver joins the RPT rooted at RP 2.  
3.  RPs share the registered multicast information by  means of SA messages. In this example, RP 1 
creates an SA message and sends it to RP 2, with  the multicast data from Source encapsulated in 
the SA message. When the SA message reaches  RP 2, RP 2 de-encapsulates the message.  
4. Receivers receive the multicast data along the RPT an d directly join the SPT rooted at the multicast 
source. In this example, RP 2 forwards the mult icast data down the RPT. When Receiver receives 
the multicast data from Source, it direct ly joins the SPT rooted at Source.  
The significance of Anycast RP is as follows: 
•   Optimal RP path —A multicast source registers with the nearest RP so that an SPT with the optimal 
path is built. A receiver joins the nearest RP so that an RPT with the optimal path is built. 
•   Load balancing between RPs —Each RP maintains just part of the source/group information within 
the PIM-SM domain and forward part of the multicast data, thereby achieving load balancing 
between different RPs.  
•   Redundancy backup between RPs —When an RP fails, the multicast source that previously 
re g istere d wi th the  R P  or  the  re c eivers  that previously joi ne d the  R P  wi l l  re g ister  wi th or  joi n anothe r  
nearest RP, thereby achieving redundancy backup between RPs.  
MSDP support for VPNs 
The interfaces on the multicast routers in a VPN can set up MSDP peering relationships between each 
other. By exchanging SA messages between MSDP peers, multicast transmission in a VPN between 
different PIM-SM domains can be implemented.  
To support MSDP for VPNs, a multicast router that  runs MSDP maintains an independent set of MSDP 
mechanism for each VPN that it supports, including SA cache, peering connection, timers, sending 
cache, and cache for exchanging PIM messages. The in formation in one VPN is isolated from another, 
and MSDP and PIM-SM messages can be ex changed only within the same VPN.  
Protocols and standards 
•  RFC 3618,  Multicast Source Discovery Protocol (MSDP)  
•   RFC 3446,  Anycast Rendezvous Point (RP) mechanism us ing Protocol Independent Multicast (PIM) 
and Multicast Source Discovery Protocol (MSDP)  
MSDP configuration task list 
 
Task Remarks 
Configuring basic MSDP 
functions Enabling MSDP 
Required Creating an MSDP peer connection Required 
Configuring a static RPF peer Optional 
Configuring an MSDP peer Configuring MSDP peer description 
Optional
    All HP manuals Comments (0)

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