HPE FlexNetwork 5510 HI Series Configuration Manual page 306

backups for dynamic RPs to enhance the robustness and operational manageability on an IPv6
multicast network.
Configuring a static RP
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 due to
frequent message exchange between C-RPs and the BSR.
In IPv6 BIDIR-PIM, a static RP can be specified with an unassigned IPv6 address. This address
must be on the same subnet with 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
assign 1001::100/64 to the static RP. As a result, the link becomes an RPL.
When you configure static RPs, follow these restrictions and guidelines:
• 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.
• The static RP configuration must be the same on all routers in the IPv6 BIDIR-PIM domain.
To configure a static RP for IPv6 BIDIR-PIM:
Step
Enter system view.
1.
Enter IPv6 PIM view.
2.
Configure a static RP for
3.
IPv6 BIDIR-PIM.
Configuring a C-RP
IMPORTANT:
• When you configure a C-RP, reserve a large bandwidth between the C-RP and other devices in
the IPv6 BIDIR-PIM domain.
• As a best practice, configure C-RPs on backbone routers.
In an IPv6 BIDIR-PIM domain, if you want a router to become the RP, you can configure the router as
a C-RP. The BSR collects the C-RP information according to the received advertisement messages
from C-RPs or the auto-RP announcements from other routers. Then, it organizes the C-RP
information into the RP-set information, which is flooded throughout the entire network. The other
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.
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. If the BSR does not receive any advertisement message when the timer expires, it
considers the C-RP failed or unreachable.
The device might use the BSR RP hash algorithm described in RFC 4601 or in RFC 2362 to
calculate the RP for a multicast group. To ensure consistent group-to-RP mappings on all PIM
routers in the IPv6 BIDIR-PIM domain, specify the same BSR RP hash algorithm on the routers.
Command
system-view
ipv6 pim [ vpn-instance
vpn-instance-name ]
static-rp ipv6-rp-address bidir
[ ipv6-acl-number | preferred ] *
296
Remarks
N/A
N/A
By default, no static RPs exist.