Decoding a SecureStack Fan Failure error message

  • 0
  • 1
  • Article
  • Updated 5 years ago
  • (Edited)
Article ID: 5743 

Products
SecureStack C3
SecureStack C2
SecureStack B3
SecureStack B2
SecureStack A2 

Goals
Decode a fan failure error message. 

Symptoms
Error message:
"0.0.0.0 SIM[]: bootos.c() % Fan has failed." 

Cause
If a SecureStack cooling fan fails, the condition is reported in the syslog, logging buffer, serial console, and current.log (10819).
It is also reported as a generic fanFail trap (13323). 

With lower firmware (C3/B3 f/w 6.03.00.0022 and lower, C2 f/w 5.02.06.0004 and lower, B2 f/w 4.02.06.0004 and lower, A2 f/w all) 

Here is an example of such an error message:

<162> MAR 20 15:00:36 0.0.0.0-5 SIM[243378128]: bootos.c(1515) 298 %%
Fan 2 has failed.

The failing stack unit number is represented by the last digit of the '<IP_address>-x' string (unit 5, in this case), and the failed fan instance on that unit is represented by the 'Fan x' designation (instance 2, in this case). 

For this example; stack unit 5 (5780), fan instance 2 (10819) has failed. 

With higher firmware (C3/B3 f/w 6.03.01.0008 and higher, C2 f/w 5.02.07.0006 and higher, B2 f/w 4.02.07.0006 and higher) 

Here is an example of such an error message:

<162> Aug 30 05:35:48 10.2.1.62-1 SIM[204096992]: edb_bxs.c(1230) 571 %%
Unit 3: Fan 1 has failed.

The stack unit number of the manager unit issuing the message is represented by the last digit of the '<IP_address>-x' string (unit 1, in this case), and the failing stack unit number and failed fan instance (unit 3's fan 1, in this case) are both now explicitly stated. 

Solution
Please contact Enterasys Networks Technical Services for assistance.
Photo of FAQ User

FAQ User, Official Rep

  • 13,620 Points 10k badge 2x thumb

Posted 5 years ago

  • 0
  • 1

There are no replies.

This conversation is no longer open for comments or replies.