Brocade BigIron RX Series Configuration Guide - Manual (Page 762)

684 BigIron RX Series Configuration Guide
53-1002484-04
PIM Sparse
24
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.
If you explicitly specify the RP, the BigIron RX 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.
To specify the IP address of the RP, enter commands such as the following.
BigIron RX(config)# router pim
BigIron RX(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 BigIron RX will use the specified RP and ignore group-to-RP
mappings received from the BSR.
ACL based RP assignment
The rp-address command allows multiple static RP configurations. For each static RP, an ACL can
be given as an option to define the multicast address ranges that the static RP permit or deny to
serve.
A static RP by default serves the range of 224.0.0.0/4 if the RP is configured without an ACL name.
If an ACL name is given but the ACL is not defined, the static RP is set to inactive mode and it will
not cover any multicast group ranges.
The optional static RP ACL can be configured as a standard ACL or as an extended ACL. For an
extended ACL, the destination filter will be used to derive the multicast group range and all other
filters are ignored. The content of the ACL needs to be defined in the order of prefix length; the
longest prefix must be placed at the top of the ACL definition.
If there are overlapping group ranges among the static RPs, the static RP with the longest prefix
match will be selected. If more than one static RP covers the exact same group range, the highest
IP static RP will be used.
Configuration considerations
• The Static RP has higher precedence over RP learnt from the BSR.
• There is a limit of 32 static RPs in the systems.
Configuring an ACL based RP assignment
To configure an ACL based RP assignment; enter commands such as the following.
BigIron RX(config)# router pim
BigIron RX(config-pim-router)# rp-address 130.1.1.1 acl1