beautypg.com

4 boostrap router configuration – CANOGA PERKINS 9175 Configuration Guide User Manual

Page 152

background image

CanogaOS Configuration Guide

24-10

interface eth-0-1
ip pim sparse-mode
!
interface eth-0-2
ip pim sparse-mode
!
ip pim rp-candidate eth-0-1


The highest priority router is chosen as the RP. If two or more routers have the same
priority, a hash function in the BSR mechanism is used to choose the RP, to make sure
that all routers in the PIM-domain have the same RP for the same group.
Use the ip pim rp-candidate IFNAME PRIORITY command to change the default priority
of any candidate RP.
At Router_D, the show ip pim sparse-mode rp-hash command shows that Router_C has
been chosen as the RP for a specified group.

PIM group-to-RP mappings
Use the show ip pim sparse-mode rp mapping command to display the group-to-RP
mapping details. The output displays information about RP candidates. There are two
RP candidates for the group range 224.0.0.0/4. RP Candidate 10.10.1.5 has a default
priority of 192, whereas, RP Candidate 172.16.1.2 has been configured to have a priority
of 2. Since RP candidate 172.16.1.2 has a higher priority, it is selected as RP for the
multicast group 224.0.0.0/24

DUT# show ip pim sparse-mode rp mapping
This system is the Bootstrap Router (v2)
Group(s): 224.0.0.0/4
RP: 10.10.1.5
Info source: 172.16.1.2, via bootstrap, priority 192
Uptime: 00:00:13, expires: 00:02:29
RP: 172.16.1.2
Info source: 172.16.1.2, via bootstrap, priority 2
Uptime: 00:34:42, expires: 00:01:49


RP details
To display information about the RP router for a particular group, use the following
command. This output displays that 172.16.1.2 has been chosen as the RP for the
multicast group 224.0.1.3.

Router_D# show ip pim sparse-mode rp-hash 224.0.1.3
Group(s): 224.0.0.0/4
RP: 172.16.1.2
Info source: 172.16.1.2, via bootstrap


After RP information reaches all PIM routers in the domain, various state machines
maintain all routing states as the result of Join/Prune from group membership. To display
information on interface details and the multicast routing table, refer to the Configuring
RP Statically section above

24.4 Boostrap Router Configuration

Every PIM multicast group needs to be associated with the IP address of a Rendezvous
Point (RP). This address is used as the root of a group-specific distribution tree whose
branches extend to all nodes in the domain that want to receive traffic sent to the group.