{"id":900,"date":"2012-12-03T22:32:47","date_gmt":"2012-12-03T22:32:47","guid":{"rendered":"http:\/\/www.kozeniauskas.com\/itblog\/?p=900"},"modified":"2012-12-03T22:32:47","modified_gmt":"2012-12-03T22:32:47","slug":"ucs-warning-there-are-pending-seeprom-errors-on-one-or-more-devices-failover-may-not-complete","status":"publish","type":"post","link":"http:\/\/www.kozeniauskas.com\/itblog\/2012\/12\/03\/ucs-warning-there-are-pending-seeprom-errors-on-one-or-more-devices-failover-may-not-complete\/","title":{"rendered":"UCS: Warning: there are pending SEEPROM errors on one or more devices, failover may not complete"},"content":{"rendered":"

In UCS CLI after issuing command ‘show cluster state<\/strong>‘ a warning is received on one of the chassis.<\/p>\n

UCS-B # show cluster state<\/em>
\nCluster Id: 0xf122a7f83dba11e0-0x9a4c123573c4f1c4<\/em><\/p>\n

B: UP, PRIMARY<\/em>
\nA: UP, SUBORDINATE<\/em><\/p>\n

HA READY<\/em>
\nDetailed state of the device selected for HA storage:<\/em>
\nChassis 1, serial: FOX1234567A, state: active<\/em>
\nChassis 2, serial: FOX1234567B, state: active<\/em>
\nChassis 5, serial: FOX1234567C, state: active with errors<\/em><\/p>\n

Fabric B, chassis-seeprom local IO failure:<\/em>
\nFOX1234567C READ_FAILED, error: TIMEOUT, error code: 10, error count: 7<\/em>
\nWarning: there are pending SEEPROM errors on one or more devices, failover may not complete<\/em><\/p>\n

In sam_techsupportinfo \u00a0log you\u2019ll see the following message
\nCreation Time: 2012-10-12T01:12:21.217<\/em>
\nID: 2712562<\/em>
\nDescription: device FOX1234567C, error accessing shared-storage<\/em>
\nAffected Object: sys\/mgmt-entity-B<\/em>
\nTrigger: Oper<\/em>
\nUser: internal<\/em>
\nCause: Device Shared Storage Io Error<\/em>
\nCode: E4196537<\/em><\/p>\n

This is known Cisco Bug\u00a0CSCtu17144<\/a>\u00a0and here is what needs to be done<\/p>\n

If the fault condition stays on or keeps being cleared and re-raised, try the following workarounds:
\n1. Reboot the IO module.
\n2. Remove and re-seat the IO module. Make sure the module is in contact with the backplane firmly.<\/p>\n

I’ve had this problem couple times and resetting IO module was enough in both cases<\/p>\n","protected":false},"excerpt":{"rendered":"

In UCS CLI after issuing command ‘show cluster state‘ a warning is received on one of the chassis. UCS-B # show cluster state Cluster Id: 0xf122a7f83dba11e0-0x9a4c123573c4f1c4 B: UP, PRIMARY A: UP, SUBORDINATE HA READY Detailed state of the device selected for HA storage: Chassis 1, serial: FOX1234567A, state: active Chassis 2, serial: FOX1234567B, state: active […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[380,381],"tags":[497,403,405,402,404,498],"_links":{"self":[{"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/posts\/900"}],"collection":[{"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/comments?post=900"}],"version-history":[{"count":1,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/posts\/900\/revisions"}],"predecessor-version":[{"id":901,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/posts\/900\/revisions\/901"}],"wp:attachment":[{"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/media?parent=900"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/categories?post=900"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/tags?post=900"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}