CANOGA PERKINS CanogaOS Configuration Guide - Manual (Page 184)

CanogaOS Configuration Guide
Proprietary & Confidential Canoga Perkins Metro Ethernet Switches Page 184 of 350
Router_C# show ip pim sparse-mode mroute
IP Multicast Routing Table
(*,*,RP) Entries: 0
(*,G) Entries: 1
(S,G) Entries: 0
(S,G,rpt) Entries: 0
(*, 224.0.1.3)
RP: 10.10.1.5
RPF nbr: 0.0.0.0
RPF idx: None
Upstream State: JOINED
Local ................................
Joined j...............................
Asserted ................................
Outgoing o...............................
Configuring RP dynamically
A static configuration of RP works for a small, stable PIM domain; however, it is not practical
for a large and not-sostable internetwork. In such a network, if the RP fails, the network
administrator might have to change the static configurations on all PIM routers. Another reason
for choosing dynamic configuration is a higher routing traffic leading to a change in the RP.
We use the BSR mechanism to dynamically maintain the RP information. For configuring RP
dynamically in the above scenario, Router_C on eth-0-1 and Router_D on eth-0-1 are configured
as Candidate RP using the ip pim rpcandidate command. Router_D on eth-0-1 is also configured
as Candidate BSR. Since no other router has been configured as Candidate BSR, the Router_D
becomes the BSR router, and is responsible for sending group-to-RP mapping information to all
other routers in this PIM domain.
The following output displays the complete configuration at Router_C and Router_D:
Router_D# show run
!
interface eth-0-0
!
interface eth-0-1
ip pim sparse-mode
!
interface eth-0-2
ip pim sparse-mode
!