Skip to main content
NetApp adopts Microsoft’s Business-to-Customer (B2C) Identity Management
Effective December 3 - NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources. For accounts that did not pre-register (prior to Dec 3) access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity. To learn more, Read the FAQ and Watch the video. Need assistance? Complete this form and select “Registration Issue” as the Feedback Category. 
NetApp Knowledge Base

System fails to boot with "SP failure. Resetting SP from primary FW" message on AFF A300/FAS8200

Views:
1,666
Visibility:
Public
Votes:
0
Category:
aff-series
Specialty:
hw
Last Updated:

Applies to

  • ONTAP 9
  • AFF A300
  • FAS 8200
  • FAS 2720
  • AFF A220

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

  • Even if the controller is replaced, the system fails to boot with same error
  • 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:

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

 

 

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support

 

  • Was this article helpful?