HP HSR6800 Routers IP Multicast Configuration Guide Part number: 5998-4493 Software version: HSR6800-CMW520-R3303P05 Document version: 6PW105-20140507
Legal and notice information © Copyright 2014 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 ················································································································ 31 Setting the 802.
Configuring an interface as a static member interface ····················································································· 77 Configuring a multicast group filter ····················································································································· 77 Setting the maximum number of multicast groups that an interface can join ················································· 78 Adjusting IGMP performance ·························································
Enabling PIM-SM ················································································································································· 127 Enabling BIDIR-PIM ·············································································································································· 128 Configuring an RP ··············································································································································· 128 Configuring a
Displaying and maintaining MSDP ···························································································································· 183 MSDP configuration examples···································································································································· 183 PIM-SM Inter-domain multicast configuration ··································································································· 184 Inter-AS multicast configuration by lev
Multicast across VPNs········································································································································· 227 Protocols and standards ····································································································································· 229 How MD-VPN works ···················································································································································· 229 Share-MDT establi
MLD SSM mapping ············································································································································· 291 MLD proxying ······················································································································································ 292 Protocols and standards ····································································································································· 292 MLD configuration ta
Configuring a BSR ··············································································································································· 336 Configuring IPv6 administrative scoping ·········································································································· 339 Configuring IPv6 multicast source registration ································································································· 341 Configuring switchover to SPT ················
Configuration prerequisites ····································································································································· 7 Configuring IPv6 MBGP route preferences············································································································7 Configuring the default local preference ··············································································································· 7 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.
In unicast transmission, the traffic transmitted over the network is proportional to the number of hosts that need the information. If a large number of hosts need the information, the information source must send a separate copy of the same information to each of these hosts. Sending many copies can place a tremendous pressure on the information source and the network bandwidth. Unicast is not suitable for batch transmission of 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) enable 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.11 Mobile agents. 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 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 DRs 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.
Timer Description Message before expiration Action after expiration Dynamic member port aging timer. When a port dynamically joins a multicast group, the router starts an aging timer for the port. When the timer expires, the dynamic member port ages out. IGMP membership report. The router removes this port from the IGMP snooping forwarding table. NOTE: In IGMP snooping, only dynamic ports age out. Static ports never age out.
know whether the reported multicast group still has active members attached to that port. For more information about the IGMP report suppression mechanism, see "Configuring IGMP." When receiving a leave message An IGMPv1 host silently leaves a multicast group and the router is not notified of the leave.
Figure 13 Network diagram IGMP Querier Router A IP network Query from Router A Report from Switch A Query from Switch A Proxy & Querier Router B Host A Receiver Report from Host Host C Receiver Host B 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.
Protocols and standards RFC 4541, Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping Switches IGMP snooping configuration task list For the configuration tasks in this section, the following rules apply: • The configurations made in IGMP-snooping view are effective on all VLANs. The configurations made in VLAN view are effective on only the current VLAN.
Task Remarks Configuring IGMP snooping policies Configuring a multicast group filter Optional. Configuring multicast source port filtering Optional. Enabling dropping unknown multicast data Optional. Enabling IGMP report suppression Optional. Setting the maximum number of multicast groups that a port can join Optional. Enabling multicast group replacement Optional. Setting the 802.1p precedence for IGMP messages Optional. Enabling the IGMP snooping host tracking function Optional.
Specifying the IGMP snooping version Different versions of IGMP snooping can process different versions of IGMP messages: • IGMPv2 snooping can process IGMPv1 and IGMPv2 messages, but flood IGMPv3 messages in the VLAN instead of processing them. • IGMPv3 snooping can process IGMPv1, IGMPv2 and IGMPv3 messages. If you change IGMPv3 snooping to IGMPv2 snooping, the system does the following: • Clears all IGMP snooping forwarding entries that are dynamically added.
Configuration prerequisites Before you configure IGMP snooping port functions, complete the following tasks: • Enable IGMP snooping in the VLAN. • Configure the corresponding port groups. • Determine the aging timer for dynamic router ports. • Determine the aging timer for dynamic member ports. • Determine the multicast group and multicast source addresses.
Configuring static ports If all hosts attached to a port are interested in the multicast data addressed to a particular multicast group or the multicast data that a particular multicast source sends to a particular group, you can configure the port as a static member port for the specified multicast group or the specified multicast source and group. You can also configure a port to be a static router port, through which the router can forward all the multicast traffic that it received.
When you disable the simulated joining function on the port, the router sends an IGMP leave message through the port. • To configure a port as a simulated member host: Step 1. Enter system view. 2. Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view, or enter port group view. Command Remarks system-view N/A • Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view: interface interface-type interface-number Use either command.
Step Command Remarks • Enter Layer 2 Ethernet interface view or Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view, or enter port group view. 2. Layer 2 aggregate interface view: interface interface-type interface-number Use either command. • Enter port group view: port-group manual port-group-name Enable IGMP snooping fast-leave processing for the port. 3. igmp-snooping fast-leave [ vlan vlan-list ] Disabled by default.
Configuration prerequisites Before you configure IGMP snooping querier, complete the following tasks: • Enable IGMP snooping in the VLAN. • Determine the interval for sending IGMP general queries. • Determine the IGMP last-member query interval. • Determine the maximum response delay for IGMP general queries. • Determine the source address of IGMP general queries. • Determine the source address of IGMP group-specific queries.
The maximum response delay for IGMP group-specific queries equals the IGMP last-member query interval. • CAUTION: Make sure the interval for sending IGMP general queries is larger than the maximum response delay for IGMP general queries. Otherwise, multicast group members might be deleted by mistake. Configuring the global parameters for IGMP queries and responses Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IGMP-snooping view. igmp-snooping N/A 3.
Step Command Remarks 2. Enter VLAN view. vlan vlan-id N/A 3. Configure the source IP address for IGMP general queries. igmp-snooping general-query source-ip { ip-address | current-interface } 0.0.0.0 by default. Configure the source IP address for IGMP group-specific queries. igmp-snooping special-query source-ip { ip-address | current-interface } 0.0.0.0 by default. 4. Configuring IGMP snooping proxying This section describes how to configure IGMP snooping proxying.
Step Command Remarks 2. Enter VLAN view. vlan vlan-id N/A 3. Configure the source IP address for the IGMP reports that the proxy sends. igmp-snooping report source-ip { ip-address | current-interface } The default is 0.0.0.0. Configure the source IP address for the IGMP leave messages that the proxy sends. igmp-snooping leave source-ip { ip-address | current-interface } The default is 0.0.0.0. 4.
Step 1. Enter system view. Command Remarks system-view N/A • Enter Layer 2 Ethernet interface 2. Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view, or enter port group view. 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 3. Configure a multicast group filter.
Enabling dropping unknown multicast data Unknown multicast data refers to multicast data for which no forwarding entries exist in the IGMP snooping forwarding table. When the router receives such multicast traffic, one of the following occurs: • If the function of dropping unknown multicast data is disabled, the router floods unknown multicast data in the VLAN to which the unknown multicast data belongs.
When you configure this maximum number, if the number of multicast groups the port has joined exceeds the configured maximum value, the system deletes all the forwarding entries for the port. The hosts connected to the port can join multicast groups before the number of multicast groups that the port joins reaches the maximum value.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IGMP-snooping view. igmp-snooping N/A 3. Enable multicast group replacement. overflow-replace [ vlan vlan-list ] Disabled by default. Enabling multicast group replacement on a port Step 1. Enter system view. Command Remarks system-view N/A • Enter Layer 2 Ethernet interface 2. Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view, or enter port group view.
Enabling the IGMP snooping host tracking function With the IGMP snooping host tracking function, the router can record the information of the member hosts that are receiving multicast traffic, including the host IP address, running duration, and timeout time. You can monitor and manage the member hosts according to the recorded information. Enabling the IGMP snooping host tracking function globally Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IGMP-snooping view.
Task Command Remarks Display statistics for the IGMP messages learned through IGMP snooping. display igmp-snooping statistics [ | { begin | exclude | include } regular-expression ] Available in any view. Available in user view. 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 ] Clear statistics for the IGMP messages learned through IGMP snooping.
Figure 14 Network diagram 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.
[RouterB-acl-basic-2001] rule permit source 224.1.1.1 0 [RouterB-acl-basic-2001] quit [RouterB] igmp-snooping [RouterB-igmp-snooping] group-policy 2001 vlan 100 [RouterB-igmp-snooping] quit # Configure GigabitEthernet 2/0/3 and GigabitEthernet 2/0/4 as simulated hosts for multicast group 224.1.1.1. [RouterB] interface gigabitethernet 2/0/3 [RouterB-GigabitEthernet2/0/3] igmp-snooping host-join 224.1.1.
Static port configuration example Network requirements As shown in Figure 15, IGMPv2 runs on Router A, and IGMPv2 snooping runs on Router B, Router C, and Router D, with Router A acting as the IGMP querier. Router B, Router C, and Router D are the HSR6800 routers. Host A and host C are permanent receivers of multicast group 224.1.1.1. GigabitEthernet 2/0/3 and GigabitEthernet 2/0/5 on Router D should be configured as static member ports for multicast group 224.1.1.
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.
# Create VLAN 100, assign GigabitEthernet 2/0/1 through GigabitEthernet 2/0/5 to this VLAN, and enable IGMP snooping in the VLAN. [RouterD] vlan 100 [RouterD-vlan100] port gigabitethernet 2/0/1 to gigabitethernet 2/0/5 [RouterD-vlan100] igmp-snooping enable [RouterD-vlan100] quit # Configure GigabitEthernet 2/0/3 and GigabitEthernet 2/0/5 as static member ports for multicast group 224.1.1.1. [RouterD] interface gigabitethernet 2/0/3 [RouterD-GigabitEthernet2/0/3] igmp-snooping static-group 224.1.1.
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/2 (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): Attribute: Host Port Host port(s):total 2 port. GE2/0/3 (S) GE2/0/5 (S) MAC group(s): MAC group address:0100-5e01-0101 Host port(s):total 2 port.
Figure 16 Network diagram Configuration procedure 1. Configure Router A: # Enable IGMP snooping globally. system-view [RouterA] igmp-snooping [RouterA-igmp-snooping] quit # Create VLAN 100 and assign GigabitEthernet 2/0/1 through GigabitEthernet 2/0/3 to the VLAN. [RouterA] vlan 100 [RouterA-vlan100] port gigabitethernet 2/0/1 to gigabitethernet 2/0/3 # Enable IGMP snooping and the function of dropping unknown multicast traffic in 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. Configure Router C and Router D in the same way as you configure Router B. (Details not shown.) 4.
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.
{ { 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. The router searches its static multicast routing table by using the IP address of the packet source as the source address and automatically chooses an optimal static multicast route.
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 18 RPF check process IP Routing Table on Router C Destination/Mask Interface 192.168.0.
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 Command Remarks 1. Enter system view. system-view N/A 2. Enable IP multicast routing. 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. ip vpn-instance vpn-instance-name 3. Configure a route distinguisher (RD) for the VPN instance.
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 Command Remarks 1. Enter system view. system-view N/A 2. 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. 3. The default value is 4096. The default value is 128. Configuring the multicast forwarding table size in a VPN instance Step Command Remarks 1.
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 (in standalone mode).
Task Command Remarks Display static multicast MAC address entries. display mac-address [ mac-address [ vlan vlan-id ] | [ multicast ] [ vlan vlan-id ] [ count ] ] [ | { begin | exclude | include } regular-expression ] Available in any view. Available in user view. Clear forwarding entries from the multicast forwarding table.
Figure 22 Network diagram Router C GE2/0/2 40.1.1.1/24 PIM-DM GE2/0/2 40.1.1.2/24 Router A GE2/0/1 50.1.1.1/24 GE2/0/1 20.1.1.2/24 GE2/0/2 20.1.1.1/24 GE2/0/3 30.1.1.2/24 GE2/0/3 30.1.1.1/24 Source Router B GE2/0/1 10.1.1.1/24 Receiver 50.1.1.100/24 10.1.1.100/24 Multicast static route Configuration procedure 1. Assign an IP address and subnet mask to each interface according to Figure 22. (Details not shown.) 2.
[RouterA-GigabitEthernet2/0/2] pim dm [RouterA-GigabitEthernet2/0/2] quit [RouterA] interface gigabitethernet 2/0/3 [RouterA-GigabitEthernet2/0/3] pim dm [RouterA-GigabitEthernet2/0/3] quit # Configure Router C in the same way as you configure Router A. (Details not shown.) # Use the display multicast rpf-info command to view the RPF route to Source on Router B. [RouterB] display multicast rpf-info 50.1.1.100 RPF information about source 50.1.1.100: RPF interface: GigabitEthernet2/0/3, RPF neighbor: 30.1.
Figure 23 Network diagram Configuration procedure 1. Assign an IP address and subnet mask to each interface according to Figure 23. (Details not shown.) 2. Enable OSPF on Router B and Router C to make sure they are interoperable at the network layer and they can dynamically update their routing information. (Details not shown.) 3.
[RouterC] display multicast rpf-info 50.1.1.100 No information is displayed. It means that that no RPF route to Source 2 exists on Router B and Router C. 4. Configure a static multicast route: # Configure a static multicast route on Router B, specifying Router A as its RPF neighbor on the route to Source 2. [RouterB] ip rpf-route-static 50.1.1.100 24 30.1.1.2 # Configure a static multicast route on Router C, specifying Router B as its RPF neighbor on the route to Source 2.
Figure 24 Network diagram Configuration procedure 1. Assign an IP address and mask to each interface according to Figure 24. (Details not shown.) 2. Configure a GRE tunnel: # Create Tunnel 0 on Router A and configure the IP address and mask for the interface. system-view [RouterA] interface tunnel 0 [RouterA-Tunnel0] ip address 50.1.1.1 24 # On Router A, specify the tunnel encapsulation mode as GRE over IPv4 and specify the source and destination addresses of the interface.
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.0] quit [RouterB-ospf-1] quit # Configure OSPF on Router C. [RouterC] ospf 1 [RouterC-ospf-1] area 0 [RouterC-ospf-1-area-0.0.0.0] network 30.1.1.0 0.0.0.255 [RouterC-ospf-1-area-0.0.0.0] network 40.1.1.0 0.0.0.255 [RouterC-ospf-1-area-0.0.0.0] network 50.1.1.0 0.0.0.255 [RouterC-ospf-1-area-0.0.0.
# Display PIM routing table information on Router C. [RouterC] display pim routing-table 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/0/1 Protocol: igmp, UpTime: 00:04:25, Expires: never (10.1.1.100, 225.1.1.
Solution 1. Use the display multicast routing-table static command to view the configuration information of static multicast routes to verify that the static multicast route has been correctly configured and that the route entry exists in the multicast routing table. 2. Check the type of the next-hop interface of the static multicast route. If the interface is not a point-to-point interface, be sure to specify the next hop address for the outgoing interface when you configure the static multicast route.
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 receive multicast data from specific sources like S1, S2, …, it sends a report with the Filter-Mode denoted as "Include Sources (S1, S2, …)." • 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.
{ IS_EX—The source filtering mode is Exclude. The report sender requests the multicast data from any sources but those defined in the specified multicast source list. { TO_IN—The filtering mode has changed from Exclude to Include. { 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.
With the IGMP SSM mapping feature configured, when Router A receives an IGMPv1 or IGMPv2 report, it checks the multicast group address G carried in the message and does the following: • If G is not in the SSM group range, Router A provides the ASM service. • 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 drops the message.
• Downstream interface—An interface that is running IGMP and is not in the direction toward the root of the multicast forwarding tree. A downstream interface acts as a router that is running IGMP. Therefore, it is also called the "router interface". A device with IGMP proxying configured maintains a group membership database, which stores the group memberships on all the downstream interfaces. Each entry comprises the multicast address, filter mode, and source list.
Task Remarks Adjusting IGMP performance Configuring IGMP SSM mapping Configuring IGMP proxying Setting the maximum number of multicast groups that an interface can join Optional. Configuring Router-Alert option handling methods Optional. Configuring IGMP query and response parameters Optional. Enabling IGMP fast-leave processing Optional. Enabling the IGMP host tracking function Optional. Enabling SSM mapping Optional. Configuring SSM mappings Optional. Enabling IGMP proxying Optional.
Step 4. Enable IGMP. Command Remarks igmp enable Disabled by default. Command Remarks Enabling IGMP for a VPN instance Step 1. Enter system view. system-view N/A 2. Create a VPN instance and enter its view. ip vpn-instance vpn-instance-name N/A 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.
Configuring an interface as a static member interface You can configure an interface as a static member of a multicast group or a multicast source and group, so that the interface can receive multicast data addressed to that multicast group for the purpose of testing multicast data forwarding. Configuration guidelines • When you configure an interface on a PIM-SM device as a static member interface, if the interface is PIM-SM enabled, the interface must be a PIM-SM DR.
Setting the maximum number of multicast groups that an interface can join This configuration only limits the number of multicast groups that the interface dynamically joins. To configure the maximum number of multicast groups an interface can join: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A The default value is 16384. 3. Configure the maximum number of multicast groups that the interface can join.
Configuring Router-Alert option handling methods IGMP queries include group-specific queries and group-and-source-specific queries. Multicast groups change dynamically, so a device cannot maintain the information for all multicast sources and groups. For this reason, when an IGMP router receives a multicast packet but cannot locate the outgoing interface for the destination multicast group, it must use the Router-Alert option to pass the multicast packet to the upper-layer protocol for processing.
Configuring IGMP query and response parameters On startup, the IGMP querier sends IGMP general queries at the startup query interval, which is one-quarter of the IGMP general query interval. The number of queries, or the startup query count, is user configurable. After startup, the IGMP querier periodically sends IGMP general queries at the IGMP general query interval to check for multicast group members on the network. You can modify the IGMP general query interval based on actual condition of the network.
Step Command Remarks 2 by default. A higher robustness variable makes the IGMP querier more robust, but results in longer multicast group timeout time. 3. Configure the IGMP querier's robustness variable. robust-count robust-value 4. Configure the startup query interval. startup-query-interval interval By default, the startup query interval is one-quarter of the "IGMP general query interval." 5. Configure the startup query count.
Step 7. 8. 9. Command Remarks Configure the maximum response time for IGMP general queries. igmp max-response-time interval 10 seconds by default. Configure the IGMP last member query interval. igmp last-member-query-interval interval 1 second by default. igmp 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.
Enabling the IGMP host tracking function When the IGMP host tracking function is enabled, the switch can record the information of the member hosts that are receiving multicast traffic. The member host information includes the host IP address, running duration, and timeout time. You can monitor and manage the member hosts according to the recorded information. Enabling the IGMP host tracking function globally Step Command Remarks 1. Enter system view. system-view N/A 2.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Enable the IGMP SSM mapping feature. igmp ssm-mapping enable Disabled by default. Configuring SSM mappings By performing this configuration multiple times, you can map a multicast group to different multicast sources.
Configuration guidelines • Each device can have only one interface serving as the proxy interface. In scenarios with multiple instances, IGMP proxying is configured on only one interface per instance. • You cannot enable IGMP on an interface with IGMP proxying enabled. Moreover, only the igmp require-router-alert, igmp send-router-alert, and igmp version commands can take effect on such an interface.
Displaying and maintaining IGMP Task Command Remarks Display IGMP group information. display igmp [ all-instance | vpn-instance vpn-instance-name ] group [ group-address | interface interface-type interface-number ] [ static | verbose ] [ | { begin | exclude | include } regular-expression ] Available in any view. Display the Layer 2 port information of IGMP groups (in standalone mode).
Task Command Remarks Display information in the IGMP routing table. display igmp [ all-instance | vpn-instance vpn-instance-name ] routing-table [ source-address [ mask { mask | mask-length } ] | group-address [ mask { mask | mask-length } ] | flags { act | suc } ] * [ | { begin | exclude | include } regular-expression ] Available in any view. Display IGMP SSM mappings.
IGMP configuration examples This section provides examples of configuring IGMP. Basic IGMP functions configuration example Network requirements The receivers receive VOD information through multicast. The receivers of different organizations form stub networks N1 and N2. Host A and Host C are receivers in N1 and N2, respectively. Router A in the PIM network connects to N1, and both Router B and Router C connect to another stub network, N2.
[RouterA] multicast routing-enable [RouterA] interface gigabitethernet 2/0/1 [RouterA-GigabitEthernet2/0/1] igmp enable [RouterA-GigabitEthernet2/0/1] pim dm [RouterA-GigabitEthernet2/0/1] quit [RouterA] interface gigabitethernet 2/0/0 [RouterA-GigabitEthernet2/0/0] pim dm [RouterA-GigabitEthernet2/0/0] quit # Enable IP multicast routing on Router B, enable PIM-DM on each interface, and enable IGMP on GigabitEthernet 2/0/1.
Value of other querier present interval for IGMP(in seconds): 125 Value of maximum query response time for IGMP(in seconds): 10 Querier for IGMP: 10.110.2.1 (this router) Total 1 IGMP Group reported SSM mapping configuration example Network requirements The PIM-SM domain applies both the ASM model and SSM model for multicast delivery. Router D's GigabitEthernet 2/1/3 serves as the C-BSR and C-RP. The SSM group range is 232.1.1.0/24. IGMPv3 runs on Router D's GigabitEthernet 2/1/1.
3. Enable IP multicast routing, enable PIM-SM on each interface, and enable IGMP and IGMP SSM mapping on the host-side interface: # Enable IP multicast routing on Router D, enable PIM-SM on each interface and enable IGMPv3 and IGMP SSM mapping on GigabitEthernet 2/1/1.
[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. Verify the configuration: # Display the IGMP SSM mapping information for multicast group 232.1.1.1 on the public network on Router D. [RouterD] display igmp ssm-mapping 232.1.1.1 Vpn-Instance: public net Group: 232.1.1.1 Source list: 133.133.1.1 133.133.3.
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. Configure the IGMP proxying feature on Router B so that Router B can maintain group memberships and forward multicast traffic without running PIM-DM. Figure 31 Network diagram Proxy & Querier Router B GE2/1/2 192.168.2.1/24 GE2/1/1 192.168.1.1/24 Querier Router A GE2/1/1 192.168.1.
3. Verify the configuration: # Display the IGMP configuration and operation information on GigabitEthernet 2/1/1 of Router B. [RouterB] display igmp interface gigabitethernet 2/1/1 verbose GigabitEthernet2/1/1(192.168.1.2): IGMP proxy is enabled Current IGMP version is 2 Multicast routing on this interface: enabled Require-router-alert: disabled Version1-querier-present-timer-expiry: 00:00:20 # Display the IGMP group information on Router A. [RouterA] display igmp group Total 1 IGMP Group(s).
configured the shutdown command on the interface, that the interface is not correctly connected, or that the IP address configuration is not correctly completed. 2. Use the display current-configuration command to verify that multicast routing is enabled. If not, use the multicast routing-enable command in system view to enable IP multicast routing. In addition, check that IGMP is enabled on the corresponding interfaces. 3.
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. If the branch does not have any multicast receiver, it is pruned again. 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.
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 in the priority, 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.
bootstrap messages, for a specific group range cannot cross the admin-scoped zone boundary. Multicast group ranges that different admin-scoped zones serve can be overlapped. A multicast group is valid only within its local admin-scoped 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-scoped zone.
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 for sending 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 timer expires, it discards the message. If this timer times out, the router will accept a new state-refresh message, refresh its own PIM-DM state, and reset the waiting timer. 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.
PIM-SM configuration task list Task Remarks Enabling PIM-SM Required. Configuring an RP Configuring a BSR Configuring administrative scoping Configuring a static RP Required. Configuring a C-RP Enabling auto-RP Use any method. 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.
• Determine the ACL rule defining a legal BSR address range. • Determine the BS period. • Determine the BS timeout timer. • Determine the ACL rule for register message filtering. • Determine the register suppression time. • Determine the register probe time. • 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.
Step 6. 7. Command Bind the interface with a VPN instance. ip binding vpn-instance vpn-instance-name Enable PIM-SM. pim sm Description By default, an interface belongs to the public network, and is not bound with any VPN instance. For more information about this command, see MPLS Command Reference. 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 3. Configure an interface to be a C-RP for PIM-SM. c-rp interface-type interface-number [ group-policy acl-number | priority priority | holdtime hold-interval | advertisement-interval adv-interval ] * No C-RPs are configured by default. 4. Configure a legal C-RP address range and the range of multicast groups to be served.
Step 4. Command Configure C-RP timeout timer. c-rp holdtime interval Remarks Optional. 150 seconds by default. For more information about the configuration of other timers in PIM-SM, see "Configuring common PIM timers." 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.
Because the BSR and the other devices exchange a large amount of information in the PIM-SM domain, provide a relatively large bandwidth between the C-BSRs and the other devices. For C-BSRs interconnected through a GRE tunnel, configure static multicast routes to make sure the next hop to a C-BSR is a tunnel interface. For more information about static multicast routes, see "Configuring multicast routing and forwarding." To configure a C-BSR: Step Command Remarks 1. Enter system view.
If you do not configure these parameters in the global scope zone or admin-scoped zone, the corresponding global values will be used. • For information about how to configure C-BSR parameters for an admin-scoped zone and global scope zone, see "Configuring C-BSRs for each admin-scoped zone and the global-scoped zone ." Perform the following configuration on C-BSR routers. To configure C-BSR parameters: Step Command Remarks 1. Enter system view. system-view N/A 2.
Step Command Remarks Optional. Configure the BS timeout timer. 4. c-bsr holdtime interval By default, the BS timeout timer is determined by the formula "BS timeout timer = BS period × 2 + 10." The default BS period is 60 seconds, so the default BS timeout timer = 60 × 2 + 10 = 130 (seconds). NOTE: If you configure the BS period or the BS timeout timer, the system uses the configured one instead of the default one.
Configuring administrative scoping When administrative scoping is disabled, a PIM-SM domain has only one BSR. The BSR manages the whole network. To manage your network more effectively and specifically, partition the PIM-SM domain into multiple admin-scoped zones. Each admin-scoped zone maintains a BSR, which serves a specific multicast group range. The global scope zone also maintains a BSR, which serves all the remaining multicast groups.
The following rules apply to the hash mask length and C-BSR priority: • You can configure these parameters globally, for an admin-scoped zone, and for the global scope zone. • The values of these parameters configured for the global scope zone or an admin-scoped zone have preference over the global values. • If you do not configure these parameters for the global scope zone or an admin-scoped zone, the corresponding global values are used.
In view of information integrity of register messages in the transmission process, you can configure the device to calculate the checksum based on the entire register messages. However, to reduce the workload of encapsulating data in register messages and for the sake of interoperability, do not use this checksum calculation method.
Step Command Remarks N/A 2. Enter public network PIM view or VPN instance PIM view. pim [ vpn-instance vpn-instance-name ] 3. Configure the criteria for triggering a switchover to SPT. spt-switch-threshold infinity [ group-policy acl-number [ order order-value] ] Optional. By default, the device switches to the SPT immediately after it receives the first multicast packet. Configuring BIDIR-PIM This section describes how to configure BIDIR-PIM.
• Determine the C-RP priority and the ACL that defines the range of multicast groups to be served by each C-RP. • Determine the legal C-RP address range and the ACL that defines the range of multicast groups to be served. • Determine the C-RP-Adv interval. • Determine the C-RP timeout timer. • Determine the C-BSR priority. • Determine the hash mask length. • Determine the ACL defining the legal BSR address range. • Determine the BS period. • Determine the BS timeout timer.
Step 5. 6. 7. Enter interface view. Command Remarks interface interface-type interface-number N/A Bind the interface with the VPN instance. ip binding vpn-instance vpn-instance-name Enable PIM-SM. pim sm By default, an interface belongs to the public network, and is not bound with any VPN instance. For more information about this command, see MPLS Command Reference. Disabled by default. Enabling BIDIR-PIM Perform this configuration on all routers in the BIDIR-PIM domain.
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 a static RP for BIDIR-PIM. static-rp rp-address [ acl-number ] [ preferred ] bidir No static RP by default. Configuring a C-RP In a BIDIR-PIM domain, you can configure routers that intend to become the RP as C-RPs.
Configuring C-RP timers globally To enable the BSR to distribute the RP-set information within the BIDIR-PIM domain, C-RPs must periodically send C-RP-Adv messages to the BSR. The BSR learns the RP-set information from the received messages, and encapsulates its own IP address together with the RP-set information in its bootstrap messages. The BSR then floods the bootstrap messages to all PIM routers in the network. Each C-RP encapsulates a timeout value in its C-RP-Adv messages.
• Some maliciously configured hosts can forge bootstrap messages to fool routers and change RP mappings. Such attacks often occur on border routers. Because a BSR is inside the network whereas hosts are outside the network, you can protect a BSR against attacks from external hosts by enabling the border routers to perform neighbor checks and RPF checks on bootstrap messages and discard unwanted messages.
Step Command Remarks 2. Enter interface view. interface interface-type interface-number N/A 3. Configure a BIDIR-PIM domain border. pim bsr-boundary By default, no BIDIR-PIM domain border is configured. Configuring global C-BSR parameters In each BIDIR-PIM domain, a unique BSR is elected from C-BSRs. The C-RPs in the BIDIR-PIM domain send advertisement messages to the BSR. The BSR summarizes the advertisement messages to form an RP-set and advertises it to all routers in the BIDIR-PIM domain.
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 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.
To disable the BSM semantic fragmentation function: 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 Disable the BSM semantic fragmentation function. undo bsm-fragment enable By default, the BSM semantic fragmentation function is enabled. 3. Configuring administrative scoping When administrative scoping is disabled, a BIDIR-PIM domain has only one BSR.
Step Command Remarks By default, no multicast forwarding boundary is configured. Configure a multicast forwarding boundary. 3. multicast boundary group-address { mask | mask-length } The group-address { mask | mask-length } argument can specify the multicast groups that an admin-scoped zone serves, in the range of 239.0.0.0/8. Configuring C-BSRs for each admin-scoped zone and the global-scoped zone In a network with administrative scoping enabled, group-range-specific BSRs are elected from C-BSRs.
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 a C-BSR for the global-scoped zone. c-bsr global [ hash-length hash-length | priority priority ] * No C-BSRs are configured for the global-scoped zone by default. Configuring PIM-SSM PIM-SSM needs the support of IGMPv3. Be sure to enable IGMPv3 on PIM routers with multicast receivers.
Step Command Remarks 3. Enter interface view. interface interface-type interface-number N/A 4. Enable PIM-SM. pim sm Disabled by default. Command Description system-view N/A Enabling PIM-SM in a VPN instance Step 1. Enter system view. 2. Create a VPN instance and enter VPN instance view. N/A 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.
Configuration procedure To configure an SSM 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 3. Configure the SSM group range. ssm-policy acl-number Optional. 232.0.0.0/8 by default. Configuring common PIM features For the configuration tasks in this section, the following rules apply: • The configurations made in PIM view are effective on all interfaces.
• Determine the prune message delay (global value/interface level value). • Determine the prune override interval (global value/interface level value). • Determine the prune delay. • Determine the hello interval (global value/interface level value). • Determine the maximum delay between hello message (interface level value). • Determine the assert timeout timer (global value/interface value). • Determine the join/prune interval (global value/interface level value).
Step 2. Enter interface view. Command Remarks interface interface-type interface-number N/A No hello message filter by default. 3. Configure a hello message filter. pim neighbor-policy acl-number When the hello message filter is configured, if hello messages of an existing PIM neighbor fail to pass the filter, the PIM neighbor will be removed automatically when it times out.
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. Set the DR priority. hello-option dr-priority priority 4. Set the neighbor lifetime. hello-option holdtime interval 5. Set the prune message delay. hello-option lan-delay interval 6. Set the override interval. hello-option override-interval interval Optional. 7. Enable the neighbor tracking function.
To set the prune delay timer: 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. Set the prune delay timer. Optional. prune delay interval By default, the prune delay timer is not configured. Configuring common PIM timers PIM routers discover PIM neighbors and maintain PIM neighboring relationship with other routers by periodically sending hello messages.
Step 7. Command Configure the multicast source lifetime. source-lifetime interval Remarks Optional. 210 seconds by default. Configuring common PIM timers 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. Configure the hello interval. pim timer hello interval 4. Configure the maximum delay between hello messages. pim triggered-hello-delay interval Configure the join/prune interval.
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. If the DR fails, a new DR election process will start after the DR is aged out. However, it might take a long period of time.
Task Command Remarks 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. Display information about join/prune messages to send.
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-scoped 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-scoped zone 1, admin-scoped 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-scoped 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] interface GigabitEthernet 2/1/1 [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-GigabitEthernet2/1/1] quit [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.
Interface State DF-Pref DF-Metric DF-Uptime DF-Address 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.
# Display the DF information of the multicast forwarding table on Router D. [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.
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 GE2/1/1 192.168.9.1/24 GE2/1/1 192.168.4.2/24 GE2/1/0 10.110.2.1/24 GE2/1/0 192.168.3.2/24 GE2/1/1 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 Router B Router C Router E Configuration procedure 1.
Use the display pim interface command to display the PIM information on each interface. For example: # 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).
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 report 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.
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.
Enabling MSDP in a VPN instance 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. 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.
Step Configure a static RPF peer. 3. Command Remarks static-rpf-peer peer-address [ rp-policy ip-prefix-name ] No static RPF peer configured by default. 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.
the mesh group. A mesh group member accepts SA messages from other members in the group without performing an RPF check, and does not forward the message within the mesh group. This mechanism not only avoids SA flooding but also simplifies the RPF check mechanism because you do not need to run BGP or MBGP between these MSDP peers. By configuring the same mesh group name for multiple MSDP peers, you can create a mesh group that contains these MSDP peers.
Step Command Remarks Enter public network MSDP view or VPN instance MSDP view. msdp [ vpn-instance vpn-instance-name ] N/A 3. Deactivate an MSDP peer. shutdown peer-address 4. 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 } 2. 5. Optional. Active by default. Optional.
address, it discards the SA message. However, in the Anycast RP application, you must configure RPs with the same IP address on two or more routers in the same PIM-SM domain and configure these routers as MSDP peers to one another. Therefore, a logical RP address (namely, the RP address on the logical interface) that is different from the actual RP address must be designated for SA messages so that the messages can pass the RPF check. To configure the SA message content: Step Command Remarks 1.
A filtering rule for receiving or forwarding SA messages enables the router to filter the (S, G) forwarding entries to be advertised when the router receives or forwards an SA message. This controls the propagation of multicast source information at SA message reception or forwarding.
To protect the router against DoS attacks, you can set a limit on the number of (S, G) entries that the router can cache. To configure the SA message cache: 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 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.
PIM-SM Inter-domain multicast configuration Network requirements As shown in Figure 54, the network has two OSPF ASs: AS 100 and AS 200. BGP runs between the two ASs. PIM-SM 1 belongs to AS 100, and PIM-SM 2 and PIM-SM 3 belong to AS 200. Each PIM-SM domain has at least one multicast source or receiver. Configure Loopback 0 as the C-BSR and C-RP of the related PIM-SM domain on Router B, Router C, and Router E.
Configuration procedure 1. Assign the IP address and subnet mask to each interface according to Figure 54. (Details not shown.) 2. Configure OSPF on the routers to make sure the routers are interoperable at the network layer in each AS, and they can dynamically update routing information. (Details not shown.) 3.
[RouterC-bgp] peer 192.168.3.2 as-number 200 [RouterC-bgp] import-route ospf 1 [RouterC-bgp] quit # Configure an eBGP peer, and redistribute OSPF routes on Router E. [RouterE] bgp 200 [RouterE-bgp] router-id 3.3.3.3 [RouterE-bgp] peer 192.168.3.1 as-number 200 [RouterE-bgp] import-route ospf 1 [RouterE-bgp] quit # Redistribute BGP routing information into OSPF on Router B.
Local AS number : 200 Total number of peers : 1 Peer 192.168.1.1 Peers in established state : 1 AS MsgRcvd 100 18 MsgSent OutQ PrefRcv Up/Down 16 0 State 1 00:12:04 Established # Display BGP routing table information on Router C. [RouterC] display bgp routing-table Total Number of Routes: 5 BGP Local router ID is 2.2.2.
Peer's Address State Up/Down time AS SA Count Reset Count 192.168.3.1 Up 01:07:08 200 8 0 # Display the detailed MSDP peer information on Router B. [RouterB] display msdp peer-status MSDP Peer Information of VPN-Instance: public net MSDP Peer 192.168.1.2, AS 200 Description: Information about connection status: State: Up Up/down time: 00:15:47 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 dampening Optional. 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.
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 1. Enter system view. system-view N/A 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 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 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 attributes of routes 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.
To configure an IPv4 MBGP peer group: 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.
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.
{ Each instance runs PIM independently. 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.
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.
transmittion of the VPN data over the public network. However, 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 share-group addresses and an MTI numbers. • 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.
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. 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.
When switch-group reuse logging is enabled, the generated group address reuse logging information will be sent to the information center, where you can configure the rules for outputting 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.
NOTE: A BGP MDT peer or peer group is a peer or peer group created in BGP-MDT subaddress family view. 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.
Create the receivers' VPN instances on the source-side PE, and • { { For source-side PE configuration, specify the share-group. For receiver-side PE configuration, create the multicast source's VPN instance on the receiver-side PE and specify the share-group. • 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.
Task Command Remarks Display information about BGP MDT peer groups. display bgp mdt group [ group-name ] [ | { begin | exclude | include } regular-expression ] Available in any view. Display information about BGP MDT peers. display bgp mdt peer [ [ ip-address ] verbose ] [ | { begin | exclude | include } regular-expression ] Available in any view. Display BGP MDT routing information.
Item Network requirements IP multicast routing • • • • • Enable IP multicast routing on the P router. Enable IP multicast routing on the public network on PE 1, PE 2, and PE 3. Enable IP multicast routing in VPN instance a on PE 1, PE 2, and PE 3. Enable IP multicast routing in VPN instance b on PE 2 and PE 3. Enable IP multicast routing on CE a1, CE a2, CE a3, CE b1, and CE b2. • Run IGMPv2 on GigabitEthernet 2/1/2 of PE 1. • Run IGMPv2 on GigabitEthernet 2/1/1 of CE a2, CE a3, and CE b2.
R4 — 10.110.11.2/24 P GE2/1/1 192.168.6.2/24 GE2/1/2 192.168.7.2/24 GE2/1/3 192.168.8.2/24 Loop1 2.2.2.2/32 GE2/1/1 192.168.6.1/24 GE2/1/2 10.110.1.1/24 GE2/1/3 10.110.2.1/24 PE 1 PE 2 Loop1 1.1.1.1/32 GE2/1/1 192.168.7.1/24 GE2/1/2 10.110.3.1/24 GE2/1/3 10.110.4.1/24 Loop1 1.1.1.2/32 CE a1 CE a2 CE a3 CE b1 CE b2 GE2/1/1 10.110.7.1/24 GE2/1/2 10.110.2.2/24 GE2/1/1 10.110.9.1/24 GE2/1/2 10.110.4.2/24 GE2/1/3 10.110.12.1/24 Loop1 22.22.22.22/32 GE2/1/1 10.110.10.
# Bind GigabitEthernet 2/1/2 with VPN instance a, configure an IP address and enable IGMP and PIM-SM on the interface. [PE1] interface gigabitethernet 2/1/2 [PE1-GigabitEthernet2/1/2] ip binding vpn-instance a [PE1-GigabitEthernet2/1/2] ip address 10.110.1.1 24 [PE1-GigabitEthernet2/1/2] igmp enable [PE1-GigabitEthernet2/1/2] pim sm [PE1-GigabitEthernet2/1/2] quit # Bind GigabitEthernet 2/1/3 with VPN instance a, configure an IP address and enable PIM-SM on the interface.
# Configure RIP. [PE1] rip 2 vpn-instance a [PE1-rip-2] network 10.0.0.0 [PE1-rip-2] import-route bgp [PE1-rip-2] return 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.
[PE2-GigabitEthernet2/1/1] quit # Bind GigabitEthernet 2/1/2 with VPN instance b, configure an IP address and enable PIM-SM on the interface. [PE2] interface gigabitethernet 2/1/2 [PE2-GigabitEthernet2/1/2] ip binding vpn-instance b [PE2-GigabitEthernet2/1/2] ip address 10.110.3.1 24 [PE2-GigabitEthernet2/1/2] pim sm [PE2-GigabitEthernet2/1/2] quit # Bind GigabitEthernet 2/1/3 with VPN instance a, configure an IP address and enable PIM-SM on the interface.
# Configure OSPF. [PE2] ospf 1 [PE2-ospf-1] area 0.0.0.0 [PE2-ospf-1-area-0.0.0.0] network 1.1.1.2 0.0.0.0 [PE2-ospf-1-area-0.0.0.0] network 192.168.0.0 0.0.255.255 [PE2-ospf-1-area-0.0.0.0] quit [PE2-ospf-1] quit # 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.
[PE3-vpn-instance-b] multicast routing-enable [PE3-vpn-instance-b] multicast-domain share-group 239.2.2.2 binding mtunnel 1 [PE3-vpn-instance-b] multicast-domain switch-group-pool 225.4.4.0 28 [PE3-vpn-instance-b] 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 192.168.8.
[PE3-bgp] peer 1.1.1.1 group vpn-g [PE3-bgp] peer 1.1.1.2 group vpn-g [PE3–bgp] ipv4-family vpn-instance a [PE3-bgp-a] import-route rip 2 [PE3-bgp-a] import-route direct [PE3-bgp-a] quit [PE3–bgp] ipv4-family vpn-instance b [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.
[P-mpls] quit [P] mpls ldp [P-mpls-ldp] quit # Configure an IP address, and enable PIM-SM and LDP capability on the public network interface GigabitEthernet 2/1/1. [P] interface gigabitethernet 2/1/1 [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.
[CEa1] interface gigabitethernet 2/1/1 [CEa1-GigabitEthernet2/1/1] ip address 10.110.7.1 24 [CEa1-GigabitEthernet2/1/1] pim sm [CEa1-GigabitEthernet2/1/1] quit # Configure an IP address and enable PIM-SM on GigabitEthernet 2/1/2. [CEa1] interface gigabitethernet 2/1/2 [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.
[CEa2-GigabitEthernet2/1/3] ip address 10.110.12.1 24 [CEa2-GigabitEthernet2/1/3] pim sm [CEa2-GigabitEthernet2/1/3] quit # Configure an IP address for Loopback 1 and enable PIM-SM on the interface. [CEa2] interface loopback 1 [CEa2-LoopBack1] ip address 22.22.22.22 32 [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.
[CEb2-GigabitEthernet2/1/1] ip address 10.110.11.1 24 [CEb2-GigabitEthernet2/1/1] igmp enable [CEb2-GigabitEthernet2/1/1] pim sm [CEb2-GigabitEthernet2/1/1] quit # Configure an IP address and enable PIM-SM on GigabitEthernet 2/1/2. [CEb2] interface gigabitethernet 2/1/2 [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.
Item Multicast sources and receivers Network requirements • In VPN a, S 1 is a multicast source, and R 2 is a receiver. • In VPN b, S 2 is a multicast source, and R 1 is a receiver. • For VPN a, the share-group address is 239.1.1.1, and the range of its switch-group-pool addresses is 225.1.1.0 to 225.1.1.15. • For VPN b, the share-group address is 239.4.4.4, and the range of its switch-group-pool addresses is 225.4.4.0 to 225.4.4.15. • PE 1—GigabitEthernet 2/1/2 belongs to VPN instance a.
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 guide 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.
{ { 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. If the router does not use the longest match principle, it selects the route that has a higher priority 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.
Configuring an IPv6 multicast routing policy You can configure the router to select the RPF route based on the longest match principle. For more information about RPF route selection, see "RPF check mechanism." By configuring per-source or per-source-and-group load splitting, you can optimize the traffic delivery when multiple IPv6 multicast data streams are handled. To configure an IPv6 multicast routing policy: Step Command Remarks system-view N/A 1. Enter system view. 2.
Configuring the IPv6 multicast forwarding table size The router maintains the corresponding forwarding entry for each IPv6 multicast packet that it receives. Excessive IPv6 multicast routing entries, however, can exhaust the router's memory and cause lower performance. You can set an upper limit on the number of entries in the IPv6 multicast forwarding table based on the actual networking situation and the performance requirements.
Step Command Remarks 1. Enter system view. system-view N/A 2. Configure a static multicast MAC address entry. mac-address multicast mac-address interface interface-list vlan vlan-id No static multicast MAC address entries existing by default. Configuring an IPv6 static multicast MAC address entry in interface view 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.
Task Command Remarks Display information about the IPv6 multicast forwarding table (in standalone mode).
Task Command Remarks Available in user view. Clear routing entries from the IPv6 multicast routing table. When a routing entry is removed from the IPv6 multicast routing table, the corresponding forwarding entry is also removed from the IPv6 multicast forwarding table.
# On Router A, specify the tunnel encapsulation mode as GRE over IPv6 and assign the source and destination addresses to interface Tunnel 0. [RouterA-Tunnel0] tunnel-protocol gre ipv6 [RouterA-Tunnel0] source 2001::1 [RouterA-Tunnel0] destination 3001::2 [RouterA-Tunnel0] quit # Create interface Tunnel 0 on Router C and assign the IPv6 address and prefix length to interface Tunnel 0.
[RouterC-Gigabitethernet2/1/1] ospfv3 1 area 0 [RouterC-Gigabitethernet2/1/1] quit [RouterC] interface gigabitethernet 2/1/2 [RouterC-Gigabitethernet2/1/2] ospfv3 1 area 0 [RouterC-Gigabitethernet2/1/2] quit [RouterC] interface tunnel 0 [RouterC-Tunnel0] ospfv3 1 area 0 [RouterC-Tunnel0] quit 4. Enable IPv6 multicast routing, IPv6 PIM-DM, and MLD: # On Router A, enable IPv6 multicast routing globally, and enable IPv6 PIM-DM on each interface.
Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Gigabitethernet2/1/1 Protocol: igmp, UpTime: 00:04:25, Expires: never (1001::100, FF1E::101) Protocol: pim-dm, Flag: ACT UpTime: 00:06:14 Upstream interface: Tunnel0 Upstream neighbor: 5001::1 RPF prime neighbor: 5001::1 Downstream interface(s) information: Total number of downstreams: 1 1: Gigabitethernet2/1/1 Protocol: pim-dm, UpTime: 00:04:25, Expires: never The output shows that Rout
of the IPv6 multicast packets and the IPv6 multicast group address can both match the IPv6 ACL rule.
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.
Setting the maximum number of IPv6 multicast groups that an interface can join 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.
An MLD message is processed differently depending on whether it carries the Router-Alert option in the IPv6 header, as follows: • For compatibility, the device by default ignores the Router-Alert option and processes all received MLD messages, no matter whether the MLD messages carry the Router-Alert option or not. • To enhance device performance, avoid unnecessary costs, and ensure protocol security, configure the device to discard MLD messages that do not carry the Router-Alert option.
multicast group and multicast source mapping change report. The number of queries, or the last listener query count, equals the robustness variable—the maximum number of packet retransmissions. A multicast listening host starts a timer for each IPv6 multicast group that it has joined when it receives an MLD query (general query), multicast-address-specific query, or multicast-address-and-source-specific query.
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.
these MLD proxy devices has been elected as the querier. Otherwise, duplicate multicast flows might be received on the shared-media network. 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.
Task Command Remarks Display MLD SSM mappings. display mld ssm-mapping ipv6-group-address [ | { begin | exclude | include } regular-expression ] Available in any view. Display the IPv6 multicast group information created based on the configured MLD SSM mappings. display mld ssm-mapping group [ ipv6-group-address | interface interface-type interface-number ] [ verbose ] [ | { begin | exclude | include } regular-expression ] Available in any view.
The hosts in N1 can only join IPv6 multicast group FF1E::101, and the hosts in N2 can join any IPv6 multicast 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.
[RouterB] interface pos 5/1/0 [RouterB-Pos5/1/0] pim ipv6 dm [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.
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).
4. Use the display current-configuration interface command to verify that no ACL rule has been configured to restrict the host from joining IPv6 multicast group G. If an IPv6 ACL is configured to 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.
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.
• Graft • 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.
Figure 88 SPT establishment in an IPv6 PIM-DM domain Host A Source Receiver Host B Server Receiver SPT Prune message IPv6 multicast packets Host C The flood-and-prune process takes place periodically. A pruned state timeout mechanism is provided. A pruned branch restarts multicast forwarding when the pruned state times out. If the branch does not have any IPv6 multicast receiver, it is pruned again. NOTE: Pruning has a similar implementation in IPv6 PIM-SM.
Figure 89 Assert mechanism As shown in Figure 89, the assert mechanism is as follows: 1. After Router A and Router B receive an (S, G) IPv6 multicast packet from the upstream node, both of them forward the packet to the local subnet. As a result, the downstream node Router C receives two identical multicast packets, and both Router A and Router B, on their own downstream interfaces, receive a duplicate IPv6 multicast packet that the other has forwarded. 2.
RPTs. An RPT is rooted at a router in the IPv6 PIM domain as the common node, or RP, through which the IPv6 multicast data travels along the RPT and reaches the receivers. • When a receiver is interested in the IPv6 multicast data addressed to a specific IPv6 multicast group, the router connected to this receiver sends a join message to the RP corresponding to that IPv6 multicast group. The path along which the message goes hop-by-hop to the RP forms a branch of the RPT.
Figure 90 DR election As shown in Figure 90, the DR election process is as follows: 1. Routers on the shared-media network send hello messages to one another. The hello messages contain the router priority for DR election. The router with the highest DR priority will become the DR. 2.
Figure 91 BSR and C-RPs Based on the information in the RP-sets, all routers in the network can calculate the location of the corresponding RPs based on the following rules: 1. The C-RP with the highest priority wins. 2. If all the C-RPs have the same priority, their hash values are calculated through the hashing algorithm. The C-RP with the largest hash value wins. 3. If all the C-RPs have the same priority and hash value, the C-RP that has the highest IP address wins.
At the receiver side: • a. A receiver host initiates an MLD report to announce that it is joining an IPv6 multicast group. b. After receiving the MLD report, the receiver-side DR resolves the RP address embedded in the IPv6 multicast address and sends a join message to the RP. At the IPv6 multicast source side: • c. The IPv6 multicast source sends IPv6 multicast traffic to the IPv6 multicast group. d.
Figure 93 IPv6 multicast source registration As shown in Figure 93, the IPv6 multicast source registers with the RP as follows: 1. The IPv6 multicast source S sends the first IPv6 multicast packet to IPv6 multicast group G. 2. After receiving the multicast packet, the DR that directly connects to the multicast source encapsulates the packet in a 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.
• The DR at the source side and the RP need to implement complicated encapsulation and de-encapsulation of IPv6 multicast packets. • IPv6 multicast packets are delivered along a path that might not be the shortest one. • An increase in IPv6 multicast traffic heavily burdens the RP, increasing the risk of failure.
Neighbor discovery IPv6 BIDIR-PIM uses the same neighbor discovery mechanism as IPv6 PIM-SM does. For more information, see "Neighbor discovery." RP discovery IPv6 BIDIR-PIM uses the same RP discovery mechanism as IPv6 PIM-SM does. For more information, see "RP discovery." In IPv6 PIM-SM, an RP must be specified with a real IPv6 address. In IPv6 BIDIR-PIM, however, an RP can be specified with a virtual IPv6 address, which is called the rendezvous point address (RPA).
3. In the case of a tie in the priority, 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 link-local IPv6 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 with the receivers as leaves.
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.
multicast protocol packets, such as assert messages and bootstrap messages, for a specific group range cannot cross the IPv6 admin-scoped zone boundary. IPv6 multicast group ranges served by different IPv6 admin-scoped zones can overlap. An IPv6 multicast group is valid only within its local IPv6 admin-scoped zone, functioning as a private group address. The IPv6 global-scoped 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-scoped 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.
pruned state timer of all the routers on the path. A shared-media subnet can have the state-refresh capability only if the state-refresh capability is enabled on all IPv6 PIM routers on the subnet. To enable the state-refresh capability: Step Command Remarks 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.
it sends a graft message, the router keeps sending new graft messages at a configurable interval (namely, graft retry period) until it receives a graft-ack message from the upstream router. To configure the IPv6 PIM-DM graft retry period: 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.
Configuration prerequisites Before you configure IPv6 PIM-SM, complete the following tasks: • Enable IPv6 forwarding and configure an IPv6 unicast routing protocol so that all devices in the 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 Command Remarks No C-RPs are configured by default. 3. Configure an interface to be a C-RP for IPv6 PIM-SM. c-rp ipv6-address [ { group-policy acl6-number | scope scope-id } | priority priority | holdtime hold-interval | advertisement-interval adv-interval ] * 4. Configure a legal C-RP address range and the range of IPv6 multicast groups to be served. crp-policy acl6-number Optional. No restrictions by default.
Step Command Remarks N/A 2. Enter IPv6 PIM view. pim ipv6 3. Configure the C-RP-Adv interval. c-rp advertisement-interval interval Configure C-RP timeout timer. c-rp holdtime interval 4. Optional. 60 seconds by default. Optional. 150 seconds by default. 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.
Because the BSR and the other devices exchange a large amount of information in the IPv6 PIM-SM domain, provide a relatively large bandwidth between the C-BSRs and the other devices. To complete basic BSR configuration: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. pim ipv6 N/A 3. Configure an interface as a C-BSR. c-bsr ipv6-address [ hash-length [ priority ] ] No C-BSRs are configured by default. 4. Configure a legal BSR address range.
Step 4. Command Configure the C-BSR priority. c-bsr priority priority Remarks Optional. 64 by default. Configuring C-BSR timers The BSR election winner multicasts its own IPv6 address and RP-set information throughout the region that it serves through bootstrap messages. The BSR floods bootstrap messages throughout the network at the interval of the BS (BSR state) period.
• After receiving a BSMF that contains the RP-set information of one group range, a non-BSR router updates corresponding RP-set information directly. • If the RP-set information of one group range is carried in multiple BSMFs, a non-BSR router updates corresponding RP-set information after receiving all these BSMFs. Because the RP-set information contained in each segment is different, loss of some IP fragments will not result in dropping of the entire message.
packets (such as assert messages and bootstrap messages) that belong to this range cannot cross the admin-scoped zone boundary. Perform the following configuration on routers that you want to configure as a ZBR. To configure an IPv6 admin-scoped zone boundary: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A Configure an IPv6 multicast forwarding boundary.
Configuring IPv6 multicast source registration Within an IPv6 PIM-SM domain, the source-side DR sends register messages to the RP, and these register messages have different IPv6 multicast source or IPv6 multicast group addresses. You can configure a filtering rule to filter register messages so that the RP can serve specific IPv6 multicast groups.
Perform the following configuration on routers that might become receiver-side DRs and on C-RP routers. To configure switchover to SPT: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. pim ipv6 N/A Configure the criteria for triggering a switchover to SPT. spt-switch-threshold infinity [ group-policy acl6-number [ order order-value ] ] Optional. 3.
• Enable IPv6 forwarding and configure an IPv6 unicast routing protocol so that all devices in the domain can communicate with each other at Layer 3. • Determine the IPv6 address of a static RP and the IPv6 ACL that defines the range of IPv6 multicast groups to be served by the static RP. • Determine the C-RP priority and the IPv6 ACL that defines 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 means 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 3. Configure an interface to be a C-RP for IPv6 BIDIR-PIM. Command Remarks c-rp ipv6-address [ { group-policy acl6-number | scope scope-id } | priority priority | holdtime hold-interval | advertisement-interval adv-interval ] * bidir No C-RP is configured by default. Enabling embedded RP With the embedded RP feature enabled, the router can resolve the RP address directly from the IPv6 multicast group address of an IPv6 multicast packets.
Step 4. Command Configure C-RP timeout timer. c-rp holdtime interval Remarks Optional. 150 seconds by default. For more information about the configuration of other timers in IPv6 PIM-SM, see "Configuring common IPv6 PIM timers." Configuring a BSR An IPv6 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 IPv6 BIDIR-PIM domain.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. pim ipv6 N/A 3. Configure an interface as a C-BSR. c-bsr ipv6-address [ hash-length [ priority ] ] No C-BSRs are configured by default. 4. Configure a legal BSR address range. Optional. bsr-policy acl6-number No restrictions on BSR address range by default.
Configuring C-BSR timers The BSR election winner multicasts its own IPv6 address and RP-Set information through bootstrap messages within the entire zone it serves. The BSR floods bootstrap messages throughout the network at the interval of BS (BSR state) period. Any C-BSR that receives a bootstrap message retains the RP-set for the length of BS timeout timer, during which no BSR election takes place.
Because the RP-set information contained in each segment is different, loss of some IP fragments will not result in dropping of the entire message. Generally, a BSR performs BSM semantic fragmentation according to the MTU of its BSR interface. However, the semantic fragmentation of BSMs originated due to learning of a new PIM neighbor is performed according to the MTU of the outgoing interface. The function of BSM semantic fragmentation is enabled by default.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A Configure an IPv6 multicast forwarding boundary. multicast ipv6 boundary { ipv6-group-address prefix-length | scope { scope-id | admin-local | global | organization-local | site-local } } By default, no IPv6 multicast forwarding boundary is configured. 3.
IPv6 PIM-SSM configuration task list Task Remarks Enabling IPv6 PIM-SM Required. Configuring the IPv6 SSM group range Optional. Configuring common IPv6 PIM features Optional. Configuration prerequisites Before you configure IPv6 PIM-SSM, complete the following tasks: • Enable IPv6 forwarding and configure an IPv6 unicast routing protocol so that all devices in the domain are interoperable at the network layer. • Determine the IPv6 SSM group range.
• Make sure the same IPv6 SSM group range is configured on all routers in the entire domain. Otherwise, IPv6 multicast data cannot be delivered through the IPv6 SSM model. • When a member of an IPv6 multicast group in the IPv6 SSM group range sends an MLDv1 report message, the device does not trigger a (*, G) join. Configuration procedure To configure the IPv6 SSM group range: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. pim ipv6 N/A 3.
• Determine the priority for DR election (global value/interface level value). • Determine the IPv6 PIM neighbor timeout timer (global value/interface value). • Determine the prune message delay (global value/interface level value). • Determine the prune override interval (global value/interface level value). • Determine the prune delay. • Determine the hello interval (global value/interface level value). • Determine the maximum delay between hello message (interface level value).
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A No hello message filter by default. 3. Configure a hello message filter. pim ipv6 neighbor-policy acl6-number When the hello message filter is configured, if the hello messages of an existing IPv6 PIM neighbor fail to pass the filter, the IPv6 PIM neighbor will be removed automatically when it times out.
Configuring hello options globally Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. pim ipv6 N/A 3. Set the DR priority. hello-option dr-priority priority 4. Set the neighbor lifetime. hello-option holdtime interval 5. Set the prune message delay. hello-option lan-delay interval 6. Set the override interval. hello-option override-interval interval Optional. 7. Enable the neighbor tracking function.
delay timer defines. In this period, if the upstream router receives a join message from the downstream router, it cancels the prune action. Otherwise, it performs the prune action. To set the prune delay timer: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. pim ipv6 N/A 3. Set the prune delay timer. Optional. prune delay interval By default, no prune delay timer is set.
Step 6. 7. Command Configure assert timeout timer. holdtime assert interval Configure the IPv6 multicast source lifetime. source-lifetime interval Remarks Optional. 180 seconds by default. Optional. 210 seconds by default. Configuring common IPv6 PIM timers 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. Configure the hello interval. pim ipv6 timer hello interval 4.
Displaying and maintaining IPv6 PIM Task Command Remarks Display information about the BSR in the IPv6 PIM-SM domain and the locally configured C-RPs in effect. display pim ipv6 bsr-info [ | { begin | exclude | include } regular-expression ] Available in any view. Display information about the IPv6 unicast routes used by IPv6 PIM. display pim ipv6 claimed-route [ ipv6-source-address ] [ | { begin | exclude | include } regular-expression ] Available in any view.
IPv6 PIM configuration examples This section provides examples of configuring IPv6 PIM on routers. IPv6 PIM-DM configuration example Network requirements The receivers receive VOD information through multicast. The receiver groups of different organizations form stub networks, and at least one receiver host exists in each stub network. The entire IPv6 PIM domain operates in the dense mode. Host A and Host C are IPv6 multicast receivers in two stub networks N1 and N2.
2. Configure OSPFv3 on the routers in the IPv6 PIM-DM domain to make sure they are interoperable at the network layer. (Details not shown.) 3. Enable IPv6 multicast routing, IPv6 PIM-DM, and MLD: # Enable IPv6 multicast routing on Router A, and enable IPv6 PIM-DM on each interface and enable MLD on GigabitEthernet 2/1/1, which connects Router A to N1.
Total Number of Neighbors = 3 Neighbor Interface Uptime Expires Dr-Priority 1002::1 Ser3/1/0 00:04:00 00:01:29 1 2002::1 Pos5/1/0 00:04:16 00:01:29 3 3001::1 Pos5/1/1 00:03:54 00:01:17 5 Assume that Host A needs to receive information addressed to IPv6 multicast group G FF0E::101. Once the IPv6 multicast source S 4001::100/64 sends IPv6 multicast packets to the IPv6 multicast group G, an SPT is established through traffic flooding.
Total number of downstreams: 3 1: Serial3/1/0 Protocol: pim-dm, UpTime: 00:02:19, Expires: never 2: Pos5/1/0 Protocol: pim-dm, UpTime: 00:02:19, Expires: never 3: Pos5/1/1 Protocol: pim-dm, UpTime: 00:02:19, Expires: never IPv6 PIM-SM non-scoped zone configuration example Network requirements 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.
Router B Router C GE2/1/1 2001::1/64 POS5/1/0 3001::2/64 POS5/1/0 2002::1/64 Router E POS5/1/1 2002::2/64 GE2/1/1 2001::2/64 POS5/1/2 1003::2/64 POS5/1/0 3001::1/64 POS5/1/3 4002::2/64 Configuration procedure 1. Enable IPv6 forwarding on each router and configure the IPv6 address and prefix length for each interface according to Figure 102. (Details not shown.) 2. Configure OSPFv3 on the routers in the IPv6 PIM-DM domain to ensure network-layer reachability among them.
[RouterE] pim ipv6 [RouterE-pim6] c-bsr 1003::2 128 20 [RouterE-pim6] c-rp 1003::2 group-policy 2005 [RouterE-pim6] quit 5. Verify the configuration: Use the display pim ipv6 interface command to display IPv6 PIM information on each interface. For example: # Display IPv6 PIM information on Router A.
Next BSR message scheduled at: 00:01:48 Candidate BSR Address: 1003::2 Priority: 20 Hash mask length: 128 State: Elected Candidate RP: 1003::2(Pos5/1/2) Priority: 192 HoldTime: 130 Advertisement Interval: 60 Next advertisement scheduled at: 00:00:48 # Display RP information on Router A.
Protocol: mld, UpTime: 00:02:15, Expires: 00:03:06 (4001::100, FF0E::100) RP: 1003::2 Protocol: pim-sm, Flag: SPT ACT UpTime: 00:02:15 Upstream interface: Serial3/1/0 Upstream neighbor: 1002::2 RPF prime neighbor: 1002::2 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet2/1/1 Protocol: pim-sm, UpTime: 00:02:15, Expires: 00:03:06 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.
IPv6 PIM-SM admin-scoped zone configuration example Network requirements The receivers receive VOD information through multicast. The entire IPv6 PIM-SM domain is divided into IPv6 admin-scoped zone 1, IPv6 admin-scoped zone 2, and the IPv6 global-scoped 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 FF14::101.
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-scoped 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-scoped 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
Figure 104 Network diagram Loop0 Receiver 1 Receiver 2 Router B GE2/1/1 S3/1/2 S3/1/1 Router C Host A Host B S3/1/2 S3/1/1 Source 1 S3/1/1 S3/1/1 G E2 /1 /1 IPv6 BIDIR-PIM GE2/1/1 Source 2 GE2/1/2 Router A Router D 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/1 1002::1/64 GE2/1/2 5001::1/64 GE2/1/1 2001::1/64 S3/1/1 3001::2/64 Router B Router C S3/1/1 1002::2/64 Source 1 - 1001::2/64 S
system-view [RouterB] multicast ipv6 routing-enable [RouterB] interface gigabitethernet 2/1/1 [RouterB-GigabitEthernet2/1/1] mld enable [RouterB-GigabitEthernet2/1/1] pim ipv6 sm [RouterB-GigabitEthernet2/1/1] quit [RouterB] interface serial 3/1/1 [RouterB-Serial3/1/1] pim ipv6 sm [RouterB-Serial3/1/1] quit [RouterB] interface serial 3/1/2 [RouterB-Serial3/1/2] pim ipv6 sm [RouterB-Serial3/1/2] quit [RouterB] pim ipv6 [RouterB-pim6] bidir-pim enable [RouterB-pim6] quit # On Router C, enable IPv6
# On Router C, configure Serial 3/1/1 as a C-BSR, and loopback interface 0 as a C-RP for the entire IPv6 BIDIR-PIM domain. [RouterC-pim6] c-bsr 3001::2 [RouterC-pim6] c-rp 6001::1 bidir [RouterC-pim6] quit 5. Verify the configuration: # Display the DF information of IPv6 BIDIR-PIM on Router A.
[RouterA] display multicast ipv6 forwarding-table df-info Multicast DF information Total 1 RP Total 1 RP matched 00001. RP Address: 6001::1 MID: 0, Flags: 0x2100000:0 Uptime: 00:08:32 RPF interface: Serial3/1/1 List of 1 DF interfaces: 1: GigabitEthernet2/1/1 # Display the DF information of the IPv6 multicast forwarding table on Router B. [RouterB] display multicast ipv6 forwarding-table df-info Multicast DF information Total 1 RP Total 1 RP matched 00001.
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 IPv6 PIM-SSM configuration example Network requirements 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 IPv6 PIM domain operates in the SSM mode.
Configuration procedure 1. Enable IPv6 forwarding on each router and configure the IPv6 address and prefix length for each interface according to Figure 105. (Details not shown.) 2. Configure OSPFv3 on the routers in the IPv6 PIM-SSM domain to ensure network-layer reachability among them. (Details not shown.) 3.
Assume that Host A needs to receive the information a specific IPv6 multicast source S (4001::100/64) sends to multicast group G (FF3E::101). Router A builds an SPT toward the multicast source. Routers on the SPT path (Router A and Router D) have generated an (S, G) entry, but Router E, which is not on the SPT path, does not have multicast routing entries. You can use the display pim ipv6 routing-table command to display the PIM routing table information on each router.
Analysis • An IPv6 PIM routing entry is created based on an IPv6 unicast route, whichever IPv6 PIM mode is running. Multicast works only when unicast does. • IPv6 PIM must be enabled on the RPF interface. An RPF neighbor must be an IPv6 PIM neighbor as well. If IPv6 PIM is not enabled on the RPF interface or the RPF neighbor, the establishment of a multicast distribution tree will surely fail, resulting in abnormal multicast forwarding.
RPT cannot be established or a source cannot register in IPv6 PIM-SM Symptom C-RPs cannot unicast advertise messages to the BSR. The BSR does not advertise bootstrap messages containing C-RP information and has no unicast route to any C-RP. An RPT cannot be established correctly, or the DR cannot perform source registration with the RP. Analysis • C-RPs periodically send advertisement messages to the BSR by unicast.
Contents 389
390
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 Enabling the IPv6 MBGP ORF capability Optional. 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.
value command. To learn how to use a routing policy to set a preferred value, see the peer { ipv6-group-name | ipv6-address } route-policy route-policy-name { import | export } command and the 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.
Step Command Description ipv6-family multicast N/A 3. Enter IPv6 MBGP multicast address family view. 4. 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 ] * ] 5. Optional. Default route redistribution is not allowed by default. Not enabled by default.
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. ipv6-family multicast N/A • Configure inbound route filtering: filter-policy { acl6-number | ipv6-prefix ipv6-prefix-name } import • Apply a routing policy to routes from a peer or a peer group: peer { ipv6-group-name | ipv6-address } route-policy route-policy-name import 4.
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 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. 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.
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 4. Create an IPv6 BGP peer group. group ipv6-group-name [ external | internal ] N/A 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.
Configuring an IPv6 MBGP route reflector To guarantee connectivity between IPv6 multicast IBGP peers, you must make them fully meshed. However, this becomes impractical when too many IPv6 multicast IBGP peers exist. Using route reflectors can solve the problem. 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.
Task Command Remarks Display IPv6 MBGP peer information or peer group information. display bgp ipv6 multicast peer [ [ ipv6-address ] verbose ] [ | { begin | exclude | include } regular-expression ] Available in any view. Display the prefix entries in the ORF information for the specified BGP peer. display bgp ipv6 multicast peer ipv6-address received ipv6-prefix [ | { begin | exclude | include } regular-expression ] Available in any view. Display IPv6 MBGP routing table information.
Task Command Remarks Display the multicast routing information for the specified destination address. display ipv6 multicast routing-table ipv6-address prefix-length [ longer-match ] [ verbose ] [ | { 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.
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.
a. Maintains the router ports according to the received PIM hello messages that PIM routers send. 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 neighbor information (in IRF mode). display pim-snooping neighbor [ [ vlan vlan-id ] [ chassis chassis-number slot slot-number ] ] [ | { begin | exclude | include } regular-expression ] Available in any view. Display PIM snooping routing entries (in standalone mode). display pim-snooping routing-table [ [ vlan vlan-id ] [ slot slot-number ] ] [ | { begin | exclude | include } regular-expression ] Available in any view.
Configuration procedure 1. Assign an IP address and subnet mask to each interface according to Figure 108. (Details not shown.) 2. On Router A, enable IP multicast routing, enable PIM-SM on each interface, and configure interface Ethernet 1/2 as a C-BSR and C-RP.
7. Verify the configuration: # On Router E, display the PIM snooping neighbor information of VLAN 100. [RouterE] display pim-snooping neighbor vlan 100 Total number of neighbors: 4 VLAN ID: 100 Total number of neighbors: 4 Neighbor Port Expires Option Flags 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.
Analysis 1. IGMP snooping or PIM snooping is not enabled. 2. PIM snooping is operating in a PIM-DM network. 1. Use the display current-configuration command to check the status of IGMP snooping and PIM snooping. 2. If IGMP snooping is not enabled, enter system view and use the igmp-snooping command to enable IGMP snooping globally. Then, enter VLAN view and use the igmp-snooping enable and pim-snooping enable commands to enable IGMP snooping and PIM snooping for the VLAN. 3.
Configuring multicast VLANs Overview 0 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). In this case, a large amount of network bandwidth is used and an extra burden is added to the Layer 3 device.
Figure 109 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 110, 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.
For more information about the port link-type, port hybrid pvid vlan, and port hybrid vlan commands, see Layer 2—LAN Switching Command Reference. Configuring multicast VLAN ports In this method, you configure a VLAN as a multicast VLAN and assign user ports to it. You can do it by either adding the user ports to the multicast VLAN or specifying the multicast VLAN on the user ports. These two methods provide the same result.
Setting the maximum number of forwarding entries in a multicast VLAN You can configure the maximum number of entries in the IGMP snooping forwarding table of a multicast VLAN. When the number of forwarding entries maintained for a multicast VLAN reaches the threshold, the device creates no more forwarding entries until some entries age out or are manually removed.
Figure 111 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 MLD proxying,302 A Configuring MLD SSM mapping,301 Adjusting IGMP performance,78 Configuring multicast routing and forwarding,53 Adjusting MLD performance,296 Configuring PIM snooping,21 Appendix,46 Configuring PIM-DM,111 C Configuring PIM-SM,114 Configuration examples,59 Configuring PIM-SSM,136 Configuration task list,52 Configuring SA message related parameters,180 Configuration task list,275 Contacting HP,39 Configuring a large scale IPv6 MBGP network,12 C
IGMP snooping configuration examples,34 Overview,272 IGMP snooping configuration task list,18 Overview,96 IPv6 MBGP configuration example,16 Overview,170 IPv6 MBGP configuration task list,1 Overview,13 IPv6 multicast forwarding over GRE tunnel configuration example,280 Overview,68 IPv6 PIM configuration examples,359 Overview,285 Overview,1 M P MBGP configuration example,218 PIM configuration examples,145 MBGP configuration task list,202 PIM snooping configuration example,22 MBGP overview,
