System fails to boot with "SP failure. Resetting SP from primary FW" message

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 3,116

Visibility:: Public

Votes:: 0

Category:: fas-systems

Specialty:: hw

Last Updated:

Applies to

ONTAP 9
FAS2720
AFF A220
AFF A300 / FAS 8200

Issue

Service Processor (SP) reports SP load is high error in the console log and a node goes down.
ONTAP is unable to boot from Loader with the following error after the node down:

Example:

LOADER-A> boot_ontap Loading X86_64/freebsd・・・ Loading X86_64/freebsd・・・ Starting program at ・・・ NetApp Data ONTAP 9.3P4 *************************************** This platform is not supported in this release. The system will now halt *************************************** BIOS Version: 11.1 Portions Copyright (C) 2014-2017 NetApp, Inc. All Rights Reserved. Initializing System Memory ... Loading Device Drivers ... Waiting for SP ... SP failure. Resetting SP from primary FW. This can take a few minutes

Or:

Failed to recover SP IPMI:Get controller FRU inventory:failed IPMI:Get midplane FRU 0 inventory:failed Configuring Devices ... IPMI PCI Slot Control failed. CPU = 1 Processor(s) Detected. Intel(R) Xeon(R) CPU D-1587 @ 1.70GHz (CPU 0) CPUID: 0x00050664. Cores per Processor = 16 131072 MB System RAM Installed. SATA (AHCI) Device: SV9MST6D120GLM41NP Boot Loader version 6.0.10 Copyright (C) 2000-2003 Broadcom Corporation. Portions Copyright (C) 2002-2020 NetApp, Inc. All Rights Reserved. BIOS POST Failure(s) detected: SP IPMI failure. Abort AUTOBOOT

Down controller fails to boot with same error after replacement
The following message appears in the SP events all. Example:

Record 231: Sun Aug 1 00:25:04 2021 [SysFW.notice]: Failed to recover SP Record 232: Sun Aug 1 00:25:04 2021 [SysFW.critical]: IPMI:Get controller FRU inventory:failed Record 233: Sun Aug 1 00:25:04 2021 [SysFW.notice]: IPMI:Get midplane FRU 0 inventory:failed Record 234: Thu Jan 1 00:05:00 1970 [Trap Event.critical]: hwassist post_error (26)

The following message appears in the SP events all log on the partner node. Example:

Sat Oct 15 13:05:38 2016 [Agent.notice]: Local Serial Exchange Error Internal MLER[4] asserted Mon Oct 17 08:38:52 2016 [Agent.notice]: Local Invalid Serial Exchange Bus Internal MLER[5] asserted Thu Jan 01 00:00:36 1970 [Agent.notice]: Midplane I2C Local Buffers Not Ready Internal MLER[6] de-asserted Mon Oct 17 08:52:11 2016 [Agent.notice]: Midplane Local Grant Timeout Internal MLER[2] asserted