Page 1: Configuration Guide
Configuration Guide Abstract This document describes the software features for the HP A Series products and guides you through the software configuration procedures. These configuration guides also provide configuration examples to help you apply software features to different network scenarios.
Page 2 The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an...
Page 3: Table Of Contents
Contents Configuring IP multicast ··············································································································································· 1 Comparing information transmission techniques ··········································································································· 1 Unicast ······································································································································································· 1 Broadcast ·································································································································································· 2 Multicast ···································································································································································· 2 Multicast features ······························································································································································ 3 Multicast common notations ············································································································································· 4 Multicast advantages and applications ·························································································································· 4 ...
Page 4 Configuring the function of dropping unknown multicast data ········································································ 28 Configuring IGMP report suppression ················································································································ 28 Configuring maximum multicast groups that can be joined on a port ···························································· 29 Configuring multicast group replacement ··········································································································· 29 Configuring 802.1p precedence for IGMP messages ······················································································ 30 ...
Page 5 Configuring the maximum number of multicast groups on an interface ·························································· 73 Adjusting IGMP performance ······································································································································· 73 Prerequisites ··························································································································································· 73 Configuring IGMP message options ··················································································································· 74 Configuring IGMP query and response parameters ························································································· 75 Configuring IGMP fast leave processing ············································································································ 77 ...
Page 6 Configuring state-refresh parameters ················································································································ 109 Configuring PIM-DM graft retry period ············································································································· 110 Configuring PIM-SM ············································································································································ 110 Configuration prerequisites ································································································································ 110 Enabling PIM-SM ················································································································································· 111 Configuring an RP ··············································································································································· 111 Configuring a BSR ··············································································································································· 113 ...
Page 7 Configuring MSDP peer connection control ····································································································· 171 Configuring SA messages related parameters ········································································································· 172 Prerequisites ························································································································································· 172 Configuring SA message content ······························································································································· 172 Configuring SA request messages ····················································································································· 173 Configuring SA message filtering rules ············································································································· 173 ...
Page 8 Introduction to MD-VPN ······································································································································ 214 Basic concepts in MD-VPN ································································································································· 214 Introduction to multicast across VPNs ··············································································································· 217 Protocols and standards ····································································································································· 220 Implementing MD-VPN ················································································································································ 220 Establishing share-MDT ······································································································································· 220 Share-MDT-based delivery ································································································································· 223 ...
Page 9 Configuring static joining ··································································································································· 279 Configuring an IPv6 multicast group filter ········································································································ 280 Configuring the maximum number of IPv6 multicast groups on an interface ··············································· 280 Adjusting MLD performance ······································································································································· 280 Prerequisites ························································································································································· 280 Configuring MLD message options ··················································································································· 281 ...
Page 10 Configuring IPv6 PIM-SSM ·········································································································································· 331 Configuration prerequisites ································································································································ 331 Enabling IPv6 PIM-SM········································································································································· 331 Configuring the IPv6 SSM group range ··········································································································· 332 Configuring IPv6 PIM common features ············································································································ 332 Configuration prerequisites ································································································································ 332 Configuring an IPv6 multicast data filter··········································································································· 333 ...
Page 11 Clearing IPv6 MBGP information ······················································································································ 383 IPv6 MBGP configuration example ···························································································································· 383 Support and other resources ·································································································································· 387 Contacting HP ······························································································································································ 387 Subscription service ············································································································································ 387 Related information ······················································································································································ 387 Documents ···························································································································································· 387 ...
Page 12: Configuring Ip Multicast
Configuring IP multicast This document focuses on the IP multicast technology and device operations. Unless otherwise stated, the term multicast in this document refers to IP multicast. Using multicast technology, a network operator can easily provide new value-added services, such as live webcasting, web TV, distance learning, telemedicine, web radio, real-time video conferencing, and other bandwidth-critical and time-critical information services.
Page 13: Broadcast
Unicast is not suitable for batch transmission of information. Broadcast In broadcast transmission, the information source sends information to all hosts on the subnet, even if some hosts do not need the information. Figure 2 Broadcast transmission In Figure 2, assume that only Hosts B, D, and E need the information. If the information is broadcast to the subnet, Hosts A and C also receive it.
Page 14: Multicast Features
Figure 3 Multicast transmission The multicast source sends only one copy of the information to a multicast group. In Figure 3, Hosts B, D, and E, which are receivers of the information, must join the multicast group. The routers on the network duplicate and forward the information based on the distribution of the group members.
Page 15: Multicast Common Notations
For a better understanding of the multicast concept, you can compare multicast transmission to the transmission of TV programs. Table 1 An analogy between TV transmission and multicast transmission TV transmission Multicast transmission A TV station transmits a TV program through a A multicast source sends multicast data to a multicast channel.
Page 16: Multicast Models
Multicast models Multicast models, including ASM, SFM, and SSM, determine how receivers treat multicast sources. ASM model In the ASM model, any sender can send information to a multicast group as a multicast source, and receivers can join a multicast group (identified by a group address) and obtain multicast information addressed to that multicast group.
Page 17: Multicast Addresses
Multicast addresses Network-layer multicast addresses (multicast IP addresses) 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. IPv4 multicast addresses IANA assigned the Class D address space (224.0.0.0 to 239.255.255.255) for IPv4 multicast. Table 2 Class D IP address blocks and description Address block Description...
Page 18 Address Description 224.0.0.14 RSVP encapsulation 224.0.0.15 All CBT routers 224.0.0.16 Designated SBM 224.0.0.17 All SBMs 224.0.0.18 VRRP IPv6 multicast addresses Figure 4 IPv6 multicast format 0xFF Flags Scope Group ID (112 bits) Referring to Figure 4, the fields of an IPv6 multicast address indicate the following: 0xFF—Most significant eight bits are 11111111, indicating that this address is an IPv6 multicast •...
Page 19 Table 5 Values of the Scope field Value Meaning 0, F Reserved Interface-local scope Link-local scope Subnet-local scope Admin-local scope Site-local scope 6, 7, 9 through D Unassigned Organization-local scope Global scope Group ID—Contains 112 bits and uniquely identifies an IPv6 multicast group that is within the scope •...
Page 20: Multicast Protocols
IPv6 multicast MAC addresses The most-significant 16 bits of an IPv6 multicast MAC address are 0x3333. The remaining 32 bits are the least-significant 32 bits of a multicast IPv6 address. Figure 7 An example of IPv6-to-MAC address mapping Multicast protocols Generally, Layer 3 multicast refers to IP multicast working at the network layer.
Page 21: Multicast Routing Protocols
Multicast group management protocols Typically, IGMP or MLD is used between hosts and Layer 3 multicast devices directly connected to the hosts. 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 to forward multicast packets correctly and efficiently.
Page 22: Multicast Packet Forwarding Mechanism
Multicast VLAN/IPv6 multicast VLAN In the traditional multicast on-demand mode, when users in different VLANs on a Layer 2 device need multicast information, the upstream Layer 3 device needs to forward a separate copy of the multicast data to each VLAN of the Layer 2 device. When the multicast VLAN or IPv6 multicast VLAN feature is enabled on the Layer 2 device, the Layer 3 multicast device sends only one copy of the multicast data to the multicast VLAN or IPv6 multicast VLAN on the Layer 2 device.
Page 23: Multi-Instance Multicast Applications
Figure 10 Networking diagram for VPN VPN A CE a2 CE b2 CE b3 PE 2 VPN B VPN B CE b1 CE a1 CE a3 PE 1 PE 3 Public network VPN A VPN A As shown in Figure 10, VPN A and VPN B separately access the public network through PE devices.
Page 24: Configuring Igmp Snooping
Configuring IGMP snooping Whenever mentioned in this document, a router port is a port on the switch that leads the switch to a Layer 3 multicast device, rather than a port on a router. Unless otherwise specified, router/member ports mentioned in this document include static and dynamic ports.
Page 25 As shown in Figure 12, Router A connects to the multicast source, IGMP snooping runs on Switch A and Switch B, and Host A and Host C are receiver hosts (namely, multicast group members). Figure 12 IGMP snooping related ports Receiver Router A Switch A...
Page 26: Understanding Igmp Snooping
Understanding IGMP snooping A switch running IGMP snooping performs different actions when it receives different IGMP messages. The description about adding or deleting a port in this section is only for a dynamic port. Static ports can be added or deleted only through the corresponding configurations. Receiving a general query The IGMP querier periodically sends IGMP general queries to all hosts and routers (224.0.0.1) on the local subnet to determine whether active multicast group members exist on the subnet.
Page 27: Receiving A Leave Message
Receiving a leave message When an IGMPv1 host leaves a multicast group, the host does not send an IGMP leave message, so the switch cannot know immediately that the host has left the multicast group. However, as the host stops sending IGMP reports as soon as it leaves a multicast group, the switch deletes the forwarding entry for the dynamic member port corresponding to the host from the forwarding table when its aging timer expires.
Page 28: Protocols And Standards
Figure 13 Network diagram for IGMP snooping proxying As shown in Figure 13, Switch A works as an IGMP snooping proxy. As a host from the perspective of the querier Router A, Switch A represents its attached hosts to send membership reports and leave messages to Router A.
Page 29: Configuring Igmp Snooping Basic Functions
Configuring IGMP snooping basic functions In IGMP-snooping view, the configuration is effective for all VLANs. In VLAN view, the configuration is effective on only the ports that belong to the current VLAN. For a given VLAN, a configuration made in IGMP-snooping view is not effective if the same configuration is made in VLAN view.
Page 30: Configuring Igmp Forwarding Entries
To do... Use the command... Remarks Enter system view. system-view — Enter VLAN view. vlan vlan-id — Optional. Configure the version of IGMP igmp-snooping version snooping. version-number Version 2 by default. If you switch IGMP snooping from version 3 to version 2, the system will clear all IGMP snooping forwarding entries from dynamic joins, and will: •...
Page 31: Configuring Static Ports
If the router receives no IGMP reports for a multicast group on a dynamic member port, the router removes the port from the outgoing port list of the forwarding table entry for that multicast group when the aging timer of the port for that group expires. If multicast group memberships change frequently, you can set a relatively small value for the dynamic member port aging timer, and vice versa.
Page 32: Configuring Simulated Joining
To do... Use the command... Remarks Required. Configure the port or ports as igmp-snooping static-router-port static router port or ports. vlan vlan-id No static router ports by default. A static (S, G) joining can take effect only if a valid multicast source address is specified and IGMP snooping version 3 is currently running.
Page 33: Configuring Fast Leave Processing
Configuring fast leave processing The fast leave processing feature allows the router to process IGMP leave messages in a fast way. With the fast leave processing feature enabled, when receiving an IGMP leave message on a port, the router immediately removes that port from the outgoing port list of the forwarding table entry for the indicated group.
Page 34: Configuring Igmp Snooping Querier
To solve these problems, you can disable that router port from changing into a dynamic router port after receiving an IGMP general query or a PIM Hello message; thus, network security and control over multicast users are enhanced. This configuration does not affect the static router port configuration. To do...
Page 35: Configuring Igmp Queries And Responses
To do... Use the command... Remarks Required. Enable IGMP snooping igmp-snooping querier querier. Disabled by default. It is meaningless to configure an IGMP snooping querier in a multicast network running IGMP. Although an IGMP snooping querier does not take part in IGMP querier elections, it might affect IGMP querier elections because it sends IGMP general queries with a low source IP address.
Page 36: Configuring Source Ip Address Of Igmp Queries
To do... Use the command... Remarks Configure the maximum Optional. response time to IGMP igmp-snooping max-response-time interval 10 seconds by default. general queries. Optional Configure the IGMP last-member igmp-snooping query interval last-member-query-interval interval 1 second by default IMPORTANT: In the configuration, make sure that the IGMP general query interval is larger than the maximum response time for IGMP general queries.
Page 37: Configuring A Source Ip Address For The Igmp Messages Sent By The Proxy
To do... Use the command... Remarks Enter system view. system-view — Enter VLAN view. vlan vlan-id — Required. Enable IGMP snooping igmp-snooping proxying enable proxying in the VLAN. Disabled by default. Configuring a source IP address for the IGMP messages sent by the proxy You can set the source IP addresses in the IGMP reports and leave messages sent by the IGMP snooping proxy on behalf of its attached hosts.
Page 38: Configuring Multicast Source Port Filtering
Configuring a multicast group filter globally To do... Use the command... Remarks Enter system view. system-view — Enter IGMP-snooping view. igmp-snooping — Required. By default, no group filter is Configure a multicast group group-policy acl-number [ vlan globally configured. That is, hosts filter.
Page 39: Configuring The Function Of Dropping Unknown Multicast Data
To do... Use the command... Remarks interface interface-type interface-number Required. Enter Ethernet interface view or port group view. Use either approach. port-group manual port-group-name Required. Enable multicast source port igmp-snooping source-deny filtering. Disabled by default. Configuring the function of dropping unknown multicast data Unknown multicast data refers to multicast data for which no forwarding entries exist in the IGMP snooping forwarding table.
Page 40: Configuring Maximum Multicast Groups That Can Be Joined On A Port
Configuring maximum multicast groups that can be joined on a port By configuring the maximum number of multicast groups that a port can join, you can limit the number of multicast programs on-demand available to users, thus to regulate traffic on the port. To do...
Page 41: Configuring 802.1P Precedence For Igmp Messages
Configuring multicast group replacement on a port or a group of ports Be sure to configure the maximum number of multicast groups allowed on a port before enabling multicast group replacement. Otherwise, the multicast group replacement functionality will not take effect. To do...
Page 42: Displaying And Maintaining Igmp Snooping
To do… Use the command… Remarks Enter IGMP-snooping view. igmp-snooping — Enable the IGMP snooping Required. host tracking function host-tracking Disabled by default. globally. Enabling the IGMP snooping host tracking function in a VLAN To do… Use the command… Remarks Enter system view.
Page 43: Igmp Snooping Configuration Examples
14, Router A connects to the multicast source through Ethernet 1/2 and to Router • B through Ethernet 1/1. IGMPv2 is required on Router A, IGMPv2 snooping is required on Router B. Router B is an A6600 • router and Router A acts as the IGMP querier on the subnet.
Page 44 [RouterA-Ethernet1/2] pim dm [RouterA-Ethernet1/2] quit Configure Router B # Enable IGMP snooping globally. <RouterB> system-view [RouterB] igmp-snooping [RouterB-igmp-snooping] quit # Create VLAN 100, assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to this VLAN, and enable IGMP snooping and the function of dropping unknown multicast traffic in the VLAN. [RouterB] vlan 100 [RouterB-vlan100] port GigabitEthernet 1/0/1 to GigabitEthernet 1/0/4 [RouterB-vlan100] igmp-snooping enable...
Page 45: Static Port Configuration Example
IP group address:224.1.1.1 (0.0.0.0, 224.1.1.1): Attribute: Host Port Host port(s):total 2 port. GE1/0/3 (D) ( 00:03:23 ) GE1/0/4 (D) ( 00:04:10 ) MAC group(s): MAC group address:0100-5e01-0101 Host port(s):total 2 port. GE1/0/3 GE1/0/4 The output shows that GigabitEthernet 1/0/3 and GigabitEthernet 1/0/4 of Router B has joined multicast group 224.1.1.1.
Page 46 Figure 15 Network diagram for static port configuration Router C Source Router B Eth1/2 Eth1/1 1.1.1.2/24 10.1.1.1/24 GE1/0/1 Router A 1.1.1.1/24 IGMP querier Router D Host C Host A Receiver Receiver Host B VLAN 100 Procedure Configure IP addresses Configure an IP address and subnet mask for each interface as per Figure 15.
Page 47 # Configure GigabitEthernet 1/0/3 to be a static router port. [RouterB] interface GigabitEthernet 1/0/3 [RouterB-GigabitEthernet1/0/3] igmp-snooping static-router-port vlan 100 [RouterB-GigabitEthernet1/0/3] quit Configure Router C # Enable IGMP snooping globally. <RouterC> system-view [RouterC] igmp-snooping [RouterC-igmp-snooping] quit # Create VLAN 100, assign GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 to this VLAN, and enable IGMP snooping in the VLAN.
Page 48 Total 1 IP Source(s). Total 1 MAC Group(s). Router port(s):total 2 port. GE1/0/1 (D) ( 00:01:30 ) GE1/0/3 IP group(s):the following ip group(s) match to one mac group. IP group address:224.1.1.1 (0.0.0.0, 224.1.1.1): Attribute: Host Port Host port(s):total 1 port. GE1/0/2 (D) ( 00:03:23 ) MAC group(s):...
Page 49: Igmp Snooping Querier Configuration Example
IGMP snooping querier configuration example Network requirements • As shown in Figure 16, in a Layer 2–only network environment, two multicast sources Source 1 and Source 2 send multicast data to multicast groups 224.1.1.1 and 225.1.1.1 respectively, Host A and Host C are receivers of multicast group 224.1.1.1, and Host B and Host D are receivers of multicast group 225.1.1.1.
Page 50 # Enable the IGMP snooping querier function in VLAN 100 [RouterA-vlan100] igmp-snooping querier # Set the source IP address of IGMP general queries and group-specific queries to 192.168.1.1 in VLAN 100. [RouterA-vlan100] igmp-snooping general-query source-ip 192.168.1.1 [RouterA-vlan100] igmp-snooping special-query source-ip 192.168.1.1 [RouterA-vlan100] quit Configure Router B # Enable IGMP snooping globally.
Page 51: Igmp Snooping Proxying Configuration Example
IGMP snooping proxying configuration example Network requirements As shown in Figure 17, Router A connects to a multicast source through port Ethernet 1/2, and to Router B through port Ethernet 1/1. Router A runs IGMPv2 and Router B runs IGMPv2 snooping. Router A serves as an IGMP querier.
Page 52 [RouterB-igmp-snooping] quit # Create VLAN 100, assign ports GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to this VLAN, and enable IGMP snooping and IGMP snooping proxying in the VLAN. [RouterB] vlan 100 [RouterB-vlan100] port GigabitEthernet 1/0/1 to GigabitEthernet 1/0/4 [RouterB-vlan100] igmp-snooping enable [RouterB-vlan100] igmp-snooping proxying enable [RouterB-vlan100] quit Verify the configuration...
Page 53: Troubleshooting Igmp Snooping Configuration
224.1.1.1 0.0.0.0 00:00:06 00:02:04 When Host A leaves the multicast group, it sends an IGMP leave message to Router B. Receiving the message, Router B removes port GigabitEthernet 1/0/3 from the member port list of the forwarding entry for the group; however, it does not remove the group or forward the leave message to Router A because Host B is still in the group.
Page 54: Configured Multicast Group Policy Fails To Take Effect
Configured multicast group policy fails to take effect Symptom Although a multicast group policy has been configured to allow hosts to join specific multicast groups, the hosts can still receive multicast data addressed to other multicast groups. Analysis The ACL rule is incorrectly configured. •...
Page 55: Configuring Multicast Routing And Forwarding
Configuring multicast routing and forwarding The interfaces in this document refer to Layer 3 interfaces in generic sense and Ethernet interfaces that operate in route mode. For more information about the operating mode of the Ethernet interfaces, see Layer 2—LAN Switching Configuration Guide. Multicast routing and forwarding overview In multicast implementations, multicast routing and forwarding are implemented by routing and forwarding tables:...
Page 56 The router automatically chooses an optimal MBGP route by searching its MBGP routing table and • using the IP address of the packet source as the destination address. The outgoing interface in the corresponding routing entry is the RPF interface, and the next hop is the RPF neighbor. The router automatically chooses an optimal multicast static route by searching its multicast static •...
Page 57: Multicast Static Routes
the RPF interface, the router forwards the packet to all the outgoing interfaces. Otherwise it discards the packet. Assume that unicast routes are available in the network, MBGP is not configured, and no multicast static routes have been configured on Router C, as shown in Figure 18.
Page 58 Figure 19 Changing an RPF route As shown in Figure 19, when no multicast static 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;...
Page 59: Application Of Gre Tunnel In Multicast Forwarding
static route on Router C and Router D, specifying Router B as the RPF neighbor of Router C and specifying Router C as the RPF neighbor of Router D, the receivers can receive multicast data that the multicast source sent. A multicast static route only affects RPF check;...
Page 60: Enabling Ip Multicast Routing
First-hop router—The router that directly connects to the multicast source is called the “first-hop • router”. Querier—The router that sends multicast traceroute requests is called the “querier”. • Introduction to multicast traceroute packets A multicast traceroute packet is a special IGMP packet, which differs from common IGMP packets in that its IGMP Type field is set to 0x1F or 0x1E and its destination IP address is a unicast address.
Page 61: Configuring Multicast Routing And Forwarding
To do… Use the command… Remarks Required. Configure a route distinguisher (RD) for the route-distinguisher route-distinguisher No RD is configured by VPN instance. default. Required. Enable IP multicast routing. multicast routing-enable Disabled by default. For more information about the ip vpn-instance and route-distinguisher commands, see MPLS Command Reference.
Page 62: Configuring A Multicast Forwarding Range
By configuring per-source or per-source-and-group load splitting, you can optimize the traffic delivery when multiple data flows are handled. Configuring a multicast routing policy for the public network network To do... Use the command... Remarks Enter system view. system-view — Required.
Page 63: Configuring The Multicast Forwarding Table Size
Configuring the multicast forwarding table size The router maintains the corresponding forwarding entry for each multicast packet that it receives. Excessive multicast routing entries, however, can exhaust the router’s memory and cause lower router performance. You can set a limit on the number of entries in the multicast forwarding table based on the networking situation and the performance requirements.
Page 64: Configuring Static Multicast Mac Address Entries
Configuring static multicast MAC address entries In Layer-2 multicast, a Layer 2 multicast protocol (such as IGMP snooping) can dynamically add multicast MAC address entries. Or, you can manually configure multicast MAC address entries. Configuring a static multicast MAC address entry in system view To do...
Page 65: Displaying And Maintaining Multicast Routing And Forwarding
Displaying and maintaining multicast routing and forwarding To do... Use the command... Remarks display multicast [ all-instance | vpn-instance Display multicast boundary vpn-instance-name ] boundary [ group-address [ mask | Available in information. mask-length ] ] [ interface interface-type interface-number ] any view.
Page 66: Configuration Examples
To do... Use the command... Remarks display multicast [ all-instance | vpn-instance Display RPF route information of vpn-instance-name ] rpf-info source-address Available in the specified multicast source. [ group-address ] [ | { begin | exclude | include } any view. regular-expression ] display multicast [ all-instance | vpn-instance Display minimum TTL required...
Page 67 Network diagram Figure 22 Network diagram for RPF route alteration configuration Procedure Configure IP addresses and unicast routing Configure the IP address and subnet mask for each interface as per Figure 22. The detailed configuration steps are omitted here. Enable OSPF on the routers in the PIM-DM domain. Ensure the network-layer interoperation among the routers in the PIM-DM domain.
Page 68: Creating An Rpf Route
[RouterA] multicast routing-enable [RouterA] interface GigabitEthernet 1/0/1 [RouterA-GigabitEthernet1/0/1] pim dm [RouterA-GigabitEthernet1/0/1] quit [RouterA] interface GigabitEthernet 1/0/2 [RouterA-GigabitEthernet1/0/2] pim dm [RouterA-GigabitEthernet1/0/2] quit [RouterA] interface GigabitEthernet 1/0/3 [RouterA-GigabitEthernet1/0/3] pim dm [RouterA-GigabitEthernet1/0/3] quit The configuration on Router C is similar to the configuration on Router A. The detailed configuration steps are omitted here.
Page 69 Network diagram Figure 23 Network diagram for creating an RPF route PIM-DM OSPF domain Router A Router B Router C GE1/0/2 GE1/0/3 GE1/0/2 30.1.1.2/24 30.1.1.1/24 20.1.1.1/24 GE1/0/2 20.1.1.2/24 GE1/0/1 GE1/0/1 GE1/0/1 50.1.1.1/24 40.1.1.1/24 10.1.1.1/24 Source 2 Source 1 Receiver 50.1.1.100/24 40.1.1.100/24 10.1.1.100/24 Multicast static route...
Page 70: Multicast Forwarding Over A Gre Tunnel
The configuration on Router B is similar to that on Router A. The specific configuration steps are omitted here. # Use display multicast rpf-info to view the information of the RPF route to Source 2 on Router B and Router C. [RouterB] display multicast rpf-info 50.1.1.100 [RouterC] display multicast rpf-info 50.1.1.100 No information is displayed.
Page 71 Network diagram Figure 24 Network diagram for configuring multicast forwarding over a GRE tunnel Multicast router Unicast router Multicast router Router A Router B Router C GE1/0/2 GE1/0/1 GE1/0/2 GE1/0/2 20.1.1.1/24 20.1.1.2/24 30.1.1.1/24 30.1.1.2/24 GE1/0/1 GE1/0/1 GRE tunnel 10.1.1.1/24 40.1.1.1/24 Tunnel0 Tunnel0 50.1.1.1/24...
Page 72 [RouterA-ospf-1-area-0.0.0.0] network 20.1.1.0 0.0.0.255 [RouterA-ospf-1-area-0.0.0.0] network 50.1.1.0 0.0.0.255 [RouterA-ospf-1-area-0.0.0.0] quit [RouterA-ospf-1] quit # Configure OSPF on Router B. <RouterB> 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...
Page 73 Configure a static multicast route # On Router C, configure a static multicast route and specify its RPF neighbor leading toward Source is Tunnel 0 on Router A. [RouterC] ip rpf-route-static 10.1.1.0 24 50.1.1.1 Verify the configuration Source sends multicast data to the multicast group 225.1.1.1 and Receiver can receive the multicast data after joining the multicast group.
Page 74: Troubleshooting Multicast Routing And Forwarding
Troubleshooting multicast routing and forwarding Multicast static route failure Symptom No dynamic routing protocol is enabled on the routers, and the physical status and link layer status of interfaces are both up, but the multicast static route fails. Analysis If the multicast static route is not configured or updated correctly to match the current network •...
Page 75: Configuring Igmp
Configuring IGMP The interfaces in this document refer to Layer 3 interfaces in generic sense and Ethernet interfaces operating in route mode. For more information about the operating mode of the Ethernet interface, see Layer 2—LAN Switching Configuration Guide. IGMP overview As a TCP/IP protocol responsible for IP multicast group member management, the Internet Group Management Protocol (IGMP) is used by IP hosts and adjacent multicast routers to establish and maintain their multicast group memberships.
Page 76 Figure 25 IGMP queries and reports IP network Router A Router B Ethernet Host A Host B Host C (G2) (G1) (G1) Query Report Assume that Host B and Host C will receive multicast data addressed to multicast group G1, and Host A will receive multicast data addressed to G2, as shown in Figure 25.
Page 77: Enhancements In Igmpv2
Enhancements in IGMPv2 Compared with IGMPv1, IGMPv2 has introduced a querier election mechanism and a leave-group mechanism. Querier election mechanism In IGMPv1, the DR elected by the Layer 3 multicast routing protocol (such as PIM) serves as the querier among multiple routers on the same subnet. IGMPv2 introduced an independent querier election mechanism.
Page 78 If it needs 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 needs to reject multicast data from specific sources like S1, S2, …, it sends a report with the •...
Page 79: Igmp Ssm Mapping
IS_EX—The source filtering mode is Exclude. Namely, 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. •...
Page 80: Igmp Proxying
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: If G is not in the SSM group range, Router A cannot provide the SSM service but can provide the •...
Page 81: Multi-Instance Igmp
A router 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. Such an entry is a collection of members in the same multicast group on each downstream interface.
Page 82: Enabling Igmp
Enabling IGMP To configure IGMP, enable IGMP on the interface on which the multicast group memberships will be established and maintained. Enabling IGMP for the public network To do... Use the command... Remarks Enter system view. system-view — Required. Enable IP multicast routing. multicast routing-enable Disabled by default.
Page 83: Configuring Static Joining
Configuring an IGMP version globally To do... Use the command... Remarks Enter system view. system-view — Enter public network IGMP view or igmp [ vpn-instance — VPN instance IGMP view. vpn-instance-name ] Optional. Configure an IGMP version version version-number globally. IGMPv2 by default.
Page 84: Configuring A Multicast Group Filter
Configuring a multicast group filter To restrict the hosts on the network attached to an interface from joining certain multicast groups, you can set an ACL rule on the interface as a packet filter so that the interface maintains only the multicast groups the match the criteria.
Page 85: Configuring Igmp Message Options
Determine the startup query interval • Determine the startup query count • Determine the IGMP general query interval • Determine the IGMP querier’s robustness variable • Determine the maximum response time for IGMP general queries • Determine the IGMP last-member query interval •...
Page 86: Configuring Igmp Query And Response Parameters
To do... Use the command... Remarks Configure the interface to Optional. discard any IGMP message igmp require-router-alert By default, the router does not that does not carry the check the Router-Alert option. Router-Alert option. Optional. Enable insertion of the Router-Alert option into IGMP igmp send-router-alert By default, IGMP messages carry messages.
Page 87 Configuring IGMP query and response parameters globally To do... Use the command... Remarks Enter system view. system-view — Enter public network IGMP igmp [ vpn-instance view or VPN instance IGMP — vpn-instance-name ] view. Optional. Configure the IGMP querier’s robust-count robust-value robustness variable.
Page 88: Configuring Igmp Fast Leave Processing
To do... Use the command... Remarks Optional Configure the startup query igmp startup-query-interval By default, the startup query interval interval interval is 1/4 of the “IGMP general query interval”. Optional. Configure the startup query By default, the startup query count igmp startup-query-count value count.
Page 89: Enabling The Igmp Host Tracking Function
Configuring IGMP fast leave processing on an interface To do... Use the command... Remarks Enter system view. system-view — interface interface-type Enter interface view. — interface-number Required. Configure IGMP fast leave igmp fast-leave [ group-policy processing, acl-number ] Disabled by default. Enabling the IGMP host tracking function With the IGMP host tracking function, the switch can record the information of the member hosts that are receiving multicast traffic, including the host IP address, running duration, and timeout time.
Page 90: Enabling Ssm Mapping
Enabling SSM mapping To do… Use the command… Remarks Enter system view. system-view — interface interface-type Enter interface view. — interface-number Required. Enable the IGMP SSM igmp ssm-mapping enable mapping feature. Disabled by default. To ensure SSM service for all hosts on a subnet, regardless of the IGMP version running on the hosts, enable IGMPv3 on the interface that forwards multicast traffic onto the subnet.
Page 91: Configuring Multicast Forwarding On A Downstream Interface
Each router can have only one interface serving as the proxy interface. In scenarios with multiple instances, configure IGMP proxying 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.
Page 92: Displaying And Maintaining Igmp Displaying And Maintaining Igmp
Displaying and maintaining IGMP Displaying and maintaining IGMP To do... Use the command... Remarks display igmp [ all-instance | vpn-instance vpn-instance-name ] group [ group-address | Available in any interface interface-type interface-number ] [ static Display IGMP group information. view. | verbose ] [ | { begin | exclude | include } regular-expression ] Display the Layer 2 port...
Page 93: Igmp Configuration Examples
To do... Use the command... Remarks display igmp [ all-instance | vpn-instance Display the multicast group vpn-instance-name ] ssm-mapping group information created from IGMPv1 Available in any [ group-address | interface interface-type and IGMPv2 reports based on the view. interface-number ] [ verbose ] [ | { begin | exclude configured IGMP SSM mappings.
Page 94 The hosts in N1 can join only multicast group 224.1.1.1, and the hosts in N2 can join any multicast • groups. Network diagram Figure 29 Network diagram for basic IGMP functions configuration Procedure Configure IP addresses and unicast routing Configure the IP address and subnet mask of each interface as per Figure 29.
Page 95 [RouterB] multicast routing-enable [RouterB] interface GigabitEthernet 1/0/1 [RouterB-GigabitEthernet1/0/1] igmp enable [RouterB-GigabitEthernet1/0/1] pim dm [RouterB-GigabitEthernet1/0/1] quit [RouterB] interface GigabitEthernet 0/0/0 [RouterB-GigabitEthernet0/0/0] pim dm [RouterB-GigabitEthernet0/0/0] quit # Enable IP multicast routing on Router C, enable PIM-DM on each interface, and enable IGMP on GigabitEthernet 1/0/1.
Page 96: Ssm Mapping Configuration Example
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 1/0/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 1/0/1. The Receiver host runs IGMPv2, and does not •...
Page 97 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 1/0/1. <RouterD>...
Page 98 The configuration on Router A, Router B and Router C is similar to that on Router D. Configure IGMP SSM mappings # Configure IGMP SSM mappings on Router D. [RouterD] igmp [RouterD-igmp] ssm-mapping 232.1.1.0 24 133.133.1.1 [RouterD-igmp] ssm-mapping 232.1.1.0 24 133.133.3.1 [RouterD-igmp] quit Verify the configuration Use display igmp ssm-mapping to view the IGMP SSM mappings on the router.
Page 99: Igmp Proxying Configuration Example
UpTime: 00:13:25 Upstream interface: GigabitEthernet1/0/2 Upstream neighbor: 192.168.3.1 RPF prime neighbor: 192.168.3.1 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet1/0/1 Protocol: igmp, UpTime: 00:13:25, Expires: - IGMP proxying configuration example Network requirements PIM-DM is required to run on the core network. Host A and Host C in the stub network receive VOD •...
Page 100: Troubleshooting Igmp
[RouterA-GigabitEthernet1/0/1] pim dm [RouterA-GigabitEthernet1/0/1] quit # Enable IP multicast routing on Router B, IGMP proxying on GigabitEthernet 1/0/1, and IGMP on GigabitEthernet 1/0/2. <RouterB> system-view [RouterB] multicast routing-enable [RouterB] interface GigabitEthernet 1/0/1 [RouterB-GigabitEthernet1/0/1] igmp proxying enable [RouterB-GigabitEthernet1/0/1] quit [RouterB] interface GigabitEthernet 1/0/2 [RouterB-GigabitEthernet1/0/2] igmp enable [RouterB-GigabitEthernet1/0/2] quit Verify the configuration...
Page 101: Inconsistent Memberships On Routers On The Same Subnet
Analysis The correctness of networking and interface connections and whether the protocol layer of the • interface is up directly affect the generation of group membership information. Multicast routing must be enabled on the router, and IGMP must be enabled on the interface •...
Page 102: Configuring Pim
Configuring PIM PIM provides IP multicast forwarding by leveraging 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 router, multicast routing can be implemented as long as the corresponding multicast routing entries are created through unicast routes.
Page 103: Neighbor Discovery
Neighbor discovery In a PIM domain, a PIM router discovers PIM neighbors, maintains PIM neighboring relationships with other routers, and builds and maintains SPTs by periodically multicasting hello messages to all other PIM routers (224.0.0.13) on the local subnet. Every PIM-enabled interface on a router sends hello messages periodically and learns the PIM neighboring information pertinent to the interface.
Page 104: Graft
Figure 32 SPT building The flood-and-prune process takes place periodically. A pruned state timeout mechanism is provided. A pruned branch restarts multicast forwarding when the pruned state times out and then is pruned again when it no longer has any multicast receiver. Pruning has a similar implementation in PIM-SM.
Page 105: Assert
Assert The assert mechanism shuts off duplicate multicast flows onto the same multi-access network, where more than one multicast router exists, by electing a unique multicast forwarder on the multi-access network. Figure 33 Assert mechanism As shown in Figure 33, after Router A and Router B receive an (S, G) packet from the upstream node, they both forward the packet to the local subnet.
Page 106: Neighbor Discovery
When a receiver is interested in the multicast data addressed to a specific multicast group, the router • connected to this receiver sends a join message to the RP that corresponds to that multicast group. The path along which the message goes hop by hop to the RP forms a branch of the RPT. When a multicast source sends multicast streams to a multicast group, the source-side designated •...
Page 107: Rp Discovery
Figure 34 DR election Receiver Source Receiver Hello message Register message Join message As shown in Figure 34, the DR election process is as follows: Routers on the multi-access network send hello messages to one another. The hello messages contain the router priority for DR election.
Page 108 Figure 35 BSR and C-RPs Based on the information in the RP-sets, all routers in the network can calculate the location of the corresponding RPs based on the following rules: The C-RP with the highest priority wins. If all the C-RPs have the same priority, their hash values are calculated through the hashing algorithm.
Page 109: Rpt Building
RPT building Figure 36 RPT building in a PIM-SM domain As shown in Figure 36, the process of building an RPT is as follows: When a receiver joins multicast group G, it uses an IGMP message to inform the directly connected After getting the receiver information, the DR sends a join message, which is forwarded hop by hop to the RP that corresponds to the multicast group.
Page 110: Multicast Source Registration
Multicast source registration The purpose of multicast source registration will inform the RP about the existence of the multicast source. Figure 37 Multicast source registration Host A Source Receiver Host B Server Receiver Join message Register message Host C Multicast packets As shown in Figure 37, the multicast source registers with the RP as follows:...
Page 111: Assert
Multicast packets are delivered along a path that might not be the shortest one. • An increase in multicast traffic adds a great burden on the RP, increasing the risk of failure. • To solve the issues, PIM-SM allows an RP or the DR at the receiver side to initiate the following SPT switchover process: The RP initiates an SPT switchover process.
Page 112: Neighbor Discovery
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 RPA.
Page 113: Bidirectional Rpt Building
In the case of a tie, the router with the route with the lowest metric wins the DF election. 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.
Page 114: Administrative Scoping
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: When a multicast source sends multicast packets to multicast group G, the DF in each network segment unconditionally forwards the packets to the RP.
Page 115 ranges that different admin-scope zones serve can be overlapped. A multicast group is valid only within its local admin-scope zone, and functions as a private group address. The global scope zone maintains a BSR, which serves the multicast groups that do not belong to any admin-scope zone.
Page 116: Understanding Pim-Ssm
Figure 42 Relationship between admin-scope zones and the global scope zone in group address ranges Figure 42, the group address ranges of admin-scope 1 and 2 have no intersection, whereas the group address range of admin-scope 3 is a subset of the address range of admin-scope 1. The group address range of the global scope zone covers all the group addresses other than those of all the admin-scope zones.
Page 117: Construction Of Spt
Construction of SPT Whether to build an RPT for PIM-SM or an SPT for PIM-SSM depends on whether the multicast group the receiver will join falls in the SSM group range (SSM group range reserved by IANA is 232.0.0.0/8). Figure 43 SPT building in PIM-SSM As shown in Figure 43, Host B and Host C are multicast information receivers.
Page 118: Multi-Instance Pim
Figure 44 Relationships among PIM protocols A receiver joins multicast group G The receiver specifies a G is in the SSM group range multicast source? An IGMP SSM mapping is BIDIR-PIM is used? configured for G? G has corresponding Use PIM-SM for G Use PIM-SSM for G BIDIR-PIM RP? Use BIDIR-PIM for G...
Page 119: Enabling Pim-Dm
Configure any unicast routing protocol so that all devices in the domain are interoperable at the • network layer Determine the interval between state-refresh messages • Determine the minimum time to wait before receiving a new refresh message • Determine the TTL value of state-refresh messages •...
Page 120: Enabling State-Refresh Capability
For more information about ip vpn-instance, route-distinguisher, and ip binding vpn-instance, see MPLS Command Reference. For more information about multicast routing-enable, see IP Multicast Command Reference. Enabling state-refresh capability Pruned interfaces resume multicast forwarding when the pruned state times out. To prevent this, the router with the multicast source attached periodically sends an (S, G) state-refresh message, which is forwarded hop by hop along the initial multicast flooding path of the PIM-DM domain, to refresh the prune timer state of all the routers on the path.
Page 121: Configuring Pim-Dm Graft Retry Period
Configuring PIM-DM graft retry period In PIM-DM, graft is the only type of message that uses the acknowledgment mechanism. In a PIM-DM domain, if a router does not receive a graft-ack message from the upstream router within the specified time after it sends a graft message, the router keeps sending new graft messages at a configurable interval—namely graft retry period, until it receives a graft-ack message from the upstream router.
Page 122: Enabling Pim-Sm
Enabling PIM-SM With PIM-SM enabled, a router sends hello messages periodically to discover PIM neighbors and processes messages from the PIM neighbors. To deploy a PIM-SM domain, enable PIM-SM on all non-border interfaces of the routers. Enabling PIM-SM globally on the public network To do...
Page 123 Then, the other routers in the network calculate the mappings between specific group ranges and the corresponding RPs based on the RP-set. HP recommends you to configure C-RPs on backbone routers. To guard against C-RP spoofing, configure a legal C-RP address range and the range of multicast groups to be served on the BSR.
Page 124: Configuring A Bsr
To do... Use the command... Remarks Enter system view. system-view — Enter public network PIM view pim [ vpn-instance — or VPN instance PIM view. vpn-instance-name ] Required. Enable auto-RP. auto-rp enable Disabled by default. Configuring C-RP timers globally To enable the BSR to distribute the RP-set information within the PIM-SM domain, C-RPs must periodically send C-RP-Adv messages to the BSR.
Page 125 address to replace its own BSR address and no longer assumes itself to be the BSR, and the winner retains its own BSR address and continues assuming itself to be the BSR. Configuring a legal range of BSR addresses enables filtering of bootstrap messages based on the address range, thus to prevent a maliciously configured host from masquerading as a BSR.
Page 126 To do… Use the command… Remarks Enter system view. system-view — interface interface-type Enter interface view. — interface-number Required. Configure a PIM domain pim bsr-boundary By default, no PIM domain border border. is configured. Configuring global C-BSR parameters In each PIM-SM domain, a unique BSR is elected from C-BSRs. The C-RPs in the PIM-SM domain send advertisement messages to the BSR.
Page 127 To do… Use the command… Remarks Optional Configure the BS timeout. c-bsr holdtime interval For the default value, see below. BS period and timeout settings Make sure that the BS period value is smaller than the BS timeout value. The BS period defaults to the value determined by the formula: “BS period = (BS timeout –...
Page 128: Configuring Administrative Scoping
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-scope zones. Each admin-scope zone maintains a BSR, which serves a specific multicast group range.
Page 129: Configuring Multicast Source Registration
To do… Use the command… Remarks Enter public network PIM view pim [ vpn-instance — or VPN instance PIM view. vpn-instance-name ] Required. c-bsr group group-address { mask Configure a C-BSR for an | mask-length } [ hash-length No C-BSRs are configured for an admin-scope zone.
Page 130: Disabling Spt Switchover
DR sends a null register message (a register message without encapsulated multicast data) to the RP. If the DR receives a register-stop message during the register probe time, it will reset its register-stop timer. Otherwise, the DR starts sending register messages with encapsulated data again when the register-stop timer expires.
Page 131: Enabling Pim-Sm
Determine the IP address of a static RP and the ACL that defines the range of the multicast groups to • be served by the static RP Determine the C-RP priority and the ACL that defines the range of multicast groups to be served by •...
Page 132: Enabling Bidir-Pim
To do... Use the command... Remarks Required. Bind the interface with the ip binding vpn-instance By default, an interface belongs to VPN instance. vpn-instance-name the public network, and is not bound with any VPN instance. Required. Enable PIM-SM. pim sm Disabled by default.
Page 133 Then, the other routers in the network calculate the mappings between specific group ranges and the corresponding RPs based on the RP-set. HP recommends that you configure C-RPs on backbone routers. To guard against C-RP spoofing, configure a legal C-RP address range and the range of multicast groups to be served on the BSR.
Page 134: Configuring A Bsr
C-RP-Adv message from the C-RP within the timeout interval, the BSR assumes the C-RP to have expired or become unreachable. The C-RP timers need to be configured on C-RP routers. To do... Use the command... Remarks Enter system view. system-view —...
Page 135 The preventive measures can partially protect the security of BSRs in a network. If a legal BSR is controlled by an attacker, the preceding problem will still occur. To do… Use the command… Remarks Enter system view. system-view — Enter public network PIM view pim [ vpn-instance —...
Page 136 To do… Use the command… Remarks Optional. Configure the hash mask c-bsr hash-length hash-length length. 30 by default. Optional. Configure the C-BSR priority. c-bsr priority priority 64 by default. Hash mask length and C-BSR priority You can configure these parameters at three levels: •...
Page 137: Configuring Administrative Scoping
Disabling BSM semantic fragmentation Generally, a BSR periodically distributes the RP-set information in bootstrap messages within the BIDIR-PIM domain. It encapsulates a BSM in an IP datagram and might split the datagram into fragments if the message exceeds the MTU. In respect of such IP fragmentation, loss of a single IP fragment leads to unavailability of the entire message.
Page 138 To do… Use the command… Remarks Required. Enable administrative c-bsr admin-scope scoping. Disabled by default. Configuring an admin-scope zone boundary The boundary of each admin-scope zone is formed by ZBRs. Each admin-scope zone maintains a BSR, which serves a specific multicast group range. Multicast protocol packets (such as assert messages and bootstrap messages) that belong to this range cannot cross the admin-scope zone boundary.
Page 139: Configuring Pim-Ssm
To do… Use the command… Remarks Enter public network PIM view pim [ vpn-instance — or VPN instance PIM view. vpn-instance-name ] Required. Configure a C-BSR for the c-bsr global [ hash-length No C-BSRs are configured for the global-scope zone. hash-length | priority priority ] * global-scope zone by default.
Page 140: Configuring The Ssm Group Range
Enabling PIM-SM in a VPN instance All the interfaces in the same VPN instance on the same device must work in the same PIM mode. To do... Use the command... Description Enter system view. system-view — Create a VPN instance and ip vpn-instance vpn-instance-name —...
Page 141: Configuring Pim Common Features
Configuring PIM common features For the functions or parameters that can be configured in both PIM view and interface view described in this section: In PIM view, the configuration is effective on all interfaces. In interface view, the configuration is effective on only the current interface.
Page 142: Configuring A Hello Message Filter
To do... Use the command... Remarks Required. Configure a multicast group source-policy acl-number filter. No multicast data filter by default. A smaller distance from the filter to the multicast source results in a more remarkable filtering effect. This filter works not only on independent multicast data but also on multicast data encapsulated in register messages.
Page 143 A hello message sent from a PIM router contains a generation ID option. The generation ID is a random value for the interface on which the hello message is sent. Normally, the generation ID of a PIM router does not change unless the status of the router changes (for example, when PIM is just enabled on the interface or the router is restarted).
Page 144: Configuring The Prune Delay
To do... Use the command... Remarks Required. Configure the interface to reject hello messages without pim require-genid By default, hello messages without a generation ID. Generation_ID are accepted. Configuring the prune delay If a downstream router does not support the prune override interval field, you can configure a prune delay interval on the upstream router so that it will not perform the prune action immediately after it receives the prune message.
Page 145: Configuring Join/Prune Message Sizes
To do... Use the command... Remarks Optional. Configure the join/prune timer join-prune interval interval. 60 seconds by default. Optional. Configure the join/prune holdtime join-prune interval timeout time. 210 seconds by default. Optional. Configure assert timeout time. holdtime assert interval 180 seconds by default. Optional.
Page 146: Displaying And Maintaining Pim
To do... Use the command... Remarks Configure the maximum Optional. number of (S, G) entries in a jp-queue-size queue-size 1,020 by default. join/prune message. Displaying and maintaining PIM To do... Use the command... Remarks Display the BSR information in display pim [ all-instance | vpn-instance the PIM-SM domain and locally Available in vpn-instance-name ] bsr-info [ | { begin | exclude |...
Page 147: Pim Configuration Examples
To do... Use the command... Remarks display pim [ all-instance | vpn-instance vpn-instance-name ] routing-table [ group-address [ mask { mask-length | mask } ] | source-address [ mask { mask-length | mask } ] | incoming-interface Display the content of the PIM Available in [ interface-type interface-number | register ] | routing table.
Page 148 Figure 45 Network diagram for PIM-DM configuration Device Interface IP address Device Interface IP address Router A GE0/0/0 10.110.1.1/24 Router D GE0/0/0 10.110.5.1/24 GE0/0/3 192.168.1.1/24 GE0/0/3 192.168.1.2/24 Router B GE0/0/0 10.110.2.1/24 GE0/0/1 192.168.2.2/24 GE0/0/1 192.168.2.1/24 GE0/0/2 192.168.3.2/24 Router C GE0/0/0 10.110.2.2/24 GE0/0/1 192.168.3.1/24...
Page 149 [RouterA-GigabitEthernet0/0/3] pim dm [RouterA-GigabitEthernet0/0/3] quit The configuration on Router B and Router C is similar to that on Router A. # Enable IP multicast routing on Router D, and enable PIM-DM on each interface. <RouterD> system-view [RouterD] multicast routing-enable [RouterD] interface GigabitEthernet 0/0/0 [RouterD-GigabitEthernet0/0/0] pim dm [RouterD-GigabitEthernet0/0/0] quit [RouterD] interface GigabitEthernet 0/0/3...
Page 150 # View the PIM routing table information on Router A. [RouterA] 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...
Page 151: Pim-Sm Non-Scoped Zone Configuration Example
PIM-SM non-scoped zone configuration example Network requirements As shown in Figure 46, receivers receive VOD information through multicast. The receiver groups of • different organizations form stub networks, and one or more receiver hosts exist in each stub network. The entire PIM-SM domain contains only one BSR. Host A and Host C are multicast receivers in two stub networks N1 and N2.
Page 152 Router C GE0/0/0 10.110.2.2/24 GE0/0/4 192.168.9.2/24 GE0/0/1 192.168.3.1/24 GE0/0/5 192.168.4.1/24 Procedure Configure IP addresses and unicast routing Configure the IP address and subnet mask for each interface as per Figure 46. Detailed configuration steps are omitted here. Configure OSPF on the routers in the PIM-SM domain to ensure network-layer reachability among them. Detailed configuration steps are omitted here.
Page 153 [RouterE-pim] c-bsr GigabitEthernet 0/0/4 32 20 [RouterE-pim] c-rp GigabitEthernet 0/0/4 group-policy 2005 [RouterE-pim] quit Verify the configuration Carry out display pim interface to view the PIM configuration and running status on each interface. For example: # Verify the PIM configuration information on Router A. [RouterA] display pim interface VPN-Instance: public net Interface...
Page 154 # View the BSR information and the locally configured C-RP information in effect on Router E. [RouterE] display pim bsr-info VPN-Instance: public net Elected BSR Address: 192.168.9.2 Priority: 20 Hash mask length: 32 State: Elected Scope: Not scoped Uptime: 00:01:18 Next BSR message scheduled at: 00:01:52 Candidate BSR Address: 192.168.9.2 Priority: 20...
Page 155 Total 1 (*, G) entry; 1 (S, G) entry (*, 225.1.1.0) RP: 192.168.9.2 Protocol: pim-sm, Flag: WC UpTime: 00:13:46 Upstream interface: GE0/0/1 Upstream neighbor: 192.168.9.2 RPF prime neighbor: 192.168.9.2 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet0/0/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...
Page 156: Pim-Sm Admin-Scope Zone Configuration Example
(*, 225.1.1.0) RP: 192.168.9.2 (local) Protocol: pim-sm, Flag: WC UpTime: 00:13:16 Upstream interface: Register Upstream neighbor: 192.168.4.2 RPF prime neighbor: 192.168.4.2 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet0/0/4 Protocol: pim-sm, UpTime: 00:13:16, Expires: 00:03:22 PIM-SM admin-scope zone configuration example Network requirements As shown in Figure...
Page 157 Figure 47 Network diagram for PIM-SM admin-scope zone configuration Device Interface IP address Device Interface IP address Router A GE0/0/0 192.168.1.1/24 Router D GE0/0/1 10.110.4.2/24 GE0/0/1 10.110.1.1/24 GE0/0/3 10.110.7.1/24 Router B GE0/0/0 192.168.2.1/24 GE0/0/2 10.110.8.1/24 GE0/0/1 10.110.1.2/24 Router E GE0/0/0 192.168.4.1/24 GE0/0/2 10.110.2.1/24...
Page 158 Configure the IP address and subnet mask for each interface as per Figure 47. The detailed configuration steps are omitted here. Configure OSPF on the routers in the PIM-SM domain to ensure network-layer reachability among them. Detailed configuration steps are omitted here. Enable IP multicast routing and administrative scoping, and enable PIM-SM and IGMP # Enable IP multicast routing and administrative scoping on Router A, enable PIM-SM on each interface, and enable IGMP on the host-side interface GigabitEthernet 0/0/0.
Page 159 [RouterB-GigabitEthernet0/0/2] quit [RouterB] interface GigabitEthernet 0/0/4 [RouterB-GigabitEthernet0/0/4] multicast boundary 239.0.0.0 8 [RouterB-GigabitEthernet0/0/4] quit # On Router C, configure GigabitEthernet 0/0/2 and GigabitEthernet 0/0/4 as the boundary of admin-scope zone 2. <RouterC> system-view [RouterC] interface GigabitEthernet 0/0/2 [RouterC-GigabitEthernet0/0/2] multicast boundary 239.0.0.0 8 [RouterC-GigabitEthernet0/0/2] quit [RouterC] interface GigabitEthernet 0/0/4 [RouterC-GigabitEthernet0/0/4] multicast boundary 239.0.0.0 8...
Page 160 Verify the configuration To view the BSR election information and the C-RP information on a router, use display pim bsr-info. For example: # View the BSR information and the locally configured C-RP information on Router B. [RouterB] display pim bsr-info VPN-Instance: public net Elected BSR Address: 10.110.9.1 Priority: 64...
Page 161 Next BSR message scheduled at: 00:01:12 Candidate BSR Address: 10.110.4.2 Priority: 64 Hash mask length: 30 State: Elected Scope: 239.0.0.0/8 Candidate RP: 10.110.4.2(GigabitEthernet0/0/1) Priority: 192 HoldTime: 150 Advertisement Interval: 60 Next advertisement scheduled at: 00:00:10 # View the BSR information and the locally configured C-RP information on Router F. [RouterF] display pim bsr-info VPN-Instance: public net Elected BSR Address: 10.110.9.1...
Page 162: Bidir-Pim Configuration Example
Priority: 192 HoldTime: 150 Uptime: 00:07:44 Expires: 00:01:51 # View the RP information on Router D. [RouterD] display pim rp-info VPN-Instance: public net PIM-SM BSR RP information: Group/MaskLen: 224.0.0.0/4 RP: 10.110.9.1 Priority: 192 HoldTime: 150 Uptime: 00:03:42 Expires: 00:01:48 Group/MaskLen: 239.0.0.0/8 RP: 10.110.4.2 (local) Priority: 192 HoldTime: 150...
Page 163 Figure 48 Network diagram for BIDIR-PIM configuration Device Interface IP address Device Interface IP address Router A GE1/0/1 192.168.1.1/24 Router D GE1/0/1 192.168.3.1/24 S2/0/1 10.110.1.1/24 GE1/0/2 192.168.4.1/24 Router B GE1/0/1 192.168.2.1/24 S2/0/1 10.110.3.2/24 S2/0/1 10.110.1.2/24 Source 1 192.168.1.100/24 S2/0/2 10.110.2.1/24 Source 2 192.168.4.100/24 Router C...
Page 164 [RouterA-pim] quit # On Router B, enable IP multicast routing, enable PIM-SM on each interface, enable IGMP on interface GigabitEthernet 1/0/1, and enable BIDIR-PIM. <RouterB> system-view [RouterB] multicast routing-enable [RouterB] interface GigabitEthernet 1/0/1 [RouterB- GigabitEthernet1/0/1] igmp enable [RouterB- GigabitEthernet1/0/1] pim sm [RouterB- GigabitEthernet1/0/1] quit [RouterB] interface serial 2/0/1 [RouterB-Serial2/0/1] pim sm...
Page 165 [RouterD-pim] bidir-pim enable [RouterD-pim] quit Configure C-BSR and C-RP # On Router C, configure Serial 2/0/1 as a C-BSR, and loopback interface 0 as a C-RP for the entire BIDIR-PIM domain. [RouterC-pim] c-bsr serial 2/0/1 [RouterC-pim] c-rp loopback 0 bidir [RouterC-pim] quit Verify the configuration To view the DF information of BIDIR-PIM on a router, use display pim df-info.
Page 166 To view the DF information of the multicast forwarding table on a router, use display multicast forwarding-table df-info. For more information about this command, see IP Multicast Command Reference. # View the DF information of the multicast forwarding table on Router A. [RouterA] display multicast forwarding-table df-info Multicast DF information of VPN-Instance: public net Total 1 RP...
Page 167: Pim-Ssm Configuration Example
Total 1 RP Total 1 RP matched 00001. RP Address: 1.1.1.1 MID: 0, Flags: 0x2100000:0 Uptime: 00:05:12 RPF interface: Serial2/0/1 List of 2 DF interfaces: 1: GigabitEthernet1/0/1 2: GigabitEthernet1/0/2 PIM-SSM configuration example Network requirements As shown in Figure 49, receivers receive VOD information through multicast. The receiver groups of •...
Page 168 Figure 49 Network diagram for PIM-SSM configuration Device Interface IP address Device Interface IP address Router A GE0/0/0 10.110.1.1/24 Router D GE0/0/0 10.110.5.1/24 GE0/0/3 192.168.1.1/24 GE0/0/3 192.168.1.2/24 GE0/0/1 192.168.9.1/24 GE0/0/1 192.168.4.2/24 Router B GE0/0/0 10.110.2.1/24 Router E GE0/0/1 192.168.3.2/24 GE0/0/1 192.168.2.1/24 GE0/0/2 192.168.2.2/24...
Page 169 [RouterA-GigabitEthernet0/0/0] igmp version 3 [RouterA-GigabitEthernet0/0/0] pim sm [RouterA-GigabitEthernet0/0/0] quit [RouterA] interface GigabitEthernet 0/0/3 [RouterA-GigabitEthernet0/0/3] pim sm [RouterA-GigabitEthernet0/0/3] quit [RouterA] interface GigabitEthernet 0/0/1 [RouterA-GigabitEthernet0/0/1] pim sm [RouterA-GigabitEthernet0/0/1] quit The configuration on Router B and Router C is similar to that on Router A. The configuration on Router D and Router E is also similar to that on Router A except that it is not necessary to enable IGMP on the corresponding interfaces on these two routers.
Page 170: Troubleshooting Pim Configuration
Upstream neighbor: 192.168.1.2 RPF prime neighbor: 192.168.1.2 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet0/0/0 Protocol: igmp, UpTime: 00:13:25, Expires: 00:03:25 The information on Router B and Router C is similar to that on Router A. # View the PIM routing table information on Router D. [RouterD] display pim routing-table VPN-Instance: public net Total 0 (*, G) entry;...
Page 171: Multicast Data Abnormally Terminated On An Intermediate Router
the existing unicast route, and is independent of PIM. The RPF interface must be PIM-enabled, and the RPF neighbor must also be a PIM neighbor. If PIM is not enabled on the router where the RPF interface or the RPF neighbor resides, the establishment of a multicast distribution tree will surely fail, causing abnormal multicast forwarding.
Page 172: Rps Unable To Join Spt In Pim-Sm
Solution Check the minimum TTL value for multicast forwarding. Use display current-configuration to check the minimum TTL value for multicast forwarding. Increase the TTL value or remove multicast minimum-ttl configured on the interface. Check the multicast forwarding boundary configuration. Use display current-configuration comand to check the multicast forwarding boundary settings.
Page 173 Solution Check whether routes to C-RPs and the BSR are available. Carry out display ip routing-table to check whether routes are available on each router to the RP and the BSR, and whether a route is available between the RP and the BSR. Make sure that each C-RP has a unicast route to the BSR, the BSR has a unicast route to each C-RP, and all the routers in the entire network have a unicast route to the RP.
Page 174: Configuring Msdp
Configuring MSDP For more information about the concepts of DR, BSR, C-BSR, RP, C-RP, SPT, and RPT mentioned in this document, see “Configuring PIM.” Multicast source discovery protocol (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.
Page 175 Source-side MSDP peer—The MSDP peer nearest to the multicast source (Source), typically the • source-side RP, like RP 1. The source-side RP creates SA messages and sends the messages to its remote MSDP peer to notify the MSDP peer of the locally registered multicast source information. A source-side MSDP peer must be created on the source-side RP.
Page 176 Figure 51 MSDP peering relationships Receiver DR 2 MSDP peers Multicast packets SA message RP 2 Join message PIM-SM 2 Register message DR 1 Source PIM-SM 4 RP 1 RP 3 PIM-SM 1 PIM-SM 3 The process of implementing inter-domain multicast delivery by leveraging MSDP peers is as follows: When the multicast source in PIM-SM 1 sends the first multicast packet to multicast group G, DR 1 •...
Page 177 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...
Page 178 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. 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).
Page 179: Multi-Instance Msdp
RPs share the registered multicast information by means of SA messages. In this example, RP 1 creates an SA message and sends it to RP 2, with the multicast data from Source encapsulated in the SA message. When the SA message reaches RP 2, RP 2 de-encapsulates the message. Receivers receive the multicast data along the RPT and directly join the SPT rooted at the multicast source.
Page 180: Enabling Msdp
Determine the IP addresses of MSDP peers • Determine the address prefix list for an RP address filtering policy • Enabling MSDP Enabling MSDP globally for the public network To do... Use the command... Remarks Enter system view. system-view — Required.
Page 181: Configuring A Static Rpf Peer
If an interface of the router is shared by an MSDP peer and a BGP or MBGP peer at the same time, HP recommends you to configure the IP address of the MSDP peer the same as that of the BGP or MBGP peer.
Page 182: Configuring An Msdp Mesh Group
Configuring an MSDP mesh group An AS can contain multiple MSDP peers. You can use the MSDP mesh group mechanism to avoid SA message flooding among these MSDP peers and optimize the multicast traffic. An MSDP peer in an MSDP mesh group forwards SA messages from outside the mesh group, that have passed the RPF check, to the other members in the mesh group.
Page 183: Configuring Sa Messages Related Parameters
Configuring SA messages related parameters Prerequisites Before configuring SA message delivery, complete the following tasks: Configure any unicast routing protocol so that all devices in the domain are interoperable at the • network layer Configuring basic functions of MSDP • Determine the ACL rules for filtering SA request messages •...
Page 184: Configuring Sa Request Messages
Configuring SA request messages By default, after receiving a new join message, a router does not send an SA request message to any MSDP peer. Instead, it waits for the next SA message from its MSDP peer. This will cause the receiver to delay obtaining multicast source information.
Page 185: Configuring The Sa Cache Mechanism
To do... Use the command... Remarks Required. Configure an SA message import-source [ acl acl-number ] No restrictions on (S, G) entries creation rule. by default. Configure a filtering rule for peer peer-address sa-policy Required. receiving or forwarding SA { import | export } [ acl No filtering rule by default.
Page 186: Displaying And Maintaining Msdp
Displaying and maintaining MSDP To do... Use the command... Remarks display msdp [ all-instance | vpn-instance View the brief information of vpn-instance-name ] brief [ state { connect | down | Available in MSDP peers. listen | shutdown | up } ] [ | { begin | exclude | any view.
Page 187 Figure 54 Network diagram for inter-AS multicast configuration leveraging BGP routes AS 100 AS 200 Receiver Receiver Loop0 Router F Router E GE1/0/1 GE1/0/1 Source 1 S2/0/0 GE1/0/2 PIM-SM 3 Router A PIM-SM 2 Router B S2/0/0 POS5/0/0 GE1/0/1 GE1/0/1 POS5/0/0 Router C Router D...
Page 188 [RouterA] multicast routing-enable [RouterA] interface GigabitEthernet 1/0/1 [RouterA-GigabitEthernet1/0/1] pim sm [RouterA-GigabitEthernet1/0/1] quit [RouterA] interface GigabitEthernet 1/0/2 [RouterA-GigabitEthernet1/0/2] pim sm [RouterA-GigabitEthernet1/0/2] quit [RouterA] interface GigabitEthernet 1/0/3 [RouterA-GigabitEthernet1/0/3] igmp enable [RouterA-GigabitEthernet1/0/3] pim sm [RouterA-GigabitEthernet1/0/3] quit The configuration on Router B, Router C, Router D, Router E, and Router F is similar to the configuration on Router A.
Page 189 # Redistribute BGP routing information into OSPF on Router B. [RouterB] ospf 1 [RouterB-ospf-1] import-route bgp [RouterB-ospf-1] quit The configuration on Router C and Router E is similar to the configuration on Router B. Configure MSDP peers # Configure an MSDP peer on Router B. [RouterB] msdp [RouterB-msdp] peer 192.168.1.2 connect-interface pos 5/0/0 [RouterB-msdp] quit...
Page 190 BGP local router ID : 3.3.3.3 Local AS number : 200 Total number of peers : 1 Peers in established state : 1 Peer MsgRcvd MsgSent OutQ PrefRcv Up/Down State 192.168.3.1 1 00:10:58 Established To view the BGP routing table information on the routers, use display bgp routing-table. For example: # View the BGP routing table information on Router C.
Page 191: Inter-As Multicast Configuration Leveraging Static Rpf Peers
MSDP Peer Brief Information of VPN-Instance: public net Configured Listen Connect Shutdown Down Peer's Address State Up/Down time SA Count Reset Count 192.168.3.2 00:15:32 192.168.1.1 00:06:39 # View the brief information about MSDP peering relationships on Router E. [RouterE] display msdp brief MSDP Peer Brief Information of VPN-Instance: public net Configured Listen...
Page 192 PIM-SM 1 belongs to AS 100, and PIM-SM 2 and PIM-SM 3 belong to AS 200. • Each PIM-SM domain has zero or one multicast source and receiver. OSPF runs within each domain • to provide unicast routes. PIM-SM 2 and PIM-SM 3 are both stub domains, and BGP or MBGP is not required between these •...
Page 193 Procedure Configure IP addresses and unicast routing Configure the IP address and subnet mask for each interface as per Figure 55. Detailed configuration steps are omitted. Configure OSPF for interconnection between the routers in each AS. Ensure the network-layer interoperation in each AS, and ensure the dynamic update of routing information through a unicast routing protocol among the routers.
Page 194 [RouterB-msdp] peer 192.168.1.2 connect-interface pos 5/0/0 [RouterB-msdp] static-rpf-peer 192.168.3.2 rp-policy list-df [RouterB-msdp] static-rpf-peer 192.168.1.2 rp-policy list-df [RouterB-msdp] quit # Configure Router B as MSDP peer and static RPF peer of Router C. [RouterC] ip ip-prefix list-c permit 192.168.0.0 16 greater-equal 16 less-equal 32 [RouterC] msdp [RouterC-msdp] peer 192.168.1.1 connect-interface pos 5/0/0 [RouterC-msdp] static-rpf-peer 192.168.1.1 rp-policy list-c...
Page 195: Anycast Rp Configuration
Peer's Address State Up/Down time SA Count Reset Count 192.168.3.1 00:16:40 Anycast RP configuration Network requirements As shown in Figure 56, the PIM-SM domain in this example has multiple multicast sources and • receivers. OSPF runs within the domain to provide unicast routes. Configure the anycast RP application so that the receiver-side DRs and the source-side DRs can •...
Page 196 Loop10 3.3.3.3/32 Router E GE1/0/1 10.110.6.1/24 Loop20 10.1.1.1/32 S2/0/0 10.110.4.2/24 Procedure Configure IP addresses and unicast routing Configure the IP address and subnet mask for each interface as per Figure 56. Detailed configuration steps are omitted. Configure OSPF for interconnection between the routers in the PIM-SM domain. Ensure the network-layer interoperation among the routers, and ensure the dynamic update of routing information through a unicast routing protocol.
Page 197 # Configure an MSDP peer on Loopback 0 of Router B. [RouterB] msdp [RouterB-msdp] originating-rp loopback 0 [RouterB-msdp] peer 2.2.2.2 connect-interface loopback 0 [RouterB-msdp] quit # Configure an MSDP peer on Loopback 0 of Router D. [RouterD] msdp [RouterD-msdp] originating-rp loopback 0 [RouterD-msdp] peer 1.1.1.1 connect-interface loopback 0 [RouterD-msdp] quit Verify the configuration...
Page 198 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet1/0/1 Protocol: igmp, UpTime: 00:15:04, Expires: - (10.110.5.100, 225.1.1.1) RP: 10.1.1.1 (local) Protocol: pim-sm, Flag: SPT 2MSDP ACT UpTime: 00:46:28 Upstream interface: Serial2/0/0 Upstream neighbor: 10.110.2.2 RPF prime neighbor: 10.110.2.2 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet1/0/1 Protocol: pim-sm, UpTime:...
Page 199: Sa Message Filtering Configuration
Protocol: igmp, UpTime: 00:12:07, Expires: - (10.110.6.100, 225.1.1.1) RP: 10.1.1.1 (local) Protocol: pim-sm, Flag: SPT 2MSDP ACT UpTime: 00:40:22 Upstream interface: Serial2/0/0 Upstream neighbor: 10.110.4.2 RPF prime neighbor: 10.110.4.2 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet1/0/1 Protocol: pim-sm, UpTime: - , Expires: SA message filtering configuration Network requirements...
Page 200 Figure 57 Network diagram for SA message filtering configuration PIM-SM 1 PIM-SM 2 PIM-SM 3 Loop0 Source 2 GE0/0/0 Receiver Loop0 Router A GE0/0/3 Host A GE0/0/0 Router C GE0/0/3 GE0/0/3 Router D GE0/0/0 GE0/0/2 Source 1 GE0/0/3 GE0/0/0 Router B Receiver Receiver Host B...
Page 201 [RouterA-GigabitEthernet0/0/0] quit [RouterA] interface GigabitEthernet 0/0/3 [RouterA-GigabitEthernet0/0/3] pim sm [RouterA-GigabitEthernet0/0/3] quit [RouterA] interface GigabitEthernet 0/0/1 [RouterA-GigabitEthernet0/0/1] pim sm [RouterA-GigabitEthernet0/0/1] quit [RouterA] interface loopback 0 [RouterA-LoopBack0] pim sm [RouterA-LoopBack0] quit The configuration on Router B, Router C and Router D is similar to the configuration on Router A. The specific configuration steps are omitted here.
Page 202 [RouterD-msdp] quit Configure SA message filtering rules # Configure an SA message filter on Router C so that Router C will not forward SA messages for (Source 1, 225.1.1.0/30) to Router D. [RouterC] acl number 3001 [RouterC-acl-adv-3001] rule deny ip source 10.110.3.100 0 destination 225.1.1.0 0.0.0.3 [RouterC-acl-adv-3001] rule permit ip source any destination any [RouterC-acl-adv-3001] quit [RouterC] msdp...
Page 203: Troubleshooting Msdp
Troubleshooting MSDP MSDP peers stay in down state Symptom The configured MSDP peers stay in the down state. Analysis A TCP connection–based MSDP peering relationship is established between the local interface • address and the MSDP peer after the configuration. The TCP connection setup will fail if the local interface address is not consistent with the MSDP peer •...
Page 204: Inter-Rp Communication Faults In Anycast Rp Application
Inter-RP communication faults in Anycast RP application Symptom RPs fail to exchange their locally registered (S, G) entries with one another in the Anycast RP application. Analysis In the Anycast RP application, RPs in the same PIM-SM domain are configured to be MSDP peers to •...
Page 205: Configuring Mbgp
Configuring MBGP This document covers configuration tasks related to multiprotocol BGP for IP multicast only. For more information about BGP, see Layer 3—IP Routing Configuration Guide. For more information about RPF, “Configuring multicast routing and forwarding.” The term router in this document refers to both routers and Layer 3 switches.
Page 206: Controlling Route Advertisement And Reception
To do… Use the command… Remarks Required. Enable a peer or peer group peer { group-name | ip-address } created in IPv4 unicast view. enable Not enabled by default. Specify a preferred value for Optional. peer { group-name | ip-address } routes from an IPv4 MBGP preferred-value value The default preferred value is 0.
Page 207: Configuring Mbgp Route Summarization
To do… Use the command… Remarks Enter MBGP address family ipv4-family multicast — view. Required. No route redistribution is import-route protocol [ { process-id configured by default. Enable route redistribution | all-processes } [ allow-direct | Currently, the allow-direct from another routing protocol. med med-value | route-policy keyword is available only when route-policy-name ] * ]...
Page 208: Configuring Outbound Mbgp Route Filtering
To do… Use the command… Remarks Enter system view. system-view — Enter BGP view. bgp as-number — Enter IPv4 MBGP address ipv4-family multicast — family view. peer { group-name | ip-address } Required. Advertise a default route to an default-route-advertise MBGP peer or peer group.
Page 209: Configuring Mbgp Route Dampening
If several filtering policies are configured, they are applied in the following sequence: filter-policy import • peer filter-policy import • peer as-path-acl import • peer ip-prefix import • peer route-policy import • Members of a peer group can have different route reception filtering policies from the peer group. Only the routes that have passed all the configured policies can be advertised.
Page 210: Configuring Mbgp Route Attributes
To do… Use the command… Remarks dampening [ half-life-reachable Required. Configure BGP route half-life-unreachable reuse dampening parameters. suppress ceiling | route-policy Not configured by default. route-policy-name ] * Configuring MBGP route attributes You can modify MBGP route attributes to affect route selection. Prerequisites Before you configure this task, you need to configure MBGP basic functions.
Page 211: Configuring The Next Hop Attribute
To do… Use the command… Remarks Enter BGP view. bgp as-number — Enter IPv4 MBGP address family ipv4-family multicast — view. Configure the Optional. default MED default med med-value 0 by default. value. Enable the comparison of Optional. the MED of compare-different-as-med Not enabled by default.
Page 212: Configuring The As-Path Attribute
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. If yes, it discards the route to avoid routing loops. To do… Use the command… Remarks Enter system view. system-view —...
Page 213: Enabling The Mbgp Orf Capability
Soft reset through route-refresh If the peer is enabled with route-refresh, when the MBGP route selection policy is modified on a router, the router advertises a route-refresh message to its MBGP peers, which resend their routing information to the router after receiving the message. Therefore, the local router can perform dynamic route update and apply the new policy without terminating MBGP connections.
Page 214 negotiation process and establishing the neighboring relationship, the MBGP router and its MBGP peer can exchange ORF information through specific route-refresh messages. For the parameters configured on both sides for ORF capability negotiation, see Table To do… Use the command… Remarks Enter system view.
Page 215: Configuring The Maximum Number Of Mbgp Routes For Load Balancing
Configuring the maximum number of MBGP routes for load balancing To do… Use the command… Remarks Enter system view. system-view — Enter BGP view. bgp as-number — Enter IPv4 MBGP address ipv4-family multicast — family view. Configure the maximum Required. number of MBGP routes for balance number Not configured by default.
Page 216: Configuring Mbgp Community
Configuring MBGP community The community attribute can be advertised between MBGP peers in different ASs. Routers in the same community share the same policy. You can reference a routing policy to modify the community attribute for routes sent to a peer. In addition, you can define extended community attributes as needed.
Page 217: Displaying And Maintaining Mbgp
To do… Use the command… Remarks Optional. Configure the cluster ID of the reflector cluster-id cluster-id By default, a route reflector uses route reflector. its router ID as the cluster ID. In general, it is not required that clients of a route reflector be fully meshed. The route reflector forwards routing information between clients.
Page 218: Resetting Mbgp Connections
To do… Use the command… Remarks display bgp multicast routing-table Display MBGP routing information community[ aa:nn&<1-13> ] [ no-advertise | Available in matching the specified BGP no-export | no-export-subconfed ] * [ whole-match ] any view. community. [ | { begin | exclude | include } regular-expression ] display bgp multicast routing-table community-list Display MBGP routing information { { basic-community-list-number | comm-list-name }...
Page 219: Mbgp Configuration Example
To do… Use the command… Remarks reset bgp ipv4 multicast flap-info [ regexp as-path-regexp | Clear MBGP route flap statistics. Available in user view. as-path-acl as-path-acl-number | ip-address [ mask | mask-length ] ] MBGP configuration example Network requirements As shown in Figure PIM-SM 1 is in AS 100 and PIM-SM 2 is in AS 200.
Page 220 Procedure Configure IP addresses for router interfaces as shown in Figure 58 (The detailed configuration steps are omitted). Configure OSPF (The detailed configuration steps are omitted). Enable IP multicast routing, PIM-SM and IGMP, and configure a PIM-SM domain border. # Enable IP multicast routing on Router A, and enable PIM-SM on each interface. <RouterA>...
Page 221 [RouterA-pim] c-rp loopback 0 [RouterA-pim] quit # Configure the C-BSR and C-RP on Router B. [RouterB] interface loopback 0 [RouterB-LoopBack0] ip address 2.2.2.2 32 [RouterB-LoopBack0] pim sm [RouterB-LoopBack0] quit [RouterB] pim [RouterB-pim] c-bsr loopback 0 [RouterB-pim] c-rp loopback 0 [RouterB-pim] quit Configure BGP, specify the MBGP peer and enable direct route redistribution.
Page 222 BGP local router ID : 2.2.2.2 Local AS number : 200 Total number of peers : 3 Peers in established state : 3 Peer MsgRcvd MsgSent OutQ PrefRcv Up/Down State 192.168.1.1 0 00:40:54 Established You can use display msdp brief to display MSDP peers on a router. For example, Display brief information about MSDP peers on Router B.
Page 223: Configuring Multicast Vpn
Configuring multicast VPN Multicast VPN is a technique that implements multicast delivery in MPLS L3VPN networks. An MPLS L3VPN is a VPN implemented based on the extension technologies of the BGP and MPLS. It comprises a set of customer sites that are interconnected only by means of an MPLS provider backbone network. You can think of the VPN as a set of policies that control the interconnections between these sites.
Page 224: Introduction To Multicast Vpn
Inner label—Represents an LSP between two CE devices interconnected over the backbone network. • It identifies the site to which the packet belongs. The PE forwards the packet to the target CE based on the inner label. Introduction to Multicast VPN As shown in Figure 60, a network carries independent multicast services—the public network, VPN...
Page 225: Introduction To Md-Vpn
Supporting information exchange and data conversion between the public network and the VPN instances Introduction to MD-VPN For more information about PIM, BSR, C-BSR, RP, C-RP, SPT, and RPT, see “Configuring PIM.” Comware implements multicast VPN by means of the MD method. This multicast VPN implementation is referred to as MD-VPN.
Page 226 Concept Description When the multicast traffic of a VPN reaches or exceeds a threshold, the ingress PE device assigns it an independent multicast address Switch-group called switch-group, and notifies the other PE devices that they should use that address to forward the multicast traffic for that VPN. This initiates a switchover to the switch-MDT.
Page 227 Figure 61 Relationship between PIMon the public network and an MD in a VPN instance Each VPN instance is assigned a unique share-group address. The VPN data is transparent to the public network. A PE device encapsulates any VPN multicast packet within a normal public network multicast packet, no matter what multicast group the VPN packet is destined for and whether it is a protocol packet or a data packet.
Page 228: Introduction To Multicast Across Vpns
PIM neighboring relationships in MD-VPN Figure 62 PIM neighboring relationships in MD-VPN CE 1 PE-P neighbors PE-PE neighbors PE-CE neighbors PE 1 CE 3 PE 3 PE 2 CE 2 PIM neighboring relationships are established between two or more directly interconnected devices on the same subnet.
Page 229 Figure 63 Multicast across VPNs VPN A Site 2 VPN instance A CE 2 Receiver 1 VPN A VPN instance A Site 1 PE 2 CE 1 PE 1 Source 1 PE 3 VPN B Public Site 1 VPN instance B CE 3 Receiver 2 As shown in...
Page 230 Figure 64 Source-side PE configuration VPN A Site 2 VPN instance A CE 2 Receiver 1 VPN instance A VPN A VPN instance B Site 1 PE 2 CE 1 PE 1 Source 1 PE 3 VPN B Public Site 1 VPN instance B Multicast packets CE 3...
Page 231: Protocols And Standards
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.
Page 232 Establishing share-MDT in a PIM-DM network Figure 66 Share-MDT establishment in a PIM-DM network As shown in 0, PIM-DM is enabled in the network and all the PE devices support VPN instance A. The process of establishing a share-MDT is as follows: The public network on PE 1 initiates a flood-prune process in the entire public network, with the BGP interface address (namely the interface address used to establish the BGP peer) as the multicast source address and the share-group address as the multicast group address.
Page 233 Establishing share-MDT 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) SPT (11.1.3.1, 239.1.1.1) PE 1 PE 2 BGP: 11.1.1.1/24 BGP: 11.1.2.1/24 As shown in 0, PIM-SM is enabled in the network and all the PE devices support VPN instance A.
Page 234: Share-Mdt-Based Delivery
Share-MDT establishment in a PIM-SSM network Figure 68 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) PE 1 PE 2 BGP: 11.1.1.1/24 BGP: 11.1.2.1/24 As shown in Figure 68, PIM-SSM is enabled in the network and all the PE devices support VPN instance A.
Page 235 share-MDT, and then decapsulated on the remote PE device to go into the normal protocol procedure. Finally a distribution tree is established across the public network. The following lists how multicast protocol packets are forwarded in the following circumstances: • If the VPN network runs PIM-DM or PIM-SSM: Hello packets are forwarded among MTI interfaces to establish PIM neighboring relationships.
Page 236 PE 2 encapsulates the join message by means of GRE, with its BGP interface address as the multicast • source address and the share-group address as the multicast group address, to convert it into a normal, public network multicast data packet (11.1.2.1, 239.1.1.1). PE 2 then forwards it to the public network.
Page 237: Mdt Switchover
Figure 70 Delivery of multicast data packets The VPN multicast traffic is delivered across the public network as follows. Source sends customer multicast data (192.1.1.1, 225.1.1.1) to CE 1. CE 1 forwards the VPN multicast data along an SPT to CE 1, and the VPN instance on PE 1 checks the MVRF.
Page 238: Multi-As Md Vpn
before it enters the public network. Then, the multicast stream is switched from the share-MDT to the switch-MDT, to deliver the multicast data to only those receivers that need it. The process of share-MDT to switch-MDT switchover is as follows: The source-side PE (PE 1 in this example) device periodically checks the forwarding rate of the VPN multicast traffic.
Page 239: Configuring Md-Vpn
VRF-to-VRF PE interconnectivity As shown in Figure 71, a VPN involves AS 1 and AS 2. PE 3 and PE 4 are the autonomous system boundary router (ASBR) for AS 1 and AS 2 respectively. PE 3 and PE 4 are interconnected through their respective VPN instance and treat each other as a CE device.
Page 240: Enabling Ip Multicast Routing In A Vpn Instance
Configure any unicast routing protocol to provide intra-domain interoperability at the network layer • Configure MPLS L3VPN • Configure PIM (PIM-DM, PIM-SM or PIM-SSM) • Determine the VPN instance names and RDs • Determine the share-group addresses and an MTI numbers •...
Page 241: Configuring Mdt Switchover Parameters
for these BGP peers. Otherwise the MTI interface will also fail to obtain an IP address, either. For more information about the peer connect-interface command, see Layer 3—IP Routing Command Reference. PIM on the MTI interface takes effect only after PIM is enabled on at least one interface of the VPN instance;...
Page 242: Configuring Bgp Mdt
With switch-group reuse logging 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.
Page 243: Specifying The Source Ip Address For Multicast Across Vpns
To do… Use the command… Remarks Enter system view. system-view — Enter BGP view. bgp as-number — Enter BGP MDT sub-address ipv4-family mdt — family view. Required. Configure the local device as peer { group-name | ip-address } a route reflector and specify By default, neither route reflectors reflect-client its clients.
Page 244: Displaying And Maintaining Multicast Vpn
Displaying and maintaining multicast VPN To do... Use the command... Remarks View the share-group information display multicast-domain vpn-instance Available in of the specified VPN instance in vpn-instance-name share-group { local | remote } [ | any view. the MD. { begin | exclude | include } regular-expression ] display multicast-domain vpn-instance vpn-instance-name switch-group receive [ brief | View the switch-group information...
Page 245 Item Network requirements • PE 1—GigabitEthernet 1/0/2 and GigabitEthernet 1/0/3 belong to VPN instance a; GigabitEthernet 1/0/1 and Loopback 1 belong to the public network. • PE 2—GigabitEthernet 1/0/2 belongs to VPN instance b; PE interfaces and VPN GigabitEthernet 1/0/3 belongs to VPN instance a; GigabitEthernet instances they belong to 1/0/1 and Loopback 1 belong to the public network.
Page 246 Figure 73 Network diagram for single-AS MD-VPN configuration Device Interface IP address Device Interface IP address — 10.110.7.2/24 PE 3 GE1/0/1 192.168.8.1/24 — 10.110.8.2/24 GE1/0/2 10.110.5.1/24 — 10.110.1.2/24 GE1/0/3 10.110.6.1/24 — 10.110.9.2/24 Loop1 1.1.1.3/32 — 10.110.10.2/24 Loop2 33.33.33.33/32 — 10.110.11.2/24 CE a1 GE1/0/1 10.110.7.1/24...
Page 247 Procedure Configure PE 1 # Configure a Router ID, enable IP multicast routingon the public network, configure an MPLS LSR ID, and enable the LDP capability. <PE1> system-view [PE1] router id 1.1.1.1 [PE1] multicast routing-enable [PE1] mpls lsr-id 1.1.1.1 [PE1] mpls [PE1-mpls] quit [PE1] mpls ldp [PE1-mpls-ldp] quit...
Page 248 # Configure an IP address for Loopback 1, and enable PIM-SM. [PE1] interface loopback 1 [PE1-LoopBack1] ip address 1.1.1.1 32 [PE1-LoopBack1] pim sm [PE1-LoopBack1] quit # Configure BGP. [PE1] bgp 100 [PE1-bgp] group vpn-g internal [PE1-bgp] peer vpn-g connect-interface loopback 1 [PE1-bgp] peer 1.1.1.2 group vpn-g [PE1-bgp] peer 1.1.1.3 group vpn-g [PE1–bgp] ipv4-family vpn-instance a...
Page 249 [PE2-mpls-ldp] quit # Create VPN instance b, configure an RD for it, and create an ingress route and an egress route for it. [PE2] ip vpn-instance b [PE2-vpn-instance-b] route-distinguisher 200:1 [PE2-vpn-instance-b] vpn-target 200:1 export-extcommunity [PE2-vpn-instance-b] vpn-target 200:1 import-extcommunity # 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.
Page 250 # Configure an IP address for Loopback 1, and enable PIM-SM. [PE2] interface loopback 1 [PE2-LoopBack1] ip address 1.1.1.2 32 [PE2-LoopBack1] pim sm [PE2-LoopBack1] quit # Configure BGP. [PE2] bgp 100 [PE2-bgp] group vpn-g internal [PE2-bgp] peer vpn-g connect-interface loopback 1 [PE2-bgp] peer 1.1.1.1 group vpn-g [PE2-bgp] peer 1.1.1.3 group vpn-g [PE2–bgp] ipv4-family vpn-instance a...
Page 251 [PE2-rip-3] return Configure PE 3 # Configure a Router ID, enable IP multicast routingon the public network, configure an MPLS LSR ID, and enable the LDP capability. <PE3> system-view [PE3] router id 1.1.1.3 [PE3] multicast routing-enable [PE3] mpls lsr-id 1.1.1.3 [PE3] mpls [PE3-mpls] quit [PE3] mpls ldp...
Page 252 [PE3-GigabitEthernet1/0/2] ip address 10.110.5.1 24 [PE3-GigabitEthernet1/0/2] pim sm [PE3-GigabitEthernet1/0/2] quit # Bind GigabitEthernet 1/0/3 with VPN instance b, configure an IP address and enable PIM-SM on the interface. [PE3] interface GigabitEthernet 1/0/3 [PE3-GigabitEthernet1/0/3] ip binding vpn-instance b [PE3-GigabitEthernet1/0/3] ip address 10.110.6.1 24 [PE3-GigabitEthernet1/0/3] pim sm [PE3-GigabitEthernet1/0/3] quit # Configure an IP address for Loopback 1, and enable PIM-SM.
Page 253 The interface MTI 0 will automatically obtain an IP address after BGP peer configuration on PE 3. This address is the loopback interface address specified in the BGP peer configuration. The PIM mode running on MTI 0 is the same as the PIM mode running on all the interfaces in VPN instance a. The interface MTI 1 will automatically obtain an IP address after BGP peer configuration on PE 3.
Page 254 [P-GigabitEthernet1/0/2] mpls [P-GigabitEthernet1/0/2] mpls ldp [P-GigabitEthernet1/0/2] quit # Configure an IP address, enable PIM-SM and LDP capability on the public network interface GigabitEthernet 1/0/3. [P] interface GigabitEthernet 1/0/3 [P-GigabitEthernet1/0/3] ip address 192.168.8.2 24 [P-GigabitEthernet1/0/3] pim sm [P-GigabitEthernet1/0/3] mpls [P-GigabitEthernet1/0/3] mpls ldp [P-GigabitEthernet1/0/3] quit # Configure an IP address for Loopback 1 and enable PIM-SM on the interface.
Page 255 # Enable IP multicast routing. <CEb1> system-view [CEb1] multicast routing-enable # Configure an IP address and enable PIM-SM on GigabitEthernet 1/0/1. [CEb1] interface GigabitEthernet 1/0/1 [CEb1-GigabitEthernet1/0/1] ip address 10.110.8.1 24 [CEb1-GigabitEthernet1/0/1] pim sm [CEb1-GigabitEthernet1/0/1] quit # Configure an IP address and enable PIM-SM on GigabitEthernet 1/0/2. [CEb1] interface GigabitEthernet 1/0/2 [CEb1-GigabitEthernet1/0/2] ip address 10.110.3.2 24 [CEb1-GigabitEthernet1/0/2] pim sm...
Page 256 [CEa2-pim] c-rp loopback 1 [CEa2-pim] quit # Configure RIP. [CEa2] rip 2 [CEa2-rip-2] network 10.0.0.0 [CEa2-rip-2] network 22.0.0.0 Configure CE a3 # Enable IP multicast routing. <CEa3> system-view [CEa3] multicast routing-enable # Configure an IP address, and enable IGMP and PIM-SM on GigabitEthernet 1/0/1. [CEa3] interface GigabitEthernet 1/0/1 [CEa3-GigabitEthernet1/0/1] ip address 10.110.10.1 24 [CEa3-GigabitEthernet1/0/1] igmp enable...
Page 257: Multi-As Md Vpn Configuration
# Configure RIP. [CEb2] rip 3 [CEb2-rip-3] network 10.0.0.0 Verify the configuration To view the share-group information of a VPN instance, use display multicast-domain vpn-instance share-group. # View the local share-group information of VPN instance a on PE 1. <PE1> 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...
Page 258 Item Network requirements • PE 1—GigabitEthernet 1/0/2 belongs to VPN instance a; GigabitEthernet 1/0/3 belongs to VPN instance b; GigabitEthernet 1/0/1 and Loopback 1 belong to the public network instance. • PE 2—GigabitEthernet 1/0/1, GigabitEthernet 1/0/2, Loopback 1 and PE interfaces and Loopback 2 belong to the public network instance.
Page 259 Figure 74 Network diagram for multi-AS MD-VPN configuration Loop0 Loop0 CE a1 CE b2 GE1/0/1 GE1/0/1 VPN a VPN b GE1/0/1 GE1/0/2 GE1/0/1 GE1/0/1 GE1/0/2 GE1/0/1 PE 1 PE 4 PE 2 PE 3 ASBR ASBR AS 100 AS 200 GE1/0/1 GE1/0/1 CE a2...
Page 260 [PE1] router id 1.1.1.1 [PE1] multicast routing-enable [PE1] mpls lsr-id 1.1.1.1 [PE1] mpls [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.
Page 261 [PE1-GigabitEthernet1/0/3] ip binding vpn-instance b [PE1-GigabitEthernet1/0/3] ip address 10.11.2.1 24 [PE1-GigabitEthernet1/0/3] pim sm [PE1-GigabitEthernet1/0/3] quit # Configure an IP address for Loopback 1, and enable PIM-SM. [PE1] interface loopback 1 [PE1-LoopBack1] ip address 1.1.1.1 32 [PE1-LoopBack1] pim sm [PE1-LoopBack1] quit # Configure BGP.
Page 262 [PE1-ospf-2-area-0.0.0.0] quit [PE1-ospf-2] quit [PE1] ospf 3 vpn-instance b [PE1-ospf-3] import-route bgp [PE1-ospf-3] area 0.0.0.0 [PE1-ospf-3-area-0.0.0.0] network 10.11.0.0 0.0.255.255 [PE1-ospf-3-area-0.0.0.0] quit [PE1-ospf-3] quit Configure PE 2 # Configure a Router ID, enable IP multicast routingon the public network, configure an MPLS LSR ID, and enable the LDP capability.
Page 263 [PE2-pim] c-bsr loopback 2 [PE2-pim] c-rp loopback 2 [PE2-pim] quit # Configure a BSR message boundary. [PE2] interface GigabitEthernet 1/0/2 [PE2-GigabitEthernet1/0/2] pim bsr-boundary [PE2-GigabitEthernet1/0/2] quit # 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.
Page 264 # Configure a Router ID, enable IP multicast routingon the public network, configure an MPLS LSR ID, and enable the LDP capability. <PE3> system-view [PE3] router id 1.1.1.3 [PE3] multicast routing-enable [PE3] mpls lsr-id 1.1.1.3 [PE3] mpls [PE3-mpls] quit [PE3] mpls ldp [PE3-mpls-ldp] quit # Configure an IP address, and enable PIM-SM and LDP capability on the public network interface GigabitEthernet 1/0/1.
Page 265 [PE3-msdp] encap-data-enable [PE3-msdp] peer 1.1.1.2 connect-interface loopback 1 # Configure a static route. [PE3] ip route-static 1.1.1.2 32 GigabitEthernet 1/0/2 192.168.1.1 # Configure BGP. [PE3] bgp 200 [PE3-bgp] import-route ospf 1 [PE3-bgp] group pe3-pe4 internal [PE3-bgp] peer pe3-pe4 route-policy map2 export [PE3-bgp] peer pe3-pe4 label-route-capability [PE3-bgp] peer pe3-pe4 connect-interface loopback 1 [PE3-bgp] peer 1.1.1.4 group pe3-pe4...
Page 266 # 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. [PE4] ip vpn-instance a [PE4-vpn-instance-a] route-distinguisher 100:1 [PE4-vpn-instance-a] vpn-target 100:1 export-extcommunity...
Page 267 [PE4-LoopBack1] pim sm [PE4-LoopBack1] quit # Configure BGP. [PE4] bgp 200 [PE4-bgp] group pe4-pe3 internal [PE4-bgp] peer pe4-pe3 label-route-capability [PE4-bgp] peer pe4-pe3 connect-interface loopback 1 [PE4-bgp] peer 1.1.1.3 group pe4-pe3 [PE4-bgp] group pe4-pe1 external [PE4-bgp] peer pe4-pe1 as-number 100 [PE4-bgp] peer pe4-pe1 ebgp-max-hop 255 [PE4-bgp] peer 1.1.1.1 group pe4-pe1 [PE4-bgp] peer pe4-pe1 connect-interface loopback 1 [PE4–bgp] ipv4-family vpn-instance a...
Page 268 [PE4-ospf-3] quit Configure CE a1. # Enable IP multicast routing. <CEa1> system-view [CEa1] multicast routing-enable # Configure an IP address and enable PIM-SM on GigabitEthernet 1/0/1. [CEa1] interface GigabitEthernet 1/0/1 [CEa1-GigabitEthernet1/0/1] ip address 10.11.5.1 24 [CEa1-GigabitEthernet1/0/1] pim sm [CEa1-GigabitEthernet1/0/1] quit # Configure an IP address and enable PIM-SM on GigabitEthernet 1/0/2.
Page 269 [CEb1-GigabitEthernet1/0/2] pim sm [CEb1-GigabitEthernet1/0/2] quit # Configure OSPF. [CEb1] ospf 1 [CEb1-ospf-1] area 0.0.0.0 [CEb1-ospf-1-area-0.0.0.0] network 10.11.0.0 0.0.255.255 [CEb1-ospf-1-area-0.0.0.0] quit [CEb1-ospf-1] quit Configure CE a2. # Enable IP multicast routing. <CEa2> system-view [CEa2] multicast routing-enable # Configure an IP address and enable IGMP and PIM-SM on GigabitEthernet 1/0/1. [CEa2] interface GigabitEthernet 1/0/1 [CEa2-GigabitEthernet1/0/1] ip address 10.11.7.1 24 [CEa2-GigabitEthernet1/0/1] igmp enable...
Page 270 # Configure an IP address for Loopback 1, and enable PIM-SM. [CEb2] interface loopback 1 [CEb2-LoopBack1] ip address 3.3.3.3 32 [CEb2-LoopBack1] pim sm [CEb2-LoopBack1] quit # Configure Loopback 1 as a C-BSR and a C-RP for VPN b. [CEb2] pim [CEb2-pim] c-bsr loopback 1 [CEb2-pim] c-rp loopback 1 [CEb2-pim] quit...
Page 271: Troubleshooting Md-Vpn Configuration
Troubleshooting MD-VPN configuration A share-MDT cannot be established Symptom A share-MDT cannot be established. PIM adjacencies cannot be established between the same VPN instance’s interfaces on different PE devices. Analysis On different PE devices, the same share-group must be configured for the same VPN instance. A •...
Page 272 The customer DR must have a route to the VPN RP. • Solution Use display pim bsr-info to check whether the BSR information existson the public network and VPN instance. If not, check whether a unicast route exists to the BSR. Use display pim rp-info to view the RP information.
Page 273: Configuring Ipv6 Multicast Routing And Forwarding
Configuring IPv6 multicast routing and forwarding In IPv6 multicast implementations, multicast routing and forwarding are implemented by routing and forwarding tables: Each IPv6 multicast routing protocol has its own multicast routing table, such as the IPv6 PIM routing • table. The multicast routing information of different IPv6 multicast routing protocols forms a general IPv6 •...
Page 274 The router selects one of these optimal routes as the RPF route. The selection process is as follows: If configured to use the longest match principle, the router selects the longest match route from the two. If these routes have the same prefix length, the router selects the route with a higher priority.
Page 275: Enabling Ipv6 Multicast Routing
Figure 75 RPF check process When an IPv6 multicast packet arrives on POS 5/0/0/1 of Router C, because the interface is the • incoming interface of the (S, G) entry, the router forwards the packet to all outgoing interfaces. When an IPv6 multicast packet arrives on POS 5/0/0 of Router C, because the interface is not the •...
Page 276: Configuring An Ipv6 Multicast Routing Policy
Configuring an IPv6 multicast routing policy You can configure the router to determine the RPF route based on the longest match principle. For more information about RPF route selection, see “RPF Check process.” 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.
Page 277: Configuring Ipv6 Static Multicast Mac Address Entries
When forwarding IPv6 multicast traffic, the router replicates a copy of the IPv6 multicast traffic for each downstream node and forwards the traffic, and thus each of these downstream nodes forms a branch of the IPv6 multicast distribution tree. You can configure the maximum number of downstream nodes (namely, the maximum number of outgoing interfaces) for a single entry in the IPv6 multicast forwarding table to lessen the burden on the router for replicating IPv6 multicast traffic.
Page 278: Displaying And Maintaining Ipv6 Multicast Routing And Forwarding
When configuring a static multicast MAC address entry in system view, the configuration is effective for the specified interface. When configuring a static multicast MAC address entry in interface view or port group view, the configuration is effective only for the current interface or interfaces in the current port group.
Page 279: Troubleshooting Ipv6 Multicast Policy Configuration
To do... Use the command... Remarks Display the RPF route information display multicast ipv6 rpf-info ipv6-source-address Available in of the specified IPv6 multicast [ ipv6-group-address ] [ | { begin | exclude | include } any view. source. regular-expression ] display mac-address [ mac-address [ vlan vlan-id ] | Display IPv6 static multicast MAC Available in...
Page 280 The multicast ipv6 boundary command filters IPv6 multicast packets received on an interface. If an • IPv6 multicast packet fails to match the IPv6 ACL rule of this command, IPv6 PIM will create no routing entry. In addition, the source-policy command in IPv6 PIM filters received IPv6 multicast packets. If an IPv6 •...
Page 281: Configuring Mld
Configuring MLD The MLD is used by an IPv6 router 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.
Page 282 Joining an IPv6 multicast group Figure 76 MLD queries and reports IPv6 network Querier Router A Router B Ethernet Host A Host B Host C (G2) (G1) (G1) Query Report Assume that Host B and Host C will receive IPv6 multicast data addressed to IPv6 multicast group G1, and Host A will receive IPv6 multicast data addressed to G2, as shown in Figure 76.
Page 283: Mldv2 Operation
The host sends an MLD done message to all IPv6 multicast routers on the local subnet. The destination address is FF02::2. After receiving the MLD done message, the querier sends a configurable number of multicast-address-specific queries to the group that the host is leaving. The destination address field and group address field of the message are both filled with the address of the IPv6 multicast group that is being queried.
Page 284: Mld Message Types
In the case of MLDv1, Host B cannot select IPv6 multicast sources when it joins IPv6 multicast group G. Therefore, IPv6 multicast streams from both Source 1 and Source 2 will flow to Host B whether it needs them or not. 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).
Page 285 Figure 78 Format of MLDv2 query message Type = 130 Code Checksum Maximum Response Delay Reserved Multicast Address (128 bits) Reserved QQIC Number of Sources (n) Source Address [1] (128 bits) Source Address [n] (128 bits) Table 11 Description on fields in an MLDv2 query message Field Description Type = 130...
Page 286 Field Description • This field is set to 0 in a general query message or a multicast-address-specific query message. Number of Sources • This field represents the number of source addresses in a multicast-address-and-source-specific query message IPv6 multicast source address in a multicast-address-specific query Source Address( i ) message (i = 1, 2, .., n, where n represents the number of multicast source addresses.)
Page 287: Mld Ssm Mapping
MLD SSM mapping The MLD SSM mapping feature enables you to configure static MLD SSM mappings on the last hop router to provide SSM support for receiver hosts that are running MLDv1. The SSM model assumes that the last hop router has identified the desired IPv6 multicast sources when receivers join IPv6 multicast groups. •...
Page 288: Mld Proxying
MLD proxying In some simple tree-shaped topologies, you do not need to configure complex IPv6 multicast routing protocols, such as IPv6 PIM, on the boundary devices. Instead, you can configure MLD proxying on these devices. With MLD proxying configured, the router serves as a proxy for the downstream hosts to send MLD messages, maintain group memberships, and implement IPv6 multicast forwarding based on the memberships.
Page 289: Protocols And Standards
If no configuration is performed in interface view, the global configuration in MLD view will apply to that interface. Configurations performed in interface view take precedence over those performed in MLD view. Protocols and standards • RFC 2710, Multicast Listener Discovery (MLD) for IPv6 •...
Page 290: Configuring Static Joining
Configuring an MLD version globally To do… Use the command… Remarks Enter system view. system-view — Enter MLD view. — Optional. Configure an MLD version version version-number globally. MLDv1 by default. Configuring an MLD version on an interface To do… Use the command…...
Page 291: Configuring An Ipv6 Multicast Group Filter
Configuring an IPv6 multicast group filter To restrict the hosts on the network attached to an interface from joining certain IPv6 multicast groups, you can set an IPv6 ACL rule on the interface so that the interface maintains only the IPv6 multicast groups matching the criteria.
Page 292: Configuring Mld Message Options
• Determine the MLD query interval • Determine the MLD querier’s robustness variable • Determine the maximum response delay of MLD general query messages • Determine the MLD last listener query interval • Determine the MLD other querier present interval Configuring MLD message options MLD queries include multicast-address-specific queries and multicast-address-and-source-specific queries, and IPv6 multicast groups change dynamically, so a router cannot maintain the information for all IPv6...
Page 293: Configuring Mld Query And Response Parameters
To do… Use the command… Remarks Optional. Enable the insertion of the Router-Alert option into MLD mld send-router-alert By default, MLD messages carry messages. the Router-Alert option. Configuring MLD query and response parameters The MLD querier’s robustness variable defines the maximum number of attempts for transmitting MLD general queries, multicast-address-specific queries, or multicast-address-and-source-specific queries in case of packet loss due to network problems.
Page 294 To do… Use the command… Remarks Enter MLD view. — Optional. Configure the MLD querier’s robust-count robust-value robustness variable. 2 times by default. Optional. Configure the startup query By default, the startup query startup-query-interval interval interval. interval is 1/4 of the “MLD query interval”.
Page 295: Configuring Mld Fast Leave Processing
To do… Use the command… Remarks Optional. Configure the MLD query mld timer query interval interval. 125 seconds by default. Configure the maximum Optional. response delay for MLD mld max-response-time interval 10 seconds by default. general query messages. Optional. Configure the MLD last listener mld last-listener-query-interval query interval.
Page 296: Enabling The Mld Host Tracking Function
To do… Use the command… Remarks interface interface-type Enter interface view. — interface-number Required. Configure MLD fast leave mld fast-leave [ group-policy processing. acl6-number ] Disabled by default. Enabling the MLD host tracking function With the MLD host tracking function, the switch can record the information of the member hosts that are receiving IPv6 multicast traffic, including the host IPv6 address, running duration, and timeout time.
Page 297: Enabling Mld Ssm Mapping
Enabling MLD SSM mapping To do… Use the command… Remarks Enter system view. system-view — interface interface-type Enter interface view. — interface-number Required. Enable the MLD SSM mld ssm-mapping enable mapping feature. Disabled by default. To ensure SSM service for all hosts on a subnet, regardless of the MLD version running on the hosts, enable MLDv2 on the interface that forwards IPv6 multicast traffic onto the subnet.
Page 298: Configuring Ipv6 Multicast Forwarding On A Downstream Interface
You cannot enable MLD on interfaces with MLD proxying enabled. Moreover, only the mld require-router-alert, mld send-router-alert, and mld version commands can take effect on such interfaces. You cannot enable other IPv6 multicast routing protocols (such as IPv6 PIM-DM or IPv6 PIM-SM) on interfaces with MLD proxying enabled, or vice versa.
Page 299: Mld Configuration Examples
To do… Use the command… Remarks Display information about the display mld host port-info vlan vlan-id group hosts tracked by MLD on the ipv6-group-address [ source ipv6-source-address ] [ vlan Available in Layer 2 ports (on a distributed vlan-id ] [ slot slot-number ] [ | { begin | exclude | any view.
Page 300 • Router A connects to N1 through GigabitEthernet 1/0/1, and to other devices in the IPv6 PIM network through POS 5/0/0. Router B and Router C connect to N2 through their respective GigabitEthernet 1/0/1, and to other • devices in the IPv6 PIM network through their respective POS 5/0/0. MLDv1 is required between Router A and N1.
Page 301 [RouterA-Pos5/0/0] quit # Enable IPv6 multicast routing on Router B, enable IPv6 PIM-DM on each interface, and enable MLD on the host-side interface GigabitEthernet 1/0/1. <RouterB> system-view [RouterB] multicast ipv6 routing-enable [RouterB] interface GigabitEthernet 1/0/1 [RouterB-GigabitEthernet1/0/1] mld enable [RouterB-GigabitEthernet1/0/1] pim ipv6 dm [RouterB-GigabitEthernet1/0/1] quit [RouterB] interface pos 5/0/0 [RouterB-Pos5/0/0] pim ipv6 dm...
Page 302: Mld Ssm Mapping Configuration Example
MLD SSM mapping configuration example Network requirements As shown in Figure 83, the IPv6 PIM-SM domain applies both the ASM model and SSM model for • IPv6 multicast delivery. Router D’s GigabitEthernet 1/0/3 serves as the C-BSR and C-RP. The SSM group range is FF3E::/64.
Page 303 Enable IPv6 multicast routing, enable IPv6 PIM-SM on each interface and enable MLD and MLD SSM mapping on the host-side interface. # Enable IPv6 multicast routing on Router D, enable IPv6 PIM-SM on each interface and enable MLD (version 2) and MLD SSM mapping on GigabitEthernet 1/0/1. <RouterD>...
Page 304 Configure MLD SSM mappings # Configure MLD SSM mappings on Router D. [RouterD] mld [RouterD-mld] ssm-mapping ff3e:: 64 1001::1 [RouterD-mld] ssm-mapping ff3e:: 64 3001::1 [RouterD-mld] quit Verify the configuration Use display mld ssm-mapping to view MLD SSM mappings on the router. # Display the MLD SSM mapping information for IPv6 multicast group FF3E::101 on Router D.
Page 305: Mld Proxying Configuration Example
UpTime: 00:13:25 Upstream interface: GigabitEthernet1/0/2 Upstream neighbor: 3002::1 RPF prime neighbor: 3002::1 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet1/0/1 Protocol: mld, UpTime: 00:13:25, Expires: - MLD proxying configuration example Network requirements As shown in Figure 84, IPv6 PIM-DM is required to run on the core network. Host A and Host C in the stub network receive VOD information sent to multicast group FF3E::101.
Page 306: Troubleshooting Mld
# Enable IPv6 multicast routing on Router B, MLD proxying on GigabitEthernet 1/0/1, and MLD on GigabitEthernet 1/0/2. <RouterB> system-view [RouterB] multicast ipv6 routing-enable [RouterB] interface GigabitEthernet 1/0/1 [RouterB-GigabitEthernet1/0/1] mld proxying enable [RouterB-GigabitEthernet1/0/1] quit [RouterB] interface GigabitEthernet 1/0/2 [RouterB-GigabitEthernet1/0/2] mld enable [RouterB-GigabitEthernet1/0/2] quit Verify the installation Use display mld interface to view the MLD configuration and operation information on an interface.
Page 307: Inconsistent Memberships On Routers On The Same Subnet
• If the MLD version on the router interface is lower than that on the host, the router will not be able to recognize the MLD report from the host. If mld group-policy has been configured on an interface, the interface cannot receive report •...
Page 308: Configuring Ipv6 Pim
Configuring IPv6 PIM Protocol Independent Multicast for IPv6 (IPv6 PIM) provides IPv6 multicast forwarding by leveraging 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.
Page 309 Neighbor discovery In an IPv6 PIM domain, a PIM router discovers IPv6 PIM neighbors, maintains IPv6 PIM neighboring relationships with other routers, and builds and maintains SPTs by periodically multicasting IPv6 PIM hello messages to all other IPv6 PIM routers on the local subnet. Every IPv6 PIM enabled interface on a router sends hello messages periodically, and thus learns the IPv6 PIM neighboring information pertinent to the interface.
Page 310 Pruning has a similar implementation in IPv6 PIM-SM. Graft When a host attached to a pruned node joins an IPv6 multicast group, to reduce the join latency, IPv6 PIM-DM uses the graft mechanism to resume IPv6 multicast data forwarding to that branch. The process is as follows: The node that needs to receive IPv6 multicast data sends a graft message toward its upstream node, as a request to join the SPT again.
Page 311: Understanding Ipv6 Pim-Sm
Understanding IPv6 PIM-SM IPv6 PIM-DM uses the flood-and-prune principle to build SPTs for IPv6 multicast data distribution. Although an SPT has the shortest path, it is built with a low efficiency. Therefore the PIM-DM mode is not suitable for large-sized and medium-sized networks. IPv6 PIM-SM is a type of sparse mode IPv6 multicast protocol.
Page 312 In the case of a multi-access network, a DR must be elected, no matter this network connects to IPv6 multicast sources or to receivers. The DR at the receiver side sends join messages to the RP; the DR at the IPv6 multicast source side sends register messages to the RP.
Page 313 A router can server as a C-RP and a C-BSR at the same time. As shown in Figure 88, each C-RP periodically unicasts its advertisement messages (C-RP-Adv messages) to the BSR. A C-RP-Adv message contains the address of the advertising C-RP and the IPv6 multicast group range it serves.
Page 314 Embedded RP The embedded RP mechanism enables a router to resolve the RP address from an IPv6 multicast address so that the IPv6 multicast group is mapped to an RP. This RP can take the place of the statically configured RP or the RP dynamically calculated based on the BSR mechanism.
Page 315 node from the outgoing interface list and determines whether it has receivers for that IPv6 multicast group. If not, the router continues to forward the prune message to its upstream router. Multicast source registration The purpose of IPv6 multicast source registration will inform the RP about the existence of the IPv6 multicast source.
Page 316: Understanding Ipv6 Bidir-Pim
The DR at the source side and the RP need to implement complicated encapsulation and • decapsulation 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. •...
Page 317 Neighbor discovery IPv6 BIDIR-PIM uses the same neighbor discovery mechanism as IPv6 PIM-SM does. For more information, “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 RPA.
Page 318 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. The source-side RPT is also rooted at the RP but takes the routers directly connected with the IPv6 multicast sources as leaves. The processes for building these two parts are different.
Page 319: Ipv6 Administrative Scoping
Figure 93 RPT building at the multicast source side As shown in Figure 93, the process of building a source-side RPT is relatively simple: When an IPv6 multicast source sends IPv6 multicast packets to IPv6 multicast group G, the DF in each network segment unconditionally forwards the packets to the RP.
Page 320 cannot cross the IPv6 admin-scope zone boundary. IPv6 multicast group ranges served by different IPv6 admin-scope zones can overlap. An IPv6 multicast group is valid only within its local IPv6 admin-scope zone, functioning as a private group address. The IPv6 global scope zone maintains a BSR, which serves the IPv6 multicast groups with the Scope field in their group addresses being 14.
Page 321: Implementing An Ssm Model In Ipv6 Pim
Figure 95 IPv6 multicast address format The admin-scope zone range increases with the value of the Scope field. For example, value E indicates IPv6 global scope, which contains other admin-scope zones with the Scope field values smaller than E. Possible values of the Scope field are given in Table Table 14 Values of the Scope field Value...
Page 322: Configuring Ipv6 Pim-Dm
DR election IPv6 PIM-SSM uses the same DR election mechanism as in IPv6 PIM-SM. For more information, see “DR election.” SPT building Whether to build an RPT for IPv6 PIM-SM or an SPT for IPv6 PIM-SSM depends on whether the IPv6 multicast group that the receiver will join falls in the IPv6 SSM group range.
Page 323: Protocols And Standards
Figure 97 Relationships among IPv6 PIM protocols A receiver joins IPv6 multicast group G G is in the IPv6 SSM The receiver specifies an group range IPv6 multicast source? An MLD SSM mapping is IPv6 BIDIR-PIM is used? configured for G? G has corresponding IPv6 Use IPv6 PIM-SM for G Use IPv6 PIM-SSM for G...
Page 324: Enabling Ipv6 Pim-Dm
Enabling IPv6 PIM-DM With IPv6 PIM-DM enabled, a router sends hello messages periodically to discover IPv6 PIM neighbors and processes messages from the IPv6 PIM neighbors. When you deploy an IPv6 PIM-DM domain, enable IPv6 PIM-DM on all non-border interfaces of routers. All the interfaces of the same device must work in the same IPv6 PIM mode.
Page 325: Configuring Ipv6 Pim-Dm Graft Retry Period
state-refresh message might cycle in the network. To control the propagation scope of state-refresh messages, you must configure an appropriate hop limit value based on the network size. Perform the following configurations on all routers in the IPv6 PIM domain. To do...
Page 326: Enabling Ipv6 Pim-Sm
Determine the legal C-RP address range and the ACL rule defining the range of IPv6 multicast groups • to be served Determine the C-RP-Adv interval • Determine the C-RP timeout • Determine the C-BSR priority • Determine the hash mask length •...
Page 327 RP-set, which is flooded throughout the entire network. Then, the other routers in the network calculate the mappings between specific group ranges and the corresponding RPs based on the RP-Set. HP recommends you to configure C-RPs on backbone routers.
Page 328: Configuring A Bsr
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. This RP can replace the statically configured RP or the RP dynamically calculated based on the BSR mechanism. Thus, the DR does not need to know the RP address beforehand.
Page 329 Configuring a C-BSR You should configure C-BSRs on routers in the backbone network. When you configure a router as a C-BSR, be sure to specify the IPv6 address of an IPv6 PIM-SM-enabled interface on the router. The BSR election process is as follows: Initially, every C-BSR assumes itself to be the BSR of this IPv6 PIM-SM domain, and uses its interface •...
Page 330 An IPv6 PIM domain border is a bootstrap message boundary. Each BSR has its specific service scope. IPv6 PIM domain border interfaces partition a network into different IPv6 PIM-SM domains. Bootstrap messages cannot cross a domain border in either direction. Perform the following configuration on routers that you want to configure as an IPv6 PIM domain border.
Page 331: Configuring Ipv6 Administrative Scoping
Make sure that the BS period value is smaller than the BS timeout value. The BS period defaults to the value determined by the formula: BS period = (BS timeout – 10) / 2 The default BS timeout is 130 seconds, so the default BS period = (130 – 10) / 2 = 60 (seconds) The BS timeout setting defaults to the value determined by the formula: BS timeout = BS period ×...
Page 332 Enabling IPv6 administrative scoping Before you configure an IPv6 admin-scope zone, you must enable IPv6 administrative scoping first. Perform the following configuration on all routers in the IPv6 PIM-SM domain. To do… Use the command… Remarks Enter system view. system-view —...
Page 333: Configuring Ipv6 Multicast Source Registration
In view of information integrity of register messages in the transmission process, you can configure the router to calculate the checksum based on the entire register messages. However, to reduce the workload of encapsulating data in register messages and for the sake of interoperability, HP does not recommend this method of checksum calculation.
Page 334: Configuring Spt Switchover
To do... Use the command... Remarks Optional. Configure the register probe probe-interval interval time. 5 seconds by default. Configuring SPT switchover Both the receiver-side DR and the RP can periodically check the traffic rate of passing-by IPv6 multicast packets (this function is not available with switches) and thus trigger RPT-to-SPT switchover. Perform the following configuration on routers that might become receiver-side DRs and on C-RP routers.
Page 335: Configuration Prerequisites
Task Remarks Configuring C-BSRs for each admin-scope zone Optional Configuring IPv6 PIM common features Configuration prerequisites Before you configure IPv6 BIDIR-PIM, complete the following tasks: Enable IPv6 forwarding and configure an IPv6 unicast routing protocol so that all devices in the •...
Page 336: Enabling Ipv6 Bidir-Pim
RP-set, which is flooded throughout the entire network. Then, the other routers in the network calculate the mappings between specific group ranges and the corresponding RPs based on the RP-set. HP recommends that you configure C-RPs on backbone routers.
Page 337 To do... Use the command... Remarks Enter IPv6 PIM view. pim ipv6 — c-rp ipv6-address [ { group-policy Required. acl6-number | scope scope-id } | Configure an interface to be a priority priority | holdtime hold-interval No C-RP is configured by C-RP for IPv6 BIDIR-PIM.
Page 338: Configuring A Bsr
To do... Use the command... Remarks Optional Configure C-RP timeout time. c-rp holdtime interval 150 seconds by default For more information about the configuration of other timers in IPv6 PIM-SM, see “Configuring IPv6 PIM common 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.
Page 339 To do… Use the command… Remarks Required. Configure an interface as a c-bsr ipv6-address [ hash-length No C-BSRs are configured by C-BSR. [ priority ] ] default. Optional. Configure a legal BSR bsr-policy acl6-number No restrictions on BSR address address range. range by default.
Page 340 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, during which no BSR election takes place.
Page 341: Configuring Ipv6 Administrative Scoping
To do… Use the command… Remarks Enter system view. system-view — Enter IPv6 PIM view. pim ipv6 — Required. Disable the BSM semantic undo bsm-fragment enable By default, the BSM semantic fragmentation function. fragmentation function is enabled. 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.
Page 342: Configuring Ipv6 Pim-Ssm
Configuring C-BSRs for each admin-scope zone In a network with administrative scoping enabled, group-range-specific BSRs are elected from C-BSRs. C-RPs in the network send advertisement messages to the specific BSR. The BSR summarizes the advertisement messages to form an RP-set and advertises it to all routers in the specific admin-scope zone. All the routers use the same hash algorithm to get the RP address corresponding to the specific multicast group.
Page 343: Configuring The Ipv6 Ssm Group Range
To do... Use the command... Remarks Enter system view. system-view — Required. Enable IPv6 multicast routing. multicast ipv6 routing-enable Disable by default. interface interface-type Enter interface view. — interface-number Required. Enable IPv6 PIM-SM. pim ipv6 sm Disabled by default. For more information about the multicast ipv6 routing-enable command, see IP Multicast Command Reference.
Page 344: Configuring An Ipv6 Multicast Data Filter
Determine the IPv6 ACL rule for filtering IPv6 multicast data • Determine the IPv6 ACL rule defining a legal source address range for hello messages • Determine the priority for DR election (global value/interface level value) • Determine the IPv6 PIM neighbor timeout time (global value/interface value) •...
Page 345: Configuring Ipv6 Pim Hello Options
To do… Use the command… Remarks interface interface-type Enter interface view. — interface-number Required. Configure a hello message pim ipv6 neighbor-policy filter. acl6-number No hello message filter by default. With the hello message filter configured, if hello messages of an existing IPv6 PIM neighbor fail to pass the filter, the IPv6 PIM neighbor will be removed automatically when it times out.
Page 346: Configuring The Prune Delay
To do... Use the command... Remarks Optional. Configure the priority for DR hello-option dr-priority priority election. 1 by default. Optional. Configure IPv6 PIM neighbor hello-option holdtime interval timeout time. 105 seconds by default. Optional. Configure the prune message hello-option lan-delay interval delay time (LAN-delay).
Page 347: Configuring Ipv6 Pim Common Timers
To do... Use the command... Remarks Optional. Configure the prune delay prune delay interval interval. 3 seconds by default. Configuring IPv6 PIM common timers IPv6 PIM routers discover IPv6 PIM neighbors and maintain IPv6 PIM neighboring relationships with other routers by periodically sending hello messages. After receiving a hello message, an IPv6 PIM router waits a random period, which is smaller than the maximum delay between hello messages, before sending a hello message.
Page 348: Configuring Join/Prune Message Sizes
To do... Use the command... Remarks interface interface-type Enter interface view. — interface-number Optional. Configure the hello interval. pim ipv6 timer hello interval 30 seconds by default. Optional. Configure the maximum delay pim ipv6 triggered-hello-delay between hello messages. interval 5 seconds by default. Optional.
Page 349: Ipv6 Pim Configuration Examples
To do... Use the command... Remarks display pim ipv6 control-message counters [ message-type { probe | register | register-stop } | View the number of IPv6 PIM [ interface interface-type interface-number | Available in control messages. message-type { assert | bsr | crp | graft | graft-ack any view.
Page 350 Router D connects to the network that comprises the IPv6 multicast source (Source) through • GigabitEthernet 1/0/1. Router A connects to N1 through GigabitEthernet 1/0/1, and to Router D through Serial 2/0/0. • Router B and Router C connect to N2 through their respective GigabitEthernet 1/0/1, and to Router •...
Page 351 <RouterA> system-view [RouterA] multicast ipv6 routing-enable [RouterA] interface GigabitEthernet 1/0/1 [RouterA-GigabitEthernet1/0/1] mld enable [RouterA-GigabitEthernet1/0/1] pim ipv6 dm [RouterA-GigabitEthernet1/0/1] quit [RouterA] interface Serial 2/0/0 [RouterA-Serial2/0/0] pim ipv6 dm [RouterA-Serial2/0/0] quit The configuration on Router B and Router C is similar to that on Router A. # On Router D, enable IPv6 multicast routing and enable IPv6 PIM-DM on each interface.
Page 352 1002::1 Ser2/0/0 00:04:00 00:01:29 1 2002::1 Pos5/0/0 00:04:16 00:01:29 3 3001::1 Pos5/0/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.
Page 353: Ipv6 Pim-Sm Non-Scoped Zone Configuration Example
Protocol: pim-dm, UpTime: 00:02:19, Expires: never 2: Pos5/0/0 Protocol: pim-dm, UpTime: 00:02:19, Expires: never 3: Pos5/0/1 Protocol: pim-dm, UpTime: 00:02:19, Expires: never IPv6 PIM-SM non-scoped zone configuration example Network requirements Receivers receive VOD information through multicast. The receiver groups of different organizations •...
Page 354 Figure 99 Network diagram for IPv6 PIM-SM non-scoped zone configuration Device Interface IPv6 address Device Interface IPv6 address Router A GE1/0/1 1001::1/64 Router D GE1/0/1 4001::1/64 S2/0/0 1002::1/64 S2/0/0 1002::2/64 POS5/0/0 1003::1/64 POS5/0/0 4002::1/64 Router B GE1/0/1 2001::1/64 Router E POS5/0/0 3001::2/64 POS5/0/0...
Page 355 [RouterA-GigabitEthernet1/0/1] pim ipv6 sm [RouterA-GigabitEthernet1/0/1] quit [RouterA] interface Serial 2/0/0 [RouterA-Serial2/0/0] pim ipv6 sm [RouterA-Serial2/0/0] quit [RouterA] interface pos 5/0/0 [RouterA-Pos5/0/0] pim ipv6 sm [RouterA-Pos5/0/0] quit The configuration on Router B and Router C is similar to that on Router A. The configuration on Router D and Router E is also similar to that on Router A except that it is not necessary to enable MLD on the corresponding interfaces on these two routers.
Page 356 [RouterA] display pim ipv6 bsr-info Elected BSR Address: 1003::2 Priority: 20 Hash mask length: 128 State: Accept Preferred Uptime: 00:04:22 Expires: 00:01:46 # View the BSR information and the locally configured C-RP information in effect on Router D. [RouterD] display pim ipv6 bsr-info Elected BSR Address: 1003::2 Priority: 20 Hash mask length: 128...
Page 357 prefix/prefix length: FF0E::101/64 RP: 4002::1 Priority: 192 HoldTime: 130 Uptime: 00:05:19 Expires: 00:02:11 RP: 1003::2 Priority: 192 HoldTime: 130 Uptime: 00:05:19 Expires: 00:02:11 Assume that Host A needs to receive information addressed to IPv6 multicast group G (FF0E::100). The RP corresponding to the multicast group G is Router E as result of hash calculation, so an RPT will be built between Router A and Router E.
Page 358: Ipv6 Pim-Sm Admin-Scope Zone Configuration Example
# View the IPv6 PIM multicast routing table information on Router D. [RouterD] display pim ipv6 routing-table Total 0 (*, G) entry; 1 (S, G) entry (4001::100, FF0E::100) RP: 1003::2 Protocol: pim-sm, Flag: SPT LOC ACT UpTime: 00:14:44 Upstream interface: GigabitEthernet1/0/1 Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information:...
Page 359 MLDv1 is required between Router A, Router E, Router I and their respective receivers. • Network diagram Figure 100 Network diagram for IPv6 PIM-SM admin-scope zone configuration Device Interface IPv6 address Device Interface IPv6 address Router A GE1/0/1 1001::1/64 Router D S2/0/1 3002::2/64 S2/0/1...
Page 360 Procedure Configure IPv6 addresses and unicast routing Configure the IPv6 address and prefix length for each interface as per Figure 100. The detailed configuration steps are omitted here. Configure OSPFv3 on the routers in the IPv6 PIM-SM domain to ensure network-layer reachability among them.
Page 361 [RouterB] interface pos 5/0/1 [RouterB-Pos5/0/1] multicast ipv6 boundary scope 4 [RouterB-Pos5/0/1] quit [RouterB] interface pos 5/0/2 [RouterB-Pos5/0/2] multicast ipv6 boundary scope 4 [RouterB-Pos5/0/2] quit # On Router C, configure POS 5/0/1 and POS 5/0/2 as the boundary of IPv6 admin-scope zone 2. <RouterC>...
Page 362 [RouterB] display pim ipv6 bsr-info Elected BSR Address: 8001::1 Priority: 64 Hash mask length: 126 State: Accept Preferred Scope: 14 Uptime: 00:01:45 Expires: 00:01:25 Elected BSR Address: 1002::2 Priority: 64 Hash mask length: 126 State: Elected Scope: 4 Uptime: 00:04:54 Next BSR message scheduled at: 00:00:06 Candidate BSR Address: 1002::2 Priority: 64...
Page 363 Candidate RP: 3002::2(Serial2/0/1) Priority: 192 HoldTime: 130 Advertisement Interval: 60 Next advertisement scheduled at: 00:00:10 # View the BSR information and the locally configured C-RP information on Router F. [RouterF] display pim ipv6 bsr-info Elected BSR Address: 8001::1 Priority: 64 Hash mask length: 126 State: Elected Scope: 14...
Page 364 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF3E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF4E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF5E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF6E::/16 RP: 8001::1...
Page 365 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFAE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFBE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFCE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFDE::/16...
Page 366 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF14::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF24::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF34::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51...
Page 367 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF84::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF94::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFA4::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39...
Page 368 prefix/prefix length: FFE4::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFF4::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 # View the RP information on Router F. [RouterF] display pim rp-info PIM-SM BSR RP information: prefix/prefix length: FF0E::/16 RP: 8001::1 Priority: 192...
Page 369 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...
Page 370: Ipv6 Bidir-Pim Configuration Example
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...
Page 371 Figure 101 Network diagram for IPv6 BIDIR-PIM configuration Device Interface IPv6 address Device Interface IPv6 address Router A GE1/0/1 1001::1/64 Router D GE1/0/1 4001::1/64 S2/0/1 1002::1/64 GE1/0/2 5001::1/64 Router B GE1/0/1 2001::1/64 S2/0/1 3001::2/64 S2/0/1 1002::2/64 Source 1 1001::2/64 S2/0/2 2002::1/64 Source 2 5001::2/64...
Page 372 [RouterA-pim6] bidir-pim enable [RouterA-pim6] quit # On Router B, enable IPv6 multicast routing, enable IPv6 PIM-SM on each interface, enable MLD on interface GigabitEthernet 1/0/1, and enable IPv6 BIDIR-PIM. <RouterB> system-view [RouterB] multicast ipv6routing-enable [RouterB] interface GigabitEthernet 1/0/1 [RouterB-GigabitEthernet1/0/1] mld enable [RouterB-GigabitEthernet1/0/1] pim ipv6 sm [RouterB-GigabitEthernet1/0/1] quit [RouterB] interface Serial 2/0/1...
Page 373 [RouterD-Serial2/0/1] quit [RouterD] pim ipv6 [RouterD-pim6] bidir-pim enable [RouterD-pim6] quit Configure C-BSR and C-RP # On Router C, configure Serial 2/0/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 Verify the configuration...
Page 374 FE71:2802 (local) Ser2/0/2 Lose 01:21:40 FE80::20F:E2FF: FE15:5602 To view the DF information of the IPv6 multicast forwarding table on a router, use display multicast ipv6 forwarding-table df-info. For more information about this command, see IP Multicast Command Reference. # View the DF information of the IPv6 multicast forwarding table on Router A. [RouterA] display multicast ipv6 forwarding-table df-info Multicast DF information Total 1 RP...
Page 375: Ipv6 Pim-Ssm Configuration Example
# View the DF information of the IPv6 multicast forwarding table on Router D. [RouterD] 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:05:12 RPF interface: Serial2/0/1 List of 2 DF interfaces: 1: GigabitEthernet1/0/1...
Page 376 Figure 102 Network diagram for IPv6 PIM-SSM configuration Device Interface IPv6 address Device Interface IPv6 address Router A GE1/0/1 1001::1/64 Router D GE1/0/1 4001::1/64 S2/0/0 1002::1/64 S2/0/0 1002::2/64 POS5/0/0 1003::1/64 POS5/0/0 4002::1/64 Router B GE1/0/1 2001::1/64 Router E POS5/0/0 3001::2/64 POS5/0/0 2002::1/64 POS5/0/1...
Page 377 [RouterA-GigabitEthernet1/0/1] mld version 2 [RouterA-GigabitEthernet1/0/1] pim ipv6 sm [RouterA-GigabitEthernet1/0/1] quit [RouterA] interface Serial 2/0/0 [RouterA-Serial2/0/0] pim ipv6 sm [RouterA-Serial2/0/0] quit [RouterA] interface pos 5/0/0 [RouterA-Pos5/0/0] pim ipv6 sm [RouterA-Pos5/0/0] quit The configuration on Router B and Router C is similar to that on Router A. The configuration on Router D and Router E is also similar to that on Router A except that it is not necessary to enable MLD on the corresponding interfaces on these two routers.
Page 378: Troubleshooting Ipv6 Pim Configuration
RPF prime neighbor: 1002::2 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet1/0/1 Protocol: mld, UpTime: 00:00:11, Expires: 00:03:25 The information on Router B and Router C is similar to that on Router A. # View the IPv6 PIM multicast routing table information on Router D. [RouterD] display pim ipv6 routing-table Total 0 (*, G) entry;...
Page 379: Rps Unable To Join Spt In Ipv6 Pim-Sm
Check that the RPF neighbor is an IPv6 PIM neighbor. Use display pim ipv6 neighbor to view the PIM neighbor information. Check that IPv6 PIM and MLD are enabled on the interfaces directly connecting to the IPv6 multicast source and to the receiver. Check that the same IPv6 PIM mode is enabled on related interfaces.
Page 380 The RP is the core of an IPv6 PIM-SM domain. Make sure that the RP information on all routers is • exactly the same, a specific group is mapped to the same RP, and a unicast route is available to the Solution Check whether routes to C-RPs, the RP and the BSR are available.
Page 381: Configuring Ipv6 Mbgp Configuration
Configuring IPv6 MBGP configuration This chapter describes only configuration for IPv6 MBGP. For IPv6 BGP related information, see Layer 3—IP Routing Configuration Guide. BGP-4 can carry routing information for IPv4 only. IETF defined multi-protocol BGP extensions to carry routing information for multiple network layer protocols. On an IPv6 network, the IPv6 multicast topology must be different from the IPv6 unicast topology.
Page 382: Configuring A Preferred Value For Routes From A Peer/Peer Group
To do… Use the command… Remarks Required. Enable the IPv6 MBGP peer. peer ipv6-address enable Not enabled by default. Configuring a preferred value for routes from a peer/peer group To do… Use the command… Remarks Enter system view. system-view — Enter BGP view.
Page 383: Configuring Ipv6 Mbgp Route Redistribution
Configuring IPv6 MBGP route redistribution To do… Use the command… Description Enter system view. system-view — Enter BGP view. bgp as-number — Enter IPv6 MBGP multicast ipv6-family multicast — address family view. Optional. Enable default route redistribution into the IPv6 default-route imported By default, default route MBGP routing table.
Page 384: Configuring Outbound Ipv6 Mbgp Route Filtering
Configuring outbound IPv6 MBGP route filtering To do… Use the command… Remarks Enter system view. system-view — Enter BGP view. bgp as-number — Enter IPv6 MBGP address ipv6-family multicast — family view. filter-policy { acl6-number | Use any of the commands. Configure the filtering of ipv6-prefix ipv6-prefix-name } No filtering is configured by...
Page 385: Configuring Ipv6 Mbgp Route Dampening
To do… Use the command… Remarks • filter-policy import Specify an AS path ACL to peer { ipv6-group-name | filter IPv6 BGP routing • peer filter-policy import ipv6-address } as-path-acl information from a peer/peer • peer as-path-acl import as-path-acl-number import group.
Page 386: Configuring Ipv6 Mbgp Route Preferences
Configuring IPv6 MBGP route preferences To do… Use the command… Remarks Enter system view. system-view — Enter BGP view. bgp as-number — Enter IPv6 MBGP address ipv6-family multicast — family view. Optional. preference { external-preference Configure preferences for The default preference values of internal-preference external, internal, local IPv6 external, internal and local routes...
Page 387: Configuring The Next_Hop Attribute
Configuring the NEXT_HOP attribute You can use the peer next-hop-local command to specify the local router as the next hop of routes sent to an IPv6 multicast iBGP peer/peer group. If load balancing is configured, the router specifies itself as the next hop of routes sent to the IPv6 multicast iBGP peer/peer group regardless of whether the peer next-hop-local command is configured.
Page 388: Tuning And Optimizing Ipv6 Mbgp Networks
Tuning and optimizing IPv6 MBGP networks Prerequisites Before tuning and optimizing an OSPF network, complete the following tasks: • Enable IPv6 • Configure the IPv6 MBGP basic functions Configuring IPv6 MBGP soft reset After modifying a route selection policy, you have to reset IPv6 MBGP connections to make the new one take effect.
Page 389: Enabling The Ipv6 Mbgp Orf Capability
To do… Use the command… Remarks Enter IPv6 MBGP address ipv6-family multicast — family view. Keep all routes from a Required. peer/peer group regardless peer { ipv6-group-name | of whether they pass the ipv6-address } keep-all-routes Not kept by default. inbound filtering policy.
Page 390: Configuring The Maximum Number Of Equal-Cost Routes For Load-Balancing
Table 15 Description of the both, send, and receive parameters and the negotiation result Local parameter Peer parameter Negotiation result receive The ORF sending capability is enabled locally and send the ORF receiving capability is enabled on the both peer. The ORF receiving capability is enabled locally send receive...
Page 391: Configuring Ipv6 Mbgp Community
To do… Use the command… Remarks peer ipv6-address group Required. Add a peer to the peer group. ipv6-group-name [ as-number By default, no peer is added. as-number ] Enter IPv6 MBGP address ipv6-family multicast — family view. Enable the configured IPv6 unicast BGP peer group to peer ipv6-group-name enable Required...
Page 392: Configuring An Ipv6 Mbgp Route Reflector
Configuring an IPv6 MBGP route reflector To guarantee connectivity between IPv6 multicast iBGP peers, you need to make them fully meshed, but it becomes unpractical when too many IPv6 multicast iBGP peers exist. Using route reflectors can solve the problem. To do…...
Page 393: Resetting Ipv6 Mbgp Connections
To do… Use the command… Remarks Display IPv6 MBGP routing display bgp ipv6 multicast routing-table as-path-acl Available in information matching a AS path as-path-acl-number [ | { begin | exclude | include } any view. ACL. regular-expression ] display bgp ipv6 multicast routing-table community Display IPv6 MBGP routing [ aa:nn<1-13>...
Page 394: Clearing Ipv6 Mbgp Information
To do… Use the command… Remarks reset bgp ipv6 multicast Reset specified IPv6 MBGP { as-number | ipv6-address | all | Available in user view connections group ipv6-group-name | external | internal } Clearing IPv6 MBGP information To do… Use the command… Remarks Clear dampened IPv6 MBGP reset bgp ipv6 multicast...
Page 395 Router A GE1/0/1 1002::1/64 S2/0/0 3001::1/64 POS5/0/0 1001::1/64 S2/0/1 2001::2/64 Router B POS5/0/0 1001::2/64 Router D S2/0/0 2002::2/64 S2/0/0 2001::1/64 S2/0/1 3001::2/64 S2/0/1 2002::1/64 Procedure Configure IPv6 addresses for router interfaces as shown in Figure 103. Detailed configuration steps are omitted here. Configure OSPFv3.
Page 396 Configure the position of C-BSR and C-RP. # Configure the position of C-BSR and C-RP on Router A. [RouterA] pim ipv6 [RouterA-pim6] c-bsr 1001::1 [RouterA-pim6] c-rp 1001::1 [RouterA-pim6] quit # Configure the position of C-BSR and C-RP on Router B. [RouterB] pim ipv6 [RouterB-pim6] c-bsr 1001::2 [RouterB-pim6] c-rp 1001::2...
Page 397 Peer MsgRcvd MsgSent OutQ PrefRcv Up/Down State 1001::1 0 00:40:54 Established...
Page 398: Support And Other Resources
Related information Documents To find related documents, browse to the Manuals page of the HP Business Support Center website: http://www.hp.com/support/manuals For related documentation, navigate to the Networking section, and select a networking category. •...
Page 399: Conventions
Conventions This section describes the conventions used in this documentation set. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown. Italic Italic text represents arguments that you replace with actual values. Square brackets enclose syntax choices (keywords or arguments) that are optional. Braces enclose a set of required syntax choices separated by vertical bars, from which { x | y | ...
Page 400 Network topology icons Represents a generic network device, such as a router, switch, or firewall. Represents a routing-capable device, such as a router or Layer 3 switch. Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features.
Page 401: Index
Index 802.1p AS_PATH attribute (MBGP), 201 configuring message precedence (IGMP snooping), ASM model (multicast), 5 assert (IPv6 PIM-DM), 299 address assert (IPv6 PIM-SM), 305 multicast, 6 assert (PIM-DM), 94 adjusting assert (PIM-SM), 100 performance (IGMP), 73 attribute adjusting MLD performance configuring AS_PATH (MBGP), 201 configuration prerequisites, 280 configuring AS_PATH attribute (IPv6 MBGP), 376...
Page 402 BSR, configuring C-BSR, admin-scope zone disabling semantic fragmentation, BIDIR-PIM, 126 boundary, 127 BSM sematic fragmentation BSR, configuring C-BSR, admin-scope zone disabling in IPv6 BIDIR-PIM, 329 boundary, 127 BSR, configuring C-BSR, global-scope zone, 127 configuring administrative scoping, BIDIR-PIM, 126 BSR, disabling semantic fragmentation, 126 configuring admin-scope zone boundary, BSR, enabling administrative scoping, 126 BIDIR-PIM, 126...
Page 403 clearing information (MGBP), 207 forwarding table size (multicast), 52 community group policy (IGMP snooping), 32 configuring (IPv6 MBGP), 380 IGMP, 64, 82 configuring (MBGP), 205 IGMP snooping, 32 inbound route filtering (MBGP), 197 concept MD-VPN basics, 214 inter-AS multicast leveraging BGP route (MSDP), multi-instance (multicast), 11 inter-AS multicast leveraging static RPF peer principle (IGMP snooping), 13...
Page 404 PIM-SSM, 156 static multicast MAC address entry (IGMP snooping), 53 policy (IGMP snooping), 26 static port (IGMP snooping), 20, 34 proxy message source IP address (IGMP snooping), static route (multicast), 50 proxying (IGMP snooping), 25, 40 static RPF peer (MSDP), 170 proxying (IGMP), 79, 88 version (IGMP snooping), 18 querier, 23...
Page 405 C-BSR (IPv6 PIM-SM), 318 configuring configuring IPv6 BIDIR-PIM, 359 domain border (IPv6 PIM-SM), 318 configuring configuring IPv6 PIM-SSM, 364 configuring C-BSR parameter globally (IPv6 PIM-SM), 319 configuring IPv6 MBGP, 370 C-BSR timer (IPv6 PIM-SM), 319 configuring configuring basic function (IPv6 MBGP), 370 administrative scoping (IPv6 PIM-SM), 320 configuring configuring...
Page 406 PIM-DM, 108 configuring connection soft reset through route refresh (IPv6 MBGP), 377 resetting (IPv6 MBGP), 382 configuring contacting HP, 387 controlling soft reset manually (IPv6 MBGP), 377 configuring route advertisement (MBGP), 195 route distribution (IPv6 MBGP), 371 max number load-balancing equal-cost routes (IPv6...
Page 407 MLD configuration, 287 querier (IGMP snooping), 23 MSDP, 175 SSM mapping (IGMP), 79 multicast forwarding, 54 enabling multicast routing, 54 IPv6 PIM-DM, 313 enabling multicast VPN, 233 PIM, 135 state-refresh capability (IPv6 PIM-DM), 313 documentation enabling conventions used, 388 IPv6 PIM-SM, 315 website, 387 enabling Domain border configuration...
Page 408 configuring basic (IGMP), 70 websites, 387 configuring basic (IPv6 MBGP), 370 icons, 388 configuring basic (MLD), 288 IGMP configuring peer (IPv6 MBGP), 370 adjusting performance, 73 configuration, 64, 82 configuring preferred route value (IPv6 MBGP), configuring basic function, 70, 82 controlling route distribution (IPv6 MBGP), 371 configuring forwarding on downstream interface, controlling route reception (IPv6 MBGP), 371...
Page 409 IGMP snooping process, 15 configuration, 32 protocols and standards, 17 configuring 802.1p message precedence, 30 proxying, 16 configuring aging timer for dynamic port, 19 receiving general query, configuring basic function, 18 receiving leave message, 16 configuring drop unknown multicast data, 28 receiving membership report, 15 configuring fast leave processing, 22, 77 troubleshooting, 42...
Page 410 unicast, 1 neighbor discovery, 306 inter-AS understanding, 305 configuring multicast leveraging BGP route (MSDP), IPv6 BIDIR-PIM administrative scoping, 308 configuring multicast leveraging static RPF peer IPv6 BIDIR-PIM (MSDP), 180 domain division, 308 interface IPv6 BIDIR-PIM configuring max number groups (IGMP), 73 configuring RP, 325 introduction IPv6 BIDIR-PIM...
Page 411 configuration, 359 tuning network, 377 IPv6 MBGP IPv6 multicast advertising default route to peer/peer group, 372 implementing RPF check mechanism, 263 clearing information, 383 RPF check mechanism, 262 IPv6 multicast routing and forwarding configuration, 370, 383 configuring AS_PATH attribute, 376 configuration, 262 configuring basic function, 370 configuring IPv6 multicast routing and forwarding,...
Page 412 enabling, 313 RP discovery, 301 enabling state-refresh capability, 313 RPT establishment, 303 establishing SPT, 298 switchover to SPT, 304 graft, 299 understanding, 300 IPv6 PIM-SSM neighbor discovery, 298 understanding, 297 building SPT, 311 IPv6 PIM-SM configuration, 364 administrative scoping, 308 configuring common feature, 332 assert, 305 configuring group range, 331...
Page 413 IPv6-MAC (multicast), 9 configuring route attribute, 199 maintaining configuring route dampening, 198 IGMP, 81 configuring route preference, 199 IGMP snooping, 31 configuring route redistribution, 195 configuring route reflector, 205 IPv6 MBGP, 381 IPv6 PIM, 337 configuring route summarization, 196 configuring soft reset, 201 MBGP, 206 MLD configuration, 287 configuring soft reset through route-refresh, 202...
Page 414 MD-VPN configuring option (IGMP), 74 basic concept, 214 configuring proxy message source IP address (IGMP snooping), 26 configuration, 228 configuring SA content (MSDP), 172 configuring MTI binding, 229 configuring SA filtering rule (MSDP), 173 configuring multi-AS, 246 configuring SA message filtering (MSDP), 188 configuring share group, 229 configuring SA parameter (MSDP), 172 configuring single-AS, 233...
Page 415 configuration, 163, 175 (*,G), 4 configuring Anycast RP, 184 (S,G), 4 configuring basic function, 168 address, 6 configuring inter-AS multicast leveraging BGP route, advantage, 4 application, 4 configuring inter-AS multicast leveraging static RPF architecture, 5 peer, 180 ASM model, 5 configuring mesh group, 171 configuring group filter (IGMP snooping), 26 configuring peer connection, 170...
Page 416 SSM model, 5 multicastcast VLAN (Layer 2), 11 information transmission technique, 2 multicast routing and forwarding multi-instance IGMP changing RPF route, 46, 55 protocols and standards, 70 multiprotocol BGP. See MBGP configuring forwarding range (multicast), 51 configuring forwarding table size (multicast), 52 neighbor discovery configuring routing policy (multicast), 50 BIDIR-PIM, 101...
Page 417 non-scoped zone configuration (IPv6 PIM-SM), 342, configuring connection control (MSDP), 171 configuring description (MSDP), 170 non-scoped zone configuration (PIM-SM), 140 configuring IPv4 group (MBGP), 204 optimizing network (IPv6 MBGP), 377 configuring preferred route value (IPv6 MBGP), PIM-DM configuration, 136 proxying configuration (IGMP snooping), 40 configuring static RPF (MSDP), 170 proxying configuration (IGMP), 88 creating connection (MSDP), 169...
Page 418 configuring C-BSR, 113 troubleshooting, 159 configuring C-BSR for admin-scope and global-scope zones, 117 PIM configuration configuring C-BSR parameter, 115 configuring PIM-DM, 107 configuring C-BSR timer, 115 protocols and standards, 107 configuring C-RP timer globally, 113 PIM-DM configuring multicast source registration, 118 assert, 94 disabling BSM semantic fragmentation, 116 configuration, 136...
Page 419 enabling PIM-SM globally, public network, 128 clearing information (MGBP), 207 enabling PIM-SM in VPN, 129 configuring 802.1p message precedence globally (IGMP snooping), 30 PIM-SSM configuring 802.1p message precedence in VLAN DR election, 105 (IGMP snooping), 30 model understanding, 105 configuring a BSR (PIM-SM), 113 neighbor discovery, 105 configuring a BSR in IPv6 BIDIR-PIM, 327 protocol relationships, 106...
Page 420 configuring basic function (MLD), 289 configuring forwarding range (multicast), 51 configuring BSR (IPv6 PIM-SM), 317 configuring forwarding table size in VPN instance (multicast), 52 configuring C-BSR (IPv6 PIM-SM), 318 configuring global C-BSR parameters in IPv6 configuring C-BSR (PIM-SM), 113 BIDIR-PIM, 328 configuring C-BSR for admin-scope and configuring graft retry period (IPv6 PIM-DM), 314 global-scope zones (PIM-SM), 117...
Page 421 configuring max number multicast groups joined configuring peer connection (MSDP), 170 on port (IGMP snooping), 29 configuring peer connection control (MSDP), 171 configuring maximum forwarding entries (IGMP configuring peer description (MSDP), 170 snooping), 19 configuring peer group (IPv6 MBGP), 379 configuring MBGP, 209 configuring PIM common timer (PIM-SSM), 133 configuring MED attribute (IPv6 MBGP), 375...
Page 422 configuring route attribute (IPv6 MBGP), 374 configuring state-refresh parameter (PIM-DM), 109 configuring route attribute (MBGP), 199 configuring static joining (IGMP), 72 configuring route dampening (IPv6 MBGP), 374 configuring static multicast MAC address entry in interface view (IGMP snooping), 53 configuring route dampening (MBGP), 198 configuring static multicast MAC address entry in configuring route preference (IPv6 MBGP), 375 system view (IGMP snooping), 53...
Page 423 enabling IP routing for public network (multicast), processing configuring fast leave (IGMP snooping), 22, 77 enabling IP routing in VPN instance (multicast), 49 configuring fast leave (MLD), 284 enabling IPv6 PIM-DM, 313 protocol enabling IPv6 PIM-SM, 315, 331 IGMP snooping, 17 enabling MSDP globally in public network, 169 IPv6 PIM, 312 enabling MSDP globally in VPN instance, 169...
Page 424 enabling querier (IGMP snooping), 23 configuring MED attribute (MBGP), 199 querier election mechanism (IGMPv2), 66 configuring NEXT_HOP attribute (IPv6 MBGP), query capability (IGMPv3), 67 configuring NEXT_HOP attribute (MBGP), 200 receiving general query (IGMP snooping), 15 configuring outbound route filtering (IPv6 MBGP), receiving leave message (IGMP snooping), 16 receiver-side PE configuration configuring outbound route filtering (MBGP), 197...
Page 425 traceroute (multicast), 48 SPT establishment (IPv6 PIM-DM), 298 configuring for BIDIR-PIM, 121 configuring mapping (MLD), 286, 291 configuring, auto-RP for BIDIR-PIM, 122 enabling mapping (MLD), 286 mapping (IGMP), 68 configuring, C-RP for BIDIR-PIM, 122 configuring, C-RP timers for BIDIR-PIM, global, 122 SSM model (multicast), 5 configuring, static RP for BIDIR-PIM, 121 static joining (IGMP), 72...
Page 426 RPs unable to join SPT in PIM-SM, 161 tuning RPT establishment failure or source registration network (IPv6 MBGP), 377 failure in PIM-SM, 161 network (MBGP), 201 troubleshooting understanding unable to build MVRF (MD-VPN), 260 MSDP, 163 troubleshooting unicast no member information on the receiver-side router information transmission technique, 1 (MLD), 295 user...

HP A6600 Configuration Manual

Configuring IP Multicast

Configuring IGMP Snooping

Configuring Multicast Routing and Forwarding

Configuring IGMP

Configuring PIM

Configuring MSDP

Configuring MBGP

Configuring Multicast VPN

Configuring Ipv6 Multicast Routing and Forwarding

Quick Links

Configuration Guide

Troubleshooting

Related Manuals for HP A6600

Summary of Contents for HP A6600