Re: Multicast Not working

one more thing i noticed , when i configure a group on R6 on any of the
interface , BB1 is able to ping but if i configure it on R1 , BB1 is not
able to ping.

On Mon, Jun 15, 2009 at 11:14 PM, dip <diptanshu.singh_at_gmail.com> wrote:

> yes chris
>
>
> On Mon, Jun 15, 2009 at 11:13 PM, Chris Breece <cbreece1_at_gmail.com> wrote:
>
>> Hrm, it's getting the *,G...
>>
>> (*, 224.1.1.1), 00:04:19/00:01:49, RP 150.1.5.5, flags: SPF
>> Incoming interface: Serial0/0/0.101, RPF nbr 54.1.1.6
>> Outgoing interface list: Null
>>
>> stupid question, but can BB1 ping 150.1.5.5?
>>
>> Chris
>>
>>
>>
>>
>> On Mon, Jun 15, 2009 at 1:30 PM, dip <diptanshu.singh_at_gmail.com> wrote:
>>
>>> Here is the BB1 config , mroute and rp mappings.
>>>
>>> BB1 Config:
>>>
>>> ip pim autorp listener
>>> interface Serial0/0/0.101 point-to-point
>>> description PVC 101 to Rack1
>>> ip address 54.1.1.254 255.255.255.0
>>> ip authentication mode eigrp 10 md5
>>> ip authentication key-chain eigrp 10 EIGRP
>>> ip pim sparse-mode
>>> ipv6 address 2001:54:254:1::254/64
>>> ipv6 address FE80::254 link-local
>>> ipv6 rip RIPng enable
>>> ipv6 ospf 1 area 0
>>> frame-relay interface-dlci 101
>>> end
>>>
>>>
>>>
>>> BB1#sh ip pim rp mapping
>>> PIM Group-to-RP Mappings
>>>
>>> Group(s) 224.0.0.0/4
>>> RP 150.1.5.5 (?), v2v1
>>> Info source: 150.1.1.1 (?), elected via Auto-RP
>>> Uptime: 00:20:22, expires: 00:00:32
>>> Group(s) 224.1.1.1/32
>>> RP 150.1.5.5 (?), v2v1
>>> Info source: 150.1.1.1 (?), elected via Auto-RP
>>> Uptime: 00:04:10, expires: 00:03:00
>>> Group(s) 224.2.2.2/32
>>> RP 150.1.5.5 (?), v2v1
>>> Info source: 150.1.1.1 (?), elected via Auto-RP
>>> Uptime: 00:04:10, expires: 00:02:55
>>> Group(s) 224.3.3.3/32
>>> RP 150.1.5.5 (?), v2v1
>>> Info source: 150.1.1.1 (?), elected via Auto-RP
>>> Uptime: 00:04:10, expires: 00:02:57
>>>
>>>
>>>
>>> BB1#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.1.1.1), 00:04:19/00:01:49, RP 150.1.5.5, flags: SPF
>>> Incoming interface: Serial0/0/0.101, RPF nbr 54.1.1.6
>>> Outgoing interface list: Null
>>>
>>> (*, 224.0.1.39), 00:21:50/stopped, RP 0.0.0.0, flags: D
>>> Incoming interface: Null, RPF nbr 0.0.0.0
>>> Outgoing interface list:
>>> Serial0/0/0.101, Forward/Sparse, 00:21:50/00:00:00
>>>
>>> (150.1.1.1, 224.0.1.39), 00:01:21/00:01:38, flags: PT
>>> Incoming interface: Serial0/0/0.101, RPF nbr 54.1.1.6
>>> Outgoing interface list: Null
>>>
>>> (*, 224.0.1.40), 00:22:30/stopped, RP 0.0.0.0, flags: DCL
>>> Incoming interface: Null, RPF nbr 0.0.0.0
>>> Outgoing interface list:
>>> Serial0/0/0.101, Forward/Sparse, 00:22:30/00:00:00
>>>
>>> (150.1.1.1, 224.0.1.40), 00:21:54/00:02:27, flags: PLTX
>>> Incoming interface: Serial0/0/0.101, RPF nbr 54.1.1.6
>>> Outgoing interface list: Null
>>>
>>> (150.1.5.5, 224.0.1.40), 00:21:53/00:02:04, flags: PLTX
>>> Incoming interface: Serial0/0/0.101, RPF nbr 54.1.1.6
>>> Outgoing interface list: Null
>>>
>>> BB1#

Blogs and organic groups at http://www.ccie.net
Received on Mon Jun 15 2009 - 23:16:53 ART