>>> ÎÁ ÓÅÍÉÔÏÎÎÉËÅ ×ÙÓËÏÞÉÌÉ ×ÏÔ ÔÁËÉÅ ÏÛÉÂËÉ × ÌÏÇÁÈ, ÞÔÏÂÙ ÜÔÏ ÚÎÁÞÉÌÏ?
>>> 016 Feb 5 01:26:44 sw1 %DIAGCLIENT-2-EEM_ACTION_HM_SHUTDOWN: Test <SpineControlBus>
>>> has been disabled as a part of default EEM action
>>> 2016 Feb 5 01:26:44 sw1 ÞVICE_TEST-2-PWR_MGMT_BUS_FAIL: Module 5 has failed test SpineControlBus
>>> 20 times on device Power Mgmt Bus on slo
>>> t 14 due to error Spine control test failed error number 0x00000002
>> ÓÁÍ ÓÐÒÏÓÉÌ ÓÁÍ ÏÔ×ÅÔÉÌ =)
>> https://quickview.cloudapps.cisco.com/quickview/bug/CSCtd94427
> Á ÎÅÔ, ÜÔÏ ÄÒÕÇÏÅ =( ÐÏÈÏÖÅ ÞÔÏ ×ÏÔ ÜÔÏ:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuc72466;jse...
Symptom:
SpineControlBus diagnostic test failure on active and/or standby supervisor.
Conditions:
This happens when active and standby supervisors run the Spine test at the same time.
Workaround:
Configure the following for the module in question (only one SUP, even if both have the error):
NOTE: Test 11 is for Sup1, Test 10 is for Sup2
N7K(config)# no diagnostic monitor module 5 test 11
N7K(config)# diagnostic clear result module 5 test 11
N7K(config)# diagnostic monitor interval module 5 test 11 hour 0 min 0 second 31
N7K(config)# diagnostic monitor module 5 test 11
N7K(config)# diagnostic start module 5 test 11
This workaround will decrease the possibility of this condition occurring but does not guarantee that the diagnostic failure will never be encountered. For that the customer needs to upgrade to the proper code with this fix.
Further Problem Description: