Here's what I see:
R2-----R6-----R9 with R2 as the RP (via auto-RP)
R6#sh ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
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
(*, 224.0.1.39), 01:24:41/stopped, RP 6.6.6.6, flags: SJC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/1/0, 144.44.56.2, Forward/Sparse-Dense, 01:24:05/00:02:58
(2.2.2.2, 224.0.1.39), 01:24:41/00:02:12, flags: PTX
Incoming interface: Serial0/1/0, RPF nbr 144.44.56.2
Outgoing interface list: Null
(*, 224.0.1.40), 01:24:48/stopped, RP 6.6.6.6, flags: SPL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list: Null
(2.2.2.2, 224.0.1.40), 01:24:09/00:02:52, flags: LT
Incoming interface: Serial0/1/0, RPF nbr 144.44.56.2
Outgoing interface list:
FastEthernet0/0, Forward/Sparse-Dense, 01:23:58/00:02:57
R6#sh ip pim rp map
PIM Group-to-RP Mappings
Group(s) 225.0.144.1/32
RP 2.2.2.2 (?), v2v1
Info source: 2.2.2.2 (?), elected via Auto-RP
Uptime: 01:25:16, expires: 00:02:11
Group(s) 225.0.144.2/32
RP 2.2.2.2 (?), v2v1
Info source: 2.2.2.2 (?), elected via Auto-RP
Uptime: 01:25:16, expires: 00:02:09
Group(s) 225.0.144.3/32
RP 2.2.2.2 (?), v2v1
Info source: 2.2.2.2 (?), elected via Auto-RP
Uptime: 01:25:16, expires: 00:02:10
Group(s) 225.0.144.4/32
RP 2.2.2.2 (?), v2v1
Info source: 2.2.2.2 (?), elected via Auto-RP
Uptime: 01:25:16, expires: 00:02:10
Group(s): 224.0.0.0/4, Static
RP: 6.6.6.6 (?)
R6#sh ip pim nei
PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
S - State Refresh Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
144.44.6.36 FastEthernet0/0 2d21h/00:01:38 v2 1 / DR S
144.44.56.2 Serial0/1/0 2d21h/00:01:37 v2 1 / S -------R2
144.44.56.5 Serial0/1/0 2d19h/00:01:22 v2 1 / S
144.44.60.9 Serial0/2/0 01:41:44/00:01:26 v2 1 / S ----\
144.44.61.9 Serial0/3/0 01:41:42/00:01:37 v2 1 / S -------R9
-------------------------------------------------------------------------------------
R9#sh ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
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
(*, 224.0.1.40), 01:46:09/stopped, RP 9.9.9.9, flags: SJCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/2/0, Forward/Sparse-Dense, 01:46:09/00:00:00
R9#sh ip pim rp map
PIM Group-to-RP Mappings
Group(s): 224.0.0.0/4, Static
RP: 9.9.9.9 (?)
R9#sh ip pim nei
PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
S - State Refresh Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
144.44.60.6 Serial0/2/0 01:45:49/00:01:18 v2 1 / S -------\
144.44.61.6 Serial0/3/0 01:45:47/00:01:19 v2 1 / S ------------R6
R9#
I think I'm running into a bug because when I do "sh ip pim rp map", it gets stuck for like 10 seconds...
Thanks,
Ron
-----Original Message-----
From: Scott Morris [mailto:smorris_at_ine.com]
Sent: Tuesday, September 08, 2009 2:44 PM
To: Ronald Johns
Cc: Bryan Bartik; ccie forum
Subject: Re: sink RP...
My 2811's still get everything 6 routers deep. I didn't bother to put
multicast on my switches, but will try that later.
R6(config)#do sh ip pim rp map
PIM Group-to-RP Mappings
Group(s) 224.0.0.0/4
RP 1.1.1.1 (?), v2v1
Info source: 1.1.1.1 (?), elected via Auto-RP
Uptime: 01:36:09, expires: 00:02:02
R6(config)#do sh ip mr | b 224.0.1.40
(*, 224.0.1.40), 01:38:05/stopped, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
GigabitEthernet0/0, Forward/Sparse, 01:38:05/00:00:00
(1.1.1.1, 224.0.1.40), 01:36:11/00:02:59, flags: PLTX
Incoming interface: GigabitEthernet0/0, RPF nbr 192.168.56.5
Outgoing interface list: Null
R6(config)#
*Scott Morris*, CCIE/x4/ (R&S/ISP-Dial/Security/Service Provider) #4713,
JNCIE-M #153, JNCIS-ER, CISSP, et al.
JNCI-M, JNCI-ER
evil_at_ine.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Outside US: 775-826-4344
Knowledge is power.
Power corrupts.
Study hard and be Eeeeviiiil......
Ronald Johns wrote:
> I'm seeing varying differences as well. My 2811's with 12.4(25b) and 3560's running 12.2(46)SE don't get maps unless they are directly adjacent to the RP, but my Cat3550 running 12.2(44)SE3 does...
>
> -----Original Message-----
> From: Scott Morris [mailto:smorris_at_ine.com]
> Sent: Tuesday, September 08, 2009 1:33 PM
> To: Bryan Bartik
> Cc: Ronald Johns; ccie forum
> Subject: Re: sink RP...
>
> Mmmm... May want to check your router/image!
>
> -------------------- 7200 with 12.2(25) S9 ---------------
>
> Rack6R2(config)#do sh ip mr | b 224.0.1.40
> (*, 224.0.1.40), 1d12h/00:02:34, RP 0.0.0.0, flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Loopback0, Forward/Sparse, 1d12h/00:02:34
>
> Rack6R2(config)#do sh ip pim rp map
>
> PIM Group-to-RP Mappings
>
> Group(s) 224.0.0.0/4
> RP 160.6.4.4 (?), v2
> Info source: 160.6.4.4 (?), via bootstrap, priority 0
> Uptime: 1d12h, expires: 00:02:48
>
> Rack6R2(config)#
>
> Rack6R2(config)#ip pim rp-addr 160.6.2.2
>
> Rack6R2(config)#do sh ip mr | b 224.0.1.40
> (*, 224.0.1.40), 1d12h/00:02:53, RP 160.6.2.2, flags: SJCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Loopback0, Forward/Sparse, 1d12h/00:02:53
>
> Rack6R2(config)#
>
> Overrides it as you noted, but not supposed to!
>
> -------------------2811 with 12.4(24)T----------------
>
> R2(config)#do sh ip mr | b 224.0.1.40
> (*, 224.0.1.40), 00:04:24/stopped, RP 0.0.0.0, flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0/0/0.1, Forward/Sparse, 00:03:59/00:00:00
> FastEthernet0/0, Forward/Sparse, 00:04:24/00:00:00
>
> (1.1.1.1, 224.0.1.40), 00:01:05/00:02:55, flags: LT
> Incoming interface: FastEthernet0/0, RPF nbr 192.168.12.1
> Outgoing interface list:
> Serial0/0/0.1, Forward/Sparse, 00:01:05/00:00:00
>
> R2(config)#
>
> R2(config)#do sh ip pim rp map
> PIM Group-to-RP Mappings
>
> Group(s) 224.0.0.0/4
> RP 1.1.1.1 (?), v2v1
> Info source: 1.1.1.1 (?), elected via Auto-RP
> Uptime: 00:01:25, expires: 00:02:30
>
> R2(config)#
>
> R2(config)#ip pim rp-addr 2.2.2.2
>
> R2(config)#do sh ip mr | b 224.0.1.40
> (*, 224.0.1.40), 00:05:30/stopped, RP 0.0.0.0, flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0/0/0.1, Forward/Sparse, 00:05:04/00:00:00
> FastEthernet0/0, Forward/Sparse, 00:05:30/00:00:00
>
> (1.1.1.1, 224.0.1.40), 00:02:10/00:02:49, flags: LT
> Incoming interface: FastEthernet0/0, RPF nbr 192.168.12.1
> Outgoing interface list:
> Serial0/0/0.1, Forward/Sparse, 00:02:10/00:00:00
>
> R2(config)#
>
> R2(config)#do sh ip pim rp map
> PIM Group-to-RP Mappings
>
> Group(s) 224.0.0.0/4
> RP 1.1.1.1 (?), v2v1
> Info source: 1.1.1.1 (?), elected via Auto-RP
> Uptime: 00:03:11, expires: 00:02:43
> Group(s): 224.0.0.0/4, Static
> RP: 2.2.2.2 (?)
>
> R2(config)#
>
> R3(config)#do sh ip mr | b 224.0.1.40
> (*, 224.0.1.40), 00:05:41/stopped, RP 0.0.0.0, flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial1/0.1, Forward/Sparse, 00:05:34/00:00:00
> FastEthernet0/0, Forward/Sparse, 00:05:41/00:00:00
>
> (1.1.1.1, 224.0.1.40), 00:02:40/00:02:28, flags: LT
> Incoming interface: Serial1/0.1, RPF nbr 192.168.23.2
> Outgoing interface list:
> FastEthernet0/0, Forward/Sparse, 00:02:40/00:00:00
>
> R3(config)#
>
> R4(config)#do sh ip mr | b 224.0.1.40
> (*, 224.0.1.40), 00:05:22/stopped, RP 0.0.0.0, flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0/1/0, Forward/Sparse, 00:04:50/00:00:00
> FastEthernet0/1, Forward/Sparse, 00:04:54/00:00:00
> FastEthernet0/0, Forward/Sparse, 00:05:22/00:00:00
>
> (1.1.1.1, 224.0.1.40), 00:02:43/00:02:17, flags: LT
> Incoming interface: FastEthernet0/0, RPF nbr 192.168.34.3
> Outgoing interface list:
> FastEthernet0/1, Forward/Sparse, 00:02:43/00:00:00
> Serial0/1/0, Prune/Sparse, 00:02:43/00:00:17, A
>
> R4(config)#
>
> R5(config)#do sh ip mr | b 224.0.1.40
> (*, 224.0.1.40), 00:05:00/stopped, RP 0.0.0.0, flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0/1/0, Forward/Sparse, 00:04:53/00:00:00
> FastEthernet0/1, Forward/Sparse, 00:04:56/00:00:00
> FastEthernet0/0, Forward/Sparse, 00:05:00/00:00:00
>
> (1.1.1.1, 224.0.1.40), 00:02:45/00:02:19, flags: LT
> Incoming interface: FastEthernet0/1, RPF nbr 192.168.45.4
> Outgoing interface list:
> FastEthernet0/0, Forward/Sparse, 00:02:45/00:00:00
> Serial0/1/0, Prune/Sparse, 00:02:45/00:00:14
>
> R5(config)#
>
> R6(config)#do sh ip mr | b 224.0.1.40
> (*, 224.0.1.40), 00:04:41/stopped, RP 0.0.0.0, flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> GigabitEthernet0/0, Forward/Sparse, 00:04:41/00:00:00
>
> (1.1.1.1, 224.0.1.40), 00:02:47/00:02:11, flags: PLTX
> Incoming interface: GigabitEthernet0/0, RPF nbr 192.168.56.5
> Outgoing interface list: Null
>
> R6(config)#
>
> All still show things... (Pause for 10 minutes to allow any timeouts
> and other random boring stuff)
>
> R2(config)#do sh ip pim rp map
> PIM Group-to-RP Mappings
>
> Group(s) 224.0.0.0/4
> RP 1.1.1.1 (?), v2v1
> Info source: 1.1.1.1 (?), elected via Auto-RP
> Uptime: 00:16:28, expires: 00:02:23
> Group(s): 224.0.0.0/4, Static
> RP: 2.2.2.2 (?)
>
> R2(config)#
>
> R2(config)#do sh ip mr | b 224.0.1.40
> (*, 224.0.1.40), 00:20:10/stopped, RP 0.0.0.0, flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0/0/0.1, Forward/Sparse, 00:19:45/00:00:00
> FastEthernet0/0, Forward/Sparse, 00:20:10/00:00:00
>
> (1.1.1.1, 224.0.1.40), 00:16:51/00:02:09, flags: LT
> Incoming interface: FastEthernet0/0, RPF nbr 192.168.12.1
> Outgoing interface list:
> Serial0/0/0.1, Forward/Sparse, 00:16:51/00:00:00
>
> R2(config)#
>
> Still dense... Still moving...
>
> R2(config)#do sh run | in pim rp
> ip pim rp-address 2.2.2.2
>
> R2(config)#do sh ip int br | in 2.2.2.2
> Loopback0 2.2.2.2 YES NVRAM
> up up
> R2(config)#
>
> And on the RP:
>
> R1(config)#do sh ip pim rp map
> PIM Group-to-RP Mappings
> This system is an RP (Auto-RP)
> This system is an RP-mapping agent (Loopback0)
>
> Group(s) 224.0.0.0/4
> RP 1.1.1.1 (?), v2v1
> Info source: 1.1.1.1 (?), elected via Auto-RP
> Uptime: 00:17:51, expires: 00:02:07
> Group(s): 224.0.0.0/4, Static
> RP: 1.1.1.1 (?)
>
> R1(config)#do sh ip mr | b 224.0.1.40
> (*, 224.0.1.40), 00:22:04/stopped, RP 0.0.0.0, flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Loopback0, Forward/Sparse, 00:19:04/00:00:00
> FastEthernet0/0, Forward/Sparse, 00:22:04/00:00:00
>
> (1.1.1.1, 224.0.1.40), 00:18:23/00:02:30, flags: LT
> Incoming interface: Loopback0, RPF nbr 0.0.0.0
> Outgoing interface list:
> FastEthernet0/0, Forward/Sparse, 00:18:23/00:00:00
>
> R1(config)#do sh ip pim rp map
>
> PIM Group-to-RP Mappings
> This system is an RP (Auto-RP)
> This system is an RP-mapping agent (Loopback0)
>
> Group(s) 224.0.0.0/4
> RP 1.1.1.1 (?), v2v1
> Info source: 1.1.1.1 (?), elected via Auto-RP
> Uptime: 00:18:38, expires: 00:02:21
> Group(s): 224.0.0.0/4, Static
> RP: 1.1.1.1 (?)
>
> R1(config)#do sh run | in pim
> ip pim sparse-mode
> ip pim sparse-mode
> ip pim rp-address 1.1.1.1
> ip pim autorp listener
> ip pim send-rp-announce Loopback0 scope 15
> ip pim send-rp-discovery Loopback0 scope 15
>
> R1(config)#do sh ip int br | in 1.1.1.1
> Loopback0 1.1.1.1 YES NVRAM
> up up
> R1(config)#
>
> So I think it may depend on what IOS/platform you are using. But the
> way it's SUPPOSED to work, you should not get overridden unless you use
> the "override" feature. Nor should it affect how you're sending things out.
>
> Unfortunately, on a 7200 on my SP rack (12.2S) it did.. But on R&S
> racks, with a 12.4T image, it does not.
> Just my observations, of course... Your mileage may vary!
>
>
>
>
>
> *Scott Morris*, CCIE/x4/ (R&S/ISP-Dial/Security/Service Provider) #4713,
>
> JNCIE-M #153, JNCIS-ER, CISSP, et al.
>
> JNCI-M, JNCI-ER
>
> evil_at_ine.com
>
>
> Internetwork Expert, Inc.
>
> http://www.InternetworkExpert.com
>
> Toll Free: 877-224-8987
>
> Outside US: 775-826-4344
>
>
> Knowledge is power.
>
> Power corrupts.
>
> Study hard and be Eeeeviiiil......
>
>
>
> Bryan Bartik wrote:
>
>> Ronald,
>>
>> If you have a static RP defined, the auto-RP groups will not
>> inherently act in dense mode.
>>
>> R9(config)#ip pim rp-address 200.200.200.9
>>
>> R9#sho ip mroute 224.0.1.40 | be \(
>> (*, 224.0.1.40), 00:09:05/00:00:14, RP 200.200.200.9, flags: SJCL
>> <----- S for Sparse
>> Incoming interface: Null, RPF nbr 0.0.0.0
>> Outgoing interface list:
>> Serial1/1, Forward/Sparse-Dense, 00:09:05/00:00:14
>>
>> Consider the following topology: R4---R6---R9 with R4 as RP (via auto-RP)
>>
>> With each router having a sink RP as its own loopback, the auto-RP
>> groups operate in sparse-mode. R9 thinks of itself as RP, so it never
>> sends any joins up to R6. R6 never populates its OIL for the auto-RP
>> groups with R9's interface. R4 sends RP mapping messages to R6, but R6
>> does not forward them because the OIL for those groups is NULL. R9
>> never learns of the real RP and cannot join any multicast groups being
>> registered at R4.
>>
>> On Mon, Sep 7, 2009 at 7:33 AM, Ronald Johns <rj686b_at_att.com
>> <mailto:rj686b_at_att.com>> wrote:
>>
>> Cool - that's what I thought. The proctor guide answer had an ACL
>> configured to deny the Auto-RP addresses and I couldn't figure out
>> why. (IPexpert Vol 3 Lab 4 Task 5.2) Thanks for clearing this up!
>>
>> - Ron
>>
>> -----Original Message-----
>> From: Scott Morris [mailto:smorris_at_ine.com <mailto:smorris_at_ine.com>]
>> Sent: Monday, September 07, 2009 6:53 AM
>> To: Hoogen
>> Cc: Jacob Uecker; Ronald Johns; ccie forum
>> Subject: Re: sink RP...
>>
>> Right... So by that mere definition alone, you won't need to worry
>> about excluding the Auto-RP addresses from the sink-hole due to
>> the fact
>> that they are SENT in dense mode, regardless.... So there won't be an
>> inherent need to "join" those groups via an RP. Therefore you won't
>> sinkhole yourself.
>>
>> ;)
>>
>>
>>
>>
>> *Scott Morris*, CCIE/x4/ (R&S/ISP-Dial/Security/Service Provider)
>> #4713,
>>
>> JNCIE-M #153, JNCIS-ER, CISSP, et al.
>>
>> JNCI-M, JNCI-ER
>>
>> evil_at_ine.com <mailto:evil_at_ine.com>
>>
>>
>> Internetwork Expert, Inc.
>>
>> http://www.InternetworkExpert.com
>>
>> Toll Free: 877-224-8987
>>
>> Outside US: 775-826-4344
>>
>>
>> Knowledge is power.
>>
>> Power corrupts.
>>
>> Study hard and be Eeeeviiiil......
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> Bryan Bartik
>> CCIE #23707 (R&S), CCNP
>> Sr. Support Engineer - IPexpert, Inc.
>> URL: http://www.IPexpert.com
Blogs and organic groups at http://www.ccie.net
Received on Tue Sep 08 2009 - 15:19:46 ART
This archive was generated by hypermail 2.2.0 : Sun Oct 04 2009 - 07:42:03 ART