Skip to main content
NetApp Knowledge Base

CFBMC-3569: BMC "heartbeat stopped" event causes node shutdown

  1. Last updated
  2. Save as PDF
Views:
465
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
hw
Last Updated:

Issue

  • On AFF A900, ASA A900 or FAS9500 systems, ONTAP might detect the loss of BMC heartbeat and initiate a system shutdown or emergency recovery to prevent hardware damage or data loss.
  • Example events indicating the issue:

[node-01: spmgrd: sp.heartbeat.stopped:info]: Have not received a IPMI heartbeat from the Service Processor (SP) in last 600 seconds.
[node-01: spmgrd: callhome.sp.hbt.missed:notice]: Call home for SP HBT MISSED
[node-01: spmgrd: callhome.sp.hbt.stopped:alert]: Call home for SP HBT STOPPED
[node-01: env_mgr: 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 10 minutes.
[node-01: env_mgr: monitor.shutdown.emergency:EMERGENCY]: Emergency shutdown: Environmental Reason Shutdown (System reboot to recover the SP)
  • When the BMC becomes unresponsive, ONTAP reboots to attempt a power-cycle of the BMC to recover it.

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.