Skip to main content
NetApp Knowledge Base

CHASSIS FAN FRU FAILED: Multiple fans have failed due to high traffic from intercluster LIFs

Views:
295
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
hw
Last Updated:

Applies to

  • ONTAP 9
  • FAS 26xx series
  • FAS 27xx series

Issue

  • One node in HA pair reports issues with reading temperature sensors which get corrected automatically:

[node1: env_mgr: monitor.fan.warning:notice]: multiple fans have failed. Replace it to avoid overheating
[node1: env_mgr: monitor.temp.unreadable:error]: The controller temperature (Module B Expander Temp) is not readable.
[node1: env_mgr: monitor.temp.unreadable:error]: The controller temperature (Module A Expander Temp) is not readable.
[node1: env_mgr: monitor.temp.unreadable:error]: The controller temperature (Midplane 4 Temp) is not readable.
[node1: env_mgr: monitor.temp.unreadable:error]: The controller temperature (Midplane 3 Temp) is not readable.
[node1: env_mgr: monitor.temp.unreadable:error]: The controller temperature (Midplane 2 Temp) is not readable.
[node1: env_mgr: monitor.temp.unreadable:error]: The controller temperature (Midplane 1 Temp) is not readable.
[node1: env_mgr: monitor.temp.unreadable:error]: The controller temperature (Ambient Temp) is not readable.
[node1: env_mgr: callhome.c.fan.fru.fault:error]: Call home for CHASSIS FAN FRU FAILED: Multiple fans have failed
[node1: env_mgr: monitor.fan.ok:notice]: All fans are OK.
[node1: env_mgr: monitor.chassisTemperature.ok:notice]: Chassis temperature is ok.
[node1: monitor: monitor.globalStatus.ok:notice]: The system's global status is normal.

  • Certain temperature sensors go unavailable on the affected node whereas the partner node reports them as normal.

cluster1::> system node run -node * -command environment status
2 entries were acted on.

Node: node1

        Shelf temperatures by element:
          [10] 28 C (82 F)  Normal temperature range
          [11] Unavailable
          [12] Unavailable
          [13] 29 C (84 F)  Normal temperature range

Node: node2

        Shelf temperatures by element:
          [10] 33 C (91 F)  Normal temperature range
          [11] 48 C (118 F)  Normal temperature range
          [12] 26 C (78 F)  Normal temperature range

          [13] 34 C (93 F)  Normal temperature range

  • The FRU status is seen degraded when the issue is active but only from one node:

cluster1::> system controller fru show
Node               FRU Name                     Subsystem          Status
------------------ ---------------------------- ------------------ -----------
node1              PSU1 FRU                     Environment        degraded
node1              PSU2 FRU                     Environment        degraded
node2              PSU1 FRU                     Environment        ok
node2              PSU2 FRU                     Environment        ok

  • The BMC of the affected node reboots frequently and reports the following in the SP event logs:

Record 1250: Sat Jan 28 10:04:27.990616 2023 [BMC.critical]: Rebooting SP due to loss of ACP comms
Record 1251: Sun Jan 01 00:00:23.962645 2017 [IPMI.notice]: 00fd | c0 | OEM: ffff70005100 | ManufId: 150300 | BMC Reset Internally

  • Packet trace analysis on port e0M during issue time reveals high incoming traffic from the intercluster logical interface (IC LIF).

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.