Configuring static RPs
About static RPs
If only one dynamic RP exists on a network, you can configure a static RP to avoid communication interruption caused by single-point failures. The static RP can also avoid bandwidth waste caused by frequent message exchanges between C-RPs and the BSR.
Restrictions and guidelines
The static RP configuration must be the same on all devices in the IPv6 BIDIR-PIM domain.
In an IPv6 BIDIR-PIM domain, you can configure the same static RP for different IPv6 multicast groups by using the same RP address but different ACLs.
You do not need to enable IPv6 PIM for an interface to be configured as a static RP.
If you configure multiple static RPs for an IPv6 multicast group, only the static RP with the highest IPv6 address takes effect.
You can specify an unused IP address for a static RP. This address must be on the same subnet as the link on which the static RP is configured. For example, if the IPv6 addresses of the interfaces at the two ends of a link are 1001::1/64 and 1001::2/64, you can specify the interface with IPv6 address 1001::100/64 as a static RP. As a result, the link becomes an RPL.
Procedure
Enter system view.
system-view
Enter IPv6 PIM view.
ipv6 pim [ vpn-instance vpn-instance-name ]
Configure a static RP for IPv6 BIDIR-PIM.
static-rp ipv6-rp-address bidir [ ipv6-acl-number | preferred ] *