Skip to main content
NetApp Knowledge Base

Node fails to boot with "BMC IPMI communication failed" error

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

Applies to

  • AFF-A700S
  • FAS8200

Issue

  • Node fails to boot with "BMC IPMI communication failed" error after replacing motherboard.

Failed to write to KCS device
BMC IPMI communication failed
ERROR: Platform verification failed. Autoboot will be disabled.
Failed to write to KCS device
Failed to get DHCP setting: Unknown IPMI completion code.
Failed to read to KCS device
Failed to get address: Unknown IPMI completion code.
Failed to set DHCP setting: Node busy.
Unable to disable DHCP on BMC internal LAN
Failed to set address: Node busy.
Failed to set BMC_A internal IP to 192.0.2.81
ERROR: Platform initialization failed. Autoboot will be disabled.

  • After upgrading SP and BIOS, still not able to boot and come to loader

Initializing System Memory ...
Loading Device Drivers ...
Waiting for SP ...

Error: Unable to establish LAN session
Unable to get Chassis Power Status

Record 93: Thu Jan  1 00:00:40 1970 [IPMI.notice]: 0e00 | c0 | OEM: fcff70560000 | ManufId: 150300 | POS Register: Power on Reset(Normal Power Cycle)
Record 94: Thu Jan  1 00:01:02 1970 [SP.notice]: Running primary version 5.11
Record 95: Thu Jan  1 00:02:06 1970 [SP.notice]: IPMI not ready & run /usr/local/bin/notify 4
Record 96: Thu Jan  1 00:06:01 1970 [IPMI.warning]: FRUID 1 Access error
Record 97: Thu Jan  1 00:06:10 1970 [SP CLI.notice]: naroot "log in from Serial Console"
Record 98: Thu Jan  1 00:07:11 1970 [SP.notice]: Switch is running on latest version 16
Record 99: Thu Jan  1 00:10:35 1970 [SP.notice]: Failure on battery wake up attempt
Record 100: Thu Jan  1 00:11:22 1970 [IPMI.warning]: FRUID 2 Access error
Record 101: Thu Jan  1 00:13:06 1970 [SP.critical]: Heartbeat stopped

SP> system fru show 0
IPMI session creation failed - err(0x0021)

SP> system fru show 1
IPMI session creation failed - err(0x0021)

  • System becomes unresponsive via console after reseating motherboard.
  • Replacing the motherboard again does not solve the problem.

 

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.