Skip to main content
NetApp Knowledge Base

Unexpected node reboot reporting "Multiple bit error address 8xxxxxxx"

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

Applies to

AFF A250

Issue

  • Unexpected node reboot with BMC syslog output example: 
2021-04-30T02:51:28.812572 00:00 localhost kernel: kernel - - [581600.980000] Multiple bit error address 8c96a038 -
...
2021-04-30T02:51:29.852344 00:00 localhost kernel: kernel - - [581602.010000] Multiple bit error address 8c96a038 -
2021-04-30T02:51:35.079281 00:00 localhost shutdown[2271]: shutdown 2271 - shutting down for system reboot -
  • EMS messages from partner, example:
Fri Apr 30 05:14:25 +0200 [node_name2: spmgrd: sp.heartbeat.stopped:error]: Have not received a IPMI heartbeat from the Service Processor (SP) in last 600 seconds.
Fri Apr 30 05:14:25 +0200 [node_name2: spmgrd: callhome.sp.hbt.missed:notice]: Call home for SP HBT MISSED
Fri Apr 30 05:25:58 +0200 [node_name2: spmgrd: callhome.sp.hbt.stopped:alert]: Call home for SP HBT STOPPED

 

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.