Technical data

Configuring PIM-SM 221
Candidate-BSRs should be configured on the routers in the network backbone. By
default, no BSR is set. The default priority is 0.
Only one router can be configured with one candidate-BSR. When a
candidate-BSR is configured on another interface, it will replace the previous
configuration.
Configuring Candidate-RPs
In PIM-SM, the shared tree built by the multicast routing data is rooted at the RP.
There is mapping from a multicast group to an RP. A multicast group can be
mapped to an RP. Different groups can be mapped to one RP.
Perform the following configuration in PIM view.
If the range of the served multicast group is not specified, the RP will serve all
multicast groups. Otherwise, the range of the served multicast group is the
multicast group in the specified range. It is suggested to configure Candidate RP
on the backbone router.
Configuring Static RP
Static RP serves as the backup of dynamic RP to make the network more robust.
Perform the following configuration in PIM view.
Basic ACLs can control the range of the multicast group served by static RP.
If static RP is in use, all routers in the PIM domain must adopt the same
configuration. If the configured static RP address is the interface address of the
local router whose state is UP, the router will function as the static RP. It is
unnecessary to enable PIM on the interface that functions as static RP.
When the RP elected from BSR mechanism is valid, static RP does not work.
Remove the candidate-BSR configured undo c-bsr
Table 36 Configuring Candidate-RPs
Operation Command
Configure a candidate-RP c-rp interface-type interface-number [
group-policy acl-number ]
Remove the candidate-RP configured undo c-rp interface-type interface-number
Table 37 Configuring Static RP
Operation Command
Configure static RP static-rp rp-address [ acl-number ]
Configure static RP undo static-rp
Table 35 Configuring Candidate-BSRs
Operation Command