11-20-2011 03:32 PM - edited 03-04-2019 02:20 PM
Hi all,
Can you please explain below output -
show ip mroute 239.9.69.39
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, E - Extranet,
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.9.69.39), 2d18h/stopped, RP 172.24.248.163, flags: SJC
Incoming interface: GigabitEthernet2/48, RPF nbr 10.111.116.9, Partial-SC
Outgoing interface list:
Vlan163, Forward/Sparse-Dense, 2d18h/00:02:50, H
(172.24.250.20, 239.9.69.39), 2d18h/00:02:55, flags: JT
Incoming interface: GigabitEthernet2/48, RPF nbr 10.111.116.9, RPF-MFD
Outgoing interface list:
Vlan163, Forward/Sparse-Dense, 2d18h/00:02:50, H
S,G group is showing stopped message- it measn its not sending traffic to downstrem ?
Can any one explain ?
Thanks
Saurabh
11-20-2011 03:48 PM
Hi Saurabh,
Here, the stopped keyword is mentioned only with (*, G) entry representing the shared tree rooted at the RP. It is indicated in the place where the Expire timer would be indicated, and it simply tells you that the shared (*, G) entry is currently not eligible for expiry, obviously because your router or somebody behind it is subscribed to this particular multicast group.
Best regards,
Peter
11-20-2011 04:02 PM
Thanks for your reply,
So if it showing stopped message then its not a problem in network.
yeah, there is server connected behind this router which is a receiver for this group.
its receving lots group from 239.9.69.X but some how it missing 5 groups. we can see from server it sending join messages for those groups.
but not sure why the switch is not passing those 5 groups.
Any advise can you provide.
Thanks
Saurabh
11-20-2011 05:43 PM
Hi Saurabh,
If the server is subscribed to a particular multicast group as a receiver but is not receiving the request traffic, I suggest first using the show ip igmp group command on the last router before this server to see if the router knows via IGMP that the server is subscribed to this particular group. If there is no such group present in the command output then there is something wrong in the IGMP communication between the server and its gateway, and that needs to be inspected further.
If the particular multicast group is visible in the command output then the next course of action should be verifying whether the router knows about the RP for this particular group. This can be performed using the show ip pim rp mapping command.
And furthermore, if the RP is properly recognized then it should be verified using the show ip rpf command whether the incoming interface for the traffic from the RP is properly determined.
Just a few very rough suggestions but I hope this will help you narrow down the problem cause.
Best regards,
Peter
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide