From: Ivan (ivan@iip.net)
Date: Fri Dec 08 2006 - 11:05:51 ART
In BSR: minimal priority - more preferred.
On Thursday 07 December 2006 19:36, Serdar Kut wrote:
> Hi Gs,
>
> I have a question about sparse mode candidate rp priority. the goal I want
> to go for is, having R1 RP and R3 will be backup RP.
>
> after configuring R1 and R3 like below;
>
> R3
>
> ip pim rp-candidate Loopback0 group-list 48 priority 50
>
> R1
>
> ip pim rp-candidate Loopback0 group-list 48 priority 200
>
> and making R6 the BSR, I have the following output from the pim sparse mode
> enable router R5:
>
> R5#sh ip pim rp mapping
> PIM Group-to-RP Mappings
>
> Group(s) 227.21.22.23/32
> RP 150.1.3.3 (?), v2
> Info source: 11.11.6.6 (?), via bootstrap, priority 50, holdtime 142
> Uptime: 00:13:12, expires: 00:02:11
> RP 150.1.1.1 (?), v2
> Info source: 11.11.6.6 (?), via bootstrap, priority 200, holdtime 137
> Uptime: 00:13:20, expires: 00:02:07
> Group(s) 227.31.32.33/32
> RP 150.1.3.3 (?), v2
> Info source: 11.11.6.6 (?), via bootstrap, priority 50, holdtime 142
> Uptime: 00:13:12, expires: 00:02:11
> RP 150.1.1.1 (?), v2
> Info source: 11.11.6.6 (?), via bootstrap, priority 200, holdtime 134
> Uptime: 00:13:20, expires: 00:02:05
> R5#
>
> and R5 gets multicast feed from 227.21.22.23 and 227.31.32.33 and its
> mrouting table is like this:
>
> R5#sh ip mro
> IP Multicast Routing Table
> Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connecte
> d,
> L - Local, P - Pruned, R - RP-bit set, F - Register flag,
> T - SPT-bit set, J - Join SPT, M - MSDP created entry,
> X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
> U - URD, I - Received Source Specific Host Report,
> Z - Multicast Tunnel, z - MDT-data group sender,
> Y - Joined MDT-data group, y - Sending to MDT-data group
> Outgoing interface flags: H - Hardware switched, A - Assert winner
> Timers: Uptime/Expires
> Interface state: Interface, Next-Hop or VCD, State/Mode
>
> (*, 227.21.22.23), 00:17:05/00:02:13, RP 150.1.3.3, flags: SJCL
> Incoming interface: Serial0, RPF nbr 167.65.11.3
> Outgoing interface list:
> FastEthernet0, Forward/Sparse, 00:17:05/00:02:13
>
> (*, 227.31.32.33), 00:17:05/00:02:16, RP 150.1.3.3, flags: SJCL
> Incoming interface: Serial0, RPF nbr 167.65.11.3
> Outgoing interface list:
> FastEthernet0, Forward/Sparse, 00:17:05/00:02:16
>
> (*, 224.0.1.40), 00:21:31/00:02:00, RP 0.0.0.0, flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0, 224.0.1.40, Forward/Sparse, 00:21:20/00:02:00
>
> R5#
>
> it looks like R5 sends joins to R3 which should be indeed back RP, as seen
> from the sh ip pim rp mapping.
>
> any comments??
>
> Serdar
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
-- Ivan
This archive was generated by hypermail 2.1.4 : Tue Jan 02 2007 - 07:50:37 ART