Header Only - DO NOT REMOVE - Extreme Networks

HAL ERROR? Slot-1: Error reading from XEN card eeprom


Does any one know what causes the following errors?
06/18/2015 14:27:51.78 Slot-2: Error reading from XEN card eeprom (1, 83)
06/18/2015 14:12:22.98 Slot-1: Error reading from XEN card eeprom (1, 83)
The errors was reported on a stacking switch running XOS 12.6.2.10-patch1-15. The stack consists if the following.
Slot-1 X650-24t (10G8X)
Slot-2 X650-24t (10G8X)
Slot-3 X450a-48t
Slot-4 X450a-48t

I haven't been able to find any information on this error, please HELP!

4 replies

Userlevel 5
Matt, This message may indicate that there is an issue with software reading the EEPROM or that the module is no longer detected. There may be some SMBUS messages that may accompany these messages, please feel free to share if so.

It would be necessary to rule out any layer 1 issues at this time. Please let us know if the messages are causing an outage on the stack. Re-seat the modules and or reboot the stack nodes (if possible).

Please review the following Knowledge base article for more information and contact GTAC if problems still arise:
https://gtacknowledge.extremenetworks.com/articles/Solution/timeout-waiting-for-smbus-error-log/?q=0...
Thanks Ty, not see any other SMBUS or EEPROM messages in the log. Also this not causing any type of outage in the stack. We are seeing the error occurs at the same time each day.

06/24/2015 14:27:51.78 Slot-2: Error reading from XEN card eeprom (1, 83)
06/24/2015 14:12:22.81 Slot-1: Error reading from XEN card eeprom (1, 83)
06/23/2015 14:27:51.76 Slot-2: Error reading from XEN card eeprom (1, 83)
06/23/2015 14:12:22.81 Slot-1: Error reading from XEN card eeprom (1, 83)

I have not reboot the stack nodes. Will try to do the reboots this weekend.
Userlevel 6
Hi Matt,

It appears you might be running into the issue mentioned in the below article:

https://gtacknowledge.extremenetworks.com/articles/Solution/timeout-waiting-for-smbus-error-log

This is why it is only displaying on slot 1 and slot 2. According to the article a reboot will temporarily resolve the issue. Ultimately I would recommend upgrading to a recommended version of code. Here is an article where you can find recommended version of codes:

https://gtacknowledge.extremenetworks.com/articles/Q_A/What-Is-The-Recommended-Release-of-EXOS-For-My-Platform

After reviewing this document myself it appears the best version to upgrade to based on this stack would be the latest patch of EXOS 15.3.5.2 (should be patch 1-3 as of today).

I hope this helps.

Patrick Voss
Rebooting the slot 1 & 2 stop the error message in the logs.

Reply