メインコンテンツまでスキップ

複数のファンに障害が発生したためにノードがシャットダウンし、ブートに失敗する

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

環境

  • ベースボード管理コントローラファームウェア が 11.5 未満です
    • AFF C190 、 AFF A220 、 FAS2720 、 FAS2750
  • 5.8 より前のサービスプロセッサファームウェアです
    • AFF A300 、 AFF A200 、 FAS8200 、 FAS2650 、 FAS2620

問題

  • 両方のノードがシャットダウンし、ブートできませんでした

  • 次のメッセージが表示されてノードがシャットダウンします。

Sat May 08 22:20:24 +0100 [node-1: env_mgr: monitor.shutdown.emergency:EMERGENCY]: Emergency shutdown: Environmental Reason Shutdown (Multiple fans failed)
Sat May 08 22:20:27 +0100 [node-1: mgwd: mgwd.notify.halt.result:info]: MGWD able to notify CLAM on its HA partner node that this node is undergoing a planned shutdown (reason: E). Error: -
Sat May 08 22:20:34 +0100 [node-1: env_mgr: monitor.shutdown.emergency:EMERGENCY]: Emergency shutdown: Status of fans is unknown for 90 seconds. Shutting down now.

  • AutoSupport ではアラートがトリガーされる可能性が

HA Group Notification (CONTROLLER TAKEOVER COMPLETE HALT) NOTICE

HA Group Notification (Health Monitor process cphm: CriticalFruMultiFaultAlert[PSQ094195000111]) ALERT

  • ノードをブートできず、コントローラの再取り付けを試行すると、ノードが停止したままになるか、起動できない可能性があります

  • コンソールログのブート時に次のようなメッセージが表示されることがあります。

Initializing System Memory ...
Loading Device Drivers ...
Configuring Devices ...
Waiting for SP ...

IPMI:Read midplane FRU 0 product info:timeout
IPMI:Read midplane FRU 0 product info:failed
Waiting for SP ...

IPMI:Get midplane FRU 1 inventory:timeout
SP failure. Resetting SP from primary FW. This can take a few minutes
Waiting for SP ...
SP failure. Resetting SP from backup FW. This can take a few minutes
Waiting for SP ...
Failed to recover SP
IPMI:Get midplane FRU 1 inventory:failed

IPMI:Get controller FRU inventory:failed
IPMI:Get midplane FRU 0 inventory:failed
Configuring Devices ...
IPMI PCI Slot Control failed.

  • ブートに成功した場合、ノードから別のセンサーに苦情があり、再度シャットダウンされる可能性があります。

Mon May 24 10:07:52 GMT [nvram.hw.initWarn:WARNING]: NVRAM hardware initialization: Failed to get Battery FRU info.

May 24 10:11:19 [node-1:sp.ipmi.lost.shutdown:EMERGENCY]: SP heartbeat stopped and cannot be recovered. To prevent hardware damage and data loss, the system will shut down in 2 minutes.
May 24 10:13:19 [node-1:monitor.shutdown.emergency:EMERGENCY]: Emergency shutdown: Environmental Reason Shutdown (System reboot to recover the SP)

 

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.