From: Jian Gu (guxiaojian@gmail.com)
Date: Sun Dec 03 2006 - 18:23:45 ART
This does not seem to have anything to do with MSDP, RP did not get (*,G)
join from down stream.
On 12/2/06, Michael Zuo <mzuo@ixiacom.com> wrote:
>
> Hi group
>
>
>
> After the MSDP peer is up and correct multicast source info received
> thru SA, what kind debug steps do I need to perform if multicast ping
> "ping 239.1.1.1" from source is not successful (I've checked a number of
> things below)? How do I check if the peer/RP associated with the source
> is forward traffic?
>
>
>
>
>
> Thanks a lot...
>
>
>
>
>
>
>
> Rack1R3#sh ip ms pee
>
> MSDP Peer 1.1.1.1 (?), AS 100
>
> Connection status:
>
> State: Up, Resets: 0, Connection source: Loopback0 (3.3.3.3)
>
> Uptime(Downtime): 00:28:53, Messages sent/received: 31/33
>
> Output messages discarded: 0
>
> Connection and counters cleared 00:29:21 ago
>
> SA Filtering:
>
> Input (S,G) filter: none, route-map: none
>
> Input RP filter: none, route-map: none
>
> Output (S,G) filter: none, route-map: none
>
> Output RP filter: none, route-map: none
>
> SA-Requests:
>
> Input filter: none
>
> Peer ttl threshold: 0
>
> SAs learned from this peer: 2
>
> Input queue size: 0, Output queue size: 0
>
> Rack1R3#
>
>
>
> Rack1R3#sh ip ms sa
>
> MSDP Source-Active Cache - 2 entries
>
> (4.4.4.4, 239.1.1.1), RP 1.1.1.1, BGP/AS 0, 00:21:53/00:02:57, Peer
> 1.1.1.1
>
> (150.1.14.4, 239.1.1.1), RP 1.1.1.1, BGP/AS 0, 00:20:55/00:01:01, Peer
> 1.1.1.1
>
> Rack1R3#
>
>
>
> Rack1R3#sh ip pim rp
>
> Group: 239.1.1.1, RP: 3.3.3.3, next RP-reachable in 00:00:18
>
> Group: 224.0.1.40, RP: 3.3.3.3, next RP-reachable in 00:00:43
>
> Rack1R3#sh ip mr
>
> 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
>
>
>
> (*, 239.1.1.1), 00:25:27/00:02:35, RP 3.3.3.3, flags: SJCL
>
> Incoming interface: Null, RPF nbr 0.0.0.0
>
> Outgoing interface list:
>
> Loopback0, Forward/Sparse, 00:25:27/00:02:35
>
>
>
> (*, 224.0.1.40), 00:37:26/00:02:33, RP 3.3.3.3, flags: SJCL
>
> Incoming interface: Null, RPF nbr 0.0.0.0
>
> Outgoing interface list:
>
> Loopback0, Forward/Sparse, 00:37:26/00:02:33
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Tue Jan 02 2007 - 07:50:36 ART