Contents

Configuring IPv6 multicast routing and forwarding· 1

About IPv6 multicast routing and forwarding· 1

RPF check mechanism·· 1

IPv6 multicast forwarding across IPv6 unicast subnets· 3

IPv6 multicast routing and forwarding tasks at a glance· 3

Prerequisites for IPv6 multicast routing and forwarding· 3

Enabling IPv6 multicast routing· 4

Specifying the longest prefix match principle· 4

Configuring IPv6 multicast load splitting· 4

Configuring an IPv6 multicast forwarding boundary· 5

Setting the maximum number of cached unknown IPv6 multicast packets· 5

Verifying and maintaining IPv6 multicast routing and forwarding· 6

Verifying IPv6 multicast routing and forwarding configuration and running status· 6

Displaying IPv6 multicast routing entries and IPv6 multicast forwarding entries· 6

Clearing IPv6 multicast routing entries and IPv6 multicast forwarding entries· 7

Displaying and clearing statistics for IPv6 multicast forwarding events· 7

 

Configuring IPv6 multicast routing and forwarding

About IPv6 multicast routing and forwarding

Each IPv6 multicast routing protocol has its own routing table. Multicast routing information in routing entries generated by the IPv6 multicast routing protocols are summarized in a set of (S, G) and (*, G) entries. All the (S, G) and (*, G) entries form a general IPv6 multicast routing table. The optimal IPv6 multicast routing entries in the general IPv6 multicast routing table are added to the IPv6 multicast forwarding table to guide IPv6 multicast data forwarding.

RPF check mechanism

An IPv6 multicast routing protocol uses the reverse path forwarding (RPF) check mechanism to ensure IPv6 multicast data delivery along the correct path and to avoid data loops.

RPF check process

An IPv6 multicast device performs the RPF check on an IPv6 multicast packet as follows:

1.     Chooses an optimal route back to the packet source separately from the IPv6 unicast and IPv6 MBGP routing tables.

In RPF check, the "packet source" means difference things in difference situations:

¡     For a packet that travels along the SPT, the packet source is the IPv6 multicast source.

¡     For a packet that travels along the RPT, the packet source is the RP.

¡     For a bootstrap message originated from the BSR, the packet source is the BSR.

For more information about the concepts of SPT, RPT, source-side RPT, RP, and BSR, see "IPv6 PIM overview."

2.     Selects one of the optimal routes as the RPF route as follows:

¡     If the device uses the longest prefix match principle, the route with a higher prefix length becomes the RPF route. If the routes have the same prefix length, the route with a higher route preference becomes the RPF route. If the routes have the same route preference, the IPv6 MBGP route becomes the RPF route. If equal cost routes exist, the equal cost route with the highest next hop IPv6 address becomes the RPF route.

For more information about the route preference, see Layer 3—IP Routing Configuration Guide.

¡     If the device does not use the longest prefix match principle, the route with a higher route preference becomes the RPF route. If the routes have the same route preference, the IPv6 MBGP route becomes the RPF route. If equal cost routes exist, the equal cost route with the highest next hop IPv6 address becomes the RPF route.

In the RPF route, the outgoing interface is the RPF interface and the next hop is the RPF neighbor.

3.     Determines whether the packet arrived at the RPF interface.

¡     If the packet arrived at the RPF interface, the RPF check succeeds and the packet is forwarded.

¡     If the packet arrived at the non-RPF interface, the RPF check fails and the packet is discarded.

RPF check implementation in IPv6 multicast

Implementing an RPF check on each received IPv6 multicast packet would heavily burden the device. The use of an IPv6 multicast forwarding table is the solution to this issue. When the device creates an IPv6 multicast forwarding entry for an IPv6 (S, G) packet, it sets the RPF interface of the packet as the incoming interface of the (S, G) entry. After the device 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 device 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 device forwards the packet out of all outgoing interfaces.

¡     If the receiving interface is not the RPF interface, the RPF check fails and the device discards the packet.

·     If a match is found and the matching forwarding entry contains the receiving interface, the device forwards the packet out of all outgoing interfaces.

·     If a match is found but the matching forwarding entry does not contain the receiving interface, the device determines the RPF route back to the packet source. Then, the device performs one of the following tasks:

¡     If the RPF interface is the incoming interface, it means that the forwarding entry is correct but the packet traveled along a wrong path. The packet fails the RPF check, and the device discards the packet.

¡     If the RPF interface is not the incoming interface, it means that the forwarding entry has expired. The device replaces the incoming interface with the RPF interface and matches the receiving interface against the RPF interface. If the receiving interface is the RPF interface, the device forwards the packet out of all outgoing interfaces. Otherwise, it discards the packet.

