Facing Layer 1 Issues in 6500 Core switch & 2960 Access Switch Experts Need advice

syed baseeruddin · ‎08-04-2018

Hi

there is 6500 Core switch and 2960 Access Switch the connection is between through Fiber

For IPTV Systems we are Facing Issues.

Many days Back there is issue in layer 1 connectivity but after More than 10 days there is Facing Channels distortion so i change the SFP in 2960 the problem is Solved

Then After more than 10 day again we are facing again channels Distortion i change the SFP for 6500 switch so again more than i am Facing same Channel distortion

The Following Show log of 6500 switch

Syslog logging: enabled (0 messages dropped, 8 messages rate-limited, 615 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.

No Inactive Message Discriminator.

Console logging: level debugging, 628798 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 236 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 626982 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
Persistent logging: disabled

No active filter modules.

ESM: 0 messages dropped

Trap logging: level informational, 626945 message lines logged

Log Buffer (8192 bytes):
(25600)
626899: Aug 2 11:31:08.011 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626900: Aug 2 11:31:08.271 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626901: Aug 2 11:31:19.087 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626902: Aug 2 11:31:22.247 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626903: Aug 2 11:31:23.147 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626904: Aug 2 11:31:30.176 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626905: Aug 2 11:31:31.617 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626906: Aug 2 11:52:33.402 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626907: Aug 2 11:52:33.870 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626908: Aug 2 11:52:38.024 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626909: Aug 2 11:52:38.968 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626910: Aug 2 11:58:42.688 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626911: Aug 2 11:58:49.395 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626912: Aug 2 11:58:50.567 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626913: Aug 2 11:59:04.531 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626914: Aug 2 11:59:04.543 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626915: Aug 2 11:59:26.547 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626916: Aug 2 12:13:30.035 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626917: Aug 2 12:14:02.999 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626918: Aug 2 12:15:53.676 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626919: Aug 2 12:18:39.494 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626920: Aug 2 12:18:39.898 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626921: Aug 2 12:19:01.307 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626922: Aug 2 12:45:34.841 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626923: Aug 2 12:45:35.233 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626924: Aug 2 12:56:40.827 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626925: Aug 2 12:56:41.287 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626926: Aug 2 12:56:45.687 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626927: Aug 2 12:56:46.239 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626928: Aug 2 13:06:45.714 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626929: Aug 2 13:06:46.106 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626930: Aug 2 13:06:51.863 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626931: Aug 2 13:07:09.598 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626932: Aug 2 13:07:09.983 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626933: Aug 2 13:07:37.665 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626934: Aug 2 13:08:35.163 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626935: Aug 2 13:08:35.647 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626936: Aug 2 14:05:49.351 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626937: Aug 2 14:05:49.767 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626938: Aug 2 14:06:28.023 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626939: Aug 2 14:08:14.571 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626940: Aug 2 14:08:15.111 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626941: Aug 2 14:08:34.987 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
626942: Aug 2 14:08:35.363 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent

The 2960 switch show log

Syslog logging: enabled (0 messages dropped, 1 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.

No Inactive Message Discriminator.

Console logging: level debugging, 155 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 155 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
File logging: disabled
Persistent logging: disabled

No active filter modules.

Trap logging: level informational, 157 message lines logged
Logging Source-Interface: VRF Name:

Log Buffer (4096 bytes):
net1/0/51, changed state to up
000119: .Jul 17 06:12:42.884: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
000120: .Jul 17 06:12:42.888: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2222, changed state to up
000121: .Jul 17 06:12:43.527: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/51, changed state to up
000122: Jul 17 06:30:08.317: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
000123: Jul 17 06:30:08.317: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2222, changed state to down
000124: .Jul 17 06:30:09.261: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/51, changed state to down
000125: .Jul 17 06:30:10.268: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/51, changed state to down
000126: .Jul 17 06:30:51.139: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/49, changed state to up
000127: .Jul 17 06:30:53.516: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2222, changed state to up
000128: .Jul 17 06:30:54.005: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/49, changed state to up
000129: .Jul 17 06:30:54.558: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
000130: Jul 17 07:45:04.676: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
000131: Jul 17 07:45:04.680: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2222, changed state to down
000132: .Jul 17 07:45:05.620: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/49, changed state to down
000133: .Jul 17 07:45:06.634: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/49, changed state to down
000134: .Jul 17 07:47:45.216: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/49, changed state to up
000135: .Jul 17 07:47:46.450: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/49, changed state to up
000136: .Jul 17 07:47:47.453: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/49, changed state to down
000137: .Jul 17 07:47:49.131: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2222, changed state to up
000138: .Jul 17 07:47:49.142: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
000139: .Jul 17 07:47:49.781: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/49, changed state to up
000140: Jul 17 10:10:42.956: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
000141: Jul 17 10:10:42.956: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2222, changed state to down
000142: .Jul 17 10:10:43.899: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/49, changed state to down
000143: .Jul 17 10:10:44.906: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/49, changed state to down
000144: .Jul 17 10:22:19.400: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/52, changed state to up
000145: .Jul 17 10:22:21.047: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
000146: .Jul 17 10:22:21.050: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2222, changed state to up
000147: .Jul 17 10:22:21.410: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/52, changed state to up
000148: Jul 17 11:01:46.113: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
000149: Jul 17 11:01:46.116: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2222, changed state to down
000150: .Jul 17 11:01:47.060: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/52, changed state to down
000151: .Jul 17 11:01:48.070: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/52, changed state to down
000152: .Jul 17 11:02:45.437: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/52, changed state to up
000153: .Jul 17 11:02:46.880: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
000154: .Jul 17 11:02:47.450: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/52, changed state to up
000155: .Jul 17 11:02:47.838: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2222, changed state to up

Experts Please advice

Leo Laohoo · ‎08-04-2018

Post the complete output to the following 2960 commands:
1. sh version;
2. sh interface Gi1/0/49;
3. sh interface Gi 1/0/52

syed baseeruddin · ‎08-04-2018

Thanks Leo Laohoo

The output Core switch

GigabitEthernet7/3 is up, line protocol is up (connected)
Hardware is C6k 1000Mb 802.3, address is f40f.1b99.cec6 (bia f40f.1b99.cec6)
Description: ****LINK TO F28-IPTV-Switch*****
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 106/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, media type is SX
input flow-control is off, output flow-control is off
Clock mode is auto
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:20, output 00:00:28, output hang never
Last clearing of "show interface" counters never
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 419275000 bits/sec, 38375 packets/sec
5 minute output rate 6000 bits/sec, 10 packets/sec
     1302859775840 packets input, 1779508502451677 bytes, 0 no buffer
     Received 1302703384985 broadcasts (1328294237 multicasts)
     4860026 runts, 0 giants, 0 throttles
     298391863 input errors, 143892865 CRC, 143889578 frame, 0 overrun, 0 ignored
     0 watchdog, 0 multicast, 0 pause input
     0 input packets with dribble condition detected
     152748801 packets output, 15014156359 bytes, 0 underruns
     0 output errors, 0 collisions, 4 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 PAUSE output
     0 output buffer failures, 0 output buffers swapped out

===========================================================

sh ver

Cisco IOS Software, s72033_rp Software (s72033_rp-IPBASE-M), Version 12.2(33)SXI4a, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Fri 16-Jul-10 19:51 by prod_rel_team

ROM: System Bootstrap, Version 12.2(17r)SX7, RELEASE SOFTWARE (fc1)

RUHHR-G-CORE-SW uptime is 1 year, 5 weeks, 3 days, 17 hours, 40 minutes
Uptime for this control processor is 1 year, 5 weeks, 3 days, 17 hours, 19 minutes
Time since RUHHR-G-CORE-SW switched to active is 1 year, 5 weeks, 3 days, 17 hours, 17 minutes
System returned to ROM by power cycle at 02:06:25 UTC Sat Jan 22 2011 (SP by power on)
System restarted at 19:34:32 Riyadh Mon Jun 26 2017
System image file is "sup-bootdisk:s72033-ipbase-mz.122-33.SXI4a.bin"
Last reload reason: Reload Command

cisco WS-C6509-E (R7000) processor (revision 1.5) with 983008K/65536K bytes of memory.
Processor board ID SMC1452001C
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
Last reset from s/w reset
28 Virtual Ethernet interfaces
167 Gigabit Ethernet interfaces
2 Ten Gigabit Ethernet interfaces
1917K bytes of non-volatile configuration memory.
8192K bytes of packet buffer memory.

65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102

=================================================

sh log

Syslog logging: enabled (0 messages dropped, 8 messages rate-limited, 615 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.

No Inactive Message Discriminator.

    Console logging: level debugging, 631210 messages logged, xml disabled,
                     filtering disabled
    Monitor logging: level debugging, 236 messages logged, xml disabled,
                     filtering disabled
    Buffer logging: level debugging, 629394 messages logged, xml disabled,
                    filtering disabled
    Exception Logging: size (4096 bytes)
    Count and timestamp logging messages: disabled
    Persistent logging: disabled

No active filter modules.

ESM: 0 messages dropped

Trap logging: level informational, 629357 message lines logged

Log Buffer (8192 bytes):
(25600)
629311: Aug 4 12:13:26.319 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629312: Aug 4 12:20:49.639 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629313: Aug 4 12:20:49.963 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629314: Aug 4 12:22:58.431 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629315: Aug 4 12:22:58.835 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629316: Aug 4 12:27:48.319 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629317: Aug 4 12:27:48.795 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629318: Aug 4 12:30:09.787 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629319: Aug 4 12:30:10.219 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629320: Aug 4 12:41:21.892 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629321: Aug 4 12:41:22.352 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629322: Aug 4 12:41:25.248 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629323: Aug 4 12:41:25.680 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629324: Aug 4 12:41:26.985 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629325: Aug 4 12:41:27.601 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629326: Aug 4 12:42:29.691 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629327: Aug 4 12:42:30.263 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629328: Aug 4 12:42:36.473 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629329: Aug 4 12:42:37.150 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629330: Aug 4 12:42:38.174 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629331: Aug 4 12:42:38.590 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629332: Aug 4 12:42:40.039 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629333: Aug 4 12:42:40.443 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629334: Aug 4 12:43:10.619 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629335: Aug 4 12:43:11.023 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629336: Aug 4 12:45:56.944 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629337: Aug 4 12:45:57.297 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629338: Aug 4 12:49:18.763 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629339: Aug 4 12:49:19.359 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629340: Aug 4 12:49:29.007 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629341: Aug 4 12:49:29.407 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629342: Aug 4 12:49:55.063 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629343: Aug 4 12:50:13.955 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629344: Aug 4 12:50:14.367 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629345: Aug 4 12:54:10.011 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629346: Aug 4 12:54:10.515 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629347: Aug 4 12:54:23.011 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629348: Aug 4 12:54:23.475 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629349: Aug 4 12:54:30.887 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629350: Aug 4 12:54:31.291 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629351: Aug 4 12:54:59.671 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629352: Aug 4 12:55:00.127 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629353: Aug 4 12:55:05.007 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600)
629354: Aug 4 12:55:05.411 Riyadh: %MCAST-SP-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the permanent threshold (25600

The out of Access Switch

GigabitEthernet1/0/52 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 204c.9e41.ed34 (bia 204c.9e41.ed34)
Description: **Connected-TO-Core-Switch**
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
     reliability 255/255, txload 106/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Full-duplex, 1000Mb/s, link type is auto, media type is 1000BaseSX SFP
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 1/75/0/0 (size/max/drops/flushes); Total output drops: 1348
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 8000 bits/sec, 12 packets/sec
5 minute output rate 418363000 bits/sec, 38282 packets/sec
     13663573 packets input, 1092577859 bytes, 0 no buffer
     Received 13333495 broadcasts (4428452 multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 4428452 multicast, 0 pause input
     0 input packets with dribble condition detected
     59443601551 packets output, 81195644673201 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     0 unknown protocol drops
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 pause output
     0 output buffer failures, 0 output buffers swapped out

===============================================================

sh ver

Cisco IOS Software, C2960X Software (C2960X-UNIVERSALK9-M), Version 15.0(2)EX5, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Fri 21-Feb-14 05:54 by prod_rel_team

ROM: Bootstrap program is C2960X boot loader
BOOTLDR: C2960X Boot Loader (C2960X-HBOOT-M) Version 15.2(2r)E1, RELEASE SOFTWARE (fc1)

F28-IPTV-Switch uptime is 2 weeks, 4 days, 16 hours, 52 minutes
System returned to ROM by power-on
System restarted at 17:00:58 UTC Mon Jul 16 2018
System image file is "flash:/c2960x-universalk9-mz.150-2.EX5/c2960x-universalk9-mz.150-2.EX5.bin"

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.

cisco WS-C2960X-48LPS-L (APM86XXX) processor (revision G0) with 524288K bytes of memory.
Processor board ID FCW1901A2GF
Last reset from power-on
2 Virtual Ethernet interfaces
1 FastEthernet interface
52 Gigabit Ethernet interfaces
The password-recovery mechanism is disabled.

512K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address       : 20:4C:9E:41:ED:00
Motherboard assembly number     : 73-15970-02
Power supply part number        : 341-0528-01
Motherboard serial number       : FOC19011LTS
Power supply serial number      : LIT18490PDL
Model revision number           : G0
Motherboard revision number     : C0
Model number                    : WS-C2960X-48LPS-L
Daughterboard assembly number   : 73-14200-03
Daughterboard serial number     : FOC18526NTS
System serial number            : FCW1901A2GF
Top Assembly Part Number        : 800-41467-01
Top Assembly Revision Number    : C0
Version ID                      : V02
CLEI Code Number                : CMMLP00ARB
Daughterboard revision number   : A0
Hardware Board Revision Number : 0x12

Switch Ports Model              SW Version            SW Image
------ ----- -----              ----------            ----------
*    1 52    WS-C2960X-48LPS-L 15.0(2)EX5            C2960X-UNIVERSALK9-M

Configuration register is 0xF

==============================================================

sh log

Syslog logging: enabled (0 messages dropped, 1 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.

No Inactive Message Discriminator.

    Console logging: level debugging, 171 messages logged, xml disabled,
                     filtering disabled
    Monitor logging: level debugging, 0 messages logged, xml disabled,
                     filtering disabled
    Buffer logging: level debugging, 171 messages logged, xml disabled,
                    filtering disabled
    Exception Logging: size (4096 bytes)
    Count and timestamp logging messages: disabled
    File logging: disabled
    Persistent logging: disabled

No active filter modules.

Trap logging: level informational, 173 message lines logged
Logging Source-Interface: VRF Name:

Log Buffer (4096 bytes):
Interface GigabitEthernet1/0/49, changed state to up
000135: .Jul 17 07:47:46.450: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/49, changed state to up
000136: .Jul 17 07:47:47.453: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/49, changed state to down
000137: .Jul 17 07:47:49.131: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2222, changed state to up
000138: .Jul 17 07:47:49.142: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
000139: .Jul 17 07:47:49.781: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/49, changed state to up
000140: Jul 17 10:10:42.956: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
000141: Jul 17 10:10:42.956: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2222, changed state to down
000142: .Jul 17 10:10:43.899: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/49, changed state to down
000143: .Jul 17 10:10:44.906: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/49, changed state to down
000144: .Jul 17 10:22:19.400: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/52, changed state to up
000145: .Jul 17 10:22:21.047: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
000146: .Jul 17 10:22:21.050: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2222, changed state to up
000147: .Jul 17 10:22:21.410: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/52, changed state to up
000148: Jul 17 11:01:46.113: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
000149: Jul 17 11:01:46.116: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2222, changed state to down
000150: .Jul 17 11:01:47.060: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/52, changed state to down
000151: .Jul 17 11:01:48.070: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/52, changed state to down
000152: .Jul 17 11:02:45.437: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/52, changed state to up
000153: .Jul 17 11:02:46.880: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
000154: .Jul 17 11:02:47.450: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/52, changed state to up
000155: .Jul 17 11:02:47.838: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2222, changed state to up
000156: Aug 2 11:36:09.340: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
000157: Aug 2 11:36:09.340: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2222, changed state to down
000158: .Aug 2 11:36:10.284: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/52, changed state to down
000159: .Aug 2 11:36:11.291: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/52, changed state to down
000160: .Aug 2 11:38:15.206: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/52, changed state to up
000161: .Aug 2 11:38:16.363: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
000162: .Aug 2 11:38:17.212: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/52, changed state to up
000163: .Aug 2 11:38:17.604: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2222, changed state to up
000164: Aug 2 12:18:25.695: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
000165: Aug 2 12:18:25.695: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2222, changed state to down
000166: .Aug 2 12:18:26.636: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/52, changed state to down
000167: .Aug 2 12:18:27.646: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/52, changed state to down
000168: .Aug 2 12:18:54.522: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/52, changed state to up
000169: .Aug 2 12:18:56.000: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
000170: .Aug 2 12:18:56.007: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2222, changed state to up
000171: .Aug 2 12:18:56.532: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/52, changed state to up

Leo Laohoo · ‎08-04-2018

@syed baseeruddin wrote:

298391863 input errors, 143892865 CRC, 143889578 frame, 0 overrun, 0 ignored

The reason why you don't see interface flapping in the core switch is because, by default, logging interface-level port changes are not enabled.

This is telling me the SFP in the core switch could be faulty.

syed baseeruddin · ‎08-04-2018

Thanks Leo Laohoo,

On This Thursday I change SFP of Core switch after one day I Facing Same Issue

Need your Advice

syed baseeruddin · ‎08-04-2018

Thanks Leo Laohoo

On This Thursday I change SFP of Core switch after one day I Facing Same Issue

Need your Advice

Leo Laohoo · ‎08-04-2018

Check the patch cable.

mvsheik123 · ‎08-04-2018

Hi,

I don't have experience in multicasting.. but your issue may not be L1 hardware related. Here is my take..

1. From 'Show int' output, the interface counters on both ends (core & access) were never cleared- that accumulates errors when your interface down/up or you replace SFPs.

2. When you bring down interface for replacing sfp or t-shoot - it appears that some multicast related queue (remember I do not have m/c exp :)) getting cleared and start build up to the point your issue resurfacing.

When was the issue started and any change made. Guess 6500s are no longer supported but see if you can find any bugs related to your code and try upgrade. Also check if this below link helps..

https://puck.nether.net/pipermail/cisco-nsp/2014-January/094736.html

hth

MS

pieterh · ‎08-06-2018

found this in a post on GT.net

>>>>>
You can do: clear ip igmp snooping statistics

...to get back on an even keel. However, for happy-fun-joy, these are
replicated in a dual-sup setup, and you cannot clear them on the standby
sup, so eventually you'll start getting -SPSTBY- versions of the message
that never stop. Standby sup reload is the only solution :o(
<<<<<

syed baseeruddin · ‎08-06-2018

Hi

Yesterday I Change the patch cord and check the Core switch interface .

Now the layer 1 Connectivity is stable

output of Core switch interface as shown below

GigabitEthernet7/3 is up, line protocol is up (connected)
Hardware is C6k 1000Mb 802.3, address is f40f.1b99.cec6 (bia f40f.1b99.cec6)
Description: ****LINK TO F28-IPTV-Switch*****
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 106/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, media type is SX
input flow-control is off, output flow-control is off
Clock mode is auto
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:22, output 00:00:24, output hang never
Last clearing of "show interface" counters 00:32:34
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 419130000 bits/sec, 38360 packets/sec
5 minute output rate 6000 bits/sec, 9 packets/sec
     75091281 packets input, 102569299842 bytes, 0 no buffer
     Received 75090703 broadcasts (75090703 multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 0 multicast, 0 pause input
     0 input packets with dribble condition detected
     19250 packets output, 1557821 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 PAUSE output
     0 output buffer failures, 0 output buffers swapped out

Leo Laohoo · ‎08-06-2018

Give it a week. The line that says "input errors" should remain "0".