メインコンテンツへスキップ

シャーシファンFRUが故障し、シャーシ構成が無効です

Views:
Visibility:
Public
Votes:
0
Category:
aff-series
Specialty:
HW
Last Updated:

環境

  • AFF A150
  • ONTAP 9
  • クラスタモード HA 構成

問題

  • 両方のノードが同時に「シャーシファンFRU障害: 複数のファンが故障しました」と報告します。

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 エラーは複数のセンサーが利用できないことを示します:

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

  • 以下の試行では問題は解決されませんでした。アラートをクリアできません。
  1. BIOSとBMCファームウェアを最新バージョンにアップグレードしました。
  2. 両ノードのBMCを再起動しました。
  3. マザーボードを装着し直し、交換を試みました。新しいマザーボードを使用しても、装着後、すべてのノードが以下のエラーで起動できません。

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  
***************************************************

BIOS Version: 11.21
Portions Copyright (C) 2014-2023 NetApp, Inc. All Rights Reserved.

Initializing System Memory ...
Loading Device Drivers ...
Waiting for SP ...
BIOS Version: 11.21
Portions Copyright (C) 2014-2023 NetApp, Inc. All Rights Reserved.

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 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.クロスコントローラテストを実施した結果、シャーシの障害が明らかになりました。

 

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.