Figure 1 RPF check process

 

‌

As shown in Figure 1, assume that IPv6 unicast routes are available on the network. IPv6 MBGP is not configured. IPv6 multicast packets travel along the SPT from the multicast source to the receivers. The IPv6 multicast forwarding table on Device C contains the (S, G) entry, with Port A as the RPF interface.

·     If an IPv6 multicast packet arrives at Device C on Port A, the receiving interface is the incoming interface of the (S, G) entry. Device C forwards the packet out of all outgoing interfaces.

·     If an IPv6 multicast packet arrives at Device C on Port B, the receiving interface is not the incoming interface of the (S, G) entry. Device C searches its IPv6 unicast routing table and finds that the outgoing interface to the source (the RPF interface) is Port A. This means that the (S, G) entry is correct but the packet traveled along a wrong path. The packet fails the RPF check, and Device C discards the packet.

IPv6 multicast forwarding across IPv6 unicast subnets

IPv6 multicast data transmission over a 6to4 tunnel is not supported in the current software version.

Devices forward the IPv6 multicast data from an IPv6 multicast source hop by hop along the forwarding tree, but some devices might not support IPv6 multicast protocols in a network. When the IPv6 multicast data is forwarded to a device that does not support IPv6 multicast, the forwarding path is blocked. In this case, you can enable IPv6 multicast data forwarding across the IPv6 unicast subnets by establishing a tunnel between the devices at both ends of the IPv6 unicast subnets.

Figure 2 IPv6 multicast data transmission through a tunnel

 

As shown in Figure 2, a tunnel is established between Device A and Device B. Device A encapsulates the IPv6 multicast data in unicast IPv6 packets, and forwards them to Device B across the tunnel through unicast devices. Then, Device B strips off the unicast IPv6 header and continues to forward the IPv6 multicast data down toward the receivers.

IPv6 multicast routing and forwarding tasks at a glance

To configure IPv6 multicast routing and forwarding, perform the following tasks:

1.     Enabling IPv6 multicast routing

2.     (Optional.) Specifying the longest prefix match principle

3.     (Optional.) Configuring IPv6 multicast load splitting

4.     (Optional.) Configuring an IPv6 multicast forwarding boundary

5.     (Optional.) Setting the maximum number of cached unknown IPv6 multicast packets

Prerequisites for IPv6 multicast routing and forwarding

Before you configure multicast routing and forwarding, configure an IPv6 unicast routing protocol so that all devices in the domain can interoperate at the network layer.

Enabling IPv6 multicast routing

About IPv6 multicast routing

Enable IPv6 multicast routing before you configure any Layer 3 IPv6 multicast functionality in the public network or VPN instance.

Procedure

1.     Enter system view.

system-view

2.     Enable IPv6 multicast routing and enter IPv6 MRIB view.

ipv6 multicast routing [ vpn-instance vpn-instance-name ]

By default, IPv6 multicast routing is disabled.

Specifying the longest prefix match principle

About the longest prefix match principle

You can enable the device to use the longest prefix match principle for RPF route selection. For more information about RPF route selection, see "RPF check process."

Procedure

1.     Enter system view.

system-view

2.     Enter IPv6 MRIB view.

ipv6 multicast routing [ vpn-instance vpn-instance-name ]

3.     Specify the longest prefix match principle for RPF route selection.

longest-match

By default, the route preference principle is used.

Configuring IPv6 multicast load splitting

About IPv6 multicast load splitting

You can enable the device to split multiple IPv6 multicast data flows on a per-source basis or on a per-source-and-group basis.

Restrictions and guidelines

This feature does not take effect on IPv6 BIDIR-PIM.

Procedure

1.     Enter system view.

system-view

2.     Enter IPv6 MRIB view.

ipv6 multicast routing [ vpn-instance vpn-instance-name ]

3.     Configure IPv6 multicast load splitting.

load-splitting { source | source-group }

By default, IPv6 multicast load splitting is disabled.

Configuring an IPv6 multicast forwarding boundary

About IPv6 multicast forwarding boundaries

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.

Restrictions and guidelines

You do not need to enable IPv6 multicast routing before this configuration.

Procedure

1.     Enter system view.

system-view

2.     Enter interface view.

interface interface-type interface-number

3.     Configure an IPv6 multicast forwarding boundary.

ipv6 multicast boundary { ipv6-group-address prefix-length | scope { scope-id | admin-local | global | organization-local | site-local } }

By default, an interface is not an IPv6 multicast forwarding boundary for any IPv6 multicast groups.

Setting the maximum number of cached unknown IPv6 multicast packets

About setting the maximum number of cached unknown IPv6 multicast packets

