SEEPROM errors

[cy-harrild]

We're upgrading our Site A UCS from 2.0.2m to 2.0.4a but have encountered an intermittent error.

Cluster Id: 0xaee77b42250911e0-0xb5bd000573abf004

A: UP, PRIMARY

B: UP, SUBORDINATE

HA READY

Detailed state of the device selected for HA storage:

Chassis 1, serial: FOX1439G3S5, state: active

Chassis 2, serial: FOX1510GCAG, state: active with errors

Chassis 3, serial: FOX1544G5VG, state: active

Fabric A, chassis-seeprom local IO failure:

FOX1510GCAG READ_FAILED, error: TIMEOUT, error code: 10, error count: 7

Warning: there are pending SEEPROM errors on one or more devices, failover may not complete

During the upgrade of our Site B UCS, we encountered the same fault on chassis 2 after failing over so the primary FI could be updated. On the Site B UCS, chassis 2 is hosting vSphere nodes, configured with dual vNIC's not failover vNIC's.

Logged a ticket, uploaded the logs, but response is slow (think I got caught at the end of a TAC switch over).. The difference is that in this UCS, chassis 2 is hosting Oracle RAC nodes with failover NIC's, i suspect that if I do proceed with the upgrade with this error a failover may occur and cause the servers to reboot rather than failover their vNIC and vHBA.

Has anyone else had a similar experience?

[sidicool2012]

Hi Cy,

I think you should open a maintenance Window then decomission and reboot your chassis.After the reboot , recomission the chassis . That will trigger a new discovery process between UCSM and the chassis.

That should do it.

Let me know

Sidi

[abbharga]

Hi Cy,

This could be due to the IOM on chassis 2 not being online yet.

Can you check in the GUI to see if the IOM is up or not? also can you verify from the CLI (conenct nxos -> show fex) to verify if the IOM is online?

In case the IOM is not online, you can wait for the TAC engineer to work with you and get the IOM online. If the IOM is not online and you reboot the other FI, there are chances of outage to blades on chassis 2.

./Abhinav