Dell BigIron RX Series, Configuration Manual

Page: 686 / 1458

610 BigIron RX Series Configuration Guide
53-1002253-01
PIM Sparse
23
The ethernet <slot> / <portnum> | loopback <num> | ve <num> parameter specifies the interface.
The BigIron RX will advertise the specified interface’s IP address as a candidate RP.
•
Enter ethernet <slot> / <portnum> for a physical interface (port).
•
Enter ve <num> for a virtual interface.
•
Enter loopback <num> for a loopback interface.
By default, this command configures the BigIron RX as a candidate RP for all group numbers
beginning with 224. As a result, the BigIron RX is a candidate RP for all valid PIM Sparse group
numbers. You can change this by adding or deleting specific address ranges. The following example
narrows the group number range for which the BigIron RX is a candidate RP by explicitly adding a
range.
BigIron RX(config-pim-router)# rp-candidate add 224.126.0.0 16
Syntax: [no] rp-candidate add <group-addr> <mask-bits>
The <group-addr> <mask-bits> specifies the group address and the number of significant bits in
the subnet mask. In this example, the BigIron RX is a candidate RP for all groups that begin with
224.126. When you add a range, you override the default. The BigIron RX then becomes a
candidate RP only for the group address ranges you add.
You also can change the group numbers for which the BigIron RX is a candidate RP by deleting
address ranges. For example, to delete all addresses from 224.126.22.0 – 224.126.22.255, enter
the following command.
BigIron RX(config-pim-router)# rp-candidate delete 224.126.22.0 24
Syntax: [no] rp-candidate delete <group-addr> <mask-bits>
The usage of the <group-addr> <mask-bits> parameter is the same as for the rp-candidate add
command.
If you enter both commands shown in the example above, the net effect is that the BigIron RX
becomes a candidate RP for groups 224.126.0.0 – 224.126.21.255 and groups 224.126.23.0 –
224.126.255.255.
Updating PIM-Sparse forwarding entries with new RP configuration
If you make changes to your static RP configuration, the entries in the PIM-Sparse multicast
forwarding table continue to use the old RP configuration until they are aged out.
The clear pim rp-map command allows you to update the entries in the static multicast forwarding
table immediately after making RP configuration changes. This command is meant to be used with
rp-address command.
To update the entries in a PIM sparse static multicast forwarding table with new RP configuration,
enter the following command at the privileged EXEC level of the CLI.
BigIron RX(config)# clear pim rp-map
Syntax: clear pim rp-map
Statically specifying the RP
Brocade recommends that you use the PIM Sparse protocol’s RP election process so that a backup
RP can automatically take over if the active RP router becomes unavailable. However, if you do not
want the RP to be selected by the RP election process but instead you want to explicitly identify the
RP by its IP address, use the rp-address command.