From: joshua atterbury (joshuaatterbury@gmail.com)
Date: Thu Jan 01 2009 - 01:54:09 ARST
For your last question about pinging a multicast group.
When you ping a multicast group, The router originates a ping request for
all pim enabled loopbacks and the physical pim enabled interface.
To check this scenario do a "debug ip mpacket" on a router then run the ping
command, This will show you all the mcast ping packets, Beaware that if you
are testing things like ttl thresholds etc then the results can be confusing
at first, As the pings originated from the loopback will have their ttl
value as 1 lower than the packet originated from the physical interface. Due
to these packets being routed from the loopback to the physical interface.
Hope this helps.
Josh.
On Thu, Jan 1, 2009 at 1:27 PM, Rado Vasilev <decklandv@gmail.com> wrote:
> Hi,
>>
>> I am good in configuring Multicast but weak in it troubleshooting if
>> devices
>> are not giving required result. Anyone please tell me some commands and
>> steps to identify cause of problem?
>>
>
> usually problems are related to failed RPF check.
>
>>
>>
>> Tell me for troubleshooting, i enable "debug ip mrouting", "debug ip
>> mpacket" but don't get any debug report when ping multicast group what
>> would
>> be reason ?
>>
>
> configure 'no ip mroute-cache' on the interfaces first.'
>
>
>> Another thing when we ping a multicast group, will source ip be of
>> loopback
>> interface ?
>>
>
>
> all ifaces
>
>
>
>
> regards,
> rado
>
>
> 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 : Sun Mar 01 2009 - 09:43:36 ARST