
352
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.
To configure a C-RP:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter IPv6 PIM view.
ipv6 pim
[
vpn-instance
vpn-instance-name
]
N/A
3.
Configure a C-RP to provide
services for IPv6 BIDIR-PIM.
c-rp
ipv6-address
[
advertisement-interval
adv-interval
| {
group-policy
ipv6-acl-number
|
scope
scope-id
}
|
holdtime hold-time
|
priority
priority
] *
bidir
By default, no C-RPs exist.
4.
(Optional.) Configure the
device to use RP hash
algorithm described in RFC
2362.
bsr-rp-mapping rfc2362
By default, the device uses the
BSR RP hash algorithm
described in RFC 4601.
Configuring the maximum number of IPv6 BIDIR-PIM RPs
In an IPv6 BIDIR-PIM domain, one DF election per RP is implemented on all IPv6 PIM-enabled
interfaces. As a best practice, do not configure multiple IPv6 BIDIR-PIM to avoid unnecessary DF
elections.
This configuration sets a limit on the number of IPv6 BIDIR-PIM RPs. If the number of RPs exceeds
the limit, excess RPs do not take effect and can be used only for DF election rather than IPv6
multicast data forwarding. The system does not delete these excess RPs. They must be deleted
manually.
To configure the maximum number of RPs:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter IPv6 PIM view.
ipv6
pim
[
vpn-instance
vpn-instance-name
]
N/A
3.
Configure the maximum
number of RPs.
bidir-rp-limit
limit
The default upper limit depends
on the device model.