05-27-2020 04:39 PM
I have a Catalyst 2960-X 48FPS-L with an uplink in port 52 using a tranciever module which is connected using an ethernet cable to a Catalyst 2960G on port 4. The link has been working for a few weeks, however today it went down. Both ports show that they are down and down. Investigation shows that the 2960-X sees the tranciever module but it shows its not connected.
I am unable to get the port to come up even if i remove the tranciever module and reinsert. If the switch is rebooted it comes back up and remains line this for a few weeks and then the same occurs again.
This has happened in at least two of these switches so far. The 2960X is runningthe below software release.
Switch#sh ver
Cisco IOS Software, C2960X Software (C2960X-UNIVERSALK9-M), Version 15.2(6)E2, R ELEASE SOFTWARE (fc4)
What can be the cause of this issue?
05-27-2020 05:37 PM
@jeremyculver wrote:
If the switch is rebooted it comes back up and remains line this for a few weeks and then the same occurs again.
Sounds like a bug.
Upgrade the firmware to a more recent version.
05-27-2020 09:13 PM
05-28-2020 01:40 AM
@mohammedshahidali88 The module is a genuine CISCO module. I have tried swapping out the module and that has no effect. The GLC-T module resides in the 2960-X, and i have tried connecting to different copper ports on 2960G with no difference. I have upgraded the firmware to 15.2(7)E2 to see whether this fixes the issue.
05-28-2020 01:36 AM
@Leo Laohoo Thanks for your response. I have upgraded firmware to 15.2(7)E2. Interfaces are both up. So now i wait to see whether it will remain up longer than two weeks (interfaces always goes down within two weeks).
05-27-2020 11:35 PM
Hello,
the bug below might apply...
2960x remain down randomly with GLC-TE in uplink ports
CSCvk44218
Description
Symptom:
Uplink ports with GLC-TE on 2960X, running IOS 15.2(2)E8, goes down after sometime and it is not able to bring up again only after the reload the interface came up, but the issue is going to happen again. "show idprom" gives the following error.
hulc_sfp_iic_intf_read_eeprom sfp _index 0 yeti_iic_read_retry fai
Conditions:
This issue could occur when I2C bus gets hung and switch not able to collect link status from GLC-T and other Fiber SFP's.
Workaround:
Reload the switch to recover from this condition temporately.
Further Problem Description:
none
05-28-2020 01:35 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide