"system node service-processor" shows degraded status after SP reboot

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

Views:: 3,951

Visibility:: Public

Votes:: 1

Category:: fas-systems

Specialty:: hw

Last Updated:

Applies to

FAS8020
FAS8040
FAS2620
FAS2650
FAS8200
Data ONTAP 9
Data ONTAP 8

Issue

After rebooting the Service Processor (SP), the SP changes to degraded status.

Cluster::*> system node service-processor reboot-sp -node *

Note: If your console connection is through the SP, it will be disconnected. Do you want to reboot the SP ? {y|n}: y 2 entries were acted on.

Cluster::*> Cluster::*> system node service-processor autosupport image network reboot-sp show snmp

Cluster::*> system node service-processor show IP Firmware Node Type Status Configured Version IP Address ------------- ---- ----------- ------------ --------- ------------------------- node-1 SP rebooting false 3.0.2 - node-2 SP rebooting false 3.0.2 -

Cluster::*> system node service-processor show IP Firmware Node Type Status Configured Version IP Address ------------- ---- ----------- ------------ --------- ------------------------- node-1 SP online false 3.0.2 - node-2 SP rebooting false 3.0.2 -

Cluster::*> system node service-processor show IP Firmware Node Type Status Configured Version IP Address ------------- ---- ----------- ------------ --------- ------------------------- node-1 SP online false 3.0.2 - node-2 SP unknown false 3.0.2 -

Cluster::*> system node service-processor show IP Firmware Node Type Status Configured Version IP Address ------------- ---- ----------- ------------ --------- ------------------------- node-1 SP online false 3.0.2 - node-2 SP degraded true 3.0.2 0.0.0.0

Cluster::> sp ervice-p r processor show (system node service-processor show) IP Firmware Node Type Status Configured Version IP Address ------------- ---- ----------- ------------ --------- ------------------------- node-1 SP online false 3.0.2 - node-2 SP offline true 3.0.2 0.0.0.0

"node-1" starts takeover because "node-2's SP goes offline.

Cluster::> Feb 20 09:53:59 [node-2:monitor.shutdown.emergency:EMERGENCY]: Emergency shutdown: Environmental Reason Shutdown (SP IPMI Dead) Waiting for PIDS: /usr/sbin/ypbind 729. Waiting for PIDS: 695. Terminated . Uptime: 28d13h49m5s System powering down... System halting... BIOS version: 9.3 Portions Copyright (c) 2011-2014 NetApp. All Rights Reserved 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 PCI Slot Control failed. IPMI:Get controller FRU inventory:failed Phoenix SecureCore Tiano(TM) Copyright 1985-2021 Phoenix Technologies Ltd. All Rights Reserved

Build Date: 12/02/2014 ********************************************** * 9.3 * * ================================== * * PHOENIX SC-T 2009-2021 * ********************************************** CPU = 1 Processor(s) Detected, Cores per Processor = 8 Intel(R) Xeon(R) CPU E5-2658 @ 2.10GHz 32768 MB System RAM Installed 256 KB L2 Cache System BIOS shadowed Video BIOS shadowed USB Device: MICRON eUSB DISK

BIOS POST Failure(s) detected: SP IPMI failure. Abort AUTOBOOT

Unplugging and re-plugging "node-2" cannot clear the error.

LOADER-B> BIOS version: 9.3 Portions Copyright (c) 2011-2014 NetApp. All Rights Reserved 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 PCI Slot Control failed. IPMI:Get controller FRU inventory:failed Phoenix SecureCore Tiano(TM) Copyright 1985-2021 Phoenix Technologies Ltd. All Rights Reserved

BIOS POST Failure(s) detected: SP IPMI failure. Abort AUTOBOOT