Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
When a Catalyst 9300 multigigabit series switch (UN/UXW/etc) is connected to a 2960X via copper ethernet/RJ45, traffic is degraded and the frames received causes errors on the interface to increment. This can be seen via "show interface N controllers": Switch#:show interface Five1/0/48 controller FiveGigabitEthernet1/0/48 is up, line protocol is up MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec, reliability 189/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Full-duplex, 1000Mb/s, media type is 100/1000/2.5G/5GBaseTX input flow-control is on, output flow-control is unsupported ARP type: ARPA, ARP Timeout 04:00:00 34107 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 2048 to 4095 byte frames 0 2048 to 4095 byte frames 0 4096 to 8191 byte frames 0 4096 to 8191 byte frames 0 8192 to 16383 byte frames 0 8192 to 16383 byte frames 0 16384 to 32767 byte frame 0 16384 to 32767 byte frame 0 > 32768 byte frames 0 > 32768 byte frames 0 Late collision frames 34107 SymbolErr frames <<<<<<<<<<<<<<<<
The switch must be a Cisco Catalyst 9300 switch using multigigabit ports (front panel copper/RJ45 ports that are capable of negotiating at speeds greater than 1Gbps.) C9300-48UN, C9300-24UN, UXW. This issue can be seeing when connecting the mgig C9300 with other devices too (APs, Servers, firewalls, non-mgig equipment). This is not specific to C2960. HW Version 04/05 are impacted. This can be seen in "show inventory": Switch-9300#sh inv NAME: "c93xx Stack", DESCR: "c93xx Stack" PID: C9300-48UN , VID: V04 , SN: [omitted] Switch-9300#sh inv NAME: "c93xx Stack", DESCR: "c93xx Stack" PID: C9300-48UN , VID: V05 , SN: [omitted]
--Can hardcode the interfaces to 100/Full ("speed 100" and "duplex full"). --Use a different device on the other side. --Use fiber
This is caused by an error in the way the switch interprets and processes the preamble of the frame when it is received. It has been found that the fix for this defect may not address all cases of failure. Please open a TAC SR for assistance in getting this fixed through a workaround as an EEM script.