Page 1 HPE FlexFabric 12900E Switch Series IP Multicast Configuration Guide Part number: 5200-1231b Software version: Release 2606 and later Document version: 6W101-20161201...
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 IP multicast architecture ················································································································ 5 Multicast addresses ··············································································································· 5 Multicast protocols ·················································································································...
Page 4 Static port configuration example (for VLANs) ··········································································· 38 IGMP snooping querier configuration example (for VLANs) ························································· 40 IGMP snooping proxying configuration example (for VLANs) ······················································· 43 Troubleshooting IGMP snooping ··································································································· 44 Layer 2 multicast forwarding cannot function ············································································ 44 Multicast group policy does not work ······················································································· 45 Configuring PIM snooping ································································...
Page 5 IGMP support for VPNs ········································································································ 84 Protocols and standards ······································································································· 84 IGMP configuration task list ·········································································································· 85 Configuring basic IGMP features ··································································································· 85 Enabling IGMP ··················································································································· 85 Specifying an IGMP version ·································································································· 86 Configuring a static group member ························································································· 86 Configuring a multicast group policy ························································································...
Page 6 Configuration prerequisites·································································································· 131 Enabling PIM-SM ·············································································································· 131 Configuring the SSM group range ························································································· 131 Configuring common PIM features ······························································································ 132 Configuration task list ········································································································· 132 Configuration prerequisites·································································································· 132 Configuring a multicast source policy ···················································································· 132 Configuring a PIM hello policy ······························································································ 133 Configuring PIM hello message options ·················································································...
Page 7 No exchange of locally registered (S, G) entries between RPs ··················································· 190 Configuring MLD snooping ····························································· 191 Overview ································································································································ 191 MLD snooping ports ··········································································································· 191 How MLD snooping works··································································································· 193 MLD snooping proxying ······································································································ 194 MLD snooping version ········································································································ 195 Protocols and standards ·····································································································...
Page 8 Index ························································································· 228...
Page 9: 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 10 Broadcast In broadcast transmission, the information source sends information to all hosts on the subnet, even if some hosts do not need the information. Figure 2 Broadcast transmission Host A Receiver Host B Source Host C Receiver Host D A network segment Receiver Packets for all hosts Host E...
Page 11: Multicast Features
Figure 3 Multicast transmission Host A Receiver Host B Source Host C Receiver Host D IP network Receiver Packets for the multicast group Host E Figure 3, the multicast source sends only one copy of the information to a multicast group. Host B, Host D, and Host E, which are information receivers, must join the multicast group.
Page 12: 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 13: Multicast Addresses
SFM model The SFM model is derived from the ASM model. To a multicast source, the two models appear to have the same multicast membership architecture. The SFM model functionally extends the ASM model. The upper-layer software checks the source address of received multicast packets and permits or denies multicast traffic from specific sources.
Page 14 Address block Description Globally scoped group addresses. This block includes the following types of designated group addresses: 224.0.1.0 to 238.255.255.255 232.0.0.0/8—SSM group addresses. • • 233.0.0.0/8—Glop group addresses. Administratively scoped multicast addresses. These addresses are considered locally unique rather than globally unique. You can 239.0.0.0 to 239.255.255.255 reuse them in domains administered by different organizations without causing conflicts.
Page 15 The following describes the fields of an IPv6 multicast address: 0xFF—The most significant eight bits are 11111111.  Flags—The Flags field contains four bits.  Figure 5 Flags field format 0 R P T Table 4 Flags field description Description Reserved, set to 0.
Page 16: Multicast Protocols
Figure 6 IPv4-to-MAC address mapping 5 bits lost XXXX X 1110 XXXX XXXX XXXX XXXX XXXX XXXX XXXX 32-bit IPv4 address 23 bits … … mapped 48-bit MAC address 0000 0001 0000 0000 0101 1110 0XXX XXXX XXXX XXXX XXXX XXXX 25-bit MAC address prefix The most significant four bits of an IPv4 multicast address are fixed at 1110.
Page 17 • IPv4 and IPv6 multicast protocols: For IPv4 networks—IGMP snooping, PIM snooping, multicast VLAN, IGMP, PIM, MSDP,  and MBGP. For IPv6 networks—MLD snooping, IPv6 PIM snooping, IPv6 multicast VLAN, MLD, IPv6  PIM, and IPv6 MBGP. This section provides only general descriptions about applications and functions of the Layer 2 and Layer 3 multicast protocols in a network.
Page 18: Multicast Packet Forwarding Mechanism
For the SSM model, multicast routes are not divided into intra-domain routes and inter-domain routes. Because receivers know the positions of the multicast sources, channels established through PIM-SM are sufficient for the transport of multicast information. Layer 2 multicast protocols Figure 9, Layer 2 multicast protocols include IGMP snooping, MLD snooping, PIM snooping, IPv6 PIM snooping, multicast VLAN, and IPv6 multicast VLAN.
Page 19: Multicast Support For Vpns
• To ensure multicast packet transmission on the network, different routing tables are used to guide multicast forwarding. These routing tables include unicast routing tables, routing tables for multicast (for example, the MBGP routing table), and static multicast routing tables. •...
Page 20: Multicast Application In Vpns
Multicast application in VPNs A PE device that supports multicast for VPNs performs the following operations: • Maintains an independent set of multicast forwarding mechanisms for each VPN, including the multicast protocols, PIM neighbor information, and multicast routing table. In a VPN, the device forwards multicast data based on the forwarding table or routing table for that VPN.
Page 21: Configuring Igmp Snooping
Configuring IGMP snooping Overview IGMP snooping runs on a Layer 2 device as a multicast constraining mechanism to improve multicast forwarding efficiency. It creates Layer 2 multicast forwarding entries from IGMP packets that are exchanged between the hosts and the router. As shown in Figure 11, when IGMP snooping is not enabled, the Layer 2 switch floods multicast...
Page 22 Figure 12 IGMP snooping ports Receiver Router A Switch A HGE1/0/1 HGE1/0/2 Host A HGE1/0/3 Host B Receiver HGE1/0/1 HGE1/0/2 Source Host C Switch B Router port Member port Multicast packets Host D Router ports On an IGMP snooping Layer 2 device, the ports toward Layer 3 multicast devices are called router ports.
Page 23: How Igmp Snooping Works
How IGMP snooping works The ports in this section are dynamic ports. For information about how to configure and remove static ports, see "Configuring static ports." IGMP messages types include general query, IGMP report, and leave message. An IGMP snooping-enabled Layer 2 device performs differently depending on the message types. General query The IGMP querier periodically sends IGMP general queries to all hosts and routers on the local subnet to check for the existence of multicast group members.
Page 24: Igmp Snooping Proxying
• 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 25: Protocols And Standards
The IGMP snooping proxy device processes different IGMP messages as follows: • General query. After receiving an IGMP general query, the device forwards the query to all ports in the VLAN except the receiving port. The device also generates an IGMP report based on the local membership information and sends the report to all router ports.
Page 26: Igmp Configuration Task List For Vsis
Tasks at a glance • (Optional.) Enabling inner VLAN ID-based forwarding Configuring the IGMP snooping querier: • (Optional.) Enabling the IGMP snooping querier • (Optional.) Configuring parameters for IGMP general queries and responses (Optional.) Enabling IGMP snooping proxying Configuring parameters for IGMP messages: •...
Page 27: Enabling Igmp Snooping
• Configure VLANs or VSIs. • Determine the IGMP snooping version. • Determine the maximum number of IGMP snooping forwarding entries. • Determine the IGMP last member query interval. Enabling IGMP snooping When you enable IGMP snooping, follow these restrictions and guidelines: You must enable IGMP snooping globally before you enable it for a VLAN or VSI.
Page 28: Setting The Maximum Number Of Igmp Snooping Forwarding Entries
• Keeps static IGMPv3 snooping forwarding entries (*, G). • Clears static IGMPv3 snooping forwarding entries (S, G), which will be restored when IGMP snooping is switched back to IGMPv3 snooping. For more information about static IGMP snooping forwarding entries, see "Configuring static ports."...
Page 29: Configuring Static Multicast Mac Address Entries
Configuring static multicast MAC address entries In Layer 2 multicast, multicast MAC address entries can be dynamically created through Layer 2 multicast protocols (such as IGMP snooping). You can also manually configure static multicast MAC address entries by binding multicast MAC addresses and ports to control the destination ports of the multicast data.
Page 30: Configuring Igmp Snooping Port Features
VSI-specific configuration takes priority over the global configuration. For a VLAN, the VLAN-specific configuration takes priority over the global configuration. Setting the IGMP last member query interval globally Step Command Remarks Enter system view. system-view Enter IGMP-snooping view. igmp-snooping Set the IGMP last member The default setting is 1 last-member-query-interval query interval globally.
Page 31: Configuring Static Ports
Setting the aging timers for dynamic ports globally Step Command Remarks Enter system view. system-view Enter IGMP-snooping view. igmp-snooping Set the aging timer for default setting dynamic router ports router-aging-time seconds seconds. globally. Set the global aging timer for default setting dynamic member...
Page 32: Configuring A Port As A Simulated Member Host
Step Command Remarks igmp-snooping static-router-port vlan vlan-id Configuring a port as a simulated member host When a port is configured as a simulated member host, it is equivalent to an independent host in the following ways: • It sends an unsolicited IGMP report when you complete the configuration. •...
Page 33: Disabling A Port From Becoming A Dynamic Router Port
Enabling fast-leave processing on a port Step Command Remarks Enter system view. system-view Enter Layer Ethernet interface interface-type interface view or Layer 2 interface-number aggregate interface view. Enable fast-leave processing igmp-snooping fast-leave [ vlan By default, fast-leave processing on the port. vlan-list ] is disabled on a port.
Page 34: Configuring The Igmp Snooping Querier
Step Command Remarks ID-based forwarding. Configuring the IGMP snooping querier This section describes how to configure an IGMP snooping querier. Configuration prerequisites Before you configure the IGMP snooping querier, complete the following tasks: • Enable IGMP snooping for the VLAN or VSI. Determine the IGMP general query interval.
Page 35: Enabling Igmp Snooping Proxying
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 or VSI based on the actual condition of the network.
Page 36: Configuring Parameters For Igmp Messages
Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Enable IGMP snooping default, IGMP snooping igmp-snooping proxy enable proxying for the VLAN. proxying is disabled for a VLAN. Configuring parameters for IGMP messages This section describes how to configure parameters for IGMP messages. Configuration prerequisites Before you configure parameters for IGMP messages, complete the following tasks: •...
Page 37 Step Command Remarks IGMP snooping querier of the VLAN received IGMP general queries. • The IP address of the current VLAN interface if the IGMP snooping querier does receive an IGMP general query. • 0.0.0.0 if the IGMP snooping querier does not receive an IGMP general query and the current VLAN interface does not have an IP address.
Page 38: Setting The 802.1P Priority For Igmp Messages
Step Command Remarks By default, the source IP address of IGMP leave messages is the IP Configure source address of the gateway interface for a igmp-snooping leave address IGMP leave VSI. If the gateway interface does not source-ip ip-address messages. have an IP address, the source IP address is 0.0.0.0.
Page 39: Configuring A Multicast Group Policy
Configuring a multicast group policy This feature enables the device to filter IGMP reports by using an ACL that specifies the multicast groups and the optional sources. It is used to control the multicast groups that hosts can join. Configuration restrictions and guidelines When you configure a multicast group policy, follow these restrictions and guidelines: •...
Page 40: Enabling Dropping Unknown Multicast Data
Enabling multicast source port filtering in interface view Step Command Remarks Enter system view. system-view Enter Layer Ethernet interface interface-type interface view. interface-number Enable multicast source port By default, multicast source port igmp-snooping source-deny filtering. filtering is disabled. Enabling dropping unknown multicast data Unknown multicast data refers to multicast data for which no forwarding entries exist in the IGMP snooping forwarding table.
Page 41: Enabling Multicast Group Replacement
Configuration restrictions and guidelines When you set the maximum number of multicast groups on a port, follow these restrictions and guidelines: • This configuration takes effect only on the multicast groups that a port joins dynamically. • If the number of multicast groups on a port exceeds the limit, the system removes all the forwarding entries related to that port.
Page 42: Displaying And Maintaining Igmp Snooping
Enabling host tracking This feature enables the device to record information about member hosts that are receiving multicast data. The information includes IP addresses of the hosts, length of time elapsed since the hosts joined multicast groups, and remaining timeout time for the hosts. This feature facilitates monitoring and managing member hosts.
Page 43 Task Command snooping group entries. source-address ] * [ vlan vlan-id ] [ verbose ] [ chassis chassis-number slot slot-number ] (In standalone mode.) Display static router port information. display igmp-snooping static-router-port [ vlan vlan-id ] [ verbose ] [ slot slot-number ] (The verbose keyword is available in R2609 and later.) (In IRF mode.) Display static router port...
Page 44: Igmp Snooping Configuration Examples
Task Command vsi-name } Clear statistics for IGMP messages and PIMv2 hello messages learned through reset igmp-snooping statistics IGMP snooping. IGMP snooping configuration examples Group policy and simulated joining configuration example(for VLANs) Network requirements As shown in Figure 14, Router A runs IGMPv2 and acts as the IGMP querier. Switch A runs IGMPv2 snooping.
Page 45 [RouterA] interface hundredgige 1/0/1 [RouterA-HundredGigE1/0/1] igmp enable [RouterA-HundredGigE1/0/1] quit # Enable PIM-DM on HundredGigE 1/0/2. [RouterA] interface hundredgige 1/0/2 [RouterA-HundredGigE1/0/2] pim dm [RouterA-HundredGigE1/0/2] quit Configure Switch A: # Enable IGMP snooping globally. <SwitchA> system-view [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 100, and assign HundredGigE 1/0/1 through HundredGigE 1/0/4 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port hundredgige 1/0/1 to hundredgige 1/0/4 # Enable IGMP snooping, and enable dropping unknown multicast data for VLAN 100.
Page 46: Static Port Configuration Example (For Vlans)
The output shows the following information: • Host A and Host B have joined multicast group 224.1.1.1 through the member ports HundredGigE 1/0/4 and HundredGigE 1/0/3 on Switch A, respectively. • Host A and Host B have failed to join multicast group 224.2.2.2. Static port configuration example (for VLANs) Network requirements As shown in...
Page 47 <RouterA> system-view [RouterA] multicast routing [RouterA-mrib] quit # Enable IGMP on HundredGigE 1/0/1. [RouterA] interface hundredgige 1/0/1 [RouterA-HundredGigE1/0/1] igmp enable [RouterA-HundredGigE1/0/1] quit # Enable PIM-DM on HundredGigE 1/0/2. [RouterA] interface hundredgige 1/0/2 [RouterA-HundredGigE1/0/2] pim dm [RouterA-HundredGigE1/0/2] quit Configure Switch A: # Enable IGMP snooping globally.
Page 48: Igmp Snooping Querier Configuration Example (For Vlans)
[SwitchC-vlan100] quit # Configure HundredGigE 1/0/3 and HundredGigE 1/0/5 as static member ports for multicast group 224.1.1.1. [SwitchC] interface hundredgige 1/0/3 [SwitchC-HundredGigE1/0/3] igmp-snooping static-group 224.1.1.1 vlan 100 [SwitchC-HundredGigE1/0/3] quit [SwitchC] interface hundredgige 1/0/5 [SwitchC-HundredGigE1/0/5] igmp-snooping static-group 224.1.1.1 vlan 100 [SwitchC-HundredGigE1/0/5] quit Verifying the configuration # Display brief information about static router ports for VLAN 100 on Switch A.
Page 49 Figure 16 Network diagram Source 1 Source 2 VLAN 100 192.168.1.10/24 192.168.1.20/24 Receiver Receiver HGE1/0/2 HGE1/0/2 HGE1/0/1 HGE1/0/3 HGE1/0/3 HGE1/0/1 Host A Host B HGE1/0/4 Switch A Switch B Querier Receiver Receiver HGE1/0/2 HGE1/0/1 HGE1/0/2 HGE1/0/3 HGE1/0/1 Host D Host C Switch D Switch C Configuration procedure...
Page 50 [SwitchB-vlan100] igmp-snooping enable [SwitchB-vlan100] igmp-snooping drop-unknown [SwitchB-vlan100] quit Configure Switch C: # Enable IGMP snooping globally. <SwitchC> system-view [SwitchC] igmp-snooping [SwitchC-igmp-snooping] quit # Create VLAN 100, and assign HundredGigE 1/0/1 through HundredGigE 1/0/3 to the VLAN. [SwitchC] vlan 100 [SwitchC-vlan100] port hundredgige 1/0/1 to hundredgige 1/0/3 # Enable IGMP snooping, and enable dropping unknown multicast data for VLAN 100.
Page 51: Igmp Snooping Proxying Configuration Example (For Vlans)
IGMP snooping proxying configuration example (for VLANs) Network requirements As shown in Figure 17, Router A runs IGMPv2 and acts as the IGMP querier. Switch A runs IGMPv2 snooping. Configure IGMP snooping proxying so that Switch A can perform the following actions: •...
Page 52: Troubleshooting Igmp Snooping
# Create VLAN 100, and assign HundredGigE 1/0/1 through HundredGigE 1/0/4 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port hundredgige 1/0/1 to hundredgige 1/0/4 # Enable IGMP snooping and IGMP snooping proxying for the VLAN. [SwitchA-vlan100] igmp-snooping enable [SwitchA-vlan100] igmp-snooping proxy enable [SwitchA-vlan100] quit Verifying the configuration # Send IGMP reports from Host A and Host B to multicast group 224.1.1.1.
Page 53: Multicast Group Policy Does Not Work
Solution To resolve the problem: Use the display igmp-snooping command to display IGMP snooping status. If IGMP snooping is not enabled, use the igmp-snooping command in system view to enable IGMP snooping globally. Then, use the igmp-snooping enable command in VLAN view or VSI view to enable IGMP snooping for the VLAN or VSI.
Page 54: 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 18 Multicast packet transmission without or with PIM snooping Multicast packet transmission Multicast packet transmission when...
Page 55: 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: d.
Page 56: Displaying And Maintaining Pim Snooping
Step Command Remarks The default setting is 210 seconds. (Optional.) Set the aging time for global downstream A global downstream port or a ports and global router ports pim-snooping graceful-restart global router port is a Layer 2 on the new active MPU after join-aging-time seconds aggregate interface,...
Page 57: Configuration Procedure
• Router C and Router D run IGMP on HundredGigE 1/0/1. Router A, Router B, Router C, and Router D run PIM-SM. • HundredGigE 1/0/2 on Router A acts as a C-BSR and a C-RP. To make sure Switch A forwards PIM protocol packets and multicast data packets only to the routers that are connected to receivers, perform the following tasks: •...
Page 58 [RouterA-pim] quit Configure Router B: # Enable IP multicast routing. <RouterB> system-view [RouterB] multicast routing [RouterB-mrib] quit # Enable PIM-SM on each interface. [RouterB] interface hundredgige 1/0/1 [RouterB-HundredGigE1/0/1] pim sm [RouterB-HundredGigE1/0/1] quit [RouterB] interface hundredgige 1/0/2 [RouterB-HundredGigE1/0/2] pim sm [RouterB-HundredGigE1/0/2] quit # Set the maximum size of a join or prune message to 1400 bytes.
Page 59: Verifying The Configuration
[RouterD-pim] jp-pkt-size 1400 Configure Switch A: # Enable IGMP snooping globally. <SwitchA> system-view [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 100, and assign HundredGigE 1/0/1 through HundredGigE 1/0/4 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port hundredgige 1/0/1 to hundredgige 1/0/4 # Enable IGMP snooping and PIM snooping for VLAN 100.
Page 60: Troubleshooting Pim Snooping
Upstream neighbor: 10.1.1.2 Upstream Ports (1 in total): HGE1/0/2 Downstream Ports (1 in total): HGE1/0/4 Expires: 00:03:11, FSM: J The output shows the following information: • Switch A will forward the multicast data intended for multicast group 224.1.1.1 only to Router C. •...
Page 61: Configuring Multicast Vlans
Configuring multicast VLANs Overview As shown in Figure 20, 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 62 Figure 21 Sub-VLAN-based multicast VLAN Multicast packets VLAN 10 (Multicast VLAN) VLAN 2 VLAN 2 Receiver VLAN 3 Host A VLAN 4 VLAN 3 Receiver Host B Switch A Switch B Source IGMP querier VLAN 4 Receiver Host C 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.
Page 63: 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 ...
Page 64: Configuring User Port Attributes
Configuring a port-based multicast VLAN You can assign only Layer 2 Ethernet interfaces or Layer 2 aggregate interfaces to a multicast VLAN. Configuration prerequisites Before you configure a port-based multicast VLAN, complete the following tasks: • Create VLANs as required. •...
Page 65: Setting The Maximum Number Of Multicast Vlan Forwarding Entries
Step Command Remarks Configure a VLAN as a By default, a VLAN is not a multicast VLAN and enter its multicast-vlan vlan-id multicast VLAN. view. Assign ports to the multicast By default, a multicast VLAN does port interface-list VLAN. not have any user ports. To assign a user port to a multicast VLAN in interface view: Step Command...
Page 66: Multicast Vlan Configuration Examples
Task Command in multicast VLANs. (In IRF mode.) Display information display multicast-vlan group [ source-address | group-address | about multicast groups in multicast chassis chassis-number slot slot-number | verbose | vlan vlan-id ] * VLANs. standalone mode.) Display display multicast-vlan forwarding-table [ group-address [ mask information about multicast VLAN { mask-length | mask } ] | source-address [ mask { mask-length | mask } ] | slot slot-number | subvlan vlan-id | vlan vlan-id ] *...
Page 67: Vlan Member
Figure 23 Network diagram Source HGE1/0/2 IGMP querier Vlan-int20 Switch A 1.1.1.2/24 HGE1/0/1 1.1.1.1/24 Vlan-int10 10.110.1.1/24 HGE1/0/1 Switch B HGE1/0/2 HGE1/0/4 HGE1/0/3 Receiver Receiver Receiver Host A Host B Host C VLAN 2 VLAN 3 VLAN 4 Configuration procedure Configure Switch A: # Enable IP multicast routing.
Page 68 Configure Switch B: # Enable IGMP snooping globally. <SwitchB> system-view [SwitchB] igmp-snooping [SwitchB-igmp-snooping] quit # Create VLAN 2, assign HundredGigE 1/0/2 to the VLAN, and enable IGMP snooping for the VLAN. [SwitchB] vlan 2 [SwitchB-vlan2] port hundredgige 1/0/2 [SwitchB-vlan2] igmp-snooping enable [SwitchB-vlan2] quit # Create VLAN 3, assign HundredGigE 1/0/3 to the VLAN, and enable IGMP snooping in the VLAN.
Page 69: 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 70 [SwitchA] multicast routing [SwitchA-mrib] quit # Create VLAN 20, and assign HundredGigE 1/0/2 to the VLAN. [SwitchA] vlan 20 [SwitchA-vlan20] port hundredgige 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 71 # Assign HundredGigE 1/0/2 to VLAN 2 and VLAN 10 as an untagged VLAN member. [SwitchB-HundredGigE1/0/2] port hybrid vlan 2 untagged [SwitchB-HundredGigE1/0/2] port hybrid vlan 10 untagged [SwitchB-HundredGigE1/0/2] quit # Configure HundredGigE 1/0/3 as a hybrid port, and configure VLAN 3 as the PVID of the hybrid port.
Page 72 (0.0.0.0, 224.1.1.1) Host slots (0 in total): Host ports (3 in total): HGE1/0/2 (00:03:23) HGE1/0/3 (00:04:07) HGE1/0/4 (00:04:16) The output shows that IGMP snooping maintains the user ports in the multicast VLAN (VLAN 10). Switch B will forward the multicast data of VLAN 10 through these user ports.
Page 73: 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 74 RPF check implementation in multicast Implementing an RPF check on each received multicast packet brings a big burden to the router. The use of a multicast forwarding table is the solution to this issue. When the router creates a multicast forwarding entry for an (S, G) packet, it sets the RPF interface of the packet as the incoming interface of the (S, G) entry.
Page 75: Static Multicast Routes
the outgoing interface to the source (the RPF interface) is VLAN-interface 20. In this case, the (S, G) entry is correct, but the packet traveled along a wrong path. The packet fails the RPF check and Device C discards the packet. Static multicast routes Depending on the application environment, a static multicast route can change an RPF route or create an RPF route.
Page 76: Multicast Forwarding Across Unicast Subnets
Figure 27 Creating an RPF route Static multicast routing table on Device C OSPF domain Source/Mask Interface RPF neighbor/Mask 192.168.0.0/24 Vlan-int10 1.1.1.1/24 Receiver Device D Static multicast routing table on Device D Vlan-int20 Source/Mask Interface RPF neighbor/Mask 2.2.2.1/24 192.168.0.0/24 Vlan-int20 2.2.2.2/24 Source Vlan-int20...
Page 77: Configuration Task List
Figure 28 Multicast data transmission through a tunnel Unicast device Unicast device Multicast device Multicast device Tunnel Device B Device A Source Receiver Unicast device Unicast device As shown in Figure 28, a tunnel is established between the multicast routers Device A and Device B. Device A encapsulates the multicast data in unicast IP packets, and forwards them to Device B across the tunnel through unicast routers.
Page 78: Configuring Multicast Routing And Forwarding
Configuring multicast routing and forwarding Before you configure multicast routing and forwarding, complete the following tasks: • Configure a unicast routing protocol so that all devices in the domain can interoperate at the network layer. • Enable PIM-DM or PIM-SM. Configuring static multicast routes To configure a static multicast route for a given multicast source, you can specify an RPF interface or an RPF neighbor for the multicast traffic from that source.
Page 79: Configuring Multicast Load Splitting
Configuring multicast load splitting You can enable the device to split multiple data flows on a per-source basis or on a per-source-and-group basis. This optimizes the traffic delivery. To configure multicast load splitting: Step Command Remarks Enter system view. system-view multicast routing [ vpn-instance Enter MRIB view.
Page 80: Displaying And Maintaining Multicast Routing And Forwarding
Step Command Remarks resource mode. { normal | enhance } hardware resource mode normal. Displaying and maintaining multicast routing and forwarding CAUTION: The reset commands might cause multicast data transmission failures. Execute display commands in any view and reset commands in user view. Task Command Display...
Page 81: Configuration Examples
Task Command outgoing-interface exclude include match interface-type interface-number | statistics ] * (In standalone mode.) Display information display multicast [ vpn-instance vpn-instance-name ] about the DF list in the multicast forwarding-table df-list [ group-address ] [ verbose ] [ slot forwarding table.
Page 82 • PIM-DM runs on the network. • All switches on the network support multicast. • Switch A, Switch B and Switch C run OSPF. • Typically, the receiver host can receive the multicast data from Source through the path: Switch A to Switch B, which is the same as the unicast route.
Page 83: Creating An Rpf Route
# On Switch A, enable IP multicast routing. <SwitchA> system-view [SwitchA] multicast routing [SwitchA-mrib] quit # Enable PIM-DM on each interface. [SwitchA] interface vlan-interface 200 [SwitchA-Vlan-interface200] pim dm [SwitchA-Vlan-interface200] quit [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] pim dm [SwitchA-Vlan-interface102] quit [SwitchA] interface vlan-interface 103 [SwitchA-Vlan-interface103] pim dm [SwitchA-Vlan-interface103] quit # Enable IP multicast routing and PIM-DM on Switch C in the same way Switch A is configured.
Page 84 • All switches on the network support IP multicast. • Switch B and Switch C run OSPF, and have no unicast routes to Switch A. • Typically, the receiver host receives the multicast data from Source 1 in the OSPF domain. Configure the switches so that the receiver host receives multicast data from Source 2, which is outside the OSPF domain.
Page 85: Troubleshooting Multicast Routing And Forwarding
[SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] pim dm [SwitchA-Vlan-interface102] quit # Enable IP multicast routing and PIM-DM on Switch B in the same way Switch A is configured. (Details not shown.) Display RPF information for Source 2 on Switch B and Switch C. [SwitchB] display multicast rpf-info 50.1.1.100 [SwitchC] display multicast rpf-info 50.1.1.100 No output is displayed because no RPF routes to Source 2 exist on Switch B or Switch C.
Page 86 Use the display multicast routing-table static command to display information about static multicast routes. Verify that the static multicast route has been correctly configured and that the route entry exists in the static multicast routing table. Check the type of interface that connects the static multicast route to the RPF neighbor. If the interface is not a point-to-point interface, be sure to specify the address for the RPF neighbor.
Page 87: 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 88: Igmpv2 Enhancements
The hosts send unsolicited IGMP reports to the multicast groups they want to join without having to wait for the IGMP queries. The IGMP querier periodically multicasts IGMP queries (with the destination address of 224.0.0.1) to all hosts and routers on the local subnet. After receiving a query message, the host whose report delay timer expires first sends an IGMP report to multicast group G1 to announce its membership for G1.
Page 89: 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 90: Igmp Ssm Mapping
IGMPv3 is compatible with IGMPv1 and IGMPv2 and supports IGMP general queries and IGMP group-specific queries. It also introduces IGMP group-and-source-specific queries. A general query does not carry a group address or a source address.  A group-specific query carries a group address, but no source address. ...
Page 91: Igmp Proxying
Figure 33 IGMP SSM mapping IGMPv1 report IGMPv2 report Querier IGMPv3 report Router A Receiver Receiver Receiver Host A (IGMPv1) Host B (IGMPv2) Host C (IGMPv3) As shown in Figure 33, on an SSM network, Host A, Host B, and Host C run IGMPv1, IGMPv2, and IGMPv3, respectively.
Page 92: Igmp Support For Vpns
Figure 34 IGMP proxying Proxy Querier Router B Router A PIM domain Ethernet Receiver Receiver Host B Host A Host C Report from Router B Query from Router A Query from Router B Host interface Report from Host Router interface The following types of interfaces are defined in IGMP proxying: •...
Page 93: 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 •...
Page 94: Specifying An Igmp Version
Specifying an IGMP version For IGMP to operate correctly, specify the same IGMP version for all routers on the same subnet. To specify an IGMP version: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Specify an IGMP version on the The default setting is 2.
Page 95: Adjusting Igmp Performance
Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, no IGMP multicast group policy exists igmp group-policy Configure a multicast group interface. Hosts attached to the ipv4-acl-number policy. [ version-number ] interface can join any multicast groups.
Page 96 • To avoid frequent IGMP querier changes, set the IGMP other querier present timer greater than the IGMP general query interval. In addition, configure the same IGMP other querier present timer for all IGMP routers on the same subnet. • To avoid mistakenly deleting multicast receivers, set the IGMP general query interval greater than the maximum response time for IGMP general queries.
Page 97: Enabling Fast-Leave Processing
Configuring the IGMP query and response parameters on an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number IGMP querier's By default, the IGMP querier's igmp robust-count count robustness variable. robustness variable is 2. By default, the IGMP startup Set the IGMP startup query query interval equals one quarter igmp...
Page 98: Configuring Igmp Proxying
Configuring IGMP SSM mappings This feature enables the device to provide SSM services for IGMPv1 or IGMPv2 hosts. This feature does not process IGMPv3 messages. Enable IGMPv3 on the receiver-side interface to ensure that IGMPv3 reports can be processed. Configuration prerequisites Before you configure IGMP SSM mappings, complete the following tasks: •...
Page 99: Enabling Multicast Forwarding On A Non-Querier Interface
ensure that the downstream receiver hosts on the router interface can receive multicast data, you must enable multicast forwarding on the interface. For more information, see "Enabling multicast forwarding on a non-querier interface." To enable IGMP proxying: Step Command Remarks Enter system view.
Page 100: Displaying And Maintaining Igmp
Step Command Remarks By default, multicast load splitting is disabled, and only the proxy Enable multicast load splitting. interface with the highest IP proxy multipath address on the IGMP proxy device forwards multicast data. Enabling IGMP NSR This feature backs up information about IGMP interfaces and IGMP multicast groups to the standby process.
Page 101: Igmp Configuration Examples
IGMP configuration examples This section provides examples of configuring IGMP on switches. Basic IGMP features configuration example Network requirements As shown in Figure • OSPF and PIM-DM run on the network. • VOD streams are sent to receiver hosts in multicast. Receiver hosts of different organizations form stub networks N1 and N2.
Page 102 # Enable IGMP on VLAN-interface 100. [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] igmp enable [SwitchA-Vlan-interface100] quit # Enable PIM-DM on VLAN-interface 101. [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim dm [SwitchA-Vlan-interface101] quit # On Switch B, enable IP multicast routing. <SwitchB> system-view [SwitchB] multicast routing [SwitchB-mrib] quit # Enable IGMP on VLAN-interface 200.
Page 103: Igmp Ssm Mapping Configuration Example
Other querier present time for IGMP: 255s Maximum query response time for IGMP: 10s Querier for IGMP: 10.110.2.1 (This router) IGMP groups reported in total: 1 IGMP SSM mapping configuration example Network requirements As shown in Figure • OSPF runs on the network. •...
Page 104 Configuration procedure Assign an IP address and subnet mask to each interface, as shown in Figure 36. (Details not shown.) Configure OSPF on the switches in the PIM-SM domain. (Details not shown.) Enable IP multicast routing, PIM-SM, and IGMP: # On Switch D, enable IP multicast routing. <SwitchD>...
Page 105 [SwitchD-pim] ssm-policy 2000 [SwitchD-pim] quit # Configure the SSM group range on Switch A, Switch B, and Switch C in the same way Switch D is configured. (Details not shown.) Configure IGMP SSM mappings on Switch D. [SwitchD] igmp [SwitchD-igmp] ssm-mapping 133.133.1.1 2000 [SwitchD-igmp] ssm-mapping 133.133.3.1 2000 [SwitchD-igmp] quit Verifying the configuration...
Page 106: Igmp Proxying Configuration Example
Total number of downstreams: 1 1: Vlan-interface400 Protocol: igmp, UpTime: 00:13:25, Expires: - IGMP proxying configuration example Network requirements As shown in Figure • PIM-DM runs on the core network. • Host A and Host C on the stub network receive VOD information sent to multicast group 224.1.1.1.
Page 107: Troubleshooting Igmp
[SwitchB-mrib] quit # Enable IGMP proxying on VLAN-interface 100. [SwitchB] interface vlan-interface 100 [SwitchB-Vlan-interface100] igmp proxy enable [SwitchB-Vlan-interface100] quit # Enable IGMP on VLAN-interface 200. [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] igmp enable [SwitchB-Vlan-interface200] quit Verifying the configuration # Display multicast group membership information maintained by the IGMP proxy on Switch B. [SwitchB] display igmp proxy group IGMP proxy group records in total: 1 Vlan-interface100(192.168.1.2):...
Page 108 Use the display current-configuration command to verify the IGMP information on the interfaces. Make sure the routers on the subnet have the same IGMP settings on their interfaces. Use the display igmp interface command on all routers on the same subnet to verify the IGMP-related timer settings.
Page 109: 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 110 this way, the upstream stream node stops forwarding subsequent packets addressed to that multicast group down to this node. NOTE: An (S, G) entry contains a multicast source address S, a multicast group address G, an outgoing interface list, and an incoming interface. A prune process is initiated by a leaf router.
Page 111: Pim-Sm Overview
Figure 39 Assert mechanism Router A Router B Ethernet Assert message Multicast packets Router C Receiver As shown in Figure 39, 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 112 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 113 As shown in Figure 41, 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 114 Anycast RP member address—IP address of each Anycast RP member for  communication among the RP members. Anycast RP address—IP address of the Anycast RP set for communication within the  PIM-SM domain. It is also known as RPA. As shown in Figure 42, RP 1, RP 2, and RP 3 are members of an Anycast RP set.
Page 115 RPT building Figure 43 RPT building in a PIM-SM domain Host A Source Receiver Host B Server Receiver Join message Multicast packets Host C As shown in Figure 43, the process of building an RPT is as follows: When a receiver wants to join the multicast group G, it uses an IGMP message to inform the receiver-side DR.
Page 116 Figure 44 Multicast source registration Host A Source Receiver Host B Server Receiver Join message Register message Host C Multicast packets As shown in Figure 44, the multicast source registers with the RP as follows: The multicast source S sends the first multicast packet to the multicast group G. When receiving the multicast packet, the source-side DR encapsulates the packet into a PIM register message and unicasts the message to the RP.
Page 117: Bidir-Pim Overview
When the RP receives multicast traffic, it sends an (S, G) source-specific join message toward the multicast source. The routers along the path from the RP to the multicast source constitute an SPT. The subsequent multicast data is forwarded to the RP along the SPT without being encapsulated into register messages.
Page 118 DF election On a subnet with multiple multicast routers, duplicate multicast packets might be forwarded to the RP. To address this issue, BIDIR-PIM uses a designated forwarder (DF) election mechanism to elect a unique DF for each RP on a subnet. Only the DFs can forward multicast data to the RP. DF election is not necessary for an RPL.
Page 119 Figure 46 RPT building at the receiver side Source Receiver Host A Server B Source Receiver Host B Server A Receiver Join message Receiver-side RPT Multicast packets Host C As shown in Figure 46, 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 120: Administrative Scoping Overview
Figure 47 RPT building at the multicast source side Source Receiver Host A Server B Source Receiver Host B Server A Receiver Source-side RPT Multicast packets Host C As shown in Figure 47, 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 121 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 122: Pim-Ssm Overview
Figure 49 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 49, 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 123: Relationship Among Pim Protocols
Figure 50 SPT building in PIM-SSM Host A Source Receiver Host B Server Receiver Subscribe message Multicast packets Host C As shown in Figure 50, 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 124: Pim Support For Vpns
Figure 51 Relationship among PIM protocols A receiver joins multicast group G. G is in the A multicast source is SSM group range? specified? BIDIR-PIM is enabled? An IGMP-SSM mapping is configured for G? PIM-SM runs for G. G has a BIDIR-PIM RP? PIM-SSM runs for G.
Page 125: 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 the PIM-DM graft retry timer (Optional.) Configuring common PIM features Configuration prerequisites Before you configure PIM-DM, configure a unicast routing protocol so that all devices in the domain can interoperate at the network layer.
Page 126: 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 127: 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 both in a •...
Page 128: Configuring An Rp
Step Command Remarks Enable IP multicast routing multicast routing [ vpn-instance By default, IP multicast routing is and enter MRIB view. vpn-instance-name ] disabled. Return to system view. quit 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.
Page 129 BSR does not receive any advertisement message when the timer expires, it considers the C-RP failed or unreachable. A C-RP policy enables the BSR to filter C-RP advertisement messages by using an ACL that specifies the packet source address range and multicast groups. It is used to guard against C-RP spoofing.
Page 130: Configuring A Bsr
Anycast RP set, the lowest IP address becomes the RP member address. The rest of the interface addresses become backup RP member addresses. To configure Anycast RP: Step Command Remarks Enter system view. system-view vpn-instance Enter PIM view. vpn-instance-name ] By default, Anycast RP is not configured.
Page 131 affected. For more information about static multicast routes, see "Configuring multicast routing and forwarding." To configure a C-BSR: Step Command Remarks Enter system view. system-view vpn-instance Enter PIM view. vpn-instance-name ] c-bsr ip-address scope group-address { mask-length | Configure a C-BSR. By default, no C-BSRs exist.
Page 132: Configuring Multicast Source Registration
NOTE: Generally, a BSR performs BSM semantic fragmentation according to the MTU of its BSR interface. For BSMs originated due to learning of a new PIM neighbor, semantic fragmentation is performed according to the MTU of the interface that sends the BSMs. Disabling BSM forwarding out of incoming interfaces By default, the device is enabled to forward BSMs out of incoming interfaces.
Page 133: Configuring The Switchover To Spt
To configure multicast source registration: Step Command Remarks Enter system view. system-view vpn-instance Enter PIM view. vpn-instance-name ] By default, no PIM register policy Configure a PIM register exists, register register-policy ipv4-acl-number policy. messages are regarded as legal. Configure device By default, the device calculates calculate checksum...
Page 134: Configuration Prerequisites
Tasks at a glance Remarks on a network without C-RPs. • (Required.) Configuring a C-BSR • (Optional.) Configuring a PIM domain border • (Optional.) Disabling BSM semantic fragmentation • (Optional.) Disabling BSM forwarding out of incoming interfaces (Optional.) Configuring common PIM features Configuration prerequisites Before you configure BIDIR-PIM, configure a unicast routing protocol so that all devices in the domain can interoperate at the network layer.
Page 135 An RP can be manually configured or dynamically elected through the BSR mechanism. For a large-scaled PIM network, configuring static RPs is a tedious job. Generally, static RPs are backups for dynamic RPs to enhance the robustness and operational manageability on a multicast network. Configuring a static RP If only one dynamic RP exists on a network, you can configure a static RP to avoid communication interruption caused by single-point failures.
Page 136: Configuring A Bsr
Step Command Remarks Enter system view. system-view vpn-instance Enter PIM view. vpn-instance-name ] c-rp ip-address advertisement-interval Configure a C-RP to provide By default, no C-RPs exist. adv-interval group-policy services for BIDIR-PIM. ipv4-acl-number holdtime hold-time | priority priority ] * bidir Enabling Auto-RP listening This feature enables the device to receive Auto-RP announcement and discovery messages and learn RP information.
Page 137 Configuring a C-BSR IMPORTANT: Because the BSR and other devices exchange a large amount of information in the BIDIR-PIM domain, reserve a large bandwidth between the C-BSR and other devices. The BSR election process is summarized as follows: Initially, each C-BSR regards itself as the BSR of the BIDIR-PIM domain and sends BSMs to other routers in the domain.
Page 138 To configure a PIM domain border: Step Command Remarks Enter system view. system-view 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 139: Configuring The Ssm Group Range
Configuring PIM-SSM PIM-SSM requires IGMPv3 support. Enable IGMPv3 on PIM routers that connect to multicast receivers. PIM-SSM configuration task list Tasks at a glance (Required.) Enabling PIM-SM (Optional.) Configuring the SSM group range (Optional.) Configuring common PIM features Configuration prerequisites Before you configure PIM-SSM, configure a unicast routing protocol so that all devices in the domain can interoperate at the network layer.
Page 140: Configuring Common Pim Features
• Configure the same SSM group range on all routers in the entire PIM-SSM domain. Otherwise, multicast information cannot be delivered through the SSM model. • When a member of a multicast group in the SSM group range sends an IGMPv1 or IGMPv2 report message, the device does not trigger a (*, G) join.
Page 141: Configuring A Pim Hello Policy
Step Command Remarks Enter system view. system-view vpn-instance Enter PIM view. vpn-instance-name ] By default, no multicast source Configure a multicast source policy exists. The device does not source-policy ipv4-acl-number policy. filter multicast data packets. Configuring a PIM hello policy This feature enables the device to filter PIM hello messages by using an ACL that specifies the packet source addresses.
Page 142 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 143: Configuring Common Pim Timers
Step Command Remarks Enable dropping hello By default, an interface accepts messages without hello messages without pim require-genid Generation ID option. Generation ID option. Configuring common 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 144: Setting The Maximum Size Of A Join Or Prune Message
Configuring common PIM timers on an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Set the hello interval. The default setting is 30 seconds. pim timer hello interval Set the triggered hello delay. The default setting is 5 seconds. pim triggered-hello-delay delay The default setting is 60 seconds.
Page 145: Enabling Pim Passive Mode
Enabling PIM passive mode To guard against PIM hello spoofing, you can enable PIM passive mode on a receiver-side interface. The PIM passive interface cannot receive or forward PIM protocol messages (excluding register, register-stop and C-RP-Adv messages), and it acts as the DR on the subnet. In BIDIR-PIM, it also acts as the DF.
Page 146: Displaying And Maintaining Pim
Setting a DSCP value for outgoing PIM messages To control the transmission preference of outgoing PIM messages, set a DSCP value for outgoing PIM messages. To set a DSCP value for outgoing PIM messages: Step Command Remarks Enter system view. system-view vpn-instance Enter PIM view.
Page 147: Pim Configuration Examples
PIM configuration examples PIM-DM configuration example Network requirements As shown in Figure • OSPF runs on the network. • VOD streams are sent to receiver hosts in multicast. The receiver groups of different organizations form stub networks, and one or more receiver hosts exist on each stub network. •...
Page 148 Configure OSPF on the switches in the PIM-DM domain. (Details not shown.) Enable IP multicast routing, IGMP, and PIM-DM: # On Switch A, enable IP multicast routing. <SwitchA> system-view [SwitchA] multicast routing [SwitchA-mrib] quit # Enable IGMP on VLAN-interface 100 (the interface that connects to the stub network). [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] igmp enable [SwitchA-Vlan-interface100] quit...
Page 149 192.168.3.1 Vlan102 00:00:23 00:01:31 5 # Send an IGMP report from Host A to join multicast group 225.1.1.1. (Details not shown.) # Send multicast data from multicast source 10.110.5.100/24 to multicast group 225.1.1.1. (Details not shown.) # Display PIM routing entries on Switch A. [SwitchA] display pim routing-table Total 1 (*, G) entry;...
Page 150: Pim-Sm Non-Scoped Zone Configuration Example
• Switch A has the correct (*, G) entry. PIM-SM non-scoped zone configuration example Network requirements As shown in Figure • OSPF runs on the network. • VOD streams are sent to receiver hosts in multicast. The receivers of different subnets form stub networks, and a minimum of one receiver host exist on each stub network.
Page 151 Device Interface IP address Device Interface IP address Switch C Vlan-int200 10.110.2.2/24 Switch E Vlan-int102 192.168.9.2/24 Switch C Vlan-int104 192.168.3.1/24 Switch E Vlan-int105 192.168.4.1/24 Configuration procedure Assign an IP address and subnet mask to each interface, as shown in Figure 53.
Page 152: Pim-Sm Admin-Scoped Zone Configuration Example
Verifying the configuration # Display PIM information on Switch A. [SwitchA] display pim interface Interface NbrCnt HelloInt DR-Pri DR-Address Vlan100 10.110.1.1 (local) Vlan101 192.168.1.2 Vlan102 192.168.9.2 # Display BSR information on Switch A. [SwitchA] display pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:44 Elected BSR address: 192.168.9.2 Priority: 64...
Page 153 • VOD streams are sent to receiver hosts in multicast. The entire PIM-SM domain is divided into admin-scoped zone 1, admin-scoped zone 2, and the global-scoped zone. Switch B, Switch C, and Switch D are ZBRs of the three zones, respectively. •...
Page 154 Device Interface IP address Device Interface IP address Switch C Vlan-int104 10.110.4.1/24 Switch F Vlan-int107 10.110.8.2/24 Switch C Vlan-int105 10.110.5.1/24 Switch F Vlan-int102 10.110.3.2/24 Switch C Vlan-int103 10.110.2.2/24 Switch G Vlan-int500 192.168.5.1/24 Switch C Vlan-int106 10.110.6.1/24 Switch G Vlan-int109 10.110.9.2/24 Switch H Vlan-int110 10.110.10.1/24...
Page 155 # Enable IP multicast routing and PIM-SM on Switch C, Switch D, Switch F, Switch G, and Switch H in the same way Switch B is configured. (Details not shown.) Configure admin-scoped zone boundaries: # On Switch B, configure VLAN-interface 102 and VLAN-interface 103 as the boundaries of admin-scoped zone 1.
Page 156 [SwitchF-pim] c-bsr 10.110.9.1 [SwitchF-pim] c-rp 10.110.9.1 [SwitchF-pim] quit Verifying the configuration # Display BSR information on Switch B. [SwitchB] display pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:44 Elected BSR address: 10.110.9.1 Priority: 64 Hash mask length: 30 Uptime: 00:01:45 Scope: 239.0.0.0/8 State: Elected...
Page 157: Bidir-Pim Configuration Example
State: Elected Bootstrap timer: 00:00:49 Elected BSR address: 10.110.9.1 Priority: 64 Hash mask length: 30 Uptime: 00:11:11 Candidate BSR address: 10.110.9.1 Priority: 64 Hash mask length: 30 # Display RP information on Switch B. [SwitchB] display pim rp-info BSR RP information: Scope: non-scoped Group/MaskLen: 224.0.0.0/4 RP address...
Page 158 • VLAN-interface 102 of Switch C acts as the C-BSR. Loopback 0 of Switch C acts as the C-RP. • IGMPv2 runs between Switch B and Host A, and between Switch D and Host B. Figure 55 Network diagram Loop0 Receiver 1 Receiver 2 Switch B...
Page 159 [SwitchA-Vlan-interface101] quit [SwitchA] pim [SwitchA-pim] bidir-pim enable [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.
Page 160 [SwitchD] interface vlan-interface 400 [SwitchD-Vlan-interface400] pim sm [SwitchD-Vlan-interface400] quit [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.
Page 161: Pim-Ssm Configuration Example
Total 1 RP, 1 matched 00001. RP address: 1.1.1.1 Flags: 0x0 Uptime: 00:08:32 RPF interface: Vlan-interface101 List of 1 DF interfaces: 1: Vlan-interface100 # Display information about DFs for multicast forwarding on Switch B. [SwitchB] display multicast forwarding df-info Total 1 RP, 1 matched 00001.
Page 162 • The receivers receive VOD information through multicast. The receiver groups of different organizations form stub networks, and one or more receiver hosts exist on each stub network. • The entire PIM domain operates in the SSM mode. • Host A and Host C are multicast receivers on two stub networks. •...
Page 163 <SwitchA> system-view [SwitchA] multicast routing [SwitchA-mrib] quit # Enable IGMPv3 on VLAN-interface 100 (the interface that connects to the stub network). [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...
Page 164: Troubleshooting Pim
RPF prime neighbor: 192.168.1.2 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: igmp, UpTime: 00:13:25, Expires: 00:03:25 # Display the PIM routing table 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...
Page 165: 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 166 If the problem persists, contact Hewlett Packard Enterprise Support.
Page 167: 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 168 As shown in Figure 57, an MSDP peer can be created on any PIM-SM router. MSDP peers created on PIM-SM routers that assume different roles function differently. • MSDP peers created on RPs: Source-side MSDP peer—MSDP peer closest to the multicast source, such as RP 1. The ...
Page 169 Figure 58 Inter-domain multicast delivery through MSDP Receiver DR 2 MSDP peers Multicast packets SA message RP 2 Join message PIM-SM 2 Register message DR 1 Source PIM-SM 4 RP 1 RP 3 PIM-SM 1 PIM-SM 3 The process of implementing PIM-SM inter-domain multicast delivery by leveraging MSDP peers is as follows: When the multicast source in PIM-SM 1 sends the first multicast packet to multicast group G, DR 1 encapsulates the data within a register message.
Page 170 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 171 Figure 59 Anycast RP through MSDP RP 1 RP 2 Router A Router B PIM-SM Source Receiver MSDP peers SA message The following describes how Anycast RP through MSDP is implemented: a. After receiving the multicast data from Source, the source-side DR registers with the closest RP (RP 1 in this example).
Page 172: Msdp Support For Vpns
Figure 60 MSDP peer-RPF forwarding Source RP 1 RP 5 RP 9 RP 8 AS 1 AS 5 Mesh group AS 3 RP 2 RP 3 AS 2 MSDP peers RP 4 RP 6 RP 7 Static RPF peers AS 4 SA message The process of peer-RPF forwarding is as follows: RP 1 creates an SA message and forwards it to its peer RP 2.
Page 173: 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 174: 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, specify the MSDP peer and the BGP or MBGP peer by using the same IP address.
Page 175: Configuring An Msdp Mesh Group
Configuring a description for an MSDP peer This feature helps administrators easily distinguish an MSDP peer from other MSDP peers. To configure a description for an MSDP peer: Step Command Remarks Enter system view. system-view msdp vpn-instance Enter MSDP view. vpn-instance-name ] Configure a description for By default, no description for an...
Page 176: Configuring Sa Message-Related Parameters
• A new MSDP peer is created. • A previously deactivated MSDP peering connection is reactivated. • A previously failed MSDP peer attempts to resume operation. You can change the MSDP connection retry interval to adjust the interval between MSDP peering connection attempts.
Page 177: Configuring Sa Request Messages
register messages and send them to the source-side RP. The source-side RP transmits the (S, G) information to the remote RP through SA messages. Then, the remote RP sends join messages to the source-side DR and builds an SPT. Because the (S, G) entries have timed out, remote receivers can never receive the multicast data from the multicast source.
Page 178: Configuring Sa Message Policies
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 peer peer-address request messages to an...
Page 179: Configuring The Sa Cache Mechanism
Configuring the SA cache mechanism The SA cache mechanism enables the router to locally cache (S, G) entries contained in SA messages. It reduces the time for obtaining multicast source information, but increases memory occupation. With the SA cache mechanism enabled, when the router receives a new (*, G) join message, it searches its SA message cache first.
Page 180: Msdp Configuration Examples
Task Command listen | shutdown } ] Display MSDP NSR status information. display msdp non-stop-routing status display msdp [ vpn-instance vpn-instance-name ] Display detailed status of MSDP peers. peer-status [ peer-address ] display msdp [ vpn-instance vpn-instance-name ] Display (S, G) entries in the SA cache. sa-cache [ group-address | source-address | as-number ] * display msdp [ vpn-instance vpn-instance-name ]...
Page 181 Figure 61 Network diagram AS 100 AS 200 Receiver Receiver Loop0 Switch F Switch E Vlan-int105 Source 1 Vlan-int105 Vlan-int102 Vlan-int100 PIM-SM 3 Switch A PIM-SM 2 Vlan-int102 Switch B Vlan-int101 Vlan-int104 Vlan-int101 Vlan-int104 Switch C Switch D Loop0 Loop0 Source 2 PIM-SM 1 MSDP peers...
Page 182 [SwitchA-Vlan-interface103] pim sm [SwitchA-Vlan-interface103] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] pim sm [SwitchA-Vlan-interface100] quit # Enable IGMP on the receiver-side interface (VLAN-interface 200). [SwitchA] interface vlan-interface 200 [SwitchA-Vlan-interface200] igmp enable [SwitchA-Vlan-interface200] quit # Enable IP multicast routing and PIM-SM on Switch B, Switch C, Switch D, Switch E, and Switch F in the same way Switch A is configured.
Page 183 [SwitchB-ospf-1] import-route bgp [SwitchB-ospf-1] quit Configure MSDP peers: # Configure an MSDP peer on Switch B. [SwitchB] msdp [SwitchB-msdp] peer 192.168.1.2 connect-interface vlan-interface 101 [SwitchB-msdp] quit # Configure an MSDP peer on Switch C. [SwitchC] msdp [SwitchC-msdp] peer 192.168.1.1 connect-interface vlan-interface 101 [SwitchC-msdp] peer 192.168.3.2 connect-interface vlan-interface 102 [SwitchC-msdp] quit # Configure MSDP peers on Switch E.
Page 184 * > 1.1.1.1/32 192.168.1.1 100? * >i 2.2.2.2/32 0.0.0.0 * > 192.168.1.0 0.0.0.0 * > 192.168.1.1/32 0.0.0.0 * > 192.168.1.2/32 0.0.0.0 # Verify that hosts in PIM-SM 1 and PIM-SM 3 can receive the multicast data from Source 1 in PIM-SM 1 and Source 2 in PIM-SM 2.
Page 185: Inter-As Multicast Configuration By Leveraging Static Rpf Peers
Import policy: None Export policy: None Information about SA-Requests: Policy to accept SA-Requests: None Sending SA-Requests status: Disable Minimum TTL to forward SA with encapsulated data: 0 SAs learned from this peer: 0, SA cache maximum for the peer: 4294967295 Input queue size: 0, Output queue size: 0 Counters for MSDP messages: RPF check failure: 0...
Page 186 Figure 62 Network diagram AS 100 AS 200 PIM-SM 3 Receiver Switch G Vlan-int106 Vlan-int106 Switch F Loop0 Loop0 Receiver Vlan-int102 Vlan-int102 Switch A Switch C PIM-SM 2 Switch D Switch E Vlan-int103 Vlan-int105 Vlan-int103 Vlan-int105 Vlan-int100 Switch B Source 1 Loop0 Source 2 PIM-SM 1...
Page 187 # Enable PIM-SM on each interface, and enable IGMP on the receiver-side interface (VLAN-interface 200). [SwitchC] interface vlan-interface 102 [SwitchC-Vlan-interface102] pim sm [SwitchC-Vlan-interface102] quit [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] igmp enable [SwitchC-Vlan-interface200] quit [SwitchC] interface vlan-interface 104 [SwitchC-Vlan-interface104] pim sm [SwitchC-Vlan-interface104] quit # Configure Switch A, Switch B, Switch D, Switch E, Switch F, and Switch G in the same way Switch C is configured.
Page 188 [SwitchC] bgp 100 [SwitchC-bgp] router-id 1.1.1.3 [SwitchC-bgp] peer 10.110.4.2 as-number 200 [SwitchC-bgp] address-family ipv4 unicast [SwitchC-bgp-ipv4] peer 10.110.4.2 enable [SwitchC-bgp-ipv4] import-route ospf 1 [SwitchC-bgp-ipv4]quit [SwitchC-bgp] quit # On Switch F, configure an EBGP peer, and redistribute OSPF routing information. [SwitchF] bgp 200 [SwitchF-bgp] router-id 3.3.3.1 [SwitchF-bgp] peer 10.110.4.1 as-number 100 [SwitchF-bgp] address-family ipv4 unicast...
Page 189: Anycast Rp Configuration
# On Switch G, configure Switch A as the MSDP peer and static RPF peer. [SwitchG] ip prefix-list list-a permit 10.110.0.0 16 greater-equal 16 less-equal 32 [SwitchG] msdp [SwitchG-msdp] peer 10.110.2.1 connect-interface vlan-interface 106 [SwitchG-msdp] static-rpf-peer 10.110.2.1 rp-policy list-a [SwitchG-msdp] quit Verifying the configuration # Display the BGP peering relationships on Switch A.
Page 190 Figure 63 Network diagram Source 1 Source 2 Switch A Switch C Switch E Vlan-int300 Vlan-int400 Receiver Receiver Switch B Switch D Vlan-int100 Vlan-int200 Host A Host B Loop10 Loop10 PIM-SM MSDP peers Table 14 Interface and IP address assignment Device Interface IP address...
Page 191 [SwitchB-Vlan-interface100] quit # Enable PIM-SM on the other interfaces. [SwitchB] interface vlan-interface 103 [SwitchB-Vlan-interface103] pim sm [SwitchB-Vlan-interface103] quit [SwitchB] interface Vlan-interface 101 [SwitchB-Vlan-interface101] pim sm [SwitchB-Vlan-interface101] quit [SwitchB] interface loopback 0 [SwitchB-LoopBack0] pim sm [SwitchB-LoopBack0] quit [SwitchB] interface loopback 10 [SwitchB-LoopBack10] pim sm [SwitchB-LoopBack10] quit [SwitchB] interface loopback 20...
Page 192 [SwitchD] display msdp brief Configured Established Listen Connect Shutdown Disabled Peer address State Up/Down time SA count Reset count 1.1.1.1 Established 00:10:57 # Send an IGMP report from Host A to join multicast group 225.1.1.1. (Details not shown.) # Send multicast data from Source 1 to multicast group 225.1.1.1. (Details not shown.) # Display the PIM routing table on Switch D.
Page 193: Sa Message Filtering Configuration
# Display the PIM routing table on Switch D. [SwitchD] display pim routing-table Total 1 (*, G) entry; 1 (S, G) entry (*, 225.1.1.1) RP: 10.1.1.1 (local) Protocol: pim-sm, Flag: WC UpTime: 00:12:07 Upstream interface: Register Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface200...
Page 194 Figure 64 Network diagram PIM-SM 1 PIM-SM 2 PIM-SM 3 Loop0 Source 2 Vlan-int100 Loop0 Switch A Receiver Host A Vlan-int400 Switch C Vlan-int104 Vlan-int104 Switch D Vlan-int300 Vlan-int500 Source 1 Vlan-int200 Switch B Receiver Receiver Host B Host C MSDP peers Table 15 Interface and IP address assignment Device...
Page 195 [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 [SwitchA] interface loopback 0 [SwitchA-LoopBack0] pim sm [SwitchA-LoopBack0] quit # Enable IP multicast routing, IGMP, and PIM-SM on Switch B, Switch C, and Switch D in the same way Switch A is configured.
Page 196: Troubleshooting Msdp
[SwitchC] acl advanced 3001 [SwitchC-acl-ipv4-adv-3001] rule deny ip source 10.110.3.100 0 destination 225.1.1.0 0.0.0.3 [SwitchC-acl-ipv4-adv-3001] rule permit ip source any destination any [SwitchC-acl-ipv4-adv-3001] quit [SwitchC] msdp [SwitchC-msdp] peer 10.110.5.2 sa-policy export acl 3001 [SwitchC-msdp] quit # Configure an SA creation policy on Switch D so that Switch D will not create SA messages for Source 2.
Page 197: Msdp Peers Stay In Disabled State
MSDP peers stay in disabled state Symptom The configured MSDP peers stay in disabled state. Analysis Possible reasons for the problem might include the following: • A TCP connection-based MSDP peering relationship is established between the local interface address and the MSDP peer. •...
Page 198: No Exchange Of Locally Registered (S, G) Entries Between Rps
No exchange of locally registered (S, G) entries between RPs Symptom RPs fail to exchange their locally registered (S, G) entries with one another in the Anycast RP application. Analysis Possible reasons for the problem might include the following: • In the Anycast RP application, RPs in the same PIM-SM domain are configured to be MSDP peers to achieve redundancy backup among the RPs.
Page 199: 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 65, when MLD snooping is not enabled, the Layer 2 switch floods IPv6 multicast...
Page 200 Figure 66 MLD snooping ports Receiver Router A Switch A HGE1/0/1 HGE1/0/2 Host A HGE1/0/3 Host B Receiver HGE1/0/1 HGE1/0/2 Source Host C Switch B Router port Member port IPv6 multicast packets Host D Router ports On an MLD snooping Layer 2 device, the ports toward Layer 3 multicast devices are called router ports.
Page 201: How Mld Snooping Works
How MLD snooping works The ports in this section are dynamic ports. For information about how to configure and remove static ports, see "Configuring static ports." MLD messages include general query, MLD report, and done message. An MLD snooping-enabled Layer 2 device performs differently depending on the MLD message types. General query The MLD querier periodically sends MLD general queries to all hosts and routers on the local subnet to check for the existence of IPv6 multicast group members.
Page 202: Mld Snooping Proxying
• 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.  Sends an MLD multicast-address-specific query to identify whether the group has active ...
Page 203: Mld Snooping Configuration Task List
After receiving an MLD general query, the device forwards the query to all ports in the VLAN except the receiving port. The device also generates an MLD report based on the local membership information and sends the report to all router ports. •...
Page 204: Mld Snooping Configuration Task List For Vsis
Tasks at a glance • (Optional.) Setting the MLD last listener query interval Configuring MLD snooping port features: • (Optional.) Setting aging timers for dynamic ports • (Optional.) Configuring static ports • (Optional.) Configuring a port as a simulated member host •...
Page 205: Configuring Basic Mld Snooping Features
interfaces do not take part in aggregation calculations. The configuration made on a member port of the aggregate group takes effect after the port leaves the aggregate group. Configuring basic MLD snooping features Before you configure basic MLD snooping features, complete the following tasks: •...
Page 206: Setting The Maximum Number Of Mld Snooping Forwarding Entries
Setting the maximum number of MLD snooping forwarding entries You can modify the maximum number of MLD snooping forwarding entries, including dynamic entries and static entries. When the number of forwarding entries on the device reaches the upper limit, the device does not automatically remove any existing entries. To allow new entries to be created, remove some entries manually.
Page 207: Setting The Mld Last Listener Query Interval
Step Command Remarks By default, no static multicast MAC address entries exist. Configure static IPv6 mac-address multicast multicast address For more information about this mac-address vlan vlan-id entry. command, Multicast Command Reference. Setting the MLD last listener query interval A receiver host starts a report delay timer for an IPv6 multicast group when it receives an MLD multicast-address-specific query for the group.
Page 208: Setting Aging Timers For Dynamic Ports
• Enable MLD snooping for the VLAN or VSI. • Determine the aging timer for dynamic router ports. • Determine the aging timer for dynamic member ports. • Determine the addresses of the IPv6 multicast group and IPv6 multicast source. Setting aging timers for dynamic ports When you set aging timers for dynamic ports, follow these restrictions and guidelines: If the memberships of IPv6 multicast groups frequently change, set a relatively small value for...
Page 209: Configuring Static Ports
Configuring static ports You can configure the following types of static ports: • Static member port—When you configure a port as a static member port for an IPv6 multicast group, all hosts attached to the port will receive IPv6 multicast data for the group. The static member port does not respond to MLD queries.
Page 210: Enabling Fast-Leave Processing
Enabling fast-leave processing This feature enables the device to immediately remove a port from the forwarding entry for an IPv6 multicast group when the port receives a done message. Configuration restrictions and guidelines When you enable fast-leave processing, follow these restrictions and guidelines: •...
Page 211: Enabling Inner Vlan Id-Based Forwarding
Step Command Remarks Enter system view. system-view Enter Layer Ethernet interface interface-type interface view or Layer 2 interface-number aggregate interface view. By default, a port is allowed to Disable port from become a dynamic router port. mld-snooping router-port-deny becoming a dynamic router [ vlan vlan-list ] This configuration does not affect port.
Page 212: Configuring Parameters For Mld General Queries And Responses
• On a VXLAN network, the MLD snooping querier in a VSI does not include VLAN tags in MLD general queries. As a best practice, do not enable the MLD snooping querier in a VSI if the VSI uses the Ethernet access mode. For more information about the Ethernet access mode, see VXLAN Configuration Guide.
Page 213: Enabling Mld Snooping Proxying
Configuring parameters for MLD general queries and responses in a VLAN or VSI Step Command Remarks Enter system view. system-view • Enter VLAN view: Enter VLAN view or VSI vlan vlan-id view. • Enter view: vsi vsi-name Set the MLD general query default setting mld-snooping...
Page 214 Configuring the source IPv6 address for MLD messages in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id By default, the source IPv6 address of MLD general queries is the IPv6 link-local address of the Configure the source IPv6 current VLAN interface.
Page 215: Setting The 802.1P Priority For Mld Messages
Step Command Remarks address for MLD general address of MLD general queries is source-ip ipv6-address queries. the IPv6 link-local address of the gateway interface for a VSI. If the gateway interface does not have an IPv6 link-local address, the source IPv6 address FE80::02FF:FFFF:FE00:0001.
Page 216: Configuring Mld Snooping Policies
Step Command Remarks Enter MLD-snooping view. mld-snooping By default, the 802.1p priority for MLD messages is not configured. For MLD messages created by the Set the 802.1p priority for device, the 802.1p priority is 0. For dot1p-priority priority MLD messages. MLD messages to be forwarded, the device does not change the 802.1p priority.
Page 217: Enabling Ipv6 Multicast Source Port Filtering
Step Command Remarks join any IPv6 multicast groups. Configuring an IPv6 multicast group policy on a port Step Command Remarks Enter system view. system-view Enter Layer Ethernet interface interface-type interface view or Layer 2 interface-number aggregate interface view. By default, no IPv6 multicast Configure an IPv6 multicast group policies exist on a port.
Page 218: Enabling Mld Report Suppression
To enable dropping unknown IPv6 multicast data in a VLAN or VSI: Step Command Remarks Enter system view. system-view • Enter VLAN view: Enter VLAN view or VSI vlan vlan-id view. • Enter view: vsi vsi-name By default, dropping unknown Enable dropping unknown IPv6 multicast data is disabled, IPv6 multicast data for the...
Page 219: Enabling Ipv6 Multicast Group Replacement
Step Command Remarks Set the maximum number of By default, no limit is placed on mld-snooping group-limit limit IPv6 multicast groups on the the maximum number of IPv6 [ vlan vlan-list ] port. multicast groups on a port. Enabling IPv6 multicast group replacement This feature enables the device to replace an existing group with a newly joined group when the number of groups exceeds the upper limit.
Page 220: Displaying And Maintaining Mld Snooping
Enabling host tracking in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Enable host tracking for the default, host tracking mld-snooping host-tracking VLAN. disabled in a VLAN. Displaying and maintaining MLD snooping Execute display commands in any view and reset commands in user view. Task Command (In standalone mode.) Display Layer...
Page 221 Task Command (In standalone mode.) Display host display mld-snooping host-tracking vlan vlan-id group tracking information. ipv6-group-address [ slot slot-number ] (In IRF mode.) Display host tracking display mld-snooping host-tracking vlan vlan-id group information. ipv6-group-address [ chassis chassis-number slot slot-number ] standalone mode.) Display...
Page 222: Mld Snooping Configuration Examples
MLD snooping configuration examples IPv6 group policy and simulated joining configuration example (for VLANs) Network requirements As shown in Figure 68, Router A runs MLDv1 and acts as the MLD querier, and Switch A runs MLDv1 snooping. Configure the group policy and simulate joining to meet the following requirements: •...
Page 223 [RouterA-HundredGigE1/0/2] ipv6 pim dm [RouterA-HundredGigE1/0/2] quit Configure Switch A: # Enable MLD snooping globally. <SwitchA> system-view [SwitchA] mld-snooping [SwitchA-mld-snooping] quit # Create VLAN 100, and assign HundredGigE 1/0/1 through HundredGigE 1/0/4 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port hundredgige 1/0/1 to hundredgige 1/0/4 # Enable MLD snooping, and enable dropping IPv6 unknown multicast data for VLAN 100.
Page 224: Static Port Configuration Example (For Vlans)
Static port configuration example (for VLANs) Network requirements As shown in Figure • Router A runs MLDv1 and acts as the MLD querier. Switch A, Switch B, and Switch C run MLDv1 snooping. • Host A and Host C are permanent receivers of IPv6 multicast group FF1E::101. Configure static ports to meet the following requirements: •...
Page 225 [RouterA-mrib6] quit # Enable MLD on HundredGigE 1/0/1. [RouterA] interface hundredgige 1/0/1 [RouterA-HundredGigE1/0/1] mld enable [RouterA-HundredGigE1/0/1] quit # Enable IPv6 PIM-DM on HundredGigE 1/0/2. [RouterA] interface hundredgige 1/0/2 [RouterA-HundredGigE1/0/2] ipv6 pim dm [RouterA-HundredGigE1/0/2] quit Configure Switch A: # Enable MLD snooping globally. <SwitchA>...
Page 226: Mld Snooping Querier Configuration Example (For Vlans)
# Configure HundredGigE 1/0/3 and HundredGigE 1/0/5 as static member ports for IPv6 multicast group FF1E::101. [SwitchC] interface hundredgige 1/0/3 [SwitchC-HundredGigE1/0/3] mld-snooping static-group ff1e::101 vlan 100 [SwitchC-HundredGigE1/0/3] quit [SwitchC] interface hundredgige 1/0/5 [SwitchC-HundredGigE1/0/5] mld-snooping static-group ff1e::101 vlan 100 [SwitchC-HundredGigE1/0/5] quit Verifying the configuration # Display brief information about static router ports for VLAN 100 on Switch A.
Page 227 Figure 70 Network diagram Source 1 Source 2 VLAN 100 1::10/64 1::20/64 Receiver Receiver HGE1/0/2 HGE1/0/2 HGE1/0/1 HGE1/0/3 HGE1/0/3 HGE1/0/1 Host A Host B HGE1/0/4 Switch A Switch B Querier Receiver Receiver HGE1/0/2 HGE1/0/1 HGE1/0/2 HGE1/0/3 HGE1/0/1 Host D Host C Switch D Switch C Configuration procedure...
Page 228: Mld Snooping Proxying Configuration Example (For Vlans)
<SwitchC> system-view [SwitchC] mld-snooping [SwitchC-mld-snooping] quit # Create VLAN 100, and assign HundredGigE 1/0/1 through HundredGigE 1/0/3 to the VLAN. [SwitchC] vlan 100 [SwitchC-vlan100] port hundredgige 1/0/1 to hundredgige 1/0/3 # Enable MLD snooping, and enable dropping unknown IPv6 multicast data for VLAN 100. [SwitchC-vlan100] mld-snooping enable [SwitchC-vlan100] mld-snooping drop-unknown [SwitchC-vlan100] quit...
Page 229 • Forward MLD report and done messages to Router A. • Respond to MLD queries sent by Router A and forward the queries to downstream hosts. Figure 71 Network diagram Receiver Host A Source Receiver HGE1/0/4 HGE1/0/1 HGE1/0/2 2001::1/64 HGE1/0/1 HGE1/0/3 1::2/64 Switch A...
Page 230: Troubleshooting Mld Snooping
[SwitchA-vlan100] mld-snooping proxy enable [SwitchA-vlan100] quit Verifying the configuration # Send MLD reports from Host A and Host B to IPv6 multicast group FF1E::101. (Details not shown.) # Display brief information about MLD snooping group entries on Switch A. [SwitchA] display mld-snooping group Total 1 entries.
Page 231: Ipv6 Multicast Group Policy Does Not Work
Use the display mld-snooping command to display MLD snooping status. If MLD snooping is not enabled, use the mld-snooping command in system view to enable MLD snooping globally. Then, use the mld-snooping enable command in VLAN view or VSI view to enable MLD snooping for the VLAN or VSI. If MLD snooping is enabled globally but not enabled for the VLAN or VSI, use the mld-snooping enable command in VLAN view or VSI view to enable MLD snooping for the VLAN or VSI.
Page 232: 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 233: 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 234: Support And Other Resources
Support and other resources Accessing Hewlett Packard Enterprise Support • For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: www.hpe.com/assistance • To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website: www.hpe.com/support/hpesc Information to collect •...
Page 235: Customer Self Repair
Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document title, 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 236 Index port-based multicast VLAN user port attribute, Numerics IGMP snooping message 802.1p priority, MLD snooping 802.1p message priority, PIM enable, bidirectional BIDIR-PIM bidirectional RPT building, BIDIR-PIM IGMP snooping policy, administrative scoping, MLD snooping policy, Auto-RP listening configuration, address bidirectional RPT building, IP multicast, BSM forwarding disable, MLD snooping message source IPv6 address,...
Page 237 PIM-SM administrative scoping zones, IGMP snooping group policy+simulated joining (for VLAN), PIM-SM BSR configuration, IGMP snooping message parameters, PIM-SM C-BSR configuration, IGMP snooping message source IP address, PIM-SM RP discovery, IGMP snooping multicast group policy, IGMP snooping multicast group policy (port), cache IGMP snooping multicast source port filtering MSDP SA message cache,...
Page 238 PIM-SM C-BSR, MLD snooping querier (for VLAN), MLD snooping report suppression, PIM-SM C-RP, MLD snooping simulated member host port, PIM-SM multicast source registration, PIM-SM non-scoped zone, MLD snooping static port (for VLAN), PIM-SM RP, MLD snooping static ports, PIM-SM SPT switchover, MSDP, 159, 165, 172 PIM-SM static RP,...
Page 239 MSDP inter-AS multicast configuration (static PIM hello message DR_Priority, RPF peers), PIM passive mode enable, MSDP PIM-SM inter-domain multicast PIM-SM DR election, configuration, PIM-SM RPT building, MSDP SA message filtering configuration, PIM-SM SPT switchover, multicast routing RPF route change, PIM-SSM DR election, multicast routing RPF route creation, PIM-SSM SPT building, multicast routing+forwarding configuration,...
Page 240 MLD snooping (VSI view), fast-leave processing MLD snooping fast-leave processing (global), MLD snooping, filtering MLD snooping fast-leave processing (port), IGMP snooping multicast source port filtering, IGMP snooping unknown multicast data drop, MLD snooping host tracking (global), MLD snooping IPv6 multicast source port, MLD snooping host tracking (VLAN), MLD snooping IPv6 multicast unknown data drop, MLD snooping inner VLAN ID-based...
Page 241 port-based multicast VLAN configuration, IGMP snooping multicast group policy, IGMP snooping multicast group replacement, protocols and standards, proxying, IGMP static group member configuration, proxying configuration, 90, 98 MLD snooping IPv6 multicast group policy, proxying enable, query/response parameter configuration, MLD snooping IPv6 multicast group query/response parameter configuration replacement, restrictions,...
Page 242 multicast group policy configuration Internet restrictions, Group Management Protocol. Use IGMP multicast group replacement, interval multicast group replacement restrictions, IGMP snooping last member query interval, multicast groups on port, IP addressing multicast groups on port restrictions, IGMP snooping message source IP address, multicast source port filtering, IP multicast address, policy configuration,...
Page 243 IGMP snooping general query, MLD snooping dynamic router port change, IGMP snooping general query/response MLD snooping fast-leave processing enable, parameters, MLD snooping forwarding entries, IGMP snooping group policy, MLD snooping general query/response IGMP snooping group policy+simulated parameters, joining configuration (for VLAN), MLD snooping group policy, IGMP snooping groups on port, MLD snooping group policy+simulated joining...
Page 244 PIM-SM RPT building, MSDP SA message multicast data encapsulation, PIM-SM source registration, MSDP SA message originating RP, PIM-SM SPT switchover, 108, 125 MSDP SA message policy, PIM-SSM, MSDP SA message-related parameters, PIM-SSM configuration, 131, 153 MSDP SA request message, PIM-SSM DR election, MSDP VPN support, PIM-SSM group range, multicast routing+forwarding.
Page 245 MLD snooping, MLD snooping simulated member host port, MSDP, PIM-DM configuration, multicast routing+forwarding, PIM-SM DR election, multicast VLAN, IPv6 multicast PIM snooping, MLD snooping proxying, 194, 205 mapping static MAC address entry configuration, IGMP SSM mapping, 82, 90 IGMP SSM mapping configuration, MLD snooping configuration, 191, 214 joining...
Page 246 done message, troubleshoot MLD snooping Layer 2 forwarding, dynamic port aging timers, VLAN configuration, dynamic router port change disable, VSI configuration, enable, mode fast-leave processing enable, PIM passive mode enable, fast-leave processing enable restrictions, model forwarding entries, IP multicast, general query, IP multicast ASM, general query/response parameter configuration,...
Page 247 boundary configuration, BIDIR-PIM domain border configuration, configuration, 65, 69, 70, 73 BIDIR-PIM neighbor discovery, display, BIDIR-PIM RP configuration, IP multicast routing enable, BIDIR-PIM RP discovery, load splitting configuration, BIDIR-PIM RP max, longest prefix match principle, BIDIR-PIM static RP configuration, maintain, IGMP basic configuration, 85, 93 multicast hardware resource mode setting,...
Page 248 MSDP peering connection, PIM-SM RP discovery, MSDP peering connection control, PIM-SM RPT building, MSDP PIM-SM inter-domain multicast PIM-SM SPT switchover, 108, 125 configuration, PIM-SM static RP, MSDP RPF static peer, PIM-SM zone relationships, MSDP SA message filtering configuration, PIM-SSM configuration, MSDP SA message-related parameters, PIM-SSM DR election, multicast forwarding across unicast subnets,...
Page 249 option hello message options, PIM hello message DR_Priority, hello policy configuration, PIM hello message Generation ID, join/prune message size, PIM hello message holdtime, multicast source policy, PIM hello message LAN_Prune_Delay, nonstop routing (NSR) enable, PIM hello message options, outgoing packet DSCP value, passive mode enable, passive mode enable restrictions, packet...
Page 250 RPT building, Anycast RP configuration, assert, SPT switchover, Auto-RP listening configuration, SPT switchover configuration, BSM forwarding disable, static RP configuration, BSM semantic fragmentation, troubleshoot multicast source registration failure, BSR configuration, troubleshoot RP cannot be built, C-BSR configuration, troubleshoot RP cannot join SPT, configuration, zone relationships, C-RP configuration,...
Page 251 MLD snooping configuration, 191, 195, 214 configuring BIDIR-PIM RP, MLD snooping dynamic port aging timers, configuring BIDIR-PIM RP max, MLD snooping dynamic router port change, configuring BIDIR-PIM static RP, configuring IGMP, MLD snooping fast-leave processing enable, configuring IGMP basic configuration, configuring IGMP basics, MLD snooping group policy+simulated joining configuring IGMP multicast group policy,...
Page 252 configuring MSDP PIM-SM inter-domain configuring IGMP SSM mapping configuration, multicast, configuring IGMP static group member, configuring MSDP RPF static peer, configuring MSDP SA message cache, configuring IPv6 static multicast MAC address entry, configuring MSDP SA message filtering, configuring MLD snooping, configuring MSDP SA message originating RP, configuring MLD snooping (for VLAN), configuring MLD snooping (for VSI),...
Page 253 enabling IGMP snooping (VLAN view), configuring port-based multicast VLAN user port attribute, enabling IGMP snooping (VSI view), configuring source IP address for IGMP enabling IGMP snooping host tracking (global), message (VLAN), configuring source IP address for IGMP enabling IGMP snooping host tracking (VLAN), message (VSI), enabling IGMP snooping inner VLAN ID-based configuring source IP address for MLD...
Page 254 specifying IGMP snooping version (VLAN view), maintaining multicast routing+forwarding, maintaining multicast VLAN, specifying IGMP snooping version (VSI view), maintaining PIM snooping, specifying IGMP version, setting IGMP last member query interval (global), specifying MSDP peer, setting IGMP last member query interval specifying multicast routing longest prefix match (VLAN), principle,...
Page 255 restrictions MLD snooping proxying configuration (for VLAN), IGMP last member query interval configuration, pruning IGMP multicast forwarding enable, PIM hello message LAN_Prune_Delay option, IGMP query/response parameter configuration, PIM join/prune message size, PIM-DM SPT building, IGMP snooping fast-leave processing enable, IGMP snooping multicast group policy configuration, querier IGMP snooping multicast group replacement,...
Page 256 BIDIR-PIM static RP configuration, MLD snooping configuration, 191, 195, 214 IGMP basic configuration, 85, 93 MLD snooping dynamic router port change, IGMP configuration, 79, 85, 93 MLD snooping forwarding entries, IGMP fast-leave processing, MLD snooping general query/response parameters, IGMP NSR, MLD snooping group policy+simulated joining IGMP performance adjustment, configuration (for VLAN),...
Page 257 MSDP RPF static peer, PIM VPN support, PIM-DM, MSDP SA message originating RP, PIM-DM assert, PIM-SM Anycast RP, 105, 121 PIM-DM configuration, 116, 139 PIM-SM Auto-RP listening, PIM-DM graft, PIM-SM configuration, PIM-DM neighbor discovery, PIM-SM C-RP, PIM-DM SPT building, PIM-SM discovery, PIM-SM, PIM-SM RPT building, PIM-SM administrative scoping,...
Page 258 troubleshooting PIM-SM multicast source IGMP last member query interval (global), registration failure, IGMP last member query interval (VLAN), specifying IGMP last member query interval (VSI), IGMP snooping version, 19, 19 IGMP snooping dynamic port aging timer (global), IGMP snooping version (IGMP-snooping view), IGMP snooping dynamic port aging timer (VLAN, VSI), IGMP snooping version (VLAN view),...
Page 259 switching IP multicast VPN application, IP multicast overview, IP multicast VPN instance, IP multicast transmission techniques, IP multicast VPN support, IP multicast VPN application, trapping IP multicast VPN instance, PIM SNMP notification enable, IP multicast VPN support, troubleshooting MSDP inter-AS multicast configuration (static IGMP, RPF peers), IGMP inconsistent membership information,...
Page 260 VLAN PIM snooping configuration, BIDIR-PIM configuration, PIM-DM configuration, IGMP snooping basic configuration, PIM-SM admin-scoped zone configuration, IGMP snooping configuration, 13, 17, 17, 36 PIM-SM non-scoped zone configuration, IGMP snooping dynamic port aging timer, PIM-SSM configuration, IGMP snooping enable, port-based multicast VLAN configuration, IGMP snooping fast-leave processing, sub-VLAN-based multicast VLAN configuration, IGMP snooping general query/response...
Page 261 PIM-SM admin-scoped/global-scoped zone relationship, PIM-SM non-scoped zone configuration,...

HPE FlexFabric 12900E Series Configuration Manual

Quick Links

Troubleshooting

Related Manuals for HPE FlexFabric 12900E Series

Summary of Contents for HPE FlexFabric 12900E Series