HPE FlexNetwork 5510 HI Series Configuration Manual
  1. Manuals
  2. Brands
  3. HPE Manuals
  4. Switch
  5. FlexNetwork 5510 HI Series
  6. Configuration manual
HPE FlexNetwork 5510 HI Series Configuration Manual

HPE FlexNetwork 5510 HI Series Configuration Manual

Ip multicast
Hide thumbs Also See for FlexNetwork 5510 HI Series:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Configuration Manual, Installation Manual
HPE FlexNetwork 5510 HI Switch Series
IP Multicast

Configuration Guide

Part number: 5200-3625
Software version: Release 13xx
Document version: 6W100-20170315

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the FlexNetwork 5510 HI Series and is the answer not in the manual?

Questions and answers

Related Manuals for HPE FlexNetwork 5510 HI Series

Summary of Contents for HPE FlexNetwork 5510 HI Series

  • Page 1: Configuration Guide

    HPE FlexNetwork 5510 HI Switch Series IP Multicast Configuration Guide Part number: 5200-3625 Software version: Release 13xx Document version: 6W100-20170315...
  • Page 2 © Copyright 2015, 2017 Hewlett Packard Enterprise Development LP The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

  • Page 3: Table Of Contents

    Contents Multicast overview ············································································ 1 Introduction to multicast ··············································································································· 1 Information transmission techniques ························································································ 1 Multicast features ················································································································ 3 Common notations in multicast ······························································································· 4 Multicast benefits and applications ·························································································· 4 Multicast models ························································································································ 4 IP multicast architecture ·············································································································· 5 Multicast addresses ·············································································································...
  • Page 4 Static port configuration example ·························································································· 36 IGMP snooping querier configuration example ········································································· 38 IGMP snooping proxying configuration example ······································································· 41 Troubleshooting IGMP snooping ································································································· 43 Layer 2 multicast forwarding cannot function ··········································································· 43 Multicast group policy does not work ····················································································· 43 Configuring PIM snooping ································································...
  • Page 5 IGMP proxying ·················································································································· 83 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 PIM-SSM configuration task list ·························································································· 131 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 ····························································································...
  • Page 7 No exchange of locally registered (S, G) entries between RPs ·················································· 189 Configuring MLD snooping ····························································· 190 Overview ······························································································································ 190 MLD snooping ports ········································································································· 190 How MLD snooping works ································································································· 192 MLD snooping proxying ···································································································· 193 Protocols and standards ··································································································· 194 MLD snooping configuration task list ··························································································...
  • Page 8 Configuring IPv6 multicast VLANs···················································· 229 Overview ······························································································································ 229 IPv6 multicast VLAN configuration task list ·················································································· 231 Configuring a sub-VLAN-based IPv6 multicast VLAN ····································································· 231 Configuration prerequisites ································································································ 231 Configuration restrictions and guidelines ·············································································· 231 Configuration procedure ··································································································· 231 Configuring a port-based IPv6 multicast VLAN ············································································· 232 Configuration prerequisites ································································································...
  • Page 9 MLD SSM mapping configuration example ············································································ 265 MLD proxying configuration example ··················································································· 267 Troubleshooting MLD ·············································································································· 269 No member information exists on the receiver-side router ························································ 269 Inconsistent membership information on the routers on the same subnet ···································· 269 Configuring IPv6 PIM ···································································· 270 Overview ······························································································································...
  • Page 10 A multicast distribution tree cannot be correctly built ······························································· 326 IPv6 multicast data is abnormally terminated on an intermediate router ······································· 326 An RP cannot join an SPT in IPv6 PIM-SM ··········································································· 327 An RPT cannot be built or IPv6 multicast source registration fails in IPv6 PIM-SM ························· 327 Document conventions and icons ····················································...

  • Page 11: Multicast Overview

    Multicast overview Introduction to multicast As a technique that coexists with unicast and broadcast, the multicast technique effectively addresses the issue of point-to-multipoint data transmission. By enabling high-efficiency point-to-multipoint data transmission over a network, multicast greatly saves network bandwidth and reduces network load.
  • Page 12 Broadcast In broadcast transmission, the information source sends information to all hosts on the subnet, even if some hosts do not need the information. Figure 2 Broadcast transmission Host A Receiver Host B Source Host C Receiver Host D A network segment Receiver Packets for all hosts Host E...

  • Page 13: 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 14: Common Notations In Multicast

    Table 1 Comparing TV program transmission and multicast transmission TV program transmission Multicast transmission A TV station transmits a TV program through a A multicast source sends multicast data to a multicast channel. group. A user tunes the TV set to the channel. A receiver joins the multicast group.

  • Page 15: Ip Multicast Architecture

    ASM model In the ASM model, any multicast sources can send information to a multicast group. Receivers can join a multicast group and get multicast information addressed to that multicast group from any multicast sources. In this model, receivers do not know the positions of the multicast sources in advance.
  • Page 16 Table 2 Class D IP address blocks and description Address block Description Reserved permanent group addresses. The IP address 224.0.0.0 is reserved. Other IP addresses can be used by routing protocols and for topology searching, protocol 224.0.0.0 to 224.0.0.255 maintenance, and so on. Table 3 lists common permanent group addresses.
  • Page 17 Figure 4 IPv6 multicast format 0xFF Flags Scope Group ID (112 bits) The following describes the fields of an IPv6 multicast address: 0xFF—The most significant eight bits are 11111111.  Flags—The Flags field contains four bits.  Figure 5 Flags field format 0 R P T Table 4 Flags field description Description...

  • Page 18: Multicast Protocols

    Value Meaning Global scope. Group ID—The Group ID field contains 112 bits. It uniquely identifies an IPv6 multicast  group in the scope that the Scope field defines. Ethernet multicast MAC addresses • IPv4 multicast MAC addresses: As defined by IANA, the most significant 24 bits of an IPv4 multicast MAC address are 0x01005E.
  • Page 19 Layer 3 multicast protocols—IGMP, MLD, PIM, IPv6 PIM, MSDP, MBGP, and IPv6 MBGP. Layer 2 multicast refers to IP multicast operating at the data link layer.  Layer 2 multicast protocols—IGMP snooping, MLD snooping, PIM snooping, IPv6 PIM snooping, multicast VLAN, and IPv6 multicast VLAN. •...
  • Page 20 An inter-domain multicast routing protocol is used for delivering multicast information  between two ASs. So far, mature solutions include Multicast Source Discovery Protocol (MSDP) and MBGP. MSDP propagates multicast source information among different ASs. MBGP is an extension of the MP-BGP for exchanging multicast routing information among different ASs.

  • Page 21: Multicast Packet Forwarding Mechanism

    Multicast packet forwarding mechanism In a multicast model, receiver hosts of a multicast group are usually located at different areas on the network. They are identified by the same multicast group address. To deliver multicast packets to these receivers, a multicast source encapsulates the multicast data in an IP packet with the multicast group address as the destination address.

  • Page 22: Multicast Application In Vpns

    • The PE devices connect to the public network and the VPNs. Each PE device must strictly distinguish the information for different networks, and maintain a separate forwarding mechanism for each network. On a PE device, a set of software and hardware that serve the same network forms an instance.

  • Page 23: 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 24 Figure 12 IGMP snooping ports Receiver Router A Switch A GE1/0/1 GE1/0/2 Host A GE1/0/3 Host B Receiver GE1/0/1 GE1/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 25: 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 26: 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 27: 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 28: Enabling Igmp Snooping

    Tasks at a glance (Optional.) Enabling IGMP snooping proxying Configuring parameters for IGMP messages: • (Optional.) Configuring source IP addresses for IGMP messages • (Optional.) Setting the 802.1p priority for IGMP messages Configuring IGMP snooping policies: • (Optional.) Configuring a multicast group policy •...

  • Page 29: Enabling Igmp Snooping For A Vlan

    Step Command Remarks By default, the IGMP snooping Enable IGMP snooping for status in a VLAN is consistent with enable vlan vlan-list multiple VLANs. the global IGMP snooping status. Enabling IGMP snooping for a VLAN Step Command Remarks Enter system view. system-view Enable the IGMP snooping By default, the IGMP snooping...

  • Page 30: Setting The Maximum Number Of Igmp Snooping Forwarding Entries

    Specifying an IGMP snooping version in IGMP-snooping view Step Command Remarks Enter system view. system-view Enable IGMP snooping globally and enter igmp-snooping IGMP-snooping view. Specify an IGMP snooping version version-number vlan version for the specified The default setting is 2. vlan-list VLANs.

  • Page 31: Setting The Igmp Last Member Query Interval

    • You can configure static multicast MAC address entries on the specified interfaces in system view or on the current interface in interface view. Configuring a static multicast MAC address entry in system view Step Command Remarks Enter system view. system-view mac-address multicast Configure a static multicast...

  • Page 32: Configuring Igmp Snooping Port Features

    Setting the IGMP last member query interval in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id igmp-snooping Set the IGMP last member The default setting is 1 last-member-query-interval query interval for the VLAN. second. interval Configuring IGMP snooping port features Before you configure IGMP snooping port features, complete the following tasks:...

  • Page 33: Configuring Static Ports

    Setting the aging timers for dynamic ports in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Set the aging timer for The default setting is 260 igmp-snooping dynamic router ports in the seconds. router-aging-time seconds VLAN.

  • Page 34: Enabling Fast-Leave Processing

    To configure a port as a simulated member host: Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface-type interface view or Layer 2 interface-number aggregate interface view. igmp-snooping host-join Configure the port as a By default, the port is not a group-address [ source-ip simulated member host.

  • Page 35: Configuring The Igmp Snooping Querier

    • All multicast data for the VLAN to which the port belongs flows to the port. Then, the port forwards the data to attached receiver hosts. The receiver hosts will receive multicast data that it does not want to receive. •...

  • Page 36: Configuring Parameters For Igmp General Queries And Responses

    Step Command Remarks Enable the IGMP snooping By default, the IGMP snooping igmp-snooping querier querier. querier is disabled. 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.

  • Page 37: Configuring Parameters For Igmp Messages

    Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Enable IGMP snooping By 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 38: Setting The 802.1P Priority For Igmp Messages

    Step Command Remarks IGMP snooping querier of the VLAN has received IGMP general queries. • The IP address of the current VLAN interface if the IGMP snooping querier does not 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...

  • Page 39: Configuring Igmp Snooping Policies

    Step Command Remarks VLAN. For IGMP packets created by the priority device, the 802.1p priority is 0. For IGMP packets to be forwarded, the device does not change the 802.1p priority. Configuring IGMP snooping policies Before you configure IGMP snooping policies, complete the following tasks: •...

  • Page 40: Enabling Multicast Source Port Filtering

    Enabling multicast source port filtering This feature enables the device to discard all multicast data packets and to accept multicast protocol packets. You can enable this feature on ports that connect only to multicast receivers. You can enable this feature for the specified ports in IGMP-snooping view or for a port in interface view.

  • Page 41: Enabling Igmp Report Suppression

    Enabling dropping unknown multicast data in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id By default, dropping unknown Enable dropping unknown multicast data is disabled, and igmp-snooping drop-unknown multicast data for the VLAN. unknown multicast data is flooded.

  • Page 42: Enabling Multicast Group Replacement

    Enabling 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. This feature is typically used in the channel switching application. Without this feature, the device discards IGMP reports for new groups, and the user cannot change to the new channel.

  • Page 43: Displaying And Maintaining Igmp Snooping

    Step Command Remarks Enter VLAN view. vlan vlan-id Enable host tracking for the By default, host tracking is igmp-snooping host-tracking VLAN. disabled for a VLAN. Displaying and maintaining IGMP snooping Execute display commands in any view and reset commands in user view. Task Command Display IGMP snooping status.

  • Page 44: Igmp Snooping Configuration Examples

    IGMP snooping configuration examples Group policy and simulated joining configuration example Network requirements As shown in Figure 14, Router A runs IGMPv2 and acts as the IGMP querier. Switch A runs IGMPv2 snooping. Configure a multicast group policy and simulated joining to meet the following requirements: •...
  • Page 45 Configure Switch A: # Enable the IGMP snooping feature. <SwitchA> system-view [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 100, and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/4 # Enable IGMP snooping, and enable dropping unknown multicast data for VLAN 100. [SwitchA-vlan100] igmp-snooping enable [SwitchA-vlan100] igmp-snooping drop-unknown [SwitchA-vlan100] quit...

  • Page 46: Static Port Configuration Example

    Static port configuration example Network requirements As shown in Figure • Router A runs IGMPv2 and acts as the IGMP querier. Switch A, Switch B, and Switch C run IGMPv2 snooping. • Host A and host C are permanent receivers of multicast group 224.1.1.1. Configure static ports to meet the following requirements: •...
  • Page 47 [RouterA-GigabitEthernet1/0/1] igmp enable [RouterA-GigabitEthernet1/0/1] quit # Enable PIM-DM on GigabitEthernet 1/0/2. [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] pim dm [RouterA-GigabitEthernet1/0/2] quit Configure Switch A: # Enable the IGMP snooping feature. <SwitchA> system-view [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 100, and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3 to the VLAN.

  • Page 48: Igmp Snooping Querier Configuration Example

    [SwitchC] interface gigabitethernet 1/0/3 [SwitchC-GigabitEthernet1/0/3] igmp-snooping static-group 224.1.1.1 vlan 100 [SwitchC-GigabitEthernet1/0/3] quit [SwitchC] interface gigabitethernet 1/0/5 [SwitchC-GigabitEthernet1/0/5] igmp-snooping static-group 224.1.1.1 vlan 100 [SwitchC-GigabitEthernet1/0/5] quit Verifying the configuration # Display static router port information for VLAN 100 on Switch A. [SwitchA] display igmp-snooping static-router-port vlan 100 VLAN 100: Router ports (1 in total): GE1/0/3...
  • Page 49 Figure 16 Network diagram Source 1 Source 2 VLAN 100 192.168.1.10/24 192.168.1.20/24 Receiver Receiver GE1/0/2 GE1/0/2 GE1/0/1 GE1/0/3 GE1/0/3 GE1/0/1 Host A Host B GE1/0/4 Switch A Switch B Querier Receiver Receiver GE1/0/2 GE1/0/1 GE1/0/2 GE1/0/3 GE1/0/1 Host D Host C Switch D Switch C Configuration procedure...
  • Page 50 [SwitchB-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/4 # Enable IGMP snooping, and enable dropping unknown multicast data for VLAN 100. [SwitchB-vlan100] igmp-snooping enable [SwitchB-vlan100] igmp-snooping drop-unknown [SwitchB-vlan100] quit Configure Switch C: # Enable the IGMP snooping feature. <SwitchC> system-view [SwitchC] igmp-snooping [SwitchC-igmp-snooping] quit # Create VLAN 100, and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3 to the VLAN.

  • Page 51: Igmp Snooping Proxying Configuration Example

    Received error IGMP messages: The output shows that all switches except Switch A can receive the IGMP general queries after Switch A acts as the IGMP snooping querier. IGMP snooping proxying configuration example Network requirements As shown in Figure 17, Router A runs IGMPv2 and acts as the IGMP querier. Switch A runs IGMPv2 snooping.
  • Page 52 # Enable the IGMP snooping feature. <SwitchA> system-view [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 100, and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 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...

  • Page 53: Troubleshooting Igmp Snooping

    Troubleshooting IGMP snooping Layer 2 multicast forwarding cannot function Symptom Layer 2 multicast forwarding cannot function on the Layer 2 device. 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 the IGMP snooping feature.

  • 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: a.

  • Page 56: Displaying And Maintaining Pim Snooping

    Step Command Remarks time for global downstream A global downstream port or a global graceful-restart ports and global router ports router port is a Layer 2 aggregate join-aging-time seconds on the master device after a interface that acts as a downstream master/subordinate port or router port.

  • Page 57: Configuration Procedure

    Figure 19 Network diagram Source 1 Receiver 1 Router A Router C GE1/0/1 GE1/0/2 GE1/0/2 GE1/0/1 1.1.1.1/24 10.1.1.1/24 10.1.1.3/24 3.1.1.1/24 1.1.1.100/24 3.1.1.100/24 Switch A GE1/0/1 GE1/0/3 GE1/0/2 GE1/0/4 Source 2 Receiver 2 GE1/0/1 GE1/0/2 GE1/0/2 GE1/0/1 2.1.1.1/24 10.1.1.2/24 10.1.1.4/24 4.1.1.1/24 2.1.1.100/24 4.1.1.100/24 Router B...
  • Page 58 [RouterB-GigabitEthernet1/0/1] pim sm [RouterB-GigabitEthernet1/0/1] quit [RouterB] interface gigabitethernet 1/0/2 [RouterB-GigabitEthernet1/0/2] pim sm [RouterB-GigabitEthernet1/0/2] quit # Set the maximum size of a join or prune message to 1400 bytes. [RouterB] pim [RouterB-pim] jp-pkt-size 1400 Configure Router C: # Enable IP multicast routing. <RouterC>...

  • Page 59: Verifying The Configuration

    [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/4 # Enable IGMP snooping and PIM snooping for VLAN 100. [SwitchA-vlan100] igmp-snooping enable [SwitchA-vlan100] pim-snooping enable [SwitchA-vlan100] quit Verifying the configuration # On Switch A, display PIM snooping neighbor information for VLAN 100. [SwitchA] display pim-snooping neighbor vlan 100 Total 4 neighbors.

  • Page 60: Troubleshooting Pim Snooping

    • Switch A will forward the multicast data intended for multicast group 224.1.1.1 only to Router C. • Switch A will forward the multicast data intended for multicast group 225.1.1.1 only to Router D. Troubleshooting PIM snooping PIM snooping does not work on a Layer 2 device Symptom PIM snooping does not work on a Layer 2 device.

  • 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 A Port-Based Multicast Vlan

    Step Command Remarks view. multicast VLAN. Assign the specified VLANs By default, a multicast VLAN does to the multicast VLAN as subvlan vlan-list not have any sub-VLANs. sub-VLANs. 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: •...

  • Page 65: Setting The Maximum Number Of Multicast Vlan Forwarding Entries

    Configuration procedure To assign user ports to a multicast VLAN in multicast VLAN view: Step Command Remarks Enter system view. system-view Configure a VLAN as a By default, a VLAN is not a multicast VLAN and enter its multicast-vlan vlan-id multicast VLAN.

  • Page 66: Displaying And Maintaining Multicast Vlans

    Displaying and maintaining multicast VLANs Execute display commands in any view and reset commands in user view. Task Command Display information about multicast display multicast-vlan [ vlan-id ] VLANs. Display information about multicast display multicast-vlan group [ source-address | group-address | groups in multicast VLANs.
  • Page 67 Figure 23 Network diagram Source GE1/0/2 IGMP querier Vlan-int20 Switch A 1.1.1.2/24 GE1/0/1 1.1.1.1/24 Vlan-int10 10.110.1.1/24 GE1/0/1 Switch B GE1/0/2 GE1/0/4 GE1/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 the IGMP snooping feature. <SwitchB> system-view [SwitchB] igmp-snooping [SwitchB-igmp-snooping] quit # Create VLAN 2, assign GigabitEthernet 1/0/2 to the VLAN, and enable IGMP snooping for the VLAN. [SwitchB] vlan 2 [SwitchB-vlan2] port gigabitethernet 1/0/2 [SwitchB-vlan2] igmp-snooping enable [SwitchB-vlan2] quit # Create VLAN 3, assign GigabitEthernet 1/0/3 to the VLAN, and enable IGMP snooping 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 GigabitEthernet 1/0/2 to the VLAN. [SwitchA] vlan 20 [SwitchA-vlan20] port gigabitethernet 1/0/2 [SwitchA-vlan20] quit # Assign an IP address to VLAN-interface 20, and enable PIM-DM on the interface. [SwitchA] interface vlan-interface 20 [SwitchA-Vlan-interface20] ip address 1.1.1.2 24 [SwitchA-Vlan-interface20] pim dm [SwitchA-Vlan-interface20] quit...
  • Page 71 # Assign GigabitEthernet 1/0/2 to VLAN 2 and VLAN 10 as an untagged VLAN member. [SwitchB-GigabitEthernet1/0/2] port hybrid vlan 2 untagged [SwitchB-GigabitEthernet1/0/2] port hybrid vlan 10 untagged [SwitchB-GigabitEthernet1/0/2] quit # Configure GigabitEthernet 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): GE1/0/2 (00:03:23) GE1/0/3 (00:04:07) GE1/0/4 (00:04:16) The output shows that IGMP snooping maintains the user ports in 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 Enable multicast forwarding By default, multicast data cannot between sub-VLANs that are be forwarded between multicast forwarding supervlan associated with a super sub-VLANs that are associated community VLAN. with a super VLAN. reset multicast [ vpn-instance vpn-instance-name ] forwarding-table Clear all multicast forwarding { { source-address [ mask...

  • Page 81: Multicast Routing And Forwarding Configuration Examples

    Task Command display multicast [ vpn-instance vpn-instance-name ] Display static multicast routing entries. routing-table static [ source-address { mask-length | mask } ] Display RPF information for a multicast display multicast [ vpn-instance vpn-instance-name ] source. rpf-info source-address [ group-address ] Clear statistics for multicast forwarding reset multicast [ vpn-instance vpn-instance-name ] events.
  • Page 82 Figure 29 Network diagram Switch C Vlan-int103 Vlan-int101 40.1.1.1/24 20.1.1.2/24 PIM-DM Vlan-int103 Vlan-int101 40.1.1.2/24 20.1.1.1/24 Switch A Switch B Vlan-int102 Vlan-int102 30.1.1.2/24 30.1.1.1/24 Vlan-int200 Vlan-int100 50.1.1.1/24 10.1.1.1/24 Source Receiver 50.1.1.100/24 10.1.1.100/24 Static multicast route Configuration procedure Assign an IP address and subnet mask for each interface, as shown in Figure 29.

  • Page 83: Creating An Rpf Route

    [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. (Details not shown.) Display RPF information for Source on Switch B.
  • Page 84 Figure 30 Network diagram PIM-DM OSPF domain Switch A Switch B Switch C Vlan-int102 Vlan-int102 Vlan-int101 30.1.1.2/24 30.1.1.1/24 20.1.1.1/24 Vlan-int101 20.1.1.2/24 Vlan-int300 Vlan-int200 Vlan-int100 50.1.1.1/24 40.1.1.1/24 10.1.1.1/24 Source 2 Source 1 Receiver 50.1.1.100/24 40.1.1.100/24 10.1.1.100/24 Static multicast route Configuration procedure Assign an IP address and subnet mask for each interface, as shown in Figure 30.

  • Page 85: Multicast Forwarding Over A Gre Tunnel

    [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. Configure a static multicast route: # Configure a static multicast route on Switch B and specify Switch A as its RPF neighbor on the route to Source 2.
  • Page 86 Figure 31 Network diagram Multicast router Unicast router Multicast router Switch A Switch B Switch C Vlan-int101 Vlan-int102 Vlan-int101 Vlan-int102 20.1.1.1/24 30.1.1.2/24 20.1.1.2/24 30.1.1.1/24 GE1/0/3 GE1/0/3 Vlan-int100 Vlan-int200 GRE tunnel 10.1.1.1/24 40.1.1.1/24 Tunnel2 Tunnel2 50.1.1.1/24 50.1.1.2/24 Source Receiver Member port of a service loopback group 10.1.1.100/24 40.1.1.100/24 Configuration procedure...
  • Page 87 [SwitchC-Tunnel2] destination 20.1.1.1 [SwitchC-Tunnel2] quit Enable IP multicast routing, PIM-DM, and IGMP: # On Switch A, enable multicast routing. [SwitchA] multicast routing [SwitchA-mrib] quit # Enable PIM-DM on each interface. [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] pim dm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim dm [SwitchA-Vlan-interface101] quit [SwitchA] interface tunnel 2...

  • Page 88: Troubleshooting Multicast Routing And Forwarding

    Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface200 Protocol: igmp, UpTime: 00:04:25, Expires: - (10.1.1.100, 225.1.1.1) Protocol: pim-dm, Flag: ACT UpTime: 00:06:14 Upstream interface: Tunnel2 Upstream neighbor: 50.1.1.1 RPF prime neighbor: 50.1.1.1 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface200 Protocol: pim-dm, UpTime: 00:04:25, Expires: - The output shows that Switch A is the RPF neighbor of Switch C and the multicast data from Switch...

  • Page 89: 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 90: 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 91: 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 92: 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 93: Igmp Proxying

    Figure 34 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 34, on an SSM network, Host A, Host B, and Host C run IGMPv1, IGMPv2, and IGMPv3, respectively.

  • Page 94: Igmp Support For Vpns

    Figure 35 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 95: 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 96: 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 97: 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 on an 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 98 • 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 99: Enabling Fast-Leave Processing

    Configuring the IGMP query and response parameters on an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Set the IGMP querier's By default, the IGMP querier's igmp robust-count count robustness variable. robustness variable is 2. By default, the IGMP startup Set the IGMP startup query query interval equals one quarter...

  • Page 100: Configuring Igmp Ssm Mappings

    Configuring IGMP SSM mappings This feature enables the device to provide SSM services for IGMPv1 or IGMPv2 hosts. This feature does not process IGMPv3 messages. 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 101: 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 102: Enabling Igmp Nsr

    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 103: 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 104 # 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 105: 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 106 Configuration procedure Assign an IP address and subnet mask to each interface, as shown in Figure 37. (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 107 [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 108: 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 109: 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 110 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 111: 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 112 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 113: Pim-Sm Overview

    Figure 40 Assert mechanism Router A Router B Ethernet Assert message Multicast packets Router C Receiver As shown in Figure 40, 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 114 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 115 As shown in Figure 42, 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 116 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 43, RP 1, RP 2, and RP 3 are members of an Anycast RP set.
  • Page 117 RPT building Figure 44 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 44, 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 118 Figure 45 Multicast source registration Host A Source Receiver Host B Server Receiver Join message Register message Host C Multicast packets As shown in Figure 45, 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 119: 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 120 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 121 Figure 47 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 47, 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 122: Administrative Scoping Overview

    Figure 48 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 48, 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 123 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 124: Pim-Ssm Overview

    Figure 50 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 50, 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 125: Relationship Among Pim Protocols

    Figure 51 SPT building in PIM-SSM Host A Source Receiver Host B Server Receiver Subscribe message Multicast packets Host C As shown in Figure 51, 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 126: Pim Support For Vpns

    Figure 52 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 127: 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 128: 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 129: 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 130: 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 131 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 132: 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 pim [ vpn-instance Enter PIM view. vpn-instance-name ] By default, Anycast RP is not configured.
  • Page 133 affected. For more information about static multicast routes, see "Configuring multicast routing forwarding." To configure a C-BSR: Step Command Remarks Enter system view. system-view pim [ vpn-instance Enter PIM view. vpn-instance-name ] c-bsr ip-address [ scope group-address { mask-length | Configure a C-BSR.

  • Page 134: Configuring Multicast Source Registration

    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 the device from forwarding BSMs out of their incoming interfaces By default, the device forwards BSMs out of their incoming interfaces to avoid the situation that some devices cannot receive the BSMs because of inconsistent routing information.

  • Page 135: Configuring The Switchover To Spt

    Step Command Remarks Enter system view. system-view pim [ vpn-instance Enter PIM view. vpn-instance-name ] By default, no PIM register policy Configure a PIM register exists, and all PIM register register-policy ipv4-acl-number policy. messages are regarded as legal. Configure the device to By default, the device calculates calculate the checksum the checksum based on the...

  • Page 136: Configuration Prerequisites

    • (Optional.) Disabling BSM semantic fragmentation • (Optional.) Disabling the device from forwarding BSMs out of their 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 137 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. The static RP also avoids bandwidth waste due to frequent message exchange between C-RPs and the BSR. The static RP configuration must be the same on all routers in the BIDIR-PIM domain.

  • Page 138: Configuring A Bsr

    c-rp ip-address [ advertisement-interval Configure a C-RP to provide adv-interval | group-policy By default, no C-RPs exist. 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 139 Initially, each C-BSR regards itself as the BSR of the BIDIR-PIM domain and sends BSMs to other routers in the domain. When a C-BSR receives the BSM from another C-BSR, it compares its own priority with the priority carried in the message. The C-BSR with a higher priority wins the BSR election. If a tie exists in the priority, the C-BSR with a higher IP address wins.

  • Page 140: Configuring Pim-Ssm

    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. In this way, a non-BSR router can update the RP-set information for a group range after receiving all BSMFs for the group range.

  • Page 141: Pim-Ssm Configuration Task List

    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 142: Configuring Common Pim Features

    Configuration procedure To configure an SSM group range: Step Command Remarks Enter system view. system-view Enter PIM view. Configure the SSM group By default, the SSM group range ssm-policy ipv4-acl-number range. is 232.0.0.0/8. Configuring common PIM features Configuration task list Tasks at a glance (Optional.) Configuring a multicast source policy...

  • Page 143: Configuring A Pim Hello Policy

    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 144 enable neighbor tracking, you must enable it on all PIM routers on a shared-media LAN. Otherwise, the upstream router cannot track join messages from every downstream routers. • Generation ID—A router generates a generation ID for hello messages when an interface is enabled with PIM.

  • Page 145: Configuring Common Pim Timers

    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. The following are common timers in PIM: • Hello interval—Interval at which a PIM router sends hello messages to discover PIM neighbors, and maintain PIM neighbor relationship.

  • Page 146: Setting The Maximum Size Of A Join Or Prune Message

    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. Set the join/prune interval. This configuration takes effect pim timer join-prune interval after the current interval ends.

  • Page 147: Enabling Pim Nsr

    Configuration restrictions and guidelines When you enable PIM passive mode, follow these restrictions and guidelines: • This feature takes effect only when PIM-DM or PIM-SM is enabled on the interface. • To avoid duplicate multicast data transmission and flow loop, do not enable this feature on a shared-media LAN with multiple PIM routers.

  • Page 148: Displaying And Maintaining Pim

    Step Command Remarks Enter system view. system-view pim [ vpn-instance Enter PIM view. vpn-instance-name ] Set a DSCP value for outgoing By default, the DSCP value for dscp dscp-value PIM messages. outgoing PIM messages is 48. Displaying and maintaining PIM Execute display commands in any view and reset commands in user view.
  • Page 149 • 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. • The entire PIM domain operates in the dense mode. •...
  • Page 150 [SwitchA-Vlan-interface100] igmp enable [SwitchA-Vlan-interface100] quit # Enable PIM-DM on VLAN-interface 103. [SwitchA] interface vlan-interface 103 [SwitchA-Vlan-interface103] pim dm [SwitchA-Vlan-interface103] quit # Enable IP multicast routing, IGMP, and PIM-DM on Switch B and Switch C in the same way Switch A is configured. (Details not shown.) # On Switch D, enable IP multicast routing, and enable PIM-DM on each interface.

  • Page 151: Pim-Sm Non-Scoped Zone Configuration Example

    (*, 225.1.1.1) Protocol: pim-dm, Flag: WC UpTime: 00:04:25 Upstream interface: NULL Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: igmp, UpTime: 00:04:25, Expires: - (10.110.5.100, 225.1.1.1) Protocol: pim-dm, Flag: ACT UpTime: 00:06:14 Upstream interface: Vlan-interface103 Upstream neighbor: 192.168.1.2...
  • Page 152 • 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. • The entire PIM-SM domain contains only one BSR. • Host A and Host C are multicast receivers on two stub networks N1 and N2.
  • Page 153 Enable IP multicast routing, and enable IGMP and PIM-SM: # 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 # Enable PIM-SM on the other interfaces.

  • Page 154: Pim-Sm Admin-Scoped Zone Configuration Example

    Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:44 Elected BSR address: 192.168.9.2 Priority: 64 Hash mask length: 30 Uptime: 00:11:18 # Display BSR information on Switch E. [SwitchE] display pim bsr-info Scope: non-scoped State: Elected Bootstrap timer: 00:01:44 Elected BSR address: 192.168.9.2 Priority: 64 Hash mask length: 30 Uptime: 00:11:18...
  • Page 155 • IGMPv2 runs between Switch A, Switch E, Switch I, and the receivers that directly connect to them, respectively. Figure 55 Network diagram Admin-scope 1 Vlan-int500 Receiver Switch G Host A Source 1 Vlan-int109 Source 3 Vlan-int100 Vlan-int200 Vlan-int109 Vlan-int101 Vlan-int102 Vlan-int102 Switch F...
  • Page 156 Configuration procedure Assign an IP address and subnet mask to each interface, as shown in Figure 55. (Details not shown.) Configure OSPF on all switches in the PIM-SM domain. (Details not shown.) Enable IP multicast routing, and enable IGMP and PIM-SM: # On Switch A, enable IP multicast routing.
  • Page 157 <SwitchC> system-view [SwitchC] interface vlan-interface 103 [SwitchC-Vlan-interface103] multicast boundary 239.0.0.0 8 [SwitchC-Vlan-interface103] quit [SwitchC] interface vlan-interface 106 [SwitchC-Vlan-interface106] multicast boundary 239.0.0.0 8 [SwitchC-Vlan-interface106] quit # On Switch D, configure VLAN-interface 107 as the boundary of admin-scoped zone 2. <SwitchD> system-view [SwitchD] interface vlan-interface 107 [SwitchD-Vlan-interface107] multicast boundary 239.0.0.0 8 [SwitchD-Vlan-interface107] quit...
  • Page 158 Uptime: 00:01:45 Scope: 239.0.0.0/8 State: Elected Bootstrap timer: 00:00:06 Elected BSR address: 10.110.1.2 Priority: 64 Hash mask length: 30 Uptime: 00:04:54 Candidate BSR address: 10.110.1.2 Priority: 64 Hash mask length: 30 # Display BSR information on Switch D. [SwitchD] display pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:44...

  • Page 159: Bidir-Pim Configuration Example

    Group/MaskLen: 224.0.0.0/4 RP address Priority HoldTime Uptime Expires 10.110.9.1 00:03:39 00:01:51 Scope: 239.0.0.0/8 Group/MaskLen: 239.0.0.0/8 RP address Priority HoldTime Uptime Expires 10.110.1.2 (local) 00:07:44 00:01:51 # Display RP information on Switch D. [SwitchD] display pim rp-info BSR RP information: Scope: non-scoped Group/MaskLen: 224.0.0.0/4 RP address Priority...
  • Page 160 Figure 56 Network diagram Loop0 Receiver 1 Receiver 2 Switch B Vlan-int200 Vlan-int102 Vlan-int102 Switch C Host A Host B Vlan-int101 Vlan-int103 BIDIR-PIM Source 1 Source 2 Vlan-int101 Vlan-int103 Vlan-int100 Vlan-int400 Switch A Switch D Table 10 Interface and IP address assignment Device Interface IP address...
  • Page 161 [SwitchA-pim] quit # On Switch B, enable IP multicast routing. <SwitchB> system-view [SwitchB] multicast routing [SwitchB-mrib] quit # Enable IGMP on the receiver-side interface (VLAN-interface 200). [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] igmp enable [SwitchB-Vlan-interface200] quit # Enable PIM-SM on the other interfaces. [SwitchB] interface vlan-interface 101 [SwitchB-Vlan-interface101] pim sm [SwitchB-Vlan-interface101] quit...
  • Page 162 [SwitchD] interface vlan-interface 103 [SwitchD-Vlan-interface103] pim sm [SwitchD-Vlan-interface103] quit # Enable BIDIR-PIM. [SwitchD] pim [SwitchD-pim] bidir-pim enable [SwitchD-pim] quit On Switch C, configure VLAN interface 102 as a C-BSR, and Loopback 0 as a C-RP for the entire BIDIR-PIM domain. [SwitchC-pim] c-bsr 10.110.2.2 [SwitchC-pim] c-rp 1.1.1.1 bidir [SwitchC-pim] quit...

  • Page 163: Pim-Ssm Configuration Example

    Flags: 0x0 Uptime: 00:08:32 RPF interface: Vlan-interface101 List of 1 DF interfaces: 1: Vlan-interface100 # Display information about DFs for multicast forwarding on Switch B. [SwitchB] display multicast forwarding df-info Total 1 RP, 1 matched 00001. RP address: 1.1.1.1 Flags: 0x0 Uptime: 00:06:24 RPF interface: Vlan-interface102 List of 2 DF interfaces:...
  • Page 164 • Host A and Host C are multicast receivers on two stub networks. • The SSM group range is 232.1.1.0/24. • IGMPv3 runs between Switch A and N1, and between Switch B, Switch C, and N2. Figure 57 Network diagram Receiver Host A Switch A...
  • Page 165 # 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 [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] pim sm...

  • Page 166: Troubleshooting Pim

    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 Upstream interface: Vlan-interface300 Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1...

  • Page 167: 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 168 If the problem persists, contact Hewlett Packard Enterprise Support.

  • Page 169: 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 170 As shown in Figure 58, 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 171 Figure 59 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 172 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 173 Figure 60 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 174: Msdp Support For Vpns

    Figure 61 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 175: 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 176: 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 177: Configuring A Description For An Msdp Peer

    Configuring a description for an MSDP peer This feature helps administrators easily distinguish an MSDP peer from other MSDP peers. To configure a description for an MSDP peer: Step Command Remarks Enter system view. system-view msdp [ vpn-instance Enter MSDP view. vpn-instance-name ] Configure a description for By default, no description for an...

  • Page 178: 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 179: Configuring The Originating Rp Of Sa 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 180: 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 message to any MSDP peer.

  • Page 181: 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 182: Msdp Configuration Examples

    MSDP configuration examples This section provides examples of configuring MSDP on switches. PIM-SM inter-domain multicast configuration Network requirements As shown in Figure • OSPF runs within AS 100 and AS 200 and BGP runs between them. • Each PIM-SM domain has a minimum of one multicast source or receiver. Set up MSDP peering relationships between the RPs in the PIM-SM domains to share multicast source information among the PIM-SM domains.
  • Page 183 Switch C Loop0 2.2.2.2/32 Switch D Vlan-int104 10.110.4.2/24 Configuration procedure Assign an IP address and subnet mask to each interface, as shown in Figure 62. (Details not shown.) Configure OSPF on the switches in the ASs. (Details not shown.) Enable IP multicast routing and PIM-SM, and configure PIM-SM domain borders: # On Switch A, enable IP multicast routing.
  • Page 184 # On Switch C, configure an EBGP peer, and redistribute OSPF routes. [SwitchC] bgp 200 [SwitchC-bgp] router-id 2.2.2.2 [SwitchC-bgp] peer 192.168.1.1 as-number 100 [SwitchC-bgp] address-family ipv4 unicast [SwitchC-bgp-ipv4] import-route ospf 1 [SwitchC-bgp-ipv4] peer 192.168.1.1 enable [SwitchC-bgp-ipv4] quit # Redistribute BGP routes into OSPF on Switch B. [SwitchB] ospf 1 [SwitchB-ospf-1] import-route bgp [SwitchB-ospf-1] quit...
  • Page 185 Peer MsgRcvd MsgSent OutQ PrefRcv Up/Down State 192.168.1.1 100 18 00:20:07 Established # Display the BGP routing table on Switch C. [SwitchC] display bgp routing-table ipv4 Total number of routes: 5 BGP local router ID is 2.2.2.2 Status codes: * - valid, > - best, d - dampened, h - history, s - suppressed, S - stale, i - internal, e - external Network NextHop...

  • Page 186: Inter-As Multicast Configuration By Leveraging Static Rpf Peers

    Description: Information about connection status: State: Established Up/down time: 00:15:47 Resets: 0 Connection interface: Vlan-interface101 (192.168.1.1) Received/sent messages: 16/16 Discarded input messages: 0 Discarded output messages: 0 Elapsed time since last connection or counters clear: 00:17:40 Mesh group peer joined: momo Last disconnect reason: Hold timer expired with truncated message Truncated packet: 5 bytes in buffer, type: 1, length: 20, without packet time: 75s Information about (Source, Group)-based SA filtering policy:...
  • Page 187 • According to the peer-RPF forwarding rule, the switches accept SA messages that pass the filtering policy from its static RPF peers. To share multicast source information among PIM-SM domains without changing the unicast topology structure, configure MSDP peering relationships for the RPs of the PIM-SM domains and configure the static RPF peering relationships.
  • Page 188 # On Switch C, enable IP multicast routing. <SwitchC> system-view [SwitchC] multicast routing [SwitchC-mrib] quit # 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...
  • Page 189 [SwitchD-bgp-ipv4] import-route ospf 1 [SwitchD-bgp-ipv4]quit [SwitchD-bgp] quit # On Switch C, configure an EBGP peer, and redistribute OSPF routing information. [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.

  • Page 190: Anycast Rp Configuration

    [SwitchD] ip prefix-list list-a permit 10.110.0.0 16 greater-equal 16 less-equal 32 [SwitchD] msdp [SwitchD-msdp] peer 10.110.1.1 connect-interface vlan-interface 103 [SwitchD-msdp] static-rpf-peer 10.110.1.1 rp-policy list-a [SwitchD-msdp] quit # 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...
  • Page 191 Configure the Anycast RP application so that the receiver-side DRs and the source-side DRs can initiate a join process to their respective RPs that are topologically closest to them. Configure the router IDs of Switch B and Switch D as 1.1.1.1 and 2.2.2.2, respectively. Set up an MSDP peering relationship between Switch B and Switch D.
  • Page 192 [SwitchB-mrib] quit # Enable IGMP on the receiver-side interface (VLAN-interface 100). [SwitchB] interface vlan-interface 100 [SwitchB-Vlan-interface100] igmp enable [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...
  • Page 193 Peer address State Up/Down time SA count Reset count 2.2.2.2 Established 00:10:57 # Display brief information about MSDP peers on Switch D. [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.

  • Page 194: Sa Message Filtering Configuration

    # Send multicast data from Source 2 to multicast group 225.1.1.1. (Details not shown.) # Display the PIM routing table on Switch B. [SwitchB] display pim routing-table No information is output on Switch B. # Display the PIM routing table on Switch D. [SwitchD] display pim routing-table Total 1 (*, G) entry;...
  • Page 195 Figure 65 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 196 [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 197: 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 198: 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 199: 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 200: 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 66, when MLD snooping is not enabled, the Layer 2 switch floods IPv6 multicast...
  • Page 201 Figure 67 MLD snooping ports Receiver Router A Switch A GE1/0/1 GE1/0/2 Host A GE1/0/3 Host B Receiver GE1/0/1 GE1/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 202: 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 203: Mld Snooping Proxying

    • If a match is found but the receiving port is not an outgoing interface in the forwarding entry, the Layer 2 device discards the MLD done message. • If a match is found and the receiving port is not the only outgoing interface in the forwarding entry, the Layer 2 device performs the following actions: Discards the MLD done message.

  • Page 204: Protocols And Standards

    The MLD snooping proxy device processes different MLD messages as follows: • General query. 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 205: Enabling Mld Snooping

    Tasks at a glance • (Optional.) Enabling the MLD snooping querier • (Optional.) Configuring parameters for MLD general queries and responses (Optional.) Enabling MLD snooping proxying Configuring parameters for MLD messages: • (Optional.) Configuring source IPv6 addresses for MLD messages •...

  • Page 206: Enabling Mld Snooping For A Vlan

    Step Command Remarks MLD-snooping view. By default, the status of MLD Enable MLD snooping for snooping for a VLAN is consistent enable vlan vlan-list multiple VLANs. with the global MLD snooping status. Enabling MLD snooping for a VLAN Step Command Remarks Enter system view.

  • Page 207: Setting The Maximum Number Of Mld Snooping Forwarding Entries

    You can specify the version for the specified VLANs in MLD-snooping view or for a VLAN in VLAN view. For a VLAN, the configuration in VLAN view has the same priority as the configuration in MLD-snooping view, and the most recent configuration takes effect. Specifying an MLD snooping version in MLD-snooping view Step Command...

  • Page 208: Setting The Mld Last Listener Query Interval

    • You must specify an unused IPv6 multicast MAC address when configuring a static IPv6 multicast MAC address entry. An IPv6 multicast MAC address is a MAC address in which the least significant bit of the most significant octet is 1. •...

  • Page 209: Configuring Mld Snooping Port Features

    Setting the MLD last listener query interval globally Step Command Remarks Enter system view. system-view Enter MLD-snooping view. mld-snooping Set the MLD last listener The default setting is 1 last-listener-query-interval interval query interval globally. second. Setting the MLD last listener query interval in a VLAN Step Command Remarks...

  • Page 210: Configuring Static Ports

    Step Command Remarks globally. Set the aging timer for The default setting is 260 dynamic member ports host-aging-time seconds seconds. globally. Setting the aging timers for dynamic ports in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Set the aging timer for mld-snooping...

  • Page 211: Enabling Fast-Leave Processing

    • It sends an unsolicited MLD report when you complete the configuration. • It responds to MLD general queries with MLD reports. • It sends an MLD done message when you remove the configuration. The version of MLD running on the simulated member host is the same as the version of MLD snooping running on the port.

  • Page 212: Disabling A Port From Becoming A Dynamic Router Port

    Disabling a port from becoming a dynamic router port A receiver host might send MLD general queries or IPv6 PIM hello messages for testing purposes. On the Layer 2 device, the port that receives either of the messages becomes a dynamic router port. Before the aging timer for the port expires, the following problems might occur: •...

  • Page 213: Configuring Parameters For Mld General Queries And Responses

    Configuration procedure To enable the MLD snooping querier for a VLAN: Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Enable the MLD snooping By default, the MLD snooping mld-snooping querier querier for the VLAN. querier is disabled for a VLAN. Configuring parameters for MLD general queries and responses CAUTION:...

  • Page 214: Enabling Mld Snooping Proxying

    Enabling MLD snooping proxying Before you enable MLD snooping proxying for a VLAN, enable MLD snooping for the VLAN. To enable MLD snooping proxying: Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Enable MLD snooping By default, MLD snooping mld-snooping proxy enable proxying for the VLAN.

  • Page 215: Setting The 802.1P Priority For Mld Messages

    Step Command Remarks multicast-address-specific multicast-address-specific queries. queries is one of the following: • The source address of MLD general queries if the MLD snooping querier of the VLAN has received MLD general queries. • The IPv6 link-local address of the current VLAN interface if the MLD snooping querier does not receive an MLD general query.

  • Page 216: Configuring Mld Snooping Policies

    Step Command Remarks the device does not change the 802.1p priority. Setting the 802.1p priority for MLD messages in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id By default, the 802.1p priority for MLD messages is not configured. Set the 802.1p priority for For MLD messages created by the mld-snooping dot1p-priority...

  • Page 217: Enabling Ipv6 Multicast Source Port Filtering

    Step Command Remarks Enter Layer 2 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. mld-snooping group-policy group policy on the port. ipv6-acl-number [ vlan vlan-list ] Hosts attached to the port can join any IPv6 multicast groups.

  • Page 218: Enabling Mld Report Suppression

    • The drop-unknown command in MLD-snooping view and the mld-snooping drop-unknown command are mutually exclusive. You cannot configure them on the same device. Enabling dropping unknown IPv6 multicast data globally Step Command Remarks Enter system view. system-view Enter MLD-snooping view. mld-snooping By default, dropping unknown Enable dropping unknown...

  • Page 219: Enabling Ipv6 Multicast Group Replacement

    Configuration procedure To set the maximum number of IPv6 multicast groups on a port: Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface-type interface view or Layer 2 interface-number aggregate interface view. Set the maximum number of By default, no limit is placed on mld-snooping group-limit limit IPv6 multicast groups on the...

  • Page 220: Displaying And Maintaining Mld Snooping

    Enabling host tracking globally Step Command Remarks Enter system view. system-view Enter MLD-snooping view. mld-snooping Enable host tracking By default, host tracking is host-tracking globally. disabled globally. Enabling host tracking in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view.

  • Page 221: Mld Snooping Configuration Examples

    Task Command display mld-snooping static-router-port [ vlan vlan-id ] Display static router port information. [ verbose ] [ slot slot-number ] Display statistics for the MLD messages and IPv6 PIM hello display mld-snooping statistics messages learned through MLD snooping. reset ipv6 l2-multicast fast-forwarding cache [ vlan vlan-id ] Clear Layer 2 IPv6 multicast fast { { ipv6-source-address | ipv6-group-address } * | all } [ slot forwarding entries.
  • Page 222 Figure 69 Network diagram Receiver Host A Source Receiver GE1/0/4 GE1/0/2 GE1/0/1 GE1/0/1 GE1/0/3 1::2/64 2001::1/64 Switch A Host B Router A GE1/0/2 1::1/64 MLD querier Host C VLAN 100 Configuration procedure Assign an IPv6 address and prefix length to each interface, as shown in Figure 69.

  • Page 223: Static Port Configuration Example

    # Configure an IPv6 multicast group policy so that hosts in VLAN 100 can join only IPv6 multicast group FF1E::101. [SwitchA] acl ipv6 basic 2001 [SwitchA-acl-ipv6-basic-2001] rule permit source ff1e::101 128 [SwitchA-acl-ipv6-basic-2001] quit [SwitchA] mld-snooping [SwitchA–mld-snooping] group-policy 2001 vlan 100 [SwitchA–mld-snooping] quit # Configure GigabitEthernet 1/0/3 and GigabitEthernet 1/0/4 as simulated member hosts to join IPv6 multicast group FF1E::101.
  • Page 224 along the path of Switch A—Switch C. In this case, the multicast delivery is interrupted during the process. For more information about the STP, see Layer 2—LAN Switching Configuration Guide. Configure GigabitEthernet 1/0/3 on Switch A as a static router port. Then, IPv6 multicast data can flow to the receivers nearly uninterrupted along the path of Switch A—Switch C when the path of Switch A—Switch B—Switch C is blocked.
  • Page 225 # Create VLAN 100, and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/3 # Enable MLD snooping for VLAN 100. [SwitchA-vlan100] mld-snooping enable [SwitchA-vlan100] quit # Configure GigabitEthernet 1/0/3 as a static router port. [SwitchA] interface gigabitethernet 1/0/3 [SwitchA-GigabitEthernet1/0/3] mld-snooping static-router-port vlan 100 [SwitchA-GigabitEthernet1/0/3] quit...

  • Page 226: Mld Snooping Querier Configuration Example

    GE1/0/3 The output shows that GigabitEthernet 1/0/3 on Switch A has become a static router port. # Display brief information about static MLD snooping group entries in VLAN 100 on Switch C. [SwitchC] display mld-snooping static-group vlan 100 Total 1 entries). VLAN 100: Total 1 entries).
  • Page 227 # Enable the MLD snooping feature. <SwitchA> system-view [SwitchA] mld-snooping [SwitchA-mld-snooping] quit # Create VLAN 100, and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/3 # Enable MLD snooping, and enable dropping unknown IPv6 multicast data for VLAN 100. [SwitchA-vlan100] mld-snooping enable [SwitchA-vlan100] mld-snooping drop-unknown # Configure Switch A as the MLD snooping querier.

  • Page 228: Mld Snooping Proxying Configuration Example

    # Enable MLD snooping, and enable dropping unknown IPv6 multicast data for VLAN 100. [SwitchD-vlan100] mld-snooping enable [SwitchD-vlan100] mld-snooping drop-unknown [SwitchD-vlan100] quit Verifying the configuration # Display statistics for MLD messages and IPv6 PIM hello messages learned through MLD snooping on Switch B.
  • Page 229 Figure 72 Network diagram Receiver Host A Source Receiver GE1/0/4 GE1/0/2 GE1/0/1 GE1/0/1 GE1/0/3 1::2/64 2001::1/64 Switch A Host B GE1/0/2 Router A 1::1/64 Proxy MLD querier Host C VLAN 100 Configuration procedure Assign an IPv6 address and subnet mask to each interface, as shown in Figure 72.

  • Page 230: Troubleshooting Mld Snooping

    Verifying the configuration # Display brief information about dynamic MLD snooping group entries on Switch A. [SwitchA] display mld-snooping group Total 1 entries. VLAN 100: Total 1 entries. (::, FF1E::101) Host ports (2 in total): GE1/0/3 (00:04:09) GE1/0/4 (00:03:06) # Send an MLD done message to leave IPv6 multicast group (FF1E::101) from Host A. (Details not shown.) # Display information about dynamic MLD groups on Router A.

  • Page 231: Ipv6 Multicast Group Policy Does Not Work

    If the problem persists, contact Hewlett Packard Enterprise Support. IPv6 multicast group policy does not work Symptom Hosts can receive IPv6 multicast data for IPv6 multicast groups that are not permitted by the IPv6 multicast group policy. Solution To resolve the problem: Use the display acl ipv6 command to verify that the configured IPv6 ACL meets the IPv6 multicast group policy requirements.

  • Page 232: Configuring Ipv6 Pim Snooping

    Configuring IPv6 PIM snooping Overview IPv6 PIM snooping runs on Layer 2 devices. It works with MLD snooping to analyze received IPv6 PIM messages, and adds the ports that are interested in specific multicast data to an IPv6 PIM snooping routing entry. In this way, the multicast data can be forwarded to only the ports that are interested in the data.

  • Page 233: Configuring Ipv6 Pim Snooping

    b. Floods all other types of received IPv6 PIM messages except PIM hello messages in the VLAN. c. Forwards all multicast data to all router ports in the VLAN. Each IPv6 PIM-capable router in the VLAN, whether interested in the multicast data or not, can receive all multicast data and all IPv6 PIM messages except IPv6 PIM hello messages.

  • Page 234: Displaying And Maintaining Ipv6 Pim Snooping

    Step Command Remarks ports on the new master seconds. graceful-restart device after a neighbor-aging-time seconds A global neighbor port is a Layer master/subordinate 2 aggregate interface that acts as switchover. a neighbor port. (Optional.) Set the aging The default setting is 210 time for global seconds.

  • Page 235: Configuration Procedure

    • On all IPv6 PIM routers connected to Switch A, set the maximum size of a join or prune message to 1400 bytes, which is less than the path MTU. Figure 74 Network diagram Source 1 Receiver 1 Router A Router C GE1/0/1 GE1/0/2...
  • Page 236 # Enable IPv6 PIM-SM on each interface. [RouterB] interface gigabitethernet 1/0/1 [RouterB-GigabitEthernet1/0/1] ipv6 pim sm [RouterB-GigabitEthernet1/0/1] quit [RouterB] interface gigabitethernet 1/0/2 [RouterB-GigabitEthernet1/0/2] ipv6 pim sm [RouterB-GigabitEthernet1/0/2] quit # Set the maximum size of a join or prune message to 1400 bytes. [RouterB] ipv6 pim [RouterB-pim6] jp-pkt-size 1400 Configure Router C:...

  • Page 237: Verifying The Configuration

    # Create VLAN 100, and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/4 # Enable MLD snooping and IPv6 PIM snooping for VLAN 100. [SwitchA-vlan100] mld-snooping enable [SwitchA-vlan100] ipv6 pim-snooping enable [SwitchA-vlan100] quit Verifying the configuration # On Switch A, display IPv6 PIM snooping neighbor information for VLAN 100.

  • Page 238: Troubleshooting Ipv6 Pim Snooping

    GE1/0/4 Expires: 00:03:01, FSM: J The output shows the following information: • Switch A will forward the multicast data intended for IPv6 multicast group FF1E::101 to only Router C. • Switch A will forward the multicast data intended for IPv6 multicast group FF2E::101 to only Router D.

  • Page 239: Configuring Ipv6 Multicast Vlans

    Configuring IPv6 multicast VLANs Overview As shown in Figure 75, Host A, Host B, and Host C are in different VLANs and the same IPv6 multicast group. When Switch A (Layer 3 device) receives IPv6 multicast data for that group, it forwards three copies of the data to Switch B (Layer 2 device).
  • Page 240 Figure 76 Sub-VLAN-based multicast VLAN IPv6 Multicast packets VLAN 10 (IPv6 Multicast VLAN) VLAN 2 VLAN 2 Receiver VLAN 3 Host A VLAN 4 VLAN 3 Receiver Host B Switch A Switch B Source MLD querier VLAN 4 Receiver Host C MLD snooping manages router ports in the IPv6 multicast VLAN and member ports in each sub-VLAN.

  • Page 241: Ipv6 Multicast Vlan Configuration Task List

    IPv6 multicast VLAN configuration task list Tasks at a glance (Required.) Perform one of the following tasks: • Configuring a sub-VLAN-based IPv6 multicast VLAN • Configuring a port-based IPv6 multicast VLAN: Configuring user port attributes  Assigning user ports to an IPv6 multicast VLAN ...

  • Page 242: Configuring A Port-Based Ipv6 Multicast Vlan

    Step Command Remarks Enter system view. system-view Configure a VLAN as an By default, a VLAN is not an IPv6 ipv6 multicast-vlan IPv6 multicast VLAN and multicast VLAN. vlan-id enter its view. Assign the specified VLANs By default, an IPv6 multicast VLAN does to the IPv6 multicast VLAN subvlan vlan-list not have any sub-VLANs.

  • Page 243: Setting The Maximum Number Of Ipv6 Multicast Vlan Forwarding Entries

    Configuration restrictions and guidelines When you perform this task, follow these restrictions and guidelines: • The VLAN to be configured as an IPv6 multicast VLAN must exist. • A port can belong to only one IPv6 multicast VLAN. Configuration procedure To assign user ports to an IPv6 multicast VLAN in IPv6 multicast VLAN view: Step Command...

  • Page 244: Displaying And Maintaining Ipv6 Multicast Vlans

    Displaying and maintaining IPv6 multicast VLANs Execute display commands in any view and reset commands in user view. Task Command Display information about IPv6 display ipv6 multicast-vlan [ vlan-id ] multicast VLANs. Display information about information display ipv6 multicast-vlan group [ ipv6-source-address | about IPv6 multicast group entries in ipv6-group-address | slot slot-number | verbose | vlan vlan-id ] * IPv6 multicast VLANs.
  • Page 245 Figure 78 Network diagram Source GE1/0/2 MLD querier Vlan-int20 Switch A 1::2/64 GE1/0/1 1::1/64 Vlan-int10 2001::1/64 GE1/0/1 Switch B GE1/0/2 GE1/0/4 GE1/0/3 Receiver Receiver Receiver Host A Host B Host C VLAN 2 VLAN 3 VLAN 4 Configuration procedure Configure Switch A: # Enable IPv6 multicast routing.
  • Page 246 Configure Switch B: # Enable the MLD snooping feature. <SwitchB> system-view [SwitchB] mld-snooping [SwitchB-mld-snooping] quit # Create VLAN 2, assign GigabitEthernet 1/0/2 to the VLAN, and enable MLD snooping for the VLAN. [SwitchB] vlan 2 [SwitchB-vlan2] port gigabitethernet 1/0/2 [SwitchB-vlan2] mld-snooping enable [SwitchB-vlan2] quit # Create VLAN 3, assign GigabitEthernet 1/0/3 to the VLAN, and enable MLD snooping for the VLAN.

  • Page 247: Port-Based Ipv6 Multicast Vlan Configuration Example

    [SwitchB] display ipv6 multicast-vlan group Total 1 entries. IPv6 multicast VLAN 10: Total 1 entries. (::, FF1E::101) Sub-VLANs (3 in total): VLAN 2 VLAN 3 VLAN 4 The output shows that IPv6 multicast group FF1E::101 belongs to IPv6 multicast VLAN 10. IPv6 multicast VLAN 10 contains sub-VLANs VLAN 2 through VLAN 4.
  • Page 248 [SwitchA] ipv6 multicast routing [SwitchA-mrib6] quit # Create VLAN 20, and assign GigabitEthernet 1/0/2 to the VLAN. [SwitchA] vlan 20 [SwitchA-vlan20] port gigabitethernet 1/0/2 [SwitchA-vlan20] quit # Assign an IPv6 address to VLAN-interface 20, and enable IPv6 PIM-DM on the interface. [SwitchA] interface vlan-interface 20 [SwitchA-Vlan-interface20] ipv6 address 1::2 64 [SwitchA-Vlan-interface20] ipv6 pim dm...
  • Page 249 # Assign GigabitEthernet 1/0/2 to VLAN 2 and VLAN 10 as an untagged VLAN member. [SwitchB-GigabitEthernet1/0/2] port hybrid vlan 2 untagged [SwitchB-GigabitEthernet1/0/2] port hybrid vlan 10 untagged [SwitchB-GigabitEthernet1/0/2] quit # Configure GigabitEthernet 1/0/3 as a hybrid port, and configure VLAN 3 as the PVID of the hybrid port.
  • Page 250 (::, FF1E::101) Host slots (0 in total): Host ports (3 in total): GE1/0/2 (00:03:23) GE1/0/3 (00:04:07) GE1/0/4 (00:04:16) The output shows that MLD snooping maintains the user ports in the multicast VLAN (VLAN 10). Switch B will forward the IPv6 multicast data of VLAN 10 through these user ports.

  • Page 251: Configuring Ipv6 Multicast Routing And Forwarding

    Configuring IPv6 multicast routing and forwarding Overview IPv6 multicast routing and forwarding uses the following tables: • IPv6 multicast protocols' routing tables, such as the IPv6 PIM routing table. • General IPv6 multicast routing table that summarizes the multicast routing information generated by different IPv6 multicast routing protocols.
  • Page 252 packet as the incoming interface of the (S, G) entry. After the router receives another (S, G) packet, it looks up its IPv6 multicast forwarding table for a matching (S, G) entry: • If no match is found, the router first determines the RPF route back to the packet source. Then, it creates a forwarding entry with the RPF interface as the incoming interface and performs one of the following tasks: If the receiving interface is the RPF interface, the RPF check succeeds and the router...

  • Page 253: Ipv6 Multicast Forwarding Across Ipv6 Unicast Subnets

    IPv6 multicast forwarding across IPv6 unicast subnets Routers forward the IPv6 multicast data from an IPv6 multicast source hop by hop along the forwarding tree, but some routers might not support IPv6 multicast protocols in a network. When the IPv6 multicast data is forwarded to a router that does not support IPv6 multicast, the forwarding path is blocked.

  • Page 254: Configuring Ipv6 Multicast Routing And Forwarding

    Configuring IPv6 multicast routing and forwarding Before you configure IPv6 multicast routing and forwarding, complete the following tasks: • Configure an IPv6 unicast routing protocol so that all devices in the domain can interoperate at the network layer. • Configure IPv6 PIM-DM or IPv6 PIM-SM. Specifying the longest prefix match principle You can enable the device to use the longest prefix match principle for RPF route selection.

  • Page 255: Enabling Ipv6 Multicast Forwarding Between Sub-Vlans Of A Super Vlan

    To configure an IPv6 multicast forwarding boundary: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number ipv6 multicast boundary By default, an interface is not an { ipv6-group-address prefix-length Configure an IPv6 multicast IPv6 multicast forwarding | scope { scope-id | admin-local | forwarding boundary.
  • Page 256 Task Command Display information about the interfaces display ipv6 mrib [ vpn-instance vpn-instance-name ] maintained by the IPv6 MRIB. interface [ interface-type interface-number ] display ipv6 multicast [ vpn-instance vpn-instance-name ] Display IPv6 multicast boundary boundary { group [ ipv6-group-address [ prefix-length ] ] | information.

  • Page 257: Ipv6 Multicast Routing And Forwarding Configuration Examples

    IPv6 multicast routing and forwarding configuration examples IPv6 multicast forwarding over a GRE tunnel Network requirements As shown in Figure • IPv6 multicast routing and IPv6 PIM-DM are enabled on Switch A and Switch C. • Switch B does not support IPv6 multicast. •...
  • Page 258 [SwitchA-Tunnel2] source 2001::1 [SwitchA-Tunnel2] destination 3001::2 [SwitchA-Tunnel2] quit # On Switch C, create service loopback group 1, and specify the unicast tunnel service for the group. <SwitchC> system-view [SwitchC] service-loopback group 1 type tunnel # Assign GigabitEthernet 1/0/3 to service loopback group 1. (GigabitEthernet 1/0/3 does not belong to VLAN 200 or VLAN 102.) [SwitchC] interface gigabitethernet 1/0/3 [SwitchC-GigabitEthernet1/0/3] port service-loopback group 1...
  • Page 259 On Switch C, configure a static IPv6 route with the destination address 1001::1/64 and the outgoing interface Tunnel 2. [SwitchC] ipv6 route-static 1001::1 64 tunnel 2 Verifying the configuration # Send an MLD report from Receiver to join the IPv6 multicast group FF1E::101. (Details not shown.) # Send IPv6 multicast data from Source to the IPv6 multicast group FF1E::101.

  • Page 260: Configuring Mld

    Configuring MLD Overview Multicast Listener Discovery (MLD) establishes and maintains IPv6 multicast group memberships between a Layer 3 multicast device and the hosts on the directly connected subnet. MLD has the following versions: • MLDv1 (defined by RFC 2710), which is derived from IGMPv2. •...
  • Page 261 Joining an IPv6 multicast group Figure 83 MLD queries and reports IPv6 network Router A Router B Ethernet Host A Host B Host C (G2) (G1) (G1) Query Report As shown in Figure 83, Host B and Host C want to receive the IPv6 multicast data addressed to IPv6 multicast group G1.

  • Page 262: Mldv2 Enhancements

    After receiving the MLD done message, the querier sends a configurable number of multicast-address-specific queries to the group that the host is leaving. The IPv6 multicast addresses queried include both the destination address field and the group address field of the message.

  • Page 263: Mld Ssm Mapping

    • Filter mode—Router keeps tracing the Include or Exclude state. • List of sources—Router keeps tracing the newly added or deleted IPv6 multicast source. • Timers—Filter timers, which include the time that the router waits before switching to the Include mode after an IPv6 multicast address times out, and source timers for source recording. MLD SSM mapping An MLDv2 host can explicitly specify multicast sources in its MLDv2 reports.

  • Page 264: Mld Proxying

    MLD proxying As shown in Figure 86, in a simple tree-shaped topology, it is not necessary to configure IPv6 multicast routing protocols, such as IPv6 PIM, on edge devices. Instead, you can configure MLD proxying on these devices. With MLD proxying configured, the edge device acts as an MLD proxy: •...

  • Page 265: Mld Configuration Task List

    • RFC 3810, Multicast Listener Discovery Version 2 (MLDv2) for IPv6 MLD configuration task list Tasks at a glance Configuring basic MLD features: • (Required.) Enabling MLD • (Optional.) Specifying an MLD version • (Optional.) Configuring a static group member •...

  • Page 266: Specifying An Mld Version

    Step Command Remarks Enable MLD. By default, MLD is disabled. mld enable Specifying an MLD version For MLD to operate correctly, specify the same MLD version for all routers on the same subnet. To specify an MLD version: Step Command Remarks Enter system view.

  • Page 267: Adjusting Mld Performance

    This configuration does not take effect on static group members, because static group members do not send MLD reports. To configure an IPv6 multicast group policy: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, no IPv6 multicast group policy exists on an mld group-policy Configure an IPv6 multicast...
  • Page 268 Configuration guidelines When you configure the MLD query and response parameters, follow these restrictions and guidelines: • You can configure the MLD query and response parameters globally for all interfaces in MLD view or for an interface in interface view. For an interface, the interface-specific configuration takes priority over the global configuration.

  • Page 269: Enabling Fast-Leave Processing

    Step Command Remarks interface interface-type Enter interface view. interface-number Set the MLD querier's By default, the MLD querier's mld robust-count count robustness variable. robustness variable is 2. By default, the MLD startup query Set the MLD startup query mld startup-query-interval interval equals one quarter of the interval.

  • Page 270: Configuration Prerequisites

    Configuration prerequisites Before you configure MLD SSM mappings, complete the following tasks: • Configure an IPv6 unicast routing protocol so that all devices in the domain can interoperate at the network layer. • Configure basic MLD features. Configuration procedure To configure an MLD SSM mapping: Step Command Remarks...

  • Page 271: Enabling Ipv6 Multicast Forwarding On A Non-Querier Interface

    Step Command Remarks Return to system view. quit interface interface-type Enter interface view. interface-number By default, MLD proxying is Enable MLD proxying. mld proxy enable disabled. Enabling IPv6 multicast forwarding on a non-querier interface Typically, only MLD queriers can forward IPv6 multicast traffic and non-queriers cannot. This prevents IPv6 multicast data from being repeatedly forwarded.

  • Page 272: Enabling Mld Nsr

    Enabling MLD NSR This feature backs up information about MLD interfaces and MLD multicast groups to the standby process. The device recovers the information without cooperation of other devices when an active/standby switchover occurs. Use this feature to prevent an active/standby switchover from affecting the IPv6 multicast service.
  • Page 273 • OSPFv3 and IPv6 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. Host A and Host C are multicast receiver hosts in N1 and N2, respectively.
  • Page 274 [SwitchA-Vlan-interface101] quit # On Switch B, enable IPv6 multicast routing. <SwitchB> system-view [SwitchB] ipv6 multicast routing [SwitchB-mrib6] quit # Enable MLD on VLAN-interface 200. [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] mld enable [SwitchB-Vlan-interface200] quit # Enable IPv6 PIM-DM on VLAN-interface 201. [SwitchB] interface vlan-interface 201 [SwitchB-Vlan-interface201] ipv6 pim dm [SwitchB-Vlan-interface201] quit...

  • Page 275: Mld Ssm Mapping Configuration Example

    MLD SSM mapping configuration example Network requirements As shown in Figure • OSPFv3 runs on the network. • The IPv6 PIM-SM domain uses both the ASM model and SSM model for IPv6 multicast delivery. VLAN-interface 104 of Router D acts as the C-BSR and C-RP. The SSM group range is FF3E::/64.
  • Page 276 # On Switch D, enable IPv6 multicast routing. <SwitchD> system-view [SwitchD] ipv6 multicast routing [SwitchD-mrib6] quit # Enable MLDv2 on the receiver-side interface (VLAN-interface 400). [SwitchD] interface vlan-interface 400 [SwitchD-Vlan-interface400] mld enable [SwitchD-Vlan-interface400] mld version 2 [SwitchD-Vlan-interface400] quit # Enable IPv6 PIM-SM on the other interfaces. [SwitchD] interface vlan-interface 103 [SwitchD-Vlan-interface103] ipv6 pim sm [SwitchD-Vlan-interface103] quit...

  • Page 277: Mld Proxying Configuration Example

    [SwitchD-mld] ssm-mapping 1001::1 2000 [SwitchD-mld] ssm-mapping 3001::1 2000 [SwitchD-mld] quit Verifying the configuration # Display MLD SSM mappings for IPv6 multicast group FF3E::101 on Switch D. [SwitchD] display mld ssm-mapping ff3e::101 Group: FF3E::101 Source list: 1001::1 3001::1 # On Switch D, display information about MLD multicast groups that hosts have dynamically joined. [SwitchD] display mld group MLD groups in total: 1 Vlan-interface400(FE80::101):...
  • Page 278 • IPv6 PIM-DM runs on the core network. • Host A and Host C on the stub network receive VOD information destined to IPv6 multicast group FF3E::101. Configure the MLD proxying feature on Switch B so that Switch B can maintain group memberships and forward IPv6 multicast traffic without running IPv6 PIM-DM.

  • Page 279: Troubleshooting Mld

    [SwitchB-Vlan-interface200] quit Verifying the configuration # Display IPv6 multicast group membership information maintained by the MLD proxy on Switch B. [SwitchB] display mld proxy group MLD proxy group records in total: 1 Vlan-interface100(FE80::16:1): MLD proxy group records in total: 1 Group address: FF1E::1 Member state: Delay Expires: 00:00:02...

  • Page 280: Configuring Ipv6 Pim

    Configuring IPv6 PIM Overview IPv6 Protocol Independent Multicast (IPv6 PIM) provides IPv6 multicast forwarding by leveraging IPv6 unicast static routes or IPv6 unicast routing tables generated by any IPv6 unicast routing protocol, such as RIPng, OSPFv3, IPv6 IS-IS, or IPv6 BGP. IPv6 PIM uses the underlying IPv6 unicast routing to generate an IPv6 multicast routing table without relying on any particular IPv6 unicast routing protocol.
  • Page 281 The nodes without downstream receivers are pruned. A router that has no downstream receivers multicasts a prune message to all IPv6 PIM routers on the subnet. When the upstream node receives the prune message, it removes the receiving interface from the (S, G) entry.

  • Page 282: Ipv6 Pim-Sm Overview

    Figure 91 Assert mechanism Router A Router B Ethernet Assert message IPv6 multicast packets Router C Receiver As shown in Figure 91, 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 283 IMPORTANT: MLD must be enabled on the device that acts as the receiver-side DR. Otherwise, the receiver hosts attached to the DR cannot join any IPv6 multicast groups. For more information about MLD, see "Configuring MLD." Figure 92 DR election Receiver Source Receiver...
  • Page 284 As shown in Figure 93, each C-RP periodically unicasts its advertisement messages (C-RP-Adv messages) to the BSR. An advertisement message contains the address of the advertising C-RP and the IPv6 multicast group range to which it is designated. The BSR collects these advertisement messages and organizes the C-RP information into an RP-set, which is a database of mappings between IPv6 multicast groups and RPs.
  • Page 285 multicast source registers with the closest RP or a receiver-side DR joins the closest RP to implement source information synchronization. Anycast RP has the following benefits: • Optimal RP path—An IPv6 multicast source registers with the closest RP to build an optimal SPT.
  • Page 286 RPT building Figure 95 RPT building in an IPv6 PIM-SM domain Host A Source Receiver Host B Server Receiver Join message IPv6 multicast packets Host C As shown in Figure 95, the process of building an RPT is as follows: When a receiver wants to join the IPv6 multicast group G, it uses an MLD message to inform the receiver-side DR.
  • Page 287 Figure 96 IPv6 multicast source registration Host A Source Receiver Host B Server Receiver Join message Register message Host C IPv6 multicast packets As shown in Figure 96, the IPv6 multicast source registers with the RP as follows: The IPv6 multicast source S sends the first multicast packet to the IPv6 multicast group G. When receiving the multicast packet, the source-side DR that directly connects to the IPv6 multicast source encapsulates the packet into a register message and unicasts the message to the RP.

  • Page 288: Ipv6 Bidir-Pim Overview

    If the RP receives IPv6 multicast traffic, it sends an (S, G) source-specific join message toward the IPv6 multicast source. The routers along the path from the RP to the IPv6 multicast source constitute an SPT branch. The subsequent IPv6 multicast data is forwarded to the RP along the SPT without being encapsulated into register messages.
  • Page 289 DF election On a subnet with multiple multicast routers, duplicate multicast packets might be forwarded to the RP. To address this issue, IPv6 BIDIR-PIM uses a designated forwarder (DF) election mechanism to elect a unique DF on each subnet. Only the DFs can forward IPv6 multicast data to the RP. DF election is not necessary for an RPL.
  • Page 290 Figure 98 RPT building at the receiver side Source Receiver Host A Server B Source Receiver Host B Server A Receiver Join message Receiver-side RPT IPv6 Multicast packets Host C As shown in Figure 98, the process for building a receiver-side RPT is the same as the process for building an RPT in IPv6 PIM-SM: When a receiver wants to join the IPv6 multicast group G, it uses an MLD message to inform the directly connected router.

  • Page 291: Ipv6 Administrative Scoping Overview

    Figure 99 RPT building at the IPv6 multicast source side Source Receiver Host A Server B Source Receiver Host B Server A Receiver Source-side RPT IPv6 Multicast packets Host C As shown in Figure 99, the process for building a source-side RPT is relatively simple: When an IPv6 multicast source sends multicast packets to the IPv6 multicast group G, the DF in each subnet unconditionally forwards the packets to the RP.
  • Page 292 BSMs, of these IPv6 multicast groups cannot cross the boundary of the IPv6 admin-scoped zone for the group range. The IPv6 multicast group ranges to which different IPv6 admin-scoped zones are designated can have intersections. However, the IPv6 multicast groups in an IPv6 admin-scoped zone are valid only within its local zone, and theses IPv6 multicast groups are regarded as private group addresses.

  • Page 293: Ipv6 Pim-Ssm Overview

    Figure 101 IPv6 multicast address format 0xFF Flags Scope Group ID (112 bits) An IPv6 admin-scoped zone with a larger scope field value contains an IPv6 admin-scoped zone with a smaller scope field value. The zone with the scope field value of E is the IPv6 global-scoped zone.

  • Page 294: Relationship Among Ipv6 Pim Protocols

    SPT building The decision to build an RPT for IPv6 PIM-SM or an SPT for IPv6 PIM-SSM depends on whether the IPv6 multicast group that the receiver host joins is in the IPv6 SSM group range. The IPv6 SSM group range reserved by IANA is FF3x::/32, where "x" represents any legal address scope. Figure 102 SPT building in IPv6 PIM-SSM Host A Source...

  • Page 295: Ipv6 Pim Support For Vpns

    Figure 103 Relationship among IPv6 PIM protocols A receiver joins IPv6 multicast group G. G is in the IPv6 An IPv6 multicast source is SSM group range? specified? IPv6 BIDIR-PIM is enabled? An MLD-SSM mapping is configured for G? IPv6 PIM-SM runs for G. G has an IPv6 BIDIR-PIM IPv6 PIM-SSM runs for G.

  • Page 296: Ipv6 Pim-Dm Configuration Task List

    IPv6 PIM-DM configuration task list Tasks at a glance (Required.) Enabling IPv6 PIM-DM (Optional.) Enabling the state refresh feature (Optional.) Configuring state refresh parameters (Optional.) Configuring the IPv6 PIM-DM graft retry timer (Optional.) Configuring common IPv6 PIM features Configuration prerequisites Before you configure IPv6 PIM-DM, configure an IPv6 unicast routing protocol so that all devices in the domain can interoperate at the network layer.

  • Page 297: Configuring State Refresh Parameters

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Enable the state refresh By default, the state refresh ipv6 pim state-refresh-capable feature. feature is enabled. Configuring state refresh parameters The state refresh interval determines the interval at which a router sends state refresh messages. It is configurable.

  • Page 298: Configuring Ipv6 Pim-Sm

    For more information about the configuration of other timers in IPv6 PIM-DM, see "Configuring common IPv6 PIM timers." Configuring IPv6 PIM-SM This section describes how to configure IPv6 PIM-SM. IPv6 PIM-SM configuration task list Tasks at a glance Remarks (Required.) Enabling IPv6 PIM-SM (Required.) Configuring an...

  • Page 299: Configuring An Rp

    Step Command Remarks vpn-instance-name ] Return to system view. quit interface interface-type Enter interface view. interface-number By default, IPv6 PIM-SM is Enable IPv6 PIM-SM. ipv6 pim sm disabled. Configuring an RP An RP can provide services for multiple or all IPv6 multicast groups. However, only one RP at a time can forward IPv6 multicast traffic for an IPv6 multicast group.
  • Page 300 A C-RP policy enables the BSR to filter C-RP advertisement messages by using an ACL that specifies the packet source address range and multicast group addresses. You must configure the same C-RP policy on all C-BSRs in the IPv6 PIM-SM domain because every C-BSR might become the BSR.

  • Page 301: Configuring A Bsr

    Step Command Remarks Enter system view. system-view ipv6 pim [ vpn-instance Enter IPv6 PIM view. vpn-instance-name ] By default, Anycast RP is not configured. anycast-rp Configure Anycast RP. You can repeat this command to ipv6-anycast-rp-address add multiple RP member ipv6-member-address addresses to an Anycast RP set.
  • Page 302 Step Command Remarks ipv6 pim [ vpn-instance Enter IPv6 PIM view. vpn-instance-name ] c-bsr ipv6-address [ scope Configure a C-BSR. scope-id ] [ hash-length By default, no C-BSRs exist. hash-length | priority priority ] * By default, no BSR policy exists, (Optional.) Configure a BSR and all bootstrap messages are bsr-policy ipv6-acl-number...

  • Page 303: Configuring Ipv6 Multicast Source Registration

    duplicated traffic. If all the devices have consistent routing information, you can disable the device from forwarding BSMs out of their incoming interfaces to reduce the traffic. To disable the device from forwarding BSMs out of their incoming interfaces: Step Command Remarks Enter system view.

  • Page 304: Configuring The Switchover To Spt

    Step Command Remarks register policy. exists, and all IPv6 register messages are regarded as legal. Configure the device to By default, the device calculates calculate the checksum the checksum based on the register-whole-checksum based on the entire register header of a register message. message.

  • Page 305: Configuration Prerequisites

    Tasks at a glance Remarks (Optional.) Enabling SNMP notifications for IPv6 PIM (Optional.) Configuring common IPv6 PIM features Configuration prerequisites Before you configure IPv6 BIDIR-PIM, configure an IPv6 unicast routing protocol so that all devices in the domain can interoperate at the network layer. Enabling IPv6 BIDIR-PIM Because IPv6 BIDIR-PIM is implemented on the basis of IPv6 PIM-SM, you must enable IPv6 PIM-SM before enabling IPv6 BIDIR-PIM.
  • Page 306 backups for dynamic RPs to enhance the robustness and operational manageability on an IPv6 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. The static RP can also avoid bandwidth waste due to frequent message exchange between C-RPs and the BSR.

  • Page 307: Configuring A Bsr

    To configure a C-RP: Step Command Remarks Enter system view. system-view ipv6 pim [ vpn-instance Enter IPv6 PIM view. vpn-instance-name ] c-rp ipv6-address [ advertisement-interval Configure a C-RP to provide adv-interval | { group-policy By default, no C-RPs exist. services for IPv6 BIDIR-PIM. ipv6-acl-number | scope scope-id } | holdtime hold-time | priority priority ] * bidir...
  • Page 308 The elected BSR distributes the RP-set information collected from C-RPs to all routers in the IPv6 BIDIR-PIM domain. All routers use the same hash algorithm to get an RP for a specific IPv6 multicast group. Configuring a C-BSR IMPORTANT: Because the BSR and other devices exchange a large amount of information in the IPv6 BIDIR-PIM domain, reserve a large bandwidth between the C-BSR and other devices.

  • Page 309: Configuring Ipv6 Pim-Ssm

    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. In this way, a non-BSR router can update the RP-set information for a group range after receiving all BSMFs for the group range. The loss of one BSMF only affects the RP-set information of the group ranges that the fragment contains.

  • Page 310: Configuration Prerequisites

    Tasks at a glance (Optional.) Configuring the IPv6 SSM group range (Optional.) Configuring common IPv6 PIM features Configuration prerequisites Before you configure IPv6 PIM-SSM, configure an IPv6 unicast IPv6 routing protocol so that all devices in the domain can interoperate at the network layer. Enabling IPv6 PIM-SM Before you configure IPv6 PIM-SSM, you must enable IPv6 PIM-SM, because the implementation of the IPv6 SSM model is based on subsets of IPv6 PIM-SM.

  • Page 311: Configuring Common Ipv6 Pim Features

    Step Command Remarks Enter system view. system-view Enter IPv6 PIM view. ipv6 pim Configure the IPv6 SSM The default range is FF3x::/32, ssm-policy ipv6-acl-number group range. where x can be any valid scope. Configuring common IPv6 PIM features Configuration task list Tasks at a glance (Optional.) Configuring an IPv6 multicast source policy...

  • Page 312: Configuring An Ipv6 Pim Hello Policy

    Step Command Remarks packets. Configuring an IPv6 PIM hello policy This feature enables the device to filter IPv6 PIM hello messages by using an ACL that specifies the packet source addresses. It is used to guard against IPv6 PIM message attacks and to establish correct IPv6 PIM neighboring relationships.
  • Page 313 enable neighbor tracking, you must enable it on all IPv6 PIM routers on a shared-media LAN. Otherwise, the upstream router cannot track join messages from every downstream routers. • Generation ID—A router generates a generation ID for hello messages when an interface is enabled with IPv6 PIM.

  • Page 314: Configuring Common Ipv6 Pim Timers

    Configuring common IPv6 PIM timers IMPORTANT: To prevent the upstream neighbors from aging out, you must configure the interval for sending join/prune messages to be less than the joined/pruned state holdtime timer. The following are common timers in IPv6 PIM: •...

  • Page 315: Setting The Maximum Size Of A Join Or Prune Message

    Configuring common IPv6 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. ipv6 pim timer hello interval ipv6 pim triggered-hello-delay Set the triggered hello delay. The default setting is 5 seconds.

  • Page 316: Enabling Ipv6 Pim Passive Mode

    Enabling IPv6 PIM passive mode To guard against IPv6 PIM hello spoofing, you can enable IPv6 PIM passive mode on a receiver-side interface. The interface cannot receive or forward IPv6 PIM protocol messages (excluding register, register-stop and C-RP-Adv messages), and acts as the DR on the subnet. In IPv6 BIDIR-PIM, it also acts as the DF.

  • Page 317: Displaying And Maintaining Ipv6 Pim

    Step Command Remarks snmp-agent trap enable pim6 Enable SNMP notifications [ candidate-bsr-win-election | By default, SNMP notifications for for IPv6 PIM. elected-bsr-lost-election | IPv6 PIM are enabled. neighbor-loss ] * Displaying and maintaining IPv6 PIM Execute display commands in any view. Task Command Display register-tunnel interface...
  • Page 318 • Host A and Host C are multicast receivers in two stub networks N1 and N2. • MLDv1 runs between Switch A and N1, and between Switch B, Switch C, and N2. Figure 104 Network diagram Receiver Host A Switch A Vlan-int100 Host B Receiver...
  • Page 319 # Enable IPv6 PIM-DM on VLAN-interface 103. [SwitchA] interface vlan-interface 103 [SwitchA-Vlan-interface103] ipv6 pim dm [SwitchA-Vlan-interface103] quit # Enable IPv6 multicast routing, MLD, and IPv6 PIM-DM on Switch B and Switch C in the same way Switch A is configured. (Details not shown.) # On Switch D, enable IPv6 multicast routing, and enable IPv6 PIM-DM on each interface.

  • Page 320: Ipv6 Pim-Sm Non-Scoped Zone Configuration Example

    Total 1 (*, G) entry; 1 (S, G) entry (*, FF0E::101) Protocol: pim-dm, Flag: WC UpTime: 00:01:24 Upstream interface: NULL Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: mld, UpTime: 00:01:20, Expires: - (4001::100, FF0E::101) Protocol: pim-dm, Flag: ACT UpTime: 00:01:20...
  • Page 321 • OSPFv3 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 in each stub network. The entire IPv6 PIM-SM domain contains only one BSR. •...
  • Page 322 Enable IPv6 multicast routing, MLD, and IPv6 PIM-SM: # On Switch A, enable IPv6 multicast routing. <SwitchA> system-view [SwitchA] ipv6 multicast routing [SwitchA-mrib6] quit # Enable MLD on VLAN-interface 100 (the interface that is connected to the stub network). [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] mld enable [SwitchA-Vlan-interface100] quit # Enable IPv6 PIM-SM on other interfaces.

  • Page 323: Ipv6 Pim-Sm Admin-Scoped Zone Configuration Example

    # Display BSR information on Switch A. [SwitchA] display ipv6 pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:44 Elected BSR address: 1003::2 Priority: 64 Hash mask length: 126 Uptime: 00:11:18 # Display BSR information on Switch E. [SwitchE] display ipv6 pim bsr-info Scope: non-scoped State: Elected Bootstrap timer: 00:01:44...
  • Page 324 2. Both of the two interfaces are designated to the IPv6 multicast groups with the scope field value of 4. VLAN-interface 109 of Switch F acts as a C-BSR and a C-RP for the IPv6 global-scoped zone, and it is designated to the IPv6 multicast groups with the scope field value of 14.
  • Page 325 Device Interface IPv6 address Device Interface IPv6 address Switch D Vlan-int108 6001::1/64 Source 2 — 3001::100/64 Switch D Vlan-int107 6002::1/64 Source 3 — 9001::100/64 Switch E Vlan-int400 7001::1/64 Configuration procedure Assign an IPv6 address and prefix length to each interface, as shown in Figure 106.
  • Page 326 [SwitchB-Vlan-interface102] quit [SwitchB] interface vlan-interface 103 [SwitchB-Vlan-interface103] ipv6 multicast boundary scope 4 [SwitchB-Vlan-interface103] quit # On Switch C, configure VLAN-interface 103 and VLAN-interface 106 as the boundaries of IPv6 admin-scoped zone 2. <SwitchC> system-view [SwitchC] interface vlan-interface 103 [SwitchC-Vlan-interface103] ipv6 multicast boundary scope 4 [SwitchC-Vlan-interface103] quit [SwitchC] interface vlan-interface 106 [SwitchC-Vlan-interface106] ipv6 multicast boundary scope 4...
  • Page 327 Scope: 4 State: Elected Bootstrap timer: 00:00:06 Elected BSR address: 1002::2 Priority: 64 Hash mask length: 126 Uptime: 00:04:54 Candidate BSR address: 1002::2 Priority: 64 Hash mask length: 126 # Display BSR information on Switch D. [SwitchD] display ipv6 pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:25...
  • Page 328 RP address Priority HoldTime Uptime Expires 8001::1 00:01:14 00:02:46 Scope: 4 Group/MaskLen: FF04::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FF14::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FF24::/16 RP address Priority HoldTime Uptime Expires...

  • Page 329: Ipv6 Bidir-Pim Configuration Example

    Group/MaskLen: FFF4::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FF04::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 # Display RP information on Switch F. [SwitchF] display ipv6 pim rp-info BSR RP information: Scope: non-scoped Group/MaskLen: FF00::/8 RP address Priority...
  • Page 330 Device Interface IPv6 address Device Interface IPv6 address Switch B Vlan-int200 2001::1/64 Switch D Vlan-int103 3001::2/64 Switch B Vlan-int101 1002::2/64 Source 1 — 1001::2/64 Switch B Vlan-int102 2002::1/64 Source 2 — 5001::2/64 Switch C Vlan-int102 2002::2/64 Receiver 1 — 2001::2/64 Switch C Vlan-int103 3001::1/64...
  • Page 331 # On Switch C, enable IPv6 multicast routing, enable IPv6 PIM-SM on each interface, and enable IPv6 BIDIR-PIM. <SwitchC> system-view [SwitchC] ipv6 multicast routing [SwitchC-mrib6] quit [SwitchC] interface vlan-interface 102 [SwitchC-Vlan-interface102] ipv6 pim sm [SwitchC-Vlan-interface102] quit [SwitchC] interface vlan-interface 103 [SwitchC-Vlan-interface103] ipv6 pim sm [SwitchC-Vlan-interface103] quit [SwitchC] interface loopback 0...
  • Page 332 Vlan101 Lose 01:07:49 FE80::20F:E2FF: FE38:4E01 # Display IPv6 BIDIR-PIM DF information on Switch B. [SwitchB] display ipv6 pim df-info RP address: 6001::1 Interface State DF-Pref DF-Metric DF-Uptime DF-Address Vlan200 01:24:09 FE80::200:5EFF: FE71:2801 (local) Vlan101 01:24:09 FE80::20F:E2FF: FE38:4E01 (local) Vlan102 Lose 01:23:12 FE80::20F:E2FF: FE15:5601...

  • Page 333: Ipv6 Pim-Ssm Configuration Example

    Uptime: 00:06:24 RPF interface: Vlan-interface102 List of 2 DF interfaces: 1: Vlan-interface101 2: Vlan-interface200 # Display information about DFs for IPv6 multicast forwarding on Switch C. [SwitchC] display ipv6 multicast forwarding df-info Total 1 RP, 1 matched 00001. RP address: 6001::1 Flags: 0x0 Uptime: 00:07:21 RPF interface: LoopBack0...
  • Page 334 Figure 108 Network diagram Receiver Host A Switch A Vlan-int100 Vlan-int102 Host B Vlan-int102 Receiver Vlan-int300 Vlan-int105 Vlan-int103 Vlan-int200 Vlan-int105 Vlan-int103 Source Vlan-int104 Switch D Switch E Switch B Host C 4001::100/64 Vlan-int104 Vlan-int200 IPv6 PIM-SSM Host D Switch C Table 22 Interface and IPv6 address assignment Device Interface...
  • Page 335 [SwitchA-Vlan-interface100] quit # Enable IPv6 PIM-SM on the other interfaces. [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] ipv6 pim sm [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] ipv6 pim sm [SwitchA-Vlan-interface102] quit # Enable IPv6 multicast routing, MLD, and IPv6 PIM-SM on Switch B and Switch C in the same way Switch A is configured.

  • Page 336: Troubleshooting Ipv6 Pim

    Total 0 (*, G) entry; 1 (S, G) entry (4001::100, FF3E::101) Protocol: pim-ssm, Flag: LOC UpTime: 00:08:02 Upstream interface: Vlan-interface300 Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface105 Protocol: pim-ssm, UpTime: 00:08:02, Expires: 00:03:25 The output shows that switches on the SPT path (Switch A and Switch D) have generated the correct (S, G) entries.

  • Page 337: An Rp Cannot Join An Spt In Ipv6 Pim-Sm

    Solution To resolve the problem: Use display current-configuration to verify the IPv6 multicast forwarding boundary settings. Use ipv6 multicast boundary to change the multicast forwarding boundary settings to make the IPv6 multicast packet able to cross the boundary. Use display current-configuration to verify the IPv6 multicast source policy. Change the ACL rule defined in the source-policy command so that the source/group address of the IPv6 multicast data can pass ACL filtering.

  • Page 338: Document Conventions And Icons

    Document conventions and icons Conventions This section describes the conventions used in the documentation. 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. Italic Square brackets enclose syntax choices (keywords or arguments) that are optional.

  • Page 339: 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 340: 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 341: Websites

    For more information and device support details, go to the following website: www.hpe.com/info/insightremotesupport/docs Documentation feedback 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,...
  • Page 342 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 343: Index

    Index Numerics IP multicast model), assert IGMP snooping message 802.1p priority, IPv6 PIM-DM, MLD snooping 802.1p message priority, IPv6 PIM-SM, PIM-DM, PIM-SM, assigning IGMP snooping policy, port-based multicast VLAN user port, MLD snooping policy, attribute address port-based multicast VLAN user port attribute, IP multicast, MLD snooping message source IPv6 address, adjusting...
  • Page 344 IPv6 PIM-SM zone border router, IPv6 PIM-SM, PIM domain border, IPv6 PIM-SM RP discovery, PIM-SM configuration, PIM-SM zone border router, boundary PIM-SM RP discovery, IPv6 multicast forwarding boundary, changing multicast routing RPF route, multicast forwarding, broadcast checking IP multicast transmission technique, IPv6 multicast RPF check implementation, IPv6 multicast RPF check mechanism, BIDIR-PIM BSM device forwarding disable,...
  • Page 345 IGMP snooping query/response parameters IPv6 PIM-SM static RP, (VLAN), IPv6 PIM-SM switchover to SPT, IGMP snooping simulated member host, IPv6 PIM-SSM, 299, 323 IGMP snooping static port, 23, 36 IPv6 PIM-SSM group range, IGMP SSM mapping, IPv6 static multicast MAC address entry, IGMP SSM mapping configuration, MLD, 250, 255, 262...
  • Page 346 MSDP mesh group, port-based multicast VLAN, 54, 59 MSDP peer description, port-based multicast VLAN user port attribute, static IPv6 multicast MAC address entry (system MSDP peering connection, view), MSDP PIM-SM inter-domain multicast, static multicast MAC address entry, MSDP RPF static peer, static multicast MAC address entry (interface MSDP SA message cache, view),...
  • Page 347 IPv6 PIM-SM non-scoped zone configuration, PIM-SM RP discovery, PIM-SSM neighbor discovery, IPv6 PIM-SSM configuration, displaying MLD basics configuration, IGMP, MLD configuration, IGMP snooping, MLD proxying configuration, IPv6 multicast routing+forwarding, MLD SSM mapping configuration, IPv6 multicast VLAN, MSDP configuration, IPv6 PIM, MSDP inter-AS multicast configuration (static IPv6 PIM snooping, RPF peers),...
  • Page 348 IGMP snooping dynamic router port, MLD NSR, IGMP snooping dynamic router port change, MLD proxying, MLD snooping, MLD snooping dynamic member port, MLD snooping (a VLAN), MLD snooping dynamic port aging timers, MLD snooping (global), MLD snooping dynamic router port, MLD snooping (multiple VLANs), MLD snooping dynamic router port change, MLD snooping fast-leave processing (global),...
  • Page 349 PIM-SM admin-scoped zone configuration, IPv6 multicast sub-VLAN forwarding, IPv6 multicast VLAN forwarding entries max, PIM-SM non-scoped zone configuration, IPv6 PIM administrative scoping, PIM-SSM configuration, IPv6 PIM common feature, IPv6 PIM configuration, 270, 307 IPv6 PIM multicast source policy, fast IPv6 PIM protocol relationships, IGMP fast-leave processing, IPv6 PIM snooping configuration, 222, 223, 224...
  • Page 350 PIM-SM zone border router, global-scoped zone PIM-SM admin-scoped/global-scoped zone IPv6 PIM hello message Generation ID option, relationship, graft PIM hello message Generation ID option, IPv6 PIM-DM, IGMP IPv6 PIM-DM graft retry timer, basic configuration, 85, 93 PIM-DM, configuration, 79, 85, 93 PIM-DM graft retry timer, display, enable,...
  • Page 351 dynamic port aging timers, implementation, 79, 79 dynamic router port change disable, version specification, IGMPv1 snooping version, enable, fast-leave processing enable, IGMPv2 fast-leave processing enable restrictions, features, IGMP versions, forwarding entries, general query, leave group mechanism, general query/response parameter querier election, configuration, version specification, group policy+simulated joining configuration,...
  • Page 352 IGMP basic configuration, 85, 93 IGMP snooping static port configuration, IGMP configuration, 79, 85, 93 IGMP snooping unknown multicast data drop, IGMP snooping version, IGMP display, IGMP fast-leave processing, IGMP SSM mapping, IGMP maintain, IGMP SSM mapping configuration, IGMP static group member configuration, IGMP multicast forwarding (non-querier interface), IGMP version specification,...
  • Page 353 Layer 2 protocols, MLD static group member, Layer 3 protocols, MLD version specification, MLD VPN support, MLD basics configuration, MLD configuration, 250, 255, 255, 262, 262 models, MLD display, MSDP Anycast RP, MSDP Anycast RP configuration, MLD fast-leave processing, MLD maintain, MSDP basics configuration, MLD performance adjustment, MSDP configuration,...
  • Page 354 PIM-DM configuration, 116, 138 troubleshooting IPv6 PIM snooping, PIM-DM enable, troubleshooting IPv6 PIM snooping on Layer 2 device, PIM-DM graft, troubleshooting IPv6 PIM-SM multicast source PIM-DM graft retry timer, registration failure, PIM-DM neighbor discovery, troubleshooting IPv6 PIM-SM RP cannot join PIM-DM SPT building, SPT, PIM-DM state-refresh,...
  • Page 355 PIM-SM DR election, forwarding entries max, PIM-SSM. See IPv6 PIM-SSM maintain, port –based implementation, IPv6 BIDIR-PIM administrative scoping, port-based configuration, 232, 237 bidirectional RPT building, port-based user port assignment, port-based user port assignment restrictions, BSM semantic fragmentation, BSR configuration, port-based user port attribute configuration, C-BSR configuration, sub-VLAN-based configuration, configuration,...
  • Page 356 IPv6 PIM protocol relationships, SPT building, neighbor discovery, protocols and standards, joining SPT building, IPv6 PIM join/prune message max size, state refresh enable, MLDv1 IPv6 multicast group joining, state refresh parameters, PIM join/prune message size, IPv6 PIM-SM administrative scoping, 281, 281 administrative scoping zone border router, Layer 2 IP multicast protocols,...
  • Page 357 static multicast MAC address entry, MSDP SA message multicast data encapsulation, maintaining MSDP SA message originating RP, IGMP, MSDP SA message policy, IGMP snooping, MSDP SA message-related parameters, IPv6 multicast routing+forwarding, MSDP SA request message, IPv6 multicast VLAN, PIM hello message options, IPv6 PIM snooping, PIM hello policy, MLD,...
  • Page 358 802.1p message priority, querier enable restrictions, basic configuration, report suppression, simulated member host port, configuration, 190, 194, 211 display, static port configuration, 200, 213 done message, troubleshoot, troubleshoot IPv6 multicast group policy, dynamic port aging timers, dynamic router port change disable, troubleshoot MLD snooping Layer 2 forwarding, enable, version specification,...
  • Page 359 peer configuration, IPv6 multicast VLAN. See IPv6 multicast VLAN peer description, maintain, port-based configuration, peering connection, peering connection control, port-based multicast VLAN configuration, peer-RPF forwarding, port-based multicast VLAN user port assignment, PIM-SM inter-domain multicast configuration, port-based multicast VLAN user port assignment restrictions, protocols and standards, port-based multicast VLAN user port attribute,...
  • Page 360 IGMP snooping proxying configuration, IPv6 PIM-SM BSM forwarding disable, IGMP snooping querier configuration, IPv6 PIM-SM BSR, IPv6 PIM-SM configuration, IGMP snooping static port configuration, IGMP SSM mapping configuration, IPv6 PIM-SM multicast source registration, IGMP static group member configuration, IPv6 PIM-SM non-scoped zone configuration, IPv6 PIM-SM RP, IGMP version specification, IP multicast address,...
  • Page 361 PIM BFD enable, port-based multicast VLAN user port assignment, PIM common features, port-based multicast VLAN user port attribute, PIM common timers, static multicast MAC address entry, PIM domain border, sub-VLAN-based IPv6 multicast VLAN PIM hello message options, configuration, PIM hello policy, sub-VLAN-based multicast VLAN configuration, PIM join/prune message size, 53, 56...
  • Page 362 option common timer configuration, IPv6 PIM hello message DR_Priority, common timer configuration (global), common timer configuration (on interface), IPv6 PIM hello message Generation ID, IPv6 PIM hello message holdtime, configuration, 101, 138 IPv6 PIM hello message LAN_Prune_Delay, display, DM. See PIM-DM IPv6 PIM hello message options, hello message option configuration (global),...
  • Page 363 PIM configuration, MSDP SA request message, PIM NSR enable, multicast routing+forwarding configuration, multicast source registration, 107, 124 PIM passive mode enable, PIM protocol relationships, neighbor discovery, PIM SNMP notification enable, non-scoped zone configuration, PIM BFD enable, protocols and standards, SPT building, PIM configuration, state-refresh enable, PIM domain border,...
  • Page 364 IGMP snooping configuration, 13, 17, 34 port-based multicast VLAN user port attribute, IGMP snooping dynamic port aging timers, port-based IPv6 multicast VLAN IGMP snooping dynamic router port change, configuration, 232, 237 implementation, IGMP snooping fast-leave processing, user port assignment, IGMP snooping group policy+simulated user port assignment restrictions, joining configuration, user port attribute configuration,...
  • Page 365 configuring IGMP snooping message configuring IPv6 PIM hello message options parameters, (interface), configuring IGMP snooping message source configuring IPv6 PIM hello policy, IP address, configuring IPv6 PIM multicast source policy, configuring IGMP snooping multicast group configuring IPv6 PIM snooping, 223, 224 policy, configuring IPv6 PIM timer, configuring IGMP snooping multicast group...
  • Page 366 configuring MLD snooping group configuring PIM common features, policy+simulated joining, configuring PIM common timer globally, configuring MLD snooping IPv6 multicast configuring PIM common timer on interface, group policy (global), configuring PIM common timers, configuring MLD snooping IPv6 multicast configuring PIM domain border, group policy (port), configuring PIM hello message option globally, configuring MLD snooping IPv6 multicast...
  • Page 367 disabling IGMP snooping dynamic router port enabling IGMP snooping host tracking (global), change, disabling IP multicast BIDIR-PIM BSM enabling IGMP snooping host tracking (VLAN), semantic fragmentation, enabling IGMP snooping proxying, disabling IPv6 BIDIR-PIM BSM semantic enabling IGMP snooping report suppression, fragmentation, enabling IP multicast routing, disabling IPv6 PIM-SM BSM forwarding,...
  • Page 368 enabling PIM-DM state-refresh, setting multicast VLAN forwarding entries max, enabling PIM-SM, setting PIM join/prune message size, enabling PIM-SM Auto-RP listening, specifying IGMP snooping version, 19, 19 maintaining IGMP, specifying IGMP snooping version (IGMP-snooping view), maintaining IGMP snooping, specifying IGMP snooping version (VLAN view), maintaining IPv6 multicast VLAN, maintaining IPv6 PIM snooping, specifying IGMP version,...
  • Page 369 troubleshooting PIM snooping does not work, IGMP snooping general query, IGMP snooping general query/response troubleshooting PIM-SM multicast source parameters, registration failure, IGMP snooping querier, 25, 25 Protocol Independent Multicast. Use IGMP snooping querier configuration, protocols and standards IGMPv2 querier election, IGMP, IGMPv3 query capability, IGMP snooping,...
  • Page 370 MLD snooping IPv6 multicast group IGMP snooping basic configuration, configuration on port, IGMP snooping configuration, 13, 17, 34 MLD snooping IPv6 multicast group policy IGMP snooping dynamic router port change, configuration, IGMP snooping forwarding entries, MLD snooping IPv6 multicast group IGMP snooping general query/response replacement, parameters,...
  • Page 371 IPv6 multicast VLAN configuration, 229, 231, MLD basics configuration, MLD configuration, 250, 255, 262 IPv6 PIM administrative scoping, MLD IPv6 multicast forwarding (non-querier IPv6 PIM common feature, interface), IPv6 PIM configuration, 270, 307 MLD MP snooping proxying, IPv6 PIM hello message options, MLD NSR, IPv6 PIM hello policy, MLD proxying,...
  • Page 372 PIM common timers, BIDIR-PIM, PIM configuration, 101, 138 BIDIR-PIM Auto-RP listening, BIDIR-PIM bidirectional RPT building, PIM domain border, PIM hello message options, BIDIR-PIM configuration, PIM hello policy, BIDIR-PIM C-RP, BIDIR-PIM discovery, PIM join/prune message size, PIM multicast source policy, BIDIR-PIM RP max, PIM NSR enable, BIDIR-PIM static RP configuration, PIM snooping configuration,...
  • Page 373 MSDP peer-RPF forwarding, IGMP snooping message 802.1p priority (VLAN), multicast check mechanism, IGMP snooping multicast groups on port, multicast check process, IPv6 BIDIR-PIM RP max, multicast routing RPF route change, IPv6 multicast VLAN forwarding entries max, multicast routing RPF route creation, IPv6 PIM join/prune message max size, multicast RPF check implementation, MLD last listener query interval (global),...
  • Page 374 IGMP snooping version (VLAN view), MLD snooping static router port, IGMP version, MSDP RPF static peer, multicast static route configuration, IPv6 multicast longest prefix match principle, multicast static RPF route, MLD snooping version, 196, 196 PIM-SM static RP, MLD snooping version (MLD-snooping view), static multicast MAC address entry, subnetting MLD snooping version (VLAN view),...
  • Page 375 IGMP configuration, 79, 85, 93 IPv6 PIM multicast distribution tree, IGMP proxying configuration, IPv6 PIM snooping, IPv6 PIM snooping on Layer 2 device, IGMP SSM mapping configuration, MSDP peering connection control, IPv6 PIM-SM multicast source registration failure, timer IPv6 PIM-SM RP cannot join SPT, IGMP snooping dynamic member port aging timer, IPv6 PIM-SM RPT cannot be built,...
  • Page 376 IGMPv3, 79, 81 MLD snooping dynamic port aging timers, IGMPv3 snooping, MLD snooping dynamic port aging timers setting, MLD snooping specification, MLD snooping enable, MLD version specification, MLD snooping fast-leave processing enable, MLDv1, MLD snooping general query/response MLDv1 snooping, parameter configuration (VLAN), MLDv2, MLD snooping general query/response MLDv2 snooping,...
  • Page 377 PIM-SM admin-scoped/global-scoped zone relationship, PIM-SM non-scoped zone configuration,...

Table of Contents