Skip to main content
NetApp Knowledge Base

CHASSIS FAN FRU FAILED warning during Service Processor version update

Views:
302
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • FAS8200
  • Service Processor(SP) 5.10

Issue

  • CHASSIS FAN FRU FAILED warning during SP version update to 5.10.
Example:
Jan  6 17:09:33 (none) env_mgr[1476]: Payload action: fruinfo_get(0, FRU_Fan3)
Jan  6 17:09:33 (none) : [360 INFO]handle_ipmi_query: Server Error: Server Is Busy
Jan  6 17:09:33 (none) : [360 INFO]Error in handle_ipmi_query()
Jan  6 17:09:33 (none) : [360 INFO]Failed to Send Message to SPEM
Jan  6 17:09:33 (none) orftp_sender_splog[697]: system() returned ret1 = 0, ret2 = 0
Jan  6 17:09:33 (none) last message repeated 4 times
Jan  6 17:09:34 (none) env_mgr[1476]: Payload EMS: EMS_callhome_c_fan_fru_fault(CHASSIS FAN FRU FAILED: SysFan3 F1)
Jan  6 17:09:34 (none) env_mgr[1476]: Payload EMS: EMS_monitor_chassisFan_stop(SysFan3 F1 (0 RPM))
Jan  6 17:09:34 (none) env_mgr[1476]: Payload action: update_fru_state(0, FRU_Fan3)
Jan  6 17:09:34 (none) env_mgr[1476]: Payload action: splog_get(1, (null))
Jan  6 17:09:34 (none) env_mgr[1476]: Payload EMS: EMS_callhome_c_fan_fru_fault(CHASSIS FAN FRU FAILED: SysFan3 F2)
  • FAN FRU status is normal after SP update.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.