c9200-48p i2c i2c-5 SCL is stuck low, exit recovery messages

[Shawn Kingston]

1 56 C9200-48P 17.09.02 CAT9K_LITE_IOSXE BUNDLE
2 56 C9200-48P 17.09.02 CAT9K_LITE_IOSXE BUNDLE
3 56 C9200-48P 17.09.02 CAT9K_LITE_IOSXE BUNDLE
4 56 C9200-48P 17.09.02 CAT9K_LITE_IOSXE BUNDLE

Stack of 4, error messages flooding with: 

%IOSXE-3-PLATFORM: Switch 3 R0/0: kernel: i2c i2c-5: SCL is stuck low, exit recovery

Any Ideas?

[Flavio Miranda]

Hi

 Sounds like a Bug.  Which version?

https://bst.cisco.com/bugsearch/bug/CSCvp59825

Symptom: Cat9200 switch continuously reports the below error log.

%IOSXE-3-PLATFORM: Switch 1 R0/0: kernel: i2c i2c-6: SCL is stuck low, exit recovery

%IOSXE-3-PLATFORM: Switch 1 R0/0: kernel: i2c i2c-6: SCL is stuck low, exit recovery

Conditions: -- Error seen once uplink module and SFPs on it are detected. -- Error logs seen only if the uplink ports are admin down and SFP is inserted. -- Error logs also seen when try to run "show idprom int <>" or "show int <> trans details". -- Issue so far seen with C9200-NM-4X and GLC-LH-SMD SFPs.

Workaround: Issue not seen if ports are not admin down whenever there is SFP inserted.

[Shawn Kingston]

Cupertino Version 17.9.1r

I have (2) SFP modules, both are active. I do have trunk ports with nothing inserted that are admin down.

[Flavio Miranda]

 This version Cupertino Version 17.9.1r does not show on the fixed list. 

 If you unshut the port does the logs stop?

"Issue not seen if ports are not admin down whenever there is SFP inserted. "

[Shawn Kingston]

No change. Opening case with Cisco, will advise. Thanks!

[mmohammed]

This error message indicates that the SCL line on the I2C bus is stuck low, which is causing the switch to enter a recovery mode. Here are a few possible solutions to try:

1. Check the physical connection: Ensure that all cables and connectors are properly seated and not loose. Check if any cables are damaged or frayed.

2. Check for firmware updates: Check if there are any firmware updates available for the switch and upgrade if necessary.

3. Check for conflicting devices: Check if there are any other devices on the same I2C bus that might be conflicting with the switch. Disconnect any such devices and check if the error goes away.

4. Replace the switch: If none of the above solutions work, it is possible that the switch itself is faulty and needs to be replaced. Contact the vendor or manufacturer for support and replacement options.

[heleros]

Replace the Uplink Module, not necassary the whole switch.