CHASSIS FAN FRU FAILED and INVALID CHASSIS CONFIGURATION

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 117

Visibility:: Public

Votes:: 0

Category:: aff-series

Specialty:: hw

Last Updated:

Applies to

AFF A150
ONTAP 9
Cluster-Mode HA Configurations

Issue

Both Nodes report "CHASSIS FAN FRU FAILED: Multiple fans have failed "at same time :

HA Group Notification from Cluster-01 (CHASSIS FAN FRU FAILED: Multiple fans have failed) ERROR HA Group Notification from Cluster-02 (CHASSIS FAN FRU FAILED: Multiple fans have failed) ERROR

EMS errors shows multiple sensors unavailable:

[Cluster: env_mgr: callhome.c.fan.fru.fault:error]: Call home for CHASSIS FAN FRU FAILED: Multiple fans have failed

The following attempts did not resolve the issue, The alert can not be cleared.

Upgraded BIOS and BMC firmware to latest version ;
Reboot BMC on both nodes.
Reseat Motherboard and try to replace Motherboard. Every node can not boot after reseat with following errors even used new MB.

Node A: +++++++++++++++++++++++++++ Initializing System Memory ... Loading Device Drivers ... Waiting for SP ... IPMI:Read midplane FRU common header:timeout SP failure. Resetting SP from primary FW. This can take a few minutes Waiting for SP ... SP recovered successfully after a reset from primary FW image Waiting for SP ... IPMI:Read midplane FRU common header:failed Configuring Devices ...

CPU = 2 Processor(s) Detected. Intel(R) Xeon(R) CPU D-1557 @ 1.50GHz (CPU 0) CPUID: 0x00050664. Cores per Processor = 12 CPU1 (CPU 1) CPUID: 0x00000000. Cores per Processor = 0 32768 MB System RAM Installed. SATA (AHCI) Device: ATP SATAIII mSATA AF120GSTHI-NT5

Boot Loader version 8.1.0 Copyright (C) 2000-2003 Broadcom Corporation. Portions Copyright (C) 2002-2023 NetApp, Inc. All Rights Reserved. BIOS POST Failure(s) detected: Failed to get FRU data. Abort AUTOBOOT

BMC Event log： Record 120: Tue Jun 03 14:38:13.347240 2025 [ASUP.notice]: First notification email | (INVALID CHASSIS CONFIGURATION (Incompatible Partner PCM)) CRITICAL | Send failed Record 121: Tue Jun 03 14:39:26.286753 2025 [ASUP.notice]: First notification email | (INVALID CHASSIS CONFIGURATION (Incompatible Partner PCM)) CRITICAL | Send failed

Node B: +++++++++++++++++++++++++++ Starting program at 0xffffffff80348000 ---<<BOOT>>--- NetApp Data ONTAP 9.14.1P1 random: registering fast source Intel Secure Key RNG *************************************************** This platform is not supported in this release. The system will now halt ***************************************************

Initializing System Memory ... Loading Device Drivers ... Waiting for SP ... IPMI:Read midplane FRU common header:timeout SP failure. Resetting SP from primary FW. This can take a few minutes Waiting for SP ... SP recovered successfully after a reset from primary FW image Waiting for SP ... IPMI:Read midplane FRU common header:failed

Configuring Devices ... CPU = 2 Processor(s) Detected. Intel(R) Xeon(R) CPU D-1557 @ 1.50GHz (CPU 0) CPUID: 0x00050664. Cores per Processor = 12 CPU1 (CPU 1) CPUID: 0x00000000. Cores per Processor = 0 32768 MB System RAM Installed. SATA (AHCI) Device: ATP SATAIII mSATA AF120GSTHI-NT5

BMC Event log： Record 444: Tue Jun 03 14:45:55.696857 2025 [ASUP.notice]: First notification email | (INVALID CHASSIS CONFIGURATION (Incompatible Partner PCM)) CRITICAL | Send failed Record 445: Tue Jun 03 14:47:08.277524 2025 [ASUP.notice]: First notification email | (INVALID CHASSIS CONFIGURATION (Incompatible Partner PCM)) CRITICAL | Send failed

4. Conducted cross-controller testing, which revealed the chassis fault.