mroute showing multicast route as being pruned, help!

[christopher.wood]

Hello,

I have an issue getting multicast to work for a new device. Trying to replace the old device, but it seems that when the new device is using multicast the route is pruned. Not sure how to fix this. Using PIM sparse-mode.

(*, 239.192.0.25), 05:18:13/stopped, RP 172.31.255.1, flags: SP
  Incoming interface: GigabitEthernet0/1, RPF nbr 172.27.65.3
  Outgoing interface list: Null

(172.27.1.60 (old), 239.192.0.25), 05:18:13/00:02:08, flags: T
  Incoming interface: GigabitEthernet0/0, RPF nbr 0.0.0.0
  Outgoing interface list:
    GigabitEthernet0/1, Forward/Sparse, 05:18:13/00:03:03

(*, 239.192.0.5), 00:01:00/stopped, RP 172.31.255.1, flags: SP
  Incoming interface: GigabitEthernet0/1, RPF nbr 172.27.65.3
  Outgoing interface list: Null

(172.27.1.81 (new), 239.192.0.5), 00:01:00/00:02:07, flags: PT
  Incoming interface: GigabitEthernet0/0, RPF nbr 0.0.0.0
  Outgoing interface list: Null

(*, 239.192.0.3), 03:19:35/stopped, RP 172.31.255.1, flags: SP
  Incoming interface: GigabitEthernet0/1, RPF nbr 172.27.65.3
  Outgoing interface list: Null

(172.27.1.60 (old), 239.192.0.3), 03:19:38/00:02:54, flags: T
  Incoming interface: GigabitEthernet0/0, RPF nbr 0.0.0.0
  Outgoing interface list:
    GigabitEthernet0/1, Forward/Sparse, 03:19:38/00:02:43

(*, 224.0.1.40), 7y34w/00:02:57, RP 0.0.0.0, flags: DPL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list: Null

It almost sounds like I just need to turn the old one off and let the new one work and the old route should age out and the new route can start working from what I've read?

[christopher.wood]

Alright, got the ip igmp join-group command on the interfaces, but seems to have made no difference in the mroute table.

YYM-6#sho 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
 
(*, 239.192.0.1), 01:22:47/00:02:32, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Dialer1, Forward/Dense, 00:02:45/00:00:00
    BVI1, Forward/Dense, 01:20:52/00:00:00
 
(*, 224.0.1.40), 01:23:21/stopped, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    BVI1, Forward/Dense, 01:23:21/00:00:00

[Felix Ng · Accepted solution]

Hi Chris,

I hope you will see this.  The reason why the router was dropping the all the multicast packets was because the server never sends out proper membership report.  There was never a proper association (and to an extension, no mroute built) between the server address and the multicast group.

And the reason why the server didn't do it properly was the application which uses Java had an outdated version (or a mismatched version) of the JMS file installed. 

Felix

[christopher.wood]

Chris R. filled me in on this after I left. I banged my head on my desk for months on this. I asked them to check the server and apps several times. "Not our problem, everything works fine."