Page 1 HPE FlexNetwork MSR Router Series Comware 7 IP Multicast Configuration Guide Part number: 5200-2392 Software version: MSR-CMW710-R0411 Document version: 6W101-20161114...
Page 2 © Copyright 2016 Hewlett Packard Enterprise Development LP The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise 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. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
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 ·························································································································· 4 Multicast architecture ···················································································································· 5 Multicast addresses ··············································································································· 5 Multicast protocols ·················································································································...
Page 4 Multicast group policy does not work ······················································································· 40 Configuring multicast routing and forwarding ········································ 41 Overview ·································································································································· 41 RPF check mechanism ········································································································· 41 Static multicast routes ·········································································································· 43 Multicast forwarding across unicast subnets ············································································· 44 Command and hardware compatibility···························································································· 45 Configuration task list··················································································································...
Page 5 Configuring PIM ············································································· 87 Overview ·································································································································· 87 PIM-DM overview ················································································································ 87 PIM-SM overview ················································································································ 89 BIDIR-PIM overview ············································································································ 95 Administrative scoping overview ····························································································· 98 PIM-SSM overview ············································································································ 100 Relationship among PIM protocols························································································ 101 PIM support for VPNs ········································································································ 102 Protocols and standards ····································································································· 102 Configuring PIM-DM ·················································································································...
Page 6 Configuring MSDP ········································································ 146 Overview ································································································································ 146 How MSDP works ············································································································· 146 MSDP support for VPNs ····································································································· 151 Protocols and standards ····································································································· 151 MSDP configuration task list ······································································································· 152 Configuring basic MSDP features ································································································ 152 Configuration prerequisites·································································································· 152 Enabling MSDP ················································································································ 152 Specifying an MSDP peer ···································································································...
Page 7 Intra-AS MD VPN configuration example ··············································································· 201 Intra-AS M6VPE configuration example ················································································· 214 MD VPN inter-AS option C configuration example ··································································· 229 MD VPN inter-AS option B configuration example ···································································· 242 Troubleshooting MD VPN ·········································································································· 255 A default-MDT cannot be established ···················································································· 255 An MVRF cannot be created ·······························································································...
Page 8 Configuring an IPv6 multicast forwarding boundary ·································································· 290 Configuring static IPv6 multicast MAC address entries ····························································· 290 Enabling IPv6 multicast forwarding between sub-VLANs of a super VLAN ··································· 291 Displaying and maintaining IPv6 multicast routing and forwarding ····················································· 292 Configuration examples ············································································································· 294 IPv6 multicast forwarding over a GRE tunnel ··········································································...
Page 9 Configuration prerequisites·································································································· 343 Enabling IPv6 PIM-SM ······································································································· 343 Configuring an RP ············································································································· 344 Configuring a BSR ············································································································· 346 Configuring IPv6 multicast source registration ········································································· 348 Configuring the switchover to SPT ························································································ 349 Configuring IPv6 BIDIR-PIM ······································································································· 349 IPv6 BIDIR-PIM configuration task list ··················································································· 349 Configuration prerequisites··································································································...
Page 10: 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.
Page 11 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 Host A Receiver Host B Source Host C Receiver Host D A network segment Receiver Packets for all hosts Host E...
Page 12: Multicast Features
Figure 3 Multicast transmission Host A Receiver Host B Source Host C Receiver Host D IP network Receiver Packets for the multicast group Host E Figure 3, 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.
Page 13: Common Notations In Multicast
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. group. A user tunes the TV set to the channel. A receiver joins the multicast group.
Page 14: Multicast Architecture
ASM model In the ASM model, any multicast sources can send information to a multicast group. Receivers can join a multicast group and get multicast information addressed to that multicast group from any multicast sources. In this model, receivers do not know the positions of the multicast sources in advance.
Page 15 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. Other IP addresses can be used by routing protocols and for topology searching, protocol 224.0.0.0 to 224.0.0.255 maintenance, and so on. Table 3 lists common permanent group addresses.
Page 16 Figure 4 IPv6 multicast format 0xFF Flags Scope Group ID (112 bits) The following describes the fields of an IPv6 multicast address: 0xFF—The most significant eight bits are 11111111.  Flags—The Flags field contains four bits.  Figure 5 Flags field format 0 R P T Table 4 Flags field description Description...
Page 17: Multicast Protocols
Value Meaning Global scope. Group ID—The Group ID field contains 112 bits. It uniquely identifies an IPv6 multicast  group in the scope that the Scope field defines. Ethernet multicast MAC addresses • IPv4 multicast MAC addresses: As defined by IANA, the most significant 24 bits of an IPv4 multicast MAC address are 0x01005E.
Page 18 Layer 3 multicast protocols—IGMP, MLD, PIM, IPv6 PIM, and MSDP. Layer 2 multicast refers to IP multicast operating at the data link layer.  Layer 2 multicast protocols—IGMP snooping and MLD snooping. • IPv4 and IPv6 multicast protocols: For IPv4 networks—IGMP snooping, IGMP, PIM, and MSDP. ...
Page 19: Multicast Packet Forwarding Mechanism
MBGP is an extension of the MP-BGP for exchanging multicast routing information among different ASs. For the SSM model, multicast routes are not divided into intra-domain routes and inter-domain routes. Because receivers know the positions of the multicast sources, channels established through PIM-SM are sufficient for the transport of multicast information.
Page 20: Multicast Application In Vpns
Figure 9 VPN networking diagram VPN A CE a2 CE b2 CE b3 PE 2 VPN B VPN B CE b1 CE a1 CE a3 PE 1 PE 3 Public network VPN A VPN A • 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.
Page 21: Configuring Igmp Snooping
Configuring IGMP snooping Overview IGMP snooping runs on a Layer 2 device as a multicast constraining mechanism to improve multicast forwarding efficiency. It creates Layer 2 multicast forwarding entries from IGMP packets that are exchanged between the hosts and the router. As shown in Figure 10, when IGMP snooping is not enabled, the Layer 2 switch floods multicast...
Page 22 Figure 11 IGMP snooping ports Receiver Router A Switch A GE1/0/1 GE1/0/2 Host A GE1/0/3 Host B Receiver GE1/0/1 Source GE1/0/2 Host C Switch B Router port Member port Multicast packets Host D Router ports On an IGMP snooping Layer 2 device, the ports toward Layer 3 multicast devices are called router ports.
Page 23: How Igmp Snooping Works
How IGMP snooping works The ports in this section are dynamic ports. For information about how to configure and remove static ports, see "Configuring static ports." IGMP messages types include general query, IGMP report, and leave message. An IGMP snooping-enabled Layer 2 device performs differently depending on the message types. General query The IGMP querier periodically sends IGMP general queries to all hosts and routers on the local subnet to check for the existence of multicast group members.
Page 24: Protocols And Standards
This feature is supported only on the following ports: • Layer 2 Ethernet ports on the following modules: HMIM-8GSW.  HMIM-24GSW.  HMIM-24GSW-PoE.  SIC-4GSW.  SIC-9FSW.  SIC-9FSW-PoE.  • Fixed Layer 2 Ethernet ports on the following routers: MSR1002-4/1003-8S.  MSR2004-24/2004-48. ...
Page 25: Command And Hardware Compatibility
MSR954 (JH296A/JH297A/JH298A/JH299A/JH373A).  MSR958 (JH300A/JH301A).  Command and hardware compatibility Commands and descriptions for centralized devices apply to the following routers: • MSR1002-4/1003-8S. • MSR2003. • MSR2004-24/2004-48. • MSR3012/3024/3044/3064. • MSR954 (JH296A/JH297A/JH298A/JH299A/JH373A). • MSR958 (JH300A/JH301A). Commands and descriptions for distributed devices apply to the following routers: •...
Page 26: Configuring Basic Igmp Snooping Features
The IGMP snooping configurations made on Layer 2 aggregate interfaces do not interfere with the configurations made on member ports. In addition, the configurations made on Layer 2 aggregate interfaces do not take part in aggregation calculations. The configuration made on a member port of the aggregate group takes effect after the port leaves the aggregate group.
Page 27: Setting The Maximum Number Of Igmp Snooping Forwarding Entries
• IGMPv2 snooping processes IGMPv1 and IGMPv2 messages, but it floods IGMPv3 messages in the VLAN instead of processing them. • IGMPv3 snooping processes IGMPv1, IGMPv2, and IGMPv3 messages. If you change IGMPv3 snooping to IGMPv2 snooping, the device does the following: •...
Page 28: Setting The Igmp Last Member Query Interval
Setting the IGMP last member query interval A receiver host starts a report delay timer for a multicast group when it receives an IGMP group-specific query for the group. This timer is set to a random value in the range of 0 to the maximum response time advertised in the query.
Page 29: Configuring Static Ports
• If a dynamic router port receives a PIMv2 hello message, the aging timer for the port is specified by the hello message. In this case, the router-aging-time or igmp-snooping router-aging-time command does not take effect on the port. • IGMP group-specific queries originated by the Layer 2 device trigger the adjustment of aging timers for dynamic member ports.
Page 30: Configuring A Port As A Simulated Member Host
Step Command Remarks • Configure the port as a static member port: igmp-snooping static-group group-address [ source-ip source-address ] By default, a port is not a static Configure the port as a static vlan vlan-id member port or a static router port.
Page 31: Disabling A Port From Becoming A Dynamic Router Port
Step Command Remarks Enter system view. system-view Enter IGMP-snooping view. igmp-snooping Enable fast-leave By default, fast-leave processing fast-leave [ vlan vlan-list ] processing globally. is disabled globally. To enable fast-leave processing on a port: Step Command Remarks Enter system view. system-view Enter Layer...
Page 32: Configuration Prerequisites
Configuration prerequisites Before you configure the IGMP snooping querier, complete the following tasks: • Enable IGMP snooping for the VLAN. • Determine the IGMP general query interval. • Determine the maximum response time for IGMP general queries. Enabling the IGMP snooping querier This feature enables the device to periodically send IGMP general queries to establish and maintain multicast forwarding entries at the data link Layer.
Page 33: Configuring Parameters For Igmp Messages
Configuring parameters for IGMP general queries and responses globally Step Command Remarks Enter system view. system-view Enter IGMP-snooping view. igmp-snooping Set the maximum response time IGMP general max-response-time seconds The default setting is 10 seconds. queries. Configuring parameters for IGMP general queries and responses in a VLAN Step Command Remarks...
Page 34: Setting The 802.1P Priority For Igmp Messages
Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id By default, the source IP address of IGMP general queries is the IP Configure source igmp-snooping address current VLAN address for IGMP general general-query source-ip interface. current VLAN queries.
Page 35: Configuring Igmp Snooping Policies
Step Command Remarks Set the 802.1p priority for By default, the 802.1p priority for dot1p-priority priority IGMP messages. IGMP packets is not set. Setting the 802.1p priority for IGMP messages in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view.
Page 36: Enabling Multicast Source Port Filtering
Enabling multicast source port filtering This feature is supported only on the following ports: • Layer 2 Ethernet ports on the HMIM-8GSW, HMIM-24GSW, and HMIM-24GSW-PoE. • Fixed Layer 2 Ethernet ports on the following routers: MSR1002-4/1003-8S.  MSR2004-24/2004-48.  MSR954 (JH296A/JH297A/JH298A/JH299A/JH373A). ...
Page 37: Enabling Igmp Report Suppression
MSR1002-4/1003-8S.  MSR2004-24/2004-48.  MSR954 (JH296A/JH297A/JH298A/JH299A/JH373A).  MSR958 (JH300A/JH301A).  This feature enables the device to drop all unknown multicast data. Unknown multicast data refers to multicast data for which no forwarding entries exist in the IGMP snooping forwarding table.
Page 38: Enabling The Multicast Group Replacement Feature
Step Command Remarks Enter system view. system-view Enter Layer Ethernet interface interface-type interface view or Layer 2 interface-number aggregate interface view. By default, no limit is placed on Set the maximum number of igmp-snooping group-limit limit the maximum number of multicast multicast groups on a port.
Page 39 Task Command display igmp-snooping [ global | vlan vlan-id ] Display IGMP snooping status. Display dynamic IGMP snooping group display igmp-snooping group group-address entries (Centralized devices in IRF source-address ] * [ vlan vlan-id ] [ verbose ] mode). Display dynamic IGMP snooping group display igmp-snooping group...
Page 40 Task Command display l2-multicast fast-forwarding cache [ vlan vlan-id ] Display Layer 2 multicast fast forwarding [ source-address | group-address ] * [ chassis chassis-number entries (Distributed devices in IRF mode). slot slot-number ] Display information about Layer 2 IP display l2-multicast ip [ group group-address | source multicast groups (Centralized devices in source-address ] * [ vlan vlan-id ]...
Page 41: Igmp Snooping Configuration Examples
Task Command reset l2-multicast fast-forwarding cache [ vlan vlan-id ] Clear Layer 2 multicast fast forwarding { { source-address | group-address } * | all } [ chassis entries (Distributed devices in IRF mode). chassis-number slot slot-number ] reset igmp-snooping router-port { all | vlan vlan-id } Clear dynamic router port information.
Page 42 [RouterA-mrib] quit # Enable IGMP on GigabitEthernet 1/0/1. [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] igmp enable [RouterA-GigabitEthernet1/0/1] quit # Enable PIM-DM on GigabitEthernet 1/0/2. [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] pim dm [RouterA-GigabitEthernet1/0/2] quit Configure Switch A: # Enable IGMP snooping globally. <SwitchA>...
Page 43: Static Port Configuration Example
Host slots (0 in total): Host ports (2 in total): GE1/0/3 (00:03:23) GE1/0/4 (00:04:10) The output shows the following information: • Host A and Host B have joined multicast group 224.1.1.1 through the member ports GigabitEthernet 1/0/4 and GigabitEthernet 1/0/3 on Switch A, respectively. •...
Page 44 Figure 13 Network diagram Switch B Source Switch A GE1/0/2 GE1/0/1 1.1.1.2/24 10.1.1.1/24 GE1/0/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, as shown in Figure 13.
Page 45 [SwitchA-vlan100] quit # Configure GigabitEthernet 1/0/3 as a static router port. [SwitchA] interface gigabitethernet 1/0/3 [SwitchA-GigabitEthernet1/0/3] igmp-snooping static-router-port vlan 100 [SwitchA-GigabitEthernet1/0/3] quit Configure Switch B: # Enable IGMP snooping globally. <SwitchB> system-view [SwitchB] igmp-snooping [SwitchB-igmp-snooping] quit # Create VLAN 100, and assign GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 to the VLAN. [SwitchB] vlan 100 [SwitchB-vlan100] port gigabitethernet 1/0/1 gigabitethernet 1/0/2 # Enable IGMP snooping for VLAN 100.
Page 46: Igmp Snooping Querier Configuration Example
VLAN 100: Total 1 entries. (0.0.0.0, 224.1.1.1) Host slots (0 in total): Host ports (2 in total): GE1/0/3 GE1/0/5 The output shows that GigabitEthernet 1/0/3 and GigabitEthernet 1/0/5 on Switch C have become static member ports of multicast group 224.1.1.1. IGMP snooping querier configuration example Network requirements As shown in...
Page 47 Configuration procedure Configure Switch A: # Enable IGMP snooping globally. <SwitchA> system-view [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 100, and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/3 # Enable IGMP snooping, and enable dropping unknown multicast data for VLAN 100.
Page 48: Troubleshooting Igmp Snooping
Configure Switch D: # Enable IGMP snooping globally. <SwitchD> system-view [SwitchD] igmp-snooping [SwitchD-igmp-snooping] quit # Create VLAN 100, and assign GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 to the VLAN. [SwitchD] vlan 100 [SwitchD-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/2 # Enable IGMP snooping, and enable dropping unknown multicast data for VLAN 100. [SwitchD-vlan100] igmp-snooping enable [SwitchD-vlan100] igmp-snooping drop-unknown [SwitchD-vlan100] quit...
Page 49: Multicast Group Policy Does Not Work
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 Hewlett Packard Enterprise Support. Multicast group policy does not work Symptom Hosts can receive multicast data for multicast groups that are not permitted by the multicast group policy.
Page 50: Configuring Multicast Routing And Forwarding
Configuring multicast routing and forwarding 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. • General multicast routing table that summarizes multicast routing information generated by different multicast routing protocols.
Page 51 RPF check implementation in multicast Implementing an RPF check on each received multicast packet brings a big burden to the router. The use of a multicast forwarding table is the solution to this issue. When the router creates a multicast forwarding entry for an (S, G) packet, it sets the RPF interface of the packet as the incoming interface of the (S, G) entry.
Page 52: Static Multicast Routes
• If a multicast packet arrives at Router C on GigabitEthernet 1/0/1, the receiving interface is not the incoming interface of the (S, G) entry. Router C searches its unicast routing table and finds that the outgoing interface to the source (the RPF interface) is GigabitEthernet 1/0/2. In this case, the (S, G) entry is correct, but the packet traveled along a wrong path.
Page 53: Multicast Forwarding Across Unicast Subnets
Figure 17 Creating an RPF route Multicast Routing Table Static on Router C OSPF domain Source/Mask Interface RPF neighbor/Mask 192.168.0.0/24 GE1/0/1 1.1.1.1/24 Receiver Router D Multicast Routing Table Static on Router D GE1/0/1 Source/Mask Interface RPF neighbor/Mask 2.2.2.1/24 192.168.0.0/24 GE1/0/1 2.2.2.2/24 Source RIP domain...
Page 54: Command And Hardware Compatibility
To use this tunnel only for multicast traffic, configure the tunnel as the outgoing interface only for multicast routes. Command and hardware compatibility Commands and descriptions for centralized devices apply to the following routers: • MSR1002-4/1003-8S. • MSR2003. • MSR2004-24/2004-48.
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 and secondary IP addresses, and IP unnumbered, see Layer 3—IP Services Configuration Guide.
Page 56: Specifying The Longest Prefix Match Principle
Step Command Remarks • Delete a specific static multicast route: undo 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 rpf-route-static vpn-instance vpn-instance-name ] Specifying the longest prefix match principle You can enable the device to use the longest prefix match principle for RPF route selection.
Page 57: Configuring Static Multicast Mac Address Entries
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 the interface as a multicast boundary multicast forwarding By default, an interface is not a group-address { mask-length |...
Page 58: Enabling Multicast Forwarding Between Sub-Vlans Of A Super Vlan
Enabling multicast forwarding between sub-VLANs of a super VLAN A super VLAN is associated with multiple sub-VLANs. Sub-VLANs are isolated with each other at Layer 2. For information about the super VLAN and sub-VLANs, see Layer 2—LAN Switching Configuration Guide. To enable multicast forwarding between sub-VLANs that are associated with a super VLAN: Step Command...
Page 59 Task Command display multicast [ vpn-instance vpn-instance-name ] Display multicast fast forwarding entries fast-forwarding cache [ source-address | group-address ] * (distributed devices in IRF mode). [ chassis chassis-number slot slot-number ] display multicast [ vpn-instance vpn-instance-name ] Display information (centralized forwarding df-info [ rp-address ] [ verbose ] devices in standalone mode).
Page 60: Configuration Examples
Task Command display multicast [ vpn-instance vpn-instance-name ] routing-table [ source-address [ mask { mask-length | mask } ] | group-address [ mask { mask-length | mask } ] | Display multicast routing entries. incoming-interface interface-type interface-number outgoing-interface exclude include match interface-type interface-number ] * display multicast [ vpn-instance vpn-instance-name ]...
Page 61 Figure 19 Network diagram Router C GE1/0/2 GE1/0/1 40.1.1.1/24 20.1.1.2/24 PIM-DM GE1/0/2 GE1/0/2 40.1.1.2/24 20.1.1.1/24 Router A Router B GE1/0/3 GE1/0/3 30.1.1.2/24 30.1.1.1/24 GE1/0/1 GE1/0/1 50.1.1.1/24 10.1.1.1/24 Source Receiver 50.1.1.100/24 10.1.1.100/24 Multicast static route Configuration procedure Assign an IP address and subnet mask for each interface, as shown in Figure 19.
Page 62: Creating An Rpf Route
[RouterA-GigabitEthernet1/0/1] quit [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] pim dm [RouterA-GigabitEthernet1/0/2] quit [RouterA] interface gigabitethernet 1/0/3 [RouterA-GigabitEthernet1/0/3] pim dm [RouterA-GigabitEthernet1/0/3] quit # Enable IP multicast routing and PIM-DM on Router C in the same way Router A is configured. (Details not shown.) Display RPF information for Source on Router B.
Page 63 Figure 20 Network diagram PIM-DM OSPF domain Router A Router B Router C GE1/0/2 GE1/0/3 GE1/0/2 30.1.1.2/24 30.1.1.1/24 20.1.1.1/24 GE1/0/2 20.1.1.2/24 GE1/0/1 GE1/0/1 GE1/0/1 50.1.1.1/24 40.1.1.1/24 10.1.1.1/24 Source 2 Source 1 Receiver 50.1.1.100/24 40.1.1.100/24 10.1.1.100/24 Multicast static route Configuration procedure Assign an IP address and subnet mask for each interface, as shown in Figure 20.
Page 64: Multicast Forwarding Over A Gre Tunnel
[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. Configure a static multicast route: # Configure a static multicast route on Router B and specify Router A as its RPF neighbor to Source 2.
Page 65 Figure 21 Network diagram Multicast router Unicast router Multicast router Router A Router B Router C GE1/0/2 GE1/0/1 GE1/0/2 GE1/0/2 20.1.1.1/24 30.1.1.2/24 20.1.1.2/24 30.1.1.1/24 GE1/0/1 GE1/0/1 GRE tunnel 10.1.1.1/24 40.1.1.1/24 Tunnel0 Tunnel0 50.1.1.1/24 50.1.1.2/24 Source Receiver 10.1.1.100/24 40.1.1.100/24 Configuration procedure Assign an IP address and mask for each interface, as shown in Figure 21.
Page 66 [RouterA] interface tunnel 0 [RouterA-Tunnel0] pim dm [RouterA-Tunnel0] quit # On Router C, enable IP multicast routing. [RouterC] multicast routing [RouterC-mrib] quit # Enable IGMP on the receiver-side interface (GigabitEthernet 1/0/1). [RouterC] interface gigabitethernet 1/0/1 [RouterC-GigabitEthernet1/0/1] igmp enable [RouterC-GigabitEthernet1/0/1] quit # Enable PIM-DM on other interfaces.
Page 67: Multicast Forwarding Over Advpn Tunnels
Protocol: pim-dm, UpTime: 00:04:25, Expires: - The output shows that Router A is the RPF neighbor of Router C and the multicast data from Router A is delivered over the GRE tunnel to Router C. Multicast forwarding over ADVPN tunnels Network requirements As shown in Figure...
Page 68 Device Interface IP address Device Interface IP address Hub 2 Loop0 2.2.2.2/32 Configuration procedure Assign an IP address and subnet mask to each interface, as shown in Table 6. (Details not shown.) Configure ADVPN: a. Configure the VAM server: # Create an ADVPN domain named abc. <Server>system-view [Server]vam server advpn-domain abc id 1 # Set the pre-shared key to 123456.
Page 69 [Hub2-vam-client-hub2]server primary ip-address 100.1.1.100 # Set the pre-shared key to 123456. [Hub2-vam-client-hub2]pre-shared-key simple 123456 # Enable the VAM client. [Hub2-vam-client-hub2]client enable d. Configure Spoke 1: # Create a VAM client named Spoke1. <Spoke1>system-view [Spoke1]vam client name Spoke1 # Specify ADVPN domain abc for the VAM client. [Spoke1-vam-client-Spoke1]advpn-domain abc # Specify the VAM server.
Page 70 [Spoke1]interface tunnel 1 mode advpn gre [Spoke1-Tunnel1]ip address 192.168.0.3 24 [Spoke1-Tunnel1]ospf network-type p2mp [Spoke1-Tunnel1]source gigabitethernet 1/0/1 [Spoke1-Tunnel1]vam client Spoke1 [Spoke1-Tunnel1]quit # On Spoke 2, configure GRE-mode IPv4 ADVPN tunnel interface tunnel1. [Spoke2]interface tunnel 1 mode advpn gre [Spoke2-Tunnel1]ip address 192.168.0.4 24 [Spoke2-Tunnel1]ospf network-type p2mp [Spoke2-Tunnel1]source gigabitethernet 1/0/1 [Spoke2-Tunnel1]vam client Spoke2...
Page 71 # Enable IP multicast routing. <Hub1>system-view [Hub1]multicast routing [Hub1-mrib]quit # Enable PIM-SM on Loopback 0 and GigabitEthernet 1/0/2. [Hub1]interface loopback 0 [Hub1-LoopBack0]pim sm [Hub1-LoopBack0]quit [Hub1]interface gigabitethernet 1/0/2 [Hub1-GigabitEthernet1/0/2]pim sm [Hub1-GigabitEthernet1/0/2]quit # Enable PIM-SM and NBMA mode on tunnel interface tunnel1. [Hub1]interface tunnel 1 [Hub1-Tunnel1]pim sm [Hub1-Tunnel1]pim nbma-mode...
Page 72 # Enable PIM-SM and IGMP on GigabitEthernet 1/0/2. [Spoke1]interface gigabitethernet 1/0/2 [Spoke1-GigabitEthernet1/0/2]pim sm [Spoke1-GigabitEthernet1/0/2]igmp enable [Spoke1-GigabitEthernet1/0/2]quit # Enable PIM-SM and NBMA mode on tunnel interface tunnel1. [Spoke1]interface tunnel 1 [Spoke1-Tunnel1]pim sm [Spoke1-Tunnel1]pim nbma-mode [Spoke1-Tunnel1]quit d. Configure Spoke 2: # Enable IP multicast routing. <Spoke2>system-view [Spoke2]multicast routing [Spoke2-mrib]quit...
Page 73: Troubleshooting Multicast Routing And Forwarding
Total number of downstream interfaces: 1 1: Tunnel1, 192.168.0.3 Protocol: pim-sm, UpTime: 00:00:02, Expires: 00:03:28 The output shows that tunnel interface tunnel1 (192.168.0.3) on Spoke 1 will receive the multicast data addressed to multicast group 225.1.1.1 from the source. Troubleshooting multicast routing and forwarding Static multicast route failure Symptom No dynamic routing protocol is enabled on the routers, and the physical status and link layer status of...
Page 74: Configuring Igmp
Configuring IGMP Overview Internet Group Management Protocol (IGMP) establishes and maintains the multicast group memberships between a Layer 3 multicast device and the hosts on the directly connected subnet. IGMP has the following versions: • IGMPv1 (defined by RFC 1112). •...
Page 75: Igmpv2 Enhancements
The hosts send unsolicited IGMP reports to the multicast groups they want to join without having to wait for the IGMP queries. The IGMP querier periodically multicasts IGMP queries (with the destination address of 224.0.0.1) to all hosts and routers on the local subnet. After receiving a query message, the host whose report delay timer expires first sends an IGMP report to multicast group G1 to announce its membership for G1.
Page 76: Igmpv3 Enhancements
After receiving the leave message, the querier sends a configurable number of IGMP group-specific queries to the group that the host is leaving. Both the destination address field and the group address field of the message are the address of the multicast group that is being queried.
Page 77: Igmp Ssm Mapping
IGMPv3 is compatible with IGMPv1 and IGMPv2 and supports IGMP general queries and IGMP group-specific queries. It also introduces IGMP group-and-source-specific queries. A general query does not carry a group address or a source address.  A group-specific query carries a group address, but no source address. ...
Page 78: Igmp Proxying
Figure 25 IGMP SSM mapping IGMPv1 report IGMPv2 report Querier IGMPv3 report Router A Receiver Receiver Receiver Host A (IGMPv1) Host B (IGMPv2) Host C (IGMPv3) As shown in Figure 25, on an SSM network, Host A, Host B, and Host C run IGMPv1, IGMPv2, and IGMPv3, respectively.
Page 79: Igmp Support For Vpns
Figure 26 IGMP proxying Proxy Querier Router B Router A PIM domain Ethernet Receiver Receiver Host B Host A Host C Report from Router B Query from Router A Query from Router B Host interface Report from Host Router interface The following types of interfaces are defined in IGMP proxying: •...
Page 80: Igmp Configuration Task List
IGMP configuration task list Tasks at a glance Configuring basic IGMP features: • (Required.) Enabling IGMP • (Optional.) Specifying an IGMP version • (Optional.) Configuring a static group member • (Optional.) Configuring a multicast group policy Adjusting IGMP performance: (Optional.) Configuring IGMP query and response parameters (Optional.) Enabling fast-leave processing...
Page 81: Specifying An Igmp Version
Specifying an IGMP version For IGMP to operate correctly, specify the same IGMP version for all routers on the same subnet. To specify an IGMP version: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Specify an IGMP version on the igmp version version-number The default setting is 2.
Page 82: Adjusting Igmp Performance
Step Command Remarks interface interface-type Enter interface view. interface-number By default, no IGMP multicast igmp group-policy group policy exists Configure a multicast group ipv4-acl-number interface. Hosts attached to the policy. [ version-number ] interface can join any multicast groups. Adjusting IGMP performance Before adjusting IGMP performance, complete the following tasks: •...
Page 83 • To avoid frequent IGMP querier changes, set the IGMP other querier present timer greater than the IGMP general query interval. In addition, configure the same IGMP other querier present timer for all IGMP routers on the same subnet. • To avoid mistakenly deleting multicast receivers, set the IGMP general query interval greater than the maximum response time for IGMP general queries.
Page 84: Enabling Fast-Leave Processing
Configuring the IGMP query and response parameters on an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number IGMP querier's By default, the IGMP querier's igmp robust-count count robustness variable. robustness variable is 2. By default, the IGMP startup Set the IGMP startup query igmp startup-query-interval...
Page 85: Configuring Igmp Ssm Mappings
Configuring IGMP SSM mappings This feature enables the device to provide SSM services for IGMPv1 or IGMPv2 hosts. This feature does not process IGMPv3 messages. As a best practice, enable IGMPv3 on the receiver-side interface to avoid IGMPv3 hosts failing to join multicast groups. Configuration prerequisites Before you configure IGMP SSM mappings, complete the following tasks: •...
Page 86: Enabling Multicast Forwarding On A Non-Querier Interface
ensure that the downstream receiver hosts on the router interface can receive multicast data, you must enable multicast forwarding on the interface. For more information, see "Enabling multicast forwarding on a non-querier interface." To enable IGMP proxying: Step Command Remarks Enter system view.
Page 87: Enabling Igmp Nsr
Enabling IGMP NSR The following matrix shows the feature and hardware compatibility: Hardware IGMP NSR compatibility MSR954 (JH296A/JH297A/JH298A/JH299A/JH373A) MSR958 (JH300A/JH301A) MSR1002-4/1003-8S MSR2003 MSR2004-24/2004-48 MSR3012/3024/3044/3064 MSR4060/4080 This feature backs up information about IGMP interfaces and IGMP multicast groups to the standby process.
Page 88: Igmp Configuration Examples
Task Command display igmp [ vpn-instance vpn-instance-name ] proxy Display multicast group membership group group-address interface interface-type information maintained by the IGMP proxy. interface-number ] [ verbose ] display igmp [ vpn-instance vpn-instance-name ] proxy routing-table [ source-address [ mask { mask-length | Display multicast routing entries maintained by the IGMP proxy.
Page 89 Figure 27 Network diagram Receiver PIM-DM Host A GE1/0/1 10.110.1.1/24 Router A Host B Querier GE1/0/1 10.110.2.1/24 Receiver Host C Router B GE1/0/1 10.110.2.2/24 Host D Router C Configuration procedure Assign an IP address and subnet mask to each interface, as shown in Figure 27.
Page 90: Igmp Ssm Mapping Configuration Example
[RouterB-GigabitEthernet1/0/2] quit # On Router C, enable IP multicast routing. <RouterC> system-view [RouterC] multicast routing [RouterC-mrib] quit # Enable IGMP on GigabitEthernet 1/0/1. [RouterC] interface gigabitethernet 1/0/1 [RouterC-GigabitEthernet1/0/1] igmp enable [RouterC-GigabitEthernet1/0/1] quit # Enable PIM-DM on GigabitEthernet 1/0/2. [RouterC] interface gigabitethernet 1/0/2 [RouterC-GigabitEthernet1/0/2] pim dm [RouterC-GigabitEthernet1/0/2] quit Configure a multicast group policy on Router A so that the hosts connected to GigabitEthernet...
Page 91 Configure the IGMP SSM mapping feature on Router D so that the receiver host can receive multicast data only from Source 1 and Source 3. Figure 28 Network diagram Source 2 Source 3 Router B Router C GE1/0/1 GE1/0/3 GE1/0/3 GE1/0/1 GE1/0/2 GE1/0/2...
Page 92 [RouterD] interface gigabitethernet 1/0/3 [RouterD-GigabitEthernet1/0/3] pim sm [RouterD-GigabitEthernet1/0/3] quit # On Router A, enable IP multicast routing. <RouterA> system-view [RouterA] multicast routing [RouterA-mrib] quit # Enable PIM-SM on each interface. [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] pim sm [RouterA-GigabitEthernet1/0/1] quit [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] pim sm [RouterA-GigabitEthernet1/0/2] quit [RouterA] interface gigabitethernet 1/0/3...
Page 93: Igmp Proxying Configuration Example
# Display information about IGMP multicast groups that hosts have dynamically joined on the public network. [RouterD] display igmp group IGMP groups in total: 1 GigabitEthernet1/0/1(133.133.4.2): IGMP groups reported in total: 1 Group address Last reporter Uptime Expires 232.1.1.1 133.133.4.1 00:02:04 # Display PIM routing entries on the public network.
Page 94 Figure 29 Network diagram Proxy Querier Router B Router A GE1/0/1 192.168.1.1/24 PIM-DM GE1/0/1 GE1/0/2 192.168.1.2/24 GE1/0/2 10.110.1.1/24 192.168.2.1/24 Receiver Receiver Host B Host A Host C Configuration procedure Assign an IP address and subnet mask to each interface, as shown in Figure 29.
Page 95: Troubleshooting Igmp
GigabitEthernet1/0/1(192.168.1.2): IGMP proxy group records in total: 1 Group address Member state Expires 224.1.1.1 Delay 00:00:02 Troubleshooting IGMP No membership information on the receiver-side router Symptom When a host sends a report for joining multicast group G, no membership information of multicast group G exists on the router closest to that host.
Page 96: 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 97 this way, the upstream stream node stops forwarding subsequent packets addressed to that multicast group down to this node. NOTE: An (S, G) entry contains a multicast source address S, a multicast group address G, an outgoing interface list, and an incoming interface. A prune process is initiated by a leaf router.
Page 98: Pim-Sm Overview
Figure 31 Assert mechanism Router A Router B Ethernet Assert message Multicast packets Receiver Router C As shown in Figure 31, after Router A and Router B receive an (S, G) packet from the upstream node, they both forward the packet to the local subnet. As a result, the downstream node Router C receives two identical multicast packets.
Page 99 PIM-DM does not require a DR. However, if IGMPv1 runs on any shared-media LAN in a PIM-DM domain, a DR must be elected to act as the IGMPv1 querier for the LAN. For more information about IGMP, see "Configuring IGMP." IMPORTANT: IGMP must be enabled on the device that acts as the receiver-side DR.
Page 100 and the multicast group range to which it is designated. The BSR collects these advertisement messages and organizes the C-RP information into an RP-set, which is a database of mappings between multicast groups and RPs. The BSR encapsulates the RP-set information in the bootstrap messages (BSMs) and floods the BSMs to the entire PIM-SM domain.
Page 101 Anycast RP member address—IP address of each Anycast RP member for  communication among the RP members. 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 34, RP 1, RP 2, and RP 3 are members of an Anycast RP set.
Page 102 RPT building Figure 35 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 35, 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 103 Figure 36 Multicast source registration Host A Source Receiver Host B Server Receiver Join message Register message Host C Multicast packets As shown in Figure 36, 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 104: Bidir-Pim Overview
The RP periodically checks the multicast packet forwarding rate. If the RP finds that the traffic rate exceeds the specified threshold, it sends an (S, G) source-specific join message toward the multicast source. The routers along the path from the RP to the multicast source constitute an SPT.
Page 105 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 a subnet. Only the DFs can forward multicast data to the RP. DF election is not necessary for an RPL.
Page 106 Figure 38 RPT building at the receiver side Source Receiver Host A Server B Source Receiver Host B Server A Receiver Join message Receiver-side RPT Multicast packets Host C As shown in Figure 38, 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 107: Administrative Scoping Overview
Figure 39 RPT building at the multicast source side Source Receiver Host A Server B Source Receiver Host B Server A Receiver Source-side RPT Multicast packets Host C As shown in Figure 39, 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 108 Multicast group ranges that are associated with different admin-scoped zones can have intersections. However, the multicast groups in an admin-scoped zone are valid only within the local zone, and theses multicast groups are regarded as private group addresses. The global-scoped zone maintains a BSR for the multicast groups that do not belong to any admin-scoped zones.
Page 109: Pim-Ssm Overview
Figure 41 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 41, 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 110: Relationship Among Pim Protocols
Figure 42 SPT building in PIM-SSM Host A Source Receiver Host B Server Receiver Subscribe message Multicast packets Host C As shown in Figure 42, 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 111: Pim Support For Vpns
Figure 43 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 112: Pim-Dm Configuration Task List
PIM-DM configuration task list Tasks at a glance (Required.) Enabling PIM-DM (Optional.) Enabling the state refresh feature (Optional.) Configuring state refresh parameters (Optional.) Configuring PIM-DM graft retry timer (Optional.) Configuring common PIM features Configuration prerequisites Before you configure PIM-DM, configure a unicast routing protocol so that all devices in the domain can interoperate at the network layer.
Page 113: Configuring State Refresh Parameters
Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Enable the state refresh By default, the state refresh pim state-refresh-capable feature. feature is enabled. Configuring state refresh parameters The state refresh interval determines the interval at which a router sends state refresh messages. It is configurable.
Page 114: Configuring Pim-Sm
For more information about the configuration of other timers in PIM-DM, see "Configuring common timers." Configuring PIM-SM This section describes how to configure PIM-SM. PIM-SM configuration task list Tasks at a glance Remarks (Required.) Enabling PIM-SM (Required.) Configuring an • Configuring a static RP You must configure a static RP, a •...
Page 115: Configuring An Rp
Step Command Remarks multicast routing Enable IP multicast routing By default, IP multicast routing is vpn-instance and enter MRIB view. disabled. vpn-instance-name ] Return to system view. quit interface interface-type Enter interface view. interface-number Enable PIM-SM. pim sm By default, PIM-SM is disabled. Configuring an RP An RP can provide services for multiple or all multicast groups.
Page 116 The holdtime option in C-RP advertisement messages defines the C-RP lifetime for the advertising C-RP. The BSR starts a holdtime timer for a C-RP after it receives an advertisement message. If the BSR does not receive any advertisement message when the timer expires, it considers the C-RP failed or unreachable.
Page 117: Configuring A Bsr
• As a best practice, configure the loopback interface address of an RP member device as the RP member address. If you add multiple interface addresses of an RP member device to an Anycast RP set, the lowest IP address becomes the RP member address. The rest of the interface addresses become backup RP member addresses.
Page 118 • When C-BSRs connect to other PIM routers through tunnels, static multicast routes must be configured to make sure the next hop to a C-BSR is a tunnel interface. Otherwise, RPF check is affected. For more information about static multicast routes, see "Configuring multicast routing and forwarding."...
Page 119: Configuring Multicast Source Registration
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. Disabling BSM forwarding out of incoming interfaces By default, the device is enabled to forward BSMs out of incoming interfaces.
Page 120: Configuring The Switchover To Spt
To configure multicast source registration: Step Command Remarks Enter system view. system-view vpn-instance Enter PIM view. vpn-instance-name ] default, PIM register Configure a PIM register register-policy ipv4-acl-number policies exist, and all PIM register policy. messages are regarded legal. Configure device By default, the device calculates calculate checksum...
Page 121: Bidir-Pim Configuration Task List
BIDIR-PIM configuration task list Tasks at a glance Remarks (Required.) Enabling BIDIR-PIM (Required.) Configuring an • Configuring a static RP You must configure a static RP, a • Configuring a C-RP C-RP, or both in a BIDIR-PIM • domain. (Optional.) Enabling Auto-RP listening •...
Page 122: Configuring An Rp
Configuring an RP CAUTION: When both PIM-SM and BIDIR-PIM run on the PIM network, do not use the same RP to provide services for PIM-SM and BIDIR-PIM. Otherwise, exceptions might occur to the PIM routing table. An RP can provide services for multiple or all multicast groups. However, only one RP can forward multicast traffic for a multicast group at a time.
Page 123 encapsulates the C-RP information and its own IP address in a BSM, and floods the BSM to all PIM routers in the domain. An advertisement message contains a holdtime option, which defines the C-RP lifetime for the advertising C-RP. After the BSR receives an advertisement message from a C-RP, it starts a timer for the C-RP.
Page 124: Configuring A Bsr
Configuring a BSR You must configure a BSR if C-RPs are configured to dynamically select the RP. You do not need to configure a BSR when you have configured only a static RP but no C-RPs. A BIDIR-PIM domain can have only one BSR, but must have a minimum of one C-BSR. Any router can be configured as a C-BSR.
Page 125 Step Command Remarks By default, no BSR policies exist, (Optional.) Configure a BSR bsr-policy ipv4-acl-number and all bootstrap messages are policy. regarded legal. Configuring a PIM domain border A PIM domain border determines the transmission boundary of bootstrap messages. Bootstrap messages cannot cross the domain border in either direction.
Page 126: Configuring Pim-Ssm
Step Command Remarks Enter system view. system-view vpn-instance Enter PIM view. vpn-instance-name ] Disable the device from By default, the device is enabled sending BSMs undo bsm-reflection enable to forward BSMs out of incoming incoming interfaces. interfaces. Configuring PIM-SSM PIM-SSM requires IGMPv3 support. Enable IGMPv3 on PIM routers that connect to multicast receivers.
Page 127: 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 128: Configuring A Multicast Source Policy
• Configure PIM-DM or PIM-SM. Configuring a multicast source policy This feature enables the device to filter multicast data by using an ACL that specifies the multicast sources and the optional groups. It filters not only data packets but also register messages with multicast data encapsulated.
Page 129 The LAN delay defines the PIM message propagation delay. The override interval defines a period for a router to override a prune message. If the propagation delay or override interval on different PIM routers on a shared-media LAN are different, the largest ones apply. On the shared-media LAN, the propagation delay and override interval are used as follows: If a router receives a prune message on its upstream interface, it means that there are ...
Page 130: Configuring Common Pim Timers
Step Command Remarks default setting Set the neighbor lifetime. pim hello-option holdtime time seconds. message hello-option lan-delay default setting propagation delay. delay milliseconds. hello-option default setting 2500 Set the override interval. override-interval interval milliseconds. hello-option By default, neighbor tracking is Enable neighbor tracking.
Page 131: Setting The Maximum Size Of Each Join Or Prune Message
Step Command Remarks The default setting is 60 seconds. Set the join/prune interval. timer join-prune interval This configuration takes effect after the current interval ends. Set the joined/pruned state default setting holdtime join-prune time holdtime. seconds. Set the multicast source default setting source-lifetime time...
Page 132: Enabling Pim Passive Mode
Enabling PIM NSR The following matrix shows the feature and hardware compatibility: Hardware PIM NSR compatibility MSR954 (JH296A/JH297A/JH298A/JH299A/JH373A) MSR958 (JH300A/JH301A) MSR1002-4/1003-8S MSR2003 MSR2004-24/2004-48 MSR3012/3024/3044/3064 MSR4060/4080 This feature enables PIM to back up protocol state information and data, including PIM neighbor...
Page 133: Enabling Snmp Notifications For Pim
immediately takes over when the active process fails. Use this feature to avoid route flapping and forwarding interruption for PIM when an active/standby switchover occurs. To enable PIM NSR: Step Command Remarks Enter system view. system-view Enable PIM NSR. pim non-stop-routing By default, PIM NSR is disabled.
Page 134: Displaying And Maintaining Pim
Displaying and maintaining PIM Execute display commands in any view and reset commands in user view. Task Command Display register-tunnel interface display interface [ register-tunnel [ interface-number ] ] [ brief information. [ description | down ] ] Display BSR information in the display pim [ vpn-instance vpn-instance-name ] bsr-info PIM-SM domain.
Page 135 Figure 44 Network diagram Receiver Host A Router A GE1/0/1 Host B Receiver GE1/0/1 GE1/0/3 GE1/0/2 GE1/0/1 Source Host C Router D Router B 10.110.5.100/24 GE1/0/1 PIM-DM Router C Host D Table 8 Interface and IP address assignment Device Interface IP address Device Interface...
Page 136 # Enable IP multicast routing, IGMP, and PIM-DM on Router B and Router C in the same way Router A is configured. (Details not shown.) # On Router D, enable IP multicast routing, and enable PIM-DM on each interface. <RouterD> system-view [RouterD] multicast routing [RouterD-mrib] quit [RouterD] interface gigabitethernet 1/0/1...
Page 137: Pim-Sm Non-Scoped Zone Configuration Example
Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet1/0/1 Protocol: igmp, UpTime: 00:04:25, Expires: - (10.110.5.100, 225.1.1.1) Protocol: pim-dm, Flag: ACT UpTime: 00:06:14 Upstream interface: GigabitEthernet1/0/2 Upstream neighbor: 192.168.1.2 RPF prime neighbor: 192.168.1.2 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet1/0/1 Protocol: pim-dm, UpTime: 00:04:25, Expires: - # Display the PIM routing table on Router D.
Page 138 • IGMPv2 runs between Router A and N1, and between Router B, Router C, and N2. Figure 45 Network diagram Receiver Host A Router A GE1/0/1 GE1/0/3 Host B GE1/0/3 Receiver GE1/0/1 GE1/0/4 GE1/0/2 GE1/0/1 GE1/0/3 GE1/0/2 Source GE1/0/1 Router D Router B Router E Host C...
Page 139 [RouterA-GigabitEthernet1/0/1] igmp enable [RouterA-GigabitEthernet1/0/1] quit # Enable PIM-SM on the other interfaces. [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] pim sm [RouterA-GigabitEthernet1/0/2] quit [RouterA] interface gigabitethernet 1/0/3 [RouterA-GigabitEthernet1/0/3] pim sm [RouterA-GigabitEthernet1/0/3] quit # Enable IP multicast routing, IGMP and PIM-SM on Router B and Router C in the same way Router A is configured.
Page 140: Pim-Sm Admin-Scoped Zone Configuration Example
Uptime: 00:11:18 # Display BSR information on Router E. [RouterE] display pim bsr-info Scope: non-scoped State: Elected Bootstrap timer: 00:01:44 Elected BSR address: 192.168.9.2 Priority: 64 Hash mask length: 30 Uptime: 00:11:18 Candidate BSR address: 192.168.9.2 Priority: 64 Hash mask length: 30 # Display RP information on Router A.
Page 141 Figure 46 Network diagram Admin-scope 1 Receiver GE1/0/1 Router G Host A Source 1 GE1/0/2 Source 3 GE1/0/1 GE1/0/1 GE1/0/1 GE1/0/2 GE1/0/4 GE1/0/3 Router F GE1/0/2 GE1/0/2 Router B Router A Router C Router I Router H GE1/0/3 GE1/0/2 GE1/0/2 GE1/0/3 Router D GE1/0/1...
Page 142 Configuration procedure Assign an IP address and subnet mask to each interface, as shown in Figure 46. (Details not shown.) Configure OSPF on all routers in the PIM-SM domain. (Details not shown.) Enable IP multicast routing, IGMP, and PIM-SM: # On Router A, enable IP multicast routing. <RouterA>...
Page 143 <RouterC> system-view [RouterC] interface gigabitethernet 1/0/4 [RouterC-GigabitEthernet1/0/4] multicast boundary 239.0.0.0 8 [RouterC-GigabitEthernet1/0/4] quit [RouterC] interface gigabitethernet 1/0/5 [RouterC-GigabitEthernet1/0/5] multicast boundary 239.0.0.0 8 [RouterC-GigabitEthernet1/0/5] quit # On Router D, configure GigabitEthernet 1/0/3 as the boundary of admin-scoped zone 2. <RouterD> system-view [RouterD] interface gigabitethernet 1/0/3 [RouterD-GigabitEthernet1/0/3] multicast boundary 239.0.0.0 8 [RouterD-GigabitEthernet1/0/3] quit...
Page 144 Uptime: 00:01:45 Scope: 239.0.0.0/8 State: Elected Bootstrap timer: 00:00:06 Elected BSR address: 10.110.1.2 Priority: 64 Hash mask length: 30 Uptime: 00:04:54 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...
Page 145: Bidir-Pim Configuration Example
Group/MaskLen: 224.0.0.0/4 RP address Priority HoldTime Uptime Expires 10.110.9.1 00:03:39 00:01:51 Scope: 239.0.0.0/8 Group/MaskLen: 239.0.0.0/8 RP address Priority HoldTime Uptime Expires 10.110.1.2 (local) 00:07:44 00:01:51 # Display RP information on Router D. [RouterD] display pim rp-info BSR RP information: Scope: non-scoped Group/MaskLen: 224.0.0.0/4 RP address Priority...
Page 146 Figure 47 Network diagram Receiver 1 Receiver 2 Loop0 Router B GE1/0/1 GE1/0/3 GE1/0/1 Router C Host A GE1/0/2 GE1/0/2 Host B BIDIR-PIM Source 1 Source 2 GE1/0/2 GE1/0/3 GE1/0/1 GE1/0/2 Router A Router D Table 11 Interface and IP address assignment Device Interface IP address...
Page 147 [RouterA-pim] quit # On Router B, enable IP multicast routing. <RouterB> system-view [RouterB] multicast routing [RouterB-mrib] quit # Enable IGMP on the receiver-side interface (GigabitEthernet 1/0/1). [RouterB] interface gigabitethernet 1/0/1 [RouterB-GigabitEthernet1/0/1] igmp enable [RouterB-GigabitEthernet1/0/1] quit # Enable PIM-SM on the other interfaces. [RouterB] interface gigabitethernet 1/0/2 [RouterB-GigabitEthernet1/0/2] pim sm [RouterB-GigabitEthernet1/0/2] quit...
Page 148 [RouterD] interface gigabitethernet 1/0/3 [RouterD-GigabitEthernet1/0/3] pim sm [RouterD-GigabitEthernet1/0/3] quit # Enable BIDIR-PIM. [RouterD] pim [RouterD-pim] bidir-pim enable [RouterD-pim] quit On Router C, configure GigabitEthernet 1/0/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...
Page 149: Pim-Ssm Configuration Example
Flags: 0x0 Uptime: 00:08:32 RPF interface: GigabitEthernet1/0/2 List of 1 DF interfaces: 1: GigabitEthernet1/0/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: GigabitEthernet1/0/3...
Page 150 • The SSM group range is 232.1.1.0/24. • IGMPv3 runs between Router A and N1, and between Router B, Router C, and N2. Figure 48 Network diagram Receiver Host A Router A GE1/0/1 GE1/0/3 Host B GE1/0/3 Receiver GE1/0/1 GE1/0/4 GE1/0/2 GE1/0/1 GE1/0/3...
Page 151 [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] igmp enable [RouterA-GigabitEthernet1/0/1] igmp version 3 [RouterA-GigabitEthernet1/0/1] quit # Enable PIM-SM on the other interfaces. [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] pim sm [RouterA-GigabitEthernet1/0/2] quit [RouterA] interface gigabitethernet 1/0/3 [RouterA-GigabitEthernet1/0/3] pim sm [RouterA-GigabitEthernet1/0/3] quit # Enable IP multicast routing, IGMP, and PIM-SM on Router B and Router C in the same way Router A is configured.
Page 152: Troubleshooting Pim
Protocol: igmp, UpTime: 00:13:25, Expires: 00:03:25 # Display PIM routing entries on Router D. [RouterD] display pim routing-table Total 0 (*, G) entry; 1 (S, G) entry (10.110.5.100, 232.1.1.1) Protocol: pim-ssm, Flag: LOC UpTime: 00:12:05 Upstream interface: GigabitEthernet1/0/1 Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1...
Page 153: Multicast Data Is Abnormally Terminated On An Intermediate Router
Multicast data is abnormally terminated on an intermediate router Symptom An intermediate router can receive multicast data successfully, but the data cannot reach the last-hop router. An interface on the intermediate router receives multicast data but does not create an (S, G) entry in the PIM routing table. Solution To resolve the problem: Use display current-configuration to verify the multicast forwarding boundary settings.
Page 154 If the problem persists, contact Hewlett Packard Enterprise Support.
Page 155: Configuring Msdp
Configuring MSDP Overview Multicast Source Discovery Protocol (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 156 As shown in Figure 49, 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 closest to the multicast source, such as RP 1. The ...
Page 157 Figure 50 Inter-domain multicast delivery through MSDP Receiver DR 2 MSDP peers Multicast packets SA message RP 2 Join message PIM-SM 2 Register message DR 1 Source PIM-SM 4 RP 1 RP 3 PIM-SM 1 PIM-SM 3 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 data within a register message.
Page 158 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. In inter-domain multicasting using MSDP, once an RP gets information about a multicast source in another PIM-SM domain, it no longer relies on RPs in other PIM-SM domains.
Page 159 Figure 51 Anycast RP through MSDP RP 1 RP 2 Router A Router B PIM-SM Source Receiver MSDP peers SA message The following describes how Anycast RP through MSDP is implemented: a. After receiving the multicast data from Source, the source-side DR registers with the closest RP (RP 1 in this example).
Page 160: Msdp Support For Vpns
Figure 52 MSDP peer-RPF forwarding Source RP 1 RP 5 RP 9 RP 8 AS 1 AS 5 Mesh group AS 3 RP 2 RP 3 AS 2 MSDP peers RP 4 RP 6 RP 7 Static RPF peers AS 4 SA message The process of peer-RPF forwarding is as follows: RP 1 creates an SA message and forwards it to its peer RP 2.
Page 161: 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 Tasks at a glance Configuring basic MSDP features: • (Required.) Enabling MSDP • (Required.) Specifying an MSDP peer •...
Page 162: Specifying An Msdp Peer
Specifying an MSDP peer An MSDP peering relationship is identified by an address pair (the addresses of the local MSDP peer and the remote MSDP peer). To create an MSDP peering connection, you must perform the following operation on both devices that are a pair of MSDP peers. If an interface of the router is shared by an MSDP peer and a BGP or MBGP peer at the same time, As a best practice, specify an MSDP peer by using the IP address of the BGP or MBGP peer.
Page 163: Configuring A Description For An Msdp Peer
Configuring a description for an MSDP peer This feature helps administrators easily distinguish an MSDP peer from other MSDP peers. To configure a description for an MSDP peer: Step Command Remarks Enter system view. system-view msdp vpn-instance Enter MSDP view. vpn-instance-name ] Configure a description for peer peer-address description...
Page 164: Configuring Sa Message-Related Parameters
• 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 change the MSDP connection retry interval to adjust the interval between MSDP peering connection attempts.
Page 165: Configuring The Originating Rp Of Sa Messages
information to the remote RP through SA messages. Then, the remote RP sends join messages to the source-side DR and builds an SPT. Because the (S, G) entries have timed out, remote receivers can never receive the multicast data from the multicast source. To avoid this problem, you can enable the source-side RP to encapsulate multicast data in SA messages.
Page 166: Configuring Sa Message Policies
Step Command Remarks Enter system view. system-view msdp vpn-instance Enter MSDP view. vpn-instance-name ] By default, after receiving a new join message, a device Enable the device to send SA peer peer-address does not send an SA request request messages to an request-sa-enable message to any MSDP peer.
Page 167: Configuring The Sa Cache Mechanism
Configuring the SA cache mechanism The SA cache mechanism enables the router to locally cache (S, G) entries contained in SA messages. It reduces the time for obtaining multicast source information, but increases memory occupation. With the SA cache mechanism enabled, when the router receives a new (*, G) join message, it searches its SA message cache first.
Page 168: Msdp Configuration Examples
MSDP configuration examples This section provides examples of configuring MSDP on routers. PIM-SM inter-domain multicast configuration Network requirements As shown in Figure • OSPF runs within AS 100 and AS 200. BGP runs between the two ASs. • Each PIM-SM domain has a minimum of one multicast source or receiver. Set up MSDP peering relationships between the RPs in the PIM-SM domains to share multicast source information among the PIM-SM domains.
Page 169 Device Interface IP address Device Interface IP address Router C Loop0 2.2.2.2/32 Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 53. (Details not shown.) Configure OSPF on the routers in the ASs. (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.
Page 170 [RouterB-bgp-ipv4] peer 192.168.1.2 enable [RouterB-bgp-ipv4] quit [RouterB-bgp] quit # On Router C, configure an EBGP peer and redistribute OSPF routes. [RouterC] bgp 200 [RouterC-bgp] router-id 2.2.2.2 [RouterC-bgp] peer 192.168.1.1 as-number 100 [RouterC-bgp] address-family ipv4 [RouterC-bgp-ipv4] import-route ospf 1 [RouterB-bgp-ipv4] peer 192.168.1.1 enable [RouterC-bgp-ipv4] quit [RouterC-bgp] quit # Redistribute BGP routing information into OSPF on Router B.
Page 171 BGP local router ID: 2.2.2.2 Local AS number: 200 Total number of peers: 1 Peers in established state: 1 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...
Page 172: Inter-As Multicast Configuration By Leveraging Static Rpf Peers
Peer address State Up/Down time SA count Reset count 192.168.3.1 Established 01:12:19 # 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: GigabitEthernet1/0/2 (192.168.1.1) Received/sent messages: 16/16...
Page 173 • The network has two ASs: AS 100 and AS 200. OSPF runs within each AS. BGP runs between the two ASs. • PIM-SM 1 belongs to AS 100, and PIM-SM 2 and PIM-SM 3 belong to AS 200. Each PIM-SM domain has a minimum of one multicast source or receiver.
Page 174 Device Interface IP address Device Interface IP address Router C GE1/0/3 10.110.4.1/24 Configuration procedure Assign an IP address and subnet mask to each interface according to Table 14. (Details not shown.) Configure OSPF on the routers in the ASs. (Details not shown.) Enable IP multicast routing, PIM-SM, and IGMP, and configure PIM-SM domain borders: # On Router C, enable IP multicast routing.
Page 175 [RouterB-bgp-ipv4] quit [RouterB-bgp] quit # On Router D, configure an EBGP peer, and redistribute OSPF routing information. [RouterD] bgp 200 [RouterD-bgp] router-id 2.2.2.2 [RouterD-bgp] peer 10.110.3.1 as-number 100 [RouterD-bgp] address-family ipv4 unicast [RouterD-bgp-ipv4] peer 10.110.3.1 enable [RouterD-bgp-ipv4] import-route ospf 1 [RouterD-bgp-ipv4] quit [RouterD-bgp] quit # On Router C, configure an EBGP peer, and redistribute OSPF routing information.
Page 176 [RouterA] ip prefix-list list-dg permit 10.110.0.0 16 greater-equal 16 less-equal 32 [RouterA] msdp [RouterA-msdp] peer 10.110.3.2 connect-interface gigabitethernet 1/0/1 [RouterA-msdp] peer 10.110.6.2 connect-interface gigabitethernet 1/0/2 [RouterA-msdp] static-rpf-peer 10.110.3.2 rp-policy list-dg [RouterA-msdp] static-rpf-peer 10.110.6.2 rp-policy list-dg [RouterA-msdp] quit # On Router D, configure Router A as the MSDP peer and static RPF peer. [RouterD] ip prefix-list list-a permit 10.110.0.0 16 greater-equal 16 less-equal 32 [RouterD] msdp [RouterD-msdp] peer 10.110.1.1 connect-interface gigabitethernet 1/0/2...
Page 177: Anycast Rp Configuration
# Verify that receivers in PIM-SM 1 and PIM-SM 3 can receive the multicast data from Source 1 and Source 2 to a multicast group. (Details not shown.) Anycast RP configuration Network requirements As shown in Figure 55, OSPF runs within the domain to provide unicast routes. Configure the Anycast RP application so that the receiver-side DRs and the source-side DRs can initiate a join process to their respective RPs that are topologically closest to them.
Page 178 Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 55. (Details not shown.) Configure OSPF on the routers in the PIM-SM domain. (Details not shown.) Enable IP multicast routing, IGMP, and PIM-SM: # On Router B, enable IP multicast routing. <RouterB>...
Page 179 [RouterD-msdp] originating-rp loopback 0 [RouterD-msdp] peer 1.1.1.1 connect-interface loopback 0 [RouterD-msdp] quit Verifying the configuration # Display brief information about MSDP peers on Router B. [RouterB] display msdp brief Configured Established Listen Connect Shutdown Disabled Peer address State Up/Down time SA count Reset count 2.2.2.2...
Page 180: Sa Message Filtering Configuration
Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet1/0/1 Protocol: pim-sm, UpTime: - , Expires: The output shows that Router B now acts as the RP for Source 1 and Host A. # Send an IGMP leave message from Host A to leave multicast group 225.1.1.1. (Details not shown.), # Send an IGMP report from Host B to join multicast group 225.1.1.1.
Page 181 • Set up an MSDP peering relationship between Router A and Router C and between Router C and Router D. • Source 1 sends multicast data to multicast groups 225.1.1.0/30 and 226.1.1.0/30. Source 2 sends multicast data to multicast group 227.1.1.0/30. Configure SA message policies to meet the following requirements: •...
Page 182 # On Router A, enable IP multicast routing. <RouterA> system-view [RouterA] multicast routing [RouterA-mrib] quit # Enable IGMP on the receiver-side interface (GigabitEthernet 1/0/1). [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] igmp enable [RouterA-GigabitEthernet1/0/1] quit # Enable PIM-SM on the other interfaces. [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] pim sm [RouterA-GigabitEthernet1/0/2] quit...
Page 183 [RouterC-msdp] peer 10.110.5.2 connect-interface gigabitethernet 1/0/2 [RouterC-msdp] quit # Configure an MSDP peer on Router D. [RouterD] msdp [RouterD-msdp] peer 10.110.5.1 connect-interface gigabitethernet 1/0/3 [RouterD-msdp] quit Configure SA message policies: # Configure an SA accepting and forwarding policy on Router C so that Router C will not forward SA messages for (Source 1, 225.1.1.0/30) to Router D.
Page 184: Troubleshooting Msdp
10.110.3.100 226.1.1.2 1.1.1.1 00:32:53 00:05:07 10.110.3.100 226.1.1.3 1.1.1.1 00:32:53 00:05:07 Troubleshooting MSDP This section describes common MSDP problems and how to troubleshoot them. MSDP peers stay in disabled state Symptom The configured MSDP peers stay in disabled state. Solution To resolve the problem: Use the display ip routing-table command to verify that the unicast route between the routers is reachable.
Page 185 Verify the configuration of the originating-rp command. In the Anycast RP application environment, use the originating-rp command to configure the RP address in the SA messages, which must be the local interface address. Verify that the C-BSR address is different from the Anycast RP address. If the problem persists, contact Hewlett Packard Enterprise Support.
Page 186: Configuring Multicast Vpn
Configuring multicast VPN Overview Multicast VPN implements multicast delivery in VPNs. A VPN contains multiple customer network sites and the public network provided by the network service provider. The sites communicate through the public network. As shown in Figure • VPN A contains Site 1, Site 3, and Site 5.
Page 187: Md Vpn Overview
Figure 58 Multicast in multiple VPN instances PE 1" PE 2" Site 3 MD A Site 1 Site 5 PE 3" VPN instance A PE 1' PE 2' PE 3' Public instance Site 4 PE 1"' MD B PE 2"' Site 2 Site 6 PE 3"'...
Page 188 Table 17 Basic MD VPN concepts Concept Description An MD is a set of PE devices that are in the same VPN instance. Multicast domain (MD) Each MD uniquely corresponds to a VPN instance. An MDT is a multicast distribution tree constructed by all PE Multicast distribution tree (MDT) devices in the same VPN.
Page 189 a. The local PE device encapsulates a VPN multicast packet into a public network multicast packet. b. The encapsulated multicast packet is sent by the PE device and travels over the public network. c. After receiving the multicast packet, the remote PE device decapsulates the multicast packet to get the original VPN multicast packet.
Page 190: Protocols And Standards
b. After a data-delay period has passed, an MDT switchover process starts. All VPN multicast packets that have entered the public network through that PE device are not encapsulated with the default-group address. They are encapsulated into public network multicast packets with the data-group address.
Page 191: How Md Vpn Works
How MD VPN works This section describes default-MDT establishment, multicast traffic delivery based on the default-MDT, and inter-AS MD VPN implementation. For a VPN instance, multicast data transmission on the public network is transparent. The VPN data is exchanged between the MTIs of the local PE and the remote PE. This implements the seamless transmission of the VPN data over the public network.
Page 192 Default-MDT establishment in a PIM-SM network Figure 62 Default-MDT establishment in a PIM-SM network BGP: 11.1.3.1/24 PE 3 Default-group: 239.1.1.1 Public instance BGP peers RPT (*, 239.1.1.1) SPT (11.1.1.1, 239.1.1.1) SPT (11.1.2.1, 239.1.1.1) SPT (11.1.3.1, 239.1.1.1) PE 1 PE 2 BGP: 11.1.1.1/24 BGP: 11.1.2.1/24 As shown in...
Page 193 Default-MDT establishment in a BIDIR-PIM network Figure 63 Default-MDT establishment in a BIDIR-PIM network BGP: 11.1.3.1/24 PE 3 Default-Group: 239.1.1.1 Public instance BGP peers Receiver-side RPT (*, 239.1.1.1) Source-side RPT (*, 239.1.1.1) PE 1 PE 2 BGP: 11.1.1.1/24 BGP: 11.1.2.1/24 As shown in Figure 63, BIDIR-PIM runs on the network, and all the PE devices support VPN instance...
Page 194: Default-Mdt-Based Delivery
Default-MDT establishment in a PIM-SSM network Figure 64 Default-MDT establishment in a PIM-SSM network BGP: 11.1.3.1/24 PE 3 Default-Group: 232.1.1.1 Public instance BGP peers SPT (11.1.1.1, 232.1.1.1) SPT (11.1.2.1, 232.1.1.1) SPT (11.1.3.1, 232.1.1.1) PE 1 PE 2 BGP: 11.1.1.1/24 BGP: 11.1.2.1/24 As shown in Figure 64, PIM-SSM runs on the network, and all the PE devices support VPN instance...
Page 195 A flood-prune process (in PIM-DM) or a join process (in PIM-SSM) is initiated across the  public network to establish an SPT across the public network. • If the VPN network runs PIM-SM: Hello packets are forwarded through MTI interfaces to establish PIM neighboring ...
Page 196 After receiving the join message from CE 2, the VPN instance on PE 2 creates a state entry (*, 225.1.1.1) and specifies the MTI interface as the upstream interface. The VPN instance on PE 2 considers the join message to have been sent out of the MTI interface, because step 3 is transparent to the VPN instance.
Page 197: Mdt Switchover
Figure 66 Multicast data packet delivery 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 Public instance BGP peers S: 192.1.1.1/24 G: 225.1.1.1 VPN instance packets (192.1.1.1, 225.1.1.1) Default-group: 239.1.1.1 Public instance packets (11.1.1.1, 239.1.1.1) A VPN multicast data packet is delivered across the public network as follows:...
Page 198: Inter-As Md Vpn
connect VPN multicast receivers and multicast sources. When specific network criteria are met, a switchover from the default-MDT to the data-MDT occurs to forward VPN multicast traffic to receivers. The process of default-MDT to data-MDT switchover is as follows: The source-side PE device (PE 1, for example) periodically examines the forwarding rate of the VPN multicast traffic.
Page 199 • Multihop EBGP redistribution of labeled VPN-IPv4 routes between PE routers—PEs advertise VPN-IPv4 routes to each other through MP-EBGP. This solution is also called inter-AS option C. For more information about the three inter-AS VPN solutions, see "Configuring MPLS L3VPN." Based on these solutions, there are three ways to implement inter-AS MD VPN: •...
Page 200 When a device receives the join message with the RPF vector, it first checks whether the RPF vector is its own IP address. If so, the device removes the RPF vector, and sends the message to its upstream neighbor according to the route to the remote PE device. Otherwise, it keeps the RPF vector, looks up the route to the RPF vector, and sends the message to the next hop of the route.
Page 201: M6Vpe
When PE 1 joins the SPT rooted at PE 1, PE 2 also initiates a join process to the SPT rooted at PE 1. A MDT is established when the two SPTs are finished. MD VPN inter-AS option C As shown in Figure •...
Page 202: Multicast Vpn Configuration Task List
Figure 70 M6VPE network Public network PE 1 PE 2 CE 1 CE 2 VPN A VPN A Site 1 Site 2 IPv6 multicast traffic forwarding over the IPv4 public network is as follows: CE 1 forwards an IPv6 multicast packet for VPN instance VPN A to PE 1. PE 1 encapsulates the IPv6 multicast packet with an IPv4 packet header and transmits the IPv4 packet in the IPv4 backbone network.
Page 203: Configuring Md Vpn
Configuring MD VPN This section describes how to configure MD VPN. Configuration prerequisites Before you configure MD VPN, complete the following tasks: • Configure a unicast routing protocol on the public network. • Configure MPLS L3VPN on the public network. •...
Page 204: Creating An Md For A Vpn Instance
Creating an MD for a VPN instance To provide multicast services for a VPN instance, you must create an MD for the VPN instance on PE devices that belong to the VPN instance. After the MD is created, the system automatically creates MTIs and binds them with the VPN instance.
Page 205: Specifying The Md Source Interface
Step Command Remarks Enter system view. system-view multicast-domain vpn-instance Enter MD view. vpn-instance-name • Enter IPv4 address family view: address-family ipv4 Enter MD address family • view. Enter IPv6 address family view: address-family ipv6 default, default-group Specify the default-group. default-group group-address exists.
Page 206: Configuring The Rpf Vector Feature
• Likewise, a backward switchover does not take place immediately after the multicast traffic rate drops below the MDT switchover threshold. It takes place after a data-holddown period, during which the traffic rate must stay lower than the switchover threshold. Configuration restrictions and guidelines When you configure MDT switchover parameters, follow these restrictions and guidelines: •...
Page 207: Enabling Data-Group Reuse Logging
Step Command Remarks Enable vector By default, the RPF vector feature rpf proxy vector feature. is disabled. Enabling RPF vector compatibility This feature enables the device to work with other manufacturers' products on RPF vectors for interoperability purposes. You must enable this feature on all HPE devices on the public network. To enable RPF vector compatibility: Step Command...
Page 208: Configuring Bgp Mdt Peers Or Peer Groups
• Configure basic BGP functions on the public network. • Configure PIM-SSM on the public network. • Determine the IP addresses of the MDT peers. • Determine the cluster IDs of the route reflectors. Configuring BGP MDT peers or peer groups Configure a BGP MDT peer or peer group on a PE router in BGP IPv4 MDT address family view.
Page 209: Displaying And Maintaining Multicast Vpn
to improve network reliability. To avoid routing loops, make sure the route reflectors in a cluster have the same cluster ID. Perform this task on PE devices. To configure a BGP MDT route reflector: Step Command Remarks Enter system view. system-view instance as-number...
Page 210: Multicast Vpn Configuration Examples
Task Command display multicast-domain vpn-instance Display information about vpn-instance-name data-groups that are sent in the data-group send [ group group-address | reuse interval | MD of a VPN instance for IPv4 vpn-source-address mask mask-length mask multicast transmission. vpn-group-address [ mask { mask-length | mask } ] ] * display multicast-domain vpn-instance vpn-instance-name ipv6 Display information...
Page 211 Item Network requirements • Enable IP multicast routing on the P router. • Enable IP multicast routing on the public network instance on PE 1, PE 2, and PE 3. • Enable IP multicast routing for VPN instance a on PE 1, PE 2, and PE IP multicast routing •...
Page 212 Device Interface IP address Device Interface IP address — 10.110.1.2/24 PE 3 GE1/0/3 10.110.6.1/24 — 10.110.9.2/24 PE 3 Loop1 1.1.1.3/32 — 10.110.10.2/24 PE 3 Loop2 33.33.33.33/32 — 10.110.11.2/24 CE a1 GE1/0/1 10.110.7.1/24 GE1/0/1 192.168.6.2/24 CE a1 GE1/0/2 10.110.2.2/24 GE1/0/2 192.168.7.2/24 CE a2 GE1/0/1 10.110.9.1/24...
Page 213 # Specify the default-group, the MD source interface, and the data-group range for VPN instance a. [PE1-md-a-ipv4] default-group 239.1.1.1 [PE1-md-a-ipv4] source loopback 1 [PE1-md-a-ipv4] data-group 225.2.2.0 28 [PE1-md-a-ipv4] quit [PE1-md-a] quit # Assign an IP address to GigabitEthernet 1/0/1. [PE1] interface gigabitethernet 1/0/1 [PE1-GigabitEthernet1/0/1] ip address 192.168.6.1 24 # Enable PIM-SM, MPLS, and IPv4 LDP on GigabitEthernet 1/0/1.
Page 214 [PE1–bgp-default-vpnv4] quit [PE1–bgp-default] quit # Configure OSPF. [PE1] ospf 1 [PE1-ospf-1] area 0.0.0.0 [PE1-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0 [PE1-ospf-1-area-0.0.0.0] network 192.168.6.0 0.0.0.255 [PE1-ospf-1-area-0.0.0.0] quit [PE1-ospf-1] quit # Configure RIP. [PE1] rip 2 vpn-instance a [PE1-rip-2] network 10.110.1.0 0.0.0.255 [PE1-rip-2] network 10.110.2.0 0.0.0.255 [PE1-rip-2] import-route bgp [PE1-rip-2] return Configure PE 2:...
Page 215 [PE2-vpn-instance-a] route-distinguisher 100:1 [PE2-vpn-instance-a] vpn-target 100:1 export-extcommunity [PE2-vpn-instance-a] vpn-target 100:1 import-extcommunity [PE2-vpn-instance-a] quit # Enable IP multicast routing for VPN instance a. [PE2] multicast routing vpn-instance a [PE2-mrib-a] quit # Create an MD for VPN instance a and enter its view. [PE2] multicast-domain vpn-instance a # Create an MD IPv4 address family for VPN instance a and enter its view.
Page 216 [PE2-bgp-default] peer vpn-g connect-interface loopback 1 [PE2-bgp-default] peer 1.1.1.1 group vpn-g [PE2-bgp-default] peer 1.1.1.3 group vpn-g [PE2–bgp-default] ip vpn-instance a [PE2-bgp-default-a] address-family ipv4 [PE2-bgp-default-ipv4-a] import-route rip 2 [PE2-bgp-default-ipv4-a] import-route direct [PE2-bgp-default-ipv4-a] quit [PE2-bgp-default-a] quit [PE2–bgp-default] ip vpn-instance b [PE2-bgp-default-b] address-family ipv4 [PE2-bgp-default-ipv4-b] import-route rip 3 [PE2-bgp-default-ipv4-b] import-route direct [PE2-bgp-default-ipv4-b] quit...
Page 217 [PE3-vpn-instance-a] vpn-target 100:1 export-extcommunity [PE3-vpn-instance-a] vpn-target 100:1 import-extcommunity [PE3-vpn-instance-a] quit # Enable IP multicast routing for VPN instance a. [PE3] multicast routing vpn-instance a [PE3-mrib-a] quit # Create an MD for VPN instance a and enter its view. [PE3] multicast-domain vpn-instance a # Create an MD IPv4 address family for VPN instance a and enter its view.
Page 218 # Assign an IP address to GigabitEthernet 1/0/2, and enable PIM-SM on the interface. [PE3-GigabitEthernet1/0/2] ip address 10.110.5.1 24 [PE3-GigabitEthernet1/0/2] pim sm [PE3-GigabitEthernet1/0/2] quit # Associate GigabitEthernet 1/0/3 with VPN instance b. [PE3] interface gigabitethernet 1/0/3 [PE3-GigabitEthernet1/0/3] ip binding vpn-instance b # Assign an IP address to GigabitEthernet 1/0/3, and enable PIM-SM on the interface.
Page 219 [PE3–bgp-default-vpnv4] quit [PE3–bgp-default] 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 192.168.8.0 0.0.0.255 [PE3-ospf-1-area-0.0.0.0] quit [PE3-ospf-1] quit # Configure RIP. [PE3] rip 2 vpn-instance a [PE3-rip-2] network 10.110.5.0 0.0.0.255 [PE3-rip-2] import-route bgp [PE3-rip-2] quit [PE3] rip 3 vpn-instance b [PE3-rip-3] network 10.110.6.0 0.0.0.255...
Page 220 # Enable PIM-SM, MPLS, and IPv4 LDP on GigabitEthernet 1/0/3. [P-GigabitEthernet1/0/3] pim sm [P-GigabitEthernet1/0/3] mpls enable [P-GigabitEthernet1/0/3] mpls ldp enable [P-GigabitEthernet1/0/3] quit # Assign an IP address to Loopback 1, and enable PIM-SM on the interface. [P] interface loopback 1 [P-LoopBack1] ip address 2.2.2.2 32 [P-LoopBack1] pim sm [P-LoopBack1] quit...
Page 221 [CEb1] interface gigabitethernet 1/0/1 [CEb1-GigabitEthernet1/0/1] ip address 10.110.8.1 24 [CEb1-GigabitEthernet1/0/1] pim sm [CEb1-GigabitEthernet1/0/1] quit # Assign an IP address to GigabitEthernet 1/0/2, and enable PIM-SM on the interface. [CEb1] interface gigabitethernet 1/0/2 [CEb1-GigabitEthernet1/0/2] ip address 10.110.3.2 24 [CEb1-GigabitEthernet1/0/2] pim sm [CEb1-GigabitEthernet1/0/2] quit # Configure RIP.
Page 222 [CEa2-rip-2] network 10.110.12.0 0.0.0.255 [CEa2-rip-2] network 22.22.22.22 0.0.0.0 Configure CE a3: # Enable IP multicast routing. <CEa3> system-view [CEa3] multicast routing [CEa3-mrib] quit # Assign an IP address to GigabitEthernet 1/0/1, and enable IGMP on the interface. [CEa3] interface gigabitethernet 1/0/1 [CEa3-GigabitEthernet1/0/1] ip address 10.110.10.1 24 [CEa3-GigabitEthernet1/0/1] igmp enable [CEa3-GigabitEthernet1/0/1] quit...
Page 223: Intra-As M6Vpe Configuration Example
Verifying the configuration # Display information about the local default-group for IPv4 multicast transmission in each VPN instance on PE 1. [PE1] display multicast-domain default-group local MD local default-group information: Group address Source address Interface VPN instance 239.1.1.1 1.1.1.1 MTunnel0 # Display information about the local default-group for IPv4 multicast transmission in each VPN instance on PE 2.
Page 224 Item Network requirements • Enable IP multicast routing on P. • Enable IP multicast routing for the public network on PE 1, PE 2, and PE 3. • Enable IPv6 multicast routing for VPN instance a on PE 1, PE 2, and IP multicast routing and IPv6 PE 3.
Page 225 Table 19 Interface and IP address assignment IPv4/IPv6 Device Interface Device Interface IPv4/IPv6 address address — 10:110:7::2/64 PE 3 GE1/0/1 192.168.8.1/24 — 10:110:8::2/64 PE 3 GE1/0/2 10:110:5::1/64 — 10:110:1::2/64 PE 3 GE1/0/3 10:110:6::1/64 — 10:110:9::2/64 PE 3 Loop1 1.1.1.3/32 — 10:110:10::2/64 PE 3 Loop2...
Page 226 # Create an MD for VPN instance a. [PE1] multicast-domain vpn-instance a # Create an MD IPv6 address family for VPN instance a and enter its view. [PE1-md-a] address-family ipv6 # Specify the default group, the MD source interface, and the data-group range for VPN instance a.
Page 227 [PE1-bgp-default] peer 1.1.1.2 group vpn-g [PE1-bgp-default] peer 1.1.1.3 group vpn-g [PE1–bgp-default] ip vpn-instance a [PE1-bgp-default-a] address-family ipv6 [PE1-bgp-default-ipv6-a] import-route ospfv3 2 [PE1-bgp-default-ipv6-a] import-route direct [PE1-bgp-default-ipv6-a] quit [PE1-bgp-default-a] quit [PE1–bgp-default] address-family vpnv6 [PE1–bgp-default-vpnv6] peer vpn-g enable [PE1–bgp-default-vpnv6] quit [PE1–bgp-default] quit # Configure OSPF. [PE1] ospf 1 [PE1-ospf-1] area 0.0.0.0 [PE1-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0...
Page 228 # Create an MD IPv6 address family for VPN instance b. [PE2-md-b] address-family ipv6 # Specify the default-group, the MD source interface, and the data-group range for VPN instance b. [PE2-md-b-ipv6] default-group 239.2.2.2 [PE2-md-b-ipv6] source loopback 1 [PE2-md-b-ipv6] data-group 225.4.4.0 28 [PE2-md-b-ipv6] quit [PE2-md-b] quit # Create a VPN instance named a, and configure the RD and route targets for the VPN...
Page 229 # Associate GigabitEthernet 1/0/3 with VPN instance a, and assign an IPv6 address to the interface. [PE2] interface gigabitethernet 1/0/3 [PE2-GigabitEthernet1/0/3] ip binding vpn-instance a [PE2-GigabitEthernet1/0/3] ipv6 address 10:110:4::1 64 # Enable IPv6 PIM-SM on GigabitEthernet 1/0/3, and configure the interface to run OSPFv3 process 2 in Area 0.
Page 230 [PE2-ospfv3-2] import-route direct [PE2-ospfv3-2] area 0 [PE2-ospfv3-2-area-0.0.0.0] quit [PE2] ospfv3 3 vpn-instance b [PE2-ospfv3-3] router-id 3.3.3.3 [PE2-ospfv3-3] import-route bgp4+ [PE2-ospfv3-3] import-route direct [PE2-ospfv3-3] area 0 [PE2-ospfv3-3-area-0.0.0.0] quit [PE2-ospfv3-3] quit Configure PE 3: # Configure a global RD, and enable IP multicast routing on the public network. <PE3>...
Page 231 # Enable IPv6 multicast routing for VPN instance b. [PE3] ipv6 multicast routing vpn-instance b [PE3-mrib6-b] quit # Create an MD for VPN instance b. [PE3] multicast-domain vpn-instance b # Create an MD IPv6 address family for VPN instance b. [PE3-md-b] address-family ipv6 # Specify the default-group, the MD source interface, and the data-group range for VPN instance b.
Page 232 [PE3] interface loopback 2 [PE3-LoopBack2] ipv6 binding vpn-instance b [PE3-LoopBack2] ip address 33:33:33::33 128 # Enable IPv6 PIM-SM on Loopback 2, and configure the interface to run OSPFv3 process 3 in Area 0. [PE3-LoopBack2] ipv6 pim sm [PE3-LoopBack2] ospfv3 3 area 0.0.0.0 [PE3-LoopBack2] quit # Configure Loopback 2 as a C-BSR and a C-RP.
Page 233: [P] Interface Loopback 1
[PE3-ospfv3-2-area-0.0.0.0] quit [PE3-ospfv3-2] quit [PE3] ospfv3 3 vpn-instance b [PE3-ospfv3-3] router-id 5.5.5.5 [PE3-ospfv3-3] import-route bgp4+ [PE3-ospfv3-3] import-route direct [PE3-ospfv3-3] area 0 [PE3-ospfv3-3-area-0.0.0.0] quit [PE3-ospfv3-3] quit Configure P: # Enable IP multicast routing on the public network. <P> system-view [P] multicast routing [P-mrib] quit # Configure an LSR ID, and enable LDP globally.
Page 234: [P] Ospf 1
# Configure Loopback 1 as a C-BSR and a C-RP. [P] pim [P-pim] c-bsr 2.2.2.2 [P-pim] c-rp 2.2.2.2 [P-pim] quit # Configure OSPF. [P] ospf 1 [P-ospf-1] area 0.0.0.0 [P-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0 [P-ospf-1-area-0.0.0.0] network 192.168.6.0 0.0.0.255 [P-ospf-1-area-0.0.0.0] network 192.168.7.0 0.0.0.255 [P-ospf-1-area-0.0.0.0] network 192.168.8.0 0.0.0.255 Configure CE a1: # Enable IPv6 multicast routing.
Page 235 [CEb1-GigabitEthernet1/0/1] ipv6 pim sm [CEb1-GigabitEthernet1/0/1] ospfv3 3 area 0.0.0.0 [CEb1-GigabitEthernet1/0/1] quit # Assign an IPv6 address to GigabitEthernet 1/0/2. [CEb1] interface gigabitethernet 1/0/2 [CEb1-GigabitEthernet1/0/2] ipv6 address 10:110:3::2 64 # Enable IPv6 PIM-SM on GigabitEthernet 1/0/2, and configure the interface to run OSPFv3 process 3 in Area 0.
Page 236 # Configure Loopback 1 to run OSPFv3 process 2 in Area 0, and enable IPv6 PIM-SM on the interface. [CEa2-LoopBack1] ospfv3 2 area 0.0.0.0 [CEa2-LoopBack1] ipv6 pim sm [CEa2-LoopBack1] quit # Configure Loopback 1 as a C-BSR and a C-RP. [CEa2] ipv6 pim [CEa2-pim6] c-bsr 22:22:22::22 [CEa2-pim6] c-rp 22:22:22::22...
Page 237 [CEa3-ospfv3-2-area-0.0.0.0] quit Configure CE b2: # Enable IPv6 multicast routing. <CEb2> system-view [CEb2] ipv6 multicast routing [CEb2-mrib6] quit # Assign an IPv6 address to GigabitEthernet 1/0/1. [CEb2] interface gigabitethernet 1/0/1 [CEb2-GigabitEthernet1/0/1] ipv6 address 10:110:11::1 64 # Configure GigabitEthernet 1/0/1 to run OSPFv3 process 3 in Area 0, and enable MLD on the interface.
Page 238: Md Vpn Inter-As Option C Configuration Example
MD VPN inter-AS option C configuration example Network requirements As shown in Figure 73, configure MD VPN inter-AS option C to meet the following requirements: Item Network requirements • In VPN instance a, S 1 is a multicast source, and R 2 is a receiver. •...
Page 239 Figure 73 Network diagram Loop0 Loop0 CE a1 CE b2 GE1/0/1 GE1/0/1 VPN b VPN a GE1/0/1 GE1/0/2 GE1/0/1 GE1/0/1 GE1/0/2 GE1/0/1 PE 1 PE 4 PE 2 PE 3 ASBR ASBR AS 100 AS 200 GE1/0/1 GE1/0/1 CE a2 CE b1 VPN b VPN a...
Page 240 [PE1] router id 1.1.1.1 [PE1] multicast routing [PE1-mrib] quit # Configure an LSR ID, and enable LDP globally. [PE1] mpls lsr-id 1.1.1.1 [PE1] mpls ldp [PE1-ldp] quit # Create a VPN instance named a, and configure an RD and route targets for the VPN instance. [PE1] ip vpn-instance a [PE1-vpn-instance-a] route-distinguisher 100:1 [PE1-vpn-instance-a] vpn-target 100:1 export-extcommunity...
Page 241 [PE1] interface gigabitethernet 1/0/1 [PE1-GigabitEthernet1/0/1] ip address 10.10.1.1 24 # Enable PIM-SM, MPLS, and IPv4 LDP on GigabitEthernet 1/0/1. [PE1-GigabitEthernet1/0/1] pim sm [PE1-GigabitEthernet1/0/1] mpls enable [PE1-GigabitEthernet1/0/1] mpls ldp enable [PE1-GigabitEthernet1/0/1] quit # Associate GigabitEthernet 1/0/2 with VPN instance a. [PE1] interface gigabitethernet 1/0/2 [PE1-GigabitEthernet1/0/2] ip binding vpn-instance a # Assign an IP address to GigabitEthernet 1/0/2, and enable PIM-SM on the interface.
Page 242 [PE1–bgp-default] address-family ipv4 [PE1-bgp-default-ipv4] peer pe1-pe2 enable [PE1-bgp-default-ipv4] peer pe1-pe2 label-route-capability [PE1-bgp-default-ipv4] quit [PE1–bgp-default] address-family vpnv4 [PE1–bgp-default-vpnv4] peer pe1-pe4 enable [PE1–bgp-default-vpnv4] quit [PE1–bgp-default] quit # Configure OSPF. [PE1] ospf 1 [PE1-ospf-1] area 0.0.0.0 [PE1-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0 [PE1-ospf-1-area-0.0.0.0] network 10.10.1.0 0.0.0.255 [PE1-ospf-1-area-0.0.0.0] quit [PE1-ospf-1] quit [PE1] ospf 2 vpn-instance a...
Page 243 # Enable PIM-SM and MPLS on GigabitEthernet 1/0/2. [PE2-GigabitEthernet1/0/2] pim sm [PE2-GigabitEthernet1/0/2] mpls enable [PE2-GigabitEthernet1/0/2] quit # Assign an IP address to Loopback 1, and enable PIM-SM on the interface. [PE2] interface loopback 1 [PE2-LoopBack1] ip address 1.1.1.2 32 [PE2-LoopBack1] pim sm [PE2-LoopBack1] quit # Assign an IP address to Loopback 2, and enable PIM-SM on the interface.
Page 244 # 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 11.11.11.11 0.0.0.0 [PE2-ospf-1-area-0.0.0.0] network 10.10.1.0 0.0.0.255 [PE2-ospf-1-area-0.0.0.0] quit [PE2-ospf-1] quit Configure PE 3: # Configure a global router ID, and enable IP multicast routing on the public network. <PE3>...
Page 245 [PE3-pim] quit # Configure GigabitEthernet 1/0/2 as a PIM-SM domain border. [PE3] interface gigabitethernet 1/0/2 [PE3-GigabitEthernet1/0/2] pim bsr-boundary [PE3-GigabitEthernet1/0/2] quit # Establish an MSDP peering relationship. [PE3] msdp [PE3-msdp] encap-data-enable [PE3-msdp] peer 1.1.1.2 connect-interface loopback 1 # Configure a static route. [PE3] ip route-static 1.1.1.2 32 gigabitethernet 1/0/2 192.168.1.1 # Configure BGP.
Page 246 # Create a VPN instance named a, and configure an RD and route targets for the VPN instance. [PE4] ip vpn-instance a [PE4-vpn-instance-a] route-distinguisher 100:1 [PE4-vpn-instance-a] vpn-target 100:1 export-extcommunity [PE4-vpn-instance-a] vpn-target 100:1 import-extcommunity [PE4-vpn-instance-a] quit # Enable IP multicast routing for VPN instance a. [PE4] multicast routing vpn-instance a [PE4-mrib-a] quit # Create an MD for VPN instance a.
Page 247 # Associate GigabitEthernet 1/0/2 with VPN instance a. [PE4] interface gigabitethernet 1/0/2 [PE4-GigabitEthernet1/0/2] ip binding vpn-instance a # Assign an IP address to GigabitEthernet 1/0/2, and enable PIM-SM on the interface. [PE4-GigabitEthernet1/0/2] ip address 10.11.3.1 24 [PE4-GigabitEthernet1/0/2] pim sm [PE4-GigabitEthernet1/0/2] quit # Associate GigabitEthernet 1/0/3 with VPN instance b.
Page 248: Configure Ce A1: # Enable Ip Multicast Routing
[PE4–bgp-default] quit # Configure OSPF. [PE4] ospf 1 [PE4-ospf-1] area 0.0.0.0 [PE4-ospf-1-area-0.0.0.0] network 1.1.1.4 0.0.0.0 [PE4-ospf-1-area-0.0.0.0] network 10.10.2.0 0.0.0.255 [PE4-ospf-1-area-0.0.0.0] quit [PE4-ospf-1] quit [PE4] ospf 2 vpn-instance a [PE4-ospf-2] import-route bgp [PE4-ospf-2] area 0.0.0.0 [PE4-ospf-2-area-0.0.0.0] network 10.11.3.0 0.0.0.255 [PE4-ospf-2-area-0.0.0.0] quit [PE4-ospf-2] quit [PE4] ospf 3 vpn-instance b [PE4-ospf-3] import-route bgp...
Page 249 [CEa1-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0 [CEa1-ospf-1-area-0.0.0.0] network 10.11.1.0 0.0.0.255 [CEa1-ospf-1-area-0.0.0.0] network 10.11.5.0 0.0.0.255 [CEa1-ospf-1-area-0.0.0.0] quit [CEa1-ospf-1] quit Configure CE b1: # Enable IP multicast routing. <CEb1> system-view [CEb1] multicast routing [CEb1-mrib] quit # Assign an IP address to GigabitEthernet 1/0/1, and enable PIM-SM on the interface. [CEb1] interface gigabitethernet 1/0/1 [CEb1-GigabitEthernet1/0/1] ip address 10.11.6.1 24 [CEb1-GigabitEthernet1/0/1] pim sm...
Page 250 [CEa2-ospf-1-area-0.0.0.0] quit [CEa2-ospf-1] quit Configure CE b2: # Enable IP multicast routing. <CEb2> system-view [CEb2] multicast routing [CEb2-mrib] quit # Assign an IP address to GigabitEthernet 1/0/1, and enable IGMP on the interface. [CEb2] interface gigabitethernet 1/0/1 [CEb2-GigabitEthernet1/0/1] ip address 10.11.8.1 24 [CEb2-GigabitEthernet1/0/1] igmp enable [CEb2-GigabitEthernet1/0/1] quit # Assign an IP address to GigabitEthernet 1/0/2, and enable PIM-SM on the interface.
Page 251: Md Vpn Inter-As Option B Configuration Example
Group address Source address Interface VPN instance 239.1.1.1 1.1.1.4 MTunnel0 239.4.4.4 1.1.1.4 MTunnel1 MD VPN inter-AS option B configuration example Network requirements As shown in Figure 74, configure MD VPN inter-AS option B to meet the following requirements: Item Network requirements •...
Page 252 Item Network requirements RPF vector Enable the RPF vector feature on PE 1 and PE 4. Figure 74 Network diagram CE a1 CE b2 GE1/0/1 GE1/0/1 VPN a VPN b Loop1 Loop1 Loop1 Loop1 GE1/0/1 GE1/0/2 GE1/0/2 GE1/0/1 GE1/0/1 GE1/0/1 GE1/0/2 GE1/0/1 GE1/0/2...
Page 253 Configuration procedure Configure PE 1: # Configure a global router ID, and enable IP multicast routing on the public network. <PE1> system-view [PE1] router id 1.1.1.1 [PE1] multicast routing [PE1-mrib] quit # Configure an LSR ID, and enable LDP globally. [PE1] mpls lsr-id 1.1.1.1 [PE1] mpls ldp [PE1-ldp] quit...
Page 254 # Specify the default-group, the MD source interface, and the data-group range for VPN instance b. [PE1-md-b-ipv4] default-group 232.3.3.3 [PE1-md-b-ivp4] source loopback 1 [PE1-md-b-ipv4] data-group 232.4.4.0 28 [PE1-md-b-ipv4] quit [PE1-md-b] quit # Assign an IP address to GigabitEthernet 1/0/1. [PE1] interface gigabitethernet 1/0/1 [PE1-GigabitEthernet1/0/1] ip address 10.1.1.1 24 # Enable PIM-SM, MPLS, and IPv4 LDP on GigabitEthernet 1/0/1.
Page 255 [PE1-bgp-default-ipv4-b] quit [PE1-bgp-default-b] quit [PE1–bgp-default] address-family vpnv4 [PE1–bgp-default-vpnv4] peer 2.2.2.2 enable [PE1–bgp-default-vpnv4] quit [PE1-bgp-default] address-family ipv4 mdt [PE1-bgp-default-mdt] peer 2.2.2.2 enable [PE1-bgp-default-mdt] quit [PE1–bgp-default] quit # Configure OSPF. [PE1] ospf 1 [PE1-ospf-1] area 0.0.0.0 [PE1-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0 [PE1-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [PE1-ospf-1-area-0.0.0.0] quit [PE1-ospf-1] quit # Configure OSPF.
Page 256 # Enable PIM-SM and MPLS on GigabitEthernet 1/0/2. [PE2-GigabitEthernet1/0/2] pim sm [PE2-GigabitEthernet1/0/2] mpls enable [PE2-GigabitEthernet1/0/2] quit # Assign an IP address to Loopback 1, and enable PIM-SM on the interface. [PE2] interface loopback 1 [PE2-LoopBack1] ip address 2.2.2.2 32 [PE2-LoopBack1] pim sm [PE2-LoopBack1] quit # Configure BGP.
Page 257 [PE3-GigabitEthernet1/0/1] quit # Assign an IP address to GigabitEthernet 1/0/2. [PE3] interface gigabitethernet 1/0/2 [PE3-GigabitEthernet1/0/2] ip address 10.3.1.2 24 # Enable PIM-SM and MPLS on GigabitEthernet 1/0/2. [PE3-GigabitEthernet1/0/2] pim sm [PE3-GigabitEthernet1/0/2] mpls enable [PE3-GigabitEthernet1/0/2] quit # Assign an IP address to Loopback 1, and enable PIM-SM on the interface. [PE3] interface loopback 1 [PE3-LoopBack1] ip address 3.3.3.3 32 [PE3-LoopBack1] pim sm...
Page 258 [PE4-vpn-instance-a] route-distinguisher 100:1 [PE4-vpn-instance-a] vpn-target 100:1 export-extcommunity [PE4-vpn-instance-a] vpn-target 100:1 import-extcommunity [PE4-vpn-instance-a] quit # Enable IP multicast routing and RPF vector for VPN instance a. [PE4] multicast routing vpn-instance a [PE4-mrib-a] rpf proxy vector [PE4-mrib-a] quit # Create an MD for VPN instance a. [PE4] multicast-domain vpn-instance a # Create an MD IPv4 address family for VPN instance a.
Page 259 [PE4-GigabitEthernet1/0/1] quit # Associate GigabitEthernet 1/0/2 with VPN instance a. [PE4] interface gigabitethernet 1/0/2 [PE4-GigabitEthernet1/0/2] ip binding vpn-instance a # Assign an IP address to GigabitEthernet 1/0/2, and enable PIM-SM on the interface. [PE4-GigabitEthernet1/0/2] ip address 11.3.1.1 24 [PE4-GigabitEthernet1/0/2] pim sm [PE4-GigabitEthernet1/0/2] quit # Associate GigabitEthernet 1/0/3 with VPN instance b.
Page 260 [PE4-ospf-1-area-0.0.0.0] quit [PE4-ospf-1] quit [PE4] ospf 2 vpn-instance a [PE4-ospf-2] area 0.0.0.0 [PE4-ospf-2-area-0.0.0.0] network 11.3.1.0 0.0.0.255 [PE4-ospf-2-area-0.0.0.0] quit [PE4-ospf-2] quit [PE4] ospf 3 vpn-instance b [PE4-ospf-3] area 0.0.0.0 [PE4-ospf-3-area-0.0.0.0] network 11.4.1.0 0.0.0.255 [PE4-ospf-3-area-0.0.0.0] quit [PE4-ospf-3] quit Configure P 1: # Enable IP multicast routing on the public network. <P1>...
Page 261 [P1-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255 Configure P 2: # Enable IP multicast routing on the public network. <P2> system-view [P2] multicast routing [P2-mrib] quit # Configure an LSR ID, and enable LDP globally. [P2] mpls lsr-id 6.6.6.6 [P2] mpls ldp [P2-ldp] quit # Assign an IP address to GigabitEthernet 1/0/1.
Page 262 # Assign an IP address to GigabitEthernet 1/0/2, and enable PIM-SM on the interface. [CEa1] interface gigabitethernet 1/0/2 [CEa1-GigabitEthernet1/0/2] ip address 11.1.1.2 24 [CEa1-GigabitEthernet1/0/2] pim sm [CEa1-GigabitEthernet1/0/2] quit # Configure GigabitEthernet 1/0/2 as a C-BSR and a C-RP. [CEa1] pim [CEa1-pim] c-bsr 11.1.1.2 [CEa1-pim] c-rp 11.1.1.2 [CEa1-pim] quit...
Page 263 [CEa2] multicast routing [CEa2-mrib] quit # Assign an IP address to GigabitEthernet 1/0/1, and enable IGMP on the interface. [CEa2] interface gigabitethernet 1/0/1 [CEa2-GigabitEthernet1/0/1] ip address 12.3.1.1 24 [CEa2-GigabitEthernet1/0/1] igmp enable [CEa2-GigabitEthernet1/0/1] quit # Assign an IP address to GigabitEthernet 1/0/2, and enable PIM-SM on the interface. [CEa2] interface gigabitethernet 1/0/2 [CEa2-GigabitEthernet1/0/2] ip address 11.3.1.2 24 [CEa2-GigabitEthernet1/0/2] pim sm...
Page 264: Troubleshooting Md Vpn
232.1.1.1 1.1.1.1 MTunnel0 232.3.3.3 1.1.1.1 MTunnel1 # Display information about the remote default-group for IPv4 multicast transmission in each VPN instance on PE 1. [PE1] display multicast-domain default-group remote MD remote default-group information: Group address Source address Next hop VPN instance 232.1.1.1 4.4.4.4 2.2.2.2...
Page 265: An Mvrf Cannot Be Created
If the problem persists, contact Hewlett Packard Enterprise Support. An MVRF cannot be created Symptom A VPN instance cannot create an MVRF correctly. Solution To resolve the problem: Use the display pim bsr-info command to verify that the BSR information exists on the public network and VPN instance.
Page 266: Configuring Mld Snooping
Configuring MLD snooping Overview MLD snooping runs on a Layer 2 device as an IPv6 multicast constraining mechanism to improve multicast forwarding efficiency. It creates Layer 2 multicast forwarding entries from MLD messages that are exchanged between the hosts and the router. As shown in Figure 75, when MLD snooping is not enabled, the Layer 2 switch floods IPv6 multicast...
Page 267 Figure 76 MLD snooping ports Receiver Router A Switch A GE1/0/1 GE1/0/2 Host A GE1/0/3 Host B Receiver GE1/0/1 Source GE1/0/2 Host C Switch B Router port Member port IPv6 multicast packets Host D Router ports On an MLD snooping Layer 2 device, the ports toward Layer 3 multicast devices are called router ports.
Page 268: How Mld Snooping Works
How MLD snooping works The ports in this section are dynamic ports. For information about how to configure and remove static ports, see "Configuring static ports." MLD messages include general query, MLD report, and done message. An MLD snooping-enabled Layer 2 device performs differently depending on the MLD message types. General query The MLD querier periodically sends MLD general queries to all hosts and routers on the local subnet to check for the existence of IPv6 multicast group members.
Page 269: Protocols And Standards
This feature is supported only on the following ports: • Layer 2 Ethernet ports on the following modules: HMIM-8GSW.  HMIM-24GSW.  HMIM-24GSW-PoE.  SIC-4GSW.  SIC-9FSW.  SIC-9FSW-PoE.  • Fixed Layer 2 Ethernet ports on the following routers: MSR1002-4/1003-8S.  MSR2004-24/2004-48.  MSR954 (JH296A/JH297A/JH298A/JH299A/JH373A). ...
Page 270: Command And Hardware Compatibility
MSR958 (JH300A/JH301A).  Command and hardware compatibility Commands and descriptions for centralized devices apply to the following routers: • MSR1002-4/1003-8S. • MSR2003. • MSR2004-24/2004-48. • MSR3012/3024/3044/3064. • MSR954 (JH296A/JH297A/JH298A/JH299A/JH373A). • MSR958 (JH300A/JH301A). Commands and descriptions for distributed devices apply to the following routers: •...
Page 271: Configuring Basic Mld Snooping Features
interfaces do not take part in aggregation calculations. The configuration made on a member port of the aggregate group takes effect after the port leaves the aggregate group. Configuring basic MLD snooping features Before you configure basic MLD snooping features, complete the following tasks: •...
Page 272: Setting The Maximum Number Of Mld Snooping Forwarding Entries
• MLDv2 snooping can process MLDv1 and MLDv2 messages. If you change MLDv2 snooping to MLDv1 snooping, the system does the following: • Clears all MLD snooping forwarding entries that are dynamically created. • Keeps static MLDv2 snooping forwarding entries (*, G). •...
Page 273: Setting The Mld Last Listener Query Interval
Setting the MLD last listener query interval A receiver host starts a report delay timer for an IPv6 multicast group when it receives an MLD multicast-address-specific query for the group. This timer is set to a random value in the range of 0 to the maximum response time advertised in the query.
Page 274: Configuring Static Ports
• If a dynamic router port receives an IPv6 PIMv2 hello message, the aging timer for the port is specified by the hello message. In this case, the mld-snooping router-aging-time command does not take effect on the port. • MLD multicast-address-specific queries originated by the Layer 2 device trigger the adjustment of aging timers of dynamic member ports.
Page 275: Configuring A Port As A Simulated Member Host
Step Command Remarks • Configure the port as a static member port: mld-snooping static-group ipv6-group-address source-ip By default, a port is not a static ipv6-source-address ] vlan Configure the port as a static member port or a static router vlan-id port.
Page 276: Disabling A Port From Becoming A Dynamic Router Port
Step Command Remarks Enter system view. system-view Enter MLD-snooping view. mld-snooping Enable fast-leave By default, fast-leave processing fast-leave [ vlan vlan-list ] processing globally. is disabled globally. To enable fast-leave processing on a port: Step Command Remarks Enter system view. system-view Enter Layer...
Page 277: Configuration Prerequisites
Configuration prerequisites Before you configure the MLD snooping querier, complete the following tasks: • Enable MLD snooping for the VLAN. • Determine the MLD general query interval. • Determine the maximum response time for MLD general queries. Enabling the MLD snooping querier This feature enables the device to periodically send MLD general queries to establish and maintain multicast forwarding entries at the data link Layer.
Page 278: Configuring Parameters For Mld Messages
Step Command Remarks Enter MLD-snooping view. mld-snooping Set the maximum response time general max-response-time seconds The default setting is 10 seconds. queries. Configuring parameters for MLD general queries and responses in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view.
Page 279: Setting The 802.1P Priority For Mld Messages
Step Command Remarks By default, the source IPv6 address of MLD general queries is the IPv6 link-local address of Configure the source IPv6 mld-snooping general-query the current VLAN interface. If the address for MLD general source-ip ipv6-address current VLAN interface does not queries.
Page 280: Configuring Mld Snooping Policies
Setting the 802.1p priority for MLD messages globally Step Command Remarks Enter system view. system-view Enter MLD-snooping view. mld-snooping Set the 802.1p priority for By default, the 802.1p priority for dot1p-priority priority MLD messages. MLD messages is not set. Setting the 802.1p priority for MLD messages in a VLAN Step Command Remarks...
Page 281: Enabling Ipv6 Multicast Source Port Filtering
Enabling IPv6 multicast source port filtering This feature is supported only on the following ports: • Layer 2 Ethernet ports on HMIM-8GSW, HMIM-24GSW, and HMIM-24GSW-PoE. • Fixed Layer 2 Ethernet ports on the following routers: MSR1002-4/1003-8S.  MSR2004-24/2004-48.  MSR954 (JH296A/JH297A/JH298A/JH299A/JH373A). ...
Page 282: Enabling Mld Report Suppression
HMIM-24GSW.  HMIM-24GSW-PoE.  SIC-4GSW.  • Fixed Layer 2 Ethernet ports on the following routers: MSR1002-4/1003-8S.  MSR2004-24/2004-48.  MSR954 (JH296A/JH297A/JH298A/JH299A/JH373A).  MSR958 (JH300A/JH301A).  This feature enables the device to drop all unknown IPv6 multicast data. Unknown IPv6 multicast data refers to IPv6 multicast data for which no forwarding entries exist in the MLD snooping forwarding table.
Page 283: Enabling The Ipv6 Multicast Group Replacement Feature
Configuration restrictions and guidelines When you set the maximum number of IPv6 multicast groups on a port, follow these restrictions and guidelines: • This configuration takes effect only on the IPv6 multicast groups that the port joins dynamically. • If the number of IPv6 multicast groups on a port exceeds the limit, the system removes all the forwarding entries related to that port.
Page 284: Displaying And Maintaining Mld Snooping
Step Command Remarks Enter Layer Ethernet interface interface-type interface view or Layer 2 interface-number aggregate interface view. Enable the IPv6 multicast By default, the IPv6 multicast mld-snooping overflow-replace group replacement feature group replacement feature is [ vlan vlan-list ] on the port. disabled on a port.
Page 285 Task Command Display information about Layer 2 IPv6 multicast groups display ipv6 l2-multicast mac [ mac-address ] [ vlan vlan-id ] [ slot (distributed devices in standalone slot-number ] mode/centralized devices in IRF mode). Display information about Layer 2 display ipv6 l2-multicast mac [ mac-address ] [ vlan vlan-id ] IPv6 multicast groups...
Page 286: Mld Snooping Configuration Examples
Task Command Display static router port information (distributed devices in standalone display mld-snooping static-router-port [ vlan vlan-id ] [ slot mode/centralized devices in IRF slot-number ] mode). display mld-snooping static-router-port [ vlan vlan-id ] [ chassis Display static router port information (distributed devices in IRF mode).
Page 287 Figure 77 Network diagram Receiver Host A Source Receiver GE1/0/4 GE1/0/2 GE1/0/1 GE1/0/1 GE1/0/3 1::2/64 2001::1/64 Switch A Host B GE1/0/2 1::1/64 Router A MLD querier Host C VLAN 100 Configuration procedure Assign an IPv6 address and prefix length to each interface, as shown in Figure 77.
Page 288: Static Port Configuration Example
# Configure an IPv6 multicast group policy so that hosts in VLAN 100 can join only IPv6 multicast group FF1E::101. [SwitchA] acl ipv6 basic 2001 [SwitchA-acl-ipv6-basic-2001] rule permit source ff1e::101 128 [SwitchA-acl-ipv6-basic-2001] quit [SwitchA] mld-snooping [SwitchA–mld-snooping] group-policy 2001 vlan 100 [SwitchA–mld-snooping] quit # Configure GigabitEthernet 1/0/3 and GigabitEthernet 1/0/4 as simulated member hosts to join IPv6 multicast group FF1E::101.
Page 289 along the path of Switch A—Switch B—Switch C. When this path is blocked, a minimum of one MLD query-response cycle must be completed before IPv6 multicast data flows to the receivers along the path of Switch A—Switch C. In this case, the multicast delivery is interrupted during the process.
Page 290 [SwitchA-mld-snooping] quit # Create VLAN 100, and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/3 # Enable MLD snooping for VLAN 100. [SwitchA-vlan100] mld-snooping enable [SwitchA-vlan100] quit # Configure GigabitEthernet 1/0/3 as a static router port. [SwitchA] interface gigabitethernet 1/0/3 [SwitchA-GigabitEthernet1/0/3] mld-snooping static-router-port vlan 100 [SwitchA-GigabitEthernet1/0/3] quit...
Page 291: Mld Snooping Querier Configuration Example
Router slots (0 in total): Router ports (1 in total): GE1/0/3 The output shows that GigabitEthernet 1/0/3 on Switch A has become a static router port. # Display static MLD snooping group entries in VLAN 100 on Switch C. [SwitchC] display mld-snooping static-group vlan 100 Total 1 entries).
Page 292 Figure 79 Network diagram Source 1 Source 2 VLAN 100 1::10/64 1::20/64 Receiver Receiver GE1/0/2 GE1/0/2 GE1/0/1 GE1/0/3 GE1/0/3 GE1/0/1 Host A GE1/0/4 Host B Switch A Switch B Querier Receiver Receiver GE1/0/2 GE1/0/1 GE1/0/2 GE1/0/3 GE1/0/1 Host D Host C Switch D Switch C Configuration procedure...
Page 293 Configure Switch C: # Enable MLD snooping globally. <SwitchC> system-view [SwitchC] mld-snooping [SwitchC-mld-snooping] quit # Create VLAN 100, and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3 to the VLAN. [SwitchC] vlan 100 [SwitchC-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/3 # Enable MLD snooping, and enable dropping unknown IPv6 multicast data for VLAN 100. [SwitchC-vlan100] mld-snooping enable [SwitchC-vlan100] mld-snooping drop-unknown [SwitchC-vlan100] quit...
Page 294: Troubleshooting Mld Snooping
Troubleshooting MLD snooping Layer 2 multicast forwarding cannot function Symptom Layer 2 multicast forwarding cannot function through MLD snooping. Solution To resolve the problem: Use the display mld-snooping command to display MLD snooping status. If MLD snooping is not enabled, use the mld-snooping command in system view to enable MLD snooping globally.
Page 295: Configuring Ipv6 Multicast Routing And Forwarding
Configuring IPv6 multicast routing and forwarding Overview IPv6 multicast routing and forwarding uses the following tables: • IPv6 multicast protocols' routing tables, such as the IPv6 PIM routing table. • General IPv6 multicast routing table that summarizes the multicast routing information generated by different IPv6 multicast routing protocols.
Page 296 packet as the incoming interface of the (S, G) entry. After the router receives another (S, G) packet, it looks up its IPv6 multicast forwarding table for a matching (S, G) entry: • If no match is found, the router first determines the RPF route back to the packet source. Then, it creates a forwarding entry with the RPF interface as the incoming interface and performs one of the following tasks: If the receiving interface is the RPF interface, the RPF check succeeds and the router...
Page 297: Ipv6 Multicast Forwarding Across Ipv6 Unicast Subnets
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. Command and hardware compatibility Commands and descriptions for centralized devices apply to the following routers: • MSR1002-4/1003-8S. • MSR2003. • MSR2004-24/2004-48.
Page 298: Enabling Ipv6 Multicast Routing
Tasks at a glance (Optional.) Configuring IPv6 multicast routing and forwarding: • (Optional.) Specifying the longest prefix match principle • (Optional.) Configuring IPv6 multicast load splitting • (Optional.) Configuring an IPv6 multicast forwarding boundary • (Optional.) Configuring static IPv6 multicast MAC address entries •...
Page 299: Configuring An Ipv6 Multicast Forwarding Boundary
You do not need to enable IPv6 multicast routing before this configuration. To configure IPv6 multicast load splitting: Step Command Remarks Enter system view. system-view ipv6 multicast routing Enter IPv6 MRIB view. vpn-instance vpn-instance-name ] By default, IPv6 multicast load splitting is disabled.
Page 300: Enabling Ipv6 Multicast Forwarding Between Sub-Vlans Of A Super Vlan
Step Command Remarks Enter system view. system-view Configure static IPv6 mac-address multicast default, static IPv6 multicast address mac-address interface multicast MAC address entries entry. interface-list vlan vlan-id exist. To configure a static IPv6 multicast MAC address entry in interface view: Step Command Remarks...
Page 301: 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 mac-address [ mac-address [ vlan vlan-id ] | Display static IPv6...
Page 302 Task Command display ipv6 multicast [ vpn-instance vpn-instance-name ] forwarding-table [ ipv6-source-address [ prefix-length ] | ipv6-group-address [ prefix-length ] | incoming-interface Display IPv6 multicast forwarding entries (centralized devices in standalone mode). interface-type interface-number outgoing-interface { exclude | include | match } interface-type interface-number | statistics ] * display ipv6 multicast [ vpn-instance vpn-instance-name ] forwarding-table [ ipv6-source-address [ prefix-length ] |...
Page 303: Configuration Examples
Task Command reset ipv6 multicast [ vpn-instance vpn-instance-name ] routing-table { { ipv6-source-address [ prefix-length ] | Clear IPv6 multicast routing entries. ipv6-group-address [ prefix-length ] | incoming-interface interface-type interface-number } * | all } NOTE: • When you clear an IPv6 multicast routing entry, the associated IPv6 multicast forwarding entry is also cleared.
Page 304 # Assign an IPv6 address to interface Tunnel 0 on Router A, and specify its source and destination addresses. [RouterA-Tunnel0] ipv6 address 5001::1 64 [RouterA-Tunnel0] source 2001::1 [RouterA-Tunnel0] destination 3001::2 [RouterA-Tunnel0] quit # Create an IPv6 GRE tunnel interface Tunnel 0 on Router C. <RouterC>...
Page 305: Ipv6 Multicast Forwarding Over Advpn Tunnel Interfaces
# Send IPv6 multicast data from Source to IPv6 multicast group FF1E::101. (Details not shown.) # Display PIM routing entries on Router C. [RouterC] display ipv6 pim routing-table Total 1 (*, G) entry; 1 (S, G) entry (*, FF1E::101) Protocol: pim-dm, Flag: WC UpTime: 00:04:25 Upstream interface: NULL Upstream neighbor: NULL...
Page 306 Figure 83 Network diagram Source GE1/0/2 Hub 1 Hub 2 GE1/0/1 Server IPv6 network Spoke 1 Spoke 2 GE1/0/2 GE1/0/2 Hub-to-Hub static tunnel Hub-to-Spoke static tunnel Receiver Site 1 Site 2 Table 22 Interface and IPv6 address assignment Device Interface IPv6 address Device Interface...
Page 307 # Configure the VAM server not to authenticate VAM clients. [Server-vam-server-domain-abc] authentication-method none # Enable the VAM server. [Server-vam-server-domain-abc] server enable # Create hub group 0. [Server-vam-server-domain-abc] hub-group 0 # Specify private IPv6 addresses for hubs in hub group 0. [Server-vam-server-domain-abc-hub-group-0] hub ipv6 private-address 192:168::1 [Server-vam-server-domain-abc-hub-group-0] hub ipv6 private-address 192:168::2 # Specify a private IPv6 address range for spokes in hub group 0.
Page 308 # Set the pre-shared key to 123456. [Spoke1-vam-client-Spoke1] pre-shared-key simple 123456 # Enable the VAM client. [Spoke1-vam-client-Spoke1] client enable [Spoke1-vam-client-Spoke1] quit e. Configure Spoke 2: # Create a VAM client named Spoke2. <Spoke2> system-view [Spoke2] vam client name Spoke2 # Specify ADVPN domain abc for the VAM client. [Spoke2-vam-client-Spoke2] advpn-domain abc # Specify the VAM server.
Page 309 [Spoke2-Tunnel1] quit Configure OSPFv3: # On Hub 1, configure OSPFv3. <Hub1> system-view [Hub1] ospfv3 [Hub1-ospfv3-1] router-id 0.0.0.1 [Hub1-ospfv3-1] area 0.0.0.0 [Hub1-ospfv3-1-area-0.0.0.0] quit [Hub1-ospfv3-1] quit [Hub1] interface loopback 0 [Hub1-LoopBack0] ospfv3 1 area 0.0.0.0 [Hub1-LoopBack0] quit [Hub1] interface gigabitethernet 1/0/2 [Hub1-GigabitEthernet1/0/2] ospfv3 1 area 0.0.0.0 [Hub1-GigabitEthernet1/0/2] quit [Hub1] interface tunnel 1 [Hub1-Tunnel1] ospfv3 1 area 0.0.0.0...
Page 310 [Spoke2-ospfv3-1] area 0.0.0.0 [Spoke2-ospfv3-1-area-0.0.0.0] quit [Spoke2-ospfv3-1] quit [Spoke2] interface tunnel 1 [Spoke2-Tunnel1] ospfv3 1 area 0.0.0.0 [Spoke2-Tunnel1] ospfv3 network-type p2mp [Spoke2-Tunnel1] quit [Spoke2] interface gigabitethernet 1/0/2 [Spoke2-GigabitEthernet1/0/2] ospfv3 1 area 0.0.0.0 [Spoke2-GigabitEthernet1/0/2] quit Configure IPv6 multicast: a. Configure Hub 1: # Enable IPv6 multicast routing.
Page 311 [Hub2-Tunnel1] quit # Configure Loopback 0 as a C-BSR and a C-RP. <Hub2>system-view [Hub2] ipv6 pim [Hub2-pim6] c-bsr 55::55 [Hub2-pim6] c-rp 55::55 [Hub2-pim6] quit c. Configure Spoke 1: # Enable IPv6 multicast routing. <Spoke1> system-view [Spoke1] ipv6 multicast routing [Spoke1-mrib6] quit # Enable IPv6 PIM-SM and NBMA mode on Tunnel interface tunnel1.
Page 312 1: Tunnel1, FE80::3 Protocol: pim-sm, UpTime: 17:01:23, Expires: 00:02:41 (100::1, FF0E::1) RP: 44::44 (local) Protocol: pim-sm, Flag: SPT LOC ACT UpTime: 00:00:02 Upstream interface: GigabitEthernet1/0/3 Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface information: Total number of downstream interfacs: 1 1: Tunnel1, FE80::3 Protocol: pim-sm, UpTime: 00:00:02, Expires: 00:03:28 The output show that Tunnel interface tunnel1 (FE80::3) on Spoke 1 will receive the IPv6 multicast...
Page 313: Configuring Mld
Configuring MLD Overview Multicast Listener Discovery (MLD) establishes and maintains IPv6 multicast group memberships between a Layer 3 multicast device and the hosts on the directly connected subnet. MLD has the following versions: • MLDv1 (defined by RFC 2710), which is derived from IGMPv2. •...
Page 314 Joining an IPv6 multicast group Figure 84 MLD queries and reports IPv6 network Router A Router B Ethernet Host A Host B Host C (G2) (G1) (G1) Query Report As shown in Figure 84, Host B and Host C want to receive the IPv6 multicast data addressed to IPv6 multicast group G1.
Page 315: Mldv2 Enhancements
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 316: Mld Ssm Mapping
• Filter mode—Router keeps tracing the Include or Exclude state. • List of sources—Router keeps tracing the newly added or deleted IPv6 multicast source. • Timers—Filter timers, which include the time that the router waits before switching to the Include mode after an IPv6 multicast address times out, and source timers for source recording. MLD SSM mapping An MLDv2 host can explicitly specify multicast sources in its MLDv2 reports.
Page 317: Mld Proxying
MLD proxying As shown in Figure 87, in a simple tree-shaped topology, it is not necessary to configure IPv6 multicast routing protocols, such as IPv6 PIM, on edge devices. Instead, you can configure MLD proxying on these devices. With MLD proxying configured, the edge device acts as an MLD proxy: •...
Page 318: Mld Configuration Task List
• RFC 3810, Multicast Listener Discovery Version 2 (MLDv2) for IPv6 MLD configuration task list Tasks at a glance Configuring basic MLD features: • (Required.) Enabling MLD • (Optional.) Specifying an MLD version • (Optional.) Configuring a static group member •...
Page 319: Specifying An Mld Version
Step Command Remarks Enable MLD. mld enable By default, MLD is disabled. Specifying an MLD version For MLD to operate correctly, specify the same MLD version for all routers on the same subnet. To specify an MLD version: Step Command Remarks Enter system view.
Page 320: Adjusting Mld Performance
To configure an IPv6 multicast group policy: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, no IPv6 multicast group-policy group polices exist Configure an IPv6 multicast ipv6-acl-number interface, and hosts attached to group policy on the interface. [ version-number ] the interface can join any IPv6 multicast groups.
Page 321 • You can configure the MLD query and response parameters globally for all interfaces in MLD view or for an interface in interface view. For an interface, the interface-specific configuration takes priority over the global configuration. • To avoid frequent MLD querier changes, set the MLD other querier present timer greater than the MLD general query interval.
Page 322: Enabling Fast-Leave Processing
Step Command Remarks querier's By default, the MLD querier's mld robust-count count robustness variable. robustness variable is 2. By default, the MLD startup query Set the MLD startup query startup-query-interval interval equals one quarter of the interval. interval MLD general query interval. By default, the MLD startup query Set the MLD startup query mld startup-query-count count...
Page 323: Configuration Prerequisites
Configuration prerequisites Before you configure MLD SSM mappings, complete the following tasks: • Configure an IPv6 unicast routing protocol so that all devices in the domain can interoperate at the network layer. • Configure basic MLD features. Configuration procedure To configure an MLD SSM mapping: Step Command Remarks...
Page 324: Enabling Ipv6 Multicast Forwarding On A Non-Querier Interface
Step Command Remarks Return to system view. quit interface interface-type Enter interface view. interface-number By default, MLD proxying is Enable MLD proxying. mld proxy enable disabled. Enabling IPv6 multicast forwarding on a non-querier interface Typically, only MLD queriers can forward IPv6 multicast traffic and non-queriers cannot. This prevents IPv6 multicast data from being repeatedly forwarded.
Page 325: Enabling Mld Nsr
Enabling MLD NSR The following matrix shows the feature and hardware compatibility: Hardware MLD NSR compatibility MSR954 (JH296A/JH297A/JH298A/JH299A/JH373A) MSR958 (JH300A/JH301A) MSR1002-4/1003-8S MSR2003 MSR2004-24/2004-48 MSR3012/3024/3044/3064 MSR4060/4080 This feature backs up information about MLD interfaces and MLD multicast groups to the standby process.
Page 326: Mld Configuration Examples
Task Command reset mld [ vpn-instance vpn-instance-name ] group { all | interface interface-type interface-number { all | Clear dynamic MLD multicast group entries. ipv6-group-address [ prefix-length ] [ ipv6-source-address [ prefix-length ] ] } } MLD configuration examples Basic MLD features configuration examples Network requirements As shown in Figure...
Page 327 Configure OSPFv3 on the routers in the IPv6 PIM-DM domain. (Details not shown.) Enable the IPv6 multicast routing, MLD, and IPv6 PIM-DM: # On Router A, enable IPv6 multicast routing. <RouterA> system-view [RouterA] ipv6 multicast routing [RouterA-mrib6] quit # Enable MLD on GigabitEthernet 1/0/1. [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] mld enable [RouterA-GigabitEthernet1/0/1] quit...
Page 328: Mld Ssm Mapping Configuration Example
Verifying the configuration # Display MLD information for GigabitEthernet 1/0/1 on Router B. [RouterB] display mld interface gigabitethernet 1/0/1 GigabitEthernet1/0/1(FE80::200:5EFF:FE66:5100): MLD is enabled. MLD version: 1 Query interval for MLD: 125s Other querier present time for MLD: 255s Maximum query response time for MLD: 10s Querier for MLD: FE80::200:5EFF:FE66:5100 (this router) MLD groups reported in total: 1 MLD SSM mapping configuration example...
Page 329 Device Interface IPv6 address Device Interface IPv6 address Router B GE 1/0/1 2001::2/64 Router D GE 1/0/1 4001::2/64 Router B GE 1/0/2 1002::2/64 Router D GE 1/0/2 3002::2/64 Router B GE 1/0/3 2002::1/64 Router D GE 1/0/3 1003::2/64 Configuration procedure Assign an IPv6 address and prefix length to each interface, as shown in Table 23.
Page 330 Configure the IPv6 SSM group range: # On Router D, specify FF3E::/64 as the IPv6 SSM group range. [RouterD] acl ipv6 basic 2000 [RouterD-acl-ipv6-basic-2000] rule permit source ff3e:: 64 [RouterD-acl-ipv6-basic-2000] quit [RouterD] ipv6 pim [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.
Page 331: Mld Proxying Configuration Example
(3001::1, FF3E::101) RP: 1003::2 Protocol: pim-ssm, Flag: UpTime: 00:13:25 Upstream interface: GigabitEthernet1/0/2 Upstream neighbor: 3002::1 RPF prime neighbor: 3002::1 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet1/0/1 Protocol: mld, UpTime: 00:13:25, Expires: - MLD proxying configuration example Network requirements As shown in Figure •...
Page 332: Troubleshooting Mld
[RouterA-GigabitEthernet1/0/2] quit # Enable MLD on GigabitEthernet 1/0/1. [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] mld enable [RouterA-GigabitEthernet1/0/1] quit # On Router B, enable IPv6 multicast routing. <RouterB> system-view [RouterB] ipv6 multicast routing [RouterB-mrib6] quit # Enable MLD proxying on GigabitEthernet 1/0/1. [RouterB] interface gigabitethernet 1/0/1 [RouterB-GigabitEthernet1/0/1] mld proxy enable [RouterB-GigabitEthernet1/0/1] quit...
Page 333: Inconsistent Membership Information On The Routers On The Same Subnet
Inconsistent membership information on the routers on the same subnet Symptom Different memberships are maintained on different MLD routers on the same subnet. Solution To resolve the problem: Use the display current-configuration command to verify the MLD information on the interface.
Page 334: 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 335 The nodes without downstream receivers are pruned. A router that has no downstream receivers multicasts a prune message to all IPv6 PIM routers on the subnet. When the upstream node receives the prune message, it removes the receiving interface from the (S, G) entry.
Page 336: Ipv6 Pim-Sm Overview
Figure 92 Assert mechanism Router A Router B Ethernet Assert message IPv6 multicast packets Receiver Router C As shown in Figure 92, after Router A and Router B receive an (S, G) packet from the upstream node, they both forward the packet to the local subnet. As a result, the downstream node Router C receives two identical multicast packets.
Page 337 IMPORTANT: MLD must be enabled on the device that acts as the receiver-side DR. Otherwise, the receiver hosts attached to the DR cannot join any IPv6 multicast groups. For more information about MLD, see "Configuring MLD." Figure 93 DR election Receiver Source Receiver...
Page 338 As shown in Figure 94, each C-RP periodically unicasts its advertisement messages (C-RP-Adv messages) to the BSR. An advertisement message contains the address of the advertising C-RP and the IPv6 multicast group range to which it is designated. The BSR collects these advertisement messages and organizes the C-RP information into an RP-set, which is a database of mappings between IPv6 multicast groups and RPs.
Page 339 multicast source registers with the closest RP or a receiver-side DR joins the closest RP to implement source information synchronization. Anycast RP has the following benefits: • Optimal RP path—An IPv6 multicast source registers with the closest RP to build an optimal SPT.
Page 340 RPT building Figure 96 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 96, 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 341 Figure 97 IPv6 multicast source registration Host A Source Receiver Host B Server Receiver Join message Register message Host C IPv6 multicast packets As shown in Figure 97, 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 342: Ipv6 Bidir-Pim Overview
The RP periodically checks the multicast packet forwarding rate. If the RP finds that the traffic rate exceeds the specified threshold, it sends an (S, G) source-specific join message toward the IPv6 multicast source. The routers along the path from the RP to the IPv6 multicast source constitute an SPT branch.
Page 343 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 on each subnet. Only the DFs can forward IPv6 multicast data to the RP. DF election is not necessary for an RPL.
Page 344 Figure 99 RPT building at the receiver side Source Receiver Host A Server B Source Receiver Host B Server A Receiver Join message Receiver-side RPT IPv6 Multicast packets Host C As shown in Figure 99, 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 345: Ipv6 Administrative Scoping Overview
Figure 100 RPT building at the IPv6 multicast source side Source Receiver Host A Server B Source Receiver Host B Server A Receiver Source-side RPT IPv6 Multicast packets Host C As shown in Figure 100, 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 346 BSMs, of these IPv6 multicast groups cannot cross the boundary of the IPv6 admin-scoped zone for the group range. The IPv6 multicast group ranges to which different IPv6 admin-scoped zones are designated can have intersections. However, the IPv6 multicast groups in an IPv6 admin-scoped zone are valid only within its local zone, and theses IPv6 multicast groups are regarded as private group addresses.
Page 347: Ipv6 Pim-Ssm Overview
Figure 102 IPv6 multicast address format 0xFF Flags Scope Group ID (112 bits) 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 348: Relationship Among Ipv6 Pim Protocols
SPT building The decision to build an RPT for IPv6 PIM-SM or an SPT for IPv6 PIM-SSM depends on whether the IPv6 multicast group that the receiver host joins is in the IPv6 SSM group range. The IPv6 SSM group range reserved by IANA is FF3x::/32, where "x" represents any legal address scope. Figure 103 SPT building in IPv6 PIM-SSM Host A Source...
Page 349: Ipv6 Pim Support For Vpns
Figure 104 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 350: Ipv6 Pim-Dm Configuration Task List
IPv6 PIM-DM configuration task list Tasks at a glance (Required.) Enabling IPv6 PIM-DM (Optional.) Enabling the state refresh feature (Optional.) Configuring state refresh parameters (Optional.) Configuring IPv6 PIM-DM graft retry timer (Optional.) Configuring common IPv6 PIM features Configuration prerequisites Before you configure IPv6 PIM-DM, configure an IPv6 unicast routing protocol so that all devices in the domain can interoperate at the network layer.
Page 351: Configuring State Refresh Parameters
Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Enable the state refresh By default, the state refresh ipv6 pim state-refresh-capable feature. feature is enabled. Configuring state refresh parameters The state refresh interval determines the interval at which a router sends state refresh messages. It is configurable.
Page 352: Configuring Ipv6 Pim-Sm
For more information about the configuration of other timers in IPv6 PIM-DM, see "Configuring common IPv6 PIM timers." Configuring IPv6 PIM-SM This section describes how to configure IPv6 PIM-SM. IPv6 PIM-SM configuration task list Tasks at a glance Remarks (Required.) Enabling IPv6 PIM-SM (Required.) Configuring an...
Page 353: Configuring An Rp
Step Command Remarks Enable IPv6 multicast ipv6 multicast routing By default, IPv6 multicast routing routing and enter IPv6 MRIB vpn-instance is disabled. view. vpn-instance-name ] Return to system view. quit interface interface-type Enter interface view. interface-number By default, IPv6 PIM-SM is Enable IPv6 PIM-SM.
Page 354 A C-RP policy enables the BSR to filter C-RP advertisement messages by using an ACL that specifies the packet source address range and multicast group addresses. You must configure the same C-RP policy on all C-BSRs in the IPv6 PIM-SM domain because every C-BSR might become the BSR.
Page 355: Configuring A Bsr
Step Command Remarks Enter system view. system-view ipv6 vpn-instance Enter IPv6 PIM view. vpn-instance-name ] By default, Anycast RP is not configured. anycast-rp Configure Anycast RP. ipv6-anycast-rp-address You can repeat this command to ipv6-member-address multiple member addresses to an Anycast RP set. Configuring a BSR You must configure a BSR if C-RPs are configured to dynamically select the RP.
Page 356 Step Command Remarks ipv6 vpn-instance Enter IPv6 PIM view. vpn-instance-name ] c-bsr ipv6-address scope Configure a C-BSR. scope-id hash-length By default, no C-BSRs exist. hash-length | priority priority ] * By default, no BSR policies exist, (Optional.) Configure a BSR bsr-policy ipv6-acl-number and all bootstrap messages are policy.
Page 357: Configuring Ipv6 Multicast Source Registration
information. To reduce traffic, you can disable this feature if all the devices have consistent routing information. To disable the device from sending BSMs out of incoming interfaces: Step Command Remarks Enter system view. system-view ipv6 vpn-instance Enter IPv6 PIM view. vpn-instance-name ] Disable the device to send By default, the device sends...
Page 358: Configuring The Switchover To Spt
Step Command Remarks By default, no IPv6 register Configure IPv6 register-policy ipv6-acl-number policies exist, and all IPv6 register register policy. messages are regarded as legal. Configure device By default, the device calculates calculate checksum register-whole-checksum the checksum based on the based on the entire register header of a register message.
Page 359: Configuration Prerequisites
Tasks at a glance Remarks Configuring a BSR • (Required.) Configuring a C-BSR • (Optional.) Configuring an IPv6 PIM domain border Skip the task of configuring a BSR on an IPv6 • network without C-RPs. (Optional.) Disabling BSM semantic fragmentation •...
Page 360: Configuring An Rp
Configuring an RP CAUTION: When both IPv6 PIM-SM and IPv6 BIDIR-PIM run on the IPv6 PIM network, do not use the same RP to provide services for IPv6 PIM-SM and IPv6 BIDIR-PIM. Otherwise, exceptions might occur to the IPv6 PIM routing table. An RP can provide services for multiple or all IPv6 multicast groups.
Page 361 routers in the network can determine the RPs for different IPv6 multicast group ranges based on the RP-set information. 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 IPv6 address in a BSM, and floods the BSM to all IPv6 PIM routers in the domain.
Page 362: Configuring A Bsr
Configuring a BSR You must configure a BSR if C-RPs are configured to dynamically select the RP. You do not need to configure a BSR when you have configured only a static RP but no C-RPs. An IPv6 BIDIR-PIM domain can have only one BSR, but must have a minimum of one C-BSR. Any router can be configured as a C-BSR.
Page 363 Configuring an IPv6 PIM domain border An IPv6 PIM domain border determines the transmission boundary of bootstrap messages. Bootstrap messages cannot cross the domain border in either direction. A number of PIM domain border interfaces partition a network into different IPv6 BIDIR-PIM domains. To configure an IPv6 PIM domain border: Step Command...
Page 364: Configuring Ipv6 Pim-Ssm
Step Command Remarks Disable the device from By default, the device sends sending BSMs undo bsm-reflection enable BSMs out of incoming interfaces. incoming interfaces. Configuring IPv6 PIM-SSM IPv6 PIM-SSM requires MLDv2 support. Enable MLDv2 on IPv6 PIM routers that connect to multicast receivers.
Page 365: 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. If the IPv6 multicast group address is not in this range, the IPv6 PIM mode is IPv6 PIM-SM.
Page 366: Configuring An Ipv6 Multicast Source Policy
• Configure IPv6 PIM-DM or IPv6 PIM-SSM. Configuring an IPv6 multicast source policy This feature enables the device to filter IPv6 multicast data by using an ACL that specifies the IPv6 multicast sources and the optional groups. It filters not only IPv6 multicast data packets but also IPv6 PIM register messages with IPv6 multicast data encapsulated.
Page 367 The LAN delay defines the IPv6 PIM message propagation delay. The override interval defines a time period for a downstream router to override a prune message. If the propagation delay or override interval on different IPv6 PIM routers on a shared-media LAN are different, the largest ones apply.
Page 368: Configuring Common Ipv6 Pim Timers
Step Command Remarks ipv6 hello-option Set the DR priority. The default setting is 1. dr-priority priority ipv6 pim hello-option holdtime default setting Set the neighbor lifetime. time seconds. Set the IPv6 PIM message ipv6 pim hello-option lan-delay default setting propagation delay. delay milliseconds.
Page 369: Setting The Maximum Size Of Each Join Or Prune Message
Step Command Remarks ipv6 vpn-instance Enter IPv6 PIM view. vpn-instance-name ] By default, the interval to send Set the hello interval. timer hello interval hello messages is 30 seconds. By default, the interval to send join/prune messages seconds. Set the join/prune interval. timer join-prune interval NOTE: This configuration takes effect...
Page 370: Enabling Bfd For Ipv6 Pim
Enabling BFD for IPv6 PIM If a DR on a shared-media network fails, a new DR election process will start after the DR ages out. However, it might take a long period of time before other routers detect the link failures and trigger a new DR election.
Page 371: Enabling Snmp Notifications For Ipv6 Pim
Hardware IPv6 PIM NSR compatibility MSR954 (JH296A/JH297A/JH298A/JH299A/JH373A) MSR958 (JH300A/JH301A) MSR1002-4/1003-8S MSR2003 MSR2004-24/2004-48 MSR3012/3024/3044/3064 MSR4060/4080 This feature enables IPv6 PIM to back up protocol state information, including IPv6 PIM neighbor information and routes, from the active process to the standby process. The standby process immediately takes over when the active process fails.
Page 372: Displaying And Maintaining Ipv6 Pim
• Do not configure MLD features on IPv6 ADVPN tunnel interfaces that are enabled with NBMA mode. Configuration procedure To enable NBMA mode for an ADVPN tunnel interface: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number default, NBMA...
Page 373: Ipv6 Pim Configuration Examples
IPv6 PIM configuration examples IPv6 PIM-DM configuration example Network requirements As shown in Figure 105: • OSPFv3 runs on the network. • VOD streams are sent to receiver hosts in multicast. The receiver groups of different organizations form stub networks, and a minimum of one receiver host exists on each stub network.
Page 374 Configure OSPFv3 on the routers in the IPv6 PIM-DM domain. (Details not shown.) Enable IPv6 multicast routing, MLD, and IPv6 PIM-DM: # On Router A, enable IPv6 multicast routing. <RouterA> system-view [RouterA] ipv6 multicast routing [RouterA-mrib6] quit # Enable MLD on GigabitEthernet 1/0/1 (the interface that connects to the stub network). [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] mld enable [RouterA-GigabitEthernet1/0/1] quit...
Page 375 Neighbor Interface Uptime Expires Dr-Priority FE80::A01:101:1 GE1/0/2 00:04:00 00:01:29 1 FE80::B01:102:2 GE1/0/3 00:04:16 00:01:29 3 FE80::C01:103:3 GE1/0/4 00:03:54 00:01:17 5 # Send an MLD report from Host A to join IPv6 multicast group FF0E::101. (Details not shown.) # Send IPv6 multicast data from IPv6 multicast source 4001::100/64 to IPv6 multicast group FF0E::101.
Page 376: Ipv6 Pim-Sm Non-Scoped Zone Configuration Example
Protocol: pim-dm, UpTime: 00:02:19, Expires: - The output shows the following information: • Routers on the SPT path (Router A and Router D) have the correct (S, G) entries. • Router A has the correct (*, G) entry. IPv6 PIM-SM non-scoped zone configuration example Network requirements As shown in Figure...
Page 377 Device Interface IPv6 address Device Interface IPv6 address Router A GE1/0/3 1003::1/64 Router D GE1/0/3 4002::1/64 Router B GE1/0/1 2001::1/64 Router E GE1/0/1 3001::2/64 Router B GE1/0/2 2002::1/64 Router E GE1/0/2 2002::2/64 Router C GE1/0/1 2001::2/64 Router E GE1/0/3 1003::2/64 Router C GE1/0/2 3001::1/64...
Page 378 [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 379: Ipv6 Pim-Sm Admin-Scoped Zone Configuration Example
IPv6 PIM-SM admin-scoped zone configuration example Network requirements As shown in Figure 107: • OSPFv3 runs on the network. 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.
Page 380 Device Interface IPv6 address Device Interface IPv6 address Router B GE1/0/1 2001::1/64 Router F GE1/0/1 8001::1/64 Router B GE1/0/2 1002::2/64 Router F GE1/0/2 6002::2/64 Router B GE1/0/3 2002::1/64 Router F GE1/0/3 2003::2/64 Router B GE1/0/4 2003::1/64 Router G GE1/0/1 9001::1/64 Router C GE1/0/1 3001::1/64...
Page 381 [RouterB] interface gigabitethernet 1/0/3 [RouterB-GigabitEthernet1/0/3] ipv6 pim sm [RouterB-GigabitEthernet1/0/3] quit [RouterB] interface gigabitethernet 1/0/4 [RouterB-GigabitEthernet1/0/4] ipv6 pim sm [RouterB-GigabitEthernet1/0/4] quit # Enable IPv6 multicast routing and IPv6 PIM-SM on Router C, Router D, Router F, Router G, and Router H in the same way Router B is configured. (Details not shown.) Configure IPv6 admin-scoped zone boundaries: # On Router B, configure GigabitEthernet 1/0/3 and GigabitEthernet 1/0/4 as the boundaries of IPv6 admin-scoped zone 1.
Page 382 [RouterF-pim6] c-rp 8001::1 [RouterF-pim6] quit Verifying the configuration # Display BSR information on Router B. [RouterB] display ipv6 pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:25 Elected BSR address: 8001::1 Priority: 64 Hash mask length: 126 Uptime: 00:01:45 Scope: 4 State: Elected Bootstrap timer: 00:00:06...
Page 383 Bootstrap timer: 00:00:49 Elected BSR address: 8001::1 Priority: 64 Hash mask length: 126 Uptime: 00:01:11 Candidate BSR address: 8001::1 Priority: 64 Hash mask length: 126 # Display RP information on Router B. [RouterB] display ipv6 pim rp-info BSR RP information: Scope: non-scoped Group/MaskLen: FF00::/8 RP address...
Page 384: Ipv6 Bidir-Pim Configuration Example
1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FFB4::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FFC4::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FFD4::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FFE4::/16 RP address Priority...
Page 385 Figure 108 Network diagram Receiver 1 Receiver 2 Loop0 Router B GE1/0/1 GE1/0/3 GE1/0/1 Router C Host A GE1/0/2 GE1/0/2 Host B IPv6 BIDIR-PIM Source 1 Source 2 GE1/0/2 GE1/0/3 GE1/0/1 GE1/0/2 Router A Router D Table 28 Interface and IPv6 address assignment Device Interface IPv6 address...
Page 386 [RouterA-pim6] quit # On Router B, enable IPv6 multicast routing. <RouterB> system-view [RouterB] ipv6 multicast routing [RouterB-mrib6] quit # Enable MLD on the receiver-side interface (GigabitEthernet 1/0/1). [RouterB] interface gigabitethernet 1/0/1 [RouterB-GigabitEthernet1/0/1] mld enable [RouterB-GigabitEthernet1/0/1] quit # Enable IPv6 PIM-SM on other interfaces. [RouterB] interface gigabitethernet 1/0/2 [RouterB-GigabitEthernet1/0/2] ipv6 pim sm [RouterB-GigabitEthernet1/0/2] quit...
Page 387 [RouterD] interface gigabitethernet 1/0/3 [RouterD-GigabitEthernet1/0/3] ipv6 pim sm [RouterD-GigabitEthernet1/0/3] quit # Enable IPv6 BIDIR-PIM. [RouterD] ipv6 pim [RouterD-pim6] bidir-pim enable [RouterD-pim6] quit On Router C, configure GigabitEthernet 1/0/1 as the C-BSR, and Loopback 0 as the C-RP for the entire IPv6 BIDIR-PIM domain. [RouterC-pim6] c-bsr 2002::2 [RouterC-pim6] c-rp 6001::1 bidir [RouterC-pim6] quit...
Page 388 GE1/0/2 00:39:34 FE80::200:5EFF: FE71:2802 (local) GE1/0/3 Lose 01:21:40 FE80::20F:E2FF: FE15:5602 Display information about the DF for IPv6 multicast forwarding: # Display information about the DF for IPv6 multicast forwarding on Router A. [RouterA] display ipv6 multicast forwarding df-info Total 1 RP, 1 matched 00001.
Page 389: Ipv6 Pim-Ssm Configuration Example
IPv6 PIM-SSM configuration example Network requirements As shown in Figure 109: • OSPFv3 runs on the network. • The receivers receive VOD information through multicast. The receiver groups of different organizations form stub networks, and one or more receiver hosts exist in each stub network. The entire IPv6 PIM domain operates in the SSM mode.
Page 390 Configuration procedure Assign an IPv6 address and prefix length for each interface, as shown in Figure 109. (Details not shown.) Configure OSPFv3 on the routers in the IPv6 PIM-SSM domain. (Details not shown.) Enable IPv6 multicast routing, MLD and IPv6 PIM-SM: # On Router A, enable IPv6 multicast routing.
Page 391: Troubleshooting Ipv6 Pim
(4001::100, FF3E::101) Protocol: pim-ssm, Flag: UpTime: 00:00:11 Upstream interface: GigabitEthernet1/0/2 Upstream neighbor: 1002::2 RPF prime neighbor: 1002::2 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet1/0/1 Protocol: mld, UpTime: 00:00:11, Expires: 00:03:25 # Display IPv6 PIM multicast routing table information on Router D. [RouterD] display ipv6 pim routing-table Total 0 (*, G) entry;...
Page 392: Ipv6 Multicast Data Is Abnormally Terminated On An Intermediate Router
Use display ipv6 pim interface verbose to verify that the same IPv6 PIM mode is enabled on the RPF interface on a router and the connected interface of the router's RPF neighbor. Use display current-configuration to verify that the same IPv6 PIM mode is enabled on all routers on the network.
Page 393 Solution To resolve the problem: Use display ipv6 routing-table on each router to view routing table information. Verify that IPv6 unicast routes to the C-RPs and the BSR are available on each router and that a route is available between each C-RP and the BSR. Use display ipv6 pim bsr-info to verify that the BSR information exists on each router.
Page 394: Document Conventions And Icons
Document conventions and icons Conventions This section describes the conventions used in the documentation. Port numbering in examples The port numbers in this document are for illustration only and might be unavailable on your device. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown.
Page 395: Network Topology Icons
Network topology icons Convention Description 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 396: Support And Other Resources
Hewlett Packard Enterprise Support Center More Information on Access to Support Materials page: www.hpe.com/support/AccessToSupportMaterials IMPORTANT: Access to some updates might require product entitlement when accessed through the Hewlett Packard Enterprise Support Center. You must have an HP Passport set up with relevant entitlements.
Page 397: Websites
Websites Website Link Networking websites Hewlett Packard Enterprise Information Library for www.hpe.com/networking/resourcefinder Networking Hewlett Packard Enterprise Networking website www.hpe.com/info/networking Hewlett Packard Enterprise My Networking website www.hpe.com/networking/support Hewlett Packard Enterprise My Networking Portal www.hpe.com/networking/mynetworking Hewlett Packard Enterprise Networking Warranty www.hpe.com/networking/warranty General websites Hewlett Packard Enterprise Information Library www.hpe.com/info/enterprise/docs Hewlett Packard Enterprise Support Center...
Page 398 part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.
Page 399: Index
Index A C D E H I M N O P T Configuring PIM-SSM,117 Configuring SA message-related parameters,155 Accessing Hewlett Packard Enterprise Support,387 Configuring the IGMP snooping querier,22 Accessing updates,387 Configuring the MLD snooping querier,267 Adjusting IGMP performance,73 Conventions,385 Adjusting MLD performance,311 Displaying and maintaining IGMP,78...
Page 400 Multicast models,4 Overview,177 Multicast packet forwarding mechanism,10 Overview,304 Multicast support for VPNs,10 Overview,257 Multicast VPN configuration examples,201 Multicast VPN configuration task list,193 PIM configuration examples,125 Network topology icons,386 Troubleshooting IGMP,86 Troubleshooting IGMP snooping,39 Overview,146 Troubleshooting IPv6 PIM,382 Overview,41 Troubleshooting MD VPN,255 Overview,325 Troubleshooting...

This manual is also suitable for:

Msr2003 Msr1003-8s Msr2004 Msr2004-48 Msr3012 Msr3024 ... Show all

HP MSR1002-4 Configuration Manual

Multicast Overview

Configuring IGMP Snooping

Configuring Multicast Routing and Forwarding

Configuring IGMP

Configuring PIM

Configuring MSDP

Configuring Multicast VPN

Configuring MLD Snooping

Configuring Ipv6 Multicast Routing and Forwarding

Quick Links

Troubleshooting

Related Manuals for HP MSR1002-4

Summary of Contents for HP MSR1002-4