198 CHAPTER 7: MULTICAST PROTOCOL
address is considered better when the priority is the same. If the new BSR
address is better, the candidate BSR will replace its BSR address and stop
regarding itself as the BSR. Otherwise, the candidate BSR will keep its BSR
address and continue to regard itself as the BSR.
Perform the following configuration in PIM view.
Candidate-BSRs should be configured on the routers in the network backbone. By
default, no BSR is set. The default priority is 0.
One Switch can only 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 a 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.
When configuring RP, 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. 3Com recommends that you
configure Candidate RP on the backbone router.
Configuring Static RP
Static RP serves as the backup of dynamic RP, so as to improve network robusticity.
Perform the following configuration in PIM view.
Table 214 Configuring candidate-BSRs
Operation Command
Configure a candidate-BSR c-bsr
interface-type interface_number
hash_mask_len
[
priority
]
Remove the candidate-BSR
configured
undo c-bsr
Table 215 Configuring candidate-RPs
Operation Command
Configure a candidate-RP c-rp
interface_type interface_number
[
group-policy
acl_number
| priority
priority_value
]*
Remove the candidate-RP
configured
undo c-rp {
interface_type interface_number
|
all }
Table 216 Configuring Static RP
Operation Command
Configure static RP static-rp
rp_address
[
acl_number
]
Remove the configured static RP undo static-rp
rp_address
To Next Page