HP MSR Router Series IP Multicast Configuration Guide(V7) Part number: 5998-5679 Software version: CMW710-R0106 Document version: 6PW100-20140607
Legal and notice information © Copyright 2014 Hewlett-Packard Development Company, L.P. No part of this documentation may be reproduced or transmitted in any form or by any means without prior written consent of Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Contents Multicast overview ······················································································································································· 1 Introduction to multicast ···················································································································································· 1 Information transmission techniques ·····················································································································
Group policy and simulated joining configuration example ············································································ 31 Static port configuration example ······················································································································· 33 IGMP snooping querier configuration example ································································································· 36 Troubleshooting IGMP snooping ···········································
Basic IGMP functions configuration examples ··································································································· 68 IGMP SSM mapping configuration example ····································································································· 71 IGMP proxying configuration example ··············································································································· 74 Troubleshooting IGMP ·················································
PIM-DM configuration example ························································································································· 115 PIM-SM non-scoped zone configuration example ··························································································· 119 PIM-SM admin-scoped zone configuration example ······················································································· 122 BIDIR-PIM configuration example··············································
Configuration prerequisites ································································································································ 184 Enabling IP multicast routing in a VPN instance ······························································································ 184 Creating the MD for a VPN instance ················································································································ 185 Specifying the default-group address ···············
MLD snooping querier configuration example ································································································· 241 Troubleshooting MLD snooping ·································································································································· 244 Layer 2 multicast forwarding cannot function ·································································································· 244 IPv6 multicast group filter does not work ·············
IPv6 PIM-SM overview ········································································································································ 277 IPv6 BIDIR-PIM overview ····································································································································· 284 IPv6 administrative scoping overview ··············································································································· 287 IPv6 PIM-SSM overview ·············
An RPT cannot be built or IPv6 multicast source registration fails in IPv6 PIM-SM ······································· 335 Support and other resources ·································································································································· 336 Contacting HP ······························································································································································ 336 Subscription service ························
Multicast overview Introduction to multicast As a technique that coexists with unicast and broadcast, the multicast technique effectively addresses the issue of point-to-multipoint data transmission. By enabling high-efficiency point-to-multipoint data transmission over a network, multicast greatly saves network bandwidth and reduces network load. By using multicast technology, a network operator can easily provide bandwidth-critical and time-critical information services.
Unicast is not suitable for batch transmission of information. Broadcast In broadcast transmission, the information source sends information to all hosts on the subnet, even if some hosts do not need the information. Figure 2 Broadcast transmission In Figure 2, assume that only Host B, Host D, and Host E need the information. If the information is broadcast to the subnet, Host A and Host C also receive it.
Figure 3 Multicast transmission The multicast source sends only one copy of the information to a multicast group. Host B, Host D, and Host E, which are information receivers, must join the multicast group. The routers on the network duplicate and forward the information based on the distribution of the group members. Finally, the information is correctly delivered to Host B, Host D, and Host E.
For a better understanding of the multicast concept, you can compare multicast transmission to the transmission of TV programs. Table 1 Comparing TV program transmission and multicast transmission TV program transmission Multicast transmission A TV station transmits a TV program through a channel. A multicast source sends multicast data to a multicast group. A user tunes the TV set to the channel. A receiver joins the multicast group.
Multicast models Based on how the receivers treat the multicast sources, the multicast models include any-source multicast (ASM), source-filtered multicast (SFM), and source-specific multicast (SSM). ASM model In the ASM model, any sender can send information to a multicast group as a multicast source. Receivers can join a multicast group identified by a group address and get multicast information addressed to that multicast group.
Multicast addresses IP multicast addresses • IPv4 multicast addresses: IANA assigned the Class D address block (224.0.0.0 to 239.255.255.255) to IPv4 multicast. Table 2 Class D IP address blocks and description Address block Description 224.0.0.0 to 224.0.0.255 Reserved permanent group addresses. The IP address 224.0.0.0 is reserved. Other IP addresses can be used by routing protocols and for topology searching, protocol maintenance, and so on. Table 3 lists common permanent group addresses.
Address Description 224.0.0.13 All Protocol Independent Multicast (PIM) routers. 224.0.0.14 RSVP encapsulation. 224.0.0.15 All Core-Based Tree (CBT) routers. 224.0.0.16 Designated SBM. 224.0.0.17 All SBMs. 224.0.0.18 VRRP. IPv6 multicast addresses: • Figure 4 IPv6 multicast format The following describes the fields of an IPv6 multicast address: { 0xFF—If the most significant eight bits are 11111111, this address is an IPv6 multicast address. { Flags—The Flags field contains four bits.
Table 5 Values of the Scope field Value Meaning 0, F Reserved. 1 Interface-local scope. 2 Link-local scope. 3 Subnet-local scope. 4 Admin-local scope. 5 Site-local scope. 6, 7, 9 through D Unassigned. 8 Organization-local scope. E Global scope. { Group ID—The Group ID field contains 112 bits. It uniquely identifies an IPv6 multicast group in the scope that the Scope field defines.
Figure 7 IPv6-to-MAC address mapping IMPORTANT: Because of the duplicate mapping from multicast IP address to multicast MAC address, the device might inadvertently send multicast protocol packets as multicast data in Layer 2 forwarding. To avoid this, do not use the IP multicast addresses that are mapped to multicast MAC addresses 0100-5E00-00xx and 3333-0000-00xx (where "x" represents any hexadecimal number from 0 to F).
Figure 8 Positions of Layer 3 multicast protocols • Multicast group management protocols: IGMP and MLD protocol are multicast group management protocols. Typically, they run between hosts and Layer 3 multicast devices that directly connect to the hosts to establish and maintain multicast group memberships. • Multicast routing protocols: A multicast routing protocol runs on Layer 3 multicast devices to establish and maintain multicast routes and correctly and efficiently forward multicast packets.
Multicast packet forwarding mechanism In a multicast model, receiver hosts of a multicast group are usually located at different areas on the network. They are identified by the same multicast group address. To deliver multicast packets to these receivers, a multicast source encapsulates the multicast data in an IP packet with the multicast group address as the destination address.
• The P device belongs to the public network. The CE devices belong to their respective VPNs. Each CE device serves its own VPN and maintains only one set of forwarding mechanisms. • The PE devices connect to the public network and the VPNs. Each PE device must strictly distinguish the information for different networks, and maintain a separate forwarding mechanism for each network. On a PE device, a set of software and hardware that serve the same network forms an instance.
Configuring IGMP snooping In this chapter, "MSR2000" refers to MSR2003. "MSR3000" collectively refers to MSR3012, MSR3024, MSR3044, MSR3064. "MSR4000" collectively refers to MSR4060 and MSR4080. Overview IGMP snooping runs on a Layer 2 switch as a multicast constraining mechanism to improve multicast forwarding efficiency. It creates Layer 2 multicast forwarding entries from IGMP packets that are exchanged between the hosts and the router.
Figure 11 IGMP snooping related ports The following describes the ports involved in IGMP snooping: • Router port—Layer 3 multicast device-side port. Layer 3 multicast devices include DRs and IGMP queriers. In Figure 11, GigabitEthernet 1/0/1 of Switch A and GigabitEthernet 1/0/1 of Switch B are the router ports. A Layer 2 device records all its router ports in a router port list. Do not confuse the "router port" in IGMP snooping with the "routed interface" commonly known as the "Layer 3 interface.
NOTE: In IGMP snooping, only dynamic ports age out. Static ports never age out. How IGMP snooping works The ports in this section are dynamic ports. For information about how to configure and remove static ports, see "Configuring static ports." IGMP messages types include general query, IGMP report, and leave message. An IGMP snooping-enabled Layer 2 device performs differently depending on the message types.
Leave message An IGMPv1 host does not send any leave messages when it leaves a multicast group. The Layer 2 device cannot immediately update the status of the port that connects to the receiver host. The Layer 2 device does not remove the port from the outgoing interface list in the associated forwarding entry until the aging time for the group expires. For a static member port, this mechanism does not take effect.
Task at a glance • (Optional.) Specifying the IGMP snooping version • (Optional.) Setting the maximum number of IGMP snooping forwarding entries Configuring IGMP snooping port functions: • • • • • (Optional.) Setting aging timers for dynamic ports (Optional.) Configuring static ports (Optional.) Configuring a port as a simulated member host (Optional.) Enabling IGMP snooping fast-leave processing (Optional.
Step Command Remarks 2. Enable IGMP snooping globally and enter IGMP-snooping view. igmp-snooping By default, IGMP snooping is disabled. 3. Enable IGMP snooping for specified VLANs. enable vlan vlan-list By default, IGMP snooping is disabled for a VLAN. To enable IGMP snooping for a VLAN in VLAN view: Step Command Remarks 4. Enter system view. system-view N/A 5. Enable IGMP snooping globally and enter IGMP-snooping view. igmp-snooping By default, IGMP snooping is disabled. 6.
To specify the IGMP snooping version for a VLAN in VLAN view: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VLAN view. vlan vlan-id N/A 3. Specify the version of IGMP snooping. igmp-snooping version version-number The default setting is IGMPv2 snooping. Setting the maximum number of IGMP snooping forwarding entries You can modify the maximum number of IGMP snooping forwarding entries.
Setting the aging timers for dynamic ports globally Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IGMP-snooping view. igmp-snooping N/A 3. Set the aging timer for dynamic router ports globally. router-aging-time interval The default setting is 260 seconds. 4. Set the global aging timer for dynamic member ports globally. host-aging-time interval The default setting is 260 seconds. Setting the aging timers for the dynamic ports in a VLAN Step Command Remarks 1.
Step Command Remarks 4. Configure the port as a static router port. igmp-snooping static-router-port vlan vlan-id By default, a port is not a static router port. Configuring a port as a simulated member host Generally, a host that runs IGMP can respond to IGMP queries. If a host fails to respond, the multicast router might consider that no member of this multicast group exists on the subnet, and removes the corresponding forwarding path.
• You can enable IGMP snooping fast-leave processing either for the current port in interface view or globally for all ports in IGMP-snooping view. If the configurations are made both in interface view and IGMP-snooping view, the configuration made in interface view takes priority. Enabling IGMP snooping fast-leave processing globally Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IGMP-snooping view. igmp-snooping N/A 3. Enable IGMP snooping fast-leave processing globally.
Configuring an IGMP snooping querier This section describes how to configure an IGMP snooping querier. Configuration prerequisites Before you configure an IGMP snooping querier, complete the following tasks: • Enable IGMP snooping for the VLAN. • Determine the interval for sending IGMP general queries. • Determine the IGMP last member query interval. • Determine the maximum response time for IGMP general queries.
You can configure parameters for IGMP queries and responses for the current VLAN in VLAN view or globally for all VLANs in IGMP-snooping view. If the configurations are made in both VLAN view and IGMP-snooping view, the configuration made in VLAN view takes priority. Configuring the global parameters for IGMP queries and responses Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IGMP-snooping view. igmp-snooping N/A 3. Set the maximum response time for IGMP general queries.
To avoid this problem, when a Layer 2 device acts as the IGMP snooping querier, you can configure a non-all-zero IP address as the source IP address of IGMP queries. You can also change the source IP address of IGMP messages sent by a simulated member host or an IGMP snooping proxy. Changing the source address of IGMP queries might affect the IGMP querier election within the subnet. To configure source IP addresses for IGMP messages: Step Command Remarks 1. Enter system view. system-view N/A 2.
Setting the 802.1p precedence for IGMP messages in a VLAN Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VLAN view. vlan vlan-id N/A 3. Set the 802.1p precedence for IGMP messages in the VLAN. igmp-snooping dot1p-priority priority-number The default setting is 0. Configuring IGMP snooping policies Before you configure IGMP snooping policies, complete the following tasks: • Enable IGMP snooping for the VLAN. • Determine the ACL used as the multicast group filter.
Configuring multicast source port filtering This feature is supported on the following hardware: MSR routers installed with the Layer 2 switching module HMIM 24GSW, HMIM 24GSW-POE, HMIM 8GSW. When the multicast source port filtering feature is enabled on a port, the port blocks all multicast data packets, but it permits multicast protocol packets to pass. You can connect the port to multicast receivers but not to multicast sources.
• If the function of dropping unknown multicast data is enabled, the Layer 2 device drops all received unknown multicast data. To enable dropping unknown multicast data for a VLAN: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VLAN view. vlan vlan-id N/A 3. Enable dropping unknown multicast data for the VLAN. igmp-snooping drop-unknown By default, the dropping unknown multicast data feature is disabled. Unknown multicast data is flooded.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter Layer 2 Ethernet interface view. interface interface-type interface-number N/A 3. Set the maximum number of multicast groups on a port. igmp-snooping group-limit limit [ vlan vlan-list ] The default setting is 4294967295.
Displaying and maintaining IGMP snooping Execute display commands in any view and reset commands in user view. Task Command Display IGMP snooping status. display igmp-snooping [ global | vlan vlan-id ] Display information about dynamic IGMP snooping forwarding entries (MSR2000/MSR3000). display igmp-snooping group [ group-address | source-address ] * [ vlan vlan-id ] [ verbose ] Display information about dynamic IGMP snooping forwarding entries (MSR4000).
Task Command Remove the dynamic IGMP snooping forwarding entries for the specified multicast groups. reset igmp-snooping group { group-address [ source-address ] | all } [ vlan vlan-id ] Remove dynamic router ports. reset igmp-snooping router-port { all | vlan vlan-id } Clear statistics for the IGMP messages learned by IGMP snooping.
[RouterA] multicast routing [RouterA-mrib] quit # Enable IGMP on GigabitEthernet 2/1/1. [RouterA] interface gigabitethernet 2/1/1 [RouterA-GigabitEthernet2/1/1] igmp enable [RouterA-GigabitEthernet2/1/1] quit # Enable PIM-DM on GigabitEthernet 2/1/2. [RouterA] interface gigabitethernet 2/1/2 [RouterA-GigabitEthernet2/1/2] pim dm [RouterA-GigabitEthernet2/1/2] quit 3. Configure Switch A: # Enable IGMP snooping globally.
(0.0.0.0, 224.1.1.1) Host slots (0 in total): Host ports (2 in total): GE2/1/3 (00:03:23) GE2/1/4 (00:04:10) The output shows the following information: • Host A and Host B have joined the multicast group 224.1.1.1 through the member ports Ethernet 1/4 and Ethernet 1/3 on Switch A, respectively. • Host A and Host B have failed to join the multicast group 224.2.2.2. Static port configuration example Network requirements As shown in Figure 13: • Router A runs IGMPv2 and serves as the IGMP querier.
Figure 13 Network diagram Switch B /1 2/1 GE Source GE2/1/2 1.1.1.2/24 GE2/1/1 10.1.1.1/24 Switch A GE2/1/1 1.1.1.1/24 Router A IGMP querier /2 2/1 GE GE 2/1 /3 GE 1/0 /1 Switch C /5 2/1 GE Host C Receiver VLAN 100 GE 2/1 /3 Host A Receiver Host B Configuration procedure 1. Assign an IP address and subnet mask to each interface according to Figure 13. (Details not shown.) 2. Configure Router A: # Enable IP multicast routing.
[SwitchA-vlan100] quit # Configure GigabitEthernet 2/1/3 as a static router port. [SwitchA] interface gigabitethernet 2/1/3 [SwitchA-GigabitEthernet2/1/3] igmp-snooping static-router-port vlan 100 [SwitchA-GigabitEthernet2/1/3] quit 4. Configure Switch B: # Enable IGMP snooping globally. system-view [SwitchB] igmp-snooping [SwitchB-igmp-snooping] quit # Create VLAN 100, assign GigabitEthernet 2/1/1 and GigabitEthernet 2/1/2 to the VLAN, and enable IGMP snooping for the VLAN.
Total 1 entries. VLAN 100: Total 1 entries. (0.0.0.0, 224.1.1.1) Host slots (0 in total): Host ports (2 in total): GE2/1/3 GE2/1/5 The output shows that GigabitEthernet 2/1/3 and GigabitEthernet 2/1/5 on Switch C have become static member ports of the multicast group 224.1.1.1. IGMP snooping querier configuration example Network requirements As shown in Figure 14: • The network is a Layer 2-only network. • Source 1 and Source 2 send multicast data to the multicast groups 224.1.1.1 and 225.1.1.
system-view [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 100, assign GigabitEthernet 2/1/1 through GigabitEthernet 2/1/3 to the VLAN, and enable IGMP snooping and dropping unknown multicast packets for the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 2/1/1 to gigabitethernet 2/1/3 [SwitchA-vlan100] igmp-snooping enable [SwitchA-vlan100] igmp-snooping drop-unknown # Configure Switch A as the IGMP snooping querier.
[SwitchD-vlan100] igmp-snooping drop-unknown [SwitchD-vlan100] quit Verifying the configuration # Display statistics for IGMP messages learned by IGMP snooping on Switch B.
Analysis • The ACL is incorrectly configured. • The multicast group filter is not correctly applied. • The function of dropping unknown multicast data is not enabled, so unknown multicast data is flooded. 1. Use the display acl command to verify that the configured ACL meets the multicast group filter requirements. 2. Use the display this command in IGMP-snooping view or in a corresponding interface view to verify that the correct multicast group filter has been applied.
Configuring multicast routing and forwarding In this chapter, "MSR2000" refers to MSR2003. "MSR3000" collectively refers to MSR3012, MSR3024, MSR3044, MSR3064. "MSR4000" collectively refers to MSR4060 and MSR4080. Overview The following tables are involved in multicast routing and forwarding: • Multicast routing table of each multicast routing protocol, such as the PIM routing table.
{ If the router uses the longest prefix match principle, the router selects the matching route as the RPF route. If the routes have the same mask, the router selects the route that has the highest priority as the RPF route. If the routes have the same priority, the router selects a route as the RPF route in the order of static multicast route, MBGP route, and unicast route. For more information about the route preference, see Layer 3—IP Routing Configuration Guide.
Figure 15 RPF check process IP Routing Table on Router C Destination/Mask Interface 192.168.0.0/24 GE1/0/2 Router B Receiver GE1/0/1 Source 192.168.0.1/24 Router A GE1/0/2 Multicast packets GE1/0/1 Receiver Router C As shown in Figure 15, assume that unicast routes are available in the network, MBGP is not configured, and no static multicast routes have been configured on Router C. Multicast packets travel along the SPT from the multicast source to the receivers.
Figure 16 Changing an RPF route As shown in Figure 16, when no static multicast route is configured, Router C's RPF neighbor on the path back to the source is Router A. The multicast data from the source travels through Router A to Router C. You can configure a static multicast route on Router C and specify Router B as Router C's RPF neighbor on the path back to the source. The multicast data from the source travels along the path: Router A to Router B and then to Router C.
C and Router D and specify Router B and Router C as the RPF neighbors of Router C and Router D, respectively. In this way, the receiver hosts can receive the multicast data from the multicast source. NOTE: A static multicast route is effective only on the multicast router on which it is configured, and will not be advertised throughout the network or redistributed to other routers.
NOTE: The device can route and forward multicast data only through the primary IP addresses of interfaces, rather than their secondary addresses or unnumbered IP addresses. For more information about primary and secondary IP addresses, and IP unnumbered, see Layer 3—IP Services Configuration Guide. Enabling IP multicast routing Enable IP multicast routing before you configure any Layer 3 multicast functionality on the public network or VPN instance.
Step Command Remarks • Delete a specific static multicast 3. (Optional.) Delete static multicast routes.
TIP: You do not need to enable IP multicast routing before this configuration. To configure a multicast forwarding boundary: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Configure a multicast forwarding boundary. multicast boundary group-address { mask-length | mask } By default, no forwarding boundary is configured.
Task Command Display multicast forwarding table information (MSR4000). display multicast [ vpn-instance vpn-instance-name ] forwarding-table [ source-address [ mask { mask-length | mask } ] | group-address [ mask { mask-length | mask } ] | incoming-interface interface-type interface-number | outgoing-interface { exclude | include | match } interface-type interface-number | slot slot-number | statistics ] * Display information about the DF list in the multicast forwarding entries (MSR2000/MSR3000).
Configure the routers so that the receiver host can receive the multicast data from Source through the path: Router A to Router C to Router B. This path is different from the unicast route. Figure 19 Network diagram Router C GE2/1/2 40.1.1.1/24 PIM-DM GE2/1/2 40.1.1.2/24 Router A GE2/1/1 50.1.1.1/24 GE2/1/1 20.1.1.2/24 GE2/1/2 20.1.1.1/24 GE2/1/3 30.1.1.2/24 GE2/1/3 30.1.1.1/24 Source Router B GE2/1/1 10.1.1.1/24 Receiver 50.1.1.100/24 10.1.1.
system-view [RouterA] multicast routing [RouterA-mrib] quit [RouterA] interface gigabitethernet 2/1/1 [RouterA-GigabitEthernet2/1/1] pim dm [RouterA-GigabitEthernet2/1/1] quit [RouterA] interface gigabitethernet 2/1/2 [RouterA-GigabitEthernet2/1/2] pim dm [RouterA-GigabitEthernet2/1/2] quit [RouterA] interface gigabitethernet 2/1/3 [RouterA-GigabitEthernet2/1/3] pim dm [RouterA-GigabitEthernet2/1/3] quit # Enable IP multicast routing and PIM-DM on Router C in the same way Router A is configured.
• Typically, the receiver host receives the multicast data from Source 1 in the OSPF domain. Configure the routers so that the receiver host can receive multicast data from Source 2, which is outside the OSPF domain. Figure 20 Network diagram Configuration procedure 1. Assign an IP address and subnet mask for each interface according to Figure 20. (Details not shown.) 2. Enable OSPF on Router B and Router C to make sure the following conditions are met: (Details not shown.) 3.
[RouterA-GigabitEthernet2/1/1] quit [RouterA] interface gigabitethernet 2/1/2 [RouterA-GigabitEthernet2/1/2] pim dm [RouterA-GigabitEthernet2/1/2] quit # Enable IP multicast routing and PIM-DM on Router B in the same way Router A is configured. (Details not shown.) 4. Display information about their RPF routes to Source 2 on Router B and Router C. [RouterB] display multicast rpf-info 50.1.1.100 [RouterC] display multicast rpf-info 50.1.1.
Figure 21 Network diagram Configuration procedure 1. Assign an IP address and mask for each interface according to Figure 21. (Details not shown.) 2. Enable OSPF on routers to make sure the following conditions are met: (Details not shown.) 3. { The routers are interoperable at the network layer. { The routers can dynamically update their routing information. Configure a GRE tunnel: # On Router A, create interface Tunnel 0, and specify the tunnel encapsulation mode as GRE over IPv4.
[RouterA-GigabitEthernet2/1/2] pim dm [RouterA-GigabitEthernet2/1/2] quit [RouterA] interface tunnel 0 [RouterA-Tunnel0] pim dm [RouterA-Tunnel0] quit # On Router C, enable multicast routing. [RouterC] multicast routing [RouterC-mrib] quit # Enable IGMP on GigabitEthernet 2/1/1 (the interface that connects to the receiver host). [RouterC] interface gigabitethernet 2/1/1 [RouterC-GigabitEthernet2/1/1] igmp enable [RouterC-GigabitEthernet2/1/1] quit # Enable PIM-DM on other interfaces.
Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet2/1/1 Protocol: pim-dm, UpTime: 00:04:25, Expires: - The output shows that Router A is the RPF neighbor of Router C and the multicast data from Router A is delivered over a GRE tunnel to Router C.
Configuring IGMP Overview Internet Group Management Protocol (IGMP) establishes and maintains the multicast group memberships between a Layer 3 multicast device and its directly connected hosts. IGMP has three versions: • IGMPv1 (defined by RFC 1112) • IGMPv2 (defined by RFC 2236) • IGMPv3 (defined by RFC 3376) All IGMP versions support the ASM model. In addition to the ASM model, IGMPv3 can directly implement the SSM model.
Figure 22 IGMP queries and reports IP network DR Router A Router B Ethernet Host A (G2) Host B (G1) Host C (G1) Query Report As shown in Figure 22, Host B and Host C are interested in the multicast data addressed to the multicast group G1. Host A is interested in the multicast data addressed to G2. The following process describes how the hosts join the multicast groups and how the IGMP querier (Router B in Figure 22) maintains the multicast group memberships: 1.
NOTE: The IGMP report suppression mechanism is not supported on MSR routers installed with the Layer 2 switching module SIC-4FSW, 4FSWP, SIC-9FSW, or 9FSWP. IGMPv2 enhancements Backwards-compatible with IGMPv1, IGMPv2 has introduced a querier election mechanism and a leave-group mechanism. Querier election mechanism In IGMPv1, the DR elected by the Layer 3 multicast routing protocol (such as PIM) serves as the querier among multiple routers that run IGMP on the same subnet.
Enhancements in control capability of hosts IGMPv3 introduced two source filtering modes (Include and Exclude). These modes allow a host to join a designated multicast group and to choose whether to receive or reject multicast data from a designated multicast source. When a host joins a multicast group, one of the following occurs: • If the host expects to receive multicast data from specific sources like S1, S2, …, it sends a report with the Filter-Mode denoted as "Include Sources (S1, S2, …).
{ { IS_IN—The source filtering mode is Include. The report sender requests the multicast data from only the sources defined in the specified multicast source list. IS_EX—The source filtering mode is Exclude. The report sender requests the multicast data from any sources except those defined in the specified multicast source list. { TO_IN—The filtering mode has changed from Exclude to Include. { TO_EX—The filtering mode has changed from Include to Exclude.
When the IGMP SSM mapping feature is configured, Router A checks the multicast group address G in the received IGMPv1 or IGMPv2 report, and does the following: • If G is not in the SSM group range, Router A provides the ASM service. • If G is in the SSM group range but does not have relevant IGMP SSM mappings, Router A drops the message. • If G is in the SSM group range and has relevant IGMP SSM mappings, Router A translates the (*, G) information in the IGMP report into (G, INCLUDE, (S1, S2...
An IGMP proxy device maintains a group membership database, which stores the group memberships on all the downstream interfaces. Each entry comprises the multicast address, filter mode, and source list. Such an entry is a collection of members in the same multicast group on each downstream interface. An IGMP proxy device performs host functions on the upstream interface based on the database.
• Determine the multicast group and multicast source addresses for static group member configuration. • Determine the ACL for multicast group filtering. Enabling IGMP To configure IGMP, enable IGMP on the interface where the multicast group memberships are established and maintained. To enable IGMP: Step Command Remarks 1. Enter system view. system-view N/A 2. Enable IP multicast routing and enter MRIB view.
any IGMP report or IGMP leave message. This is because the interface is not a real member of the multicast group or the multicast source and group. Configuration procedure To configure an interface as a static member interface: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Configure the interface as a static member interface.
If multiple multicast routers exist on the same subnet, only the IGMP querier sends IGMP queries. When a non-querier receives an IGMP query, it starts an IGMP other querier present timer. If it receives a new IGMP query before the timer expires, the non-querier resets the timer. Otherwise, it considers that the querier has failed and starts a new querier election.
Configuring IGMP SSM mappings On an SSM network, some receiver hosts run only IGMPv1 or IGMPv2. To provide the SSM service to these receiver hosts, you can configure the IGMP mapping feature on the IGMP-enabled routers. The IGMP SSM mapping feature does not process IGMPv3 messages. To provide SSM services for all hosts that run different IGMP versions on a subnet, you must enable IGMPv3 on the interface that forwards multicast traffic onto the subnet.
Configuration procedure To enable IGMP proxying: Step Command Remarks 1. Enter system view. system-view N/A 2. Enable IP multicast routing and enter MRIB view. multicast routing [ vpn-instance vpn-instance-name ] By default, IP multicast routing is disabled. 3. Return to system view. quit N/A 4. Enter interface view. interface interface-type interface-number N/A 5. Enable the IGMP proxying feature. igmp proxying enable By default, IGMP proxying is disabled.
Step Command Remarks 2. Enter IGMP view. igmp [ vpn-instance vpn-instance-name ] N/A 3. Enable the load splitting function on the IGMP proxy. proxy multipath By default, the load splitting function is disabled. Displaying and maintaining IGMP CAUTION: The reset igmp group command might cause multicast data transmission failures. Execute display commands in any view and reset commands in user view. Task Command Remarks Display IGMP group information.
• IGMPv2 runs between Router A and N1, and between the other two routers and N2. Router A acts as the IGMP querier in N1. Router B acts as the IGMP querier in N2 because it has a lower IP address. Configure the routers to meet the following requirements: • The hosts in N1 can join only the multicast group 224.1.1.1. • The hosts in N2 can join any multicast groups. Figure 26 Network diagram Receiver PIM network Host A GE2 /1/2 Router A Querier GE2 /1/2 GE2/1/1 10.110.1.
[RouterA-GigabitEthernet2/1/2] quit # On Router B, enable IP multicast routing. system-view [RouterB] multicast routing [RouterB-mrib] quit # Enable IGMP on GigabitEthernet 2/1/1. [RouterB] interface gigabitethernet 2/1/1 [RouterB-GigabitEthernet2/1/1] igmp enable [RouterB-GigabitEthernet2/1/1] quit # Enable PIM-DM on GigabitEthernet 2/1/2.
IGMP SSM mapping configuration example Network requirements As shown in Figure 27: • The PIM-SM domain uses both the ASM model and SSM model for multicast delivery. GigabitEthernet 2/1/3 on Router D serves as the C-BSR and C-RP. The SSM group range is 232.1.1.0/24. • IGMPv3 runs on GigabitEthernet 2/1/1 on Router D. The receiver host runs IGMPv2, and does not support IGMPv3. Therefore, the receiver host cannot specify expected multicast sources in its membership reports.
Configuration procedure 1. Assign an IP address and subnet mask to each interface according to Figure 27. (Details not shown.) 2. Configure OSPF on the routers in the PIM-SM domain to make sure the following conditions are met: (Details not shown.) 3. { The routers are interoperable at the network layer. { The routers can dynamically update their routing information. Enable IP multicast routing, PIM-SM, and IGMP: # On Router D, enable IP multicast routing.
[RouterD] acl number 2000 [RouterD-acl-basic-2000] rule permit source 232.1.1.0 0.0.0.255 [RouterD-acl-basic-2000] quit [RouterD] pim [RouterD-pim] ssm-policy 2000 [RouterD-pim] quit # Configure the SSM group range on Router A, Router B, and Router C in the same way Router D is configured. (Details not shown.) 6. Configure IGMP SSM mappings on Router D. [RouterD] igmp [RouterD-igmp] ssm-mapping 133.133.1.1 2000 [RouterD-igmp] ssm-mapping 133.133.3.
UpTime: 00:13:25 Upstream interface: GigabitEthernet2/1/2 Upstream neighbor: 192.168.3.1 RPF prime neighbor: 192.168.3.1 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet2/1/1 Protocol: igmp, UpTime: 00:13:25, Expires: - IGMP proxying configuration example Network requirements As shown in Figure 28, PIM-DM runs on the core network. Host A and Host C in the stub network receive VOD information sent to multicast group 224.1.1.1.
[RouterA-GigabitEthernet2/1/1] quit # Enable IP multicast routing on Router B. system-view [RouterB] multicast routing [RouterB-mrib] quit # Enable IGMP proxying on GigabitEthernet 2/1/1. [RouterB] interface gigabitethernet 2/1/1 [RouterB-GigabitEthernet2/1/1] igmp proxy enable [RouterB-GigabitEthernet2/1/1] quit # Enable IGMP on GigabitEthernet 2/1/2.
2. Use the display current-configuration command to verify that multicast routing is enabled. If it is not enabled, use the multicast routing command in system view to enable IP multicast routing. In addition, verify that IGMP is enabled on the associated interfaces. 3. Use the display igmp interface command to verify that the IGMP version on the interface is lower than that on the host. 4.
Configuring PIM Overview Protocol Independent Multicast (PIM) provides IP multicast forwarding by leveraging unicast static routes or unicast routing tables generated by any unicast routing protocol, such as RIP, OSPF, IS-IS, or BGP. PIM uses the underlying unicast routing to generate a multicast routing table without relying on any particular unicast routing protocol. PIM uses the RPF mechanism to implement multicast forwarding.
messages, all PIM routers on the subnet discover their PIM neighbors, maintain PIM neighboring relationship with other routers, and build and maintain SPTs. SPT building The process of building an SPT is the flood-and-prune process: 1. In a PIM-DM domain, when the multicast source S sends multicast data to the multicast group G, the multicast data is flooded throughout the domain. A router performs an RPF check for the multicast data.
1. The node that needs to receive the multicast data sends a graft message to its upstream node, telling it to rejoin the SPT. 2. After receiving this graft message, the upstream node adds the receiving interface to the outgoing interface list of the (S, G) entry. It also sends a graft-ack message to the graft sender. 3. If the graft sender receives a graft-ack message, the graft process finishes.
The basic implementation of PIM-SM is as follows: • PIM-SM assumes that no hosts need multicast data. In the PIM-SM mode, a host must express its interest in the multicast data for a multicast group before the data is forwarded to it. PIM-SM implements multicast forwarding by building and maintaining rendezvous point trees (RPTs). An RPT is rooted at a router that has been configured as the rendezvous point (RP) for a multicast group.
Figure 31 DR election As shown in Figure 31, the DR election process is as follows: 1. The routers on the shared-media LAN send hello messages to one another. The hello messages contain the priority for DR election. The router with the highest DR priority is elected as the DR. 2. The router with the highest IP address wins the DR election under either of following conditions: { All the routers have the same DR election priority.
Figure 32 Information exchange between C-RPs and BSR Based on the information in the RP-set, all routers in the network can select an RP for a specific multicast group based on the following rules: 1. The C-RP that is designated to the smallest group range wins. 2. If the C-RPs are designated to the same group ranges, the C-RP with the highest priority wins. 3. If the C-RPs have the same priority, the C-RP with the largest hash value wins. The hash value is calculated through the hash algorithm. 4.
{ Anycast RP address—IP address of the Anycast RP set for communication within the PIM-SM domain. It is also known as RPA. As shown in Figure 33, RP 1, RP 2, and RP 3 are members of an Anycast RP set. Figure 33 Anycast RP through PIM-SM The following describes how Anycast RP through PIM-SM is implemented: a. RP 1 receives a register message destined to the Anycast RP address (RPA).
RPT building Figure 34 RPT building in a PIM-SM domain Host A Source RP DR Server Receiver Host B DR Receiver RPT Join message Multicast packets Host C As shown in Figure 34, the process of building an RPT is as follows: 1. When a receiver wants to join the multicast group G, it uses an IGMP message to inform the receiver-side DR. 2. After getting the receiver information, the DR sends a join message, which is forwarded hop by hop to the RP for the multicast group. 3.
Figure 35 Multicast source registration As shown in Figure 35, the multicast source registers with the RP as follows: 1. The multicast source S sends the first multicast packet to the multicast group G. When receiving the multicast packet, the source-side DR encapsulates the packet into a PIM register message and unicasts the message to the RP. 2. After the RP receives the register message, it decapsulates the register message and forwards the register message down to the RPT.
The subsequent multicast data is forwarded to the RP along the SPT without being encapsulated into register messages. For more information about the switchover to SPT initiated by the RP, see "Multicast source registration." • The receiver-side DR initiates a switchover to SPT: The receiver-side DR periodically checks the forwarding rate of the multicast packets that the multicast source S sends to the multicast group G.
DF election On a subnet with multiple multicast routers, duplicate multicast packets might be forwarded to the RP. To address this issue, BIDIR-PIM uses a designated forwarder (DF) election mechanism to elect a unique DF for each RP on each subnet in the BIDIR-PIM domain. Only the DF can forward multicast data to the RP. DF election is not necessary for an RPL.
Figure 37 RPT building at the receiver side As shown in Figure 37, the process for building a receiver-side RPT is the same as the process for building an RPT in PIM-SM: 1. When a receiver wants to join the multicast group G, it uses an IGMP message to inform the directly connected router. 2. After receiving the message, the router sends a join message, which is forwarded hop by hop to the RP for the multicast group. 3.
Figure 38 RPT building at the multicast source side As shown in Figure 38, the process for building a source-side RPT is relatively simple: 4. When a multicast source sends multicast packets to the multicast group G, the DF in each subnet unconditionally forwards the packets to the RP. 5. The routers along the path from the source's directly connected router to the RP constitute an RPT branch.
Admin-scoped zones are divided for multicast groups. Zone border routers (ZBRs) form the boundary of an admin-scoped zone. Each admin-scoped zone maintains one BSR for multicast groups within a specific range. Multicast protocol packets, such as assert messages and BSMs, for a specific group range cannot cross the boundary of the admin-scoped zone for the group range. Multicast group ranges that are associated with different admin-scoped zones can have intersections.
Figure 40 Relationship in view of multicast group address ranges Admin-scope 1 Admin-scope 3 G1 address G3 address Admin-scope 2 Global-scope G2 address G−G1−G2 address As shown in Figure 40, the admin-scoped zones 1 and 2 have no intersection, but the admin-scoped zone 3 is a subset of the admin-scoped zone 1. The global-scoped zone provides services for all the multicast groups that are not covered by the admin-scoped zones 1 and 2, G-G1-G2 in this case.
Figure 41 SPT building in PIM-SSM Host A Source RP DR Server Receiver Host B DR Receiver SPT Subscribe message Multicast packets Host C As shown in Figure 41, Host B and Host C are receivers. They send IGMPv3 report messages to their DRs to express their interest in the multicast information that the multicast source S sends to the multicast group G.
Figure 42 Relationship among PIM protocols A receiver joins multicast group G. G is in the SSM group range? Yes A multicast source is specified? No No No BIDIR-PIM is enabled? No An IGMP-SSM mapping is configured for G? Yes PIM-SM runs for G. No Yes G has a BIDIR-PIM RP? Yes PIM-SSM runs for G. Yes BIDIR-PIM runs for G.
PIM-DM configuration task list Task at a glance (Required.) Enabling PIM-DM (Optional.) Enabling the state refresh feature (Optional.) Configuring state refresh parameters (Optional.) Configuring PIM-DM graft retry timer (Optional.) Configuring common PIM features Configuration prerequisites Before you configure PIM-DM, configure a unicast routing protocol so that all devices in the domain are interoperable at the network layer Enabling PIM-DM Enable IP multicast routing before you configure PIM.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Enable the state refresh feature. pim state-refresh-capable By default, the state refresh feature is enabled. Configuring state refresh parameters The router directly connected with the multicast source periodically sends state refresh messages. You can configure the interval for sending such messages on that router.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Configure the graft retry timer. pim timer graft-retry interval The default setting is 3 seconds. Configuring PIM-SM This section describes how to configure PIM-SM. PIM-SM configuration task list Task at a glance (Required.) Enabling PIM-SM (Required.) Configuring an RP: • Configuring a static RP • Configuring a C-RP • (Optional.
IMPORTANT: All the interfaces on the same router must operate in the same PIM mode in the public network or the same VPN instance. To enable PIM-SM: Step Command Remarks 1. Enter system view. system-view N/A 2. Enable IP multicast routing and enter MRIB view. multicast routing [ vpn-instance vpn-instance-name ] By default, IP multicast routing is disabled. 3. Return to system view. quit N/A 4. Enter interface view. interface interface-type interface-number N/A 5. Enable PIM-SM.
The C-RPs periodically send advertisement messages to the BSR, which collects RP set information for RP election. You can configure the interval for sending the advertisement messages. The holdtime option in C-RP advertisement messages defines the C-RP lifetime for the advertising C-RP. The BSR starts a holdtime timer for a C-RP after it receives an advertisement message. If the BSR does not receive any advertisement message when the timer expires, it considers the C-RP failed or unreachable.
Step 3. Configure Anycast RP. Command Remarks anycast-rp anycast-rp-address member-rp-address By default, Anycast RP is not configured. You can repeat this command to add multiple RP member addresses to the Anycast RP set. Configuring a BSR You must configure a BSR if C-RPs are configured to dynamically select the RP. In a network with a static RP, this configuration task is unnecessary. A PIM-SM domain can have only one BSR, but must have at least one C-BSR. Any router can be configured as a C-BSR.
These preventive measures can partially protect the BSR in a network. However, if an attacker controls a legal BSR, the problem still exists. When you configure a C-BSR, reserve a relatively large bandwidth between the C-BSR and the other devices in the PIM-SM domain. When C-BSRs connect to other PIM routers through tunnels, static multicast routes must be configured to make sure the next hop to a C-BSR is a tunnel interface. Otherwise, RPF check is affected.
• If the RP-set information is carried in multiple BSMFs, the router updates the RP-set information for the group range after receiving all these BSMFs. The loss of some IP fragments does not result in dropping of the entire BSM. The BSM semantic fragmentation function is enabled by default. A device that does not support this function might regard a fragment as a BSM. Therefore, the device learns only part of the RP-set information.
The register-stop timer is set to a random value chosen uniformly from (0.5 × register_suppression_time minus register_probe_time) to (1.5 × register_suppression_time minus register_probe_time). The register_probe_time is fixed to 5 seconds. On all C-RP routers, configure a filtering rule for register messages and configure the device to calculate the checksum based on the entire register messages. On all routers that might become the source-side DR, configure the register suppression time.
Configuring BIDIR-PIM This section describes how to configure BIDIR-PIM. BIDIR-PIM configuration task list Task at a glance (Required.) Enabling BIDIR-PIM (Required.) Configuring an RP: • Configuring a static RP • Configuring a C-RP • (Optional.) Configuring the maximum number of BIDIR-PIM RPs NOTE: You must configure a static RP, a C-RP, or both in a BIDIR-PIM domain. In a network without C-RPs, skip the task of configuring a BSR. Configuring a BSR: • (Required.) Configuring a C-BSR • (Optional.
Step Command Remarks 5. Enable PIM-SM. pim sm By default, PIM-SM is disabled. 6. Return to system view. quit N/A 7. Enter PIM view. pim [ vpn-instance vpn-instance-name ] N/A 8. Enable BIDIR-PIM. bidir-pim enable By default, BIDIR-PIM is disabled. Configuring an RP CAUTION: When both PIM-SM and BIDIR-PIM run on the PIM network, do not use the same RP to provide services for PIM-SM and BIDIR-PIM. Otherwise, exceptions might occur to the PIM routing table.
determine the RPs for different multicast group ranges based on the RP-set information. HP recommends that you configure C-RPs on backbone routers. To enable the BSR to distribute the RP-set information in the BIDIR-PIM domain, the C-RPs must periodically send advertisement messages to the BSR. The BSR learns the C-RP information, encapsulates the C-RP information and its own IP address in a BSM, and floods the BSM to all PIM routers in the domain.
For C-BSRs interconnected through a GRE tunnel, configure static multicast routes to make sure the next hop to a C-BSR is a tunnel interface. For more information about static multicast routes, see "Configuring multicast routing and forwarding." C-BSRs should be configured on routers on the backbone network. The BSR election process is summarized as follows: 1. Initially, each C-BSR regards itself as the BSR of the BIDIR-PIM domain and sends BSMs to other routers in the domain. 2.
Step Command Remarks 4. (Optional.) Configure a legal BSR address range. bsr-policy acl-number By default, no restrictions are defined. Configuring a PIM domain border As the administrative core of a BIDIR-PIM domain, the BSR sends the collected RP-set information in the BSMs to all routers in the BIDIR-PIM domain. A PIM domain border is a bootstrap message boundary. Each BSR has its specific service scope. A number of PIM domain border interfaces partition a network into different BIDIR-PIM domains.
NOTE: Generally, a BSR performs BSM semantic fragmentation according to the MTU of its BSR interface. For BSMs originated due to learning of a new PIM neighbor, semantic fragmentation is performed according to the MTU of the interface that sends the BSMs. Configuring PIM-SSM PIM-SSM requires IGMPv3 support. Enable IGMPv3 on PIM routers that connect to multicast receivers. PIM-SSM configuration task list Task at a glance (Required.) Enabling PIM-SM (Optional.) Configuring the SSM group range (Optional.
Configuring the SSM group range When a PIM-SM enabled interface receives a multicast packet, it checks whether the multicast group address of the packet is in the SSM group range. If the multicast group address is in this range, the PIM mode for this packet is PIM-SSM. If the multicast group address is not in this range, the PIM mode is PIM-SM. Configuration guidelines • Perform the following configuration on all routers in the PIM-SSM domain.
Configuring a multicast data filter To control multicast traffic and the information available to downstream receivers, you can configure a PIM router as a multicast data filter. Then, the router will check IP packets that pass by and forward or discard the packets based on the filtering policy. A filter can filter not only independent multicast data but also multicast data encapsulated in register messages. Generally, a filter nearer to the multicast source has a better filtering effect.
• Holdtime—PIM neighbor lifetime. If a router does not receive a hello message from a neighbor when the neighbor lifetime expires, it regards the neighbor failed or unreachable. • LAN_Prune_Delay—Delay of forwarding prune messages on a shared-media LAN. This option consists of LAN delay (namely, prune message delay), override interval, and neighbor tracking support (namely, the capability to disable join message suppression).
Configuring hello message options on an interface Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Set the DR priority. pim hello-option dr-priority priority The default setting is 1. 4. Set the neighbor lifetime. pim hello-option holdtime time The default setting is 105 seconds. 5. Set the prune delay. pim hello-option lan-delay delay The default setting is 500 milliseconds. 6. Set the override interval.
Configuring common PIM timers globally Step Command Remarks 1. Enter system view. system-view N/A 2. Enter PIM view. pim [ vpn-instance vpn-instance-name ] N/A 3. Set the interval for sending hello messages. timer hello interval The default setting is 30 seconds. The default setting is 60 seconds. 4. Set the interval for sending join/prune messages. timer join-prune interval 5. Set the joined/pruned state holdtime timer. holdtime join-prune time The default setting is 210 seconds. 6.
Step Command Remarks 3. Set the maximum size of each join or prune message. jp-pkt-size size The default setting is 8100 bytes. Enabling BFD for PIM PIM uses hello messages to elect a DR for a shared-media network. The elected DR is the only multicast forwarder on the shared-media network. If the DR fails, a new DR election process does not start until the DR ages out. In addition, it might take a long period of time before other routers detect the link failures and trigger a new DR election.
Task Command Display information about the register-tunnel interface. display interface [ register-tunnel [ interface-number ] ] [ brief [ description | down ] ] Display BSR information in the PIM-SM domain. display pim [ vpn-instance vpn-instance-name ] bsr-info Display information about the routes used by PIM. display pim [ vpn-instance vpn-instance-name ] claimed-route [ source-address ] Display C-RP information in the PIM-SM domain.
Figure 43 Network diagram Receiver Host A Router A G E2 /1 /2 GE2/1/1 Host B G E2 /1 /2 Receiver GE2/1/1 GE2/1/3 GE2/1/1 Host C Router B 1/ Router D / E2 G Source GE2/1/2 4 /2 /1 E2 G 10.110.5.100/24 GE2/1/1 PIM-DM Router C Host D Table 7 Interface and IP address assignment Device Interface IP address Device Interface IP address Router A GigabitEthernet 2/1/1 10.110.1.1/24 Router C GigabitEthernet 2/1/2 192.168.3.1/24 Router A GigabitEthernet 2/1/2 192.168.1.
[RouterA-mrib] quit # Enable IGMP on GigabitEthernet 2/1/1 (the interface that connects to the stub network). [RouterA] interface gigabitethernet 2/1/1 [RouterA-GigabitEthernet2/1/1] igmp enable [RouterA-GigabitEthernet2/1/1] quit # Enable PIM-DM on GigabitEthernet 2/1/2. [RouterA] interface gigabitethernet 2/1/2 [RouterA-GigabitEthernet2/1/2] pim dm [RouterA-GigabitEthernet2/1/2] quit # Enable IP multicast routing, IGMP, and PIM-DM on Router B and Router C in the same way Router A is configured.
# Display the PIM routing table information on Router A. [RouterA] display pim routing-table Total 1 (*, G) entry; 1 (S, G) entry (*, 225.1.1.1) Protocol: pim-dm, Flag: WC UpTime: 00:04:25 Upstream interface: NULL Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet2/1/1 Protocol: igmp, UpTime: 00:04:25, Expires: (10.110.5.100, 225.1.1.
PIM-SM non-scoped zone configuration example Network requirements As shown in Figure 44: • VOD streams are sent to receiver hosts in multicast. The receivers of different subnets form stub networks, and at least one receiver host exist in each stub network. • The entire PIM-SM domain contains only one BSR. • Host A and Host C are multicast receivers in the stub networks N1 and N2. • Specify GigabitEthernet 2/1/3 on Router E as a C-BSR and a C-RP.
Device Interface IP address Device Interface IP address Router B GigabitEthernet 2/1/2 192.168.2.1/24 Router E GigabitEthernet 2/1/2 192.168.2.2/24 Router C GigabitEthernet 2/1/1 10.110.2.2/24 Router E GigabitEthernet 2/1/3 192.168.9.2/24 Configuration procedure 1. Assign an IP address and subnet mask to each interface according to Figure 44. (Details not shown.) 2. Configure OSPF on all routers on the PIM-SM network to make sure the following conditions are met: (Details not shown.
[RouterE-pim] quit # On Router A, configure GigabitEthernet 2/1/2 of Router D as the static RP. [RouterA] pim [RouterA-pim] static-rp 192.168.1.2 [RouterA-pim] quit # Configure the static RP on Router B, Router C, and Router D in the same way Router A is configured. (Details not shown.) Verifying the configuration # Display PIM information on Router A. [RouterA] display pim interface Interface NbrCnt HelloInt DR-Pri DR-Address GE2/1/1 0 30 1 10.110.1.1 GE2/1/2 1 30 1 192.168.1.
PIM-SM admin-scoped zone configuration example Network requirements As shown in Figure 45: • VOD streams are sent to receiver hosts in multicast. The entire PIM-SM domain is divided into admin-scoped zone 1, admin-scoped zone 2, and the global-scoped zone. Router B, Router C, and Router D are ZBRs of the three zones, respectively. • Source 1 and Source 2 send different multicast data to the multicast group 239.1.1.1.
Device Interface IP address Device Interface IP address Router A GigabitEthernet 2/1/2 10.110.1.1/24 Router D GigabitEthernet 2/1/2 10.110.7.1/24 Router B GigabitEthernet 2/1/1 192.168.2.1/24 Router D GigabitEthernet 2/1/3 10.110.8.1/24 Router B GigabitEthernet 2/1/2 10.110.1.2/24 Router E GigabitEthernet 2/1/1 192.168.4.1/24 Router B GigabitEthernet 2/1/3 10.110.2.1/24 Router E GigabitEthernet 2/1/2 10.110.4.2/24 Router B GigabitEthernet 2/1/4 10.110.3.
[RouterA-GigabitEthernet2/1/1] igmp enable [RouterA-GigabitEthernet2/1/1] quit # Enable PIM-SM on GigabitEthernet 2/1/2. [RouterA] interface gigabitethernet 2/1/2 [RouterA-GigabitEthernet2/1/2] pim sm [RouterA-GigabitEthernet2/1/2] quit # Enable IP multicast routing, IGMP and PIM-SM on Router E and Router I in the same way Router A is configured. (Details not shown.) # On Router B, enable IP multicast routing, and enable PIM-SM on each interface.
[RouterD-GigabitEthernet2/1/3] multicast boundary 239.0.0.0 8 [RouterD-GigabitEthernet2/1/3] quit 5. Configure C-BSRs and C-RPs: # On Router B, configure the service scope of RP advertisements. [RouterB] acl number 2001 [RouterB-acl-basic-2001] rule permit source 239.0.0.0 0.255.255.255 [RouterB-acl-basic-2001] quit # Configure GigabitEthernet 2/1/2 as a C-BSR and a C-RP for admin-scoped zone 1. [RouterB] pim [RouterB-pim] c-bsr 10.110.1.2 scope 239.0.0.0 8 [RouterB-pim] c-rp 10.110.1.
Candidate BSR address: 10.110.1.2 Priority: 64 Hash mask length: 30 # Display BSR information on Router D. [RouterD] display pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:44 Elected BSR address: 10.110.9.1 Priority: 64 Hash mask length: 30 Uptime: 00:01:45 Scope: 239.0.0.0/8 State: Elected Bootstrap timer: 00:01:12 Elected BSR address: 10.110.5.2 Priority: 64 Hash mask length: 30 Uptime: 00:03:48 Candidate BSR address: 10.110.5.
[RouterD] display pim rp-info BSR RP information: Scope: non-scoped Group/MaskLen: 224.0.0.0/4 RP address Priority HoldTime Uptime Expires 10.110.9.1 192 150 00:03:42 00:01:48 RP address Priority HoldTime Uptime Expires 10.110.5.2 (local) 192 150 00:06:54 00:02:41 RP address Priority HoldTime Uptime Expires 10.110.9.1 (local) 192 150 00:00:32 00:01:58 Scope: 239.0.0.0/8 Group/MaskLen: 239.0.0.0/8 # Display RP information on Router F.
Table 10 Interface and IP address assignment Device Interface IP address Device Interface IP address Router A GigabitEthernet 2/1/1 192.168.1.1/24 Router D GigabitEthernet 2/1/1 192.168.3.1/24 Router A GigabitEthernet 2/1/2 10.110.1.1/24 Router D GigabitEthernet 2/1/2 192.168.4.1/24 Router B GigabitEthernet 2/1/1 192.168.2.1/24 Router D GigabitEthernet 2/1/3 10.110.3.2/24 Router B GigabitEthernet 2/1/2 10.110.1.2/24 Source 1 — 192.168.1.
# Enable IGMP on GigabitEthernet 2/1/1 (the interface that connects to the receiver host). [RouterB] interface gigabitethernet 2/1/1 [RouterB-GigabitEthernet2/1/1] igmp enable [RouterB-GigabitEthernet2/1/1] quit # Enable PIM-SM on the other interfaces. [RouterB] interface gigabitethernet 2/1/2 [RouterB-GigabitEthernet2/1/2] pim sm [RouterB-GigabitEthernet2/1/2] quit [RouterB] interface gigabitethernet 2/1/3 [RouterB-GigabitEthernet2/1/3] pim sm [RouterB-GigabitEthernet2/1/3] quit # Enable BIDIR-PIM.
[RouterD] pim [RouterD-pim] bidir-pim enable [RouterD-pim] quit 4. On Router C, configure GigabitEthernet 2/1/1 as the C-BSR, and Loopback 0 as the C-RP for the entire BIDIR-PIM domain. [RouterC-pim] c-bsr 10.110.2.2 [RouterC-pim] c-rp 1.1.1.1 bidir [RouterC-pim] quit Verifying the configuration 1. Display the DF information of BIDIR-PIM: # Display the DF information of BIDIR-PIM on Router A. [RouterA] display pim df-info RP address: 1.1.1.
List of 1 DF interfaces: 1: GigabitEthernet2/1/1 # Display information about the DF for multicast forwarding on Router B. [RouterB] display multicast forwarding df-info Total 1 RP, 1 matched 00001. RP address: 1.1.1.1 Flags: 0x0 Uptime: 00:06:24 RPF interface: GigabitEthernet2/1/3 List of 2 DF interfaces: 1: GigabitEthernet2/1/1 2: GigabitEthernet2/1/2 # Display information about the DF for multicast forwarding on Router C. [RouterC] display multicast forwarding df-info Total 1 RP, 1 matched 00001.
Figure 47 Network diagram Receiver Host A Router A G E2 /1 /2 G E2 /1 /2 GE2/1/1 GE2/1/1 GE2/1/3 GE2/1/3 GE2/1/4 Router D Receiver GE2/1/1 GE2/1/2 GE2/1/3 Source Host B GE2/1/2 Router E 10.110.5.100/24 GE2/1/1 Router B Host C GE2/1/2 GE2/1/1 PIM-SSM Host D Router C Table 11 Interface and IP address assignment Device Interface IP address Device Interface IP address Router A GigabitEthernet 2/1/1 10.110.1.1/24 Router D GigabitEthernet 2/1/1 10.110.5.
{ 3. The routers can dynamically update their routing information. Enable IP multicast routing, IGMP and PIM-SM: # On Router A, enable IP multicast routing. system-view [RouterA] multicast routing [RouterA-mrib] quit # Enable IGMPv3 on GigabitEthernet 2/1/1 (the interface that connects to the stub network).
(10.110.5.100, 232.1.1.1) Protocol: pim-ssm, Flag: UpTime: 00:13:25 Upstream interface: GigabitEthernet2/1/2 Upstream neighbor: 192.168.1.2 RPF prime neighbor: 192.168.1.2 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet2/1/1 Protocol: igmp, UpTime: 00:13:25, Expires: 00:03:25 # Display PIM routing table information on Router D. [RouterD] display pim routing-table Total 0 (*, G) entry; 1 (S, G) entry (10.110.5.100, 232.1.1.
• When a multicast router receives a multicast packet, it looks up the existing unicast routing table for the optimal route to the packet source. The outgoing interface of this route act as the RPF interface and the next hop acts the RPF neighbor. The RPF interface completely relies on the existing unicast route and is independent of PIM. The RPF interface must be enabled with PIM, and the RPF neighbor must be a PIM neighbor.
2. Use display current-configuration to verify the multicast data filter. Change the ACL rule defined in the source-policy command so that the source/group address of the multicast data can pass ACL filtering. 3. If the problem persists, contact HP Support. An RP cannot join an SPT in PIM-SM Symptom An RPT cannot be correctly built, or an RP cannot join the SPT toward the multicast source. Analysis • RPs are the core of a PIM-SM domain.
2. Use display pim bsr-info to verify that the BSR information exists on each router, and then use display pim rp-info to verify that the RP information is correct on each router. 3. Use display pim neighbor to verify that PIM neighboring relationship has been correctly established among the routers. 4. If the problem persists, contact HP Support.
Configuring MSDP Overview MSDP is an inter-domain multicast solution that addresses the interconnection of PIM-SM domains. It discovers 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 in each domain is isolated. As a result, both of the following occur: • The RP obtains the source information only within the local domain.
As shown in Figure 48, an MSDP peer can be created on any PIM-SM router. MSDP peers created on PIM-SM routers that assume different roles function differently. • MSDP peers created on RPs: { Source-side MSDP peer—MSDP peer nearest to the multicast source, such as RP 1. The source-side RP creates and sends SA 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.
Figure 49 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. This register message is forwarded to RP 1, and RP 1 obtains the multicast source information from the message. 2.
The subsequent multicast data flows to RP 2 along the SPT, and from RP 2 to the receiver-side DR along the RPT. After receiving the multicast data, the receiver-side DR determines whether to initiate an RPT-to-SPT switchover process based on its configuration. { If no receivers exist in the domain, RP 2 neither creates an (S, G) entry nor sends a join message toward the multicast source.
Figure 50 Anycast RP through MSDP The following describes how Anycast RP through MSDP is implemented: a. After receiving the multicast data from Source, the source-side DR registers with the nearest RP (RP 1 in this example). b. After receiving the IGMP report message from the receiver, the receiver-side DR sends a join message toward the nearest RP (RP 2 in this example). Therefore, an RPT rooted at this RP is established. c. The RPs share the registered multicast source information through SA messages.
Figure 51 MSDP peer-RPF forwarding The process of peer-RPF forwarding is as follows: 1. RP 1 creates an SA message and forwards it to its peer RP 2. 2. RP 2 determines that RP 1 is the RP that creates the SA message because the RP address in the SA message is the same as that of RP 1. Then, RP 2 accepts and forwards the SA message. 3. RP 2 and RP 3 reside in the same AS, and RP 2 is the next hop of RP 3 to RP 1. RP 3 accepts and forwards the SA message. 4.
RFC 3446, Anycast Rendezvous Point (RP) mechanism using Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP) • MSDP configuration task list Task at a glance Configuring basic MSDP functions: • (Required.) Enabling MSDP • (Required.) Creating an MSDP peering connection • (Optional.) Configuring a static RPF peer Configuring an MSDP peering connection: • (Optional.) Configuring the description for an MSDP peer • (Optional.) Configuring an MSDP mesh group • (Optional.
Creating an MSDP peering connection An MSDP peering relationship is identified by an address pair (the addresses of the local MSDP peer and the remote MSDP peer). To create an MSDP peering connection, you must perform the creation operation on both devices that are a pair of MSDP peers. If an MSDP peer and a BGP peer share the same interface at the same time, HP recommends that you configure the same IP address for them. To create an MSDP peering connection: Step Command Remarks 1. Enter system view.
To describe an MSDP peer: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter MSDP view. msdp [ vpn-instance vpn-instance-name ] N/A 3. Configure the description for an MSDP peer. peer peer-address description text By default, no description is configured for an MSDP peer. Configuring an MSDP mesh group An AS might contain multiple MSDP peers. You can use the MSDP mesh group mechanism to avoid SA message flooding among these MSDP peers and to optimize the multicast traffic.
A TCP connection is required when one of the following conditions exists: • A new MSDP peer is created. • A previously deactivated MSDP peering connection is reactivated. • A previously failed MSDP peer attempts to resume operation. You can adjust the interval between MSDP peering connection attempts. To enhance MSDP security, configure a key for MD5 authentication used by both MSDP peers to establish a TCP connection. If the MD5 authentication fails, the TCP connection cannot be established.
Configuring SA message contents Some multicast sources send multicast data at an interval longer than the aging time of (S, G) entries. In this case, the source-side DR must encapsulate multicast data packet-by-packet in register messages and send them to the source-side RP. The source-side RP transmits the (S, G) information to the remote RP through SA messages. Then, the remote RP sends join messages to the source-side DR and builds an SPT.
Step Command Remarks 2. Enter MSDP view. msdp [ vpn-instance vpn-instance-name ] N/A 3. Enable the device to send SA request messages. peer peer-address request-sa-enable By default, after receiving a new join message, a device does not send an SA request message to any MSDP peer. Instead, it waits for the next SA message from its MSDP peer. 4. Configure a filtering rule for SA request messages.
Step Command Remarks 5. Configure the lower TTL threshold for multicast data packets encapsulated in SA messages. peer peer-address minimum-ttl ttl-value The default setting is 0. Configuring the SA message cache To reduce the time spent in obtaining the multicast information, enable the SA message cache mechanism to locally cache (S, G) entries contained in SA messages on the router. More cached (S, G) entries occupy more memory spaces on the router.
Task Command Display brief information about MSDP peers. display msdp [ vpn-instance vpn-instance-name ] brief [ state { connect | disabled | established | listen | shutdown } ] Display detailed information about the MSDP peer status. display msdp [ vpn-instance vpn-instance-name ] peer-status [ peer-address ] Display information about the (S, G) entries in the SA message cache.
Figure 52 Network diagram G E2 /1 /3 /2 /1 E2 G /1 E2 G /1 G E2 /1 /2 /1 /1 E2 G Table 12 Interface and IP address assignment Device Interface IP address Device Interface IP address Router A GigabitEthernet 2/1/1 10.110.1.2/24 Router D GigabitEthernet 2/1/1 10.110.4.2/24 Router A GigabitEthernet 2/1/2 10.110.2.1/24 Router D GigabitEthernet 2/1/2 10.110.5.1/24 Router A GigabitEthernet 2/1/3 10.110.3.1/24 Router E GigabitEthernet 2/1/1 10.110.6.
2. Configure OSPF on the routers. (Details not shown.) 3. Enable IP multicast routing, enable PIM-SM and IGMP, and configure a PIM-SM domain border: # On Router A, enable IP multicast routing. system-view [RouterA] multicast routing [RouterA-mrib] quit # Enable PIM-SM on GigabitEthernet 2/1/1 and GigabitEthernet 2/1/2.
[RouterC-bgp] peer 192.168.1.1 as-number 100 [RouterC-bgp] address-family ipv4 [RouterC-bgp-ipv4] import-route ospf 1 [RouterB-bgp-ipv4] peer 192.168.1.1 enable [RouterC-bgp-ipv4] quit [RouterC-bgp] quit # Redistribute BGP routing information into OSPF on Router B. [RouterB] ospf 1 [RouterB-ospf-1] import-route bgp [RouterB-ospf-1] quit # Redistribute BGP routing information into OSPF on Router C. [RouterC] ospf 1 [RouterC-ospf-1] import-route bgp [RouterC-ospf-1] quit 6.
Peer 192.168.1.1 AS MsgRcvd 100 18 MsgSent OutQ PrefRcv Up/Down 16 0 State 1 00:12:04 Established # Display the BGP IPv4 unicast routing table on Router C. [RouterC] display bgp routing-table ipv4 Total number of routes: 5 BGP local router ID is 2.2.2.2 Status codes: * - valid, > - best, d - dampened, h - history, s - suppressed, S - stale, i - internal, e - external Origin: i - IGP, e - EGP, ? - incomplete Network NextHop MED 1.1.1.1/32 192.168.1.1 0 0 100? * >i 2.2.2.2/32 0.0.0.
# Display detailed MSDP peer information on Router B. [RouterB] display msdp peer-status MSDP Peer 192.168.1.2; AS 200 Description: Information about connection status: State: Established Up/down time: 00:15:47 Resets: 0 Connection interface: GigabitEthernet2/1/2 (192.168.1.
• Configure Loopback 0 as the C-BSR and C-RP of the related PIM-SM domain on Router A, Router D and Router G. • According to the peer-RPF forwarding rule, the routers accept SA messages that pass the filtering policy from its static RPF peers. To share multicast source information among PIM-SM domains without changing the unicast topology structure, configure MSDP peering relationships for the RPs of the PIM-SM domains and configure the static RPF peering relationships.
Device Interface IP address Device Interface IP address Router C GigabitEthernet 2/1/1 10.110.2.2/24 Router G GigabitEthernet 2/1/2 192.168.4.1/24 Router C GigabitEthernet 2/1/2 192.168.2.1/24 Router G Loopback 0 3.3.3.3/32 Router C GigabitEthernet 2/1/3 10.110.4.1/24 Configuration procedure 1. Assign an IP address and subnet mask to each interface according to Table 13. (Details not shown.) 2.
# Configure C-BSRs and C-RPs on Router D and Router G in the same way. (Details not shown.) 5. Configure BGP, and redistribute BGP routing information into OSPF and OSPF routing information into BGP: # On Router B, configure an eBGP peer, and redistribute OSPF routing information. [RouterB] bgp 100 [RouterB-bgp] router-id 1.1.1.2 [RouterB-bgp] peer 10.110.3.2 as-number 200 [RouterB-bgp] address-family ipv4 unicast [RouterB-bgp-ipv4] peer 10.110.3.
# On Router C, redistribute BGP routing information into OSPF [RouterC] ospf 1 [RouterC-ospf-1] import-route bgp [RouterC-ospf-1] quit # On Router F, redistribute BGP routing information into OSPF. [RouterF] ospf 1 [RouterF-ospf-1] import-route bgp [RouterF-ospf-1] quit 6. Configure MSDP peers and static RPF peers: # On Router A, configure Router D and Router G as the MSDP peers and static RPF peers. [RouterA] ip prefix-list list-dg permit 10.110.0.
1 1 0 0 Peer address State 10.110.1.1 Established 01:07:09 Up/Down time 0 0 AS SA count Reset count ? 8 0 # Display brief information about MSDP peers on Router G. [RouterG] display msdp brief Configured Established Listen Connect Shutdown Disabled 1 1 0 0 0 0 Peer address State Up/Down time 10.110.2.
Table 14 Interface and IP address assignment Device Interface IP address Device Interface IP address Source 1 — 10.110.5.100/24 Router C GigabitEthernet 2/1/1 192.168.1.2/24 Source 2 — 10.110.6.100/24 Router C GigabitEthernet 2/1/2 192.168.2.2/24 Router A GigabitEthernet 2/1/1 10.110.5.1/24 Router D GigabitEthernet 2/1/1 10.110.3.1/24 Router A GigabitEthernet 2/1/2 10.110.2.2/24 Router D GigabitEthernet 2/1/2 10.110.4.1/24 Router B GigabitEthernet 2/1/1 10.110.1.
[RouterB-GigabitEthernet2/1/3] quit [RouterB] interface loopback 0 [RouterB-LoopBack0] pim sm [RouterB-LoopBack0] quit [RouterB] interface loopback 10 [RouterB-LoopBack10] pim sm [RouterB-LoopBack10] quit [RouterB] interface loopback 20 [RouterB-LoopBack20] pim sm [RouterB-LoopBack20] quit # Enable IP multicast routing, IGMP, and PIM-SM on Router A, Router C, Router D, and Router E in the same way Router B is configured. (Details not shown.) 4.
# Send an IGMP report from Host A to join the multicast group 225.1.1.1. (Details not shown.) # Send multicast data from Source 1 10.110.5.100/24 to the multicast group 225.1.1.1. (Details not shown.) # Display the PIM routing table on Router D. [RouterD] display pim routing-table No information is output on Router D. # Display the PIM routing table on Router B. [RouterB] display pim routing-table Total 1 (*, G) entry; 1 (S, G) entry (*, 225.1.1.1) RP: 10.1.1.
(*, 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: GigabitEthernet2/1/1 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: GigabitEthernet2/1/2 Upstream neighbor: 10.110.4.2 RPF prime neighbor: 10.110.4.
Figure 55 Network diagram PIM-SM 1 PIM-SM 2 Loop0 PIM-SM 3 Source 2 GE2/1/1 Receiver Host A Router A GE 2/1 /3 GE2/1/2 Loop0 GE 2/1 /3 GE2/1/1 Router C GE2/1/3 GE2/1/2 Source 1 GE2/1/2 /3 2/1 GE /4 2/1 GE GE2/1/1 Router D GE2/1/2 GE2/1/1 Router B Receiver Host B MSDP peers Receiver Host C Table 15 Interface and IP address assignment Device Interface IP address Device Interface IP address Source 1 — 10.110.3.100/24 Router C GigabitEthernet 2/1/1 10.110.4.
{ 3. The routers can dynamically update routing information. Enable IP multicast routing, IGMP, and PIM-SM, and configure a PIM domain border: # On Router A, enable IP multicast routing. system-view [RouterA] multicast routing [RouterA-mrib] quit # Enable IGMP on GigabitEthernet 2/1/1 (the interface that connects to the receiver host).
[RouterA-msdp] quit # Configure MSDP peers on Router C. [RouterC] msdp [RouterC-msdp] peer 192.168.1.1 connect-interface gigabitethernet 2/1/3 [RouterC-msdp] peer 10.110.5.2 connect-interface gigabitethernet 2/1/2 [RouterC-msdp] quit # Configure an MSDP peer on Router D. [RouterD] msdp [RouterD-msdp] peer 10.110.5.1 connect-interface gigabitethernet 2/1/3 [RouterD-msdp] quit 6.
MSDP Total Source-Active Cache - 4 entries Matched 4 entries Source Group Origin RP Pro AS Uptime Expires 10.110.3.100 226.1.1.0 1.1.1.1 ? ? 00:32:53 00:05:07 10.110.3.100 226.1.1.1 1.1.1.1 ? ? 00:32:53 00:05:07 10.110.3.100 226.1.1.2 1.1.1.1 ? ? 00:32:53 00:05:07 10.110.3.100 226.1.1.3 1.1.1.1 ? ? 00:32:53 00:05:07 Troubleshooting MSDP This section describes common MSDP problems and how to troubleshoot them.
Solution 1. Use the display ip routing-table command to verify that the unicast route between the routers is reachable. 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 make sure the ACL rule filters appropriate (S, G) entries. 4. If the problem persists, contact HP Support.
Configuring multicast VPN Overview Multicast VPN is a technique that implements multicast delivery in VPNs. A VPN comprises multiple sites of the customer network and the public network provided by the network service provider. The sites communicate through the public network. As shown in Figure 56: • VPN A comprises Site 1, Site 3, and Site 5. • VPN B comprises Site 2, Site 4, and Site 6.
can consider these instances on PE 1 to be independent virtual devices, which are PE 1', PE 1", and PE 1'". Each virtual device works on a plane, as shown in Figure 57. Figure 57 Multicast in multiple VPN instances Through multicast VPN, multicast data of VPN A for a multicast group can arrive at only receiver hosts in Site 1, Site 3, and Site 5 of VPN A. The stream is multicast in these sites and on the public network. The prerequisites for implementing multicast VPN are as follows: 1.
Table 16 Basic MD-VPN concepts Concept Description Multicast domain (MD) An MD is a set of VPN instances running on PE devices that can send multicast traffic to each other. Each MD uniquely corresponds to the same set of VPN instances. Multicast distribution tree (MDT) An MDT is a multicast distribution tree constructed by all PE devices in the same VPN. MDT types include default-MDT and data-MDT.
As shown in Figure 57, the ellipse area in the center of each VPN instance plane represents an MD that provides services for a particular VPN instance. All the VPN multicast traffic in that VPN is transmitted within that MD. • Inside an MD, all the private traffic is transmitted through the MT. The process of multicast traffic transmission through an MT is as follows: a. The local PE device encapsulates a VPN multicast packet into a public network multicast packet. b.
{ • Uses the address to encapsulate the multicast packets for that VPN. All the PE devices in the network monitor the forwarding rate on the default-MDT. a. When the rate of a VPN multicast stream that entered the public network at a specific PE device exceeds the threshold, the PE device initiates an MDT switchover message. The message travels to the downstream along the default-MDT.
Protocols and standards RFC 6037, Cisco Systems' Solution for Multicast in BGP/MPLS IP VPNs How MD-VPN works This section describes how the MD-VPN technology is implemented, including the default-MDT construction, multicast traffic delivery based on the default-MDT, and inter-AS MD-VPN implementation. The VPN multicast data transmission on the public network is transparent to this VPN instance. The VPN data is exchanged between the MTIs of the local PE and the remote PE.
2. At the same time, PE 2 and PE 3 separately initiate a similar flood-prune process. Finally, three independent SPTs are established in the MD, constituting a default-MDT in the PIM-DM network. Default-MDT establishment in a PIM-SM network Figure 61 Default-MDT establishment in a PIM-SM network As shown in Figure 61, PIM-SM is enabled in the network, and all the PE devices support VPN instance A. The process of establishing a default-MDT is as follows: 1.
Default-MDT characteristics No matter which PIM mode is running on the public network, the default-MDT has the following characteristics: • All PE devices that support the same VPN instance join the default-MDT. • All multicast packets that belong to this VPN are forwarded along the default-MDT to every PE device on the public network, even if no active downstream receivers exist. Default-MDT-based delivery The default-MDT delivers multicast protocol packets and multicast data packets differently.
Figure 62 Transmission of multicast protocol packets BGP: 11.1.3.1/24 PE 3 Source Receiver RP CE 1 Site 1 P PE 1 PE 2 MD BGP: 11.1.1.1/24 CE 2 BGP: 11.1.2.1/24 Site 2 Public instance BGP peers S: 192.1.1.1/24 G: 225.1.1.1 VPN instance join (*, 225.1.1.1) Default-group: 239.1.1.1 Public instance join (11.1.2.1, 239.1.1.1) The multicast protocol packet is delivered as follows: 1. Receiver sends an IGMP report to CE 2 to join the multicast group G. CE 2 creates a local state entry (*, 225.
multicast packets on the local PE device, and transmitted along the default-MDT. When the VPN multicast packets arrive at the remote PE device, they are decapsulated and transmitted in that VPN site. VPN multicast data packets are forwarded across the public network differently in the following circumstances: • If PIM-DM or PIM-SSM is running in the VPN, the multicast source forwards multicast data packets to the receivers along the VPN SPT across the public network.
1. Source sends a VPN multicast data packet (192.1.1.1, 225.1.1.1) to CE 1. 2. CE 1 forwards the VPN multicast data packet along an SPT to PE 1, and the VPN instance on PE 1 examines the MVRF. If the outgoing interface list of the forwarding entry contains an MTI, PE 1 processes the VPN multicast data packet as described in step 3. The VPN instance on PE 1 considers the VPN multicast data packet to have been sent out of the MTI, because step 3 is transparent to it. 3.
If so, it joins the data-MDT rooted at PE 1. Otherwise, it caches the message and will join the data-MDT when it has attached receivers. 4. After sending the MDT switchover message, PE 1 waits a certain period of time (known as the data-delay period). After this period of time, PE 1 starts using the default-group address to encapsulate the VPN multicast data. The multicast data is then forwarded down the data-MDT. 5.
Figure 64 VPN instance-VPN instance interconnectivity By using this method, a separate MD must be established within each AS, and VPN multicast data traffic between different ASs is transmitted between the two MDs. Because only VPN multicast data traffic is forwarded between ASBRs, different PIM modes can run within different ASs. However, the same PIM mode must run on all interfaces that belong to the same VPN (including interfaces with VPN bindings on ASBRs).
Task at a glance • (Required.) Creating the MD for a VPN instance • (Required.) Specifying the default-group address • (Required.) Specifying the MD source interface • (Optional.) Configuring MDT switchover parameters • (Optional.) Enabling data-group reuse logging Configuring BGP MDT: • (Required.) Enabling BGP MDT peers or peer groups • (Optional.
Step Command Remarks 1. Enter system view. system-view N/A 2. Create a VPN instance and enter VPN instance view. By default, no VPN instance exists on the device. ip vpn-instance vpn-instance-name For more information about this command, see MPLS Command Reference. By default, no RD is configured for a VPN instance. 3. Configure an RD for the VPN instance. route-distinguisher route-distinguisher 4. Return to system view. quit N/A 5.
Step 3. Specify address. a default-group Command Remarks default-group group-address By default, no default-group address is specified. Specifying the MD source interface The MTI uses the IP address of the MD source interface as the source address to encapsulate the VPN multicast packets. The IP address of the MD source interface must be the same as the source address used for establishing BGP peer relationship. Otherwise, correct routing information cannot be obtained.
Step Command 5. Configure the data-holddown period. data-holddown delay Remarks Optional. The default setting is 60 seconds. Enabling data-group reuse logging For a given VPN, the number of VPN multicast streams to be switched to data-MDTs might exceed the number of addresses in the data-group address range. In this case, the VPN instance on the source-side PE device can reuse the addresses in the address range. With data-group reuse logging enabled, the address reuse information will be logged.
The MDT information includes the IP address of the PE and the default-group to which the PE belongs. On a public network running PIM-SSM, the multicast VPN establishes a default-MDT rooted at the PE (multicast source) based on the MDT information. Perform the following tasks on the PE. To configure BGP MDT peers or peer groups: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Create a BGP IPv4 MDT address family and enter its view.
Step Command Remarks 4. Configure the device as a route reflector and specify its peers or peer groups as clients. peer { group-name | ip-address } reflect-client By default, neither route reflectors nor clients exist. 5. Disable route between clients. undo reflect between-clients reflection 6. Configure the cluster IDs of the route reflectors. Optional. reflector cluster-id { cluster-id | ip-address } By default, clients can reflect routes with each other. Optional.
Intra-AS MD VPN configuration example Network requirements Item Network requirements • In VPN instance a, S 1 is a multicast source, and R 1, R 2, and R 3 are receivers. Multicast sources and receivers • In VPN instance b, S 2 is a multicast source, and R 4 is a receiver. • For VPN instance a, the default-group address is 239.1.1.1, and the data-group address range is 225.2.2.0 to 225.2.2.15. • For VPN instance b, the default-group address is 239.2.2.2, and the data-group address range is 225.4.4.
Figure 66 Network diagram VPN a Loop1 S2 VPN b GE2/1/1 CE b1 GE 2/1 /2 GE 2/1 /2 GE GE GE 2/1 /2 CE a1 GE2/1/1 GE 2/1 /3 VPN a R3 GE 2/1 /3 /3 2/1 Loop1 GE2/1/1 Loop1 GE 2 2/1 /1/2 /1 /1 2/1 GE 2/1/1 GE S1 CE a2 /2 2/1 GE Loop1 PE 2 R1 GE 2/1 /1 R2 /2 2/1 /1/2 CE a3 2 GE GE GE2/1/1 GE2/1/3 PE 3 P GE GE 2/1 2/1 /2 /3 GE2/1/1 Loop2 /2 /3 2/1 2/1 GE GE PE 1 CE b2 R4 Public Loop1 VPN b VPN a Table 17 Interface and IP address assignment Device Interface IP address Devi
Device Interface IP address Device Interface IP address PE 1 GigabitEthernet 2/1/3 10.110.2.1/24 CE a3 GigabitEthernet 2/1/2 10.110.5.2/24 PE 1 Loopback 1 1.1.1.1/32 CE a3 GigabitEthernet 2/1/3 10.110.12.2/24 PE 2 GigabitEthernet 2/1/1 192.168.7.1/24 CE b1 GigabitEthernet 2/1/1 10.110.8.1/24 PE 2 GigabitEthernet 2/1/2 10.110.3.1/24 CE b1 GigabitEthernet 2/1/2 10.110.3.2/24 PE 2 GigabitEthernet 2/1/3 10.110.4.1/24 CE b2 GigabitEthernet 2/1/1 10.110.11.
[PE1-GigabitEthernet2/1/1] pim sm [PE1-GigabitEthernet2/1/1] mpls enable [PE1-GigabitEthernet2/1/1] mpls ldp enable [PE1-GigabitEthernet2/1/1] quit # Bind GigabitEthernet 2/1/2 with VPN instance a, assign an IP address to GigabitEthernet 2/1/2, and enable IGMP on the interface. [PE1] interface gigabitethernet 2/1/2 [PE1-GigabitEthernet2/1/2] ip binding vpn-instance a [PE1-GigabitEthernet2/1/2] ip address 10.110.1.
[PE1] rip 2 vpn-instance a [PE1-rip-2] network 10.0.0.0 [PE1-rip-2] import-route bgp [PE1-rip-2] return 2. Configure PE 2: # Configure a Router ID globally, and enable IP multicast routing on the public network. system-view [PE2] router id 1.1.1.2 [PE2] multicast routing [PE2-mrib] quit # Configure an MPLS LSR ID, and enable the LDP capability. [PE2] mpls lsr-id 1.1.1.2 [PE2] mpls ldp [PE2-ldp] quit # Create VPN instance b and configure an RD and route target attributes for the instance.
# Assign an IP address to the public network interface GigabitEthernet 2/1/1, and enable PIM-SM, MPLS capability, and LDP capability on the interface. [PE2] interface gigabitethernet 2/1/1 [PE2-GigabitEthernet2/1/1] ip address 192.168.7.
[PE2–bgp] quit # Configure OSPF. [PE2] ospf 1 [PE2-ospf-1] area 0.0.0.0 [PE2-ospf-1-area-0.0.0.0] network 1.1.1.2 0.0.0.0 [PE2-ospf-1-area-0.0.0.0] network 192.168.0.0 0.0.255.255 [PE2-ospf-1-area-0.0.0.0] quit [PE2-ospf-1] quit # Configure RIP. [PE2] rip 2 vpn-instance a [PE2-rip-2] network 10.0.0.0 [PE2-rip-2] import-route bgp [PE2-rip-2] quit [PE2] rip 3 vpn-instance b [PE2-rip-3] network 10.0.0.0 [PE2-rip-3] import-route bgp [PE2-rip-3] return 3.
[PE3-vpn-instance-b] vpn-target 200:1 export-extcommunity [PE3-vpn-instance-b] vpn-target 200:1 import-extcommunity [PE3-vpn-instance-b] quit # Enable IP multicast routing in VPN instance b. [PE3] multicast routing vpn-instance b [PE3-mrib-b] quit # Create the MD for VPN instance b, and specify the default-group, MD source interface, and data-group address range for the MD. [PE3] multicast-domain vpn-instance b [PE3-md-b] default-group 239.2.2.2 [PE3-md-b] source loopback 1 [PE3-md-b] data-group 225.4.4.
# Configure Loopback 2 as a C-BSR and C-RP for VPN instance b. [PE3] pim vpn-instance b [PE3-pim-b] c-bsr 33.33.33.33 [PE3-pim-b] c-rp 33.33.33.33 [PE3-pim-b] quit # Configure BGP. [PE3] bgp 100 [PE3-bgp] group vpn-g internal [PE3-bgp] peer vpn-g connect-interface loopback 1 [PE3-bgp] peer 1.1.1.1 group vpn-g [PE3-bgp] peer 1.1.1.
[P] multicast routing [P-mrib] quit # Configure an MPLS LSR ID, and enable the LDP capability. [P] mpls lsr-id 2.2.2.2 [P] mpls ldp [P-ldp] quit # Assign an IP address to the public network interface GigabitEthernet 2/1/1, and enable PIM-SM, MPLS capability, and LDP capability on the interface. [P] interface gigabitethernet 2/1/1 [P-GigabitEthernet2/1/1] ip address 192.168.6.
system-view [CEa1] multicast routing [CEa1-mrib] quit # Assign an IP address to GigabitEthernet 2/1/1, and enable PIM-SM on the interface. [CEa1] interface gigabitethernet 2/1/1 [CEa1-GigabitEthernet2/1/1] ip address 10.110.7.1 24 [CEa1-GigabitEthernet2/1/1] pim sm [CEa1-GigabitEthernet2/1/1] quit # Assign an IP address to GigabitEthernet 2/1/2, and enable PIM-SM on the interface. [CEa1] interface gigabitethernet 2/1/2 [CEa1-GigabitEthernet2/1/2] ip address 10.110.2.
[CEa2-GigabitEthernet2/1/2] ip address 10.110.4.2 24 [CEa2-GigabitEthernet2/1/2] pim sm [CEa2-GigabitEthernet2/1/2] quit # Assign an IP address to GigabitEthernet 2/1/3, and enable PIM-SM on the interface. [CEa2] interface gigabitethernet 2/1/3 [CEa2-GigabitEthernet2/1/3] ip address 10.110.12.1 24 [CEa2-GigabitEthernet2/1/3] pim sm [CEa2-GigabitEthernet2/1/3] quit # Assign an IP address to Loopback 1, and enable PIM-SM on the interface. [CEa2] interface loopback 1 [CEa2-LoopBack1] ip address 22.22.22.
# Enable IP multicast routing. system-view [CEb2] multicast routing [CEb2-mrib] quit # Assign an IP address to GigabitEthernet 2/1/1, and enable IGMP on the interface. [CEb2] interface gigabitethernet 2/1/1 [CEb2-GigabitEthernet2/1/1] ip address 10.110.11.1 24 [CEb2-GigabitEthernet2/1/1] igmp enable [CEb2-GigabitEthernet2/1/1] quit # Assign an IP address to GigabitEthernet 2/1/2, and enable PIM-SM on the interface. [CEb2] interface gigabitethernet 2/1/2 [CEb2-GigabitEthernet2/1/2] ip address 10.
Item Network requirements • PE 1: GigabitEthernet 2/1/2 belongs to VPN instance a. GigabitEthernet 2/1/3 belongs to VPN instance b. GigabitEthernet 2/1/1 and Loopback 1 belong to the public network instance. PE interfaces and VPN instances to which they belong • PE 2: GigabitEthernet 2/1/1, GigabitEthernet 2/1/2, Loopback 1, and Loopback 2 belong to the public network instance. • PE 3: GigabitEthernet 2/1/1, GigabitEthernet 2/1/2, Loopback 1, and Loopback 2 belong to the public network instance.
Lo op 2 Lo op 2 1 op Lo Lo op 1 Figure 67 Network diagram Table 18 Interface and IP address assignment Device Interface IP address Device Interface IP address S1 — 10.11.5.2/24 R1 — 10.11.8.2/24 S2 — 10.11.6.2/24 R2 — 10.11.7.2/24 PE 1 GigabitEthernet 2/1/1 10.10.1.1/24 PE 3 GigabitEthernet 2/1/1 10.10.2.1/24 PE 1 GigabitEthernet 2/1/2 10.11.1.1/24 PE 3 GigabitEthernet 2/1/2 192.168.1.2/24 PE 1 GigabitEthernet 2/1/3 10.11.2.1/24 PE 3 Loopback 1 1.1.1.
Device Interface IP address Device Interface IP address CE a1 Loopback 0 2.2.2.2/32 CE b2 GigabitEthernet 2/1/1 10.11.8.1/24 CE a2 GigabitEthernet 2/1/1 10.11.7.1/24 CE b2 GigabitEthernet 2/1/2 10.11.4.2/24 CE a2 GigabitEthernet 2/1/2 10.11.3.2/24 CE b2 Loopback 0 3.3.3.3/32 Configuration procedure 1. Configure PE 1: # Configure a Router ID, and enable IP multicast routing on the public network. system-view [PE1] router id 1.1.1.
# Create the MD for VPN instance b, and specify the default-group, MD source interface, and data-group address range for the MD. [PE1] multicast-domain vpn-instance b [PE1-md-b] default-group 239.4.4.4 [PE1-md-b] source loopback 1 [PE1-md-b] data-group 225.4.4.0 28 [PE1-md-b] quit # Assign an IP address to the public network interface GigabitEthernet 2/1/1, and enable PIM-SM, MPLS capability, and LDP capability on the interface.
[PE1-bgp-ipv4-a] import-route direct [PE1-bgp-ipv4-a] quit [PE1-bgp-a] quit [PE1–bgp] ip vpn-instance b [PE1-bgp-b] address-family ipv4 [PE1-bgp-ipv4-b] import-route ospf 3 [PE1-bgp-ipv4-b] import-route direct [PE1-bgp-ipv4-b] quit [PE1-bgp-b] quit [PE1–bgp] address-family ipv4 [PE1-bgp-ipv4] peer pe1-pe2 enable [PE1-bgp-ipv4] peer pe1-pe2 label-route-capability [PE1-bgp-ipv4] quit [PE1–bgp] address-family vpnv4 [PE1–bgp-vpnv4] peer pe1-pe4 enable [PE1–bgp-vpnv4] quit [PE1–bgp] quit # Configure OSPF.
# Assign an IP address to the public network interface GigabitEthernet 2/1/1, and enable PIM-SM, MPLS capability, and LDP capability on the interface. [PE2] interface gigabitethernet 2/1/1 [PE2-GigabitEthernet2/1/1] ip address 10.10.1.2 24 [PE2-GigabitEthernet2/1/1] pim sm [PE2-GigabitEthernet2/1/1] mpls enable [PE2-GigabitEthernet2/1/1] mpls ldp enable [PE2-GigabitEthernet2/1/1] quit # Assign an IP address to the public network interface GigabitEthernet 2/1/2, and enable PIM-SM and MPLS on the interface.
[PE2-bgp] peer pe2-pe3 connect-interface loopback 1 [PE2-bgp] peer 1.1.1.3 group pe2-pe3 [PE2-bgp] address-family ipv4 [PE2-bgp-ipv4] peer pe2-pe1 enable [PE2-bgp-ipv4] peer pe2-pe1 route-policy map2 export [PE2-bgp-ipv4] peer pe2-pe1 label-route-capability [PE2-bgp-ipv4] peer pe2-pe3 enable [PE2-bgp-ipv4] peer pe2-pe3 route-policy map1 export [PE2-bgp-ipv4] peer pe2-pe3 label-route-capability [PE2-bgp-ipv4] import-route ospf 1 [PE2-bgp-ipv4] quit [PE2–bgp] quit # Configure OSPF.
# Assign an IP address to the public network interface GigabitEthernet 2/1/2, and enable PIM-SM and MPLS on the interface. [PE3] interface gigabitethernet 2/1/2 [PE3-GigabitEthernet2/1/2] ip address 192.168.1.2 24 [PE3-GigabitEthernet2/1/2] pim sm [PE3-GigabitEthernet2/1/2] mpls enable [PE3-GigabitEthernet2/1/2] quit # Assign an IP address to Loopback 1, and enable PIM-SM on this interface. [PE3] interface loopback 1 [PE3-LoopBack1] ip address 1.1.1.
[PE3-bgp-ipv4] peer pe3-pe2 label-route-capability [PE3-bgp-ipv4] import-route ospf 1 [PE3-bgp-ipv4] quit [PE3–bgp] quit # Configure OSPF. [PE3] ospf 1 [PE3-ospf-1] area 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 1.1.1.3 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 22.22.22.22 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 10.10.0.0 0.0.255.255 [PE3-ospf-1-area-0.0.0.0] quit [PE3-ospf-1] quit # Configure a routing policy.
# Create VPN instance b and configure an RD and route target attributes for the instance. [PE4] ip vpn-instance b [PE4-vpn-instance-b] route-distinguisher 200:1 [PE4-vpn-instance-b] vpn-target 200:1 export-extcommunity [PE4-vpn-instance-b] vpn-target 200:1 import-extcommunity [PE4-vpn-instance-b] quit # Enable IP multicast routing in VPN instance b.
[PE4-bgp] peer 1.1.1.3 group pe4-pe3 [PE4-bgp] group pe4-pe1 external [PE4-bgp] peer pe4-pe1 as-number 100 [PE4-bgp] peer pe4-pe1 ebgp-max-hop 255 [PE4-bgp] peer pe4-pe1 connect-interface loopback 1 [PE4-bgp] peer 1.1.1.
[CEa1] multicast routing [CEa1-mrib] quit # Assign an IP address to GigabitEthernet 2/1/1, and enable PIM-SM on the interface. [CEa1] interface gigabitethernet 2/1/1 [CEa1-GigabitEthernet2/1/1] ip address 10.11.5.1 24 [CEa1-GigabitEthernet2/1/1] pim sm [CEa1-GigabitEthernet2/1/1] quit # Assign an IP address to GigabitEthernet 2/1/2, and enable PIM-SM on the interface. [CEa1] interface gigabitethernet 2/1/2 [CEa1-GigabitEthernet2/1/2] ip address 10.11.1.
[CEb1-ospf-1] area 0.0.0.0 [CEb1-ospf-1-area-0.0.0.0] network 10.11.0.0 0.0.255.255 [CEb1-ospf-1-area-0.0.0.0] quit [CEb1-ospf-1] quit 7. Configure CE a2: # Enable IP multicast routing. system-view [CEa2] multicast routing [CEa2-mrib] quit # Assign an IP address to GigabitEthernet 2/1/1, and enable IGMP on the interface . [CEa2] interface gigabitethernet 2/1/1 [CEa2-GigabitEthernet2/1/1] ip address 10.11.7.
[CEb2] pim [CEb2-pim] c-bsr 3.3.3.3 [CEb2-pim] c-rp 3.3.3.3 [CEb2-pim] quit # Configure OSPF. [CEb2] ospf 1 [CEb2-ospf-1] area 0.0.0.0 [CEb2-ospf-1-area-0.0.0.0] network 3.3.3.3 0.0.0.0 [CEb2-ospf-1-area-0.0.0.0] network 10.11.0.0 0.0.255.255 [CEb2-ospf-1-area-0.0.0.0] quit [CEb2-ospf-1] quit Verifying the configuration # Display information about the default-groups in VPN instances on PE 1. [PE1] display multicast-domain default-group Group address Source address Interface VPN instance 239.1.1.1 1.
enabled with PIM. A PIM neighboring relationship can be established between the same VPN instance on different PE devices only after the MTI interface obtains an IP address and becomes PIM-enabled. Solution 1. Use the display interface command to examine the MTI interface state and address encapsulation on the MTI. 2. Use the display multicast-domain default-group command to verify that the same default-group address has been configured for the same VPN instance on different PE devices. 3.
Configuring MLD snooping In this chapter, "MSR2000" refers to MSR2003. "MSR3000" collectively refers to MSR3012, MSR3024, MSR3044, MSR3064. "MSR4000" collectively refers to MSR4060 and MSR4080. Overview MLD snooping runs on a Layer 2 switch as an IPv6 multicast constraining mechanism to improve multicast forwarding efficiency. It creates Layer 2 multicast forwarding entries from MLD messages that are exchanged between the hosts and the router.
Figure 69 MLD snooping related ports The following describes the ports involved in MLD snooping, as shown in Figure 69: • Router port—Layer 3 multicast device-side port. Layer 3 multicast devices include DRs and MLD queriers. In Figure 69, GigabitEthernet 1/0/1 of Switch A and GigabitEthernet 1/0/1 of Switch B are the router ports. A switch records all its local router ports in a router port list.
NOTE: In MLD snooping, only dynamic ports age out. Static ports never age out. How MLD snooping works The ports in this section are dynamic ports. For information about how to configure and remove static ports, see "Configuring static ports." MLD messages include general query, MLD report, and done message. An MLD snooping-enabled switch performs differently depending on the MLD message types.
A Layer 2 device does not forward an MLD report through a non-router port because of the MLD report suppression mechanism. For more information about the MLD report suppression mechanism, see "Configuring MLD." Done message When a host leaves an IPv6 multicast group, the host sends an MLD done message to the Layer 3 devices.
MLD snooping configuration task list Task at a glance Configuring basic MLD snooping functions: • (Required.) Enabling MLD snooping • (Optional.) Specifying the MLD snooping version • (Optional.) Setting the maximum number of MLD snooping forwarding entries Configuring MLD snooping port functions: • • • • • (Optional.) Setting aging timers for dynamic ports (Optional.) Configuring static ports (Optional.) Configuring a port as a simulated member host (Optional.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enable MLD snooping globally and enter MLD-snooping view. mld-snooping By default, MLD snooping is disabled. 3. Enable MLD snooping for the specified VLANs. enable vlan vlan-list By default, MLD snooping is disabled for a VLAN. To enable MLD snooping for a VLAN in VLAN view: Step Command Remarks 1. Enter system view. system-view N/A 2. Enable MLD snooping globally and enter MLD-snooping view.
To specify the MLD snooping version for a VLAN in VLAN view: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VLAN view. vlan vlan-id N/A 3. Specify the version of MLD snooping. mld-snooping version version-number The default setting is MLDv1 snooping. Setting the maximum number of MLD snooping forwarding entries You can modify the maximum number of MLD snooping forwarding entries.
Setting the aging timers for dynamic ports globally Step Command Remarks 1. Enter system view. system-view N/A 2. Enter MLD-snooping view. mld-snooping N/A 3. Set the aging timer for dynamic router ports globally. router-aging-time interval The default setting is 260 seconds. 4. Set the aging timer for dynamic member ports globally. host-aging-time interval The default setting is 260 seconds. Setting the aging timers for the dynamic ports in a VLAN Step Command Remarks 1.
Step Command Remarks 4. Configure the port as a static router port. mld-snooping static-router-port vlan vlan-id By default, a port is not a static router port. Configuring a port as a simulated member host Generally, a host that runs MLD can respond to MLD queries. If a host fails to respond, the multicast router might consider that the IPv6 multicast group has no members on the subnet. Then, the router removes the corresponding forwarding path.
• You can enable MLD snooping fast-leave processing either on the current port in interface view or globally for all ports in MLD-snooping view. If configurations are made in both interface view and MLD-snooping view, the configuration made in interface view takes priority. To enable MLD snooping fast-leave processing globally: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter MLD-snooping view. mld-snooping N/A 3. Enable MLD snooping fast-leave processing globally.
Configuring the MLD snooping querier This section describes how to configure the MLD snooping querier. Configuration prerequisites Before you configure the MLD snooping querier, complete the following tasks: • Enable MLD snooping for the VLAN. • Determine the interval for sending MLD general queries. • Determine the MLD last listener query interval. • Determine the maximum response time for MLD general queries.
To speed up the response of hosts to MLD queries and to avoid simultaneous timer expirations from causing MLD report traffic bursts, you must correctly set the maximum response time. • The maximum response time for MLD general queries is set by the max-response-time command. • The maximum response time for MLD multicast-address-specific queries is the same as the MLD last listener query interval, which is set by the last-listener-query-interval command.
Configuring source IPv6 addresses for MLD messages You can perform the following configuration to change the source IPv6 address of MLD queries sent by an MLD snooping querier. You can also change the source IPv6 address of MLD reports or done messages sent by a simulated member host or an MLD snooping proxy. Changing the source IPv6 address of MLD queries might affect MLD querier election within the subnet. To configure the source IP address for MLD queries: Step Command Remarks 1. Enter system view.
Setting the 802.1p precedence for MLD messages globally Step Command Remarks 1. Enter system view. system-view N/A 2. Enter MLD-snooping view. mld-snooping N/A 3. Set the 802.1p precedence for MLD messages. dot1p-priority priority-number The default setting is 0. Setting the 802.1p precedence for MLD messages in a VLAN Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VLAN view. vlan vlan-id N/A 3. Set the 802.1p precedence for MLD messages.
Configuring an IPv6 multicast group filter on a port Step Command Remarks 1. Enter system view. system-view N/A 2. Enter Layer 2 Ethernet interface view. interface interface-type interface-number N/A 3. Configure an IPv6 multicast group filter for the port. mld-snooping group-policy acl6-number [ vlan vlan-list ] By default, no IPv6 multicast group filter is configured for the port. The hosts on this port can join any valid IPv6 multicast group.
Enabling dropping unknown IPv6 multicast data CAUTION: For MSR routers installed with the Layer 2 switching module SIC 4GSW or SIC 4GSWP, unknown IPv4 multicast data will be dropped if you enable dropping unknown IPv6 multicast data on them. Unknown IPv6 multicast data refers to IPv6 multicast data for which no forwarding entries exist in the MLD snooping forwarding table.
Setting the maximum number of IPv6 multicast groups on a port You can set the maximum number of IPv6 multicast groups on a port to regulate the port traffic. When you set the maximum number of IPv6 multicast groups on a port, follow these guidelines: • This configuration takes effect on the IPv6 multicast groups that the port dynamically joins. If you configure the port as a static member port for an IPv6 multicast group, this configuration does not take effect on the multicast group.
Step Command Remarks 3. Enable the IPv6 multicast group replacement function globally. overflow-replace [ vlan vlan-list ] By default, the IPv6 multicast group replacement function is disabled. To enable the IPv6 multicast group replacement on a port: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter Layer 2 Ethernet interface view. interface interface-type interface-number N/A 3. Enable the IPv6 multicast group replacement function on the port.
Task Command Display information about dynamic router ports (MSR2000/MSR3000). display mld-snooping router-port [ vlan vlan-id ] Display information about dynamic router ports (MSR4000). display mld-snooping router-port [ vlan vlan-id ] [ slot slot-number ] Display information about static MLD snooping forwarding entries (MSR2000/MSR3000).
Figure 70 Network diagram Configuration procedure 1. Assign an IPv6 address and prefix length to each interface according to Figure 70. (Details not shown.) 2. Configure Router A: # Enable IPv6 multicast routing. system-view [RouterA] ipv6 multicast routing [RouterA-mrib6] quit # Enable MLD on GigabitEthernet 2/1/1. [RouterA] interface gigabitethernet 2/1/1 [RouterA-GigabitEthernet2/1/1] mld enable [RouterA-GigabitEthernet2/1/1] quit # Enable IPv6 PIM-DM on GigabitEthernet 2/1/2.
# Configure an IPv6 multicast group filter so that the hosts in VLAN 100 can join only the IPv6 multicast group FF1E::101. [SwitchA] acl ipv6 number 2001 [SwitchA-acl6-basic-2001] rule permit source ff1e::101 128 [SwitchA-acl6-basic-2001] quit [SwitchA] mld-snooping [SwitchA–mld-snooping] group-policy 2001 vlan 100 [SwitchA–mld-snooping] quit # Configure GigabitEthernet 2/1/3 and GigabitEthernet 2/1/4 as simulated member hosts to join IPv6 multicast group FF1E::101.
• Suppose the STP runs on the network. To avoid data loops, the forwarding path from Switch A to Switch C is blocked under normal conditions. IPv6 multicast data flows to the receivers attached to Switch C only along the path of Switch A—Switch B—Switch C. When this path is blocked, at least one MLD query-response cycle must be completed before IPv6 multicast data flows to the receivers along the path of Switch A—Switch C. In this case, the multicast delivery is interrupted during the process.
[SwitchA-mld-snooping] quit # Create VLAN 100, assign GigabitEthernet 2/1/1 through GigabitEthernet 2/1/3 to the VLAN, and enable MLD snooping for the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 2/1/1 to gigabitethernet 2/1/3 [SwitchA-vlan100] mld-snooping enable [SwitchA-vlan100] quit # Configure GigabitEthernet 2/1/3 as a static router port.
Router ports (1 in total): GE2/1/3 The output shows that GigabitEthernet 2/1/3 on Switch A has become a static router port. # Display information about the static MLD snooping forwarding entries in VLAN 100 on Switch C. [SwitchC] display mld-snooping static-group vlan 100 Total 1 entries). VLAN 100: Total 1 entries).
Figure 72 Network diagram Configuration procedure 1. Configure Switch A: # Enable MLD snooping globally. system-view [SwitchA] mld-snooping [SwitchA-mld-snooping] quit # Create VLAN 100, assign GigabitEthernet 2/1/1 through GigabitEthernet 2/1/3 to the VLAN, and enable MLD snooping and dropping unknown IPv6 multicast packets for the VLAN.
# Enable MLD snooping globally. system-view [SwitchC] mld-snooping [SwitchC-mld-snooping] quit # Create VLAN 100, assign GigabitEthernet 2/1/1 through GigabitEthernet 2/1/3 to the VLAN, and enable MLD snooping and dropping unknown multicast packets for the VLAN. [SwitchC] vlan 100 [SwitchC-vlan100] port gigabitethernet 2/1/1 to gigabitethernet 2/1/3 [SwitchC-vlan100] mld-snooping enable [SwitchC-vlan100] mld-snooping drop-unknown [SwitchC-vlan100] quit 4.
Troubleshooting MLD snooping Layer 2 multicast forwarding cannot function Symptom Layer 2 multicast forwarding cannot function through MLD snooping. Analysis MLD snooping is not enabled. Solution 1. Use the display mld-snooping command to display MLD snooping status. 2. If MLD snooping is not enabled, use the mld-snooping command in system view to enable MLD snooping globally. Then, use the mld-snooping enable command in VLAN view to enable MLD snooping for the VLAN. 3.
Configuring IPv6 multicast routing and forwarding In this chapter, "MSR2000" refers to MSR2003. "MSR3000" collectively refers to MSR3012, MSR3024, MSR3044, MSR3064. "MSR4000" collectively refers to MSR4060 and MSR4080. Overview IPv6 multicast routing and forwarding uses the following tables: • IPv6 multicast protocols' routing tables, such as the IPv6 PIM routing table.
priority as the RPF route. If the routes have the same priority, the router selects the IPv6 MBGP route as the RPF route. For more information about the route preference, see Layer 3—IP Routing Configuration Guide. { If the router does not use the longest prefix match principle, the router selects the route that has a higher priority as the RPF route. If the routes have the same priority, the router selects the IPv6 MBGP route as the RPF route.
Figure 73 RPF check process IPv6 Routing Table on Router C Destination/Prefix Interface 2000::/16 GE1/0/2 Router B Receiver GE1/0/1 Source 2000::101/16 Router A GE1/0/2 IPv6 Multicast packets GE1/0/1 Receiver Router C As shown in Figure 73, assume that IPv6 unicast routes are available in the network, IPv6 MBGP is not configured. The IPv6 multicast packets travel along the SPT from the multicast source to the receivers.
As shown in Figure 74, a tunnel is established between the multicast routers Router A and Router B. Router A encapsulates the IPv6 multicast data in unicast IPv6 packets, and forwards them to Router B across the tunnel through unicast routers. Then, Router B strips off the unicast IPv6 header and continues to forward the IPv6 multicast data down toward the receivers. Configuration task list Tasks at a glance (Required.) Enabling IPv6 multicast routing (Optional.
Step Command Remarks 3. Configure the device to select the RPF route based on the longest prefix match. longest-match By default, the route with the highest priority is selected as the RPF route. Configuring IPv6 multicast load splitting By configuring per-source or per-source-and-group load splitting, you can optimize the traffic delivery when multiple IPv6 multicast data streams are handled. You do not need to enable IPv6 multicast routing before this configuration.
Displaying and maintaining IPv6 multicast routing and forwarding CAUTION: The reset commands might cause IPv6 multicast data transmission failures. Execute display commands in any view and reset commands in user view. Task Command Display information about the interfaces maintained by the IPv6 MRIB. display ipv6 mrib [ vpn-instance vpn-instance-name ] interface [ interface-type interface-number ] Display IPv6 multicast boundary information.
Task Command Display information about the IPv6 multicast routing table. display ipv6 multicast [ vpn-instance vpn-instance-name ] routing-table [ ipv6-source-address [ prefix-length ] | ipv6-group-address [ prefix-length ] | incoming-interface interface-type interface-number | outgoing-interface { exclude | include | match } interface-type interface-number ] * Display the RPF route information of the specified IPv6 multicast source.
Figure 75 Network diagram Configuration procedure 1. Assign an IP address and prefix length to each interface according to Figure 75. (Details not shown.) 2. Configure OSPFv3 on the routers to make sure the following conditions are met: (Details not shown.) 3. { The routers are interoperable at the network layer. { The routers can dynamically update their routing information. Configure a GRE tunnel: # Create interface Tunnel 0 on Router A and specify the tunnel encapsulation mode as GRE over IPv6.
[RouterA-GigabitEthernet2/1/1] ipv6 pim dm [RouterA-GigabitEthernet2/1/1] quit [RouterA] interface gigabitethernet 2/1/2 [RouterA-GigabitEthernet2/1/2] ipv6 pim dm [RouterA-GigabitEthernet2/1/2] quit [RouterA] interface tunnel 0 [RouterA-Tunnel0] ipv6 pim dm [RouterA-Tunnel0] quit # On Router C, enable IPv6 multicast routing. [RouterC] ipv6 multicast routing [RouterC-mrib6] quit # Enable MLD on GigabitEthernet 2/1/1 (the interface that connects to the receiver host).
Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet2/1/1 Protocol: pim-dm, UpTime: 00:04:25, Expires: - The output shows the following: • Router A is the RPF neighbor of Router C. • The IPv6 multicast data from Router A is delivered over a GRE tunnel to Router C.
Configuring MLD MLD is not supported on SIC-4FSW, 4FSWP, SIC-9FSW, or 9FSWP. Overview Multicast Listener Discovery (MLD) establishes and maintains IPv6 multicast group memberships between a Layer 3 multicast device and its directly connected hosts. MLD has two versions: • MLDv1 (defined by RFC 2710), which is derived from IGMPv2. • MLDv2 (defined by RFC 3810), which is derived from IGMPv3. The two MLD versions support the ASM model.
Joining an IPv6 multicast group Figure 76 MLD queries and reports IPv6 network Querier Router A Router B Ethernet Host A (G2) Host B (G1) Host C (G1) Query Report As shown in Figure 76, Host B and Host C want to receive the IPv6 multicast data addressed to IPv6 multicast group G1. Host A wants to receive the IPv6 multicast data addressed to G2.
1. The host sends an MLD done message to all IPv6 multicast routers on the local subnet. The destination address is FF02::2. 2. After receiving the MLD done message, the querier sends a configurable number of multicast-address-specific queries to the group that the host is leaving. The IPv6 multicast addresses queried include both the destination address field and the group address field of the message. 3.
When MLDv2 runs on the hosts and routers, Host B can explicitly express its interest in the IPv6 multicast data that Source 1 sends to G (denoted as (S1, G)). It can also explicitly express that it does not want to receive the IPv6 multicast data that Source 2 sends to G (denoted as (S2, G)). As a result, Host B receives only IPv6 multicast data from Source 1.
• If G is in the IPv6 SSM group range but does not have relevant MLD SSM mappings, Router A drops the packet. • If G is in the IPv6 SSM group range, and has relevant MLD SSM mappings, Router A translates the (*, G) information in the MLD report into (G, INCLUDE, (S1, S2...)) information to provide the SSM service. NOTE: The MLD SSM mapping feature does not process MLDv2 reports. For more information about the IPv6 SSM group ranges, see "Configuring IPv6 PIM.
An MLD proxy device performs host functions on the upstream interface based on the membership database. It responds to the MLD queries according to the information in the database or sends report/done messages when the database changes. The MLD proxy device performs router functions on the downstream interfaces by participating in the querier election, sending queries, and maintaining memberships based on the reports. MLD support for VPNs MLD maintains group memberships on a per-interface base.
Enabling MLD Enable MLD on the interface on which IPv6 multicast group memberships are created and maintained. To enable MLD: Step Command Remarks 1. Enter system view. system-view N/A 2. Enable IPv6 multicast routing and enter IPv6 MRIB view. ipv6 multicast routing [ vpn-instance vpn-instance-name ] By default, IPv6 multicast routing is disabled. 3. Return to system view. quit N/A 4. Enter interface view. interface interface-type interface-number N/A 5. Enable MLD.
Configuration procedure To configure an interface as a static member interface: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Configure the interface as a static member interface. mld static-group ipv6-group-address [ source ipv6-source-address ] By default, an interface is not a static member of any IPv6 multicast group or IPv6 multicast source and group.
When multiple IPv6 multicast routers exist on the same subnet, only the MLD querier sends MLD queries. When a non-querier router receives an MLD query, it starts an MLD other querier present timer. If it receives a new MLD query before the timer expires, it resets the timer. Otherwise, it considers that the querier has failed and starts a new querier election. To avoid frequent MLD querier changes, set the MLD other querier present interval greater than the MLD general query interval.
Configuration prerequisites Before you configure the MLD SSM mapping feature, complete the following tasks: • Configure an IPv6 unicast routing protocol so that all devices in the domain are interoperable at the network layer. • Configure basic MLD functions. Configuration procedure To configure MLD SSM mappings: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter MLD view.
Step Command Remarks 2. Enable IPv6 multicast routing and enter IPv6 MRIB view. ipv6 multicast routing [ vpn-instance vpn-instance-name ] By default, IPv6 multicast routing is disabled. 3. Return to system view. quit N/A 4. Enter interface view. interface interface-type interface-number N/A 5. Enable the MLD proxying feature. mld proxy enable By default, MLD proxying is disabled.
Step Command Remarks 3. Enable the load splitting function on the MLD proxy. proxy multipath By default, the load splitting function is disabled. Displaying and maintaining MLD CAUTION: The reset mld group command might cause IPv6 multicast data transmission failures. Execute display commands in any view and reset commands in user view. Task Command Remarks Display MLD group information.
• VOD streams are sent to receiver hosts in multicast. Receiver hosts of different organizations form stub networks N1 and N2. Host A and Host C are multicast receiver hosts in N1 and N2, respectively. • MLDv1 runs between Router A and N1, and between the other two routers (Router B and Router C) and N2. • Router A acts as the MLD querier in N1. Router B acts as the MLD querier in N2 because it has a lower IPv6 address.
[RouterA-GigabitEthernet2/1/1] quit # Enable IPv6 PIM-DM on GigabitEthernet 2/1/2. [RouterA] interface gigabitethernet 2/1/2 [RouterA-GigabitEthernet2/1/2] ipv6 pim dm [RouterA-GigabitEthernet2/1/2] quit # On Router B, enable IPv6 multicast routing. system-view [RouterB] ipv6 multicast routing [RouterB-mrib6] quit # Enable MLD on GigabitEthernet 2/1/1.
Querier for MLD: FE80::200:5EFF:FE66:5100 (this router) MLD groups reported in total: 1 MLD SSM mapping configuration example Network requirements As shown in Figure 81: • The IPv6 PIM-SM domain uses both the ASM model and SSM model for IPv6 multicast delivery. GigabitEthernet 2/1/3 of Router D serves as the C-BSR and C-RP. The IPv6 SSM group range is FF3E::/64. • MLDv2 runs on GigabitEthernet 2/1/1 of Router D. The receiver host runs MLDv1, and does not support MLDv2.
2. 3. Configure OSPFv3 on the routers in the IPv6 PIM-SM domain to make sure the following conditions are met: (Details not shown.) { The routers are interoperable at the network layer. { The routers can dynamically update their routing information. Enable IPv6 multicast routing, IPv6 PIM-SM, and MLD: # On Router D, enable IPv6 multicast routing.
[RouterD-pim6] ssm-policy 2000 [RouterD-pim6] quit # Configure Router A, Router B, and Router C in the same way Router D is configured. (Details not shown.) 6. Configure MLD SSM mappings on Router D. [RouterD] mld [RouterD-mld] ssm-mapping 1001::1 2000 [RouterD-mld] ssm-mapping 3001::1 2000 [RouterD-mld] quit Verifying the configuration # Display MLD SSM mapping information for IPv6 multicast group FF3E::101 on Router D.
Upstream neighbor: 3002::1 RPF prime neighbor: 3002::1 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet2/1/1 Protocol: mld, UpTime: 00:13:25, Expires: - MLD proxying configuration example Network requirements As shown in Figure 82, IPv6 PIM-DM runs on the core network. Host A and Host C in the stub network receive VOD information sent to IPv6 multicast group FF3E::101.
system-view [RouterB] ipv6 multicast routing [RouterB-mrib6] quit # Enable MLD proxying on GigabitEthernet 2/1/1. [RouterB] interface gigabitethernet 2/1/1 [RouterB-GigabitEthernet2/1/1] mld proxy enable [RouterB-GigabitEthernet2/1/1] quit # Enable MLD on GigabitEthernet 2/1/2.
{ The IPv6 addresses are not correctly configured. 2. Use the display current-configuration command to verify that the IPv6 multicast routing is enabled. If it is not enabled, use the ipv6 multicast routing command in system view to enable IPv6 multicast routing. In addition, verify that MLD is enabled on the associated interfaces. 3. Use the display mld interface command to verify that the MLD version on the interface is lower than that on the host. 4.
Configuring IPv6 PIM Overview IPv6 Protocol Independent Multicast (IPv6 PIM) provides IPv6 multicast forwarding by leveraging IPv6 unicast static routes or IPv6 unicast routing tables generated by any IPv6 unicast routing protocol, such as RIPng, OSPFv3, IPv6 IS-IS, or IPv6 BGP. IPv6 PIM uses the underlying IPv6 unicast routing to generate an IPv6 multicast routing table without relying on any particular IPv6 unicast routing protocol. IPv6 PIM uses the RPF mechanism to implement multicast forwarding.
routers discover their IPv6 PIM neighbors, maintain IPv6 PIM neighboring relationship with other routers, and build and maintain SPTs. SPT building The process of building an SPT is the flood-and-prune process: 1. In an IPv6 PIM-DM domain, the IPv6 multicast data from the IPv6 multicast source S to the IPv6 multicast group G is flooded throughout the domain. A router performs an RPF check for the IPv6 multicast data.
1. The node that needs to receive the IPv6 multicast data sends a graft message to its upstream node, telling it to rejoin the SPT. 2. After receiving this graft message, the upstream node adds the receiving interface to the outgoing interface list of the (S, G) entry for the IPv6 multicast group. It also sends a graft-ack message to the graft sender. 3. If the graft sender receives a graft-ack message, the graft process finishes.
The basic implementation of IPv6 PIM-SM is as follows: • IPv6 PIM-SM assumes that no hosts need IPv6 multicast data. In the IPv6 PIM-SM mode, a host must express its interest in the IPv6 multicast data for an IPv6 multicast group before the data is forwarded to it. IPv6 PIM-SM implements multicast forwarding by building and maintaining rendezvous point trees (RPTs). An RPT is rooted at a router that has been configured as the rendezvous point (RP) for an IPv6 multicast group.
Figure 85 DR election As shown in Figure 85, the DR election process is as follows: 1. The routers on the shared-media LAN send hello messages to one another. The hello messages contain the DR priority for DR election. The router with the highest DR priority is elected as the DR. 2. The router with the highest IPv6 link-local address wins the DR election under either of the following conditions: a. All the routers have the same DR priority. b.
The BSR encapsulates the RP-set information in the bootstrap messages (BSMs) and floods the BSMs to the entire IPv6 PIM-SM domain. Figure 86 Information exchange between C-RPs and BSR Based on the information in the RP-set, all routers in the network can select an RP for a specific IPv6 multicast group based on the following rules: 1. The C-RP that is designated to the smallest IPv6 multicast group range wins. 2.
Anycast RP has the following benefits: • Optimal RP path—An IPv6 multicast source registers with the nearest RP to build an optimal SPT. A receiver joins the nearest RP to build an optimal RPT. • Redundancy backup among RPs—When an RP fails, the RP-related sources and receiver-side DRs will register with or join their nearest available RPs. This achieves redundancy backup among RPs.
RPT building Figure 88 RPT building in an IPv6 PIM-SM domain Host A Source RP DR Server Receiver Host B DR Receiver RPT Join message IPv6 multicast packets Host C As shown in Figure 88, the process of building an RPT is as follows: 1. When a receiver wants to join the IPv6 multicast group G, it uses an MLD message to inform the receiver-side DR. 2. After getting the receiver information, the DR sends a join message, which is forwarded hop by hop to the RP for the IPv6 multicast group. 3.
Figure 89 IPv6 multicast source registration As shown in Figure 89, the IPv6 multicast source registers with the RP as follows: 1. The IPv6 multicast source S sends the first multicast packet to the IPv6 multicast group G. When receiving the multicast packet, the source-side DR that directly connects to the IPv6 multicast source encapsulates the packet into a register message and unicasts the message to the RP. 2.
SPT branch. The subsequent IPv6 multicast data is forwarded to the RP along the SPT without being encapsulated into register messages. For more information about the switchover to SPT initiated by the RP, see "IPv6 multicast source registration." • The receiver-side DR initiates a switchover to SPT: The receiver-side DR periodically checks the forwarding rate of the multicast packets that the IPv6 multicast source S sends to the IPv6 multicast group G.
DF election On a subnet with multiple multicast routers, duplicate multicast packets might be forwarded to the RP. To address this issue, IPv6 BIDIR-PIM uses a designated forwarder (DF) election mechanism to elect a unique DF for each RP on each subnet in the IPv6 BIDIR-PIM domain. Only the DF can forward IPv6 multicast data to the RP. DF election is not necessary for an RPL.
Figure 91 RPT building at the receiver side As shown in Figure 91, the process for building a receiver-side RPT is the same as the process for building an RPT in IPv6 PIM-SM: 1. When a receiver wants to join the IPv6 multicast group G, it uses an MLD message to inform the directly connected router. 2. After receiving the message, the router sends a join message, which is forwarded hop by hop to the RP for the IPv6 multicast group. 3.
Figure 92 RPT building at the IPv6 multicast source side As shown in Figure 92, the process for building a source-side RPT is relatively simple: 4. When an IPv6 multicast source sends multicast packets to the IPv6 multicast group G, the DF in each subnet unconditionally forwards the packets to the RP. 5. The routers along the path from the source's directly connected router to the RP constitute an RPT branch.
An IPv6 admin-scoped zone is designated to particular IPv6 multicast groups with the same scope field value in their group addresses. Zone border routers (ZBRs) form the boundary of an IPv6 admin-scoped zone. Each IPv6 admin-scoped zone maintains one BSR for IPv6 multicast groups with the same scope field value. IPv6 multicast protocol packets, such as assert messages and BSMs, of these IPv6 multicast groups cannot cross the boundary of the IPv6 admin-scoped zone for the group range.
Figure 94 IPv6 multicast address format An IPv6 admin-scoped zone with a larger scope field value contains an IPv6 admin-scoped zone with a smaller scope field value. The zone with the scope field value of E is the IPv6 global-scoped zone. Table 20 lists the possible values of the scope field. Table 20 Values of the Scope field Value Meaning Remarks 0, F Reserved N/A 1 Interface-local scope N/A 2 Link-local scope N/A 3 Subnet-local scope IPv6 admin-scoped zone.
SPT building When a receiver joins an IPv6 multicast group, the receiver-side DR uses the IPv6 SSM group range to determine whether to build an RPT for IPv6 PIM-SM or an SPT for IPv6 PIM-SSM. The IPv6 SSM group range reserved by IANA is FF3x::/32, where "x" represents any legal address scope. Figure 95 SPT building in IPv6 PIM-SSM Host A Source RP DR Server Receiver Host B DR Receiver SPT Subscribe message IPv6 multicast packets Host C As shown in Figure 95, Host B and Host C are receivers.
Figure 96 Relationship among IPv6 PIM protocols A receiver joins IPv6 multicast group G. G is in the IPv6 SSM group range? Yes An IPv6 multicast source is specified? No No No IPv6 BIDIR-PIM is enabled? No An MLD-SSM mapping is configured for G? Yes IPv6 PIM-SM runs for G. No G has an IPv6 BIDIR-PIM RP? Yes Yes IPv6 PIM-SSM runs for G. Yes IPv6 BIDIR-PIM runs for G.
IPv6 PIM-DM configuration task list Task at a glance (Required.) Enabling IPv6 PIM-SM (Optional.) Enabling the state refresh feature (Optional.) Configuring state refresh parameters (Optional.) Configuring IPv6 PIM-DM graft retry timer (Optional.) Configuring common IPv6 PIM features Configuration prerequisites Before you configure IPv6 PIM-DM, configure an IPv6 unicast routing protocol so that all devices in the domain are interoperable at the network layer.
To enable the state refresh feature on all routers in IPv6 PIM-DM domain: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Enable the state refresh feature. ipv6 pim state-refresh-capable By default, the state refresh feature is enabled. Configuring state refresh parameters The router directly connected with the IPv6 multicast source periodically sends state refresh messages.
To configure the IPv6 PIM-DM graft retry timer: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Configure the graft retry timer. ipv6 pim timer graft-retry interval By default, the graft retry timer is 3 seconds. Configuring IPv6 PIM-SM This section describes how to configure IPv6 PIM-SM. IPv6 PIM-SM configuration task list Task at a glance (Required.) Enabling IPv6 PIM-SM (Required.
IMPORTANT: All the interfaces on the same router must operate in the same IPv6 PIM mode in the public network or the same VPN instance. To enable IPv6 PIM-SM: Step Command Remarks 1. Enter system view. system-view N/A 2. Enable IPv6 multicast routing and enter IPv6 MRIB view. ipv6 multicast routing [ vpn-instance vpn-instance-name ] By default, IPv6 multicast routing is disabled. 3. Return to system view. quit 4. Enter interface view. interface interface-type interface-number N/A 5.
The holdtime option in C-RP advertisement messages defines the C-RP lifetime for the advertising C-RP. The BSR starts a holdtime timer for a C-RP after it receives an advertisement message. If the BSR does not receive any advertisement message when the timer expires, it considers the C-RP failed or unreachable. To guard against C-RP spoofing, configure a filtering policy on the BSR to define the legal C-RP address range and the multicast group range to which the C-RP is designated.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. ipv6 pim [ vpn-instance vpn-instance-name ] N/A anycast-rp ipv6-anycast-rp-address ipv6-member-address By default, Anycast RP is not configured. You can repeat this command to add multiple RP member addresses to an Anycast RP set. 3. Configure Anycast RP. Configuring a BSR You must configure a BSR if C-RPs are configured to dynamically select the RP.
• When an attacker controls a router on the network, the attacker can configure the router as a C-BSR to win the BSR election. Through this router, the attacker controls the advertising of RP information. For security purposes, you can configure a legal BSR address range on all routers on the network. All routers will discard BSMs that are out of the legal address range. These preventive measures can partially protect the BSR in a network.
• If the RP-set information is carried in one BSMF, the router directly updates the RP-set information for the group range. • If the RP-set information is carried in multiple BSMFs, the router updates the RP-set information for the group range after receiving all these BSMFs. The loss of some IP fragments does not result in dropping of the entire BSM. The BSM semantic fragmentation function is enabled by default. A device that does not support this function might regard a fragment as a BSM.
expires, it resets its register-stop timer. Otherwise, the DR starts sending register messages with encapsulated data again. The register-stop timer is set to a random value chosen uniformly from (0.5 × register_suppression_time minus register_probe_time) to (1.5 × register_suppression_time minus register_probe_time). The register_probe_time is (5 seconds).
Configuring IPv6 BIDIR-PIM This section describes how to configure IPv6 BIDIR-PIM. IPv6 BIDIR-PIM configuration task list Task at a glance (Required.) Enabling IPv6 BIDIR-PIM (Required.) Configuring an RP: • Configuring a static RP • Configuring a C-RP • Configuring the maximum number of IPv6 BIDIR-PIM RPs NOTE: You must configure a static RP, a C-RP, or both in an IPv6 BIDIR-PIM domain. In an IPv6 network without C-RPs, skip the task of configuring a BSR. Configuring a BSR • (Required.
Step Command Remarks 4. Enter interface view. interface interface-type interface-number N/A 5. Enable IPv6 PIM-SM. ipv6 pim sm By default, IPv6 PIM-SM is disabled. 6. Return to system view. quit N/A 7. Enter IPv6 PIM view ipv6 pim [ vpn-instance vpn-instance-name ] N/A 8. Enable IPv6 BIDIR-PIM bidir-pim enable By default, IPv6 BIDIR-SM is disabled.
In an IPv6 BIDIR-PIM domain, if you want a router to become the RP, you can configure the router as a C-RP. The BSR collects the C-RP information according to the received advertisement messages from C-RPs or the auto-RP announcements from other routers. Then, it organizes the C-RP information into the RP-set information, which is flooded throughout the entire network. The other routers in the network can determine the RPs for different IPv6 multicast group ranges based on the RP-set information.
Configuring a C-BSR IMPORTANT: Because the BSR and other devices exchange a large amount of information in the IPv6 BIDIR-PIM domain, reserve a large bandwidth between the C-BSR and other devices. C-BSRs should be configured on routers on the backbone network. The BSR election process is summarized as follows: 1. Initially, each C-BSR regards itself as the BSR of the IPv6 BIDIR-PIM domain and sends BSMs to other routers in the domain. 2.
Step Command Remarks 4. (Optional.) Configure a legal BSR address range. bsr-policy acl6-number By default, no restrictions are defined. Configuring an IPv6 PIM domain border As the administrative core of an IPv6 BIDIR-PIM domain, the BSR sends the collected RP-set information in the bootstrap messages to all routers in the IPv6 BIDIR-PIM domain. An IPv6 PIM domain border is a bootstrap message boundary. Each BSR has its specific service scope.
NOTE: Generally, a BSR performs BSM semantic fragmentation according to the MTU of its BSR interface. For BSMs originated due to learning of a new IPv6 PIM neighbor, semantic fragmentation is performed according to the MTU of the interface that sends the BSMs. Configuring IPv6 PIM-SSM IPv6 PIM-SSM requires MLDv2 support. Enable MLDv2 on IPv6 PIM routers that connect to multicast receivers. IPv6 PIM-SSM configuration task list Task at a glance (Required.) Enabling IPv6 PIM-SM (Optional.
Configuring the IPv6 SSM group range When an IPv6 PIM-SM enabled interface receives an IPv6 multicast packet, it checks whether the IPv6 multicast group address of the packet is in the IPv6 SSM group range. If the IPv6 multicast group address is in this range, the IPv6 PIM mode for this packet is IPv6 PIM-SSM. If the IPv6 multicast group address is not in this range, the IPv6 PIM mode is IPv6 PIM-SM. Configuration guidelines • Perform the following configuration on all routers in the IPv6 PIM-SSM domain.
Configuring an IPv6 multicast data filter To control IPv6 multicast traffic and the information available to downstream receivers, you can configure an IPv6 router as an IPv6 multicast data filter. The router will check IPv6 multicast packets that pass by and determine to forward or discard the packets. A filter can filter not only independent IPv6 multicast data but also IPv6 multicast data encapsulated in register messages.
• Holdtime—IPv6 PIM neighbor lifetime. If a router receives no hello message from a neighbor when the neighbor lifetime expires, it regards the neighbor failed or unreachable. • LAN_Prune_Delay—Delay of forwarding prune messages on a shared-media LAN. This option consists of LAN delay (namely, prune message delay), override interval, and neighbor tracking support (namely, the capability to disable join message suppression).
Configuring hello message options on an interface Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Set the DR priority. ipv6 pim hello-option dr-priority priority By default, the DR priority is 1. 4. Set the neighbor lifetime. ipv6 pim hello-option holdtime time By default, the neighbor lifetime is 105 seconds. 5. Set the prune delay.
Configuring common IPv6 PIM timers globally Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. ipv6 pim [ vpn-instance vpn-instance-name ] N/A 3. Set the interval for sending hello messages. timer hello interval By default, the interval to send hello messages is 30 seconds. 4. Set the interval for sending join/prune messages. timer join-prune interval By default, the interval to send join/prune messages is 60 seconds.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. ipv6 pim [ vpn-instance vpn-instance-name ] N/A 3. Set the maximum size of each join or prune message. jp-pkt-size size By default, the maximum size of a join or prune message is 8100 bytes. Enabling BFD for IPv6 PIM IPv6 PIM uses hello messages to elect a DR for a shared-media network. The elected DR is the only multicast forwarder on the shared-media network.
Displaying and maintaining IPv6 PIM Execute display commands in any view. Task Command Display information about the register-tunnel interface. display interface [ register-tunnel [ interface-number ] ] [ brief [ description| down ] ] Display BSR information in the IPv6 PIM-SM domain. display ipv6 pim [ vpn-instance vpn-instance-name ] bsr-info Display information about the routes used by IPv6 PIM.
Figure 97 Network diagram Table 21 Interface and IPv6 address assignment Device Interface IPv6 address Device Interface IPv6 address Router A GigabitEthernet 2/1/1 1001::1/64 Router C GigabitEthernet 2/1/2 3001::1/64 Router A GigabitEthernet 2/1/2 1002::1/64 Router D GigabitEthernet 2/1/1 4001::1/64 Router B GigabitEthernet 2/1/1 2001::1/64 Router D GigabitEthernet 2/1/2 1002::2/64 Router B GigabitEthernet 2/1/2 2002::1/64 Router D GigabitEthernet 2/1/3 2002::2/64 Router C Gi
[RouterA-GigabitEthernet2/1/1] mld enable [RouterA-GigabitEthernet2/1/1] quit # Enable IPv6 PIM-DM on GigabitEthernet 2/1/2. [RouterA] interface gigabitethernet 2/1/2 [RouterA-GigabitEthernet2/1/2] ipv6 pim dm [RouterA-GigabitEthernet2/1/2] quit # Enable IPv6 multicast routing, MLD, and IPv6 PIM-DM on Router B and Router C in the same way Router A is configured. (Details not shown.) # On Router D, enable IPv6 multicast routing and enable IPv6 PIM-DM on each interface.
# Send IPv6 multicast data from the IPv6 multicast source 4001::100/64 to the IPv6 multicast group FF0E::101. (Details not shown.) # Display IPv6 PIM multicast routing table information on Router A.
IPv6 PIM-SM non-scoped zone configuration example Network requirements As shown in Figure 98: • VOD streams are sent to receiver hosts in multicast. The receivers of different subnets form stub networks, and at least one receiver host exist in each stub network. The entire IPv6 PIM-SM domain contains only one BSR. • Host A and Host C are multicast receivers in the stub networks N1 and N2. • Specify GigabitEthernet 2/1/3 on Router E as a C-BSR and a C-RP.
Device Interface IPv6 address Device Interface IPv6 address Router C GigabitEthernet 2/1/2 3001::1/64 Router E GigabitEthernet 2/1/4 4002::2/64 Configuration procedure 1. Assign an IPv6 address and prefix length to each interface according to Figure 98. (Details not shown.) 2. Enable OSPFv3 on all routers on the IPv6 PIM-SM network to make sure the following conditions are met: (Details not shown.) 3. { The routers are interoperable at the network layer.
[RouterA] ipv6 pim [RouterA-pim6] static-rp 1002::2 [RouterA-pim6] quit # Configure a static RP on Router B, Router C, and Router D in the same way Router A is configured. (Details not shown.) Verifying the configuration # Display IPv6 PIM information on Router A. [RouterA] display ipv6 pim interface Interface NbrCnt HelloInt DR-Pri DR-Address GE2/1/1 0 1 FE80::A01:201:1 30 (local) GE2/1/2 1 30 1 FE80::A01:201:2 GE2/1/2 1 30 1 FE80::A01:201:2 # Display BSR information on Router A.
IPv6 PIM-SM admin-scoped zone configuration example Network requirements As shown in Figure 99: • VOD streams are sent to receiver hosts in multicast. The entire IPv6 PIM-SM domain is divided into IPv6 admin-scoped zone 1, IPv6 admin-scoped zone 2, and the IPv6 global-scoped zone. Router B, Router C, and Router D are ZBRs of the three zones, respectively. • Source 1 and Source 2 send different IPv6 multicast data to the IPv6 multicast group FF14::101.
Device Interface IPv6 address Device Interface IPv6 address Router A GigabitEthernet 2/1/2 1002::1/64 Router E GigabitEthernet 2/1/3 6001::2/64 Router B GigabitEthernet 2/1/1 2001::1/64 Router F GigabitEthernet 2/1/1 8001::1/64 Router B GigabitEthernet 2/1/2 1002::2/64 Router F GigabitEthernet 2/1/2 6002::2/64 Router B GigabitEthernet 2/1/3 2002::1/64 Router F GigabitEthernet 2/1/3 2003::2/64 Router B GigabitEthernet 2/1/4 2003::1/64 Router G GigabitEthernet 2/1/1 9001::1/
# On Router B, enable IPv6 multicast routing, and enable IPv6 PIM-SM on each interface.
[RouterB-pim6] quit # On Router D, configure GigabitEthernet 2/1/1 as a C-BSR and a C-RP for IPv6 admin-scoped zone 2. [RouterD] ipv6 pim [RouterD-pim6] c-bsr 3003::2 scope 4 [RouterD-pim6] c-rp 3003::2 scope 4 [RouterD-pim6] quit # On Router F, configure GigabitEthernet 2/1/1 as a C-BSR and a C-RP for the IPv6 global-scoped zone.
Bootstrap timer: 00:01:25 Elected BSR address: 3003::2 Priority: 64 Hash mask length: 126 Uptime: 00:01:45 Candidate BSR address: 3003::2 Priority: 64 Hash mask length: 126 # Display BSR information on Router F. [RouterF] display ipv6 pim bsr-info Scope: non-scoped State: Elected Bootstrap timer: 00:00:49 Elected BSR address: 8001::1 Priority: 64 Hash mask length: 126 Uptime: 00:01:11 Candidate BSR address: 8001::1 Priority: 64 Hash mask length: 126 # Display RP information on Router B.
1002::2 (local) 192 180 00:02:03 00:02:56 RP address Priority HoldTime Uptime Expires 1002::2 (local) 192 180 00:02:03 00:02:56 RP address Priority HoldTime Uptime Expires 1002::2 (local) 192 180 00:02:03 00:02:56 RP address Priority HoldTime Uptime Expires 1002::2 (local) 192 180 00:02:03 00:02:56 RP address Priority HoldTime Uptime Expires 1002::2 (local) 192 180 00:02:03 00:02:56 RP address Priority HoldTime Uptime Expires 1002::2 (local) 192 180 00:02
Figure 100 Network diagram Loop0 Receiver 1 Receiver 2 Router B GE2/1/1 GE2/1/3 GE2/1/1 Router C Host A GE2/1/2 Host B GE2/1/2 Source 1 GE2/1/2 GE2/1/3 G E2 /1 /1 IPv6 BIDIR-PIM Source 2 GE2/1/2 GE2/1/1 Router D Router A Table 24 Interface and IPv6 address assignment Device Interface IPv6 address Device Interface IPv6 address Router A GigabitEthernet 2/1/1 1001::1/64 Router D GigabitEthernet 2/1/1 4001::1/64 Router A GigabitEthernet 2/1/2 1002::1/64 Router D GigabitEthern
[RouterA-mrib6] quit [RouterA] interface gigabitethernet 2/1/1 [RouterA-GigabitEthernet2/1/1] ipv6 pim sm [RouterA-GigabitEthernet2/1/1] quit [RouterA] interface gigabitethernet 2/1/2 [RouterA-GigabitEthernet2/1/2] ipv6 pim sm [RouterA-GigabitEthernet2/1/2] quit [RouterA] ipv6 pim [RouterA-pim6] bidir-pim enable [RouterA-pim6] quit # On Router B, enable IPv6 multicast routing.
[RouterD] ipv6 multicast routing [RouterD-mrib6] quit # Enable MLD on GigabitEthernet 2/1/1 (the interface that connects to the receiver host). [RouterD] interface gigabitethernet 2/1/1 [RouterD-GigabitEthernet2/1/1] mld enable [RouterD-GigabitEthernet2/1/1] quit # Enable IPv6 PIM-SM on the other interfaces.
Loop0 - - - - - GE2/1/1 Win 0 0 01:06:07 FE80::20F:E2FF: GE2/1/2 Win 0 0 01:06:07 FE15:5601 (local) FE80::20F:E2FF: FE15:5602 (local) # Display the DF information of IPv6 BIDIR-PIM on Router D.
2: GigabitEthernet2/1/2 # Display information about the DF for IPv6 multicast forwarding on Router D. [RouterD] display ipv6 multicast forwarding df-info Total 1 RP, 1 matched 00001. RP address: 6001::1 Flags: 0x0 Uptime: 00:05:12 RPF interface: GigabitEthernet2/1/3 List of 2 DF interfaces: 1: GigabitEthernet2/1/1 2: GigabitEthernet2/1/2 IPv6 PIM-SSM configuration example Network requirements As shown in Figure 101: • The receivers receive VOD information through multicast.
Table 25 Interface and IPv6 address assignment Device Interface IPv6 address Device Interface IPv6 address Router A GigabitEthernet 2/1/1 1001::1/64 Router D GigabitEthernet 2/1/1 4001::1/64 Router A GigabitEthernet 2/1/2 1002::1/64 Router D GigabitEthernet 2/1/2 1002::2/64 Router A GigabitEthernet 2/1/3 1003::1/64 Router D GigabitEthernet 2/1/3 4002::1/64 Router B GigabitEthernet 2/1/1 2001::1/64 Router E GigabitEthernet 2/1/1 3001::2/64 Router B GigabitEthernet 2/1/2 2002::
[RouterA] ipv6 pim [RouterA-pim6] ssm-policy 2000 [RouterA-pim6] quit 5. Configure the IPv6 SSM group range on Router B, Router C, Router D and Router E in the same way Router A is configured. (Details not shown.) Verifying the configuration # Display IPv6 PIM information on Router A.
Troubleshooting IPv6 PIM A multicast distribution tree cannot be correctly built Symptom An IPv6 multicast distribution tree cannot be correctly built because no IPv6 multicast forwarding entries are established on the routers (including routers directly connected with multicast sources or receivers) in an IPv6 PIM network.
6. Use display current-configuration to verify that the same IPv6 PIM mode is enabled on all routers on the network. For IPv6 PIM-SM, verify that the BSR and C-RPs are correctly configured. 7. If the problem persists, contact HP Support. IPv6 multicast data is abnormally terminated on an intermediate router Symptom An intermediate router can receive IPv6 multicast data successfully, but the data cannot reach the last-hop router.
4. If the problem persists, contact HP Support. An RPT cannot be built or IPv6 multicast source registration fails in IPv6 PIM-SM Symptom The C-RPs cannot unicast advertisement messages to the BSR. The BSR does not advertise BSMs containing C-RP information and has no IPv6 unicast route to any C-RP. An RPT cannot be correctly established, or the source-side DR cannot register the IPv6 multicast source with the RP. Analysis • The C-RPs periodically send advertisement messages to the BSR by unicast.
Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
Conventions This section describes the conventions used in this documentation set. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown. Italic Italic text represents arguments that you replace with actual values. [] Square brackets enclose syntax choices (keywords or arguments) that are optional. { x | y | ... } Braces enclose a set of required syntax choices separated by vertical bars, from which you select one.
Network topology icons Represents a generic network device, such as a router, switch, or firewall. Represents a routing-capable device, such as a router or Layer 3 switch. Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features. Represents an access controller, a unified wired-WLAN module, or the switching engine on a unified wired-WLAN switch. Represents an access point. Represents a mesh access point.
Index ACDEFHIMOPRT Configuring PIM-SSM,108 A Configuring SA message related parameters,147 Adjusting IGMP performance,64 Configuring the MLD snooping querier,228 Adjusting MLD performance,262 Contacting HP,336 C Conventions,337 Configuration examples,48 D Configuration task list,248 Displaying and maintaining IGMP,68 Configuring an IGMP snooping querier,23 Displaying and maintaining IGMP snooping,30 Configuring an MSDP peering connection,145 Displaying and maintaining IPv6 multicast routing
MLD configuration examples,266 Overview,40 MLD configuration task list,260 Overview,13 MLD snooping configuration examples,236 Overview,77 MLD snooping configuration task list,222 Overview,138 MSDP configuration examples,151 Overview,171 MSDP configuration task list,144 P Multicast architecture,5 PIM configuration examples,115 Multicast models,5 Multicast packet forwarding mechanism,11 R Multicast routing and forwarding configuration task list,44 Related information,336 T Multicast support
