From: Jeff Andiorio (jandiorio@gmail.com)
Date: Mon Mar 02 2009 - 11:49:06 ARST
Have you verified that the source is sending an IGMP join message?
as stated earlier, an igmp static group command on the interface of
the source will certainly help move things along.
Jeff
On Mon, Mar 2, 2009 at 6:33 AM, Pavel Bykov <slidersv@gmail.com> wrote:
> If you don't even see an S,G, that means you have a TTL problem.
> Sniff out the traffic, it'll probably have TTL=1
>
> On Sat, Feb 28, 2009 at 2:17 PM, Mahesh Shivaswamy
> <maheshs.cisco@gmail.com>wrote:
>
>> Hi,
>>
>> I have a multicast source connected to port G2/2 & the source is
>> streaming to group 239.192.0.1 with IP 10.1.105.6 but I do not see the
>> source getting registered with RP & an (S,G) entry for the group, I
>> have the following configs on 6509,
>>
>> 6509#sh run int gi2/2
>> Building configuration...
>>
>> Current configuration : 155 bytes
>> !
>> interface GigabitEthernet2/2
>> description Connection test server
>> ip address 10.1.105.5 255.255.255.252
>> ip pim sparse-mode
>> load-interval 30
>> end
>>
>> 6509#sh run int loop 1
>> Building configuration...
>>
>> Current configuration : 139 bytes
>> !
>> interface Loopback1
>> ip address 10.255.0.1 255.255.255.252
>> ip pim sparse-mode
>> end
>>
>>
>> router eigrp 1
>> network 10.0.0.0
>> no auto-summary
>>
>>
>> ip pim rp-address 10.255.0.1 grp-acl
>> !
>> ip access-list standard grp-acl
>> permit 239.192.0.0 0.0.0.255
>>
>>
>>
>> 6509#sh ip pim rp mapping
>> PIM Group-to-RP Mappings
>>
>> Acl: grp-acl, Static
>> RP: 10.255.0.1 (?)
>>
>>
>> 6509#sh ip mroute 239.192.0.1
>> 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
>> V - RD & Vector, v - Vector
>> Outgoing interface flags: H - Hardware switched, A - Assert winner
>> Timers: Uptime/Expires
>> Interface state: Interface, Next-Hop or VCD, State/Mode
>>
>> (*, 239.192.0.1), 05:09:55/00:03:21, RP 10.255.0.1, flags: SJC
>> Incoming interface: Null, RPF nbr 0.0.0.0
>> Outgoing interface list:
>> Vlan10, Forward/Sparse, 03:57:30/00:02:18
>> TenGigabitEthernet8/6, Forward/Sparse, 05:09:11/00:03:06
>> TenGigabitEthernet8/2, Forward/Sparse, 05:09:41/00:02:46
>> TenGigabitEthernet8/7, Forward/Sparse, 05:09:41/00:02:50
>> TenGigabitEthernet4/7, Forward/Sparse, 05:09:45/00:03:21
>> TenGigabitEthernet7/10, Forward/Sparse, 05:09:54/00:03:20
>> TenGigabitEthernet4/8, Forward/Sparse, 05:09:55/00:03:21
>>
>> Any suggestion will be of great help...
>>
>> rgds
>> Mahesh
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>>
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> Pavel Bykov
> ----------------
> Don't forget to help stopping the braindumps, use of which reduces value of
> your certifications. Sign the petition at http://www.stopbraindumps.com/
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Mon Apr 06 2009 - 06:44:03 ART