rp-candidate
rp-candidate{ethernetstackid/slot/portnum|loopbacknum|venum|tunnelnum}rp-candidate{add|delete }
group-addr mask-bitsno rp-candidate{ethernetstackid/slot/portnum|loopbacknum|venum|tunnelnum}no rp-candidate{add|delete }
group-addr mask-bitsThe PIM router is not available for selection as an RP.
- ethernetstackid/slot/portnum
- Specifies a physical interface for the candidate RP. On standalone devices specify the interface ID in the format slot/port-id; on stacked devices you must also specify the stack ID, in the format stack-id/slot/port-id.
- add
- Specifies adding a group address or range of group addresses to the default group configured by the those the device is the candidate RP for by default, that is, groups with the prefix 224.0.0.0/4.
- delete
- Specifies deleting a group address or range of group addresses, that were added using the add keyword.
Router PIM configuration mode
The
no rp-candidate command makes the PIM router cease to act as a candidate RP.
The
no rp-candidate add command deletes a group address or range of group addresses that were added using
the
add keyword.
Configuring the
rp-candidate command on an Ethernet, loopback, virtual, or tunnel interface, configures the device
as a candidate RP for all multicast groups with the prefix 224.0.0.0/4, by default.
You can configure the
rp-candidate add command to add to those a group address or range of group addresses. You can configure
the
rp-candidate delete command to delete a group address or range of group addresses that were added to
the default addresses.
The RP is the meeting point for PIM Sparse sources and receivers. A PIM Sparse domain can have multiple RPs, but each PIM Sparse multicast group address can have only one active RP. PIM Sparse routers learn the addresses of RPs and the groups for which they are responsible from messages that the bootstrap router (BSR) sends to each of the PIM Sparse routers.
Although you can configure the device as only a candidate BSR or an RP, it is recommended that you configure the same interface on the same device as both a BSR and an RP.
This example configures a physical device as a candidate RP.
device(config)# router pim device(config-pim-router)# rp-candidate ethernet 1/2/2
This example uses a loopback interface to configure a device as a candidate RP.
device(config)# router pim device(config-pim-router)# rp-candidate loopback 1
This example uses a virtual interface to configure a device as a candidate RP.
device(config)# router pim device(config-pim-router)# rp-candidate ve 120
This example configures an address group to the devices for which it is a candidate RP.
device(config)# router pim device(config-pim-router)# rp-candidate add 224.126.0.0 16