Page 1 HP MSR Router Series IP Multicast Configuration Guide(V7) Part number: 5998-5679 Software version: CMW710-R0106 Document version: 6PW100-20140607...
Page 2 The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty.
Page 3: Table Of Contents
Contents Multicast overview ······················································································································································· 1 Introduction to multicast ···················································································································································· 1 Information transmission techniques ······················································································································· 1 Multicast features ······················································································································································ 3 Common notations in multicast ······························································································································· 4 Multicast benefits and applications ························································································································ 4 Multicast models ································································································································································ 5 ...
Page 4 Group policy and simulated joining configuration example ············································································ 31 Static port configuration example ······················································································································· 33 IGMP snooping querier configuration example ································································································· 36 Troubleshooting IGMP snooping ·································································································································· 38 Layer 2 multicast forwarding cannot function ···································································································· 38 Multicast group filter does not work ····················································································································...
Page 5 Basic IGMP functions configuration examples ··································································································· 68 IGMP SSM mapping configuration example ····································································································· 71 IGMP proxying configuration example ··············································································································· 74 Troubleshooting IGMP ··················································································································································· 75 No membership information on the receiver-side router ··················································································· 75 Inconsistent membership information on the routers on the same subnet ························································ 76 ...
Page 6 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 ······················································································································· 127 PIM-SSM configuration example ························································································································ 131 Troubleshooting PIM ···················································································································································· 134 A multicast distribution tree cannot be correctly built ······················································································ 134 ...
Page 7 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 ················································································································ 185 Specifying the MD source interface ·················································································································· 186 ...
Page 8 MLD snooping querier configuration example ································································································· 241 Troubleshooting MLD snooping ·································································································································· 244 Layer 2 multicast forwarding cannot function ·································································································· 244 IPv6 multicast group filter does not work ·········································································································· 244 Configuring IPv6 multicast routing and forwarding ····························································································· 245 ...
Page 9 IPv6 PIM-SM overview ········································································································································ 277 IPv6 BIDIR-PIM overview ····································································································································· 284 IPv6 administrative scoping overview ··············································································································· 287 IPv6 PIM-SSM overview ······································································································································ 289 Relationship among IPv6 PIM protocols ············································································································ 290 IPv6 PIM support for VPNs ································································································································· 291 ...
Page 10 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 ············································································································································ 336 Related information ······················································································································································ 336 Documents ···························································································································································· 336 ...
Page 11: Multicast Overview
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.
Page 12 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 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.
Page 13: Multicast Features
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.
Page 14: Common Notations In Multicast
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 A multicast source sends multicast data to a multicast channel.
Page 15: Multicast Models
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.
Page 16: Multicast Addresses
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 Reserved permanent group addresses. The IP address 224.0.0.0 is reserved.
Page 17 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 1 1 1 1 1 1 1 1, this address is an IPv6 multicast address.
Page 18 Table 5 Values of the Scope field Value Meaning 0, F Reserved. Interface-local scope. Link-local scope. Subnet-local scope. Admin-local scope. Site-local scope. 6, 7, 9 through D Unassigned. Organization-local scope. Global scope. Group ID—The Group ID field contains 1 12 bits. It uniquely identifies an IPv6 multicast group in the scope that the Scope field defines.
Page 19: Multicast Protocols
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"...
Page 20 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.
Page 21: Multicast Packet Forwarding Mechanism
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.
Page 22: Multicast Application In Vpns
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 •...
Page 23: Configuring Igmp Snooping
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.
Page 24 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 1 1, GigabitEthernet 1/0/1 of Switch A and GigabitEthernet 1/0/1 of Switch B are the router ports.
Page 25: How Igmp Snooping Works
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.
Page 26: Protocols And Standards
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.
Page 27: Configuring Basic Igmp Snooping Functions
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 •...
Page 28: Specifying The Igmp Snooping Version
Step Command Remarks Enable IGMP snooping globally and enter igmp-snooping By default, IGMP snooping is disabled. IGMP-snooping view. Enable IGMP snooping for By default, IGMP snooping is disabled for a enable vlan vlan-list specified VLANs. VLAN. To enable IGMP snooping for a VLAN in VLAN view: Step Command Remarks...
Page 29: Setting The Maximum Number Of Igmp Snooping Forwarding Entries
You can modify the maximum number of IGMP snooping forwarding entries. When the number of forwarding entries on the device reaches the upper limit, the device does not automatically remove any existing entries. To avoid the situation that new entries cannot be created, HP recommends that you manually remove some entries.
Page 30: Configuring Static Ports
Setting the aging timers for dynamic ports globally Step Command Remarks Enter system view. system-view Enter IGMP-snooping view. igmp-snooping Set the aging timer for dynamic The default setting is 260 router-aging-time interval router ports globally. seconds. Set the global aging timer for The default setting is 260 host-aging-time interval dynamic member ports globally.
Page 31: Configuring A Port As A Simulated Member Host
Step Command Remarks Configure the port as a static igmp-snooping static-router-port By default, a port is not a static router port. vlan vlan-id 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.
Page 32: Disabling A Port From Becoming A Dynamic Router Port
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...
Page 33: Configuring An Igmp Snooping Querier
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. •...
Page 34: Configuring Parameters For Igmp Messages
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...
Page 35: Setting The 802.1P Precedence For Igmp Messages
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.
Page 36: Configuring Igmp Snooping Policies
Setting the 802.1p precedence for IGMP messages in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Set the 802.1p precedence for igmp-snooping dot1p-priority The default setting is 0. IGMP messages in the VLAN. priority-number Configuring IGMP snooping policies Before you configure IGMP snooping policies, complete the following tasks: •...
Page 37: Configuring Multicast Source Port Filtering
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.
Page 38: Enabling Igmp Report Suppression
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 Enter system view. system-view Enter VLAN view. vlan vlan-id By default, the dropping unknown Enable...
Page 39: Enabling The Multicast Group Replacement Function
Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface interface-type view. interface-number Set the maximum number of igmp-snooping group-limit limit The default setting is multicast groups on a port. [ vlan vlan-list ] 4294967295. Enabling the multicast group replacement function When the number of multicast groups on a Layer 2 device or a port exceeds the limit: If the multicast group replacement is enabled, the Layer 2 device or the port replaces an existing •...
Page 40: Displaying And Maintaining Igmp Snooping
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 display igmp-snooping group [ group-address | snooping forwarding entries source-address ] * [ vlan vlan-id ] [ verbose ] (MSR2000/MSR3000).
Page 41: Igmp Snooping Configuration Examples
Task Command Remove the dynamic IGMP snooping forwarding reset igmp-snooping group { group-address entries for the specified multicast groups. [ 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 reset igmp-snooping statistics IGMP snooping.
Page 42 [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 Configure Switch A: # Enable IGMP snooping globally. <SwitchA>...
Page 43: Static Port Configuration Example
(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.
Page 44 Figure 13 Network diagram Switch B Source Switch A GE2/1/2 GE2/1/1 1.1.1.2/24 10.1.1.1/24 GE2/1/1 Router A 1.1.1.1/24 IGMP querier Switch C Host C Host A Receiver Receiver Host B VLAN 100 Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 13.
Page 45 [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 Configure Switch B: # Enable IGMP snooping globally. <SwitchB> 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.
Page 46: Igmp Snooping Querier Configuration Example
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...
Page 47 <SwitchA> 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.
Page 48: Troubleshooting Igmp Snooping
If IGMP snooping is enabled globally but not enabled for the VLAN, use the igmp-snooping enable command in VLAN view to enable IGMP snooping for the VLAN. If the problem persists, contact HP Support. Multicast group filter does not work Symptom Hosts can receive multicast data from multicast groups that are not permitted by the multicast group filter.
Page 49 Use the display igmp-snooping command to verify that the function of dropping unknown multicast data is enabled. If not, use the drop-unknown or igmp-snooping drop-unknown command to enable the function of dropping unknown multicast data. If the problem persists, contact HP Support.
Page 50: Configuring Multicast Routing And Forwarding
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.
Page 51 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.
Page 52: Static Multicast Routes
Figure 15 RPF check process IP Routing Table on Router C Receiver Router B Destination/Mask Interface 192.168.0.0/24 GE1/0/2 GE1/0/1 Source Router A 192.168.0.1/24 Receiver GE1/0/1 GE1/0/2 Multicast packets 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.
Page 53 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.
Page 54: Multicast Forwarding Across Unicast Subnets
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.
Page 55: Enabling Ip Multicast Routing
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 Layer 3—IP Services Configuration Guide and secondary IP addresses, and IP unnumbered, see Enabling IP multicast routing Enable IP multicast routing before you configure any Layer 3 multicast functionality on the public network or VPN instance.
Page 56: Configuring The Rpf Route Selection Rule
Step Command Remarks • Delete a specific static multicast route: undo ip rpf-route-static [ vpn-instance vpn-instance-name ] source-address { mask-length | (Optional.) Delete static mask } { rpf-nbr-address | multicast routes. interface-type interface-number } • Delete all static multicast routes: delete ip rpf-route-static [ vpn-instance vpn-instance-name ] Configuring the RPF route selection rule...
Page 57: Displaying And Maintaining Multicast Routing And Forwarding
TIP: You do not need to enable IP multicast routing before this configuration. To configure a multicast forwarding boundary: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure a multicast multicast boundary group-address By default, no forwarding forwarding boundary.
Page 58: Configuration Examples
Task Command display multicast [ vpn-instance vpn-instance-name ] forwarding-table [ source-address [ mask { mask-length | mask } ] | group-address Display multicast forwarding table [ mask { mask-length | mask } ] | incoming-interface interface-type information (MSR4000). interface-number | outgoing-interface { exclude | include | match } interface-type interface-number | slot slot-number | statistics ] * Display information about the DF list display multicast [ vpn-instance vpn-instance-name ] forwarding-table...
Page 59 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 GE2/1/1 40.1.1.1/24...
Page 60: Creating An Rpf Route
<RouterA> 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. (Details not shown.) Display the RPF route to Source on Router B.
Page 61 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 Assign an IP address and subnet mask for each interface according to Figure...
Page 62: Multicast Forwarding Over A Gre Tunnel
[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.) 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.100 No output is displayed because no RPF routes to Source 2 exist on Router B and Router C.
Page 63 Figure 21 Network diagram Configuration procedure Assign an IP address and mask for each interface according to Figure 21. (Details not shown.) Enable OSPF on routers 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.
Page 64 [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...
Page 65: Troubleshooting Multicast Routing And Forwarding
Check the type of the interface that connects the static multicast route to the RPF neighbor. If the interface is not a point-to-point interface, make sure you specify the address for the RPF neighbor. If the problem persists, contact HP Support.
Page 66: Configuring Igmp
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 1 1 12) • • IGMPv2 (defined by RFC 2236) IGMPv3 (defined by RFC 3376) •...
Page 67 Figure 22 IGMP queries and reports IP network Router A Router B Ethernet Host A Host B Host C (G2) (G1) (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.
Page 68: Igmpv2 Enhancements
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.
Page 69 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: •...
Page 70: Igmp Ssm Mapping
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.
Page 71: Igmp Proxying
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. •...
Page 72: Igmp Support For Vpns
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.
Page 73: Enabling Igmp
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...
Page 74: Configuring A Multicast Group Filter
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 Enter system view.
Page 75: Enabling Igmp Fast-Leave Processing
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.
Page 76: Configuring Igmp Ssm Mappings
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.
Page 77: Configuring Multicast Forwarding On A Downstream Interface
Configuration procedure To enable IGMP proxying: Step Command Remarks Enter system view. system-view Enable IP multicast routing multicast routing [ vpn-instance By default, IP multicast routing is and enter MRIB view. vpn-instance-name ] disabled. Return to system view. quit Enter interface view. interface interface-type interface-number Enable the IGMP proxying By default, IGMP proxying is...
Page 78: Displaying And Maintaining Igmp
Step Command Remarks igmp [ vpn-instance Enter IGMP view. vpn-instance-name ] Enable the load splitting By default, the load splitting proxy multipath function on the IGMP proxy. 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.
Page 79 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.
Page 80 [RouterA-GigabitEthernet2/1/2] quit # On Router B, enable IP multicast routing. <RouterB> 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. [RouterB] interface gigabitethernet 2/1/2 [RouterB-GigabitEthernet2/1/2] pim dm [RouterB-GigabitEthernet2/1/2] quit # On Router C, enable IP multicast routing.
Page 81: Igmp Ssm Mapping Configuration Example
IGMP SSM mapping configuration example Network requirements As shown in Figure 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.
Page 82 Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 27. (Details not shown.) Configure OSPF on the routers in the 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.
Page 83 [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.) Configure IGMP SSM mappings on Router D.
Page 84: Igmp Proxying Configuration Example
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.
Page 85: Troubleshooting Igmp
[RouterA-GigabitEthernet2/1/1] quit # Enable IP multicast routing on Router B. <RouterB> 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. [RouterB] interface gigabitethernet 2/1/2 [RouterB-GigabitEthernet2/1/2] igmp enable [RouterB-GigabitEthernet2/1/2] quit...
Page 86: Inconsistent Membership Information On The Routers On The Same Subnet
Use the display current-configuration interface command to verify that no ACL rule has been configured to filter out the reports sent by the host to the multicast group G. If the problem persists, contact HP Support. Inconsistent membership information on the routers on the same...
Page 87: Configuring Pim
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.
Page 88 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: 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.
Page 89: Pim-Sm Overview
The node that needs to receive the multicast data sends a graft message to its upstream node, telling it to rejoin the SPT. 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. If the graft sender receives a graft-ack message, the graft process finishes.
Page 90 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).
Page 91 Figure 31 DR election As shown in Figure 31, the DR election process is as follows: 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. 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.
Page 92 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: The C-RP that is designated to the smallest group range wins. If the C-RPs are designated to the same group ranges, the C-RP with the highest priority wins.
Page 93 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: RP 1 receives a register message destined to the Anycast RP address (RPA).
Page 94 RPT building Figure 34 RPT building in a PIM-SM domain Host A Source Receiver Host B Server Receiver Join message Multicast packets Host C As shown in Figure 34, the process of building an RPT is as follows: When a receiver wants to join the multicast group G, it uses an IGMP message to inform the receiver-side DR.
Page 95 Figure 35 Multicast source registration As shown in Figure 35, the multicast source registers with the RP as follows: 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.
Page 96: Bidir-Pim Overview
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: •...
Page 97 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.
Page 98 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: When a receiver wants to join the multicast group G, it uses an IGMP message to inform the directly connected router.
Page 99: Administrative Scoping Overview
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: When a multicast source sends multicast packets to the multicast group G, the DF in each subnet unconditionally forwards the packets to the RP.
Page 100 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.
Page 101: Pim-Ssm Overview
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 − − 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.
Page 102: Relationship Among Pim Protocols
Figure 41 SPT building in PIM-SSM Host A Source Receiver Host B Server Receiver 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.
Page 103: Pim Support For Vpns
Figure 42 Relationship among PIM protocols A receiver joins multicast group G. G is in the A multicast source is SSM group range? specified? BIDIR-PIM is enabled? An IGMP-SSM mapping is configured for G? PIM-SM runs for G. G has a BIDIR-PIM RP? PIM-SSM runs for G.
Page 104: Pim-Dm Configuration Task List
Enable IP multicast routing before you configure PIM. With PIM-DM enabled on interfaces, routers can establish PIM neighbor relationship and process PIM messages from their PIM neighbors. When you deploy a PIM-DM domain, HP recommends that you enable PIM-DM on all non-border interfaces of the routers.
Page 105: Configuring State Refresh Parameters
Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, the state refresh Enable the state refresh feature. pim state-refresh-capable 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.
Page 106: Configuring Pim-Sm
Enable IP multicast routing before you configure PIM. With PIM-SM enabled on interfaces, routers can establish PIM neighbor relationship and process PIM messages from their PIM neighbors. When you deploy a PIM-SM domain, HP recommends that you enable PIM-SM on all non-border interfaces.
Page 107: Configuring An Rp
When you configure a C-RP, reserve a relatively large bandwidth between the C-RP and other devices in the PIM-SM domain. In a PIM-SM domain, if you want a router to become the RP, you can configure the router as a C-RP. HP recommends that you configure C-RPs on backbone routers.
Page 108 You must add all RP member addresses (including the local RP member address) to the Anycast RP • set on each RP member device. HP recommends that you configure no more than 16 Anycast RP members for an Anycast RP set. • •...
Page 109: Configuring A Bsr
Step Command Remarks By default, Anycast RP is not configured. You can repeat this anycast-rp anycast-rp-address Configure Anycast RP. command to add multiple RP member-rp-address 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.
Page 110 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.
Page 111: Configuring Multicast Source Registration
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.
Page 112: Configuring Switchover To Spt
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.
Page 113: Configuring Bidir-Pim
Enabling BIDIR-PIM Because BIDIR-PIM is implemented on the basis of PIM-SM, you must enable PIM-SM before you enable BIDIR-PIM. When you deploy a BIDIR-PIM domain, HP recommends that you enable PIM-SM on all non-border interfaces of the domain. IMPORTANT: All interfaces on a device must be enabled with the same PIM mode.
Page 114: Configuring An Rp
Step Command Remarks Enable PIM-SM. pim sm By default, PIM-SM is disabled. Return to system view. quit pim [ vpn-instance Enter PIM view. vpn-instance-name ] 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.
Page 115: Configuring A Bsr
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.
Page 116 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: Initially, each C-BSR regards itself as the BSR of the BIDIR-PIM domain and sends BSMs to other routers in the domain.
Page 117 Step Command Remarks (Optional.) Configure a legal BSR By default, no restrictions are bsr-policy acl-number address range. 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.
Page 118: Configuring Pim-Ssm
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.
Page 119: Configuring The Ssm Group Range
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.
Page 120: Configuring A Multicast Data Filter
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.
Page 121 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).
Page 122: Configuring Common Pim Timers
The configurations made in interface view are effective on only the current interface. If you configure common PIM timers in both PIM view and interface view, the configuration in interface view always takes precedence. TIP: For a network without special requirements, HP recommends using the defaults.
Page 123: Setting The Maximum Size Of Each Join Or Prune Message
Configuring common PIM timers globally Step Command Remarks Enter system view. system-view pim [ vpn-instance Enter PIM view. vpn-instance-name ] Set the interval for sending timer hello interval The default setting is 30 seconds. hello messages. The default setting is 60 seconds. Set the interval for sending NOTE: timer join-prune interval...
Page 124: Enabling Bfd For Pim
Step Command Remarks Set the maximum size of each jp-pkt-size size The default setting is 8100 bytes. join or prune message. 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.
Page 125: Pim Configuration Examples
Task Command Display information about the display interface [ register-tunnel [ interface-number ] ] [ brief register-tunnel interface. [ description | down ] ] Display BSR information in the display pim [ vpn-instance vpn-instance-name ] bsr-info PIM-SM domain. Display information about the display pim [ vpn-instance vpn-instance-name ] claimed-route routes used by PIM.
Page 126 Figure 43 Network diagram Receiver Host A Router A GE2/1/1 Host B Receiver GE2/1/1 GE2/1/3 GE2/1/2 GE2/1/1 Source Host C Router D Router B 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...
Page 127 [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.
Page 128 # 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...
Page 129: Pim-Sm Non-Scoped Zone Configuration Example
PIM-SM non-scoped zone configuration example Network requirements As shown in Figure 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. •...
Page 130 Device Interface IP address Device Interface IP address GigabitEthernet GigabitEthernet Router B 192.168.2.1/24 Router E 192.168.2.2/24 2/1/2 2/1/2 GigabitEthernet GigabitEthernet Router C 10.110.2.2/24 Router E 192.168.9.2/24 2/1/1 2/1/3 Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 44.
Page 131 [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.
Page 132: Pim-Sm Admin-Scoped Zone Configuration Example
PIM-SM admin-scoped zone configuration example Network requirements As shown in Figure 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.
Page 133 Device Interface IP address Device Interface IP address GigabitEthernet GigabitEthernet Router A 10.110.1.1/24 Router D 10.110.7.1/24 2/1/2 2/1/2 GigabitEthernet GigabitEthernet Router B 192.168.2.1/24 Router D 10.110.8.1/24 2/1/1 2/1/3 GigabitEthernet GigabitEthernet Router B 10.110.1.2/24 Router E 192.168.4.1/24 2/1/2 2/1/1 GigabitEthernet GigabitEthernet Router B 10.110.2.1/24 Router E...
Page 134 [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.
Page 135 [RouterD-GigabitEthernet2/1/3] multicast boundary 239.0.0.0 8 [RouterD-GigabitEthernet2/1/3] quit 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.2 group-policy 2001...
Page 136 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...
Page 137: Bidir-Pim Configuration Example
[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 00:03:42 00:01:48 Scope: 239.0.0.0/8 Group/MaskLen: 239.0.0.0/8 RP address Priority HoldTime Uptime Expires 10.110.5.2 (local) 00:06:54 00:02:41 # Display RP information on Router F. [RouterF] display pim rp-info BSR RP information: Scope: non-scoped...
Page 138 Table 10 Interface and IP address assignment Device Interface IP address Device Interface IP address GigabitEthernet GigabitEthernet Router A 192.168.1.1/24 Router D 192.168.3.1/24 2/1/1 2/1/1 GigabitEthernet GigabitEthernet Router A 10.110.1.1/24 Router D 192.168.4.1/24 2/1/2 2/1/2 GigabitEthernet GigabitEthernet Router B 192.168.2.1/24 Router D 10.110.3.2/24 2/1/1...
Page 139 # 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.
Page 140 [RouterD] pim [RouterD-pim] bidir-pim enable [RouterD-pim] quit 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 Display the DF information of BIDIR-PIM: # Display the DF information of BIDIR-PIM on Router A.
Page 141: Pim-Ssm Configuration Example
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...
Page 142 Figure 47 Network diagram Receiver Host A Router A GE2/1/1 GE2/1/3 Host B GE2/1/3 Receiver GE2/1/1 GE2/1/4 GE2/1/2 GE2/1/1 GE2/1/3 GE2/1/2 Source GE2/1/1 Router D Router E Router B Host C 10.110.5.100/24 GE2/1/2 GE2/1/1 PIM-SSM Host D Router C Table 11 Interface and IP address assignment Device Interface IP address...
Page 143 The routers can dynamically update their routing information. Enable IP multicast routing, IGMP and PIM-SM: # On Router A, enable IP multicast routing. <RouterA> system-view [RouterA] multicast routing [RouterA-mrib] quit # Enable IGMPv3 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] igmp version 3...
Page 144: Troubleshooting Pim
(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;...
Page 145: Multicast Data Is Abnormally Terminated On An Intermediate Router
Use display current-configuration to verify that the same PIM mode is enabled on all routers. For PIM-SM, verify that the BSR and C-RPs are correctly configured. If the problem persists, contact HP Support. Multicast data is abnormally terminated on an intermediate...
Page 146: An Rp Cannot Join An Spt In Pim-Sm
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. 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.
Page 147 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. Use display pim neighbor to verify that PIM neighboring relationship has been correctly established among the routers. If the problem persists, contact HP Support.
Page 148: Configuring Msdp
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.
Page 149 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.
Page 150 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: 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.
Page 151 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.
Page 152 Figure 50 Anycast RP through MSDP The following describes how Anycast RP through MSDP is implemented: After receiving the multicast data from Source, the source-side DR registers with the nearest RP (RP 1 in this example). 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).
Page 153: Msdp Support For Vpns
Figure 51 MSDP peer-RPF forwarding The process of peer-RPF forwarding is as follows: RP 1 creates an SA message and forwards it to its peer RP 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.
Page 154: Msdp Configuration Task List
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 •...
Page 155: Creating An Msdp Peering Connection
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.
Page 156: Configuring An Msdp Mesh Group
To describe an MSDP peer: Step Command Remarks Enter system view. system-view msdp [ vpn-instance Enter MSDP view. vpn-instance-name ] Configure the description for By default, no description is peer peer-address description text an MSDP peer. configured for an MSDP peer. Configuring an MSDP mesh group An AS might contain multiple MSDP peers.
Page 157: Configuring Sa Message Related Parameters
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.
Page 158: Configuring Sa Message Contents
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.
Page 159: Configuring Sa Message Filtering Rules
Step Command Remarks Enter MSDP view. msdp [ vpn-instance vpn-instance-name ] By default, after receiving a new join message, a device does not Enable the device to send send an SA request message to peer peer-address request-sa-enable SA request messages. any MSDP peer.
Page 160: Configuring The Sa Message Cache
Step Command Remarks Configure lower threshold for multicast data peer peer-address minimum-ttl The default setting is 0. packets encapsulated in SA ttl-value messages. 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.
Page 161: Msdp Configuration Examples
Task Command Display brief information about display msdp [ vpn-instance vpn-instance-name ] brief [ state { connect | MSDP peers. disabled | established | listen | shutdown } ] Display detailed information about display msdp [ vpn-instance vpn-instance-name ] peer-status the MSDP peer status.
Page 162 Figure 52 Network diagram Table 12 Interface and IP address assignment Device Interface IP address Device Interface IP address GigabitEthernet GigabitEthernet Router A 10.110.1.2/24 Router D 10.110.4.2/24 2/1/1 2/1/1 GigabitEthernet GigabitEthernet Router A 10.110.2.1/24 Router D 10.110.5.1/24 2/1/2 2/1/2 GigabitEthernet GigabitEthernet Router A 10.110.3.1/24...
Page 163 Configure OSPF on the routers. (Details not shown.) Enable IP multicast routing, enable PIM-SM and IGMP, and configure a PIM-SM domain border: # On Router A, enable IP multicast routing. <RouterA> system-view [RouterA] multicast routing [RouterA-mrib] quit # Enable PIM-SM on GigabitEthernet 2/1/1 and GigabitEthernet 2/1/2. [RouterA] interface gigabitethernet 2/1/1 [RouterA-GigabitEthernet2/1/1] pim sm [RouterA-GigabitEthernet2/1/1] quit...
Page 164 [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...
Page 165 Peer MsgRcvd MsgSent OutQ PrefRcv Up/Down State 192.168.1.1 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...
Page 166: Inter-As Multicast Configuration By Leveraging Static Rpf Peers
# 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.1) Received/sent messages: 16/16 Discarded input messages: 0 Discarded output messages: 0 Elapsed time since last connection or counters clear: 00:17:40 Mesh group peer joined: momo...
Page 167 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.
Page 168 Device Interface IP address Device Interface IP address GigabitEthernet GigabitEthernet Router C 10.110.2.2/24 Router G 192.168.4.1/24 2/1/1 2/1/2 GigabitEthernet Router C 192.168.2.1/24 Router G Loopback 0 3.3.3.3/32 2/1/2 GigabitEthernet Router C 10.110.4.1/24 2/1/3 Configuration procedure Assign an IP address and subnet mask to each interface according to Table 13.
Page 169 # Configure C-BSRs and C-RPs on Router D and Router G in the same way. (Details not shown.) 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...
Page 170 # 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 Configure MSDP peers and static RPF peers: # On Router A, configure Router D and Router G as the MSDP peers and static RPF peers.
Page 171: Anycast Rp Configuration
Peer address State Up/Down time SA count Reset count 10.110.1.1 Established 01:07:09 # Display brief information about MSDP peers on Router G. [RouterG] display msdp brief Configured Established Listen Connect Shutdown Disabled Peer address State Up/Down time SA count Reset count 10.110.2.1 Established 00:16:40 # Verify that receivers in PIM-SM 1 and PIM-SM 3 can receive the multicast data from Source 1 and...
Page 172 Table 14 Interface and IP address assignment Device Interface IP address Device Interface IP address GigabitEthernet Source 1 — 10.110.5.100/24 Router C 192.168.1.2/24 2/1/1 GigabitEthernet Source 2 — 10.110.6.100/24 Router C 192.168.2.2/24 2/1/2 GigabitEthernet GigabitEthernet Router A 10.110.5.1/24 Router D 10.110.3.1/24 2/1/1 2/1/1...
Page 173 [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.
Page 174 # 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.1 10.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.
Page 175: Sa Message Filtering Configuration
(*, 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...
Page 176 Figure 55 Network diagram PIM-SM 1 PIM-SM 2 PIM-SM 3 Loop0 Source 2 GE2/1/1 Loop0 Receiver Router A GE2/1/2 Host A GE2/1/1 Router C GE2/1/3 GE2/1/2 Router D GE2/1/1 GE2/1/2 Source 1 GE2/1/2 GE2/1/1 Router B Receiver Receiver Host B Host C MSDP peers Table 15 Interface and IP address assignment...
Page 177 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. <RouterA> system-view [RouterA] multicast routing [RouterA-mrib] quit # Enable IGMP on GigabitEthernet 2/1/1 (the interface that connects to the receiver host). [RouterA] interface gigabitethernet 2/1/1 [RouterA-GigabitEthernet2/1/1] igmp enable [RouterA-GigabitEthernet2/1/1] quit...
Page 178 [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 Configure SA message filtering rules: # Configure an SA message filter on Router C so that Router C will not forward SA messages for...
Page 179: Troubleshooting Msdp
Use the display current-configuration command to verify that the local interface address and the MSDP peer address of the remote router are the same. If the problem persists, contact HP Support. No SA entries exist in the router's SA message cache Symptom MSDP fails to send (S, G) entries through SA messages.
Page 180: No Exchange Of Locally Registered (S, G) Entries Between Rps
Verify the configuration of the import-source command and its acl-number argument, and make sure the ACL rule filters appropriate (S, G) entries. If the problem persists, contact HP Support. No exchange of locally registered (S, G) entries between RPs Symptom RPs fail to exchange their locally registered (S, G) entries with one another in the Anycast RP application.
Page 181: Configuring Multicast Vpn
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 •...
Page 182: Md-Vpn Overview
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 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.
Page 183 Table 16 Basic MD-VPN concepts Concept Description An MD is a set of VPN instances running on PE devices that can send Multicast domain (MD) multicast traffic to each other. Each MD uniquely corresponds to the same set of VPN instances. An MDT is a multicast distribution tree constructed by all PE devices in Multicast distribution tree (MDT) the same VPN.
Page 184 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. •...
Page 185 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. 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.
Page 186: Protocols And Standards
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.
Page 187 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...
Page 188: Default-Mdt-Based Delivery
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 •...
Page 189 Figure 62 Transmission of multicast protocol packets BGP: 11.1.3.1/24 PE 3 Source Receiver CE 1 CE 2 PE 1 PE 2 Site 1 Site 2 BGP: 11.1.1.1/24 BGP: 11.1.2.1/24 S: 192.1.1.1/24 Public instance BGP peers 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:...
Page 190 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 •...
Page 191: Mdt Switchover
Source sends a VPN multicast data packet (192.1.1.1, 225.1.1.1) to CE 1. 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.
Page 192: Inter-As Md Vpn
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. After sending the MDT switchover message, PE 1 waits a certain period of time (known as the data-delay period).
Page 193: Multicast Vpn Configuration Task List
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.
Page 194: Configuring Md-Vpn
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: •...
Page 195: Creating The Md For A Vpn Instance
Step Command Remarks Enter system view. system-view By default, no VPN instance exists on the device. Create a VPN instance and ip vpn-instance vpn-instance-name For more information about this enter VPN instance view. command, see MPLS Command Reference. By default, no RD is configured for a VPN instance.
Page 196: Specifying The Md Source Interface
Step Command Remarks Specify default-group By default, no default-group default-group group-address address. 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.
Page 197: Enabling Data-Group Reuse Logging
Step Command Remarks Optional. Configure the data-holddown data-holddown delay period. 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.
Page 198: Configuring A Bgp Mdt Route Reflector
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.
Page 199: Displaying And Maintaining Multicast Vpn
Step Command Remarks Configure the device as a route peer { group-name | ip-address } By default, neither route reflectors reflector and specify its peers reflect-client nor clients exist. or peer groups as clients. Optional. Disable route reflection undo reflect between-clients By default, clients can reflect routes between clients.
Page 200: Intra-As Md Vpn Configuration Example
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. • In VPN instance b, S 2 is a multicast source, and R 4 is a receiver. Multicast sources and receivers •...
Page 201 Figure 66 Network diagram VPN a Loop1 VPN b CE a2 VPN a GE2/1/1 Loop1 CE b1 GE2/1/1 Loop1 Loop1 CE a3 PE 2 GE2/1/1 GE2/1/3 PE 3 GE2/1/1 Loop2 PE 1 CE a1 CE b2 Public GE2/1/1 Loop1 VPN b VPN a Table 17 Interface and IP address assignment Device...
Page 202 Device Interface IP address Device Interface IP address GigabitEthernet GigabitEthernet PE 1 10.110.2.1/24 CE a3 10.110.5.2/24 2/1/3 2/1/2 GigabitEthernet PE 1 Loopback 1 1.1.1.1/32 CE a3 10.110.12.2/24 2/1/3 GigabitEthernet GigabitEthernet PE 2 192.168.7.1/24 CE b1 10.110.8.1/24 2/1/1 2/1/1 GigabitEthernet GigabitEthernet PE 2 10.110.3.1/24 CE b1...
Page 203 [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.1 24 [PE1-GigabitEthernet2/1/2] igmp enable [PE1-GigabitEthernet2/1/2] quit...
Page 204 [PE1] rip 2 vpn-instance a [PE1-rip-2] network 10.0.0.0 [PE1-rip-2] import-route bgp [PE1-rip-2] return Configure PE 2: # Configure a Router ID globally, and enable IP multicast routing on the public network. <PE2> 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.
Page 205 # 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.1 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 # Bind GigabitEthernet 2/1/2 with VPN instance b, assign an IP address to GigabitEthernet 2/1/2, and enable PIM-SM on the interface.
Page 206 [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...
Page 207 [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.
Page 208 # 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.2 group vpn-g [PE3–bgp] ip vpn-instance a...
Page 209 [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.2 24 [P-GigabitEthernet2/1/1] pim sm...
Page 210 <CEa1> 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.2 24 [CEa1-GigabitEthernet2/1/2] pim sm...
Page 211 [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.22 32 [CEa2-LoopBack1] pim sm...
Page 212: Inter-As Md Vpn Configuration Example
# Enable IP multicast routing. <CEb2> 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.
Page 213 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 2: GigabitEthernet 2/1/1, GigabitEthernet 2/1/2, Loopback 1, and Loopback 2 PE interfaces and belong to the public network instance.
Page 214 Figure 67 Network diagram Table 18 Interface and IP address assignment Device Interface IP address Device Interface IP address — 10.11.5.2/24 — 10.11.8.2/24 — 10.11.6.2/24 — 10.11.7.2/24 GigabitEthernet GigabitEthernet PE 1 10.10.1.1/24 PE 3 10.10.2.1/24 2/1/1 2/1/1 GigabitEthernet GigabitEthernet PE 1 10.11.1.1/24 PE 3 192.168.1.2/24...
Page 215 Device Interface IP address Device Interface IP address GigabitEthernet CE a1 Loopback 0 2.2.2.2/32 CE b2 10.11.8.1/24 2/1/1 GigabitEthernet GigabitEthernet CE a2 10.11.7.1/24 CE b2 10.11.4.2/24 2/1/1 2/1/2 GigabitEthernet CE a2 Loopback 0 10.11.3.2/24 CE b2 3.3.3.3/32 2/1/2 Configuration procedure Configure PE 1: # Configure a Router ID, and enable IP multicast routing on the public network.
Page 216 # 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.
Page 217 [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...
Page 218 # 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.
Page 219 [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...
Page 220 # 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.3 32 [PE3-LoopBack1] pim sm...
Page 221 [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. [PE3] route-policy map1 permit node 10 [PE3-route-policy-map1-10] apply mpls-label [PE3-route-policy-map1-10] quit...
Page 222 # 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] multicast routing vpn-instance b [PE4-mrib-b] quit # Create the MD for VPN instance b, and specify the default-group, MD source interface, and the...
Page 223 [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.1 group pe4-pe1 [PE4–bgp] ip vpn-instance a [PE4-bgp-a] address-family ipv4 [PE4-bgp-ipv4-a] import-route ospf 2 [PE4-bgp-ipv4-a] import-route direct [PE4-bgp-ipv4-a] quit [PE4-bgp-a] quit...
Page 224 [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.2 24 [CEa1-GigabitEthernet2/1/2] pim sm...
Page 225 [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 Configure CE a2: # Enable IP multicast routing. <CEa2> 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.1 24 [CEa2-GigabitEthernet2/1/1] igmp enable...
Page 226: Troubleshooting Md-Vpn
[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...
Page 227: An Mvrf Cannot Be Created
PE device to the same VPN instance on each remote PE device. Use the display bgp peer command to verify that the BGP peer connections have been correctly configured. If the problem persists, contact HP Support. An MVRF cannot be created Symptom A VPN instance cannot create an MVRF correctly.
Page 228: Configuring Mld Snooping
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.
Page 229 Figure 69 MLD snooping related ports The following describes the ports involved in MLD snooping, as shown in Figure • 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.
Page 230: How Mld Snooping Works
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.
Page 231: Protocols And Standards
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. When the Layer 2 device receives the MLD done message on a dynamic member port, the Layer 2 device first examines whether a forwarding entry matches the IPv6 multicast group address in the message: If no match is found, the Layer 2 device directly discards the MLD done message.
Page 232: Mld Snooping Configuration Task List
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: •...
Page 233: Specifying The Mld Snooping Version
Step Command Remarks Enter system view. system-view Enable MLD snooping globally By default, MLD snooping is mld-snooping and enter MLD-snooping view. disabled. Enable MLD snooping for the By default, MLD snooping is enable vlan vlan-list specified VLANs. disabled for a VLAN. To enable MLD snooping for a VLAN in VLAN view: Step Command...
Page 234: Setting The Maximum Number Of Mld Snooping Forwarding Entries
You can modify the maximum number of MLD snooping forwarding entries. When the number of forwarding entries on the device reaches the upper limit, the device does not automatically remove any existing entries. To avoid the situation that new entries cannot be created, HP recommends that you manually remove some entries.
Page 235: Configuring Static Ports
Setting the aging timers for dynamic ports globally Step Command Remarks Enter system view. system-view Enter MLD-snooping view. mld-snooping Set the aging timer for dynamic router-aging-time interval The default setting is 260 seconds. router ports globally. Set the aging timer for dynamic host-aging-time interval The default setting is 260 seconds.
Page 236: Configuring A Port As A Simulated Member Host
Step Command Remarks Configure the port as a static mld-snooping static-router-port By default, a port is not a static router port. vlan vlan-id 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.
Page 237: Disabling A Port From Becoming A Dynamic Router Port
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...
Page 238: Configuring The Mld Snooping Querier
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. •...
Page 239: Configuring Parameters For Mld Messages
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. •...
Page 240: Configuring Source Ipv6 Addresses For Mld Messages
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.
Page 241: Configuring Mld Snooping Policies
Setting the 802.1p precedence for MLD messages globally Step Command Remarks Enter system view. system-view Enter MLD-snooping view. mld-snooping Set the 802.1p precedence for dot1p-priority priority-number The default setting is 0. MLD messages. Setting the 802.1p precedence for MLD messages in a VLAN Step Command Remarks...
Page 242: Configuring Ipv6 Multicast Source Port Filtering
Configuring an IPv6 multicast group filter on a port Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface interface-type view. interface-number By default, no IPv6 multicast group Configure an IPv6 multicast mld-snooping group-policy filter is configured for the port. The group filter for the port.
Page 243: Enabling Dropping Unknown Ipv6 Multicast Data
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.
Page 244: Setting The Maximum Number Of Ipv6 Multicast Groups On A Port
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: •...
Page 245: Displaying And Maintaining Mld Snooping
Step Command Remarks Enable the IPv6 multicast group By default, the IPv6 multicast group overflow-replace [ vlan vlan-list ] replacement function globally. replacement function is disabled. To enable the IPv6 multicast group replacement on a port: Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface interface-type...
Page 246: Mld Snooping Configuration Examples
Task Command Display information about dynamic router display mld-snooping router-port [ vlan vlan-id ] ports (MSR2000/MSR3000). Display information about dynamic router display mld-snooping router-port [ vlan vlan-id ] [ slot ports (MSR4000). slot-number ] Display information about static MLD display mld-snooping static-group [ ipv6-group-address | snooping forwarding entries ipv6-source-address ] * [ vlan vlan-id ] [ verbose ] (MSR2000/MSR3000).
Page 247 Figure 70 Network diagram Configuration procedure Assign an IPv6 address and prefix length to each interface according to Figure 70. (Details not shown.) Configure Router A: # Enable IPv6 multicast routing. <RouterA> 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...
Page 248: Static Port Configuration Example
# 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.
Page 249 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.
Page 250 [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. [SwitchA] interface gigabitethernet 2/1/3 [SwitchA-GigabitEthernet2/1/3] mld-snooping static-router-port vlan 100 [SwitchA-GigabitEthernet2/1/3] quit...
Page 251: Mld Snooping Querier Configuration Example
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).
Page 252 Figure 72 Network diagram Configuration procedure Configure Switch A: # Enable MLD snooping globally. <SwitchA> 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. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 2/1/1 to gigabitethernet 2/1/3 [SwitchA-vlan100] mld-snooping enable...
Page 253 # Enable MLD snooping globally. <SwitchC> 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...
Page 254: Troubleshooting Mld Snooping
If MLD snooping is enabled globally but not enabled for the VLAN, use the mld-snooping enable command in VLAN view to enable MLD snooping for the VLAN. If the problem persists, contact HP Support. IPv6 multicast group filter does not work...
Page 255: Configuring Ipv6 Multicast Routing And Forwarding
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.
Page 256 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.
Page 257: Ipv6 Multicast Forwarding Across Ipv6 Unicast Subnets
Figure 73 RPF check process IPv6 Routing Table on Router C Receiver Router B Destination/Prefix Interface 2000::/16 GE1/0/2 GE1/0/1 Source Router A 2000::101/16 Receiver GE1/0/1 GE1/0/2 IPv6 Multicast packets Router C As shown in Figure 73, assume that IPv6 unicast routes are available in the network, IPv6 MBGP is not configured.
Page 258: Configuration Task List
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.
Page 259: Configuring Ipv6 Multicast Load Splitting
Step Command Remarks Configure the device to select By default, the route with the the RPF route based on the longest-match highest priority is selected as the longest prefix match. 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.
Page 260: Displaying And Maintaining Ipv6 Multicast Routing And Forwarding
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 display ipv6 mrib [ vpn-instance vpn-instance-name ] maintained by the IPv6 MRIB.
Page 261: Ipv6 Multicast Routing And Forwarding Configuration Examples
Task Command display ipv6 multicast [ vpn-instance vpn-instance-name ] routing-table [ ipv6-source-address [ prefix-length ] | Display information about the IPv6 multicast ipv6-group-address [ prefix-length ] | incoming-interface routing table. interface-type interface-number | outgoing-interface { exclude | include | match } interface-type interface-number ] Display the RPF route information of the display ipv6 multicast [ vpn-instance vpn-instance-name ] specified IPv6 multicast source.
Page 262 Figure 75 Network diagram Configuration procedure Assign an IP address and prefix length to each interface according to Figure 75. (Details not shown.) Configure OSPFv3 on the routers 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.
Page 263 [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).
Page 264 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. •...
Page 265: Configuring Mld
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. •...
Page 266 Joining an IPv6 multicast group Figure 76 MLD queries and reports IPv6 network Querier Router A Router B Ethernet Host A Host B Host C (G2) (G1) (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.
Page 267: Mldv2 Enhancements
The host sends an MLD done message to all IPv6 multicast routers on the local subnet. The destination address is FF02::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.
Page 268: Mld Ssm Mapping
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)).
Page 269: Mld Proxying
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 •...
Page 270: Mld Support For Vpns
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.
Page 271: Enabling Mld
Enabling MLD Enable MLD on the interface on which IPv6 multicast group memberships are created and maintained. To enable MLD: Step Command Remarks Enter system view. system-view By default, IPv6 Enable IPv6 multicast routing ipv6 multicast routing [ vpn-instance multicast routing is and enter IPv6 MRIB view.
Page 272: Configuring An Ipv6 Multicast Group Filter
Configuration procedure To configure an interface as a static member interface: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, an interface is not a mld static-group Configure the interface as a static member of any IPv6 multicast ipv6-group-address [ source static member interface.
Page 273: Enabling Mld Fast-Leave Processing
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.
Page 274: Configuration Prerequisites
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...
Page 275: Configuring Ipv6 Multicast Forwarding On A Downstream Interface
Step Command Remarks Enable IPv6 multicast ipv6 multicast routing [ vpn-instance By default, IPv6 multicast routing routing and enter IPv6 vpn-instance-name ] is disabled. MRIB view. Return to system view. quit Enter interface view. interface interface-type interface-number Enable the MLD proxying By default, MLD proxying is mld proxy enable feature.
Page 276: Displaying And Maintaining Mld
Step Command Remarks Enable load splitting By default, the load splitting proxy multipath function on the MLD proxy. 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...
Page 277 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.
Page 278 [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. <RouterB> system-view [RouterB] ipv6 multicast routing [RouterB-mrib6] quit # Enable MLD on GigabitEthernet 2/1/1. [RouterB] interface gigabitethernet 2/1/1 [RouterB-GigabitEthernet2/1/1] mld enable [RouterB-GigabitEthernet2/1/1] quit...
Page 279: Mld Ssm Mapping Configuration Example
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 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.
Page 280 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.
Page 281 [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.) 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.
Page 282: Mld Proxying Configuration Example
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.
Page 283: Troubleshooting Mld
<RouterB> 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. [RouterB] interface gigabitethernet 2/1/2 [RouterB-GigabitEthernet2/1/2] mld enable [RouterB-GigabitEthernet2/1/2] quit Verifying the configuration # On Router B, display IPv6 multicast group membership information maintained by the MLD proxy.
Page 284: Inconsistent Membership Information On The Routers On The Same Subnet
Use the display current-configuration interface command to verify that no ACL has been configured to filter out the reports to the IPv6 multicast group G. If the problem persists, contact HP Support. Inconsistent membership information on the routers on the same...
Page 285: Configuring Ipv6 Pim
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.
Page 286 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: 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.
Page 287: Ipv6 Pim-Sm Overview
The node that needs to receive the IPv6 multicast data sends a graft message to its upstream node, telling it to rejoin the SPT. 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.
Page 288 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.
Page 289 Figure 85 DR election As shown in Figure 85, the DR election process is as follows: 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. The router with the highest IPv6 link-local address wins the DR election under either of the following conditions: All the routers have the same DR priority.
Page 290 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: The C-RP that is designated to the smallest IPv6 multicast group range wins.
Page 291 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 •...
Page 292 RPT building Figure 88 RPT building in an IPv6 PIM-SM domain Host A Source Receiver Host B Server Receiver Join message IPv6 multicast packets Host C As shown in Figure 88, the process of building an RPT is as follows: When a receiver wants to join the IPv6 multicast group G, it uses an MLD message to inform the receiver-side DR.
Page 293 Figure 89 IPv6 multicast source registration As shown in Figure 89, the IPv6 multicast source registers with the RP as follows: 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.
Page 294: Ipv6 Bidir-Pim Overview
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: •...
Page 295 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.
Page 296 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: When a receiver wants to join the IPv6 multicast group G, it uses an MLD message to inform the directly connected router.
Page 297: Ipv6 Administrative Scoping Overview
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: 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.
Page 298 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.
Page 299: Ipv6 Pim-Ssm Overview
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.
Page 300: Relationship Among Ipv6 Pim Protocols
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...
Page 301: Ipv6 Pim Support For Vpns
Figure 96 Relationship among IPv6 PIM protocols A receiver joins IPv6 multicast group G. G is in the IPv6 An IPv6 multicast source is SSM group range? specified? IPv6 BIDIR-PIM is enabled? An MLD-SSM mapping is configured for G? IPv6 PIM-SM runs for G. G has an IPv6 BIDIR-PIM IPv6 PIM-SSM runs for G.
Page 302: Ipv6 Pim-Dm Configuration Task List
With IPv6 PIM-DM enabled on interfaces, routers can establish IPv6 PIM neighbor relationship and process IPv6 PIM messages from their IPv6 PIM neighbors. When you deploy an IPv6 PIM-DM domain, HP recommends that you enable IPv6 PIM-DM on all non-border interfaces of routers. IMPORTANT: All the interfaces on a device must operate in the same IPv6 PIM mode in the public network or the same VPN instance.
Page 303: Configuring State Refresh Parameters
To enable the state refresh feature on all routers in IPv6 PIM-DM domain: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, the state refresh feature Enable the state refresh feature. ipv6 pim state-refresh-capable is enabled.
Page 304: Configuring Ipv6 Pim-Sm
With IPv6 PIM-SM enabled on interfaces, routers can establish IPv6 PIM neighbor relationship and process IPv6 PIM messages from their IPv6 PIM neighbors. When you deploy an IPv6 PIM-SM domain, HP recommends that you enable IPv6 PIM-SM on all non-border interfaces.
Page 305: Configuring An Rp
In an IPv6 PIM-SM domain, if you want a router to become the RP, you can configure the router as a C-RP. HP recommends that you configure C-RPs on backbone routers. The C-RPs periodically send advertisement messages to the BSR, which collects RP set information for the...
Page 306 • set on each member RP device. HP recommends that you configure no more than 16 Anycast RP members for an Anycast RP set. • HP recommends that you configure the loopback interface address of an RP member RP device as •...
Page 307: Configuring A Bsr
Step Command Remarks Enter system system-view view. Enter IPv6 PIM ipv6 pim [ vpn-instance vpn-instance-name ] view. By default, Anycast RP is not configured. You can repeat this Configure anycast-rp ipv6-anycast-rp-address command to add multiple RP Anycast RP. ipv6-member-address member addresses to an Anycast RP set.
Page 308 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.
Page 309: Configuring Ipv6 Multicast Source Registration
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.
Page 310: Configuring Switchover To Spt
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).
Page 311: Configuring Ipv6 Bidir-Pim
Because IPv6 BIDIR-PIM is implemented on the basis of IPv6 PIM-SM, you must enable IPv6 PIM-SM before enabling IPv6 BIDIR-PIM. When you deploy an IPv6 BIDIR-PIM domain, HP recommends that you enable IPv6 PIM-SM on all non-border interfaces of the domain.
Page 312: Configuring An Rp
IPv6 BIDIR-PIM. preferred ] * configured. Configuring a C-RP IMPORTANT: When you configure a C-RP, reserve a large bandwidth between the C-RP and other devices in the IPv6 • BIDIR-PIM domain. • HP recommends that you configure C-RPs on backbone routers.
Page 313: Configuring A Bsr
In an IPv6 BIDIR-PIM domain, one DF election per RP is implemented on all IPv6 PIM-enabled interfaces. To avoid unnecessary DF elections, HP recommends not configuring multiple RPs for BIDIR-PIM. This configuration sets a limit on the number of IPv6 BIDIR-PIM RPs. If the number of RPs exceeds the limit, excess RPs do not take effect and can be used only for DF election rather than IPv6 multicast data forwarding.
Page 314 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: Initially, each C-BSR regards itself as the BSR of the IPv6 BIDIR-PIM domain and sends BSMs to other routers in the domain.
Page 315 Step Command Remarks (Optional.) Configure a legal By default, no restrictions are bsr-policy acl6-number BSR address range. 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.
Page 316: Configuring Ipv6 Pim-Ssm
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.
Page 317: Configuring The Ipv6 Ssm Group Range
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.
Page 318: Configuring An Ipv6 Multicast Data Filter
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.
Page 319 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).
Page 320: Configuring Common Ipv6 Pim Timers
If you configure hello message options in both IPv6 PIM view and interface view, the configuration in interface view always takes precedence. TIP: For a network without special requirements, HP recommends that you use the defaults.
Page 321: Setting The Maximum Size Of Each Join Or Prune Message
Configuring common IPv6 PIM timers globally Step Command Remarks Enter system view. system-view ipv6 pim [ vpn-instance Enter IPv6 PIM view. vpn-instance-name ] Set the interval for sending By default, the interval to send timer hello interval hello messages. hello messages is 30 seconds. By default, the interval to send join/prune messages is 60 seconds.
Page 322: Enabling Bfd For Ipv6 Pim
Step Command Remarks Enter system view. system-view ipv6 pim [ vpn-instance Enter IPv6 PIM view. vpn-instance-name ] By default, the maximum size of a Set the maximum size of each jp-pkt-size size join or prune message is 8100 join or prune message. bytes.
Page 323: Displaying And Maintaining Ipv6 Pim
Displaying and maintaining IPv6 PIM Execute display commands in any view. Task Command Display information about the display interface [ register-tunnel [ interface-number ] ] [ brief register-tunnel interface. [ description| down ] ] Display BSR information in the IPv6 display ipv6 pim [ vpn-instance vpn-instance-name ] bsr-info PIM-SM domain.
Page 324 Figure 97 Network diagram Table 21 Interface and IPv6 address assignment IPv6 Device Interface IPv6 address Device Interface 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...
Page 325 [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.
Page 326 # 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. [RouterA] display ipv6 pim routing-table Total 1 (*, G) entry; 1 (S, G) entry (*, FF0E::101) Protocol: pim-dm, Flag: WC UpTime: 00:01:24...
Page 327: Ipv6 Pim-Sm Non-Scoped Zone Configuration Example
IPv6 PIM-SM non-scoped zone configuration example Network requirements As shown in Figure 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.
Page 328 IPv6 Device Interface IPv6 address Device Interface address Router C GigabitEthernet 2/1/2 3001::1/64 Router E GigabitEthernet 2/1/4 4002::2/64 Configuration procedure Assign an IPv6 address and prefix length to each interface according to Figure 98. (Details not shown.) Enable OSPFv3 on all routers on the IPv6 PIM-SM network to make sure the following conditions are met: (Details not shown.) The routers are interoperable at the network layer.
Page 329 [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...
Page 330: Ipv6 Pim-Sm Admin-Scoped Zone Configuration Example
IPv6 PIM-SM admin-scoped zone configuration example Network requirements As shown in Figure 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.
Page 331 IPv6 Device Interface Device Interface IPv6 address 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...
Page 332 # On Router B, enable IPv6 multicast routing, and enable IPv6 PIM-SM on each interface. <RouterB> system-view [RouterB] ipv6 multicast routing [RouterB-mrib6] quit [RouterB] interface gigabitethernet 2/1/1 [RouterB-GigabitEthernet2/1/1] ipv6 pim sm [RouterB-GigabitEthernet2/1/1] quit [RouterB] interface gigabitethernet 2/1/2 [RouterB-GigabitEthernet2/1/2] ipv6 pim sm [RouterB-GigabitEthernet2/1/2] quit [RouterB] interface gigabitethernet 2/1/3 [RouterB-GigabitEthernet2/1/3] ipv6 pim sm...
Page 333 [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.
Page 334 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...
Page 335: Ipv6 Bidir-Pim Configuration Example
1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FF74::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FF84::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FF94::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FFA4::/16 RP address Priority...
Page 336 Figure 100 Network diagram Loop0 Receiver 1 Receiver 2 Router B GE2/1/1 GE2/1/3 GE2/1/1 Router C Host A Host B GE2/1/2 GE2/1/2 IPv6 BIDIR-PIM Source 1 Source 2 GE2/1/2 GE2/1/3 GE2/1/1 GE2/1/2 Router A Router D Table 24 Interface and IPv6 address assignment IPv6 Device Interface...
Page 337 [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. <RouterB> system-view [RouterB] ipv6 multicast routing [RouterB-mrib6] quit # Enable MLD on GigabitEthernet 2/1/1 (the interface that connects to the receiver host).
Page 338 [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. [RouterD] interface gigabitethernet 2/1/2 [RouterD-GigabitEthernet2/1/2] ipv6 pim sm [RouterD-GigabitEthernet2/1/2] quit [RouterD] interface gigabitethernet 2/1/3...
Page 339 Loop0 GE2/1/1 01:06:07 FE80::20F:E2FF: FE15:5601 (local) GE2/1/2 01:06:07 FE80::20F:E2FF: FE15:5602 (local) # Display the DF information of IPv6 BIDIR-PIM on Router D. [RouterD] display ipv6 pim df-info RP address: 6001::1 Interface State DF-Pref DF-Metric DF-Uptime DF-Address GE2/1/1 01:19:53 FE80::200:5EFF: FE71:2803 (local) GE2/1/2 00:39:34 FE80::200:5EFF:...
Page 340: Ipv6 Pim-Ssm Configuration Example
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...
Page 341 Table 25 Interface and IPv6 address assignment IPv6 Device Interface Device Interface IPv6 address 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...
Page 342 [RouterA] ipv6 pim [RouterA-pim6] ssm-policy 2000 [RouterA-pim6] quit 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. [RouterA] display ipv6 pim interface Interface NbrCnt HelloInt...
Page 343: Troubleshooting Ipv6 Pim
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.
Page 344: Ipv6 Multicast Data Is Abnormally Terminated On An Intermediate Router
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. If the problem persists, contact HP Support. IPv6 multicast data is abnormally terminated on an...
Page 345: An Rpt Cannot Be Built Or Ipv6 Multicast Source Registration Fails In Ipv6 Pim-Sm
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.
Page 346: Support And Other Resources
Related information Documents To find related documents, browse to the Manuals page of the HP Business Support Center website: http://www.hp.com/support/manuals For related documentation, navigate to the Networking section, and select a networking category. •...
Page 347: Conventions
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. Braces enclose a set of required syntax choices separated by vertical bars, from which { x | y | ...
Page 348 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.
Page 349 Configuring PIM-SSM,108 Configuring SA message related parameters,147 Adjusting IGMP performance,64 Configuring the MLD snooping querier,228 Adjusting MLD performance,262 Contacting HP,336 Conventions,337 Configuration examples,48 Configuration task list,248 Displaying and maintaining IGMP,68 Configuring an IGMP snooping querier,23 Displaying and maintaining IGMP snooping,30...
Page 350 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 Multicast architecture,5 PIM configuration examples,1 15 Multicast models,5 Multicast packet forwarding mechanism,1 1 Multicast routing and forwarding configuration task Related information,336...

This manual is also suitable for:

Msr3024 Msr3044 Msr3064 Msr4000 Msr4060 Msr4080. ... Show all

HP MSR2003 Configuration Manual

Quick Links

Troubleshooting

Need help?

Questions and answers

Related Manuals for HP MSR2003

Summary of Contents for HP MSR2003