Skip to main content
NetApp Knowledge Base

CFBMC-6022: Takeover due to BMC SoC hang causes ONTAP shutdown with BMC FW 13.11

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

Issue

Platforms running:

  • BMC FW 13.11
  • BMC FW 13.11P1

Takeover performed by partner node after a missed and stopped heartbeat.
  • The ONTAP has not received an IPMI heartbeat from the Service Processor (SP) in the last 600 seconds
  • The ASUP system has notified that the SP heartbeat has stopped
  • The system has been rebooted to recover the BMC

EMS log Example:
ERROR  asup.post.drop: AutoSupport message (HA Group Notification from node-01 (SP HBT MISSED) NOTICE) was not posted to NetApp. The system will drop the message.
ERROR  mgmtgwd.vreport.nodesUnreachable: Vreport encountered some unreachable nodes. The report may be incomplete.
ALERT  callhome.sfo.takeover: Call home for CONTROLLER TAKEOVER COMPLETE AUTOMATIC
ERROR  cf.fsm.takeoverOfPartnerDisabled: Failover monitor: takeover of node-02 disabled (local halt in progress).
EMERGENCY   monitor.shutdown.emergency: Emergency shutdown: Environmental Reason Shutdown (System reboot to recover the BMC)
EMERGENCY   sp.ipmi.lost.shutdown: SP heartbeat stopped and cannot be recovered. To prevent hardware damage and data loss, the system will shut down in 10 minutes.
ALERT  callhome.sp.hbt.stopped: Call home for SP HBT STOPPED
ALERT  callhome.sp.hbt.missed:notice]: Call home for SP HBT MISSED
ERROR  sp.heartbeat.stopped: Have not received a IPMI heartbeat from the Service Processor (SP) in last 600 seconds.

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.