Specifying Static Rps That Support All Groups - HP 7102dl - ProCurve Secure Router Configuration Manual

N o t e s
For the simplest configuration, and the configuration least prone to errors,
you should allow all RPs to support any group. There is no reason to configure
different RPs for various groups unless you expect these conditions to be true:
only certain areas of the network will use certain groups
having a router act as RP for groups expected in its area will significantly
decrease bandwidth usage
routers will not immediately switch to the SP tree

Specifying Static RPs that Support All Groups

To specify the IP address of a router that you have selected as a potential RP,
move to the PIM configuration mode context and enter:
Syntax: rp-address <A.B.C.D>
The command enables the router specified to act as RP for all multicast
groups. Enter this command on all routers in the PIM domain.
You can specify up to four router IP addresses in the RP set. Each router can
potentially act as RP for any multicast group. However, the router will only
actually do so if selected by the hash function PIM routers perform when they
add a new group to their multicast routing tables.
If you configure only one RP on a router and that RP fails, you must manually
reconfigure a new RP on each router.
Every router must have exactly the same RPs in their RP sets. For example,
if you allow Router A to use itself or Router B as RP, it is not enough to allow
Router B to use itself. You must also add Router A to Router B's RP set.
Otherwise, Router B would be left out of multicasts for which Router A selects
itself as the RP.
The IP address specified for an RP must be exactly the same address specified
for that RP on every other router in the WAN. It is not enough to specify any
IP address on one of the RP's interfaces. For this reason, it can be a good idea
to use the IP address of a loopback interface to identify an RP.
Configuring Multicast Support with PIM-SM
Configuring PIM-SM
13-31