Page 1: Configuration Guide
HP 6125 Blade Switch Series IP Multicast Configuration Guide Part number: 5998-3158 Software version: Release 2103 Document version: 6W100-20120907...
Page 2 HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
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 advantages and applications ················································································································· 4 Multicast models ································································································································································ 5 ...
Page 4 Static port configuration example ······················································································································· 35 IGMP snooping querier configuration example ································································································· 38 IGMP snooping proxying configuration example ······························································································ 40 Troubleshooting IGMP snooping ·································································································································· 43 Layer 2 multicast forwarding cannot function ···································································································· 43 Configured multicast group policy fails to take effect ······················································································· 43 ...
Page 5 IGMP configuration task list ·········································································································································· 82 Configuring basic IGMP functions ······························································································································· 83 Enabling IGMP ······················································································································································ 83 Configuring IGMP versions ·································································································································· 83 Configuring static joining ····································································································································· 84 Configuring a multicast group filter ····················································································································· 84 Setting the maximum number of multicast groups that an interface can join ················································· 85 ...
Page 6 Configuration prerequisites ································································································································ 127 Enabling PIM-SM ················································································································································· 127 Configuring the SSM group range ···················································································································· 128 Configuring PIM common features ····························································································································· 128 PIM common feature configuration task list ······································································································ 129 Configuration prerequisites ································································································································ 129 Configuring a multicast data filter ····················································································································· 129 ...
Page 7 Configuring MBGP ·················································································································································· 186 MBGP overview ···························································································································································· 186 Protocols and standards ·············································································································································· 186 MBGP configuration task list ······································································································································· 186 Configuring basic MBGP functions ···························································································································· 187 Controlling route advertisement and reception ········································································································· 187 Configuring MBGP route redistribution ············································································································· 187 ...
Page 8 Enabling MLD snooping proxying ····················································································································· 219 Configuring the source IPv6 addresses for the MLD messages sent by the proxy ······································· 220 Configuring an MLD snooping policy ························································································································ 220 Configuring an IPv6 multicast group filter ········································································································ 220 Configuring IPv6 multicast source port filtering ·······························································································...
Page 9 How MLDv1 works ·············································································································································· 258 How MLDv2 works ·············································································································································· 260 MLD messages ····················································································································································· 261 MLD SSM mapping ············································································································································· 264 MLD proxying ······················································································································································ 265 Protocols and standards ····································································································································· 265 MLD configuration task list ·········································································································································· 266 ...
Page 10 Configuring an RP ··············································································································································· 303 Configuring a BSR ··············································································································································· 305 Configuring IPv6 administrative scoping ·········································································································· 309 Configuring IPv6 multicast source registration ································································································· 310 Disabling the switchover to SPT ························································································································· 311 Configuring IPv6 PIM-SSM ·········································································································································· 311 ...
Page 11 Tuning and optimizing IPv6 MBGP networks ············································································································ 354 Configuration prerequisites ································································································································ 354 Configuring IPv6 MBGP soft reset ····················································································································· 354 Enabling the IPv6 MBGP orf capability ············································································································ 355 Configuring the maximum number of equal-cost routes for load-balancing ················································· 356 ...
Page 12: Multicast Overview
Multicast overview Introduction to multicast As a technique that coexists with unicast and broadcast, the multicast technique effectively addresses the issue of point-to-multipoint data transmission. By enabling high-efficiency point-to-multipoint data transmission over a network, multicast greatly saves network bandwidth and reduces network load. By using multicast technology, a network operator can easily provide new value-added services, such as live webcasting, web TV, distance learning, telemedicine, web radio, real time video conferencing, and other bandwidth-critical and time-critical information services.
Page 13 In unicast transmission, the traffic transmitted over the network is proportional to the number of hosts that need the information. If a large number of hosts need the information, the information source must send a separate copy of the same information to each of these hosts. Sending many copies can place a tremendous pressure on the information source and the network bandwidth.
Page 14: Multicast Features
Figure 3 Multicast transmission The multicast source sends only one copy of the information to a multicast group. Host B, Host D and Host E, which are receivers of the information, must join the multicast group. The routers on the network duplicate and forward the information based on the distribution of the group members.
Page 15: Common Notations In Multicast
For a better understanding of the multicast concept, you can compare multicast transmission to the transmission of TV programs. Table 1 Comparing TV program transmission and multicast transmission TV transmission Multicast transmission A TV station transmits a TV program through a A multicast source sends multicast data to a multicast channel.
Page 16: Multicast Models
Multicast models Based on how the receivers treat the multicast sources, the multicast models include any-source multicast (ASM), source-filtered multicast (SFM), and source-specific multicast (SSM). ASM model In the ASM model, any sender can send information to a multicast group as a multicast source, and receivers can join a multicast group (identified by a group address) and obtain multicast information addressed to that multicast group.
Page 17: Multicast Addresses
Multicast addresses Network-layer multicast addresses (multicast IP addresses) enables communication between multicast sources and multicast group members. In addition, a technique must be available to map multicast IP addresses to link-layer multicast MAC addresses. IP multicast addresses IPv4 multicast addresses •...
Page 18 Address Description 224.0.0.12 Dynamic Host Configuration Protocol (DHCP) server/relay agent 224.0.0.13 All Protocol Independent Multicast (PIM) routers 224.0.0.14 Resource Reservation Protocol (RSVP) encapsulation 224.0.0.15 All Core-Based Tree (CBT) routers 224.0.0.16 Designated Subnetwork Bandwidth Management (SBM) 224.0.0.17 All SBMs 224.0.0.18 Virtual Router Redundancy Protocol (VRRP) IPv6 multicast addresses •...
Page 19 Table 5 Values of the Scope field Value Meaning 0, F Reserved Interface-local scope Link-local scope Subnet-local scope Admin-local scope Site-local scope 6, 7, 9 through D Unassigned Organization-local scope Global scope Group ID—The Group ID field contains 1 12 bits. It uniquely identifies an IPv6 multicast group in the scope that the Scope field defines.
Page 20: Multicast Protocols
Figure 7 An example of IPv6-to-MAC address mapping Multicast protocols Generally, Layer 3 multicast refers to IP multicast working at the network layer. The corresponding multicast protocols are Layer 3 multicast protocols, which include IGMP, MLD, PIM, IPv6 PIM, MSDP, MBGP, and IPv6 MBGP.
Page 21 protocols define the mechanism of establishing and maintaining group memberships between hosts and Layer 3 multicast devices. Multicast routing protocols • A multicast routing protocol runs on Layer 3 multicast devices to establish and maintain multicast routes and forward multicast packets correctly and efficiently. Multicast routes constitute loop-free data transmission paths from a data source to multiple receivers, namely, a multicast distribution tree.
Page 22: Multicast Packet Forwarding Mechanism
PIM snooping and IPv6 PIM snooping • PIM snooping and IPv6 PIM snooping run on Layer 2 devices. They determine which ports are interested in multicast data by analyzing the received IPv6 PIM messages, and add the ports to a multicast forwarding entry to make sure that multicast data can be forwarded to only the ports that are interested in the data.
Page 23: Configuring Igmp Snooping
Configuring IGMP snooping Overview Internet Group Management Protocol (IGMP) snooping is a multicast constraining mechanism that runs on Layer 2 devices to manage and control multicast groups. By analyzing received IGMP messages, a Layer 2 device that runs IGMP snooping establishes mappings between ports and multicast MAC addresses, and forwards multicast data based on these mappings.
Page 24 Figure 11 IGMP snooping related ports The following describes the ports involved in IGMP snooping: • Router port—Layer 3 multicast device-side port. Layer 3 multicast devices include designated routers (DRs) and IGMP queriers. In Figure 1 1, GigabitEthernet 1/0/1 of Switch A and GigabitEthernet 1/0/1 of Switch B are router ports.
Page 25: How Igmp Snooping Works
Timer Description Message before expiry Action after expiry When a port dynamically joins a multicast group, The switch removes this the switch starts an aging Dynamic member port IGMP membership port from the IGMP timer for the port. When aging timer report.
Page 26: Igmp Snooping Proxying
unable to know whether the reported multicast group still has active members attached to that port. For more information about the IGMP report suppression mechanism, see "Configuring IGMP." When receiving a leave message When an IGMPv1 host leaves a multicast group, the host does not send an IGMP leave message, and the switch cannot know immediately that the host has left the multicast group.
Page 27 Figure 12 Network diagram IGMP Querier IP network Router A Query from Router A Report from Switch A Query from Switch A Proxy & Querier Switch A Report from Host Host A Host C Receiver Receiver Host B As shown in Figure 12, Switch A works as an IGMP snooping proxy.
Page 28: Protocols And Standards
Protocols and standards RFC 4541, Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping Switches IGMP snooping configuration task list Task Remarks Enabling IGMP snooping Required Configuring basic IGMP snooping Specifying the version of IGMP snooping Optional functions Configuring static multicast MAC address entries...
Page 29: Configuring Basic Igmp Snooping Functions
effective only on the current port. For a given port, a configuration that you make in IGMP snooping view is effective only if you do not make the same configuration in Layer 2 Ethernet interface view or Layer 2 aggregate interface view. •...
Page 30: Configuring Static Multicast Mac Address Entries
For more information about static joins, see "Configuring static ports." To specify the version of IGMP snooping: Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Specify the version of IGMP igmp-snooping version Version 2 by default snooping.
Page 31: Setting Aging Timers For Dynamic Ports
Determine the aging time of dynamic router ports. • • Determine the aging time of dynamic member ports. Determine the multicast group and multicast source addresses. • Setting aging timers for dynamic ports If a switch receives no IGMP general queries or PIM hello messages on a dynamic router port when the aging timer of the port expires, the switch removes the port from the router port list.
Page 32: Configuring A Port As A Simulated Member Host
Configuration guidelines A static member port does not respond to queries from the IGMP querier; when you configure a port • as a static member port or cancel this configuration on the port, the port does not send an unsolicited IGMP report or an IGMP leave message. •...
Page 33: Enabling Igmp Snooping Fast-Leave Processing
Step Command Remarks igmp-snooping host-join Configure a port as a group-address [ source-ip Not configured by default. simulated member host. source-address ] vlan vlan-id Enabling IGMP snooping fast-leave processing IGMP snooping fast-leave processing enables the switch to process IGMP leave messages quickly. With IGMP snooping fast-leave processing enabled, when the switch receives an IGMP leave message on a port, it immediately removes that port from the forwarding entry for the multicast group specified in the message.
Page 34: Configuring Igmp Snooping Querier
In addition, the IGMP general query or PIM hello message that the host sends affects the multicast • routing protocol state on Layer 3 devices, such as the IGMP querier or DR election, and might further cause network interruption. To solve these problems, disable that router port from becoming a dynamic router port after the port receives an IGMP general query or a PIM hello message, so as to improve network security and control over multicast users.
Page 35: Configuring Parameters For Igmp Queries And Responses
Step Command Remarks Enter VLAN view. vlan vlan-id Enable IGMP snooping igmp-snooping querier Disabled by default querier. IMPORTANT: In a multicast network that runs IGMP, you do not need to configure an IGMP snooping querier because it may affect IGMP querier elections by sending IGMP general queries with a low source IP address. Configuring parameters for IGMP queries and responses CAUTION: In the configuration, make sure that the IGMP general query interval is larger than the maximum response...
Page 36: Configuring The Source Ip Addresses For Igmp Queries
Step Command Remarks Set the maximum response delay for IGMP general igmp-snooping max-response-time interval 10 seconds by default queries. Set the IGMP last-member igmp-snooping 1 second by default query interval. last-member-query-interval interval Configuring the source IP addresses for IGMP queries After the switch receives an IGMP query whose source IP address is 0.0.0.0 on a port, it does not enlist that port as a dynamic router port.
Page 37: Configuring A Source Ip Address For The Igmp Messages Sent By The Proxy
Step Command Remarks Enter VLAN view. vlan vlan-id Enable IGMP snooping igmp-snooping proxying enable Disabled by default proxying in the VLAN. Configuring a source IP address for the IGMP messages sent by the proxy You can set the source IP addresses in the IGMP reports and leave messages that the IGMP snooping proxy sends on behalf of its attached hosts.
Page 38: Configuring Multicast Source Port Filtering
Configuration guidelines When you configure a multicast group filter in a multicast VLAN, be sure to configure the filter in the • sub-VLANs of the multicast VLAN. Otherwise, the configuration does not take effect. • In IGMPv3, when a host is enabled to join multiple multicast groups, the multicast group filter cannot correctly filter multicast groups because the host that runs IGMPv3 sends multiple multicast groups that it wants to join in one membership report.
Page 39: Enabling Dropping Unknown Multicast Data
Configuring multicast source port filtering on a port Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface-type Use either command. interface view. interface-number Enable multicast source port igmp-snooping source-deny Disabled by default. filtering. Enabling dropping unknown multicast data Unknown multicast data refers to multicast data for which no entries exist in the IGMP snooping forwarding table.
Page 40: Configuring Igmp Report Suppression
Configuring IGMP report suppression When a Layer 2 switch receives an IGMP report from a multicast group member, the switch forwards the message to the Layer 3 device that directly connects to the Layer 2 switch. When multiple members of a multicast group are attached to the Layer 2 switch, the Layer 3 device might receive duplicate IGMP reports for the multicast group from these members.
Page 41: Enabling Multicast Group Replacement
Enabling multicast group replacement For various reasons, the number of multicast groups that the switch or a port joins might exceed the upper limit. In addition, in some specific applications, a multicast group that the switch newly joins must replace an existing multicast group automatically.
Page 42: Enabling The Igmp Snooping Host Tracking Function
Setting the 802.1p precedence for IGMP messages globally Step Command Remarks Enter system view. system-view Enter IGMP-snooping view. igmp-snooping Set the 802.1p precedence for The default 802.1p precedence for dot1p-priority priority-number IGMP messages. IGMP messages is 0. Setting the 802.1p precedence for IGMP messages in a VLAN Step Command Remarks...
Page 43: Displaying And Maintaining Igmp Snooping
This configuration applies to only the IGMP messages that the local switch generates when the switch or its port acts as a member host, rather than those forwarded ones. To set the DSCP value for IGMP messages: Step Command Remarks Enter system view.
Page 44: Igmp Snooping Configuration Examples
IGMP snooping configuration examples Group policy and simulated joining configuration example Network requirements As shown in Figure 13, IGMPv2 runs on Router A, IGMPv2 snooping runs on Switch A, and Router A acts as the IGMP querier on the subnet. The receivers, Host A and Host B, can receive multicast traffic addressed to multicast group 224.1.1.1 only.
Page 45: Verifying The Configuration
<SwitchA> system-view [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 100, assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to this VLAN, and enable IGMP snooping and the function of dropping unknown multicast traffic in the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/4 [SwitchA-vlan100] igmp-snooping enable [SwitchA-vlan100] igmp-snooping drop-unknown [SwitchA-vlan100] quit...
Page 46: Static Port Configuration Example
GE1/0/4 (D) ( 00:04:10 ) MAC group(s): MAC group address:0100-5e01-0101 Host port(s):total 2 port. GE1/0/3 GE1/0/4 The output shows that GigabitEthernet 1/0/3 and GigabitEthernet 1/0/4 of Switch A has joined multicast group 224.1.1.1. Static port configuration example Network requirements As shown in Figure 14, IGMPv2 runs on Router A, and IGMPv2 snooping runs on Switch A, Switch B, and Switch C.
Page 47: Configuration Procedure
Figure 14 Network diagram Switch B Source Switch A GE1/0/2 GE1/0/1 1.1.1.2/24 10.1.1.1/24 GE1/0/1 Router A 1.1.1.1/24 IGMP querier Switch C Host C Host A Receiver Receiver Host B VLAN 100 Configuration procedure Configure an IP address and subnet mask for each interface as per Figure 14.
Page 48 [SwitchA-GigabitEthernet1/0/3] igmp-snooping static-router-port vlan 100 [SwitchA-GigabitEthernet1/0/3] quit Configure Switch B: # Enable IGMP snooping globally. <SwitchB> system-view [SwitchB] igmp-snooping [SwitchB-igmp-snooping] quit # Create VLAN 100, assign GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 to this VLAN, and enable IGMP snooping in the VLAN. [SwitchB] vlan 100 [SwitchB-vlan100] port gigabitethernet 1/0/1 gigabitethernet 1/0/2 [SwitchB-vlan100] igmp-snooping enable...
Page 49: Igmp Snooping Querier Configuration Example
GE1/0/1 (D) ( 00:01:30 ) GE1/0/3 IP group(s):the following ip group(s) match to one mac group. IP group address:224.1.1.1 (0.0.0.0, 224.1.1.1): Attribute: Host Port Host port(s):total 1 port. GE1/0/2 (D) ( 00:03:23 ) MAC group(s): MAC group address:0100-5e01-0101 Host port(s):total 1 port. GE1/0/2 The output shows that GigabitEthernet 1/0/3 of Switch A has become a static router port.
Page 50 are receivers of multicast group 224.1.1.1, and Host B and Host D are receivers of multicast group 225.1.1.1. All the receivers run IGMPv2, and all the switches run IGMPv2 snooping. Switch A, which is close to the multicast sources, is chosen as the IGMP snooping querier. To prevent flooding of unknown multicast traffic within the VLAN, be sure to configure all the switches to drop unknown multicast data packets.
Page 51: Igmp Snooping Proxying Configuration Example
Configure Switch B: # Enable IGMP snooping globally. <SwitchB> system-view [SwitchB] igmp-snooping [SwitchB-igmp-snooping] quit # Create VLAN 100, and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to the VLAN. [SwitchB] vlan 100 [SwitchB-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/4 # Enable IGMP snooping and the function of dropping unknown multicast traffic in VLAN 100. [SwitchB-vlan100] igmp-snooping enable [SwitchB-vlan100] igmp-snooping drop-unknown [SwitchB-vlan100] quit...
Page 52 Figure 16 Network diagram Configuration procedure Configure an IP address and subnet mask for each interface as per Figure 16. (Details not shown.) On Router A, enable IP multicast routing, enable IGMP on GigabitEthernet 1/0/1, and enable PIM-DM on each interface. <RouterA>...
Page 53 Verifying the configuration After the configuration is completed, Host A and Host B send IGMP join messages for group 224.1.1.1. Receiving the messages, Switch A sends a join message for the group out of port GigabitEthernet 1/0/1 (a router port) to Router A. Use the display igmp-snooping group command and the display igmp group command to display information about IGMP snooping groups and IGMP multicast groups.
Page 54: Troubleshooting Igmp Snooping
Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s). Port flags: D-Dynamic port, S-Static port, C-Copy port, P-PIM port Subvlan flags: R-Real VLAN, C-Copy VLAN Vlan(id):100. Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s). Router port(s):total 1 port.
Page 55: Appendix
The multicast group policy is not correctly applied. • • The function of dropping unknown multicast data is not enabled, so unknown multicast data is flooded. Solution Use the display acl command to check the configured ACL rule. Make sure that the ACL rule conforms to the multicast group policy to be implemented.
Page 56: Configuring Multicast Vlans
Configuring multicast VLANs Overview In the traditional multicast programs-on-demand mode shown in Figure 17, when hosts (Host A, Host B and Host C) that belong to different VLANs require multicast programs-on-demand service, the Layer 3 device, Router A, must forward a separate copy of the multicast traffic in each user VLAN to the Layer 2 device, Switch A.
Page 57 Figure 18 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 Router A Switch A Source IGMP querier VLAN 4 Receiver Host C After the configuration, IGMP snooping manages router ports in the multicast VLAN and member ports in the sub-VLANs.
Page 58: Multicast Vlan Configuration Task List
For more information about IGMP snooping, router ports, and member ports, see "Configuring IGMP snooping." For more information about VLAN tags, see Layer 2—LAN Switching Configuration Guide. Multicast VLAN configuration task list Task Remarks Configuring a sub-VLAN-based multicast VLAN Required Configuring user port attributes Configuring a port-based Use either approach.
Page 59: Configuring A Port-Based Multicast Vlan
Configuring a port-based multicast VLAN When you configure a port-based multicast VLAN, you must configure the attributes of each user port and then assign the ports to the multicast VLAN. A user port can be configured as a multicast VLAN port only if it is an Ethernet port, or Layer 2 aggregate interface.
Page 60: Configuring Multicast Vlan Ports
Configuring multicast VLAN ports In this approach, you configure a VLAN as a multicast VLAN and assign user ports to it. You can do this by either adding the user ports in the multicast VLAN or specifying the multicast VLAN on the user ports. These two methods provide the same result.
Page 61: Multicast Vlan Configuration Examples
Multicast VLAN configuration examples Sub-VLAN-based multicast VLAN configuration example Network requirements As shown in Figure 20, IGMPv2 runs on Router A, and IGMPv2 snooping runs on Switch A, Switch B, and Switch C. Router A acts as the IGMP querier. The multicast source sends multicast data to multicast group 224.1.1.1.
Page 62 Configure Switch A: # Enable IGMP snooping globally. <SwitchA> system-view [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 2 through VLAN 5. [SwitchA] vlan 2 to 5 # Configure GigabitEthernet 1/0/2 as a trunk port, and assign it to VLAN 2 and VLAN 3. [SwitchA] interface gigabitethernet 1/0/2 [SwitchA-GigabitEthernet1/0/2] port link-type trunk [SwitchA-GigabitEthernet1/0/2] port trunk permit vlan 2 3...
Page 63 [SwitchB] interface gigabitethernet 1/0/1 [SwitchB-GigabitEthernet1/0/1] port link-type trunk [SwitchB-GigabitEthernet1/0/1] port trunk permit vlan 2 3 Configure Switch C in the same way as you configure Switch B. (Details not shown.) Verifying the configuration # Display information about the multicast VLAN. [SwitchA] display multicast-vlan Total 1 multicast-vlan(s) Multicast vlan 10...
Page 64 MAC group(s): MAC group address:0100-5e01-0101 Host port(s):total 1 port(s). GE1/0/2 Vlan(id):4. Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s). Router port(s):total 0 port(s). IP group(s):the following ip group(s) match to one mac group. IP group address:224.1.1.1 (0.0.0.0, 224.1.1.1): Host port(s):total 1 port(s).
Page 65: Port-Based Multicast Vlan Configuration Example
The output shows that IGMP snooping is maintaining the router port in the multicast VLAN (VLAN 10) and the member ports in the sub-VLANs (VLAN 2 through VLAN 5). Port-based multicast VLAN configuration example Network requirements As shown in Figure 21, IGMPv2 runs on Router A.
Page 66 [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 10, assign GigabitEthernet 1/0/1 to VLAN 10, and enable IGMP snooping in this VLAN. [SwitchA] vlan 10 [SwitchA-vlan10] port gigabitethernet 1/0/1 [SwitchA-vlan10] igmp-snooping enable [SwitchA-vlan10] quit # Create VLAN 2 and enable IGMP snooping in the VLAN. [SwitchA] vlan 2 [SwitchA-vlan2] igmp-snooping enable [SwitchA-vlan2] quit...
Page 67 Total 1 IP Source(s). Total 1 MAC Group(s). Port flags: D-Dynamic port, S-Static port, C-Copy port, P-PIM port Subvlan flags: R-Real VLAN, C-Copy VLAN Vlan(id):10. Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s). Router port(s):total 1 port(s). GE1/0/1 IP group(s):the following ip group(s) match to one mac group.
Page 68: Configuring Multicast Routing And Forwarding
Configuring multicast routing and forwarding Overview In multicast implementations, the following types of tables implement multicast routing and forwarding: Multicast routing table of a multicast routing protocol—Each multicast routing protocol has its own • multicast routing table, such as PIM routing table. General multicast routing table—The multicast routing information of different multicast routing •...
Page 69 The router automatically chooses an optimal MBGP route by searching its MBGP routing table, and using the IP address of the packet source as the destination address. The outgoing interface in the corresponding routing entry is the RPF interface and the next hop is the RPF neighbor.
Page 70: Static Multicast Routes
packet arrived is the RPF interface, the router forwards the packet to all the outgoing interfaces. Otherwise, it discards the packet. Assume that unicast routes are available in the network, MBGP is not configured, and no static multicast routes have been configured on Switch C, as shown in Figure 22.
Page 71 Figure 23 Changing an RPF route As shown in Figure 23, when no static multicast route is configured, Switch C’s RPF neighbor on the path back to Source is Switch A. The multicast information from Source travels along the path from Switch A to Switch C, which is the unicast route between the two routers.
Page 72: Multicast Forwarding Across Unicast Subnets
multicast route on Switch C and Switch D, specifying Switch B as the RPF neighbor of Switch C and specifying Switch C as the RPF neighbor of Switch D, the receivers can receive multicast data that the multicast source sent. NOTE: Static multicast routes only affect RPF check but cannot guide multicast forwarding.
Page 73: Configuration Task List
First-hop router—The router that directly connects to the multicast source is called the "first-hop • router". Querier—The router that sends multicast traceroute requests is called the "querier". • Introduction to multicast traceroute packets A multicast traceroute packet is a special IGMP packet that is different from common IGMP packets in that its IGMP Type field is set to 0x1F or 0x1E and its destination IP address is a unicast address.
Page 74: Configuring Multicast Routing And Forwarding
Step Command Remarks Enter system view. system-view Enable IP multicast routing. multicast routing-enable Disabled by default 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 are interoperable at the •...
Page 75: Configuring A Multicast Forwarding Range
Step Command Remarks Configure the device to select The route with the highest priority is the RPF route based on the multicast longest-match selected as the RPF route by longest match. default. Configure multicast load Optional. multicast load-splitting { source | splitting.
Page 76: Tracing A Multicast Path
Step Command Remarks Enter system view. system-view Configure the maximum Optional. multicast forwarding-table number of entries in the route-limit limit 2000 by default. multicast forwarding table. Configure the maximum number of downstream nodes Optional. multicast forwarding-table for a single multicast downstream-limit limit 128 by default.
Page 77: Configuration Examples
Task Command Remarks display multicast routing-table [ source-address [ mask { mask | mask-length } ] | group-address [ mask { mask | mask-length } ] | incoming-interface { interface-type Available in any Display information about interface-number | register } | outgoing-interface the multicast routing table.
Page 78 Figure 26 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 Multicast static route Configuration procedure Configure the IP address and subnet mask for each interface as per Figure 26.
Page 79: Creating An Rpf Route
[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. (Details not shown.) # Use the display multicast rpf-info command to display the RPF route to Source on Switch B. [SwitchB] display multicast rpf-info 50.1.1.100 RPF information about source 50.1.1.100: RPF interface: Vlan-interface102, RPF neighbor: 30.1.1.2...
Page 80 Figure 27 Network diagram Configuration procedure Configure the IP address and subnet mask for each interface as per Figure 27. (Details not shown.) Enable OSPF on Switch B and Switch C to make sure they are interoperable at the network layer and they can dynamically update their routing information.
Page 81: Multicast Forwarding Over A Tunnel
No information is displayed. This means that no RPF route to Source 2 exists on Switch B or Switch Configure a static multicast route: # Configure a static multicast route on Switch B, specifying Switch A as its RPF neighbor on the route to Source 2.
Page 82 Figure 28 Network diagram Configuration procedure Configure the IP address and subnet mask for each interface as per Figure 28. (Details not shown.) Configure an IPv4 over IPv4 tunnel: # Create service loopback group 1 on Switch A and specify its service type as Tunnel. <SwitchA>...
Page 83 [SwitchC-GigabitEthernet1/0/3] quit # Create interface Tunnel 0 on Switch C, assign the IP address and subnet mask to the interface Tunnel 0, and reference service loopback group 1 on interface Tunnel 0. [SwitchC] interface tunnel 0 [SwitchC-Tunnel0] ip address 50.1.1.2 24 [SwitchC-Tunnel0] service-loopback-group 1 # Specify the tunnel encapsulation mode as IPv4 over IPv4 and assign the source and destination addresses to the interface.
Page 84 [SwitchA-Tunnel0] pim dm [SwitchA-Tunnel0] quit # Enable multicast routing on Switch C, enable PIM-DM on each interface, and enable IGMP on VLAN-interface 200. [SwitchC] multicast routing-enable [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] igmp enable [SwitchC-Vlan-interface200] pim dm [SwitchC-Vlan-interface200] quit [SwitchC] interface vlan-interface 102 [SwitchC-Vlan-interface102] pim dm [SwitchC-Vlan-interface102] quit [SwitchC] interface tunnel 0...
Page 85: Troubleshooting Multicast Routing And Forwarding
The output shows that Switch A is the RPF neighbor of Switch C and the multicast data from Switch A is delivered over an IPv4 over IPv4 tunnel to Switch C. Troubleshooting multicast routing and forwarding Static multicast route failure Symptom No dynamic routing protocol is enabled on the routers, and the physical status and link layer status of interfaces are both up, but the static multicast route fails.
Page 86 In the case of PIM-SM, use the display current-configuration command to check the BSR and RP information.
Page 87: Configuring Igmp
Configuring IGMP Overview As a TCP/IP protocol responsible for IP multicast group member management, the Internet Group Management Protocol (IGMP) is used by IP hosts and adjacent multicast routers to establish and maintain their multicast group memberships. The term "router" in this document refers to both routers and Layer 3 switches. IGMP versions IGMPv1 (defined in RFC 1 1 12) •...
Page 88 Figure 29 IGMP queries and reports IP network Router A Router B Ethernet Host A Host B Host C (G2) (G1) (G1) Query Report Assume that Host B and Host C are interested in multicast data addressed to multicast group G1, and Host A is interested in multicast data addressed to G2, as shown in Figure 29.
Page 89: Enhancements In Igmpv2
Enhancements in IGMPv2 Compared with IGMPv1, IGMPv2 has introduced a querier election mechanism and a leave-group mechanism. Querier election mechanism In IGMPv1, the DR elected by the Layer 3 multicast routing protocol (such as PIM) serves as the querier among multiple routers on the same subnet. IGMPv2 introduced an independent querier election mechanism.
Page 90 If it needs to reject multicast data from specific sources like S1, S2, …, it sends a report with the • Filter-Mode denoted as "Exclude Sources (S1, S2, …)." As shown in Figure 30, the network comprises two multicast sources, Source 1 (S1) and Source 2 (S2), both of which can send multicast data to multicast group G.
Page 91: Igmp Ssm Mapping
TO_EX—The filtering mode has changed from Include to Exclude. ALLOW—The Source Address fields in this group record contain a list of the additional sources that the system wants to obtain data from, for packets sent to the specified multicast address. If the change was to an Include source list, these sources are the addresses that were added to the list.
Page 92: Igmp Proxying
If G is in the SSM group range but no IGMP SSM mappings that correspond to the multicast group • G have been configured on Router A, Router A cannot provide SSM service and drops the message. If G is in the SSM group range and the IGMP SSM mappings have been configured on Router A for •...
Page 93: Protocols And Standards
mode, and source list. Such an entry is a collection of members in the same multicast group on each downstream interface. A proxy device performs host functions on the upstream interface based on the database. It responds to queries according to the information in the database or sends join/leave messages when the database changes.
Page 94: Configuring Basic Igmp Functions
If a feature is not configured on an interface in interface view, the global configuration in IGMP • view will apply to that interface. If a feature is configured in both IGMP view and interface view, the configuration in interface view will be given priority. Configuring basic IGMP functions Before you configure basic IGMP functions, complete the following tasks: Configure any unicast routing protocol so that all devices in the domain are interoperable at the...
Page 95: Configuring Static Joining
Configuring an IGMP version on an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure an IGMP version igmp version version-number IGMPv2 by default on the interface. Configuring static joining After an interface is configured as a static member of a multicast group or a multicast source group, it will act as a virtual member of the multicast group to receive multicast data addressed to that multicast group for the purpose of testing multicast data forwarding.
Page 96: Setting The Maximum Number Of Multicast Groups That An Interface Can Join
Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, no multicast group filter Configure a multicast group igmp group-policy acl-number is configured on an interface, and filter. [ version-number ] hosts on an interface can join any valid multicast group.
Page 97: Configuring Router-Alert Option Handling Methods
Determine the IGMP last-member query interval. • • Determine the other querier present interval. Determine the DSCP value for IGMP messages. • Configuring Router-Alert option handling methods IGMP queries include group-specific queries and group-and-source-specific queries, and multicast groups change dynamically, so a device cannot maintain the information for all multicast sources and groups.
Page 98: Configuring Igmp Query And Response Parameters
Configuring IGMP query and response parameters On startup, the IGMP querier sends IGMP general queries at the startup query interval, which is one-quarter of the IGMP general query interval. The number of queries, or the startup query count, is user configurable.
Page 99 Step Command Remarks By default, the startup query Configure the startup query startup-query-interval interval interval is 1/4 of the "IGMP interval. general query interval." By default, the startup query count Configure the startup query startup-query-count value is set to the IGMP querier’s count.
Page 100: Configuring Igmp Fast-Leave Processing
Configuring IGMP fast-leave processing IGMP fast-leave processing is implemented by IGMP snooping. For more information, see "Configuring IGMP snooping." Enabling the IGMP host tracking function With the IGMP host tracking function, the switch can record the information of the member hosts that are receiving multicast traffic, including the host IP address, running duration, and timeout time.
Page 101: Configuring Igmp Ssm Mapping
Configuring IGMP SSM mapping Because of some possible restrictions, some receiver hosts on an SSM network might run IGMPv1 or IGMPv2. To provide SSM service support for these receiver hosts, configure the IGMP mapping feature on the last-hop router. Before you configure the IGMP SSM mapping feature, complete the following tasks: Configure any unicast routing protocol so that all devices in the domain are interoperable at the •...
Page 102: Enabling Igmp Proxying
Configure any unicast routing protocol so that all devices in the domain are interoperable at the • network layer. Enable IP multicast routing. • Enabling IGMP proxying You can enable IGMP proxying on the interface in the direction toward the root of the multicast forwarding tree to make the switch serve as an IGMP proxy.
Page 103: Displaying And Maintaining Igmp
Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Enable multicast forwarding on a non-querier downstream igmp proxying forwarding Disabled by default interface. Displaying and maintaining IGMP CAUTION: The reset igmp group command might cause multicast data transmission failures. To display and maintain IGMP: Task Command...
Page 104: Igmp Configuration Examples
Task Command display igmp ssm-mapping group-address [ | { begin | Display IGMP SSM mappings. Available in any view. exclude | include } regular-expression ] display igmp ssm-mapping group Display the multicast group [ group-address | interface information created from IGMPv1 interface-type interface-number ] Available in any view.
Page 105 Figure 33 Network diagram Receiver PIM network Host A Vlan-int101 Vlan-int100 10.110.1.1/24 Switch A Host B Querier Vlan-int200 10.110.2.1/24 Receiver Vlan-int201 Host C Switch B Vlan-int200 10.110.2.2/24 Vlan-int202 Host D Switch C Configuration procedure Configure the IP address and subnet mask of each interface as per Figure 33.
Page 106: Ssm Mapping Configuration Example
# Enable IP multicast routing on Switch C, enable PIM-DM on each interface, and enable IGMP on VLAN-interface 200. <SwitchC> system-view [SwitchC] multicast routing-enable [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] igmp enable [SwitchC-Vlan-interface200] pim dm [SwitchC-Vlan-interface200] quit [SwitchC] interface vlan-interface 202 [SwitchC-Vlan-interface202] pim dm [SwitchC-Vlan-interface202] quit Configure a multicast group filter on Switch A, so that the hosts connected to VLAN-interface 100...
Page 107 Figure 34 Network diagram Device Interface IP address Device Interface IP address Source 1 — 133.133.1.1/24 Source 3 — 133.133.3.1/24 Source 2 — 133.133.2.1/24 Receiver — 133.133.4.1/24 Switch A Vlan-int100 133.133.1.2/24 Switch C Vlan-int300 133.133.3.2/24 Vlan-int101 192.168.1.1/24 Vlan-int103 192.168.3.1/24 Vlan-int104 192.168.4.2/24 Vlan-int102 192.168.2.2/24...
Page 108 <SwitchA> system-view [SwitchA] multicast routing-enable [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] pim sm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim sm [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 104 [SwitchA-Vlan-interface104] pim sm [SwitchA-Vlan-interface104] quit # Enable IP multicast routing and PIM-SM on Switch B and Switch C in the same way. (Details not shown.) Configure C-BSR and C-RP interfaces on Switch D.
Page 109: Igmp Proxying Configuration Example
Group Address Last Reporter Uptime Expires 232.1.1.1 133.133.4.1 00:02:04 # Display PIM routing table information on Switch D. [SwitchD] display pim routing-table Total 0 (*, G) entry; 2 (S, G) entry (133.133.1.1, 232.1.1.1) Protocol: pim-ssm, Flag: UpTime: 00:13:25 Upstream interface: Vlan-interface104 Upstream neighbor: 192.168.4.2 RPF prime neighbor: 192.168.4.2 Downstream interface(s) information:...
Page 110 Figure 35 Network diagram Configuration procedure Configure the IP address and subnet mask of each interface as per Figure 35. (Details not shown.) Enable IP multicast routing, PIM-DM, IGMP, and IGMP proxying: # Enable IP multicast routing on Switch A, PIM-DM on VLAN-interface 101, and IGMP on VLAN-interface 100.
Page 111: Troubleshooting Igmp
Version1-querier-present-timer-expiry: 00:00:20 # Display IGMP group information on Switch A. [SwitchA] display igmp group Total 1 IGMP Group(s). Interface group report information Vlan-interface100(192.168.1.1): Total 1 IGMP Groups reported Group Address Last Reporter Uptime Expires 224.1.1.1 192.168.1.2 00:02:04 00:01:15 The output shows that IGMP reports from the hosts are forwarded to Switch A through the proxy interface, VLAN-interface 100 on Switch B.
Page 112: Inconsistent Memberships On Routers On The Same Subnet
Inconsistent memberships on routers on the same subnet Symptom Different memberships are maintained on different IGMP routers on the same subnet. Analysis A router running IGMP maintains multiple parameters for each interface, and these parameters • influence one another, forming very complicated relationships. Inconsistent IGMP interface parameter configurations for routers on the same subnet will surely result in inconsistency of memberships.
Page 113: Configuring Pim
Configuring PIM 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 routing information protocol (RIP), open shortest path first (OSPF), or border gateway protocol (BGP). Independent of the unicast routing protocols running on the device, multicast routing can be implemented as long as the corresponding multicast routing entries are created through unicast routes.
Page 114 Neighbor discovery In a PIM domain, a PIM router discovers PIM neighbors, maintains PIM neighboring relationships with other routers, and builds and maintains SPTs by periodically multicasting hello messages to all other PIM routers (224.0.0.13) on the local subnet. NOTE: Every PIM-enabled interface on a router sends hello messages periodically, and thus learns the PIM neighboring information pertinent to the interface.
Page 115 The flood-and-prune process takes place periodically. A pruned state timeout mechanism is provided. A pruned branch restarts multicast forwarding when the pruned state times out and then is pruned again when it no longer has any multicast receiver. NOTE: Pruning has a similar implementation in PIM-SM. Graft When a host attached to a pruned node joins a multicast group, to reduce the join latency, PIM-DM uses a graft mechanism to resume data forwarding to that branch.
Page 116: Pim-Sm Overview
If a tie exists in route metric to the source, the router with a higher IP address of the downstream interface wins. PIM-SM overview PIM-DM uses the flood-and-prune principle to build SPTs for multicast data distribution. Although an SPT has the shortest path, it is built with a low efficiency. Therefore, the PIM-DM mode is not suitable for large- and medium-sized networks.
Page 117 A DR must be elected in a multi-access network, no matter this network connects to multicast sources or to receivers. The receiver-side DR sends join messages to the RP. The source-side DR sends register messages to the RP. A DR is elected on a multi-access subnet by means of comparison of the priorities and IP addresses carried in hello messages.
Page 118 NOTE: An RP can serve multiple multicast groups or all multicast groups. Only one RP can serve a given • multicast group at a time. A device can serve as a C-RP and a C-BSR at the same time. • As shown in Figure 39, each C-RP periodically unicasts its advertisement messages (C-RP-Adv messages)
Page 119 Value Description Modulo operator, which gives the remainder of an integer division RPT building Figure 40 RPT building in a PIM-SM domain As shown in Figure 40, the process of building an RPT is as follows: When a receiver joins multicast group G, it uses an IGMP message to inform the directly connected DR.
Page 120 Figure 41 Multicast source registration Host A Source Receiver Host B Server Receiver Join message Register message Host C Multicast packets As shown in Figure 41, the multicast source registers with the RP as follows: The multicast source S sends the first multicast packet to multicast group G. After receiving the multicast packet, the DR that directly connects to the multicast source encapsulates the packet in a PIM register message.
Page 121: Administrative Scoping Overview
The RP can periodically check the passing-by IPv4 multicast packets. If it finds that the traffic rate exceeds a configurable threshold, the RP sends an (S, G) join message hop by hop toward the multicast source to establish an SPT between the DR at the source side and the RP. Subsequent multicast data travels along the established SPT to the RP.
Page 122 cannot cross this boundary in either direction. You can have a better understanding of the global-scoped zone and admin-scoped zones based on geographical locations and multicast group address ranges. In view of geographical locations • An admin-scope zone is a logical zone for particular multicast groups. The multicast packets for such multicast groups are confined within the local admin-scope zone and cannot cross the boundary of the zone.
Page 123: Pim-Ssm Overview
Figure 43, 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. The global-scoped zone serves all the multicast groups that are not covered by the admin-scoped zones 1 and 2, that is, G−G1−G2 in this case. PIM-SSM overview The source-specific multicast (SSM) model and the any-source multicast (ASM) model are opposites.
Page 124: Relationships Among Pim Protocols
Figure 44 SPT building in PIM-SSM As shown in Figure 44, Host B and Host C are multicast information receivers. They send IGMPv3 report messages to the respective DRs to express their interest in the information about the specific multicast source S.
Page 125: Protocols And Standards
Figure 45 Relationships among PIM protocols For more information about IGMP SSM mapping, see "Configuring IGMP." Protocols and standards RFC 3973, Protocol Independent Multicast-Dense Mode (PIM-DM): Protocol Specification(Revised) • RFC 4601, Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification (Revised) • RFC 5059, Bootstrap Router (BSR) Mechanism for Protocol Independent Multicast (PIM) •...
Page 126: Enabling Pim-Dm
Determine the interval between state-refresh messages. • • Determine the minimum time to wait before receiving a new refresh message. Determine the TTL value of state-refresh messages. • Determine the graft retry period. • Enabling PIM-DM With PIM-DM enabled, a router sends hello messages periodically to discover PIM neighbors and processes messages from the PIM neighbors.
Page 127: Configuring Pim-Dm Graft Retry Period
A router might receive multiple state-refresh messages within a short time, and some of them might be duplicated messages. To keep a router from receiving such duplicated messages, you can configure the time that the router must wait before it receives next state-refresh message. If the router receives a new state-refresh message within the waiting time, it discards the message.
Page 128: Configuring Pim-Sm
Configuring PIM-SM PIM-SM configuration task list Task Remarks Enabling PIM-SM Required. Configuring a static RP Required. Configuring a C-RP Use any approach. Configuring an RP Enabling auto-RP Configuring C-RP timers globally Optional. Configuring a C-BSR Required. Configuring a PIM domain border Optional.
Page 129: Enabling Pim-Sm
Determine the BS period. • • Determine the BS timeout. Determine the ACL rule for register message filtering. • Determine the register suppression time. • • Determine the register probe time. Determine the ACL rule and sequencing rule for disabling the switchover to SPT. •...
Page 130 Step Command Remarks Configure a static RP for static-rp rp-address [ acl-number ] No static RP by default PIM-SM. [ preferred ] Configuring a C-RP In a PIM-SM domain, you can configure routers that intend to become the RP as C-RPs. The BSR collects the C-RP information by receiving the C-RP-Adv messages from C-RPs or auto-RP announcements from other routers and organizes the information into an RP-set, which is flooded throughout the entire network.
Page 131: Configuring A Bsr
Each C-RP encapsulates a timeout value in its C-RP-Adv messages. After receiving a C_RP-Adv message, the BSR obtains this timeout value and starts a C-RP timeout timer. If the BSR fails to hear a subsequent C-RP-Adv message from the C-RP when this timer times out, the BSR assumes the C-RP to have expired or become unreachable.
Page 132 When an attacker controls a router in the network or when an illegal router is present in the network, • the attacker can configure this router as a C-BSR and make it win BSR election to control the right of advertising RP information in the network. After a router is configured as a C-BSR, it automatically floods the network with bootstrap messages.
Page 133 Configuring global C-BSR parameters In each PIM-SM domain, a unique BSR is elected from C-BSRs. The C-RPs in the PIM-SM domain send advertisement messages to the BSR. The BSR summarizes the advertisement messages to form an RP-set and advertises it to all routers in the PIM-SM domain. All the routers use the same hash algorithm to get the RP address that corresponds to specific multicast groups.
Page 134 Step Command Remarks Optional. By default, the BS period is determined by the formula "BS period = (BS timeout timer– 10) / 2." The default BS timeout timer is Configure the BS period. c-bsr interval interval 130 seconds, so the default BS period is (130 –...
Page 135: Configuring Administrative Scoping
Step Command Remarks Enter system view. system-view Enter PIM view. Disable the BSM semantic By default, the BSM semantic undo bsm-fragment enable fragmentation function. fragmentation function is enabled. Configuring administrative scoping When administrative scoping is disabled, a PIM-SM domain has only one BSR. The BSR manages the whole network.
Page 136 Configuring C-BSRs for each admin-scope zone and the global-scope zone In a network with administrative scoping enabled, group-range-specific BSRs are elected from C-BSRs. C-RPs in the network send advertisement messages to the specific BSR. The BSR summarizes the advertisement messages to form an RP-set and advertises it to all routers in the specific admin-scope zone. All the routers use the same hash algorithm to get the RP address corresponding to the specific multicast group.
Page 137: Configuring Multicast Source Registration
Configuring multicast source registration Within a PIM-SM domain, the source-side DR sends register messages to the RP, and these register messages have different multicast source or group addresses. You can configure a filtering rule to filter register messages so that the RP can serve specific multicast groups. If the filtering rule denies an (S, G) entry, or if the filtering rule does not define the action for this entry, the RP will send a register-stop message to the DR to stop the registration process for the multicast data.
Page 138: Disabling The Switchover To Spt
Disabling the switchover to SPT CAUTION: If the switch is an RP, disabling switchover to SPT might cause multicast traffic forwarding failures on the source-side DR. When disabling switchover to SPT, be sure you fully understand its impact on your network.
Page 139: Configuring The Ssm Group Range
When deploying a PIM-SSM domain, enable PIM-SM on non-border interfaces of the routers. IMPORTANT: All the interfaces on the same device must operate in the same PIM mode. Step Command Remarks Enter system view. system-view Enable IP multicast routing. multicast routing-enable Disabled by default interface interface-type Enter interface view.
Page 140: Pim Common Feature Configuration Task List
PIM common feature configuration task list Task Remarks Configuring a multicast data filter Optional Configuring a hello message filter Optional Configuring PIM hello options Optional Configuring the prune delay Optional Configuring PIM common timers Optional Configuring join/prune message sizes Optional Setting the DSCP value for PIM messages Optional Configuration prerequisites...
Page 141: Configuring A Hello Message Filter
Generally, a smaller distance from the filter to the multicast source results in a more remarkable filtering effect. This filter works not only on independent multicast data but also on multicast data encapsulated in register messages. To configure a multicast data filter: Step Command Remarks...
Page 142 value takes effect. If you want to enable neighbor tracking, be sure to enable the neighbor tracking feature on all PIM routers on a multi-access subnet. The LAN-delay setting will cause the upstream routers to delay processing received prune messages. The override-interval sets the length of time that a downstream router can wait before sending a prune override message.
Page 143: Configuring The Prune Delay
Step Command Remarks Optional. Configure PIM neighbor pim hello-option holdtime interval timeout time. 105 seconds by default. Optional. Configure the prune message pim hello-option lan-delay interval delay time (LAN-delay). 500 milliseconds by default. Optional. Configure the prune override pim hello-option override-interval interval.
Page 144: Configuring Join/Prune Message Sizes
NOTE: If no special networking requirements are raised, use the default settings. Configuring PIM common timers globally Step Command Remarks Enter system view. system-view Enter PIM view. Optional. Configure the hello interval. timer hello interval 30 seconds by default. Optional. Configure the join/prune timer join-prune interval interval.
Page 145: Setting The Dscp Value For Pim Messages
By controlling the maximum number of (S, G) entries in a join/prune message, you can effectively reduce the number of (S, G) entries sent per unit of time. IMPORTANT: If PIM snooping–enabled switches are deployed in the PIM network, be sure to set a value no greater than the path MTU for the maximum size of each join/prune message on the receiver-side edge PIM devices To configure join/prune message sizes: Step...
Page 146 Task Command Remarks display pim control-message counters [ message-type { probe | register | register-stop } | [ interface interface-type Display the number of PIM control interface-number | message-type Available in any view messages. { assert | bsr | crp | graft | graft-ack | hello | join-prune | state-refresh } ] * ] [ | { begin | exclude | include }...
Page 147: Pim Configuration Examples
PIM configuration examples PIM-DM configuration example Network requirements As shown in Figure 46, receivers receive VOD information through multicast. The receiver groups of different organizations form stub networks, and one or more receiver hosts exist in each stub network. The entire PIM domain is operating in the dense mode.
Page 148 # Enable IP multicast routing on Switch A, enable IGMP on VLAN-interface 100, and enable PIM-DM on each interface. <SwitchA> system-view [SwitchA] multicast routing-enable [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] igmp enable [SwitchA-Vlan-interface100] pim dm [SwitchA-Vlan-interface100] quit [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.
Page 149 entries. Host A sends an IGMP report to Switch A to join the multicast group G, and a (*, G) entry is generated on Switch A. You can use the display pim routing-table command to view the PIM routing table information on each switch. For example: # Display PIM routing table information on Switch A.
Page 150: Pim-Sm Non-Scoped Zone Configuration Example
PIM-SM non-scoped zone configuration example Network requirements As shown in Figure 47, receivers receive VOD information through multicast. The receiver groups of different organizations form stub networks, and one or more receiver hosts exist in each stub network. The entire PIM-SM domain contains only one BSR. Host A and Host C are multicast receivers in two stub networks.
Page 151 Configure OSPF on the switches in the PIM-SM domain to make sure they are interoperable at the network layer. (Details not shown.) Enable IP multicast routing, IGMP and PIM-SM: # Enable IP multicast routing on Switch A, enable IGMP on VLAN-interface 100, and enable PIM-SM on each interface.
Page 152 Vlan100 10.110.1.1 (local) Vlan101 192.168.1.2 Vlan102 192.168.9.2 # Display BSR information and the locally configured C-RP information in effect on Switch A. [SwitchA] display pim bsr-info Elected BSR Address: 192.168.9.2 Priority: 20 Hash mask length: 32 State: Accept Preferred Scope: Not scoped Uptime: 00:40:40 Expires: 00:01:42 # Display BSR information and the locally configured C-RP information in effect on Switch D.
Page 153 Candidate RP: 192.168.9.2(Vlan-interface102) Priority: 192 HoldTime: 150 Advertisement Interval: 60 Next advertisement scheduled at: 00:00:48 # Display RP information on Switch A. [SwitchA] display pim rp-info PIM-SM BSR RP information: Group/MaskLen: 225.1.1.0/24 RP: 192.168.4.2 Priority: 192 HoldTime: 150 Uptime: 00:51:45 Expires: 00:02:22 RP: 192.168.9.2 Priority: 192...
Page 154: Pim-Sm Admin-Scope Zone Configuration Example
Upstream neighbor: 192.168.1.2 RPF prime neighbor: 192.168.1.2 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: pim-sm, UpTime: 00:00:42, Expires: 00:03:06 The information on Switch B and Switch C is similar to that on Switch A. # Display PIM routing table information on Switch D. [SwitchD] display pim routing-table Total 0 (*, G) entry;...
Page 155 Source 2. Source 3 sends multicast information to multicast group 224.1.1.1. Host C is a multicast receiver for this multicast group. VLAN-interface 101 of Switch B acts as a C-BSR and C-RP of admin-scope zone 1, which serves the multicast group range 239.0.0.0/8. VLAN-interface 104 of Switch D acts as a C-BSR and C-RP of admin-scope zone 2, which also serves the multicast group range 239.0.0.0/8.
Page 156 Vlan-int110 10.110.10.2/24 Configuration procedure Configure the IP address and subnet mask for each interface as per Figure 48. (Details not shown.) Configure OSPF on the switches in the PIM-SM domain to make sure they are interoperable at the network layer. (Details not shown.) Enable IP multicast routing and administrative scoping, and enable IGMP and PIM-SM: # Enable IP multicast routing and administrative scoping on Switch A, enable IGMP on VLAN-interface 100, and enable PIM-SM on each interface.
Page 157 # On Switch B, configure VLAN-interface 102 and VLAN-interface 103 to be the boundary of admin-scope zone 1. [SwitchB] interface vlan-interface 102 [SwitchB-Vlan-interface102] multicast boundary 239.0.0.0 8 [SwitchB-Vlan-interface102] quit [SwitchB] interface vlan-interface 103 [SwitchB-Vlan-interface103] multicast boundary 239.0.0.0 8 [SwitchB-Vlan-interface103] quit # On Switch C, configure VLAN-interface 103 and VLAN-interface 106 to be the boundary of admin-scope zone 2.
Page 158 [SwitchF-pim] c-bsr vlan-interface 109 [SwitchF-pim] c-rp vlan-interface 109 [SwitchF-pim] quit Verifying the configuration # Display BSR information and the locally configured C-RP information on Switch B. [SwitchB] display pim bsr-info Elected BSR Address: 10.110.9.1 Priority: 64 Hash mask length: 30 State: Accept Preferred Scope: Global Uptime: 00:01:45...
Page 159 Candidate BSR Address: 10.110.4.2 Priority: 64 Hash mask length: 30 State: Elected Scope: 239.0.0.0/8 Candidate RP: 10.110.4.2(Vlan-interface104) Priority: 192 HoldTime: 150 Advertisement Interval: 60 Next advertisement scheduled at: 00:00:10 # Display BSR information and the locally configured C-RP information on Switch F. [SwitchF] display pim bsr-info Elected BSR Address: 10.110.9.1 Priority: 64...
Page 160: Pim-Ssm Configuration Example
# Display RP information on Switch D. [SwitchD] display pim rp-info PIM-SM BSR RP information: Group/MaskLen: 224.0.0.0/4 RP: 10.110.9.1 Priority: 192 HoldTime: 150 Uptime: 00:03:42 Expires: 00:01:48 Group/MaskLen: 239.0.0.0/8 RP: 10.110.4.2 (local) Priority: 192 HoldTime: 150 Uptime: 00:06:54 Expires: 00:02:41 # Display RP information on Switch F.
Page 161 Figure 49 Network diagram Device Interface IP address Device Interface IP address Switch A Vlan-int100 10.110.1.1/24 Switch D Vlan-int300 10.110.5.1/24 Vlan-int101 192.168.1.1/24 Vlan-int101 192.168.1.2/24 Vlan-int102 192.168.9.1/24 Vlan-int105 192.168.4.2/24 Switch B Vlan-int200 10.110.2.1/24 Switch E Vlan-int104 192.168.3.2/24 Vlan-int103 192.168.2.1/24 Vlan-int103 192.168.2.2/24 Switch C Vlan-int200 10.110.2.2/24...
Page 162 [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] pim sm [SwitchA-Vlan-interface102] quit # Enable IP multicast routing, IGMP and PIM-SM on Switch B and Switch C in the same way. (Details not shown.) # Enable IP multicast routing and PIM-SM on Switch D and Switch E in the same way. (Details not shown.) Configure the SSM group range: # Configure the SSM group range to be 232.1.1.0/24 on Switch A.
Page 163: Troubleshooting Pim
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 1: Vlan-interface105 Protocol: pim-ssm, UpTime: 00:12:05, Expires: 00:03:25 Troubleshooting PIM A multicast distribution tree cannot be built correctly Symptom...
Page 164: Multicast Data Abnormally Terminated On An Intermediate Router
Solution Use the display ip routing-table command to verify that a unicast route exists from the receiver host to the multicast source. Use the display pim interface command to verify that PIM is enabled on the interfaces, especially on the RPF interface. If PIM is not enabled on the interface, use the pim dm or pim sm command to enable PIM-DM or PIM-SM.
Page 165: Rpt Establishment Failure Or Source Registration Failure In Pim-Sm
Analysis As the core of a PIM-SM domain, the RPs serve specific multicast groups. Multiple RPs can coexist • in a network. Make sure that the RP information on all routers is exactly the same and that a specific group is mapped to the same RP. Otherwise, multicast forwarding will fail. •...
Page 166: Configuring Msdp
Configuring MSDP Overview Multicast source discovery protocol (MSDP) is an inter-domain multicast solution that addresses the interconnection of protocol independent multicast sparse mode (PIM-SM) domains. You can use it to discover 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 about a domain is isolated from that of another domain.
Page 167 Figure 50 Where MSDP peers are in the network As shown in Figure 50, 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 on RPs include the following types: Source-side MSDP peer—The MSDP peer nearest to the multicast source (Source), typically the source-side RP, like RP 1.
Page 168 Figure 51 Inter-domain multicast delivery through MSDP The process of implementing PIM-SM inter-domain multicast delivery by leveraging MSDP peers is as follows: When the multicast source in PIM-SM 1 sends the first multicast packet to multicast group G, DR 1 encapsulates the multicast data within a register message and sends the register message to RP 1.
Page 169 If no receivers for the group exist in the domain, RP 2 neither creates an (S, G) entry nor joins the SPT rooted at the source. NOTE: When using MSDP for inter-domain multicasting, once an RP receives information form a multicast source, it no longer relies on RPs in other PIM-SM domains.
Page 170 Because the SA message is from an MSDP peer (RP 3) in the same mesh group, RP 4 and RP 5 both accept the SA message, but they do not forward the message to other members in the mesh group. Instead, they forward it to other MSDP peers (RP 6 in this example) out of the mesh group.
Page 171: Protocols And Standards
Figure 53 Intra-domain Anycast RP through MSDP The work process of Anycast RP is as follows: The multicast source registers with the nearest RP. In this example, Source registers with RP 1, with its multicast data encapsulated in the register message. When the register message arrives at RP 1, RP 1 de-encapsulates the message.
Page 172: Msdp Configuration Task List
MSDP configuration task list Task Remarks Enabling MSDP Required Configuring basic MSDP Creating an MSDP peer connection Required functions Configuring a static RPF peer Optional Configuring MSDP peer description Optional Configuring an MSDP peer Configuring an MSDP mesh group Optional connection Configuring MSDP peer connection control Optional...
Page 173: Creating An Msdp Peer Connection
Creating an MSDP peer connection An MSDP peering relationship is identified by an address pair, namely, the address of the local MSDP peer and that of the remote MSDP peer. An MSDP peer connection must be created on both devices that are a pair of MSDP peers.
Page 174: Configuring Msdp Peer Description
Configuring MSDP peer description With the MSDP peer description information, the administrator can easily distinguish different MSDP peers to better manage MSDP peers. To configure description for an MSDP peer: Step Command Remarks Enter system view. system-view Enter MSDP view. msdp Configure description for an No description is configured for an...
Page 175: Configuring Sa Messages Related Parameters
them, and the TCP connection is closed without any connection setup retry. The configuration information, however, remain unchanged. A TCP connection is required in the following situations: When a new MSDP peer is created • When you reactivate a previously deactivated MSDP peer connection •...
Page 176: Configuring Sa Message Content
Configuring SA message content Some multicast sources send multicast data at an interval longer than the aging time of (S, G) entries. In this case, the source-side DR must encapsulate multicast data packet by packet in register messages and send them to the source-side RP. The source-side RP transmits the (S, G) information to the remote RP through SA messages.
Page 177: Configuring Sa Message Filtering Rules
Step Command Remarks Optional. Enable the device to send SA peer peer-address request messages. request-sa-enable Disabled by default. Optional. peer peer-address Configure a filtering rule for SA sa-request-policy [ acl SA request messages are not request messages. acl-number ] filtered by default. Configuring SA message filtering rules By configuring an SA message creation rule, you can enable the router to filter the (S, G) entries to be advertised when creating an SA message, so that the propagation of messages of multicast sources is...
Page 178: Configuring The Sa Cache Mechanism
Configuring the SA cache mechanism To reduce the time spent in obtaining the multicast information, you can enable the SA cache mechanism to cache (S, G) entries contained in SA messages locally on the router. However, caching (S, G) entries uses memory space on the router.
Page 179: Msdp Configuration Examples
Step Command Remarks Clear (S, G) entries in the SA reset msdp sa-cache Available in user view cache. [ group-address ] Clear statistics for an MSDP reset msdp statistics Available in user view peer. [ peer-address ] MSDP configuration examples PIM-SM Inter-domain multicast configuration Network requirements As shown in...
Page 180 Loop0 1.1.1.1/32 Switch F Vlan-int105 10.110.6.2/24 Switch C Vlan-int104 10.110.4.1/24 Vlan-int400 10.110.7.1/24 Vlan-int102 192.168.3.1/24 Source 1 — 10.110.2.100/24 Vlan-int101 192.168.1.2/24 Source 2 — 10.110.5.100/24 Loop0 2.2.2.2/32 Configuration procedure Configure the IP address and subnet mask for each interface as per Figure 54.
Page 181 [SwitchB-bgp] peer 192.168.1.2 as-number 200 [SwitchB-bgp] import-route ospf 1 [SwitchB-bgp] quit # Configure an EBGP peer, and redistribute OSPF routes on Switch C. [SwitchC] bgp 200 [SwitchC-bgp] router-id 2.2.2.2 [SwitchC-bgp] peer 192.168.1.1 as-number 100 [SwitchC-bgp] import-route ospf 1 [SwitchC-bgp] quit # Redistribute BGP routes into OSPF on Switch B.
Page 182 [SwitchC] display bgp peer BGP local router ID : 2.2.2.2 Local AS number : 200 Total number of peers : 1 Peers in established state : 1 Peer MsgRcvd MsgSent OutQ PrefRcv Up/Down State 192.168.1.1 1 00:12:04 Established To display BGP routing table information on the switches, use the display bgp routing-table command. For example: # Display BGP routing table information on Switch C.
Page 183: Inter-As Multicast Configuration By Leveraging Static Rpf Peers
192.168.3.2 00:15:32 192.168.1.1 00:06:39 # Display brief information about MSDP peering relationship on Switch E. [SwitchE] display msdp brief MSDP Peer Brief Information Configured Listen Connect Shutdown Down Peer's Address State Up/Down time SA Count Reset Count 192.168.3.1 01:07:08 # Display detailed MSDP peer information on Switch B. [SwitchB] display msdp peer-status MSDP Peer Information MSDP Peer 192.168.1.2, AS 200...
Page 184 According to the RPF principle, the device can receive 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 relationship for the RPs of the PIM-SM domains and configure static RPF peering relationship for the MSDP peers to share multicast source information among the PIM-SM domains.
Page 185 [SwitchC] multicast routing-enable [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] pim sm [SwitchC-Vlan-interface200] quit [SwitchC] interface vlan-interface 104 [SwitchC-Vlan-interface104] pim sm [SwitchC-Vlan-interface104] quit # Enable IP multicast routing, PIM-SM and IGMP on Switch A, Switch B, Switch D, Switch E, Switch F, and Switch G in the same way.
Page 186 # Configure the EBGP peer, and redistribute OSPF routing information on Switch F. [SwitchF] bgp 200 [SwitchF-bgp] router-id 3.3.3.1 [SwitchF-bgp] peer 10.110.4.1 as-number 100 [SwitchF-bgp] import-route ospf 1 [SwitchF-bgp] quit # Redistribute BGP routing information into OSPF on Switch B. [SwitchB] ospf 1 [SwitchB-ospf-1] import-route bgp [SwitchB-ospf-1] quit...
Page 187: Anycast Rp Configuration
Verifying the configuration Use the display bgp peer command to display the BGP peering relationship between the switches. If the command gives no output information on Switch A, it means that no BGP peering relationship has been established between Switch A and Switch D, or between Switch A and Switch G. When the multicast source in PIM-SM 1 (Source 1) and the multicast source in PIM-SM 2 (Source 2) send multicast information, receivers in PIM-SM 1 and PIM-SM 3 can receive the multicast data.
Page 188 Figure 56 Network diagram Device Interface IP address Device Interface IP address Source 1 — 10.110.5.100/24 Switch C Vlan-int101 192.168.1.2/24 Source 2 — 10.110.6.100/24 Vlan-int102 192.168.2.2/24 Switch A Vlan-int300 10.110.5.1/24 Switch D Vlan-int200 10.110.3.1/24 Vlan-int103 10.110.2.2/24 Vlan-int104 10.110.4.1/24 Switch B Vlan-int100 10.110.1.1/24 Vlan-int102...
Page 189 [SwitchB] interface Vlan-interface 101 [SwitchB-Vlan-interface101] pim sm [SwitchB-Vlan-interface101] quit [SwitchB] interface loopback 0 [SwitchB-LoopBack0] pim sm [SwitchB-LoopBack0] quit [SwitchB] interface loopback 10 [SwitchB-LoopBack10] pim sm [SwitchB-LoopBack10] quit [SwitchB] interface loopback 20 [SwitchB-LoopBack20] pim sm [SwitchB-LoopBack20] quit # Enable IP multicast routing, IGMP and PIM-SM on Switch A, Switch C, Switch D, and Switch E in the same way.
Page 190 MSDP Peer Brief Information Configured Listen Connect Shutdown Down Peer's Address State Up/Down time SA Count Reset Count 1.1.1.1 00:10:18 To display the PIM routing information on the switches, use the display pim routing-table command. When Source 1 10.1 10.5.100/24 sends multicast data to multicast group G 225.1.1.1, Host A joins multicast group G.
Page 191: Sa Message Filtering Configuration
No information is output on Switch B. # Display PIM routing information on Switch D. [SwitchD] display pim routing-table Total 1 (*, G) entry; 1 (S, G) entry (*, 225.1.1.1) RP: 10.1.1.1 (local) Protocol: pim-sm, Flag: WC UpTime: 00:12:07 Upstream interface: Register Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information:...
Page 192 Figure 57 Network diagram PIM-SM 1 PIM-SM 2 PIM-SM 3 Loop0 Source 2 Vlan-int100 Switch A Loop0 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 Device Interface...
Page 193 [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. (Details not shown.) # Configure a PIM domain border on Switch C. [SwitchC] interface vlan-interface 101 [SwitchC-Vlan-interface101] pim bsr-boundary [SwitchC-Vlan-interface101] quit...
Page 194 [SwitchC-acl-adv-3001] quit [SwitchC] msdp [SwitchC-msdp] peer 10.110.5.2 sa-policy export acl 3001 [SwitchC-msdp] quit # Configure an SA message rule on Switch D so that Switch D will not create SA messages for Source 2. [SwitchD] acl number 2001 [SwitchD-acl-basic-2001] rule deny source 10.110.6.100 0 [SwitchD-acl-basic-2001] quit [SwitchD] msdp [SwitchD-msdp] import-source acl 2001...
Page 195: Troubleshooting Msdp
Troubleshooting MSDP MSDP peers stay in down state Symptom The configured MSDP peers stay in the down state. Analysis • A TCP connection–based MSDP peering relationship is established between the local interface address and the MSDP peer after the configuration. The TCP connection setup will fail if the local interface address is not consistent with the MSDP peer •...
Page 196: Inter-Rp Communication Faults In Anycast Rp Application
Inter-RP communication faults in Anycast RP application Symptom RPs fail to exchange their locally registered (S, G) entries with one another in the Anycast RP application. Analysis In the Anycast RP application, RPs in the same PIM-SM domain are configured to be MSDP peers to •...
Page 197: Configuring Mbgp
Configuring MBGP This chapter covers configuration tasks related to multiprotocol BGP for IP multicast only. For more information about BGP, see Layer 3—IP Routing Configuration Guide. The term "router" in this chapter refers to both routers and Layer 3 switches. MBGP overview BGP-4 can carry routing information for IPv4 only.
Page 198: Configuring Basic Mbgp Functions
Task Remarks Configuring MBGP route preferences Configuring the default local preference Configuring MBGP Configuring the MED attribute Optional route attributes Configuring the NEXT_HOP attribute Configuring the AS_PATH attributes Configuring MBGP soft reset Optional Tuning and Enabling the MBGP ORF capability Optional optimizing MBGP networks...
Page 199: Configuring Default Route Redistribution Into Mbgp
Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter IPv4 MBGP address ipv4-family multicast family view. Use either command No route redistribution is Enable route redistribution from configured by default. another routing protocol: The allow-direct keyword is import-route protocol [ { process-id available only when the specified | all-processes } [ allow-direct |...
Page 200: Configuring Mbgp Route Summarization
Configuring MBGP route summarization To reduce the routing table size on medium and large MBGP networks, you need to configure route summarization on peers. MBGP supports automatic and manual summarization modes: Automatic summarization—Summarizes subnets redistributed from IGP. With the feature •...
Page 201: Configuring Outbound Mbgp Route Filtering
NOTE: With the peer default-route-advertise command executed, the router sends a default route with the next hop as itself to the specified MBGP peer or peer group, whether the default route is available or not in the routing table. Configuring outbound MBGP route filtering If several filtering policies are configured, they are applied in the following sequence: filter-policy export peer filter-policy export...
Page 202: Configuring Inbound Mbgp Route Filtering
Configuring inbound MBGP route filtering By configuring MBGP route reception filtering policies, you can filter out unqualified routes from an MBGP peer or peer group. Members of a peer group can have different route reception filtering policies from the peer group. If several filtering policies are configured, they are applied in the following sequence: filter-policy import peer filter-policy import...
Page 203: Configuring Mbgp Route Dampening
Step Command Remarks • Filter incoming routes using an ACL or IP prefix list: filter-policy { acl-number | ip-prefix ip-prefix-name } import • Reference a routing policy to routes from an IPv4 MBGP peer or a peer group: peer { group-name | ip-address } route-policy policy-name import •...
Page 204: Configuring Mbgp Route Attributes
Step Command Remarks dampening [ half-life-reachable Configure BGP route half-life-unreachable reuse Not configured by default. dampening parameters. suppress ceiling | route-policy route-policy-name ] * Configuring MBGP route attributes You can modify MBGP route attributes to affect route selection. Before you configure this task, configure basic MBGP functions first. Configuring MBGP route preferences You can reference a routing policy to set preferences for routes matching it.
Page 205: Configuring The Next_Hop Attribute
Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter IPv4 MBGP address ipv4-family multicast family view. Optional. Configure the default MED default med med-value value. 0 by default. Enable the comparison of the Optional. MED of routes from different compare-different-as-med Not enabled by default.
Page 206: Tuning And Optimizing Mbgp Networks
Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter IPv4 MBGP address ipv4-family multicast family view. Allow the local AS number to appear in the AS_PATH of Optional. routes from a peer or a peer group and specify the number peer { group-name | ip-address } By default, the local AS number of times that the local AS...
Page 207: Enabling The Mbgp Orf Capability
Step Command Remarks Optional. Enable BGP route refresh for a peer { group-name | ip-address } peer or a peer group. capability-advertise route-refresh Enabled by default. Performing soft reset manually If the peer does not support route refresh, you can use the peer keep-all-routes command to save all the route updates from the peer, and then use the refresh bgp ipv4 multicast command to soft-reset MBGP connections to refresh the MBGP routing table and apply the new policy without terminating MBGP connections.
Page 208: Configuring The Maximum Number Of Mbgp Routes For Load Balancing
Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Optional. Enabled by default. If this feature is not enabled, you Enable BGP route refresh for a peer { group-name | ip-address } need to configure this peer or a peer group. capability-advertise route-refresh command.
Page 209: Configuring A Large Scale Mbgp Network
Step Command Remarks Enter IPv4 MBGP address ipv4-family multicast family view. Configure the maximum number of MBGP routes for balance number Not configured by default. load balancing. Configuring a large scale MBGP network Before you configure this task, you must make peering nodes accessible to each other at the network layer.
Page 210: Configuring An Mbgp Route Reflector
When you configure MBGP community, you must reference a routing policy to define the specific COMMUNITY attributes, and apply the routing policy for route advertisement. For routing policy configuration, see Layer 3—IP Routing Configuration Guide. To configure MBGP community: Step Command Remarks Enter system view.
Page 211: Displaying And Maintaining Mbgp
Step Command Remarks Configure the router as a route reflector and specify an peer { group-name | peer-address } Not configured by default. MBGP peer or a peer group reflect-client as its client. Optional. Enable route reflection reflect between-clients between clients. Enabled by default.
Page 212: Resetting Mbgp Connections
Task Command Remarks display bgp multicast routing-table Display MBGP routing community[ aa:nn&<1-13> ] [ no-advertise | no-export Available in any information matching the | no-export-subconfed ] * [ whole-match ] [ | { begin | view specified BGP community. exclude | include } regular-expression ] display bgp multicast routing-table community-list Display MBGP routing { { basic-community-list-number | comm-list-name }...
Page 213: Mbgp Configuration Example
MBGP configuration example Network requirements As shown in the following figure: PIM-SM 1 is in AS 100, and PIM-SM 2 is in AS 200. OSPF is the IGP in the two ASs, and MBGP • runs between the two ASs to exchange multicast route information. The multicast source belongs to PIM-SM 1, and the receiver belongs to PIM-SM 2.
Page 214 [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] pim sm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim sm [SwitchA-Vlan-interface101] quit The configuration on Switch B and Switch D is similar to the configuration on Switch A. # Enable IP multicast routing on Switch C, enable PIM-SM on each interface, and enable IGMP on the host-side interface VLAN-interface 200.
Page 215 [SwitchB-pim] quit Configure BGP, specify the MBGP peer and enable direct route redistribution: # On Switch A, configure the MBGP peer and enable direct route redistribution. [SwitchA] bgp 100 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] peer 192.168.1.2 as-number 200 [SwitchA-bgp] import-route direct [SwitchA-bgp] ipv4-family multicast [SwitchA-bgp-af-mul] peer 192.168.1.2 enable [SwitchA-bgp-af-mul] import-route direct...
Page 216 MSDP Peer Brief Information of VPN-Instance: public net Configured Listen Connect Shutdown Down Peer's Address State Up/Down time SA Count Reset Count 192.168.1.1 00:07:17...
Page 217: Configuring Mld Snooping
Configuring MLD snooping Overview Multicast Listener Discovery (MLD) snooping is an IPv6 multicast constraining mechanism that runs on Layer 2 devices to manage and control IPv6 multicast groups. By analyzing received MLD messages, a Layer 2 device that runs MLD snooping establishes mappings between ports and multicast MAC addresses and forwards IPv6 multicast data based on these mappings.
Page 218 Figure 60 MLD snooping related ports Ports involved in MLD snooping, as shown in Figure 60, are described as follows: • Router port—Layer 3 multicast device-side port. Layer 3 multicast devices include designated routers (DRs) and MLD querier. In the figure, GigabitEthernet 1/0/1 of Switch A and GigabitEthernet 1/0/1 of Switch B are router ports.
Page 219: How Mld Snooping Works
NOTE: In MLD snooping, only dynamic ports age out. Static ports never age out. How MLD snooping works In this section, the involved ports are dynamic ports. For information about how to configure and remove static ports, see "Configuring static ports."...
Page 220: Mld Snooping Proxying
checks whether a forwarding entry matches the IPv6 multicast group address in the message, and, if a match is found, whether the forwarding entry contains the dynamic member port. If no forwarding entry matches the IPv6 multicast group address, or if the forwarding entry does not •...
Page 221 Figure 61 Network diagram As shown in Figure 61, Switch A works as an MLD snooping proxy. As a host from the perspective of the querier Router A, Switch A represents its attached hosts to send their membership reports and done messages to Router A.
Page 222: Protocols And Standards
Protocols and standards RFC 4541, Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping Switches MLD snooping configuration task list Task Remarks Enabling MLD snooping Required Configuring basic MLD Specifying the version of MLD snooping Optional snooping functions Configuring IPv6 static multicast MAC address entries Optional...
Page 223: Configuring Basic Mld Snooping Functions
view is effective only if you do not make the same configuration in Layer 2 Ethernet interface view or Layer 2 aggregate interface view. For MLD snooping, the configurations that you make on a Layer 2 aggregate interface do not •...
Page 224: Configuring Ipv6 Static Multicast Mac Address Entries
For more information about static joining, see "Configuring static ports." Configuration procedure To specify the version of MLD snooping: Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Specify the version of MLD mld-snooping version Version 1 by default snooping.
Page 225: Configuring Aging Timers For Dynamic Ports
Enable MLD snooping in the VLAN. • • Determine the aging time of dynamic router ports. Determine the aging time of dynamic member ports. • Determine the IPv6 multicast group and IPv6 multicast source addresses. • Configuring aging timers for dynamic ports If a switch receives no MLD general queries or IPv6 PIM hello messages on a dynamic router port when the aging timer of the port expires, the switch removes the port from the router port list.
Page 226: Configuring A Port As A Simulated Member Host
A static member port does not respond to queries from the MLD querier; when you configure a port as a static member port or cancel this configuration on the port, the port does not send an unsolicited MLD report or an MLD done message. Static member ports and static router ports never age out.
Page 227: Enabling Fast-Leave Processing
NOTE: Unlike a static member port, a port that you configure as a simulated member host ages out like a dynamic member port. Enabling fast-leave processing The fast-leave processing feature enables the switch to process MLD done messages quickly. After the fast-leave processing feature is enabled, when the switch receives an MLD done message on a port, it immediately removes that port from the forwarding entry for the multicast group specified in the message.
Page 228: Configuring Mld Snooping Querier
To solve these problems, disable that router port from becoming a dynamic router port after the port receives an MLD general query or IPv6 PIM hello message, so as to improve network security and control over multicast users. To disable a port from becoming a dynamic router port: Step Command Remarks...
Page 229: Configuring Parameters For Mld Queries And Responses
Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Enable the MLD snooping mld-snooping querier Disabled by default querier. Configuring parameters for MLD queries and responses CAUTION: In the configuration, make sure that the interval for sending MLD general queries is greater than the maximum response delay for MLD general queries.
Page 230: Configuring The Source Ipv6 Addresses For Mld Queries
Step Command Remarks Set the maximum response mld-snooping max-response-time delay for MLD general 10 seconds by default interval queries. Set the MLD last-member mld-snooping 1 second by default query interval. last-listener-query-interval interval Configuring the source IPv6 addresses for MLD queries Step Command Remarks...
Page 231: Configuring The Source Ipv6 Addresses For The Mld Messages Sent By The Proxy
Configuring the source IPv6 addresses for the MLD messages sent by the proxy You can set the source IPv6 addresses for the MLD reports and done messages that the MLD snooping proxy sends on behalf of its attached hosts. To configure the source IPv6 addresses for the MLD messages that the MLD snooping proxy sends in a VLAN: Step Command...
Page 232: Configuring Ipv6 Multicast Source Port Filtering
Configuring an IPv6 multicast group globally Step Command Remarks Enter system view. system-view Enter MLD-snooping view. mld-snooping By default, no IPv6 group filter is Configure an IPv6 multicast group-policy acl6-number [ vlan globally configured. That is, the group filter. vlan-list ] hosts in a VLAN can join any valid multicast group.
Page 233: Enabling Dropping Unknown Ipv6 Multicast Data
Step Command Remarks Enable IPv6 multicast source mld-snooping source-deny Disabled by default. port filtering. NOTE: Some models of devices, when enabled to filter IPv6 multicast data based on the source ports, are automatically enabled to filter IPv4 multicast data based on the source ports. Enabling dropping unknown IPv6 multicast data Unknown IPv6 multicast data refers to IPv6 multicast data for which no entries exist in the MLD snooping forwarding table.
Page 234: Setting The Maximum Number Of Multicast Groups That A Port Can Join
With the MLD report suppression function enabled, within a query interval, the Layer 2 switch forwards only the first MLD report for the IPv6 multicast group to the Layer 3 device. It does not forward subsequent MLD reports for the same IPv6 multicast group to the Layer 3 device. This helps reduce the number of packets being transmitted over the network.
Page 235: Setting The 802.1P Precedence For Mld Messages
To realize such requirements, you can enable the IPv6 multicast group replacement function on the switch or on a certain port. When the number of IPv6 multicast groups that the switch or the port has joined reaches the limit, one of the following occurs: •...
Page 236: Enabling The Mld Snooping Host Tracking Function
Setting the 802.1p precedence for MLD messages in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Set the 802.1p precedence mld-snooping dot1p-priority The default 802.1p precedence for for MLD messages. priority-number MLD messages is 0. Enabling the MLD snooping host tracking function With the MLD snooping host tracking function, the switch can record the information of the member hosts that are receiving IPv6 multicast traffic, including the host IPv6 address, running duration, and timeout...
Page 237: Displaying And Maintaining Mld Snooping
Step Command Remarks Set the DSCP value for MLD By default, the DSCP value in MLD dscp dscp-value messages. messages is 48. Displaying and maintaining MLD snooping Task Command Remarks display mld-snooping group [ vlan Display MLD snooping group vlan-id ] [ slot slot-number ] Available in any view.
Page 238 IPv6 multicast data for group FF1E::101 can be forwarded through GigabitEthernet 1/0/3 and GigabitEthernet 1/0/4 of Switch A even if Host A and Host B accidentally, temporarily stop receiving IPv6 multicast data, and that Switch A drops unknown IPv6 multicast data and does not broadcast the data to the VLAN where Switch A resides.
Page 239 [SwitchA-vlan100] mld-snooping drop-unknown [SwitchA-vlan100] quit # Configure an IPv6 multicast group filter so that the hosts in VLAN 100 can join only the IPv6 multicast group FF1E::101. [SwitchA] acl ipv6 number 2001 [SwitchA-acl6-basic-2001] rule permit source ff1e::101 128 [SwitchA-acl6-basic-2001] quit [SwitchA] mld-snooping [SwitchA–mld-snooping] group-policy 2001 vlan 100 [SwitchA–mld-snooping] quit...
Page 240: Static Port Configuration Example
Static port configuration example Network requirements As shown in Figure 63, MLDv1 runs on Router A, and MLDv1 snooping runs on Switch A, Switch B and Switch C. Router A acts as the MLD querier. Host A and Host C are permanent receivers of IPv6 multicast group FF1E::101. GigabitEthernet 1/0/3 and GigabitEthernet 1/0/5 on Switch C are required to be configured as static member ports for multicast group FF1E::101 to enhance the reliability of multicast traffic transmission.
Page 241 On Router A, enable IPv6 multicast routing, enable IPv6 PIM-DM on each interface, and enable MLD on GigabitEthernet 1/0/1. <RouterA> system-view [RouterA] multicast ipv6 routing-enable [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] mld enable [RouterA-GigabitEthernet1/0/1] pim ipv6 dm [RouterA-GigabitEthernet1/0/1] quit [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] pim ipv6 dm [RouterA-GigabitEthernet1/0/2] quit Configure Switch A:...
Page 242 [SwitchC-vlan100] mld-snooping enable [SwitchC-vlan100] quit # Configure GigabitEthernet 1/0/3 and GigabitEthernet 1/0/5 as static member ports for IPv6 multicast group FF1E::101. [SwitchC] interface GigabitEthernet 1/0/3 [SwitchC-GigabitEthernet1/0/3] mld-snooping static-group ff1e::101 vlan 100 [SwitchC-GigabitEthernet1/0/3] quit [SwitchC] interface GigabitEthernet 1/0/5 [SwitchC-GigabitEthernet1/0/5] mld-snooping static-group ff1e::101 vlan 100 [SwitchC-GigabitEthernet1/0/5] quit Verifying the configuration # Display detailed MLD snooping group information in VLAN 100 on Switch A.
Page 243: Mld Snooping Querier Configuration Example
Total 1 IP Source(s). Total 1 MAC Group(s). Router port(s):total 1 port(s). GE1/0/2 (D) ( 00:01:23 ) IP group(s):the following ip group(s) match to one mac group. IP group address:FF1E::101 (::, FF1E::101): Attribute: Host Port Host port(s):total 2 port(s). GE1/0/3 GE1/0/5 MAC group(s): MAC group address:3333-0000-0101...
Page 244 Figure 64 Network diagram Configuration procedure Configure Switch A: # Enable IPv6 forwarding and enable MLD snooping globally. <SwitchA> system-view [SwitchA] ipv6 [SwitchA] mld-snooping [SwitchA-mld-snooping] quit # Create VLAN 100 and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3 to VLAN 100. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/3 # Enable MLD snooping and the function of dropping unknown IPv6 multicast data packets in...
Page 245: Mld Snooping Proxying Configuration Example
# Enable the MLD snooping feature and the function of dropping unknown IPv6 multicast data packets in VLAN 100. [SwitchB-vlan100] mld-snooping enable [SwitchB-vlan100] mld-snooping drop-unknown [SwitchB-vlan100] quit Configure Switch C and Switch D in the same way as you configure Switch B. Verifying the configuration When the MLD snooping querier starts to work, all the switches but the querier receive MLD general queries.
Page 246 Figure 65 Network diagram Configuration procedure Configure an IP address and prefix length for each interface as per Figure 65. (Details not shown.) On Router A, enable IPv6 multicast routing, enable IPv6 PIM-DM on each interface, and enable MLD on port GigabitEthernet 1/0/1. <RouterA>...
Page 247 GigabitEthernet 1/0/1 (a router port) to Router A. Use the display mld-snooping group command and the display mld group command to display information about MLD snooping groups and MLD multicast groups. For example: # Display information about MLD snooping groups on Switch A. [SwitchA] display mld-snooping group Total 1 IP Group(s).
Page 248: Troubleshooting Mld Snooping
Total 1 MAC Group(s). Port flags: D-Dynamic port, S-Static port, C-Copy port, P-PIM port Subvlan flags: R-Real VLAN, C-Copy VLAN Vlan(id):100. Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s). Router port(s):total 1 port(s). GE1/0/1 IP group(s):the following ip group(s) match to one mac group. IP group address:FF1E::101 (::, FF1E::101): Host port(s):total 1 port(s).
Page 249: Appendix
Solution Use the display acl ipv6 command to check the configured IPv6 ACL rule. Make sure that the IPv6 ACL rule conforms to the IPv6 multicast group policy to be implemented. Use the display this command in MLD-snooping view or the corresponding interface view to verify that the correct IPv6 multicast group policy has been applied.
Page 250: Configuring Ipv6 Multicast Vlans
Configuring IPv6 multicast VLANs Overview As shown in Figure 66, in the traditional IPv6 multicast programs-on-demand mode, when hosts (Host A, Host B, and Host C), which belong to different VLANs, require IPv6 multicast programs on demand service, the Layer 3 device, Router A, must forward a separate copy of the multicast traffic in each user VLAN to the Layer 2 device, Switch A.
Page 251 Figure 67 Sub-VLAN-based IPv6 multicast VLAN After the configuration, MLD snooping manages router ports in the IPv6 multicast VLAN and member ports in the sub-VLANs. When forwarding multicast data to Switch A, Router A sends only one copy of multicast data to Switch A in the IPv6 multicast VLAN, and Switch A distributes the data to the sub-VLANs that contain receivers.
Page 252: Ipv6 Multicast Vlan Configuration Task List
For more information about VLAN tags, see Layer 2—LAN Switching Configuration Guide. IPv6 multicast VLAN configuration task list Configuration task Remarks Configuring a sub-VLAN-based IPv6 multicast VLAN Required. Configuring user port attributes Configuring a port-based IPv6 Use either approach. multicast VLAN Configuring IPv6 multicast VLAN ports NOTE: If you have configured both sub-VLAN-based IPv6 multicast VLAN and port-based IPv6 multicast VLAN...
Page 253: Configuring A Port-Based Ipv6 Multicast Vlan
Step Command Remarks Configure the specified By default, an IPv6 multicast VLAN VLANs as sub-VLANs of the subvlan vlan-list has no sub-VLANs. IPv6 multicast VLAN. Configuring a port-based IPv6 multicast VLAN When you configure a port-based IPv6 multicast VLAN, you need to configure the attributes of each user port and then assign the ports to the IPv6 multicast VLAN.
Page 254: Configuring Ipv6 Multicast Vlan Ports
For more information about the port link-type, port hybrid pvid vlan, and port hybrid vlan commands, see Layer 2—LAN Switching Command Reference. Configuring IPv6 multicast VLAN ports In this approach, you configure a VLAN as an IPv6 multicast VLAN and assign user ports to it. You can do this by either adding the user ports in the IPv6 multicast VLAN or specifying the IPv6 multicast VLAN on the user ports.
Page 255: Ipv6 Multicast Vlan Configuration Examples
Task Command Remarks display multicast-vlan ipv6 Display information about an IPv6 [ vlan-id ] [ | { begin | exclude | Available in any view multicast VLAN. include } regular-expression ] IPv6 multicast VLAN configuration examples Sub-VLAN-based multicast VLAN configuration example Network requirements As shown in Figure...
Page 256 [RouterA] multicast ipv6 routing-enable [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] pim ipv6 dm [RouterA-GigabitEthernet1/0/1] quit [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] pim ipv6 dm [RouterA-GigabitEthernet1/0/2] mld enable Configure Switch A: # Enable MLD snooping globally. <SwitchA> system-view [SwitchA] mld-snooping [SwitchA-mld-snooping] quit # Create VLAN 2 through VLAN 5. [SwitchA] vlan 2 to 5 # Configure GigabitEthernet 1/0/2 as a trunk port that permits packets from VLAN 2 and VLAN 3 to pass through.
Page 257 [SwitchB-vlan2] mld-snooping enable [SwitchB-vlan2] quit # Create VLAN 3, assign GigabitEthernet 1/0/3 to VLAN 3, and enable MLD snooping in the VLAN. [SwitchB] vlan 3 [SwitchB-vlan3] port gigabitethernet 1/0/3 [SwitchB-vlan3] mld-snooping enable [SwitchB-vlan3] quit # Configure GigabitEthernet 1/0/1 as a trunk port that permits packets from VLAN 2 and VLAN 3 to pass through.
Page 258 Total 1 MAC Group(s). Router port(s):total 0 port(s). IP group(s):the following ip group(s) match to one mac group. IP group address:FF1E::101 (::, FF1E::101): Host port(s):total 1 port(s). GE1/0/2 MAC group(s): MAC group address:3333-0000-0101 Host port(s):total 1 port(s). GE1/0/2 Vlan(id):4. Total 1 IP Group(s). Total 1 IP Source(s).
Page 259: Port-Based Multicast Vlan Configuration Example
IP group address:FF1E::101 (::, FF1E::101): Host port(s):total 0 port(s). MAC group(s): MAC group address:3333-0000-0101 Host port(s):total 0 port(s). The output shows that MLD snooping is maintaining the router port in the IPv6 multicast VLAN (VLAN 10) and the member ports in the sub-VLANs (VLAN 2 through VLAN 5). Port-based multicast VLAN configuration example Network requirements As shown in...
Page 260 [RouterA-GigabitEthernet1/0/1] quit [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] ipv6 pim dm [RouterA-GigabitEthernet1/0/2] mld enable Configure Switch A: # Enable MLD snooping globally. <SwitchA> system-view [SwitchA] mld-snooping [SwitchA-mld-snooping] quit # Create VLAN 10, assign GigabitEthernet 1/0/1 to VLAN 10, and enable MLD snooping in this VLAN.
Page 261 no subvlan port list: GE1/0/2 GE1/0/3 GE1/0/4 # Display the MLD snooping multicast group information on Switch A. [SwitchA] display mld-snooping group Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s). Port flags: D-Dynamic port, S-Static port, C-Copy port, P-PIM port Subvlan flags: R-Real VLAN, C-Copy VLAN Vlan(id):10.
Page 262: Configuring Ipv6 Multicast Routing And Forwarding
Configuring IPv6 multicast routing and forwarding Overview In IPv6 multicast implementations, the following types of tables implement multicast routing and forwarding: Multicast routing table of an IPv6 multicast routing protocol—Each IPv6 multicast routing protocol • has its own multicast routing table, such as IPv6 PIM routing table. General IPv6 multicast routing table—The multicast routing information of different IPv6 multicast •...
Page 263: Rpf Check Implementation In Ipv6 Multicast
interface in the corresponding routing entry is the RPF interface and the next hop is the RPF neighbor. The router selects one of these optimal routes as the RPF route. The selection process is as follows: If configured to use the longest match principle, the router selects the longest match route from these optimal routes.
Page 264: Configuration Task List
Assume that IPv6 unicast routes are available in the network, IPv6 MBGP is not configured, and IPv6 multicast packets travel along the SPT from the multicast source to the receivers, as shown in Figure The IPv6 multicast forwarding table on Router C contains the (S, G) entry, with VLAN-interface 20 as the RPF interface.
Page 265: Configuring Ipv6 Multicast Routing And Forwarding
Step Command Remarks Enable IPv6 multicast routing. multicast ipv6 routing-enable Disabled by default. Configuring IPv6 multicast routing and forwarding Before you configure IPv6 multicast routing and forwarding, complete the following tasks: Enable IPv6 forwarding and configure an IPv6 unicast routing protocol so that all devices in the •...
Page 266: Configuring The Ipv6 Multicast Forwarding Table Size
Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number multicast ipv6 boundary { ipv6-group-address prefix-length | Configure an IPv6 multicast No forwarding boundary by scope { scope-id | admin-local | forwarding boundary. default. global | organization-local | site-local } } Configuring the IPv6 multicast forwarding table size The switch maintains the corresponding forwarding entry for each IPv6 multicast packet that it receives.
Page 267: Displaying And Maintaining Ipv6 Multicast Routing And Forwarding
Displaying and maintaining IPv6 multicast routing and forwarding CAUTION: The reset commands might cause IPv6 multicast data transmission failures. To display and maintain IPv6 multicast routing and forwarding: Task Command Remarks display multicast ipv6 boundary { group [ ipv6-group-address Display the IPv6 multicast boundary [ prefix-length ] ] | scope [ scope-id ] } Available in any view.
Page 268: Troubleshooting Ipv6 Multicast Policy Configuration
Task Command Remarks Available in user view. When a routing entry is deleted from the IPv6 reset multicast ipv6 routing-table multicast routing table, the { { ipv6-source-address [ prefix-length ] Clear routing entries from the IPv6 corresponding | ipv6-group-address [ prefix-length ] | multicast routing table.
Page 269: Configuring Mld
Configuring MLD Overview An IPv6 router uses the Multicast Listener Discovery (MLD) protocol to discover the presence of multicast listeners on the directly attached subnets. Multicast listeners are nodes that want to receive IPv6 multicast packets. Through MLD, the router can determine whether any IPv6 multicast listeners exist on the directly connected subnets, put corresponding records in the database, and maintain timers related to IPv6 multicast addresses.
Page 270 Joining an IPv6 multicast group Figure 72 MLD queries and reports IPv6 network Querier Router A Router B Ethernet Host A Host B Host C (G2) (G1) (G1) Query Report Assume that Host B and Host C will receive IPv6 multicast data addressed to IPv6 multicast group G1, and Host A will receive IPv6 multicast data addressed to G2, as shown in Figure 72.
Page 271: How Mldv2 Works
The host sends an MLD done message to all IPv6 multicast routers on the local subnet. The destination address is FF02::2. After receiving the MLD done message, the querier sends a configurable number of multicast-address-specific queries to the group that the host is leaving. The destination address field and group address field of the message are both filled with the address of the IPv6 multicast group that is being queried.
Page 272: Mld Messages
When MLDv2 is running on the hosts and routers, Host B can explicitly express its interest in the IPv6 multicast data that Source 1 sends to G (denoted as (S1, G)), rather than the IPv6 multicast data that Source 2 sends to G (denoted as (S2, G)). Thus, only IPv6 multicast data from Source 1 will be delivered to Host B.
Page 273 Figure 74 MLDv2 query message format Type = 130 Code Checksum Maximum Response Delay Reserved Multicast Address (128 bits) Reserved QQIC Number of Sources (n) Source Address [1] (128 bits) Source Address [n] (128 bits) Table 9 MLDv2 query message field description Field Description Type = 130...
Page 274 Field Description • This field is set to 0 in a general query message or a multicast-address-specific query message. Number of Sources • This field represents the number of source addresses in a multicast-address-and-source-specific query message. IPv6 multicast source address in a multicast-address-specific query Source Address( i ) message.
Page 275: Mld Ssm Mapping
MLD SSM mapping The MLD SSM mapping feature enables you to configure static MLD SSM mappings on the last hop router to provide SSM support for receiver hosts that are running MLDv1. The SSM model assumes that the last hop router has identified the desired IPv6 multicast sources when receivers join IPv6 multicast groups. When an MLDv2 enabled host joins a multicast group, it can explicitly specify one or more multicast •...
Page 276: Mld Proxying
MLD proxying In some simple tree-shaped topologies, you do not need to configure complex IPv6 multicast routing protocols, such as IPv6 PIM, on the boundary devices. Instead, you can configure MLD proxying on these devices. With MLD proxying configured, the device serves as a proxy for the downstream hosts to send MLD messages, maintain group memberships, and implement IPv6 multicast forwarding based on the memberships.
Page 277: Mld Configuration Task List
RFC 4605, Internet Group Management Protocol (IGMP)/Multicast Listener Discovery (MLD)-Based • Multicast Forwarding ("IGMP/MLD Proxying") MLD configuration task list Task Remarks Enabling MLD Required Configuring the MLD version Option Configuring static joining Optional Configuring basic MLD functions Configuring an IPv6 multicast group filter Optional Setting the maximum number of IPv6 multicast Optional...
Page 278: Enabling Mld
Determine the maximum number of IPv6 multicast groups that an interface can join. • Enabling MLD Enable MLD on the interface on which IPv6 multicast group memberships will be created and maintained. To enable MLD: Step Command Remarks Enter system view. system-view Enable IPv6 multicast routing.
Page 279: Configuring An Ipv6 Multicast Group Filter
Configuration guidelines Before you can configure an interface of an IPv6 PIM-SM device as a static member of an IPv6 • multicast group or an IPv6 multicast source and group, if the interface is IPv6 PIM-SM enabled, it must be an IPv6 PIM-SM DR. If this interface is MLD enabled but not IPv6 PIM-SM enabled, it must be an MLD querier.
Page 280: Adjusting Mld Performance
Step Command Remarks interface interface-type Enter interface view. interface-number Configure the maximum number of IPv6 multicast groups that the mld group-limit limit 1000 by default. interface can join. NOTE: This configuration takes effect for dynamically joined IPv6 multicast groups but not the statically configured multicast groups.
Page 281: Configuring Mld Query And Response Parameters
For compatibility, the device by default ignores the Router-Alert option and processes all received • MLD messages, no matter whether the MLD messages carry the Router-Alert option or not. To enhance device performance, avoid unnecessary costs, and ensure protocol security, configure •...
Page 282 query). The timer is initialized to a random value in the range of 0 to the maximum response delay advertised in the MLD query message. When the timer decreases to 0, the host sends an MLD membership report message to the IPv6 multicast group. To speed up the response of hosts to MLD queries and avoid simultaneous timer expirations causing MLD report traffic bursts, you must properly set the maximum response delay.
Page 283: Configuring Mld Fast-Leave Processing
Step Command Remarks By default, the other querier present interval is determined by the formula "Other querier present Configure the MLD other timer other-querier-present interval (in seconds) = [ MLD query querier present interval. interval interval ] × [ MLD querier’s robustness variable ] + [ maximum response delay for MLD general query ] /2".
Page 284: Enabling The Mld Host Tracking Function
Enabling the MLD host tracking function With the MLD host tracking function, the switch can record the information of the member hosts that are receiving IPv6 multicast traffic, including the host IPv6 address, running duration, and timeout time. You can monitor and manage the member hosts according to the recorded information. Enabling the MLD host tracking function globally Step Command...
Page 285: Configuration Prerequisites
Configuration prerequisites Before you configure the MLD SSM mapping feature, complete the following tasks: Enable IPv6 forwarding and configure an IPv6 unicast routing protocol so that all devices in the • domain can be interoperable at the network layer. • Configure basic MLD functions.
Page 286: Enabling Mld Proxying
Enabling MLD proxying You can enable MLD proxying on the interface in the direction toward the root of the multicast forwarding tree to make the device serve as an MLD proxy. Configuration guidelines Each device can have only one interface serving as the MLD proxy interface. •...
Page 287: Displaying And Maintaining Mld
Step Command Remarks Enable IPv6 multicast forwarding on a non-querier downstream mld proxying forwarding Disabled by default interface. Displaying and maintaining MLD CAUTION: The reset mld group command might cause multicast data transmission failures. To display and maintain MLD: Task Command Remarks display mld group...
Page 288: Mld Configuration Examples
Task Command Remarks display mld ssm-mapping group Display the IPv6 multicast group [ ipv6-group-address | interface information created based on the interface-type interface-number ] Available in any view. configured MLD SSM mappings. [ verbose ] [ | { begin | exclude | include } regular-expression ] reset mld group { all | interface interface-type interface-number...
Page 289 Figure 78 Network diagram Receiver IPv6 PIM network Host A Vlan-int101 Vlan-int100 3000::12/64 Switch A Host B Querier Vlan-int200 3001::10/64 Receiver Vlan-int201 Host C Switch B Vlan-int200 3001::12/64 Vlan-int202 Host D Switch C Configuration procedure Enable IPv6 forwarding on each switch and configure an IP address and prefix length for each interface as shown in Figure 78.
Page 290: Mld Ssm Mapping Configuration Example
[SwitchB-Vlan-interface201] pim ipv6 dm [SwitchB-Vlan-interface201] quit # Enable IPv6 multicast routing on Switch C, enable IPv6 PIM-DM on each interface, and enable MLD on VLAN-interface 200. <SwitchC> system-view [SwitchC] multicast ipv6 routing-enable [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] mld enable [SwitchC-Vlan-interface200] pim ipv6 dm [SwitchC-Vlan-interface200] quit [SwitchC] interface vlan-interface 202 [SwitchC-Vlan-interface202] pim ipv6 dm...
Page 291 Figure 79 Network diagram Device Interface IPv6 address Device Interface IPv6 address Source 1 — 1001::1/64 Source 3 — 3001::1/64 Source 2 — 2001::1/64 Receiver — 4001::1/64 Switch A Vlan-int100 1001::2/64 Switch C Vlan-int300 3001::2/64 Vlan-int101 1002::1/64 Vlan-int103 3002::1/64 Vlan-int104 1003::1/64 Vlan-int102 2002::2/64...
Page 292 # Enable IPv6 multicast routing on Switch A, and enable IPv6 PIM-SM on each interface. <SwitchA> system-view [SwitchA] multicast ipv6 routing-enable [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] pim ipv6 sm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim ipv6 sm [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 104 [SwitchA-Vlan-interface104] pim ipv6 sm [SwitchA-Vlan-interface104] quit...
Page 293: Mld Proxying Configuration Example
Vlan-interface400 (4001::2): Total 1 MLD SSM-mapping Group reported Group Address: FF3E::101 Last Reporter: 4001::1 Uptime: 00:02:04 Expires: off # Display the IPv6 PIM routing table information on Switch D. [SwitchD] display pim ipv6 routing-table Total 0 (*, G) entry; 2 (S, G) entry (1001::1, FF3E::101) Protocol: pim-ssm, Flag: UpTime: 00:13:25...
Page 294 Figure 80 Network diagram Configuration procedure Enable IPv6 forwarding on each switch and configure the IPv6 address and prefix length of each interface as per Figure 80. (Details not shown.) Enable IPv6 multicast routing, IPv6 PIM-DM, MLD, and MLD proxying: # Enable IPv6 multicast routing on Switch A, IPv6 PIM-DM on VLAN-interface 101, and MLD on VLAN-interface 100.
Page 295: Troubleshooting Mld
# Display MLD group information on Switch A. [SwitchA] display mld group Total 1 MLD Group(s). Interface group report information Vlan-interface100(2001::1): Total 1 MLD Groups reported Group Address Last Reporter Uptime Expires ff3e::101 2001::2 00:02:04 00:01:15 The output shows that the MLD reports sent from the hosts are forwarded to Switch A through the proxy interface, VLAN-interface 100 of Switch B.
Page 296: Inconsistent Memberships On Routers On The Same Subnet
Inconsistent memberships on routers on the same subnet Symptom Different memberships are maintained on different MLD routers on the same subnet. Analysis A router running MLD maintains multiple parameters for each interface, and these parameters • influence one another, forming very complicated relationships. Inconsistent MLD interface parameter configurations for routers on the same subnet will surely result in inconsistent MLD memberships.
Page 297: Configuring Ipv6 Pim
Configuring IPv6 PIM Overview Protocol Independent Multicast for IPv6 (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, or BGP4+. IPv6 PIM uses an IPv6 unicast routing table to perform reverse path forwarding (RPF) check to implement IPv6 multicast forwarding.
Page 298 SPT establishment • • Graft Assert • Neighbor discovery In an IPv6 PIM domain, a PIM router discovers IPv6 PIM neighbors, maintains IPv6 PIM neighboring relationships with other routers, and builds and maintains SPTs by periodically multicasting IPv6 PIM hello messages to all other IPv6 PIM routers on the local subnet. NOTE: Every IPv6 PIM enabled interface on a router sends hello messages periodically and, therefore, learns the IPv6 PIM neighboring information pertinent to the interface.
Page 299 Figure 81 SPT establishment in an IPv6 PIM-DM domain Host A Source Receiver Host B Server Receiver Prune message IPv6 multicast packets Host C The flood-and-prune process takes place periodically. A pruned state timeout mechanism is provided. A pruned branch restarts multicast forwarding when the pruned state times out and then is pruned again when it no longer has any multicast receiver.
Page 300: Ipv6 Pim-Sm Overview
Figure 82 Assert mechanism As shown in Figure 82, after Router A and Router B receive an (S, G) IPv6 multicast 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, and both Router A and Router B, on their own downstream interface, receive a duplicate IPv6 multicast packet that the other has forwarded.
Page 301 multicast group. The path along which the message goes hop by hop to the RP forms a branch of the RPT. When an IPv6 multicast source sends IPv6 multicast streams to an IPv6 multicast group, the • source-side designated router (DR) first registers the multicast source with the RP by sending register messages to the RP by unicast until it receives a register-stop message from the RP.
Page 302 Figure 83 DR election As shown in Figure 83, the DR election process is as follows: Routers on the multi-access network send hello messages to one another. The hello messages contain the router priority for DR election. The router with the highest DR priority will become the In the case of a tie in the router priority, or if any router in the network does not support carrying the DR-election priority in hello messages, the router with the highest IPv6 link-local address will win the DR election.
Page 303 multicast groups and RPs. The BSR then encapsulates the RP-set in the bootstrap messages it periodically originates and floods the bootstrap messages (BSMs) to the entire IPv6 PIM-SM domain. Figure 84 BSR and C-RPs Based on the information in the RP-sets, all routers in the network can calculate the location of the corresponding RPs based on the following rules: The C-RP with the highest priority wins.
Page 304 Embedded RP The embedded RP mechanism enables a router to resolve the RP address from an IPv6 multicast address so that the IPv6 multicast group is mapped to an RP. This RP can take the place of the statically configured RP or the RP dynamically calculated based on the BSR mechanism.
Page 305 node from the outgoing interface list and determines whether it has receivers for that IPv6 multicast group. If not, the router continues to forward the prune message to its upstream router. Multicast source registration The purpose of IPv6 multicast source registration will inform the RP about the existence of the IPv6 multicast source.
Page 306: Ipv6 Administrative Scoping Overview
DRs at the receiver side. The RP acts as a transfer station for all IPv6 multicast packets. The whole process involves the following issues: The DR at the source side and the RP need to implement complicated encapsulation and • de-encapsulation of IPv6 multicast packets.
Page 307 multicast protocol packets, such as assert messages and bootstrap messages, for a specific group range cannot cross the IPv6 admin-scope zone boundary. IPv6 multicast group ranges served by different IPv6 admin-scope zones can overlap. An IPv6 multicast group is valid only within its local IPv6 admin-scope zone, functioning as a private group address.
Page 308: Ipv6 Pim-Ssm Overview
Figure 88 IPv6 multicast address format An IPv6 admin-scoped zone with a larger scope field value contains an IPv6 admin-scoped zone with a smaller scope field value. The zone with the scope field value of E is the IPv6 global-scoped zone.
Page 309 Neighbor discovery IPv6 PIM-SSM uses the same neighbor discovery mechanism as in IPv6 PIM-SM. For more information, "Neighbor discovery." DR election IPv6 PIM-SSM uses the same DR election mechanism as in IPv6 PIM-SM. For more information, see "DR election." 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 will join falls into the IPv6 SSM group range.
Page 310: Relationship Among Ipv6 Pim Protocols
Relationship among IPv6 PIM protocols In an IPv6 PIM network, IPv6 PIM-DM cannot work with IPv6 PIM-SM or IPv6 PIM-SSM. However, IPv6 PIM-SM and IPv6 PIM-SSM can work together. When they work together, which one is chosen for a receiver trying to join a group depends, as shown in Figure Figure 90 Relationship among IPv6 PIM protocols For more information about MLD SSM mapping, see...
Page 311: Configuration Prerequisites
Configuration prerequisites Before you configure IPv6 PIM-DM, complete the following tasks: Enable IPv6 forwarding and configure an IPv6 unicast routing protocol so that all devices in the • domain are interoperable at the network layer. • Determine the interval between state refresh messages. Determine the minimum time to wait before receiving a new refresh message.
Page 312: Configuring State Refresh Parameters
Configuring state refresh parameters The router directly connected with the multicast source periodically sends state-refresh messages. You can configure the interval for sending such messages. A router might receive multiple state-refresh messages within a short time. Some messages might be duplicated messages.
Page 313: Configuring Ipv6 Pim-Sm
For more information about the configuration of other timers in IPv6 PIM-DM, see "Configuring IPv6 PIM common timers." Configuring IPv6 PIM-SM IPv6 PIM-SM configuration task list Task Remarks Enabling IPv6 PIM-SM Required. Configuring a static RP Required. Configuring a C-RP Use any approach.
Page 314: Enabling Ipv6 Pim-Sm
Determine the IPv6 ACL rule defining a legal BSR address range. • • Determine the BS period. Determine the BS timeout. • Determine the IPv6 ACL rule for register message filtering. • • Determine the register suppression time. Determine the register probe time. •...
Page 315 Step Command Remarks Enter IPv6 PIM view. pim ipv6 Configure a static RP for IPv6 static-rp ipv6-rp-address No static RP by default. PIM-SM. [ acl6-number ] [ preferred ] Configuring a C-RP In an IPv6 PIM-SM domain, you can configure routers that intend to become the RP as C-RPs. The BSR collects the C-RP information by receiving the C-RP-Adv messages from C-RPs or auto-RP announcements from other routers and organizes the information into an RP-set, which is flooded throughout the entire network.
Page 316: Configuring A Bsr
Step Command Remarks Optional. By default, embedded RP is enabled for IPv6 multicast groups in the default embedded RP address scopes. Enable embedded RP. embedded-rp [ acl6-number ] The default embedded RP address scopes are FF7x::/12 and FFFx::/12. Here "x" refers to any legal address scope.
Page 317 When a C-BSR receives the bootstrap message of another C-BSR, it first compares its own priority with the other C-BSR’s priority carried in the message. The C-BSR with a higher priority wins. If a tie exists in the priority, the C-BSR with a higher IPv6 address wins. The loser uses the winner’s BSR address to replace its own BSR address and no longer assumes itself to be the BSR, and the winner keeps its own BSR address and continues assuming itself to be the BSR.
Page 318 Perform the following configuration on routers that you want to configure as an IPv6 PIM domain border. To configure an IPv6 PIM border domain: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure an IPv6 PIM No IPv6 PIM domain border is pim ipv6 bsr-boundary domain border.
Page 319 Step Command Remarks Optional. By default, the BS period is determined by the formula "BS period = (BS timeout – 10) / 2." Configure the BS period. c-bsr interval interval The default BS timeout is 130 seconds, so the default BS period = (130 –...
Page 320: Configuring Ipv6 Administrative Scoping
Step Command Remarks Enter system view. system-view Enter IPv6 PIM view. pim ipv6 Disable the BSM semantic By default, the BSM semantic undo bsm-fragment enable fragmentation function. fragmentation function is enabled. Configuring IPv6 administrative scoping With IPv6 administrative scoping disabled, an IPv6 PIM-SM domain has only one BSR. The BSR manages the whole network.
Page 321: Configuring Ipv6 Multicast Source Registration
Configuring C-BSRs for IPv6 admin-scope zones In a network with IPv6 administrative scoping enabled, BSRs are elected from C-BSRs specific to different Scope field values. The C-RPs in the network send advertisement messages to the specific BSR. The BSR summarizes the advertisement messages to form an RP-set and advertises it to all routers in the specific admin-scope zone.
Page 322: Disabling The Switchover To Spt
Configure a filtering rule for register messages on all C-RP routers, and configure them to calculate the checksum based on the entire register messages. Configure the register suppression time and the register probe time on all routers that might become IPv6 source-side DRs. To configure register-related parameters: Step Command...
Page 323: Ipv6 Pim-Ssm Configuration Task List
IPv6 PIM-SSM configuration task list Task Remarks Enabling IPv6 PIM-SM Required Configuring the IPv6 SSM group range Optional Configuring IPv6 PIM common features Optional Configuration prerequisites Before you configure IPv6 PIM-SSM, complete the following tasks: Enable IPv6 forwarding and configure an IPv6 unicast routing protocol so that all devices in the •...
Page 324: Configuring Ipv6 Pim Common Features
Configuration procedure Perform the following configuration on all routers in the IPv6 PIM-SSM domain. To configure the IPv6 SSM group range: Step Command Remarks Enter system view. system-view Enter IPv6 PIM view. pim ipv6 Optional. Configure the IPv6 SSM group ssm-policy acl6-number FF3x::/32 by default, here "x"...
Page 325: Configuring An Ipv6 Multicast Data Filter
Determine the prune message delay (global value/interface level value). • • Determine the prune override interval (global value/interface level value). Determine the prune delay. • Determine the hello interval (global value/interface level value). • • Determine the maximum delay between hello message (interface level value). Determine the assert timeout time (global value/interface value).
Page 326: Configuring Ipv6 Pim Hello Options
Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure a hello message pim ipv6 neighbor-policy No hello message filter by default filter. acl6-number NOTE: With the hello message filter configured, if hello messages of an existing IPv6 PIM neighbor fail to pass the filter, the IPv6 PIM neighbor will be removed automatically when it times out.
Page 327: Configuring The Prune Delay
Step Command Remarks Enter system view. system-view Enter IPv6 PIM view. pim ipv6 Optional. Configure the priority for DR hello-option dr-priority priority election. 1 by default. Optional. Configure IPv6 PIM neighbor hello-option holdtime interval timeout time. 105 seconds by default. Optional.
Page 328: Configuring Ipv6 Pim Common Timers
Step Command Remarks Enter system view. system-view Enter IPv6 PIM view. pim ipv6 Optional. Configure the prune delay prune delay interval By default, the prune delay is not interval. configured.. Configuring IPv6 PIM common timers IPv6 PIM routers discover IPv6 PIM neighbors and maintain IPv6 PIM neighboring relationships with other routers by periodically sending hello messages.
Page 329: Configuring Join/Prune Message Sizes
Configuring IPv6 PIM common timers on an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Optional. Configure the hello interval. pim ipv6 timer hello interval 30 seconds by default. Optional. Configure the maximum delay pim ipv6 triggered-hello-delay between hello messages.
Page 330: Setting The Dscp Value For Ipv6 Pim Messages
Setting the DSCP value for IPv6 PIM messages IPv6 uses an eight-bit Traffic class field (called ToS in IPv4) to identify type of service for IP packets. As defined in RFC 24724, the first six bits contains the DSCP priority for prioritizing traffic in the network and the last two bits are reserved.
Page 331: Ipv6 Pim Configuration Examples
Task Command Remarks display pim ipv6 join-prune mode { sm [ flags flag-value ] | ssm } [ interface interface-type Display information about interface-number | neighbor Available in any view join/prune messages to send. ipv6-neighbor-address ] * [ verbose ] [ | { begin | exclude | include } regular-expression ] display pim ipv6 neighbor [ interface interface-type...
Page 332 Figure 91 Network diagram Device Interface IPv6 address Device Interface IPv6 address Switch A Vlan-int100 1001::1/64 Switch D Vlan-int300 4001::1/64 Vlan-int103 1002::1/64 Vlan-int103 1002::2/64 Switch B Vlan-int200 2001::1/64 Vlan-int101 2002::2/64 Vlan-int101 2002::1/64 Vlan-int102 3001::2/64 Switch C Vlan-int200 2001::2/64 Vlan-int102 3001::1/64 Configuration procedure Enable IPv6 forwarding on each switch and configure the IPv6 address and prefix length for each interface as per...
Page 333 # Enable IPv6 multicast routing, MLD and IPv6 PIM-DM on Switch B and Switch C in the same way. (Details not shown.) # Enable IPv6 multicast routing on Switch D, and enable IPv6 PIM-DM on each interface. <SwitchD> system-view [SwitchD] multicast ipv6 routing-enable [SwitchD] interface vlan-interface 300 [SwitchD-Vlan-interface300] pim ipv6 dm [SwitchD-Vlan-interface300] quit...
Page 334: Ipv6 Pim-Sm Non-Scoped Zone Configuration Example
(*, FF0E::101) Protocol: pim-dm, Flag: WC UpTime: 00:01:24 Upstream interface: NULL Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: mld, UpTime: 00:01:20, Expires: never (4001::100, FF0E::101) Protocol: pim-dm, Flag: ACT UpTime: 00:01:20 Upstream interface: Vlan-interface103 Upstream neighbor: 1002::2...
Page 335 FF0E::101/64. Modify the hash mask length to map a certain number of consecutive IPv6 group addresses within the range to the two C-RPs. MLDv1 runs between Switch A and N1 and between Switch B/Switch C and N2. Figure 92 Network diagram Device Interface IPv6 address...
Page 336 [SwitchA-Vlan-interface100] pim ipv6 sm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim ipv6 sm [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] pim ipv6 sm [SwitchA-Vlan-interface102] quit # Enable IPv6 multicast routing, MLD and IPv6 PIM-SM on Switch B and Switch C in the same way (Details not shown.).
Page 337 State: Accept Preferred Uptime: 00:04:22 Expires: 00:01:46 # Display information about the BSR and locally configured C-RP in effect on Switch D. [SwitchD] display pim ipv6 bsr-info Elected BSR Address: 1003::2 Priority: 20 Hash mask length: 128 State: Elected Uptime: 00:05:26 Expires: 00:01:45 Candidate BSR Address: 4002::1 Priority: 10...
Page 338 Expires: 00:02:11 RP: 1003::2 Priority: 192 HoldTime: 130 Uptime: 00:05:19 Expires: 00:02:11 Assume that Host A needs to receive information addressed to the IPv6 multicast group G FF0E::100. The RP corresponding to the multicast group G is Switch E as a result of hash calculation, so an RPT will be built between Switch A and Switch E.
Page 339: Ipv6 Pim-Sm Admin-Scope Zone Configuration Example
Protocol: pim-sm, Flag: SPT LOC ACT UpTime: 00:14:44 Upstream interface: Vlan-interface300 Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface105 Protocol: mld, UpTime: 00:14:44, Expires: 00:02:26 # Display IPv6 PIM multicast routing table information on Switch E. [SwitchE] display pim ipv6 routing-table Total 1 (*, G) entry;...
Page 340 Figure 93 Network diagram IPv6 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 Vlan-int101 Vlan-int107 Switch B Switch A Switch C Switch I Switch H Vlan-int107 Vlan-int110 Vlan-int106 Vlan-int104 Switch D...
Page 341 # Enable IPv6 multicast routing and administrative scoping on Switch A, enable MLD on the host-side interface VLAN-interface 100, and enable IPv6 PIM-SM on each interface. <SwitchA> system-view [SwitchA] multicast ipv6 routing-enable [SwitchA] pim ipv6 [SwitchA-pim6] c-bsr admin-scope [SwitchA-pim6] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] mld enable [SwitchA-Vlan-interface100] pim ipv6 sm...
Page 342 # On Switch C, configure VLAN-interface 103 and VLAN-interface 106 to be the boundary of admin-scope zone 2. <SwitchC> system-view [SwitchC] interface vlan-interface 103 [SwitchC-Vlan-interface103] multicast ipv6 boundary scope 4 [SwitchC-Vlan-interface103] quit [SwitchC] interface vlan-interface 106 [SwitchC-Vlan-interface106] multicast ipv6 boundary scope 4 [SwitchC-Vlan-interface106] quit # On Switch D, configure VLAN-interface 107 to be the boundary of admin-scope zone 2.
Page 343 Priority: 64 Hash mask length: 126 State: Elected Scope: 4 Uptime: 00:04:54 Next BSR message scheduled at: 00:00:06 Candidate BSR Address: 1002::2 Priority: 64 Hash mask length: 126 State: Elected Scope: 4 Candidate RP: 1002::2(Vlan-interface101) Priority: 192 HoldTime: 130 Advertisement Interval: 60 Next advertisement scheduled at: 00:00:15 # Display information about the BSR and locally configured C-RP on Switch D.
Page 344 Hash mask length: 126 State: Elected Scope: 14 Uptime: 00:01:11 Next BSR message scheduled at: 00:00:49 Candidate BSR Address: 8001::1 Priority: 64 Hash mask length: 126 State: Elected Scope: 14 Candidate RP: 8001::1(Vlan-interface109) Priority: 192 HoldTime: 130 Advertisement Interval: 60 Next advertisement scheduled at: 00:00:55 To view the RP information learned on a switch, use the display pim ipv6 rp-info command.
Page 345 prefix/prefix length: FF4E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF5E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF6E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF7E::/16 RP: 8001::1 Priority: 192 HoldTime: 130...
Page 346 prefix/prefix length: FFBE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFCE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFDE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFEE::/16 RP: 8001::1 Priority: 192 HoldTime: 130...
Page 347 Expires: 00:01:51 prefix/prefix length: FF24::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF34::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF44::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF54::/16 RP: 1002::2 Priority: 192...
Page 348 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF94::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFA4::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFB4::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFC4::/16 RP: 1002::2...
Page 349 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 # Display RP information on Switch F. [SwitchF] display pim rp-info PIM-SM BSR RP information: prefix/prefix length: FF0E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF1E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51...
Page 350 prefix/prefix length: FF6E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF7E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF8E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF9E::/16 RP: 8001::1 Priority: 192 HoldTime: 130...
Page 351: Ipv6 Pim-Ssm Configuration Example
prefix/prefix length: FFDE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFEE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFFE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 IPv6 PIM-SSM configuration example Network requirements Receivers receive VOD information through multicast.
Page 352 Figure 94 Network diagram Device Interface IPv6 address Device Interface IPv6 address Switch A Vlan-int100 1001::1/64 Switch D Vlan-int300 4001::1/64 Vlan-int101 1002::1/64 Vlan-int101 1002::2/64 Vlan-int102 1003::1/64 Vlan-int105 4002::1/64 Switch B Vlan-int200 2001::1/64 Switch E Vlan-int104 3001::2/64 Vlan-int103 2002::1/64 Vlan-int103 2002::2/64 Switch C Vlan-int200 2001::2/64...
Page 353 [SwitchA-Vlan-interface101] pim ipv6 sm [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] pim ipv6 sm [SwitchA-Vlan-interface102] quit # Enable IPv6 multicast routing, MLD and IPv6 PIM-SM on Switch B and Switch C is similar to that on Switch A in the same way. (Details not shown.) # Enable IPv6 multicast routing and IPv6 PIM-SM on Switch D and Switch E in the same way.
Page 354: Troubleshooting Ipv6 Pim Configuration
# Display IPv6 PIM multicast routing table information on Switch B. [SwitchD] display pim ipv6 routing-table 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...
Page 355: Ipv6 Multicast Data Abnormally Terminated On An Intermediate Router
Use the display current-configuration command to verify that the same IPv6 PIM mode is enabled on all the routers in the entire network. Make sure that the same IPv6 PIM mode is enabled on all the routers: IPv6 PIM-SM on all routers, or IPv6 PIM-DM on all routers. IPv6 multicast data abnormally terminated on an intermediate router Symptom...
Page 356: Rpt Establishment Failure Or Source Registration Failure In Ipv6 Pim-Sm
Use the display pim ipv6 rp-info command to verify that the same RP address has been configured on all the routers throughout the network. RPT establishment failure or source registration failure in IPv6 PIM-SM Symptom C-RPs cannot unicast advertise messages to the BSR. The BSR does not advertise bootstrap messages containing C-RP information and has no unicast route to any C-RP.
Page 357: Configuring Ipv6 Mbgp
Configuring IPv6 MBGP This chapter covers configuration tasks related to multiprotocol BGP for IPv6 multicast. For information about BGP and IPv6 BGP, see Layer 3—IP Routing Configuration Guide. The term "router" in this chapter refers to both routers and Layer 3 switches. IPv6 MBGP overview IETF defined Multiprotocol BGP (MP-BGP) to carry routing information for multiple network-layer protocols.
Page 358: Configuring Basic Ipv6 Mbgp Functions
Task Remarks optimizing IPv6 Enabling the IPv6 MBGP orf capability Optional MBGP networks Configuring the maximum number of equal-cost routes for Optional load-balancing Configuring an IPv6 MBGP peer group Optional Configuring a large scale IPv6 MBGP Configuring IPv6 MBGP community Optional network Configuring an IPv6 MBGP route reflector...
Page 359: Controlling Route Distribution And Reception
To configure a preferred value for routes from a peer or a peer group: Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter IPv6 MBGP address ipv6-family multicast family view. Specify a preferred value for peer { ipv6-group-name | Optional.
Page 360: Configuring Ipv6 Mbgp Route Summarization
Step Command Description Optional. By default, default route Enable default route redistribution is not allowed. redistribution into the IPv6 default-route imported If the default-route imported MBGP routing table. command is not configured, using the import-route command cannot redistribute any IGP default route. import-route protocol [ process-id Enable route redistribution [ med med-value | route-policy...
Page 361: Configuring Outbound Ipv6 Mbgp Route Filtering
Configuring outbound IPv6 MBGP route filtering Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter IPv6 MBGP address ipv6-family multicast family view. • Configure the filtering of outgoing routes: filter-policy { acl6-number | ipv6-prefix ipv6-prefix-name } export Use any of the commands.
Page 362: Configuring Ipv6 Mbgp Route Dampening
Step Command Remarks Use any of the commands • Configure inbound route filtering: By default, advertised routes filter-policy { acl6-number | ipv6-prefix are not filtered. ipv6-prefix-name } import You can configure a filtering • Apply a routing policy to routes from a policy as required.
Page 363: Configuration Prerequisites
IPv6 MBGP protocol preference • • Default LOCAL_PREF attribute MED attribute • NEXT_HOP attribute • • AS_PATH attribute Configuration prerequisites Before you configure IPv6 MBGP route attributes, complete the following tasks: Enable IPv6. • Configure basic IPv6 MBGP functions. • Configuring IPv6 MBGP route preferences Step Command...
Page 364: Configuring The Next_Hop Attribute
Step Command Remarks Enter IPv6 MBGP address ipv6-family multicast family view. Optional. Configure a default MED default med med-value By default, the default med-value is value. Enable the comparison of the Optional. MED for routes from different compare-different-as-med Not enabled by default. ASs.
Page 365: Tuning And Optimizing Ipv6 Mbgp Networks
Step Command Remarks Allow the local AS number to appear in the as-path of routes from a peer or a peer peer { ipv6-group-name | Optional. group and specify the number ipv6-address } allow-as-loop of times that the local AS Not allowed by default.
Page 366: Enabling The Ipv6 Mbgp Orf Capability
Step Command Remarks Enter IPv6 address family ipv6-family view. peer { ipv6-group-name | Optional. Enable IPv6 BGP route refresh ipv6-address } capability-advertise for a peer or a peer group. Enabled by default. route-refresh Performing soft reset manually If the peer does not support route refresh, you can use the peer keep-all-routes command to save all the route updates from the peer, and then use the refresh bgp ipv6 multicast command to soft-reset IPv6 MBGP connections to refresh the IPv6 MBGP routing table and apply the new policy without terminating IPv6 MBGP connections.
Page 367: Configuring The Maximum Number Of Equal-Cost Routes For Load-Balancing
Step Command Remarks Enter IPv6 address family ipv6-family view. Optional. peer { group-name | Enable BGP route refresh for a Enabled by default. ipv6-address } capability-advertise peer or a peer group. If this feature is not enabled, you route-refresh must configure this command. Optional.
Page 368: Configuring A Large Scale Ipv6 Mbgp Network
Configuring a large scale IPv6 MBGP network Before you configure the following tasks, you must configure basic IPv6 MBGP functions. Configuring an IPv6 MBGP peer group For easy management and configuration, you can organize some IPv6 MBGP peers that have the same route update policy into a peer group.
Page 369: Configuring An Ipv6 Mbgp Route Reflector
Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter IPv6 MBGP address ipv6-family multicast family view. Advertise the COMMUNITY peer { ipv6-group-name | By default, no COMMUNITY attribute to an IPv6 MBGP ipv6-address } attribute is advertised to any peer peer or a peer group.
Page 370: Displaying And Maintaining Ipv6 Mbgp
Displaying and maintaining IPv6 MBGP Displaying IPv6 MBGP Task Command Remarks Display IPv6 MBGP peer group display bgp ipv6 multicast group [ ipv6-group-name ] [ | Available in information. { begin | exclude | include } regular-expression ] any view Display IPv6 MBGP routing display bgp ipv6 multicast network [ | { begin | exclude Available in...
Page 371: Resetting Ipv6 Mbgp Connections
Task Command Remarks display bgp ipv6 multicast routing-table peer Display the IPv6 MBGP routes ipv6-address { advertised-routes | received-routes } Available in received from or advertised to the [ network-address prefix-length | statistic ] [ | { begin | any view IPv6 MBGP peer or peer group.
Page 372 The IPv6 multicast source belongs to IPv6 PIM-SM 1 and the receiver belongs to IPv6 PIM-SM 2. • • The VLAN-interface 101 of Switch A and Switch B must be configured as the C-BSR and C-RP of the IPv6 PIM-SM domains. Enable the imbedded RP function for all switches in IPv6 PIM domain.
Page 373 [SwitchC] multicast ipv6 routing-enable [SwitchC] interface vlan-interface 102 [SwitchC-Vlan-interface102] pim ipv6 sm [SwitchC-Vlan-interface102] quit [SwitchC] interface vlan-interface 104 [SwitchC-Vlan-interface104] pim ipv6 sm [SwitchC-Vlan-interface104] quit [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] pim ipv6 sm [SwitchC-Vlan-interface200] mld enable [SwitchC-Vlan-interface200] quit # Configure an IPv6 PIM domain border on Switch A. [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim ipv6 bsr-boundary [SwitchA-Vlan-interface101] quit...
Page 374 [SwitchB-bgp-af-ipv6-mul] import-route ospfv3 1 [SwitchB-bgp-af-ipv6-mul] quit [SwitchB-bgp] quit Verify the configuration: Use the display bgp ipv6 multicast peer command to display IPv6 MBGP peers on a switch. For example: # Display IPv6 MBGP peers on Switch B. [SwitchB] display bgp ipv6 multicast peer BGP local router ID : 2.2.2.2 Local AS number : 200 Total number of peers : 3...
Page 375: Support And Other Resources
Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.com/support Before contacting HP, collect the following information: Product model names and numbers • • Technical support registration number (if applicable) Product serial numbers •...
Page 376: Conventions
Conventions This section describes the conventions used in this documentation set. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown. Italic Italic text represents arguments that you replace with actual values. Square brackets enclose syntax choices (keywords or arguments) that are optional. Braces enclose a set of required syntax choices separated by vertical bars, from which { x | y | ...
Page 377 Network topology icons Represents a generic network device, such as a router, switch, or firewall. Represents a routing-capable device, such as a router or Layer 3 switch. Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features.
Page 378: Index
Index A C D E I M O P R T Configuring IPv6 PIM-SSM,31 1 Configuring MBGP route attributes,193 Adjusting IGMP performance,85 Configuring MLD proxying,274 Adjusting MLD performance,269 Configuring MLD snooping port functions,213 Appendix,238 Configuring MLD snooping proxying,219 Appendix,44 Configuring MLD snooping querier,217 Configuring MLD SSM mapping,273...
Page 379 IGMP configuration examples,93 Overview,57 IGMP configuration task list,82 Overview,258 IGMP snooping configuration examples,33 Overview,251 IGMP snooping configuration task list,17 Overview,45 Introduction to multicast,1 Overview,206 IPv6 MBGP configuration example,360 Overview,239 IPv6 MBGP configuration task list,346 Overview,155 IPv6 MBGP overview,346 Overview,12 IPv6 multicast VLAN configuration examples,244 IPv6 multicast VLAN configuration task list,241...

This manual is also suitable for:

6125 blade switch series

HP 6125G Configuration Manual

Multicast Overview

Configuring IGMP Snooping

Appendix

Configuring Multicast Vlans

Configuring Multicast Routing and Forwarding

Configuring IGMP

Configuring PIM

Configuring MSDP

Configuring MBGP

Configuring MLD Snooping

Appendix

Configuring Ipv6 Multicast Vlans

Quick Links

Configuration Guide

Troubleshooting

Related Manuals for HP 6125G

Summary of Contents for HP 6125G