Skip to main content
NetApp Knowledge Base

After replacing PANIC node, the replacing node can't boot up and stop at POST with error "IPMI:Get midplane FRU 0 inventory:failed"

Views:
1,399
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • FAS27x0
  • AFF-A220
  • FAS8200
  • AFF-A300

Issue

  • Node Panic with "NMI watch-dog reset" error, after replacing Node the following error raises and system stop at POST.

Example:

Initializing System Memory ...
Loading Device Drivers ...
Waiting for SP ...
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 controller FRU inventory:failed
IPMI:Get midplane FRU 0 inventory:failed

  • From Service Processor (SP) log , the following midplane errors raise.

Example1:

Record 717: Wed Dec 25 01:38:47.000000 2019 [SysFW.notice]: BIOS Version: 11.5
Record 718: Wed Dec 25 01:38:49.000000 2019 [SysFW.notice]: Waiting for SP ...
Record 719: Wed Dec 25 01:38:49.000000 2019 [SysFW.notice]: IPMI:Read midplane FRU common header:device busy. Retrying
Record 720: Sun Jan 01 00:00:33.660000 2017 [BMC.notice]: Running primary version 11.4

Example2:

Record 649: Sat Oct 15 13:05:38.834785 2016 [Agent.notice]: 720.089: 150 : Local Serial Exchange Error Internal MLER[4] asserted
Record 1003: Mon Oct 17 08:38:52.362718 2016 [Agent.notice]: 193.618: 151 : Local Invalid Serial Exchange Bus Internal MLER[5] asserted
Record 807: Thu Jan 01 00:00:36.931067 1970 [Agent.notice]: 000.267: 152 : Midplane I2C Local Buffers Not Ready Internal MLER[6] de-asserted
Record 797: Mon Oct 17 08:52:11.001689 2016 [Agent.notice]: 919.800: 148 : Midplane Local Grant Timeout Internal MLER[2] asserted

 

 

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.