SPAutoUpgradeFailedMajorAlert remains in SYSTEM-HEALTH-ALERT-PERSISTENT after successful SP/BMC upgrade
Applies to
- ONTAP 9
- Service Processor (SP)
- Baseboard Management Controller (BMC)
- Firmware upgrade
Issue
- After an SP automatic firmware upgrade failure during an ONTAP upgrade, the health alert
SPAutoUpgradeFailedMajorAlertis generated.
Cluster::> system health alert show -instance
Node: Node01
Monitor: controller
Alert ID: SPAutoUpgradeFailedMajorAlert
Alerting Resource: SP Upgrade
Subsystem: Service-Processor
Indication Time: Tue Jun 28 21:04:44 2022
Perceived Severity: Major
Probable Cause: Configuration_error
Description: A Service Processor automatic firmware update failure was detected, which can result in Service Processor not being updated to the latest available compatible firmware package.
Corrective Actions: 1. Use the "system service-processor image show" command to display the firmware version that SP is currently booted from.
2. Manually upgrade Service Processor by using the "system service-processor image update" command.
3. Allow sufficient time for the system to update Service Processor firmware to the specified SP firmware package.
4. Contact the technical support if the alert persists.
Possible Effect: Suboptimal system behavior can result from Service Processor not being updated to the latest available compatible firmware package.
Acknowledge: false
Suppress: false
Policy: SPAutoUpgradeFailedMajorAlertPolicy
Acknowledger: -
Suppressor: -
Additional Information: New firmware available: false
New firmware Version : Not Applicable
Auto update: true
Auto update Status: installed
Previous AutoUpdate Status : failed
Alerting Resource Name: SP Upgrade
Additional Alert Tags: device
- SP firmware is later upgraded successfully and all health subsystems report ok, the alert can continue to appear in AutoSupport under
SYSTEM-HEALTH-ALERT-PERSISTENT.XMLeven after theSPAutoUpgradeFailedMajorAlerthas been deleted.Cluster::> system health alert delete -node * -alert-id SPAutoUpgradeFailedMajorAlertError:There are no entries matching your query.Cluster::> system health subsystem showSubsystem Health----------------- ------------------SAS-connect okEnvironment okMemory okService-Processor okSwitch-Health okCIFS-NDO okMotherboard okIO okMetroCluster okMetroCluster_Node okFHM-Switch okFHM-Bridge okSAS-connect_Cluster ok13 entries were displayed.
