HP 5500 Ei 5500 Si Switch Series Configuration Guide
Here you can view all the pages of manual HP 5500 Ei 5500 Si Switch Series Configuration Guide. The HP manuals for Printer are available online for free. You can easily download all the documents as PDF.
Page 1321
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...
Page 1322
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...
Page 1323
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...
Page 1324
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...
Page 1325
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...
Page 1326
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...
Page 1327
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...
Page 1328
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...
Page 1329
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...
Page 1330
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...