Page 1 HPE VSR1000 Virtual Services Router IP Multicast Configuration Guide Part number: 5200-3152 Software version: VSR1000_HPE-CMW710-E0518-X64 Document version: 5W100-20170314...
Page 2 © Copyright 2017 Hewlett Packard Enterprise Development LP The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Page 3: Table Of Contents
Contents Multicast overview ··························································································· 1 Introduction to multicast ····································································································································· 1 Information transmission techniques ·········································································································· 1 Multicast features ······································································································································· 3 Common notations in multicast ·················································································································· 4 Multicast benefits and applications ············································································································ 4 Multicast models ················································································································································ 4 ...
Page 4 Configuration prerequisites ······················································································································ 47 Configuration procedure ··························································································································· 47 Configuring IGMP proxying ······························································································································ 47 Configuration prerequisites ······················································································································ 47 Enabling IGMP proxying ·························································································································· 48 Enabling multicast forwarding on a non-querier interface ········································································ 48 Configuring multicast load splitting on an IGMP proxy ············································································· 49 ...
Page 5 Configuration task list ····························································································································· 105 Configuration prerequisites ···················································································································· 105 Configuring a multicast source policy ····································································································· 106 Configuring a PIM hello policy ················································································································ 106 Configuring PIM hello message options ································································································· 106 Configuring common PIM timers ············································································································ 108 ...
Page 6 IPv6 multicast forwarding across IPv6 unicast subnets ········································································· 215 Configuration task list ····································································································································· 215 Enabling IPv6 multicast routing ······················································································································ 215 Configuring IPv6 multicast routing and forwarding ························································································ 216 Specifying the longest prefix match principle ························································································· 216 ...
Page 7 IPv6 administrative scoping overview ···································································································· 278 IPv6 PIM-SSM overview ························································································································ 280 Relationship among IPv6 PIM protocols ································································································ 281 IPv6 PIM support for VPNs ···················································································································· 282 Protocols and standards ························································································································ 282 Configuring IPv6 PIM-DM ······························································································································ 282 ...
Page 8 Accessing updates ········································································································································· 328 Websites ················································································································································ 329 Customer self repair ······························································································································· 329 Remote support ······································································································································ 329 Documentation feedback ······················································································································· 329 Index ··········································································································· 331 ...
Page 9: Multicast Overview
Multicast overview Introduction to multicast As a technique that coexists with unicast and broadcast, the multicast technique effectively addresses the issue of point-to-multipoint data transmission. By enabling high-efficiency point-to-multipoint data transmission over a network, multicast greatly saves network bandwidth and reduces network load.
Page 10 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 Figure 2, only Host B, Host D, and Host E need the information. If the information is broadcast to the subnet, Host A and Host C also receive it.
Page 11: Multicast Features
Figure 3 Multicast transmission Figure 3, the multicast source sends only one copy of the information to a multicast group. Host B, Host D, and Host E, which are information receivers, must join the multicast group. The routers on the network duplicate and forward the information based on the distribution of the group members. Finally, the information is correctly delivered to Host B, Host D, and Host E.
Page 12: Common Notations In Multicast
Table 1 Comparing TV program transmission and multicast transmission TV program transmission Multicast transmission A TV station transmits a TV program through a A multicast source sends multicast data to a multicast channel. group. A user tunes the TV set to the channel. A receiver joins the multicast group.
Page 13: Multicast Architecture
ASM model In the ASM model, any multicast sources can send information to a multicast group. Receivers can join a multicast group and get multicast information addressed to that multicast group from any multicast sources. In this model, receivers do not know the positions of the multicast sources in advance.
Page 14 Table 2 Class D IP address blocks and description Address block Description Reserved permanent group addresses. The IP address 224.0.0.0 is reserved. Other IP addresses can be used by routing protocols and for topology searching, protocol 224.0.0.0 to 224.0.0.255 maintenance, and so on. Table 3 lists common permanent group addresses.
Page 15 Figure 4 IPv6 multicast format The following describes the fields of an IPv6 multicast address: 0xFF—The most significant eight bits are 11111111. Flags—The Flags field contains four bits. Figure 5 Flags field format Table 4 Flags field description Description Reserved, set to 0. •...
Page 16 Value Meaning Global scope. Group ID—The Group ID field contains 112 bits. It uniquely identifies an IPv6 multicast group in the scope that the Scope field defines. Ethernet multicast MAC addresses • IPv4 multicast MAC addresses: As defined by IANA, the most significant 24 bits of an IPv4 multicast MAC address are 0x01005E.
Page 17: Multicast Protocols
Multicast protocols Multicast protocols include the following categories: • Layer 3 and Layer 2 multicast protocols: Layer 3 multicast refers to IP multicast operating at the network layer. Layer 3 multicast protocols—IGMP, MLD, PIM, IPv6 PIM, MSDP, MBGP, and IPv6 MBGP.
Page 18 In the ASM model, multicast routes include intra-domain routes and inter-domain routes. An intra-domain multicast routing protocol discovers multicast sources and builds multicast distribution trees within an AS to deliver multicast data to receivers. Among a variety of mature intra-domain multicast routing protocols, PIM is most widely used. Based on the forwarding mechanism, PIM has dense mode (often referred to as PIM-DM) and sparse mode (often referred to as PIM-SM).
Page 19: Multicast Packet Forwarding Mechanism
VLAN on the Layer 2 device. This method avoids waste of network bandwidth and extra burden on the Layer 3 device. Multicast packet forwarding mechanism In a multicast model, receiver hosts of a multicast group are usually located at different areas on the network.
Page 20: Multicast Application In Vpns
Figure 10 VPN networking diagram 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 • The P device belongs to the public network. The CE devices belong to their respective VPNs. Each CE device serves its own VPN and maintains only one set of forwarding mechanisms.
Page 21: Configuring Multicast Routing And Forwarding
Configuring multicast routing and forwarding Overview The following tables are involved in multicast routing and forwarding: • Multicast routing table of each multicast routing protocol, such as the PIM routing table. • General multicast routing table that summarizes multicast routing information generated by different multicast routing protocols.
Page 22 RPF check implementation in multicast Implementing an RPF check on each received multicast packet brings a big burden to the router. The use of a multicast forwarding table is the solution to this issue. When the router creates a multicast forwarding entry for an (S, G) packet, it sets the RPF interface of the packet as the incoming interface of the (S, G) entry.
Page 23: Static Multicast Routes
• If a multicast packet arrives at Router C on GigabitEthernet 1/0/2, the receiving interface is the incoming interface of the (S, G) entry. Router C forwards the packet out of all outgoing interfaces. • If a multicast packet arrives at Router C on GigabitEthernet 1/0/1, the receiving interface is not the incoming interface of the (S, G) entry.
Page 24: Multicast Forwarding Across Unicast Subnets
Figure 13 Creating an RPF route Multicast Routing Table Static on Router C OSPF domain Source/Mask Interface RPF neighbor/Mask 192.168.0.0/24 GE1/0/1 1.1.1.1/24 Receiver Router D Multicast Routing Table Static on Router D GE1/0/1 Source/Mask Interface RPF neighbor/Mask 2.2.2.1/24 192.168.0.0/24 GE1/0/1 2.2.2.2/24 Source RIP domain...
Page 25: Configuration Task List
Figure 14 Multicast data transmission through a tunnel As shown in Figure 14, a tunnel is established between the multicast routers Router A and Router B. Router A encapsulates the multicast data in unicast IP packets, and forwards them to Router B across the tunnel through unicast routers.
Page 26: Configuring Multicast Routing And Forwarding
Configuring multicast routing and forwarding Before you configure multicast routing and forwarding, complete the following tasks: • Configure a unicast routing protocol so that all devices in the domain can interoperate at the network layer. • Enable PIM-DM or PIM-SM. Configuring static multicast routes To configure a static multicast route for a given multicast source, you can specify an RPF interface or an RPF neighbor for the multicast traffic from that source.
Page 27: Configuring Multicast Load Splitting
Configuring multicast load splitting You can enable the device to split multiple data flows on a per-source basis or on a per-source-and-group basis. This optimizes the traffic delivery. To configure multicast load splitting: Step Command Remarks Enter system view. system-view multicast routing [ vpn-instance Enter MRIB view.
Page 28: Displaying And Maintaining Multicast Routing And Forwarding
travel along the SPT will fail the RPF check and be discarded. If the RPT is pruned at this moment, the multicast service is instantaneously interrupted. To avoid this problem, you can configure the router to deliver the packets that travel along the SPT and fail the RPF check to the CPU.
Page 29 Task Command Display statistics for multicast forwarding display multicast [ vpn-instance vpn-instance-name ] events (in standalone mode). forwarding event Display statistics for multicast forwarding display multicast [ vpn-instance vpn-instance-name ] events (in IRF mode). forwarding event [ slot slot-number ] display multicast [ vpn-instance vpn-instance-name ] forwarding-table [ source-address [ mask { mask-length | Display multicast forwarding entries (in...
Page 30: Multicast Routing And Forwarding Configuration Examples
NOTE: • When you clear a multicast routing entry, the associated multicast forwarding entry is also cleared. • When you clear a multicast forwarding entry, the associated multicast routing entry is also cleared. Multicast routing and forwarding configuration examples Changing an RPF route Network requirements As shown in Figure...
Page 31 Enable IP multicast routing, and enable IGMP and PIM-DM: # On Router B, enable IP multicast routing. <RouterB> system-view [RouterB] multicast routing [RouterB-mrib] quit # Enable IGMP on the receiver-side interface (GigabitEthernet 1/0/1). [RouterB] interface gigabitethernet 1/0/1 [RouterB-GigabitEthernet1/0/1] igmp enable [RouterB-GigabitEthernet1/0/1] quit # Enable PIM-DM on the other interfaces.
Page 32: Creating An Rpf Route
[RouterB] display multicast rpf-info 50.1.1.100 RPF information about source 50.1.1.100: RPF interface: GigabitEthernet1/0/2, RPF neighbor: 20.1.1.2 Referenced route/mask: 50.1.1.0/24 Referenced route type: multicast static Route selection rule: preference-preferred Load splitting rule: disable The output shows the following information: • The RPF route on Router B is the configured static multicast route. •...
Page 33 [RouterC-mrib] quit # Enable IGMP on the receiver-side interface (GigabitEthernet 1/0/1). [RouterC] interface gigabitethernet 1/0/1 [RouterC-GigabitEthernet1/0/1] igmp enable [RouterC-GigabitEthernet1/0/1] quit # Enable PIM-DM on GigabitEthernet 1/0/2. [RouterC] interface gigabitethernet 1/0/2 [RouterC-GigabitEthernet1/0/2] pim dm [RouterC-GigabitEthernet1/0/2] quit # On Router A, enable IP multicast routing. <RouterA>...
Page 34: Multicast Forwarding Over A Gre Tunnel
Referenced route type: multicast static Route selection rule: preference-preferred Load splitting rule: disable The output shows that the RPF routes to Source 2 exist on Router B and Router C. These RPF routes are the configured static multicast routes. Multicast forwarding over a GRE tunnel Network requirements As shown in Figure...
Page 35 [RouterC-Tunnel0] ip address 50.1.1.2 24 [RouterC-Tunnel0] source 30.1.1.2 [RouterC-Tunnel0] destination 20.1.1.1 [RouterC-Tunnel0] quit Enable IP multicast routing, PIM-DM, and IGMP: # On Router A, enable IP multicast routing. [RouterA] multicast routing [RouterA-mrib] quit # Enable PIM-DM on each interface. [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] pim dm [RouterA-GigabitEthernet1/0/1] quit [RouterA] interface gigabitethernet 1/0/2...
Page 36: Multicast Forwarding Over Advpn Tunnels
RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet1/0/1 Protocol: igmp, UpTime: 00:04:25, Expires: - (10.1.1.100, 225.1.1.1) Protocol: pim-dm, Flag: ACT UpTime: 00:06:14 Upstream interface: Tunnel0 Upstream neighbor: 50.1.1.1 RPF prime neighbor: 50.1.1.1 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet1/0/1 Protocol: pim-dm, UpTime: 00:04:25, Expires: -...
Page 37 Figure 18 Network diagram Table 6 Interface and IP address assignment Device Interface IP address Device Interface IP address Hub 1 GE1/0/1 100.1.1.1/24 Spoke 1 GE1/0/1 100.1.1.3/24 Hub 1 Tunnel1 192.168.0.1/24 Spoke 1 Tunnel1 192.168.0.3/24 Hub 1 Loop0 1.1.1.1/32 Spoke 1 GE1/0/2 20.1.1.10/24 Hub 1...
Page 38 # Enable the VAM server. [Server-vam-server-domain-abc]server enable # Create hub group 0. [Server-vam-server-domain-abc]hub-group 0 # Specify private IPv4 addresses for hubs in hub group 0. [Server-vam-server-domain-abc-hub-group-0]hub private-address 192.168.0.1 [Server-vam-server-domain-abc-hub-group-0]hub private-address 102.168.0.2 # Specify a private IPv4 address range for spokes in hub group 0. [Server-vam-server-domain-abc-hub-group-0]spoke private-address range 192.168.0.0 192.168.0.255 [Server-vam-server-domain-abc-hub-group-0]quit...
Page 39 # Enable the VAM client. [Spoke1-vam-client-Spoke1]client enable [Spoke1-vam-client-Spoke1]quit e. Configure Spoke 2: # Create a VAM client named Spoke2. <Spoke2>system-view [Spoke2]vam client name Spoke2 # Specify ADVPN domain abc for the VAM client. [Spoke2-vam-client-Spoke2]advpn-domain abc # Specify the VAM server. [Spoke2-vam-client-Spoke2]server primary ip-address 100.1.1.100 # Set the pre-shared key to 123456.
Page 40 <Hub1>system-view [Hub1]ospf [Hub1-ospf-1]area 0.0.0.0 [Hub1-ospf-1-area-0.0.0.0]network 10.1.1.0 0.0.0.255 [Hub1-ospf-1-area-0.0.0.0]network 1.1.1.1 0.0.0.255 [Hub1-ospf-1-area-0.0.0.0]network 192.168.0.0 0.0.0.255 [Hub1-ospf-1-area-0.0.0.0]quit [Hub1-ospf-1]quit # On Hub 2, configure OSPF. <Hub2>system-view [Hub2]ospf [Hub2-ospf-1]area 0.0.0.0 [Hub2-ospf-1-area-0.0.0.0]network 2.2.2.2 0.0.0.255 [Hub2-ospf-1-area-0.0.0.0]network 192.168.0.0 0.0.0.255 [Hub2-ospf-1-area-0.0.0.0]quit [Hub2-ospf-1]quit # On Spoke 1, configure OSPF. <Spoke1>system-view [Spoke1]ospf [Spoke1-ospf-1]area 0.0.0.0 [Spoke1-ospf-1-area-0.0.0.0]network 192.168.0.0 0.0.0.255...
Page 41 [Hub1-Tunnel1]quit # Configure Loopback 0 as a C-BSR and a C-RP. <Hub1>system-view [Hub1]pim [Hub1-pim]c-bsr 1.1.1.1 [Hub1-pim]c-rp 1.1.1.1 [Hub1-pim]quit b. Configure Hub 2: # Enable IP multicast routing. <Hub2>system-view [Hub2]multicast routing [Hub2-mrib] quit # Enable PIM-SM on Loopback 0. [Hub2]interface loopback 0 [Hub2-LoopBack0]pim sm [Hub2-LoopBack0]quit # Enable PIM-SM and NBMA mode on tunnel interface tunnel1.
Page 42: Troubleshooting Multicast Routing And Forwarding
# Enable PIM-SM and NBMA mode on tunnel interface tunnel1. [Spoke2]interface tunnel 1 [Spoke2-Tunnel1]pim sm [Spoke2-Tunnel1]pim nbma-mode [Spoke2-Tunnel1]quit Verifying the configuration # Send an IGMP report from Spoke 1 to join multicast group 225.1.1.1. (Details not shown.) # Send multicast data from the source to the multicast group. (Details not shown.) # Display PIM routing entries on Hub 1.
Page 43 Solution To resolve the problem: Use the display multicast routing-table static command to display information about static multicast routes. Verify that the static multicast route has been correctly configured and that the route entry exists in the static multicast routing table. Check the type of interface that connects the static multicast route to the RPF neighbor.
Page 44: Configuring Igmp
Configuring IGMP Overview Internet Group Management Protocol (IGMP) establishes and maintains the multicast group memberships between a Layer 3 multicast device and the hosts on the directly connected subnet. IGMP has the following versions: • IGMPv1 (defined by RFC 1112). •...
Page 45: Igmpv2 Enhancements
The hosts send unsolicited IGMP reports to the multicast groups they want to join without having to wait for the IGMP queries. The IGMP querier periodically multicasts IGMP queries (with the destination address of 224.0.0.1) to all hosts and routers on the local subnet. After receiving a query message, the host whose report delay timer expires first sends an IGMP report to multicast group G1 to announce its membership for G1.
Page 46: Igmpv3 Enhancements
After receiving the leave message, the querier sends a configurable number of IGMP group-specific queries to the group that the host is leaving. Both the destination address field and the group address field of the message are the address of the multicast group that is being queried.
Page 47: Igmp Ssm Mapping
IGMPv3 is compatible with IGMPv1 and IGMPv2 and supports IGMP general queries and IGMP group-specific queries. It also introduces IGMP group-and-source-specific queries. A general query does not carry a group address or a source address. A group-specific query carries a group address, but no source address. A group-and-source-specific query carries a group address and one or more source addresses.
Page 48: Igmp Proxying
Figure 21 IGMP SSM mapping As shown in Figure 21, on an SSM network, Host A, Host B, and Host C run IGMPv1, IGMPv2, and IGMPv3, respectively. To provide the SSM service for Host A and Host B, you must configure the IGMP SSM mapping feature on Router A.
Page 49: Multicast Access Control
Figure 22 IGMP proxying Proxy Querier Router B Router A PIM domain Ethernet Receiver Receiver Host B Host A Host C Report from Router B Query from Router A Query from Router B Host interface Report from Host Router interface The following types of interfaces are defined in IGMP proxying: •...
Page 50: Protocols And Standards
Protocols and standards • RFC 1112, Host Extensions for IP Multicasting • RFC 2236, Internet Group Management Protocol, Version 2 • RFC 3376, Internet Group Management Protocol, Version 3 IGMP configuration task list Tasks at a glance Configuring basic IGMP features: •...
Page 51: Specifying An Igmp Version
Step Command Remarks Enter system view. system-view Enable IP multicast routing multicast routing [ vpn-instance By default, IP multicast routing is and enter MRIB view. vpn-instance-name ] disabled. Return to system view. quit interface interface-type Enter interface view. interface-number Enable IGMP. By default, IGMP is disabled.
Page 52: Configuring A Multicast Group Policy
Configuring a multicast group policy This feature enables an interface to filter IGMP reports by using an ACL that specifies multicast groups and the optional sources. It is used to control the multicast groups that the hosts attached to an interface can join. This configuration does not take effect on static group members.
Page 53 • IGMP other querier present timer—Lifetime for an IGMP querier after a non-querier receives an IGMP general query. If the non-querier does not receive a new query when this timer expires, the non-querier considers that the querier has failed and starts a new querier election. Configuration restrictions and guidelines When you configure the IGMP query and response parameters, follow these restrictions and guidelines:...
Page 54: Enabling Fast-Leave Processing
Step Command Remarks Set the maximum response By default, the maximum time for IGMP general response time for IGMP general max-response-time time queries. queries is 10 seconds. By default, the IGMP other querier present timer is calculated by using the following formula: 10.
Page 55: Configuring Igmp Ssm Mappings
To enable fast-leave processing: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Enable fast-leave igmp fast-leave [ group-policy By default, fast-leave processing processing. ipv4-acl-number ] is disabled. Configuring IGMP SSM mappings This feature enables the device to provide SSM services for IGMPv1 or IGMPv2 hosts. This feature does not process IGMPv3 messages.
Page 56: Enabling Igmp Proxying
Enabling IGMP proxying When you enable IGMP proxying, follow these restrictions and guidelines: • You must enable IGMP proxying on the receiver-side interfaces. • On an interface enabled with IGMP proxying, only the igmp version command takes effect and other IGMP commands do not take effect. •...
Page 57: Configuring Multicast Load Splitting On An Igmp Proxy
Configuring multicast load splitting on an IGMP proxy This feature enables all proxy interfaces on an IGMP proxy device to share multicast traffic on a per-group basis. To enable multicast load splitting on an IGMP proxy device: Step Command Remarks Enter system view.
Page 58: Configuring An Igmp User Access Policy
Configuring an IGMP user access policy This feature enables the BRAS to filter IGMP reports by using an ACL that specifies the multicast groups in a user profile. Use this feature to control the multicast groups that an IGMP user can join. You can also configure a multicast group list on the RADIUS server to achieve the same purpose.
Page 59: Configuring A Vlan-Based Static Group Member
If the downstream device does not support IGMP snooping, you can configure the downstream interface on the BRAS to forward multicast traffic on a per-session basis. This allows the BRAS to send a separate copy of the multicast data to each receiver. To configure per-session multicast forwarding: Step Command...
Page 60: Displaying And Maintaining Igmp
Displaying and maintaining IGMP CAUTION: The reset igmp group command might cause multicast data transmission failures. Execute display commands in any view and reset commands in user view. Task Command display igmp [ vpn-instance vpn-instance-name ] group Display information about IGMP multicast [ group-address | interface interface-type interface-number ] groups.
Page 61 Figure 23 Network diagram Receiver PIM-DM Host A GE1/0/1 10.110.1.1/24 Router A Host B Querier GE1/0/1 10.110.2.1/24 Receiver Host C Router B GE1/0/1 10.110.2.2/24 Host D Router C Configuration procedure Assign an IP address and subnet mask to each interface, as shown in Figure 23.
Page 62: Igmp Ssm Mapping Configuration Example
[RouterB-GigabitEthernet1/0/2] quit # On Router C, enable IP multicast routing. <RouterC> system-view [RouterC] multicast routing [RouterC-mrib] quit # Enable IGMP on GigabitEthernet 1/0/1. [RouterC] interface gigabitethernet 1/0/1 [RouterC-GigabitEthernet1/0/1] igmp enable [RouterC-GigabitEthernet1/0/1] quit # Enable PIM-DM on GigabitEthernet 1/0/2. [RouterC] interface gigabitethernet 1/0/2 [RouterC-GigabitEthernet1/0/2] pim dm [RouterC-GigabitEthernet1/0/2] quit Configure a multicast group policy on Router A so that the hosts connected to GigabitEthernet...
Page 63 Configure the IGMP SSM mapping feature on Router D so that the receiver host can receive multicast data only from Source 1 and Source 3. Figure 24 Network diagram Source 2 Source 3 Router B Router C GE1/0/1 GE1/0/3 GE1/0/3 GE1/0/1 GE1/0/2 GE1/0/2...
Page 64 [RouterD] interface gigabitethernet 1/0/3 [RouterD-GigabitEthernet1/0/3] pim sm [RouterD-GigabitEthernet1/0/3] quit # On Router A, enable IP multicast routing. <RouterA> system-view [RouterA] multicast routing [RouterA-mrib] quit # Enable PIM-SM on each interface. [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...
Page 65: Igmp Proxying Configuration Example
# Display information about IGMP multicast groups that hosts have dynamically joined on the public network. [RouterD] display igmp group IGMP groups in total: 1 GigabitEthernet1/0/1(133.133.4.2): IGMP groups reported in total: 1 Group address Last reporter Uptime Expires 232.1.1.1 133.133.4.1 00:02:04 # Display PIM routing entries on the public network.
Page 66 Figure 25 Network diagram Proxy Querier Router B Router A GE1/0/1 192.168.1.1/24 PIM-DM GE1/0/1 GE1/0/2 192.168.1.2/24 GE1/0/2 10.110.1.1/24 192.168.2.1/24 Receiver Receiver Host B Host A Host C Configuration procedure Assign an IP address and subnet mask to each interface, as shown in Figure 25.
Page 67: Multicast Access Control Configuration Example (For Pppoe)
GigabitEthernet1/0/1(192.168.1.2): IGMP proxy group records in total: 1 Group address Member state Expires 224.1.1.1 Delay 00:00:02 Multicast access control configuration example (for PPPoE) As shown in Figure • OSPF runs in the PIM-SM domain. • Source 1, Source 2, and Source 3 send multicast data to multicast groups 224.1.1.1, 225.1.1.1, and 226.1.1.1, respectively.
Page 68 Table 8 Interface and IP address assignment Device Interface IP address Device Interface IP address Source 1 — 10.100.1.1/24 Host A — 192.168.1.2/24 Source 2 — 10.100.2.1/24 Host B — 192.168.1.3/24 Source 3 — 10.100.3.1/24 Host C — 192.168.2.2/24 RADIUS —...
Page 69 # Configure Router C and Router D in the same way Router B is configured. (Details not shown.) # On Router A, configure GigabitEthernet 1/0/2 as a C-BSR and a C-RP. [RouterA] pim [RouterA-pim] c-bsr 11.110.2.1 [RouterA-pim] c-rp 11.110.2.1 [RouterA-pim] quit Configure the access service on the BRAS: # Configure Router A as the RADIUS client.
Page 70 [RouterA-Virtual-Template2] quit # Configure GigabitEthernet 1/0/5.1 to terminate VLAN-tagged packets whose outer VLAN ID is 1 and inner VLAN ID is in the range of 1 to 100. [RouterA] interface gigabitethernet 1/0/5.1 [RouterA-GigabitEthernet1/0/5.1] vlan-type dot1q vid 1 second-dot1q 1 to 100 # Bind GigabitEthernet 1/0/5.1 to interface Virtual-Template 1.
Page 71: Multicast Access Control Configuration Example (For Ipoe)
[RouterA-isp-isp2] quit Verifying the configuration # Display authorized IGMP user information on Router A after Host A and Host C log in. [RouterA] display igmp user-authorization Authorized users in total: 2 User name: user1@isp1 Access type: PPP Interface: Virtual-Access0 Access interface: Virtual-Access0 Maximum programs for order: 4 User profile: profile1 Authorized programs list:...
Page 72 Figure 27 Network diagram Source 1 Source 2 Source 3 GE1/0/2 GE1/0/2 GE1/0/2 Router C GE1/0/1 Router B Router D RADIUS server GE1/0/4 BRAS Router A PIM-SM ISP 1 ISP 2 Access Access network network Host A Host B Host C Host D User1@ISP1 User2@ISP1...
Page 73 Enable IP multicast routing, and configure PIM-SM: # On Router A, enable IP multicast routing. <RouterA> system-view [RouterA] multicast routing [RouterA-mrib] quit # Enable PIM-SM on GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3. [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...
Page 74 [RouterA-isp-isp1] authorization ipoe radius-scheme spec [RouterA-isp-isp1] accounting ipoe radius-scheme spec [RouterA-isp-isp1] quit # Create an ISP domain named isp2, and specify the STB service for users in the ISP domain. [RouterA] domain isp2 [RouterA-isp-isp2] service-type stb # Configure AAA methods for ISP domain isp2. [RouterA-isp-isp2] authentication ipoe radius-scheme spec [RouterA-isp-isp2] authorization ipoe radius-scheme spec [RouterA-isp-isp2] accounting ipoe radius-scheme spec...
Page 75 Configure multicast access control on the BRAS: # Enable IGMP and multicast access control, and enable per-session multicast forwarding on GigabitEthernet 1/0/5.1. [RouterA] interface gigabitethernet 1/0/5.1 [RouterA-GigabitEthernet1/0/5.1] igmp enable [RouterA-GigabitEthernet1/0/5.1] igmp authorization-enable [RouterA-GigabitEthernet1/0/5.1] igmp join-by-session [RouterA-GigabitEthernet1/0/5.1] quit # Configure GigabitEthernet 1/0/5.2 in the same way GigabitEthernet 1/0/5.1 is configured. (Details not shown.) # Configure an access policy in user profile profile1 to authorize IGMP users to join multicast groups 224.1.1.1 and 225.1.1.1.
Page 76: Multicast Access Control Configuration Example (For Portal)
User profile: profile1 Authorized programs list: User name: user1@isp2 Access type: IPoE Interface: Multicast-UA2 Access interface: GigabitEthernet1/0/5.2 VLAN ID: 2 Second VLAN ID: 2 Maximum programs for order: 4 User profile: profile2 Authorized programs list: Multicast access control configuration example (for Portal) As shown in Figure •...
Page 77 Figure 28 Network diagram Source 1 Source 2 Source 3 GE1/0/2 GE1/0/2 GE1/0/2 Router C GE1/0/1 Router B Router D iMC server RADIUS server GE1/0/4 GE1/0/7 BRAS PIM-SM Router A ISP 1 ISP 2 Access Access network network Host A Host B Host C Host D...
Page 78 Configure OSPF in the PIM-SM domain. (Details not shown.) Enable IP multicast routing, and configure PIM-SM: # On Router A, enable IP multicast routing. <RouterA> system-view [RouterA] multicast routing [RouterA-mrib] quit # Enable PIM-SM on GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3. [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] pim sm [RouterA-GigabitEthernet1/0/1] quit...
Page 79 [RouterA-portal-server-spec] ip 10.110.5.2 key simple 123456 [RouterA-portal-websvr-spec] quit # On the RADIUS server, configure the user accounts with the same usernames, passwords, and IP addresses as those on the RADIUS client. (Details not shown.) # On the IMC server, configure the IP address group for users. Specify the next hop of the default route to users as 11.110.5.1.
Page 80 # Configure GigabitEthernet 1/0/6 in the same way GigabitEthernet 1/0/5 is configured. (Details not shown.) # Configure an access policy in user profile profile1 to authorize MLD users to join multicast groups 224.1.1.1 and 225.1.1.1. [RouterA] acl basic 2000 [RouterA-acl-ipv4-basic-2000] rule permit source 224.1.1.1 0 [RouterA-acl-ipv4-basic-2000] rule permit source 225.1.1.1 0 [RouterA-acl-ipv4-basic-2000] quit [RouterA] user-profile profile1...
Page 81: Troubleshooting Igmp
Troubleshooting IGMP No membership information on the receiver-side router Symptom When a host sends a report for joining multicast group G, no membership information of multicast group G exists on the router closest to that host. Solution To resolve the problem: Use the display igmp interface command to verify that the networking, interface connection, and IP address configuration are correct.
Page 82: Configuring Pim
Configuring PIM Overview Protocol Independent Multicast (PIM) provides IP multicast forwarding by leveraging unicast static routes or unicast routing tables generated by any unicast routing protocol, such as RIP, OSPF, IS-IS, or BGP. PIM uses the underlying unicast routing to generate a multicast routing table without relying on any particular unicast routing protocol.
Page 83 this way, the upstream stream node stops forwarding subsequent packets addressed to that multicast group down to this node. NOTE: An (S, G) entry contains a multicast source address S, a multicast group address G, an outgoing interface list, and an incoming interface. A prune process is initiated by a leaf router.
Page 84: Pim-Sm Overview
Figure 30 Assert mechanism As shown in Figure 30, after Router A and Router B receive an (S, G) packet from the upstream node, they both forward the packet to the local subnet. As a result, the downstream node Router C receives two identical multicast packets.
Page 85 PIM-DM does not require a DR. However, if IGMPv1 runs on any shared-media LAN in a PIM-DM domain, a DR must be elected to act as the IGMPv1 querier for the LAN. For more information about IGMP, see "Configuring IGMP." IMPORTANT: IGMP must be enabled on the device that acts as the receiver-side DR.
Page 86 As shown in Figure 32, each C-RP periodically unicasts its advertisement messages (C-RP-Adv messages) to the BSR. An advertisement message contains the address of the advertising C-RP and the multicast group range to which it is designated. The BSR collects these advertisement messages and organizes the C-RP information into an RP-set, which is a database of mappings between multicast groups and RPs.
Page 87 Anycast RP member address—IP address of each Anycast RP member for communication among the RP members. Anycast RP address—IP address of the Anycast RP set for communication within the PIM-SM domain. It is also known as RPA. As shown in Figure 33, RP 1, RP 2, and RP 3 are members of an Anycast RP set.
Page 88 RPT building Figure 34 RPT building in a PIM-SM domain Host A Source Receiver Host B Server Receiver Join message Multicast packets Host C As shown in Figure 34, the process of building an RPT is as follows: When a receiver wants to join the multicast group G, it uses an IGMP message to inform the receiver-side DR.
Page 89 Figure 35 Multicast source registration As shown in Figure 35, the multicast source registers with the RP as follows: The multicast source S sends the first multicast packet to the multicast group G. When receiving the multicast packet, the source-side DR encapsulates the packet into a PIM register message and unicasts the message to the RP.
Page 90: Bidir-Pim Overview
The RP periodically checks the multicast packet forwarding rate. If the RP finds that the traffic rate exceeds the specified threshold, it sends an (S, G) source-specific join message toward the multicast source. The routers along the path from the RP to the multicast source constitute an SPT.
Page 91 DF election On a subnet with multiple multicast routers, duplicate multicast packets might be forwarded to the RP. To address this issue, BIDIR-PIM uses a designated forwarder (DF) election mechanism to elect a unique DF for each RP on a subnet. Only the DFs can forward multicast data to the RP. DF election is not necessary for an RPL.
Page 92 Figure 37 RPT building at the receiver side As shown in Figure 37, the process for building a receiver-side RPT is the same as the process for building an RPT in PIM-SM: When a receiver wants to join the multicast group G, it uses an IGMP message to inform the directly connected router.
Page 93: Administrative Scoping Overview
Figure 38 RPT building at the multicast source side As shown in Figure 38, the process for building a source-side RPT is relatively simple: When a multicast source sends multicast packets to the multicast group G, the DF in each subnet unconditionally forwards the packets to the RP.
Page 94 Multicast group ranges that are associated with different admin-scoped zones can have intersections. However, the multicast groups in an admin-scoped zone are valid only within the local zone, and theses multicast groups are regarded as private group addresses. The global-scoped zone maintains a BSR for the multicast groups that do not belong to any admin-scoped zones.
Page 95: Pim-Ssm Overview
Figure 40 Relationship in view of multicast group address ranges Admin-scope 1 Admin-scope 3 G1 address G3 address Admin-scope 2 Global-scope G2 address − − G2 address As shown in Figure 40, the admin-scoped zones 1 and 2 have no intersection, but the admin-scoped zone 3 is a subset of the admin-scoped zone 1.
Page 96: Relationship Among Pim Protocols
Figure 41 SPT building in PIM-SSM Host A Source Receiver Host B Server Receiver Subscribe message Multicast packets Host C As shown in Figure 41, Host B and Host C are receivers. They send IGMPv3 report messages to their DRs to express their interest in the multicast information that the multicast source S sends to the multicast group G.
Page 97: Pim Support For Vpns
Figure 42 Relationship among PIM protocols A receiver joins multicast group G. G is in the A multicast source is SSM group range? specified? BIDIR-PIM is enabled? An IGMP-SSM mapping is configured for G? PIM-SM runs for G. G has a BIDIR-PIM RP? PIM-SSM runs for G.
Page 98: Pim-Dm Configuration Task List
PIM-DM configuration task list Tasks at a glance (Required.) Enabling PIM-DM (Optional.) Enabling the state refresh feature (Optional.) Configuring state refresh parameters (Optional.) Configuring PIM-DM graft retry timer (Optional.) Configuring common PIM features Configuration prerequisites Before you configure PIM-DM, configure a unicast routing protocol so that all devices in the domain can interoperate at the network layer.
Page 99: Configuring State Refresh Parameters
Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Enable the state refresh By default, the state refresh pim state-refresh-capable feature. feature is enabled. Configuring state refresh parameters The state refresh interval determines the interval at which a router sends state refresh messages. It is configurable.
Page 100: Configuring Pim-Sm
For more information about the configuration of other timers in PIM-DM, see "Configuring common timers." Configuring PIM-SM This section describes how to configure PIM-SM. PIM-SM configuration task list Tasks at a glance Remarks (Required.) Enabling PIM-SM (Required.) Configuring an • Configuring a static RP You must configure a static RP, a •...
Page 101: Configuring An Rp
Step Command Remarks Enable IP multicast routing multicast routing [ vpn-instance By default, IP multicast routing is and enter MRIB view. vpn-instance-name ] disabled. Return to system view. quit interface interface-type Enter interface view. interface-number Enable PIM-SM. By default, PIM-SM is disabled. pim sm Configuring an RP An RP can provide services for multiple or all multicast groups.
Page 102 BSR does not receive any advertisement message when the timer expires, it considers the C-RP failed or unreachable. A C-RP policy enables the BSR to filter C-RP advertisement messages by using an ACL that specifies the packet source address range and multicast groups. It is used to guard against C-RP spoofing.
Page 103: Configuring A Bsr
Anycast RP set, the lowest IP address becomes the RP member address. The rest of the interface addresses become backup RP member addresses. To configure Anycast RP: Step Command Remarks Enter system view. system-view pim [ vpn-instance Enter PIM view. vpn-instance-name ] By default, Anycast RP is not configured.
Page 104 affected. For more information about static multicast routes, see "Configuring multicast routing forwarding." To configure a C-BSR: Step Command Remarks Enter system view. system-view pim [ vpn-instance Enter PIM view. vpn-instance-name ] c-bsr ip-address [ scope group-address { mask-length | Configure a C-BSR.
Page 105: Configuring Multicast Source Registration
NOTE: Generally, a BSR performs BSM semantic fragmentation according to the MTU of its BSR interface. For BSMs originated due to learning of a new PIM neighbor, semantic fragmentation is performed according to the MTU of the interface that sends the BSMs. Disabling the device from forwarding BSMs out of their incoming interfaces By default, the device forwards BSMs out of their incoming interfaces to avoid the situation that some devices cannot receive the BSMs because of inconsistent routing information.
Page 106: Configuring The Switchover To Spt
To configure multicast source registration: Step Command Remarks Enter system view. system-view pim [ vpn-instance Enter PIM view. vpn-instance-name ] By default, no PIM register Configure a PIM register policies exist, and all PIM register register-policy ipv4-acl-number policy. messages are regarded legal. Configure the device to By default, the device calculates calculate the checksum...
Page 107: Bidir-Pim Configuration Task List
BIDIR-PIM configuration task list Tasks at a glance Remarks (Required.) Enabling BIDIR-PIM (Required.) Configuring an • Configuring a static RP You must configure a static RP, a • Configuring a C-RP C-RP, or both in a BIDIR-PIM domain. • (Optional.) Enabling Auto-RP listening •...
Page 108: Configuring An Rp
Configuring an RP CAUTION: When both PIM-SM and BIDIR-PIM run on the PIM network, do not use the same RP to provide services for PIM-SM and BIDIR-PIM. Otherwise, exceptions might occur to the PIM routing table. An RP can provide services for multiple or all multicast groups. However, only one RP can forward multicast traffic for a multicast group at a time.
Page 109 encapsulates the C-RP information and its own IP address in a BSM, and floods the BSM to all PIM routers in the domain. An advertisement message contains a holdtime option, which defines the C-RP lifetime for the advertising C-RP. After the BSR receives an advertisement message from a C-RP, it starts a timer for the C-RP.
Page 110: Configuring A Bsr
Configuring a BSR You must configure a BSR if C-RPs are configured to dynamically select the RP. You do not need to configure a BSR when you have configured only a static RP but no C-RPs. A BIDIR-PIM domain can have only one BSR, but must have a minimum of one C-BSR. Any router can be configured as a C-BSR.
Page 111 Step Command Remarks By default, no BSR policies exist, (Optional.) Configure a BSR and all bootstrap messages are bsr-policy ipv4-acl-number policy. regarded legal. Configuring a PIM domain border A PIM domain border determines the transmission boundary of bootstrap messages. Bootstrap messages cannot cross the domain border in either direction.
Page 112: Configuring Pim-Ssm
Step Command Remarks Enter system view. system-view pim [ vpn-instance Enter PIM view. vpn-instance-name ] Disable the device from By default, the device forwards forwarding BSMs out of their BSMs out of their incoming undo bsm-reflection enable incoming interfaces. interfaces. Configuring PIM-SSM PIM-SSM requires IGMPv3 support.
Page 113: Configuring The Ssm Group Range
Configuring the SSM group range When a PIM-SM enabled interface receives a multicast packet, it checks whether the multicast group address of the packet is in the SSM group range. If the multicast group address is in this range, the PIM mode for this packet is PIM-SSM.
Page 114: Configuring A Multicast Source Policy
Configuring a multicast source policy This feature enables the device to filter multicast data by using an ACL that specifies the multicast sources and the optional groups. It filters not only data packets but also register messages with multicast data encapsulated. It controls the information available to downstream receivers. To configure a multicast source policy: Step Command...
Page 115 On the shared-media LAN, the propagation delay and override interval are used as follows: If a router receives a prune message on its upstream interface, it means that there are downstream routers on the shared-media LAN. If this router still needs to receive multicast data, it must send a join message to override the prune message within the override interval.
Page 116: Configuring Common Pim Timers
Step Command Remarks Set the PIM message The default setting is 500 pim hello-option lan-delay delay propagation delay. milliseconds. The default setting is 2500 pim hello-option Set the override interval. milliseconds. override-interval interval By default, neighbor tracking is pim hello-option Enable neighbor tracking.
Page 117: Setting The Maximum Size Of A Join Or Prune Message
Step Command Remarks The default setting is 60 seconds. Set the join/prune interval. timer join-prune interval This configuration takes effect after the current interval ends. Set the joined/pruned state The default setting is 210 holdtime join-prune time holdtime. seconds. Set the multicast source The default setting is 210 source-lifetime time lifetime.
Page 118: Enabling Pim Passive Mode
To enable BFD for PIM: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, BFD is disabled for Enable BFD for PIM. pim bfd enable PIM. Enabling PIM passive mode To guard against PIM hello spoofing, you can enable PIM passive mode on a receiver-side interface. The PIM passive interface cannot receive or forward PIM protocol messages (excluding register, register-stop and C-RP-Adv messages), and it acts as the DR on the subnet.
Page 119: Enabling Nbma Mode For Advpn Tunnel Interfaces
Enabling NBMA mode for ADVPN tunnel interfaces This feature allows ADVPN tunnel interfaces to forward multicast data to target spokes and hubs. For more information about ADVPN, see Layer 3 — IP Services Configuration Guide. Configuration restrictions and guidelines When you enable NBMA mode, follow these restrictions and guidelines: •...
Page 120: Pim Configuration Examples
Task Command display pim [ vpn-instance vpn-instance-name ] routing-table [ group-address [ mask { mask-length | mask } ] | source-address [ mask { mask-length | mask } ] | flags flag-value | fsm | Display PIM routing entries. incoming-interface interface-type interface-number | mode mode-type | outgoing-interface { exclude | include | match } interface-type interface-number | proxy ] * Display RP information in the...
Page 121 Figure 43 Network diagram Receiver Host A Router A GE1/0/1 Host B Receiver GE1/0/1 GE1/0/3 GE1/0/2 GE1/0/1 Source Host C Router D Router B 10.110.5.100/24 GE1/0/1 PIM-DM Router C Host D Table 11 Interface and IP address assignment Device Interface IP address Device Interface...
Page 122 # Enable IP multicast routing, IGMP, and PIM-DM on Router B and Router C in the same way Router A is configured. (Details not shown.) # On Router D, enable IP multicast routing, and enable PIM-DM on each interface. <RouterD> system-view [RouterD] multicast routing [RouterD-mrib] quit [RouterD] interface gigabitethernet 1/0/1...
Page 123: Pim-Sm Non-Scoped Zone Configuration Example
Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet1/0/1 Protocol: igmp, UpTime: 00:04:25, Expires: - (10.110.5.100, 225.1.1.1) Protocol: pim-dm, Flag: ACT UpTime: 00:06:14 Upstream interface: GigabitEthernet1/0/2 Upstream neighbor: 192.168.1.2 RPF prime neighbor: 192.168.1.2 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet1/0/1 Protocol: pim-dm, UpTime: 00:04:25, Expires: - # Display the PIM routing table on Router D.
Page 124 • IGMPv2 runs between Router A and N1, and between Router B, Router C, and N2. Figure 44 Network diagram Receiver Host A Router A GE1/0/1 GE1/0/3 Host B GE1/0/3 Receiver GE1/0/1 GE1/0/4 GE1/0/2 GE1/0/1 GE1/0/3 GE1/0/2 Source GE1/0/1 Router D Router E Router B Host C...
Page 125 [RouterA-GigabitEthernet1/0/1] igmp enable [RouterA-GigabitEthernet1/0/1] quit # Enable PIM-SM on the other interfaces. [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] pim sm [RouterA-GigabitEthernet1/0/3] quit # Enable IP multicast routing, IGMP and PIM-SM on Router B and Router C in the same way Router A is configured.
Page 126: Pim-Sm Admin-Scoped Zone Configuration Example
Uptime: 00:11:18 # Display BSR information on Router E. [RouterE] display pim bsr-info Scope: non-scoped State: Elected Bootstrap timer: 00:01:44 Elected BSR address: 192.168.9.2 Priority: 64 Hash mask length: 30 Uptime: 00:11:18 Candidate BSR address: 192.168.9.2 Priority: 64 Hash mask length: 30 # Display RP information on Router A.
Page 127 Figure 45 Network diagram Admin-scope 1 GE1/0/1 Receiver Router G Host A Source 1 GE1/0/2 Source 3 GE1/0/1 GE1/0/1 GE1/0/1 GE1/0/2 GE1/0/4 GE1/0/3 Router F GE1/0/2 GE1/0/2 Router B Router A Router C Router I Router H GE1/0/3 GE1/0/2 GE1/0/2 GE1/0/3 Router D GE1/0/1...
Page 128 Configuration procedure Assign an IP address and subnet mask to each interface, as shown in Figure 45. (Details not shown.) Configure OSPF on all routers in the PIM-SM domain. (Details not shown.) Enable IP multicast routing, IGMP, and PIM-SM: # On Router A, enable IP multicast routing. <RouterA>...
Page 129 <RouterC> system-view [RouterC] interface gigabitethernet 1/0/4 [RouterC-GigabitEthernet1/0/4] multicast boundary 239.0.0.0 8 [RouterC-GigabitEthernet1/0/4] quit [RouterC] interface gigabitethernet 1/0/5 [RouterC-GigabitEthernet1/0/5] multicast boundary 239.0.0.0 8 [RouterC-GigabitEthernet1/0/5] quit # On Router D, configure GigabitEthernet 1/0/3 as the boundary of admin-scoped zone 2. <RouterD> system-view [RouterD] interface gigabitethernet 1/0/3 [RouterD-GigabitEthernet1/0/3] multicast boundary 239.0.0.0 8 [RouterD-GigabitEthernet1/0/3] quit...
Page 130 Uptime: 00:01:45 Scope: 239.0.0.0/8 State: Elected Bootstrap timer: 00:00:06 Elected BSR address: 10.110.1.2 Priority: 64 Hash mask length: 30 Uptime: 00:04:54 Candidate BSR address: 10.110.1.2 Priority: 64 Hash mask length: 30 # Display BSR information on Router D. [RouterD] display pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:44...
Page 131: Bidir-Pim Configuration Example
Group/MaskLen: 224.0.0.0/4 RP address Priority HoldTime Uptime Expires 10.110.9.1 00:03:39 00:01:51 Scope: 239.0.0.0/8 Group/MaskLen: 239.0.0.0/8 RP address Priority HoldTime Uptime Expires 10.110.1.2 (local) 00:07:44 00:01:51 # Display RP information on Router D. [RouterD] display pim rp-info BSR RP information: Scope: non-scoped Group/MaskLen: 224.0.0.0/4 RP address Priority...
Page 132 Figure 46 Network diagram Loop0 Receiver 1 Receiver 2 Router B GE1/0/1 GE1/0/3 GE1/0/1 Router C Host A Host B GE1/0/2 GE1/0/2 BIDIR-PIM Source 1 Source 2 GE1/0/2 GE1/0/3 GE1/0/1 GE1/0/2 Router A Router D Table 14 Interface and IP address assignment Device Interface IP address...
Page 133 [RouterA-pim] quit # On Router B, enable IP multicast routing. <RouterB> system-view [RouterB] multicast routing [RouterB-mrib] quit # Enable IGMP on the receiver-side interface (GigabitEthernet 1/0/1). [RouterB] interface gigabitethernet 1/0/1 [RouterB-GigabitEthernet1/0/1] igmp enable [RouterB-GigabitEthernet1/0/1] quit # Enable PIM-SM on the other interfaces. [RouterB] interface gigabitethernet 1/0/2 [RouterB-GigabitEthernet1/0/2] pim sm [RouterB-GigabitEthernet1/0/2] quit...
Page 134 [RouterD] interface gigabitethernet 1/0/3 [RouterD-GigabitEthernet1/0/3] pim sm [RouterD-GigabitEthernet1/0/3] quit # Enable BIDIR-PIM. [RouterD] pim [RouterD-pim] bidir-pim enable [RouterD-pim] quit On Router C, configure GigabitEthernet 1/0/1 as the C-BSR, and Loopback 0 as the C-RP for the entire BIDIR-PIM domain. [RouterC-pim] c-bsr 10.110.2.2 [RouterC-pim] c-rp 1.1.1.1 bidir [RouterC-pim] quit Verifying the configuration...
Page 135: Pim-Ssm Configuration Example
Flags: 0x0 Uptime: 00:08:32 RPF interface: GigabitEthernet1/0/2 List of 1 DF interfaces: 1: GigabitEthernet1/0/1 # Display information about the DF for multicast forwarding on Router B. [RouterB] display multicast forwarding df-info Total 1 RP, 1 matched 00001. RP address: 1.1.1.1 Flags: 0x0 Uptime: 00:06:24 RPF interface: GigabitEthernet1/0/3...
Page 136 • The SSM group range is 232.1.1.0/24. • IGMPv3 runs between Router A and N1, and between Router B, Router C, and N2. Figure 47 Network diagram Receiver Host A Router A GE1/0/1 GE1/0/3 Host B GE1/0/3 Receiver GE1/0/1 GE1/0/4 GE1/0/2 GE1/0/1 GE1/0/3...
Page 137 [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] igmp enable [RouterA-GigabitEthernet1/0/1] igmp version 3 [RouterA-GigabitEthernet1/0/1] quit # Enable PIM-SM on the other interfaces. [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] pim sm [RouterA-GigabitEthernet1/0/3] quit # Enable IP multicast routing, IGMP, and PIM-SM on Router B and Router C in the same way Router A is configured.
Page 138: Troubleshooting Pim
Protocol: igmp, UpTime: 00:13:25, Expires: 00:03:25 # Display PIM routing entries on Router D. [RouterD] display pim routing-table Total 0 (*, G) entry; 1 (S, G) entry (10.110.5.100, 232.1.1.1) Protocol: pim-ssm, Flag: LOC UpTime: 00:12:05 Upstream interface: GigabitEthernet1/0/1 Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1...
Page 139: Multicast Data Is Abnormally Terminated On An Intermediate Router
Multicast data is abnormally terminated on an intermediate router Symptom An intermediate router can receive multicast data successfully, but the data cannot reach the last-hop router. An interface on the intermediate router receives multicast data but does not create an (S, G) entry in the PIM routing table. Solution To resolve the problem: Use display current-configuration to verify the multicast forwarding boundary settings.
Page 140 If the problem persists, contact Hewlett Packard Enterprise Support.
Page 141: Configuring Multicast Vpn
Configuring multicast VPN Overview Multicast VPN implements multicast delivery in VPNs. A VPN contains multiple customer network sites and the public network provided by the network service provider. The sites communicate through the public network. As shown in Figure • VPN A contains Site 1, Site 3, and Site 5.
Page 142: Md Vpn Overview
Figure 49 Multicast in multiple VPN instances Through multicast VPN, multicast data of VPN A for a multicast group can only arrive at receiver hosts in Site 1, Site 3, and Site 5 of VPN A. The stream is multicast in these sites and on the public network.
Page 143 Table 16 Basic MD VPN concepts Concept Description An MD is a set of PE devices that are in the same VPN instance. Multicast domain (MD) Each MD uniquely corresponds to a VPN instance. An MDT is a multicast distribution tree constructed by all PE devices Multicast distribution tree (MDT) in the same VPN.
Page 144 b. The encapsulated multicast packet is sent by the PE device and travels over the public network. c. After receiving the multicast packet, the remote PE device decapsulates the multicast packet to get the original VPN multicast packet. • The local PE device sends VPN data out of the MTI. The remote PE devices receive the private data from their MTI interfaces.
Page 145: Protocols And Standards
packets with the data-group address. Then they are switched from the default-MDT to the data-MDT. For more information about MDT switchover, see "MDT switchover." NOTE: A VPN uniquely corresponds to an MD and an MD provides services for only one VPN, which is called a one-to-one relationship.
Page 146: Default-Mdt Establishment
For a VPN instance, multicast data transmission on the public network is transparent. The VPN data is exchanged between the MTIs of the local PE and the remote PE. This implements the seamless transmission of the VPN data over the public network. However, the multicast data transmission process (the MDT transmission process) over the public network is very complicated.
Page 147 Default-MDT establishment in a PIM-SM network Figure 53 Default-MDT establishment in a PIM-SM network As shown in Figure 53, PIM-SM is enabled on the network, and all the PE devices support VPN instance A. The process of establishing a default-MDT is as follows: PE 1 initiates a join to the public network RP by specifying the multicast group address as the default-group address in the join message.
Page 148 Default-MDT establishment in a BIDIR-PIM network Figure 54 Default-MDT establishment in a BIDIR-PIM network As shown in Figure 54, BIDIR-PIM runs on the network, and all the PE devices support VPN instance A. The process of establishing a default-MDT is as follows: PE 1 initiates a join to the public network RP by specifying the multicast group address as the default-group address in the join message.
Page 149: Default-Mdt-Based Delivery
Default-MDT establishment in a PIM-SSM network Figure 55 Default-MDT establishment in a PIM-SSM network As shown in Figure 55, PIM-SSM runs on the network, and all the PE devices support VPN instance A. The process of establishing a default-MDT is as follows: PE 1, PE 2, and PE 3 exchange MDT route information (including BGP interface address and the default-group address) through BGP.
Page 150 A flood-prune process (in PIM-DM) or a join process (in PIM-SSM) is initiated across the public network to establish an SPT across the public network. • If the VPN network runs PIM-SM: Hello packets are forwarded through MTI interfaces to establish PIM neighboring relationships.
Page 151 After receiving the join message from CE 2, the VPN instance on PE 2 creates a state entry (*, 225.1.1.1) and specifies the MTI interface as the upstream interface. The VPN instance on PE 2 considers the join message to have been sent out of the MTI interface, because step 3 is transparent to the VPN instance.
Page 152: Mdt Switchover
Figure 57 Multicast data packet delivery A VPN multicast data packet is delivered across the public network as follows: Source sends a VPN multicast data packet (192.1.1.1, 225.1.1.1) to CE 1. CE 1 forwards the VPN multicast data packet along an SPT to PE 1, and the VPN instance on PE 1 examines the MVRF.
Page 153: Inter-As Md Vpn
connect VPN multicast receivers and multicast sources. When specific network criteria are met, a switchover from the default-MDT to the data-MDT occurs to forward VPN multicast traffic to receivers. The process of default-MDT to data-MDT switchover is as follows: The source-side PE device (PE 1, for example) periodically examines the forwarding rate of the VPN multicast traffic.
Page 154 • Multihop EBGP redistribution of labeled VPN-IPv4 routes between PE routers—PEs advertise VPN-IPv4 routes to each other through MP-EBGP. This solution is also called inter-AS option C. For more information about the three inter-AS VPN solutions, see "Configuring MPLS L3VPN." Based on these solutions, there are three ways to implement inter-AS MD VPN: •...
Page 155 When a device receives the join message with the RPF vector, it first checks whether the RPF vector is its own IP address. If so, the device removes the RPF vector, and sends the message to its upstream neighbor according to the route to the remote PE device. Otherwise, it keeps the RPF vector, looks up the route to the RPF vector, and sends the message to the next hop of the route.
Page 156: M6Vpe
When PE 1 joins the SPT rooted at PE 1, PE 2 also initiates a join process to the SPT rooted at PE 1. A MDT is established when the two SPTs are finished. MD VPN inter-AS option C As shown in Figure •...
Page 157: Multicast Vpn Configuration Task List
Figure 61 M6VPE network IPv6 multicast traffic forwarding over the IPv4 public network is as follows: CE 1 forwards an IPv6 multicast packet for VPN instance VPN A to PE 1. PE 1 encapsulates the IPv6 multicast packet with an IPv4 packet header and transmits the IPv4 packet in the IPv4 backbone network.
Page 158: Configuring Md Vpn
Configuring MD VPN This section describes how to configure MD VPN. Configuration prerequisites Before you configure MD VPN, complete the following tasks: • Configure a unicast routing protocol on the public network. • Configure MPLS L3VPN on the public network. •...
Page 159: Creating An Md For A Vpn Instance
Creating an MD for a VPN instance To provide multicast services for a VPN instance, you must create an MD for the VPN instance on PE devices that belong to the VPN instance. After the MD is created, the system automatically creates MTIs and binds them with the VPN instance.
Page 160: Specifying The Md Source Interface
Step Command Remarks Enter system view. system-view multicast-domain vpn-instance Enter MD view. vpn-instance-name • Enter MD IPv4 address family view: Enter MD address family address-family ipv4 view. • Enter MD IPv6 address family view: address-family ipv6 By default, no default-group Specify the default-group.
Page 161: Configuring The Rpf Vector Feature
• Likewise, a backward switchover does not take place immediately after the multicast traffic rate drops below the MDT switchover threshold. It takes place after a data-holddown period, during which the traffic rate must stay lower than the switchover threshold. Configuration restrictions and guidelines When you configure MDT switchover parameters, follow these restrictions and guidelines: •...
Page 162: Enabling Data-Group Reuse Logging
Step Command Remarks Enable the RPF vector By default, the RPF vector feature rpf proxy vector feature. is disabled. Enabling RPF vector compatibility This feature enables the device to work with other manufacturers' products on RPF vectors for interoperability purposes. You must enable this feature on all HPE devices on the public network. To enable RPF vector compatibility: Step Command...
Page 163: Configuring Bgp Mdt Peers Or Peer Groups
• Configure basic BGP functions on the public network. • Configure PIM-SSM on the public network. • Determine the IP addresses of the MDT peers. • Determine the cluster IDs of the route reflectors. Configuring BGP MDT peers or peer groups Configure a BGP MDT peer or peer group on a PE router in BGP IPv4 MDT address family view.
Page 164: Displaying And Maintaining Multicast Vpn
to improve network reliability. To avoid routing loops, make sure the route reflectors in a cluster have the same cluster ID. Perform this task on PE devices. To configure a BGP MDT route reflector: Step Command Remarks Enter system view. system-view bgp as-number [ instance Enter BGP instance view.
Page 165: Multicast Vpn Configuration Examples
Task Command Display information about display multicast-domain vpn-instance vpn-instance-name data-groups that are sent in the data-group send [ group group-address | reuse interval | MD of a VPN instance for IPv4 vpn-source-address [ mask { mask-length | mask } ] | multicast transmission.
Page 166 Item Network requirements • Enable IP multicast routing on the P router. • Enable IP multicast routing on the public network instance on PE 1, PE 2, and PE 3. • Enable IP multicast routing for VPN instance a on PE 1, PE 2, and PE IP multicast routing •...
Page 167 Device Interface IP address Device Interface IP address — 10.110.1.2/24 PE 3 GE1/0/3 10.110.6.1/24 — 10.110.9.2/24 PE 3 Loop1 1.1.1.3/32 — 10.110.10.2/24 PE 3 Loop2 33.33.33.33/32 — 10.110.11.2/24 CE a1 GE1/0/1 10.110.7.1/24 GE1/0/1 192.168.6.2/24 CE a1 GE1/0/2 10.110.2.2/24 GE1/0/2 192.168.7.2/24 CE a2 GE1/0/1 10.110.9.1/24...
Page 168 # Specify the default-group, the MD source interface, and the data-group range for VPN instance a. [PE1-md-a-ipv4] default-group 239.1.1.1 [PE1-md-a-ipv4] source loopback 1 [PE1-md-a-ipv4] data-group 225.2.2.0 28 [PE1-md-a-ipv4] quit [PE1-md-a] quit # Assign an IP address to GigabitEthernet 1/0/1. [PE1] interface gigabitethernet 1/0/1 [PE1-GigabitEthernet1/0/1] ip address 192.168.6.1 24 # Enable PIM-SM, MPLS, and IPv4 LDP on GigabitEthernet 1/0/1.
Page 169 [PE1–bgp-default-vpnv4] quit [PE1–bgp-default] quit # Configure OSPF. [PE1] ospf 1 [PE1-ospf-1] area 0.0.0.0 [PE1-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0 [PE1-ospf-1-area-0.0.0.0] network 192.168.6.0 0.0.0.255 [PE1-ospf-1-area-0.0.0.0] quit [PE1-ospf-1] quit # Configure RIP. [PE1] rip 2 vpn-instance a [PE1-rip-2] network 10.110.1.0 0.0.0.255 [PE1-rip-2] network 10.110.2.0 0.0.0.255 [PE1-rip-2] import-route bgp [PE1-rip-2] return Configure PE 2:...
Page 170 [PE2-vpn-instance-a] route-distinguisher 100:1 [PE2-vpn-instance-a] vpn-target 100:1 export-extcommunity [PE2-vpn-instance-a] vpn-target 100:1 import-extcommunity [PE2-vpn-instance-a] quit # Enable IP multicast routing for VPN instance a. [PE2] multicast routing vpn-instance a [PE2-mrib-a] quit # Create an MD for VPN instance a. [PE2] multicast-domain vpn-instance a # Create an MD IPv4 address family for VPN instance a.
Page 171 [PE2-bgp-default] peer vpn-g connect-interface loopback 1 [PE2-bgp-default] peer 1.1.1.1 group vpn-g [PE2-bgp-default] peer 1.1.1.3 group vpn-g [PE2–bgp-default] ip vpn-instance a [PE2-bgp-default-a] address-family ipv4 [PE2-bgp-default-ipv4-a] import-route rip 2 [PE2-bgp-default-ipv4-a] import-route direct [PE2-bgp-default-ipv4-a] quit [PE2-bgp-default-a] quit [PE2–bgp-default] ip vpn-instance b [PE2-bgp-default-b] address-family ipv4 [PE2-bgp-default-ipv4-b] import-route rip 3 [PE2-bgp-default-ipv4-b] import-route direct [PE2-bgp-default-ipv4-b] quit...
Page 172 [PE3-vpn-instance-a] vpn-target 100:1 export-extcommunity [PE3-vpn-instance-a] vpn-target 100:1 import-extcommunity [PE3-vpn-instance-a] quit # Enable IP multicast routing for VPN instance a. [PE3] multicast routing vpn-instance a [PE3-mrib-a] quit # Create an MD for VPN instance a. [PE3] multicast-domain vpn-instance a # Create an MD IPv4 address family for VPN instance a. [PE3-md-a] address-family ipv4 # Specify the default-group, the MD source interface, and the data-group range for VPN instance a.
Page 173 # Assign an IP address to GigabitEthernet 1/0/2, and enable PIM-SM on the interface. [PE3-GigabitEthernet1/0/2] ip address 10.110.5.1 24 [PE3-GigabitEthernet1/0/2] pim sm [PE3-GigabitEthernet1/0/2] quit # Associate GigabitEthernet 1/0/3 with VPN instance b. [PE3] interface gigabitethernet 1/0/3 [PE3-GigabitEthernet1/0/3] ip binding vpn-instance b # Assign an IP address to GigabitEthernet 1/0/3, and enable PIM-SM on the interface.
Page 174 [PE3–bgp-default-vpnv4] quit [PE3–bgp-default] quit # Configure OSPF. [PE3] ospf 1 [PE3-ospf-1] area 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 1.1.1.3 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 192.168.8.0 0.0.0.255 [PE3-ospf-1-area-0.0.0.0] quit [PE3-ospf-1] quit # Configure RIP. [PE3] rip 2 vpn-instance a [PE3-rip-2] network 10.110.5.0 0.0.0.255 [PE3-rip-2] import-route bgp [PE3-rip-2] quit [PE3] rip 3 vpn-instance b [PE3-rip-3] network 10.110.6.0 0.0.0.255...
Page 175 # Enable PIM-SM, MPLS, and IPv4 LDP on GigabitEthernet 1/0/3. [P-GigabitEthernet1/0/3] pim sm [P-GigabitEthernet1/0/3] mpls enable [P-GigabitEthernet1/0/3] mpls ldp enable [P-GigabitEthernet1/0/3] quit # Assign an IP address to Loopback 1, and enable PIM-SM on the interface. [P] interface loopback 1 [P-LoopBack1] ip address 2.2.2.2 32 [P-LoopBack1] pim sm [P-LoopBack1] quit...
Page 176 [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 # Assign an IP address to GigabitEthernet 1/0/2, and enable PIM-SM on the interface. [CEb1] interface gigabitethernet 1/0/2 [CEb1-GigabitEthernet1/0/2] ip address 10.110.3.2 24 [CEb1-GigabitEthernet1/0/2] pim sm [CEb1-GigabitEthernet1/0/2] quit # Configure RIP.
Page 177 [CEa2-rip-2] network 10.110.12.0 0.0.0.255 [CEa2-rip-2] network 22.22.22.22 0.0.0.0 Configure CE a3: # Enable IP multicast routing. <CEa3> system-view [CEa3] multicast routing [CEa3-mrib] quit # Assign an IP address to GigabitEthernet 1/0/1, and enable IGMP on the interface. [CEa3] interface gigabitethernet 1/0/1 [CEa3-GigabitEthernet1/0/1] ip address 10.110.10.1 24 [CEa3-GigabitEthernet1/0/1] igmp enable [CEa3-GigabitEthernet1/0/1] quit...
Page 178: Intra-As M6Vpe Configuration Example
Verifying the configuration # Display information about the local default-group for IPv4 multicast transmission in each VPN instance on PE 1. [PE1] display multicast-domain default-group local MD local default-group information: Group address Source address Interface VPN instance 239.1.1.1 1.1.1.1 MTunnel0 # Display information about the local default-group for IPv4 multicast transmission in each VPN instance on PE 2.
Page 179 Item Network requirements • Enable IP multicast routing on P. • Enable IP multicast routing for the public network on PE 1, PE 2, and PE 3. • Enable IPv6 multicast routing for VPN instance a on PE 1, PE 2, and IP multicast routing and IPv6 PE 3.
Page 180 Table 18 Interface and IP address assignment IPv4/IPv6 Device Interface Device Interface IPv4/IPv6 address address — 10:110:7::2/64 PE 3 GE1/0/1 192.168.8.1/24 — 10:110:8::2/64 PE 3 GE1/0/2 10:110:5::1/64 — 10:110:1::2/64 PE 3 GE1/0/3 10:110:6::1/64 — 10:110:9::2/64 PE 3 Loop1 1.1.1.3/32 — 10:110:10::2/64 PE 3 Loop2...
Page 181 # Create an MD for VPN instance a. [PE1] multicast-domain vpn-instance a # Create an MD IPv6 address family for VPN instance a. [PE1-md-a] address-family ipv6 # Specify the default group, the MD source interface, and the data-group range for VPN instance a.
Page 182 [PE1-bgp-default] peer 1.1.1.2 group vpn-g [PE1-bgp-default] peer 1.1.1.3 group vpn-g [PE1–bgp-default] ip vpn-instance a [PE1-bgp-default-a] address-family ipv6 [PE1-bgp-default-ipv6-a] import-route ospfv3 2 [PE1-bgp-default-ipv6-a] import-route direct [PE1-bgp-default-ipv6-a] quit [PE1-bgp-default-a] quit [PE1–bgp-default] address-family vpnv6 [PE1–bgp-default-vpnv6] peer vpn-g enable [PE1–bgp-default-vpnv6] quit [PE1–bgp-default] quit # Configure OSPF. [PE1] ospf 1 [PE1-ospf-1] area 0.0.0.0 [PE1-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0...
Page 183 # Create an MD IPv6 address family for VPN instance b. [PE2-md-b] address-family ipv6 # Specify the default-group, the MD source interface, and the data-group range for VPN instance b. [PE2-md-b-ipv6] default-group 239.2.2.2 [PE2-md-b-ipv6] source loopback 1 [PE2-md-b-ipv6] data-group 225.4.4.0 28 [PE2-md-b-ipv6] quit [PE2-md-b] quit # Create a VPN instance named a, and configure the RD and route targets for the VPN...
Page 184 # Associate GigabitEthernet 1/0/3 with VPN instance a, and assign an IPv6 address to the interface. [PE2] interface gigabitethernet 1/0/3 [PE2-GigabitEthernet1/0/3] ip binding vpn-instance a [PE2-GigabitEthernet1/0/3] ipv6 address 10:110:4::1 64 # Enable IPv6 PIM-SM on GigabitEthernet 1/0/3, and configure the interface to run OSPFv3 process 2 in Area 0.
Page 185 [PE2-ospfv3-2] import-route direct [PE2-ospfv3-2] area 0 [PE2-ospfv3-2-area-0.0.0.0] quit [PE2] ospfv3 3 vpn-instance b [PE2-ospfv3-3] router-id 3.3.3.3 [PE2-ospfv3-3] import-route bgp4+ [PE2-ospfv3-3] import-route direct [PE2-ospfv3-3] area 0 [PE2-ospfv3-3-area-0.0.0.0] quit [PE2-ospfv3-3] quit Configure PE 3: # Configure a global RD, and enable IP multicast routing on the public network. <PE3>...
Page 186 # Enable IPv6 multicast routing for VPN instance b. [PE3] ipv6 multicast routing vpn-instance b [PE3-mrib6-b] quit # Create an MD for VPN instance b. [PE3] multicast-domain vpn-instance b # Create an MD IPv6 address family for VPN instance b. [PE3-md-b] address-family ipv6 # Specify the default-group, the MD source interface, and the data-group range for VPN instance b.
Page 187 [PE3] interface loopback 2 [PE3-LoopBack2] ipv6 binding vpn-instance b [PE3-LoopBack2] ip address 33:33:33::33 128 # Enable IPv6 PIM-SM on Loopback 2, and configure the interface to run OSPFv3 process 3 in Area 0. [PE3-LoopBack2] ipv6 pim sm [PE3-LoopBack2] ospfv3 3 area 0.0.0.0 [PE3-LoopBack2] quit # Configure Loopback 2 as a C-BSR and a C-RP.
Page 188 [PE3-ospfv3-2-area-0.0.0.0] quit [PE3-ospfv3-2] quit [PE3] ospfv3 3 vpn-instance b [PE3-ospfv3-3] router-id 5.5.5.5 [PE3-ospfv3-3] import-route bgp4+ [PE3-ospfv3-3] import-route direct [PE3-ospfv3-3] area 0 [PE3-ospfv3-3-area-0.0.0.0] quit [PE3-ospfv3-3] quit Configure P: # Enable IP multicast routing on the public network. <P> system-view [P] multicast routing [P-mrib] quit # Configure an LSR ID, and enable LDP globally.
Page 189 # Configure Loopback 1 as a C-BSR and a C-RP. [P] pim [P-pim] c-bsr 2.2.2.2 [P-pim] c-rp 2.2.2.2 [P-pim] quit # Configure OSPF. [P] ospf 1 [P-ospf-1] area 0.0.0.0 [P-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0 [P-ospf-1-area-0.0.0.0] network 192.168.6.0 0.0.0.255 [P-ospf-1-area-0.0.0.0] network 192.168.7.0 0.0.0.255 [P-ospf-1-area-0.0.0.0] network 192.168.8.0 0.0.0.255 Configure CE a1: # Enable IPv6 multicast routing.
Page 190 [CEb1-GigabitEthernet1/0/1] ipv6 pim sm [CEb1-GigabitEthernet1/0/1] ospfv3 3 area 0.0.0.0 [CEb1-GigabitEthernet1/0/1] quit # Assign an IPv6 address to GigabitEthernet 1/0/2. [CEb1] interface gigabitethernet 1/0/2 [CEb1-GigabitEthernet1/0/2] ipv6 address 10:110:3::2 64 # Enable IPv6 PIM-SM on GigabitEthernet 1/0/2, and configure the interface to run OSPFv3 process 3 in Area 0.
Page 191 # Configure Loopback 1 to run OSPFv3 process 2 in Area 0, and enable IPv6 PIM-SM on the interface. [CEa2-LoopBack1] ospfv3 2 area 0.0.0.0 [CEa2-LoopBack1] ipv6 pim sm [CEa2-LoopBack1] quit # Configure Loopback 1 as a C-BSR and a C-RP. [CEa2] ipv6 pim [CEa2-pim6] c-bsr 22:22:22::22 [CEa2-pim6] c-rp 22:22:22::22...
Page 192 [CEa3-ospfv3-2-area-0.0.0.0] quit Configure CE b2: # Enable IPv6 multicast routing. <CEb2> system-view [CEb2] ipv6 multicast routing [CEb2-mrib6] quit # Assign an IPv6 address to GigabitEthernet 1/0/1. [CEb2] interface gigabitethernet 1/0/1 [CEb2-GigabitEthernet1/0/1] ipv6 address 10:110:11::1 64 # Configure GigabitEthernet 1/0/1 to run OSPFv3 process 3 in Area 0, and enable MLD on the interface.
Page 193: Md Vpn Inter-As Option B Configuration Example
MD VPN inter-AS option B configuration example Network requirements As shown in Figure 64, configure MD VPN inter-AS option B to meet the following requirements: Item Network requirements • In VPN instance a, S 1 is a multicast source, and R 2 is a receiver. •...
Page 194 Figure 64 Network diagram Table 19 Interface and IP address assignment Devic Device Interface IP address Interface IP address — 12.1.1.100/24 — 12.4.1.100/24 — 12.2.1.100/24 — 12.3.1.100/24 PE 1 GE1/0/1 10.1.1.1/24 PE 3 GE1/0/1 10.4.1.1/24 PE 1 GE1/0/2 11.1.1.1/24 PE 3 GE1/0/2 10.3.1.2/24 PE 1...
Page 195 # Configure a global router ID, and enable IP multicast routing on the public network. <PE1> system-view [PE1] router id 1.1.1.1 [PE1] multicast routing [PE1-mrib] quit # Configure an LSR ID, and enable LDP globally. [PE1] mpls lsr-id 1.1.1.1 [PE1] mpls ldp [PE1-ldp] quit # Create a VPN instance named a, and configure the RD and route targets for the VPN instance.
Page 196 [PE1-md-b-ipv4] default-group 232.3.3.3 [PE1-md-b-ivp4] source loopback 1 [PE1-md-b-ipv4] data-group 232.4.4.0 28 [PE1-md-b-ipv4] quit [PE1-md-b] quit # Assign an IP address to GigabitEthernet 1/0/1. [PE1] interface gigabitethernet 1/0/1 [PE1-GigabitEthernet1/0/1] ip address 10.1.1.1 24 # Enable PIM-SM, MPLS, and IPv4 LDP on GigabitEthernet 1/0/1. [PE1-GigabitEthernet1/0/1] pim sm [PE1-GigabitEthernet1/0/1] mpls enable [PE1-GigabitEthernet1/0/1] mpls ldp enable...
Page 197 [PE1–bgp-default] address-family vpnv4 [PE1–bgp-default-vpnv4] peer 2.2.2.2 enable [PE1–bgp-default-vpnv4] quit [PE1-bgp-default] address-family ipv4 mdt [PE1-bgp-default-mdt] peer 2.2.2.2 enable [PE1-bgp-default-mdt] quit [PE1–bgp-default] quit # Configure OSPF. [PE1] ospf 1 [PE1-ospf-1] area 0.0.0.0 [PE1-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0 [PE1-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [PE1-ospf-1-area-0.0.0.0] quit [PE1-ospf-1] quit # Configure OSPF.
Page 198 [PE2-GigabitEthernet1/0/2] pim sm [PE2-GigabitEthernet1/0/2] mpls enable [PE2-GigabitEthernet1/0/2] quit # Assign an IP address to Loopback 1, and enable PIM-SM on the interface. [PE2] interface loopback 1 [PE2-LoopBack1] ip address 2.2.2.2 32 [PE2-LoopBack1] pim sm [PE2-LoopBack1] quit # Configure BGP. [PE2] bgp 100 [PE2-bgp-default] group 1.1.1.1 as-number 100 [PE2-bgp-default] peer 1.1.1.1 connect-interface loopback 1 [PE2-bgp-default] peer 10.3.1.2 as-number 200...
Page 199 # Assign an IP address to GigabitEthernet 1/0/2. [PE3] interface gigabitethernet 1/0/2 [PE3-GigabitEthernet1/0/2] ip address 10.3.1.2 24 # Enable PIM-SM and MPLS on GigabitEthernet 1/0/2. [PE3-GigabitEthernet1/0/2] pim sm [PE3-GigabitEthernet1/0/2] mpls enable [PE3-GigabitEthernet1/0/2] quit # Assign an IP address to Loopback 1, and enable PIM-SM on the interface. [PE3] interface loopback 1 [PE3-LoopBack1] ip address 3.3.3.3 32 [PE3-LoopBack1] pim sm...
Page 200 [PE4-vpn-instance-a] vpn-target 100:1 export-extcommunity [PE4-vpn-instance-a] vpn-target 100:1 import-extcommunity [PE4-vpn-instance-a] quit # Enable IP multicast routing and RPF vector for VPN instance a. [PE4] multicast routing vpn-instance a [PE4-mrib-a] rpf proxy vector [PE4-mrib-a] quit # Create an MD for VPN instance a. [PE4] multicast-domain vpn-instance a # Create an MD IPv4 address family for VPN instance a.
Page 201 # Associate GigabitEthernet 1/0/2 with VPN instance a. [PE4] interface gigabitethernet 1/0/2 [PE4-GigabitEthernet1/0/2] ip binding vpn-instance a # Assign an IP address to GigabitEthernet 1/0/2, and enable PIM-SM on the interface. [PE4-GigabitEthernet1/0/2] ip address 11.3.1.1 24 [PE4-GigabitEthernet1/0/2] pim sm [PE4-GigabitEthernet1/0/2] quit # Associate GigabitEthernet 1/0/3 with VPN instance b.
Page 202 [PE4-ospf-1] quit [PE4] ospf 2 vpn-instance a [PE4-ospf-2] area 0.0.0.0 [PE4-ospf-2-area-0.0.0.0] network 11.3.1.0 0.0.0.255 [PE4-ospf-2-area-0.0.0.0] quit [PE4-ospf-2] quit [PE4] ospf 3 vpn-instance b [PE4-ospf-3] area 0.0.0.0 [PE4-ospf-3-area-0.0.0.0] network 11.4.1.0 0.0.0.255 [PE4-ospf-3-area-0.0.0.0] quit [PE4-ospf-3] quit Configure P 1: # Enable IP multicast routing on the public network. <P1>...
Page 203 Configure P 2: # Enable IP multicast routing on the public network. <P2> system-view [P2] multicast routing [P2-mrib] quit # Configure an LSR ID, and enable LDP globally. [P2] mpls lsr-id 6.6.6.6 [P2] mpls ldp [P2-ldp] quit # Assign an IP address to GigabitEthernet 1/0/1. [P2] interface gigabitethernet 1/0/1 [P2-GigabitEthernet1/0/1] ip address 10.5.1.1 24 # Enable PIM-SM, MPLS, and IPv4 LDP on GigabitEthernet 1/0/1.
Page 204 [CEa1] interface gigabitethernet 1/0/2 [CEa1-GigabitEthernet1/0/2] ip address 11.1.1.2 24 [CEa1-GigabitEthernet1/0/2] pim sm [CEa1-GigabitEthernet1/0/2] quit # Configure GigabitEthernet 1/0/2 as a C-BSR and a C-RP. [CEa1] pim [CEa1-pim] c-bsr 11.1.1.2 [CEa1-pim] c-rp 11.1.1.2 [CEa1-pim] quit # Configure OSPF. [CEa1] ospf 1 [CEa1-ospf-1] area 0.0.0.0 [CEa1-ospf-1-area-0.0.0.0] network 12.1.1.0 0.0.0.255 [CEa1-ospf-1-area-0.0.0.0] network 11.1.1.0 0.0.0.255...
Page 205 [CEa2-mrib] quit # Assign an IP address to GigabitEthernet 1/0/1, and enable IGMP on the interface. [CEa2] interface gigabitethernet 1/0/1 [CEa2-GigabitEthernet1/0/1] ip address 12.3.1.1 24 [CEa2-GigabitEthernet1/0/1] igmp enable [CEa2-GigabitEthernet1/0/1] quit # Assign an IP address to GigabitEthernet 1/0/2, and enable PIM-SM on the interface. [CEa2] interface gigabitethernet 1/0/2 [CEa2-GigabitEthernet1/0/2] ip address 11.3.1.2 24 [CEa2-GigabitEthernet1/0/2] pim sm...
Page 206: Md Vpn Inter-As Option C Configuration Example
232.3.3.3 1.1.1.1 MTunnel1 # Display information about the remote default-group for IPv4 multicast transmission in each VPN instance on PE 1. [PE1] display multicast-domain default-group remote MD remote default-group information: Group address Source address Next hop VPN instance 232.1.1.1 4.4.4.4 2.2.2.2 232.3.3.3 4.4.4.4...
Page 207 Item Network requirements • Enable IP multicast routing on the public network on PE 1, PE 2, PE 3, and PE 4. • Enable IP multicast routing for VPN instance a on PE 1 and PE 4. IP multicast routing •...
Page 208 Device Interface IP address Device Interface IP address PE 1 GE1/0/3 Loop1 10.11.2.1/24 PE 3 1.1.1.3/32 PE 1 Loop1 1.1.1.1/32 PE 3 Loop2 22.22.22.22/32 PE 2 GE1/0/1 10.10.1.2/24 PE 4 GE1/0/1 10.10.2.2/24 PE 2 GE1/0/2 192.168.1.1/24 PE 4 GE1/0/2 10.11.3.1/24 PE 2 Loop1 GE1/0/3...
Page 209 # Create a VPN instance named b, and configure an RD and route targets for the VPN instance. [PE1] ip vpn-instance b [PE1-vpn-instance-b] route-distinguisher 200:1 [PE1-vpn-instance-b] vpn-target 200:1 export-extcommunity [PE1-vpn-instance-b] vpn-target 200:1 import-extcommunity [PE1-vpn-instance-b] quit # Enable IP multicast routing for VPN instance b. [PE1] multicast routing vpn-instance b [PE1-mrib-b] quit # Create an MD for VPN instance b.
Page 210 # Configure BGP. [PE1] bgp 100 [PE1-bgp-default] group pe1-pe2 internal [PE1-bgp-default] peer pe1-pe2 connect-interface loopback 1 [PE1-bgp-default] peer 1.1.1.2 group pe1-pe2 [PE1-bgp-default] group pe1-pe4 external [PE1-bgp-default] peer pe1-pe4 as-number 200 [PE1-bgp-default] peer pe1-pe4 ebgp-max-hop 255 [PE1-bgp-default] peer pe1-pe4 connect-interface loopback 1 [PE1-bgp-default] peer 1.1.1.4 group pe1-pe4 [PE1–bgp-default] ip vpn-instance a [PE1-bgp-default-a] address-family ipv4...
Page 211 [PE1-ospf-3] quit Configure PE 2: # Configure a global router ID, and enable IP multicast routing on the public network. <PE2> system-view [PE2] router id 1.1.1.2 [PE2] multicast routing [PE2-mrib] quit # Configure an LSR ID, and enable LDP globally. [PE2] mpls lsr-id 1.1.1.2 [PE2] mpls ldp [PE2-mpls-ldp] quit...
Page 212 [PE2-msdp] encap-data-enable [PE2-msdp] peer 1.1.1.3 connect-interface loopback 1 # Configure a static route. [PE2] ip route-static 1.1.1.3 32 gigabitethernet 1/0/2 192.168.1.2 # Configure BGP. [PE2] bgp 100 [PE2-bgp-default] group pe2-pe1 internal [PE2-bgp-default] peer pe2-pe1 connect-interface loopback 1 [PE2-bgp-default] peer 1.1.1.1 group pe2-pe1 [PE2-bgp-default] group pe2-pe3 external [PE2-bgp-default] peer pe2-pe3 as-number 200 [PE2-bgp-default] peer pe2-pe3 connect-interface loopback 1...
Page 213 [PE3-GigabitEthernet1/0/1] quit # Assign an IP address to GigabitEthernet 1/0/2. [PE3] interface gigabitethernet 1/0/2 [PE3-GigabitEthernet1/0/2] ip address 192.168.1.2 24 # Enable PIM-SM and MPLS on GigabitEthernet 1/0/2. [PE3-GigabitEthernet1/0/2] pim sm [PE3-GigabitEthernet1/0/2] mpls enable [PE3-GigabitEthernet1/0/2] quit # Assign an IP address to Loopback 1, and enable PIM-SM on the interface. [PE3] interface loopback 1 [PE3-LoopBack1] ip address 1.1.1.3 32 [PE3-LoopBack1] pim sm...
Page 214 [PE3-bgp-default-ipv4] peer pe3-pe2 route-policy map1 export [PE3-bgp-default-ipv4] peer pe3-pe2 label-route-capability [PE3-bgp-default-ipv4] import-route ospf 1 [PE3-bgp-default-ipv4] quit [PE3–bgp-default] quit # Configure OSPF. [PE3] ospf 1 [PE3-ospf-1] area 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 1.1.1.3 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 22.22.22.22 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 10.10.2.0 0.0.0.255 [PE3-ospf-1-area-0.0.0.0] quit [PE3-ospf-1] quit Configure PE 4: # Configure a global router ID, and enable IP multicast routing on the public network.
Page 215 [PE4-vpn-instance-b] quit # Enable IP multicast routing for VPN instance b. [PE4] multicast routing vpn-instance b [PE4-mrib-b] quit # Create an MD for VPN instance b. [PE4] multicast-domain vpn-instance b # Create an MD IPv4 address family for VPN instance b. [PE4-md-b] address-family ipv4 # Specify the default-group, MD source interface, and the data-group range for VPN instance b.
Page 216 [PE4-bgp-default] peer pe4-pe1 as-number 100 [PE4-bgp-default] peer pe4-pe1 ebgp-max-hop 255 [PE4-bgp-default] peer pe4-pe1 connect-interface loopback 1 [PE4-bgp-default] peer 1.1.1.1 group pe4-pe1 [PE4–bgp-default] ip vpn-instance a [PE4-bgp-default-a] address-family ipv4 [PE4-bgp-default-ipv4-a] import-route ospf 2 [PE4-bgp-default-ipv4-a] import-route direct [PE4-bgp-default-ipv4-a] quit [PE4-bgp-default-a] quit [PE4–bgp-default] ip vpn-instance b [PE4-bgp-default-b] address-family ipv4 [PE4-bgp-default-ipv4-b] import-route ospf 3 [PE4-bgp-default-ipv4-b] import-route direct...
Page 217 # Assign an IP address to GigabitEthernet 1/0/1, and enable PIM-SM on the interface. [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 # Assign an IP address to GigabitEthernet 1/0/2, and enable PIM-SM on the interface. [CEa1] interface gigabitethernet 1/0/2 [CEa1-GigabitEthernet1/0/2] ip address 10.11.1.2 24 [CEa1-GigabitEthernet1/0/2] pim sm...
Page 218 [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 [CEa2-mrib] quit # Assign an IP address to GigabitEthernet 1/0/1, and enable IGMP on the interface. [CEa2] interface gigabitethernet 1/0/1 [CEa2-GigabitEthernet1/0/1] ip address 10.11.7.1 24 [CEa2-GigabitEthernet1/0/1] igmp enable [CEa2-GigabitEthernet1/0/1] quit # Assign an IP address to GigabitEthernet 1/0/2, and enable PIM-SM on the interface.
Page 219: Troubleshooting Md Vpn
[CEb2-pim] c-rp 3.3.3.3 [CEb2-pim] quit # Configure OSPF. [CEb2] ospf 1 [CEb2-ospf-1] area 0.0.0.0 [CEb2-ospf-1-area-0.0.0.0] network 3.3.3.3 0.0.0.0 [CEb2-ospf-1-area-0.0.0.0] network 10.11.4.0 0.0.0.255 [CEb2-ospf-1-area-0.0.0.0] network 10.11.8.0 0.0.0.255 [CEb2-ospf-1-area-0.0.0.0] quit [CEb2-ospf-1] quit Verifying the configuration # Display information about the local default-group for IPv4 multicast transmission in each VPN instance on PE 1.
Page 220: An Mvrf Cannot Be Created
Use the display bgp peer command to verify that the BGP peer connections have been correctly configured. If the problem persists, contact Hewlett Packard Enterprise Support. An MVRF cannot be created Symptom A VPN instance cannot create an MVRF correctly. Solution To resolve the problem: Use the display pim bsr-info command to verify that the BSR information exists on the public...
Page 221: Configuring Ipv6 Multicast Routing And Forwarding
Configuring IPv6 multicast routing and forwarding Overview IPv6 multicast routing and forwarding uses the following tables: • IPv6 multicast protocols' routing tables, such as the IPv6 PIM routing table. • General IPv6 multicast routing table that summarizes the multicast routing information generated by different IPv6 multicast routing protocols.
Page 222 the incoming interface of the (S, G) entry. After the router receives another (S, G) packet, it looks up its IPv6 multicast forwarding table for a matching (S, G) entry: • If no match is found, the router first determines the RPF route back to the packet source. Then, it creates a forwarding entry with the RPF interface as the incoming interface and performs one of the following tasks: If the receiving interface is the RPF interface, the RPF check succeeds and the router...
Page 223: Ipv6 Multicast Forwarding Across Ipv6 Unicast Subnets
• If an IPv6 multicast packet arrives at Router C on GigabitEthernet 1/0/1, the receiving interface is not the incoming interface of the (S, G) entry. Router C searches its IPv6 unicast routing table and finds that the outgoing interface to the source (the RPF interface) is GigabitEthernet 1/0/2. This means that the (S, G) entry is correct but the packet traveled along a wrong path.
Page 224: Configuring Ipv6 Multicast Routing And Forwarding
Step Command Remarks Enter system view. system-view Enable IPv6 multicast ipv6 multicast routing By default, IPv6 multicast routing routing and enter IPv6 MRIB [ vpn-instance is disabled. view. vpn-instance-name ] Configuring IPv6 multicast routing and forwarding Before you configure IPv6 multicast routing and forwarding, complete the following tasks: •...
Page 225: Configuring An Ipv6 Multicast Forwarding Boundary
Configuring an IPv6 multicast forwarding boundary You can configure an interface as an IPv6 multicast forwarding boundary for an IPv6 multicast group range. The interface cannot receive or forward IPv6 multicast packets for the groups in the range. TIP: You do not need to enable IPv6 multicast routing before this configuration. To configure an IPv6 multicast forwarding boundary: Step Command...
Page 226: Displaying And Maintaining Ipv6 Multicast Routing And Forwarding
Step Command Remarks reset ipv6 multicast [ vpn-instance vpn-instance-name ] routing-table { { ipv6-source-address Delete all IPv6 multicast [ prefix-length ] | forwarding entries. ipv6-group-address [ prefix-length ] | incoming-interface interface-type interface-number } * | all } Displaying and maintaining IPv6 multicast routing and forwarding CAUTION: The reset commands might cause IPv6 multicast data transmission failures.
Page 227 Task Command display ipv6 multicast [ vpn-instance vpn-instance-name ] forwarding-table [ ipv6-source-address [ prefix-length ] | ipv6-group-address [ prefix-length ] | incoming-interface Display IPv6 multicast forwarding entries (in IRF mode). interface-type interface-number | outgoing-interface { exclude | include | match } interface-type interface-number | slot slot-number | statistics ] * Display information about the DF list in display ipv6 multicast [ vpn-instance vpn-instance-name ]...
Page 228: Ipv6 Multicast Routing And Forwarding Configuration Examples
IPv6 multicast routing and forwarding configuration examples IPv6 multicast forwarding over a GRE tunnel Network requirements As shown in Figure • IPv6 multicast routing and IPv6 PIM-DM are enabled on Router A and Router C. • Router B does not support IPv6 multicast. •...
Page 229 [RouterC-Tunnel0] ipv6 address 5001::2 64 [RouterC-Tunnel0] source 3001::2 [RouterC-Tunnel0] destination 2001::1 [RouterC-Tunnel0] quit Enable IPv6 multicast routing, IPv6 PIM-DM, and MLD: # On Router A, enable IPv6 multicast routing, and enable IPv6 PIM-DM on each interface. [RouterA] ipv6 multicast routing [RouterA-mrib6] quit [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] ipv6 pim dm...
Page 230: Ipv6 Multicast Forwarding Over Advpn Tunnel Interfaces
Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet1/0/1 Protocol: mld, UpTime: 00:04:25, Expires: - (1001::100, FF1E::101) Protocol: pim-dm, Flag: ACT UpTime: 00:06:14 Upstream interface: Tunnel0 Upstream neighbor: FE80::A01:101:1 RPF prime neighbor: FE80::A01:101:1 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet1/0/1 Protocol: pim-dm, UpTime: 00:04:25, Expires: - The output shows the following information:...
Page 231 Figure 69 Network diagram Table 21 Interface and IPv6 address assignment Device Interface IPv6 address Device Interface IPv6 address Hub 1 GE1/0/1 1::1/64 Spoke 1 GE1/0/1 1::3/64 192:168::1/64 192:168::3/64 Hub 1 Tunnel1 Spoke 1 Tunnel1 FE80::1 FE80::3 Hub 1 Loop0 44::44/64 Spoke 1 GE1/0/2...
Page 232 # Configure the VAM server not to authenticate VAM clients. [Server-vam-server-domain-abc] authentication-method none # Enable the VAM server. [Server-vam-server-domain-abc] server enable # Create hub group 0. [Server-vam-server-domain-abc] hub-group 0 # Specify private IPv6 addresses for hubs in hub group 0. [Server-vam-server-domain-abc-hub-group-0] hub ipv6 private-address 192:168::1 [Server-vam-server-domain-abc-hub-group-0] hub ipv6 private-address 192:168::2 # Specify a private IPv6 address range for spokes in hub group 0.
Page 233 # Set the pre-shared key to 123456. [Spoke1-vam-client-Spoke1] pre-shared-key simple 123456 # Enable the VAM client. [Spoke1-vam-client-Spoke1] client enable [Spoke1-vam-client-Spoke1] quit e. Configure Spoke 2: # Create a VAM client named Spoke2. <Spoke2> system-view [Spoke2] vam client name Spoke2 # Specify ADVPN domain abc for the VAM client. [Spoke2-vam-client-Spoke2] advpn-domain abc # Specify the VAM server.
Page 234 [Spoke2-Tunnel1] quit Configure OSPFv3: # On Hub 1, configure OSPFv3. <Hub1> system-view [Hub1] ospfv3 [Hub1-ospfv3-1] router-id 0.0.0.1 [Hub1-ospfv3-1] area 0.0.0.0 [Hub1-ospfv3-1-area-0.0.0.0] quit [Hub1-ospfv3-1] quit [Hub1] interface loopback 0 [Hub1-LoopBack0] ospfv3 1 area 0.0.0.0 [Hub1-LoopBack0] quit [Hub1] interface gigabitethernet 1/0/2 [Hub1-GigabitEthernet1/0/2] ospfv3 1 area 0.0.0.0 [Hub1-GigabitEthernet1/0/2] quit [Hub1] interface tunnel 1 [Hub1-Tunnel1] ospfv3 1 area 0.0.0.0...
Page 235 [Spoke2-ospfv3-1] area 0.0.0.0 [Spoke2-ospfv3-1-area-0.0.0.0] quit [Spoke2-ospfv3-1] quit [Spoke2] interface tunnel 1 [Spoke2-Tunnel1] ospfv3 1 area 0.0.0.0 [Spoke2-Tunnel1] ospfv3 network-type p2mp [Spoke2-Tunnel1] quit [Spoke2] interface gigabitethernet 1/0/2 [Spoke2-GigabitEthernet1/0/2] ospfv3 1 area 0.0.0.0 [Spoke2-GigabitEthernet1/0/2] quit Configure IPv6 multicast: a. Configure Hub 1: # Enable IPv6 multicast routing.
Page 236 [Hub2-Tunnel1] quit # Configure Loopback 0 as a C-BSR and a C-RP. <Hub2>system-view [Hub2] ipv6 pim [Hub2-pim6] c-bsr 55::55 [Hub2-pim6] c-rp 55::55 [Hub2-pim6] quit c. Configure Spoke 1: # Enable IPv6 multicast routing. <Spoke1> system-view [Spoke1] ipv6 multicast routing [Spoke1-mrib6] quit # Enable IPv6 PIM-SM and NBMA mode on Tunnel interface tunnel1.
Page 237 1: Tunnel1, FE80::3 Protocol: pim-sm, UpTime: 17:01:23, Expires: 00:02:41 (100::1, FF0E::1) RP: 44::44 (local) Protocol: pim-sm, Flag: SPT LOC ACT UpTime: 00:00:02 Upstream interface: GigabitEthernet1/0/3 Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface information: Total number of downstream interfacs: 1 1: Tunnel1, FE80::3 Protocol: pim-sm, UpTime: 00:00:02, Expires: 00:03:28 The output show that Tunnel interface tunnel1 (FE80::3) on Spoke 1 will receive the IPv6 multicast...
Page 238: Configuring Mld
Configuring MLD Overview Multicast Listener Discovery (MLD) establishes and maintains IPv6 multicast group memberships between a Layer 3 multicast device and the hosts on the directly connected subnet. MLD has the following versions: • MLDv1 (defined by RFC 2710), which is derived from IGMPv2. •...
Page 239 Joining an IPv6 multicast group Figure 70 MLD queries and reports As shown in Figure 70, Host B and Host C want to receive the IPv6 multicast data addressed to IPv6 multicast group G1. Host A wants to receive the IPv6 multicast data addressed to G2. The following process describes how the hosts join the IPv6 multicast groups and how the MLD querier (Router B Figure 70) maintains the IPv6 multicast group memberships:...
Page 240: Mldv2 Enhancements
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 IPv6 multicast addresses queried include both the destination address field and the group address field of the message.
Page 241: Mld Ssm Mapping
• Filter mode—Router keeps tracing the Include or Exclude state. • List of sources—Router keeps tracing the newly added or deleted IPv6 multicast source. • Timers—Filter timers, which include the time that the router waits before switching to the Include mode after an IPv6 multicast address times out, and source timers for source recording. MLD SSM mapping An MLDv2 host can explicitly specify multicast sources in its MLDv2 reports.
Page 242: Mld Proxying
MLD proxying As shown in Figure 73, in a simple tree-shaped topology, it is not necessary to configure IPv6 multicast routing protocols, such as IPv6 PIM, on edge devices. Instead, you can configure MLD proxying on these devices. With MLD proxying configured, the edge device acts as an MLD proxy: •...
Page 243: Mld Support For Vpns
MLD support for VPNs MLD maintains group memberships on a per-interface basis. After receiving an MLD message on an interface, MLD processes the packet within the VPN to which the interface belongs. MLD only communicates with other multicast protocols within the same VPN instance. Protocols and standards •...
Page 244: Enabling Mld
Enabling MLD Perform this task on interfaces where IPv6 multicast group memberships are created and maintained. To enable MLD: Step Command Remarks Enter system view. system-view Enable IPv6 multicast By default, IPv6 multicast routing ipv6 multicast routing routing and enter IPv6 [ vpn-instance vpn-instance-name ] is disabled.
Page 245: Configuring An Ipv6 Multicast Group Policy
Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, the interface is not a mld static-group Configure a static group ipv6-group-address [ source static group member of any IPv6 member. ipv6-source-address ] multicast groups. Configuring an IPv6 multicast group policy This feature enables an interface to filter MLD reports by using an ACL that specifies IPv6 multicast groups and the optional sources.
Page 246 interval at which a querier sends multicast-address-and-source-specific queries after receiving a report that changes IPv6 multicast source and group mappings. • MLD last listener query count—In MLDv1, it sets the number of multicast-address-specific queries that the querier sends after receiving a done message. In MLDv2, it sets the number of multicast-address-and-source-specific queries that the querier sends after receiving a report that changes IPv6 multicast group and source mappings.
Page 247: Enabling Fast-Leave Processing
Step Command Remarks Set the maximum response By default, the maximum time for MLD general response time for MLD general max-response-time time queries. queries is 10 seconds. By default, the MLD other querier present timer is calculated by using the following formula: 10.
Page 248: Configuring Mld Ssm Mappings
Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Enable fast-leave mld fast-leave [ group-policy By default, fast-leave processing processing. ipv6-acl-number ] is disabled. Configuring MLD SSM mappings This feature enables the device to provide SSM services for MLDv1 hosts. This feature does not process MLDv2 messages.
Page 249: Enabling Mld Proxying
Enabling MLD proxying When you enable MLD proxying, follow these restrictions and guidelines: • You must enable MLD proxying on the receiver-side interfaces. • On an interface enabled with MLD proxying, only the mld version command takes effect and other MLD commands do not take effect. •...
Page 250: Configuring Ipv6 Multicast Access Control
To enable IPv6 multicast load splitting on an MLD proxy: Step Command Remarks Enter system view. system-view mld [ vpn-instance Enter MLD view. vpn-instance-name ] By default, IPv6 multicast load splitting is disabled on an MLD Enable IPv6 multicast load proxy, and only the proxy proxy multipath splitting on an MLD proxy.
Page 251: Enabling Per-Session Ipv6 Multicast Forwarding
If you specify both an IPv6 multicast group list and a user access policy, a user can join an IPv6 multicast group that meets either of them. To configure an MLD user access policy: Step Command Remarks Enter system view. system-view For more information about Enter ISP domain view.
Page 252: Configuring A Vlan-Based Static Group Member
Step Command Remarks Enter Layer 3 Ethernet interface view, Layer 3 interface interface-type Ethernet subinterface view, { interface-number | Layer 3 aggregate interface interface-number.subnumber } view, or Layer 3 aggregate subinterface view. By default, per-session IPv6 Enable per-session IPv6 multicast forwarding is mld join-by-session multicast forwarding.
Page 253: Displaying And Maintaining Mld
Displaying and maintaining MLD CAUTION: The reset mld group command might cause IPv6 multicast data transmission failures. Execute display commands in any view and reset commands in user view. Task Command display mld [ vpn-instance vpn-instance-name ] group Display information about MLD multicast [ ipv6-group-address | interface interface-type groups.
Page 254 Figure 74 Network diagram Receiver IPv6 PIM-DM Host A GE1/0/1 3000::12/64 Router A Host B Querier GE1/0/1 3001::10/64 Receiver Host C Router B GE1/0/1 3001::12/64 Host D Router C Configuration procedure Assign an IPv6 address and prefix length to each interface, as shown in Figure 74.
Page 255: Mld Ssm Mapping Configuration Example
[RouterB-GigabitEthernet1/0/2] quit # On Router C, enable IPv6 multicast routing. <RouterC> system-view [RouterC] ipv6 multicast routing [RouterC-mrib6] quit # Enable MLD on GigabitEthernet 1/0/1. [RouterC] interface gigabitethernet 1/0/1 [RouterC-GigabitEthernet1/0/1] mld enable [RouterC-GigabitEthernet1/0/1] quit # Enable IPv6 PIM-DM on GigabitEthernet 1/0/2. [RouterC] interface gigabitethernet 1/0/2 [RouterC-GigabitEthernet1/0/2] ipv6 pim dm [RouterC-GigabitEthernet1/0/2] quit...
Page 256 Figure 75 Network diagram Source 2 Source 3 Router B Router C GE1/0/1 GE1/0/3 GE1/0/3 GE1/0/1 GE1/0/2 GE1/0/2 IPv6 PIM-SM Source 1 Receiver GE1/0/2 GE1/0/2 GE1/0/1 GE1/0/3 GE1/0/3 GE1/0/1 Router A Router D Table 22 Interface and IPv6 address assignment Device Interface IPv6 address...
Page 257 <RouterA> system-view [RouterA] ipv6 multicast routing [RouterA-mrib6] quit # Enable IPv6 PIM-SM on each interface. [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] ipv6 pim sm [RouterA-GigabitEthernet1/0/1] quit [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] ipv6 pim sm [RouterA-GigabitEthernet1/0/2] quit [RouterA] interface gigabitethernet 1/0/3 [RouterA-GigabitEthernet1/0/3] ipv6 pim sm [RouterA-GigabitEthernet1/0/3] quit # Configure Router B and Router C in the same way Router A is configured.
Page 258: Mld Proxying Configuration Example
Group address: FF3E::101 Last reporter: FE80::1 Uptime: 00:02:04 Expires: Off # Display IPv6 PIM routing entries on Router D. [RouterD] display ipv6 pim routing-table Total 0 (*, G) entry; 2 (S, G) entry (1001::1, FF3E::101) RP: 1003::2 Protocol: pim-ssm, Flag: UpTime: 00:13:25 Upstream interface: GigabitEthernet1/0/3 Upstream neighbor: 1003::1...
Page 259 Figure 76 Network diagram Configuration procedure Assign an IPv6 address and prefix length to each interface, as shown in Figure 76. (Details not shown.) Enable IPv6 multicast routing, IPv6 PIM-DM, MLD, and MLD proxying: # On Router A, enable IPv6 multicast routing. <RouterA>...
Page 260: Ipv6 Multicast Access Control Configuration Example (For Pppoe)
GigabitEthernet1/0/1(FE80::16:1): MLD proxy group records in total: 1 Group address: FF3E::101 Member state: Delay Expires: 00:00:02 IPv6 multicast access control configuration example (for PPPoE) As shown in Figure • OSPF runs in the PIM-SM domain. • Source 1, Source 2, and Source 3 send IPv6 multicast data to IPv6 multicast groups FF1E::101, FF1E::102, and FF1E::103, respectively.
Page 261 Table 23 Interface and IPv6 address assignment Device Interface IPv6 address Device Interface IPv6 address Source 1 — 1001::1/64 Host A 3001::2/64 — Source 2 — 1002::1/64 Host B 3001::3/64 — Source 3 — 1003::1/64 Host C 3002::2/64 — RADIUS —...
Page 262 # Configure Router C and Router D in the same way Router B is configured. (Details not shown.) # On Router A, configure GigabitEthernet 1/0/2 as a C-BSR and a C-RP. [RouterA] ipv6 pim [RouterA-pim6] c-bsr 2002::1 [RouterA-pim6] c-rp 2002::1 [RouterA-pim6] quit Configure the access service on the BRAS: # Configure Router A as the RADIUS client.
Page 263 [RouterA-Virtual-Template2] quit # Configure GigabitEthernet 1/0/5.1 to terminate VLAN-tagged packets whose outer VLAN ID is 1 and inner VLAN ID is in the range of 1 to 100. [RouterA] interface gigabitethernet 1/0/5.1 [RouterA-GigabitEthernet1/0/5.1] vlan-type dot1q vid 1 second-dot1q 1 to 100 # Bind GigabitEthernet 1/0/5.1 to interface Virtual-Template 1.
Page 264: Ipv6 Multicast Access Control Configuration Example (For Ipoe)
[RouterA-isp-isp2] quit Verifying the configuration # Display authorized MLD user information on Router A after Host A and Host C log in. [RouterA] display mld user-authorization Authorized users in total: 2 User name: user1@isp1 Access type: PPP Interface: Virtual-Access0 Access interface: Virtual-Access0 Maximum programs for order: 10 User profile: profile1 Authorized programs list:...
Page 265 Figure 78 Network diagram Source 1 Source 2 Source 3 GE1/0/2 GE1/0/2 GE1/0/2 Router C GE1/0/1 Router B Router D RADIUS server GE1/0/4 BRAS Router A IPv6 PIM-SM ISP 1 ISP 2 Access Access network network Host A Host B Host C Host D User1@ISP1...
Page 266 Enable IPv6 multicast routing, and configure IPv6 PIM-SM: # On Router A, enable IPv6 multicast routing. <RouterA> system-view [RouterA] ipv6 multicast routing [RouterA-mrib6] quit # Enable IPv6 PIM-SM on GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3. [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] ipv6 pim sm [RouterA-GigabitEthernet1/0/1] quit [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] ipv6 pim sm...
Page 267 [RouterA-isp-isp1] authorization ipoe radius-scheme spec [RouterA-isp-isp1] accounting ipoe radius-scheme spec [RouterA-isp-isp1] quit # Create an ISP domain named isp2, and specify the STB service for users in the ISP domain. [RouterA] domain isp2 [RouterA-isp-isp2] service-type stb # Configure AAA methods for ISP domain isp2. [RouterA-isp-isp2] authentication ipoe radius-scheme spec [RouterA-isp-isp2] authorization ipoe radius-scheme spec [RouterA-isp-isp2] accounting ipoe radius-scheme spec...
Page 268 [RouterA-GigabitEthernet1/0/5.2] quit Configure IPv6 multicast access control on the BRAS: # Enable MLD on GigabitEthernet 1/0/5.1. [RouterA] interface gigabitethernet 1/0/5.1 [RouterA-GigabitEthernet1/0/5.1] mld enable # Enable IPv6 multicast access control on GigabitEthernet 1/0/5.1. [RouterA-GigabitEthernet1/0/5.1] mld authorization-enable # Enable per-session IPv6 multicast forwarding on GigabitEthernet 1/0/5.1. [RouterA-GigabitEthernet1/0/5.1] mld join-by-session [RouterA-GigabitEthernet1/0/5.1] quit # Configure GigabitEthernet 1/0/5.2 in the same way GigabitEthernet 1/0/5.1 is configured.
Page 269: Ipv6 Multicast Access Control Configuration Example (For Portal)
VLAN ID: 1 Second VLAN ID: 2 Maximum programs for order: 10 User profile: profile1 Authorized programs list: User name: user1@isp2 Access type: IPoE Interface: Multicast-UA2 Access interface: GigabitEthernet1/0/5.2 VLAN ID: 2 Second VLAN ID: 2 Maximum programs for order: 10 User profile: profile2 Authorized programs list: IPv6 multicast access control configuration example (for...
Page 270 Figure 79 Network diagram Source 1 Source 2 Source 3 GE1/0/2 GE1/0/2 GE1/0/2 Router C GE1/0/1 Router B Router D iMC server RADIUS server GE1/0/4 GE1/0/7 BRAS IPv6 PIM-SM Router A ISP 1 ISP 2 Access Access network network Host A Host B Host C Host D...
Page 271 Configure OSPFv3 in the IPv6 PIM-SM domain. (Details not shown.) Enable IPv6 multicast routing, and configure IPv6 PIM-SM: # On Router A, enable IPv6 multicast routing. <RouterA> system-view [RouterA] ipv6 multicast routing [RouterA-mrib6] quit # Enable IPv6 PIM-SM on GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3. [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] ipv6 pim sm [RouterA-GigabitEthernet1/0/1] quit...
Page 272 [RouterA-portal-server-spec] ipv6 2005::2 key simple 123456 [RouterA-portal-websvr-spec] quit # On the RADIUS server, configure the user accounts with the same usernames, passwords, and IPv6 addresses as those on the RADIUS client. (Details not shown.) # On the IMC server, configure the IPv6 address group for users. Specify the next hop of the default route to users as 2005::1, and specify the same passwords and IPv6 addresses for users as those on the IMC client.
Page 273 # Configure GigabitEthernet 1/0/6 in the same way GigabitEthernet 1/0/5 is configured. (Details not shown.) # Configure an access policy in user profile profile1 to authorize MLD users to join IPv6 multicast groups FF03::101 and FF03::102. [RouterA] acl ipv6 basic 2000 [RouterA-acl-ipv6-basic-2000] rule permit source ff1e::101 128 [RouterA-acl-ipv6-basic-2000] rule permit source ff1e::102 128 [RouterA-acl-ipv6-basic-2000] quit...
Page 274: Troubleshooting Mld
Troubleshooting MLD No member information exists on the receiver-side router Symptom When a host sends a message to announce that it is joining IPv6 multicast group G, no member information of multicast group G exists on the immediate router. Solution To resolve the problem: Use the display mld interface command to verify that the networking, interface connections, and IP address configuration are correct.
Page 275: Configuring Ipv6 Pim
Configuring IPv6 PIM Overview IPv6 Protocol Independent Multicast (IPv6 PIM) provides IPv6 multicast forwarding by leveraging IPv6 unicast static routes or IPv6 unicast routing tables generated by any IPv6 unicast routing protocol, such as RIPng, OSPFv3, IPv6 IS-IS, or IPv6 BGP. IPv6 PIM uses the underlying IPv6 unicast routing to generate an IPv6 multicast routing table without relying on any particular IPv6 unicast routing protocol.
Page 276 The nodes without downstream receivers are pruned. A router that has no downstream receivers multicasts a prune message to all IPv6 PIM routers on the subnet. When the upstream node receives the prune message, it removes the receiving interface from the (S, G) entry.
Page 277: Ipv6 Pim-Sm Overview
Figure 81 Assert mechanism As shown in Figure 81, after Router A and Router B receive an (S, G) packet from the upstream node, they both forward the packet to the local subnet. As a result, the downstream node Router C receives two identical multicast packets.
Page 278 IMPORTANT: MLD must be enabled on the device that acts as the receiver-side DR. Otherwise, the receiver hosts attached to the DR cannot join any IPv6 multicast groups. For more information about MLD, see "Configuring MLD." Figure 82 DR election As shown in Figure 82, the DR election process is as follows:...
Page 279 As shown in Figure 83, each C-RP periodically unicasts its advertisement messages (C-RP-Adv messages) to the BSR. An advertisement message contains the address of the advertising C-RP and the IPv6 multicast group range to which it is designated. The BSR collects these advertisement messages and organizes the C-RP information into an RP-set, which is a database of mappings between IPv6 multicast groups and RPs.
Page 280 multicast source registers with the closest RP or a receiver-side DR joins the closest RP to implement source information synchronization. Anycast RP has the following benefits: • Optimal RP path—An IPv6 multicast source registers with the closest RP to build an optimal SPT.
Page 281 RPT building Figure 85 RPT building in an IPv6 PIM-SM domain Host A Source Receiver Host B Server Receiver Join message IPv6 multicast packets Host C As shown in Figure 85, the process of building an RPT is as follows: When a receiver wants to join the IPv6 multicast group G, it uses an MLD message to inform the receiver-side DR.
Page 282 Figure 86 IPv6 multicast source registration As shown in Figure 86, the IPv6 multicast source registers with the RP as follows: The IPv6 multicast source S sends the first multicast packet to the IPv6 multicast group G. When receiving the multicast packet, the source-side DR that directly connects to the IPv6 multicast source encapsulates the packet into a register message and unicasts the message to the RP.
Page 283: Ipv6 Bidir-Pim Overview
The RP periodically checks the multicast packet forwarding rate. If the RP finds that the traffic rate exceeds the specified threshold, it sends an (S, G) source-specific join message toward the IPv6 multicast source. The routers along the path from the RP to the IPv6 multicast source constitute an SPT branch.
Page 284 DF election On a subnet with multiple multicast routers, duplicate multicast packets might be forwarded to the RP. To address this issue, IPv6 BIDIR-PIM uses a designated forwarder (DF) election mechanism to elect a unique DF on each subnet. Only the DFs can forward IPv6 multicast data to the RP. DF election is not necessary for an RPL.
Page 285 Figure 88 RPT building at the receiver side As shown in Figure 88, the process for building a receiver-side RPT is the same as the process for building an RPT in IPv6 PIM-SM: When a receiver wants to join the IPv6 multicast group G, it uses an MLD message to inform the directly connected router.
Page 286: Ipv6 Administrative Scoping Overview
Figure 89 RPT building at the IPv6 multicast source side As shown in Figure 89, the process for building a source-side RPT is relatively simple: When an IPv6 multicast source sends multicast packets to the IPv6 multicast group G, the DF in each subnet unconditionally forwards the packets to the RP.
Page 287 BSMs, of these IPv6 multicast groups cannot cross the boundary of the IPv6 admin-scoped zone for the group range. The IPv6 multicast group ranges to which different IPv6 admin-scoped zones are designated can have intersections. However, the IPv6 multicast groups in an IPv6 admin-scoped zone are valid only within its local zone, and theses IPv6 multicast groups are regarded as private group addresses.
Page 288: Ipv6 Pim-Ssm Overview
Figure 91 IPv6 multicast address format An IPv6 admin-scoped zone with a larger scope field value contains an IPv6 admin-scoped zone with a smaller scope field value. The zone with the scope field value of E is the IPv6 global-scoped zone. Table 26 lists the possible values of the scope field.
Page 289: Relationship Among Ipv6 Pim Protocols
SPT building The decision to build an RPT for IPv6 PIM-SM or an SPT for IPv6 PIM-SSM depends on whether the IPv6 multicast group that the receiver host joins is in the IPv6 SSM group range. The IPv6 SSM group range reserved by IANA is FF3x::/32, where "x" represents any legal address scope. Figure 92 SPT building in IPv6 PIM-SSM Host A Source...
Page 290: Ipv6 Pim Support For Vpns
Figure 93 Relationship among IPv6 PIM protocols A receiver joins IPv6 multicast group G. G is in the IPv6 An IPv6 multicast source is SSM group range? specified? IPv6 BIDIR-PIM is enabled? An MLD-SSM mapping is configured for G? IPv6 PIM-SM runs for G. G has an IPv6 BIDIR-PIM IPv6 PIM-SSM runs for G.
Page 291: Ipv6 Pim-Dm Configuration Task List
IPv6 PIM-DM configuration task list Tasks at a glance (Required.) Enabling IPv6 PIM-DM (Optional.) Enabling the state refresh feature (Optional.) Configuring state refresh parameters (Optional.) Configuring IPv6 PIM-DM graft retry timer (Optional.) Configuring common IPv6 PIM features Configuration prerequisites Before you configure IPv6 PIM-DM, configure an IPv6 unicast routing protocol so that all devices in the domain can interoperate at the network layer.
Page 292: Configuring State Refresh Parameters
Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Enable the state refresh By default, the state refresh ipv6 pim state-refresh-capable feature. feature is enabled. Configuring state refresh parameters The state refresh interval determines the interval at which a router sends state refresh messages. It is configurable.
Page 293: Configuring Ipv6 Pim-Sm
For more information about the configuration of other timers in IPv6 PIM-DM, see "Configuring common IPv6 PIM timers." Configuring IPv6 PIM-SM This section describes how to configure IPv6 PIM-SM. IPv6 PIM-SM configuration task list Tasks at a glance Remarks (Required.) Enabling IPv6 PIM-SM (Required.) Configuring an...
Page 294: Configuring An Rp
Step Command Remarks ipv6 multicast routing Enable IPv6 multicast routing By default, IPv6 multicast routing [ vpn-instance and enter IPv6 MRIB view. is disabled. vpn-instance-name ] Return to system view. quit interface interface-type Enter interface view. interface-number By default, IPv6 PIM-SM is Enable IPv6 PIM-SM.
Page 295 A C-RP policy enables the BSR to filter C-RP advertisement messages by using an ACL that specifies the packet source address range and multicast group addresses. You must configure the same C-RP policy on all C-BSRs in the IPv6 PIM-SM domain because every C-BSR might become the BSR.
Page 296: Configuring A Bsr
Step Command Remarks Enter system view. system-view ipv6 pim [ vpn-instance Enter IPv6 PIM view. vpn-instance-name ] By default, Anycast RP is not configured. anycast-rp Configure Anycast RP. ipv6-anycast-rp-address You can repeat this command to ipv6-member-address add multiple RP member addresses to an Anycast RP set.
Page 297 Step Command Remarks ipv6 pim [ vpn-instance Enter IPv6 PIM view. vpn-instance-name ] c-bsr ipv6-address [ scope Configure a C-BSR. scope-id ] [ hash-length By default, no C-BSRs exist. hash-length | priority priority ] * By default, no BSR policies exist, (Optional.) Configure a BSR and all bootstrap messages are bsr-policy ipv6-acl-number...
Page 298: Configuring Ipv6 Multicast Source Registration
duplicated traffic. To reduce duplicated traffic, you can disable the device from forwarding BSMs out of their incoming interfaces if all the devices have consistent routing information. To disable the device from forwarding BSMs out of their incoming interfaces: Step Command Remarks Enter system view.
Page 299: Configuring The Switchover To Spt
Step Command Remarks By default, no IPv6 register Configure an IPv6 PIM policies exist, and all IPv6 register register-policy ipv6-acl-number register policy. messages are regarded as legal. Configure the device to By default, the device calculates calculate the checksum the checksum based on the register-whole-checksum based on the entire register header of a register message.
Page 300: Configuration Prerequisites
Tasks at a glance Remarks Configuring a BSR • (Required.) Configuring a C-BSR • (Optional.) Configuring an IPv6 PIM domain border Skip the task of configuring a BSR on an IPv6 network without C-RPs. • (Optional.) Disabling BSM semantic fragmentation •...
Page 301: Configuring An Rp
Configuring an RP CAUTION: When both IPv6 PIM-SM and IPv6 BIDIR-PIM run on the IPv6 PIM network, do not use the same RP to provide services for IPv6 PIM-SM and IPv6 BIDIR-PIM. Otherwise, exceptions might occur to the IPv6 PIM routing table. An RP can provide services for multiple or all IPv6 multicast groups.
Page 302 routers in the network can determine the RPs for different IPv6 multicast group ranges based on the RP-set information. To enable the BSR to distribute the RP-set information in the BIDIR-PIM domain, the C-RPs must periodically send advertisement messages to the BSR. The BSR learns the C-RP information, encapsulates the C-RP information and its own IPv6 address in a BSM, and floods the BSM to all IPv6 PIM routers in the domain.
Page 303: Configuring A Bsr
Configuring a BSR You must configure a BSR if C-RPs are configured to dynamically select the RP. You do not need to configure a BSR when you have configured only a static RP but no C-RPs. An IPv6 BIDIR-PIM domain can have only one BSR, but must have a minimum of one C-BSR. Any router can be configured as a C-BSR.
Page 304 Configuring an IPv6 PIM domain border An IPv6 PIM domain border determines the transmission boundary of bootstrap messages. Bootstrap messages cannot cross the domain border in either direction. A number of PIM domain border interfaces partition a network into different IPv6 BIDIR-PIM domains. To configure an IPv6 PIM border domain: Step Command...
Page 305: Configuring Ipv6 Pim-Ssm
Step Command Remarks Disable the device from By default, the device forwards forwarding BSMs out of their BSMs out of their incoming undo bsm-reflection enable incoming interfaces. interfaces. Configuring IPv6 PIM-SSM IPv6 PIM-SSM requires MLDv2 support. Enable MLDv2 on IPv6 PIM routers that connect to multicast receivers.
Page 306: Configuring The Ipv6 Ssm Group Range
Configuring the IPv6 SSM group range When an IPv6 PIM-SM enabled interface receives an IPv6 multicast packet, it checks whether the IPv6 multicast group address of the packet is in the IPv6 SSM group range. If the IPv6 multicast group address is in this range, the IPv6 PIM mode for this packet is IPv6 PIM-SSM. If the IPv6 multicast group address is not in this range, the IPv6 PIM mode is IPv6 PIM-SM.
Page 307: Configuring An Ipv6 Multicast Source Policy
Configuring an IPv6 multicast source policy This feature enables the device to filter IPv6 multicast data by using an ACL that specifies the IPv6 multicast sources and the optional groups. It filters not only IPv6 multicast data packets but also IPv6 PIM register messages with IPv6 multicast data encapsulated.
Page 308 override interval on different IPv6 PIM routers on a shared-media LAN are different, the largest ones apply. On the shared-media LAN, the propagation delay and override interval are used as follows: If a router receives a prune message on its upstream interface, it means that there are downstream routers on the shared-media LAN.
Page 309: Configuring Common Ipv6 Pim Timers
Step Command Remarks The default setting is 105 ipv6 pim hello-option holdtime Set the neighbor lifetime. seconds. time Set the IPv6 PIM message The default setting is 500 ipv6 pim hello-option lan-delay propagation delay. milliseconds. delay The default setting is 2500 ipv6 pim hello-option Set the override interval.
Page 310: Setting The Maximum Size Of A Join Or Prune Message
Step Command Remarks By default, the interval to send Set the hello interval. timer hello interval hello messages is 30 seconds. By default, the interval to send join/prune messages is 60 seconds. Set the join/prune interval. timer join-prune interval NOTE: This configuration takes effect after the current interval ends.
Page 311: Enabling Ipv6 Pim Passive Mode
new DR election. To start a new DR election process immediately after the original DR fails, you can enable BFD for IPv6 PIM to detect link failures among IPv6 PIM neighbors. You must enable BFD for IPv6 PIM on all IPv6 PIM routers on a shared-media network. For more information about BFD, see High Availability Configuration Guide.
Page 312: Enabling Nbma Mode For Ipv6 Advpn Tunnel Interfaces
Step Command Remarks snmp-agent trap enable pim6 Enable SNMP notifications [ candidate-bsr-win-election | By default, SNMP notifications for for IPv6 PIM. elected-bsr-lost-election | IPv6 PIM are enabled. neighbor-loss ] * Enabling NBMA mode for IPv6 ADVPN tunnel interfaces This feature allows IPv6 ADVPN tunnel interfaces to forward IPv6 multicast data to target spokes and hubs.
Page 313: Ipv6 Pim Configuration Examples
Task Command Display IPv6 PIM information on display ipv6 pim [ vpn-instance vpn-instance-name ] interface an interface. [ interface-type interface-number ] [ verbose ] display ipv6 pim [ vpn-instance vpn-instance-name ] neighbor Display IPv6 PIM neighbor [ ipv6-neighbor-address | interface interface-type interface-number | information.
Page 314 Figure 94 Network diagram Table 27 Interface and IPv6 address assignment Device Interface IPv6 address Device Interface IPv6 address Router A GE1/0/1 1001::1/64 Router C GE1/0/2 3001::1/64 Router A GE1/0/2 1002::1/64 Router D GE1/0/1 4001::1/64 Router B GE1/0/1 2001::1/64 Router D GE1/0/2 1002::2/64 Router B...
Page 315 # Enable IPv6 multicast routing, MLD, and IPv6 PIM-DM on Router B and Router C in the same way Router A is configured. (Details not shown.) # On Router D, enable IPv6 multicast routing, and enable IPv6 PIM-DM on each interface. <RouterD>...
Page 316: Ipv6 Pim-Sm Non-Scoped Zone Configuration Example
UpTime: 00:01:24 Upstream interface: NULL Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet1/0/1 Protocol: mld, UpTime: 00:01:20, Expires: - (4001::100, FF0E::101) Protocol: pim-dm, Flag: ACT UpTime: 00:01:20 Upstream interface: GigabitEthernet1/0/2 Upstream neighbor: 1002::2 RPF prime neighbor: 1002::2 Downstream interface(s) information: Total number of downstreams: 1...
Page 317 • Host A and Host C are multicast receivers on the stub networks N1 and N2. • Specify GigabitEthernet 1/0/3 on Router E as a C-BSR and a C-RP. The C-RP is designated to IPv6 multicast group range FF0E::101/64. Specify GigabitEthernet 1/0/2 of Router D as the static RP on all the routers to back up the dynamic RP.
Page 318 [RouterA] ipv6 multicast routing [RouterA-mrib6] quit # Enable MLD on GigabitEthernet 1/0/1 (the interface that connects to the stub network). [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] mld enable [RouterA-GigabitEthernet1/0/1] quit # Enable IPv6 PIM-SM on the other interfaces. [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] ipv6 pim sm [RouterA-GigabitEthernet1/0/2] quit [RouterA] interface gigabitethernet 1/0/3...
Page 319: Ipv6 Pim-Sm Admin-Scoped Zone Configuration Example
State: Accept Preferred Bootstrap timer: 00:01:44 Elected BSR address: 1003::2 Priority: 64 Hash mask length: 126 Uptime: 00:11:18 # Display BSR information on Router E. [RouterE] display ipv6 pim bsr-info Scope: non-scoped State: Elected Bootstrap timer: 00:01:44 Elected BSR address: 1003::2 Priority: 64 Hash mask length: 126 Uptime: 00:11:18...
Page 320 • MLDv1 separately runs between Router A, Router E, Router I, and the receivers that directly connect to them. Figure 96 Network diagram IPv6 admin-scope 1 GE1/0/1 Receiver Router G Host A Source 1 GE1/0/2 Source 3 GE1/0/1 GE1/0/1 GE1/0/1 GE1/0/2 GE1/0/4 GE1/0/3...
Page 321 Configuration procedure Assign an IPv6 address and prefix length to each interface, as shown in Figure 96. (Details not shown.) Configure OSPFv3 on all routers in the IPv6 PIM-SM domain. (Details not shown.) Enable IPv6 multicast routing, MLD, and IPv6 PIM-SM: # On Router A, enable IPv6 multicast routing.
Page 322 <RouterC> system-view [RouterC] interface gigabitethernet 1/0/4 [RouterC-GigabitEthernet1/0/4] ipv6 multicast boundary scope 4 [RouterC-GigabitEthernet1/0/4] quit [RouterC] interface gigabitethernet 1/0/5 [RouterC-GigabitEthernet1/0/5] ipv6 multicast boundary scope 4 [RouterC-GigabitEthernet1/0/5] quit # On Router D, configure GigabitEthernet 1/0/3 as the boundary of IPv6 admin-scoped zone 2. <RouterD>...
Page 323 Hash mask length: 126 Uptime: 00:04:54 Candidate BSR address: 1002::2 Priority: 64 Hash mask length: 126 # Display BSR information on Router D. [RouterD] display ipv6 pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:25 Elected BSR address: 8001::1 Priority: 64 Hash mask length: 126 Uptime: 00:01:45...
Page 324 Group/MaskLen: FF14::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FF24::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FF34::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FF44::/16 RP address Priority HoldTime Uptime...
Page 325: Ipv6 Bidir-Pim Configuration Example
# Display RP information on Router F. [RouterF] display ipv6 pim rp-info BSR RP information: Scope: non-scoped Group/MaskLen: FF00::/8 RP address Priority HoldTime Uptime Expires 8001::1 (local) 00:10:28 00:02:31 IPv6 BIDIR-PIM configuration example Network requirements As shown in Figure • OSPFv3 runs on the network.
Page 326 Configuration procedure Assign an IPv6 address and prefix length to each interface, as shown in Figure 97. (Details not shown.) Configure OSPFv3 on the routers in the IPv6 BIDIR-PIM domain. (Details not shown.) Enable IPv6 multicast routing, IPv6 PIM-SM, IPv6 BIDIR-PIM, and MLD: # On Router A, enable IPv6 multicast routing, enable IPv6 PIM-SM on each interface, and enable IPv6 BIDIR-PIM.
Page 327 [RouterC-GigabitEthernet1/0/2] quit [RouterC] interface loopback 0 [RouterC-LoopBack0] ipv6 pim sm [RouterC-LoopBack0] quit [RouterC] ipv6 pim [RouterC-pim6] bidir-pim enable # On Router D, enable IPv6 multicast routing. <RouterD> system-view [RouterD] ipv6 multicast routing [RouterD-mrib6] quit # Enable MLD on the receiver-side interface (GigabitEthernet 1/0/1). [RouterD] interface gigabitethernet 1/0/1 [RouterD-GigabitEthernet1/0/1] mld enable [RouterD-GigabitEthernet1/0/1] quit...
Page 328 FE38:4E01 (local) GE1/0/3 Lose 01:23:12 FE80::20F:E2FF: FE15:5601 # Display the DF information of IPv6 BIDIR-PIM on Router C. [RouterC] display ipv6 pim df-info RP address: 6001::1 Interface State DF-Pref DF-Metric DF-Uptime DF-Address Loop0 GE1/0/1 01:06:07 FE80::20F:E2FF: FE15:5601 (local) GE1/0/2 01:06:07 FE80::20F:E2FF: FE15:5602 (local) # Display the DF information of IPv6 BIDIR-PIM on Router D.
Page 329: Ipv6 Pim-Ssm Configuration Example
00001. RP address: 6001::1 Flags: 0x0 Uptime: 00:07:21 RPF interface: LoopBack0 List of 2 DF interfaces: 1: GigabitEthernet1/0/1 2: GigabitEthernet1/0/2 # Display information about the DF for IPv6 multicast forwarding on Router D. [RouterD] display ipv6 multicast forwarding df-info Total 1 RP, 1 matched 00001.
Page 330 Figure 98 Network diagram Table 31 Interface and IPv6 address assignment Device Interface IPv6 address Device Interface IPv6 address Router A GE1/0/1 1001::1/64 Router D GE1/0/1 4001::1/64 Router A GE1/0/2 1002::1/64 Router D GE1/0/2 1002::2/64 Router A GE1/0/3 1003::1/64 Router D GE1/0/3 4002::1/64 Router B...
Page 331 [RouterA-GigabitEthernet1/0/1] quit # Enable IPv6 PIM-SM on other interfaces. [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] ipv6 pim sm [RouterA-GigabitEthernet1/0/2] quit [RouterA] interface gigabitethernet 1/0/3 [RouterA-GigabitEthernet1/0/3] ipv6 pim sm [RouterA-GigabitEthernet1/0/3] quit # Enable IPv6 multicast routing, MLD and IPv6 PIM-SM on Router B and Router C in the same way Router A is configured.
Page 332: Troubleshooting Ipv6 Pim
Total 0 (*, G) entry; 1 (S, G) entry (4001::100, FF3E::101) Protocol: pim-ssm, Flag: LOC UpTime: 00:08:02 Upstream interface: GigabitEthernet1/0/1 Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet1/0/2 Protocol: pim-ssm, UpTime: 00:08:02, Expires: 00:03:25 The output shows that routers on the SPT path (Router A and Router D) have generated the correct (S, G) entries.
Page 333: An Rp Cannot Join An Spt In Ipv6 Pim-Sm
Solution To resolve the problem: Use display current-configuration to verify the IPv6 multicast forwarding boundary settings. Use ipv6 multicast boundary to change the multicast forwarding boundary settings to make the IPv6 multicast packet able to cross the boundary. Use display current-configuration to verify the IPv6 multicast source policy. Change the ACL rule defined in the source-policy command so that the source/group address of the IPv6 multicast data can pass ACL filtering.
Page 334: Document Conventions And Icons
Document conventions and icons Conventions This section describes the conventions used in the documentation. Command conventions Convention Description Bold text represents commands and keywords that you enter literally as shown. Boldface Italic text represents arguments that you replace with actual values. Italic Square brackets enclose syntax choices (keywords or arguments) that are optional.
Page 335: Network Topology Icons
Network topology icons Convention Description 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 336: Support And Other Resources
Hewlett Packard Enterprise Support Center More Information on Access to Support Materials page: www.hpe.com/support/AccessToSupportMaterials IMPORTANT: Access to some updates might require product entitlement when accessed through the Hewlett Packard Enterprise Support Center. You must have an HP Passport set up with relevant entitlements.
Page 337: Websites
Websites Website Link Networking websites Hewlett Packard Enterprise Information Library for www.hpe.com/networking/resourcefinder Networking Hewlett Packard Enterprise Networking website www.hpe.com/info/networking Hewlett Packard Enterprise My Networking website www.hpe.com/networking/support Hewlett Packard Enterprise My Networking Portal www.hpe.com/networking/mynetworking Hewlett Packard Enterprise Networking Warranty www.hpe.com/networking/warranty General websites Hewlett Packard Enterprise Information Library www.hpe.com/info/enterprise/docs Hewlett Packard Enterprise Support Center...
Page 338 part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.
Page 339: Index
PIM-SM RP, Index application IP multicast data distribution, IP multicast VPN, architecture access IP multicast network, MLD IPv6 multicast access control configuration (PPPoE), intra-AS M6VPE configuration, accessing multicast inter-AS MD VPN, IGMP multicast access control, 41, 49 multicast intra-AS MD VPN configuration, IGMP multicast access control configuration multicast VPN inter-AS option B, (IPoE),...
Page 340 BSR configuration, IPv6 PIM-SM, C-BSR configuration, IPv6 PIM-SM administrative scoping zone border router, configuration, 98, 123 IPv6 PIM-SM C-BSR, C-RP configuration, PIM-SM administrative scoping zones, DF election, PIM-SM BSR configuration, domain border configuration, PIM-SM C-BSR configuration, enable, PIM-SM RP discovery, introduction, IPv6.
Page 341 IGMP proxying, 47, 57 IPv6 PIM-SSM group range, IGMP query/response parameter (global), MLD, 230, 235, 245 IGMP query/response parameter MLD basics, 235, 245 (interface), MLD IPv6 multicast access control, IGMP SSM mapping, 47, 54 MLD IPv6 multicast access control (PPPoE), IGMP static group member, MLD IPv6 multicast access control configuration IGMP user access policy,...
Page 342 PIM hello message options, multicast VPN default-MDT establishment (PIM-SM network), PIM hello policy, multicast VPN default-MDT establishment PIM multicast source policy, (PIM-SSM network), PIM-DM, 89, 112 multicast VPN MDT establishment, PIM-DM graft retry timer, multicast VPN MDT-based delivery, PIM-DM state-refresh parameter, troubleshooting multicast MD VPN default-MDT PIM-SM, establishment,...
Page 343 BIDIR-PIM, PIM-SM DR election, IPv6 BIDIR-PIM, PIM-SM RPT building, disabling PIM-SM SPT switchover, BIDIR-PIM BSM device forwarding, PIM-SSM DR election, BIDIR-PIM BSM semantic fragmentation, PIM-SSM SPT building, IPv6 BIDIR-PIM BSM device forwarding, DR election IPv6 BIDIR-PIM BSM semantic IPv6 PIM-SSM, fragmentation, IPv6 PIM-SM BSM forwarding, electing...
Page 344 multicast VPN default MDT establishment IPv6 BIDIR-PIM bidirectional RPT building, (PIM-DM network), IPv6 BIDIR-PIM BSM device forwarding multicast VPN default MDT establishment disable, (PIM-SM network), IPv6 BIDIR-PIM BSR, multicast VPN default MDT establishment IPv6 BIDIR-PIM configuration, 291, 317 (PIM-SSM network), IPv6 BIDIR-PIM DF election, Ethernet IPv6 BIDIR-PIM RP,...
Page 345 multicast VPN default-MDT to data-MDT IPv6 PIM policy, switch, PIM common timer configuration (global), multicast VPN default-MDT-based PIM common timer configuration (on delivery, interface), multicast VPN inter-AS option B PIM hello message option configuration configuration, (global), multicast VPN inter-AS option C PIM hello message option configuration (on configuration, interface),...
Page 346 protocols and standards, IP addressing proxying, IP multicast address, proxying configuration, 47, 57 IP multicast packet forwarding, proxying enable, multicast VPN MD address family creation, query/response parameter configuration, IP multicast query/response parameter configuration address, restrictions, architecture, snooping. See IGMP snooping ASM model, SSM mapping, BIDIR-PIM,...
Page 347 IGMP static group member configuration, MD VPN instance IP multicast routing, IGMP user access policy, MLD basics configuration, IGMP version specification, MLD configuration, 230, 235, 235, 245 IGMP versions, MLD display, IGMP VLAN-based static group member, MLD fast-leave processing, IGMP VPN support, MLD IPv6 multicast access control, 242, 242 IGMPv1,...
Page 348 PIM-SM, troubleshooting PIM-SM multicast source registration failure, PIM-SM administrative scoping, unicast transmission technique, PIM-SM admin-scoped zone configuration, VPN application, PIM-SM Anycast RP, VPN instance, PIM-SM configuration, VPN support, PIM-SM DR election, IPv4 PIM-SM enable, Ethernet multicast MAC address, PIM-SM multicast source registration, IP multicast address, PIM-SM neighbor discovery, IPv6...
Page 349 forwarding/GRE tunnel configuration, configuration, 282, 305 load splitting configuration, enable, longest prefix match principle, graft, MLD basics configuration, graft retry timer, MLD IPv6 multicast forwarding (non-querier introduction, interface), IPv6 PIM passive mode enable, MLD IPv6 multicast group policy, IPv6 PIM protocol relationships, MLD IPv6 multicast load splitting (MLD neighbor discovery, proxy),...
Page 350 group range configuration restrictions, Ethernet multicast MAC address, introduction, maintaining IPv6 PIM protocol relationships, IGMP, IPv6 PIM-SM enable, IPv6 multicast routing+forwarding, neighbor discovery, MLD, protocols and standards, multicast routing+forwarding, SPT building, multicast VPN, IPv6 VPN mapping provider edge. See M6VPE IGMP SSM mapping, 39, 47 IGMP SSM mapping configuration,...
Page 351 configuration, 230, 235, 245 IPv6 multicast group leave, configuration restrictions, MLD support, display, querier election, enable, MLDv2 fast-leave processing enable, filter mode, IPv6 multicast access control, 234, 242, 242 how it works, IPv6 multicast access control configuration IPv6 PIM-SSM introduction, (IPoE), MLD support, IPv6 multicast access control configuration...
Page 352 static route, neighbor static route configuration, multicast MD VPN PIM neighbor relationships, troubleshoot, neighbor discovery troubleshoot static route failure, BIDIR-PIM, unicast subnets, IPv6 BIDIR-PIM, multicast VPN IPv6 PIM-DM, BGP MDT configuration, IPv6 PIM-SM, BGP MDT peer/peer group, IPv6 PIM-SSM, BGP MDT route reflector, PIM-DM, configuration, 133, 149, 157...
Page 353 IPv6 BIDIR-PIM BSM device forwarding MLD IPv6 multicast access control configuration disable, (Portal), IPv6 BIDIR-PIM BSR, MLD IPv6 multicast access control configuration (PPPoE), IPv6 BIDIR-PIM configuration, 291, 317 MLD IPv6 multicast group policy, IPv6 BIDIR-PIM RP, MLD IPv6 multicast VLAN-based static group IPv6 multicast forwarding (unicast member, subnet),...
Page 354 PIM-DM graft, PIM-SSM, PIM-DM graft retry timer, PIM-SSM configuration, PIM-DM neighbor discovery, transmission techniques, PIM-DM SPT building, non-querier PIM-DM state-refresh, IGMP forwarding (non-querier interface), PIM-DM state-refresh parameters, notifying IPv6 multicast PIM SNMP notification, PIM-SM C-RP, PIM-SM administrative scoping, PIM SNMP notification enable, PIM-SM admin-scoped zone configuration, option...
Page 355 multicast VPN BGP MDT peer/peer troubleshoot abnormal multicast data group, termination, troubleshoot multicast distribution tree, BFD enable, VPN support, BIDIR. See BIDIR-PIM PIM-DM common feature configuration, assert, common timer configuration, configuration, 89, 112 common timer configuration (global), enable, common timer configuration (on graft, interface), graft retry timer,...
Page 356 non-scoped zone configuration, configuring BIDIR-PIM static RP, PIM BFD enable, configuring IGMP, PIM configuration, configuring IGMP basics, 42, 52 PIM domain border, configuring IGMP multicast access control, PIM passive mode enable, configuring IGMP multicast access control (IPoE), PIM protocol relationships, configuring IGMP multicast access control PIM SNMP notification enable, (Portal),...
Page 357 configuring IPv6 PIM-DM graft retry timer, configuring multicast intra-AS M6VPE, configuring IPv6 PIM-DM state refresh configuring multicast intra-AS MD VPN, parameter, configuring multicast routing load splitting, configuring IPv6 PIM-SM, configuring multicast routing+forwarding, 17, 18 configuring IPv6 PIM-SM admin-scoped configuring multicast static route, zone, configuring multicast VPN, configuring IPv6 PIM-SM Anycast RP,...
Page 358 delivering multicast routing failed RPF check enabling MLD per-session IPv6 multicast packets to the CPU, forwarding, disabling BIDIR-PIM BSM device enabling MLD proxying, forwarding, enabling multicast VPN data-group reuse disabling IP multicast BIDIR-PIM BSM logging, semantic fragmentation, enabling multicast VPN RPF vector, disabling IPv6 BIDIR-PIM BSM f device enabling multicast VPN RPF vector orwarding,...
Page 359 troubleshooting multicast MD VPN MLD querier election, default-MDT establishment, MLD query/response parameter, troubleshooting multicast VPN MVRF creation, RADIUS troubleshooting PIM abnormal multicast data termination, MLD IPv6 multicast user access policy, troubleshooting PIM multicast distribution reflecting tree, multicast VPN BGP MDT route reflector, troubleshooting PIM RP cannot join SPT, refreshing troubleshooting PIM-SM multicast source...
Page 360 BIDIR-PIM C-BSR configuration, IPv6 PIM protocol relationships, BIDIR-PIM configuration, 98, 123 IPv6 PIM timer, BIDIR-PIM C-RP, IPv6 PIM VPN support, BIDIR-PIM DF election, IPv6 PIM-DM, BIDIR-PIM discovery, IPv6 PIM-DM assert, BIDIR-PIM domain border configuration, IPv6 PIM-DM configuration, 282, 305 BIDIR-PIM neighbor discovery, IPv6 PIM-DM graft, BIDIR-PIM RP configuration, IPv6 PIM-DM neighbor discovery,...
Page 361 multicast routing, multicast PIM-SM RP discovery, See also routing+forwarding PIM-SM RPT building, multicast VPN BGP MDT configuration, PIM-SM SPT switchover, 81, 98 multicast VPN BGP MDT route reflector, PIM-SM static RP, multicast VPN configuration, 133, 149, 157 PIM-SM zone relationships, multicast VPN data-MDT to default-MDT PIM-SSM, switch,...
Page 362 troubleshooting PIM-SM RP cannot be shortest path tree. Use built, SNMP troubleshooting PIM-SM RP cannot join IPv6 multicast PIM SNMP notification enable, SPT, PIM SNMP notification enable, source IPv6 multicast check mechanism, MLDv2 source list, IPv6 multicast longest prefix match multicast VPN MD source interface, principle, source registration...
Page 363 IPv6 BIDIR-PIM RP, IGMP proxying configuration, IPv6 PIM-SM RP, IGMP SSM mapping configuration, MLD group member, MLD IPv6 multicast access control configuration (IPoE ), MLD IPv6 multicast VLAN-based static group member, MLD IPv6 multicast access control configuration (Portal ), multicast static route configuration, MLD IPv6 multicast access control configuration multicast static RPF route, (PPPoE ),...
Page 364 multicast MD VPN default-MDT BIDIR-PIM configuration, establishment, IGMP VLAN-based static group member, multicast routing+forwarding, IPv6 BIDIR-PIM configuration, multicast static route failure, IPv6 PIM configuration, multicast VPN MVRF creation, IPv6 PIM-DM configuration, PIM, IPv6 PIM-SM admin-scoped zone PIM abnormal multicast data termination, configuration, PIM multicast distribution tree, IPv6 PIM-SM non-scoped zone configuration,...

HP VSR1000 Configuration Manual

Multicast Overview

Configuring Multicast Routing and Forwarding

Configuring IGMP

Configuring PIM

Configuring Multicast VPN

Configuring Ipv6 Multicast Routing and Forwarding

Configuring MLD

Configuring Ipv6 PIM

Document Conventions and Icons

Support and Other Resources

Quick Links

Troubleshooting

Related Manuals for HP VSR1000

Summary of Contents for HP VSR1000