Purpose
Command or Action
•
For
interface-id
, enter the interface on this device from which the
BSR address is derived to make it a candidate. This interface must
Example:
Device(config)#
ip pim bsr-candidate
be enabled with PIM. Valid interfaces include physical ports, port
channels, and VLANs.
gigabitethernet 1/0/3 28 100
•
For
hash-mask-length
, specify the mask length (32 bits maximum)
that is to be ANDed with the group address before the hash function
is called. All groups with the same seed hash correspond to the
same RP. For example, if this value is 24, only the first 24 bits of
the group addresses matter.
•
(Optional) For
priority
, enter a number from 0 to 255. The BSR
with the larger priority is preferred. If the priority values are the
same, the device with the highest IP address is selected as the BSR.
The default is 0.
Returns to privileged EXEC mode.
end
Step 4
Example:
Device(config-if)#
end
Verifies your entries.
show running-config
Step 5
Example:
Device#
show running-config
(Optional) Saves your entries in the configuration file.
copy running-config startup-config
Step 6
Example:
Device#
copy running-config
startup-config
Related Topics
PIM v2 BSR, on page 120
Example: Configuring Candidate BSRs, on page 159
Configuring the Candidate RPs (CLI)
You can configure one or more candidate RPs. Similar to BSRs, the RPs should also have good connectivity
to other devices and be in the backbone portion of the network. An RP can serve the entire IP multicast address
space or a portion of it. Candidate RPs send candidate RP advertisements to the BSR. When deciding which
devices should be RPs, consider these options:
IP Multicast Routing Configuration Guide, Cisco IOS XE Release 3SE (Catalyst 3650 Switches)
142
OL-29890-01
Configuring PIM
Configuring PIMv2 BSR
