HP 6600/HSR6600 Routers IP Multicast Configuration Guide Part number: 5998-1497 Software version: A6602-CMW520-R3103 A6600-CMW520-R3102-RPE A6600-CMW520-R3102-RSE HSR6602_MCP-CMW520-R3102 Document version: 6PW103-20130628
Legal and notice information © Copyright 2013 Hewlett-Packard Development Company, L.P. No part of this documentation may be reproduced or transmitted in any form or by any means without prior written consent of Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Contents Multicast overview ······················································································································································· 1 Overview············································································································································································ 1 Multicast overview ································································································································
Setting the maximum number of multicast groups that a port can join ··························································· 30 Enabling multicast group replacement ················································································································ 30 Setting the 802.
Configuring an interface as a static member interface ····················································································· 73 Configuring a multicast group filter ····················································································································· 74 Setting the maximum number of multicast groups that an interface can join ················································· 74 Adjusting IGMP performance ·························································
Enabling PIM-SM ················································································································································· 122 Enabling BIDIR-PIM ·············································································································································· 123 Configuring an RP ··············································································································································· 124 Configuring a
Displaying and maintaining MSDP ···························································································································· 178 MSDP configuration examples···································································································································· 178 PIM-SM Inter-domain multicast configuration ··································································································· 178 Inter-AS multicast configuration by lev
Multicast across VPNs········································································································································· 222 Protocols and standards ····································································································································· 224 How MD-VPN works ···················································································································································· 224 Share-MDT establi
MLD SSM mapping ············································································································································· 285 MLD proxying ······················································································································································ 286 Protocols and standards ····································································································································· 286 MLD configuration ta
Configuring a BSR ··············································································································································· 330 Configuring IPv6 administrative scoping ·········································································································· 333 Configuring IPv6 multicast source registration ································································································· 334 Configuring switchover to SPT ················
Configuration prerequisites ································································································································ 388 Configuring IPv6 MBGP route preferences······································································································· 388 Configuring the default local preference ·········································································································· 388 Configuring the MED attribute ······················
Multicast overview Overview As a technique that coexists with unicast and broadcast, the multicast technique effectively addresses the issue of point-to-multipoint data transmission. By enabling high-efficiency point-to-multipoint data transmission over a network, multicast greatly saves network bandwidth and reduces network load.
a separate copy of the same information to each of these hosts. Sending many copies can place a tremendous pressure on the information source and the network bandwidth. Unicast is not suitable for batch transmission of information. Broadcast In broadcast transmission, the information source sends information to all hosts on the subnet, even if some hosts do not need the information. Figure 2 Broadcast transmission In Figure 2, assume that only Host B, Host D, and Host E need the information.
Figure 3 Multicast transmission As shown in Figure 3, the multicast source sends only one copy of the information to a multicast group. Host B, Host D and Host E, which are 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. Finally, the information is correctly delivered to Host B, Host D, and Host E.
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 Comparing TV program transmission and multicast transmission TV program transmission Multicast transmission A TV station transmits a TV program through a channel. A multicast source sends multicast data to a multicast group.
Multicast models Based on how the receivers treat the multicast sources, the multicast models include any-source multicast (ASM), source-filtered multicast (SFM), and source-specific multicast (SSM). • ASM model—In the ASM model, any sender can send information to a multicast group as a multicast source, and receivers can join a multicast group (identified by a group address) and obtain multicast information addressed to that multicast group.
Multicast addresses Network-layer multicast addresses (namely, multicast IP addresses) enables communication between multicast sources and multicast group members. In addition, a technique must be available to map multicast IP addresses to link-layer multicast MAC addresses. The membership of a group is dynamic. Hosts can join or leave multicast groups at any time. IP multicast addresses • IPv4 multicast addresses The IANA assigned the Class D address space (224.0.0.0 to 239.255.255.
Address Description 224.0.0.12 DHCP server/relay agent. 224.0.0.13 All PIM routers. 224.0.0.14 RSVP encapsulation. 224.0.0.15 All CBT routers. 224.0.0.16 SBM. 224.0.0.17 All SBMs. 224.0.0.18 VRRP. IPv6 multicast addresses • Figure 4 IPv6 multicast format The following describes the fields of an IPv6 multicast address, as shown in Figure 4: { { 0xFF—The most significant eight bits are 11111111, which indicates that this address is an IPv6 multicast address.
{ Scope—The Scope field contains four bits, which indicate the scope of the IPv6 internetwork for which the multicast traffic is intended. Table 5 describes the values of the Scope field. Table 5 Values of the Scope field Value Meaning 0, F Reserved. 1 Interface-local scope. 2 Link-local scope. 3 Subnet-local scope. 4 Admin-local scope. 5 Site-local scope. 6, 7, 9 through D Unassigned. 8 Organization-local scope. E Global scope. { Group ID—The Group ID field contains 112 bits.
Figure 7 An example of IPv6-to-MAC address mapping Multicast protocols Generally, Layer 3 multicast refers to IP multicast working at the network layer. The corresponding multicast protocols are Layer 3 multicast protocols, which include IGMP, MLD, PIM, IPv6 PIM, MSDP, MBGP, and IPv6 MBGP. Layer 2 multicast refers to IP multicast working at the data link layer. The corresponding multicast protocols are Layer 2 multicast protocols, including IGMP snooping, PIM snooping, and multicast VLAN.
These protocols define the mechanism of establishing and maintaining group memberships between hosts and Layer 3 multicast devices. • Multicast routing protocols A multicast routing protocol runs on Layer 3 multicast devices to establish and maintain multicast routes and forward multicast packets correctly and efficiently. Multicast routes constitute loop-free data transmission paths (namely, a multicast distribution tree) from a data source to multiple receivers.
PIM snooping runs on Layer 2 devices. It determines which ports are interested in multicast data by analyzing the received PIM messages, and add the ports to a multicast forwarding entry to make sure multicast data can be forwarded to only the ports that are interested in the data.
Figure 10 VPN networking diagram VPN A CE a2 CE b2 CE b3 PE 2 VPN B VPN B CE b1 P CE a1 CE a3 PE 1 Public network PE 3 VPN A VPN A • The provider (P) device belongs to the public network. The customer edge (CE) devices belong to their respective VPNs. Each CE device serves its own VPN and maintains only one set of forwarding mechanisms. • The provider edge (PE) devices connect to the public network and the VPNs.
Configuring IGMP snooping Overview IGMP snooping is a multicast constraining mechanism that runs on Layer 2 devices to manage and control multicast groups. By analyzing received IGMP messages, an IGMP snooping-enabled Layer 2 device establishes mappings between ports and multicast MAC addresses, and forwards multicast data based on these mappings. As shown in Figure 11, without IGMP snooping, a Layer 2 switch floods multicast packets out of all ports but the incoming port.
Figure 12 IGMP snooping related ports As shown in Figure 12, IGMP snooping divides the ports on the router into the following types: • Router port—Layer 3 multicast device-side port. Layer 3 multicast devices include designated routers and IGMP queriers. In the figure, GigabitEthernet 1/0/1 of Router B and GigabitEthernet 1/0/1 of Router C are router ports. The router registers all its local router ports in its router port list.
NOTE: In IGMP snooping, only dynamic ports age out. Static ports never age out. How IGMP snooping works An IGMP snooping-enabled router performs different actions when it receives different IGMP messages. The ports in this section are dynamic ports. For information about how to configure and remove static ports, see "Configuring static ports." When receiving a general query The IGMP querier periodically sends IGMP general queries to all hosts and routers (224.0.0.
When the router receives an IGMP leave message on a dynamic member port, the router first examines whether a forwarding entry matches the group address in the message, and, if a match is found, whether the forwarding entry for the group contains the dynamic member port. • If no forwarding entry matches the group address, or if the forwarding entry does not contain the port, the router directly discards the IGMP leave message.
As shown in Figure 13, Router B operates as an IGMP snooping proxy. As a host from the perspective of the querier Router A, Router B represents its attached hosts to send membership reports and leave messages to Router A. Table 6 IGMP message processing on an IGMP snooping proxy IGMP message Actions General query When receiving an IGMP general query, the proxy forwards it to all ports except the port that receive the query.
configurations made on a member port of the aggregate group will take effect after the port leaves the aggregate group. Complete these tasks to configure IGMP snooping: Task Configuring basic IGMP snooping functions Configuring IGMP snooping port functions Configuring IGMP snooping querier Configuring IGMP snooping proxying Configuring IGMP snooping policies Remarks Enabling IGMP snooping Required. Specifying the IGMP snooping version Optional.
Enabling IGMP snooping When you enable IGMP snooping, follow these guidelines: • Enable IGMP snooping globally before you enable it for a VLAN. • If you enable IGMP snooping for a VLAN, do not enable IGMP or PIM on the corresponding VLAN interface, or vice versa. • IGMP snooping for a VLAN works on only the ports within that VLAN. To enable IGMP snooping: Step Command Remarks 1. Enter system view. system-view N/A 2. Enable IGMP snooping globally and enter IGMP-snooping view.
Setting the maximum number of IGMP snooping forwarding entries You can modify the maximum number of entries in the IGMP snooping forwarding table. When the number of forwarding entries on the router reaches the upper limit, the router does not creates any more forwarding entries until some entries time out or are removed. If the number of existing IGMP snooping forwarding entries is larger than the upper limit that you set, the router gives a prompt asking you to manually remove the excessive entries.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IGMP-snooping view. igmp-snooping N/A 3. Set the aging timer for the dynamic router ports. router-aging-time interval 105 seconds by default. 4. Set the aging timer for the dynamic member ports. host-aging-time interval 260 seconds by default. Setting aging timers for the dynamic ports in a VLAN Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VLAN view . vlan vlan-id N/A 3.
Step Command Remarks 3. Configure the port as a static member port. igmp-snooping static-group group-address [ source-ip source-address ] vlan vlan-id No static member ports exist by default. 4. Configure the port as a static router port. igmp-snooping static-router-port vlan vlan-id No static router ports exist by default. Configuring a port as a simulated member host Generally, a host that runs IGMP can respond to IGMP queries.
processing if you have enabled dropping unknown multicast data globally or for the port. Otherwise, if a host on the port leaves a multicast group, the other hosts attached to the port in the same multicast group cannot receive the multicast data for the group. Enabling IGMP snooping fast-leave processing globally Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IGMP-snooping view. igmp-snooping N/A 3. Enable IGMP snooping fast-leave processing.
Step Command Remarks • Enter Layer 2 Ethernet interface Enter Ethernet interface view or Layer 2 aggregate interface view, or enter port group view. 2. view or Layer 2 aggregate interface view: interface interface-type interface-number Use either command. • Enter port group view: port-group manual port-group-name Disable the port from becoming a dynamic router port. 3. igmp-snooping router-port-deny [ vlan vlan-list ] By default, a port can become a dynamic router port.
Step Command Remarks 2. Enter VLAN view. vlan vlan-id N/A 3. Enable IGMP snooping querier. igmp-snooping querier Disabled by default. Configuring parameters for IGMP queries and responses You can modify the IGMP general query interval based on actual condition of the network. A multicast listening host starts a timer for each multicast group that it has joined when it receives an IGMP query (general query or group-specific query).
Step Set the IGMP last-member query interval. 5. Command Remarks igmp-snooping last-member-query-interval interval 1 second by default. Configuring source IP addresses for IGMP queries After a router receives an IGMP query whose source IP address is 0.0.0.0 on a port, it does not enlist that port as a dynamic router port. This might prevent multicast forwarding entries from being correctly created at the data link layer and eventually cause multicast traffic forwarding to fail.
Step Command Remarks 2. Enter VLAN view. vlan vlan-id N/A 3. Enable IGMP snooping proxying in the VLAN. igmp-snooping proxying enable Disabled by default. Configuring the source IP addresses for the IGMP messages sent by the proxy You can set source the IP addresses for the IGMP reports and leave messages that the IGMP snooping proxy sends on behalf of its attached hosts. To configure the source IP addresses for the IGMP messages sent by the proxy in a VLAN: Step Command Remarks 1.
Configuring a multicast group filter globally Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IGMP-snooping view. igmp-snooping N/A 3. Configure a multicast group filter globally. group-policy acl-number [ vlan vlan-list ] By default, no group filter is globally configured. That is, a host can join any valid multicast group. Configuring a multicast group filter on a port Step 1. Enter system view. Command Remarks system-view N/A • Enter Layer 2 Ethernet interface 2.
Step Command Remarks • Enter Layer 2 Ethernet interface Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view, or enter port group view. 2. view or Layer 2 aggregate interface view: interface interface-type interface-number Use either command. • Enter port group view: port-group manual port-group-name Enable multicast source port filtering. 3. igmp-snooping source-deny Disabled by default.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IGMP-snooping view. igmp-snooping N/A 3. Enable IGMP report suppression. report-aggregation Enabled by default. Setting the maximum number of multicast groups that a port can join You can set the maximum number of multicast groups that a port can join to regulate traffic on the port.
If the multicast group replacement feature is enabled, the multicast group that the router or the port newly joins automatically replaces an existing multicast group that has the lowest address. • IMPORTANT: Be sure to configure the maximum number of multicast groups that a port can join to a value other than the default one (see "Setting the maximum number of multicast groups that a port can join") before enabling multicast group replacement.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VLAN view. vlan vlan-id N/A 3. Set the 802.1p precedence for IGMP messages in the VLAN. igmp-snooping dot1p-priority priority-number The default 802.1p precedence for IGMP messages is 0.
Task Command Remarks Remove all the dynamic group entries of a specified IGMP snooping group or all IGMP snooping groups. reset igmp-snooping group { group-address | all } [ vlan vlan-id ] Available in user view. Clear statistics for the IGMP messages learned through IGMP snooping. reset igmp-snooping statistics Available in user view. NOTE: The reset igmp-snooping group command takes effect only in IGMP snooping-enabled VLANs but not in VLANs with IGMP-enabled VLAN interfaces.
Configuration procedure 1. Assign an IP address and subnet mask to each interface according to Figure 14. (Details not shown.) 2. On Router A, enable IP multicast routing, enable PIM-DM on each interface, and enable IGMP on Ethernet 1/1.
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. GE2/0/1 (D) ( 00:01:30 ) IP group(s):the following ip group(s) match to one mac group. IP group address:224.1.1.1 (0.0.0.0, 224.1.1.1): Attribute: Host Port Host port(s):total 2 port.
Figure 15 Network diagram Router C /1 2/0 GE Source Eth1/2 1.1.1.2/24 Router B Eth1/1 10.1.1.1/24 GE2/0/1 1.1.1.1/24 Router A IGMP querier /2 2/0 GE GE 2/0 /3 GE 2/0 /1 GE Router D /5 2/0 Host C Receiver VLAN 100 GE 2/0 /3 Host A Receiver Host B Configuration procedure 1. Assign an IP address and subnet mask to each interface according to Figure 15. (Details not shown.) 2. On Router A, enable IP multicast routing, enable PIM-DM on each interface, and enable IGMP on Ethernet 1/1.
[RouterB] interface gigabitethernet 2/0/3 [RouterB-GigabitEthernet2/0/3] igmp-snooping static-router-port vlan 100 [RouterB-GigabitEthernet2/0/3] quit 4. Configure Router C: # Enable IGMP snooping globally. system-view [RouterC] igmp-snooping [RouterC-igmp-snooping] quit # Create VLAN 100, assign GigabitEthernet 2/0/1 and GigabitEthernet 2/0/2 to this VLAN, and enable IGMP snooping in the VLAN.
GE2/0/1 (D) ( 00:01:30 ) GE2/0/3 (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): Attribute: Host Port Host port(s):total 1 port. GE2/0/2 (D) ( 00:03:23 ) MAC group(s): MAC group address:0100-5e01-0101 Host port(s):total 1 port. GE2/0/2 The output shows that GigabitEthernet 2/0/3 of Router B has become a static router port. # Display detailed IGMP snooping group information in VLAN 100 on Router D.
IGMPv2 runs on all the receivers, and IGMPv2 snooping runs on all the routers. Router A, which is close to the multicast sources, is chosen as the IGMP snooping querier. To prevent flooding of unknown multicast traffic within the VLAN, be sure to configure all the routers to drop unknown multicast data packets. Because the SAP module does not enlist a port that has heard an IGMP query with a source IP address of 0.0.0.
# Enable IGMP snooping globally. system-view [RouterB] igmp-snooping [RouterB-igmp-snooping] quit # Create VLAN 100, and assign GigabitEthernet 2/0/1 through GigabitEthernet 2/0/4 to the VLAN. [RouterB] vlan 100 [RouterB-vlan100] port gigabitethernet 2/0/1 to gigabitethernet 2/0/4 # Enable IGMP snooping and the function of dropping unknown multicast traffic in VLAN 100. [RouterB-vlan100] igmp-snooping enable [RouterB-vlan100] igmp-snooping drop-unknown [RouterB-vlan100] quit 3.
Figure 17 Network diagram Configuration procedure 1. Assign an IP address and subnet mask to each interface according to Figure 17. (Details not shown.) 2. On Router A, enable IP multicast routing, enable PIM-DM on each interface, and enable IGMP on Ethernet 1/1.
After the configuration is completed, Host A and Host B send IGMP join messages for group 224.1.1.1. Receiving the messages, Router B sends a join message for the group out of GigabitEthernet 2/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. For example: # Display information about the IGMP snooping groups on Router B.
Port flags: D-Dynamic port, S-Static port, C-Copy port, P-PIM port Subvlan flags: R-Real VLAN, C-Copy VLAN Vlan(id):100. Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s). Router port(s):total 1 port. GE2/0/1 (D) ( 00:01:23 ) 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. GE2/0/3 (D) MAC group(s): MAC group address:0100-5e01-0101 Host port(s):total 1 port.
Analysis • The ACL rule is incorrectly configured. • The multicast group policy is not correctly applied. • The function of dropping unknown multicast data is not enabled, so unknown multicast data is flooded. 1. Use the display acl command to check the configured ACL rule. Make sure the ACL rule conforms to the multicast group policy to be implemented. 2.
Configuring multicast routing and forwarding Overview In multicast implementations, the following types of tables implement multicast routing and forwarding: • Multicast routing table of a multicast routing protocol—Each multicast routing protocol has its own multicast routing table, such as the PIM routing table. • General multicast routing table—The multicast routing information of different multicast routing protocols forms a general multicast routing table.
considers the path of the packet that the RPF interface receives from the RPF neighbor as the shortest path that leads back to the source. { { 2. The router searches its MBGP routing table by using the IP address of the packet source as the destination address and automatically chooses an optimal MBGP route. The outgoing interface of the route is the RPF interface and the next hop is the RPF neighbor.
that received the packet is the RPF interface, the router forwards the packet out of all outgoing interfaces. Otherwise, it discards the packet. As shown in Figure 18, assume that unicast routes are available in the network, MBGP is not configured, and no static multicast routes have been configured on Router C. Multicast packets travel along the SPT from the multicast source to the receivers. The multicast forwarding table on Router C contains the (S, G) entry, with POS 5/0/1 as the incoming interface.
Figure 19 Changing an RPF route As shown in Figure 19, when no static multicast route is configured, Router C's RPF neighbor on the path back to Source is Router A. The multicast information from Source travels along the path from Router A to Router C, which is the unicast route between the two routers.
Router C and Router D, to specify Router B as the RPF neighbor of Router C and Router C as the RPF neighbor of Router D, the receiver hosts will receive the multicast data from the multicast source. Multicast forwarding across unicast subnets Some networking devices might not support multicast protocols in a network. Multicast devices forward multicast traffic from a multicast source hop by hop along the forwarding tree.
Introduction to multicast traceroute packets A multicast traceroute packet is a special IGMP packet that is different from common IGMP packets in that its IGMP Type field is set to 0x1F or 0x1E and its destination IP address is a unicast address. The following types of multicast traceroute packets are available: • Query—Its IGMP Type field set to 0x1F. • Request—Its IGMP Type field set to 0x1F. • Response—Its IGMP Type field set to 0x1E. Process of multicast traceroute 1.
Step Enable IP multicast routing. 2. Command Remarks multicast routing-enable Disabled by default. Enabling IP multicast routing in a VPN instance Step Command Remarks system-view N/A 1. Enter system view. 2. Create a VPN instance and enter VPN instance view. 3. Configure a route distinguisher (RD) for the VPN instance. route-distinguisher route-distinguisher For more information about this command, see MPLS Command Reference. 4. Enable IP multicast routing.
Step Command Remarks No static multicast route configured by default. 2. Configure a static multicast route. ip rpf-route-static [ vpn-instance vpn-instance-name ] source-address { mask | mask-length } [ protocol [ process-id ] ] [ route-policy policy-name ] { rpf-nbr-address | interface-type interface-number } [ preference preference ] [ order order-number ] 3. Delete static multicast routes.
Configuring a multicast forwarding range Multicast packets do not travel without a boundary in a network. The multicast data of each multicast group must be transmitted within a definite scope. You can configure a forwarding boundary specific to a 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.
Step 2. 3. Command Remarks Configure the maximum number of entries in the multicast forwarding table. multicast forwarding-table route-limit limit Optional. Configure the maximum number of downstream nodes for a single multicast forwarding entry. multicast forwarding-table downstream-limit limit Optional. The default value is 4096. The default value is 128. Configuring the multicast forwarding table size in a VPN instance Step Command Remarks 1. Enter system view. system-view N/A 2.
Configuring a static multicast MAC address entry in interface view Step 1. Enter system view. Command Remarks system-view N/A • Enter Ethernet interface/Layer 2. Enter Ethernet interface/Layer 2 aggregate interface view or port group view. 2 aggregate interface view: interface interface-type interface-number • Enter port group view: port-group manual port-group-name 3. Configure a static multicast MAC address entry.
Task Command Remarks Display multicast forwarding table information.
Task Command Remarks Available in user view. reset multicast [ all-instance | vpn-instance vpn-instance-name ] routing-table { { source-address [ mask { mask | mask-length } ] | group-address [ mask { mask | mask-length } ] | incoming-interface { interface-type interface-number | register } } * | all } Clear routing entries from the multicast routing table.
2. Enable OSPF on the routers in the PIM-DM domain to make sure they are interoperable at the network layer and they can dynamically update their routing information. (Details not shown.) 3. Enable IP multicast routing, and enable PIM-DM and IGMP: # Enable IP multicast routing on Router B, enable PIM-DM on each interface, and enable IGMP on GigabitEthernet 2/0/1.
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 route on Router B has changed. It is now the configured static multicast route, and the RPF neighbor is now Router C. Creating an RPF route Network requirements PIM-DM runs in the network and all routers in the network support IP multicast. Router B and Router C run OSPF, and have no unicast routes to Router A.
[RouterC-GigabitEthernet2/0/2] pim dm [RouterC-GigabitEthernet2/0/2] quit # Enable IP multicast routing on Router A and enable PIM-DM on each interface. system-view [RouterA] multicast routing-enable [RouterA] interface gigabitethernet 2/0/1 [RouterA-GigabitEthernet2/0/1] pim dm [RouterA-GigabitEthernet2/0/1] quit [RouterA] interface gigabitethernet 2/0/2 [RouterA-GigabitEthernet2/0/2] pim dm [RouterA-GigabitEthernet2/0/2] quit # Configure Router B in the same way as you configure Router A.
Multicast forwarding over GRE tunnels Network requirements Multicast routing and PIM-DM are enabled on Router A and Router C. Router B does not support multicast. OSPF is running on Router A, Router B, and Router C. Configure a GRE tunnel so that Receiver can receive the multicast data from Source. Figure 24 Network diagram Configuration procedure 1. Assign an IP address and mask to each interface according to Figure 24. (Details not shown.) 2.
[RouterA-ospf-1] area 0 [RouterA-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [RouterA-ospf-1-area-0.0.0.0] network 20.1.1.0 0.0.0.255 [RouterA-ospf-1-area-0.0.0.0] network 50.1.1.0 0.0.0.255 [RouterA-ospf-1-area-0.0.0.0] quit [RouterA-ospf-1] quit # Configure OSPF on Router B. system-view [RouterB] ospf 1 [RouterB-ospf-1] area 0 [RouterB-ospf-1-area-0.0.0.0] network 20.1.1.0 0.0.0.255 [RouterB-ospf-1-area-0.0.0.0] network 30.1.1.0 0.0.0.255 [RouterB-ospf-1-area-0.0.0.
5. On Router C, configure a static multicast route and specify its RPF neighbor leading toward Source is Tunnel 0 on Router A. [RouterC] ip rpf-route-static 10.1.1.0 24 50.1.1.1 6. Verify the configuration: Source sends multicast data to the multicast group 225.1.1.1 and Receiver can receive the multicast data after joining the multicast group. You can display PIM routing table information on the routers using the display pim routing-table command.
Analysis • If the static multicast route is not configured or updated correctly to match the current network conditions, the route entry and the configuration information of static multicast route do not exist in the multicast routing table. • If a better route is found, the static multicast route might also fail. 1.
Configuring IGMP Overview As a TCP/IP protocol responsible for IP multicast group member management, the IGMP is used by IP hosts and adjacent multicast routers to establish and maintain their multicast group memberships. IGMP versions • IGMPv1 (documented in RFC 1112) • IGMPv2 (documented in RFC 2236) • IGMPv3 (documented in RFC 3376) All IGMP versions support the ASM model. In addition to the ASM model, IGMPv3 can directly implement the SSM model.
Figure 25 IGMP queries and reports 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 25. The following process describes how the hosts join the multicast groups and how the IGMP querier (Router B in the figure) maintains the multicast group memberships: 1.
IGMPv2 overview Compared with IGMPv1, IGMPv2 has introduced a querier election mechanism and a leave-group mechanism. Querier election mechanism In IGMPv1, the DR elected by the Layer 3 multicast routing protocol (such as PIM) serves as the querier among multiple routers on the same subnet. IGMPv2 introduced an independent querier election mechanism. The querier election process is as follows: 1.
• If it expects to reject multicast data from specific sources like S1, S2, …, it sends a report with the Filter-Mode denoted as "Exclude Sources (S1, S2, …)." As shown in Figure 26, the network comprises two multicast sources, Source 1 (S1) and Source 2 (S2), both of which can send multicast data to multicast group G. Host B is interested in the multicast data that Source 1 sends to G but not in the data from Source 2.
{ { { TO_EX—The filtering mode has changed from Include to Exclude. ALLOW—The Source Address fields in this group record contain a list of the additional sources that the system wants to obtain data from, for packets sent to the specified multicast address. If the change was to an Include source list, these sources are the addresses that were added to the list. If the change was to an Exclude source list, these sources are the addresses that were deleted from the list.
• If G is in the SSM group range but no IGMP SSM mappings that correspond to the multicast group G have been configured on Router A, Router A cannot provide SSM service and drops the message. • If G is in the SSM group range and the IGMP SSM mappings have been configured on Router A for multicast group G, Router A translates the (*, G) information in the IGMP report into (G, INCLUDE, (S1, S2...)) information based on the configured IGMP SSM mappings and provides SSM service accordingly.
mode, and source list. Such an entry is a collection of members in the same multicast group on each downstream interface. A proxy device performs host functions on the upstream interface based on the database. It responds to queries according to the information in the database or sends join/leave messages when the database changes.
Task Remarks Configuring IGMP SSM mapping Configuring IGMP proxying Enabling SSM mapping Optional. Configuring SSM mappings Optional. Enabling IGMP proxying Optional. Configuring multicast forwarding on a downstream interface Optional. Configuring basic IGMP functions This section describes how to configure basic IGMP functions.
Step Command Remarks 3. Configure an RD for the VPN instance. route-distinguisher route-distinguisher No RD is configured by default. 4. Enable IP multicast routing. multicast routing-enable Disabled by default. 5. Enter interface view. interface interface-type interface-number N/A 6. Bind the interface with the VPN instance. ip binding vpn-instance vpn-instance-name By default, an interface belongs to the public network, and is not bound with any VPN instance. 7. Enable IGMP.
PIM-SM enabled, it must be an IGMP querier. For more information about PIM-SM and a DR, see "Configuring PIM." A static member interface does not respond to queries that the IGMP querier sends. When you configure an interface as a static member or cancel this configuration on the interface, the interface does not unsolicitedly send any IGMP report or IGMP leave message. In other words, the interface is not a real member of the multicast group or the multicast source and group.
Step Command Remarks The default value is 16384. 3. Configure the maximum number of multicast groups that the interface can join. igmp group-limit limit The maximum number of multicast groups that a VLAN interface can join is 1000. If more than 1000 multicast groups are configured, only 1000 multicast groups takes effect. Adjusting IGMP performance When you adjust IGMP performance, follow these guidelines: • The configurations made in IGMP view are effective on all interfaces.
Configuring Router-Alert option handling methods globally Step Command Remarks 1. Enter system view. system-view N/A 2. Enter public network IGMP view or VPN instance IGMP view. igmp [ vpn-instance vpn-instance-name ] N/A Configure the router to discard any IGMP message that does not carry the Router-Alert option. require-router-alert By default, the device does not check the Router-Alert option. Enable insertion of the Router-Alert option into IGMP messages.
To speed up the response of hosts to IGMP queries and avoid simultaneous timer expirations causing IGMP report traffic bursts, you must correctly set the maximum response time. • For IGMP general queries, the maximum response time is set by the max-response-time command. • For IGMP group-specific queries and IGMP group-and-source-specific queries, the maximum response time equals the IGMP last-member query interval.
Step 9. Configure the other querier present interval. Command Remarks timer other-querier-present interval By default, the other querier present interval is [ IGMP general query interval ] × [ IGMP robustness variable ] + [ maximum response time for IGMP general queries ] / 2. Configuring IGMP query and response parameters on an interface Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 2 by default.
or IGMP group-and-source-specific queries. Thus, the leave latency is reduced on one hand, and the network bandwidth is saved on the other hand. The IGMP fast-leave processing configuration is effective only if the device is running IGMPv2 or IGMPv3. Enabling IGMP fast-leave processing globally Step Command Remarks 1. Enter system view. system-view N/A 2. Enter public network IGMP view or VPN instance IGMP view. igmp [ vpn-instance vpn-instance-name ] N/A Enable IGMP fast-leave processing.
Step Enable the IGMP host tracking function on the interface. 3. Command Remarks igmp host-tracking Disabled by default. Configuring IGMP SSM mapping Because of some possible restrictions, some receiver hosts on an SSM network might run IGMPv1 or IGMPv2. To provide SSM service support for these receiver hosts, configure the IGMP mapping feature on the last-hop router.
Step 2. 3. Command Remarks Enter public network IGMP view or VPN instance IGMP view. igmp [ vpn-instance vpn-instance-name ] N/A Configure an IGMP SSM mapping. ssm-mapping group-address { mask | mask-length } source-address No IGMP mappings are configured by default. Configuring IGMP proxying This section describes how to configure IGMP proxying.
Configuring multicast forwarding on a downstream interface Typically, to avoid duplicate multicast flows, only queriers can forward multicast traffic. On IGMP proxy devices, a downstream interface must be a querier in order to forward multicast traffic to downstream hosts. If the interface has failed in the querier election, you must manually enable multicast forwarding on this interface.
Task Command Remarks Display IGMP configuration and operation information. display igmp [ all-instance | vpn-instance vpn-instance-name ] interface [ interface-type interface-number ] [ verbose ] [ | { begin | exclude | include } regular-expression ] Available in any view. Display the information of IGMP proxying groups.
Task Command Remarks Clear IGMP SSM mappings. reset igmp [ all-instance | vpn-instance vpn-instance-name ] ssm-mapping group { all | interface interface-type interface-number { all | group-address [ mask { mask | mask-length } ] [ source-address [ mask { mask | mask-length } ] ] } } Available in user view. IGMP configuration examples This section provides examples of configuring IGMP.
Configuration procedure 1. Assign an IP address and subnet mask to each interface according to Figure 29. (Details not shown.) 2. Configure OSPF on the routers on the PIM network to make sure they are interoperable at the network layer and they can dynamically update their routing information. (Details not shown.) 3. Enable IP multicast routing, and enable PIM-DM and IGMP: # Enable IP multicast routing on Router A, enable PIM-DM on each interface, and enable IGMP on GigabitEthernet 2/0/1.
5. Verify the configuration: Use the display igmp interface command to view the IGMP configuration and operation status on each router interface. For example: # Display IGMP information on GigabitEthernet 2/0/1 of Router B. [RouterB] display igmp interface gigabitethernet 2/0/1 GigabitEthernet2/0/1(10.110.2.
GE2/1/2 192.168.1.2/24 GE2/1/2 192.168.3.2/24 GE2/1/3 192.168.2.1/24 GE2/1/3 192.168.4.1/24 Configuration procedure 1. Assign an IP address and subnet mask to each interface according to Figure 30. (Details not shown.) 2. Configure OSPF on the routers in the PIM-SM domain to make sure they are interoperable at the network layer and they can dynamically update their routing information. (Details not shown.) 3.
[RouterD] acl number 2000 [RouterD-acl-basic-2000] rule permit source 232.1.1.0 0.0.0.255 [RouterD-acl-basic-2000] quit [RouterD] pim [RouterD-pim] ssm-policy 2000 [RouterD-pim] quit # Configure Router A, Router B, and Router C in the same way as you configure Router D. (Details not shown.) 6. Configure IGMP SSM mappings on Router D. [RouterD] igmp [RouterD-igmp] ssm-mapping 232.1.1.0 24 133.133.1.1 [RouterD-igmp] ssm-mapping 232.1.1.0 24 133.133.3.1 [RouterD-igmp] quit 7.
UpTime: 00:13:25 Upstream interface: GigabitEthernet2/1/2 Upstream neighbor: 192.168.3.1 RPF prime neighbor: 192.168.3.1 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet2/1/1 Protocol: igmp, UpTime: 00:13:25, Expires: - IGMP proxying configuration example Network requirements PIM-DM runs on the core network. Host A and Host C in the stub network receive VOD information sent to multicast group 224.1.1.1.
# Enable IP multicast routing on Router B, IGMP proxying on GigabitEthernet 2/1/1, and IGMP on GigabitEthernet 2/1/2. system-view [RouterB] multicast routing-enable [RouterB] interface gigabitethernet 2/1/1 [RouterB-GigabitEthernet2/1/1] igmp proxying enable [RouterB-GigabitEthernet2/1/1] quit [RouterB] interface gigabitethernet 2/1/2 [RouterB-GigabitEthernet2/1/2] igmp enable [RouterB-GigabitEthernet2/1/2] quit 3.
• If the IGMP version on the router interface is lower than that on the host, the router will not be able to recognize the IGMP report from the host. • If you have configured the igmp group-policy command on the interface, the interface cannot receive report messages that fail to pass filtering. 1. Use the display interface command to verify that the networking, interface connection, and IP address configuration are correct.
Configuring PIM Overview PIM provides IP multicast forwarding by leveraging unicast static routes or unicast routing tables generated by any unicast routing protocol, such as RIP, OSPF, IS-IS, or BGP. Independent of the unicast routing protocols running on the device, multicast routing can be implemented as long as the corresponding multicast routing entries are created through unicast routes. PIM uses the RPF mechanism to implement multicast forwarding.
Neighbor discovery In a PIM domain, a PIM router discovers PIM neighbors and maintains PIM neighboring relationship with other routers. It also builds and maintains SPTs by periodically multicasting hello messages to all other PIM routers (224.0.0.13) on the local subnet. Every PIM-enabled interface on a router sends hello messages periodically, and thus learns the PIM neighboring information pertinent to the interface. SPT building The process of building an SPT is the flood-and-prune process. 1.
The flood-and-prune process takes place periodically. A pruned state timeout mechanism is provided. A pruned branch restarts multicast forwarding when the pruned state times out and then is pruned again when it no longer has any multicast receiver. NOTE: Pruning has a similar implementation in PIM-SM. Graft When a host attached to a pruned node joins a multicast group, to reduce the join latency, PIM-DM uses a graft mechanism to resume data forwarding to that branch. The process is as follows: 1.
3. The routers compare these parameters, and either Router A or Router B becomes the unique forwarder of the subsequent (S, G) packets on the shared-media subnet. The comparison process is as follows: a. The router with a higher preference to the source wins. b. If both routers have the same preference to the source, the router with a smaller metric to the source wins. c. If a tie exists in route metric to the source, the router with a higher IP address on the downstream interface wins.
Neighbor discovery PIM-SM uses a similar neighbor discovery mechanism as PIM-DM does. For more information, see "Neighbor discovery." DR election PIM-SM also uses hello messages to elect a DR for a shared-media network (such as Ethernet). The elected DR will be the only multicast forwarder on this shared-media network. A DR must be elected in a shared-media network, no matter this network connects to multicast sources or to receivers. The receiver-side DR sends join messages to the RP.
each router in the PIM-SM domain. An RP can serve multiple multicast groups or all multicast groups, but a given multicast group can have only one RP to serve it at a time. In most cases, however, a PIM-SM network covers a wide area, and a huge amount of multicast traffic must be forwarded through the RP. To lessen the RP burden and optimize the topological structure of the RPT, you can configure multiple C-RPs in a PIM-SM domain, among which an RP is dynamically elected through the bootstrap mechanism.
Value Description M Hash mask length. Ci IP address of the C-RP. & Logical operator of "and." XOR Logical operator of "exclusive-or." Mod Modulo operator, which gives the remainder of an integer division. RPT building Figure 36 RPT building in a PIM-SM domain Host A Source RP DR Server Receiver Host B DR Receiver RPT Join message Multicast packets Host C As shown in Figure 36, the process of building an RPT is as follows: 1.
Figure 37 Multicast source registration As shown in Figure 37, the multicast source registers with the RP as follows: 1. The multicast source S sends the first multicast packet to multicast group G. 2. After receiving the multicast packet, the DR that directly connects to the multicast source encapsulates the packet in a PIM register message, and then sends the message to the corresponding RP by unicast. 3. When the RP receives the register message, it does the following: a.
receiver-side DRs. The RP acts as a transfer station for all multicast packets. The whole process involves the following issues: • The source-side DR and the RP need to implement complicated encapsulation and de-encapsulation of multicast packets. • Multicast packets are delivered along a path that might not be the shortest one. • An increase in multicast traffic adds a great burden on the RP, increasing the risk of failure.
• DF election • Bidirectional RPT building Neighbor discovery BIDIR-PIM uses the same neighbor discovery mechanism as PIM-SM does. For more information, see "Neighbor discovery." RP discovery BIDIR-PIM uses the same RP discovery mechanism as PIM-SM does. For more information, see "RP discovery." 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).
2. The router with a route of the highest priority becomes the DF. 3. In the case of a tie, the router with the route with the lowest metric wins the DF election. 4. In the case of a tie in the metric, the router with the highest IP address wins. Bidirectional RPT building A bidirectional RPT comprises a receiver-side RPT and a source-side RPT. The receiver-side RPT is rooted at the RP and takes the routers directly connected to the receivers as leaves.
Figure 40 RPT building at the multicast source side As shown in Figure 40, the process for building a source-side RPT is relatively simple: 4. When a multicast source sends multicast packets to multicast group G, the DF in each network segment unconditionally forwards the packets to the RP. 5. The routers along the path from the source's directly connected router to the RP form an RPT branch. Each router on this branch adds a (*, G) entry to its forwarding table. The * means any multicast source.
ranges that different admin-scope zones serve can be overlapped. A multicast group is valid only within its local admin-scope zone, and functions as a private group address. The global scope zone maintains a BSR, which serves the multicast groups that do not belong to any admin-scope zone. Relationship between admin-scope zones and the global scope zone The global-scoped zone and each admin-scoped zone have their own C-RPs and BSRs.
Figure 42 Relationship in view of multicast group address ranges Admin-scope 1 Admin-scope 3 G1 address G3 address Admin-scope 2 Global-scope G−G1−G2 address G2 address As shown in Figure 42, the admin-scoped zones 1 and 2 have no intersection, but the admin-scoped zone 3 is a subset of the admin-scoped zone 1. The global-scoped zone serves all the multicast groups that are not covered by the admin-scoped zones 1 and 2, that is, G−G1−G2 in this case.
Figure 43 SPT building in PIM-SSM Host A Source RP DR Server Receiver Host B DR Receiver SPT Subscribe message Multicast packets Host C As shown in Figure 43, 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.
Figure 44 Relationship among PIM protocols A receiver joins multicast group G. G is in the SSM group range? Yes A multicast source is specified? No No No BIDIR-PIM is enabled? No An IGMP-SSM mapping is configured for G? Yes PIM-SM runs for G. No G has a BIDIR-PIM RP? Yes Yes PIM-SSM runs for G. Yes BIDIR-PIM runs for G.
Task Remarks Enabling PIM-DM Required. Enabling state-refresh capability Optional. Configuring state-refresh parameters Optional. Configuring PIM-DM graft retry period Optional. Configuring common PIM 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 network layer. • Determine the interval between state-refresh messages.
Step Command Description N/A 2. Create a VPN instance and enter VPN instance view. ip vpn-instance vpn-instance-name 3. Configure an RD for the VPN instance. route-distinguisher route-distinguisher For more information about this command, see MPLS Command Reference. 4. Enable IP multicast routing. multicast routing-enable Disabled by default. 5. Enter interface view. interface interface-type interface-number N/A For more information about this command, see MPLS Command Reference.
The TTL value of a state-refresh message decrements by 1 whenever it passes a router before it is forwarded to the downstream node until the TTL value comes down to 0. In a small network, a state-refresh message might cycle in the network. To effectively control the propagation scope of state-refresh messages, configure an appropriate TTL value based on the network size. Perform the following configurations on all routers in the PIM domain. To configure state-refresh parameters: Step Command Remarks 1.
Task Remarks Enabling PIM-SM Required. Configuring an RP Configuring a BSR Configuring administrative scoping Configuring a static RP Required. Configuring a C-RP Use any method. Enabling auto-RP Configuring C-RP timers globally Optional. Configuring a C-BSR Required. Configuring a PIM domain border Optional. Configuring global C-BSR parameters Optional. Configuring C-BSR timers Optional. Disabling BSM semantic fragmentation Optional. Enabling administrative scoping Optional.
• Determine the multicast traffic rate threshold, ACL rule, and sequencing rule for a switchover to SPT. • Determine the interval of checking the traffic rate threshold before a switchover to SPT. Enabling PIM-SM With PIM-SM enabled, a router sends hello messages periodically to discover PIM neighbors and processes messages from the PIM neighbors. To deploy a PIM-SM domain, enable PIM-SM on all non-border interfaces of the routers.
Configuring an RP An RP can be manually configured or dynamically elected through the BSR mechanism. For a large PIM network, static RP configuration is a tedious job. Generally, static RP configuration is just a backup method for the dynamic RP election mechanism to enhance the robustness and operational manageability of a multicast network. When both PIM-SM and BIDIR-PIM run on the PIM network, do not use the same RP to serve PIM-SM and BIDIR-PIM.
Step 4. Command Configure a legal C-RP address range and the range of multicast groups to be served. crp-policy acl-number Remarks Optional. No restrictions by default. Enabling auto-RP Auto-RP announcement and discovery messages are addressed to the multicast group addresses 224.0.1.39 and 224.0.1.40, respectively. With auto-RP enabled on a device, the device can receive these two types of messages and record the RP information carried in such messages. To enable auto-RP: Step Command Remarks 1.
Configuring a BSR A PIM-SM domain can have only one BSR, but must have at least one C-BSR. Any router can be configured as a C-BSR. Elected from C-BSRs, the BSR is responsible for collecting and advertising RP information in the PIM-SM domain. Configuring a C-BSR C-BSRs should be configured on routers in the backbone network. When configuring a router as a C-BSR, be sure to specify a PIM-SM-enabled interface on the router.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter public network PIM view or VPN instance PIM view. pim [ vpn-instance vpn-instance-name ] N/A 3. Configure an interface as a C-BSR. c-bsr interface-type interface-number [ hash-length [ priority ] ] No C-BSRs are configured by default. 4. Configure a legal BSR address range. bsr-policy acl-number Optional. No restrictions on BSR address range by default.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter public network PIM view or VPN instance PIM view. pim [ vpn-instance vpn-instance-name ] N/A 3. Configure the hash mask length. c-bsr hash-length hash-length Configure the C-BSR priority. c-bsr priority priority 4. Optional. 30 by default. Optional. By default, the C-BSR priority is 64.
Disabling BSM semantic fragmentation Generally, a BSR periodically distributes the RP-set information in bootstrap messages within the PIM-SM domain. It encapsulates a BSM in an IP datagram and might split the datagram into fragments if the message exceeds the MTU. In respect of such IP fragmentation, loss of a single IP fragment leads to unavailability of the entire message. Semantic fragmentation of BSMs can solve this issue. When a BSM exceeds the MTU, it is split to multiple BSMFs.
Step Command Remarks 2. Enter public network PIM view or VPN instance PIM view. pim [ vpn-instance vpn-instance-name ] N/A 3. Enable administrative scoping. c-bsr admin-scope Disabled by default. Configuring an admin-scope zone boundary ZBRs form the boundary of each admin-scope zone. Each admin-scope zone maintains a BSR, which serves a specific multicast group range.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter public network PIM view or VPN instance PIM view. pim [ vpn-instance vpn-instance-name ] N/A No C-BSRs are configured for an admin-scope zone by default. Configure a C-BSR for an admin-scope zone. 3. 2. c-bsr group group-address { mask | mask-length } [ hash-length hash-length | priority priority ] * The group-address { mask | mask-length } argument can specify the multicast groups that the C-BSR serves, in the range of 239.
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. On the 6600/HSR6600 router, only the first register message carries multicast data. To configure register-related parameters: Step Command Remarks 1. Enter system view. system-view N/A 2.
Task Remarks Enabling PIM-SM Required. Enabling BIDIR-PIM Required. Configuring a static RP Configuring an RP Configuring a BSR Configuring administrative scoping Configuring a C-RP Enabling auto-RP Required. Use any method. Configuring C-RP timers globally Optional. Configuring a C-BSR Required. Configuring a BIDIR-PIM domain border Optional. Configuring global C-BSR parameters Optional. Configuring C-BSR timers Optional. Disabling BSM semantic fragmentation Optional.
IMPORTANT: All interfaces on a device must be enabled with the same PIM mode. Enabling PIM-SM globally for the public network Step Command Remarks 1. Enter system view. system-view N/A 2. Enable IP multicast routing. multicast routing-enable Disabled by default. 3. Enter interface view. interface interface-type interface-number N/A 4. Enable PIM-SM. pim sm Disabled by default. Command Remarks system-view N/A Enabling PIM-SM for a VPN instance Step 1. Enter system view. N/A 2.
Step Command Remarks 2. Enter public network PIM view or VPN instance PIM view. pim [ vpn-instance vpn-instance-name ] N/A 3. Enable BIDIR-PIM. bidir-pim enable Disabled by default. Configuring an RP An RP can be manually configured or dynamically elected through the BSR mechanism. For a large PIM network, static RP configuration is a tedious job.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter public network PIM view or VPN instance PIM view. pim [ vpn-instance vpn-instance-name ] N/A Configure an interface to be a C-RP for BIDIR-PIM. c-rp interface-type interface-number [ group-policy acl-number | priority priority | holdtime hold-interval | advertisement-interval adv-interval ] * bidir No C-RP is configured by default. 3.
For more information about the configuration of other timers in BIDIR-PIM, see "Configuring common PIM timers." Configuring a BSR A BIDIR-PIM domain can have only one BSR, but must have at least one C-BSR. Any router can be configured as a C-BSR. Elected from C-BSRs, the BSR collects and advertises RP information in the BIDIR-PIM domain. Configuring a C-BSR C-BSRs must be configured on routers in the backbone network.
Step Command Remarks 2. Enter public network PIM view or VPN instance PIM view. pim [ vpn-instance vpn-instance-name ] N/A 3. Configure an interface as a C-BSR. c-bsr interface-type interface-number [ hash-length [ priority ] ] No C-BSRs are configured by default. 4. Configure a legal BSR address range. Optional. bsr-policy acl-number No restrictions on BSR address range by default.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter public network PIM view or VPN instance PIM view. pim [ vpn-instance vpn-instance-name ] N/A 3. Configure the hash mask length. c-bsr hash-length hash-length Configure the C-BSR priority. c-bsr priority priority 4. Optional. 30 by default. Optional. 64 by default.
Disabling BSM semantic fragmentation Generally, a BSR periodically distributes the RP-set information in bootstrap messages within the BIDIR-PIM domain. It encapsulates a BSM in an IP datagram and might split the datagram into fragments if the message exceeds the MTU. In respect of such IP fragmentation, loss of a single IP fragment leads to unavailability of the entire message. Semantic fragmentation of BSMs can solve this issue. When a BSM exceeds the MTU, it is split to BSMFs.
Step Command Remarks 2. Enter public network PIM view or VPN instance PIM view. pim [ vpn-instance vpn-instance-name ] N/A 3. Enable administrative scoping. c-bsr admin-scope Disabled by default. 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.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter public network PIM view or VPN instance PIM view. pim [ vpn-instance vpn-instance-name ] N/A No C-BSRs are configured for an admin-scope zone by default. Configure a C-BSR for an admin-scope zone. 3. 2. c-bsr group group-address { mask | mask-length } [ hash-length hash-length | priority priority ] * The group-address { mask | mask-length } argument can specify the multicast groups that the C-BSR serves, in the range of 239.
Enabling PIM-SM The implementation of the SSM model is based on some subsets of PIM-SM. Therefore, you must enable PIM-SM before configuring PIM-SSM. When you deploy a PIM-SSM domain, enable PIM-SM on non-border interfaces of the routers. IMPORTANT: All the interfaces on a device must be enabled with the same PIM mode. Enabling PIM-SM globally on the public network Step Command Remarks 1. Enter system view. system-view N/A 2. Enable IP multicast routing.
Configuring the SSM group range Whether the PIM-SSM model or the PIM-SM model delivers the information from a multicast source the receivers depends on whether the group address in the (S, G) packets that the receivers request is in the SSM group range. All PIM-SM-enabled interfaces assume the PIM-SSM model for multicast groups within this address range. Configuration guidelines • Perform the following configuration on all routers in the PIM-SSM domain.
Configuration prerequisites Before you configure common PIM features, complete the following tasks: • Configure any unicast routing protocol so that all devices in the domain are interoperable at the network layer. • Configure PIM-DM, or PIM-SM, or PIM-SSM. • Determine the ACL rule for filtering multicast data. • Determine the ACL rule defining a legal source address range for hello messages. • Determine the priority for DR election (global value/interface level value).
Configuring a hello message filter Along with the wide applications of PIM, the security requirement for the protocol is becoming increasingly demanding. The establishment of correct PIM neighboring relationship is the prerequisite for secure application of PIM. To guard against PIM message attacks, you can configure a legal source address range for hello messages on interfaces of routers to ensure the correct PIM neighboring relationship. To configure a hello message filter: Step Command Remarks 1.
Generation ID—A router generates a generation ID for hello messages when an interface is enabled with PIM. The generation ID is a random value, but only changes when the status of the router changes. If an PIM router finds that the generation ID in a hello message from the upstream router has changed, it assumes that the status of the upstream router has changed. In this case, it sends a join message to the upstream router for status update.
Setting the prune delay timer The prune delay timer on an upstream router on a shared-media network can make the upstream router not perform the prune action immediately after it receives the prune message from its downstream router. Instead, the upstream router maintains the current forwarding state for a period of time that the prune delay timer defines. In this period, if the upstream router receives a join message from the downstream router, it cancels the prune action.
Step 4. 5. 6. 7. Command Configure the join/prune interval. timer join-prune interval Configure the join/prune timeout timer. holdtime join-prune interval Configure assert timeout timer. holdtime assert interval Configure the multicast source lifetime. source-lifetime interval Remarks Optional. 60 seconds by default. Optional. 210 seconds by default. Optional. 180 seconds by default. Optional. 210 seconds by default. Configuring common PIM timers on an interface Step Command Remarks 1.
Step 3. 4. Command Configure the maximum size of each join/prune message. jp-pkt-size packet-size Configure the maximum number of (S, G) entries in each join/prune message. jp-queue-size queue-size Remarks Optional. 8100 bytes by default. Optional. 1020 by default. Configuring PIM to work with BFD PIM uses hello messages to elect a DR for a shared-media network. The elected DR will be the only multicast forwarder on the shared-media network.
Task Command Remarks Display information about unacknowledged PIM-DM graft messages. display pim [ all-instance | vpn-instance vpn-instance-name ] grafts [ | { begin | exclude | include } regular-expression ] Available in any view. Display PIM information on an interface or all interfaces. display pim [ all-instance | vpn-instance vpn-instance-name ] interface [ interface-type interface-number ] [ verbose ] [ | { begin | exclude | include } regular-expression ] Available in any view.
Figure 45 Network diagram Receiver Host A Router A G E2 /1 /3 GE2/1/0 Host B G E2 /1 /3 Receiver GE2/1/0 GE2/1/1 GE2/1/0 Router B 1/ Router D / E2 G Source GE2/1/1 Host C 2 /1 /1 E2 G 10.110.5.100/24 GE2/1/0 PIM-DM Router C Host D Device Interface IP address Device Interface IP address Router A GE2/1/0 10.110.1.1/24 Router D GE2/1/0 10.110.5.1/24 GE2/1/3 192.168.1.1/24 GE2/1/3 192.168.1.2/24 Router B Router C GE2/1/0 10.110.2.1/24 GE2/1/1 192.168.2.
# Enable IP multicast routing, PIM-DM, and IGMP on Router B and Router C in the same way. (Details not shown.) # Enable IP multicast routing on Router D, and enable PIM-DM on each interface.
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: GigabitEthernet2/1/0 Protocol: igmp, UpTime: 00:04:25, Expires: never (10.110.5.100, 225.1.1.1) Protocol: pim-dm, Flag: ACT UpTime: 00:06:14 Upstream interface: GigabitEthernet2/1/3 Upstream neighbor: 192.168.1.2 RPF prime neighbor: 192.168.1.
PIM-SM non-scoped zone configuration example Network requirements As shown in Figure 46, the 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 N1 and N2. Both GigabitEthernet 2/1/1 on Router D and GigabitEthernet 2/1/4 on Router E act as C-BSRs and C-RPs.
Configuration procedure 1. Assign an IP address and subnet mask to each interface according to Figure 46. (Details not shown.) 2. Configure OSPF on the routers in the PIM-SM domain to make sure they are interoperable at the network layer. (Details not shown.) 3. Enable IP multicast routing, PIM-SM, and IGMP: # Enable IP multicast routing on Router A, enable PIM-SM on each interface, and enable IGMP on GigabitEthernet 2/1/0, which connects Router A to the stub network.
Use the display pim interface command to display PIM information on each interface. For example: # Display PIM information on Router A. [RouterA] display pim interface VPN-Instance: public net Interface NbrCnt HelloInt DR-Pri DR-Address GE2/1/0 0 30 1 10.110.1.1 GE2/1/3 1 30 1 192.168.1.2 GE2/1/1 1 30 1 192.168.9.2 (local) # Display information about the BSR and locally configured C-RP on Router A. [RouterA] display pim bsr-info VPN-Instance: public net Elected BSR Address: 192.168.9.
Uptime: 00:01:18 Next BSR message scheduled at: 00:01:52 Candidate BSR Address: 192.168.9.2 Priority: 20 Hash mask length: 32 State: Elected Scope: Not scoped Candidate RP: 192.168.9.2(GE2/1/4) Priority: 192 HoldTime: 150 Advertisement Interval: 60 Next advertisement scheduled at: 00:00:48 # Display RP information on Router A. [RouterA] display pim rp-info VPN-Instance: public net PIM-SM BSR RP information: Group/MaskLen: 225.1.1.0/24 RP: 192.168.4.
Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet2/1/0 Protocol: igmp, UpTime: 00:13:46, Expires: 00:03:06 (10.110.5.100, 225.1.1.0) RP: 192.168.9.2 Protocol: pim-sm, Flag: SPT ACT UpTime: 00:00:42 Upstream interface: GE2/1/3 Upstream neighbor: 192.168.1.2 RPF prime neighbor: 192.168.1.
Protocol: pim-sm, UpTime: 00:13:16, Expires: 00:03:22 PIM-SM admin-scope zone configuration example Network requirements As shown in Figure 47, the receivers receive VOD information through multicast. The entire PIM-SM domain is divided into admin-scope zone 1, admin-scope zone 2, and the global scope zone. Router B, Router C, and Router D are ZBRs of the three domains, respectively. Source 1 and Source 2 send different multicast information to multicast group 239.1.1.1.
Device Interface IP address Device Interface IP address Router A GE2/1/0 192.168.1.1/24 Router D GE2/1/1 10.110.4.2/24 GE2/1/1 10.110.1.1/24 GE2/1/3 10.110.7.1/24 Router B GE2/1/0 192.168.2.1/24 GE2/1/2 10.110.8.1/24 GE2/1/1 10.110.1.2/24 GE2/1/0 192.168.4.1/24 GE2/1/2 10.110.2.1/24 GE2/1/1 10.110.5.2/24 GE2/1/4 10.110.3.1/24 GE2/1/3 10.110.7.2/24 GE2/1/0 192.168.3.1/24 GE2/1/1 10.110.9.1/24 GE2/1/1 10.110.4.1/24 GE2/1/2 10.110.8.2/24 GE2/1/3 10.110.5.
[RouterB] interface gigabitethernet 2/1/0 [RouterB-GigabitEthernet2/1/0] pim sm [RouterB-GigabitEthernet2/1/0] quit [RouterB] interface gigabitethernet 2/1/1 [RouterB-GigabitEthernet2/1/1] pim sm [RouterB-GigabitEthernet2/1/1] quit [RouterB] interface gigabitethernet 2/1/2 [RouterB-GigabitEthernet2/1/2] pim sm [RouterB-GigabitEthernet2/1/2] quit [RouterB] interface gigabitethernet 2/1/4 [RouterB-GigabitEthernet2/1/4] pim sm [RouterB-GigabitEthernet2/1/4] quit # Enable IP multicast routing, administrative s
[RouterB-pim] quit # On Router D, configure the service scope of RP advertisements and configure GigabitEthernet 2/1/1 as a C-BSR and C-RP of admin-scope zone 2. [RouterD] acl number 2001 [RouterD-acl-basic-2001] rule permit source 239.0.0.0 0.255.255.255 [RouterD-acl-basic-2001] quit [RouterD] pim [RouterD-pim] c-bsr group 239.0.0.
# Display information about the BSR and locally configured C-RP on Router D. [RouterD] 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.4.2 Priority: 64 Hash mask length: 30 State: Elected Scope: 239.0.0.0/8 Uptime: 00:03:48 Next BSR message scheduled at: 00:01:12 Candidate BSR Address: 10.110.4.
Next advertisement scheduled at: 00:00:55 # Display RP information on Router B. [RouterB] 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:39 Expires: 00:01:51 Group/MaskLen: 239.0.0.0/8 RP: 10.110.1.2 (local) Priority: 192 HoldTime: 150 Uptime: 00:07:44 Expires: 00:01:51 # Display RP information on Router D.
BIDIR-PIM configuration example Network requirements In the BIDIR-PIM domain shown in Figure 48, Source 1 and Source 2 send different multicast information to multicast group 225.1.1.1. Host A and Host B receive multicast information from the two sources. Serial 3/1/1 of Router C acts as a C-BSR, and loopback interface 0 of Switch C acts as a C-RP of the BIDIR-PIM domain. IGMPv2 runs between Router B and Host A and between Router D and Host B.
[RouterA-GigabitEthernet2/1/1] pim sm [RouterA-GigabitEthernet2/1/1] quit [RouterA] interface serial 3/1/1 [RouterA-Serial3/1/1] pim sm [RouterA-Serial3/1/1] quit [RouterA] pim [RouterA-pim] bidir-pim enable [RouterA-pim] quit # On Router B, enable IP multicast routing, enable PIM-SM on each interface, enable IGMP on interface GigabitEthernet 2/1/1, and enable BIDIR-PIM.
[RouterD] interface e GigabitEthernet 2/1/2 [RouterD-GigabitEthernet2/1/2] pim sm [RouterD-GigabitEthernet2/1/2] quit [RouterD] interface serial 3/1/1 [RouterD-Serial3/1/1] pim sm [RouterD-Serial3/1/1] quit [RouterD] pim [RouterD-pim] bidir-pim enable [RouterD-pim] quit 4. On Router C, configure Serial 3/1/1 as a C-BSR, and loopback interface 0 as a C-RP for the entire BIDIR-PIM domain. [RouterC-pim] c-bsr serial 3/1/1 [RouterC-pim] c-rp loopback 0 bidir [RouterC-pim] quit 5.
GE2/1/1 Win 100 1 01:19:53 192.168.3.1 (local) GE2/1/2 Win 100 1 00:39:34 192.168.4.1 (local) Ser3/1/2 Lose 0 0 01:21:40 10.110.3.1 To display the DF information of the multicast forwarding table on a router, use the display multicast forwarding-table df-info command. # Display the DF information of the multicast forwarding table on Router A. [RouterA] display multicast forwarding-table df-info Multicast DF information of VPN-Instance: public net Total 1 RP Total 1 RP matched 00001.
[RouterD] display multicast forwarding-table df-info Multicast DF information of VPN-Instance: public net Total 1 RP Total 1 RP matched 00001. RP Address: 1.1.1.1 MID: 0, Flags: 0x2100000:0 Uptime: 00:05:12 RPF interface: Serial3/1/1 List of 2 DF interfaces: 1: GigabitEthernet2/1/1 2: GigabitEthernet2/1/2 PIM-SSM configuration example Network requirements As shown in Figure 49, the receivers receive VOD information through multicast.
Router A Router B Router C GE2/1/0 10.110.5.1/24 GE2/1/3 192.168.1.2/24 GE2/1/1 192.168.4.2/24 GE2/1/0 192.168.3.2/24 192.168.2.1/24 GE2/1/1 192.168.2.2/24 GE2/1/0 10.110.2.2/24 GE2/1/2 192.168.9.2/24 GE2/1/1 192.168.3.1/24 GE2/1/3 192.168.4.1/24 GE2/1/0 10.110.1.1/24 GE2/1/3 192.168.1.1/24 GE2/1/1 192.168.9.1/24 GE2/1/0 10.110.2.1/24 GE2/1/1 Router D Router E Configuration procedure 1. Assign an IP address and subnet mask to each interface according to Figure 49.
# Display PIM configuration information on Router A. [RouterA] display pim interface VPN-Instance: public net Interface NbrCnt HelloInt DR-Pri DR-Address GE2/1/0 0 30 1 10.110.1.1 GE2/1/3 1 30 1 192.168.1.2 GE2/1/1 1 30 1 192.168.9.2 (local) Assume that Host A needs to receive the information a specific multicast source S (10.110.5.100/24) sends to multicast group G (232.1.1.1). Router A builds an SPT toward the multicast source.
Troubleshooting PIM This section describes common PIM problems and how to troubleshoot them. A multicast distribution tree cannot be built correctly Symptom None of the routers in the network (including routers directly connected with multicast sources and receivers) have multicast forwarding entries. In other words, a multicast distribution tree cannot be correctly built and the receivers cannot receive multicast data.
6. Verify that the same PIM mode is enabled on all the routers in the entire network. Make sure the same PIM mode (PIM-SM or PIM-DM) is enabled on all routers. For PIM-SM, verify that the BSR and RP configurations are correct. Multicast data abnormally terminated on an intermediate router Symptom An intermediate router can receive multicast data successfully, but the data cannot reach the last-hop router.
RPT establishment failure or source registration failure in PIM-SM Symptom C-RPs cannot unicast advertise messages to the BSR. The BSR does not advertise bootstrap messages containing C-RP information and has no unicast route to any C-RP. An RPT cannot be established correctly, or the DR cannot perform source registration with the RP. Analysis • The C-RPs periodically send C-RP-Adv messages to the BSR by unicast.
Configuring MSDP For more information about the concepts of designated router (DR), bootstrap router (BSR), candidate-BSR (C-BSR), rendezvous point (RP), candidate-RP (C-RP), shortest path tree (SPT) and rendezvous point tree (RPT) mentioned in this document, see "Configuring PIM." Overview MSDP is an inter-domain multicast solution that addresses the interconnection of protocol independent multicast sparse mode (PIM-SM) domains. It discovers multicast source information in other PIM-SM domains.
Figure 50 Where MSDP peers are in the network As shown in Figure 50, an MSDP peer can be created on any PIM-SM router. MSDP peers created on PIM-SM routers, that assume different roles, will function differently. 1. MSDP peers on RPs include the following types: { { { 2. Source-side MSDP peer—The MSDP peer nearest to the multicast source (Source), typically the source-side RP, like RP 1.
Figure 51 Inter-domain multicast delivery through MSDP The process of implementing PIM-SM inter-domain multicast delivery by leveraging MSDP peers is as follows: 1. When the multicast source in PIM-SM 1 sends the first multicast packet to multicast group G, DR 1 encapsulates the multicast data within a register message and sends the register message to RP 1. Then, RP 1 identifies the information related to the multicast source. 2.
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. When using MSDP for inter-domain multicasting, once an RP receives information form a multicast source, it no longer relies on RPs in other PIM-SM domains. The receivers can override the RPs in other domains and directly join the multicast source-based SPT. RPF check rules for SA messages As shown in Figure 52, the autonomous systems in the network are AS 1 through AS 5.
Although RP 4 and RP 5 are in the same AS (AS 3) and both are MSDP peers of RP 6, because RP 5 has a higher IP address, RP 6 accepts only the SA message from RP 5. 5. When RP 7 receives the SA message from RP 6: Because the SA message is from a static RPF peer (RP 6), RP 7 accepts the SA message and forwards it to other peer (RP 8). 6. When RP 8 receives the SA message from RP 7: A BGP or MBGP route exists between two MSDP peers in different ASs.
The working process of Anycast RP is as follows: 4. The multicast source registers with the nearest RP. In this example, Source registers with RP 1, with its multicast data encapsulated in the register message. When the register message arrives at RP 1, RP 1 de-encapsulates the message. 5. Receivers send join messages to the nearest RP to join in the RPT rooted as this RP. In this example, Receiver joins the RPT rooted at RP 2. 6. RPs share the registered multicast information by means of SA messages.
MSDP configuration task list Task Remarks Configuring basic MSDP functions Configuring an MSDP peer connection Configuring SA message related parameters Enabling MSDP Required. Creating an MSDP peer connection Required. Configuring a static RPF peer Optional. Configuring MSDP peer description Optional. Configuring an MSDP mesh group Optional. Configuring MSDP peer connection control Optional. Configuring SA message content Optional. Configuring SA request messages Optional.
Step Command Remarks 1. Enter system view. system-view N/A 2. Create a VPN instance and enter VPN instance view. ip vpn-instance vpn-instance-name For more information about this command, see MPLS Command Reference. No RD is configured by default. 3. Configure an RD for the VPN instance. route-distinguisher route-distinguisher For more information about this command, see MPLS Command Reference. 4. Enable IP multicast routing. multicast routing-enable Disabled by default. 5.
NOTE: If only one MSDP peer is configured on a router, this MSDP peer is registered as a static RPF peer. Configuring an MSDP peer connection This section describes how to configure an MSDP peer connection. Configuration prerequisites Before you configure an MSDP peer connection, complete the following tasks: • Configure any unicast routing protocol so that all devices in the domain are interoperable at the network layer. • Configure basic MSDP functions. • Determine the description of MSDP peers.
Before grouping multiple routers into an MSDP mesh group, make sure these routers are interconnected with one another. To create an MSDP mesh group: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter public network MSDP view or VPN instance MSDP view. msdp [ vpn-instance vpn-instance-name ] N/A Create an MSDP mesh group and assign an MSDP peer to that mesh group. 3. An MSDP peer does not belong to any mesh group by default.
Step 4. 5. Command Configure the interval between MSDP peer connection retries. timer retry interval Configure a password for MD5 authentication used by both MSDP peers to establish a TCP connection. peer peer-address password { cipher cipher-password | simple simple -password } Remarks Optional. 30 seconds by default. Optional. By default, MD5 authentication is not performed before a TCP connection is established.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter public network MSDP view or VPN instance MSDP view. msdp [ vpn-instance vpn-instance-name ] N/A 3. Enable encapsulation of multicast data in SA messages. encap-data-enable Configure the interface address as the RP address in SA messages. originating-rp interface-type interface-number 4. Optional. Disabled by default. Optional. PIM RP address by default.
{ If the TTL value is greater than or equal to the threshold, the router encapsulates the multicast data in an SA message and sends the SA message. After receiving an SA message with an encapsulated multicast data packet, the router decreases the TTL value of the multicast packet by 1 and then checks the TTL value: • { { If the TTL value is less than the threshold, the router does not forward the SA message to the designated MSDP peer.
Step Command 3. Enable the SA cache mechanism. cache-sa-enable 4. Configure the maximum number of (S, G) entries learned from the specified MSDP peer that the router can cache. peer peer-address sa-cache-maximum sa-limit Remarks Optional. Enabled by default. Optional. 8192 by default. Displaying and maintaining MSDP Task Command Remarks Display brief information about MSDP peers.
Configure Loopback 0 as the C-BSR and C-RP of the related PIM-SM domain on Router B, Router C, and Router E. Set up MSDP peering relationships through eBGP between the RPs of the PIM-SM domains to share multicast source information among the PIM-SM domains. Figure 54 Network diagram G E2 /1 /3 /2 /1 E2 G /1 /1 E2 G /1 E2 G G E2 /1 /2 /1 Device Interface IP address Device Router A GE2/1/1 10.110.1.2/24 Router D GE2/1/2 10.110.2.1/24 GE2/1/3 10.110.3.1/24 GE2/1/1 POS5/1/0 Loop0 1.1.1.
[RouterA] interface gigabitethernet 2/1/1 [RouterA-GigabitEthernet2/1/1] pim sm [RouterA-GigabitEthernet2/1/1] quit [RouterA] interface gigabitethernet 2/1/2 [RouterA-GigabitEthernet2/1/2] pim sm [RouterA-GigabitEthernet2/1/2] quit [RouterA] interface gigabitethernet 2/1/3 [RouterA-GigabitEthernet2/1/3] igmp enable [RouterA-GigabitEthernet2/1/3] pim sm [RouterA-GigabitEthernet2/1/3] quit # Enable IP multicast routing, PIM-SM, and IGMP on Router B, Router C, Router D, Router E, and Router F in the same way.
[RouterB-ospf-1] import-route bgp [RouterB-ospf-1] quit # Redistribute BGP routing information into OSPF on Router C. [RouterC] ospf 1 [RouterC-ospf-1] import-route bgp [RouterC-ospf-1] quit 6. Configure MSDP peers: # Configure an MSDP peer on Router B. [RouterB] msdp [RouterB-msdp] peer 192.168.1.2 connect-interface pos 5/1/0 [RouterB-msdp] quit # Configure MSDP peers on Router C. [RouterC] msdp [RouterC-msdp] peer 192.168.1.1 connect-interface pos 5/1/0 [RouterC-msdp] peer 192.168.3.
BGP Local router ID is 2.2.2.2 Status codes: * - valid, ^ - VPNv4 best, > - best, d - damped, h - history, i - internal, s - suppressed, S - Stale Origin : i - IGP, e - EGP, ? - incomplete Network NextHop MED 1.1.1.1/32 192.168.1.1 0 0 100? * >i 2.2.2.2/32 0.0.0.0 0 0 ? * > 192.168.1.0 0.0.0.0 0 0 ? * > 192.168.1.1/32 0.0.0.0 0 0 ? * > 192.168.1.2/32 0.0.0.
Resets: 0 Connection interface: Pos5/1/0 (192.168.1.
Figure 55 Network diagram AS 200 AS 100 PIM-SM 3 Receiver 0 /1/ S3 /2 /1 E2 G Loop0 GE2/1/2 GE2/1/1 /1 /1 E2 G Router A Router F 0 /1/ S3 Router G GE2/1/1 G E2 /1 /2 GE2/1/1 Loop0 Receiver Router C PIM-SM 2 /1 E2 G Router D /1 POS5/1/0 POS5/1/0 Router E GE2/1/1 GE2/1/1 Router B Source 1 Loop0 G E2 /1 /2 GE2/1/2 Source 2 PIM-SM 1 BGP peers Device Interface IP address Device Interface IP address Source 1 - 192.168.1.100/24 Router D GE2/1/1 10.110.5.
[RouterC] interface gigabitethernet 2/1/2 [RouterC-GigabitEthernet2/1/2] igmp enable [RouterC-GigabitEthernet2/1/2] pim sm [RouterC-GigabitEthernet2/1/2] quit [RouterC] interface serial 3/1/0 [RouterC-Serial3/1/0] pim sm [RouterC-Serial3/1/0] quit # Enable IP multicast routing, PIM-SM, and IGMP on Router A, Router B, Router D, Router E, Router F, and Router G in the same way. (Details not shown.) # Configure PIM domain borders on Router B.
[RouterF-bgp] import-route ospf 1 [RouterF-bgp] quit # Redistribute BGP routing information into OSPF on Router B. [RouterB] ospf 1 [RouterB-ospf-1] import-route bgp [RouterB-ospf-1] quit # Redistribute BGP routing information into OSPF on Router D. [RouterD] ospf 1 [RouterD-ospf-1] import-route bgp [RouterD-ospf-1] quit # Redistribute BGP routing information into OSPF on Router C.
You can use the display msdp brief command to display brief information about MSDP peering relationship between the routers. For example: # Display brief information about MSDP peers on Router A. [RouterA] display msdp brief MSDP Peer Brief Information of VPN-Instance: public net Configured Up Listen Connect Shutdown Down 2 2 0 0 0 0 Peer's Address State Up/Down time AS SA Count Reset Count 10.110.3.2 Up 01:07:08 ? 8 0 10.110.6.
Lo op 0 S3 /1/ 0 S3 /1/ 0 0 op Lo 20 op Lo Lo op 20 0 /1/ S5 PO 0 /1/ S3 PO S5 /1/ 0 1 /1/ S5 PO 0 /1/ S3 PO S5 /1/ 0 Figure 56 Network diagram Device Interface IP address Device Interface IP address Source 1 — 10.110.5.100/24 Router C POS5/1/0 192.168.1.2/24 Source 2 — 10.110.6.100/24 POS5/1/1 192.168.2.2/24 Router A Router B GE2/1/1 10.110.5.1/24 GE2/1/1 10.110.3.1/24 S3/1/0 10.110.2.2/24 S3/1/0 10.110.4.1/24 GE2/1/1 10.110.1.1/24 POS5/1/0 192.168.2.
[RouterB-Serial3/1/0] pim sm [RouterB-Serial3/1/0] quit [RouterB] interface pos 5/1/0 [RouterB-Pos5/1/0] pim sm [RouterB-Pos5/1/0] quit [RouterB] interface loopback 0 [RouterB-LoopBack0] pim sm [RouterB-LoopBack0] quit [RouterB] interface loopback 10 [RouterB-LoopBack10] pim sm [RouterB-LoopBack10] quit [RouterB] interface loopback 20 [RouterB-LoopBack20] pim sm [RouterB-LoopBack20] quit # Enable IP multicast routing, PIM-SM, and IGMP on Router A, Router C, Router D, and Router E in the same way.
Configured Up Listen Connect Shutdown Down 1 1 0 0 0 0 Peer's Address State Up/Down time AS SA Count Reset Count 1.1.1.1 Up 00:10:18 ? 0 0 When Source 1 (10.110.5.100/24) sends multicast data to multicast group G (225.1.1.1), Host A joins multicast group G. By comparing the PIM routing information displayed on Router B with that displayed on Router D, you can see that Router B acts now as the RP for Source 1 and Host A. # Display PIM routing information on Router B.
[RouterD] display pim routing-table VPN-Instance: public net Total 1 (*, G) entry; 1 (S, G) entry (*, 225.1.1.1) RP: 10.1.1.1 (local) Protocol: pim-sm, Flag: WC UpTime: 00:12:07 Upstream interface: Register Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet2/1/1 Protocol: igmp, UpTime: 00:12:07, Expires: - (10.110.6.100, 225.1.1.1) RP: 10.1.1.
Figure 57 Network diagram PIM-SM 1 PIM-SM 2 Loop0 PIM-SM 3 Source 2 GE2/1/0 Receiver Host A Router A GE 2/1 /1 GE2/1/3 Loop0 GE 2/1 /1 GE2/1/0 Router C GE2/1/3 GE2/1/3 GE2/1/0 Source 1 Router D GE2/1/2 GE2/1/3 GE2/1/0 Router B Receiver Host B MSDP peers Receiver Host C Device Interface IP address Device Interface IP address Source 1 — 10.110.3.100/24 Router C GE2/1/0 10.110.4.1/24 Source 2 — 10.110.6.100/24 GE2/1/3 10.110.5.1/24 Router A GE2/1/0 10.110.1.
[RouterA-GigabitEthernet 2/1/1] pim sm [RouterA-GigabitEthernet 2/1/1] quit [RouterA] interface loopback 0 [RouterA-LoopBack0] pim sm [RouterA-LoopBack0] quit # Enable IP multicast routing, PIM-SM, and IGMP on Router B, Router C and Router D in the same way. (Details not shown.) # Configure PIM domain borders on Router C.
[RouterC-acl-adv-3001] rule permit ip source any destination any [RouterC-acl-adv-3001] quit [RouterC] msdp [RouterC-msdp] peer 10.110.5.2 sa-policy export acl 3001 [RouterC-msdp] quit # Configure an SA message filter on Router D so that Router D will not create SA messages for Source 2. [RouterD] acl number 2001 [RouterD-acl-basic-2001] rule deny source 10.110.6.100 0 [RouterD-acl-basic-2001] quit [RouterD] msdp [RouterD-msdp] import-source acl 2001 [RouterD-msdp] quit 7.
MSDP peers stay in down state Symptom The configured MSDP peers stay in down state. Analysis • A TCP connection–based MSDP peering relationship is established between the local interface address and the MSDP peer after the configuration. • The TCP connection setup will fail if the local interface address is not consistent with the MSDP peer address configured on the peer router. • If no route is available between the MSDP peers, the TCP connection setup will fail. 1.
Analysis • In the Anycast RP application, RPs in the same PIM-SM domain are configured to be MSDP peers to achieve load balancing among the RPs. • An MSDP peer address must be different from the Anycast RP address, and the C-BSR and C-RP must be configured on different devices or interfaces. • If you configure the originating-rp command, MSDP replaces the RP address in the SA messages with the address of the interface specified in the command.
Configuring MBGP The term "router" in this document refers to both routers and routing-capable Ethernet switches. MBGP overview BGP-4 can carry routing information for IPv4 only. IETF defined Multiprotocol Border Gateway Protocol (MP-BGP) to extend BGP-4 so that BGP can carry routing information for multiple network-layer protocols. For a network, the topology for multicast might be different from that for unicast.
Task Remarks Configuring MBGP route preferences Configuring the default local preference Configuring MBGP route attributes Configuring the MED attribute Optional. Configuring the NEXT_HOP attribute Configuring the AS_PATH attribute Optimizing MBGP networks Configuring a large scale MBGP network Configuring MBGP soft reset Optional. Enabling the MBGP ORF capability Optional. Configuring the maximum number of MBGP routes for load balancing Optional. Configuring IPv4 MBGP peer groups Optional.
Controlling route advertisement and reception Configuration prerequisites You must configure basic MBGP functions before you configure this task. Configuring MBGP route redistribution MBGP can advertise routing information in the local AS to neighboring ASs. It redistributes such routing information from IGP into its routing table rather than learns the information by itself.
Step Command Remarks 2. Enter BGP view. bgp as-number N/A 3. Enter MBGP address family view. ipv4-family multicast N/A 4. Enable route redistribution from another routing protocol. import-route protocol [ { process-id | all-processes } [ allow-direct | med med-value | route-policy route-policy-name ] * ] 5. Enable default route redistribution into the MBGP routing table. default-route imported No route redistribution is configured by default.
Step Command Remarks 2. Enter BGP view. bgp as-number N/A 3. Enter IPv4 MBGP address family view. ipv4-family multicast N/A 4. Advertise a default route to an MBGP peer or peer group. peer { group-name | ip-address } default-route-advertise [ route-policy route-policy-name ] Not advertised by default.
Step Command Remarks • Configure the filtering of redistributed routes: filter-policy { acl-number | ip-prefix ip-prefix-name } export [ direct | isis process-id | ospf process-id | rip process-id | static ] • Apply a routing policy to advertisements to an IPv4 MBGP peer or a peer group: peer { group-name | peer-address } route-policy route-policy-name export Configure BGP route distribution filtering policies. 4.
Step Command Remarks • Filter incoming routes using an ACL or IP prefix list: filter-policy { acl-number | ip-prefix ip-prefix-name } import • Reference a routing policy to routes from an IPv4 MBGP peer or a peer group: peer { group-name | ip-address } route-policy policy-name import • Reference an ACL to filter routing 4. information from an IPv4 MBGP peer or a peer group: peer { group-name | ip-address } filter-policy acl-number import Configure MBGP route reception filtering policies.
Step 4. Configure BGP route dampening parameters. Command Remarks dampening [ half-life-reachable half-life-unreachable reuse suppress ceiling | route-policy route-policy-name ] * Not configured by default. Configuring MBGP route attributes You can modify MBGP route attributes to affect route selection. Configuration prerequisites Before you configure this task, you must configure basic MBGP functions.
Configuring the MED attribute When other conditions of routes to a destination are identical, the route with the smallest MED is selected. To configure the MED attribute: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter IPv4 MBGP address family view. ipv4-family multicast N/A • Configure the default MED value: default med med-value • Enable the comparison of the 4. Configure the MED attribute.
Step Command Remarks Optional. 4. Specify the router as the next hop of routes sent to a peer or a peer group. peer { group-name | ip-address } next-hop-local By default, MBGP specifies the local router as the next hop for routes advertised to a MBGP EBGP peer or a peer group, but not for routes advertised to a MBGP IBGP peer or a peer group. Configuring the AS_PATH attribute In general, MBGP checks whether the AS-PATH attribute of a route from a peer contains the local AS number.
Configuration prerequisites Before you configure this task, configure basic MBGP functions. Configuring MBGP soft reset After modifying a route selection policy, you have to reset MBGP connections to make it take effect. The current MBGP implementation supports the route refresh feature that enables dynamic route refresh without terminating MBGP connections.
Step 6. Soft-reset MBGP connections manually. Command Remarks refresh bgp ipv4 multicast { all | ip-address | group group-name | external | internal } { export | import } Optional. Enabling the MBGP ORF capability The MBGP Outbound Router Filter (ORF) feature enables an MBGP speaker to send a set of ORFs to its MBGP peer through route-refresh messages.
Table 8 Description of the both, send, and receive parameters and the negotiation result Local parameter Peer parameter Negotiation result send • receive • both The ORF sending capability is enabled locally and the ORF receiving capability is enabled on the peer. receive • send • both The ORF receiving capability is enabled locally and the ORF sending capability is enabled on the peer. both both Both the ORF sending and receiving capabilities are enabled locally and on the peer.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Create a BGP peer group. group group-name [ external | internal ] Not created by default. 4. Add a peer into the peer group. peer ip-address group group-name [ as-number as-number ] No peer added by default. 5. Enter IPv4 MBGP address family view. ipv4-family multicast N/A 6. Enable the IPv4 unicast peer group. peer group-name enable N/A 7. Add an IPv4 MBGP peer to the peer group.
Configuring an MBGP route reflector To guarantee the connectivity between multicast IBGP peers in an AS, you need to make them fully meshed. However, this becomes impractical when large numbers of multicast IBGP peers exist. Configuring route reflectors can solve this problem. In general, it is not required that clients of a route reflector be fully meshed. The route reflector forwards routing information between clients.
Task Command Remarks Display the advertised networks. display bgp multicast network [ | { begin | exclude | include } regular-expression ] Available in any view. Display AS path information. display bgp multicast paths [ as-regular-expression | | { begin | exclude | include } regular-expression ] Available in any view. Display MBGP peer information or peer group information.
Task Command Remarks Display IPv4 MBGP routing information sent to or received from an MBGP peer. display bgp multicast routing-table peer ip-address { advertised-routes | received-routes } [ network-address [ mask | mask-length ] | statistic ] [ | { begin | exclude | include } regular-expression ] Available in any view. Display IPv4 MBGP routing information matching an AS regular expression. display bgp multicast routing-table regular-expression as-regular-expression Available in any view.
Figure 58 Network diagram AS 100 AS 200 Loop0 Loop0 POS5/1/0 Router A POS5/1/0 Router B Receiver GE2/1/1 Source Router D S3/1/1 S3/1/0 Router C PIM-SM 1 Loop0 Loop0 PIM-SM 2 MBGP peers Device Interface IP address Device Interface Source - 10.110.1.100/24 Router C GE2/1/1 10.110.2.1/24 Router A GE2/1/1 10.110.1.1/24 S3/1/0 192.168.4.1/24 POS5/1/0 192.168.1.1/24 S3/1/1 192.168.2.2/24 Loop0 3.3.3.3/32 S3/1/0 192.168.3.2/24 Router B Loop0 1.1.1.1/32 POS5/1/0 192.168.1.
[RouterC] interface serial 3/1/0 [RouterC-Serial3/1/0] pim sm [RouterC-Serial3/1/0] quit [RouterC] interface serial 3/1/1 [RouterC-Serial3/1/1] pim sm [RouterC-Serial3/1/1] quit [RouterC] interface gigabitethernet 2/1/1 [RouterC-GigabitEthernet2/1/1] pim sm [RouterC-GigabitEthernet2/1/1] igmp enable [RouterC-GigabitEthernet2/1/1] quit # Configure a PIM domain border on Router A.
[RouterA-bgp] quit # On Router B, configure the MBGP peer and enable route redistribution from OSPF. [RouterB] bgp 200 [RouterB-bgp] router-id 2.2.2.2 [RouterB-bgp] peer 192.168.1.1 as-number 100 [RouterB-bgp] import-route ospf 1 [RouterB-bgp] ipv4-family multicast [RouterB-bgp-af-mul] peer 192.168.1.1 enable [RouterB-bgp-af-mul] import-route ospf 1 [RouterB-bgp-af-mul] quit [RouterB-bgp] quit 6. Configure MSDP peers: # Specify the MSDP peer on Router A. [RouterA] msdp [RouterA-msdp] peer 192.168.1.
Configuring multicast VPN Overview Multicast VPN is a technique that implements multicast delivery in VPNs. A VPN is comprised of multiple sites and the public network provided by the network provider. The sites communicate through the public network. As shown in Figure 59, VPN A comprises Site 1, Site 3 and Site 5, and VPN B comprises Site 2, Site 4 and Site 6.
Figure 60 Multicast in multiple VPN instances With multicast VPN, when a multicast source in VPN A sends a multicast stream to a multicast group, of all possible receivers on the network for that group, only those that belong to VPN A, namely, in Site 1, Site 3 or Site 5, can receive the multicast stream. The stream is multicast in these sites and in the public network. The prerequisites for implementing multicast VPN are as follows: 1. Within each site, multicast for a single VPN is supported. 2.
MD-VPN overview The basic concepts involved in MD-VPN are described in Table 9. Table 9 Basic concepts in MD-VPN Concept Description Multicast domain (MD) An MD is a set of VPN instances running on PE devices that can send multicast traffic to each other. Each MD uniquely corresponds to the same set of VPN instances. Multicast distribution tree (MDT) An MDT is a multicast distribution tree between all PE devices in the same VPN. MDT types include share-MDT and switch-MDT.
VPN multicast traffic between the PE devices and the CE devices is transmitted on a per-VPN-instance basis, but the public network multicast traffic between the PE devices and the P devices is transmitted through the public network. • Logically, an MD defines the transmission range of the multicast traffic of a specific VPN over the public network. Physically, an MD identifies all the PE devices that support that VPN on the public network. Different VPN instances correspond to different MDs.
multicast packets transmitted in this VPN are forwarded along this share-MDT, no matter at which PE device they entered the public network. • A share-group is assigned a unique switch-group-pool for MDT switchover. When the rate of a VPN multicast stream that entered the public network at a PE device exceeds the switchover threshold, the PE chooses an idle address (namely, switch-group) from the switch-group-pool, and encapsulates the multicast packets for that VPN using that address.
• PE-PE neighboring relationship—PIM neighboring relationship established after a VPN instance on a PE device receives a PIM hello from a VPN instance on a remote PE device through an MTI. • PE-CE neighboring relationship—PIM neighboring relationship established between a VPN-instance-associated interface on a PE device and an interface on a peer CE device. Multicast across VPNs MD VPN implements multicasting between the multicast source and the receivers when they are in the same VPN.
Figure 64 Source-side PE configuration As shown in Figure 64, configure VPN instance A, create VPN instance B, and specify the share-group on PE 1. After the configuration, a share-MDT is established for VPN instance A and VPN instance B respectively on the public network. After receiving multicast packets from Source 1, PE 1 duplicates and encapsulates them, and forwards them to PE 2 and PE 3 along the share-MDTs. PE 2 and PE 3 de-encapsulate and forward them to Receiver 1 and Receiver 2, respectively.
Figure 65 Receiver-side PE configuration As shown in Figure 65, configure VPN instance B, create VPN instance A, and specify the share-group on PE 3. Because PE 2 serves VPN A, create VPN instance A and specify the share-group on PE 2. After the configuration, a share-MDT is established for VPN instance A. After receiving multicast packets from Source 1, PE 1 encapsulates and forwards them to PE 2 and PE 3 along the share-MDT.
then the remote site can receive the data through the MTI. Actually, the multicast data transmission process (the MDT transmission process) over the public network is very complicated. Share-MDT establishment The multicast routing protocol running on the public network can be PIM-DM, PIM-SM, BIDIR-PIM, or PIM-SSM. The process of creating a share-MDT is different in these PIM modes. Share-MDT establishment in a PIM-DM network Figure 66 Share-MDT establishment in a PIM-DM network BGP: 11.1.3.
Share-MDT establishment in a PIM-SM network Figure 67 Share-MDT establishment in a PIM-SM network BGP: 11.1.3.1/24 PE 3 Share-Group: 239.1.1.1 Public instance BGP peers RPT (*, 239.1.1.1) SPT (11.1.1.1, 239.1.1.1) SPT (11.1.2.1, 239.1.1.1) RP SPT (11.1.3.1, 239.1.1.1) P PE 1 BGP: 11.1.1.1/24 PE 2 MD BGP: 11.1.2.1/24 As shown in Figure 67, PIM-SM is enabled in the network and all the PE devices support VPN instance A. The process of establishing a share-MDT is as follows: 1.
Share-MDT establishment in a BIDIR-PIM network Figure 68 Share-MDT establishment in a BIDIR-PIM network As shown in Figure 68, BIDIR-PIM is enabled in the network and all the PE devices support VPN instance A. The process of establishing a share-MDT is as follows: 1. The public network on PE 1 initiates a join to the public network RP, with the share-group address as the multicast group address in the join message, and a (*, 239.1.1.1) entry is created on each device along the path on the public network.
Share-MDT establishment in a PIM-SSM network Figure 69 Share-MDT establishment in a PIM-SSM network BGP: 11.1.3.1/24 PE 3 Share-Group: 232.1.1.1 Public instance BGP peers SPT (11.1.1.1, 232.1.1.1) SPT (11.1.2.1, 232.1.1.1) SPT (11.1.3.1, 232.1.1.1) P PE 1 BGP: 11.1.1.1/24 PE 2 MD BGP: 11.1.2.1/24 As shown in Figure 69, PIM-SSM is enabled in the network and all the PE devices support VPN instance A. The process of establishing a share-MDT is as follows: 1.
Share-MDT-based delivery A share-MDT can be used for delivering multicast packets, including both multicast protocol packets and multicast data packets. However, the transmission processes for these two types of multicast packets are different. Multicast protocol packet delivery To forward the multicast protocol packets of a VPN over the public network, the local PE device encapsulates them into public-network multicast data packets.
Figure 70 Transmission of multicast protocol packets BGP: 11.1.3.1/24 PE 3 Source Receiver RP CE 1 Site 1 P PE 1 MD BGP: 11.1.1.1/24 PE 2 CE 2 BGP: 11.1.2.1/24 Site 2 S: 192.1.1.1/24 Public instance BGP peers G: 225.1.1.1 VPN instance join (*, 225.1.1.1) Share-Group: 239.1.1.1 Public instance join (11.1.2.1, 239.1.1.1) The work process of multicast protocol packets is as follows: 1. Receiver sends an IGMP membership report for multicast group G to CE 2.
the remote PE device and transmitted in that VPN site. VPN multicast data flows are forwarded across the public network differently in the following circumstances: 1. If PIM-DM or PIM-SSM is running in the VPN, the multicast source forwards multicast data to the receivers along the VPN SPT across the public network. 2. When PIM-SM is running in the VPN: { { 3.
If the outgoing interface list of the forwarding entry contains an MTI, PE 1 processes the VPN multicast data. Now, the VPN instance on PE 1 considers that the VPN multicast data has been sent out of the MTI. 6. PE 1 encapsulates the multicast data by means of GRE. Its BGP interface address is the multicast source address and the share-group address is the multicast group address, converting it into a normal, public network multicast data packet (11.1.1.1, 239.1.1.1).
5. After the multicast traffic is switched from the share-MDT to the switch-MDT, PE 1 continues sending MDT switchover messages periodically, so that subsequent PE devices with attached receivers can join the switch-MDT. When a downstream PE device has no longer active receivers attached to it, it leaves the switch-MDT. For a given VPN instance, the share-MDT and the switch-MDT are both forwarding tunnels in the same MD.
Multi-hop EBGP interconnectivity As shown in Figure 73, a VPN network involves AS 1 and AS 2. PE 3 and PE 4 are the ASBRs for AS 1 and AS 2, respectively. PE 3 and PE 4 are interconnected through their respective public network instance and treat each other as a P device. Figure 73 Multi-hop EBGP interconnectivity In the multi-hop EBGP interconnectivity approach, only one MD needs to be established for all the ASs, and public network multicast traffic between different ASs is transmitted within this MD.
• Determine the address ranges of switch-group-pools and ACL rules for MDT switchover. • Determine the switch-delay period. • Determine the switch-holddown period. Enabling IP multicast routing in a VPN instance Before you configure any MD-VPN functionality for a VPN, you must enable IP multicast routing in the VPN instance. To enable IP multicast routing in a VPN instance: Step 1. Enter system view. 2. Create a VPN instance and enter VPN instance view.
Step Command Remarks 2. Enter VPN instance view. ip vpn-instance vpn-instance-name N/A 3. Configure a share-group address and an MTI binding. multicast-domain share-group group-address binding mtunnel mtunnel-number No share-group address or MTI binding is configured. Configuring MDT switchover parameters In some cases, the traffic rate of the customer network multicast data might fluctuate around the MDT switchover threshold.
the logging information. For more information about the configuration of the information center, see Network Management and Monitoring Configuration Guide. Configuration procedure To enable the switch-group reuse logging: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VPN instance view. ip vpn-instance vpn-instance-name N/A 3. Enable the switch-group reuse logging. multicast-domain log switch-group-reuse Disabled by default.
Configuring a BGP MDT route reflector BGP MDT peers in the same AS must be fully meshed to maintain connectivity. However, when many BGP MDT peers exist in an AS, connection establishment among them might cause great expenses. To reduce connections between them, you can configure one of them as a route reflector and specify other routers as clients. The clients establish BGP MDT connections with the route reflector, and the route reflector forwards (reflects) BGP MDT routing information between clients.
• Configure the same PIM mode (PIM-SM, BIDIR-PIM, or PIM-SSM) in the multicast source's VPN and the receivers' VPNs. • Determine the IP addresses of the multicast source and RP, and their home VPN instances. Configuration procedure If the receivers and the multicast source are in different VPNs, configure the IP addresses of both the multicast source and RP as the source IP address. This allows multicast across VPNs in the VPN instance views of the receivers on the receiver-side PE.
Task Command Remarks Display BGP MDT routing information. display bgp mdt { all | route-distinguisher route-distinguisher } routing-table [ ip-address [ mask | mask-length ] ] [ | { begin | exclude | include } regular-expression ] Available in any view. Reset BGP MDT connections. reset bgp mdt { as-number | ip-address | all | external | group group-name | internal } Available in user view. Multicast VPN configuration examples This section provides examples of configuring multicast VPN.
Item Network requirements • Enable PIM-SM on all interfaces of the P router. • Enable PIM-SM on all public and private network interfaces of PE 1, PE 2, and PE 3. • Enable PIM-SM on all interfaces of CE a1, CE a2, CE a3, CE b1, and CE b2. PIM • Configure Loopback 1 of P as a public network C-BSR and C-RP (to work for all multicast groups). • Configure Loopback 1 of CE a2 as a C-BSR and a C-RP for VPN a (to work for all multicast groups).
PE 2 GE2/1/3 10.110.2.1/24 GE2/1/2 10.110.5.2/24 Loop1 1.1.1.1/32 GE2/1/3 10.110.12.2/24 GE2/1/1 192.168.7.1/24 GE2/1/1 10.110.8.1/24 GE2/1/2 10.110.3.1/24 GE2/1/2 10.110.3.2/24 GE2/1/3 10.110.4.1/24 GE2/1/1 10.110.11.1/24 Loop1 1.1.1.2/32 GE2/1/2 10.110.6.2/24 CE b1 CE b2 Configuration procedure 1. Configure PE 1: # Configure a Router ID, enable IP multicast routing on the public network, configure an MPLS LSR ID, and enable the LDP capability.
# Bind GigabitEthernet 2/1/3 with VPN instance a, configure an IP address and enable PIM-SM on the interface. [PE1] interface gigabitethernet 2/1/3 [PE1-GigabitEthernet2/1/3] ip binding vpn-instance a [PE1-GigabitEthernet2/1/3] ip address 10.110.2.1 24 [PE1-GigabitEthernet2/1/3] pim sm [PE1-GigabitEthernet2/1/3] quit # Configure an IP address for Loopback 1, and enable PIM-SM. [PE1] interface loopback 1 [PE1-LoopBack1] ip address 1.1.1.1 32 [PE1-LoopBack1] pim sm [PE1-LoopBack1] quit # Configure BGP.
system-view [PE2] router id 1.1.1.2 [PE2] multicast routing-enable [PE2] mpls lsr-id 1.1.1.2 [PE2] mpls [PE2-mpls] quit [PE2] mpls ldp [PE2-mpls-ldp] quit # Create VPN instance b, configure an RD for it, and create an ingress route and an egress route for it.
# Bind GigabitEthernet 2/1/3 with VPN instance a, configure an IP address and enable PIM-SM on the interface. [PE2] interface gigabitethernet 2/1/3 [PE2-GigabitEthernet2/1/3] ip binding vpn-instance a [PE2-GigabitEthernet2/1/3] ip address 10.110.4.1 24 [PE2-GigabitEthernet2/1/3] pim sm [PE2-GigabitEthernet2/1/3] quit # Configure an IP address for Loopback 1, and enable PIM-SM. [PE2] interface loopback 1 [PE2-LoopBack1] ip address 1.1.1.2 32 [PE2-LoopBack1] pim sm [PE2-LoopBack1] quit # Configure BGP.
# Configure RIP. [PE2] rip 2 vpn-instance a [PE2-rip-2] network 10.0.0.0 [PE2-rip-2] import-route bgp [PE2-rip-2] quit [PE2] rip 3 vpn-instance b [PE2-rip-3] network 10.0.0.0 [PE2-rip-3] import-route bgp [PE2-rip-3] return 3. Configure PE 3: # Configure a Router ID, enable IP multicast routing on the public network, configure an MPLS LSR ID, and enable the LDP capability. system-view [PE3] router id 1.1.1.3 [PE3] multicast routing-enable [PE3] mpls lsr-id 1.1.1.
[PE3-GigabitEthernet2/1/1] ip address 192.168.8.1 24 [PE3-GigabitEthernet2/1/1] pim sm [PE3-GigabitEthernet2/1/1] mpls [PE3-GigabitEthernet2/1/1] mpls ldp [PE3-GigabitEthernet2/1/1] quit # Bind GigabitEthernet 2/1/2 with VPN instance a, configure an IP address and enable PIM-SM on the interface. [PE3] interface gigabitethernet 2/1/2 [PE3-GigabitEthernet2/1/2] ip binding vpn-instance a [PE3-GigabitEthernet2/1/2] ip address 10.110.5.
[PE3-bgp-b] import-route rip 3 [PE3-bgp-b] import-route direct [PE3-bgp-b] quit [PE3–bgp] ipv4-family vpnv4 [PE3–bgp-af-vpnv4] peer vpn-g enable [PE3-bgp-af-vpnv4] peer 1.1.1.1 group vpn-g [PE3–bgp-af-vpnv4] peer 1.1.1.2 group vpn-g [PE3–bgp-af-vpnv4] quit [PE3–bgp] quit The interface MTI 0 will automatically obtain an IP address after BGP peer configuration on PE 3. This address is the loopback interface address specified in the BGP peer configuration.
[P-GigabitEthernet2/1/1] ip address 192.168.6.2 24 [P-GigabitEthernet2/1/1] pim sm [P-GigabitEthernet2/1/1] mpls [P-GigabitEthernet2/1/1] mpls ldp [P-GigabitEthernet2/1/1] quit # Configure an IP address, enable PIM-SM and LDP capability on the public network interface GigabitEthernet 2/1/2. [P] interface gigabitethernet 2/1/2 [P-GigabitEthernet2/1/2] ip address 192.168.7.
[CEa1-GigabitEthernet2/1/2] ip address 10.110.2.2 24 [CEa1-GigabitEthernet2/1/2] pim sm [CEa1-GigabitEthernet2/1/2] quit # Configure RIP. [CEa1] rip 2 [CEa1-rip-2] network 10.0.0.0 6. Configure CE b1: # Enable IP multicast routing. system-view [CEb1] multicast routing-enable # Configure an IP address and enable PIM-SM on GigabitEthernet 2/1/1. [CEb1] interface gigabitethernet 2/1/1 [CEb1-GigabitEthernet2/1/1] ip address 10.110.8.
[CEa2-LoopBack1] pim sm [CEa2-LoopBack1] quit # Configure Loopback 1 as a BSR and RP for VPN a. [CEa2] pim [CEa2-pim] c-bsr loopback 1 [CEa2-pim] c-rp loopback 1 [CEa2-pim] quit # Configure RIP. [CEa2] rip 2 [CEa2-rip-2] network 10.0.0.0 [CEa2-rip-2] network 22.0.0.0 8. Configure CE a3: # Enable IP multicast routing. system-view [CEa3] multicast routing-enable # Configure an IP address, and enable IGMP and PIM-SM on GigabitEthernet 2/1/1.
[CEb2-GigabitEthernet2/1/2] ip address 10.110.6.2 24 [CEb2-GigabitEthernet2/1/2] pim sm [CEb2-GigabitEthernet2/1/2] quit # Configure RIP. [CEb2] rip 3 [CEb2-rip-3] network 10.0.0.0 10. Verify the configuration: # Display the local share-group information of VPN instance a on PE 1. display multicast-domain vpn-instance a share-group local MD local share-group information for VPN-Instance: a Share-group: 239.1.1.1 MTunnel address: 1.1.1.
Item Network requirements • PE 1—GigabitEthernet 2/1/2 belongs to VPN instance a. GigabitEthernet 2/1/3 belongs to VPN instance b. Ethernet 1/1 and Loopback 1 belong to the public network instance. PE interfaces and VPN instances they belong to • PE 2—GigabitEthernet 2/1/1, GigabitEthernet 2/1/2, Loopback 1 and Loopback 2 belong to the public network instance. • PE 3—GigabitEthernet 2/1/1, GigabitEthernet 2/1/2, Loopback 1 and Loopback 2 belong to the public network instance.
Figure 75 Network diagram Lo op 1 Lo op 2 1 op Lo Lo op 2 Device Interface IP address Device Interface IP address S1 — 10.11.5.2/24 R1 — 10.11.8.2/24 S2 — 10.11.6.2/24 R2 — 10.11.7.2/24 PE 1 GE2/1/1 10.10.1.1/24 PE 3 GE2/1/1 10.10.2.1/24 GE2/1/2 10.11.1.1/24 GE2/1/2 192.168.1.2/24 GE2/1/3 10.11.2.1/24 Loop1 1.1.1.3/32 Loop1 1.1.1.1/32 Loop2 22.22.22.22/32 PE 2 CE a1 CE a2 GE2/1/1 10.10.1.2/24 GE2/1/1 10.10.2.2/24 GE2/1/2 192.168.1.1/24 PE 4 GE2/1/2 10.11.
[PE1-mpls] quit [PE1] mpls ldp [PE1-mpls-ldp] quit # Create VPN instance a, configure an RD for it, and create an ingress route and an egress route for it. Enable IP multicast routing in VPN instance a, configure a share-group address, associate an MTI with the VPN instance, and define the switch-group-pool address range.
[PE1] interface loopback 1 [PE1-LoopBack1] ip address 1.1.1.1 32 [PE1-LoopBack1] pim sm [PE1-LoopBack1] quit # Configure BGP. [PE1] bgp 100 [PE1-bgp] group pe1-pe2 internal [PE1-bgp] peer pe1-pe2 label-route-capability [PE1-bgp] peer pe1-pe2 connect-interface loopback 1 [PE1-bgp] peer 1.1.1.2 group pe1-pe2 [PE1-bgp] group pe1-pe4 external [PE1-bgp] peer pe1-pe4 as-number 200 [PE1-bgp] peer pe1-pe4 ebgp-max-hop 255 [PE1-bgp] peer 1.1.1.
[PE1-ospf-3-area-0.0.0.0] quit [PE1-ospf-3] quit 2. Configure PE 2: # Configure a Router ID, enable IP multicast routing on the public network, configure an MPLS LSR ID, and enable the LDP capability. system-view [PE2] router id 1.1.1.2 [PE2] multicast routing-enable [PE2] mpls lsr-id 1.1.1.2 [PE2] mpls [PE2-mpls] quit [PE2] mpls ldp [PE2-mpls-ldp] quit # Configure an IP address, and enable PIM-SM and LDP capability on the public network interface GigabitEthernet 2/1/1.
# Establish an MSDP peering relationship. [PE2] msdp [PE2-msdp] encap-data-enable [PE2-msdp] peer 1.1.1.3 connect-interface loopback 1 # Configure a static route. [PE2] ip route-static 1.1.1.3 32 gigabitethernet 2/1/2 192.168.1.2 # Configure BGP. [PE2] bgp 100 [PE2-bgp] import-route ospf 1 [PE2-bgp] group pe2-pe1 internal [PE2-bgp] peer pe2-pe1 route-policy map2 export [PE2-bgp] peer pe2-pe1 label-route-capability [PE2-bgp] peer pe2-pe1 connect-interface loopback 1 [PE2-bgp] peer 1.1.1.
[PE3-mpls-ldp] quit # Configure an IP address, and enable PIM-SM and LDP capability on the public network interface GigabitEthernet 2/1/1. [PE3] interface gigabitethernet 2/1/1 [PE3-GigabitEthernet2/1/1] ip address 10.10.2.1 24 [PE3-GigabitEthernet2/1/1] pim sm [PE3-GigabitEthernet2/1/1] mpls [PE3-GigabitEthernet2/1/1] mpls ldp [PE3-GigabitEthernet2/1/1] quit # Configure an IP address, and enable PIM-SM and MPLS on the public network interface GigabitEthernet 2/1/2.
[PE3-bgp] peer pe3-pe4 connect-interface loopback 1 [PE3-bgp] peer 1.1.1.4 group pe3-pe4 [PE3-bgp] group pe3-pe2 external [PE3-bgp] peer pe3-pe2 as-number 100 [PE3-bgp] peer pe3-pe2 route-policy map1 export [PE3-bgp] peer pe3-pe2 label-route-capability [PE3-bgp] peer pe3-pe2 connect-interface loopback 1 [PE3-bgp] peer 1.1.1.2 group pe3-pe2 [PE3–bgp] quit # Configure OSPF. [PE3] ospf 1 [PE3-ospf-1] area 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 1.1.1.3 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 22.22.22.
# Create VPN instance b, configure an RD for it, and create an ingress route and an egress route for it. Enable IP multicast routing in VPN instance b, configure a share-group address, associate an MTI with the VPN instance, and define the switch-group-pool address range.
[PE4-bgp] peer pe4-pe1 connect-interface loopback 1 [PE4–bgp] ipv4-family vpn-instance a [PE4-bgp-a] import-route ospf 2 [PE4-bgp-a] import-route direct [PE4-bgp-a] quit [PE4–bgp] ipv4-family vpn-instance b [PE4-bgp-b] import-route ospf 3 [PE4-bgp-b] import-route direct [PE4-bgp-b] quit [PE4–bgp] ipv4-family vpnv4 [PE4–bgp-af-vpnv4] peer 1.1.1.
[CEa1-GigabitEthernet2/1/2] ip address 10.11.1.2 24 [CEa1-GigabitEthernet2/1/2] pim sm [CEa1-GigabitEthernet2/1/2] quit # Configure an IP address for Loopback 1, and enable PIM-SM. [CEa1] interface loopback 1 [CEa1-LoopBack1] ip address 2.2.2.2 32 [CEa1-LoopBack1] pim sm [CEa1-LoopBack1] quit # Configure Loopback 1 as a C-BSR and a C-RP for VPN a. [CEa1] pim [CEa1-pim] c-bsr loopback 1 [CEa1-pim] c-rp loopback 1 [CEa1-pim] quit # Configure OSPF. [CEa1] ospf 1 [CEa1-ospf-1] area 0.0.0.
[CEa2-GigabitEthernet2/1/1] ip address 10.11.7.1 24 [CEa2-GigabitEthernet2/1/1] igmp enable [CEa2-GigabitEthernet2/1/1] pim sm [CEa2-GigabitEthernet2/1/1] quit # Configure an IP address and enable PIM-SM on GigabitEthernet 2/1/2. [CEa2] interface gigabitethernet 2/1/2 [CEa2-GigabitEthernet2/1/2] ip address 10.11.3.2 24 [CEa2-GigabitEthernet2/1/2] pim sm [CEa2-GigabitEthernet2/1/2] quit # Configure OSPF. [CEa2] ospf 1 [CEa2-ospf-1] area 0.0.0.0 [CEa2-ospf-1-area-0.0.0.0] network 10.11.0.0 0.0.255.
[CEb2-ospf-1] quit 9. Verify the configuration: # Display the local share-group information of VPN instance a on PE 1. display multicast-domain vpn-instance a share-group local MD local share-group information for VPN-Instance: a Share-group: 239.1.1.1 MTunnel address: 1.1.1.1 # Display the local share-group information of VPN instance b on PE 1. display multicast-domain vpn-instance b share-group local MD local share-group information for VPN-Instance: b Share-group: 239.4.4.
Solution 1. Use the display multicast-domain vpn-instance share-group command to verify that the same share-group address has been configured for the same VPN instance on different PE devices. 2. Use the display pim interface command to verify that PIM is enabled on at least one interface of the same VPN on different PE devices and the same PIM mode is running on all the interfaces of the same VPN instance on different PE devices and on all the interfaces of the P router. 3.
Configuring IPv6 multicast routing and forwarding Overview In IPv6 multicast implementations, the following types of tables implement multicast routing and forwarding: • Multicast routing table of an IPv6 multicast routing protocol—Each IPv6 multicast routing protocol has its own multicast routing table, such as the IPv6 PIM routing table. • General IPv6 multicast routing table—The multicast routing information of different IPv6 multicast routing protocols forms a general IPv6 multicast routing table.
2. The router selects one of the optimal routes as the RPF route according to the following principles: { { If the router uses the longest match principle, it selects the longest matching route as the RPF route. If the routes have the same prefix length, the router selects the route that has a higher priority as the RPF route. If the routes have the same priority, the router selects the IPv6 MBGP route as the RPF route.
Figure 76 RPF check process IPv6 Routing Table on Router C Destination/Prefix Interface 2000::/16 POS5/1/1 Router B Receiver POS5/1/0 Source 2000::101/16 Router A POS5/1/1 IPv6 Multicast packets POS5/1/0 Receiver Router C When POS 5/1/1 of Router C receives an IPv6 multicast packet, because the interface is the incoming interface of the (S, G) entry, the router forwards the packet to all outgoing interfaces.
across the GRE tunnel through unicast routers. Then, Router B strips off the unicast IPv6 header and continues to forward the IPv6 multicast data down toward the receivers. Configuration task list Task Remarks Enabling IPv6 multicast routing Required. Configuring IPv6 multicast routing and forwarding Configuring an IPv6 multicast routing policy Optional. Configuring an IPv6 multicast forwarding range Optional. Configuring the IPv6 multicast forwarding table size Optional.
To configure an IPv6 multicast routing policy: Step Command Remarks system-view N/A 1. Enter system view. 2. Configure the device to select the RPF route based on the longest match. multicast ipv6 longest-match The route with the highest priority is selected as the RPF route by default. Configure IPv6 multicast load splitting. multicast ipv6 load-splitting {source | source-group } Optional. 3. Optional. Disabled by default.
When the router forwards IPv6 multicast data, it replicates a copy of the IPv6 multicast data for each downstream node and forwards the data. Each of these downstream nodes is a branch of the IPv6 multicast distribution tree. You can configure the maximum number of downstream nodes (namely, the maximum number of outgoing interfaces) for a single entry in the IPv6 multicast forwarding table to lessen the burden on the router for replicating IPv6 multicast traffic.
Step 1. Enter system view. Command Remarks system-view N/A • Enter Ethernet interface/Layer 2 2. Enter Ethernet interface/Layer 2 aggregate interface view or port group view. aggregate interface view: interface interface-type interface-number • Enter port group view: port-group manual port-group-name In Ethernet interface view or Layer 2 aggregate interface view, the configuration is effective on only the current interface.
Task Command Remarks Display information about the IPv6 multicast routing table. display multicast ipv6 routing-table [ ipv6-source-address [ prefix-length ] | ipv6-group-address [ prefix-length ] | incoming-interface { interface-type interface-number | register } | outgoing-interface { { exclude | include | match } { interface-type interface-number | register } } ] * [ | { begin | exclude | include } regular-expression ] Available in any view.
Figure 78 Network diagram IPv6 multicast router Router A GE2/1/2 2001::1/64 GE2/1/1 1001::1/64 IPv6 unicast router Router B GE2/1/1 2001::2/64 GE2/1/2 3001::1/64 IPv6 multicast router Router C GE2/1/2 3001::2/64 GRE tunnel Tunnel0 5001::1/64 Tunnel0 5001::2/64 Source GE2/1/1 4001::1/64 Receiver 4001::100/64 1001::100/64 Configuration procedure 1. Enable IPv6 forwarding and configure the IP address and prefix length for each interface as shown in Figure 78. (Details not shown.) 2.
[RouterA-Gigabitethernet2/1/1] ospfv3 1 area 0 [RouterA-Gigabitethernet2/1/1] quit [RouterA] interface gigabitethernet 2/1/2 [RouterA-Gigabitethernet2/1/2] ospfv3 1 area 0 [RouterA-Gigabitethernet2/1/2] quit [RouterA] interface tunnel 0 [RouterA-Tunnel0] ospfv3 1 area 0 [RouterA-Tunnel0] quit # Configure OSPFv3 on Router B. system-view [RouterB] ospfv3 1 [RouterB-ospfv3-1] router-id 2.2.2.
[RouterC] interface gigabitethernet 2/1/1 [RouterC-Gigabitethernet2/1/1] mld enable [RouterC-Gigabitethernet2/1/1] pim ipv6 dm [RouterC-Gigabitethernet2/1/1] quit [RouterC] interface gigabitethernet 2/1/2 [RouterC-Gigabitethernet2/1/2] pim ipv6 dm [RouterC-Gigabitethernet2/1/2] quit [RouterC] interface tunnel 0 [RouterC-Tunnel0] pim ipv6 dm [RouterC-Tunnel0] quit Verifying the configuration The source sends the IPv6 multicast data to the IPv6 multicast group FF1E::101 and the receiver can receive the IPv6
Troubleshooting abnormal termination of IPv6 multicast data Symptom • A host sends an MLD report announcing its joining an IPv6 multicast group (G). However, no member information about the IPv6 multicast group (G) exists on the intermediate router. The intermediate router can receive IPv6 multicast packets successfully, but the packets cannot reach the stub network.
Configuring MLD Overview An IPv6 router uses the MLD protocol to discover the presence of multicast listeners on the directly attached subnets. Multicast listeners are nodes wishing to receive IPv6 multicast packets. Through MLD, the router can learn whether any IPv6 multicast listeners exist on the directly connected subnets, put corresponding records in the database, and maintain timers related to IPv6 multicast addresses.
Joining an IPv6 multicast group Figure 79 MLD queries and reports IPv6 network Querier Router A Router B Ethernet Host A (G2) Host B (G1) Host C (G1) Query Report Assume that Host B and Host C will receive IPv6 multicast data addressed to IPv6 multicast group G1, and Host A will receive IPv6 multicast data addressed to G2, as shown in Figure 79.
1. The host sends an MLD done message to all IPv6 multicast routers on the local subnet. The destination address is FF02::2. 2. After receiving the MLD done message, the querier sends a configurable number of multicast-address-specific queries to the group that the host is leaving. The destination address field and group address field of the message are both filled with the address of the IPv6 multicast group that is being queried. 3.
When MLDv2 is running on the hosts and routers, Host B can explicitly express its interest in the IPv6 multicast data that Source 1 sends to G (denoted as (S1, G)), rather than the IPv6 multicast data that Source 2 sends to G (denoted as (S2, G)). Thus, only IPv6 multicast data from Source 1 will be delivered to Host B. MLD state A multicast router that is running MLDv2 maintains the multicast address state per multicast address per attached subnet.
Figure 81 MLDv2 query message format 3 4 0 7 Type = 130 15 31 Code Checksum Maximum Response Delay Reserved Multicast Address (128 bits) Reserved S QRV 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 Message type. For a query message, this field is set to 130. Code Initialized to zero. Checksum Standard IPv6 checksum.
Field Description • This field is set to 0 in a general query message or a Number of Sources multicast-address-specific query message. • This field represents the number of source addresses in a multicast-address-and-source-specific query message. Source Address( i ) IPv6 multicast source address in a multicast-address-specific query message (i = 1, 2, .., n, where n represents the number of multicast source addresses.
MLD SSM mapping The MLD SSM mapping feature enables you to configure static MLD SSM mappings on the last-hop router to provide SSM support for receiver hosts that are running MLDv1. The SSM model assumes that the last-hop router has identified the desired IPv6 multicast sources when receivers join IPv6 multicast groups. • When a host that runs MLDv2 joins a multicast group, it can explicitly specify one or more multicast sources in its MLDv2 report.
MLD proxying In some simple tree-shaped topologies, you do not need to configure complex IPv6 multicast routing protocols, such as IPv6 PIM, on the boundary devices. Instead, you can configure MLD proxying on these devices. With MLD proxying configured, the device serves as a proxy for the downstream hosts to send MLD messages, maintain group memberships, and implement IPv6 multicast forwarding based on the memberships.
• RFC 4605, Internet Group Management Protocol (IGMP)/Multicast Listener Discovery (MLD)-Based Multicast Forwarding ("IGMP/MLD Proxying") MLD configuration task list For the configuration tasks in this section, the following rules apply: • In MLD view, the configuration is effective globally. In interface view, the configuration is effective on only the current interface. • The configurations made in interface view take precedence over those in MLD view.
• Determine the IPv6 multicast group address and IPv6 multicast source address for static group member configuration. • Determine the ACL rule for IPv6 multicast group filtering. • Determine the maximum number of IPv6 multicast groups that an interface can join. Enabling MLD Enable MLD on the interface on which IPv6 multicast group memberships will be created and maintained. To enable MLD: Step Command Remarks 1. Enter system view. system-view N/A 2. Enable IPv6 multicast routing.
Configuring static joining After an interface is configured as a static member of an IPv6 multicast group or an IPv6 multicast source and group, it 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.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Configure the maximum number of IPv6 multicast groups that the interface can join. mld group-limit limit The default value is 1024. Adjusting MLD performance For the configuration tasks in this section, the following rules apply: • The configurations made in MLD view are effective on all interfaces.
To enhance device performance, avoid unnecessary costs, and ensure protocol security, configure the device to discard MLD messages that do not carry the Router-Alert option. • Configuring Router-Alert option handling methods globally Step Command Remarks 1. Enter system view. system-view N/A 2. Enter MLD view. mld N/A 3. Configure the interface to discard any MLD message without the Router-Alert option.
advertised in the MLD query message. When the timer decreases to 0, the host sends an MLD membership report message to the IPv6 multicast group. To speed up the response of hosts to MLD queries and avoid simultaneous timer expirations causing MLD report traffic bursts, you must correctly set the maximum response delay: • For MLD general queries, the maximum response delay is set by the max-response-time command.
Step 9. Configure the MLD other querier present interval. Command Remarks timer other-querier-present interval By default, the other querier present interval is determined by the formula "Other querier present interval (in seconds) = [ MLD query interval ] × [ MLD querier's robustness variable ] + [ maximum response delay for MLD general query ] / 2". Configuring MLD query and response parameters on an interface Step Command Remarks 1. Enter system view. system-view N/A 2.
frequently from one IPv6 multicast group to another, you can enable MLD fast-leave processing on the MLD querier. When fast-leave processing is enabled, after receiving an MLD done message from a host, the MLD querier sends a leave notification to the upstream immediately without first sending MLD multicast-address-specific queries. In this way, the leave latency is reduced on one hand, and the network bandwidth is saved on the other hand.
Step Enable the MLD host tracking function on the interface. 3. Command Remarks mld host-tracking Disabled by default. Configuring MLD SSM mapping For some certain restrictions, some receiver hosts on an SSM network might run MLDv1. To provide SSM service support for these receiver hosts, configure the MLD SSM mapping feature on the last-hop router.
Configuring MLD proxying This section describes how to configure MLD proxying. Configuration prerequisites Before you configure the MLD proxying feature, complete the following tasks: • Enable IPv6 forwarding and configure an IPv6 unicast routing protocol so that all devices in the domain are interoperable at the network layer. • Enable IPv6 multicast routing.
To enable IPv6 multicast forwarding on a downstream interface Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Enable IPv6 multicast forwarding on a non-querier downstream interface. mld proxying forwarding Disabled by default. Displaying and maintaining MLD CAUTION: The reset mld group command might cause IPv6 multicast transmission failures.
Task Command Remarks Display information about the hosts that join based on the MLD SSM mappings on an interface. display mld ssm-mapping host interface interface-type interface-number group ipv6-group-address source ipv6-source-address [ | { begin | exclude | include } regular-expression ] Available in any view. Remove the dynamic group entries of a specified MLD group or all MLD groups.
Figure 85 Network diagram Receiver IPv6 PIM network Host A POS5/1/0 Router A Querier POS5/1/0 GE2/1/1 3000::12/64 N1 Host B GE2/1/1 3001::10/64 Receiver Host C Router B GE2/1/1 3001::12/64 POS5/1/0 N2 Host D Router C Configuration procedure 1. Enable IPv6 forwarding on each router and assign an IPv6 address and prefix length to each interface according to Figure 85. (Details not shown.) 2.
[RouterB-Pos5/1/0] quit # Enable IPv6 multicast routing on Router C, enable IPv6 PIM-DM on each interface, and enable MLD on the host-side interface GigabitEthernet 2/1/1. system-view [RouterC] multicast ipv6 routing-enable [RouterC] interface gigabitethernet 2/1/1 [RouterC-GigabitEthernet2/1/1] mld enable [RouterC-GigabitEthernet2/1/1] pim ipv6 dm [RouterC-GigabitEthernet2/1/1] quit [RouterC] interface pos 5/1/0 [RouterC-Pos5/1/0] pim ipv6 dm [RouterC-Pos5/1/0] quit 4.
Figure 86 Network diagram Source 2 Router B GE2/1/1 Source 3 Router C GE2/1/3 GE2/1/2 GE2/1/3 GE2/1/1 GE2/1/2 IPv6 PIM-SM Source 1 GE2/1/2 GE2/1/1 Receiver GE2/1/2 GE2/1/3 GE2/1/3 Router A GE2/1/1 Router D Device Interface IPv6 address Device Interface IPv6 address Source 1 — 1001::1/64 Source 3 — 3001::1/64 Source 2 — 2001::1/64 Receiver — 4001::1/64 Router A GE2/1/1 1001::2/64 Router C GE2/1/1 3001::2/64 GE2/1/2 1002::1/64 GE2/1/2 3002::1/64 GE2/1/3 1003::1/64
# Enable IPv6 multicast routing on Router A, and enable IPv6 PIM-SM on each interface.
Total 1 MLD SSM-mapping Group reported Group Address: FF3E::101 Last Reporter: 4001::1 Uptime: 00:02:04 Expires: off # Display IPv6 PIM routing table information on Router D.
Figure 87 Network diagram Configuration procedure 1. Enable IPv6 forwarding on each router and assign an IPv6 address and prefix length to each interface according to Figure 87. (Details not shown.) 2. Enable IPv6 multicast routing, IPv6 PIM-DM, MLD, and MLD proxying: # Enable IPv6 multicast routing on Router A, IPv6 PIM-DM on Serial 3/1/1, and MLD on GigabitEthernet 2/1/1.
Current MLD version is 1 Multicast routing on this interface: enabled Require-router-alert: disabled # Display MLD group information on Router A. [RouterA] display mld group Total 1 MLD Group(s).
restrict the host from joining IPv6 multicast group G, the ACL must be modified to allow IPv6 multicast group G to receive report messages. Membership information is inconsistent on the routers on the same subnet Symptom The MLD routers on the same subnet have different membership information. Analysis • A router running MLD maintains multiple parameters for each interface, and these parameters influence one another, forming very complicated relationships.
Configuring IPv6 PIM Overview IPv6 PIM provides IPv6 multicast forwarding by leveraging IPv6 unicast static routes or IPv6 unicast routing tables generated by any IPv6 unicast routing protocol, such as RIPng, OSPFv3, IS-ISv6, or BGP4+. IPv6 PIM uses an IPv6 unicast routing table to perform RPF check to implement IPv6 multicast forwarding.
Assert • Neighbor discovery In an IPv6 PIM domain, a PIM router discovers IPv6 PIM neighbors, maintains IPv6 PIM neighboring relationship with other routers, and builds and maintains SPTs by periodically multicasting IPv6 PIM hello messages to all other IPv6 PIM routers on the local subnet. Every IPv6 PIM enabled interface on a router sends hello messages periodically, and, therefore, learns the IPv6 PIM neighboring information pertinent to the interface.
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 IPv6 PIM-SM. Graft When a host attached to a pruned node 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.
The assert message contains the multicast source address (S), the multicast group address (G), and the preference and metric of the IPv6 unicast route/IPv6 MBGP route/IPv6 multicast static route to the source. 3. The routers compare these parameters, and either Router A or Router B becomes the unique forwarder of the subsequent (S, G) IPv6 multicast packets on the shared-media subnet. The comparison process is as follows: a. The router with a higher preference to the source wins. b.
• Switchover to SPT • Assert Neighbor discovery IPv6 PIM-SM uses the similar neighbor discovery mechanism as IPv6 PIM-DM does. For more information, see "Neighbor discovery." DR election IPv6 PIM-SM also uses hello messages to elect a DR for a shared-media network (such as a LAN). The elected DR will be the only IPv6 multicast forwarder on this shared-media network. In the case of a shared-media network, a DR must be elected, no matter this network connects to IPv6 multicast sources or to receivers.
specified on each router in the IPv6 PIM-SM domain. An RP can serve multiple IPv6 multicast groups, but a given IPv6 multicast group can have only one RP to serve it at a time. In most cases, however, an IPv6 PIM-SM network covers a wide area and a huge amount of IPv6 multicast traffic must be forwarded through the RP. To lessen the RP burden and optimize the topological structure of the RPT, you can configure multiple C-RPs in an IPv6 PIM-SM domain.
Value Description G The digest from the exclusive-or (XOR) operation between the 32-bit segments of the IPv6 multicast group address. For example, if the IPv6 multicast address is FF0E:C20:1A3:63::101, G = 0xFF0E0C20 XOR 0x01A30063 XOR 0x00000000 XOR 0x00000101. M Hash mask length. Ci The digest from the exclusive-or (XOR) operation between the 32-bit segments of the C-RP IPv6 address.
As shown in Figure 92, the process of building an RPT is as follows: 1. When a receiver joins the IPv6 multicast group G, it uses an MLD report message to inform the directly connected DR. 2. After getting the IPv6 multicast group G's receiver information, the DR sends a join message, which is forwarded hop-by-hop to the RP that corresponds to the multicast group. 3. The routers along the path from the DR to the RP form an RPT branch.
c. Sends an (S, G) join message hop-by-hop toward the IPv6 multicast source. The routers along the path from the RP to the IPv6 multicast source form an SPT branch. Each router on this branch generates an (S, G) entry in its forwarding table. The source-side DR is the root of the SPT, and the RP is the leaf of the SPT. 4. The subsequent IPv6 multicast data from the IPv6 multicast source travels along the established SPT to the RP. Then, the RP forwards the data along the RPT to the receivers.
Assert IPv6 PIM-SM uses a similar assert mechanism as IPv6 PIM-DM does. For more information, see "Assert." IPv6 BIDIR-PIM overview In some many-to-many applications, such as multi-side video conference, there might be multiple receivers interested in multiple IPv6 multicast sources simultaneously. With IPv6 PIM-DM or IPv6 PIM-SM, each router along the SPT must create an (S, G) entry for each IPv6 multicast source, consuming a lot of system resources. IPv6 BIDIR-PIM is introduced to address this problem.
Figure 94 DF election Router E Router D RP Router B Router C Ethernet DF election message IPv6 Multicast packets Router A Source As shown in Figure 94, 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.
Figure 95 RPT building at the receiver side As shown in Figure 95, the process for building a receiver-side RPT is similar to that for building an RPT in IPv6 PIM-SM: 1. When a receiver joins IPv6 multicast group G, it uses an MLD message to inform the directly connected router. 2. After getting the receiver information, the router sends a join message, which is forwarded hop-by-hop to the RP of the IPv6 multicast group. 3.
Figure 96 RPT building at the multicast source side As shown in Figure 96, the process of building a source-side RPT is relatively simple: 4. 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. 5. The routers along the path from the source's directly connected router to the RP form an RPT branch. Each router on this branch adds a (*, G) entry to its forwarding table.
cannot cross the IPv6 admin-scope zone boundary. IPv6 multicast group ranges served by different IPv6 admin-scope zones can overlap. An IPv6 multicast group is valid only within its local IPv6 admin-scope zone, functioning as a private group address. The IPv6 global scope zone maintains a BSR, which serves the IPv6 multicast groups with the Scope field in their group addresses being 14.
Figure 98 IPv6 multicast address format An IPv6 admin-scoped zone with a larger scope field value contains an IPv6 admin-scoped zone with a smaller scope field value. The zone with the scope field value of E is the IPv6 global-scoped zone. Table 13 lists the possible values of the scope field. Table 13 Values of the Scope field Value Meaning Remarks 0, F Reserved N/A 1 Interface-local scope N/A 2 Link-local scope N/A 3 Subnet-local scope IPv6 admin-scope zone.
Neighbor discovery IPv6 PIM-SSM uses the same neighbor discovery mechanism as in IPv6 PIM-SM. For more information, see "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 is in the IPv6 SSM group range.
Relationship 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, which one is chosen for a receiver trying to join a group depends, as shown in Figure 100. For more information about MLD SSM mapping, see "Configuring MLD." Figure 100 Relationship among IPv6 PIM protocols A receiver joins IPv6 multicast group G.
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 common IPv6 PIM features Optional. Configuration prerequisites Before you configure IPv6 PIM-DM, complete the following tasks: • Enable IPv6 forwarding and configure an IPv6 unicast routing protocol so that all devices in the domain are interoperable at the network layer.
To enable the state-refresh capability: Step Command Remarks 5. Enter system view. system-view N/A 6. Enter interface view. interface interface-type interface-number N/A 7. Enable the state-refresh capability. pim ipv6 state-refresh-capable Optional. Enabled by default. Configuring state refresh parameters The router directly connected with the multicast source periodically sends state-refresh messages. You can configure the interval for sending such messages.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Configure the graft retry period. pim ipv6 timer graft-retry interval Optional. 3 seconds by default. For more information about the configuration of other timers in IPv6 PIM-DM, see "Configuring common IPv6 PIM timers." Configuring IPv6 PIM-SM This section describes how to configure IPv6 PIM-SM.
• Enable IPv6 forwarding and configure an IPv6 unicast routing protocol so that all devices in the domain are interoperable at the network layer. • Determine the IP address of a static RP and the ACL rule defining the range of IPv6 multicast groups to be served by the static RP. • Determine the C-RP priority and the ACL rule defining the range of IPv6 multicast groups to be served by each C-RP.
Configuring an RP An RP can be manually configured or dynamically elected through the BSR mechanism. For a large IPv6 PIM network, static RP configuration is a tedious job. Generally, static RP configuration is just a backup method for the dynamic RP election mechanism to enhance the robustness and operation manageability of a multicast network. When both IPv6 PIM-SM and IPv6 BIDIR-PIM run on the IPv6 PIM network, do not use the same RP to serve IPv6 PIM-SM and IPv6 BIDIR-PIM.
Step 4. Command Configure a legal C-RP address range and the range of IPv6 multicast groups to be served. crp-policy acl6-number Remarks Optional. No restrictions by default. Enabling embedded RP When the embedded RP feature is enabled, the router can resolve the RP address directly from the IPv6 multicast group address of an IPv6 multicast packets. This RP can replace the statically configured RP or the RP dynamically calculated based on the BSR mechanism.
For information about the configuration of other timers in IPv6 PIM-SM, see "Configuring common IPv6 PIM timers." Configuring a BSR An IPv6 PIM-SM domain can have only one BSR, but must have at least one C-BSR. Any router can be configured as a C-BSR. Elected from C-BSRs, the BSR is responsible for collecting and advertising RP information in the IPv6 PIM-SM domain. Configuring a C-BSR You should configure C-BSRs on routers in the backbone network.
Step Command Remarks No C-BSRs are configured by default. 3. Configure an interface as a C-BSR. c-bsr ipv6-address [ hash-length [ priority ] ] 4. Configure a legal BSR address range. bsr-policy acl6-number Optional. No restrictions by default. Configuring an IPv6 PIM domain border As the administrative core of an IPv6 PIM-SM domain, the BSR sends the collected RP-set information in the form of bootstrap messages to all routers in the IPv6 PIM-SM domain.
the length of BS timeout timer, during which no BSR election occurs. If no bootstrap message is received from the BSR when the BS timeout timer expires, a new BSR election process begins among the C-BSRs. Perform the following configuration on C-BSR routers. To configure C-BSR timers: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. pim ipv6 N/A Optional. 3. Configure the BS period.
The function of BSM semantic fragmentation is enabled by default. A device that does not support this function might regard a fragment as an entire message and learns only part of the RP-set information. Therefore, if such devices exist in the IPv6 PIM-SM domain, you need to disable the semantic fragmentation function on the C-BSRs. To disable the BSM semantic fragmentation function: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. pim ipv6 N/A 3.
Step Configure an IPv6 multicast forwarding boundary. 3. Command Remarks multicast ipv6 boundary { ipv6-group-address prefix-length | scope { scope-id | admin-local | global | organization-local | site-local } } By default, no multicast forwarding boundary is configured. Configuring C-BSRs for IPv6 admin-scope zones In a network with IPv6 administrative scoping enabled, BSRs are elected from C-BSRs specific to different Scope field values.
When receivers stop receiving data addressed to a certain IPv6 multicast group through the RP (that is, the RP stops serving the receivers of that IPv6 multicast group), or when the RP starts receiving IPv6 multicast data from the IPv6 multicast source along the SPT, the RP sends a register-stop message to the source-side DR. After receiving this message, the DR stops sending register messages encapsulated with IPv6 multicast data and starts a register-stop timer.
Configuring IPv6 BIDIR-PIM This section describes how to configure IPv6 BIDIR-PIM. IPv6 BIDIR-PIM configuration task list Task Remarks Enabling IPv6 PIM-SM Required. Enabling IPv6 BIDIR-PIM Required. Configuring a static RP Configuring an RP Configuring a BSR Configuring IPv6 administrative scoping Configuring a C-RP Enabling embedded RP Required. Use any method. Configuring C-RP timers globally Optional. Configuring a C-BSR Required. Configuring an IPv6 BIDIR-PIM domain border Optional.
Determine the BS timeout timer. • Enabling IPv6 PIM-SM You must enable IPv6 PIM-SM before enabling IPv6 BIDIR-PIM because IPv6 BIDIR-PIM is implemented on the basis of IPv6 PIM-SM. To deploy an IPv6 BIDIR-PIM domain, enable IPv6 PIM-SM on all non-border interfaces of the domain. IMPORTANT: All interfaces on a device must operate in the same IPv6 PIM mode. To enable IPv6 PIM-SM: Step Command Remarks 1. Enter system view. system-view N/A 2. Enable IPv6 multicast routing.
In IPv6 BIDIR-PIM, a static RP can be specified with a virtual IPv6 address. For example, if the IPv6 addresses of the interfaces at the two ends of a link are 1001::1/64 and 1001::2/64, you can specify a virtual IPv6 address, like 1001::100/64, for the static RP. As a result, the link becomes an RPL. To make a static RP to operate correctly, you must perform this configuration on all routers in the IPv6 BIDIR-PIM domain and specify the same RP address. To configure a static RP: Step Command Remarks 1.
To enable embedded RP: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. pim ipv6 N/A Optional. Enable embedded RP. 3. embedded-rp [ acl6-number ] By default, embedded RP is enabled for IPv6 multicast groups in the default embedded RP address scopes. Configuring C-RP timers globally To enable the BSR to distribute the RP-Set information within the IPv6 BIDIR-PIM domain, C-RPs must periodically send C-RP-Adv messages to the BSR.
When a C-BSR receives the bootstrap message of another C-BSR, it first compares its own priority with the other C-BSR's priority carried in message. The C-BSR with a higher priority wins. If a tie exists in the priority, the C-BSR with a higher IPv6 address wins. The loser uses the winner's BSR address to replace its own BSR address and no longer assumes itself to be the BSR, and the winner retains its own BSR address and continues assuming itself to be the BSR.
To configure an IPv6 BIDIR-PIM domain border: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Configure an IPv6 BIDIR-PIM domain border. pim ipv6 bsr-boundary By default, no IPv6 BIDIR-PIM domain border is configured. Configuring C-BSR parameters globally In each IPv6 BIDIR-PIM domain, a unique BSR is elected from C-BSRs. The C-RPs in the IPv6 BIDIR-PIM domain send advertisement messages to the BSR.
Step Command Remarks Optional. 3. Configure the BS period. c-bsr interval interval By default, the BS period is determined by the formula "BS period = (BS timeout timer – 10) / 2". The default BS timeout timer is 130 seconds, so the default BS period is (130 – 10) / 2 = 60 (seconds). The BS period value must be smaller than the BS timeout timer. Optional. 4. Configure the BS timeout timer.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. pim ipv6 N/A 3. Disable the BSM semantic fragmentation function. undo bsm-fragment enable By default, the BSM semantic fragmentation function is enabled. Configuring IPv6 administrative scoping When administrative scoping is disabled, an IPv6 BIDIR-PIM domain has only one BSR. The BSR manages the whole network.
Configuring C-BSRs for each admin-scope zone In a network with administrative scoping enabled, group-range-specific BSRs are elected from C-BSRs. C-RPs in the network send advertisement messages to the specific BSR. The BSR summarizes the advertisement messages to form an RP-set and advertises it to all routers in the specific admin-scope zone. All the routers use the same hash algorithm to get the RP address corresponding to the specific multicast group.
• Enable IPv6 forwarding and configure an IPv6 unicast routing protocol so that all devices in the domain are interoperable at the network layer. • Determine the IPv6 SSM group range. Enabling IPv6 PIM-SM The implementation of the SSM model is based on some subsets of IPv6 PIM-SM. Therefore, you must enable IPv6 PIM-SM before configuring IPv6 PIM-SSM. When you deploy an IPv6 PIM-SSM domain, enable IPv6 PIM-SM on all non-border interfaces of routers.
Configuring common IPv6 PIM features For the configuration tasks in this section, the following rules apply: • The configurations made in IPv6 PIM view are effective on all interfaces. The configurations made in interface view are effective only on the current interface. • A configuration made in interface view always has priority over the same configuration made in IPv6 PIM view, regardless of the configuration sequence.
Configuring an IPv6 multicast data filter In either an IPv6 PIM-DM domain or an IPv6 PIM-SM domain, routers can check passing-by IPv6 multicast data based on the configured filtering rules and determine whether to continue forwarding the IPv6 multicast data. In other words, IPv6 PIM routers can act as IPv6 multicast data filters. These filters can help implement traffic control and also control the information available to downstream receivers to enhance data security.
• DR_Priority (for IPv6 PIM-SM only)—Priority for DR election. The device with the highest priority wins the DR election. You can configure this option for all the routers in a shared-media LAN that directly connects to the IPv6 multicast source or the receivers. • Holdtime—IPv6 PIM neighbor lifetime. If a router receives no hello message from a neighbor when the neighbor lifetime expires, it regards the neighbor failed or unreachable.
Configuring hello options on an interface Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Set the DR priority. pim ipv6 hello-option dr-priority priority Optional. 4. Set the neighbor lifetime. pim ipv6 hello-option holdtime interval Optional. 5. Set the prune message delay. pim ipv6 hello-option lan-delay interval Optional. 6. Set the override interval.
An IPv6 PIM router periodically sends join/prune messages to its upstream for state update. A join/prune message contains the join/prune timeout timer. The upstream router sets a join/prune timeout timer for each pruned downstream interface. 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.
Step 6. 7. Command Remarks Configure the join/prune timeout timer. pim ipv6 holdtime join-prune interval Optional. Configure assert timeout timer. pim ipv6 holdtime assert interval 210 seconds by default. Optional. 180 seconds by default. Configuring join/prune message sizes A large size of a join/prune message might result in loss of a larger amount of information if a message is lost.
Task Command Remarks Display information about unacknowledged graft messages. display pim ipv6 grafts [ | { begin | exclude | include } regular-expression ] Available in any view. Display IPv6 PIM information on an interface or all interfaces. display pim ipv6 interface [ interface-type interface-number ] [ verbose ] [ | { begin | exclude | include } regular-expression ] Available in any view. Display information about join/prune messages to send.
Figure 101 Network diagram /1 S5 PO /1 /1 S5 PO /0 Device Interface IPv6 address Device Interface IPv6 address Router A GE2/1/1 1001::1/64 Router D GE2/1/1 4001::1/64 S3/1/0 1002::1/64 S3/1/0 1002::2/64 GE2/1/1 2001::1/64 POS5/1/0 2002::2/64 POS5/1/0 2002::1/64 POS5/1/1 3001::2/64 GE2/1/1 2001::2/64 POS5/1/0 3001::1/64 Router B Router C Configuration procedure 1.
# Enable IPv6 multicast routing, IPv6 PIM-DM, and MLD on Router B and Router C in the same way. (Details not shown.) # On Router D, enable IPv6 multicast routing and enable IPv6 PIM-DM on each interface.
Total 1 (*, G) entry; 1 (S, G) entry (*, FF0E::101) Protocol: pim-dm, Flag: WC UpTime: 00:01:24 Upstream interface: NULL Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet2/1/1 Protocol: mld, UpTime: 00:01:20, Expires: never (4001::100, FF0E::101) Protocol: pim-dm, Flag: ACT UpTime: 00:01:20 Upstream interface: Serial3/1/0 Upstream neighbor: 1002::2 RPF prime neighbor: 1002::2 Downstream interface(s) information: Total num
Host A and Host C are IPv6 multicast receivers in two stub networks, N1 and N2. Both POS 5/1/0 on Router D and POS 5/1/2 on Router E act as C-BSRs and C-RPs. The C-BSR on Router E has a higher priority. The range of IPv6 multicast groups served by the C-RP is FF0E::101/64. Modify the hash mask length to map a certain number of consecutive IPv6 multicast group addresses within the range to the two C-RPs. MLDv1 runs between Router A and N1 and between Router B, Router C, and N2.
[RouterA] multicast ipv6 routing-enable [RouterA] interface gigabitethernet 2/1/1 [RouterA-GigabitEthernet2/1/1] mld enable [RouterA-GigabitEthernet2/1/1] pim ipv6 sm [RouterA-GigabitEthernet2/1/1] quit [RouterA] interface serial 3/1/0 [RouterA-Serial3/1/0] pim ipv6 sm [RouterA-Serial3/1/0] quit [RouterA] interface pos 5/1/0 [RouterA-Pos5/1/0] pim ipv6 sm [RouterA-Pos5/1/0] quit # Enable IPv6 multicast routing, IPv6 PIM-SM, and MLD on Router B and Router C in the same way. (Details not shown.
[RouterA] display pim ipv6 bsr-info Elected BSR Address: 1003::2 Priority: 20 Hash mask length: 128 State: Accept Preferred Uptime: 00:04:22 Expires: 00:01:46 # Display information about the BSR and locally configured C-RP on Router D.
Priority: 192 HoldTime: 130 Uptime: 00:05:19 Expires: 00:02:11 RP: 1003::2 Priority: 192 HoldTime: 130 Uptime: 00:05:19 Expires: 00:02:11 Assume that Host A needs to receive information addressed to IPv6 multicast group G (FF0E::100). The RP corresponding to the multicast group G is Router E as result of hash calculation, so an RPT will be built between Router A and Router E. When the multicast source S (4001::100/64) registers with the RP, an SPT will be built between Router D and Router E.
Total 0 (*, G) entry; 1 (S, G) entry (4001::100, FF0E::100) RP: 1003::2 Protocol: pim-sm, Flag: SPT LOC ACT UpTime: 00:14:44 Upstream interface: GigabitEthernet2/1/1 Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Pos5/1/0 Protocol: mld, UpTime: 00:14:44, Expires: 00:02:26 # Display IPv6 PIM routing table information on Router E.
Figure 103 Network diagram IPv6 admin-scope 1 GE2/1/1 Receiver Host A Source 1 GE2/1/1 Router G S3/1/1 Source 3 GE2/1/1 S3/1/1 S3/1/1 POS5/1/2 POS5/1/2 Router F S3/1/1 Router H S3/1/1 POS5/1/1 S3/1/1 POS5/1/1 /1 /1 S5 PO Router I /1 /1 S5 PO Router B ZBR Router A Router C ZBR Router D ZBR S3/1/1 /1 /1 E2 /2 /1 S3 G G E2 /1 /1 POS5/1/2 S3/1/2 Source 2 Receiver Host B /1 /1 S3 Receiver Host C POS5/1/1 S3/1/1 S3/1/2 GE2/1/1 Router E IPv6 PIM-SM IPv6 admin-scope 2 IPv6 globa
# Enable IPv6 multicast routing and IPv6 administrative scoping on Router A, enable IPv6 PIM-SM on each interface, and enable MLD on the host-side interface GigabitEthernet 2/1/1.
# On Router C, configure POS 5/1/1 and POS 5/1/2 as the boundary of IPv6 admin-scope zone 2. system-view [RouterC] interface pos 5/1/1 [RouterC-Pos5/1/1] multicast ipv6 boundary scope 4 [RouterC-Pos5/1/1] quit [RouterC] interface pos 5/1/2 [RouterC-Pos5/1/2] multicast ipv6 boundary scope 4 [RouterC-Pos5/1/2] quit # On Router D, configure POS 5/1/1 as the boundary of admin-scope zone 2.
Priority: 64 Hash mask length: 126 State: Elected Scope: 4 Uptime: 00:04:54 Next BSR message scheduled at: 00:00:06 Candidate BSR Address: 1002::2 Priority: 64 Hash mask length: 126 State: Elected Scope: 4 Candidate RP: 1002::2(Serial3/1/1) Priority: 192 HoldTime: 130 Advertisement Interval: 60 Next advertisement scheduled at: 00:00:15 # Display information about the BSR and locally configured C-RP on Router D.
Hash mask length: 126 State: Elected Scope: 14 Uptime: 00:01:11 Next BSR message scheduled at: 00:00:49 Candidate BSR Address: 8001::1 Priority: 64 Hash mask length: 126 State: Elected Scope: 14 Candidate RP: 8001::1(Serial3/1/1) Priority: 192 HoldTime: 130 Advertisement Interval: 60 Next advertisement scheduled at: 00:00:55 # Display RP information on Router B.
RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF5E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF6E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF7E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 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/prefix length: FFBE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFCE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFDE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFEE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFFE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 0
prefix/prefix length: FF24::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF34::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF44::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF54::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF64::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 0
Expires: 00:01:51 prefix/prefix length: FF94::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFA4::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFB4::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFC4::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFD4::/16 RP: 1002::2 Priority: 192 HoldT
Uptime: 00:03:39 Expires: 00:01:51 # Display RP information on Router F.
RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF7E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF8E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF9E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 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/prefix length: FFDE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFEE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFFE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 IPv6 BIDIR-PIM configuration example Network requirements In the IPv6 BIDIR-PIM domain shown in Figure 104, Source 1 and Source 2 send different IPv6 multicast information to IPv6 multicas
Router A Router B Router C GE2/1/1 1001::1/64 S3/1/1 1002::1/64 Router D GE2/1/1 4001::1/64 GE2/1/2 5001::1/64 GE2/1/1 2001::1/64 S3/1/1 1002::2/64 Source 1 S3/1/1 3001::2/64 - 1001::2/64 S3/1/2 2002::1/64 Source 2 - 5001::2/64 S3/1/1 S3/1/2 2002::2/64 Receiver 1 - 2001::2/64 3001::1/64 Receiver 2 - 4001::2/64 Loop0 6001::1/128 Configuration procedure 1.
system-view [RouterC] multicast ipv6 routing-enable [RouterC] interface serial 3/1/1 [RouterC-Serial3/1/1] pim ipv6 sm [RouterC-Serial3/1/1] quit [RouterC] interface serial 3/1/2 [RouterC-Serial3/1/2] pim ipv6 sm [RouterC-Serial3/1/2] quit [RouterC] interface loopback 0 [RouterC-LoopBack0] pim ipv6 sm [RouterC-LoopBack0] quit [RouterC] pim ipv6 [RouterC-pim6] bidir-pim enable # On Router D, enable IPv6 multicast routing, enable IPv6 PIM-SM on each interface, enable MLD on interface GigabitEtherne
RP Address: 6001::1 Interface State DF-Pref DF-Metric DF-Uptime DF-Address GE2/1/1 Win 100 1 01:24:09 FE80::200:5EFF: FE71:2801 (local) Ser3/1/1 Win 100 1 01:24:09 FE80::20F:E2FF: FE38:4E01 (local) Ser3/1/2 Lose 0 0 01:23:12 FE80::20F:E2FF: FE15:5601 # Display the DF information of IPv6 BIDIR-PIM on Router C.
Total 1 RP matched 00001. RP Address: 6001::1 MID: 0, Flags: 0x2100000:0 Uptime: 00:06:24 RPF interface: Serial3/1/2 List of 2 DF interfaces: 1: GigabitEthernet2/1/1 2: Serial3/1/1 # Display the DF information of the IPv6 multicast forwarding table on Router C. [RouterC] display multicast ipv6 forwarding-table df-info Multicast DF information Total 1 RP Total 1 RP matched 00001.
MLDv2 runs between Router A and N1 and between Router B, Router C, and N2.
[RouterA-GigabitEthernet2/1/1] quit [RouterA] interface serial 3/1/0 [RouterA-Serial3/1/0] pim ipv6 sm [RouterA-Serial3/1/0] quit [RouterA] interface pos 5/1/0 [RouterA-Pos5/1/0] pim ipv6 sm [RouterA-Pos5/1/0] quit # Enable IPv6 multicast routing, IPv6 PIM-SM, and MLD on Router B and Router C in the same way. (Details not shown.) # Enable IPv6 multicast routing and IPv6 PIM-SM on Router D and Router E in the same way. (Details not shown.) 4.
Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet2/1/1 Protocol: mld, UpTime: 00:00:11, Expires: 00:03:25 The information on Router B and Router C is similar to that on Router A. # Display IPv6 PIM multicast routing table information on Router D.
3. Use the display pim ipv6 neighbor command to verify that the RPF neighbor is an IPv6 PIM neighbor. 4. Verify that IPv6 PIM and MLD are enabled on the interfaces directly connecting to the IPv6 multicast source and to the receiver. 5. Use the display pim ipv6 interface verbose command to verify that the same PIM mode is enabled on the RPF interface and the corresponding interface of the RPF neighbor router. 6.
Solution 1. Use the display ipv6 routing-table command to verify that routes to the RP and the BSR are available on each router, and that a route between the RP and the BSR is available. Make sure each C-RP has a unicast route to the BSR, the BSR has a unicast route to each C-RP, and all the routers in the entire network have a unicast route to the RP. 2. IPv6 PIM-SM needs the support of the RP and BSR.
Configuring IPv6 MBGP This chapter covers configuration tasks related to multiprotocol BGP for IPv6 multicast. For information about BGP and IPv6 BGP, see Layer 3—IP Routing Configuration Guide. Overview IETF defined Multiprotocol BGP (MP-BGP) to enable BGP to carry routing information for multiple network-layer protocols. For an IPv6 network, the topology for IPv6 multicast might be different from that for IPv6 unicast.
Task Remarks Configuring a large scale IPv6 MBGP network Configuring the maximum number of equal-cost routes for load-balancing Optional. Configuring an IPv6 MBGP peer group Optional. Configuring IPv6 MBGP community Optional. Configuring an IPv6 MBGP route reflector Optional. Configuring basic IPv6 MBGP functions Configuration prerequisites IPv6 MBGP is an application of multiprotocol BGP. Before you configure IPv6 MBGP, complete the following tasks: 1. Enable IPv6. 2.
apply preferred-value preferred-value command. For more information about these commands, see Layer 3—IP Routing Command Reference. To configure a preferred value for routes from a peer or a peer group: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter IPv6 MBGP address family view. ipv6-family multicast N/A 4. Specify a preferred value for routes received from the IPv6 MBGP peer or the peer group.
Step 4. 5. Command Description Optional. Enable default route redistribution into the IPv6 MBGP routing table. default-route imported Enable route redistribution from another routing protocol. import-route protocol [ process-id [ med med-value | route-policy route-policy-name ] * ] Default route redistribution is not allowed by default. Not enabled by default. NOTE: If the default-route imported command is not configured, using the import-route command cannot redistribute any IGP default route.
NOTE: With the peer default-route-advertise command executed, the router sends a default route with the next hop as itself to the specified IPv6 MBGP peer or the specified peer group, regardless of whether the default route is available in the routing table. Configuring outbound IPv6 MBGP route filtering IMPORTANT: • Members of an IPv6 MBGP peer group must have the same outbound route filtering policy as the peer group.
Configuring inbound IPv6 MBGP route filtering Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter IPv6 MBGP address family view.
Step Command Remarks N/A 3. Enter IPv6 MBGP address family view. ipv6-family multicast 4. Configure IPv6 MBGP route dampening parameters. dampening [ half-life-reachable half-life-unreachable reuse suppress ceiling | route-policy route-policy-name ]* Optional. Not configured by default. Configuring IPv6 MBGP route attributes This section describes how to use IPv6 MBGP route attributes to affect IPv6 MBGP route selection.
Step Command Remarks N/A 3. Enter IPv6 MBGP address family view. ipv6-family multicast 4. Set the default local preference. default local-preference value Optional. 100 by default. Configuring the MED attribute Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter IPv6 MBGP address family view. ipv6-family multicast N/A 4. Configure a default MED value.
Step Command Remarks Optional. Configure the router as the next hop of routes sent to the peer or the peer group. 4. peer { ipv6-group-name | ipv6-address } next-hop-local By default, IPv6 MBGP specifies the local router as the next hop for routes sent to an EBGP peer or a peer group, but not for routes sent to an IBGP peer or a peer group. Configuring the AS_PATH attribute Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3.
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.
Enabling the IPv6 MBGP ORF capability The BGP Outbound Route Filter (ORF) feature enables a BGP speaker to send a set of ORFs to its BGP peer through route-refresh messages. The peer then applies the ORFs, in addition to its local routing policies (if any), to filter updates to the BGP speaker, thus reducing the number of exchanged update messages and saving network resources. After you enable the ORF capability, the local BGP router negotiates the ORF capability with the BGP peer through open messages.
Local parameter Peer parameter Negotiation result both both Both the ORF sending and receiving capabilities are enabled locally and on the peer. Configuring the maximum number of equal-cost routes for load-balancing Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter IPv6 MBGP address family view. ipv6-family multicast N/A 4. Configure the maximum number of equal-cost routes for load balancing.
Step Command Remarks 5. Add a peer to the peer group. peer ipv6-address group ipv6-group-name [ as-number as-number ] No peers are added by default. 6. Enter IPv6 MBGP address family view. ipv6-family multicast N/A 7. Enable the configured IPv6 unicast BGP peer group to create the IPv6 MBGP peer group. peer ipv6-group-name enable N/A Add the IPv6 MBGP peer into the peer group peer ipv6-address group ipv6-group-name No peers are added by default. 8.
The clients of a route reflector should not be fully meshed, and the route reflector reflects the routes of a client to the other clients. If the clients are fully meshed, you must disable route reflection between clients to reduce routing costs. If a cluster has multiple route reflectors, you must specify the same cluster ID for these route reflectors to avoid routing loops. To configure an IPv6 BGP route reflector: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view.
Task Command Remarks Display IPv6 MBGP routing table information. display bgp ipv6 multicast routing-table [ ipv6-address prefix-length ] [ | { begin | exclude | include } regular-expression ] Available in any view. Display IPv6 MBGP routing information that matches an AS path ACL. display bgp ipv6 multicast routing-table as-path-acl as-path-acl-number [ | { begin | exclude | include } regular-expression ] Available in any view.
Resetting IPv6 MBGP connections When you change an IPv6 MBGP routing policy, you can make the new configuration effective by resetting the IPv6 MBGP connections. To reset the specified IPv6 MBGP connections: Task Command Remarks Reset the specified IPv6 MBGP connections. reset bgp ipv6 multicast { as-number | ipv6-address | all | group ipv6-group-name | external | internal } Available in user view.
GE 2/1 /1 1 /1/ S3 S3 /1/ 0 0 /1/ S3 S3 /1/ 1 Figure 106 Network diagram Device Interface IP address Device Interface IP address Source - 1002::100/64 Router C GE2/1/1 3002::1/64 Router A GE2/1/1 1002::1/64 S3/1/0 3001::1/64 POS5/1/0 1001::1/64 Router B POS5/1/0 1001::2/64 S3/1/0 2001::1/64 S3/1/1 2002::1/64 Router D S3/1/1 2001::2/64 S3/1/0 2002::2/64 S3/1/1 3001::2/64 Configuration procedure 1. Configure IPv6 addresses for router interfaces as shown in Figure 106 .
[RouterC-Serial3/1/1] pim ipv6 sm [RouterC-Serial3/1/1] quit [RouterC] interface gigabitethernet 2/1/1 [RouterC-GigabitEthernet2/1/1] pim ipv6 sm [RouterC-GigabitEthernet2/1/1] mld enable [RouterC-GigabitEthernet2/1/1] quit # Configure an IPv6 PIM domain border on Router A. [RouterA] interface pos 5/1/0 [RouterA-Pos5/1/0] pim ipv6 bsr-boundary [RouterA-Pos5/1/0] quit # Configure an IPv6 PIM domain border on Router B.
[RouterB-bgp] ipv6-family multicast [RouterB-bgp-af-ipv6-mul] peer 1001::1 enable [RouterB-bgp-af-ipv6-mul] import-route ospfv3 1 [RouterB-bgp-af-ipv6-mul] quit [RouterB-bgp] quit 6. Verify the configuration: Use the display bgp ipv6 multicast peer command to display IPv6 MBGP peers on each router. For example: # Display IPv6 MBGP peers on Router B. [RouterB] display bgp ipv6 multicast peer BGP local router ID : 2.2.2.
Configuring PIM snooping Overview PIM snooping is a multicast constraining mechanism operating at Layer 2. It examines which ports are interested in multicast data by analyzing the received PIM messages, and adds the ports to a multicast forwarding entry to make sure multicast data can be forwarded to only the ports that are interested in the data.
b. Broadcasts all other types of received PIM messages in the VLAN. c. Forwards all multicast data to all router ports in the VLAN. Each PIM router in the VLAN, whether interested in the multicast data or not, can receive all multicast data and all PIM messages except PIM hello messages. When the Layer 2 switch runs both IGMP snooping and PIM snooping, it does the following actions: • a.
Task Command Remarks Display PIM snooping routing entries. display pim-snooping routing-table [ [ vlan vlan-id ] [ slot slot-number ] ] [ | { begin | exclude | include } regular-expression ] Available in any view. Display the statistics for PIM messages learned through PIM snooping. display pim-snooping statistics [ | { begin | exclude | include } regular-expression ] Available in any view. Clear the statistics for PIM messages learned through PIM snooping.
[RouterA-Ethernet1/1] pim sm [RouterA-Ethernet1/1] quit [RouterA] interface ethernet 1/2 [RouterA-Ethernet1/2] pim sm [RouterA-Ethernet1/2] quit [RouterA] pim [RouterA-pim] c-bsr ethernet 1/2 [RouterA-pim] c-rp ethernet 1/2 3. On Router B, enable IP multicast routing, and enable PIM-SM on each interface.
10.1.1.1 GE2/0/1 02:02:23 LAN Prune Delay 10.1.1.2 GE2/0/2 03:00:05 LAN Prune Delay 10.1.1.3 GE2/0/3 02:22:13 LAN Prune Delay 10.1.1.4 GE2/0/4 03:07:22 LAN Prune Delay The output shows that Router A, Router B, Router C, and Router D are PIM snooping neighbors. # On Router E, display the PIM snooping routing information of VLAN 100. [RouterE] display pim-snooping routing-table vlan 100 Total 2 entry(ies) FSM Flag: NI-no info, J-join, PP-prune pending VLAN ID: 100 Total 2 entry(ies) (*, 224.
3. If PIM snooping is not enabled, enter VLAN view and use the pim-snooping enable command to enable PIM snooping for the VLAN. 4. Verify that PIM snooping is operating in a PIM-SM network. PIM snooping only supports the PIM-SM mode but not the PIM-DM mode. If the network is in the PIM-DM mode, change it to the PIM-SM mode. Some downstream PIM routers cannot receive multicast data Symptom In a network with fragmented join/prune messages, some downstream PIM routers cannot receive multicast data.
Configuring multicast VLANs Overview Figure 109 shows the traditional multicast programs-on-demand mode. When the hosts ( Host A, Host B, and Host C) that belong to different VLANs require the multicast programs-on-demand service, the Layer 3 device (Switch A) must forward a separate copy of the multicast data in each VLAN to the Layer 2 device (Switch B). This causes a waste of network bandwidth and adds an extra burden on the Layer 3 device.
Figure 110 Sub-VLAN-based multicast VLAN After the configuration, IGMP snooping manages router ports in the multicast VLAN and member ports in each sub-VLAN. When Switch A forwards the multicast data to Switch B, it sends only one copy of the multicast data to Switch B. Switch B distributes the data to the multicast VLAN's sub-VLANs that contain receivers. Port-based multicast VLAN As shown in Figure 111, Host A, Host B, and Host C are in VLAN 2 through VLAN 4, respectively.
For more information about IGMP snooping, router ports, and member ports, see "Configuring IGMP snooping." For more information about VLAN tags, see Layer 2—LAN Switching Configuration Guide. Multicast VLAN configuration task list Task Remarks Configuring a sub-VLAN-based multicast VLAN Configuring a port-based multicast VLAN Required. Configuring user port attributes Configuring multicast VLAN ports Setting the maximum number of forwarding entries in a multicast VLAN Optional.
Configuring a port-based multicast VLAN When you configure a port-based multicast VLAN, you must configure the attribute of each user port and then assign the ports to the multicast VLAN. A user port can be configured as a multicast VLAN port only if it is an Ethernet port or a Layer 2 aggregate interface. In Ethernet interface view or Layer 2 aggregate interface view, the configurations are effective only on the current port.
Configuring multicast VLAN ports In this approach, you configure a VLAN as a multicast VLAN and assign user ports to it. You can do it by either adding the user ports in the multicast VLAN or specifying the multicast VLAN on the user ports. These two methods provide the same result. When you configure multicast VLAN ports, follow these guidelines: • Do not configure a multicast VLAN on a device with multicast routing enabled. • The VLAN to be configured as a multicast VLAN must exist.
When you are setting this upper limit, if the total number of the entries exceeds the value that you set, the system informs you to remove excessive entries. In this case, the system does not automatically remove any existing entries or create new entries. To set the maximum number of entries in the forwarding table: Step Command Remarks 1. Enter system view. system-view N/A 2. Set the maximum number of forwarding entries in a multicast VLAN.
Figure 112 Network diagram Configuration procedure 1. Configure Router A: # Enable IP multicast routing. system-view [RouterA] multicast routing-enable # Create VLAN 20 and assign GigabitEthernet 2/0/2 into this VLAN. [RouterA] vlan 20 [RouterA-vlan20] port gigabitethernet 2/0/2 [RouterA-vlan20] quit # Configure an IP address for VLAN-interface 20 and enable PIM-DM. [RouterA] interface vlan-interface 20 [RouterA-Vlan-interface20] ip address 1.1.1.
2. Configure Router B: # Enable IGMP snooping globally. system-view [RouterB] igmp-snooping [RouterB-igmp-snooping] quit # Create VLAN 2 and assign GigabitEthernet 2/0/2 to this VLAN. [RouterB] vlan 2 [RouterB-vlan2] port gigabitethernet 2/0/2 [RouterB-vlan2] quit # Create VLAN 3 and assign GigabitEthernet 2/0/3 to this VLAN. [RouterB] vlan 3 [RouterB-vlan3] port gigabitethernet 2/0/3 [RouterB-vlan3] quit # Create VLAN 4 and assign GigabitEthernet 2/0/4 to this VLAN.
Total 4 MAC Group(s). Port flags: D-Dynamic port, S-Static port, C-Copy port, P-PIM port Subvlan flags: R-Real VLAN, C-Copy VLAN Vlan(id):2. Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s). Router port(s):total 0 port(s). IP group(s):the following ip group(s) match to one mac group. IP group address:224.1.1.1 (0.0.0.0, 224.1.1.1): Host port(s):total 1 port(s). GE2/0/2 (D) MAC group(s): MAC group address:0100-5e01-0101 Host port(s):total 1 port(s). GE2/0/2 Vlan(id):3. Total 1 IP Group(s).
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). GE2/0/1 (D) 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 0 port(s). MAC group(s): MAC group address:0100-5e01-0101 Host port(s):total 0 port(s). The output shows that IGMP snooping is maintaining the router port in the multicast VLAN (VLAN 10) and the member ports in the sub-VLANs (VLAN 2 through VLAN 4).
Configuration procedure 1. Configure Router A: # Enable IP multicast routing. system-view [RouterA] multicast routing-enable # Create VLAN 20 and assign GigabitEthernet 2/0/2 to this VLAN. [RouterA] vlan 20 [RouterA-vlan20] port gigabitethernet 2/0/2 [RouterA-vlan20] quit # Configure an IP address for VLAN-interface 20 and enable PIM-DM. [RouterA] interface vlan-interface 20 [RouterA-Vlan-interface20] ip address 1.1.1.
# Configure GigabitEthernet 2/0/2 as a hybrid port and its PVID to be 2. Configure GigabitEthernet 2/0/2 to permit packets from VLAN 2 and VLAN 10 to pass and untag the packets when forwarding them.
Host port(s):total 3 port(s). GE2/0/2 (D) GE2/0/3 (D) GE2/0/4 (D) MAC group(s): MAC group address:0100-5e01-0101 Host port(s):total 3 port(s). GE2/0/2 GE2/0/3 GE2/0/4 The output shows that IGMP snooping is maintaining the router ports and member ports in VLAN 10.
Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
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. { x | y | ... } Braces enclose a set of required syntax choices separated by vertical bars, from which you select one.
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. Represents an access controller, a unified wired-WLAN module, or the switching engine on a unified wired-WLAN switch. Represents an access point.
Index ACDEHIMOPRST Configuring MD-VPN,234 A Configuring MLD proxying,296 Adjusting IGMP performance,75 Configuring MLD SSM mapping,295 Adjusting MLD performance,290 Configuring multicast routing and forwarding,51 Appendix,44 Configuring PIM snooping,402 C Configuring PIM-DM,107 Configuration examples,57 Configuring PIM-SM,110 Configuration task list,50 Configuring PIM-SSM,131 Configuration task list,270 Configuring SA message related parameters,175 Configuring a large scale IPv6 MBGP networ
IGMP configuration task list,71 Overview,217 IGMP snooping configuration examples,33 Overview,267 IGMP snooping configuration task list,17 Overview,92 IPv6 MBGP configuration example,397 Overview,165 IPv6 MBGP configuration task list,382 Overview,13 IPv6 multicast forwarding over GRE tunnel configuration example,274 Overview,65 IPv6 PIM configuration examples,352 Overview,279 Overview,1 M P MBGP configuration example,213 PIM configuration examples,140 MBGP configuration task list,197 PIM
