Exterity IPTV multicast

[ahmed.gadi]

Dear All,

             We have Exterity IPTV solution implemented in our network.

We have cisco 4507R with 3560 edge switches. Now we are facing lot of multicast/broadcast flooding in our network due to which our voice and data vlans are affected.

I need suggestion to stop multicast/broadcast flooding.

(please check attached wireshark screenshot)

On core switch the config looks like

interface Vlan30
description *** IPTV ***
ip address 101.101.2.X 255.255.0.0
ip pim sparse-dense-mode
ip igmp query-interval 60

++++++++++++++++++++++++++++++

sh ip igmp groups
IGMP Connected Group Membership
Group Address Interface Uptime Expires Last Reporter Group Accounted
239.192.1.77 Vlan30 33w6d 00:01:06 101.101.2.121
239.1.1.1 Vlan30 1w1d 00:00:59 101.101.2.53
239.192.137.79 Vlan30 33w6d 00:01:11 101.101.2.79
239.255.255.255 Vlan30 33w6d 00:01:06 101.101.2.232
239.192.136.78 Vlan30 5w6d 00:01:08 101.101.2.218
239.192.3.6 Vlan30 33w6d 00:01:12 101.101.2.113
239.192.3.7 Vlan30 9w6d 00:01:09 101.101.2.7
239.192.3.77 Vlan30 33w6d 00:01:13 101.101.2.77
239.192.2.8 Vlan30 2w5d 00:01:14 101.101.2.8
239.192.2.9 Vlan30 27w5d 00:01:07 101.101.2.62

.

.

.

+++++++++++++++++++++++++++++++++++++++++++

sh ip igmp snooping vlan 30 detail
Global IGMP Snooping configuration:
-------------------------------------------
IGMP snooping : Enabled
IGMPv3 snooping : Enabled
Report suppression : Enabled
TCN solicit query : Disabled
TCN flood query count : 2
Last Member Query Interval : 1000

Vlan 30:
--------
IGMP snooping : Enabled
CAPWAP enabled : Disabled
IGMPv2 immediate leave : Disabled
Explicit host tracking : Enabled
Multicast router learning mode : pim-dvmrp
CGMP interoperability mode : IGMP_ONLY
Last Member Query Interval : 1000

Topology change : No

++++++++++++++++++++++++++++++

sh ip igmp interface vlan 30
Vlan30 is up, line protocol is up
Internet address is 101.101.2.X/16
IGMP is enabled on interface
Current IGMP host version is 2
Current IGMP router version is 2
IGMP query interval is 25 seconds
IGMP configured query interval is 60 seconds
IGMP querier timeout is 50 seconds
IGMP configured querier timeout is 120 seconds
IGMP max query response time is 10 seconds
Last member query count is 2
Last member query response interval is 1000 ms
Inbound IGMP access group is not set
IGMP activity: 2459 joins, 2406 leaves
Multicast routing is enabled on interface
Multicast TTL threshold is 0
Multicast designated router (DR) is 101.101.2.X (this system)
IGMP querying router is 101.101.2.X (this system)
Multicast groups joined by this system (number of users): 224.0.1.40(1)

+++++++++++++++++++++++++++++++

sh ip igmp snooping querier detail
Vlan IP Address IGMP Version Port
-------------------------------------------------------------
30 101.101.2.X v2 Router

Global IGMP switch querier status
--------------------------------------------------------
admin state : Disabled
admin version : 2
source IP address : 0.0.0.0
query-interval (sec) : 60
max-response-time (sec) : 10
querier-timeout (sec) : 120
tcn query count : 2
tcn query interval (sec) : 10

++++++++++++++++++++++++++++++++++++++

On edge switches

sh ip igmp snooping
Global IGMP Snooping configuration:
-------------------------------------------
IGMP snooping : Enabled
IGMPv3 snooping (minimal) : Enabled
Report suppression : Enabled
TCN solicit query : Disabled
TCN flood query count : 2
Robustness variable : 2
Last member query count : 2
Last member query interval : 1000

++++++++++++++++++++++++++++++++++++++

sh ip igmp snooping vlan 30 detail
Global IGMP Snooping configuration:
-------------------------------------------
IGMP snooping : Enabled
IGMPv3 snooping (minimal) : Enabled
Report suppression : Enabled
TCN solicit query : Disabled
TCN flood query count : 2
Robustness variable : 2
Last member query count : 2
Last member query interval : 1000

Vlan 30:
--------
IGMP snooping : Enabled
IGMPv2 immediate leave : Disabled
Multicast router learning mode : pim-dvmrp
CGMP interoperability mode : IGMP_ONLY
Robustness variable : 2
Last member query count : 2
Last member query interval : 1000
Topology change : No

+++++++++++++++++++++++++++++++++++++

Look forward for positive response.

Thanks & Regards

Ahmed...

[chrihussey]

On the surface it looks as if something is flooding VLAN 30 trying to get to a destination host that does not exist. Exterity is ARPing for 101.101.2.2##, not sure if that is the full IP or not. Think you need to identify why it is trying to get to that host. Might just be a configuration issue in the Exterity.

Hope this helps

[ahmed.gadi]

Heloo,

101.101.2.20 is headend and 101.101.2.XXX are receivers (hardware).

Do you mean receivers are trying to look (ask) for 101.101.2.20 with broadcast packets?

Thanks & Regards

Ahmed...

[chrihussey]

It's tough to say what's going on, but if it were multicast there would be IGMP joins and the source would be transmitting. ARP really wouldn't come into play. Yet the trace you provided looks like constant ARP requests. So are the hosts trying to get the streams using unicast on the same subnet? If so, are the ARP requests to a valid IP, and are the ARP requests getting responses?

Again, if it were multicast flooding I'd assume there would be multicast packets in your trace.

So if flooding is the issue, you need to determine if it is broadcast problems, multicast, or possibly spanning tree issues. Spanning a port and doing a more thorough trace may prove helpful.

[ahmed.gadi]

Please find the pcap file for your reference.

[paul driver]

Hello

sh ip igmp groups
IGMP Connected Group Membership
Group Address Interface Uptime Expires Last Reporter Group Accounted
239.192.1.77 Vlan30 33w6d 00:01:06 101.101.2.121
239.1.1.1 Vlan30 1w1d 00:00:59 101.101.2.53

By the looks of it the other MC groups have been active for quite a while aprt from 239.1.1.1

You could try filtering this group out and see if anything stablilises.

access-list 1 deny host 239.1.1.1
access-list 1 permit any

int vlan 30

ip igmp access-group 1
end

debug ip igmp 239.1.1.1

[ahmed.gadi]

Hi an update on my case.

Actually, 20% of IPTV receivers were configured to send logs to syslog server 101.101.2.20 with debugging level.

101.101.2.20 server was brought down a few weeks back, so all IPTV receivers were sending broadcast and chocking up the bandwidth, so after enabling local logging, network became stable.

Thank you for your input.