Cisco Bugid CSCul44421 Chassis seeprom local IO failure error on Switch

Symptom:

Error accessing shared-storage fault.

Problem Details: affected="sys/mgmt-entity-A"
cause="device-shared-storage-IO-error"
changeSet=""
code="E4196535"
created="2013-12-18T08:50:03"
descr="device Fxxxxxxxxxxxx, error accessing shared-storage"
dn="event-log/785673"
id="785673"
ind="state-transition"

From Cisco support :

The error accessing shared-storage fault is not harmful and does not affect system functionalities.  In UCS chassis design, we build in a chip called, SEEPROM, on the backplane. SEEPROM is a permanent memory and used to store cluster database version to avoid the case of cluster database being overwritten by old version when failover happens.

The communication between IO module and SEEPROM is one way. We store the identical SAM DB version in three chassis rather than in one (so called three chassis redundancy). Because the communication between IO module and SEEPROM happens only one way, the error accessing shared-storage fault can happen sometimes - this is system behavior per specification and design. So, as long as one SEEPROM is readable, the UCS works normally.

If the error accessing shared-storage fault is currently in cleared state and does not raise again, do not apply the workaround and do not do anything.

If the error accessing shared-storage fault is raised state and is never cleared, or the fault keeps coming back, try the following workarounds:

* Reboot the IO module.


* If alert does not clear, reseat IO module. Make sure it's firmly seated.

https://tools.cisco.com/bugsearch/bug/CSCul44421

Other workaround mentioned in Cisco support forum:

• Reboot/Reseat IOM
• Reboot Chassis

https://supportforums.cisco.com/discussion/11349691/ucs-error-accessing-shared-storage-f0863