Multicast traffic is stopping and only starts on reboot.

[Jeff Horton]

I have a switch stack that consist of a WS-C3850-12S and a WS-C3850-24U running cat3k_caa-universalk9.16.06.03.SPA. We are experiencing a stoppage of multicast video and only restarts when we perform a reload. Here is some mroute statements that show the stoppage:

(192.168.30.11, 239.224.30.20), 4d01h/00:02:47, flags: T
Incoming interface: Vlan30, RPF nbr 0.0.0.0
Outgoing interface list:
Vlan200, Forward/Sparse-Dense, 4d01h/stopped

(*, 239.224.30.16), 4d01h/stopped, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Vlan200, Forward/Sparse-Dense, 4d01h/stopped

(192.168.30.11, 239.224.30.16), 4d01h/00:02:49, flags: T
Incoming interface: Vlan30, RPF nbr 0.0.0.0
Outgoing interface list:
Vlan200, Forward/Sparse-Dense, 4d01h/stopped

(*, 239.224.30.15), 4d01h/stopped, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Vlan200, Forward/Sparse-Dense, 4d01h/stopped

Any suggestion on what to look for would greatly be appreciated...

Just a little bit on the configuration also:

Each port is setup as an access port and each vlan has a SVI of .1 for each vlan/subnet (Bascially the GW).. Those interfaces have ip pim sparse-dense-mode configured on them.

At one point I had ip pim rp-address for our vlan 200 svi. That is no longer there. Could this cause it to just stop?

[Sergey Lisitsin]

Jeff, we would need some  more information to help you. Firstly, what is your network topology. What devices do unicast routing? is multicast traffic confined to the single stack? What is your IGMP status? Can you please show the output of show ip igmp group.

[Jeff Horton]

Here is a short snippet of it:

Group Address Interface Uptime Expires Last Reporter Group Accounted
239.224.50.21 Vlan200 4d00h 00:02:22 192.168.200.94
239.224.50.20 Vlan200 4d00h 00:02:16 192.168.200.94
239.224.50.19 Vlan200 1d11h 00:02:18 192.168.200.94
239.224.50.18 Vlan200 1d11h 00:02:16 192.168.200.94
239.224.50.17 Vlan200 1d11h 00:02:21 192.168.200.94
239.255.255.250 Vlan10 4d01h 00:02:39 169.254.142.203
239.255.255.250 Vlan40 4d01h 00:02:39 169.254.248.83
239.255.255.250 Vlan20 4d01h 00:02:39 192.168.20.91
239.255.255.250 Vlan30 4d01h 00:02:58 169.254.228.217
239.255.255.250 Vlan50 4d01h 00:02:39 192.168.50.90
239.255.255.250 Vlan200 4d01h 00:02:19 192.168.200.202
239.224.20.31 Vlan200 1d00h 00:02:19 192.168.200.96
239.224.20.31 Vlan20 4d01h 00:02:43 192.168.20.92
239.224.20.26 Vlan200 1d00h 00:02:24 192.168.200.96
239.224.20.26 Vlan20 4d01h 00:02:39 192.168.20.92
239.224.20.25 Vlan200 1d00h 00:02:19 192.168.200.96
239.224.20.25 Vlan20 4d01h 00:02:41 192.168.20.92
239.224.20.22 Vlan200 1d00h 00:02:17 192.168.200.96
239.224.20.22 Vlan20 4d01h 00:02:45 192.168.20.92
--More--  IGMP Connected Group Membership
Group Address Interface Uptime Expires Last Reporter Group Accounted
239.224.20.21 Vlan200 1d00h 00:02:24 192.168.200.96
239.224.20.21 Vlan20 4d01h 00:02:42 192.168.20.92
239.224.20.20 Vlan200 1d00h 00:02:19 192.168.200.96
239.224.20.20 Vlan20 4d01h 00:02:48 192.168.20.92
239.224.20.17 Vlan200 1d00h 00:02:25 192.168.200.96
239.224.20.17 Vlan20 4d01h 00:02:47 192.168.20.92
239.224.20.16 Vlan200 1d00h 00:02:16 192.168.200.96
239.224.20.16 Vlan20 4d01h 00:02:39 192.168.20.92
239.224.20.10 Vlan200 1d00h 00:02:17 192.168.200.96
239.224.20.10 Vlan20 4d01h 00:02:39 192.168.20.91
239.224.20.4 Vlan200 1d00h 00:02:21 192.168.200.96
239.224.20.4 Vlan20 4d01h 00:02:41 192.168.20.92
239.224.20.5 Vlan200 1d00h 00:02:21 192.168.200.96
239.224.20.5 Vlan20 4d01h 00:02:41 192.168.20.91
239.224.20.32 Vlan200 1d00h 00:02:17 192.168.200.96
239.224.20.32 Vlan20 4d01h 00:02:43 192.168.20.91
239.200.200.200 Vlan200 4d01h 00:02:21 192.168.200.101
225.10.10.10 Vlan200 4d01h 00:02:17 10.10.125.5
225.86.67.83 Vlan30 4d01h 00:02:59 192.168.0.81
239.192.8.88 Vlan40 4d01h 00:02:39 192.168.40.31
239.192.8.88 Vlan20 4d01h 00:02:40 192.168.20.30

[Jeff Horton]

Also here is the igmp on our vlan 10.. Same on all our vlans, which is only 7 of them...

Vlan 10:
--------
IGMP snooping : Enabled
IGMPv2 immediate leave : Disabled
Explicit host tracking : Enabled
Multicast router learning mode : pim-dvmrp
CGMP interoperability mode : IGMP_ONLY
Robustness variable : 2
Last member query count : 2
Last member query interval : 1000

[Sergey Lisitsin]

Also Jeff,

Do you know if the actual mutlicast stream is still active at the time when this happens? From the show ip mroute output, the state entries look ok.

[Jeff Horton]

Yes.. There are multiple servers that provide the multicast streams and all the multicast streams to the clients stop at the same time...

[Sergey Lisitsin]

OK, in that case, can you please draw a quick diagram of your network, including the servers and receivers locations.

[rais]

Apparently there is no RP in the network.  You need an RP for ASM.

HTH.

[Sergey Lisitsin]

rais,

I don't think RP would necessarily be an issue here, as Jeff is using sparse-dense mode.

[Jeff Horton]

Sure.. Give me a bit and I will have one.

[Jeff Horton]

[Jeff Horton]

In this drawing all links from 2960 switches to 3850 switchstack are 1G fiber links.. Each View Station view local multicast except for the vlan 200 stations.. They view all multicast. Every vlan GW is located on the 3850 stack. The 2960 links to the 3850 stack are configured as access ports.. 

Anymore info needed let me know.

[Sergey Lisitsin]

OK, so as I suspected, all your multicast L3 is happening on a single device. There is no reason why it wouldn't be able to forward multicast traffic. At least not in the control plane. I would search for bugs. Also, I would try to ping the multicast groups from the 3850 stack and see what happens when multicast streams break.

[Jeff Horton]

Have you ever seen any issues with the CPP policy-map that polices the multicast rates?

[Sergey Lisitsin]

Jeff, can you try disabling and re-enabling the IGMP snooping on the affected VLANs when this happens.