Page 1: Configuration Guide
Configuration Guide Abstract This document describes the software features for the HP A Series products and guides you through the software configuration procedures. These configuration guides also provide configuration examples to help you apply software features to different network scenarios.
Page 2 The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an...
Page 3: Table Of Contents
Contents Multicast overview ······················································································································································· 1 Introduction to multicast ···················································································································································· 1 Comparison of information transmission techniques ···························································································· 1 Features of multicast ················································································································································· 3 Common notations in multicast ······························································································································· 4 Advantages and applications of multicast ············································································································· 4 Multicast models ································································································································································ 5 Multicast architecture ························································································································································ 5 Multicast addresses ··················································································································································...
Page 4 Configuring multicast group replacement ··········································································································· 33 Configuring 802.1p precedence for IGMP messages ······················································································ 34 Configuring a multicast user control policy ········································································································ 35 Displaying and maintaining IGMP snooping ·············································································································· 36 IGMP snooping configuration examples ····················································································································· 36 Group policy and simulated joining configuration example ············································································ 36 Static port configuration example ·······················································································································...
Page 5 Introduction to IGMPv1 ········································································································································· 84 Enhancements in IGMPv2 ···································································································································· 86 Enhancements in IGMPv3 ···································································································································· 86 IGMP SSM mapping ············································································································································· 88 IGMP proxying ······················································································································································ 89 Multi-instance IGMP ·············································································································································· 90 Protocols and standards ······································································································································· 90 IGMP configuration task list ·········································································································································· 90 Configuring basic functions of IGMP ··························································································································· 91 Configuration prerequisites ··································································································································...
Page 6 Configuration prerequisites ································································································································ 131 Enabling PIM-SM ················································································································································· 132 Configuring an RP ··············································································································································· 133 Configuring a BSR ··············································································································································· 135 Configuring administrative scoping ·················································································································· 139 Configuring multicast source registration ········································································································· 141 Disabling SPT switchover ···································································································································· 142 Configuring BIDIR-PIM ················································································································································· 143 BIDIR-PIM configuration task list ························································································································· 143 Configuration prerequisites ································································································································...
Page 7 Configuring an MSDP mesh group ··················································································································· 198 Configuring MSDP peer connection control ····································································································· 198 Configuring SA messages related parameters ········································································································· 199 Configuration prerequisites ································································································································ 199 Configuring SA message content ······················································································································ 199 Configuring SA request messages ····················································································································· 200 Configuring SA message filtering rules ············································································································· 200 Configuring the SA cache mechanism ··············································································································...
Page 8 MBGP configuration example ···································································································································· 236 MLD snooping configuration ·································································································································· 240 MLD snooping overview ·············································································································································· 240 Introduction to MLD snooping ···························································································································· 240 Basic concepts in MLD snooping ······················································································································· 241 How MLD snooping works ································································································································· 242 MLD snooping proxying ····································································································································· 244 Protocols and standards ····································································································································· 245 MLD snooping configuration task list ·························································································································...
Page 9 Configuring IPv6 sub-VLAN-based IPv6 multicast VLAN ························································································· 282 Configuration prerequisites ································································································································ 282 Configuring sub-VLAN-based IPv6 multicast VLAN ························································································· 282 Configuring port-based IPv6 multicast VLAN ············································································································ 283 Configuration prerequisites ································································································································ 283 Configuring user port attributes ························································································································· 283 Configuring IPv6 multicast VLAN ports ············································································································· 284 Displaying and maintaining IPv6 multicast VLAN ····································································································...
Page 10 MLD configuration examples ······································································································································ 319 Basic MLD functions configuration example ····································································································· 319 MLD SSM mapping configuration example ····································································································· 321 MLD proxying configuration example ··············································································································· 324 Troubleshooting MLD ··················································································································································· 325 No member information on the receiver-side router ························································································ 325 Inconsistent memberships on routers on the same subnet ··············································································· 326 IPv6 PIM configuration (available only on the A5500 EI) ···················································································...
Page 11 Resetting IPv6 MBGP connections ····················································································································· 420 Clearing IPv6 MBGP information ······················································································································ 421 IPv6 MBGP configuration example ···························································································································· 421 Support and other resources ·································································································································· 424 Contacting HP ······························································································································································ 424 Subscription service ············································································································································ 424 Related information ······················································································································································ 424 Documents ···························································································································································· 424 Websites ······························································································································································ 424...
Page 12 Conventions ·································································································································································· 425 Index ········································································································································································ 427...
Page 13: Multicast Overview
Multicast overview NOTE: This document focuses on the IP multicast technology and device operations. Unless otherwise stated, multicast the term in this document refers to IP multicast. 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.
Page 14 In unicast transmission, the traffic transmitted over the network is proportional to the number of hosts that need the information. If a large number of hosts need the information, the information source must send a copy of the same information to each of these hosts. Sending many copies can place a tremendous pressure on the information source and the network bandwidth.
Page 15: Features Of Multicast
Figure 3 Multicast transmission The multicast source sends only one copy of the information to a multicast group. In Figure 3, 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 16: Common Notations In Multicast
manage multicast group memberships on stub subnets with attached group members. A multicast router itself can be a multicast group member. For a better understanding of the multicast concept, you can compare multicast transmission to the transmission of TV programs. Table 1 An analogy between TV transmission and multicast transmission TV transmission Multicast transmission...
Page 17: Multicast Models
Communication for training and cooperative operations, such as distance learning and • telemedicine Data warehouse and financial applications, such as stock quotes • Any other point-to-multipoint applications for data distribution • Multicast models Based on how the receivers treat the multicast sources, the multicast models include any-source multicast (ASM), source-filtered multicast (SFM), and source-specific multicast (SSM).
Page 18: Multicast Addresses
Multicast routing—A multicast distribution tree—a forwarding path tree for multicast data on the network—is constructed for delivering multicast data from a multicast source to receivers. Multicast applications—A software system that supports multicast applications, such as video conferencing, must be installed on multicast sources and receiver hosts. The TCP/IP stack must support reception and transmission of multicast data.
Page 19 Address Description 224.0.0.4 Distance Vector Multicast Routing Protocol (DVMRP) routers 224.0.0.5 Open Shortest Path First (OSPF) routers 224.0.0.6 OSPF designated routers and backup designated routers 224.0.0.7 Shared Tree (ST) routers 224.0.0.8 ST hosts 224.0.0.9 Routing Information Protocol version 2 (RIPv2) routers 224.0.0.11 Mobile agents 224.0.0.12...
Page 20 Description • When set to 0, it indicates that this address is an IPv6 multicast address not based on a unicast prefix. • When set to 1, it indicates that this address is an IPv6 multicast address based on a unicast prefix—the T bit must also be set to 1.
Page 21: Multicast Protocols
Figure 6 IPv4-to-MAC address mapping The most-significant four bits of a multicast IPv4 address are 1110, which indicates that this address is a multicast address. Only 23 bits of the remaining 28 bits are mapped to a MAC address, so five bits of the multicast IPv4 address are lost.
Page 22 Layer 3 multicast protocols Layer 3 multicast protocols include multicast group management protocols and multicast routing protocols. Figure 8 Positions of Layer 3 multicast protocols Multicast group management protocols Typically, the Internet Group Management Protocol (IGMP) or Multicast Listener Discovery Protocol (MLD) is used between hosts and Layer 3 multicast devices that directly connect to the hosts.
Page 23: Multicast Packet Forwarding Mechanism
Figure 9 Positions of Layer 2 multicast protocols Source Multicast VLAN /IPv6 Multicast VLAN IGMP Snooping /MLD Snooping Receiver Receiver IPv4/IPv6 multicast packets IGMP snooping and MLD snooping IGMP snooping and MLD snooping are multicast constraining mechanisms that run on Layer 2 devices. They manage and control multicast groups by monitoring and analyzing IGMP or MLD messages exchanged between the hosts and Layer 3 multicast devices, effectively controlling the flooding of multicast data in a Layer 2 network.
Page 24: Multi-Instance Multicast
Multi-instance multicast Multi-instance multicast refers to multicast in virtual private networks (VPNs). Introduction to the multi-instance concept VPN networks must be isolated from one another and from the public network. Figure 10 Networking diagram for VPN VPN A CE a2 CE b2 CE b3 PE 2...
Page 25 Implement information exchange and data conversion between the public network and VPN • instances. NOTE: Only one set of unified multicast service runs on a non-PE device. It is called a “public network.” The configuration made in VPN instance view takes effect only on the VPN instance interface. An interface that does not belong to any VPN instance is called a “public network interface.”...
Page 26: Igmp Snooping Configuration
IGMP snooping configuration IGMP snooping overview IGMP snooping is a multicast constraining mechanism that runs on Layer 2 devices to manage and control multicast groups. Principle of IGMP snooping By analyzing received IGMP messages, a Layer 2 switch that runs IGMP snooping establishes mappings between ports and multicast MAC addresses, and forwards multicast data based on these mappings.
Page 27: Basic Concepts In Igmp Snooping
Basic concepts in IGMP snooping IGMP snooping related ports Figure 12, Router A connects to the multicast source, IGMP snooping runs on Switch A and Switch B, and Host A and Host C are receiver hosts—also called “multicast group members.” Figure 12 IGMP snooping related ports Receiver Router A...
Page 28: How Igmp Snooping Works
Aging timers for dynamic ports in IGMP snooping and related messages and actions Message before Timer Description Action after expiry expiry For each dynamic router IGMP general query of port, the switch sets a The switch removes this Dynamic router port which the source timer initialized to the port from its router port...
Page 29 After receiving an IGMP report, the switch forwards it through all the router ports in the VLAN, resolves the address of the reported multicast group. The switch also performs the following judgment: If no entry in the forwarding table exists for the reported group, the switch creates an entry, adds •...
Page 30: Igmp Snooping Proxying
If the port receives no IGMP report in response to the group-specific query before its aging timer • expires, it indicates that no hosts attached to the port are still monitoring that group address. The switch removes the port from the outgoing port list of the entry in the forwarding table for that multicast group when the aging timer expires.
Page 31: Protocols And Standards
IGMP message Actions When receiving a report for a multicast group, the proxy looks up the multicast forwarding table for the entry for the multicast group. If the forwarding entry is found with the receiving port contained as a dynamic member port in the outgoing port list, the proxy resets the aging timer for the entry.
Page 32: Configuring Basic Functions Of Igmp Snooping
Task Remarks Configuring the function of dropping unknown Optional multicast data Configuring IGMP report suppression Optional Configuring the maximum number of multicast groups Optional that a port can join Configuring 802.1p precedence for IGMP messages Optional Configuring multicast group replacement Optional Configuring a multicast user control policy Optional...
Page 33: Configuring The Version Of Igmp Snooping
To do... Use the command... Remarks Enter VLAN view vlan vlan-id — Required Enable IGMP snooping in the VLAN igmp-snooping enable Disabled by default NOTE: IGMP snooping must be enabled globally before it can be enabled on a VLAN. After enabling IGMP snooping in a VLAN, do not enable IGMP or PIM on the corresponding VLAN interface.
Page 34: Configuring Igmp Snooping Port Functions
To do... Use the command... Remarks Enter system view system-view — Required mac-address multicast mac- Configure a static multicast MAC address interface interface-list vlan No static multicast MAC address address entry vlan-id entries exist by default. Configuring a static multicast MAC address entry in interface view Follow these steps to configure static multicast MAC address entries in interface view To do...
Page 35: Configuring Aging Timers For Dynamic Ports
Configuring aging timers for dynamic ports If the switch receives no IGMP general queries or PIM hello messages on a dynamic router port, the switch removes the port from the router port list when the aging timer of the port expires. If the switch receives no IGMP reports for a multicast group on a dynamic member port, the switch removes the port from the outgoing port list of the entry in the forwarding table for that multicast group when the aging timer of the port for that group expires.
Page 36: Configuring Simulated Joining
To do... Use the command... Remarks interface interface-type interface- Enter Ethernet interface view, number Required Layer 2 aggregate interface view, Use either approach port-group manual port-group- or port group view name Required igmp-snooping static-group Configure the port as a static group-address [ source-ip source- No static member ports exist by member port...
Page 37: Configuring Fast-Leave Processing
NOTE: A simulated host is equivalent to an independent host. For example, when a simulated member host receives an IGMP query, it gives a response separately. Unlike a static member port, a port that you configure as a simulated member host ages out like a dynamic member port.
Page 38: Disabling A Port From Becoming A Dynamic Router Port
Disabling a port from becoming a dynamic router port The following problems might exist in a multicast access network: After receiving an IGMP general query or a 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 39: Enabling Igmp Snooping Querier
Enabling IGMP snooping querier In an IP multicast network that runs IGMP, a multicast router or Layer 3 multicast switch sends IGMP queries, so that all Layer 3 multicast devices can establish and maintain multicast forwarding entries, in order to forward multicast traffic correctly at the network layer. This router or Layer 3 switch is called the “IGMP querier”.
Page 40: Configuring Source Ip Address Of Igmp Queries
To avoid this problem, when a Layer 2 switch acts as the IGMP snooping querier, HP recommends you to configure a non-all-zero IP address as the source IP address of IGMP queries.
Page 41: Configuring Igmp Snooping Proxying
CAUTION: The source address of IGMP query messages might affect the IGMP querier election within the segment. Configuring IGMP snooping proxying Configuration prerequisites Before you configure IGMP snooping proxying in a VLAN, complete the following tasks: Enable IGMP snooping in the VLAN •...
Page 42: Configuring An Igmp Snooping Policy
Configuring an IGMP snooping policy Configuration prerequisites Before you configure an IGMP snooping policy, complete the following tasks: Enable IGMP snooping in the VLAN • Determine the ACL rules for multicast group filtering • Determine the maximum number of multicast groups that can pass the ports •...
Page 43: Configuring Multicast Source Port Filtering
To do... Use the command... Remarks Required By default, no group filter is igmp-snooping group-policy acl- Configure a multicast group filter configured on the current port. number [ vlan vlan-list ] That is, the hosts on this port can join any valid multicast group. Configuring multicast source port filtering When the multicast source port filtering feature is enabled on a port, the port can connect to only multicast receivers rather than to multicast sources, because the port blocks all multicast data packets but...
Page 44: Configuring Igmp Report Suppression
When the function of dropping unknown multicast data is enabled, the switch forwards unknown • multicast data to its router ports instead of flooding it in the VLAN. If no router ports exist, the switch drops the unknown multicast data. Follow these steps to configure the function of dropping unknown multicast data in a VLAN: To do...
Page 45: Configuring Multicast Group Replacement
A5500 EI Switch Series • 1000 by default on the A5500 SI Switch Series NOTE: When you configure this maximum number, if the number of multicast groups the port has joined exceeds the configured maximum value, the system deletes all the forwarding entries for the port from the IGMP snooping forwarding table, and the hosts on this port join multicast groups again until the number of multicast groups that the port joins reaches the maximum value.
Page 46: Configuring 802.1P Precedence For Igmp Messages
Configuring multicast group replacement on a port or a group of ports Follow these steps to configure multicast group replacement on a port or a group of ports: To do... Use the command... Remarks Enter system view system-view — interface interface-type interface- Enter Ethernet interface view, number Required...
Page 47: Configuring A Multicast User Control Policy
Configuring a multicast user control policy Multicast user control policies are configured on access switches to allow only authorized users to receive requested multicast traffic flows. This helps restrict users from ordering certain multicast-on- demand programs. In practice, a device first needs to perform authentication (802.1X authentication, for example) on connected hosts through a RADIUS server.
Page 48: Displaying And Maintaining Igmp Snooping
Displaying and maintaining IGMP snooping To do... Use the command... Remarks display igmp-snooping group [ vlan vlan-id ] [ Display IGMP snooping group Available in slot slot-number ] [ verbose ] [ | { begin | information any view exclude | include } regular-expression ] Display the statistics information of display igmp-snooping statistics [ | { begin | Available in...
Page 49 Figure 14 Network diagram for group policy simulated joining configuration Configuration procedure Configure IP addresses Configure an IP address and subnet mask for each interface according to Figure 14 (details not shown). Configure Router A # Enable IP multicast routing, enable PIM-DM on each interface, and enable IGMP on GigabitEthernet 1/0/1.
Page 50 # Configure a multicast group filter so that the hosts in VLAN 100 can join only the multicast group 224.1.1.1. [SwitchA] acl number 2001 [SwitchA-acl-basic-2001] rule permit source 224.1.1.1 0 [SwitchA-acl-basic-2001] quit [SwitchA] igmp-snooping [SwitchA-igmp-snooping] group-policy 2001 vlan 100 [SwitchA-igmp-snooping] quit # Configure GigabitEthernet 1/0/3 and GigabitEthernet 1/0/4 as simulated hosts for multicast group 224.1.1.1.
Page 51: Static Port Configuration Example
Static port configuration example Network requirements As shown in Figure 15, Router A connects to a multicast source—Source—through GigabitEthernet • 1/0/2, and to Switch A through GigabitEthernet 1/0/1. IGMPv2 will run on Router A, and IGMPv2 snooping will run on Switch A, Switch B and Switch C, •...
Page 52 Configuration procedure Configure IP addresses Configure an IP address and subnet mask for each interface according to Figure 15 (details not shown). Configure Router A # Enable IP multicast routing, enable PIM-DM on each interface, and enable IGMP on GigabitEthernet 1/0/1.
Page 53 [SwitchC] igmp-snooping [SwitchC-igmp-snooping] quit # Create VLAN 100, assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/5 to this VLAN, and enable IGMP snooping in the VLAN. [SwitchC] vlan 100 [SwitchC-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/5 [SwitchC-vlan100] igmp-snooping enable [SwitchC-vlan100] quit # Configure GigabitEthernet 1/0/3 and GigabitEthernet 1/0/5 as static member ports for multicast group 224.1.1.1.
Page 54: Igmp Snooping Querier Configuration Example
Total 1 IP Source(s). Total 1 MAC Group(s). Port flags: D-Dynamic port, S-Static port, C-Copy 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. GE1/0/2 (D) ( 00:01:23 ) IP group(s):the following ip group(s) match to one mac group.
Page 55 Figure 16 Network diagram for IGMP snooping querier configuration Configuration procedure Configure switch A # Enable IGMP snooping globally. <SwitchA> system-view [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 100 and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/3 # Enable IGMP snooping and the function of dropping unknown multicast traffic in VLAN 100.
Page 56: Igmp Snooping Proxying Configuration Example
# Enable IGMP snooping and the function of dropping unknown multicast traffic in VLAN 100. [SwitchB-vlan100] igmp-snooping enable [SwitchB-vlan100] igmp-snooping drop-unknown [SwitchB-vlan100] quit Configurations on Switch C and Switch D are similar to the configuration on Switch B. Verify the configuration After the IGMP snooping querier starts to work, all the switches but the querier can receive IGMP general queries.
Page 57 Figure 17 Network diagram for IGMP snooping proxying configuration Configuration procedure Configure IP addresses for interfaces Configure an IP address and subnet mask for each interface according to Figure 17 (details not shown). Configure Router A # Enable IP multicast routing, enable PIM-DM on each interface, and enable IGMP on GigabitEthernet 1/0/1.
Page 58 Verify the configuration After the configuration is completed, Host A and Host B send IGMP join messages for group 224.1.1.1. Receiving the messages, Switch A sends a join message for the group out port GigabitEthernet 1/0/1— a router port—to Router A. Use the display igmp-snooping group command and the display igmp group command to display information about IGMP snooping groups and IGMP multicast groups.
Page 59: Multicast Source And User Control Policy Configuration Example
Total 1 IP Source(s). Total 1 MAC Group(s). Port flags: D-Dynamic port, S-Static port, C-Copy 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. GE1/0/1 (D) ( 00:01:23 ) IP group(s):the following ip group(s) match to one mac group.
Page 60 Figure 18 Network diagram for multicast source/user control policy configuration Source 1 1.1.1.1/24 GE1/0/1 Source 2 Vlan-int101 Receiver GE1/0/2 Switch B 1.1.1.2/24 Vlan-int102 GE1/0/1 GE1/0/3 2.1.1.2/24 GE1/0/4 Vlan-int104 GE1/0/3 Host A GE1/0/2 4.1.1.1/24 2.1.1.1/24 Vlan-int103 3.1.1.2/24 Switch A RADIUS server 3.1.1.1/24 Host B Configuration procedures...
Page 61 [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 CAUTION: When configuring a multicast source control policy, you need to apply an advanced ACL to match both...
Page 62 # Create ISP domain domain1; reference scheme1 for the authentication, authorization, and accounting of LAN users; specify domain1 as the default ISP domain. [SwitchA] domain domain1 [SwitchA-isp-domian1] authentication lan-access radius-scheme scheme1 [SwitchA-isp-domian1] authorization lan-access radius-scheme scheme1 [SwitchA-isp-domian1] accounting lan-access radius-scheme scheme1 [SwitchA-isp-domian1] quit [SwitchA] domain default enable domain1 # Globally enable 802.1X and then enable it on GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2...
Page 63 [SwitchB-radius-scheme2] user-name-format without-domain [SwitchB-radius-scheme2] quit # Create an ISP domain domain2; reference scheme2 for the authentication, authorization, and accounting of LAN users; specify domain2 as the default ISP domain. [SwitchB] domain domain2 [SwitchB-isp-domian2] authentication lan-access radius-scheme scheme2 [SwitchB-isp-domian2] authorization lan-access radius-scheme scheme2 [SwitchB-isp-domian2] accounting lan-access radius-scheme scheme2 [SwitchB-isp-domian2] quit [SwitchB] domain default enable domain2...
Page 64: Troubleshooting Igmp Snooping Configuration
GE1/0/3 (D) ( 00:04:10 ) MAC group(s): MAC group address:0100-5e01-0101 Host port(s):total 1 port. GE1/0/3 The output shows that GigabitEthernet 1/0/3 on Switch B has joined 224.1.1.1 but not 224.1.1.2. 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.
Page 65: 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 66 If PIM is disabled on the switch, one of the following occurs: If IGMP is disabled, the switch deletes all its dynamic router ports. If IGMP is enabled, the switch maintains all its dynamic member ports and dynamic router ports.
Page 67: Multicast Vlan Configuration
Multicast VLAN configuration Multicast VLAN overview In the traditional multicast programs-on-demand mode shown in Figure 19, 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 68 Figure 20 Sub-VLAN-based multicast VLAN Multicast packets VLAN 10 (Multicast VLAN) VLAN 2 VLAN 2 Receiver VLAN 3 Host A VLAN 4 VLAN 3 Receiver Host B Router A Switch A Source IGMP querier VLAN 4 Receiver Host C After the configuration, IGMP snooping manages router ports in the multicast VLAN and member ports in the sub-VLANs.
Page 69: Multicast Vlan Configuration Task List
NOTE: For more information about IGMP snooping, router ports, and member ports, see the chapter “IGMP snooping configuration.” Layer 2—LAN Switching Configuration Guide For more information about VLAN tags, see the Multicast VLAN configuration task list Complete the following tasks to configure multicast VLAN: Task Remarks Configuring sub-VLAN-based multicast VLAN...
Page 70: Configuring Port-Based Multicast Vlan
NOTE: You cannot configure multicast VLAN on a device with IP multicast routing enabled. The VLAN to be configured as a multicast VLAN must exist. The VLANs to be configured as sub-VLANs of the multicast VLAN must exist and must not be sub- VLANs of any other multicast VLAN.
Page 71: Configuring Multicast Vlan Ports
To do... Use the command... Remarks Specify the user VLAN that Required comprises the current user ports port hybrid pvid vlan vlan-id VLAN 1 by default as the default VLAN Configure the current user ports to Required permit packets of the specified port hybrid vlan vlan-id-list By default, a hybrid port permits multicast VLANs to pass and...
Page 72: Displaying And Maintaining Multicast Vlan
To do… Use this command… Remarks port-group manual port-group- name Required Configure the current port as a member port of the multicast port multicast-vlan vlan-id By default, a user port does not VLAN belong to any multicast VLAN. NOTE: You cannot configure multicast VLAN on a device with multicast routing enabled. The VLAN to be configured as a multicast VLAN must exist.
Page 73 Network diagram Figure 22 Network diagram for sub-VLAN-based multicast VLAN configuration Source IGMP querier Router A GE1/0/1 1.1.1.2/24 GE1/0/2 1.1.1.1/24 10.110.1.1/24 GE1/0/1 Switch A GE1/0/2 GE1/0/4 GE1/0/3 Receiver Receiver Receiver Host A Host B Host C VLAN 2 VLAN 3 VLAN 4 Configuration procedure Configure IP addresses...
Page 74 # Create VLAN 10, assign GigabitEthernet 1/0/1 to this VLAN and enable IGMP snooping in the VLAN. [SwitchA] vlan 10 [SwitchA-vlan10] port gigabitethernet 1/0/1 [SwitchA-vlan10] igmp-snooping enable [SwitchA-vlan10] quit # Configure VLAN 10 as a multicast VLAN and configure VLAN 2 through VLAN 4 as its sub-VLANs. [SwitchA] multicast-vlan 10 [SwitchA-mvlan-10] subvlan 2 to 4 [SwitchA-mvlan-10] quit...
Page 75: Port-Based Multicast Vlan Configuration
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):4. Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s).
Page 76 IGMPv2 runs on Router A. IGMPv2 snooping runs on Switch A. Router A acts as the IGMP querier. • Switch A’s GigabitEthernet 1/0/1 belongs to VLAN 10, GigabitEthernet 1/0/2 through • GigabitEthernet 1/0/4 belong to VLAN 2 through VLAN 4 respectively, and Host A through Host C are attached to GigabitEthernet 1/0/2 through GigabitEthernet 1/0/4 of Switch A respectively.
Page 77 <SwitchA> system-view [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 10, assign GigabitEthernet 1/0/1 to VLAN 10, and enable IGMP snooping in this VLAN. [SwitchA] vlan 10 [SwitchA-vlan10] port gigabitethernet 1/0/1 [SwitchA-vlan10] igmp-snooping enable [SwitchA-vlan10] quit # Create VLAN 2 and enable IGMP snooping in the VLAN. [SwitchA] vlan 2 [SwitchA-vlan2] igmp-snooping enable [SwitchA-vlan2] quit...
Page 78 [SwitchA] display igmp-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 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).
Page 79: Multicast Routing And Forwarding Configuration (Available Only On The A5500 Ei)
Multicast routing and forwarding configuration (available only on the A5500 EI) NOTE: router The term in this document refers to both routers and Layer 3 switches. The interfaces in this document refer to Layer 3 interfaces in generic sense and Ethernet interfaces that operate in route mode.
Page 80 When performing an RPF check, a router searches its unicast routing table, MBGP routing table, and multicast static routing table at the same time. The following describes the specific process: The router first chooses an optimal route from each of the unicast routing table, the MBGP routing table, and the multicast static routing table: The router automatically chooses an optimal unicast route by searching its unicast routing table and using the IP address of the packet source as the destination address.
Page 81: Multicast Static Routes
If the interface that received the packet is the RPF interface, the RPF check succeeds, and the router forwards the packet to all the outgoing interfaces. If the interface that received the packet is not the RPF interface, the RPF check fails, and the router discards the packet.
Page 82 RPF route change The topology structure of a multicast network is the same as that of a unicast network, and multicast traffic follows the same transmission path that unicast traffic does. You can configure a multicast static route for a given multicast source to change the RPF route to create a transmission path for multicast traffic different from the transmission path for unicast traffic.
Page 83: Multicast Traceroute
Figure 26 Creating an RPF route As shown in Figure 26, the RIP domain and the OSPF domain are unicast isolated from each other. When no multicast static route is configured, the hosts—Receivers—in the OSPF domain cannot receive the multicast packets that the multicast source sent in the RIP domain. After you configure a multicast static route on Router C and Router D, specifying Router B as the RPF neighbor of Router C and Router C as the RPF neighbor of Router D, the receivers can receive multicast data that the multicast source sent.
Page 84: Configuration Task List
Query—Its IGMP Type field is set to 0x1F • Request—Its IGMP Type field is set to 0x1F • Response—Its IGMP Type field is set to 0x1E • 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 85: Configuring Multicast Routing And Forwarding
To do... Use the command... Remarks Required Enable IP multicast routing multicast routing-enable Disabled by default Enabling IP multicast routing in a VPN instance Follow these steps to enable IP multicast routing in a VPN instance: To do… Use the command… Remarks Enter system view system-view...
Page 86: Configuring A Multicast Routing Policy
To do... Use the command... Remarks ip rpf-route-static [ vpn-instance vpn-instance-name ] Required source-address { mask | mask-length } [ protocol [ Configure a multicast process-id ] ] [ route-policy policy-name ] { rpf-nbr- No multicast static route static route address | interface-type interface-number } [ configured by default.
Page 87: Configuring A Multicast Forwarding Range
• NOTE: Setting the minimum TTL is not supported on HP A5500 EI Switch Series. You can configure a forwarding boundary specific to a particular multicast group on all interfaces that support multicast forwarding. A multicast forwarding boundary sets the boundary condition for the multicast groups in the specified range.
Page 88: Tracing A Multicast Path
downstream nodes for a single multicast forwarding entry is smaller than the current number, the downstream nodes in excess are not deleted immediately. Instead, the multicast routing protocol that runs on the switch deletes them. The switch no longer adds new multicast forwarding entries for newly added downstream nodes until the number of existing downstream nodes comes down below the configured value.
Page 89: Displaying And Maintaining Multicast Routing And Forwarding
Displaying and maintaining multicast routing and forwarding To do... Use the command... Remarks display multicast [ all-instance | vpn-instance vpn- Display multicast boundary instance-name ] boundary [ group-address [ mask | mask- Available in information length ] ] [ interface interface-type interface-number ] [ | { any view begin | exclude | include } regular-expression ] display multicast [ all-instance | vpn-instance vpn-...
Page 90: Configuration Examples
NOTE: For more information about designated forwarder (DF), see the chapter “PIM configuration.” CAUTION: The reset command clears the information in the multicast routing table or the multicast forwarding table, and might cause failure of multicast transmission. When a routing entry is deleted from the multicast routing table, the corresponding forwarding entry is also deleted from the multicast forwarding table.
Page 91 Configuration procedure Configure IP addresses and unicast routing Configure the IP address and subnet mask for each interface according to Figure 27 (details not shown). Enable OSPF on the switches in the PIM-DM domain. Ensure the network-layer interoperation among the switches in the PIM-DM domain.
Page 92: Creating An Rpf Route
# Configure a multicast static route on Switch B, specifying Switch C as its RPF neighbor on the route to Source. [SwitchB] ip rpf-route-static 50.1.1.100 24 20.1.1.2 Verify the configuration # Use the display multicast rpf-info command to view the information about the RPF route to Source on Switch B.
Page 93 Enable OSPF on Switch B and Switch C. Ensure the network-layer interoperation among Switch B and Switch C. Ensure that the switches can dynamically update their routing information by leveraging the unicast routing protocol (details not shown). Enable IP multicast routing, and enable PIM-DM and IGMP # Enable IP multicast routing on Switch C, enable PIM-DM on each interface, and enable IGMP on VLAN-interface 100.
Page 94: Troubleshooting Multicast Routing And Forwarding
Route selection rule: preference-preferred Load splitting rule: disable [SwitchC] display multicast rpf-info 50.1.1.100 RPF information about source 50.1.1.100: RPF interface: Vlan-interface101, RPF neighbor: 20.1.1.2 Referenced route/mask: 50.1.1.0/24 Referenced route type: multicast static Route selection rule: preference-preferred Load splitting rule: disable The output shows that the RPF routes to Source 2 exist on Switch B and Switch C.
Page 95: 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 check whether the (S, G) entries exist on the router.
Page 96: Igmp Configuration (Available Only On The A5500 Ei)
IGMP configuration (available only on the A5500 EI) NOTE: router The term in this document refers to both routers and Layer 3 switches. The interfaces in this document refer to Layer 3 interfaces in generic sense and Ethernet interfaces operating in route mode. For more information about the operating mode of the Ethernet interface, Layer 2—LAN Switching Configuration Guide see the IGMP overview...
Page 97 Figure 29 IGMP queries and reports IP network Router A Router B Ethernet Host A Host B Host C (G2) (G1) (G1) Query Report Assume that Host B and Host C are interested in multicast data addressed to multicast group G1, and Host A is interested in multicast data addressed to G2, as shown in Figure 29.
Page 98: Enhancements In Igmpv2
receive any report addressed to that multicast group. In this case, the router will delete the multicast forwarding entries for that multicast group after a period of time. Enhancements in IGMPv2 Compared with IGMPv1, IGMPv2 has introduced a querier election mechanism and a leave-group mechanism.
Page 99 Enhancements in control capability of hosts IGMPv3 introduced two source filtering modes—Include and Exclude. These modes allow a host to join a designated multicast group and to choose whether to receive or reject multicast data from a designated multicast source. When a host joins a multicast group, one the following occurs: If it needs to receive multicast data from specific sources like S1, S2, …, it sends a report with the •...
Page 100: Igmp Ssm Mapping
Group records fall into the following categories: IS_IN—The source filtering mode is Include. The report sender requests the multicast data from only • the sources defined in the specified multicast source list. IS_EX—The source filtering mode is Exclude. The report sender requests the multicast data from any •...
Page 101: Igmp Proxying
As shown in Figure 31, on an SSM network, Host A, Host B, and Host C are running IGMPv1, IGMPv2, and IGMPv3 respectively. To provide SSM service for all the hosts if it is infeasible to run IGMPv3 on Host A and Host B, you must configure the IGMP SSM mapping feature on Router A. With the IGMP SSM mapping feature configured, when Router A receives an IGMPv1 or IGMPv2 report, it checks the multicast group address G carried in the message and does the following: If G is not in the SSM group range, Router A cannot provide the SSM service but can provide the...
Page 102: Multi-Instance Igmp
Upstream interface—Also called the “proxy interface.” A proxy interface is an interface on which • IGMP 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 IGMP. It is also called the “host interface.” Downstream interface—An interface that is running IGMP and is not in the direction toward the •...
Page 103: Configuring Basic Functions Of Igmp
Task Remarks Configuring IGMP fast-leave processing Optional Enabling SSM mapping Optional Configuring IGMP SSM mapping Configuring SSM mappings Optional Enabling IGMP proxying Optional Configuring IGMP proxying Configuring multicast forwarding on a downstream Optional interface NOTE: In IGMP view, the configuration is effective on all interfaces. In interface view, the configuration is effective on only the current interface.
Page 104: Configuring Igmp Versions
To do... Use the command... Remarks Required Enable IGMP igmp enable Disabled by default Enabling IGMP in a VPN instance Follow these steps to enable IGMP in a VPN instance: To do... Use the command... Remarks Enter system view system-view —...
Page 105: Configuring Static Joining
Configuring an IGMP version on an interface Follow these steps to configure an IGMP version on an interface: To do... Use the command... Remarks Enter system view system-view — interface interface-type interface- Enter interface view — number Optional Configure an IGMP version on the igmp version version-number interface IGMPv2 by default...
Page 106: Configuring The Maximum Number Of Multicast Groups That An Interface Can Join
To do... Use the command... Remarks Enter system view system-view — interface interface-type interface- Enter interface view — number Required By default, no multicast group igmp group-policy acl-number [ Configure a multicast group filter filter is configured on an interface version-number ] and hosts on an interface can join any valid multicast group.
Page 107: Configuring Igmp Message Options
Determine the IGMP general query interval • Determine the IGMP querier’s robustness variable • Determine the maximum response time for IGMP general queries • Determine the IGMP last-member query interval • Determine the other querier present interval • Configuring IGMP message options IGMP queries include group-specific queries and group-and-source-specific queries, and multicast groups change dynamically, so a device cannot maintain the information for all multicast sources and groups.
Page 108: Configuring Igmp Query And Response Parameters
To do... Use the command... Remarks Optional Configure the interface to discard any IGMP message that does not igmp require-router-alert By default, the device does not carry the Router-Alert option check the Router-Alert option. Optional Enable insertion of the Router-Alert igmp send-router-alert By default, IGMP messages carry option into IGMP messages...
Page 109 To do... Use the command... Remarks Enter system view system-view — Enter public network IGMP view igmp [ vpn-instance vpn-instance- — or VPN instance IGMP view name ] Optional Configure the IGMP querier’s robust-count robust-value robustness variable 2 by default Optional Configure the startup query By default, the startup query...
Page 110: Configuring Igmp Fast-Leave Processing
To do... Use the command... Remarks Optional By default, the startup query count Configure the startup query count igmp startup-query-count value is set to the IGMP querier’s robustness variable. Optional Configure the IGMP general igmp timer query interval query interval 60 seconds by default Optional Configure the maximum response...
Page 111: Enabling Ssm Mapping
Enabling SSM mapping Follow these steps to enable the IGMP SSM mapping feature: To do… Use the command… Remarks Enter system view system-view — interface interface-type interface- Enter interface view — number Required Enable the IGMP SSM igmp ssm-mapping enable mapping feature Disabled by default NOTE:...
Page 112: Enabling Igmp Proxying
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 device serve as an IGMP proxy. Follow these steps to enable IGMP proxying: To do… Use the command…...
Page 113: Displaying And Maintaining Igmp
CAUTION: On a multi-access network with more than one IGMP proxy device, do not enable multicast forwarding on any other non-querier downstream interface after one of the downstream interfaces of these IGMP proxy devices has been elected as the querier. Otherwise, duplicate multicast flows might be received on the multi-access network.
Page 114: Igmp Configuration Examples
To do... Use the command... Remove all the dynamic Layer 2 port reset igmp group port-info { all | group-address Available in user entries of a specified IGMP group or } [ vlan vlan-id ] view all IGMP groups reset igmp [ all-instance | vpn-instance vpn- instance-name ] ssm-mapping group { all | interface interface-type interface-number { all | Available in user...
Page 115 Figure 33 Network diagram for basic IGMP functions configuration Configuration procedure Configure IP addresses and unicast routing Configure the IP address and subnet mask of each interface according to Figure 33. The detailed configuration steps are omitted here. Configure the OSPF protocol for interoperation on the PIM network. Ensure the network-layer interoperation on the PIM network and dynamic update of routing information among the switches through a unicast routing protocol.
Page 116: Ssm Mapping Configuration Example
[SwitchB-Vlan-interface200] quit [SwitchB] interface vlan-interface 201 [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...
Page 117 Figure 34 Network diagram for IGMP SSM mapping configuration 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...
Page 118 [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 119: Igmp Proxying Configuration Example
133.133.3.1 Use the display igmp ssm-mapping group command to view the multicast group information that was created based on the configured IGMP SSM mappings. # 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).
Page 120 Figure 35 Network diagram for IGMP Proxying configuration Configuration procedure Configure IP addresses Configure the IP address and subnet mask of each interface according to Figure 35. The detailed configuration steps are omitted here. 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 121: Troubleshooting Igmp
Vlan-interface100(192.168.1.2): IGMP proxy is enabled Current IGMP version is 2 Multicast routing on this interface: enabled Require-router-alert: disabled Version1-querier-present-timer-expiry: 00:00:20 Use the display igmp group command to view the IGMP group information. For example, # Display the IGMP group information on Switch A. [SwitchA] display igmp group Total 1 IGMP Group(s).
Page 122: Inconsistent Memberships On Routers On The Same Subnet
Verify the IGMP version on the interface. Use the display igmp interface command to check whether the IGMP version on the interface is lower than that on the host. Check that no ACL rule has been configured to restrict the host from joining the multicast group G. Use the display current-configuration interface command to check whether the igmp group-policy command has been executed.
Page 123: Pim Configuration (Available Only On The A5500 Ei)
PIM configuration (available only on the A5500 EI) NOTE: router The term in this document refers to both routers and Layer 3 switches. • PIM domain To facilitate description, the term in this document refers to a network that comprises •...
Page 124 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. Generally speaking, the multicast forwarding path is a source tree. That is, it is a forwarding tree with the multicast source as its “root”...
Page 125 Figure 36 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 126: Pim-Sm Overview
Figure 37 Assert mechanism As shown in Figure 37, 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 local interface, receive a duplicate packet forwarded by the other.
Page 127 When a multicast source sends multicast streams to a multicast group, the source-side designated • router (DR) first registers the multicast source with the RP by sending register messages to the RP by unicast until it receives a register-stop message from the RP. The arrival of a register message at the RP triggers the establishment of an SPT.
Page 128 Figure 38 DR election Receiver Source Receiver Hello message Register message Join message As shown in Figure 38, the following describes the DR election process: Routers on the multi-access network send hello messages to one another. The hello messages contain the router priority for DR election. The router with the highest DR priority will become the If a tie occurs in the router priority, or if any router in the network does not support carrying the DR- election priority in hello messages, the router with the highest IP address will win the DR election.
Page 129 messages (BSMs) that it periodically originates and floods the bootstrap messages to the entire PIM-SM domain. Figure 39 BSR and C-RPs Based on the information in the RP-sets, all routers in the network can calculate the location of the corresponding RPs based on the following rules: The C-RP with the highest priority wins.
Page 130 RPT building Figure 40 RPT building in a PIM-SM domain As shown in Figure 40, the following describes the process of building an RPT: When a receiver joins multicast group G, it uses an IGMP message to inform the directly connected Upon getting the receiver information, the DR sends a join message, which is forwarded hop by hop to the RP that corresponds to the multicast group.
Page 131 Figure 41 Multicast source registration Host A Source Receiver Host B Server Receiver Join message Register message Host C Multicast packets As shown in Figure 41, the following describes the process that how a multicast source registers with the The multicast source S sends the first multicast packet to multicast group G. Upon receiving the multicast packet, the DR that directly connects the multicast source encapsulates the packet in a PIM register message.
Page 132: Bidir-Pim Overview
An increase in multicast adds a great burden to the RP, increasing the risk of failure. • To solve these issues, PIM-SM allows an RP or the DR at the receiver side to initiate an SPT switchover process when the traffic rate exceeds the threshold. The RP initiates an SPT switchover process The RP can periodically check the passing-by IPv4 multicast packets.
Page 133 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.” In PIM-SM, an RP must be specified with a real IP address. In BIDIR-PIM, however, an RP can be specified with a virtual IP address, which is called the rendezvous point address (RPA).
Page 134 Router B and Router C multicast DF election messages to all PIM routers—224.0.0.13. The election messages carry the RP’s address, and the priority and metric of the unicast route, MBGP route, or multicast static route to the RP. The router with a route of the highest priority becomes the DF. If a tie occurs in the priority, the router with the route with the lowest metric wins the DF election.
Page 135: Administrative Scoping Overview
Figure 44 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 44, the process of 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 136 Admin-scope zones are divided specific to multicast groups. Zone border routers (ZBRs) form the boundary of the admin-scope zone. Each admin-scope zone maintains one BSR, which serves multicast groups within a specific range. Multicast protocol packets, such as assert messages and bootstrap messages, for a specific group range cannot cross the admin-scope zone boundary.
Page 137: Pim-Ssm Overview
Figure 46 Relationship between admin-scope zones and the global-scope zone in group address ranges Figure 46, the group address ranges of admin-scope 1 and 2 have no intersection, whereas the group address range of admin-scope 3 is a subset of the address range of admin-scope 1. The group address range of the global-scope zone—G-G1-G2—covers all the group addresses other than those of all the admin-scope zones.
Page 138: Relationships Among Pim Protocols
Figure 47 SPT building in PIM-SSM As shown in Figure 47, Host B and Host C are multicast information receivers. They send IGMPv3 report messages to the respective DRs to express their interest in the information about the specific multicast source S.
Page 139: Multi-Instance Pim
Figure 48 Selection of PIM-SM, BIDIR-PIM, and PIM-SSM A receiver joins multicast group G. G is in the The receiver specifies a SSM group range? multicast source? BIDIR-PIM is enabled? IGMP SSM mapping is configured for G? G has corresponding Enable PIM-SM for G Enable PIM-SSM for G BIDIR-PIM RP?
Page 140: Configuring Pim-Dm
Configuring PIM-DM PIM-DM configuration task list Complete these tasks to configure PIM-DM: Task Remarks Enabling PIM-DM Required Enabling state-refresh capability Optional Configuring state-refresh parameters Optional Configuring PIM-DM graft retry period Optional Configuring PIM common features Optional Configuration prerequisites Before you configure PIM-DM, complete the following tasks: Configure any unicast routing protocol so that all devices in the domain are interoperable at the •...
Page 141: Enabling State-Refresh Capability
To do... Use the command... Description Enter system view system-view — Create a VPN instance and enter ip vpn-instance vpn-instance-name — VPN instance view Required Configure an RD for the VPN route-distinguisher route- instance distinguisher Not configured by default. Required Enable IP multicast routing multicast routing-enable Disabled by default.
Page 142: Configuring State-Refresh Parameters
Configuring state-refresh parameters The router directly connected with the multicast source periodically sends state-refresh messages. You can configure an 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 143: Configuring Pim-Sm
NOTE: For more information about the configuration of other timers in PIM-DM, see “Configuring PIM common timers.” Configuring PIM-SM PIM-SM configuration task list Complete these tasks to configure PIM-SM: Task Remarks Enabling PIM-SM Required Configuring a static RP Optional Configuring a C-RP Optional Configuring an RP Enabling auto-RP...
Page 144: Enabling Pim-Sm
Determine the C-RP timeout. • Determine the C-BSR priority. • Determine the hash mask length. • Determine the ACL rule defining a legal BSR address range. • Determine the BS period. • Determine the BS timeout. • Determine the ACL for register message filtering. •...
Page 145: Configuring An Rp
To do... Use the command... Remarks Required Associate the current interface ip binding vpn-instance vpn- No VPN instance is associated with the VPN instance instance-name with an interface by default. Required Enable PIM-SM pim sm Disabled by default CAUTION: All the interfaces in the same VPN instance on the same router must work in the same PIM mode. NOTE: For more information about the ip vpn-instance, route-distinguisher, and ip binding vpn-instance •...
Page 146 Configuring a C-RP In a PIM-SM domain, you can configure routers that will become the RP as C-RPs. The BSR collects the C- RP information by receiving the C-RP-Adv messages from C-RPs or auto-RP announcements from other routers and organizes the information into an RP-set, which is flooded throughout the entire network. Then, the other routers in the network calculate the mappings between specific group ranges and the corresponding RPs based on the RP-set.
Page 147: Configuring A Bsr
and encapsulates its own IP address together with the RP-set information in its bootstrap messages. The BSR then floods the bootstrap messages to all PIM routers in the network. Each C-RP encapsulates a timeout value in its C-RP-Adv messages. Upon receiving a C_RP-Adv message, the BSR obtains this timeout value and starts a C-RP timeout timer.
Page 148 Some maliciously configured hosts can forge bootstrap messages to fool routers and change RP mappings. Such attacks often occur on border routers. Because a BSR is inside the network whereas hosts are outside the network, a BSR can be protected against attacks from external hosts after you enable the border routers to perform neighbor checks and RPF checks on bootstrap messages and to discard unwanted messages.
Page 149 To do… Use the command… Remarks Required Configure a PIM domain border pim bsr-boundary By default, no PIM domain border is configured. Configuring global C-BSR parameters In each PIM-SM domain, a unique BSR is elected from C-BSRs. The C-RPs in the PIM-SM domain send advertisement messages to the BSR.
Page 150 To do… Use the command… Remarks Enter public network PIM view or pim [ vpn-instance vpn-instance-name — VPN instance PIM view Optional Configure the BS period c-bsr interval interval For the default value, see the note under this table. Optional Configure the BS timeout timer c-bsr holdtime interval For the default value, see the...
Page 151: Configuring Administrative Scoping
To do… Use the command… Remarks Enter system view system-view — Enter public network PIM view pim [ vpn-instance vpn-instance- — or VPN instance PIM view name ] Required Disable the BSM semantic By default, the BSM semantic undo bsm-fragment enable fragmentation function fragmentation function is enabled.
Page 152 To do… Use the command… Remarks Required Configure a multicast forwarding multicast boundary group-address { By default, no multicast boundary mask | mask-length } forwarding boundary is configured. NOTE: group-address mask mask-length } parameter of the multicast boundary command can be used to specify the multicast groups an admin-scope zone serves, in the range of 239.0.0.0/8.
Page 153: Configuring 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, HP does not recommend this method of checksum calculation.
Page 154: Disabling Spt Switchover
To do... Use the command... Remarks Enter public network PIM view or pim [ vpn-instance vpn-instance- — VPN instance PIM view name ] Optional Configure a filtering rule for register-policy acl-number No register filtering rule by register messages default. Optional Configure the device to calculate By default, the checksum is the checksum based on the entire...
Page 155: Configuring Bidir-Pim
Configuring BIDIR-PIM BIDIR-PIM configuration task list Complete these tasks to configure BIDIR-PIM: Task Remarks Enabling PIM-SM Required Enabling BIDIR-PIM Required Configuring a static RP Required Configuring a C-RP Use any approach Configuring an RP Enabling auto-RP Configuring C-RP timers globally Optional Configuring a C-BSR Required...
Page 156: Enabling Pim-Sm
Determine the BS period. • Determine the BS timeout. • Enabling PIM-SM Because BIDIR-PIM is implemented on the basis of PIM-SM, you must enable PIM-SM before enabling BIDIR-PIM. To deploy a BIDIR-PIM domain, enable PIM-SM on all non-border interfaces of the domain. Enabling PIM-SM globally for the public network Follow these steps to enable PIM-SM for the public network: To do...
Page 157: Enabling Bidir-Pim
NOTE: For more information about the ip vpn-instance, route-distinguisher, and ip binding vpn-instance • MPLS Command Reference commands, see the IP Multicast Command For more information about the multicast routing-enable command, see the • Reference Enabling BIDIR-PIM Perform this configuration on all routers in the BIDIR-PIM domain. Follow these steps to enable BIDIR-PIM: To do...
Page 158 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. HP recommends that you configure C-RPs on backbone routers.
Page 159: Configuring A Bsr
To do... Use the command... Remarks Required 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 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 160 address to replace its own BSR address and no longer assumes itself to be the BSR, and the winner retains its own BSR address and continues assuming itself to be the BSR. Configuring a legal range of BSR addresses enables filtering of bootstrap messages based on the address range, to prevent a maliciously configured host from masquerading as a BSR.
Page 161 Configuring a 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 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 BIDIR-PIM domains.
Page 162 Configuring C-BSR timers The BSR election winner multicasts its own IP address and RP-Set information through bootstrap messages within the entire zone it serves. The BSR floods bootstrap messages throughout the network at the interval of BS (BSR state) period. Any C-BSR that receives a bootstrap message retains the RP-set for the length of BS timeout, during which no BSR election takes place.
Page 163: Configuring Administrative Scoping
If the RP-set information of one group range is carried in multiple BSMFs, a non-BSR router updates • corresponding RP-set information upon receiving all these BSMFs. Because the RP-set information contained in each segment is different, loss of some IP fragments will not result in dropping of the entire message.
Page 164 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 serves a specific multicast group range. Multicast protocol packets (such as assert messages and bootstrap messages) that belong to this range cannot cross the admin-scope zone boundary. Perform the following configuration on routers that can become a ZBR.
Page 165: Configuring Pim-Ssm
Follow these steps to configure a C-BSR for the global-scope zone: To do… Use the command… Remarks Enter system view system-view — Enter public network PIM view or pim [ vpn-instance vpn-instance- — VPN instance PIM view name ] Required Configure a C-BSR for the c-bsr global [ hash-length hash- No C-BSRs are configured for...
Page 166: Enabling Pim-Sm
The implementation of the SSM model is based on some subsets of PIM-SM. Therefore, a router is PIM- SSM capable after you enable PIM-SM on it. When you deploy a PIM-SM domain, HP recommends that you enable PIM-SM on non-border interfaces of the routers.
Page 167: Configuring The Ssm Group Range
NOTE: For more information about the ip vpn-instance, route-distinguisher and ip binding vpn-instance • MPLS Command Reference commands, see the IP Multicast Command For more information about the multicast routing-enable command, see the • Reference Configuring the SSM group range Whether the information from a multicast source is delivered to the receivers based on the PIM-SSM model or the PIM-SM model depends on whether the group address in the (S, G) channel subscribed by the receivers falls into the SSM group range.
Page 168: Configuration Prerequisites
Task Remarks Configuring PIM hello options Optional Configuring the prune delay Optional Configuring PIM common timers Optional Configuring join/prune message sizes Optional Configuration prerequisites Before you configuring PIM common features, complete the following tasks: Configure any unicast routing protocol so that all devices in the domain are interoperable at the •...
Page 169: Configuring A Hello Message Filter
To do... Use the command... Remarks Required Configure a multicast group filter source-policy acl-number No multicast data filter by default. NOTE: Generally, a smaller distance from the filter to the multicast source results in a more remarkable • filtering effect. This filter works not only on independent multicast data but also on multicast data encapsulated in •...
Page 170 the largest value will take effect. If you want to enable neighbor tracking, be sure to enable the neighbor tracking feature on all PIM routers on a multi-access subnet. The LAN-delay setting will cause the upstream routers to delay processing received prune messages. The override-interval sets the length of time that a downstream router can wait before sending a prune override message.
Page 171: Configuring The Prune Delay
To do... Use the command... Remarks Optional Configure the priority for DR pim hello-option dr-priority election priority 1 by default. Optional Configure PIM neighbor timeout pim hello-option holdtime interval time 105 seconds by default. Optional Configure the prune message pim hello-option lan-delay interval delay time (LAN-delay) 500 milliseconds by default.
Page 172 When a router fails to receive subsequent multicast data from multicast source S, the router does not immediately delete the corresponding (S, G) entry. Instead, it maintains the (S, G) entry for a period of time—namely, the multicast source lifetime—before deleting the (S, G) entry. Configuring PIM common timers globally Follow these steps to configure PIM common timers globally: To do...
Page 173: Configuring Join/Prune Message Sizes
Configuring join/prune message sizes A larger join/prune message size will result in loss of a larger amount of information if a message is lost. With a reduced join/message size, the loss of a single message has a relatively minor impact. Controlling the maximum number of (S, G) entries in a join/prune message can reduce the number of (S, G) entries sent per unit of time.
Page 174: Pim Configuration Examples
To do... Use the command... Remarks display pim [ all-instance | vpn-instance vpn-instance- name ] join-prune mode { sm [ flags flag-value ] | ssm } [ Display the information of Available in interface interface-type interface-number | neighbor join/prune messages to send any view neighbor-address ] * [ verbose ] [ | { begin | exclude | include } regular-expression ]...
Page 175 Figure 49 Network diagram for PIM-DM configuration 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...
Page 176 The configuration on Switch B and Switch C is similar to that on Switch A. # 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 [SwitchD-Vlan-interface103] pim dm...
Page 177 VPN-Instance: public net 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...
Page 178: Pim-Sm Non-Scoped Zone Configuration Example
PIM-SM non-scoped zone configuration example Network requirements As shown in Figure 50, receivers receive VOD information through multicast. The receiver groups • of different organizations form stub networks, and one or more receiver hosts exist in each stub network. The entire PIM-SM domain contains only one BSR. Host A and Host C are multicast receivers in two stub networks.
Page 179 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 IP addresses and unicast routing. Configure the IP address and subnet mask for each interface according to Figure 50 (details not shown). Configure OSPF on the switches in the PIM-SM domain to ensure network-layer reachability among them (details not shown).
Page 180 [SwitchE-pim] c-bsr vlan-interface 102 32 20 [SwitchE-pim] c-rp vlan-interface 102 group-policy 2005 [SwitchE-pim] quit Verify the configuration. Carry out the display pim interface command to view the PIM configuration and running status on each interface. For example: # View the PIM configuration information on Switch A. [SwitchA] display pim interface VPN-Instance: public net Interface...
Page 181 # View the BSR information and the locally configured C-RP information in effect on Switch E. [SwitchE] display pim bsr-info VPN-Instance: public net Elected BSR Address: 192.168.9.2 Priority: 20 Hash mask length: 32 State: Elected Scope: Not scoped Uptime: 00:01:18 Next BSR message scheduled at: 00:01:52 Candidate BSR Address: 192.168.9.2 Priority: 20...
Page 182 [SwitchA] display pim routing-table VPN-Instance: public net Total 1 (*, G) entry; 1 (S, G) entry (*, 225.1.1.0) RP: 192.168.9.2 Protocol: pim-sm, Flag: WC UpTime: 00:13:46 Upstream interface: Vlan-interface102 Upstream neighbor: 192.168.9.2 RPF prime neighbor: 192.168.9.2 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: igmp, UpTime: 00:13:46, Expires: 00:03:06 (10.110.5.100, 225.1.1.0)
Page 183: Pim-Sm Admin-Scope Zone Configuration Example
Total 1 (*, G) entry; 0 (S, G) entry (*, 225.1.1.0) RP: 192.168.9.2 (local) Protocol: pim-sm, Flag: WC UpTime: 00:13:16 Upstream interface: Register Upstream neighbor: 192.168.4.2 RPF prime neighbor: 192.168.4.2 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface102 Protocol: pim-sm, UpTime: 00:13:16, Expires: 00:03:22 PIM-SM admin-scope zone configuration example Network requirements...
Page 184 Figure 51 Network diagram for PIM-SM admin-scope zone configuration Admin-scope 1 Receiver Vlan-int500 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 Switch B Vlan-int107 Switch A Switch C Switch I Switch H Vlan-int107 Vlan-int110...
Page 185 Enable IP multicast routing and administrative scoping, and enable PIM-SM and IGMP. # Enable IP multicast routing and administrative scoping on Switch A, enable PIM-SM on each interface, and enable IGMP on the host-side interface VLAN-interface 100. <SwitchA> system-view [SwitchA] multicast routing-enable [SwitchA] pim [SwitchA-pim] c-bsr admin-scope [SwitchA-pim] quit...
Page 186 # 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 187 [SwitchB] display pim bsr-info 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...
Page 188 Scope: 239.0.0.0/8 Candidate RP: 10.110.4.2(Vlan-interface104) Priority: 192 HoldTime: 150 Advertisement Interval: 60 Next advertisement scheduled at: 00:00:10 # View the 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...
Page 189: Bidir-Pim Configuration Example
[SwitchD] display pim rp-info VPN-Instance: public net 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 # View the RP information on Switch F. [SwitchF] display pim rp-info VPN-Instance: public net PIM-SM BSR RP information:...
Page 190 Figure 52 Network diagram for BIDIR-PIM configuration 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...
Page 191 # On Switch B, enable IP multicast routing, enable PIM-SM on each interface, enable IGMP on 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 192 [SwitchD-pim] quit Configure C-BSR and C-RP. # 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 Verify the configuration.
Page 193 To view the DF information of the multicast forwarding table on a switch, use the display multicast forwarding-table df-info command. For more information about this command, see the IP Multicast Command Reference. # View the DF information of the multicast forwarding table on Switch A. [SwitchA] display multicast forwarding-table df-info Multicast DF information of VPN-Instance: public net Total 1 RP...
Page 194: Pim-Ssm Configuration Example
Total 1 RP Total 1 RP matched 00001. RP Address: 1.1.1.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 PIM-SSM configuration example Network requirements As shown in Figure 53, receivers receive VOD information through multicast. The receiver groups •...
Page 195 Figure 53 Network diagram for PIM-SSM configuration Device Interface IP address Device Interface IP address Switch A Vlan-int100 10.110.1.1/24 Switch D Vlan-int300 10.110.5.1/24 Vlan-int101 192.168.1.1/24 Vlan-int101 192.168.1.2/24 Vlan-int102 192.168.9.1/24 Vlan-int105 192.168.4.2/24 Switch B Vlan-int200 10.110.2.1/24 Switch E Vlan-int104 192.168.3.2/24 Vlan-int103 192.168.2.1/24 Vlan-int103 192.168.2.2/24...
Page 196 [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim sm [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] pim sm [SwitchA-Vlan-interface102] quit The configuration on Switch B and Switch C is similar to that on Switch A. The configuration on Switch D and Switch E is also similar to that on Switch A except that it is not necessary to enable IGMP on the corresponding interfaces on these two switches.
Page 197: Troubleshooting Pim Configuration
Total number of downstreams: 1 1: Vlan-interface100 Protocol: igmp, UpTime: 00:13:25, Expires: 00:03:25 The information on Switch B and Switch C is similar to that on Switch A. # View the PIM routing table information on Switch D. [SwitchD] display pim routing-table VPN-Instance: public net Total 0 (*, G) entry;...
Page 198: Multicast Data Abnormally Terminated On An Intermediate Router
Because a hello message does not carry the PIM mode information, a router running PIM is unable • to know what PIM mode its PIM neighbor is running. If different PIM modes are enabled on the RPF interface and on the corresponding interface of the RPF neighbor router, the establishment of a multicast distribution tree will fail, causing abnormal multicast forwarding.
Page 199: Rps Unable To Join Spt In Pim-Sm
RPs unable to join SPT in PIM-SM Symptom An RPT cannot be established correctly, or the RPs cannot join the SPT to the multicast source. Analysis As the core of a PIM-SM domain, the RPs serve specific multicast groups. Multiple RPs can coexist •...
Page 200 Verify the PIM neighboring relationships. Use the display pim neighbor command to determine whether the normal PIM neighboring relationships have been established among the routers.
Page 201: Msdp Configuration (Available Only On The A5500 Ei)
MSDP configuration (available only on the A5500 EI) NOTE: router The term in this document refers to both routers and Layer 3 switches. For more information about the concepts of DR, BSR, C-BSR, RP, C-RP, SPT and RPT in this document, see the chapter “PIM configuration.”...
Page 202 Figure 54 Where MSDP peers are in the network As shown in Figure 54, an MSDP peer can be created on any PIM-SM router. MSDP peers created on PIM-SM routers that assume different roles function differently. MSDP peers on RPs include the following types: Source-side MSDP peer—The MSDP peer nearest to the multicast source—Source, typically the •...
Page 203 HP recommends you to establish MSDP peering relationships between RP 1 and RP 3 and between RP 3 and RP 2, respectively. Figure 55 MSDP peering relationships Receiver DR 2 MSDP peers Multicast packets SA message RP 2 Join message...
Page 204 If no receivers for the group exist in the domain, RP 2 neither creates an (S, G) entry nor joins the SPT rooted at the source. NOTE: An MSDP mesh group refers to a group of MSDP peers that have MSDP peering relationships among one another and share the same group name.
Page 205 Because the SA message is from an MSDP peer—RP 2—in the same AS, and the MSDP peer is the next hop on the optimal path to the source-side RP, RP 3 accepts the message and forwards it to other peers—RP 4 and RP 5. When RP 4 and RP 5 receive the SA message from RP 3: Because the SA message is from an MSDP peer—RP 3—in the same mesh group, RP 4 and RP 5 both accept the SA message, but they do not forward the message to other members in the mesh...
Page 206: Multi-Instance Msdp
Figure 57 Typical network diagram of Anycast RP RP 1 RP 2 Router A Router B Source Receiver PIM-SM MSDP peers SA message The work process of Anycast RP is as follows: The multicast source registers with the nearest RP. In this example, Source registers with RP 1, with its multicast data encapsulated in the register message.
Page 207: Protocols And Standards
A multicast router that runs multiple MSDP instances maintains an independent set of MSDP mechanism for each instance that it supports, including SA cache, peering connection, timers, sending cache, and cache for exchanging information with PIM, but these instances are isolated from one another. Interoperability between MSDP and PIM-SM is available only within the same instance.
Page 208: Enabling Msdp
Enabling MSDP Enabling MSDP globally for the public network Follow these steps to enable MSDP globally for the public network: To do... Use the command... Remarks Enter system view system-view — Required Enable IP multicast routing multicast routing-enable Disabled by default Required Enable MSDP and enter public msdp...
Page 209: Configuring A Static Rpf Peer
NOTE: If an interface of the router is shared by an MSDP peer and a BGP/MBGP peer at the same time, HP recommends you to use the IP address of the BGP/MBGP peer as the IP address of the for the MSDP peer.
Page 210: Configuring An Msdp Mesh Group
To do... Use the command... Remarks Enter system view system-view — Enter public network MSDP view msdp [ vpn-instance vpn-instance- — or VPN instance MSDP view name ] Required Configure description for an peer peer-address description text No description for MSDP peers MSDP peer by default Configuring an MSDP mesh group...
Page 211: Configuring Sa Messages Related Parameters
When you reactivate a previously deactivated MSDP peer connection • When a previously failed MSDP peer attempts to resume operation • You can adjust the interval between MSDP peer connection retries. Follow these steps to configure MSDP peer connection control: To do...
Page 212: Configuring Sa Request Messages
The MSDP peers deliver SA messages to one another. After receiving an SA message, a switch performs RPF check on the message. If the switch 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 devices in the same PIM-SM domain and configure these devices as MSDP peers to one another.
Page 213: Configuring The Sa Cache Mechanism
By configuring a filtering rule for receiving or forwarding SA messages, you can enable the switch to filter the (S, G) forwarding entries to be advertised when receiving or forwarding an SA message, so that the propagation of multicast source information is controlled at SA message reception or forwarding.
Page 214: Displaying And Maintaining Msdp
To do... Use the command... Remarks Enter system view system-view — Enter public network MSDP view or VPN msdp [ vpn-instance vpn-instance- — instance MSDP view name ] Optional Enable the SA cache mechanism cache-sa-enable Enabled by default Configure the maximum number of (S, G) Optional peer peer-address sa-cache- entries learned from the specified MSDP...
Page 215 Each PIM-SM domain has zero or one multicast source and receiver. OSPF runs within each • domain to provide unicast routes. Loopback 0 of Switch B, Switch C, and Switch E must be configured as the C-BSR and C-RP of the •...
Page 216 # Enable IP multicast routing on Switch A, enable PIM-SM on each interface, and enable IGMP on the host-side interface VLAN-interface 200. <SwitchA> system-view [SwitchA] multicast routing-enable [SwitchA] interface vlan-interface 103 [SwitchA-Vlan-interface103] pim sm [SwitchA-Vlan-interface103] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] pim sm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 200...
Page 217 [SwitchE-bgp] peer 192.168.3.1 as-number 200 [SwitchE-bgp] import-route ospf 1 [SwitchE-bgp] quit # Redistribute BGP routes into OSPF on Switch B. [SwitchB] ospf 1 [SwitchB-ospf-1] import-route bgp [SwitchB-ospf-1] quit The configuration on Switch C and Switch E is similar to the configuration on Switch B. Configure MSDP peers # Configure an MSDP peer on Switch B.
Page 218 192.168.3.2 6 00:12:05 Established # View the information about BGP peering relationships on Switch E. [SwitchE] display bgp peer BGP local router ID : 3.3.3.3 Local AS number : 200 Total number of peers : 1 Peers in established state : 1 Peer MsgRcvd MsgSent...
Page 219 Peer's Address State Up/Down time SA Count Reset Count 192.168.1.2 00:12:27 # View the brief information about MSDP peering relationships on Switch C. [SwitchC] display msdp brief MSDP Peer Brief Information of VPN-Instance: public net Configured Listen Connect Shutdown Down Peer's Address State Up/Down time...
Page 220: Inter-As Multicast Configuration Leveraging Static Rpf Peers
Incoming/outgoing SA responses: 0/0 Incoming/outgoing data packets: 0/0 Inter-AS multicast configuration leveraging static RPF peers Network requirements As shown in Figure 59, AS 100 and AS 200 run OSPF within each AS, and run BGP between • each other. PIM-SM 1 belongs to AS 100, and PIM-SM 2 and PIM-SM 3 belong to AS 200. •...
Page 221 Loop0 1.1.1.1/32 Vlan-int400 10.110.7.1/24 Switch C Vlan-int101 192.168.1.2/24 Source 1 — 10.110.2.100/24 Vlan-int104 10.110.4.1/24 Source 2 — 10.110.5.100/24 Loop0 2.2.2.2/32 Configuration procedure Configure IP addresses and unicast routing Configure the IP address and subnet mask for each interface according to Figure 59 (details not shown).
Page 222 # Configure Switch C and Switch E as a static RPF peers of Switch B. [SwitchB] ip ip-prefix list-df permit 192.168.0.0 16 greater-equal 16 less-equal 32 [SwitchB] msdp [SwitchB-msdp] peer 192.168.3.2 connect-interface vlan-interface 102 [SwitchB-msdp] peer 192.168.1.2 connect-interface vlan-interface 101 [SwitchB-msdp] static-rpf-peer 192.168.3.2 rp-policy list-df [SwitchB-msdp] static-rpf-peer 192.168.1.2 rp-policy list-df [SwitchB-msdp] quit...
Page 223: Anycast Rp Configuration
# View the brief MSDP peer information on Switch E. [SwitchE] 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 192.168.3.1 00:16:40 Anycast RP configuration Network requirements As shown in Figure...
Page 224 Vlan-int101 192.168.1.1/24 Loop10 4.4.4.4/32 Loop0 1.1.1.1/32 Loop20 10.1.1.1/32 Loop10 3.3.3.3/32 Switch E Vlan-int400 10.110.6.1/24 Loop20 10.1.1.1/32 Vlan-int104 10.110.4.2/24 Configuration procedure Configure IP addresses and unicast routing Configure the IP address and subnet mask for each interface according to Figure 60 (details not shown).
Page 225 # Configure an MSDP peer on Loopback 0 of Switch B. [SwitchB] msdp [SwitchB-msdp] originating-rp loopback 0 [SwitchB-msdp] peer 2.2.2.2 connect-interface loopback 0 [SwitchB-msdp] quit # Configure an MSDP peer on Loopback 0 of Switch D. [SwitchD] msdp [SwitchD-msdp] originating-rp loopback 0 [SwitchD-msdp] peer 1.1.1.1 connect-interface loopback 0 [SwitchD-msdp] quit Verify the configuration...
Page 226 Total number of downstreams: 1 1: Vlan-interface100 Protocol: igmp, UpTime: 00:15:04, Expires: - (10.110.5.100, 225.1.1.1) RP: 10.1.1.1 (local) Protocol: pim-sm, Flag: SPT 2MSDP ACT UpTime: 00:46:28 Upstream interface: Vlan-interface103 Upstream neighbor: 10.110.2.2 RPF prime neighbor: 10.110.2.2 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: pim-sm, UpTime: - , Expires:...
Page 227: Sa Message Filtering Configuration
Upstream interface: Vlan-interface104 Upstream neighbor: 10.110.4.2 RPF prime neighbor: 10.110.4.2 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface200 Protocol: pim-sm, UpTime: - , Expires: SA message filtering configuration Network requirements As shown in Figure 61, the network has three PIM-SM domains, and OSPF runs within and among •...
Page 228 Loop0 1.1.1.1/32 Switch D Vlan-int400 10.110.6.1/24 Switch B Vlan-int200 10.110.3.1/24 Vlan-int500 10.110.7.1/24 Vlan-int102 10.110.2.2/24 Vlan-int104 10.110.5.2/24 Vlan-int103 192.168.2.1/24 Loop0 3.3.3.3/32 Configuration Procedure Configure IP addresses and unicast routing Configure the IP address and subnet mask for each interface according to Figure 61 (details not shown).
Page 229 # Configure Loopback 0 on Switch A as a C-BSR and a C-RP. [SwitchA] pim [SwitchA-pim] c-bsr loopback 0 [SwitchA-pim] c-rp loopback 0 [SwitchA-pim] quit The configuration on Switch C and Switch D is similar to the configuration on Switch A (details not shown).
Page 230: Troubleshooting Msdp
MSDP Total Source-Active Cache - 8 entries MSDP matched 8 entries (Source, Group) Origin RP Uptime Expires (10.110.3.100, 225.1.1.0) 1.1.1.1 02:03:30 00:05:31 (10.110.3.100, 225.1.1.1) 1.1.1.1 02:03:30 00:05:31 (10.110.3.100, 225.1.1.2) 1.1.1.1 02:03:30 00:05:31 (10.110.3.100, 225.1.1.3) 1.1.1.1 02:03:30 00:05:31 (10.110.3.100, 226.1.1.0) 1.1.1.1 02:03:30 00:05:31 (10.110.3.100, 226.1.1.1) 1.1.1.1...
Page 231: No Sa Entries In The Switch's Sa Cache
No SA entries in the switch’s SA cache Symptom MSDP fails to send (S, G) entries through SA messages. Analysis The import-source command controls sending (S, G) entries through SA messages to MSDP peers. If • this command is executed without the acl-number argument, all the (S, G) entries will be filtered off. That is, no (S, G) entries of the local domain will be advertised.
Page 232: Mbgp Configuration (Available Only On The A5500 Ei)
MBGP configuration (available only on the A5500 EI) NOTE: router The term in this document refers to both routers and Layer 3 switches. This document covers configuration tasks related to multiprotocol BGP for IP multicast only. For more Layer 3—IP Routing Configuration Guide information about BGP, see the For more information about RPF, see the chapter “Multicast routing and forwarding configuration.”...
Page 233: Configuring Mbgp Basic Functions
Task Remarks reception Configuring MBGP route summarization Optional Advertising a default route to an IPv4 MBGP peer or peer Optional group Configuring outbound MBGP route filtering Optional Configuring inbound MBGP route filtering Optional Configuring MBGP route dampening Optional Configuring MBGP route preferences Configuring the default local preference Configuring MBGP Configuring the MED attribute...
Page 234: Controlling Route Advertisement And Reception
To do… Use the command… Remarks Specify a preferred value for Optional peer { group-name | ip-address } routes from an IPv4 MBGP peer preferred-value value The default preferred value is 0. or peer group Controlling route advertisement and reception Configuration prerequisites Before you configure this task, configure MBGP basic functions.
Page 235: Configuring Mbgp Route Summarization
To do… Use the command… Remarks Enter system view system-view — Enter BGP view bgp as-number — Enter MBGP address family view ipv4-family multicast — Required No route redistribution is import-route protocol [ { process- configured by default. Enable route redistribution from id | all-processes } [ allow-direct Currently, the allow-direct another routing protocol...
Page 236: Advertising A Default Route To An Ipv4 Mbgp Peer Or Peer Group
Advertising a default route to an IPv4 MBGP peer or peer group Follow these steps to advertise a default route to an MBGP peer or peer group: To do… Use the command… Remarks Enter system view system-view — Enter BGP view bgp as-number —...
Page 237: Configuring Inbound Mbgp Route Filtering
To do… Use the command… Remarks Reference an ACL to filter peer { group-name | ip-address } advertisements to an IPv4 MBGP filter-policy acl-number export peer/peer group Reference an AS path ACL to filter peer { group-name | ip-address } route advertisements to an IPv4 as-path-acl as-path-acl-number MBGP peer/peer group...
Page 238: Configuring Mbgp Route Dampening
To do… Use the command… Remarks Optional Specify the maximum number of peer { group-name | ip-address } routes that can be received from The number is unlimited by route-limit limit [ percentage ] an IPv4 MBGP peer/peer group default. CAUTION: Members of a peer group can have different route reception filtering policies from the peer group.
Page 239: Configuring The Default Local Preference
To do… Use the command… Remarks Optional preference { external-preference The default preferences of Configure preferences for external, internal-preference local- multicast MBGP eBGP, MBGP internal, local MBGP routes preference | route-policy route- iBGP, and local MBGP routes are policy-name } 255, 255, and 130, respectively.
Page 240: Configuring The Next Hop Attribute
Configuring the Next Hop attribute You can use the peer next-hop-local command to specify the local switch as the next hop of routes sent to an MBGP iBGP peer or peer group. If load balancing is configured, the switch specifies itself as the next hop of route advertisements to the multicast iBGP peer or peer group, regardless of whether the peer next-hop-local command is configured.
Page 241: Tuning And Optimizing Mbgp Networks
To do… Use the command… Remarks Optional Configure updates to a peer/peer group peer { group-name | ip-address } By default, BGP updates to not keep private AS numbers public-as-only carry private AS numbers. Tuning and optimizing MBGP networks This task involves resetting MBGP connections and configuring load balancing. Configuration prerequisites Before you configure this task, configure BGP basic functions.
Page 242: Enabling The Mbgp Orf Capability
To do… Use the command… Remarks Disable BGP route-refresh and Optional peer { group-name | ip-address } multi-protocol extensions for a capability-advertise conventional Enabled by default peer/peer group Enter IPv4 MBGP address family ipv4-family multicast — view Keep all original routes from a Required peer/peer group regardless of peer { group-name | ip-address }...
Page 243: Configuring The Maximum Number Of Mbgp Routes For Load Balancing
To do… Use the command… Remarks Optional By default, standard BGP ORF capability defined in RFC 5291 and RFC 5292 is supported. Enable the non-standard ORF peer { group-name | ipv6-address capability for a BGP peer/peer } capability-advertise orf non- If this feature is not enabled, you group standard...
Page 244: Configuring A Large Scale Mbgp Network
Configuring a large scale MBGP network Configuration prerequisites Before performing this task, make peering nodes accessible to each other at the network layer. Configuring IPv4 MBGP peer groups In a large-scale network, configuration and maintenance become difficult because of large numbers of MBGP peers.
Page 245: Configuring An Mbgp Route Reflector
To do… Use the command… Remarks Enter IPv4 MBGP address family view ipv4-family multicast — Advertise the community attribute to an peer { group-name | ip-address } MBGP advertise-community peer/peer Advertise the group Required community attribute Advertise the to an MBGP Not configured by default extended peer/peer group...
Page 246: Displaying And Maintaining Mbgp
NOTE: In general, the clients of a route reflector need not to be fully meshed. The route reflector forwards routing information between clients. If clients are fully meshed, disable route reflection between clients to reduce routing costs. In general, a cluster has only one route reflector, and the router ID of the route reflector identifies the cluster.
Page 247: Resetting Mbgp Connections
To do… Use the command… Remarks Display MBGP dampened routing display bgp multicast routing-table dampened [ | { Available in information begin | exclude | include } regular-expression ] any view display bgp multicast routing-table dampening Display MBGP dampening Available in parameter [ | { begin | exclude | include } regular- parameter information any view...
Page 248: Mbgp Configuration Example
MBGP configuration example Network requirements As shown in Figure PIM-SM 1 is in AS 100, and PIM-SM 2 is in AS 200. OSPF is the IGP in the two ASs, and MBGP • runs between the two ASs to exchange multicast route information. The multicast source belongs to PIM-SM 1, and the receiver belongs to PIM-SM 2.
Page 249 [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] pim sm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim sm [SwitchA-Vlan-interface101] quit The configuration on Switch B and Switch D is similar to the configuration on Switch A. # Enable IP multicast routing on Switch C, enable PIM-SM on each interface, and enable IGMP on the host-side interface VLAN-interface 200.
Page 250 [SwitchB-pim] c-rp loopback 0 [SwitchB-pim] quit Configure BGP, specify the MBGP peer and enable direct route redistribution. # On Switch A, configure the MBGP peer and enable direct route redistribution. [SwitchA] bgp 100 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] peer 192.168.1.2 as-number 200 [SwitchA-bgp] import-route direct [SwitchA-bgp] ipv4-family multicast [SwitchA-bgp-af-mul] peer 192.168.1.2 enable...
Page 251 Use the display msdp brief command to display MSDP peers on a switch. For example, display brief information about MSDP peers on Switch B. [SwitchB] display msdp brief MSDP Peer Brief Information of VPN-Instance: public net Configured Listen Connect Shutdown Down Peer's Address State...
Page 252: Mld Snooping Configuration
MLD snooping configuration MLD snooping overview MLD snooping is an IPv6 multicast constraining mechanism that runs on Layer 2 switches to manage and control IPv6 multicast groups. Introduction to MLD snooping By analyzing received MLD messages, a Layer 2 switch that runs MLD snooping establishes mappings between ports and multicast MAC addresses and forwards IPv6 multicast data based on these mappings.
Page 253: Basic Concepts In Mld Snooping
Basic concepts in MLD snooping MLD snooping related ports As shown in Figure 64, Router A connects to the multicast source, MLD snooping runs on Switch A and Switch B, and Host A and Host C are receiver hosts—namely, IPv6 multicast group members. Figure 64 MLD snooping related ports Receiver Router A...
Page 254: How Mld Snooping Works
Aging timers for dynamic ports and related messages and actions Message before Timer Description Action after expiry expiry For each dynamic router MLD general query of The switch removes this Dynamic router port port, the switch sets a timer which the source port from its router port aging timer initialized to the dynamic...
Page 255 If no forwarding table entry exists for the reported IPv6 multicast group, the switch creates an entry, • adds the port as a dynamic member port to the outgoing port list, and starts a member port aging timer for that port. If a forwarding table entry exists for the reported IPv6 multicast group but the port is not included in •...
Page 256: Mld Snooping Proxying
MLD snooping proxying You can configure the MLD snooping proxying function on an edge device to reduce the number of MLD reports and done messages sent to its upstream device. The device configured with MLD snooping proxying is called an MLD snooping proxy. It is a host from the perspective of its upstream device. NOTE: 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.
Page 257: 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 the receiving port. After making sure that no Done member port is contained in the forwarding entry for the IPv6 multicast group, the proxy sends a done message for the group out all router ports.
Page 258: Configuring Basic Functions Of Mld Snooping
NOTE: In MLD-snooping view, configurations that you make are effective on all VLANs. In VLAN view, • 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 259: Configuring The Version Of Mld Snooping
Configuring the version of MLD snooping By configuring the MLD snooping version, you actually configure the version of MLD messages that MLD snooping can process. MLDv1 snooping can process MLDv1 messages, but cannot analyze or process MLDv2 messages, • which will be flooded in the VLAN. MLDv2 snooping can process MLDv1 and MLDv2 messages.
Page 260: Configuring Mld Snooping Port Functions
To do... Use the command... Remarks Required In Ethernet interface view or Layer 2 aggregate interface Enter Ethernet interface view, interface interface-type interface- view, the configuration takes Layer 2 aggregate interface view, number effect on only the current or port group view interface.
Page 261: Configuring Static Ports
Configuring aging timers for dynamic ports globally Follow these steps to configure aging timers for dynamic ports globally: To do... Use the command... Remarks Enter system view system-view — Enter MLD snooping view mld-snooping — Optional Set the aging timer for dynamic router-aging-time interval router ports 260 seconds by default...
Page 262: Configuring Simulated Joining
NOTE: An IPv6 static (S, G) entry for a port takes effect only if a valid IPv6 multicast source address is specified and MLDv2 snooping runs. A static member port does not respond to queries from the MLD querier. When a static (*, G) or (S, G) entry is configured or removed for a port, the port does not send an unsolicited MLD report or an MLD done message.
Page 263: Disabling A Port From Becoming A Dynamic Router Port
switch immediately removes that port from the outgoing port list of the forwarding table entry for the indicated IPv6 multicast group. Then, when the switch receives MLD multicast-address-specific queries for that IPv6 multicast group, it does not forward them to that port. In VLANs where only one host is attached to each port, fast-leave processing helps improve bandwidth and resource usage.
Page 264: Configuring Mld Snooping Querier
To do... Use the command... Remarks Enter system view system-view — Enter Ethernet interface view, interface interface-type interface-number Required Layer 2 aggregate interface Use either approach port-group manual port-group-name view, or port group view Required Disable the port from mld-snooping router-port-deny [ vlan By default, a port can becoming a dynamic router vlan-list ]...
Page 265: Configuring Mld Queries And Responses
NOTE: It is meaningless to configure an MLD snooping querier in an IPv6 multicast network that runs MLD. Although an MLD snooping querier does not participate in MLD querier elections, it might affect MLD querier elections because it sends MLD general queries with a low source IPv6 address. For more information about MLD querier, see the chapter “MLD configuration.”...
Page 266: Configuring Source Ipv6 Addresses Of Mld Queries
To do... Use the command... Remarks Optional Set the MLD last-member query mld-snooping last-listener-query- interval interval interval 1 second by default CAUTION: Be sure to configure the MLD query interval greater than the maximum response time for MLD general queries. Otherwise, unexpected deletion of IPv6 multicast members might occur. Configuring source IPv6 addresses of MLD queries This configuration allows you to change the source IPv6 address of MLD queries.
Page 267: Configuring A Source Ipv6 Address For The Mld Messages Sent By The Proxy
To do... Use the command... Remarks Enter system view system-view — Enter VLAN view vlan vlan-id — Required Enable MLD snooping proxying mld-snooping proxying enable in the VLAN Disabled by default. Configuring a source IPv6 address for the MLD messages sent by the proxy You can set the source IPv6 addresses in the MLD reports and done messages that the MLD snooping proxy sends on behalf of its attached hosts.
Page 268: Configuring Ipv6 Multicast Source Port Filtering
IPv6 multicast data that fails the ACL check is not sent to this port. In this way, the service provider can control the VOD programs provided for multicast users. Configuring an IPv6 multicast group filter globally Follow these steps to configure an IPv6 multicast group globally: To do...
Page 269: Configuring The Function Of Dropping Unknown Ipv6 Multicast Data
Configuring IPv6 multicast source port filtering on a port or a group of ports Follow these steps to configure IPv6 multicast source port filtering on a port or a group of ports: To do... Use the command... Remarks Enter system view system-view —...
Page 270: Configuring The Maximum Number Of Multicast Groups That A Port Can Join
To do... Use the command... Remarks Enter MLD snooping view mld-snooping — Optional Enable MLD report suppression report-aggregation Enabled by default CAUTION: On an MLD snooping proxy, MLD membership reports are suppressed if the entries for the corresponding groups exist in the forwarding table, regardless of whether the suppression function is enabled or not.
Page 271: Configuring 802.1P Precedence For Mld Messages
To address this situation, enable the IPv6 multicast group replacement function on the switch or a certain port. When the number of IPv6 multicast groups that a switch or a port has joined exceeds the limit, one of the following occurs: If the IPv6 multicast group replacement is not enabled, new MLD reports will be automatically •...
Page 272: Configuring An Ipv6 Multicast User Control Policy
To do... Use the command... Remarks Enter MLD snooping view mld-snooping — Required Configure 802.1p precedence dot1p-priority priority-number The default 802.1p precedence for for MLD Messages MLD messages is 0. Configuring 802.1p precedence for MLD messages in a VLAN Follow these steps to configure 802.1p precedence for MLD messages in a VLAN: To do...
Page 273: Displaying And Maintaining Mld Snooping
To do... Use the command... Remarks Required Enable the created user profile user-profile profile-name enable Not enabled by default. NOTE: Security For more information about the user-profile and user-profile enable commands, see the Command Reference. An IPv6 multicast user control policy is functionally similar to an IPv6 multicast group filter. A difference lies in that a control policy can control both multicast joining and leaving of users based on authentication and authorization, but a multicast group filter is configured on a port to control only multicast joining but not leaving of users without authentication or authorization.
Page 274: Mld Snooping Configuration Examples
MLD snooping configuration examples IPv6 group policy and simulated joining configuration example Network requirements As shown in Figure 66, Router A connects to the IPv6 multicast source through GigabitEthernet • 1/0/2 and to Switch A through GigabitEthernet 1/0/1. Router A is the MLD querier on the subnet. MLDv1 runs on Router A, MLDv1 snooping runs on Switch A, and Router A acts as the MLD querier •...
Page 275 [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. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/4 [SwitchA-vlan100] mld-snooping enable...
Page 276: Static Port Configuration Example
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). GE1/0/3 GE1/0/4 The output shows that GigabitEthernet 1/0/3 and GigabitEthernet 1/0/4 of Switch A have joined IPv6...
Page 277 Figure 67 Network diagram for static port configuration Source Switch A GE1/0/2 GE1/0/1 1::2/64 2001::1/64 GE1/0/1 Router A 1::1/64 MLD querier Switch C GE1/0/5 GE1/0/2 GE1/0/2 Host C Switch B Receiver Host B Host A Receiver Configuration procedure Enable IPv6 forwarding and configure IPv6 addresses Enable IPv6 forwarding and configure an IPv6 address and prefix length for each interface according to Figure Configure Router A...
Page 278 # 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 279 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). GE1/0/2 (D) ( 00:03:23 ) MAC group(s):...
Page 280: Mld Snooping Querier Configuration Example
MLD snooping querier configuration example Network requirements As shown in Figure 68, 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 281: Mld Snooping Proxying Configuration Example
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. [SwitchB] vlan 100 [SwitchB-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/4 # Enable the MLD snooping feature and the function of dropping unknown IPv6 multicast data packets in VLAN 100.
Page 282 Figure 69 Network diagram for MLD snooping proxying configuration Configuration procedure Configure IPv6 addresses for interfaces Configure an IP address and prefix length for each interface according to Figure 69 (details not shown). Configure Router A # Enable IPv6 multicast routing, enable IPv6 PIM-DM on each interface, and enable MLD on port GigabitEthernet 1/0/1.
Page 283 After the configuration is completed, Host A and Host B send MLD join messages addressed to group FF1E::101. When receiving the messages, Switch A sends a join message for the group out port GigabitEthernet 1/0/1—a router port—to Router A. Use the display mld-snooping group command and the display mld group command to display information about MLD snooping groups and MLD multicast groups.
Page 284: Ipv6 Multicast Source And User Control Policy Configuration Example
Total 1 IP Source(s). Total 1 MAC Group(s). Port flags: D-Dynamic port, S-Static port, C-Copy port Subvlan flags: R-Real VLAN, C-Copy VLAN Vlan(id):100. Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s). Router port(s):total 1 port(s). GE1/0/1 (D) ( 00:01:23 ) IP group(s):the following ip group(s) match to one mac group.
Page 285 Figure 70 Network diagram for IPv6 multicast source/user control policy configuration Source 1 1::1/64 GE1/0/1 Source 2 Vlan-int101 Receiver GE1/0/2 Switch B 1::2/24 Vlan-int102 GE1/0/1 GE1/0/3 2::2/64 GE1/0/4 Vlan-int104 GE1/0/3 Host A GE1/0/2 2001::1/64 2::1/64 Vlan-int103 3::2/64 Switch A RADIUS server 3::1/64 Host B Configuration procedures...
Page 286 [SwitchA-Vlan-interface102] quit [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 CAUTION:...
Page 287 # Create an ISP domain domain1; reference scheme1 for the authentication, authorization, and accounting for LAN users; specify domain1 as the default ISP domain. [SwitchA] domain domain1 [SwitchA-isp-domian1] authentication lan-access radius-scheme scheme1 [SwitchA-isp-domian1] authorization lan-access radius-scheme scheme1 [SwitchA-isp-domian1] accounting lan-access radius-scheme scheme1 [SwitchA-isp-domian1] quit [SwitchA] domain default enable domain1 # Globally enable 802.1X and then enable it on GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2...
Page 288 [SwitchB-radius-scheme2] user-name-format without-domain [SwitchB-radius-scheme2] quit # Create an ISP domain domain2; reference scheme2 for the authentication, authorization, and accounting for LAN users; specify domain2 as the default ISP domain. [SwitchB] domain domain2 [SwitchB-isp-domian2] authentication lan-access radius-scheme scheme2 [SwitchB-isp-domian2] authorization lan-access radius-scheme scheme2 [SwitchB-isp-domian2] accounting lan-access radius-scheme scheme2 [SwitchB-isp-domian2] quit [SwitchB] domain default enable domain2...
Page 289: Troubleshooting Mld Snooping
Host port(s):total 1 port(s). GE1/0/3 (D) ( 00:04:10 ) MAC group(s): MAC group address:3333-0000-0101 Host port(s):total 1 port(s). GE1/0/3 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.
Page 290: 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 291 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. For more information about this command, see the Multicast Command Reference 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 292: Ipv6 Multicast Vlan Configuration
IPv6 multicast VLAN configuration IPv6 multicast VLAN overview As shown in Figure 71, 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 293 Figure 72 Sub-VLAN-based IPv6 multicast VLAN IPv6 Multicast packets VLAN 10 (IPv6 Multicast VLAN) VLAN 2 VLAN 2 Receiver VLAN 3 Host A VLAN 4 VLAN 3 Receiver Host B Router A Switch A Source MLD querier VLAN 4 Receiver Host C After the configuration, MLD snooping manages router ports in the IPv6 multicast VLAN and member ports in the sub-VLANs.
Page 294: Ipv6 Multicast Vlan Configuration Task List
NOTE: For more information about MLD snooping, router ports, and member ports, see the chapter “MLD snooping configuration.” Layer 2—LAN Switching Configuration Guide. For more information about VLAN tags, see the IPv6 multicast VLAN configuration task list Complete the following tasks to configure IPv6 multicast VLAN: Configuration task Remarks Configuring IPv6 sub-VLAN-based IPv6 multicast VLAN...
Page 295: Configuring Port-Based Ipv6 Multicast Vlan
NOTE: You cannot configure IPv6 multicast VLAN on a device with IP multicast routing enabled. The VLAN to be configured as an IPv6 multicast VLAN must exist. The VLANs to be configured as the sub-VLANs of the IPv6 multicast VLAN must exist and must not be sub-VLANs of another IPv6 multicast VLAN.
Page 296: Configuring Ipv6 Multicast Vlan Ports
To do... Use the command... Remarks Specify the user VLAN that Required comprises the current user ports port hybrid pvid vlan vlan-id VLAN 1 by default as the default VLAN Configure the current user ports to Required permit packets of the specified port hybrid vlan vlan-id-list { By default, a hybrid port permits IPv6 multicast VLAN to pass and...
Page 297: Displaying And Maintaining Ipv6 Multicast Vlan
To do… Use this command… Remarks Required Configure the ports as By default, a user port does member ports of the IPv6 port multicast-vlan ipv6 vlan-id not belong to any IPv6 multicast VLAN multicast VLAN. NOTE: You cannot configure IPv6 multicast VLAN on a device with multicast routing enabled. The VLAN to be configured as an IPv6 multicast VLAN must exist.
Page 298 Figure 74 Network diagram for sub-VLAN-based IPv6 multicast VLAN configuration 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 GE1/0/2 GE1/0/4 GE1/0/3 Receiver Receiver Receiver Host A Host B Host C VLAN 2 VLAN 3 VLAN 4 Configuration procedure Enable IPv6 forwarding, and configure IPv6 addresses Enable IPv6 forwarding on each device and configure an IPv6 address and address prefix for each...
Page 299 [SwitchA] vlan 10 [SwitchA-vlan10] port gigabitethernet 1/0/1 [SwitchA-vlan10] mld-snooping enable [SwitchA-vlan10] quit # Configure VLAN 10 as an IPv6 multicast VLAN and configure VLAN 2 through VLAN 4 as its sub- VLANs. [SwitchA] multicast-vlan ipv6 10 [SwitchA-ipv6-mvlan-10] subvlan 2 to 4 [SwitchA-ipv6-mvlan-10] quit Verify the configuration # Display information about the IPv6 multicast VLAN.
Page 300: Port-Based Multicast Vlan Configuration Example
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):4. Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s). Router port(s):total 0 port(s). IP group(s):the following ip group(s) match to one mac group. IP group address:FF1E::101 (::, FF1E::101): Host port(s):total 1 port(s).
Page 301 Configure the port-based IPv6 multicast VLAN feature so that Router A sends IPv6 multicast data to • Switch A through the IPv6 multicast VLAN, and Switch A forwards the IPv6 multicast data to the receivers that belong to different user VLANs. Figure 75 Network diagram for port-based IPv6 multicast VLAN configuration Source MLD querier...
Page 302 [SwitchA-vlan10] mld-snooping enable [SwitchA-vlan10] quit # Create VLAN 2 and enable MLD snooping in the VLAN. [SwitchA] vlan 2 [SwitchA-vlan2] mld-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. Configure VLAN 2 as the default VLAN. Configure GigabitEthernet 1/0/2 to permit packets of VLAN 2 to pass and untag the packets when forwarding them.
Page 303 Total 1 IP Source(s). Total 1 MAC Group(s). Router port(s):total 1 port(s). GE1/0/1 IP group(s):the following ip group(s) match to one mac group. IP group address:FF1E::101 (::, FF1E::101): Host port(s):total 3 port(s). GE1/0/2 GE1/0/3 GE1/0/4 MAC group(s): MAC group address:3333-0000-0101 Host port(s):total 3 port(s).
Page 304: Ipv6 Multicast Routing And Forwarding Configuration (Available Only On The A5500 Ei)
IPv6 multicast routing and forwarding configuration (available only on the A5500 EI) NOTE: router The term in this document refers to both routers and Layer 3 switches. The interfaces in this document refer to Layer 3 interfaces in generic sense and Ethernet interfaces operating in route mode.
Page 305 The router chooses an optimal route from the IPv6 unicast routing table and the IPv6 MBGP routing table, respectively: The router searches its IPv6 unicast routing table using the IPv6 address of the packet source as the destination address and automatically selects the optimal route as the RPF route. The outgoing interface in the corresponding routing entry is the RPF interface and the next hop is the RPF neighbor.
Page 306: Configuration Task List
If the corresponding (S, G) entry exists, but the interface that received the packet is not the incoming interface in the IPv6 multicast forwarding table, the IPv6 multicast packet is subject to an RPF check. If the RPF interface is the incoming interface of the (S, G) entry, this means that the (S, G) entry is correct but the packet arrived from a wrong path.
Page 307: Enabling Ipv6 Multicast Routing
Task Remarks Configuring an IPv6 multicast Optional forwarding range Configuring the IPv6 multicast Optional forwarding table size Enabling IPv6 multicast routing Before you configure any Layer 3 IPv6 multicast functionality, you must enable IPv6 multicast routing. Follow these steps to enable IPv6 multicast routing: To do…...
Page 308: Configuring An Ipv6 Multicast Forwarding Range
• NOTE: Setting the minimum hop limit is not supported on HP A5500 EI Switch Series. You can configure the forwarding boundary for a specific IPv6 multicast group or an IPv6 multicast group with the scope field in its group address being specified on all interfaces that support IPv6 multicast forwarding.
Page 309: Displaying And Maintaining Ipv6 Multicast Routing And Forwarding
maximum number of outgoing interfaces—for a single entry in the IPv6 multicast forwarding table to lessen the burden on the switch for replicating IPv6 multicast traffic. If the configured maximum number of downstream nodes for a single IPv6 multicast forwarding entry is smaller than the current number, the downstream nodes in excess are not deleted immediately.
Page 310: Troubleshooting Ipv6 Multicast Policy Configuration
reset multicast ipv6 forwarding-table { { ipv6- source-address [ prefix-length ] | ipv6-group- Clear forwarding entries from the IPv6 Available in address [ prefix-length ] | incoming-interface { multicast forwarding table user view interface-type interface-number | register } } * | all } reset multicast ipv6 routing-table { { ipv6-source- Clear routing entries from the IPv6...
Page 311 Evaluate the configuration of the multicast filter. Use the display current-configuration command to display the configuration of the IPv6 multicast filter. Change the IPv6 ACL rule used in the source- policy command so that the source IP address of the IPv6 multicast packets and the IPv6 multicast group address can both match the IPv6 ACL rule.
Page 312: Mld Configuration (Available Only On The A5500 Ei)
MLD configuration (available only on the A5500 EI) MLD overview An IPv6 router uses the Multicast Listener Discovery (MLD) protocol to discover the presence of multicast listeners on the directly attached subnets. Multicast listeners are nodes that want to receive IPv6 multicast packets.
Page 313 messages (often called “queries”). A 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. The destination address is FF02::1. Upon identifying a general query, every MLD router compares the source IPv6 address of the query message with its own interface address.
Page 314: How Mldv2 Works
At the same time, because Host A is interested in G2, it sends a report to the IPv6 multicast group address of G2. Through the query/report process, the MLD routers discover that members of G1 and G2 are attached to the local subnet. The IPv6 multicast routing protocol (for example, IPv6 PIM) that is running on the routers generates (*, G1) and (*, G2) multicast forwarding entries.
Page 315: Mld Messages
Figure 78 Flow paths of multicast-address-and-source-specific multicast traffic Source 1 Host A Receiver Host B Source 2 Host C Packets (S1,G) Packets (S2,G) In the case of MLDv1, Host B cannot select IPv6 multicast sources when it joins IPv6 multicast group G. Therefore, IPv6 multicast streams from both Source 1 and Source 2 will flow to Host B whether it needs them or not.
Page 316 Figure 79 MLDv2 query message format Type = 130 Code Checksum Maximum Response Delay Reserved Multicast Address (128 bits) Reserved QQIC Number of Sources (n) Source Address [1] (128 bits) Source Address [n] (128 bits) Table 10 MLDv2 query message field description Field Description Type = 130...
Page 317 Field Description • This field is set to 0 in a general query message or a multicast- address-specific query message. Number of Sources • This field represents the number of source addresses in a multicast- address-and-source-specific query message. IPv6 multicast source address in a multicast-address-specific query Source Address( i ) message.
Page 318: Mld Ssm Mapping
MLD SSM mapping You can use the MLD SSM mapping feature to configure static MLD SSM mappings on the last hop router to provide SSM support for receiver hosts that are running MLDv1. The SSM model assumes that the last hop router has identified the desired IPv6 multicast sources when receivers join IPv6 multicast groups.
Page 319: Mld Proxying
MLD proxying In some simple tree-shaped topologies, you do not need to configure complex IPv6 multicast routing protocols, such as IPv6 PIM, on the boundary device. Instead, you can configure MLD proxying on the boundary device. With MLD proxying configured, the device serves as a proxy for the downstream hosts to send MLD messages, maintain group memberships, and implement IPv6 multicast forwarding based on the memberships.
Page 320: Mld Configuration Task List
RFC 4605, Internet Group Management Protocol (IGMP)/Multicast Listener Discovery (MLD)-Based • Multicast Forwarding (“IGMP/MLD Proxying”) MLD configuration task list Complete these tasks to configure MLD: Task Remarks Enabling MLD Required Configuring the MLD version Option Configuring static joining Optional Configuring basic functions of MLD Configuring an ipv6 multicast group filter Optional Configuring the maximum number of IPv6...
Page 321: Enabling Mld
Determine the ACL rule for IPv6 multicast group filtering • Determine the maximum number of IPv6 multicast groups that can be joined on an interface • Enabling MLD Enable MLD on the interface on which IPv6 multicast group memberships will be created and maintained.
Page 322: Configuring Static Joining
Configuring static joining After you configure an interface as a static member of an IPv6 multicast group or an IPv6 multicast source and group, the interface will act as a virtual member of the IPv6 multicast group to receive IPv6 multicast data addressed to that IPv6 multicast group for the purpose of testing IPv6 multicast data forwarding.
Page 323: Configuring The Maximum Number Of Ipv6 Multicast Groups That An Interface Can Join
To do… Use the command… Remarks Required By default, no IPv6 group filter is Configure an IPv6 multicast group mld group-policy acl6-number [ configured on the interface. That filter version-number ] is, hosts on the current interface can join any valid multicast group.
Page 324: Configuring Mld Message Options
Determine the maximum response delay of MLD general query messages • Determine the MLD last listener query interval • Determine the MLD other querier present interval • Configuring MLD message options MLD queries include multicast-address-specific queries and multicast-address-and-source-specific queries, and IPv6 multicast groups change dynamically, so a device cannot maintain the information for all IPv6 multicast sources and groups.
Page 325: Configuring Mld Query And Response Parameters
To do… Use the command… Remarks Optional Enable the insertion of the Router- mld send-router-alert By default, MLD messages carry Alert option into MLD messages the Router-Alert option. Configuring MLD query and response parameters On startup, the MLD querier sends MLD general queries at the startup query interval, which is one- quarter of the MLD query interval.
Page 326 To do… Use the command… Remarks Optional Configure the startup query By default, the startup query startup-query-interval interval interval interval is 1/4 of the “MLD query interval”. Optional By default, the startup query count Configure the startup query count startup-query-count value is set to the MLD querier’s robustness variable.
Page 327: Configuring Mld Fast Leave Processing
To do… Use the command… Remarks Configure the maximum response Optional delay for MLD general query mld max-response-time interval 10 seconds by default messages Optional Configure the MLD last listener mld last-listener-query-interval query interval interval 1 second by default Optional By default, the other querier present interval is determined by the formula: Other querier present...
Page 328: Configuring Mld Ssm Mappings
To do… Use the command… Remarks interface interface-type interface- Enter interface view — number Required Enable the MLD SSM mapping mld ssm-mapping enable feature Disabled by default NOTE: To ensure SSM service for all hosts on a subnet, regardless of the MLD version that is running on the hosts, enable MLDv2 on the interface that forwards IPv6 multicast traffic onto the subnet.
Page 329: Configuring Ipv6 Multicast Forwarding On A Downstream Interface
Follow these steps to enable MLD proxying: To do… Use the command… Remarks Enter system view system-view — interface interface-type interface- Enter interface view — number Required Enable the MLD proxying feature mld proxying enable Disabled by default NOTE: Each device can have only one interface serving as the MLD proxy interface. Do not enable MLD on interfaces with MLD proxying enabled.
Page 330: Displaying And Maintaining Mld Configuration
Displaying and maintaining MLD configuration To do… Use the command… Remarks display mld group [ ipv6-group-address | interface Available in Display MLD group information interface-type interface-number ] [ static | verbose ] [ | { any view begin | exclude | include } regular-expression ] display mld group port-info [ vlan vlan-id ] [ slot slot- Display Layer 2 port information Available in...
Page 331: Mld Configuration Examples
MLD configuration examples Basic MLD functions configuration example Network requirements As shown in Figure 83, 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 332 # Enable IPv6 multicast routing on Switch A, enable IPv6 PIM-DM on each interface, and enable MLD on VLAN-interface 100. <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 IPv6 PIM-DM on each interface, and enable MLD on...
Page 333: Mld Ssm Mapping Configuration Example
MLD SSM mapping configuration example Network requirements As shown in Figure 84, the IPv6 PIM-SM domain applies both the ASM model and SSM model for • IPv6 multicast delivery. Switch D’s VLAN-interface 104 serves as the C-BSR and C-RP. The SSM group range is FF3E::/64.
Page 334 # Enable IPv6 multicast routing on Switch D, enable IPv6 PIM-SM on each interface, and enable MLDv2 and MLD SSM mapping on VLAN-interface 400. <SwitchD> system-view [SwitchD] multicast ipv6 routing-enable [SwitchD] interface vlan-interface 400 [SwitchD-Vlan-interface400] mld enable [SwitchD-Vlan-interface400] mld version 2 [SwitchD-Vlan-interface400] mld ssm-mapping enable [SwitchD-Vlan-interface400] pim ipv6 sm [SwitchD-Vlan-interface400] quit...
Page 335 # 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 Verify the configuration Use the display mld ssm-mapping command to view MLD SSM mappings on the switch. # Display the MLD SSM mapping information for IPv6 multicast group FF3E::101 on Switch D. [SwitchD] display mld ssm-mapping ff3e::101 Group: FF3E::101 Source list:...
Page 336: Mld Proxying Configuration Example
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 85, IPv6 PIM-DM is required to run on the core network. Host A and Host C in the stub network receive VOD information destined to multicast group FF3E::101.
Page 337: Troubleshooting Mld
# 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 Verify the installation Use the display mld interface command to view the MLD configuration and operation information on an...
Page 338: 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 •...
Page 339: Ipv6 Pim Configuration (Available Only On The A5500 Ei)
IPv6 PIM configuration (available only on the A5500 EI) NOTE: router The term in this document refers to both routers and Layer 3 switches. • IPv6 PIM domain To facilitate description, the term refers to a network that comprises IPv6 PIM– •...
Page 340 When a new receiver on a previously pruned branch joins an IPv6 multicast group, to reduce the • join latency, IPv6 PIM-DM uses the graft mechanism to resume IPv6 multicast data forwarding to that branch. In general, the IPv6 multicast forwarding path is a source tree. That is, it is a forwarding tree with the IPv6 multicast source as its “root”...
Page 341 Figure 86 SPT establishment in an IPv6 PIM-DM domain The flood-and-prune process occurs periodically. A pruned state timeout mechanism exists. 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 IPv6 PIM-SM.
Page 342: Ipv6 Pim-Sm Overview
Figure 87 Assert mechanism As shown in Figure 87, after Router A and Router B receive an (S, G) IPv6 multicast packet from the upstream node, they both forward the packet to the local subnet. As a result, the downstream node Router C receives two identical multicast packets, and both Router A and Router B, on their own local interface, receive a duplicate IPv6 multicast packet that the other has forwarded.
Page 343 IPv6 multicast group. The path along which the message goes hop by hop to the RP forms a branch of the RPT. When an IPv6 multicast source sends IPv6 multicast streams to an IPv6 multicast group, the source- • side designated router (DR) first registers the multicast source with the RP by sending register messages to the RP by unicast until it receives a register-stop message from the RP.
Page 344 Figure 88 DR election Receiver Source Receiver Hello message Register message Join message As shown in Figure 88, the DR election process is as follows: Routers on the multi-access network send hello messages to one another. The hello messages contain the router priority for DR election. The router with the highest DR priority will become the In the case of a tie in the router priority, or if any router in the network does not support carrying the DR-election priority in hello messages, the router with the highest IPv6 link-local address will win the DR election.
Page 345 mappings between IPv6 multicast groups and RPs. The BSR then encapsulates the RP-set in the bootstrap messages it periodically originates and floods the bootstrap messages (BSMs) to the entire IPv6 PIM-SM domain. Figure 89 BSR and C-RPs IPv6 PIM-SM C-RP C-RP C-BSR C-RP...
Page 346 Embedded RP The embedded RP mechanism enables a router to resolve the RP address from an IPv6 multicast address so that the IPv6 multicast group is mapped to an RP. This RP can take the place of the statically configured RP or the RP dynamically calculated based on the BSR mechanism. The DR does not need to identify the RP address beforehand.
Page 347 receiving the prune message, the upstream node deletes the interface connected with this downstream node from the outgoing interface list and determines whether it has receivers for that IPv6 multicast group. If not, the router continues to forward the prune message to its upstream router. Multicast source registration The purpose of IPv6 multicast source registration will inform the RP about the existence of the IPv6 multicast source.
Page 348: Ipv6 Bidir-Pim Overview
multicast group in register messages and sends these messages to the RP. Upon receiving these register messages, the RP extracts the multicast data and sends the multicast data down the RPT to the DRs at the receiver side. The RP acts as a transfer station for all IPv6 multicast packets. The process involves the following issues: The DR at the source side and the RP need to implement complicated encapsulation and de- •...
Page 349 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: Neighbor discovery • RP discovery • DF election • Bidirectional RPT building • Neighbor discovery IPv6 BIDIR-PIM uses the same neighbor discovery mechanism as IPv6 PIM-SM does. For more information, see “Neighbor discovery.”...
Page 350 Figure 92 DF election As shown in Figure 92, 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 351 Figure 93 RPT building at the receiver side Source Receiver Host A Server B Source Receiver Host B Server A Receiver Join message Receiver-side RPT IPv6 Multicast packets Host C As shown in Figure 93, 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 IGMP message to inform the directly connected router.
Page 352: Ipv6 Administrative Scoping Overview
Figure 94 RPT building at the multicast source side Source Receiver Host A Server B Source Receiver Host B Server A Receiver Source-side RPT IPv6 Multicast packets Host C As shown in Figure 94, 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 353 IPv6 admin-scope zones correspond to IPv6 multicast groups with different scope values in their group addresses. The boundary of the IPv6 admin-scope zone is formed by zone border routers (ZBRs). Each IPv6 admin-scope zone maintains one BSR, which serves multicast groups within a specific scope. IPv6 multicast protocol packets, such as assert messages and bootstrap messages, for a specific group range cannot cross the IPv6 admin-scope zone boundary.
Page 354: Ipv6 Pim-Ssm Overview
Figure 96 IPv6 multicast address format The admin-scope zone range increases with the value of the Scope field. For example, value E indicates IPv6 global scope, which contains other admin-scope zones with the Scope field values smaller than E. Table 13 Values of the Scope field Value Meaning Remarks...
Page 355 Neighbor discovery IPv6 PIM-SSM uses the same neighbor discovery mechanism as in IPv6 PIM-SM. For more information, “Neighbor discovery.” DR election IPv6 PIM-SSM uses the same DR election mechanism as in IPv6 PIM-SM. For more information, see “DR election.” SPT building The decision to build an RPT for IPv6 PIM-SM or an SPT for IPv6 PIM-SSM depends on whether the IPv6 multicast group that the receiver will join falls into the IPv6 SSM group range.
Page 356: Relationships Among Ipv6 Pim Protocols
Relationships among IPv6 PIM protocols In an IPv6 PIM network, IPv6 PIM-DM cannot work with IPv6 PIM-SM, IPv6 BIDIR-PIM, or IPv6 PIM-SSM. However, IPv6 PIM-SM, IPv6 BIDIR-PIM, and IPv6 PIM-SSM can work together. When they work together, they are adopted in the order of IPv6 PIM-SSM, IPv6 BIDIR-PIM, and IPv6 PIM-SM, as shown in Figure Figure 98 Selection of IPv6 PIM-SM, IPv6 BIDIR-PIM, and IPv6 PIM-SSM A receiver joins IPv6 multicast group G.
Page 357: Configuring Ipv6 Pim-Dm
Configuring IPv6 PIM-DM IPv6 PIM-DM configuration task list Complete these tasks to configure IPv6 PIM-DM: Task Remarks Enabling IPv6 PIM-DM Required Enabling state-refresh capability Optional 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:...
Page 358: Enabling State-Refresh Capability
NOTE: IP Multicast For more information about the multicast ipv6 routing-enable command, see the Command Reference Enabling state-refresh capability Pruned interfaces resume multicast forwarding when the pruned state times out. To prevent this, the router directly connected with the IPv6 multicast source periodically sends an (S, G) state-refresh message, which is forwarded hop by hop along the initial flooding path of the IPv6 PIM-DM domain, to refresh the prune timer state of all the routers on the path.
Page 359: Configuring Ipv6 Pim-Dm Graft Retry Period
To do... Use the command... Remarks Optional Configure the hop limit value of state-refresh-hoplimit hoplimit- state-refresh messages value 255 by default 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, the graft retry period—until it receives a graft-ack message from the...
Page 360: Configuration Prerequisites
Task Remarks Enabling IPv6 administrative scoping Optional Configuring IPv6 Configuring an IPv6 admin-scope zone boundary Optional administrative scoping Configuring C-BSRs for IPv6 admin-scope zones Optional Configuring IPv6 multicast source registration Optional Disabling SPT switchover Optional Configuring IPv6 PIM common features Optional Configuration prerequisites Before you configure IPv6 PIM-SM, complete the following tasks:...
Page 361: Configuring An Rp
To do... Use the command... Remarks interface interface-type interface- Enter interface view — number Required Enable IPv6 PIM-SM pim ipv6 sm Disabled by default. CAUTION: All interfaces of the same device must work in the same IPv6 PIM mode. NOTE: IP Multicast For more information about the multicast ipv6 routing-enable command, see the Command Reference...
Page 362 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. HP recommends that you configure C-RPs on backbone routers.
Page 363: Configuring A Bsr
IPv6 PIM-SM domain. Configuring a C-BSR HP recommends that you configure C-BSRs on routers in the backbone network. When you are configuring a router as a C-BSR, be sure to specify the IPv6 address of an IPv6 PIM-SM-enabled interface on the router.
Page 364 Some maliciously configured hosts can forge bootstrap messages to fool routers and change RP mappings. Such attacks often occur on border routers. Because a BSR is inside the network whereas hosts are outside the network, a BSR can be protected against attacks from external hosts after you enable the border routers to perform neighbor checks and RPF checks on bootstrap messages and to discard unwanted messages.
Page 365 To do... Use the command... Remarks Required Configure an IPv6 PIM domain pim ipv6 bsr-boundary No IPv6 PIM domain border is border configured by default. Configuring C-BSR parameters globally In each IPv6 PIM-SM domain, a unique BSR is elected from C-BSRs. The C-RPs in the IPv6 PIM-SM domain send advertisement messages to the BSR.
Page 366 NOTE: About the BS period: By default, the BS period is determined by this formula “BS period = (BS timeout – 10) / 2”. The • default BS timeout is 130 seconds, so the default BS period = (130 – 10) / 2 = 60 (seconds). If this parameter is manually configured, the system will use the configured value.
Page 367: Configuring Ipv6 Administrative Scoping
Configuring IPv6 administrative scoping With IPv6 administrative scoping disabled, an IPv6 PIM-SM domain has only one BSR. The BSR manages the whole network. To manage your network more effectively and specifically, partition the IPv6 PIM-SM domain into multiple IPv6 admin-scope zones. Each IPv6 admin-scope zone maintains a BSR, which serves a specific IPv6 multicast group range.
Page 368: 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, HP does not recommend this method of checksum calculation.
Page 369: Disabling Spt Switchover
Configure a filtering rule for register messages on all C-RP routers, and configure them to calculate the checksum based on the entire register messages. Configure the register suppression time and the register probe time on all routers that might become source-side DRs. Follow these steps to configure register-related parameters: To do...
Page 370: Configuring Ipv6 Bidir-Pim
Configuring IPv6 BIDIR-PIM IPv6 BIDIR-PIM configuration task list Complete these tasks to configure IPv6 BIDIR-PIM: Task Remarks Enabling IPv6 PIM-SM Required Enabling IPv6 BIDIR-PIM Required Configuring a static RP Required Configuring a C-RP Use any Configuring an RP approach Enabling embedded RP Configuring C-RP timers globally Optional Configuring a C-BSR...
Page 371: Enabling Ipv6 Pim-Sm
Determine the BS timeout. • Enabling IPv6 PIM-SM Because IPV6 BIDIR-PIM is implemented on the basis of IPv6 PIM-SM, you must enable IPv6 PIM-SM before enabling IPV6 BIDIR-PIM. To deploy an IPv6 BIDIR-PIM domain, enable IPv6 PIM-SM on all non- border interfaces of the domain.
Page 372 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. HP recommends that you configure C-RPs on backbone routers.
Page 373 To do... Use the command... Remarks c-rp ipv6-address [ { group-policy acl6- Required number | scope scope-id } | priority Configure an interface to be a C- priority | holdtime hold-interval | No C-RP is configured by RP for IPv6 BIDIR-PIM advertisement-interval adv-interval ] * default.
Page 374: Configuring A Bsr
To do... Use the command... Remarks Enter system view system-view — Enter IPv6 PIM view pim ipv6 — Optional c-rp advertisement-interval Configure the C-RP-Adv interval interval 60 seconds by default Optional Configure C-RP timeout time c-rp holdtime interval 150 seconds by default NOTE: For more information about the configuration of other timers in IPv6 PIM-SM, see “Configuring IPv6...
Page 375 The preventive measures can partially protect the security of BSRs in a network. However, if a legal BSR is controlled by an attacker, the mentioned problem will still occur. Follow these steps to configure a C-BSR: To do… Use the command… Remarks Enter system view system-view...
Page 376 To do… Use the command… Remarks Enter system view system-view — Enter IPv6 PIM view pim ipv6 — Optional Configure the hash mask length c-bsr hash-length hash-length 126 by default 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 it serves.
Page 377: Configuring Ipv6 Administrative Scoping
Disabling BSM semantic fragmentation Generally, a BSR periodically distributes the RP-set information in bootstrap messages within the IPv6 BIDIR-PIM domain. It encapsulates a BSM in an IP datagram and might split the datagram into fragments if the 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.
Page 378 To do… Use the command… Remarks Enter system view system-view — Enter IPv6 PIM view pim ipv6 — Required Enable IPv6 administrative c-bsr admin-scope scoping Disabled by default Configuring an IPv6 admin-scope zone boundary The boundary of each IPv6 admin-scope zone is formed by ZBRs. Each admin-scope zone maintains a BSR, which serves a specific IPv6 multicast group range.
Page 379: Configuring Ipv6 Pim-Ssm
NOTE: The following points apply to the hash mask length and C-BSR priority: You can configure these parameters at global configuration level and admin-scope zone level. • The value configured at the admin-scope zone level have preference over the global values. •...
Page 380: Configuring The Ipv6 Ssm Group Range
To do... Use the command... Remarks interface interface-type interface- Enter interface view — number Required Enable IPv6 PIM-SM pim ipv6 sm Disabled by default CAUTION: All interfaces of the same device must work in the same IPv6 PIM mode. NOTE: IP Multicast For more information about the multicast ipv6 routing-enable command, see the Command Reference...
Page 381: Ipv6 Pim Common Feature Configuration Task List
IPv6 PIM common feature configuration task list Complete these tasks to configure IPv6 PIM common features: Task Remarks Configuring an IPv6 multicast data filter Optional Configuring a hello message filter Optional Configuring IPv6 PIM hello options Optional Configuring the prune delay Optional Configuring IPv6 PIM common timers Optional...
Page 382: Configuring A Hello Message Filter
Follow these steps to configure an IPv6 multicast data filter: To do... Use the command... Remarks Enter system view system-view — Enter IPv6 PIM view pim ipv6 — Required Configure an IPv6 multicast group source-policy acl6-number No IPv6 multicast data filter by filter default NOTE:...
Page 383 LAN_Prune_Delay—Delay of prune messages on a multi-access network. This option consists of • LAN-delay (namely, prune message delay), override-interval, and neighbor tracking flag. If the LAN-delay or override- interval values of different IPv6 PIM routers on a multi-access subnet are different, the largest value will take effect.
Page 384: Configuring The Prune Delay
To do... Use the command... Remarks interface interface-type interface- Enter interface view — number Optional Configure the priority for DR pim ipv6 hello-option dr-priority election priority 1 by default Optional Configure IPv6 PIM neighbor pim ipv6 hello-option holdtime timeout time interval 105 seconds by default Optional...
Page 385 Any router that has lost assert election will prune its downstream interface and maintain the assert state for a period of time. When the assert state times out, the assert loser will resume IPv6 multicast forwarding. When a router fails to receive subsequent IPv6 multicast data from the IPv6 multicast source S, the router does not immediately delete the corresponding (S, G) entry.
Page 386: Configuring Join/Prune Message Sizes
NOTE: Use the default settings if no special networking requirements are raised. Configuring join/prune message sizes A larger join/prune message size will result in loss of a larger amount of information when a message is lost. With a reduced join/message size, the loss of a single message has a relatively minor impact. The maximum number of (S, G) entries in a join/prune message can reduce the number of (S, G) entries sent per unit of time.
Page 387: Ipv6 Pim Configuration Examples
To do... Use the command... Remarks display pim ipv6 join-prune mode { sm [ flags flag- value ] | ssm } [ interface interface-type interface- Display the information of Available in number | neighbor ipv6-neighbor-address ] * [ join/prune messages to send any view verbose ] [ | { begin | exclude | include } regular- expression ]...
Page 388 Figure 99 Network diagram for IPv6 PIM-DM configuration Device Interface IP address Device Interface IP 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...
Page 389 [SwitchA-Vlan-interface103] quit The configuration on Switch B and Switch C is similar to that on Switch A. # 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 [SwitchD] interface vlan-interface 103...
Page 390 entry is generated on Switch A. Use the display pim IPv6 routing-table command to view the IPv6 PIM routing table information on each switch. For example: # View the IPv6 PIM multicast routing table information on Switch A. [SwitchA] display pim ipv6 routing-table Total 1 (*, G) entry;...
Page 391: Ipv6 Pim-Sm Non-Scoped Zone Configuration Example
IPv6 PIM-SM non-scoped zone 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. The entire PIM domain operates in the sparse mode. Host A and Host C are IPv6 multicast receivers in two stub networks, N1 and N2.
Page 392 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, and configure IPv6 addresses and IPv6 unicast routing. Enable IPv6 forwarding on each switch, and configure the IPv6 address and prefix length for each interface according to Figure 100 (details not shown).
Page 393 [SwitchE] pim ipv6 [SwitchE-pim6] c-bsr 1003::2 128 20 [SwitchE-pim6] c-rp 1003::2 group-policy 2005 [SwitchE-pim6] quit Verify the configuration. Use the display pim ipv6 interface command to view the IPv6 PIM configuration and running status on each interface. For example: # View the IPv6 PIM information on all interfaces of Switch A. [SwitchA] display pim ipv6 interface Interface NbrCnt HelloInt...
Page 394 Hash mask length: 128 State: Elected Uptime: 00:01:10 Next BSR message scheduled at: 00:01:48 Candidate BSR Address: 1003::2 Priority: 20 Hash mask length: 128 State: Elected Candidate RP: 1003::2(Vlan-interface102) Priority: 192 HoldTime: 130 Advertisement Interval: 60 Next advertisement scheduled at: 00:00:48 To view the RP information discovered on a switch, use the display pim ipv6 rp-info command.
Page 395 Upstream interface: Vlan-interface102 Upstream neighbor: 1003::2 RPF prime neighbor: 1003::2 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: mld, UpTime: 00:02:15, Expires: 00:03:06 (4001::100, FF0E::100) RP: 1003::2 Protocol: pim-sm, Flag: SPT ACT UpTime: 00:02:15 Upstream interface: Vlan-interface101 Upstream neighbor: 1002::2 RPF prime neighbor: 1002::2 Downstream interface(s) information:...
Page 396: Ipv6 Pim-Sm Admin-Scope Zone Configuration Example
Total number of downstreams: 1 1: Vlan-interface102 Protocol: pim-sm, UpTime: 00:16:56, Expires: 00:02:34 IPv6 PIM-SM admin-scope zone configuration example Network requirements Receivers receive VOD information through multicast. The entire IPv6 PIM-SM domain is divided • into IPv6 admin-scope zone 1, IPv6 admin-scope zone 2, and the IPv6 global zone. Switch B, Switch C, and Switch D are ZBRs of these three domains respectively.
Page 397 Switch A Vlan-int100 1001::1/64 Switch D Vlan-int104 3002::2/64 Vlan-int101 1002::1/64 Vlan-int108 6001::1/64 Switch B Vlan-int200 2001::1/64 Vlan-int107 6002::1/64 Vlan-int101 1002::2/64 Switch E Vlan-int400 7001::1/64 Vlan-int103 2002::1/64 Vlan-int105 3003::2/64 Vlan-int102 2003::1/64 Vlan-int108 6001::2/64 Switch C Vlan-int300 3001::1/64 Switch F Vlan-int109 8001::1/64 Vlan-int104 3002::1/64 Vlan-int107...
Page 398 [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] pim ipv6 sm [SwitchB-Vlan-interface200] quit [SwitchB] interface vlan-interface 101 [SwitchB-Vlan-interface101] pim ipv6 sm [SwitchB-Vlan-interface101] quit [SwitchB] interface vlan-interface 102 [SwitchB-Vlan-interface102] pim ipv6 sm [SwitchB-Vlan-interface102] quit [SwitchB] interface vlan-interface 103 [SwitchB-Vlan-interface103] pim ipv6 sm [SwitchB-Vlan-interface103] quit The configuration on Switch C, Switch D, Switch F, Switch G, and Switch H is similar to the configuration on Switch B.
Page 399 # On Switch D, configure the service scope of RP advertisements, and configure VLAN-interface 104 as a C-BSR and C-RP of admin-scope zone 2. [SwitchD] pim ipv6 [SwitchD-pim6] c-bsr scope 4 [SwitchD-pim6] c-bsr 3002::2 [SwitchD-pim6] c-rp 3002::2 scope 4 [SwitchD-pim6] quit # On Switch F, configure VLAN-interface 109 as a C-BSR and C-RP in the global scope zone.
Page 400 Elected BSR Address: 8001::1 Priority: 64 Hash mask length: 126 State: Accept Preferred Scope: 14 Uptime: 00:01:45 Expires: 00:01:25 Elected BSR Address: 3002::2 Priority: 64 Hash mask length: 126 State: Elected Scope: 4 Uptime: 00:03:48 Next BSR message scheduled at: 00:01:12 Candidate BSR Address: 3002::2 Priority: 64 Hash mask length: 126...
Page 401 # View the RP information on Switch B. [SwitchB] display pim ipv6 rp-info PIM-SM BSR RP information: prefix/prefix length: FF0E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF1E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF2E::/16 RP: 8001::1...
Page 402 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF7E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF8E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF9E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFAE::/16...
Page 403 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFEE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFFE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF04::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51...
Page 404 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF54::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF64::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF74::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39...
Page 405 prefix/prefix length: FFB4::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFC4::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFD4::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFE4::/16 RP: 1002::2 Priority: 192 HoldTime: 130...
Page 406 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF2E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF3E::/16 RP: 8001::1 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...
Page 407 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF9E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFAE::/16 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...
Page 408: Ipv6 Bidir-Pim Configuration Example
Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 IPv6 BIDIR-PIM configuration example Network requirements In the IPv6 BIDIR-PIM domain in Figure 102. Source 1 and Source 2 send different multicast • information to IPv6 multicast group FF14::101. Host A and Host B receive multicast information from the two sources.
Page 409 Configure OSPF on the switches in the IPv6 BIDIR-PIM domain to ensure network-layer reachability among them (details not shown). Enable IPv6 multicast routing, IPv6 PIM-SM, IPv6 BIDIR-PIM, and MLD. # On Switch A, enable IPv6 multicast routing, enable IPv6 PIM-SM on each interface, and enable IPv6 BIDIR-PIM.
Page 410 [SwitchC-pim6] bidir-pim enable # On Switch D, enable IPv6 multicast routing, enable IPv6 PIM-SM on each interface, enable MLD on VLAN interface 300, and enable IPv6 BIDIR-PIM. <SwitchD> system-view [SwitchD] multicast ipv6 routing-enable [SwitchD] interface vlan-interface 300 [SwitchD-Vlan-interface300] mld enable [SwitchD-Vlan-interface300] pim ipv6 sm [SwitchD-Vlan-interface300] quit [SwitchD] interface vlan-interface 400...
Page 411 [SwitchC] display pim ipv6 df-info RP Address: 6001::1 Interface State DF-Pref DF-Metric DF-Uptime DF-Address Loop0 Vlan102 01:06:07 FE80::20F:E2FF: FE15:5601 (local) Vlan103 01:06:07 FE80::20F:E2FF: FE15:5602 (local) # View the DF information of IPv6 BIDIR-PIM on Switch D. [SwitchD] display pim ipv6 df-info RP Address: 6001::1 Interface State...
Page 412: Ipv6 Pim-Ssm Configuration Example
2: Vlan-interface200 # View the DF information of the IPv6 multicast forwarding table on Switch C. [SwitchC] 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:07:21 RPF interface: LoopBack0 List of 2 DF interfaces:...
Page 413 Figure 103 Network diagram for IPv6 PIM-SSM configuration Receiver Host A Switch A Vlan-int100 Vlan-int102 Host B Vlan-int102 Receiver Vlan-int300 Vlan-int105 Vlan-int103 Vlan-int200 Vlan-int105 Vlan-int103 Source Vlan-int104 Switch D Switch E Switch B Host C 4001::100/64 Vlan-int104 Vlan-int200 IPv6 PIM-SM Host D Switch C Device...
Page 414 [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim ipv6 sm [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] pim ipv6 sm [SwitchA-Vlan-interface102] quit The configuration on Switch B and Switch C is similar to that on Switch A. The configuration on Switch D and Switch E is also similar to that on Switch A except that it is not necessary to enable MLD on the corresponding interfaces on these two switches.
Page 415: Troubleshooting Ipv6 Pim Configuration
Total number of downstreams: 1 1: Vlan-interface100 Protocol: mld, UpTime: 00:00:11, Expires: 00:03:25 The output on Switch B and Switch C is similar to that on Switch A. # View the IPv6 PIM multicast routing table information on Switch B. [SwitchD] display pim ipv6 routing-table Total 0 (*, G) entry;...
Page 416: Ipv6 Multicast Data Abnormally Terminated On An Intermediate Router
Verify that IPv6 PIM and MLD are enabled on the interfaces that are directly connected to the IPv6 multicast source and to the receiver. Verify that the same IPv6 PIM mode is enabled on related interfaces. Use the display pim ipv6 interface verbose command to determine whether the same PIM mode is enabled on the RPF interface and the corresponding interface of the RPF neighbor router.
Page 417: Rpt Establishment Failure Or Source Registration Failure In Ipv6 Pim-Sm
Solution Verify that a route is available to the RP. Use the display ipv6 routing-table command to determine whether a route is available on each router to the RP. Evaluate the dynamic RP information. Use the display pim ipv6 rp-info command to determine whether the RP information is consistent on all routers.
Page 418: Ipv6 Mbgp Configuration (Available Only On The A5500 Ei)
IPv6 MBGP configuration (available only on the A5500 EI) NOTE: router The term in this document refers to both routers and Layer 3 switches. This chapter only describes configuration for IPv6 MBGP. For more information about IPv6 BGP, see Layer 3—IP Routing Configuration Guide Layer 3—IP .
Page 419: Configuring Ipv6 Mbgp Basic 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 optimizing IPv6 Enabling the IPv6 MBGP ORF capability Optional MBGP networks...
Page 420: Configuring A Preferred Value For Routes From A Peer/Peer Group
Configuring a preferred value for routes from a peer/peer group Follow these steps to configure a preferred value for routes from a peer/peer group: To do… Use the command… Remarks Enter system view system-view — Enter BGP view bgp as-number —...
Page 421: Configuring Ipv6 Mbgp Route Redistribution
Configuring IPv6 MBGP route redistribution Follow these steps to configure IPv6 MBGP route redistribution: To do… Use the command… Description Enter system view system-view — Enter BGP view bgp as-number — Enter IPv6 MBGP multicast ipv6-family multicast — address family view Optional Enable default route redistribution default-route imported...
Page 422: Configuring Outbound Ipv6 Mbgp Route Filtering
To do… Use the command… Remarks Enter BGP view bgp as-number — Enter IPv6 MBGP address family ipv6-family multicast — view peer { ipv6-group-name | ipv6- Required Advertise a default route to an address } default-route-advertise [ IPv6 MBGP peer or peer group Not advertised by default route-policy route-policy-name ] NOTE:...
Page 423: Configuring Inbound Ipv6 Mbgp Route Filtering
Configuring inbound IPv6 MBGP route filtering Follow these steps to configure IPv6 MBGP inbound route filtering: To do… Use the command… Remarks Enter system view system-view — Enter BGP view bgp as-number — Enter IPv6 MBGP address family ipv6-family multicast —...
Page 424: Configuring Ipv6 Mbgp Route Attributes
To do… Use the command… Remarks 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. IPv6 MBGP route attributes involve the following: IPv6 MBGP protocol preference •...
Page 425: Configuring The Med Attribute
To do… Use the command… Remarks Enter IPv6 MBGP address family ipv6-family multicast — view Optional Set the default local preference default local-preference value By default, the default local preference is 100. Configuring the MED attribute Follow these steps to configure the MED attribute: To do…...
Page 426: Configuring The As_Path Attribute
To do… Use the command… Remarks Optional By default, IPv6 MBGP specifies Configure the router as the next peer { ipv6-group-name | ipv6- the local router as the next hop for hop of routes sent to the address } next-hop-local routes sent to an eBGP peer/peer peer/peer group group, but not for routes sent to...
Page 427: Enabling The Ipv6 Mbgp Orf Capability
The current IPv6 MBGP implementation supports the route-refresh feature that enables dynamic route refresh without terminating IPv6 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 will update the IPv6 MBGP routing table and apply the new policy.
Page 428 policies if any, to filter updates to the BGP speaker, thus reducing update messages and saving network resources. After you enable the BGP ORF capability, the local BGP router negotiates the ORF capability with the BGP peer through open messages. That is, the router determines whether to carry ORF information in messages, and if yes, whether to carry nonstandard ORF information in the packets.
Page 429: Configuring The Maximum Number Of Equal-Cost Routes For Load-Balancing
Configuring the maximum number of equal-cost routes for load- balancing Follow these steps to configure the maximum number of equal-cost routes for load-balancing: To do… Use the command… Remarks Enter system view system-view — Enter BGP view bgp as-number — Enter IPv6 MBGP address family ipv6-family multicast —...
Page 430: Configuring Ipv6 Mbgp Community
CAUTION: To create an IPv6 MBGP peer group, you need to enable an existing IPv6 unicast peer group in IPv6 MBGP address family view. Before adding an IPv6 MBGP peer to the IPv6 MBGP peer group, you need to add the corresponding IPv6 BGP unicast peer to the corresponding IPv6 BGP unicast peer group.
Page 431: Displaying And Maintaining Ipv6 Mbgp
To do… Use the command… Remarks Enter system view system-view — Enter BGP view bgp as-number — Enter IPv6 MBGP address family ipv6-family multicast — view Configure the router as a route Required peer { ipv6-group-name | ipv6- reflector and specify an IPv6 MBGP peer/peer group as its address } reflect-client Not configured by default...
Page 432: Resetting Ipv6 Mbgp Connections
To do… Use the command… Remarks Display IPv6 MBGP routing display bgp ipv6 multicast routing-table as-path-acl as- Available in information matching an AS path path-acl-number [ | { begin | exclude | include } any view regular-expression ] display bgp ipv6 multicast routing-table community [ Display IPv6 MBGP routing aa:nn<1-13>...
Page 433: Clearing Ipv6 Mbgp Information
To do… Use the command… Remarks reset bgp ipv6 multicast { as- Reset specified IPv6 MBGP number | ipv6-address | all | Available in user view connections group ipv6-group-name | external | internal } Clearing IPv6 MBGP information To do… Use the command…...
Page 434 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 Configure IPv6 addresses for interfaces as shown in Figure 104 (details not shown). Configure OSPFv3 (details not shown). Enable IPv6 multicast routing, IPv6 PIM-SM and MLD, and configure an IPv6 PIM-SM domain border.
Page 435 [SwitchA-pim6] c-bsr 1001::1 [SwitchA-pim6] c-rp 1001::1 [SwitchA-pim6] quit # Configure the position of C-BSR and C-RP on Switch B. [SwitchB] pim ipv6 [SwitchB-pim6] c-bsr 1001::2 [SwitchB-pim6] c-rp 1001::2 [SwitchB-pim6] quit Configure BGP, specify the IPv6 MBGP peer and enable direct route redistribution. # On Switch A, configure the IPv6 MBGP peer and enable direct route redistribution.
Page 436: Support And Other Resources
Related information Documents To find related documents, browse to the Manuals page of the HP Business Support Center website: http://www.hp.com/support/manuals For related documentation, navigate to the Networking section, and select a networking category. •...
Page 437: Command Conventions
Conventions This section describes the conventions used in this documentation set. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown. Italic Italic text represents arguments that you replace with actual values. Square brackets enclose syntax choices (keywords or arguments) that are optional. Braces enclose a set of required syntax choices separated by vertical bars, from which { x | y | ...
Page 438 Network topology icons Represents a generic network device, such as a router, switch, or firewall. Represents a routing-capable device, such as a router or Layer 3 switch. Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features.
Page 439 Index A B C D E F G H I L M N P R S T Configuration prerequisites,199 Configuration prerequisites,369 Abnormal termination of IPv6 multicast data,298 Configuration prerequisites,367 Administrative scoping overview,123 Configuration prerequisites,22 Advantages and applications of multicast,4 Configuration prerequisites,128 Advertising a default route to a peer or peer Configuration...
Page 440 Configured multicast group policy fails to take Configuring fast-leave processing,250 effect,53 Configuring IGMP fast-leave processing,98 Configuring 802.1p precedence for IGMP Configuring IGMP message options,95 messages,34 Configuring IGMP queries and responses,27 Configuring 802.1p precedence for MLD Configuring IGMP query and response parameters,96 messages,259 Configuring IGMP report...
Page 441 Configuring multicast forwarding on a downstream Configuring the maximum number of MBGP routes for interface,100 load balancing,231 Configuring multicast group replacement,33 Configuring the maximum number of multicast groups that a port can join,32 Configuring multicast source port filtering,31 Configuring the maximum number of multicast groups Configuring multicast source registration,141 that a port can...
Page 442 Enabling IPv6 PIM-SM,348 Inconsistent memberships on routers on the same subnet,326 Enabling MLD,309 Inconsistent memberships on routers on the same Enabling MLD proxying,316 subnet,110 Enabling MLD snooping,246 Injecting a local IPv6 MBGP route,408 Enabling MLD snooping proxying,254 Inter-AS multicast configuration leveraging BGP Enabling MLD snooping querier,252 routes,202...
Page 443 MLD snooping proxying,244 PIM-SSM overview,125 MLD snooping proxying configuration example,269 Port-based multicast VLAN configuration,63 MLD snooping querier configuration example,268 Port-based multicast VLAN configuration example,288 MLD SSM mapping,306 Principle of IGMP snooping,14 MLD SSM mapping configuration example,321 Processing of IPv6 multicast protocol messages,278 versions,300 Processing of multicast protocol...

This manual is also suitable for:

A5500 ei switch series

HP A5500 SI Switch Series Configuration Manual

Multicast Overview

IGMP Snooping Configuration

Appendix (Available Only on the A5500 EI)

Multicast VLAN Configuration

Multicast Routing and Forwarding Configuration (Available Only on the A5500 EI)

IGMP Configuration (Available Only on the A5500 EI)

PIM Configuration (Available Only on the A5500 EI)

MSDP Configuration (Available Only on the A5500 EI)

MBGP Configuration (Available Only on the A5500 EI)

MLD Snooping Configuration

Appendix (Available Only on the A5500 EI)

Quick Links

Configuration Guide

Troubleshooting

Related Manuals for HP A5500 SI Switch Series

Summary of Contents for HP A5500 SI Switch Series