Page 1 H3C S5500-EI & S5500-SI Switch Series IP Multicast Configuration Guide Hangzhou H3C Technologies Co., Ltd. http://www.h3c.com Software version: Release 2220 Document version: 6W100-20130527...
Page 2 Copyright © 2013, Hangzhou H3C Technologies Co., Ltd. and its licensors All rights reserved No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of Hangzhou H3C Technologies Co., Ltd.
Page 3 The H3C S5500-EI & S5500-SI documentation set includes 10 configuration guides, which describe the software features for the H3C S5500-EI & S5500-SI Switch Series Release 2220, and guide you through the software configuration procedures. These configuration guides also provide configuration examples to help you apply software features to different network scenarios.
Page 4: Command Conventions
Configuration guide Added and modified features IGMP (available only on the Added features: setting the DSCP value for IGMP messages. S5500-EI) PIM (available only on the Added feature: setting the DSCP value for PIM messages. S5500-EI) MSDP (available only on the...
Page 5 Layer 2 forwarding and other Layer 2 features. Port numbering in examples The port numbers in this document are for illustration only and might be unavailable on your device. About the S5500-EI & S5500-SI documentation set The H3C S5500-EI & S5500-SI documentation set includes: Category Documents Purposes Marketing brochure Describe product specifications and benefits.
Page 6: Obtaining Documentation
Obtaining documentation You can access the most up-to-date H3C product documentation on the World Wide Web at http://www.h3c.com. Click the links on the top navigation bar to obtain different categories of product documentation: [Technical Support & Documents > Technical Documents] –...
Page 7: Technical Support
[Technical Support & Documents > Software Download] – Provides the documentation released with the software version. Technical support service@h3c.com http://www.h3c.com Documentation feedback You can e-mail your comments about product documentation to info@h3c.com. We appreciate your comments.
Page 8: Table Of Contents
Contents Multicast overview ······················································································································································· 1 Introduction to multicast ···················································································································································· 1 Information transmission techniques ······················································································································· 1 Multicast features ······················································································································································ 4 Common notations in multicast ······························································································································· 5 Multicast advantages and applications ················································································································· 5 Multicast models ································································································································································ 6 ...
Page 9 Configuring an IGMP snooping policy ························································································································ 32 Configuring a multicast group filter ····················································································································· 32 Configuring multicast source port filtering ·········································································································· 33 Enabling dropping unknown multicast data ······································································································· 34 Configuring IGMP report suppression ················································································································ 34 Setting the maximum number of multicast groups that a port can join ··························································· 35 ...
Page 10 Sub-VLAN-based multicast VLAN configuration example ················································································· 70 Port-based multicast VLAN configuration example ···························································································· 74 Configuring multicast routing and forwarding (available only on the S5500-EI) ················································· 78 Overview ········································································································································································· 78 RPF check mechanism ··········································································································································· 78 Static multicast routes ············································································································································ 81 ...
Page 11 No membership information on the receiver-side router ················································································· 129 Inconsistent memberships on routers on the same subnet ··············································································· 130 Configuring PIM (available only on the S5500-EI) ······························································································· 131 PIM overview ································································································································································ 131 PIM-DM overview ················································································································································ 131 ...
Page 12 RPs cannot join SPT in PIM-SM ·························································································································· 209 RPT establishment failure or source registration failure in PIM-SM ································································ 210 Configuring MSDP (available only on the S5500-EI) ··························································································· 211 Overview ······································································································································································· 211 How MSDP works ··············································································································································· 212 ...
Page 13 No SA entries in the switch's SA cache ············································································································ 243 Inter-RP communication faults in Anycast RP application ················································································ 244 Configuring MBGP (available only on the S5500-EI) ·························································································· 245 MBGP overview ···························································································································································· 245 Protocols and standards ·············································································································································· 245 ...
Page 14 Configuring the AS_PATH attributes ················································································································· 254 Tuning and optimizing MBGP networks ···················································································································· 254 Configuring MBGP soft reset ······························································································································ 254 Enabling the MBGP ORF capability ·················································································································· 256 Configuring the maximum number of MBGP routes for load balancing ······················································· 257 ...
Page 15 IPv6 multicast VLAN configuration examples ············································································································ 320 Sub-VLAN-based multicast VLAN configuration example ··············································································· 320 Port-based multicast VLAN configuration example ·························································································· 325 Configuring IPv6 multicast routing and forwarding (available only on the S5500-EI) ······································ 328 Overview ······································································································································································· 328 viii...
Page 16 Displaying and maintaining IPv6 multicast routing and forwarding ······································································ 333 Troubleshooting IPv6 multicast policy configuration ································································································ 335 Abnormal termination of IPv6 multicast data ··································································································· 335 Configuring MLD (available only on the S5500-EI) ····························································································· 336 Overview ······································································································································································· 336 MLD versions ························································································································································ 336 ...
Page 17 No member information on the receiver-side router ························································································ 364 Inconsistent memberships on routers on the same subnet ··············································································· 365 Configuring IPv6 PIM (available only on the S5500-EI) ······················································································ 366 Overview ······································································································································································· 366 IPv6 PIM-DM overview ········································································································································ 366 ...
Page 18 RPS cannot join SPT in IPv6 PIM-SM ················································································································· 448 RPT establishment failure or source registration failure in IPv6 PIM-SM ························································ 449 Configuring IPv6 MBGP (available only on the S5500-EI) ·················································································· 450 IPv6 MBGP overview ··················································································································································· 450 ...
Page 19 Configuring the default local preference ·········································································································· 456 Configuring the MED attribute ··························································································································· 457 Configuring the NEXT_HOP attribute ················································································································ 457 Configuring the AS_PATH attribute ··················································································································· 458 Tuning and optimizing IPv6 MBGP networks ············································································································ 458 Configuration prerequisites ································································································································ 458 ...
Page 20: 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 21 Figure 1 Unicast transmission Host A Receiver Host B Source Host C Receiver Host D IP network Receiver Packets for Host B Host E Packets for Host D Packets for Host E Figure 1, assume that Host B, Host D and Host E need the information. A separate transmission channel must be established from the information source to each of these hosts.
Page 22 Figure 2 Broadcast transmission Figure 2, assume that only Host B, Host D, and Host E need the information. If the information is broadcast to the subnet, Host A and Host C also receive it. In addition to information security issues, broadcasting to hosts that do not need the information also causes traffic flooding on the same subnet.
Page 23: 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 24: Common Notations In Multicast
G. Here, "S" represents a specific multicast source, and "G" represents a specific multicast group. For more information about the concepts RPT and SPT, see "Configuring PIM (available only on the S5500-EI)" and "Configuring IPv6 PIM (available only on the S5500-EI)." Multicast advantages and applications...
Page 25: Multicast Models
• Distributed application—Enables point-to-multipoint applications at the price of minimum network resources. Multicast applications The scenarios in which the multicast technique can be effectively applied are: • Multimedia and streaming applications, such as web TV, web radio, and real time video/audio conferencing •...
Page 26: Multicast Architecture
Multicast architecture IP multicast addresses the following questions: • Where should the multicast source transmit information to? (Multicast addressing.) What receivers exist on the network? (Host registration.) • Where is the multicast source that will provide data to the receivers? (Multicast source discovery.) •...
Page 27 Address block Description Administratively scoped multicast addresses. These addresses are considered locally unique rather than globally unique, and can be 239.0.0.0 to 239.255.255.255 reused in domains administered by different organizations without causing conflicts. For more information, see RFC 2365. NOTE: "Glop"...
Page 28 The following describes the fields of an IPv6 multicast address: 0xFF—The most significant eight bits are 1 1 1 1 1 1 1 1, which indicates that this address is an IPv6 multicast address. Flags—The Flags field contains four bits. Figure 5 Flags field format Table 4 Flags field description Description...
Page 29 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. Ethernet multicast MAC addresses A multicast MAC address identifies a group of receivers at the data link layer. •...
Page 30: Multicast Protocols
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. Layer 2 multicast refers to IP multicast working at the data link layer. The corresponding multicast protocols are Layer 2 multicast protocols, which include IGMP snooping, MLD snooping, PIM snooping, IPv6 PIM snooping, multicast VLAN, and IPv6 multicast VLAN.
Page 31 In the ASM model, multicast routes include intra-domain routes and inter-domain routes. An intra-domain multicast routing protocol discovers multicast sources and builds multicast distribution trees within an AS to deliver multicast data to receivers. Among a variety of mature intra-domain multicast routing protocols, Protocol Independent Multicast (PIM) is most widely used.
Page 32: Multicast Packet Forwarding Mechanism
The RPF check mechanism is the basis for most multicast routing protocols to implement multicast forwarding. For more information about the RPF mechanism, see "Configuring multicast routing and forwarding (available only on the S5500-EI)" and "Configuring IPv6 multicast routing and forwarding (available only on the S5500-EI)." Multicast support for VPNs Multicast support for VPNs refers to multicast applied in virtual private networks (VPNs).
Page 33: Introduction To Vpn Instances
VPNs are called VPN instances. NOTE: The S5500-EI switches can acts as MCE or CE devices. Multicast application in VPNs A PE or MCE device that supports multicast for VPNs does the following operations: Maintains an independent set of multicast forwarding mechanisms for each VPN, including the •...
Page 34 The PE device also implements information exchange and data conversion between the public network and VPN instances. As shown in Figure 10, when a multicast source in VPN A sends a multicast stream to a multicast group, only the receivers that belong to both the multicast group and VPN A can receive the multicast stream. The multicast data is multicast both in VPN A and on the public network.
Page 35: 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 36 An IGMP-snooping-enabled switch deems that all its ports on which IGMP general queries with the source IP address other than 0.0.0.0 or that receive PIM hello messages are received are dynamic router ports. For more information about PIM hello messages, see "Configuring PIM (available only on the S5500-EI)."...
Page 37: How Igmp Snooping Works
Aging timers for dynamic ports in IGMP snooping and related messages and actions Timer Description Message before expiry Action after expiry For each dynamic router port, the switch starts an IGMP general query of The switch removes this Dynamic router port aging timer.
Page 38 IGMP report suppression mechanism, see "Configuring IGMP (available only on the S5500-EI)." 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 39: Igmp Snooping Proxying
Even though an IGMP snooping proxy is a host from the perspective of its upstream device, the IGMP membership report suppression mechanism for hosts does not take effect on it. For more information about the IGMP report suppression mechanism for hosts, see "Configuring IGMP (available only on the S5500-EI)." Figure 13 Network diagram IGMP Querier IP network...
Page 40: Protocols And Standards
IGMP message Actions In response to the IGMP group-specific query for a certain multicast Group-specific query group, the proxy sends the report to the group out of all router ports if the forwarding entry for the group still contains a member port. After receiving a report for a multicast group, the proxy looks up the multicast forwarding table for the forwarding entry for the multicast group.
Page 41: Configuring Basic Igmp Snooping Functions
Task Remarks Enabling IGMP snooping proxying Optional Configuring IGMP Configuring a source IP address for the IGMP messages sent by snooping proxying Optional the proxy Configuring a multicast group filter Optional Configuring multicast source port filtering Optional Enabling dropping unknown multicast data Optional Configuring IGMP report suppression Optional...
Page 42: Enabling Igmp Snooping
Enabling IGMP snooping When you enable IGMP snooping, follow these guidelines: • You must enable IGMP snooping globally before you enable it in a VLAN. After you enable IGMP snooping in a VLAN, do not enable IGMP or PIM on the corresponding •...
Page 43: Configuring Static Multicast Mac Address Entries
Configuring static multicast MAC address entries In Layer-2 multicast, a Layer 2 multicast protocol (such as IGMP snooping) can dynamically add multicast MAC address entries. Or, you can manually configure multicast MAC address entries. Configuration guidelines In system view, the configuration is effective for the specified ports. In interface view or port group •...
Page 44: Setting Aging Timers For Dynamic 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. If the switch receives no IGMP reports for a multicast group on a dynamic member port when the aging timer of the port expires, the switch removes the port from the multicast forwarding entry for that multicast group.
Page 45: 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. Static member ports and static router ports never age out.
Page 46: Enabling Igmp Snooping Fast-Leave Processing
Unlike a static member port, a port that you configure as a simulated member host ages out like a dynamic member port. To configure a port as a simulated member host: Step Command Remarks Enter system view. system-view • Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view: Enter Layer 2 Ethernet...
Page 47: Disabling A Port From Becoming A Dynamic Router Port
Step Command Remarks • Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view: Enter Layer 2 Ethernet interface interface-type interface view, Layer 2 Use either command. interface-number aggregate interface view, or port group view. • Enter port group view: port-group manual port-group-name Enable IGMP snooping...
Page 48: Configuring Igmp Snooping Querier
"IGMP querier." For more information about IGMP querier, see "Configuring IGMP (available only on S5500-EI)." However, a Layer 2 multicast switch does not support IGMP, and therefore cannot send general queries by default. When you enable IGMP snooping querier on a Layer 2 switch in a VLAN where multicast traffic is switched only at Layer 2 and no multicast routers are present, the Layer 2 switch sends IGMP queries, so that multicast forwarding entries can be established and maintained at the data link layer.
Page 49: Configuring The Source Ip Addresses For Igmp Queries
To avoid this problem, when a Layer 2 switch acts as the IGMP snooping querier, H3C recommends you to configure a non-all-zero IP address as the source IP address of IGMP queries.
Page 50: Configuring Igmp Snooping Proxying
IMPORTANT: The source address of IGMP query messages might affect the IGMP querier election within the segment To configure the source IP addresses for IGMP queries: Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Configure the source address igmp-snooping general-query source-ip 0.0.0.0 by default of IGMP general queries.
Page 51: Configuring An Igmp Snooping Policy
To configure the source IP addresses for the IGMP messages that the IGMP snooping proxy sends on behalf of its attached hosts in a VLAN: Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Configure a source IP igmp-snooping report source-ip address for the IGMP The default is 0.0.0.0.
Page 52: Configuring Multicast Source Port Filtering
Step Command Remarks Enter system view. system-view Enter IGMP-snooping view. igmp-snooping By default, no group filter is Configure a multicast group group-policy acl-number [ vlan globally configured. That is, the filter. vlan-list ] hosts in a VLAN can join any valid multicast group.
Page 53: 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 view: interface interface-type Enter Layer 2 Ethernet interface-number interface view or port group Use either command. view. • Enter port group view: port-group manual port-group-name Enable multicast source port...
Page 54: Setting The Maximum Number Of Multicast Groups That A Port Can Join
With the IGMP report suppression function enabled, within each query interval, the Layer 2 switch forwards only the first IGMP report for the multicast group to the Layer 3 device. It does not forward the subsequent IGMP reports for the same multicast group. This helps reduce the number of packets being transmitted over the network.
Page 55: Enabling Multicast Group Replacement
Set the maximum number of By default, the upper limit is 2000 igmp-snooping group-limit limit multicast groups that a port for the S5500-EI switches, and [ vlan vlan-list ] can join. 1000 for the S5500-SI switches. Enabling multicast group replacement For various reasons, the number of multicast groups that the switch or a port joins might exceed the upper limit.
Page 56: Setting The 802.1P Precedence For Igmp Messages
Step Command Remarks • Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view: Enter Layer 2 Ethernet interface interface-type interface view, Layer 2 Use either command. interface-number aggregate interface view, or port group view. • Enter port group view: port-group manual port-group-name Enable multicast group...
Page 57: Enabling The Igmp Snooping Host Tracking Function
• After receiving an IGMP report from a host, the access switch matches the multicast group address and multicast source address carried in the report with the configured policies. If a match is found, the host is allowed to join the multicast group. Otherwise, the join report is dropped by the access switch.
Page 58: Setting The Dscp Value For Igmp Messages
Enabling the IGMP snooping host tracking function in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Enable the IGMP snooping host tracking function in the igmp-snooping host-tracking Disabled by default VLAN. Setting the DSCP value for IGMP messages IPv4 uses an eight-bit ToS field to identify type of service for IP packets.
Page 59: Igmp Snooping Configuration Examples
Task Command Remarks Available in user view. This command works only on an Remove all the dynamic group IGMP snooping–enabled VLAN, reset igmp-snooping group entries of a specified IGMP but not in a VLAN with IGMP { group-address | all } [ vlan snooping group or all IGMP enabled on its VLAN interface.
Page 60 Configuration procedure Configure an IP address and subnet mask for each interface as per Figure 14. (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> system-view [RouterA] multicast routing-enable [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] igmp enable [RouterA-GigabitEthernet1/0/1] pim dm...
Page 61: Static Port Configuration Example
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 62 NOTE: If no static router port is configured, when the path of Switch A—Switch B—Switch C gets blocked, at least one IGMP query-response cycle must be completed before the multicast data can flow to the receivers along the new path of Switch A—Switch C. Namely multicast delivery will be interrupted during this process.
Page 63 # Create VLAN 100, assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3 to this VLAN, and enable IGMP snooping in the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/3 [SwitchA-vlan100] igmp-snooping enable [SwitchA-vlan100] quit # Configure GigabitEthernet 1/0/3 to be a static router port. [SwitchA] interface gigabitethernet 1/0/3 [SwitchA-GigabitEthernet1/0/3] igmp-snooping static-router-port vlan 100 [SwitchA-GigabitEthernet1/0/3] quit...
Page 64 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 2 port.
Page 65: Igmp Snooping Querier Configuration Example
Host port(s):total 2 port. GE1/0/3 GE1/0/5 The output shows that GigabitEthernet 1/0/3 and GigabitEthernet 1/0/5 on Switch C have become static member ports for multicast group 224.1.1.1. IGMP snooping querier configuration example Network requirements As shown in Figure 16, in a Layer 2–only network environment, two multicast sources Source 1 and Source 2 send multicast data to multicast groups 224.1.1.1 and 225.1.1.1 respectively, Host A and Host C are receivers of multicast group 224.1.1.1, and Host B and Host D are receivers of multicast group 225.1.1.1.
Page 66 [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 100 and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/3 # Enable IGMP snooping and the function of dropping unknown multicast traffic in VLAN 100. [SwitchA-vlan100] igmp-snooping enable [SwitchA-vlan100] igmp-snooping drop-unknown # Enable the IGMP snooping querier function in VLAN 100...
Page 67: Igmp Snooping Proxying Configuration Example
Received IGMPv3 reports with right and wrong records:0. Received IGMPv3 specific queries:0. Received IGMPv3 specific sg queries:0. Sent IGMPv3 specific queries:0. Sent IGMPv3 specific sg queries:0. Received error IGMP messages:0. IGMP snooping proxying configuration example Network requirements As shown in Figure 17, Router A runs IGMPv2 and Switch A runs IGMPv2 snooping.
Page 68 [RouterA-GigabitEthernet1/0/2] pim dm [RouterA-GigabitEthernet1/0/2] quit Configure Switch A: # Enable IGMP snooping globally. <SwitchA> system-view [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 100, assign ports GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to this VLAN, and enable IGMP snooping and IGMP snooping proxying in the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/4 [SwitchA-vlan100] igmp-snooping enable...
Page 69: Multicast Source And User Control Policy Configuration Example
# Display information about IGMP multicast groups on Router A. [RouterA] display igmp group Total 1 IGMP Group(s). Interface group report information of VPN-Instance: public net GigabitEthernet1/0/1(10.1.1.1): Total 1 IGMP Group reported Group Address Last Reporter Uptime Expires 224.1.1.1 0.0.0.0 00:00:06 00:02:04 When Host A leaves the multicast group, it sends an IGMP leave message to Switch A.
Page 70 A multicast user control policy is configured on Switch B so that Host A can join or leave only multicast group 224.1.1.1. Figure 18 Network diagram Configuration procedures Configure an IP address and subnet mask for each interface as per Figure 18.
Page 71 [SwitchA-Vlan-interface102] pim dm [SwitchA-Vlan-interface102] quit [SwitchA] interface vlan-interface 104 [SwitchA-Vlan-interface104] pim dm [SwitchA-Vlan-interface104] igmp enable [SwitchA-Vlan-interface104] quit # Create QoS policy policy1 to block multicast flows from Source 2 to 224.1.1.1. [SwitchA] acl number 3001 [SwitchA-acl-adv-3001] rule permit udp source 2.1.1.1 0 destination 224.1.1.1 0 [SwitchA-acl-adv-3001] quit [SwitchA] traffic classifier classifier1 [SwitchA-classifier-classifier1] if-match acl 3001 [SwitchA-classifier-classifier1] quit...
Page 72 [SwitchA] dot1x [SwitchA] interface gigabitethernet 1/0/1 [SwitchA-GigabitEthernet1/0/1] dot1x [SwitchA-GigabitEthernet1/0/1] quit [SwitchA] interface gigabitethernet 1/0/2 [SwitchA-GigabitEthernet1/0/2] dot1x [SwitchA-GigabitEthernet1/0/2] quit Configure Switch B: # Globally enable IGMP snooping. <SwitchB> system-view [SwitchB] igmp-snooping [SwitchB-igmp-snooping] quit # Create VLAN 104, assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3 to this VLAN, and enable IGMP snooping in this VLAN.
Page 73 [SwitchB-isp-domian2] quit [SwitchB] domain default enable domain2 # Globally enable 802.1X and then enable it on GigabitEthernet 1/0/2 and GigabitEthernet 1/0/3 respectively. [SwitchB] dot1x [SwitchB] interface gigabitethernet 1/0/2 [SwitchB-GigabitEthernet1/0/2] dot1x [SwitchB-GigabitEthernet1/0/2] quit [SwitchB] interface gigabitethernet 1/0/3 [SwitchB-GigabitEthernet1/0/3] dot1x [SwitchB-GigabitEthernet1/0/3] quit Configure the RADIUS server: On the RADIUS server, configure the parameters related to Switch A and Switch B.
Page 74: Troubleshooting Igmp Snooping
Assume that Source 2 starts sending multicast traffic to 224.1.1.1. Use the display multicast forwarding-table to display the multicast forwarding table information. # Display information about 224.1.1.1 in the multicast forwarding table on Switch A. [SwitchA] display multicast forwarding-table 224.1.1.1 Multicast Forwarding Table of VPN-Instance: public net Total 1 entry Total 1 entry matched...
Page 75: Configured Multicast Group Policy Fails To Take Effect
Configured multicast group policy fails to take effect Symptom Although a multicast group policy has been configured to allow hosts to join specific multicast groups, the hosts can still receive multicast data addressed to other multicast groups. Analysis The ACL rule is incorrectly configured. •...
Page 76 If PIM is enabled, the switch deletes only its dynamic member ports but not its dynamic router ports. NOTE: On a switch with Layer-3 multicast routing enabled, use the display igmp group port-info command to display Layer-2 port information. If PIM is disabled on the switch, one of the following occurs: If IGMP is disabled, the switch deletes all its dynamic router ports.
Page 77: Configuring Pim Snooping
Configuring PIM snooping Overview Protocol Independent Multicast (PIM) snooping runs on Layer 2 devices. It determines which ports are interested in multicast data by analyzing the received PIM messages, and adds 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 78: Configuring Pim Snooping
For more information about PIM, see "Configuring PIM (available only on the S5500-EI)." Configuring PIM snooping When you configure PIM snooping, follow these guidelines: Before configuring PIM snooping for a VLAN, be sure to enable IGMP snooping globally and •...
Page 79: Displaying And Maintaining Pim Snooping
For more information about the igmp-snooping and igmp-snooping enable commands, see IP Multicast Command Reference. Displaying and maintaining PIM snooping Task Command Remarks display pim-snooping neighbor Display PIM snooping neighbor [ vlan vlan-id ] [ slot slot-number ] Available in any view information.
Page 80 Figure 20 Network diagram Configuration procedure Configure an IP address and subnet mask for each interface according to Figure 20. (Details not shown.) On Router A, enable IP multicast routing, enable PIM-SM on each interface, and configure interface GigabitEthernet 1/0/2 as a C-BSR and C-RP. <RouterA>...
Page 81 [RouterC-GigabitEthernet1/0/1] pim sm [RouterC-GigabitEthernet1/0/1] igmp enable [RouterC-GigabitEthernet1/0/1] quit [RouterC] interface gigabitethernet 1/0/2 [RouterC-GigabitEthernet1/0/2] pim sm Configure Router D in the same way as you configure Router C. (Details not shown.) Configure Switch A: # Enable IGMP snooping globally. <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,...
Page 82: Troubleshooting Pim Snooping
Upstream neighbor: 10.1.1.2 Upstream port: GE1/0/2 Total number of downstream ports: 1 1: GE1/0/4 Expires: 00:01:05, FSM: J The output shows that Switch A will forward the multicast data intended for multicast group 224.1.1.1 to only Router C, and forward the multicast data intended for multicast group 225.1.1.1 to only Router D. Troubleshooting PIM snooping PIM snooping does not work Symptom...
Page 83 messages are suppressed. To solve this problem, disable the join suppression function on all PIM-capable routers that connect to the PIM snooping-capable switch in the VLAN. Solution Use the pim hello-option neighbor-tracking command to enable the neighbor tracking function on the interfaces of PIM routers that connect to the PIM snooping-capable switch.
Page 84: Configuring Multicast Vlans
Configuring multicast VLANs Overview In the traditional multicast programs-on-demand mode shown in Figure 21, 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 85 Figure 22 Sub-VLAN-based multicast VLAN Multicast packets VLAN 10 (Multicast VLAN) VLAN 2 VLAN 2 Receiver VLAN 3 Host A VLAN 4 VLAN 3 Receiver Host B Switch A Router 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 86: Multicast Vlan Configuration Task List
Enable IGMP snooping in the VLAN to be configured as a multicast VLAN. • Configuration guidelines For the S5500-EI switches, you cannot configure multicast VLAN on a device with IP multicast • routing enabled. The VLAN to be configured as a multicast VLAN must exist.
Page 87: Configuring A Port-Based Multicast Vlan
Step Command Remarks Enter system view. system-view Configure the specified VLAN By default, a VLAN is not a as a multicast VLAN and enter multicast-vlan vlan-id multicast VLAN. multicast VLAN view. Configure the specified By default, a multicast VLAN has VLANs as sub-VLANs of the subvlan vlan-list no sub-VLANs.
Page 88: Configuring Multicast Vlan Ports
VLAN or specifying the multicast VLAN on the user ports. These two methods provide the same result. Configuration guidelines For the S5500-EI switches, you cannot configure multicast VLAN on a device with multicast routing • enabled.
Page 89: Displaying And Maintaining Multicast Vlan
To configure multicast VLAN ports in interface view or port group view: Step Command Remarks Enter system view. system-view Configure the specified VLAN By default, a VLAN is not a as a multicast VLAN and enter multicast-vlan vlan-id multicast VLAN. multicast VLAN view.
Page 90 Figure 24 Network diagram Configuration procedure Configure an IP address and subnet mask for each interface as per Figure 24. (Details not shown.) On Router A, enable IP multicast routing, enable PIM-DM on each interface and enable IGMP on the host-side interface GigabitEthernet 1/0/2. <RouterA>...
Page 91 [SwitchA-GigabitEthernet1/0/2] quit # Configure GigabitEthernet 1/0/3 as a trunk port, and assign it to VLAN 4 and VLAN 5. [SwitchA] interface gigabitethernet 1/0/3 [SwitchA-GigabitEthernet1/0/3] port link-type trunk [SwitchA-GigabitEthernet1/0/3] port trunk permit vlan 4 5 [SwitchA-GigabitEthernet1/0/3] quit # Create VLAN 10, assign GigabitEthernet 1/0/1 to this VLAN and enable IGMP snooping in the VLAN.
Page 92 Multicast vlan 10 subvlan list: vlan 2-5 port list: no port # Display the IGMP snooping multicast group information on Switch A. [SwitchA] display igmp-snooping group Total 5 IP Group(s). Total 5 IP Source(s). Total 5 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):2.
Page 93: Port-Based Multicast Vlan Configuration Example
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). GE1/0/3 MAC group(s): MAC group address:0100-5e01-0101 Host port(s):total 1 port(s). GE1/0/3 Vlan(id):5. Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s).
Page 94 and Host C are receivers of the multicast group, and the hosts belong to VLAN 2 through VLAN 4 respectively. Configure the port-based multicast VLAN feature on Switch A so that Router A just sends multicast data to Switch A through the multicast VLAN and Switch A forwards the multicast data to the receivers that belong to different user VLANs.
Page 95 [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 The configuration for VLAN 3 and VLAN 4 is similar. (Details not shown.) # Configure GigabitEthernet 1/0/2 as a hybrid port.
Page 96 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. IP group address:224.1.1.1 (0.0.0.0, 224.1.1.1): Host port(s):total 3 port(s).
Page 97: Configuring Multicast Routing And Forwarding (Available Only On The S5500-Ei)
Configuring multicast routing and forwarding (available only on the S5500-EI) 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.
Page 98 • Static multicast routing table—Contains the RPF routing information defined by the user through static configuration. MBGP multicast routing table and static multicast routing table are used for RPF check rather than multicast routing. When a router performs an RPF check, it searches its unicast routing table, MBGP routing table, and static multicast routing table at the same time.
Page 99 For more information about the concepts of SPT, RPT, source-side RPT, RP, and BSR, see "Configuring PIM (available only on the S5500-EI)." RPF check implementation in multicast Implementing an RPF check on each received multicast data packet would be a big burden to the router.
Page 100: Static Multicast Routes
If the corresponding (S, G) entry exists, but the interface that received the packet is not the incoming interface in the multicast forwarding table, the multicast packet undergoes an RPF check. If the RPF interface is the incoming interface of the (S, G) entry, it indicates that the (S, G) entry is correct but the packet arrived from a wrong path.
Page 101 Changing an RPF route Typically, the topology structure of a multicast network is the same as that of a unicast network, and multicast traffic follows the same transmission path as unicast traffic does. You can configure a static multicast route for a given multicast source to change the RPF route to create a transmission path for multicast traffic that is different from that for unicast traffic.
Page 102: Multicast Forwarding Across Unicast Subnets
Figure 28 Creating an RPF route Multicast Routing Table Static on Switch C OSPF domain Source/Mask Interface RPF neighbor/Mask 192.168.0.0/24 Vlan-int10 1.1.1.1/24 Receiver Switch D Multicast Routing Table Static on Switch D Vlan-int20 Source/Mask Interface RPF neighbor/Mask 2.2.2.1/24 192.168.0.0/24 Vlan-int20 2.2.2.2/24 Source RIP domain...
Page 103: Multicast Traceroute
Figure 29 Multicast data transmission through a tunnel Unicast router Unicast router Multicast router Multicast router Tunnel Switch A Switch B Source Receiver Unicast router Unicast router As shown in Figure 29, with tunnel established between Switch A and Switch B, Switch A encapsulates multicast data in unicast IP packets, which unicast routers then forward to Switch B across the tunnel.
Page 104: Configuration Task List
Process of multicast traceroute The querier sends a query to the last-hop router. After receiving the query, the last-hop router turns the query packet into a request packet by adding a response data block (which contains its interface addresses and packet statistics) to the end of the packet.
Page 105: Configuring Multicast Routing And Forwarding
Enabling IP multicast routing in a VPN instance Step Command Remarks Enter system view. system-view Create a VPN instance and ip vpn-instance vpn-instance-name enter VPN instance view. Configure a route distinguisher (RD) for the route-distinguisher route-distinguisher No RD is configured by default. VPN instance.
Page 106: Configuring A Multicast Routing Policy
Step Command Remarks Delete static delete ip rpf-route-static [ vpn-instance Optional. multicast routes. vpn-instance-name ] Configuring a multicast routing policy You can configure the router to determine the RPF route based on the longest match principle. For more information about RPF route selection, see "RPF check process."...
Page 107: Configuring The Multicast Forwarding Table Size
multicast groups in the specified range. If the destination address of a multicast packet matches the set boundary condition, the packet will not be forwarded. After you configure an interface as a multicast boundary, the interface can no longer forward multicast packets—including packets sent from the local device—or receive multicast packets.
Page 108: Tracing A Multicast Path
Step Command Remarks Configure the maximum number of downstream nodes Optional. multicast forwarding-table for a single multicast downstream-limit limit 128 by default. forwarding entry. Configuring the multicast forwarding table size in a VPN instance Step Command Remarks Enter system view. system-view Enter VPN instance view.
Page 109 Task Command Remarks display multicast [ all-instance | vpn-instance vpn-instance-name ] boundary [ group-address [ mask | Display multicast boundary Available in any mask-length ] ] [ interface interface-type information. view. interface-number ] [ | { begin | exclude | include } regular-expression ] display multicast [ all-instance | vpn-instance vpn-instance-name ] forwarding-table [ source-address...
Page 110: Configuration Examples
For more information about designated forwarder (DF), see "Configuring PIM (available only on the S5500-EI)." Configuration examples Changing an RPF route Network requirements PIM-DM runs in the network. All switches in the network support multicast. Switch A, Switch B, and Switch C run OSPF.
Page 111 Figure 30 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 30.
Page 112: Creating An Rpf Route
[SwitchA-Vlan-interface200] quit [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] pim dm [SwitchA-Vlan-interface102] quit [SwitchA] interface vlan-interface 103 [SwitchA-Vlan-interface103] pim dm [SwitchA-Vlan-interface103] quit # Enable IP multicast routing and PIM-DM on Switch C in the same way. (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 113 Figure 31 Network diagram Configuration procedure Configure the IP address and subnet mask for each interface as per Figure 31. (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 114: Multicast Forwarding Over A Tunnel
[SwitchB] display multicast rpf-info 50.1.1.100 [SwitchC] display multicast rpf-info 50.1.1.100 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 115 Figure 32 Network diagram Configuration procedure Configure the IP address and subnet mask for each interface as per Figure 32. (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 116: Configure Ospf
# Disable STP, LLDP and NDP on interface GigabitEthernet 1/0/3 of Switch C, and add the interface to service loopback group 1. GigabitEthernet 1/0/3 does not belong to VLAN 200 or VLAN 102. [SwitchC] interface gigabitethernet 1/0/3 [SwitchC-GigabitEthernet1/0/3] undo stp enable [SwitchC-GigabitEthernet1/0/3] undo ndp enable [SwitchC-GigabitEthernet1/0/3] undo lldp enable [SwitchC-GigabitEthernet1/0/3] port service-loopback group 1...
Page 117 Enable IP multicast routing, PIM-DM, and IGMP: # Enable multicast routing on Switch A and enable PIM-DM on each interface. [SwitchA] multicast routing-enable [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] pim dm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim dm [SwitchA-Vlan-interface101] quit [SwitchA] interface tunnel 0 [SwitchA-Tunnel0] pim dm [SwitchA-Tunnel0] quit...
Page 118: Troubleshooting Multicast Routing And Forwarding
1: Vlan-interface200 Protocol: igmp, UpTime: 00:04:25, Expires: never (10.1.1.100, 225.1.1.1) Protocol: pim-dm, Flag: ACT UpTime: 00:06:14 Upstream interface: Tunnel0 Upstream neighbor: 50.1.1.1 RPF prime neighbor: 50.1.1.1 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface200 Protocol: pim-dm, UpTime: 00:04:25, Expires: never 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.
Page 119: Multicast Data Fails To Reach Receivers
Multicast data fails to reach receivers Symptom The multicast data can reach some routers but fails to reach the last-hop router. Analysis If a multicast forwarding boundary has been configured through the multicast boundary command, any multicast packet will be kept from crossing the boundary. Solution Use the display pim routing-table command to verify that the corresponding (S, G) entries exist on the router.
Page 120: Configuring Igmp (Available Only On The S5500-Ei)
Configuring IGMP (available only on the S5500-EI) 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.
Page 121 In IGMPv1, the designated router (DR) elected by the working multicast routing protocol (such as PIM) serves as the IGMP querier. For more information about DR, see "Configuring PIM (available only on the S5500-EI)." Figure 33 IGMP queries and reports IP network Router A...
Page 122: Enhancements In Igmpv2
When the multicast data addressed to G1 or G2 reaches an IGMP router, because the (*, G1) and (*, G2) multicast forwarding entries exist on the IGMP router, the router forwards the multicast data to the local subnet, and then the receivers on the subnet receive the data. IGMPv1 does not specifically define a leave group message (often called a "leave message").
Page 123: Enhancements In Igmpv3
If the querier receives a membership report for the group within the maximum response time, it will maintain the memberships of the group. Otherwise, the querier will assume that no hosts on the subnet are still interested in multicast traffic to that group and will stop maintaining the memberships of the group.
Page 124: Igmp Ssm Mapping
multicast data that Source 2 sends to multicast group G—denoted as (S2, G). Thus, only multicast data from Source 1 will be delivered to Host B. Enhancements in query and report capabilities Query message carrying the source addresses IGMPv3 supports not only general queries (feature of IGMPv1) and group-specific queries (feature of IGMPv2), but also group-and-source-specific queries.
Page 125: Igmp Proxying
The IGMP SSM mapping feature does not process IGMPv3 reports. For more information about the SSM group range, see "Configuring PIM (available only on the S5500-EI)." IGMP proxying In some simple tree-shaped topologies, it is not necessary to configure complex multicast routing...
Page 126 devices. With IGMP proxying configured, the device serves as a proxy for the downstream hosts to send IGMP messages, maintain group memberships, and implement multicast forwarding based on the memberships. In this case, each boundary device is a host but no longer a PIM neighbor to the upstream device.
Page 127: Igmp Support For Vpns
IGMP support for VPNs IGMP maintains group memberships on a per-interface base. After receiving an IGMP message on an interface, IGMP processes the packet within the VPN that the interface belongs to. If IGMP that runs in a VPN needs to exchange information with another multicast protocol, it passes the information only to the protocol that runs in this VPN.
Page 128: 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 129: Configuring Igmp Versions
PIM-SM enabled, it must be a PIM-SM DR. If the interface is enabled with IGMP but not with PIM-SM, it must be an IGMP querier. For more information about PIM-SM and DR, see "Configuring PIM (available only on the S5500-EI)"...
Page 130: Configuring A Multicast Group Filter
• A static member port does not respond to queries from the IGMP querier. When you configure a port as a static member port or remove this configuration on the port, the port does not unsolicitedly send any IGMP report or IGMP leave message. In other words, the port is not a real member of the multicast group or the multicast source and group.
Page 131: Adjusting Igmp Performance
Step Command Remarks Configure the maximum number of multicast groups igmp group-limit limit 2000 by default. that the interface can join. NOTE: This configuration takes effect for dynamically joined multicast groups but not for statically configured multicast groups. Adjusting IGMP performance For the configuration tasks described in this section: The configuration in IGMP view is effective on all interfaces, whereas the configuration in interface •...
Page 132: Configuring Igmp Query And Response Parameters
An IGMP message is processed differently depending on whether it carries the Router-Alert option in the IP header: • By default, for the consideration of compatibility, the switch does not verify the Router-Alert option but processes all the IGMP messages that it received. In this case, IGMP messages are directly passed to the upper-layer protocol, whether or not the IGMP messages carry the Router-Alert option.
Page 133 After startup, the IGMP querier periodically sends IGMP general queries at the IGMP general query interval to check for multicast group members on the network. You can modify the IGMP general query interval based on actual condition of the network. The IGMPv2 querier sends IGMP group-specific queries at the IGMP last-member query interval when it receives an IGMP leave message.
Page 134 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 135: Configuring Igmp Fast-Leave Processing
Configuring IGMP fast-leave processing In some applications, such as ADSL dial-up networking, only one multicast receiver host is attached to a port of the IGMP querier. To allow fast response to the leave messages of the host when it switches frequently from one multicast group to another, you can enable IGMP fast-leave processing on the IGMP querier.
Page 136: Enabling The Igmp Host Tracking Function
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. You can monitor and manage the member hosts according to the recorded information. Enabling the IGMP host tracking function globally Step Command...
Page 137: 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 138: Configuring Igmp Proxying
Configuring IGMP proxying Before you configure the IGMP proxying feature, complete the following tasks: 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 139: Configuring Multicast Forwarding On A Downstream Interface
Configuring multicast forwarding on a downstream interface Only queriers can forward multicast traffic but non-queriers have no multicast forwarding capabilities. This design helps avoid duplicate multicast flows. It is the same on IGMP proxy switches. Only the downstream interfaces acting as a querier can forward multicast traffic to downstream hosts. However, when a downstream interface of a proxy switch fails to win the querier election, you must enable multicast forwarding on this interface.
Page 140 Task Command display igmp host interface interface-type interface-number Display information about the hosts group group-address [ source Available in any view. tracked by IGMP on an interface. source-address ] [ | { begin | exclude | include } regular-expression ] display igmp host port-info vlan vlan-id group group-address Display information about the hosts...
Page 141: Igmp Configuration Examples
Task Command reset igmp [ all-instance | vpn-instance vpn-instance-name ] Available in user view. group { all | interface Remove all the dynamic IGMP interface-type interface-number This command cannot remove group entries of IGMP groups. { all | group-address [ mask { mask static IGMP group entries.
Page 142 Figure 37 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 37.
Page 143: Ssm Mapping Configuration Example
[SwitchB-Vlan-interface201] pim dm [SwitchB-Vlan-interface201] quit # 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...
Page 144 Figure 38 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 145 [SwitchD-Vlan-interface104] pim sm [SwitchD-Vlan-interface104] quit # Enable IP multicast routing on Switch A, and enable PIM-SM on each interface. <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...
Page 146: Igmp Proxying Configuration Example
# Display the IGMP group information created based on the IGMP SSM mappings on Switch D. [SwitchD] display igmp ssm-mapping group Total 1 IGMP SSM-mapping Group(s). Interface group report information of VPN-Instance: public net Vlan-interface400(133.133.4.2): Total 1 IGMP SSM-mapping Group reported Group Address Last Reporter Uptime...
Page 147 Figure 39 Network diagram Configuration procedure Configure the IP address and subnet mask of each interface as per Figure 39. (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 148: Troubleshooting Igmp
Multicast routing on this interface: enabled Require-router-alert: disabled 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 of VPN-Instance: public net Vlan-interface100(192.168.1.1): Total 1 IGMP Groups reported Group Address Last Reporter Uptime...
Page 149: Inconsistent Memberships On Routers On The Same Subnet
Use the display current-configuration interface command to verify that no ACL rule has been configured to restrict the host from joining the multicast group G. If the host is restricted from joining the multicast group G, the ACL rule must be modified to allow receiving the reports for the multicast group G.
Page 150: Configuring Pim (Available Only On The S5500-Ei)
Configuring PIM (available only on the S5500-EI) 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), intermediate system to intermediate system (IS-IS), or border gateway protocol (BGP).
Page 151 forwarding when the pruned state times out. Data is then flooded again down these branches, and then the branches are pruned again. • When a new receiver on a previously pruned branch joins a multicast group, to reduce the join latency, PIM-DM uses a graft mechanism to resume data forwarding to that branch.
Page 152 Figure 40 SPT building 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.
Page 153: Pim-Sm Overview
Figure 41 Assert mechanism As shown in Figure 41, after Router A and Router B receive an (S, G) packet from the upstream node, they both forward the packet to the local subnet. As a result, the downstream node Router C receives two identical multicast packets, and both Router A and Router B, on their own downstream interface, receive a duplicate packet forwarded by the other.
Page 154 An RPT is rooted at a router in the PIM domain as the common node, or rendezvous point (RP), through which the multicast data travels along the RPT and reaches the receivers. • When a receiver is interested in the multicast data addressed to a specific multicast group, the router connected to this receiver sends a join message to the RP that corresponds to that multicast group.
Page 155 For more information about IGMP, see "Configuring IGMP (available only on the S5500-EI)." Figure 42 DR election Receiver Source Receiver Hello message Register message Join message As shown in Figure 42, 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.
Page 156 As shown in Figure 43, each C-RP periodically unicasts its advertisement messages (C-RP-Adv messages) to the BSR. An advertisement message contains the address of the advertising C-RP and the multicast group range to which it is designated. The BSR collects these advertisement messages and organizes the C-RP information into an RP-set, which is a database of mappings between multicast groups and RPs.
Page 157 Value Description Modulo operator, which gives the remainder of an integer division RPT building Figure 44 RPT building in a PIM-SM domain As shown in Figure 44, 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 158 Figure 45 Multicast source registration Host A Source Receiver Host B Server Receiver Join message Register message Host C Multicast packets As shown in Figure 45, the multicast source registers with the RP as follows: The multicast source S sends the first multicast packet to 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 159: Bidir-Pim Overview
• Multicast packets are delivered along a path that might not be the shortest one. An increase in multicast traffic adds a great burden on the RP, increasing the risk of failure. • To solve the issues, PIM-SM allows an RP or the DR at the receiver side to initiate the switchover to SPT. The RP initiates the switchover to SPT.
Page 160 • RP discovery DF election • Bidirectional RPT building • Neighbor discovery BIDIR-PIM uses the same neighbor discovery mechanism as PIM-SM does. For more information, see "Neighbor discovery." RP discovery BIDIR-PIM uses the same RP discovery mechanism as PIM-SM does. For more information, see "RP discovery."...
Page 161 Figure 46 DF election As shown in Figure 46, without the DF election mechanism, both Router B and Router C can receive multicast packets from Route A, and they might both forward the packets to downstream routers on the local subnet. As a result, the RP (Router E) receives duplicate multicast packets. With the DF election mechanism, once receiving the RP information, Router B and Router C initiate a DF election process for the RP: Router B and Router C multicast DF election messages to all PIM routers (224.0.0.13).
Page 162 Figure 47 RPT building at the receiver side Source Receiver Host A Server B Source Receiver Host B Server A Receiver Join message Receiver-side RPT Multicast packets Host C As shown in Figure 47, the process for building a receiver-side RPT is similar to that for building an RPT in PIM-SM: When a receiver joins multicast group G, it uses an IGMP message to inform the directly connected router.
Page 163: Administrative Scoping Overview
Figure 48 RPT building at the multicast source side Source Receiver Host A Server B Source Receiver Host B Server A Receiver Source-side RPT Multicast packets Host C As shown in Figure 48, the process for building a source-side RPT is relatively simple: When a multicast source sends multicast packets to multicast group G, the DF in each network segment unconditionally forwards the packets to the RP.
Page 164 To implement refined management, you can divide a PIM-SM domain or BIDIR-PIM domain into one global scope zone and multiple administratively scoped zones (admin-scope zones). This is called the "administrative scoping mechanism." The administrative scoping mechanism effectively releases stress on the management in a single-BSR domain and enables provision of zone-specific services through private group addresses.
Page 165: Pim-Ssm Overview
As shown in Figure 49, for the multicast groups in a specific group address range, the admin-scope zones must be geographically separated and isolated. A router cannot belong to multiple admin-scope zones. In other words, different admin-scope zones contain different routers. However, the global-scoped zone includes all routers in the PIM-SM domain or BIDIR-PIM domain.
Page 166 The working mechanism of PIM-SSM is summarized as follows: Neighbor discovery • DR election • SPT building • Neighbor discovery PIM-SSM uses the same neighbor discovery mechanism as in PIM-DM and PIM-SM. See "Neighbor discovery." DR election PIM-SSM uses the same DR election mechanism as in PIM-SM. See "DR election."...
Page 167: Relationships Among Pim Protocols
Figure 52 Relationships among PIM protocols For more information about IGMP SSM mapping, see "Configuring IGMP (available only on the S5500-EI)." PIM support for VPNs To support PIM for VPNs, a multicast router that runs PIM maintains an independent set of PIM neighbor table, multicast routing table, BSR information, and RP-set information for each VPN.
Page 168: Configuring Pim-Dm
• RFC 4601, Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification (Revised) RFC 5015, Bidirectional Protocol Independent Multicast (BIDIR-PIM) • RFC 5059, Bootstrap Router (BSR) Mechanism for Protocol Independent Multicast (PIM) • RFC 4607, Source-Specific Multicast for IP • • Draft-ietf-ssm-overview-05, An Overview of Source-Specific Multicast (SSM) Configuring PIM-DM PIM-DM configuration task list Task...
Page 169: Enabling State-Refresh Capability
Enabling PIM-DM globally on the public network Step Command Remarks Enter system view. system-view Enable IP multicast routing. multicast routing-enable Disabled by default. interface interface-type Enter interface view. interface-number Enable PIM-DM. pim dm Disabled by default. Enabling PIM-DM in a VPN instance Step Command Description...
Page 170: Configuring State-Refresh Parameters
Step Command Remarks interface interface-type Enter interface view. interface-number Optional Enable the state-refresh pim state-refresh-capable capability. Enabled by default 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, and some of them might be duplicated messages.
Page 171: Configuring Pim-Sm
To configure the graft retry period: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Optional Configure the graft retry pim timer graft-retry interval period. 3 seconds by default For more information about the configuration of other timers in PIM-DM, see "Configuring PIM common timers."...
Page 172: Enabling Pim-Sm
• Configure any unicast routing protocol so that all devices in the domain are interoperable at the network layer. • Determine the IP address of a static RP and the ACL rule defining the range of multicast groups to which the static RP is designated. Determine the C-RP priority and the ACL rule defining the range of multicast groups to which each •...
Page 173: Configuring An Rp
Enabling PIM-SM in a VPN instance Step Command Description Enter system view. system-view Create a VPN instance and ip vpn-instance vpn-instance-name enter VPN instance view. Configure an RD for the VPN route-distinguisher Not configured by default. instance. route-distinguisher Enable IP multicast routing. multicast routing-enable Disabled by default.
Page 174 Then, the other routers in the network calculate the mappings between specific group ranges and the corresponding RPs based on the RP-set. H3C recommends you to configure C-RPs on backbone routers. To guard against C-RP spoofing, you must configure a legal C-RP address range and the range of multicast groups to which the C-RP is designated on the BSR.
Page 175: Configuring A Bsr
Step Command Remarks Enable auto-RP. auto-rp enable Disabled by default Configuring C-RP timers globally To enable the BSR to distribute the RP-set information within the PIM-SM domain, C-RPs must periodically send C-RP-Adv messages to the BSR. The BSR learns the RP-set information from the received messages, and encapsulates its own IP address together with the RP-set information in its bootstrap messages.
Page 176 PIM routers to make sure the next hop to a C-BSR is a tunnel interface. Otherwise, RPF check is affected. For more information about static multicast routes, see "Configuring multicast routing and forwarding (available only on the S5500-EI)." To configure a C-BSR: Step Command Remarks Enter system view.
Page 177 Configuring a PIM domain border As the administrative core of a PIM-SM domain, the BSR sends the collected RP-set information in the form of bootstrap messages to all routers in the PIM-SM domain. A PIM domain border is a bootstrap message boundary. Each BSR has its specific service scope. A number of PIM domain border interfaces partition a network into different PIM-SM domains.
Page 178 Step Command Remarks Optional. Configure the C-BSR priority. c-bsr priority priority By default, the C-BSR priority is 64. Configuring C-BSR timers The BSR election winner multicasts its own IP address and RP-set information through bootstrap messages within the entire zone to which it is designated. The BSR floods bootstrap messages throughout the network at the interval of BS (BSR state) period.
Page 179: Configuring Administrative Scoping
message exceeds the maximum transmission unit (MTU). In respect of such IP fragmentation, loss of a single IP fragment leads to unavailability of the entire message. Semantic fragmentation of BSMs can solve this issue. When a BSM exceeds the MTU, it is split to multiple bootstrap message fragments (BSMFs).
Page 180 Step Command Remarks Enter system view. system-view Enter public network PIM view pim [ vpn-instance or VPN instance PIM view. vpn-instance-name ] Enable administrative c-bsr admin-scope Disabled by default scoping. Configuring an admin-scope zone boundary ZBRs form the boundary of each admin-scope zone. Each admin-scope zone maintains a BSR, which provides services for a specific multicast group range.
Page 181: Configuring Multicast Source Registration
• Configure C-BSRs for each admin-scope zone Perform the following configuration on the routers that you want to configure as C-BSRs in admin-scope zones. To configure a C-BSR for an admin-scope zone: Step Command Remarks Enter system view. system-view Enter public network PIM view pim [ vpn-instance or VPN instance PIM view.
Page 182: Disabling The Switchover To Spt
multicast data from the multicast source along the SPT, the RP sends a register-stop message to the source-side DR. After receiving this message, the DR stops sending register messages encapsulated with multicast data and starts a register-stop timer. Before the register-stop timer expires, the DR sends a null register message (a register message without encapsulated multicast data) to the RP.
Page 183: Configuring Bidir-Pim
Step Command Remarks Enter public network PIM view pim [ vpn-instance or VPN instance PIM view. vpn-instance-name ] Optional. spt-switch-threshold infinity By default, the device switches to the Disable the switchover to SPT. [ group-policy acl-number SPT immediately after it receives the [ order order-value] ] first multicast packet.
Page 184: Enabling Pim-Sm
• Determine the legal C-RP address range and the ACL that defines the range of multicast groups to which the C-RP is designated. • Determine the C-RP-Adv interval. Determine the C-RP timeout. • Determine the C-BSR priority. • Determine the hash mask length. •...
Page 185: Enabling Bidir-Pim
Step Command Remarks Enable PIM-SM. pim sm Disabled by default. For more information about the ip vpn-instance, route-distinguisher, and ip binding vpn-instance commands, see IP Routing Command Referenc e . Enabling BIDIR-PIM Perform this configuration on all routers in the BIDIR-PIM domain. To enable BIDIR-PIM: Step Command...
Page 186 Then, the other routers in the network calculate the mappings between specific group ranges and the corresponding RPs based on the RP-set. H3C recommends that you configure C-RPs on backbone routers. To guard against C-RP spoofing, configure a legal C-RP address range and the range of multicast groups to which the C-RP is designated on the BSR.
Page 187: Configuring A Bsr
Configuring C-RP timers globally To enable the BSR to distribute the RP-set information within the BIDIR-PIM domain, C-RPs must periodically send C-RP-Adv messages to the BSR. The BSR learns the RP-set information from the received messages, and encapsulates its own IP address together with the RP-set information in its bootstrap messages.
Page 188 PIM routers to make sure the next hop to a C-BSR is a tunnel interface. Otherwise, RPF check is affected. For more information about static multicast routes, see "Configuring multicast routing and forwarding (available only on the S5500-EI)." To configure a C-BSR: Step Command Remarks Enter system view.
Page 189 Configuring a BIDIR-PIM domain border As the administrative core of a BIDIR-PIM domain, the BSR sends the collected RP-Set information in the form of bootstrap messages to all routers in the BIDIR-PIM domain. A BIDIR-PIM domain border is a bootstrap message boundary. Each BSR has its specific service scope. A number of BIDIR-PIM domain border interfaces partition a network into different BIDIR-PIM domains.
Page 190 Step Command Remarks Optional. Configure the C-BSR priority. c-bsr priority priority 64 by default. Configuring C-BSR timers The BSR election winner multicasts its own IP address and RP-Set information through bootstrap messages within the entire zone to which it is designated. The BSR floods bootstrap messages throughout the network at the interval of BS (BSR state) period.
Page 191: Configuring Administrative Scoping
if the message exceeds the MTU. In respect of such IP fragmentation, loss of a single IP fragment leads to unavailability of the entire message. Semantic fragmentation of BSMs can solve this issue. When a BSM exceeds the MTU, it is split to multiple bootstrap message fragments (BSMFs).
Page 192 Step Command Remarks Enter system view. system-view Enter public network PIM view pim [ vpn-instance or VPN instance PIM view. vpn-instance-name ] Enable administrative c-bsr admin-scope Disabled by default scoping. Configuring an admin-scope zone boundary The boundary of each admin-scope zone is formed by ZBRs. Each admin-scope zone maintains a BSR, which provides services for a specific multicast group range.
Page 193: Configuring Pim-Ssm
• Configure C-BSRs for each admin-scope zone Perform the following configuration on the routers that you want to configure as C-BSRs in admin-scope zones. To configure a C-BSR for an admin-scope zone: Step Command Remarks Enter system view. system-view Enter public network PIM view pim [ vpn-instance or VPN instance PIM view.
Page 194: Configuration Prerequisites
Configuration prerequisites Before you configure PIM-SSM, complete the following tasks: • Configure any unicast routing protocol so that all devices in the domain are interoperable at the network layer. • Determine the SSM group range. Enabling PIM-SM The implementation of the SSM model is based on some subsets of PIM-SM. Therefore, you must enable PIM-SM before configuring PIM-SSM.
Page 195: Configuring The Ssm Group Range
For more information about the ip vpn-instance, route-distinguisher, and ip binding vpn-instance commands, see IP Routing Command Referenc e . Configuring the SSM group range As for whether the information from a multicast source is delivered to the receivers based on the PIM-SSM model or the PIM-SM model, this depends on whether the group address in the (S, G) channel subscribed by the receivers falls into the SSM group range.
Page 196: Configuration Prerequisites
Task Remarks 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 Configuring PIM to work with BFD Optional Setting the DSCP value for PIM messages Optional Configuration prerequisites Before you configure PIM common features, complete the following tasks:...
Page 197: Configuring A Hello Message Filter
words, PIM routers can act as multicast data filters. These filters can help implement traffic control on one hand, and control the information available to receivers downstream to enhance data security on the other hand. Generally, a smaller distance from the filter to the multicast source results in a more remarkable filtering effect.
Page 198 • DR_Priority (for PIM-SM only)—Priority for DR election. The device with the highest priority wins the DR election. You can configure this parameter on all the routers in a multi-access network directly connected to multicast sources or receivers. Holdtime—The timeout time of PIM neighbor reachability state. When this timer times out, if the •...
Page 199: Configuring The Prune Delay
Step Command Remarks Optional. Configure the prune override hello-option override-interval interval. interval 2500 milliseconds by default. Disable join suppression. hello-option neighbor-tracking Enabled by default. Configuring hello options on an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Optional.
Page 200: Configuring Pim Common Timers
Configuring PIM common timers PIM routers discover PIM neighbors and maintain PIM neighboring relationships with other routers by periodically sending out hello messages. After receiving a hello message, a PIM router waits a random period, which is smaller than the maximum delay between hello messages, before sending a hello message.
Page 201: Configuring Join/Prune Message Sizes
Step Command Remarks interface interface-type Enter interface view. interface-number Optional. Configure the hello interval. pim timer hello interval 30 seconds by default. Optional. Configure the maximum delay pim triggered-hello-delay interval between hello messages. 5 seconds by default. Optional. Configure the join/prune pim timer join-prune interval interval.
Page 202: Setting The Dscp Value For Pim Messages
If the DR fails, a new DR election process will start after the DR is aged out. However, it might take a long period of time. To start a new DR election process immediately after the original DR fails, enable PIM to work with Bidirectional Forwarding Detection (BFD) on a multi-access network to detect failures of the links among PIM neighbors.
Page 203 Task Command Remarks display pim [ all-instance | vpn-instance vpn-instance-name ] Display the information of unicast claimed-route [ source-address ] [ | Available in any view routes used by PIM. { begin | exclude | include } regular-expression ] display pim [ all-instance | vpn-instance vpn-instance-name ] control-message counters [ message-type { probe | register |...
Page 204: Pim Configuration Examples
Task Command Remarks display pim [ all-instance | vpn-instance vpn-instance-name ] routing-table [ group-address [ mask { mask-length | mask } ] | source-address [ mask { mask-length | mask } ] | Display the content of the PIM incoming-interface [ interface-type Available in any view routing table.
Page 205 Figure 53 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-int103 192.168.1.1/24 Vlan-int103 192.168.1.2/24 Switch B Vlan-int200 10.110.2.1/24 Vlan-int101 192.168.2.2/24 Vlan-int101 192.168.2.1/24 Vlan-int102 192.168.3.2/24 Switch C Vlan-int200 10.110.2.2/24 Vlan-int102 192.168.3.1/24 Configuration procedure Configure the IP address and subnet mask for each interface as per Figure...
Page 206 #Enable IP multicast routing, IGMP and PIM-DM on Switch B and Switch C in the same way. (Details not shown.) # Enable IP multicast routing on Switch D, and enable PIM-DM on each interface. <SwitchD> system-view [SwitchD] multicast routing-enable [SwitchD] interface vlan-interface 300 [SwitchD-Vlan-interface300] pim dm [SwitchD-Vlan-interface300] quit [SwitchD] interface vlan-interface 103...
Page 207: Pim-Sm Non-Scoped Zone Configuration Example
Total 1 (*, G) entry; 1 (S, G) entry (*, 225.1.1.1) Protocol: pim-dm, Flag: WC UpTime: 00:04:25 Upstream interface: NULL Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: igmp, UpTime: 00:04:25, Expires: never (10.110.5.100, 225.1.1.1) Protocol: pim-dm, Flag: ACT UpTime: 00:06:14...
Page 208 Host A and Host C are multicast receivers in two stub networks. VLAN-interface 105 on Switch D and VLAN-interface 102 on Switch E act as C-BSRs and C-RPs. The C-BSR on Switch E has a higher priority. The multicast group range to which the C-RP is designated is 225.1.1.0/24.
Page 209 # Enable IP multicast routing on Switch A, enable IGMP on VLAN-interface 100, and enable PIM-SM on each interface. <SwitchA> system-view [SwitchA] multicast routing-enable [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] igmp enable [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 102...
Page 210 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 VPN-Instance: public net 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 211 Scope: Not scoped 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 VPN-Instance: public net 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...
Page 212 (10.110.5.100, 225.1.1.0) RP: 192.168.9.2 Protocol: pim-sm, Flag: SPT ACT UpTime: 00:00:42 Upstream interface: Vlan-interface101 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.
Page 213: Pim-Sm Admin-Scope Zone Configuration Example
PIM-SM admin-scope zone configuration example Network requirements As shown in Figure 55, receivers receive VOD information through multicast. The entire PIM-SM domain is divided into admin-scope zone 1, admin-scope zone 2, and the global zone. Switch B, Switch C, and Switch D are ZBRs of these three domains respectively.
Page 214 Figure 55 Network diagram Device Interface IP address Device Interface IP address Switch A Vlan-int100 192.168.1.1/24 Switch D Vlan-int104 10.110.4.2/24 Vlan-int101 10.110.1.1/24 Vlan-int108 10.110.7.1/24 Switch B Vlan-int200 192.168.2.1/24 Vlan-int107 10.110.8.1/24 Vlan-int101 10.110.1.2/24 Switch E Vlan-int400 192.168.4.1/24 Vlan-int103 10.110.2.1/24 Vlan-int105 10.110.5.2/24 Vlan-int102 10.110.3.1/24 Vlan-int108...
Page 215 # Enable IP multicast routing and administrative scoping on Switch A, enable IGMP on VLAN-interface 100, and enable PIM-SM on each interface. <SwitchA> system-view [SwitchA] multicast routing-enable [SwitchA] pim [SwitchA-pim] c-bsr admin-scope [SwitchA-pim] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] igmp enable [SwitchA-Vlan-interface100] pim sm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 101...
Page 216 # 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 boundary 239.0.0.0 8 [SwitchC-Vlan-interface103] quit [SwitchC] interface vlan-interface 106 [SwitchC-Vlan-interface106] multicast boundary 239.0.0.0 8 [SwitchC-Vlan-interface106] quit # On Switch D, configure VLAN-interface 107 to be the boundary of admin-scope zone 2.
Page 217 VPN-Instance: public net Elected BSR Address: 10.110.9.1 Priority: 64 Hash mask length: 30 State: Accept Preferred Scope: Global Uptime: 00:01:45 Expires: 00:01:25 Elected BSR Address: 10.110.1.2 Priority: 64 Hash mask length: 30 State: Elected Scope: 239.0.0.0/8 Uptime: 00:04:54 Next BSR message scheduled at: 00:00:06 Candidate BSR Address: 10.110.1.2 Priority: 64 Hash mask length: 30...
Page 218 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 VPN-Instance: public net Elected BSR Address: 10.110.9.1 Priority: 64 Hash mask length: 30 State: Elected Scope: Global...
Page 219: Bidir-Pim Configuration Example
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. [SwitchF] display pim rp-info VPN-Instance: public net PIM-SM BSR RP information: Group/MaskLen: 224.0.0.0/4...
Page 220 Figure 56 Network diagram Device Interface IP address Device Interface IP address Switch A Vlan-int100 192.168.1.1/24 Switch D Vlan-int300 192.168.3.1/24 Vlan-int101 10.110.1.1/24 Vlan-int400 192.168.4.1/24 Switch B Vlan-int200 192.168.2.1/24 Vlan-int103 10.110.3.2/24 Vlan-int101 10.110.1.2/24 Source 1 192.168.1.100/24 Vlan-int102 10.110.2.1/24 Source 2 192.168.4.100/24 Switch C Vlan-int102 10.110.2.2/24...
Page 221 # On Switch B, enable IP multicast routing, enable PIM-SM on each interface, enable IGMP in VLAN interface 200, and enable BIDIR-PIM. <SwitchB> system-view [SwitchB] multicast routing-enable [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] igmp enable [SwitchB-Vlan-interface200] pim sm [SwitchB-Vlan-interface200] quit [SwitchB] interface vlan-interface 101 [SwitchB-Vlan-interface101] pim sm [SwitchB-Vlan-interface101] quit [SwitchB] interface vlan-interface 102...
Page 222 [SwitchD-pim] bidir-pim enable [SwitchD-pim] quit On Switch C, configure VLAN interface 102 as a C-BSR, and loopback interface 0 as a C-RP for the entire BIDIR-PIM domain. [SwitchC-pim] c-bsr vlan-interface 102 [SwitchC-pim] c-rp loopback 0 bidir [SwitchC-pim] quit Verifying the configuration # Display the DF information of BIDIR-PIM on Switch A.
Page 223 Multicast DF information of VPN-Instance: public net Total 1 RP Total 1 RP matched 00001. RP Address: 1.1.1.1 MID: 0, Flags: 0x2100000:0 Uptime: 00:08:32 RPF interface: Vlan-interface101 List of 1 DF interfaces: 1: Vlan-interface100 # Display the DF information of the multicast forwarding table on Switch B. [SwitchB] display multicast forwarding-table df-info Multicast DF information of VPN-Instance: public net Total 1 RP...
Page 224: Pim-Ssm Configuration Example
MID: 0, Flags: 0x2100000:0 Uptime: 00:05:12 RPF interface: Vlan-interface103 List of 2 DF interfaces: 1: Vlan-interface300 2: Vlan-interface400 PIM-SSM configuration example Network requirements As shown in Figure 57, 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 SSM mode.
Page 225 Vlan-int103 192.168.2.1/24 Vlan-int103 192.168.2.2/24 Switch C Vlan-int200 10.110.2.2/24 Vlan-int102 192.168.9.2/24 Vlan-int104 192.168.3.1/24 Vlan-int105 192.168.4.1/24 Configuration procedure Configure the IP address and subnet mask for each interface as per Figure 57. (Details not shown.) Configure OSPF on the switches in the PIM-SSM domain to make sure they are interoperable at the network layer.
Page 226 Vlan100 10.110.1.1 (local) Vlan101 192.168.1.2 Vlan102 192.168.9.2 Assume that Host A needs to receive the information a specific multicast source S 10.1 10.5.100/24 sends to multicast group G 232.1.1.1. Switch A builds an SPT toward the multicast source. Switches on the SPT path (Switch A and Switch D) have generated an (S, G) entry, but Switch E, which is not on the SPT path, does not have multicast routing entries.
Page 227: Troubleshooting Pim
Troubleshooting PIM A multicast distribution tree cannot be built correctly Symptom None of the routers in the network (including routers directly connected with multicast sources and receivers) have multicast forwarding entries. That is, a multicast distribution tree cannot be built correctly and clients cannot receive multicast data.
Page 228: Multicast Data Abnormally Terminated On An Intermediate Router
Verify that PIM and IGMP are enabled on the interfaces directly connecting to the multicast source and to the receivers. Use the display pim interface verbose command to verify that the same PIM mode is enabled on the RPF interface and the corresponding interface of the RPF neighbor router. Verify that the same PIM mode is enabled on all the routers in the entire network.
Page 229: Rpt Establishment Failure Or Source Registration Failure In Pim-Sm
• If the static RP mechanism is used, the same static RP command must be executed on all the routers in the entire network. Otherwise, multicast forwarding will fail. Solution Use the display ip routing-table command to verify that a route is available on each router to the Use the display pim rp-info command to verify that the RP information is consistent on all routers.
Page 230: Configuring Msdp (Available Only On The S5500-Ei)
Configuring MSDP (available only on the S5500-EI) 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.
Page 231: How Msdp Works
How MSDP works MSDP peers Configuring one or more pairs of MSDP peers in the network forms an MSDP interconnection map, where the RPs of different PIM-SM domains are interconnected in series. An SA message that an RP sends and that these MSDP peers relay can be delivered to all other RPs. Figure 58 Where MSDP peers are in the network As shown in Figure...
Page 232 Source through multicast source registration. If RPs in PIM-SM 2 and PIM-SM 3 also seek the specific location of Source so that receiver hosts can receive multicast traffic that the source sends, H3C recommends you to establish MSDP peering relationship between RP 1 and RP 3 and between RP 3 and RP 2, respectively.
Page 233 In addition, you can configure MSDP peers into an MSDP mesh group so as to avoid flooding of SA messages between MSDP peers. An MSDP mesh group refers to a group of MSDP peers that have MSDP peering relationship among one another and share the same group name. SA messages are forwarded from one MSDP peer to another, and finally the information about the multicast source traverses all PIM-SM domains with MSDP peers (PIM-SM 2 and PIM-SM 3, in this example).
Page 234 Figure 60 Diagram for RPF check for SA messages As shown in Figure 60, these MSDP peers dispose of SA messages according to the following RPF check rules: When RP 2 receives an SA message from RP 1: Because the source-side RP address carried in the SA message is the same as the MSDP peer address, which means that the MSDP peer where the SA is from is the RP that has created the SA message, RP 2 accepts the SA message and forwards it to its other MSDP peer (RP 3).
Page 235 MBGP route to the source-side RP, RP 8 accepts the message and forwards it to its other peer (RP When RP 9 receives the SA message from RP 8: Because RP 9 has only one MSDP peer, RP 9 accepts the SA message. SA messages from paths other than those described previously are not accepted or forwarded by MSDP peers.
Page 236: Msdp Support For Vpns
RPs share the registered multicast information by means of SA messages. In this example, RP 1 creates an SA message and sends it to RP 2, with the multicast data from Source encapsulated in the SA message. When the SA message reaches RP 2, RP 2 de-encapsulates the message. Receivers receive the multicast data along the RPT and directly join the SPT rooted at the multicast source.
Page 237: Configuring Basic Msdp Functions
Task Remarks connection Configuring an MSDP mesh group Optional Configuring MSDP peer connection control Optional Configuring SA message content Optional Configuring SA request messages Optional Configuring SA messages related parameters Configuring SA message filtering rules Optional Configuring the SA cache mechanism Optional Configuring basic MSDP functions All the configuration tasks should be carried out on RPs in PIM-SM domains, and each of these RPs acts...
Page 238: Creating An Msdp Peer Connection
NOTE: If an interface of the router is shared by an MSDP peer and a BGP or MBGP peer at the same time, H3C recommends you to configure the IP address of the MSDP peer the same as that of the BGP or MBGP peer.
Page 239: Configuring An Msdp Peer Connection
Step Command Remarks static-rpf-peer peer-address No static RPF peer is configured by Configure a static RPF peer. [ rp-policy ip-prefix-name ] default. NOTE: If only one MSDP peer is configured on a router, this MSDP will be registered as a static RPF peer. Configuring an MSDP peer connection Before you configure an MSDP peer connection, complete the following tasks: Configure any unicast routing protocol so that all devices in the domain are interoperable at the...
Page 240: Configuring Msdp Peer Connection Control
within the mesh group. This mechanism not only avoids SA flooding but also simplifies the RPF check mechanism because you do not need to run BGP or MBGP between these MSDP peers. By configuring the same mesh group name for multiple MSDP peers, you can create a mesh group that contains these MSDP peers.
Page 241: Configuring Sa Messages Related Parameters
To configure MSDP peer connection control: Step Command Remarks Enter system view. system-view Enter public network MSDP msdp [ vpn-instance view or VPN instance MSDP vpn-instance-name ] view. Optional. Deactivate an MSDP peer. shutdown peer-address Active by default. Configure the interval Optional.
Page 242: Configuring Sa Request Messages
The MSDP peers deliver SA messages to one another. After receiving an SA message, a router performs RPF check on the message. If the router finds that the remote RP address is the same as the local RP address, it discards the SA message. In the Anycast RP application, however, you must configure RPs with the same IP address on two or more routers in the same PIM-SM domain and configure these routers as MSDP peers to one another.
Page 243: Configuring Sa Message Filtering Rules
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 controlled.
Page 244: Displaying And Maintaining Msdp
When the SA cache mechanism is enabled and the router receives a new (*, G) join message, the router searches its SA cache first. • If the corresponding (S, G) entry does not exist in the cache, the router waits for the SA message that its MSDP peer will send in the next cycle.
Page 245: Msdp Configuration Examples
Step Command Remarks reset msdp [ all-instance | Reset the TCP connection with vpn-instance vpn-instance-name ] Available in user view an MSDP peer. peer [ peer-address ] reset msdp [ all-instance | Clear (S, G) entries in the SA vpn-instance vpn-instance-name ] Available in user view cache.
Page 246 Figure 62 Network diagram Device Interface IP address Device Interface IP address Switch A Vlan-int103 10.110.1.2/24 Switch D Vlan-int104 10.110.4.2/24 Vlan-int100 10.110.2.1/24 Vlan-int300 10.110.5.1/24 Vlan-int200 10.110.3.1/24 Switch E Vlan-int105 10.110.6.1/24 Switch B Vlan-int103 10.110.1.1/24 Vlan-int102 192.168.3.2/24 Vlan-int101 192.168.1.1/24 Loop0 3.3.3.3/32 Loop0 1.1.1.1/32 Switch F...
Page 247 [SwitchA-Vlan-interface103] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] pim sm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 200 [SwitchA-Vlan-interface200] igmp enable [SwitchA-Vlan-interface200] pim sm [SwitchA-Vlan-interface200] quit # Enable IP multicast routing, enable PIM-SM on each interface, and enable IGMP on Switch B, Switch C, Switch D, Switch E, and Switch F in the same way. (Details not shown.) # Configure a PIM domain border on Switch B.
Page 248 # Configure an MSDP peer on Switch B. [SwitchB] msdp [SwitchB-msdp] peer 192.168.1.2 connect-interface vlan-interface 101 [SwitchB-msdp] quit # Configure an MSDP peer on Switch C. [SwitchC] msdp [SwitchC-msdp] peer 192.168.1.1 connect-interface vlan-interface 101 [SwitchC-msdp] peer 192.168.3.2 connect-interface vlan-interface 102 [SwitchC-msdp] quit # Configure MSDP peers on Switch E.
Page 249 Status codes: * - valid, ^ - VPNv4 best, > - best, d - damped, h - history, i - internal, s - suppressed, S - Stale Origin : i - IGP, e - EGP, ? - incomplete Network NextHop LocPrf PrefVal Path/Ogn * >...
Page 250: Inter-As Multicast Configuration By Leveraging Static Rpf Peers
Information about connection status: State: Up Up/down time: 00:15:47 Resets: 0 Connection interface: Vlan-interface101 (192.168.1.1) Number of sent/received messages: 16/16 Number of discarded output messages: 0 Elapsed time since last connection or counters clear: 00:17:51 Information about (Source, Group)-based SA filtering policy: Import policy: none Export policy: none Information about SA-Requests:...
Page 251 Figure 63 Network diagram AS 100 AS 200 PIM-SM 3 Receiver Switch G Vlan-int106 Vlan-int106 Switch F Loop0 Loop0 Receiver Vlan-int102 Vlan-int102 Switch A Switch C PIM-SM 2 Switch D Switch E Vlan-int103 Vlan-int105 Vlan-int103 Vlan-int105 Vlan-int100 Switch B Source 1 Loop0 Source 2 PIM-SM 1...
Page 252 [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 253 [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 # Redistribute BGP routing information into OSPF on Switch D. [SwitchD] ospf 1 [SwitchD-ospf-1] import-route bgp [SwitchD-ospf-1] quit...
Page 254: 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 255 The router ID of Switch B is 1.1.1.1, and the router ID of Switch D is 2.2.2.2. Set up an MSDP peering relationship between Switch B and Switch D. Figure 64 Network diagram Device Interface IP address Device Interface IP address Source 1 —...
Page 256 [SwitchB-Vlan-interface100] pim sm [SwitchB-Vlan-interface100] quit [SwitchB] interface vlan-interface 103 [SwitchB-Vlan-interface103] pim sm [SwitchB-Vlan-interface103] quit [SwitchB] interface Vlan-interface 101 [SwitchB-Vlan-interface101] pim sm [SwitchB-Vlan-interface101] quit [SwitchB] interface loopback 0 [SwitchB-LoopBack0] pim sm [SwitchB-LoopBack0] quit [SwitchB] interface loopback 10 [SwitchB-LoopBack10] pim sm [SwitchB-LoopBack10] quit [SwitchB] interface loopback 20 [SwitchB-LoopBack20] pim sm [SwitchB-LoopBack20] quit...
Page 257 Peer's Address State Up/Down time SA Count Reset Count 2.2.2.2 00:10:17 # Display brief MSDP peer information on Switch D. [SwitchD] display msdp brief 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...
Page 258: Sa Message Filtering Configuration
No information is output on Switch D. Host A has left multicast group G. Source 1 has stopped sending multicast data to multicast group G. When Source 2 10.1 10.6.100/24 sends multicast data to G, Host B joins G. By comparing the PIM routing information displayed on Switch B with that displayed on Switch D, you can see that Switch D acts now as the RP for Source 2 and Host B.
Page 259 An MSDP peering relationship is set up between Switch A and Switch C and between Switch C and Switch D. Source 1 sends multicast data to multicast groups 225.1.1.0/30 and 226.1.1.0/30, and Source 2 sends multicast data to multicast group 227.1.1.0/30. Configure SA message filtering rules so that receivers Host A and Host B can receive only the multicast data addressed to multicast groups 225.1.1.0/30 and 226.1.1.0/30, and Host can receive only the multicast data addressed to multicast groups 226.1.1.0/30 and 227.1.1.0/30.
Page 260 <SwitchA> system-view [SwitchA] multicast routing-enable [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] igmp enable [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 102 [SwitchA-Vlan-interface102] pim sm [SwitchA-Vlan-interface102] quit [SwitchA] interface loopback 0 [SwitchA-LoopBack0] pim sm [SwitchA-LoopBack0] quit # Enable IP multicast routing, IGMP and PIM-SM on Switch B, Switch C and Switch D in the same way.
Page 261 [SwitchC-msdp] quit # Configure an MSDP peer on Switch D. [SwitchD] msdp [SwitchD-msdp] peer 10.110.5.1 connect-interface vlan-interface 104 [SwitchD-msdp] quit Configure SA message filtering rules: # Configure an SA message rule on Switch C so that Switch C will not forward SA messages for (Source 1, 225.1.1.0/30) to Switch D.
Page 262: Troubleshooting Msdp
MSDP Source-Active Cache Information of VPN-Instance: public net MSDP Total Source-Active Cache - 4 entries MSDP matched 4 entries (Source, Group) Origin RP Uptime Expires (10.110.3.100, 226.1.1.0) 1.1.1.1 00:32:53 00:05:07 (10.110.3.100, 226.1.1.1) 1.1.1.1 00:32:53 00:05:07 (10.110.3.100, 226.1.1.2) 1.1.1.1 00:32:53 00:05:07 (10.110.3.100, 226.1.1.3) 1.1.1.1 00:32:53 00:05:07...
Page 263: Inter-Rp Communication Faults In Anycast Rp Application
• If the import-source command is not executed, the system will advertise all the (S, G) entries of the local domain. If MSDP fails to send (S, G) entries through SA messages, verify that the import-source command has been correctly configured. Solution Use the display ip routing-table command to verify that the unicast route between the routers is correct.
Page 264: Configuring Mbgp (Available Only On The S5500-Ei)
Configuring MBGP (available only on the S5500-EI) 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.
Page 265: Configuring Basic Mbgp Functions
Task Remarks Configuring MBGP route redistribution Required Configuring default route redistribution into MBGP Optional Configuring MBGP route summarization Optional Controlling route advertisement and Advertising a default route to an IPv4 MBGP peer or peer group Optional reception Configuring outbound MBGP route filtering Optional Configuring inbound MBGP route filtering Optional...
Page 266: Controlling Route Advertisement And Reception
Controlling route advertisement and reception Before configuring this task, configure basic MBGP functions first. Configuring MBGP route redistribution MBGP can advertise routing information in the local AS to neighboring ASs. It redistributes such routing information from IGP into its routing table rather than learning the information by itself. To configure MBGP route redistribution: Step Command...
Page 267: Configuring Mbgp Route Summarization
Step Command Remarks Enter MBGP address family ipv4-family multicast view. No route redistribution is import-route protocol [ { process-id configured by default. Enable route redistribution | all-processes } [ allow-direct | The allow-direct keyword is from another routing protocol. med med-value | route-policy available only when the specified route-policy-name ] * ] routing protocol is OSPF.
Page 268: Advertising A Default Route To An Ipv4 Mbgp Peer Or Peer Group
Advertising a default route to an IPv4 MBGP peer or peer group Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter IPv4 MBGP address ipv4-family multicast family view. peer { group-name | ip-address } Advertise a default route to an default-route-advertise Not advertised by default.
Page 269: Configuring Inbound Mbgp Route Filtering
Step Command Remarks • Configure the filtering of redistributed routes: filter-policy { acl-number | ip-prefix ip-prefix-name } export [ direct | isis process-id | ospf process-id | rip process-id | static ] • Apply a routing policy to advertisements to an IPv4 MBGP peer or a peer group: peer { group-name | peer-address } route-policy route-policy-name export...
Page 270: Configuring Mbgp Route Dampening
Step Command Remarks Enter BGP view. bgp as-number Enter IPv4 MBGP address ipv4-family multicast family view. • 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 |...
Page 271: Configuring Mbgp Route Attributes
Step Command Remarks Enter BGP view. bgp as-number Enter IPv4 MBGP address ipv4-family multicast family view. 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.
Page 272: Configuring The Med Attribute
Configuring the MED attribute When other conditions of routes to a destination are identical, the route with the smallest MED is selected. To configure the MED attribute: Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter IPv4 MBGP address ipv4-family multicast family view.
Page 273: Configuring The As_Path Attributes
Step Command Remarks Optional. By default, IPv6 MBGP specifies Specify the router as the next the local router as the next hop for peer { group-name | ip-address } hop of routes sent to a peer or routes sent to an EBGP peer or a next-hop-local a peer group.
Page 274 The current MBGP implementation supports the route refresh feature that enables dynamic route refresh without terminating MBGP connections. However, if a peer that does not support route refresh exists in the network, you must configure the peer keep-all-routes command to save all routes from the peer. When the routing policy is changed, the system updates the MBGP routing table and applies the new policy.
Page 275: Enabling The Mbgp Orf Capability
Step Command Remarks refresh bgp ipv4 multicast { all | Soft-reset MBGP connections ip-address | group group-name | Optional. manually. external | internal } { export | import } Enabling the MBGP ORF capability The MBGP Outbound Router Filter (ORF) feature enables an MBGP speaker to send a set of ORFs to its MBGP peer through route-refresh messages.
Page 276: Configuring The Maximum Number Of Mbgp Routes For Load Balancing
Step Command Remarks Enable the ORF IP prefix peer { group-name | ip-address } Optional. negotiation capability for an capability-advertise orf ip-prefix Not enabled by default. MBGP peer or a peer group. { both | receive | send } Table 7 Description of the both, send, and receive parameters and the negotiation result Local parameter Peer parameter Negotiation result...
Page 277: Configuring Mbgp Community
IMPORTANT: To configure an MBGP peer group, you must enable the corresponding IPv4 BGP unicast peer group in • IPv4 MBGP address family view. Before adding an MBGP peer to an MBGP peer group, you must add the corresponding IPv4 unicast •...
Page 278: Configuring An Mbgp Route Reflector
Step Command Remarks • Advertise the COMMUNITY attribute to an MBGP peer or a peer group: peer { group-name | ip-address } Use either command Advertise the COMMUNITY advertise-community attribute to an MBGP peer or Not configured by • Advertise the extended community attribute a peer group.
Page 279: Displaying And Maintaining Mbgp
Displaying and maintaining MBGP Displaying MBGP Task Command Remarks Display the IPv4 MBGP display ip multicast routing-table [ verbose] [ | { begin | Available in any routing table. exclude | include } regular-expression ] view Display the IPv4 MBGP display ip multicast routing-table ip-address routing information matching Available in any...
Page 280: Resetting Mbgp Connections
Task Command Remarks Display MBGP routing Available in any display bgp multicast routing-table different-origin-as information originating from [ | { begin | exclude | include } regular-expression ] view different ASs. display bgp multicast routing-table flap-info [ regular-expression as-regular-expression | Display IPv4 MBGP routing Available in any [ as-path-acl as-path-acl-number | ip-address [ { mask |...
Page 281 • Configure the respective Loopback 0 of Switch A and Switch B as the C-BSR and C-RP of the respective PIM-SM domains. • Set up an MSDP peer relationship between Switch A and Switch B through MBGP. Figure 66 Network diagram AS 100 AS 200 Loop0...
Page 282 # Enable IP multicast routing on Switch C, enable PIM-SM on each interface, and enable IGMP on the host-side interface VLAN-interface 200. <SwitchC> system-view [SwitchC] multicast routing-enable [SwitchC] interface vlan-interface 102 [SwitchC-Vlan-interface102] pim sm [SwitchC-Vlan-interface102] quit [SwitchC] interface vlan-interface 104 [SwitchC-Vlan-interface104] pim sm [SwitchC-Vlan-interface104] quit [SwitchC] interface vlan-interface 200...
Page 283: Verify The Configuration
[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 [SwitchA-bgp-af-mul] quit [SwitchA-bgp] quit # On Switch B, configure the MBGP peer and enable route redistribution from OSPF. [SwitchB] bgp 200 [SwitchB-bgp] router-id 2.2.2.2 [SwitchB-bgp] peer 192.168.1.1 as-number 100 [SwitchB-bgp] import-route ospf 1 [SwitchB-bgp] ipv4-family multicast...
Page 284 192.168.1.1 00:07:17...
Page 285: 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 286 0::0 or that receive IPv6 PIM hello messages are dynamic router ports. For more information about IPv6 PIM hello messages, see "Configuring IPv6 PIM (available only on the S5500-EI)." Aging timers for dynamic ports in MLD snooping and related messages and actions Timer...
Page 287: How Mld Snooping Works
Timer Description Message before expiry Action after expiry When a port dynamically joins a multicast group, the switch The switch removes this Dynamic member starts an aging timer for the port from the MLD MLD report message. port aging timer port.
Page 288: Mld Snooping Proxying
For more information about the MLD report suppression mechanism of hosts, see "Configuring MLD (available only on the S5500-EI)." When receiving a done message When a host leaves an IPv6 multicast group, the host sends an MLD done message to the multicast routers.
Page 289 Even though an MLD snooping proxy is a host from the perspective of its upstream device, the MLD membership report suppression mechanism for hosts does not take effect on it. For more information about the MLD report suppression mechanism for hosts, see "Configuring MLD (available only on the S5500-EI)." Figure 69 Network diagram As shown in Figure 69, Switch A works as an MLD snooping proxy.
Page 290: Protocols And Standards
MLD message Actions In response to a done message for an IPv6 multicast group, the proxy sends a multicast-address-specific query for the group out of the receiving port. After making sure Done that no member port is contained in the forwarding entry for the IPv6 multicast group, the proxy sends a done message for the group out of all router ports.
Page 291: Configuring Basic Mld Snooping Functions
For the configuration tasks in this section: • In MLD-snooping view, the configurations that you make are effective in all VLANs . In VLAN view, the configurations that you make are effective only on the ports that belong to the current VLAN. For a given VLAN, a configuration that you make in MLD-snooping view is effective only if you do not make the same configuration in VLAN view.
Page 292: Specifying The Version Of Mld Snooping
Step Command Remarks Enable MLD snooping for the mld-snooping enable Disabled by default VLAN. Specifying the version of MLD snooping Different versions of MLD snooping can process different versions of MLD messages: MLDv1 snooping can process MLDv1 messages, but flood MLDv2 messages in the VLAN instead •...
Page 293: Configuring Mld Snooping Port Functions
Configuration procedure To configure an IPv6 static multicast MAC address entry in system view: Step Command Remarks Enter system view. system-view mac-address multicast Configure a static multicast No static multicast MAC address mac-address interface interface-list MAC address entry. entries exist by default. vlan vlan-id To configure an IPv6 static multicast MAC address entry in interface view: Step...
Page 294: Configuring Static Ports
If the memberships of IPv6 multicast groups change frequently, you can set a relatively small value for the aging timer of the dynamic member ports. If the memberships of IPv6 multicast groups change rarely, you can set a relatively large value. Setting the global aging timers for dynamic ports Step Command...
Page 295: Configuring A Port As A Simulated Member Host
Step Command Remarks • Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view: Enter Layer 2 Ethernet interface interface-type interface view, Layer 2 Use either command. interface-number aggregate interface view, or port group view. • Enter port group view: port-group manual port-group-name mld-snooping static-group...
Page 296: Enabling Fast-Leave Processing
Step Command Remarks mld-snooping host-join Configure the port as a ipv6-group-address [ source-ip Not configured by default. simulated member host. ipv6-source-address ] vlan vlan-id NOTE: Unlike a static member port, a port that you configure as a simulated member host ages out like a dynamic member port.
Page 297: Disabling A Port From Becoming A Dynamic Router Port
Disabling a port from becoming a dynamic router port The following problems exist in a multicast access network: After receiving an MLD general query or IPv6 PIM hello message from a connected host, a router • port becomes a dynamic router port. Before its timer expires, this dynamic router port receives all multicast packets within the VLAN where the port belongs, and forwards them to the host, affecting normal multicast reception of the host.
Page 298: Enabling Mld Snooping Querier
"MLD querier." For more information about MLD querier, see "Configuring MLD (available only on the S5500-EI)." However, a Layer 2 multicast switch does not support MLD. Therefore, it cannot send MLD general queries by default. When you enable MLD snooping querier on a Layer 2 switch in a VLAN where...
Page 299: Configuring The Source Ipv6 Addresses For Mld Queries
• The maximum response delay for MLD general queries is set by the max-response-time command. The maximum response delay for MLD multicast-address-specific queries equals the MLD • last-listener query interval. Configuring MLD queries and responses globally Step Command Remarks Enter system view. system-view Enter MLD-snooping view.
Page 300: Configuring Mld Snooping Proxying
Configuring MLD snooping proxying Before you configure MLD snooping proxying in a VLAN, complete the following tasks: • Enable MLD snooping in the VLAN. Determine the source IPv6 address for the MLD reports sent by the proxy. • Determine the source IPv6 address for the MLD done messages sent by the proxy. •...
Page 301: Configuring An Mld Snooping Policy
Configuring an MLD snooping policy Before you configure an MLD snooping policy, complete the following tasks: • Enable MLD snooping in the VLAN. Determine the IPv6 ACL rule for IPv6 multicast group filtering. • Determine the maximum number of IPv6 multicast groups that a port can join. •...
Page 302: Configuring Ipv6 Multicast Source Port Filtering
Step Command Remarks • Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view: Enter Layer 2 Ethernet interface interface-type interface view, Layer 2 Use either command. interface-number aggregate interface view, or port group view. • Enter port group view: port-group manual port-group-name By default, no IPv6 group filter is...
Page 303: Enabling Dropping Unknown Ipv6 Multicast Data
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 304: Setting The Maximum Number Of Multicast Groups That A Port Can Join
Step Command Remarks Enter MLD-snooping view. mld-snooping Enable MLD report report-aggregation Enabled by default suppression. Setting the maximum number of multicast groups that a port can join You can set the maximum number of IPv6 multicast groups that a port can join to regulate the traffic on the port.
Page 305: 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: If the IPv6 multicast group replacement feature is disabled, new MLD reports are automatically •...
Page 306: Configuring An Ipv6 Multicast User Control Policy
Step Command Remarks Enter system view. system-view Enter MLD-snooping view. mld-snooping Set the 802.1p precedence The default 802.1p precedence for dot1p-priority priority-number for MLD messages. MLD messages is 0. Setting the 802.1p precedence for MLD messages in a VLAN Step Command Remarks Enter system view.
Page 307: Enabling The Mld Snooping Host Tracking Function
Step Command Remarks No policy is configured by default. Configure a multicast user mld-snooping access-policy That is, a host can join or leave a control policy. acl6-number valid multicast group at any time. Return to system view. quit Enable the created user user-profile profile-name enable Not enabled by default.
Page 308: Displaying And Maintaining Mld Snooping
Step Command Remarks Enter system view. system-view Enter MLD-snooping view. mld-snooping 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 309: Mld Snooping Configuration Examples
MLD snooping configuration examples IPv6 group policy and simulated joining configuration example Network requirements As shown in Figure 70, MLDv1 runs on Router A, MLDv1 snooping required on Switch A, and Router A acts as the MLD querier on the subnet. The receivers, Host A and Host B can receive IPv6 multicast traffic addressed to IPv6 multicast group FF1E::101 only.
Page 310 [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] pim ipv6 dm [RouterA-GigabitEthernet1/0/2] quit Configure Switch A: # Enable MLD snooping globally. <SwitchA> system-view [SwitchA] mld-snooping [SwitchA-mld-snooping] quit # Create VLAN 100, assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to this VLAN, and enable MLD snooping and the function of dropping IPv6 unknown multicast traffic in the VLAN.
Page 311: Static Port Configuration Example
Router port(s):total 1 port(s). GE1/0/1 (D) ( 00:01:30 ) 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 (D) ( 00:03:23 ) GE1/0/4 (D) ( 00:04:10 ) MAC group(s): MAC group address:3333-0000-0101 Host port(s):total 2 port(s).
Page 312 Figure 71 Network diagram Configuration procedure Enable IPv6 forwarding and configure an IPv6 address and prefix length for each interface as Figure On Router A, enable IPv6 multicast routing, enable IPv6 PIM-DM on each interface, and enable MLD on GigabitEthernet 1/0/1. <RouterA>...
Page 313 [SwitchA-vlan100] quit # Configure GigabitEthernet 1/0/3 to be a static router port. [SwitchA] interface gigabitethernet 1/0/3 [SwitchA-GigabitEthernet1/0/3] mld-snooping static-router-port vlan 100 [SwitchA-GigabitEthernet1/0/3] quit Configure Switch B: # Enable MLD snooping globally. <SwitchB> system-view [SwitchB] mld-snooping [SwitchB-mld-snooping] quit # Create VLAN 100, assign GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 to this VLAN, and enable MLD snooping in the VLAN.
Page 314 Vlan(id):100. Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s). Router port(s):total 2 port(s). 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:FF1E::101 (::, FF1E::101): Attribute: Host Port Host port(s):total 1 port(s).
Page 315: Mld Snooping Querier Configuration Example
MLD snooping querier configuration example Network requirements As shown in Figure 72, in a Layer-2-only network environment, two multicast sources (Source 1 and Source 2) send IPv6 multicast data to multicast groups FF1E::101 and FF1E::102 respectively, Host A and Host C are receivers of multicast group FF1E::101 and Host B and Host D are receivers of multicast group FF1E::102.
Page 316 [SwitchA-vlan100] mld-snooping enable [SwitchA-vlan100] mld-snooping drop-unknown # Configure MLD snooping querier feature in VLAN 100. [SwitchA-vlan100] mld-snooping querier [SwitchA-vlan100] quit Configure Switch B: # Enable IPv6 forwarding, and enable MLD snooping globally. <SwitchB> system-view [SwitchB] ipv6 [SwitchB] mld-snooping [SwitchB-mld-snooping] quit # Create VLAN 100, add GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 into VLAN 100.
Page 317: Mld Snooping Proxying Configuration Example
MLD snooping proxying configuration example Network requirements As shown in Figure 73, MLDv1 runs on Router A and MLDv1 snooping runs on Switch A. Router A acts as the MLD querier. Configure MLD snooping proxying on Switch A. This enables the switch to forward MLD reports and done messages on behalf of the attached hosts and to respond to MLD queries from Router A and then forward the queries to the hosts on behalf of Router A.
Page 318 [SwitchA-mld-snooping] quit # Create VLAN 100, assign ports GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to this VLAN, and enable MLD snooping and MLD snooping proxying in the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/4 [SwitchA-vlan100] mld-snooping enable [SwitchA-vlan100] mld-snooping proxying enable [SwitchA-vlan100] quit Verifying the configuration...
Page 319: Ipv6 Multicast Source And User Control Policy Configuration Example
Group Address: FF1E::1 Last Reporter: FE80::2FF:FFFF:FE00:1 Uptime: 00:00:03 Expires: 00:04:17 When Host A leaves the IPv6 multicast group, it sends an MLD done message to Switch A. Receiving the message, Switch A removes port GigabitEthernet 1/0/4 from the member port list of the forwarding entry for the group;...
Page 320 Figure 74 Network diagram Configuration procedures Enable IPv6 forwarding and configure an IP address and prefix length for each interface as Figure 74. (Details not shown.) Configure Switch A: # Create VLAN 101 through VLAN 104 and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to the four VLANs respectively.
Page 321 [SwitchA] interface vlan-interface 104 [SwitchA-Vlan-interface104] pim ipv6 dm [SwitchA-Vlan-interface104] mld enable [SwitchA-Vlan-interface104] quit # Create a multicast source control policy, policy1, so that multicast flows from Source 2 to FF1E::101 will be blocked. [SwitchA] acl ipv6 number 3001 [SwitchA-acl6-adv-3001] rule permit udp source 2::1 128 destination ff1e::101 128 [SwitchA-acl6-adv-3001] quit [SwitchA] traffic classifier classifier1 [SwitchA-classifier-classifier1] if-match acl ipv6 3001...
Page 322 [SwitchA] dot1x [SwitchA] interface gigabitethernet 1/0/1 [SwitchA-GigabitEthernet1/0/1] dot1x [SwitchA-GigabitEthernet1/0/1] quit [SwitchA] interface gigabitethernet 1/0/2 [SwitchA-GigabitEthernet1/0/2] dot1x [SwitchA-GigabitEthernet1/0/2] quit Configure Switch B: # Globally enable MLD snooping. <SwitchB> system-view [SwitchB] mld-snooping [SwitchB-mld-snooping] quit # Create VLAN 104, assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3 to this VLAN, and enable MLD snooping in this VLAN.
Page 323 [SwitchB-isp-domian2] quit [SwitchB] domain default enable domain2 # Globally enable 802.1X and then enable it on GigabitEthernet 1/0/2 and GigabitEthernet 1/0/3. [SwitchB] dot1x [SwitchB] interface gigabitethernet 1/0/2 [SwitchB-GigabitEthernet1/0/2] dot1x [SwitchB-GigabitEthernet1/0/2] quit [SwitchB] interface gigabitethernet 1/0/3 [SwitchB-GigabitEthernet1/0/3] dot1x [SwitchB-GigabitEthernet1/0/3] quit Configure RADIUS server: On the RADIUS server, configure the parameters related to Switch A and Switch B.
Page 324: Troubleshooting Mld Snooping
The output shows that GigabitEthernet 1/0/3 on Switch B has joined FF1E::101 but not FF1E::102. Assume that Source 2 starts sending multicast traffic to FF1E::101. Use the display multicast ipv6 forwarding-table to display the IPv6 multicast forwarding table information. # Display the information about FF1E::101 in the IPv6 multicast forwarding table on Switch A. [SwitchA] display multicast ipv6 forwarding-table ff1e::101 IPv6 Multicast Forwarding Table Total 1 entry...
Page 325: Configured Ipv6 Multicast Group Policy Fails To Take Effect
Configured IPv6 multicast group policy fails to take effect Symptom Although an IPv6 multicast group policy has been configured to allow hosts to join specific IPv6 multicast groups, the hosts can still receive IPv6 multicast data addressed to other groups. Analysis The IPv6 ACL rule is incorrectly configured.
Page 326 If IPv6 PIM is enabled, the switch deletes only its dynamic member ports but not its dynamic router ports. NOTE: On a switch with Layer-3 IPv6 multicast routing enabled, use the display mld group port-info command to display Layer-2 port information. If IPv6 PIM is disabled on the switch, one of the following occurs: If MLD is disabled, the switch deletes all its dynamic router ports.
Page 327: Configuring Ipv6 Pim Snooping
Configuring IPv6 PIM snooping Overview IPv6 Protocol Independent Multicast (PIM) snooping runs on Layer 2 devices. It determines which ports are interested in multicast data by analyzing the received IPv6 PIM messages, and adds 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 328: Configuring Ipv6 Pim Snooping
For more information about IPv6 PIM, see "Configuring IPv6 PIM (available only on the S5500-EI)." Configuring IPv6 PIM snooping When you configure IPv6 PIM snooping, follow these guidelines: Before you configure IPv6 PIM snooping for a VLAN, you must enable IPv6 forwarding and MLD •...
Page 329: Displaying And Maintaining Ipv6 Pim Snooping
Step Command Remarks Enable IPv6 PIM snooping in pim-snooping ipv6 enable Disabled by default the VLAN. Displaying and maintaining IPv6 PIM snooping Task Command Remarks display pim-snooping ipv6 Display IPv6 PIM snooping neighbor [ vlan vlan-id ] [ slot Available in any view neighbor information.
Page 330 Figure 76 Network diagram Configuration procedure Enable IPv6 forwarding on the devices, configure an IPv6 address and prefix length for each interface according to Figure 76. (Details not shown.) On Router A, enable IPv6 multicast routing, enable IPv6 PIM-SM on each interface, and configure interface GigabitEthernet 1/0/2 as a C-BSR and C-RP.
Page 331 [RouterC-GigabitEthernet1/0/1] pim ipv6 sm [RouterC-GigabitEthernet1/0/1] mld enable [RouterC-GigabitEthernet1/0/1] quit [RouterC] interface gigabitethernet 1/0/2 [RouterC-GigabitEthernet1/0/2] pim ipv6 sm Configure Router D in the same way as you configure Router C. (Details not shown.) Configure Switch A: # Enable MLD snooping globally. <SwitchA>...
Page 332: Troubleshooting Ipv6 Pim Snooping
Upstream neighbor: FE80::2 Upstream port: GE1/0/2 Total number of downstream ports: 1 1: GE1/0/4 Expires: 00:01:05, FSM: J The output shows that Switch A will forward the multicast data intended for IPv6 multicast group FF1E::101 to only Router C, and forward the multicast data intended for IPv6 multicast group FF2E::101 to only Router D.
Page 333 message fragments might suppress the join messages of other IPv6 PIM-capable routers in the VLAN. As a result, some IPv6 PIM-capable routers cannot receive the multicast data addressed to a specific multicast group because their join messages are suppressed. To solve this problem, disable the join suppression function on all IPv6 PIM-capable routers that connect to the IPv6 PIM snooping-capable switch in the VLAN.
Page 334: Configuring Ipv6 Multicast Vlans
Configuring IPv6 multicast VLANs Overview As shown in Figure 77, 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 335 Figure 78 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 336: Ipv6 Multicast Vlan Configuration Task List
• Enable MLD snooping in the VLAN to be configured as an IPv6 multicast VLAN. Configuration guidelines For the S5500-EI switches, you cannot configure an IPv6 multicast VLAN on a device with IP • multicast routing enabled. The VLAN to be configured as an IPv6 multicast VLAN must exist.
Page 337: Configuration Procedure
Configuration procedure In this approach, you configure a VLAN as an IPv6 multicast VLAN, and configure user VLANs as sub-VLANs of the IPv6 multicast VLAN. To configure a sub-VLAN-based IPv6 multicast VLAN: Step Command Remarks Enter system view. system-view Configure the specified VLAN as an IPv6 multicast VLAN No IPv6 multicast VLAN multicast-vlan ipv6 vlan-id...
Page 338: Configuring Ipv6 Multicast Vlan Ports
IPv6 multicast VLAN or specifying the IPv6 multicast VLAN on the user ports. These two methods provide the same result. Configuration guidelines For the S5500-EI switches, you cannot configure an IPv6 multicast VLAN on a device with multicast • routing enabled.
Page 339: Displaying And Maintaining Ipv6 Multicast Vlan
Step Command Remarks Configure the ports as By default, an IPv6 multicast member ports of the IPv6 port interface-list VLAN has no member ports. multicast VLAN. To configure IPv6 multicast VLAN ports in interface view or port group view: Step Command Remarks Enter system view.
Page 340 Figure 80 Network diagram Source MLD querier Router A GE1/0/1 1::2/64 GE1/0/2 1::1/64 2001::1/64 GE1/0/1 Switch A Switch B Switch C GE1/0/2 GE1/0/3 GE1/0/2 GE1/0/3 Receiver Receiver Receiver Receiver Host A Host B Host C Host D VLAN 2 VLAN 3 VLAN 4 VLAN 5 Configuration procedure...
Page 341 [SwitchA] interface gigabitethernet 1/0/2 [SwitchA-GigabitEthernet1/0/2] port link-type trunk [SwitchA-GigabitEthernet1/0/2] port trunk permit vlan 2 3 [SwitchA-GigabitEthernet1/0/2] quit # Configure GigabitEthernet 1/0/3 as a trunk port that permits packets from VLAN 4 and VLAN 5 to pass through. [SwitchA] interface gigabitethernet 1/0/3 [SwitchA-GigabitEthernet1/0/3] port link-type trunk [SwitchA-GigabitEthernet1/0/3] port trunk permit vlan 4 5 [SwitchA-GigabitEthernet1/0/3] quit...
Page 342 Verifying the configuration # Display information about the IPv6 multicast VLAN. [SwitchA] display multicast-vlan ipv6 Total 1 IPv6 multicast-vlan(s) IPv6 Multicast vlan 10 subvlan list: vlan 2-5 port list: no port # Display the MLD snooping IPv6 multicast group information on Switch A. [SwitchA] display mld-snooping group Total 5 IP Group(s).
Page 343 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/3 MAC group(s): MAC group address:3333-0000-0101 Host port(s):total 1 port(s). GE1/0/3 Vlan(id):5. Total 1 IP Group(s). Total 1 IP Source(s).
Page 344: Port-Based Multicast Vlan Configuration Example
Port-based multicast VLAN configuration example Network requirements As shown in Figure 81, MLDv1 runs on Router A. MLDv1 snooping runs on Switch A. Router A acts as the MLD querier. The IPv6 multicast source sends IPv6 multicast data to IPv6 multicast group FF1E::101. Host A, Host B, and Host C are receivers of the IPv6 multicast group.
Page 345 # 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. [SwitchA] vlan 10 [SwitchA-vlan10] port gigabitethernet 1/0/1 [SwitchA-vlan10] mld-snooping enable [SwitchA-vlan10] quit # Create VLAN 2 and enable MLD snooping in the VLAN.
Page 346 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 347: Configuring Ipv6 Multicast Routing And Forwarding (Available Only On The S5500-Ei)
Configuring IPv6 multicast routing and forwarding (available only on the S5500-EI) 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 •...
Page 348: Rpf Check Implementation In Ipv6 Multicast
For more information about the concepts of SPT, RPT, source-side RPT, RP, and BSR, see "Configuring IPv6 PIM (available only on the S5500-EI)." RPF check implementation in IPv6 multicast Implementing an RPF check on each received IPv6 multicast data packet would heavily burden the router.
Page 349 If the corresponding (S, G) entry does not exist in the IPv6 multicast forwarding table, the packet undergoes an RPF check. The router creates an IPv6 multicast routing entry based on the relevant routing information and installs the entry into the IPv6 multicast forwarding table, with the RPF interface as the incoming interface.
Page 350: Configuration Task List
• When an IPv6 multicast packet arrives on VLAN-interface 10 of Router C, because the interface is not the incoming interface of the (S, G) entry, the router performs an RPF check on the packet. The router searches its IPv6 unicast routing table and finds that the outgoing interface to Source (the RPF interface) is VLAN-interface 20.
Page 351: Configuring An Ipv6 Multicast Forwarding Range
By configuring per-source or per-source-and-group load splitting, you can optimize the traffic delivery when multiple IPv6 multicast data streams are handled. To configure an IPv6 multicast routing policy: Step Command Remarks Enter system view. system-view Optional. Configure the device to select The route with the highest priority is the RPF route based on the multicast ipv6 longest-match...
Page 352: Displaying And Maintaining Ipv6 Multicast Routing And Forwarding
performance. You can set a limit on the number of entries in the IPv6 multicast forwarding table based on the actual networking situation and the performance requirements. If the configured maximum number of IPv6 multicast forwarding table entries is smaller than the current value, the entries in excess are not immediately deleted.
Page 353 Task Command Remarks display multicast ipv6 forwarding-table [ ipv6-source-address [ prefix-length ] | ipv6-group-address [ prefix-length ] | incoming-interface { interface-type Display the information of the IPv6 interface-number | register } | Available in any view. multicast forwarding table. outgoing-interface { exclude | include | match } { interface-type interface-number | register } | statistics | slot slot-number ] *...
Page 354: Troubleshooting Ipv6 Multicast Policy Configuration
For more information about designated forwarder (DF), see "Configuring IPv6 PIM (available only on the S5500-EI)." Troubleshooting IPv6 multicast policy configuration Abnormal termination of IPv6 multicast data Symptom • A host sends an MLD report announcing its joining an IPv6 multicast group (G). However, no member information about the IPv6 multicast group (G) exists on the intermediate router.
Page 355: Configuring Mld (Available Only On The S5500-Ei)
Configuring MLD (available only on the S5500-EI) 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.
Page 356 MLD querier election All IPv6 multicast routers on the same subnet can monitor MLD listener report messages (often called "reports") from hosts, but only one router is needed to send MLD query messages (often called "queries"). The querier election mechanism determines which router will act as the MLD querier on the subnet. Initially, every MLD router assumes itself as the querier and sends MLD general query messages (often called "general queries") to all hosts and routers on the local subnet.
Page 357: How Mldv2 Works
After receiving a query message, Host B or Host C (the delay timer of whichever expires first) sends an MLD report to the IPv6 multicast group address of G1, to announce its membership for G1. Assume that Host B sends the report message. After hearing the report from Host B, Host C, which is on the same subnet as Host B, suppresses its own report for G1, because the MLD routers (Router A and Router B) have already known that at least one host on the local subnet is interested in G1.
Page 358 • If it expects IPv6 multicast data from specific IPv6 multicast sources like S1, S2, …, it sends a report with Filter-Mode denoted as "Include Sources (S1, S2, …)." • If it does not expect IPv6 multicast data from specific IPv6 multicast sources like S1, S2, …, it sends a report with Filter-Mode denoted as "Exclude Sources (S1, S2, …)."...
Page 359: Mld Messages
MLD messages The following descriptions are based on MLDv2 messages. MLD query message An MLD querier learns the multicast listening state of neighbor interfaces by sending MLD query messages. The dark area in Figure 85 shows the MLDv1 message format. Figure 85 MLDv2 query message format Type = 130 Code...
Page 360 Field Description • This field is set to 0 in a general query message. • It is set to a specific IPv6 multicast address in a Multicast Address multicast-address-specific query message or multicast-address-and-source-specific query message. Flag indicating whether a router updates the timer for suppression after receiving a query message.
Page 361: Mld Ssm Mapping
Field Description The Reserved fields are set to 0 on transmission and ignored on Reserved reception. Checksum Standard IPv6 checksum. This field indicates how many IPv6 multicast address records are Number of Multicast Address Records present in this report message. This field represents information of each IPv6 multicast address the host listens to on the interface from which the report message Multicast Address Record(i)
Page 362: Mld Proxying
The MLD SSM mapping feature does not process MLDv2 reports. For more information about the IPv6 SSM group range, see "Configuring IPv6 PIM (available only on the S5500-EI)." 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.
Page 363: Protocols And Standards
As shown in Figure 88, an MLD proxy device has the following types of interfaces: Upstream interface—Also called the "proxy interface." A proxy interface is an interface on which • MLD proxying is configured. It is in the direction toward the root of the multicast forwarding tree. An upstream interface acts as a host that is running MLD, and is also called a "host interface."...
Page 364: Configuring Basic Mld Functions
Task Remarks Enabling MLD SSM mapping Optional Configuring MLD SSM mapping Configuring MLD SSM mappings Optional Enabling MLD proxying Optional Configuring MLD proxying Configuring IPv6 multicast forwarding on a Optional downstream interface NOTE: In MLD view, the configuration is effective globally. In interface view, the configuration is effective on •...
Page 365: Configuring The Mld Version
MLD querier. For more information about IPv6 PIM-SM and a DR, see "Configuring IPv6 PIM (available only on the S5500-EI)." A static member port does not respond to queries from the MLD querier. When you configure an •...
Page 366: Configuring An Ipv6 Multicast Group Filter
Configuration procedure To configure a static member of an IPv6 multicast group or an IPv6 multicast source and group: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure a static member of By default, an interface is not a mld static-group an IPv6 multicast group or an static member of any IPv6 multicast...
Page 367: Adjusting Mld Performance
NOTE: This configuration takes effect for dynamically joined IPv6 multicast groups but not the statically configured multicast groups. Adjusting MLD performance For the configuration tasks in this section: In MLD view, the configuration is effective globally. In interface view, the configuration is effective •...
Page 368: 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 the device to discard MLD messages that do not carry the Router-Alert option.
Page 369 multicast group and multicast source mapping change report. The number of queries, or the last listener query count, equals the robustness variable (the maximum number of packet retransmissions). A multicast listening host starts a timer for each IPv6 multicast group that it has joined when it receives an MLD query (general query, multicast-address-specific query, or multicast-address-and-source-specific query).
Page 370: Configuring Mld Fast-Leave Processing
Step Command Remarks Configure the MLD last last-listener-query-interval interval 1 second by default. listener query interval. 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.
Page 371: Enabling The Mld Host Tracking Function
frequently from one IPv6 multicast group to another, you can enable MLD fast-leave processing on the MLD querier. With fast-leave processing enabled, after receiving an MLD done message from a host, the MLD querier sends leave notification upstream immediately without first sending multicast-address-specific queries.
Page 372: Setting The Dscp Value For Mld Messages
Step Command Remarks Configure the MLD host host-tracking Disabled by default tracking function globally. Enabling the MLD host tracking function on an interface Step Command Remarks Enter system view. system-view Enter interface view. interface interface-type interface-number Enable the MLD host tracking mld host-tracking Disabled by default function on the interface.
Page 373: Enabling Mld Ssm Mapping
Enabling MLD SSM mapping Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Enable the MLD SSM mld ssm-mapping enable Disabled by default mapping feature. NOTE: To ensure SSM service for all hosts on a subnet, regardless of the MLD version running on the hosts, enable MLDv2 on the interface that forwards IPv6 multicast traffic onto the subnet.
Page 374: 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 375: Displaying And Maintaining Mld
Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number 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...
Page 376 Task Command Remarks display mld routing-table [ ipv6-source-address [ prefix-length ] | Display the information of the MLD ipv6-group-address [ prefix-length ] Available in any view. routing table. | flags { act | suc } ] * [ | { begin | exclude | include } regular-expression ] display mld ssm-mapping...
Page 377: Mld Configuration Examples
MLD configuration examples Basic MLD functions configuration example Network requirements As shown in Figure 89, receivers receive VOD information in the multicast mode. Receivers of different organizations form stub networks N1 and N2, and Host A and Host C are multicast receivers in N1 and N2 respectively.
Page 378 <SwitchA> system-view [SwitchA] multicast ipv6 routing-enable [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] mld enable [SwitchA-Vlan-interface100] pim ipv6 dm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim ipv6 dm [SwitchA-Vlan-interface101] quit # Enable IPv6 multicast routing on Switch B, enable MLD on VLAN-interface 200, and enable IPv6 PIM-DM on each interface.
Page 379: Mld Ssm Mapping Configuration Example
Value of other querier present interval for MLD(in seconds): 255 Value of maximum query response time for MLD(in seconds): 10 Querier for MLD: FE80::200:5EFF:FE66:5100 (this router) Total 1 MLD Group reported MLD SSM mapping configuration example Network requirements As shown in Figure 90, the IPv6 PIM-SM domain applies both the ASM model and SSM model for IPv6 multicast delivery.
Page 380 Configure OSPFv3 on the switches in the IPv6 PIM-SM domain to make sure the switches are interoperable at the network layer and they can dynamically update their routing information. (Details not shown.) Enable IPv6 multicast routing, enable IPv6 PIM-SM on each interface and enable MLD and MLD SSM mapping on the host-side interface: # Enable IPv6 multicast routing on Switch D, enable IPv6 PIM-SM on each interface, and enable MLD (version 2) and MLD SSM mapping on VLAN-interface 400.
Page 381 [SwitchD] pim ipv6 [SwitchD-pim6] ssm-policy 2000 [SwitchD-pim6] quit # Configure the IPv6 SSM group range on Switch A, Switch B and Switch C in the same way. (Details not shown.) Configure MLD SSM mappings on Switch D. [SwitchD] mld [SwitchD-mld] ssm-mapping ff3e:: 64 1001::1 [SwitchD-mld] ssm-mapping ff3e:: 64 3001::1 [SwitchD-mld] quit Verifying the configuration...
Page 382: Mld Proxying Configuration Example
UpTime: 00:13:25 Upstream interface: Vlan-interface103 Upstream neighbor: 3002::1 RPF prime neighbor: 3002::1 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface400 Protocol: mld, UpTime: 00:13:25, Expires: - MLD proxying configuration example Network requirements As shown in Figure 91, IPv6 PIM-DM runs on the core network. Host A and Host C in the stub network receive VOD information destined to multicast group FF3E::101.
Page 383: Troubleshooting Mld
[SwitchA-Vlan-interface100] quit # Enable IPv6 multicast routing on Switch B, MLD proxying on VLAN-interface 100, and MLD on VLAN-interface 200. <SwitchB> system-view [SwitchB] multicast ipv6 routing-enable [SwitchB] interface vlan-interface 100 [SwitchB-Vlan-interface100] mld proxying enable [SwitchB-Vlan-interface100] quit [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] mld enable [SwitchB-Vlan-interface200] quit Verifying the configuration...
Page 384: Inconsistent Memberships On Routers On The Same Subnet
• If the MLD version on the router interface is lower than that on the host, the router will not be able to recognize the MLD report from the host. • If the mld group-policy command has been configured on an interface, the interface cannot receive report messages that fail to pass filtering.
Page 385: Configuring Ipv6 Pim (Available Only On The S5500-Ei)
Configuring IPv6 PIM (available only on the S5500-EI) 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, IS-ISv6, or BGP4+. IPv6 PIM uses an IPv6 unicast routing table to perform reverse path forwarding (RPF) check to implement IPv6 multicast forwarding.
Page 386 • IPv6 PIM-DM assumes that at least one IPv6 multicast group member exists on each subnet of a network. Therefore, IPv6 multicast data is flooded to all nodes on the network. Then, branches without IPv6 multicast forwarding are pruned from the forwarding tree, leaving only those branches that contain receivers.
Page 387 For a given IPv6 multicast stream, the interface that receives the IPv6 multicast stream is referred to as "upstream," and the interfaces that forward the IPv6 multicast stream are referred to as "downstream. A leaf router first initiates a prune process. As shown in Figure 92, a router without any receiver attached to it (the router connected with Host A, for example) sends a prune message, and this prune process...
Page 388: Ipv6 Pim-Sm Overview
Assert Where more than one multicast routers exists, the assert mechanism shuts off duplicate IPv6 multicast flows onto the same multi-access network. It does this by electing a unique IPv6 multicast forwarder on the multi-access network. Figure 93 Assert mechanism As shown in Figure 93, after Router A and Router B receive an (S, G) IPv6 multicast packet from the...
Page 389 The basic implementation of IPv6 PIM-SM is as follows: IPv6 PIM-SM assumes that no hosts need to receive IPv6 multicast data. In the IPv6 PIM-SM mode, • routers must specifically request a particular IPv6 multicast stream before the data is forwarded to them.
Page 390 MLD must be enabled on a device that acts as a receiver-side DR before receivers attached to this device can join IPv6 multicast groups through this DR. For more information about MLD, see "Configuring MLD (available only on the S5500-EI)." Figure 94 DR election As shown in Figure 94, the DR election process is as follows: Routers on the multi-access network send hello messages to one another.
Page 391 a BSR. The BSR acts as the administrative core of the IPv6 PIM-SM domain. An IPv6 PIM-SM domain can have only one BSR, but can have multiple C-BSRs. If the BSR fails, a new BSR is automatically elected from the C-BSRs to avoid service interruption. NOTE: An RP can provide services for multiple IPv6 multicast groups, but an IPv6 multicast group only uses one •...
Page 392 Table 11 Values in the hashing algorithm Value Description Value Hash value. The digest from the exclusive-or (XOR) operation between the 32-bit segments of the IPv6 multicast group address. For example, if the IPv6 multicast address is FF0E:C20:1A3:63::101, G = 0xFF0E0C20 XOR 0x01A30063 XOR 0x00000000 XOR 0x00000101.
Page 393 RPT establishment Figure 96 RPT establishment in an IPv6 PIM-SM domain Host A Source Receiver Host B Server Receiver Join message IPv6 multicast packets Host C As shown in Figure 96, the process of building an RPT is as follows: When a receiver joins IPv6 multicast group G, it uses an MLD report message to inform the directly connected DR.
Page 394 Figure 97 IPv6 multicast source registration As shown in Figure 97, the IPv6 multicast source registers with the RP as follows: The IPv6 multicast source S sends the first IPv6 multicast packet to IPv6 multicast group G. After receiving the multicast packet, the DR that directly connects to the multicast source encapsulates the packet in a register message.
Page 395: Ipv6 Bidir-Pim 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 396 through the RP to the receivers along the bidirectional RPT. In this case, each router needs to maintain only a (*, G) multicast routing entry, saving system resources. IPv6 BIDIR-PIM is suitable for networks with dense multicast sources and dense receivers. The working mechanism of IPv6 BIDIR-PIM is summarized as follows: •...
Page 397 Figure 98 DF election Router E Router D Router B Router C Ethernet DF election message IPv6 Multicast packets Router A Source As shown in Figure 98, without the DF election mechanism, both Router B and Router C can receive multicast packets from Route A, and they might both forward the packets to downstream routers on the local subnet.
Page 398 Figure 99 RPT building at the receiver side As shown in Figure 99, the process for building a receiver-side RPT is similar to that for building an RPT in IPv6 PIM-SM: When a receiver joins IPv6 multicast group G, it uses an MLD message to inform the directly connected router.
Page 399: Ipv6 Administrative Scoping Overview
Figure 100 RPT building at the multicast source side As shown in Figure 100, the process of building a source-side RPT is relatively simple: When an IPv6 multicast source sends IPv6 multicast packets to IPv6 multicast group G, the DF in each network segment unconditionally forwards the packets to the RP.
Page 400 To implement refined management, an IPv6 PIM-SM/IPv6 BIDIR-PIM domain can be divided into one IPv6 global scope zone and multiple IPv6 administratively scoped zones (IPv6 admin-scope zones). We call this IPv6 administrative scoping mechanism. The IPv6 administrative scoping mechanism effectively releases stress on the management in a single-BSR domain and enables provision of zone-specific services using private group addresses.
Page 401 Figure 101 Relationship in view of geographical locations As shown in Figure 101, for the IPv6 multicast groups with the same scope field value, the IPv6 admin-scope zones must be geographically separated and isolated. The IPv6 global-scoped zone includes all routers in the IPv6 PIM-SM domain or IPv6 BIDIR-PIM domain. IPv6 multicast packets that do not belong to any IPv6 admin-scope zones are forwarded in the entire IPv6 PIM-SM domain or IPv6 BIDIR-PIM domain.
Page 402: Ipv6 Pim-Ssm Overview
Value Meaning Remarks Subnet-local scope IPv6 admin-scope zone Admin-local scope IPv6 admin-scope zone Site-local scope IPv6 admin-scope zone 6, 7, 9 through D Unassigned IPv6 admin-scope zone Organization-local scope IPv6 admin-scope zone Global scope IPv6 global-scope zone IPv6 PIM-SSM overview The source-specific multicast (SSM) model and the any-source multicast (ASM) model are opposites.
Page 403: Relationship Among Ipv6 Pim Protocols
Figure 103 Building an SPT in IPv6 PIM-SSM Host A Source Receiver Host B Server Receiver Subscribe message IPv6 multicast packets Host C As shown in Figure 103, Hosts B and C are IPv6 multicast information receivers. They send an MLDv2 report message to the respective DRs to announce that they are interested in the information about the specific IPv6 multicast source S and that sent to the IPv6 multicast group G.
Page 404: Protocols And Standards
Figure 104 Relationship among IPv6 PIM protocols For more information about MLD SSM mapping, see "Configuring MLD (available only on the S5500-EI)." 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) •...
Page 405: Configuration Prerequisites
Task Remarks Configuring state refresh parameters Optional Configuring IPv6 PIM-DM graft retry period Optional Configuring IPv6 PIM common features Optional 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 •...
Page 406: Configuring State Refresh Parameters
prune timer state of all the routers on the path. A multi-access subnet can have the state-refresh capability only if the state-refresh capability is enabled on all IPv6 PIM routers on the subnet. To enable the state-refresh capability: Step Command Remarks Enter system view.
Page 407: Configuring Ipv6 Pim-Dm Graft Retry Period
Configuring IPv6 PIM-DM graft retry period In IPv6 PIM-DM, graft is the only type of message that uses the acknowledgment mechanism. In an IPv6 PIM-DM domain, if a router does not receive a graft-ack message from the upstream router within the specified time after it sends a graft message, the router keeps sending new graft messages at a configurable interval (namely, graft retry period) until it receives a graft-ack message from the upstream router.
Page 408: Configuration Prerequisites
Task Remarks Disabling the switchover to SPT Optional. Configuring IPv6 PIM common features Optional. Configuration prerequisites Before you configure IPv6 PIM-SM, complete the following tasks: Enable IPv6 forwarding and configure an IPv6 unicast routing protocol so that all devices in the •...
Page 409: Configuring An Rp
RP-set, which is flooded throughout the entire network. Then, the other routers in the network calculate the mappings between specific group ranges and the corresponding RPs based on the RP-set. H3C recommends that you configure C-RPs on backbone routers.
Page 410 To guard against C-RP spoofing, you need to configure a legal C-RP address range and the range of IPv6 multicast groups to which the C-RP is designated on the BSR. In addition, because every C-BSR has a chance to become the BSR, you need to configure the same filtering policy on all C-BSRs in the IPv6 PIM-SM domain.
Page 411: Configuring A Bsr
Configuring C-RP timers globally To enable the BSR to distribute the RP-set information within the IPv6 PIM-SM domain, C-RPs must periodically send C-RP-Adv messages to the BSR. The BSR obtains the RP-set information from the received messages, and encapsulates its own IPv6 address together with the RP-set information in its bootstrap messages.
Page 412 Configuring a legal range of BSR addresses enables filtering of bootstrap messages based on the address range, thereby preventing a maliciously configured host from masquerading as a BSR. You must make the same configuration on all routers in the IPv6 PIM-SM domain. Typical BSR spoofing cases and the corresponding preventive measures are as follows: Some maliciously configured hosts can forge bootstrap messages to fool routers and change RP •...
Page 413 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. configured by default. Configuring C-BSR parameters globally In each IPv6 PIM-SM domain, a unique BSR is elected from C-BSRs.
Page 414 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 415: Configuring Ipv6 Administrative Scoping
To disable the BSM semantic fragmentation function: 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.
Page 416: Configuring Ipv6 Multicast Source Registration
In view of information integrity of register messages in the transmission process, you can configure the device to calculate the checksum based on the entire register messages. However, to reduce the workload of encapsulating data in register messages and for the sake of interoperability, H3C does not recommend this method of checksum calculation.
Page 417: Disabling The Switchover To Spt
When receivers stop receiving data addressed to a certain IPv6 multicast group through the RP (which means that the RP stops serving the receivers of that IPv6 multicast group), or when the RP starts receiving IPv6 multicast data from the IPv6 multicast source along the SPT, the RP sends a register-stop message to the source-side DR.
Page 418: Configuring Ipv6 Bidir-Pim
Step Command Remarks Enter system view. system-view Enter IPv6 PIM view. pim ipv6 Optional. spt-switch-threshold infinity Disable the switchover to By default, the device switches to the SPT [ group-policy acl6-number SPT. immediately after it receives the first IPv6 [ order order-value ] ] multicast packet from the RPT.
Page 419: Enabling Ipv6 Pim-Sm
• Determine the C-RP priority and the IPv6 ACL that defines the range of IPv6 multicast groups to which each C-RP is designated. • Determine the legal C-RP address range and the IPv6 ACL that defines the range of IPv6 multicast groups to which the C-RP is designated.
Page 420: Configuring An Rp
RP-set, which is flooded throughout the entire network. Then, the other routers in the network calculate the mappings between specific group ranges and the corresponding RPs based on the RP-set. H3C recommends that you configure C-RPs on backbone routers.
Page 421 To configure a C-RP: Step Command Remarks Enter system view. system-view Enter IPv6 PIM view. pim ipv6 c-rp ipv6-address [ { group-policy acl6-number | scope scope-id } | Configure an interface to be a priority priority | holdtime No C-RP is configured by default. C-RP for IPv6 BIDIR-PIM.
Page 422: Configuring A Bsr
The C-RP timers need to be configured on C-RP routers. To configure C-RP timers globally: Step Command Remarks Enter system view. system-view Enter IPv6 PIM view. pim ipv6 Optional. Configure the C-RP-Adv c-rp advertisement-interval interval interval. 60 seconds by default. Optional.
Page 423 the right of advertising RP information in the network. After being configured as a C-BSR, a router automatically floods the network with bootstrap messages. Because a bootstrap message has a hop limit value of 1, the whole network will not be affected as long as the neighbor router discards these bootstrap messages.
Page 424 Configuring global C-BSR parameters In each IPv6 BIDIR-PIM domain, a unique BSR is elected from C-BSRs. The C-RPs in the IPv6 BIDIR-PIM 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 IPv6 BIDIR-PIM domain. All the routers use the same hash algorithm to get the RP address corresponding to specific multicast groups.
Page 425 Step Command Remarks Optional. By default, the BS timeout value is determined by the formula "BS Configure the BS timeout timeout timer = BS period × 2 + c-bsr holdtime interval timer. 10." The default BS period is 60 seconds, so the default BS timeout timer = 60 ×...
Page 426: Configuring Ipv6 Administrative Scoping
Configuring IPv6 administrative scoping With administrative scoping disabled, an IPv6 BIDIR-PIM domain has only one BSR. The BSR manages the whole network. To manage your network more effectively and specifically, you can partition the IPv6 BIDIR-PIM domain into multiple admin-scope zones. Each admin-scope zone maintains a BSR, which provides services for a specific multicast group range.
Page 427: Configuring Ipv6 Pim-Ssm
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. You can configure the hash mask length and C-BSR priority globally, only in an IPv6 admin-scope zone, or both globally and in an IPv6 admin-scope zone.
Page 428: Enabling Ipv6 Pim-Sm
Enabling IPv6 PIM-SM When you enable IPv6 PIM-SM, follow these guidelines: • The SSM model is implemented based on some subsets of IPv6 PIM-SM. Therefore, you must enable IPv6 PIM-SM before configuring IPv6 PIM-SSM. • When you deploy an IPv6 PIM-SSM domain, enable IPv6 PIM-SM on all non-border interfaces of routers.
Page 429: Configuring Ipv6 Pim Common Features
Configuring IPv6 PIM common features For the configuration tasks in this section: • In IPv6 PIM view, the configuration is effective on all interfaces. In interface view, the configuration is effective on only the current interface. • If the same function or parameter is configured in both IPv6 PIM view and interface view, the configuration in interface view has preference over the configuration in PIM view, regardless of the configuration sequence.
Page 430: Configuring An Ipv6 Multicast Data Filter
• Determine the join/prune interval (global value/interface level value). Determine the join/prune timeout (global value/interface value). • Determine the IPv6 multicast source lifetime. • Determine the maximum size of join/prune messages. • • Determine the maximum number of (S, G) entries in a join/prune message. Determine the DSCP value for IPv6 PIM messages.
Page 431: Configuring Ipv6 Pim Hello Options
Step Command Remarks 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 432 If you disable join suppression (namely, enable neighbor tracking), be sure to disable the join suppression feature on all IPv6 PIM routers on a multi-access subnet. Otherwise, the upstream router will fail to explicitly track join messages from downstream routers. Configuring hello options globally Step Command...
Page 433: Configuring The Prune Delay
Configuring the prune delay Configuring the prune delay interval on an upstream router in a shared network segment can make the upstream router not perform the prune action immediately after receiving the prune message from its downstream router. Instead, the upstream router maintains the current forwarding state for a period of time that the prune delay interval defines.
Page 434: Configuring Join/Prune Message Sizes
Step Command Remarks Enter IPv6 PIM view. pim ipv6 Optional. Configure the hello interval. timer hello interval 30 seconds by default. Optional. Configure the join/prune timer join-prune interval interval. 60 seconds by default. Optional. Configure the join/prune holdtime join-prune interval timeout time.
Page 435: Configuring Ipv6 Pim To Work With Bfd
IMPORTANT: If IPv6 PIM snooping–enabled switches are deployed in the IPv6 PIM network, be sure to set a value no greater than the IPv6 path MTU for the maximum size of each join/prune message on the receiver-side edge IPv6 PIM devices. To configure join/prune message sizes: Step Command...
Page 436: 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 2474, the first six bits contains the DSCP priority for prioritizing traffic in the network and the last two bits are reserved.
Page 437: 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 438 Figure 105 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 439 # 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 440: Ipv6 Pim-Sm Non-Scoped Zone Configuration Example
[SwitchA] display pim ipv6 routing-table Total 1 (*, G) entry; 1 (S, G) entry (*, FF0E::101) Protocol: pim-dm, Flag: WC UpTime: 00:01:24 Upstream interface: NULL Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: mld, UpTime: 00:01:20, Expires: never (4001::100, FF0E::101)
Page 441 Host A and Host C are IPv6 multicast receivers in two stub networks, N1 and N2. VLAN-interface 105 on Switch D and VLAN-interface 102 on Switch E act as C-BSRs and C-RPs. The C-BSR on Switch E has a higher priority. The IPv6 multicast group range to which the C-RP is designated is FF0E::101/64.
Page 442 # Enable IPv6 multicast routing on Switch A, enable MLD on VLAN-interface 300, and enable IPv6 PIM-SM on each interface. <SwitchA> system-view [SwitchA] multicast ipv6 routing-enable [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] mld enable [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...
Page 443 Vlan101 FE80::A01:201:2 Vlan102 FE80::A01:201:3 # Display information about the BSR and locally configured C-RP in effect on Switch A. [SwitchA] display pim ipv6 bsr-info Elected BSR Address: 1003::2 Priority: 20 Hash mask length: 128 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.
Page 444 # Display RP information on Switch A. [SwitchA] display pim ipv6 rp-info PIM-SM BSR RP information: prefix/prefix length: FF0E::101/64 RP: 4002::1 Priority: 192 HoldTime: 130 Uptime: 00:05:19 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 445: Ipv6 Pim-Sm Admin-Scope Zone Configuration Example
Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: pim-sm, UpTime: 00:02:15, Expires: 00:03:06 # Display IPv6 PIM multicast routing table information on Switch D. [SwitchD] display pim ipv6 routing-table Total 0 (*, G) entry; 1 (S, G) entry (4001::100, FF0E::100) RP: 1003::2 Protocol: pim-sm, Flag: SPT LOC ACT...
Page 446 VLAN-interface 101 of Switch B acts as a C-BSR and C-RP of admin-scope zone 1, which provides services for the IPv6 multicast groups with the Scope field value in their group addresses being 4. VLAN-interface 104 of Switch D acts as a C-BSR and C-RP of admin-scope zone 2, which also provides services for the IPv6 multicast groups with the Scope field value in their group addresses being 4.
Page 447 Figure 107 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 448 Enable IPv6 multicast routing and IPv6 administrative scoping, and enable IPv6 PIM-SM and MLD: # 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>...
Page 449 [SwitchB-Vlan-interface103] multicast ipv6 boundary scope 4 [SwitchB-Vlan-interface103] quit # 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...
Page 450 Scope: 14 Uptime: 00:01:45 Expires: 00:01:25 Elected BSR Address: 1002::2 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...
Page 451 # Display information about the BSR and locally configured C-RP on Switch F. [SwitchF] display pim ipv6 bsr-info Elected BSR Address: 8001::1 Priority: 64 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...
Page 452 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 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...
Page 453 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 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...
Page 454 prefix/prefix length: FF14::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 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...
Page 455 prefix/prefix length: FF84::/16 RP: 1002::2 Priority: 192 HoldTime: 130 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...
Page 456 Expires: 00:01:51 prefix/prefix length: FFF4::/16 RP: 1002::2 Priority: 192 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...
Page 457 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 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...
Page 458: Ipv6 Bidir-Pim Configuration Example
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 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFFE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39...
Page 459 Figure 108 Network diagram Loop0 Receiver 1 Receiver 2 Switch B Vlan-int200 Vlan-int102 Vlan-int102 Switch C Host A Host B Vlan-int101 Vlan-int103 IPv6 BIDIR-PIM Source 1 Source 2 Vlan-int101 Vlan-int103 Vlan-int100 Vlan-int400 Switch A Switch D Device Interface IPv6 address Device Interface IPv6 address...
Page 460 # On Switch B, enable IPv6 multicast routing, enable IPv6 PIM-SM on each interface, enable MLD in VLAN interface 200, and enable IPv6 BIDIR-PIM. <SwitchB> system-view [SwitchB] multicast ipv6 routing-enable [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] mld enable [SwitchB-Vlan-interface200] pim ipv6 sm [SwitchB-Vlan-interface200] quit [SwitchB] interface vlan-interface 101 [SwitchB-Vlan-interface101] pim ipv6 sm...
Page 461 [SwitchD-pim6] bidir-pim enable [SwitchD-pim6] quit On Switch C, configure VLAN interface 102 as a C-BSR, and loopback interface 0 as a C-RP for the entire IPv6 BIDIR-PIM domain. [SwitchC-pim6] c-bsr 2002::2 [SwitchC-pim6] c-rp 6001::1 bidir [SwitchC-pim6] quit Verifying the configuration # Display the DF information of IPv6 BIDIR-PIM on Switch A.
Page 462 # Display the DF information of the IPv6 multicast forwarding table on Switch A. [SwitchA] display multicast ipv6 forwarding-table df-info Multicast DF information Total 1 RP Total 1 RP matched 00001. RP Address: 6001::1 MID: 0, Flags: 0x2100000:0 Uptime: 00:08:32 RPF interface: Vlan-interface101 List of 1 DF interfaces: 1: Vlan-interface100...
Page 463: Ipv6 Pim-Ssm Configuration Example
00001. RP Address: 6001::1 MID: 0, Flags: 0x2100000:0 Uptime: 00:05:12 RPF interface: Vlan-interface103 List of 2 DF interfaces: 1: Vlan-interface300 2: Vlan-interface400 IPv6 PIM-SSM configuration example Network requirements 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.
Page 464 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 Vlan-int102 1003::2/64 Vlan-int104 3001::1/64 Vlan-int105 4002::2/64 Configuration procedure Enable IPv6 forwarding on each switch and configure the IPv6 address and prefix length for each interface as per Figure 109.
Page 465 Verifying the configuration # Display IPv6 PIM information on Switch A. [SwitchA] display pim ipv6 interface Interface NbrCnt HelloInt DR-Pri DR-Address Vlan100 FE80::A01:201:1 (local) Vlan101 FE80::A01:201:2 Vlan102 FE80::A01:201:3 Assume that Host A needs to receive the information a specific IPv6 multicast source S 4001::100/64 sends to IPv6 multicast group G FF3E::101.
Page 466: Troubleshooting Ipv6 Pim Configuration
Troubleshooting IPv6 PIM configuration Failure to build a multicast distribution tree correctly Symptom None of the routers in the network (including routers directly connected with IPv6 multicast sources and receivers) have IPv6 multicast forwarding entries. That is, a multicast distribution tree cannot be built correctly and clients cannot receive IPv6 multicast data.
Page 467: Ipv6 Multicast Data Abnormally Terminated On An Intermediate Router
IPv6 multicast data abnormally terminated on an intermediate router Symptom An intermediate router can receive IPv6 multicast data successfully, but the data cannot reach the last hop router. An interface on the intermediate router receives data, but no corresponding (S, G) entry is created in the IPv6 PIM routing table.
Page 468: Rpt Establishment Failure Or Source Registration Failure In Ipv6 Pim-Sm
Use the display pim ipv6 rp-info command to verify that the RP information is consistent on all routers. In the case of inconsistent RP information, configure consistent RP address on all the routers. 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.
Page 469: Configuring Ipv6 Mbgp (Available Only On The S5500-Ei)
Configuring IPv6 MBGP (available only on the S5500-EI) 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.
Page 470: Configuring Basic Ipv6 Mbgp Functions
Task Remarks Configuring IPv6 MBGP route preferences Configuring the default local preference Optional Configuring IPv6 MBGP route Configuring the MED attribute attributes Configuring the NEXT_HOP attribute Optional Configuring the AS_PATH attribute Optional Configuring IPv6 MBGP soft reset Optional Tuning and Enabling the IPv6 MBGP orf capability Optional optimizing IPv6...
Page 471: Configuring A Preferred Value For Routes From A Peer Or A Peer Group
Configuring a preferred value for routes from a peer or a peer group If you both reference a routing policy and use the command peer { ipv6-group-name | ipv6-address } preferred-value value to set a preferred value for routes from a peer or a peer group, the routing policy sets the specified preferred value for the routes that match it.
Page 472: Configuring Ipv6 Mbgp Route Redistribution
Step Command Remarks Inject a network into the IPv6 network ipv6-address prefix-length Not injected by default. MBGP routing table. [ route-policy route-policy-name | short-cut ] Configuring IPv6 MBGP route redistribution Step Command Description Enter system view. system-view Enter BGP view. bgp as-number Enter IPv6 MBGP multicast ipv6-family multicast...
Page 473: 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. Not advertised by default. With the peer default-route-advertise peer { ipv6-group-name | command executed, the router sends a Advertise a default route to an ipv6-address } default route with the next hop as itself IPv6 MBGP peer or peer...
Page 474: Configuring Inbound Ipv6 Mbgp Route Filtering
NOTE: Members of an IPv6 MBGP peer group must have the same outbound route filtering policy as the peer • group. IPv6 BGP advertises the redistributed routes that pass the specified policy to the IPv6 MBGP peer. • Configuring inbound IPv6 MBGP route filtering Step Command Remarks...
Page 475: Configuring Ipv6 Mbgp Route Attributes
Step Command Remarks Enter BGP view. bgp as-number Enter IPv6 MBGP address ipv6-family multicast family view. dampening [ half-life-reachable Optional. Configure IPv6 MBGP route half-life-unreachable reuse dampening parameters. suppress ceiling | route-policy Not configured by default. route-policy-name ]* Configuring IPv6 MBGP route attributes This section describes how to use IPv6 MBGP route attributes to affect IPv6 MBGP route selection.
Page 476: Configuring The Med Attribute
Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter IPv6 MBGP address ipv6-family multicast family view. Optional. Set the default local default local-preference value By default, the default local preference. preference is 100. Configuring the MED attribute Step Command Remarks...
Page 477: Configuring The As_Path Attribute
Step Command Remarks Enter BGP view. bgp as-number Enter IPv6 MBGP address ipv6-family multicast family view. Optional. By default, IPv6 MBGP specifies Configure the router as the peer { ipv6-group-name | the local router as the next hop for next hop of routes sent to the ipv6-address } next-hop-local routes sent to an EBGP peer or a peer or the peer group.
Page 478: Configuring Ipv6 Mbgp Soft Reset
Configuring IPv6 MBGP soft reset After you modify a route selection policy, you must reset IPv6 MBGP connections to make the new one take effect. The current IPv6 MBGP implementation supports the route-refresh feature that enables dynamic route refresh without terminating IPv6 MBGP connections. If a peer that does not support route refresh exists in the network, you must configure the peer keep-all-routes command to save all routes from the peer.
Page 479: Enabling The Ipv6 Mbgp Orf Capability
Step Command Remarks Keep all routes from a peer or a peer group regardless of peer { ipv6-group-name | ipv6-address } Not kept by default. whether they pass the keep-all-routes inbound filtering policy. refresh bgp ipv6 multicast { all | Perform soft reset manually.
Page 480: Configuring The Maximum Number Of Equal-Cost Routes For Load-Balancing
Table 12 Description of the send, receive, and both parameters and the negotiation result Local parameter Peer parameter Negotiation result • receive The ORF sending capability is enabled locally and the ORF send receiving capability is enabled on the peer. •...
Page 481: Configuring Ipv6 Mbgp Community
Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter IPv6 address family ipv6-family view. Create an IPv6 BGP peer group ipv6-group-name [ external group. | internal ] peer ipv6-address group Add a peer to the peer group. ipv6-group-name [ as-number By default, no peer is added.
Page 482: Configuring An Ipv6 Mbgp Route Reflector
NOTE: You must configure a routing policy to define the COMMUNITY attribute, and apply the policy to outgoing routes. Configuring an IPv6 MBGP route reflector To guarantee connectivity between IPv6 multicast IBGP peers, you must make them fully meshed. However, this becomes unpractical when too many IPv6 multicast IBGP peers exist. Using route reflectors can solve the problem.
Page 483 Task Command Remarks Display the IPv6 MBGP AS path display bgp ipv6 multicast paths [ as-regular-expression Available in information of routes. | | { begin | exclude | include } regular-expression ] any view Display IPv6 MBGP peer display bgp ipv6 multicast peer [ [ ipv6-address ] Available in information or peer group verbose ] [ | { begin | exclude | include }...
Page 484: Resetting Ipv6 Mbgp Connections
Task Command Remarks Display the multicast routing display ipv6 multicast routing-table ipv6-address Available in information of the specified prefix-length [ longer-match ] [ verbose ] [ | { begin | any view destination address. exclude | include } regular-expression ] Resetting IPv6 MBGP connections When you change an IPv6 MBGP routing policy, you can make the new configuration effective by resetting the IPv6 MBGP connections.
Page 485 Figure 110 Network diagram Device Interface IP address Device Interface IP address Source 1002::100/64 Switch C Vlan-int200 3002::1/64 Switch A Vlan-int100 1002::1/64 Vlan-int102 2001::2/64 Vlan-int101 1001::1/64 Vlan-int104 3001::1/64 Switch B Vlan-int101 1001::2/64 Switch D Vlan-int103 2002::2/64 Vlan-int102 2001::1/64 Vlan-int104 3001::2/64 Vlan-int103 2002::1/64 Configuration procedure...
Page 486 [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 # Configure an IPv6 PIM domain border on Switch B.
Page 487 [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 Peers in established state : 3...
Page 488: Index
Index A C D E I M O P T Configuring IGMP SSM mapping,1 18 Configuring IPv6 BIDIR-PIM,399 Adjusting IGMP performance,1 12 Configuring IPv6 MBGP route attributes,456 Adjusting MLD performance,348 Configuring IPv6 multicast routing and forwarding,331 Appendix,56 Configuring IPv6 PIM common features,410 Appendix,306 Configuring IPv6 PIM...
Page 489 Displaying and maintaining IPv6 PIM,417 Multicast architecture,7 Displaying and maintaining IPv6 PIM snooping,310 Multicast models,6 Displaying and maintaining MBGP,260 Multicast packet forwarding mechanism,13 Displaying and maintaining MLD,356 Multicast support for VPNs,13 Displaying and maintaining MLD snooping,289 Multicast VLAN configuration examples,70 Displaying and maintaining MSDP,225 Multicast VLAN configuration task...
Page 490 Tuning and optimizing IPv6 MBGP networks,458 Tuning and optimizing MBGP networks,254...

This manual is also suitable for:

S5500-si

H3C S5500-EI Configuration Manual

Quick Links

Troubleshooting

Related Manuals for H3C S5500-EI

Summary of Contents for H3C S5500-EI