Statically Specifying The Rp - Foundry Networks Switch and Router Installation And Configuration Manual

Foundry Switch and Router Installation and Configuration Guide
By default, this command configures the Layer 3 Switch as a candidate RP for all group numbers beginning with
224. As a result, the Layer 3 Switch 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 Layer 3 Switch is a candidate RP by explicitly adding a range.
BigIron(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 sub-net
mask. In this example, the Layer 3 Switch is a candidate RP for all groups that begin with 224.126. When you
add a range, you override the default. The Layer 3 Switch then becomes a candidate RP only for the group
address range(s) you add.
You also can change the group numbers for which the Layer 3 Switch 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(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 Layer 3 Switch becomes a
candidate RP for groups 224.126.0.0 – 224.126.21.255 and groups 224.126.23.0 – 224.126.255.255.
USING THE WEB MANAGEMENT INTERFACE
You cannot configure PIM Sparse parameters using the Web management interface.

Statically Specifying the RP

Foundry Networks 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, you can
do using the following CLI method.
If you explicitly specify the RP, the Layer 3 Switch uses the specified RP for all group-to-RP mappings and
overrides the set of candidate RPs supplied by the BSR.
NOTE: Specify the same IP address as the RP on all PIM Sparse routers within the PIM Sparse domain. Make
sure the router is on the backbone or is otherwise well connected to the rest of the network.
USING THE CLI
To specify the IP address of the RP, enter commands such as the following:
BigIron(config)# router pim
BigIron(config-pim-router)# rp-address 207.95.7.1
Syntax: [no] rp-address <ip-addr>
The <ip-addr> parameter specifies the IP address of the RP.
The command in the example above identifies the router interface at IP address 207.95.7.1 as the RP for the PIM
Sparse domain. The Layer 3 Switch will use the specified RP and ignore group-to-RP mappings received from
the BSR.
USING THE WEB MANAGEMENT INTERFACE
You cannot configure PIM Sparse parameters using the Web management interface.
18 - 16 December 2000