Page 1 HPE FlexNetwork 7500 Switch Series IP Multicast Configuration Guide Part number: 5998-7469R Software version: 7500-CMW710-R7178 Document version: 6W100-20160129...
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 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 Displaying and maintaining PIM snooping ······································································································· 41 PIM snooping configuration example ··············································································································· 41 Troubleshooting PIM snooping ························································································································ 45 PIM snooping does not work on a Layer 2 device ··················································································· 45 Configuring multicast VLANs ········································································ 46 Overview ·························································································································································· 46 Multicast VLAN configuration task list ·············································································································· 48 Configuring a sub-VLAN-based multicast VLAN ······························································································...
Page 5 Configuring IGMP SSM mappings ··················································································································· 85 Configuration prerequisites ······················································································································ 85 Configuration procedure ··························································································································· 85 Displaying and maintaining IGMP ···················································································································· 85 IGMP configuration examples ·························································································································· 86 Basic IGMP features configuration examples ·························································································· 86 IGMP SSM mapping configuration example ···························································································· 88 Troubleshooting IGMP ····································································································································· 91 No membership information on the receiver-side router ··········································································...
Page 6 PIM-SM non-scoped zone configuration example ················································································· 131 PIM-SM admin-scoped zone configuration example ·············································································· 134 BIDIR-PIM configuration example ·········································································································· 139 PIM-SSM configuration example ············································································································ 143 Troubleshooting PIM ······································································································································ 146 A multicast distribution tree cannot be correctly built ············································································· 146 Multicast data is abnormally terminated on an intermediate router ························································ 147 An RP cannot join an SPT in PIM-SM ····································································································...
Page 7 Configuring BGP MDT ··································································································································· 196 Configuration prerequisites ···················································································································· 197 Enabling BGP MDT peers or peer groups ····························································································· 197 Configuring a BGP MDT route reflector ································································································· 197 Displaying and maintaining multicast VPN ···································································································· 198 Multicast VPN configuration examples ·········································································································· 199 Intra-AS MD VPN configuration example ······························································································· 199 MD VPN inter-AS option C configuration example ·················································································...
Page 8 Configuring IPv6 multicast VLANs ······························································ 262 Overview ························································································································································ 262 IPv6 multicast VLAN configuration task list ···································································································· 264 Configuring a sub-VLAN-based IPv6 multicast VLAN ··················································································· 264 Configuration prerequisites ···················································································································· 264 Configuration guidelines ························································································································· 264 Configuration procedure ························································································································· 264 Configuring a port-based IPv6 multicast VLAN ······························································································ 265 Configuration prerequisites ····················································································································...
Page 9 Inconsistent membership information on the routers on the same subnet ············································· 300 Configuring IPv6 PIM ·················································································· 301 Overview ························································································································································ 301 IPv6 PIM-DM overview ··························································································································· 301 IPv6 PIM-SM overview ··························································································································· 303 IPv6 BIDIR-PIM overview ······················································································································· 308 IPv6 administrative scoping overview ···································································································· 311 IPv6 PIM-SSM overview ························································································································...
Page 10 Document conventions and icons ······························································· 356 Conventions ··················································································································································· 356 Network topology icons ·································································································································· 357 Support and other resources ······································································ 358 Accessing Hewlett Packard Enterprise Support ···························································································· 358 Accessing updates ········································································································································· 358 Websites ················································································································································ 359 Customer self repair ······························································································································· 359 Remote support ······································································································································ 359 Documentation feedback ·······················································································································...
Page 11: Multicast Overview
Multicast overview Introduction to multicast As a technique that coexists with unicast and broadcast, the multicast technique effectively addresses the issue of point-to-multipoint data transmission. By enabling high-efficiency point-to-multipoint data transmission over a network, multicast greatly saves network bandwidth and reduces network load.
Page 12 Broadcast In broadcast transmission, the information source sends information to all hosts on the subnet, even if some hosts do not need the information. Figure 2 Broadcast transmission Figure 2, only Host B, Host D, and Host E need the information. If the information is broadcast to the subnet, Host A and Host C also receive it.
Page 13: Multicast Features
Figure 3 Multicast transmission The multicast source sends only one copy of the information to a multicast group. Host B, Host D, and Host E, which are information receivers, must join the multicast group. The routers on the network duplicate and forward the information based on the distribution of the group members. Finally, the information is correctly delivered to Host B, Host D, and Host E.
Page 14: Common Notations In Multicast
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 15: 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 16 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 17 Figure 4 IPv6 multicast format 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 Table 4 Flags field description Description Reserved, set to 0. •...
Page 18: 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 19 Layer 3 multicast protocols—IGMP, MLD, PIM, IPv6 PIM, MSDP, MBGP, and IPv6 MBGP. Layer 2 multicast refers to IP multicast operating at the data link layer. Layer 2 multicast protocols—IGMP snooping, MLD snooping, PIM snooping, IPv6 PIM snooping, multicast VLAN, and IPv6 multicast VLAN. •...
Page 20 An inter-domain multicast routing protocol is used for delivering multicast information between two ASs. So far, mature solutions include Multicast Source Discovery Protocol (MSDP) and MBGP. MSDP propagates multicast source information among different ASs. MBGP is an extension of the MP-BGP for exchanging multicast routing information among different ASs.
Page 21: Multicast Packet Forwarding Mechanism
Multicast packet forwarding mechanism In a multicast model, receiver hosts of a multicast group are usually located at different areas on the network. They are identified by the same multicast group address. To deliver multicast packets to these receivers, a multicast source encapsulates the multicast data in an IP packet with the multicast group address as the destination address.
Page 22: 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 23 Figure 11 IGMP snooping ports Router ports On an IGMP snooping Layer 2 device, the ports toward Layer 3 multicast devices are called router ports. In Figure 11, GigabitEthernet 1/0/1 of Switch A and GigabitEthernet 1/0/1 of Switch B are router ports.
Page 24: 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 25: Protocols And Standards
• If no match is found, the Layer 2 device discards the IGMP leave message. • If a match is found but the receiving port is not an outgoing interface in the forwarding entry, the Layer 2 device discards the IGMP leave message. •...
Page 26: Igmp Snooping Configuration Task List
IGMP snooping configuration task list Tasks at a glance Configuring basic IGMP snooping features: • (Required.) Enabling IGMP snooping • (Optional.) Specifying an IGMP snooping version • (Optional.) Setting the maximum number of IGMP snooping forwarding entries • (Optional.) Setting the IGMP last member query interval Configuring IGMP snooping port features: •...
Page 27: Specifying An Igmp Snooping Version
Enabling IGMP snooping for the specified VLANs Step Command Remarks Enter system view. system-view Enable IGMP snooping By default, IGMP snooping is globally and enter igmp-snooping globally disabled. IGMP-snooping view. Enable IGMP snooping for By default, IGMP snooping is enable vlan vlan-list the specified VLANs.
Page 28: Setting The Maximum Number Of Igmp Snooping Forwarding Entries
VLANs. Specifying an IGMP snooping version for a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Specify an IGMP snooping igmp-snooping version The default setting is 2. version for the VLAN. version-number Setting the maximum number of IGMP snooping forwarding entries You can set the maximum number of IGMP snooping forwarding entries, including dynamic entries and static entries.
Page 29: Configuring Igmp Snooping Port Features
Step Command Remarks Enter IGMP-snooping view. igmp-snooping Set the IGMP last member The default setting is 1 last-member-query-interval query interval globally. second. interval Setting the IGMP last member query interval in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view.
Page 30: Configuring Static Ports
globally. Setting the aging timers for dynamic ports in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Set the aging timer for The default setting is 260 igmp-snooping dynamic router ports in the seconds. router-aging-time interval VLAN.
Page 31: Enabling Fast-Leave Processing
The version of IGMP running on the simulated member host is the same as the version of IGMP snooping running on the port. The port ages out in the same way as a dynamic member port. To configure a port as a simulated member host: Step Command Remarks...
Page 32: Configuring The Igmp Snooping Querier
• The port that receives the IGMP general query or PIM hello message becomes a dynamic router port. Before its aging timer expires, this dynamic router port receives all multicast packets within the VLAN where the port belongs and forwards them to the host. The receiver host will receive multicast data that it does not want to receive.
Page 33: Configuring Parameters For Igmp General Queries And Responses
Configuring parameters for IGMP general queries and responses CAUTION: To avoid mistakenly deleting multicast group members, make sure the IGMP general query interval is greater than the maximum response time for IGMP general queries. You can modify the IGMP general query interval for a VLAN based on the actual condition of the network.
Page 34: Configuration Prerequisites
Configuration prerequisites Before you configure parameters for IGMP messages, complete the following tasks: • Enable IGMP snooping for the VLAN. • Determine the source IP address of IGMP general queries. • Determine the source IP address of IGMP group-specific queries. •...
Page 35: Setting The 802.1P Priority For Igmp Messages
VLAN interface does not have an IP address, the source IP address is 0.0.0.0. By default, the source IP address of IGMP leave messages is the IP Configure the source IP address of the current VLAN igmp-snooping leave address for IGMP leave interface.
Page 36: Enabling Multicast Source Port Filtering
Configuration restrictions and guidelines When you configure a multicast group policy, follow these guidelines: • This configuration takes effect only on the multicast groups that ports join dynamically. • You can configure a multicast group policy globally for all ports in IGMP-snooping view or for a port in interface view.
Page 37: Enabling Dropping Unknown Multicast Data
Enable multicast source port By default, multicast source port igmp-snooping source-deny filtering. filtering is disabled. Enabling dropping unknown multicast data This feature enables the switch 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. Configuration restrictions and guidelines When you enable dropping unknown multicast data, follow these restrictions and guidelines: •...
Page 38: Setting The Maximum Number Of Multicast Groups On A Port
Step Command Remarks Enter system view. system-view Enter IGMP-snooping view. igmp-snooping Enable IGMP report By default, IGMP report report-aggregation suppression. suppression is enabled. Setting the maximum number of multicast groups on a port You can set the maximum number of multicast groups on a port to regulate the port traffic. Configuration restrictions and guidelines When you set the maximum number of multicast groups on a port, follow these guidelines: •...
Page 39: Displaying And Maintaining Igmp Snooping
Enabling multicast group replacement on a port Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface-type interface view or Layer 2 interface-number aggregate interface view. Enable multicast group By default, multicast group igmp-snooping replacement on a port. overflow-replace [ vlan vlan-list ] replacement is disabled.
Page 40: Igmp Snooping Configuration Examples
Display information about Layer 2 MAC display l2-multicast mac [ mac-address ] [ vlan vlan-id ] [ slot multicast groups (in standalone mode). slot-number ] Display information about Layer 2 MAC display l2-multicast mac [ mac-address ] [ vlan vlan-id ] multicast groups (in IRF mode).
Page 41 Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 12. (Details not shown.) Configure Router A: # Enable IP multicast routing. <RouterA> system-view [RouterA] multicast routing [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...
Page 42: Static Port Configuration Example
Verifying the configuration # Send IGMP reports from Host A and Host B to join multicast groups 224.1.1.1 and 224.2.2.2. (Details not shown.) # Display dynamic IGMP snooping forwarding entries for VLAN 100 on Switch A. [SwitchA] display igmp-snooping group vlan 100 Total 1 entries.
Page 43 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 according to Figure 13.
Page 44 [SwitchA-vlan100] quit # Configure GigabitEthernet 1/0/3 as a static router port for VLAN 100. [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 45: 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 46 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 packets for VLAN 100.
Page 47: 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 packets for VLAN 100. [SwitchD-vlan100] igmp-snooping enable [SwitchD-vlan100] igmp-snooping drop-unknown [SwitchD-vlan100] quit...
Page 48: Multicast Group Policy Does Not Work
Multicast group policy does not work Symptom Hosts can receive multicast data from multicast groups that are not permitted by the multicast group policy. Solution To resolve the problem: Use the display acl command to verify that the configured ACL meets the multicast group policy requirements.
Page 49: Configuring Pim Snooping
Configuring PIM snooping Overview PIM snooping runs on Layer 2 devices. It works with IGMP snooping to analyze received PIM messages, and adds the ports that are interested in specific multicast data to a PIM snooping routing entry. In this way, the multicast data can be forwarded to only the ports that are interested in the data. Figure 15 Multicast packet transmission without or with PIM snooping Multicast packet transmission Multicast packet transmission when...
Page 50: Configuring Pim Snooping
Each PIM router in the VLAN, whether interested in the multicast data or not, can receive all multicast data and all PIM messages except PIM hello messages. • When the Layer 2 switch runs both IGMP snooping and PIM snooping, it performs the following actions: a.
Page 51: Displaying And Maintaining Pim Snooping
Step Command Remarks (Optional.) Set the aging The default setting is 210 seconds. time for global downstream pim-snooping A global downstream port or a global ports and global router ports graceful-restart router port is a Layer 2 aggregate on the new active MPU after join-aging-time interval interface that acts as a downstream an active/standby...
Page 52 Figure 16 Network diagram Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 16. (Details not shown.) Configure OSPF on the routers. (Details not shown.) Configure Router A: # Enable IP multicast routing. <RouterA> system-view [RouterA] multicast routing [RouterA-mrib] quit # Enable PIM-SM on each interface.
Page 53 [RouterB-GigabitEthernet1/0/2] pim sm [RouterB-GigabitEthernet1/0/2] quit Configure 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-SM on GigabitEthernet 1/0/2. [RouterC] interface gigabitethernet 1/0/2 [RouterC-GigabitEthernet1/0/2] pim sm [RouterC-GigabitEthernet1/0/2] quit...
Page 54 Slots (0 in total): Ports (1 in total): GE1/0/1 (00:32:43) 10.1.1.2 Slots (0 in total): Ports (1 in total): GE1/0/2 (00:32:43) 10.1.1.3 Slots (0 in total): Ports (1 in total): GE1/0/3 (00:32:43) 10.1.1.4 Slots (0 in total): Ports (1 in total): GE1/0/4 (00:32:43) The output shows that Router A, Router B, Router C, and Router D are PIM snooping neighbors.
Page 55: Troubleshooting Pim Snooping
Troubleshooting PIM snooping PIM snooping does not work on a Layer 2 device Symptom PIM snooping does not work on a Layer 2 device. Solution To resolve the problem: Use the display current-configuration command to display information about IGMP snooping and PIM snooping.
Page 56: Configuring Multicast Vlans
Configuring multicast VLANs Overview As shown in Figure 17, Host A, Host B, and Host C are in three different VLANs and the same multicast group. When Switch A (Layer 3 device) receives multicast data for that group, it sends three copies of the multicast data to Switch B (Layer 2 device).
Page 57 Figure 18 Sub-VLAN-based multicast VLAN IGMP snooping manages router ports in the multicast VLAN and member ports in each sub-VLAN. When Switch A receives multicast data from the multicast source, it sends only one copy of the multicast data to the multicast VLAN on Switch B. Then, Switch B sends a separate copy to each sub-VLAN in the multicast VLAN.
Page 58: Multicast Vlan Configuration Task List
Multicast VLAN configuration task list Tasks at a glance (Required.) Perform one of the following tasks: • Configuring a sub-VLAN-based multicast VLAN • Configuring a port-based multicast VLAN: Configuring user port attributes Assigning user ports to a multicast VLAN (Optional.) Setting the maximum number of multicast VLAN forwarding entries When you configure the multicast VLANs, follow these guidelines: •...
Page 59: Configuring A Port-Based Multicast Vlan
Step Command Remarks Configure a VLAN as a By default, a VLAN is not a multicast multicast VLAN and multicast-vlan vlan-id VLAN. enter its view. Assign the specified By default, a multicast VLAN does not VLANs to the multicast subvlan vlan-list have any sub-VLANs.
Page 60: Assigning User Ports To A Multicast Vlan
Assigning user ports to a multicast VLAN You can assign multiple user ports to a multicast VLAN in multicast VLAN view, or assign one user port to a multicast VLAN in interface view. When you perform this task, follow these guidelines: •...
Page 61: Displaying And Maintaining Multicast Vlans
Displaying and maintaining multicast VLANs Execute display commands in any view and reset commands in user view. Task Command Display information about multicast VLANs. display multicast-vlan [ vlan-id ] Display information about multicast groups display multicast-vlan group [ source-address | in multicast VLANs (in standalone mode).
Page 62 Figure 20 Network diagram Configuration procedure Configure Switch A: # Enable IP multicast routing. <SwitchA> system-view [SwitchA] multicast routing [SwitchA-mrib] quit # Create VLAN 20, and assign GigabitEthernet 1/0/2 to the VLAN. [SwitchA] vlan 20 [SwitchA-vlan20] port gigabitethernet 1/0/2 [SwitchA-vlan20] quit # Assign an IP address to VLAN-interface 20, and enable PIM-DM on the interface.
Page 63 Configure Switch B: # Enable IGMP snooping globally. <SwitchB> system-view [SwitchB] igmp-snooping [SwitchB-igmp-snooping] quit # Create VLAN 2, assign GigabitEthernet 1/0/2 to the VLAN, and enable IGMP snooping for the VLAN. [SwitchB] vlan 2 [SwitchB-vlan2] port gigabitethernet 1/0/2 [SwitchB-vlan2] igmp-snooping enable [SwitchB-vlan2] quit # Create VLAN 3, assign GigabitEthernet 1/0/3 to the VLAN, and enable IGMP snooping for the VLAN.
Page 64: Port-Based Multicast Vlan Configuration Example
[SwitchB] display multicast-vlan group Total 1 entries. Multicast VLAN 10: Total 1 entries. (0.0.0.0, 224.1.1.1) Sub-VLANs (3 in total): VLAN 2 VLAN 3 VLAN 4 The output shows that multicast group 224.1.1.1 belongs to multicast VLAN 10. Multicast VLAN 10 contains sub-VLANs VLAN 2 through VLAN 4.
Page 65 [SwitchA] multicast routing [SwitchA-mrib] quit # Create VLAN 20, and assign GigabitEthernet 1/0/2 to the VLAN. [SwitchA] vlan 20 [SwitchA-vlan20] port gigabitethernet 1/0/2 [SwitchA-vlan20] quit # Assign an IP address to VLAN-interface 20, and enable PIM-DM on the interface. [SwitchA] interface vlan-interface 20 [SwitchA-Vlan-interface20] ip address 1.1.1.2 24 [SwitchA-Vlan-interface20] pim dm [SwitchA-Vlan-interface20] quit...
Page 66 # Configure GigabitEthernet 1/0/2 as a hybrid port, and configure VLAN 2 as the PVID of the hybrid port. [SwitchB] interface gigabitethernet 1/0/2 [SwitchB-GigabitEthernet1/0/2] port link-type hybrid [SwitchB-GigabitEthernet1/0/2] port hybrid pvid vlan 2 # Assign GigabitEthernet 1/0/2 to VLAN 2 and VLAN 10 as an untagged VLAN member. [SwitchB-GigabitEthernet1/0/2] port hybrid vlan 2 untagged [SwitchB-GigabitEthernet1/0/2] port hybrid vlan 10 untagged [SwitchB-GigabitEthernet1/0/2] quit...
Page 67 # Display dynamic IGMP snooping forwarding entries on Switch B. [SwitchB] display igmp-snooping group Total 1 entries. VLAN 10: Total 1 entries. (0.0.0.0, 224.1.1.1) Host slots (0 in total): Host ports (3 in total): GE1/0/2 (00:03:23) GE1/0/3 (00:04:07) GE1/0/4 (00:04:16) The output shows that IGMP snooping maintains the user ports in multicast VLAN 10.
Page 68: 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 69 The RPF route contains the RPF interface and RPF neighbor information. If the RPF route is a unicast route or MBGP route, the outgoing interface is the RPF interface and the next hop is the RPF neighbor. If the RPF route is a static multicast route, the RPF interface and RPF neighbor are specified in the route.
Page 70: Static Multicast Routes
As shown in Figure 22, assume that unicast routes are available on the network, MBGP is not configured, and no static multicast routes have been configured on Router C. Multicast packets travel along the SPT from the multicast source to the receivers. The multicast forwarding table on Router C contains the (S, G) entry, with GigabitEthernet 1/0/2 as the incoming interface.
Page 71: Multicast Forwarding Across Unicast Subnets
Figure 24 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 72: Configuration Task List
the tunnel through unicast routers. Then, Router B strips off the unicast IP header and continues to forward the multicast data to the receiver. To use this tunnel only for multicast traffic, configure static multicast routes instead of static unicast routes at the two ends of the tunnel.
Page 73: Specifying The Longest Prefix Match Principle
To configure a static multicast route: Step Command Remarks Enter system view. system-view ip rpf-route-static [ vpn-instance vpn-instance-name ] source-address Configure a static By default, static multicast { mask-length | mask } { rpf-nbr-address multicast route. routes do not exist. | interface-type interface-number } [ preference preference ] •...
Page 74: Configuring A Multicast Forwarding Boundary
Step Command Remarks By default, load splitting is disabled. Configure multicast load load-splitting { source | splitting. source-group } This command does not take effect on BIDIR-PIM. Configuring a multicast forwarding boundary You can configure an interface as a multicast forwarding boundary for a multicast group range. The interface cannot receive or forward multicast packets for the group range.
Page 75: Enabling Multicast Forwarding Between Sub-Vlans Of A Super Vlan
Step Command Remarks Enter Layer 2 Ethernet interface interface-type interface/Layer 2 aggregate interface-number interface view. Configure a static multicast By default, static multicast MAC mac-address multicast MAC address entry. address entries do not exist. mac-address vlan vlan-id Enabling multicast forwarding between sub-VLANs of a super VLAN A super VLAN is associated with multiple sub-VLANs.
Page 76 Task Command display multicast [ vpn-instance vpn-instance-name ] Display multicast boundary information. boundary [ group-address [ mask-length | mask ] ] [ interface interface-type interface-number ] display multicast [ vpn-instance vpn-instance-name ] Display DF information (in standalone forwarding df-info [ rp-address ] [ verbose ] [ slot mode).
Page 77: Multicast Routing And Forwarding Configuration Examples
Task Command reset multicast [ vpn-instance vpn-instance-name ] routing-table { { source-address [ mask { mask-length | Clear multicast routing entries. mask } ] | group-address [ mask { mask-length | mask } ] | incoming-interface interface-type interface-number } * | all } NOTE: •...
Page 78 Configuration procedure Assign an IP address and subnet mask for each interface according to Figure 26. (Details not shown.) Configure OSPF on the switches in the PIM-DM domain. (Details not shown.) Enable IP multicast routing, and enable IGMP and PIM-DM: # On Switch B, enable IP multicast routing.
Page 79: Creating An Rpf Route
Verifying the configuration # Display RPF information for the source on Switch B. [SwitchB] display multicast rpf-info 50.1.1.100 RPF information about source 50.1.1.100: RPF interface: Vlan-interface101, RPF neighbor: 20.1.1.2 Referenced route/mask: 50.1.1.0/24 Referenced route type: multicast static Route selection rule: preference-preferred Load splitting rule: disable The output shows that: •...
Page 80 <SwitchC> system-view [SwitchC] multicast routing [SwitchC-mrib] quit # Enable IGMP on the receiver-side interface (VLAN-interface 100). [SwitchC] interface vlan-interface 100 [SwitchC-Vlan-interface100] igmp enable [SwitchC-Vlan-interface100] quit # Enable PIM-DM on VLAN-interface 101. [SwitchC] interface vlan-interface 101 [SwitchC-Vlan-interface101] pim dm [SwitchC-Vlan-interface101] quit # On Switch A, enable IP multicast routing, and enable PIM-DM on each interface.
Page 81: Multicast Forwarding Over A Gre Tunnel
Referenced route/mask: 50.1.1.0/24 Referenced route type: multicast static Route selection rule: preference-preferred Load splitting rule: disable The output shows that the RPF routes to Source 2 exist on Switch B and Switch C. The routes are the configured static routes. Multicast forwarding over a GRE tunnel Network requirements As shown in...
Page 82 [SwitchA-Tunnel1] source 20.1.1.1 [SwitchA-Tunnel1] destination 30.1.1.2 [SwitchA-Tunnel1] quit # On Switch C, create service loopback group 1, and specify the unicast tunnel service for the group. <SwitchC> system-view [SwitchC] service-loopback group 1 type tunnel # Add GigabitEthernet 1/0/3 to service loopback group 1. GigabitEthernet 1/0/3 does not belong to VLAN 200 or VLAN 102.
Page 83: Troubleshooting Multicast Routing And Forwarding
On Switch C, configure a static multicast route to the source and specify Switch A as the RPF neighbor. [SwitchC] ip rpf-route-static 50.1.1.0 24 50.1.1.1 Verifying the configuration # Send an IGMP report from Receiver to join multicast group 225.1.1.1. (Details not shown.) # Send multicast data from Source to multicast group 225.1.1.1.
Page 84 Check the type of the interface that connects the static multicast route to the RPF neighbor. If the interface is not a point-to-point interface, make sure that you specify the address of the RPF neighbor. If the problem persists, contact Hewlett Packard Enterprise Support.
Page 85: 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 86: Igmpv2 Enhancements
The hosts send unsolicited IGMP reports to the multicast groups they want to join without having to wait for the IGMP queries from the IGMP querier. 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 delay timer expires first sends an IGMP report to the multicast group G1 to announce its membership for G1.
Page 87: 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 88: Igmp Ssm Mapping
• Query message carrying the source addresses 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 89: Igmp Support For Vpns
Figure 31 IGMP SSM mapping As shown in Figure 31, on an SSM network, Host A, Host B, and Host C run IGMPv1, IGMPv2, and IGMPv3, respectively. To provide the SSM service for Host A and Host B, you must configure the IGMP SSM mapping feature on Router A.
Page 90: 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 91: Specifying An Igmp Version
Specifying an IGMP version For IGMP to operate correctly, you must 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.
Page 92: Adjusting Igmp Performance
Step Command Remarks interface interface-type Enter interface view. interface-number By default, an interface is not configured with a multicast group Configure a multicast group igmp group-policy acl-number policy. Hosts attached to the policy. [ version-number ] interface can join any multicast groups.
Page 93 • You can configure the IGMP query and response parameters either for the current port in interface view or globally for all ports in IGMP view. The configuration made in interface view takes priority over the configuration made in IGMP view. •...
Page 94: 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 Set the 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 query interval equals one quarter...
Page 95: Enabling Igmp Nsr
Enabling IGMP NSR This feature enables the switch to back up information about IGMP interfaces and IGMP forwarding entries to the standby process. After an active/standby switchover, the switch can recover the information without cooperation of other devices. This prevents the active/standby switchover from affecting the multicast service.
Page 96: Igmp Configuration Examples
Task Command display igmp [ vpn-instance vpn-instance-name ] group Display IGMP information about multicast [ group-address | interface interface-type interface-number ] groups. [ static | verbose ] display igmp[ vpn-instance vpn-instance-name ] interface Display IGMP information for interfaces. [ interface-type interface-number ] [ host] [ verbose ] display igmp [ vpn-instance vpn-instance-name ] Display IGMP SSM mappings.
Page 97 Figure 32 Network diagram Receiver PIM-DM Host A Vlan-int100 10.110.1.1/24 Switch A Host B Querier Vlan-int200 10.110.2.1/24 Receiver Host C Switch B Vlan-int200 10.110.2.2/24 Host D Switch C Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 32.
Page 98: Igmp Ssm Mapping Configuration Example
[SwitchB-Vlan-interface201] quit # On Switch C, enable IP multicast routing. <SwitchC> system-view [SwitchC] multicast routing [SwitchC-mrib] quit # Enable IGMP on VLAN-interface 200. [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] igmp enable [SwitchC-Vlan-interface200] quit # Enable PIM-DM on VLAN-interface 202. [SwitchC] interface vlan-interface 202 [SwitchC-Vlan-interface202] pim dm [SwitchC-Vlan-interface202] quit Configure a multicast group policy on Switch A so that the hosts connected to VLAN-interface...
Page 99 Configure the IGMP SSM mapping feature on Switch D so that the receiver host can receive multicast data from Source 1 and Source 3 only. Figure 33 Network diagram Source 2 Source 3 Switch B Switch C Vlan-int200 Vlan-int102 Vlan-int300 Vlan-int102 Vlan-int103 Vlan-int101...
Page 100 [SwitchD] interface vlan-interface 104 [SwitchD-Vlan-interface104] pim sm [SwitchD-Vlan-interface104] quit # On Switch A, enable IP multicast routing, and enable PIM-SM on each interface. <SwitchA> system-view [SwitchA] multicast routing [SwitchA-mrib] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] pim sm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim sm [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 104...
Page 101: Troubleshooting Igmp
Vlan-interface400(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 the PIM routing table on Switch D. [SwitchD] display pim routing-table Total 0 (*, G) entry; 2 (S, G) entry (133.133.1.1, 232.1.1.1) RP: 192.168.4.1 Protocol: pim-ssm, Flag: UpTime: 00:13:25...
Page 102: Inconsistent Membership Information On The Routers On The Same Subnet
Use the display igmp interface command to verify that the IGMP version on the interface is lower than that on the host. Use the display current-configuration interface command to verify that no ACL rule has been configured to filter out the reports sent by the host to the multicast group G. If the problem persists, contact Hewlett Packard Enterprise Support.
Page 104: 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 105 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. As shown in Figure 34, the router interface that does not have any downstream receivers initiates a prune process by sending a prune message toward the multicast source.
Page 106: Pim-Sm Overview
Figure 35 Assert mechanism As shown in Figure 35, 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 107 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 108 As shown in Figure 37, 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 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.
Page 109 As shown in Figure 38, 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. After getting the receiver information, the DR sends a join message, which travels hop by hop to the RP for the multicast group.
Page 110: Bidir-Pim Overview
Switchover to SPT In a PIM-SM domain, only one RP and one RPT provide services for a specific multicast group. Before the switchover to SPT occurs, the source-side DR encapsulates all multicast data in register messages and sends them to the RP. After receiving these register messages, the RP decapsulates them and forwards them to the receiver-side DR along the RPT.
Page 111 Neighbor discovery BIDIR-PIM uses the same neighbor discovery mechanism as PIM-SM does. For more information, "Neighbor discovery." RP discovery BIDIR-PIM uses the same RP discovery mechanism as PIM-SM does. For more information, see "RP discovery." In BIDIR-PIM, an RPF interface is the interface toward an RP, and an RPF neighbor is the address of the next hop to the RP.
Page 112 Figure 41 RPT building at the receiver side As shown in Figure 41, 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 113: Administrative Scoping Overview
Figure 42 RPT building at the multicast source side As shown in Figure 42, 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 114 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 115: Pim-Ssm Overview
Figure 44 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 44, 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 116: Relationship Among Pim Protocols
Figure 45 SPT building in PIM-SSM Host A Source Receiver Host B Server Receiver Subscribe message Multicast packets Host C As shown in Figure 45, 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 117: Pim Support For Vpns
Figure 46 Relationship among PIM protocols A receiver joins multicast group G. Is G in the SSM Is a multicast source group range? specified? Is BIDIR-PIM enabled? Does G have a PIM-SM runs for G. PIM-SSM runs for G. BIDIR-PIM RP? BIDIR-PIM runs for G.
Page 118: 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 Enabling PIM-DM Enable IP multicast routing before you configure PIM.
Page 119: 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 120: 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 C-RP, or •...
Page 121: Configuring An Rp
Step Command Remarks Return to system view. quit interface interface-type Enter interface view. interface-number Enable PIM-SM. By default, PIM-SM is disabled. pim sm Configuring an RP 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 122: Configuring A Bsr
Step Command Remarks Enter system view. system-view pim [ vpn-instance Enter PIM view. vpn-instance-name ] c-rp ip-address [ advertisement-interval adv-interval | Configure a C-RP. By default, no C-RPs exist. group-policy acl-number | holdtime hold-time | priority priority ] * (Optional.) Configure a C-RP By default, no C-RP policy crp-policy acl-number policy.
Page 123 • When an attacker controls a router on the network, the attacker can configure the router as a C-BSR to win the BSR election. Through this router, the attacker controls the advertising of RP information. When you configure a C-BSR, follow these guidelines: •...
Page 124: Configuring Multicast Source Registration
To disable BSM semantic fragmentation: Step Command Remarks Enter system view. system-view pim [ vpn-instance Enter PIM view. vpn-instance-name ] Disable BSM semantic By default, BSM semantic undo bsm-fragment enable fragmentation. fragmentation is enabled. 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.
Page 125: Configuring The Switchover To Spt
Step Command Remarks Configure the device to By default, the device calculates calculate the checksum the checksum based on the register-whole-checksum based on the entire register header of a register message. message. Configure the register register-suppression-timeout The default setting is 60 seconds. suppression time.
Page 126: Configuration Prerequisites
Tasks at a glance Remarks (Required.) Configuring an • Configuring a static RP • Configuring a C-RP You must configure a static RP, a C-RP, or both in a BIDIR-PIM domain. • (Optional.) Enabling Auto-RP listening • (Optional.) Configuring the maximum number of BIDIR-PIM RPs Configuring a BSR:...
Page 127: 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 128: Configuring A Bsr
Step Command Remarks Enter system view. system-view Enter PIM view. pim [ vpn-instance vpn-instance-name ] c-rp ip-address [ advertisement-interval Configure a C-RP to adv-interval | group-policy acl-number | provide services for By default, no C-RPs exist. holdtime hold-time | priority priority ] * BIDIR-PIM.
Page 129 The BSR election process is summarized as follows: Initially, each C-BSR regards itself as the BSR of the BIDIR-PIM domain and sends BSMs to other routers in the domain. When a C-BSR receives the BSM from another C-BSR, it compares its own priority with the priority carried in the message.
Page 130: Configuring Pim-Ssm
Step Command Remarks interface interface-type Enter interface view. interface-number Configure a PIM domain By default, an interface is not a pim bsr-boundary border. PIM domain border. Disabling BSM semantic fragmentation BSM semantic fragmentation enables a BSR to split a BSM into multiple BSM fragments (BSMFs) if the BSM exceeds the MTU.
Page 131: Enabling Pim-Sm
Enabling PIM-SM Before you configure PIM-SSM, you must enable PIM-SM, because the implementation of the SSM model is based on subsets of PIM-SM. When you deploy a PIM-SSM domain, enable PIM-SM on non-border interfaces of the routers. IMPORTANT: All the interfaces on a device must be enabled with the same PIM mode. To enable PIM-SM: Step Command...
Page 132: Configuring Common Pim Features
Configuring common PIM features Configuration task list Tasks at a glance (Optional.) Configuring a multicast source policy (Optional.) Configuring a PIM hello policy (Optional.) Configuring PIM hello message options (Optional.) Configuring common PIM timers (Optional.) Setting the maximum size of each join or prune message (Optional.) Enabling BFD for PIM (Optional.)
Page 133: Configuring Pim Hello Message Options
Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, no PIM hello policy exists. If a PIM neighbor's hello messages cannot pass the policy, Configure a PIM hello policy. pim neighbor-policy acl-number the neighbor is automatically removed when its maximum number of hello attempts is reached.
Page 134: Configuring Common Pim Timers
Configuring hello message options globally Step Command Remarks Enter system view. system-view pim [ vpn-instance Enter PIM view. vpn-instance-name ] Set the DR priority. The default setting is 1. hello-option dr-priority priority The default setting is 105 Set the neighbor lifetime. hello-option holdtime time seconds.
Page 135 for a random time before sending a hello message. This random time is in the range of 0 to the triggered hello delay. • Join/Prune interval—Interval at which a PIM router sends join/prune messages to its upstream routers for state update. •...
Page 136: Setting The Maximum Size Of Each Join Or Prune Message
Setting the maximum size of each join or prune message The loss of an oversized join or prune message might result in loss of massive information. You can set a small value for the size of each join or prune message to reduce the impact. To set the maximum size of each join or prune message: Step Command...
Page 137: Enabling Pim Nsr
Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Enable PIM passive mode By default, PIM passive mode is pim passive on the interface. disabled. Enabling PIM NSR This feature enables PIM to back up protocol state information and data, including PIM neighbor information and routes, from the active process to the standby process.
Page 138: Pim Configuration Examples
Task Command display pim [ vpn-instance vpn-instance-name ] routing-table [ group-address [ mask { mask-length | mask } ] | source-address [ mask { mask-length | mask } ] | flags flag-value | fsm | Display PIM routing entries. incoming-interface interface-type interface-number | mode mode-type | outgoing-interface { exclude | include | match } interface-type interface-number ] * Display RP information in the...
Page 139 Table 7 Interface and IP address assignment Device Interface IP address Device Interface IP address Switch A Vlan-int100 10.110.1.1/24 Switch C Vlan-int102 192.168.3.1/24 Switch A Vlan-int103 192.168.1.1/24 Switch D Vlan-int300 10.110.5.1/24 Switch B Vlan-int200 10.110.2.1/24 Switch D Vlan-int103 192.168.1.2/24 Switch B Vlan-int101 192.168.2.1/24 Switch D...
Page 140 [SwitchD] display pim interface Interface NbrCnt HelloInt DR-Pri DR-Address Vlan300 10.110.5.1 (local) Vlan103 192.168.1.2 (local) Vlan101 192.168.2.2 (local) Vlan102 192.168.3.2 (local) # Display PIM neighboring relationships on Switch D. [SwitchD] display pim neighbor Total Number of Neighbors = 3 Neighbor Interface Uptime Expires...
Page 141: Pim-Sm Non-Scoped Zone Configuration Example
Protocol: pim-dm, Flag: LOC ACT UpTime: 00:03:27 Upstream interface: Vlan-interface300 Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 2 1: Vlan-interface103 Protocol: pim-dm, UpTime: 00:03:27, Expires: - 2: Vlan-interface102 Protocol: pim-dm, UpTime: 00:03:27, Expires: - The output shows that: •...
Page 142 Figure 48 Network diagram Receiver Host A Switch A Vlan-int100 Vlan-int102 Host B Vlan-int102 Receiver Vlan-int300 Vlan-int105 Vlan-int103 Vlan-int200 Vlan-int105 Vlan-int103 Source Vlan-int104 Switch D Switch E Switch B Host C 10.110.5.100/24 Vlan-int104 Vlan-int200 PIM-SM Host D Switch C Table 8 Interface and IP address assignment Device Interface IP address...
Page 143 # Enable PIM-SM on the other interfaces. [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim sm [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] pim sm [SwitchA-Vlan-interface102] quit # Enable IP multicast routing, IGMP, and PIM-SM on Switch B and Switch C in the same way Switch A is configured.
Page 144: Pim-Sm Admin-Scoped Zone Configuration Example
[SwitchE] 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 Switch A. [SwitchA] display pim rp-info BSR RP information: Scope: non-scoped...
Page 145 Figure 49 Network diagram Table 9 Interface and IP address assignment Device Interface IP address Device Interface IP address Switch A Vlan-int100 192.168.1.1/24 Switch D Vlan-int105 10.110.5.2/24 Switch A Vlan-int101 10.110.1.1/24 Switch D Vlan-int108 10.110.7.1/24 Switch B Vlan-int200 192.168.2.1/24 Switch D Vlan-int107 10.110.8.1/24 Switch B...
Page 146 Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 49. (Details not shown.) Configure OSPF on all switches in the PIM-SM domain. (Details not shown.) Enable IP multicast routing, and enable IGMP and PIM-SM: # On Switch A, enable IP multicast routing.
Page 147 <SwitchC> system-view [SwitchC] interface vlan-interface 103 [SwitchC-Vlan-interface103] multicast boundary 239.0.0.0 8 [SwitchC-Vlan-interface103] quit [SwitchC] interface vlan-interface 106 [SwitchC-Vlan-interface106] multicast boundary 239.0.0.0 8 [SwitchC-Vlan-interface106] quit # On Switch D, configure VLAN-interface 107 as the boundary of admin-scoped zone 2. <SwitchD> system-view [SwitchD] interface vlan-interface 107 [SwitchD-Vlan-interface107] multicast boundary 239.0.0.0 8 [SwitchD-Vlan-interface107] quit...
Page 148 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 Switch D. [SwitchD] display pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:44...
Page 149: 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 Switch D. [SwitchD] display pim rp-info BSR RP information: Scope: non-scoped Group/MaskLen: 224.0.0.0/4 RP address Priority...
Page 150 Figure 50 Network diagram Loop0 Receiver 1 Receiver 2 Switch B Vlan-int200 Vlan-int102 Vlan-int102 Switch C Host A Host B Vlan-int101 Vlan-int103 BIDIR-PIM Source 1 Source 2 Vlan-int101 Vlan-int103 Vlan-int100 Vlan-int400 Switch A Switch D Table 10 Interface and IP address assignment Device Interface IP address...
Page 151 [SwitchA-pim] quit # On Switch B, enable IP multicast routing. <SwitchB> system-view [SwitchB] multicast routing [SwitchB-mrib] quit # Enable IGMP on the receiver-side interface (VLAN-interface 200). [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] igmp enable [SwitchB-Vlan-interface200] quit # Enable PIM-SM on the other interfaces. [SwitchB] interface vlan-interface 101 [SwitchB-Vlan-interface101] pim sm [SwitchB-Vlan-interface101] quit...
Page 152 [SwitchD] interface vlan-interface 103 [SwitchD-Vlan-interface103] pim sm [SwitchD-Vlan-interface103] quit # Enable BIDIR-PIM. [SwitchD] pim [SwitchD-pim] bidir-pim enable [SwitchD-pim] quit On Switch C, configure VLAN interface 102 as a C-BSR, and Loopback 0 as a C-RP for the entire BIDIR-PIM domain. [SwitchC-pim] c-bsr 10.110.2.2 [SwitchC-pim] c-rp 1.1.1.1 bidir [SwitchC-pim] quit...
Page 153: Pim-Ssm Configuration Example
Flags: 0x0 Uptime: 00:08:32 RPF interface: Vlan-interface101 List of 1 DF interfaces: 1: Vlan-interface100 # Display information about the DF for multicast forwarding on Switch B. [SwitchB] 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: Vlan-interface102...
Page 154 • Host A and Host C are multicast receivers on two stub networks. • The SSM group range is 232.1.1.0/24. • IGMPv3 runs between Switch A and N1 and between Switch B, Switch C, and N2. Figure 51 Network diagram Receiver Host A Switch A...
Page 155 # Enable IGMPv3 on the receiver-side interface (VLAN-interface 100). [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] igmp enable [SwitchA-Vlan-interface100] igmp version 3 [SwitchA-Vlan-interface100] quit # Enable PIM-SM on the other interfaces. [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim sm [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] pim sm [SwitchA-Vlan-interface102] quit # Enable IP multicast routing, IGMP, and PIM-SM on Switch B and Switch C in the same way...
Page 156: Troubleshooting Pim
1: Vlan-interface100 Protocol: igmp, UpTime: 00:13:25, Expires: 00:03:25 # Display PIM routing table information on Switch D. [SwitchD] 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: Vlan-interface300 Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information:...
Page 157: 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 158 Use the display pim neighbor command to verify that PIM neighboring relationship has been correctly established among the routers. If the problem persists, contact Hewlett Packard Enterprise Support.
Page 159: 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 160 As shown in Figure 52, 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 source-side RP creates and sends SA messages to its remote MSDP peer to notify the MSDP peer of the locally registered multicast source information.
Page 161 Figure 53 Inter-domain multicast delivery through MSDP The process of implementing PIM-SM inter-domain multicast delivery by leveraging MSDP peers is as follows: When the multicast source in PIM-SM 1 sends the first multicast packet to multicast group G, DR 1 encapsulates the data within a register message. It sends the register message to RP 1, and RP 1 obtains information about the multicast source.
Page 162 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 163 Figure 54 Anycast RP through MSDP The following describes how Anycast RP through MSDP is implemented: a. After receiving the multicast data from Source, the source-side DR registers with the closest RP (RP 1 in this example). b. After receiving the IGMP report message from the receiver, the receiver-side DR sends a join message toward the closest RP (RP 2 in this example).
Page 164: Msdp Support For Vpns
Figure 55 MSDP peer-RPF forwarding The process of peer-RPF forwarding is as follows: RP 1 creates an SA message and forwards it to its peer RP 2. RP 2 determines that RP 1 is the RP that creates the SA message because the RP address in the SA message is the same as that of RP 1.
Page 165: 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 166: 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 MSDP peer and a BGP or MBGP peer share the same interface, configure the same IP address for the MSDP peer and the BGP or MBGP peer as a best practice.
Page 167: Configuration Prerequisites
Configuration prerequisites Before you configure an MSDP peering connection, complete the following tasks: • Configure a unicast routing protocol so that all devices in the domain can interoperate at the network layer. • Configure basic MSDP features. Configuring a description for an MSDP peer This feature helps administrators easily distinguish an MSDP peer from other MSDP peers.
Page 168: Configuring Sa Message-Related Parameters
them. No attempt is made to re-establish the connection. The configuration information for the peer remains unchanged. MSDP peers periodically send keepalive messages to each other to keep a session alive. When a session is established, an MSDP peer sends a keepalive message to its peer and starts a keepalive timer and a peer hold timer.
Page 169: Enabling Multicast Data Encapsulation In Sa Messages
Enabling multicast data encapsulation in SA messages Some multicast sources send multicast data at an interval longer than the aging time of (S, G) entries. In this case, the source-side DR must encapsulate multicast data packet-by-packet in register messages and send them to the source-side RP. The source-side RP transmits the (S, G) information to the remote RP through SA messages.
Page 170: Configuring Sa Message Policies
IMPORTANT: Before you enable the router to send SA requests, make sure you disable the SA message cache mechanism. To configure SA request messages: 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 does not send an SA request...
Page 171: Configuring The Sa Cache Mechanism
Step Command Remarks Set the lower TTL threshold for multicast data packets peer peer-address minimum-ttl The default setting is 0. encapsulated in SA ttl-value messages. Configuring the SA cache mechanism The SA cache mechanism enables the router to locally cache (S, G) entries contained in SA messages.
Page 172: Msdp Configuration Examples
Task Command Reset the TCP connection with an MSDP peer and reset msdp [ vpn-instance vpn-instance-name ] clear statistics for the MSDP peer. peer [ peer-address ] reset msdp [ vpn-instance vpn-instance-name ] Clear (S, G) entries in the SA cache. sa-cache [ group-address ] Clear statistics for an MSDP peer without resetting reset msdp [ vpn-instance vpn-instance-name ]...
Page 173 Device Interface IP address Device Interface IP address Switch A Vlan-int200 10.110.3.1/24 Switch E Vlan-int105 10.110.6.1/24 Switch B Vlan-int103 10.110.1.1/24 Switch E Vlan-int102 192.168.3.2/24 Switch B Vlan-int101 192.168.1.1/24 Switch E Loop0 3.3.3.3/32 Switch B Loop0 1.1.1.1/32 Switch F Vlan-int105 10.110.6.2/24 Switch C Vlan-int104 10.110.4.1/24...
Page 174 # Configure C-BSRs and C-RPs on Switch C and Switch E in the same way Switch B is configured. (Details not shown.) Configure BGP for mutual route redistribution between BGP and OSPF: # On Switch B, configure an EBGP peer, and redistribute OSPF routes. [SwitchB] bgp 100 [SwitchB-bgp] router-id 1.1.1.1 [SwitchB-bgp] peer 192.168.1.2 as-number 200...
Page 175 Total number of peers: 1 Peers in established state: 1 Peer MsgRcvd MsgSent OutQ PrefRcv Up/Down State 192.168.1.2 200 24 00:20:07 Established # Display information about BGP peer groups on Switch C. [SwitchC] display bgp peer ipv4 BGP local router ID: 2.2.2.2 Local AS number: 1 Total number of peers: 1 Peers in established state: 1...
Page 176 192.168.1.1 Established 01:43:57 # Display brief information about MSDP peer groups on Switch E. [SwitchE] display msdp brief Configured Established Listen Connect Shutdown Disabled Peer address State Up/Down time SA count Reset count 192.168.3.1 Established 01:07:57 # Display detailed MSDP peer information on Switch B. [SwitchB] display msdp peer-status MSDP Peer 192.168.1.2;...
Page 177: Inter-As Multicast Configuration By Leveraging Static Rpf Peers
Inter-AS multicast configuration by leveraging static RPF peers Network requirements As shown in Figure • 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 at least one multicast source or receiver.
Page 178 Device Interface IP address Device Interface IP address Switch B Vlan-int101 10.110.1.2/24 Switch F Vlan-int106 10.110.6.1/24 Switch B Vlan-int100 192.168.1.1/24 Switch F Vlan-int104 10.110.4.2/24 Switch B Vlan-int103 10.110.3.1/24 Switch G Vlan-int106 10.110.6.2/24 Switch C Vlan-int102 10.110.2.2/24 Switch G Vlan-int400 192.168.4.1/24 Switch C Vlan-int200 192.168.2.1/24...
Page 179 # On Switch B, configure an EBGP peer, and redistribute OSPF routing information. [SwitchB] bgp 100 [SwitchB-bgp] router-id 1.1.1.2 [SwitchB-bgp] peer 10.110.3.2 as-number 200 [SwitchB-bgp] address-family ipv4 unicast [SwitchB-bgp-ipv4] peer 10.110.3.2 enable [SwitchB-bgp-ipv4] import-route ospf 1 [SwitchB-bgp-ipv4]quit [SwitchB-bgp] quit # On Switch D, configure an EBGP peer, and redistribute OSPF routing information. [SwitchD] bgp 200 [SwitchD-bgp] router-id 2.2.2.2 [SwitchD-bgp] peer 10.110.3.1 as-number 100...
Page 180 # On Switch F, redistribute BGP routing information into OSPF. [SwitchF] ospf 1 [SwitchF-ospf-1] import-route bgp [SwitchF-ospf-1] quit Configure MSDP peers and static RPF peers: # On Switch A, configure Switch D and Switch G as the MSDP peers and static RPF peers. [SwitchA] ip prefix-list list-dg permit 10.110.0.0 16 greater-equal 16 less-equal 32 [SwitchA] msdp [SwitchA-msdp] peer 10.110.3.2 connect-interface vlan-interface 101...
Page 181: Anycast Rp Configuration
[SwitchG] display msdp brief Configured Established Listen Connect Shutdown Disabled Peer address State Up/Down time SA count Reset count 10.110.2.1 Established 00:16:40 # Verify that receivers in PIM-SM 1 and PIM-SM 3 can receive the multicast data from Source 1 and Source 2 to a multicast group.
Page 182 Device Interface IP address Device Interface IP address Switch B Vlan-int101 192.168.1.1/24 Switch D Loop10 4.4.4.4/32 Switch B Loop0 1.1.1.1/32 Switch D Loop20 10.1.1.1/32 Switch B Loop10 3.3.3.3/32 Switch E Vlan-int400 10.110.6.1/24 Switch B Loop20 10.1.1.1/32 Switch E Vlan-int104 10.110.4.2/24 Configuration procedure Assign an IP address and subnet mask to each interface according to Figure...
Page 183 # Configure an MSDP peer on Loopback 0 of Switch B. [SwitchB] msdp [SwitchB-msdp] originating-rp loopback 0 [SwitchB-msdp] peer 2.2.2.2 connect-interface loopback 0 [SwitchB-msdp] quit # Configure an MSDP peer on Loopback 0 of Switch D. [SwitchD] msdp [SwitchD-msdp] originating-rp loopback 0 [SwitchD-msdp] peer 1.1.1.1 connect-interface loopback 0 [SwitchD-msdp] quit Verifying the configuration...
Page 184 (10.110.5.100, 225.1.1.1) RP: 10.1.1.1 (local) Protocol: pim-sm, Flag: SPT 2MSDP ACT UpTime: 00:46:28 Upstream interface: Vlan-interface103 Upstream neighbor: 10.110.2.2 RPF prime neighbor: 10.110.2.2 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: pim-sm, UpTime: - , Expires: The output shows that Switch 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.
Page 185: Sa Message Filtering Configuration
SA message filtering configuration Network requirements As shown in Figure • OSPF runs within and among the PIM-SM domains to provide unicast routing. • Set up an MSDP peering relationship between Switch A and Switch C and between Switch C and Switch D.
Page 186 Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 59. (Details not shown.) Configure OSPF on the switches in the PIM-SM domains. (Details not shown.) Enable IP multicast routing, IGMP, and PIM-SM, and configure PIM domain borders: # On Switch A, enable IP multicast routing.
Page 187 [SwitchA] msdp [SwitchA-msdp] peer 192.168.1.2 connect-interface vlan-interface 101 [SwitchA-msdp] quit # Configure MSDP peers on Switch C. [SwitchC] msdp [SwitchC-msdp] peer 192.168.1.1 connect-interface vlan-interface 101 [SwitchC-msdp] peer 10.110.5.2 connect-interface vlan-interface 104 [SwitchC-msdp] quit # Configure an MSDP peer on Switch D. [SwitchD] msdp [SwitchD-msdp] peer 10.110.5.1 connect-interface vlan-interface 104 [SwitchD-msdp] quit...
Page 188: Troubleshooting Msdp
MSDP Total Source-Active Cache - 4 entries Matched 4 entries Source Group Origin RP Uptime Expires 10.110.3.100 226.1.1.0 1.1.1.1 00:32:53 00:05:07 10.110.3.100 226.1.1.1 1.1.1.1 00:32:53 00:05:07 10.110.3.100 226.1.1.2 1.1.1.1 00:32:53 00:05:07 10.110.3.100 226.1.1.3 1.1.1.1 00:32:53 00:05:07 Troubleshooting MSDP This section describes common MSDP problems and how to troubleshoot them. MSDP peers stay in disabled state Symptom The configured MSDP peers stay in disabled state.
Page 189 Solution To resolve the problem: Use the display ip routing-table command to verify that the unicast route between the routers is reachable. Verify that a unicast route is available between the two routers that will establish an MSDP peering relationship. Verify the configuration of the originating-rp command.
Page 190: 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 191: Md Vpn Overview
Figure 61 Multicast in multiple VPN instances Through multicast VPN, multicast data of VPN A for a multicast group can only arrive at receiver hosts in Site 1, Site 3, and Site 5 of VPN A. The stream is multicast in these sites and on the public network.
Page 192 Table 16 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 193 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 194: 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 195: 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 196 Default-MDT establishment in a PIM-SM network Figure 65 Default-MDT establishment in a PIM-SM network As shown in Figure 65, PIM-SM is enabled on the network, and all the PE devices support VPN instance A. The process of establishing a default-MDT is as follows: PE 1 initiates a join to the public network RP by specifying the multicast group address as the default-group address in the join message.
Page 197: Default-Mdt-Based Delivery
Default-MDT establishment in a PIM-SSM network Figure 66 Default-MDT establishment in a PIM-SSM network As shown in Figure 66, PIM-SSM runs on the public network, and all the PE devices support VPN instance A. The process of establishing a default-MDT is as follows: PE 1, PE 2, and PE 3 exchange MDT route information (including BGP interface address and the default-group address) through BGP.
Page 198 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 relationships.
Page 199 The default-MDT forwards the multicast data packet (11.1.2.1, 239.1.1.1) to the public network instance on all the PE devices. After receiving this packet, every PE device decapsulates it to get the original join message to be sent to the VPN RP. Then, each PE device examines the VPN RP address in the join message.
Page 200: Mdt Switchover
Figure 68 Multicast data packet delivery A VPN multicast data packet is delivered across the public network as follows: Source sends a VPN multicast data packet (192.1.1.1, 225.1.1.1) to CE 1. CE 1 forwards the VPN multicast data packet along an SPT to PE 1, and the VPN instance on PE 1 examines the MVRF.
Page 201: 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 202 • 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, the following ways are available to implement inter-AS MD VPN: •...
Page 203: Multicast Vpn Configuration Task List
• PEs in different ASs establish a multihop MP-EBGP session to advertise VPN-IPv4 routes to each other. Figure 70 MD VPN inter-AS option C To implement MD VPN inter-AS option C, only one MD needs to be created for the two ASs. Multicast data is transmitted between the two ASs through the MD.
Page 204: Configuring Md Vpn
• The PIM mode on the MTI must be the same as the PIM mode running on the VPN instance to which the MTI belongs. When at least one interface on the VPN instance is enabled with PIM, the MTI is enabled with PIM accordingly. When all interfaces on the VPN instance are PIM-disabled, PIM is also disabled on the MTI.
Page 205: Creating An Md For A Vpn Instance
Creating an MD for a VPN instance You can create one or multiple MDs to provide services for their associated VPN instances on the PE device. When you create an MD for a VPN instance, the system automatically create MTI interfaces and bind them with the VPN instance.
Page 206: Configuring Mdt Switchover Parameters
Step Command Remarks multicast-domain vpn-instance Enter MD view. vpn-instance-name Specify the MD source By default, an MD source source interface-type interface. interface does not exist. interface-number Configuring MDT switchover parameters To decrease traffic interruption caused by frequent default-MDT to data-MDT switchovers, you can specify a data-delay period.
Page 207: Configuration Prerequisites
Configuration prerequisites Before you configure BGP MDT, complete the following tasks: • Configure MPLS L3VPN on the public network. • Configure basic BGP functions on the public network. • Configure the PIM-SSM on the public network. • Determine the IP addresses of the MDT peers. •...
Page 208: Displaying And Maintaining Multicast Vpn
Perform this task on PE devices. For more information about the commands in this task, see Layer 3—IP Routing Command Reference. To configure a BGP MDT route reflector: Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter BGP IPv4 MDT address-family ipv4 mdt address family view.
Page 209: Multicast Vpn Configuration Examples
Multicast VPN configuration examples This section provides examples of configuring multicast VPN on switches. Intra-AS MD VPN configuration example Network requirements Item Network requirements • In VPN instance a, S 1 is a multicast source, and R 1, R 2 and R 3 are receivers. •...
Page 210 Figure 71 Network diagram Table 17 Interface and IP address assignment Device Interface IP address Device Interface IP address — 10.110.7.2/24 PE 3 Vlan-int19 192.168.8.1/24 — 10.110.8.2/24 PE 3 Vlan-int17 10.110.5.1/24 — 10.110.1.2/24 PE 3 Vlan-int18 10.110.6.1/24 Loop1 — 10.110.9.2/24 PE 3 1.1.1.3/32 Loop2...
Page 211 # 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 MPLS LSR ID, and enable the LDP capability. [PE1] mpls lsr-id 1.1.1.1 [PE1] mpls ldp [PE1-ldp] quit # Create service group 1 and specify the multicast tunnel service for the group.
Page 212 # Bind VLAN-interface 11 with VPN instance a, assign an IP address to VLAN-interface 11, and enable PIM-SM on the interface. [PE1] interface vlan-interface 11 [PE1-Vlan-interface11] ip binding vpn-instance a [PE1-Vlan-interface11] ip address 10.110.2.1 24 [PE1-Vlan-interface11] pim sm [PE1-Vlan-interface11] quit # Assign an IP address to Loopback 1, and enable PIM-SM on the interface.
Page 213 [PE2] mpls lsr-id 1.1.1.2 [PE2] mpls ldp [PE2-ldp] quit # Create service group 1 and specify the multicast tunnel service for the group. [PE2] service-loopback group 1 type multicast-tunnel # Assign GigabitEthernet 1/0/5 to service group 1. [PE2] interface gigabitethernet 1/0/5 [PE2-GigabitEthernet1/0/5] port link-mode bridge [PE2-GigabitEthernet1/0/5] port service-loopback group 1 [PE2-GigabitEthernet1/0/5] quit...
Page 214 [PE2-Vlan-interface15] pim sm [PE2-Vlan-interface15] mpls enable [PE2-Vlan-interface15] mpls ldp enable [PE2-Vlan-interface15] quit # Bind VLAN-interface 13 with VPN instance b, assign an IP address to VLAN-interface 13, and enable PIM-SM on the interface. [PE2] interface vlan-interface 13 [PE2-Vlan-interface13] ip binding vpn-instance b [PE2-Vlan-interface13] ip address 10.110.3.1 24 [PE2-Vlan-interface13] pim sm [PE2-Vlan-interface13] quit...
Page 215 [PE2-ospf-1-area-0.0.0.0] network 1.1.1.2 0.0.0.0 [PE2-ospf-1-area-0.0.0.0] network 192.168.7.0 0.0.0.255 [PE2-ospf-1-area-0.0.0.0] quit [PE2-ospf-1] quit # Configure RIP. [PE2] rip 2 vpn-instance a [PE2-rip-2] network 10.110.3.0 0.0.0.255 [PE2-rip-2] import-route bgp [PE2-rip-2] quit [PE2] rip 3 vpn-instance b [PE2-rip-3] network 10.110.4.0 0.0.0.255 [PE2-rip-3] import-route bgp [PE2-rip-3] return Configure PE 3: # Configure a global router ID, and enable IP multicast routing on the public network.
Page 216 # Create a VPN instance named b and configure an RD and route target attributes for the instance. [PE3] ip vpn-instance b [PE3-vpn-instance-b] route-distinguisher 200:1 [PE3-vpn-instance-b] vpn-target 200:1 export-extcommunity [PE3-vpn-instance-b] vpn-target 200:1 import-extcommunity [PE3-vpn-instance-b] quit # Enable IP multicast routing for VPN instance b. [PE3] multicast routing vpn-instance b [PE3-mrib-b] quit # Create an MD for VPN instance b, and specify the default-group, the MD source interface,...
Page 217 [PE3-LoopBack2] pim sm [PE3-LoopBack2] quit # Configure Loopback 2 as a C-BSR and a C-RP for VPN instance b. [PE3] pim vpn-instance b [PE3-pim-b] c-bsr 33.33.33.33 [PE3-pim-b] c-rp 33.33.33.33 [PE3-pim-b] quit # Configure BGP. [PE3] bgp 100 [PE3-bgp] group vpn-g internal [PE3-bgp] peer vpn-g connect-interface loopback 1 [PE3-bgp] peer 1.1.1.1 group vpn-g [PE3-bgp] peer 1.1.1.2 group vpn-g...
Page 218 <P> system-view [P] multicast routing [P-mrib] quit # Configure an MPLS LSR ID, and enable the LDP capability. [P] mpls lsr-id 2.2.2.2 [P] mpls ldp [P-ldp] quit # Assign an IP address to VLAN-interface 12, and enable PIM-SM, MPLS capability, and LDP capability on the interface.
Page 219 Configure CE a1: # Enable IP multicast routing. <CEa1> system-view [CEa1] multicast routing [CEa1-mrib] quit # Assign an IP address to VLAN-interface 10, and enable PIM-SM on the interface. [CEa1] interface vlan-interface 10 [CEa1-Vlan-interface10] ip address 10.110.7.1 24 [CEa1-Vlan-interface10] pim sm [CEa1-Vlan-interface10] quit # Assign an IP address to VLAN-interface 11, and enable PIM-SM on the interface.
Page 220 [CEa2-Vlan-interface40] quit # Assign an IP address to VLAN-interface 14, and enable PIM-SM on the interface. [CEa2] interface vlan-interface 14 [CEa2-Vlan-interface14] ip address 10.110.4.2 24 [CEa2-Vlan-interface14] pim sm [CEa2-Vlan-interface14] quit # Assign an IP address to VLAN-interface 16, and enable PIM-SM on the interface. [CEa2] interface vlan-interface 16 [CEa2-Vlan-interface16] ip address 10.110.12.1 24 [CEa2-Vlan-interface16] pim sm...
Page 221 # Configure RIP. [CEa3] rip 2 [CEa3-rip-2] network 10.110.5.0 0.0.0.255 [CEa3-rip-2] network 10.110.10.0 0.0.0.255 [CEa3-rip-2] network 10.110.12.0 0.0.0.255 Configure CE b2: # Enable IP multicast routing. <CEb2> system-view [CEb2] multicast routing [CEb2-mrib] quit # Assign an IP address to VLAN-interface 60, and enable IGMP on the interface. [CEb2] interface vlan-interface 60 [CEb2-Vlan-interface60] ip address 10.110.11.1 24 [CEb2-Vlan-interface60] igmp enable...
Page 222: Md Vpn Inter-As Option C Configuration Example
MD VPN inter-AS option C configuration example Network requirements Item Network requirements • In VPN instance a, S 1 is a multicast source, and R 2 is a receiver. • In VPN instance b, S 2 is a multicast source, and R 1 is a receiver. •...
Page 223 Figure 72 Network diagram Table 18 Interface and IP address assignment Device Interface IP address Device Interface IP address — 10.11.5.2/24 — 10.11.8.2/24 — 10.11.6.2/24 — 10.11.7.2/24 PE 1 Vlan-int2 10.10.1.1/24 PE 3 Vlan-int4 10.10.2.1/24 PE 1 Vlan-int11 10.11.1.1/24 PE 3 Vlan-int3 192.168.1.2/24 PE 1...
Page 224 [PE1] router id 1.1.1.1 [PE1] multicast routing [PE1-mrib] quit # Configure an MPLS LSR ID, and enable the LDP capability. [PE1] mpls lsr-id 1.1.1.1 [PE1] mpls ldp [PE1-ldp] quit # Create service group 1 and specify the multicast tunnel service for the group. [PE1] service-loopback group 1 type multicast-tunnel # Assign GigabitEthernet 1/0/5 to service group 1.
Page 225 # Assign an IP address to VLAN-interface 2, and enable PIM-SM, MPLS capability, and LDP capability on the interface. [PE1] interface vlan-interface 2 [PE1-Vlan-interface2] ip address 10.10.1.1 24 [PE1-Vlan-interface2] pim sm [PE1-Vlan-interface2] mpls enable [PE1-Vlan-interface2] mpls ldp enable [PE1-Vlan-interface2] quit # Bind VLAN-interface 11 with VPN instance a, assign an IP address to VLAN-interface 11, and enable PIM-SM on the interface.
Page 226 [PE1–bgp] address-family ipv4 [PE1-bgp-ipv4] peer pe1-pe2 enable [PE1-bgp-ipv4] peer pe1-pe2 label-route-capability [PE1-bgp-ipv4] quit [PE1–bgp] address-family vpnv4 [PE1–bgp-vpnv4] peer pe1-pe4 enable [PE1–bgp-vpnv4] quit [PE1–bgp] quit # Configure OSPF. [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 227 [PE2-Vlan-interface2] pim sm [PE2-Vlan-interface2] mpls enable [PE2-Vlan-interface2] mpls ldp enable [PE2-Vlan-interface2] quit # Assign an IP address to VLAN-interface 3, and enable PIM-SM and MPLS on the interface. [PE2] interface vlan-interface 3 [PE2-Vlan-interface3] ip address 192.168.1.1 24 [PE2-Vlan-interface3] pim sm [PE2-Vlan-interface3] mpls enable [PE2-Vlan-interface3] quit # Assign an IP address to Loopback 1, and enable PIM-SM on the interface.
Page 228 [PE2-bgp-ipv4] peer pe2-pe3 enable [PE2-bgp-ipv4] peer pe2-pe3 route-policy map1 export [PE2-bgp-ipv4] peer pe2-pe3 label-route-capability [PE2-bgp-ipv4] import-route ospf 1 [PE2-bgp-ipv4] quit [PE2–bgp] quit # Configure OSPF. [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 a routing policy.
Page 229 [PE3] interface vlan-interface 3 [PE3-Vlan-interface3] ip address 192.168.1.2 24 [PE3-Vlan-interface3] pim sm [PE3-Vlan-interface3] mpls enable [PE3-Vlan-interface3] quit # Assign an IP address to Loopback 1, and enable PIM-SM on the interface. [PE3] interface loopback 1 [PE3-LoopBack1] ip address 1.1.1.3 32 [PE3-LoopBack1] pim sm [PE3-LoopBack1] quit # Assign an IP address to Loopback 2, and enable PIM-SM on the interface.
Page 230 [PE3–bgp] quit # Configure OSPF. [PE3] ospf 1 [PE3-ospf-1] area 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 1.1.1.3 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 22.22.22.22 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 10.10.2.0 0.0.0.255 [PE3-ospf-1-area-0.0.0.0] quit [PE3-ospf-1] quit # Configure a routing policy. [PE3] route-policy map1 permit node 10 [PE3-route-policy-map1-10] apply mpls-label [PE3-route-policy-map1-10] quit [PE3] route-policy map2 permit node 10 [PE3-route-policy-map2-10] if-match mpls-label...
Page 231 [PE4-md-a] source loopback 1 [PE4-md-a] data-group 225.1.1.0 28 [PE4-md-a] quit # Create a VPN instance named b and configure an RD and route target attributes for the instance. [PE4] ip vpn-instance b [PE4-vpn-instance-b] route-distinguisher 200:1 [PE4-vpn-instance-b] vpn-target 200:1 export-extcommunity [PE4-vpn-instance-b] vpn-target 200:1 import-extcommunity [PE4-vpn-instance-b] quit # Enable IP multicast routing for VPN instance b.
Page 232 [PE4] bgp 200 [PE4-bgp] group pe4-pe3 internal [PE4-bgp] peer pe4-pe3 connect-interface loopback 1 [PE4-bgp] peer 1.1.1.3 group pe4-pe3 [PE4-bgp] group pe4-pe1 external [PE4-bgp] peer pe4-pe1 as-number 100 [PE4-bgp] peer pe4-pe1 ebgp-max-hop 255 [PE4-bgp] peer pe4-pe1 connect-interface loopback 1 [PE4-bgp] peer 1.1.1.1 group pe4-pe1 [PE4–bgp] ip vpn-instance a [PE4-bgp-a] address-family ipv4 [PE4-bgp-ipv4-a] import-route ospf 2...
Page 233 Configure CE a1: # Enable IP multicast routing. <CEa1> system-view [CEa1] multicast routing [CEa1-mrib] quit # Assign an IP address to VLAN-interface 10, and enable PIM-SM on the interface. [CEa1] interface vlan-interface 10 [CEa1-Vlan-interface10] ip address 10.11.5.1 24 [CEa1-Vlan-interface10] pim sm [CEa1-Vlan-interface10] quit # Assign an IP address to VLAN-interface 11, and enable PIM-SM on the interface.
Page 234 [CEb1-Vlan-interface12] quit # Configure OSPF. [CEb1] ospf 1 [CEb1-ospf-1] area 0.0.0.0 [CEb1-ospf-1-area-0.0.0.0] network 10.11.2.0 0.0.0.255 [CEb1-ospf-1-area-0.0.0.0] network 10.11.6.0 0.0.0.255 [CEb1-ospf-1-area-0.0.0.0] quit [CEb1-ospf-1] quit Configure CE a2: # Enable IP multicast routing. <CEa2> system-view [CEa2] multicast routing [CEa2-mrib] quit # Assign an IP address to VLAN-interface 30, and enable IGMP on the interface. [CEa2] interface vlan-interface 30 [CEa2-Vlan-interface30] ip address 10.11.7.1 24 [CEa2-Vlan-interface30] igmp enable...
Page 235: Troubleshooting Md Vpn
[CEb2-LoopBack1] ip address 3.3.3.3 32 [CEb2-LoopBack1] pim sm [CEb2-LoopBack1] quit # Configure Loopback 1 as a C-BSR and a C-RP. [CEb2] pim [CEb2-pim] c-bsr 3.3.3.3 [CEb2-pim] c-rp 3.3.3.3 [CEb2-pim] quit # Configure OSPF. [CEb2] ospf 1 [CEb2-ospf-1] area 0.0.0.0 [CEb2-ospf-1-area-0.0.0.0] network 3.3.3.3 0.0.0.0 [CEb2-ospf-1-area-0.0.0.0] network 10.11.4.0 0.0.0.255 [CEb2-ospf-1-area-0.0.0.0] network 10.11.8.0 0.0.0.255 [CEb2-ospf-1-area-0.0.0.0] quit...
Page 236: An Mvrf Cannot Be Created
The same PIM mode is running on all the interfaces of the same VPN instance on different PE devices and on all the interfaces of the P router. Use the display ip routing-table command to verify that a unicast route exists from the VPN instance on the local PE device to the same VPN instance on each remote PE device.
Page 237: 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 73, when MLD snooping is not enabled, the Layer 2 switch floods IPv6 multicast...
Page 238 Figure 74 MLD snooping ports Router ports On an MLD snooping Layer 2 device, the ports toward Layer 3 multicast device are called router ports. In Figure 74, GigabitEthernet 1/0/1 of Switch A and GigabitEthernet 1/0/1 of Switch B are router ports.
Page 239: 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 switch 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 240: Protocols And Standards
• If a match is found but the receiving port is not an outgoing interface in the forwarding entry, the Layer 2 device discards the MLD done message. • If a match is found and the receiving port is not the only outgoing interface in the forwarding entry, the Layer 2 device performs the following actions: Discards the MLD done message.
Page 241: Mld Snooping Configuration Task List
MLD snooping configuration task list Tasks at a glance Configuring basic MLD snooping features: • (Required.) Enabling MLD snooping • (Optional.) Specifying an MLD snooping version • (Optional.) Setting the maximum number of MLD snooping forwarding entries • (Optional.) Setting the MLD last listener query interval Configuring MLD snooping port features: •...
Page 242: Specifying An Mld Snooping Version
Enabling MLD snooping for the specified VLANs Step Command Remarks Enter system view. system-view Enable MLD snooping By default, MLD snooping is globally and enter mld-snooping globally disabled. MLD-snooping view. Enable MLD snooping for By default, MLD snooping is enable vlan vlan-list the specified VLANs.
Page 243: Setting The Maximum Number Of Mld Snooping Forwarding Entries
Specifying an MLD snooping version for a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Specify an MLD snooping mld-snooping version The default setting is 1. version for the VLAN. version-number Setting the maximum number of MLD snooping forwarding entries You can set the maximum number of MLD snooping forwarding entries, including dynamic entries and static entries.
Page 244: Configuring Mld Snooping Port Features
Step Command Remarks Set the MLD last listener The default setting is 1 last-listener-query-interval interval query interval globally. second. Setting the MLD last listener query interval in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Set the MLD last listener The default setting is 1 mld-snooping...
Page 245: Configuring Static Ports
Setting the aging timers for dynamic ports in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Set the aging timer for The default setting is 260 mld-snooping dynamic router ports in the seconds. router-aging-time interval VLAN.
Page 246: Enabling Fast-Leave Processing
The version of MLD running on the simulated member host is the same as the version of MLD snooping running on the port. The port ages out in the same way as a dynamic member port. Configuration procedure To configure a port as a simulated member host: Step Command Remarks...
Page 247: Disabling A Port From Becoming A Dynamic Router Port
Disabling a port from becoming a dynamic router port A receiver host might send an MLD general query or IPv6 PIM hello message for testing purposes. In this case, the following problems might exist: • The router port that receives the MLD general query or IPv6 PIM hello message becomes a dynamic router port.
Page 248: Configuring Parameters For Mld General Queries And Responses
Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Enable the MLD snooping By default, the MLD snooping mld-snooping querier querier. querier is disabled. Configuring parameters for MLD general queries and responses CAUTION: To avoid mistakenly deleting IPv6 multicast group members, make sure the MLD general query interval is greater than the maximum response time for MLD general queries.
Page 249: Configuring Parameters For Mld Messages
Configuring parameters for MLD messages This section describes how to configure parameters for MLD messages. Configuration prerequisites Before you configure parameters for MLD messages, complete the following tasks: • Enable MLD snooping for the VLAN. • Determine the source IPv6 address of MLD general queries. •...
Page 250: Setting The 802.1P Priority For Mld Messages
Step Command Remarks By default, the source IPv6 address of MLD multicast-address-specific queries is one of the following: • The source address of MLD general queries if the MLD snooping querier has received MLD general queries. Configure the source IPv6 •...
Page 251: Configuring Mld Snooping Policies
Setting the 802.1p priority for MLD messages in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Set the 802.1p priority for mld-snooping dot1p-priority MLD messages in the The default setting is 0. priority-number VLAN. Configuring MLD snooping policies Before you configure MLD snooping policies, complete the following tasks: •...
Page 252: Enabling Ipv6 Multicast Source Port Filtering
Enabling IPv6 multicast source port filtering This feature enables the switch to discard all IPv6 multicast data packets and to accept IPv6 multicast protocol packets. You can enable this feature on ports that connect to only IPv6 multicast receivers. You can enable multicast source port filtering for the specified ports in MLD-snooping view or for a port in interface view.
Page 253: Enabling Mld Report Suppression
Enabling dropping unknown IPv6 multicast data globally Step Command Remarks Enter system view. system-view Enter MLD-snooping view. mld-snooping By default, this feature is Enable dropping unknown disabled. Unknown IPv6 multicast drop-unknown IPv6 multicast data globally. data is flooded in the VLAN to which the data belongs.
Page 254: Enabling Ipv6 Multicast Group Replacement
Configuration procedure To set the maximum number of IPv6 multicast groups on a port: Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface-type interface view or Layer 2 interface-number aggregate interface view. Set the maximum number of The default setting is mld-snooping group-limit limit IPv6 multicast groups on the...
Page 255 Task Command Display information about Layer 2 display ipv6 l2-multicast ip [ group ipv6-group-address | source IPv6 multicast groups (in standalone ipv6-source-address ] * [ vlan vlan-id ] [ slot slot-number ] mode). display ipv6 l2-multicast ip [ group ipv6-group-address | source Display information about Layer 2 ipv6-source-address ] * [ vlan vlan-id ] [ chassis chassis-number IPv6 multicast groups (in IRF mode).
Page 256: Mld Snooping Configuration Examples
Task Command Clear dynamic router port reset mld-snooping router-port { all | vlan vlan-id } information. Clear statistics for the MLD messages learned through MLD reset mld-snooping statistics snooping. MLD snooping configuration examples IPv6 group policy and simulated joining configuration example Network requirements As shown in...
Page 257 [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 # Enable IPv6 PIM-DM on GigabitEthernet 1/0/2. [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] ipv6 pim dm [RouterA-GigabitEthernet1/0/2] quit Configure Switch A: # Enable MLD snooping globally. <SwitchA>...
Page 258: 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 IPv6 multicast group FF1E::101 through the member ports GigabitEthernet 1/0/4 and GigabitEthernet 1/0/3 on Switch A, respectively. •...
Page 259 Figure 76 Network diagram Configuration procedure Assign an IPv6 address and prefix length to each interface according to Figure 76. (Details not shown.) Configure 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 260 [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 Configure Switch B: # Enable MLD snooping globally. <SwitchB> system-view [SwitchB] mld-snooping [SwitchB-mld-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 MLD snooping for VLAN 100.
Page 261: Mld Snooping Querier Configuration Example
VLAN 100: Total 1 entries). (::, FF1E::101) 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 IPv6 multicast group FF1E::101. MLD snooping querier configuration example Network requirements As shown in...
Page 262 # 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, and enable dropping unknown IPv6 multicast data packets for VLAN 100. [SwitchA-vlan100] mld-snooping enable [SwitchA-vlan100] mld-snooping drop-unknown # Configure Switch A as the MLD snooping querier.
Page 263: Troubleshooting Mld Snooping
# Enable MLD snooping, and enable dropping unknown IPv6 multicast data packets for VLAN 100. [SwitchD-vlan100] mld-snooping enable [SwitchD-vlan100] mld-snooping drop-unknown [SwitchD-vlan100] quit Verifying the configuration # Display statistics for MLD messages learned through MLD snooping on Switch B. [SwitchB] display mld-snooping statistics Received MLD general queries: Received MLDv1 specific queries: Received MLDv1 reports:...
Page 264 Use the display acl ipv6 command to verify that the configured IPv6 ACL meets the IPv6 multicast group policy requirements. Use the display this command in MLD-snooping view or in a corresponding interface view to verify that the correct IPv6 multicast group policy has been correctly applied. If the applied IPv6 multicast group policy is not correct, use the group-policy or mld-snooping group-policy command to apply the correct IPv6 multicast group policy.
Page 265: Configuring Ipv6 Pim Snooping
Configuring IPv6 PIM snooping Overview IPv6 PIM snooping runs on Layer 2 devices. It works with MLD snooping to analyze received IPv6 PIM messages, and adds the ports that are interested in specific multicast data to an IPv6 PIM snooping routing entry. In this way, the multicast data can be forwarded to only the ports that are interested in the data.
Page 266: Configuring Ipv6 Pim Snooping
b. Floods all other types of received IPv6 PIM messages except PIM hello messages in the VLAN. c. Forwards all multicast data to all router ports in the VLAN. Each IPv6 PIM-capable router in the VLAN, whether interested in the multicast data or not, can receive all multicast data and all IPv6 PIM messages except IPv6 PIM hello messages.
Page 267: Displaying And Maintaining Ipv6 Pim Snooping
Step Command Remarks The default setting is 105 (Optional.) Set the aging seconds. time for global neighbor ipv6 pim-snooping ports on the new active graceful-restart A global neighbor port is a Layer MPU after an neighbor-aging-time interval 2 aggregate interface that acts as active/standby switchover.
Page 268 • Router A, Router B, Router C, and Router D run IPv6 PIM-SM. GigabitEthernet 1/0/2 on Router A acts as a C-BSR and a C-RP. Configure MLD snooping and IPv6 PIM snooping on Switch A. Then, Switch A forwards IPv6 PIM protocol packets and IPv6 multicast data packets to only the routers that connect to receivers.
Page 269 [RouterB-GigabitEthernet1/0/1] ipv6 pim sm [RouterB-GigabitEthernet1/0/1] quit [RouterB] interface gigabitethernet 1/0/2 [RouterB-GigabitEthernet1/0/2] ipv6 pim sm [RouterB-GigabitEthernet1/0/2] quit Configure Router C: # Enable IPv6 multicast routing. <RouterC> system-view [RouterC] ipv6 multicast routing [RouterC-mrib6] quit # Enable MLD on GigabitEthernet 1/0/1. [RouterC] interface gigabitethernet 1/0/1 [RouterC-GigabitEthernet1/0/1] mld enable [RouterC-GigabitEthernet1/0/1] quit # Enable IPv6 PIM-SM on GigabitEthernet 1/0/2.
Page 270 VLAN 100: Total 4 neighbors. FE80::1 Slots (0 in total): Ports (1 in total): GE1/0/1 (00:32:43) FE80::2 Slots (0 in total): Ports (1 in total): GE1/0/2 (00:32:43) FE80::3 Slots (0 in total): Ports (1 in total): GE1/0/3 (00:32:43) FE80::4 Slots (0 in total): Ports (1 in total): GE1/0/4 (00:32:43)
Page 271: Troubleshooting Ipv6 Pim Snooping
• Switch A will forward the multicast data intended for IPv6 multicast group FF2E::101 to only Router D. Troubleshooting IPv6 PIM snooping This section describes common IPv6 PIM snooping problems and how to troubleshoot them. IPv6 PIM snooping does not work on a Layer 2 device Symptom IPv6 PIM snooping does not work on a Layer 2 device.
Page 272: Configuring Ipv6 Multicast Vlans
Configuring IPv6 multicast VLANs Overview As shown in Figure 80, Host A, Host B, and Host C are in different VLANs and the same IPv6 multicast group. When Switch A (Layer 3 device) receives IPv6 multicast data for that group, it forwards three copies of the data to Switch B (Layer 2 device).
Page 273 Figure 81 Sub-VLAN-based multicast VLAN MLD snooping manages router ports in the IPv6 multicast VLAN and member ports in each sub-VLAN. When Switch A receives IPv6 multicast data from the IPv6 multicast source, it sends only one copy of the IPv6 multicast data to the IPv6 multicast VLAN on Switch B. Then, Switch B sends a separate copy to each sub-VLAN of the IPv6 multicast VLAN.
Page 274: Ipv6 Multicast Vlan Configuration Task List
IPv6 multicast VLAN configuration task list Tasks at a glance (Required.) Perform one of the following tasks: • Configuring a sub-VLAN-based IPv6 multicast VLAN • Configuring a port-based IPv6 multicast VLAN: Configuring user port attributes Assigning user ports to an IPv6 multicast VLAN (Optional.) Setting the maximum number of IPv6 multicast VLAN forwarding entries When you configure the IPv6 multicast VLANs, follow these guidelines:...
Page 275: Configuring A Port-Based Ipv6 Multicast Vlan
Step Command Remarks Enter system view. system-view Configure a VLAN as an By default, a VLAN is not an IPv6 ipv6 multicast-vlan IPv6 multicast VLAN and multicast VLAN. vlan-id enter its view. Assign the specified VLANs By default, an IPv6 multicast VLAN does to the IPv6 multicast VLAN subvlan vlan-list not have any sub-VLANs.
Page 276: Assigning User Ports To An Ipv6 Multicast Vlan
Assigning user ports to an IPv6 multicast VLAN You must configure a VLAN as an IPv6 multicast VLAN, and then assign the desired user ports to the IPv6 multicast VLAN. You can assign multiple user ports to an IPv6 multicast VLAN in IPv6 multicast VLAN view, or assign a user port to an IPv6 multicast VLAN in interface view.
Page 277: Displaying And Maintaining Ipv6 Multicast Vlans
Step Command Remarks By default, no limit is placed on Set the maximum number of the maximum number of IPv6 ipv6 multicast-vlan entry-limit IPv6 multicast VLAN multicast VLAN forwarding limit forwarding entries. entries. Displaying and maintaining IPv6 multicast VLANs Execute display commands in any view and reset commands in user view. Task Command Display information about IPv6...
Page 278 Figure 83 Network diagram Configuration procedure Configure Switch A: # Enable IPv6 multicast routing. <SwitchA> system-view [SwitchA] ipv6 multicast routing [SwitchA-mrib6] quit # Create VLAN 20, and assign GigabitEthernet 1/0/2 to the VLAN. [SwitchA] vlan 20 [SwitchA-vlan20] port gigabitethernet 1/0/2 [SwitchA-vlan20] quit # Assign an IPv6 address to VLAN-interface 20, and enable IPv6 PIM-DM on the interface.
Page 279 Configure Switch B: # Enable MLD snooping globally. <SwitchB> system-view [SwitchB] mld-snooping [SwitchB-mld-snooping] quit # Create VLAN 2, assign GigabitEthernet 1/0/2 to the VLAN, and enable MLD snooping for the VLAN. [SwitchB] vlan 2 [SwitchB-vlan2] port gigabitethernet 1/0/2 [SwitchB-vlan2] mld-snooping enable [SwitchB-vlan2] quit # Create VLAN 3, assign GigabitEthernet 1/0/3 to the VLAN, and enable MLD snooping for the VLAN.
Page 280: Port-Based Ipv6 Multicast Vlan Configuration Example
[SwitchB] display ipv6 multicast-vlan group Total 1 entries. IPv6 multicast VLAN 10: Total 1 entries. (::, FF1E::101) Sub-VLANs (3 in total): VLAN 2 VLAN 3 VLAN 4 The output shows that IPv6 multicast group FF1E::101 belongs to IPv6 multicast VLAN 10. IPv6 multicast VLAN 10 contains sub-VLANs VLAN 2 through VLAN 4.
Page 281 [SwitchA] ipv6 multicast routing [SwitchA-mrib6] quit # Create VLAN 20, and assign GigabitEthernet 1/0/2 to the VLAN. [SwitchA] vlan 20 [SwitchA-vlan20] port gigabitethernet 1/0/2 [SwitchA-vlan20] quit # Assign an IPv6 address to VLAN-interface 20, and enable IPv6 PIM-DM on the interface. [SwitchA] interface vlan-interface 20 [SwitchA-Vlan-interface20] ipv6 address 1::2 64 [SwitchA-Vlan-interface20] ipv6 pim dm...
Page 282 # Configure GigabitEthernet 1/0/2 as a hybrid port, and configure VLAN 2 as the PVID of the hybrid port. [SwitchB] interface gigabitethernet 1/0/2 [SwitchB-GigabitEthernet1/0/2] port link-type hybrid [SwitchB-GigabitEthernet1/0/2] port hybrid pvid vlan 2 # Assign GigabitEthernet 1/0/2 to VLAN 2 and VLAN 10 as an untagged VLAN member. [SwitchB-GigabitEthernet1/0/2] port hybrid vlan 2 untagged [SwitchB-GigabitEthernet1/0/2] port hybrid vlan 10 untagged [SwitchB-GigabitEthernet1/0/2] quit...
Page 283 # Display dynamic MLD snooping forwarding entries on Switch B. [SwitchB] display mld-snooping group Total 1 entries. VLAN 10: Total 1 entries. (::, FF1E::101) Host slots (0 in total): Host ports (3 in total): GE1/0/2 (00:03:23) GE1/0/3 (00:04:07) GE1/0/4 (00:04:16) The output shows that MLD snooping maintains the user ports in IPv6 multicast VLAN 10.
Page 284: 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 285 The router checks whether the packet arrived at the RPF interface. If yes, the RPF check succeeds and the packet is forwarded. If not, the RPF check fails and the packet is discarded. RPF check implementation in IPv6 multicast Implementing an RPF check on each received IPv6 multicast packet would heavily burden the router. The use of an IPv6 multicast forwarding table is the solution to this issue.
Page 286: Ipv6 Multicast Forwarding Across Ipv6 Unicast Subnets
• If an IPv6 multicast packet arrives at Router C on GigabitEthernet 1/0/2, the receiving interface is the incoming interface of the (S, G) entry. Router C forwards the packet out of all outgoing interfaces. • If an IPv6 multicast packet arrives at Router C on GigabitEthernet 1/0/1, the receiving interface is not the incoming interface of the (S, G) entry.
Page 287: Configuring Ipv6 Multicast Routing And Forwarding
To enable IPv6 multicast routing: Step Command Remarks Enter system view. system-view Enable IPv6 multicast ipv6 multicast routing By default, IPv6 multicast routing routing and enter IPv6 MRIB [ vpn-instance is disabled. view. vpn-instance-name ] Configuring IPv6 multicast routing and forwarding Before you configure IPv6 multicast routing and forwarding, complete the following tasks: •...
Page 288: Configuring An Ipv6 Multicast Forwarding Boundary
Configuring an IPv6 multicast forwarding boundary You can configure an interface as an IPv6 multicast forwarding boundary for an IPv6 multicast group range. The interface cannot receive or forward IPv6 multicast packets for the groups in the range. To configure an IPv6 multicast forwarding boundary: Step Command Remarks...
Page 289: Enabling Ipv6 Multicast Forwarding Between Sub-Vlans Of A Super Vlan
Enabling IPv6 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 290 Task Command display ipv6 multicast [ vpn-instance vpn-instance-name ] Display DF information (in IRF mode). forwarding df-info [ ipv6-rp-address ] [ verbose ] [ chassis chassis-number slot slot-number ] Display statistics for IPv6 multicast display ipv6 multicast [ vpn-instance vpn-instance-name ] forwarding events (in standalone mode).
Page 291: Ipv6 Multicast Forwarding Over A Gre Tunnel Configuration Example
IPv6 multicast forwarding over a GRE tunnel configuration example Network requirements As shown in Figure • IPv6 multicast routing and IPv6 PIM-DM are enabled on Switch A and Switch C. • Switch B does not support IPv6 multicast. • Switch A, Switch B, and Switch C run OSPFv3. The source-side interface (VLAN-interface 100) on Switch A does not run OSPFv3.
Page 292 [SwitchA-Tunnel1] source 2001::1 [SwitchA-Tunnel1] destination 3001::2 [SwitchA-Tunnel1] quit # On Switch C, create service loopback group 1, and specify the unicast tunnel service for the group. <SwitchC> system-view [SwitchC] service-loopback group 1 type tunnel # Assign GigabitEthernet 1/0/3 to service loopback group 1. (GigabitEthernet 1/0/3 does not belong to VLAN 200 or VLAN 102.) [SwitchC] interface gigabitethernet 1/0/3 [SwitchC-GigabitEthernet1/0/3] port service-loopback group 1...
Page 293: Verifying The Configuration
On Switch C, configure a static IPv6 route with destination address 1001::1/64 and outgoing interface Tunnel 1. [SwitchC] ipv6 route-static 1001::1 64 tunnel 0 Verifying the configuration # Send an MLD report from Receiver to join IPv6 multicast group FF1E::101. (Details not shown.) # Send IPv6 multicast data from Source to IPv6 multicast group FF1E::101.
Page 294: 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 295 Joining an IPv6 multicast group Figure 88 MLD queries and reports As shown in Figure 88, Host B and Host C want to receive the IPv6 multicast data addressed to IPv6 multicast group G1. Host A wants to receive the IPv6 multicast data addressed to G2. The following process describes how the hosts join the IPv6 multicast groups and how the MLD querier (Router B Figure 88) maintains the IPv6 multicast group memberships:...
Page 296: 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 297: Mld Ssm Mapping
Enhancement in MLD state A multicast router that is running MLDv2 maintains the multicast address state for each multicast address on each attached subnet. The multicast address state consists of the following information: • Filter mode—Router keeps tracing the Include or Exclude state. •...
Page 298: Mld Support For Vpns
MLD support for VPNs MLD maintains group memberships on a per-interface base. After receiving an MLD message on an interface, MLD processes the packet within the VPN to which the interface belongs. MLD only communicates with other multicast protocols within the same VPN instance. Protocols and standards •...
Page 299: Specifying An Mld Version
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 Enable MLD. By default, MLD is disabled. mld enable Specifying an MLD version For MLD to operate correctly, you must specify the same MLD version for all routers on the same...
Page 300: Configuring An Ipv6 Multicast Group Policy
Configuring an IPv6 multicast group policy This feature enables an interface to filter MLD reports by using an ACL that specifies IPv6 multicast groups and the optional sources. It is used to control the IPv6 multicast groups that the hosts attached to an interface can join.
Page 301 maximum response time specified in the MLD query. When the timer value decreases to 0, the receiver sends an MLD report to the group. • MLD other querier present timer—Lifetime for an MLD querier after a non-querier receives an MLD general query. If the non-querier does not receive a new query from the querier when this timer expires, the non-querier considers that the querier has failed and starts a new querier election.
Page 302: Enabling Fast-Leave Processing
Configuring the MLD query and response parameters on an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Set the MLD 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 mld startup-query-interval...
Page 303: Configuring Mld Ssm Mappings
information without cooperation of other devices. This prevents an active/standby switchover from affecting the multicast service. To enable MLD NSR: Step Command Remarks Enter system view. system-view By default, MLD NSR is Enable MLD NSR. mld non-stop-routing disabled. Configuring MLD SSM mappings This feature enables the switch to provide SSM services for MLDv1 receiver hosts.
Page 304: Mld Configuration Examples
Task Command display mld [ vpn-instance vpn-instance-name ] Display MLD information for interfaces. interface [ interface-type interface-number ] [ proxy ] [ verbose ] display mld [ vpn-instance vpn-instance-name ] Display MLD SSM mappings. ssm-mapping ipv6-group-address reset mld [ vpn-instance vpn-instance-name ] group { all | interface interface-type interface-number { all | Clear dynamic MLD group entries.
Page 305 Figure 91 Network diagram Receiver IPv6 PIM-DM Host A Vlan-int100 3000::12/64 Switch A Host B Querier Vlan-int200 3001::10/64 Receiver Host C Switch B Vlan-int200 3001::12/64 Host D Switch C Configuration procedure Assign an IPv6 address and prefix length to each interface according to Figure 91.
Page 306: Mld Ssm Mapping Configuration Example
[SwitchB-Vlan-interface201] quit # On Switch C, enable IPv6 multicast routing. <SwitchC> system-view [SwitchC] ipv6 multicast routing [SwitchC-mrib6] quit # Enable MLD on VLAN-interface 200. [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] mld enable [SwitchC-Vlan-interface200] quit # Enable IPv6 PIM-DM on VLAN-interface 202. [SwitchC] interface vlan-interface 202 [SwitchC-Vlan-interface202] ipv6 pim dm [SwitchC-Vlan-interface202] quit...
Page 307 Configure the MLD SSM mapping feature on Router D so that the receiver host will receive IPv6 multicast data only from Source 1 and Source 3. Figure 92 Network diagram Source 2 Source 3 Switch B Switch C Vlan-int200 Vlan-int102 Vlan-int300 Vlan-int102 Vlan-int103...
Page 308 [SwitchD-Vlan-interface104] quit # On Switch A, enable IPv6 multicast routing. <SwitchA> system-view [SwitchA] ipv6 multicast routing [SwitchA-mrib6] quit # Enable IPv6 PIM-SM on each interface. [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] ipv6 pim sm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] ipv6 pim sm [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 104 [SwitchA-Vlan-interface104] ipv6 pim sm...
Page 309: Troubleshooting Mld
MLD groups in total: 1 Vlan-interface400(FE80::101): MLD groups reported in total: 1 Group address: FF3E::101 Last reporter: FE80::1 Uptime: 00:02:04 Expires: Off # Display the IPv6 PIM routing table for the public network on Switch D. [SwitchD] display ipv6 pim routing-table Total 0 (*, G) entry;...
Page 310: Inconsistent Membership Information On The Routers On The Same Subnet
Use the display current-configuration command to verify that the IPv6 multicast routing is enabled. If it is not enabled, use the ipv6 multicast routing command in system view to enable IPv6 multicast routing. In addition, verify that MLD is enabled on the associated interfaces. Use the display mld interface command to verify that the MLD version on the interface is lower than that on the host.
Page 311: 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 312 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 313: Ipv6 Pim-Sm Overview
Figure 94 Assert mechanism As shown in Figure 94, 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 314 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 95 DR election As shown in Figure 95, the DR election process is as follows:...
Page 315 As shown in Figure 96, 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 316 RPT building Figure 97 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 97, 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 317 Figure 98 IPv6 multicast source registration As shown in Figure 98, 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 318: Ipv6 Bidir-Pim Overview
For more information about the switchover to SPT initiated by the RP, see "IPv6 multicast source registration." • The receiver-side DR initiates the switchover to SPT: The receiver-side DR periodically checks the forwarding rate of the multicast packets that the IPv6 multicast source S sends to the IPv6 multicast group G.
Page 319 Figure 99 DF election Router E Router D Router B Router C Ethernet DF election message IPv6 Multicast packets Router A Source As shown in Figure 99, without the DF election mechanism, both Router B and Router C can receive IPv6 multicast packets from Route A.
Page 320 Figure 100 RPT building at the receiver side As shown in Figure 100, 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 321: Ipv6 Administrative Scoping Overview
Figure 101 RPT building at the IPv6 multicast source side As shown in Figure 101, 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 322 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 323: Ipv6 Pim-Ssm Overview
Figure 103 IPv6 multicast address format An IPv6 admin-scoped zone with a larger scope field value contains an IPv6 admin-scoped zone with a smaller scope field value. The zone with the scope field value of E is the IPv6 global-scoped zone. Table 20 lists the possible values of the scope field.
Page 324: 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 104 SPT building in IPv6 PIM-SSM Host A Source...
Page 325: Ipv6 Pim Support For Vpns
Figure 105 Relationship among IPv6 PIM protocols A receiver joins an IPv6 multicast group G. Is G in the SSM Is an IPv6 multicast group range? source specified? Is IPv6 BIDIR-PIM enabled? Does G have an IPv6 IPv6 PIM-SM runs for G. IPv6 PIM-SSM runs for G.
Page 326: 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 327: 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 328: 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 329: Configuring An Rp
Step Command Remarks interface interface-type Enter interface view. interface-number By default, IPv6 PIM-SM is Enable IPv6 PIM-SM. ipv6 pim sm disabled. Configuring an RP An RP can provide services for multiple or all IPv6 multicast groups. However, only one RP at a time can forward IPv6 multicast traffic for an IPv6 multicast group.
Page 330: Configuring A Bsr
Step Command Remarks Enter system view. system-view ipv6 pim [ vpn-instance Enter IPv6 PIM view. vpn-instance-name ] c-rp ipv6-address [ advertisement-interval adv-interval | Configure a C-RP. { group-policy acl6-number | scope By default, no C-RPs exist. scope-id } | holdtime hold-time | priority priority ] * (Optional.) Configure a C-RP By default, no C-RP policy...
Page 331 Step Command Remarks Enter system view. system-view ipv6 pim [ 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 ] * (Optional.) Configure a BSR By default, no BSR policy exists.
Page 332: Configuring Ipv6 Multicast Source Registration
Configuring IPv6 multicast source registration An IPv6 PIM register policy enables an RP to filter register messages by using an ACL that specifies the IPv6 multicast sources and groups. The policy limits the multicast groups to which the RP is designated.
Page 333: Configuring Ipv6 Bidir-Pim
Step Command Remarks By default, the switch immediately spt-switch-threshold Configure the switchover to triggers the switchover to SPT { immediacy | infinity } SPT. after receiving the first multicast [ group-policy acl6-number ] packet. Configuring IPv6 BIDIR-PIM This section describes how to configure IPv6 BIDIR-PIM. Configuration restrictions and guidelines When you configure IPv6 BIDIR-PIM, follow these restrictions and guidelines: •...
Page 334: Configuring An Rp
To enable IPv6 BIDIR-PIM: Step Command Remarks Enter system view. system-view ipv6 multicast routing Enable IPv6 multicast By default, IPv6 multicast routing [ vpn-instance routing and enter MRIB view. is disabled. vpn-instance-name ] Return to system view. quit interface interface-type Enter interface view.
Page 335 Step Command Remarks Configure a static RP for static-rp ipv6-rp-address bidir By default, no static RPs exist. IPv6 BIDIR-PIM. [ acl6-number | preferred ] * Configuring a C-RP IMPORTANT: • When you configure a C-RP, reserve a large bandwidth between the C-RP and other devices in the IPv6 BIDIR-PIM domain.
Page 336: Configuring A Bsr
Step Command Remarks ipv6 pim [ vpn-instance Enter IPv6 PIM view. vpn-instance-name ] Set the maximum number of The default setting is 6. bidir-rp-limit limit RPs. 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.
Page 337: Configuring Ipv6 Pim-Ssm
Step Command Remarks c-bsr ipv6-address [ scope Configure a C-BSR. scope-id ] [ hash-length By default, no C-BSRs exist. hash-length | priority priority ] * (Optional.) Configure a BSR By default, no BSR policy exists. bsr-policy acl6-number policy. Configuring an IPv6 PIM domain border An IPv6 PIM domain border determines the transmission boundary of bootstrap messages.
Page 338: Ipv6 Pim-Ssm Configuration Task List
IPv6 PIM-SSM configuration task list Tasks at a glance (Required.) Enabling IPv6 PIM-SM (Optional.) Configuring the IPv6 SSM group range (Optional.) Configuring common IPv6 PIM features Configuration prerequisites Before you configure IPv6 PIM-SSM, configure an IPv6 unicast IPv6 routing protocol so that all devices in the domain can interoperate at the network layer.
Page 339: Configuring Common Ipv6 Pim Features
• When a member of an IPv6 multicast group in the IPv6 SSM group range sends an MLDv1 report message, the device does not trigger a (*, G) join. Configuration procedure To configure an IPv6 SSM group range: Step Command Remarks Enter system view.
Page 340: Configuring An Ipv6 Pim Hello Policy
Step Command Remarks ipv6 pim [ vpn-instance Enter IPv6 PIM view. vpn-instance-name ] Configure an IPv6 multicast By default, no IPv6 multicast source-policy acl6-number source policy. source policy exists. Configuring an IPv6 PIM hello policy This feature enables the device to filter IPv6 PIM hello messages by using an ACL that specifies the packet source addresses.
Page 341 override interval). If interface receives a join message before the timer expires, the router does not prune the interface. Otherwise, the router prunes the interface. If you enable neighbor tracking on an upstream router, this router can track the states of the downstream nodes for which the joined state holdtime timer has not expired.
Page 342: Configuring Common Ipv6 Pim Timers
Step Command Remarks Enable dropping hello By default, an interface accepts messages without the hello message without the ipv6 pim require-genid Generation ID option. Generation ID option. Configuring common IPv6 PIM timers IMPORTANT: To prevent the upstream neighbors from aging out, you must configure the interval for sending join/prune messages to be less than the joined/pruned state holdtime timer.
Page 343: Setting The Maximum Size Of Each Join Or Prune Message
Step Command Remarks By default, the joined/pruned Set the joined/pruned state state holdtime timer is 210 holdtime join-prune time holdtime. seconds. Set the IPv6 multicast By default, the IPv6 multicast source-lifetime time source lifetime. source lifetime is 210 seconds. Configuring common IPv6 PIM timers on an interface Step Command Remarks...
Page 344: Enabling Ipv6 Pim Passive Mode
Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, BFD is disabled for Enable BFD for IPv6 PIM. ipv6 pim bfd enable IPv6 PIM. Enabling IPv6 PIM passive mode To guard against IPv6 PIM hello spoofing, you can enable IPv6 PIM passive mode on an interface which is directly connected to user hosts.
Page 345: Displaying And Maintaining Ipv6 Pim
Displaying and maintaining IPv6 PIM Execute display commands in any view. Task Command Display register-tunnel interface display interface [ register-tunnel [ interface-number ] ] [ brief information. [ description| down ] ] Display BSR information in the display ipv6 pim [ vpn-instance vpn-instance-name ] bsr-info IPv6 PIM-SM domain.
Page 346 Figure 106 Network diagram Table 21 Interface and IPv6 address assignment Device Interface IPv6 address Device Interface IPv6 address Switch A Vlan-int100 1001::1/64 Switch D Vlan-int300 4001::1/64 Switch A Vlan-int103 1002::1/64 Switch D Vlan-int103 1002::2/64 Switch B Vlan-int200 2001::1/64 Switch D Vlan-int101 2002::2/64 Switch B...
Page 347 [SwitchA-Vlan-interface103] ipv6 pim dm [SwitchA-Vlan-interface103] quit # Enable IPv6 multicast routing, MLD, and IPv6 PIM-DM on Switch B and Switch C in the same way Switch A is configured. (Details not shown.) # On Switch D, enable IPv6 multicast routing, and enable IPv6 PIM-DM on each interface. <SwitchD>...
Page 348: Ipv6 Pim-Sm Non-Scoped Zone Configuration Example
(*, FF0E::101) Protocol: pim-dm, Flag: WC UpTime: 00:01:24 Upstream interface: NULL Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: mld, UpTime: 00:01:20, Expires: - (4001::100, FF0E::101) Protocol: pim-dm, Flag: ACT UpTime: 00:01:20 Upstream interface: Vlan-interface103 Upstream neighbor: 1002::2...
Page 349 • VOD streams are sent to receiver hosts in multicast. The receivers of different subnets form stub networks, and at least one receiver host exist in each stub network. The entire IPv6 PIM-SM domain contains only one BSR. • Host A and Host C are multicast receivers in the stub networks N1 and N2. •...
Page 350 # On Switch A, enable IPv6 multicast routing. <SwitchA> system-view [SwitchA] ipv6 multicast routing [SwitchA-mrib6] quit # Enable MLD on the receiver-side interface (VLAN-interface 100). [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] mld enable [SwitchA-Vlan-interface100] quit # Enable IPv6 PIM-SM on other interfaces. [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] ipv6 pim sm [SwitchA-Vlan-interface101] quit...
Page 351: Ipv6 Pim-Sm Admin-Scoped Zone Configuration Example
[SwitchA] display ipv6 pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:44 Elected BSR address: 1003::2 Priority: 64 Hash mask length: 126 Uptime: 00:11:18 # Display BSR information on Switch E. [SwitchE] display ipv6 pim bsr-info Scope: non-scoped State: Elected Bootstrap timer: 00:01:44 Elected BSR address: 1003::2 Priority: 64...
Page 352 global-scoped zone, and it is designated to the IPv6 multicast groups with the scope field value of 14. • MLDv1 runs between Switch A, Switch E, Switch I, and the receivers that directly connect to them, respectively. Figure 108 Network diagram Table 23 Interface and IPv6 address assignment Device Interface...
Page 353 Device Interface IPv6 address Device Interface IPv6 address Switch E Vlan-int400 7001::1/64 Configuration procedure Assign an IPv6 address and prefix length to each interface according to Table 23. (Details not shown.) Configure OSPFv3 on all switches in the IPv6 PIM-SM domain. (Details not shown.) Enable IPv6 multicast routing, MLD, and IPv6 PIM-SM: # On Switch A, enable IPv6 multicast routing.
Page 354 [SwitchB-Vlan-interface103] ipv6 multicast boundary scope 4 [SwitchB-Vlan-interface103] quit # On Switch C, configure VLAN-interface 103 and VLAN-interface 106 as the boundaries of IPv6 admin-scoped zone 2. <SwitchC> system-view [SwitchC] interface vlan-interface 103 [SwitchC-Vlan-interface103] ipv6 multicast boundary scope 4 [SwitchC-Vlan-interface103] quit [SwitchC] interface vlan-interface 106 [SwitchC-Vlan-interface106] ipv6 multicast boundary scope 4 [SwitchC-Vlan-interface106] quit...
Page 355 State: Elected Bootstrap timer: 00:00:06 Elected BSR address: 1002::2 Priority: 64 Hash mask length: 126 Uptime: 00:04:54 Candidate BSR address: 1002::2 Priority: 64 Hash mask length: 126 # Display BSR information on Switch D. [SwitchD] display ipv6 pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:25 Elected BSR address: 8001::1...
Page 356 Scope: 4 Group/MaskLen: FF04::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FF14::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FF24::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FF34::/16 RP address Priority HoldTime...
Page 357: Ipv6 Bidir-Pim Configuration Example
1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FF04::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 # Display RP information on Switch F. [SwitchF] display ipv6 pim rp-info BSR RP information: Scope: non-scoped Group/MaskLen: FF00::/8 RP address Priority HoldTime Uptime Expires 8001::1 (local) 00:10:28...
Page 358 Device Interface IPv6 address Device Interface IPv6 address Switch B Vlan-int102 2002::1/64 Source 2 — 5001::2/64 Switch C Vlan-int102 2002::2/64 Receiver 1 — 2001::2/64 Switch C Vlan-int103 3001::1/64 Receiver 2 — 4001::2/64 Switch C Loop0 6001::1/128 Configuration procedure Assign an IPv6 address and prefix length to each interface according to Table 24.
Page 359 <SwitchC> system-view [SwitchC] ipv6 multicast routing [SwitchC-mrib6] quit [SwitchC] interface vlan-interface 102 [SwitchC-Vlan-interface102] ipv6 pim sm [SwitchC-Vlan-interface102] quit [SwitchC] interface vlan-interface 103 [SwitchC-Vlan-interface103] ipv6 pim sm [SwitchC-Vlan-interface103] quit [SwitchC] interface loopback 0 [SwitchC-LoopBack0] ipv6 pim sm [SwitchC-LoopBack0] quit [SwitchC] ipv6 pim [SwitchC-pim6] bidir-pim enable # On Switch D, enable IPv6 multicast routing.
Page 360 FE38:4E01 # Display the DF information of IPv6 BIDIR-PIM on Switch B. [SwitchB] display ipv6 pim df-info RP address: 6001::1 Interface State DF-Pref DF-Metric DF-Uptime DF-Address Vlan200 01:24:09 FE80::200:5EFF: FE71:2801 (local) Vlan101 01:24:09 FE80::20F:E2FF: FE38:4E01 (local) Vlan102 Lose 01:23:12 FE80::20F:E2FF: FE15:5601 # Display the DF information of IPv6 BIDIR-PIM on Switch C.
Page 361: Ipv6 Pim-Ssm Configuration Example
RPF interface: Vlan-interface102 List of 2 DF interfaces: 1: Vlan-interface101 2: Vlan-interface200 # Display information about the DF for IPv6 multicast forwarding on Switch C. [SwitchC] display ipv6 multicast forwarding df-info Total 1 RP, 1 matched 00001. RP address: 6001::1 Flags: 0x0 Uptime: 00:07:21 RPF interface: LoopBack0...
Page 362 Figure 110 Network diagram Table 25 Interface and IPv6 address assignment Device Interface IPv6 address Device Interface IPv6 address Switch A Vlan-int100 1001::1/64 Switch D Vlan-int300 4001::1/64 Switch A Vlan-int101 1002::1/64 Switch D Vlan-int101 1002::2/64 Switch A Vlan-int102 1003::1/64 Switch D Vlan-int105 4002::1/64 Switch B...
Page 363 [SwitchA-Vlan-interface100] quit # Enable IPv6 PIM-SM on the other interfaces. [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] ipv6 pim sm [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] ipv6 pim sm [SwitchA-Vlan-interface102] quit # Enable IPv6 multicast routing, MLD, and IPv6 PIM-SM on Switch B and Switch C in the same way Switch A is configured.
Page 364: Troubleshooting Ipv6 Pim
Total 0 (*, G) entry; 1 (S, G) entry (4001::100, FF3E::101) Protocol: pim-ssm, Flag: LOC UpTime: 00:08:02 Upstream interface: Vlan-interface300 Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface105 Protocol: pim-ssm, UpTime: 00:08:02, Expires: 00:03:25 The output shows that switches on the SPT path (Switch A and Switch D) have generated the correct (S, G) entries.
Page 365: An Rp Cannot Join An Spt In Ipv6 Pim-Sm
Solution To resolve the problem: Use display current-configuration to verify the IPv6 multicast forwarding boundary settings. Use ipv6 multicast boundary to change the multicast forwarding boundary settings to make the IPv6 multicast packet able to cross the boundary. Use display current-configuration to verify the IPv6 multicast source policy. Change the ACL rule defined in the source-policy command so that the source/group address of the IPv6 multicast data can pass ACL filtering.
Page 366: 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 Bold text represents commands and keywords that you enter literally as shown. Boldface Italic text represents arguments that you replace with actual values.
Page 367: 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 368: 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 369: 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 370 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 371: Index
Index multicast VPN inter-AS option A, Numerics IP multicast model), IGMP snooping message 802.1p priority, assert MLD snooping message 802.1p priority, IPv6 PIM-DM, IPv6 PIM-SM, PIM-DM, IGMP snooping policy, PIM-SM, MLD snooping policy, assigning address port-based multicast VLAN user port, IP multicast, 5, attribute IP multicast MD VPN default group,...
Page 372 RP configuration, RP discovery, multicast MD VPN PIM neighbor relationships, RP max, changing static RP configuration, multicast routing RPF route, bootstrap router. See checking border IPv6 multicast RPF check implementation, IPv6 BIDIR-PIM domain border, IPv6 multicast RPF check mechanism, IPv6 PIM-SM domain border, IPv6 multicast RPF check process, IPv6 PIM-SM zone border router, multicast RPF check mechanism,...
Page 373 IPv6 BIDIR-PIM C-BSR, MLD NSR, IPv6 BIDIR-PIM C-RP, MLD query/response parameter, IPv6 BIDIR-PIM domain border, MLD query/response parameter (global), IPv6 BIDIR-PIM RP, MLD query/response parameter (on interface), IPv6 BIDIR-PIM static RP, MLD snooping, 227, 231, IPv6 multicast forwarding boundary, MLD snooping basic features, IPv6 multicast forwarding/GRE tunnel configuration, MLD snooping fast leave processing,...
Page 374 multicast routing longest prefix match connection principle, MSDP peer configuration, multicast routing+forwarding, 58, 62, 62, controlling multicast routing+forwarding MAC address IGMPv3 host control capability, static entry, MSDP peering connection, multicast static route, creating multicast VLAN, 46, 48, MD VPN instance, multicast VPN, 180, 193, multicast routing RPF route, multicast VPN BGP MDT,...
Page 375 IPv6 BIDIR-PIM BSM semantic IPv6 PIM-SM SPT switchover, fragmentation, PIM BFD enable, IPv6 PIM-SM BSM semantic PIM hello message DR_Priority, fragmentation, PIM passive mode enable, MLD snooping dynamic router port PIM-SM DR election, change, PIM-SM RPT building, PIM-SM BSM semantic fragmentation, PIM-SM SPT switchover, discovering PIM-SSM election,...
Page 376 IP multicast routing, multicast VPN default MDT establishment in PIM-DM network, IPv6 BIDIR-PIM, multicast VPN default MDT establishment in IPv6 multicast group replacement PIM-SM network, (global), Ethernet IPv6 multicast group replacement (port), BIDIR-PIM configuration, IPv6 multicast routing, IP multicast MAC address, IPv6 multicast sub-VLAN forwarding, IP multicast overview, IPv6 PIM BFD,...
Page 377 IPv6 BIDIR-PIM, multicast VLAN forwarding entries max, IPv6 BIDIR-PIM bidirectional RPT multicast VPN BGP MDT configuration, building, multicast VPN configuration, 180, 193, IPv6 BIDIR-PIM BSR, multicast VPN data-MDT to default-MDT IPv6 BIDIR-PIM configuration, 323, switch, IPv6 BIDIR-PIM DF election, multicast VPN default-MDT establishment, IPv6 BIDIR-PIM RP, multicast VPN default-MDT to data-MDT switch,...
Page 378 PIM-SSM group range, query/response parameter configuration restrictions, snooping. See IGMP snooping hello SSM mapping, IPv6 PIM hello message options, SSM mapping configuration, 85, IPv6 PIM policy, static group member configuration, PIM common timer configuration (global), static group member configuration restrictions, PIM common timer configuration (on sub-VLAN-based multicast VLAN interface),...
Page 379 multicast groups on port restrictions, Internet multicast source port filtering, Group Management Protocol. Use IGMP policy configuration, IP addressing port, IGMP snooping message source IP address, port feature configuration, IP multicast address, 5, protocols and standards, IP multicast packet forwarding, querier configuration, 22, MLD snooping message source IP address, querier enable,...
Page 380 IGMP snooping protocols and standards, IPv6 PIM-SM non-scoped zone configuration, IGMP snooping querier, IPv6 PIM-SM RP, IGMP snooping querier configuration, IPv6 PIM-SM SPT switchover, 307, IGMP snooping report suppression, IPv6 PIM-SSM configuration, 327, IGMP snooping source port filtering, IPv6 PIM-SSM DR election, IGMP snooping static port, IPv6 PIM-SSM group range, IGMP snooping static port configuration,...
Page 381 MLD snooping unknown IPv6 multicast data SSM model, drop, transmission technique, MLD snooping version, transmission techniques, MLD SSM mapping, troubleshooting IGMP, MLD SSM mapping configuration, 296, troubleshooting IGMP inconsistent membership MLD static group member, information, MLD version specification, troubleshooting IGMP no membership information on router, MLD VPN support, troubleshooting IGMP snooping,...
Page 382 multicast MLD SSM mapping IPv6 multicast VLAN configuration, configuration, 262, 264, multicast MLDv1 IPv6 group joining, display, multicast MLDv1 IPv6 group leaving, forwarding entries max, multicast VLAN. See IPv6 multicast VLAN maintain, PIM. See IPv6 PIM port –based implementation, PIM snooping. See port-based configuration, 265, PIM-DM.
Page 383 IPv6 PIM passive mode enable, joining IPv6 PIM protocol relationships, IPv6 PIM join/prune message max size, neighbor discovery, MLDv1 IPv6 group joining, protocols and standards, PIM join/prune message max size, SPT building, state refresh enable, Layer 2 state refresh parameters, IP multicast protocols and standards, IPv6 PIM-SM IPv6 PIM snooping configuration, 255, 256,...
Page 384 IPv6 multicast VLAN, MSDP SA message filtering configuration, IPv6 PIM snooping, MSDP SA message multicast data encapsulation, MLD, MSDP SA message originating RP, MLD snooping, MSDP SA message policy, MSDP, MSDP SA message-related parameters, multicast routing+forwarding, MSDP SA request message, multicast VLAN, PIM hello message options, PIM snooping,...
Page 385 fast-leave processing enable restrictions, MLDv1 forwarding entries max, how it works, general configuration restrictions and joining IPv6 multicast group, guidelines, leaving IPv6 multicast group, general query, MLD support, general query/response parameter querier election, configuration, MLDv1 snooping version, group policy+simulated joining MLDv2 configuration, filter mode,...
Page 386 peer-RPF forwarding, PIM-SM admin-scoped zone configuration, PIM-SM inter-domain multicast PIM-SM assert, configuration, PIM-SM configuration, protocols and standards, PIM-SM DR election, RPF static peer, PIM-SM enable, 110, SA message cache, PIM-SM multicast source registration, SA message filtering configuration, PIM-SM neighbor discovery, SA message multicast data PIM-SM non-scoped zone configuration, encapsulation,...
Page 387 forwarding entries max, neighbor discovery IPv6 multicast VLAN. See IPv6 multicast BIDIR-PIM, VLAN IPv6 BIDIR-PIM, maintain, IPv6 PIM-DM, port-based configuration, IPv6 PIM-SM, port-based multicast VLAN configuration, IPv6 PIM-SSM, port-based multicast VLAN user port PIM-DM, assignment, PIM-SM, port-based multicast VLAN user port PIM-SSM, attribute, network...
Page 388 IPv6 multicast load splitting, MLD version specification, IPv6 multicast longest prefix match MSDP basics configuration, principle, MSDP mesh group, IPv6 multicast port-based VLAN MSDP peer configuration, configuration, MSDP peer description, IPv6 multicast port-based VLAN user port MSDP peering connection, assignment, MSDP peering connection control, IPv6 multicast port-based VLAN user port MSDP RPF static peer,...
Page 389 PIM-SM BSM semantic fragmentation, MSDP PIM-SM inter-domain multicast configuration, PIM-SM BSR configuration, MSDP SA message filtering configuration, PIM-SM C-BSR, multicast routing+forwarding PIM-SM configuration, configuration, 58, 62, PIM-SM DR election, multicast VLAN configuration, 46, 48, PIM-SM multicast source registration, 99, multicast VPN configuration, 180, 193, PIM-SM neighbor discovery, PIM configuration, 94, PIM-SM RP configuration,...
Page 390 multicast VPN data-MDT to default-MDT common timer configuration (global), switch, common timer configuration (on interface), multicast VPN default-MDT to data-MDT configuration, 94, switch, display, multicast VPN default-MDT-based data DM. See PIM-DM packet delivery, hello message option configuration (global), multicast VPN default-MDT-based hello message option configuration (on delivery, interface),...
Page 391 multicast routing+forwarding configuration, MSDP SA message policy, multicast VPN default MDT establishment in MSDP SA message-related parameters, PIM-DM network, MSDP SA request message, neighbor discovery, multicast routing+forwarding configuration, PIM BFD enable, multicast source registration, 99, PIM configuration, multicast VPN default MDT characteristics, PIM NSR enable, multicast VPN default MDT establishment in PIM passive mode enable,...
Page 392 MLD snooping group policy+simulated joining port-based multicast VLAN user port attribute, configuration, port-based IPv6 multicast VLAN MLD snooping IPv6 multicast group configuration, 265, policy, implementation, MLD snooping policy, user port assignment, port user port attribute configuration, IGMP snooping basic configuration, port-based multicast VLAN IGMP snooping configuration, 12, 16, configuration, 49, 51,...
Page 393 configuring IGMP snooping multicast source configuring IPv6 PIM timer (interface), port filtering (port), configuring IPv6 PIM-DM, 315, configuring IGMP snooping multicast source configuring IPv6 PIM-DM graft retry timer, port filtering (specific port), configuring IPv6 PIM-DM state refresh configuring IGMP snooping policy, parameter, configuring IGMP snooping port feature, configuring IPv6 PIM-SM,...
Page 394 configuring MLD snooping policy, configuring PIM common timers, configuring MLD snooping port feature, configuring PIM domain border, 113, configuring MLD snooping querier, 237, configuring PIM hello message option globally, configuring MLD snooping simulated member host, configuring PIM hello message option on interface, configuring MLD snooping static port, 235,...
Page 395 displaying IPv6 multicast enabling IPv6 PIM NSR, routing+forwarding, enabling IPv6 PIM passive mode, displaying IPv6 multicast VLAN, enabling IPv6 PIM-DM, displaying IPv6 PIM, enabling IPv6 PIM-DM state refresh feature, displaying IPv6 PIM snooping, enabling IPv6 PIM-SM, displaying MLD, enabling IPv6 PIM-SM IPv6 PIM-SSM, displaying MLD snooping, enabling MD VPN instance IP multicast displaying MSDP,...
Page 396 maintaining multicast VLAN, specifying IPv6 multicast longest prefix match principle, maintaining PIM snooping, specifying MLD snooping version, 232, setting IGMP last member query interval (global), specifying MLD snooping version(MLD-snooping view), setting IGMP last member query interval (VLAN), specifying MLD snooping version(VLAN view), setting IGMP snooping dynamic port aging timer,...
Page 397 troubleshooting PIM-SM multicast source MLD snooping querier, registration failure, MLD snooping querier configuration, Protocol Independent Multicast. Use protocols and standards reflecting IGMP, multicast VPN BGP MDT route reflector, IGMP snooping, refreshing IP multicast, IPv6 PIM-DM state refresh enable, IPv6 PIM, IPv6 PIM-DM state refresh parameters, Layer 2 multicast, PIM-DM state-refresh,...
Page 398 IGMP snooping router port, IGMP version specification, MLD snooping router port, IP multicast address, 5, routing IP multicast inter-AS MD VPN, BIDIR-PIM, IP multicast overview, BIDIR-PIM Auto-RP listening, IP multicast packet forwarding, BIDIR-PIM bidirectional RPT building, IP multicast transmission techniques, BIDIR-PIM BSM semantic fragmentation, IPv6 BIDIR-PIM, BIDIR-PIM BSR configuration,...
Page 399 IPv6 PIM-SM configuration, MLD SSM mapping configuration, IPv6 PIM-SM DR election, MSDP Anycast RP, IPv6 PIM-SM embedded RP, MSDP Anycast RP configuration, IPv6 PIM-SM multicast source MSDP basics configuration, registration, 306, MSDP configuration, 149, 155, IPv6 PIM-SM neighbor discovery, MSDP inter-AS multicast configuration (static IPv6 PIM-SM non-scoped zone RPF peers), configuration,...
Page 400 PIM-DM SPT building, IPv6 PIM-SM embedded RP, PIM-SM, IPv6 PIM-SM RP, PIM-SM administrative scoping, IPv6 PIM-SM RP discovery, PIM-SM administrative zones, IPv6 PIM-SM RPT building, PIM-SM admin-scoped zone IPv6 PIM-SM SPT switchover, configuration, IPv6 PIM-SM static RP, PIM-SM assert, IPv6 PIM-SSM SPT building, PIM-SM Auto-RP listening, MSDP Anycast RP, PIM-SM BSM semantic fragmentation,...
Page 401 PIM-SM multicast source registration, PIM-SM RPT building, IP multicast model, troubleshooting IPv6 PIM-SM RPT cannot be shortest path tree. Use built, snooping rule IGMP snooping configuration, MSDP SA message policy, IPv6 PIM. See IPv6 PIM snooping MLD snooping configuration, PIM. See PIM snooping source MSDP peer-RPF forwarding,...
Page 402 MLD SSM mapping configuration, IP multicast transmission techniques, state MSDP inter-AS multicast configuration (static RPF peers), IPv6 PIM-DM state refresh enable, MSDP PIM-SM inter-domain multicast IPv6 PIM-DM state refresh parameters, configuration, MLDv2, multicast forwarding across unicast subnets, PIM-DM state-refresh, multicast forwarding/GRE tunnel configuration, PIM-DM state-refresh parameters, multicast routing RPF route change, static...
Page 403 multicast routing load splitting, PIM-SM RP cannot be built, transmitting PIM-SM RP cannot join SPT, IP multicast, tunneling IP multicast broadcast, IPv6 multicast forwarding/GRE tunnel configuration, IP multicast overview, multicast forwarding across unicast subnets, IP multicast transmission techniques, multicast forwarding/GRE tunnel configuration, IP multicast unicast, troubleshooting IGMP,...
Page 404 IGMP snooping querier configuration, PIM-SM admin-scoped zone configuration, IGMP snooping querier enable, PIM-SM non-scoped zone configuration, IGMP snooping simulated member host, PIM-SSM configuration, IGMP snooping static port, port-based multicast VLAN configuration, IGMP snooping static port configuration, sub-VLAN-based multicast VLAN configuration, IGMP snooping unknown multicast data drop, IGMP snooping version,...

HP FlexNetwork 7500 Series Configuration Manual

Quick Links

Troubleshooting

Related Manuals for HP FlexNetwork 7500 Series

Summary of Contents for HP FlexNetwork 7500 Series