Hi Matt,

thanks for the hint, I must have overread this small difference all the time lately :-/

Unfortunately, using the zip file doesn’t change the behaviour:

CLUSTER::*> system node image package show

Package

Node Repository Package File Name

------------ -------------- -----------------

Node1

mroot

SP_FW_308-04195_11.11.zip

Node2

mroot

SP_FW_308-04195_11.11.zip

2 entries were displayed.

The auto update kicks in about 20min after the download, event log says:

CLUSTER::*> event log show

Time Node Severity Event

------------------- ---------------- ------------- ---------------------------

1/14/2025 17:39:18 Node1 ERROR sp.upd.unzip.event: Service Processor failed to decompress the image package.

1/14/2025 17:38:07 Node2 ERROR sp.upd.unzip.event: Service Processor failed to decompress the image package.

A manual try says:

CLUSTER::*> system service-processor image update -node Node1 -package SP_FW_308-04195_11.11.zip

Note: Firmware update will need to reboot the SP on completion. If your console connection is through the SP, it will be disconnected

Do you want to proceed with the firmware update ? {y|n}: y

Error: command failed: Unable to schedule Service Processor update.

And this command does not produce any additional entry in the event log.

Best,

Alexander Griesser

Head of Systems Operations

ANEXIA Internetdienstleistungs GmbH

E-Mail: AGriesser@anexia.com

Web: https://www.anexia.com

Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt

Geschäftsführer: Alexander Windbichler

Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601

Von: Sullivan, Matt <Matt.Sullivan@netapp.com>
Gesendet: Dienstag, 14. Jänner 2025 16:52
An: Alexander Griesser <AGriesser@anexia.com>; toasters@teaparty.net
Betreff: [EXT] RE: Unable to schedule service processor update

ATTENTION: This email originated from outside of the organisation. Do not click on links or open attachments unless you recognize the sender and know the content is safe

Hi Alexander,

Installing SP Firmware from ONTAP would use a .zip file. The .tar file is the one used when installing from the SP prompt.

Download this one and give it a shot:

https://mysupport.netapp.com/site/downloads/firmware/system-firmware-diagnostics/download/SYSTEM/30804195_ontap/SP_FW_308-04195_11.11.zip

Matt Sullivan

Account Technical Specialist

Civilian Agencies

NetApp U.S. Public Sector, Inc.

From: Alexander Griesser <AGriesser@anexia.com>
Sent: Tuesday, January 14, 2025 12:23 AM
To: toasters@teaparty.net
Subject: Unable to schedule service processor update

You don't often get email from agriesser@anexia.com. Learn why this is important

EXTERNAL EMAIL - USE CAUTION when clicking links or attachments

Hey folks,

I got a bunch of A220s here which I want to update to the latest SP firmware:

CLUSTER::*> system service-processor show

IP Firmware

Node Type Status Configured Version IP Address

------------- ---- ----------- ------------ --------- -------------------------

Node1 BMC online true 11.9P1 127.0.0.1

Node2 BMC online true 11.9P1 127.0.0.2

2 entries were displayed.

But everytime I try to install the update from the Ontap prompt, I get the following message:

CLUSTER::*> system service-processor image update -node * -package SP_FW_308-04195_11.11.tar.gz

Note: Firmware update will need to reboot the SP on completion. If your console

connection is through the SP, it will be disconnected

Do you want to proceed with the firmware update ? {y|n}: y

Error: command failed on node "Node1": Unable to schedule Service

Processor update.

The only KB article I found for this issue is this one:

https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/BMC_upgrade_fails_with_Error_command_failed__Unable_to_schedule_Service_Processor_update

I can verify that the file is not corrupted (compared the MD5 sums) and I tried to reboot the SP before the update, but all to no avail.

The only way I can get the BMC firmware update installed is by using “bmc update -f” directly on the bmc shell, but that’s harder to automate.

Has anyone ever stumbled upon that and has an idea?

SP Auto Updates are enabled, but they’re not starting either – waited for a day for them to do their job.

Thanks,