The device caches an IPv6 multicast packet for a period of time if no matching multicast forwarding entry is found for the packet. If a multicast forwarding entry is established for the packet within the time period, the device forwards the packet. This mechanism prevents the device from mistakenly dropping IPv6 multicast packets when the multicast forwarding entries for these packets are to be established.

You can set the maximum number of unknown IPv6 multicast packets that can be cached for an (S, G) entry, in total, or both.

Restrictions and guidelines

As a best practice, set the value in the ipv6 multicast forwarding-table cache-unknown total command to be far greater than the value in the ipv6 multicast forwarding-table cache-unknown per-entry command.

Procedure

1.     Enter system view.

system-view

2.     Set the maximum number of unknown IPv6 multicast packets that can be cached for an (S, G) entry.

ipv6 multicast forwarding-table cache-unknown per-entry per-entry-limit

By default, the device can cache only one unknown IPv6 multicast packet for an (S, G) entry.

3.     Set the maximum number of unknown IPv6 multicast packets that can be cached in total.

ipv6 multicast forwarding-table cache-unknown total total-limit

By default, the device can cache 1024 unknown IPv6 multicast packets in total.

Verifying and maintaining IPv6 multicast routing and forwarding

Verifying IPv6 multicast routing and forwarding configuration and running status

Perform display tasks in any view.

·     Display information about the interfaces maintained by the IPv6 MRIB.

display ipv6 mrib [ vpn-instance vpn-instance-name ] interface [ interface-type interface-number ]

·     Display IPv6 multicast boundary information.

display ipv6 multicast [ vpn-instance vpn-instance-name ] boundary { group [ ipv6-group-address [ prefix-length ] ] | scope [ scope-id ] } [ interface interface-type interface-number ]

·     Display IPv6 DF information.

display ipv6 multicast [ vpn-instance vpn-instance-name ] forwarding df-info [ ipv6-rp-address ] [ verbose ] [ slot slot-number ]

·     Display RPF information for an IPv6 multicast source.

display ipv6 multicast [ vpn-instance vpn-instance-name ] rpf-info ipv6-source-address [ ipv6-group-address ]

Displaying IPv6 multicast routing entries and IPv6 multicast forwarding entries

Displaying IPv6 multicast routing entries

Perform display tasks in any view.

display ipv6 multicast [ vpn-instance vpn-instance-name ] routing-table [ ipv6-source-address [ prefix-length ] | ipv6-group-address [ prefix-length ] | incoming-interface interface-type interface-number | outgoing-interface { exclude | include | match } interface-type interface-number ] *

Displaying IPv6 multicast forwarding entries

Perform display tasks in any view.

·     Display IPv6 multicast forwarding entries.

display ipv6 multicast [ vpn-instance vpn-instance-name ] forwarding-table [ ipv6-source-address [ prefix-length ] | ipv6-group-address [ prefix-length ] | incoming-interface interface-type interface-number | outgoing-interface { exclude | include | match } interface-type interface-number | slot slot-number | statistics ] *

·     Display information about the DF list in the IPv6 multicast forwarding table.

display ipv6 multicast [ vpn-instance vpn-instance-name ] forwarding-table df-list [ ipv6-group-address ] [ verbose ] [ slot slot-number ]

Clearing IPv6 multicast routing entries and IPv6 multicast forwarding entries

Restrictions and guidelines

The reset commands might cause IPv6 multicast data transmission failures.

When you clear an IPv6 multicast routing entry, the associated IPv6 multicast forwarding entry is also cleared.

When you clear an IPv6 multicast forwarding entry, the associated IPv6 multicast routing entry is also cleared.

Procedure

Perform clear tasks in user view.

·     Clear IPv6 multicast forwarding entries.

reset ipv6 multicast [ vpn-instance vpn-instance-name ] forwarding-table { { ipv6-source-address [ prefix-length ] | ipv6-group-address [ prefix-length ] | incoming-interface { interface-type interface-number } } * | all }

·     Clear IPv6 multicast routing entries.

reset ipv6 multicast [ vpn-instance vpn-instance-name ] routing-table { { ipv6-source-address [ prefix-length ] | ipv6-group-address [ prefix-length ] | incoming-interface interface-type interface-number } * | all }

Displaying and clearing statistics for IPv6 multicast forwarding events

To display statistics for IPv6 multicast forwarding events, execute the following command in any view:

display ipv6 multicast [ vpn-instance vpn-instance-name ] forwarding event [ slot slot-number ]

To clear statistics for IPv6 multicast forwarding events, execute the following command in user view:

reset ipv6 multicast [ vpn-instance vpn-instance-name ] forwarding event