Skip to main content
NetApp Knowledge Base

CFBMC-8474: BMC hang in "pilot4_lowlevel_init" during u-boot initialization causes BMC unresponsiveness

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

Issue

  • On AFF A250 systems with BMC firmware version 15.13, the BMC may become unresponsive during the u-boot initialization process.

  • The hang has been observed in the pilot4_lowlevel_init function, and in some cases in the Boot_To_BackupSPI function.

  • When this occurs, ONTAP may detect the loss of BMC heartbeat and initiate a system shutdown or emergency recovery to prevent hardware damage or data loss.

The BMC typically recovers after a Power On Reset (POR).
Example events indicating the issue include:
[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.

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.