Skip to main content
A newer release of this product is available.

system service-processor image update

Contributors
Suggest changes
PDFs

Update Service Processor firmware

Availability: This command is available to cluster administrators at the admin privilege level.

Description

The system service-processor image update command installs a new firmware version on the Service Processor of specified node in a cluster. If this command fails, it will display and log an appropriate error message and abort. No automatic command retries will be performed. This command also specifies which firmware image is to be installed on the Service Processor and how.

You can use the command system service-processor image update-progress show to check the progress of the update.

The following parameter combinations are not supported for this command:

  • `-update-type`differential with `-clear-logs`true

  • `-baseline`true with `-package`<text>

Parameters

-node {<nodename>|local} - Node

This parameter specifies the node whose Service Processor's firmware is to be updated.

[-package <text>] - Firmware Package

This parameter specifies the package that will be installed. You can find the package file in the SP Update Repository field of the system node image package show command. If you do not specify this parameter, the Service Processor is updated to the most recent version of the firmware that is available in the update repository. You must specify this parameter if baseline is false or omitted.

[-baseline {true|false}] - Install Baseline

If you set this parameter to true, the command installs the Service Processor firmware version that is bundled with the currently running release of Data ONTAP. This is a safety mechanism that allows you to revert the SP firmware to the version that was qualified and bundled with the currently running version of Data ONTAP on your system. If not specified, this parameter defaults to false.

-update-type {serial-full|serial-differential|network-full} - Type

This parameter specifies the type of update to be performed.

If you set the value to serial-full , the command transfers contents of the entire SP firmware image to the SP via the packetized serial interface, and the contents are written to the SP primary partition.

If you set the value to serial-differential , the command transfers the SP firmware files that are different between the old SP firmware image and the new SP firmware image to the SP via the packetized serial interface, and the contents are written to SP primary partition.

If you set the value to network-full , the command transfers the entire SP firmware image to the SP via the SP network interface, and the contents are written to the SP primary partition.

If you do not specify the update-type option, the command checks for dependencies of network-based SP firmware updates. If the dependencies are satisfied, then the command uses the SP network interface to update the SP firmware. If the dependencies are not satisfied, then the serial interface is used.

[-clear-logs {true|false}] - Clear Logs After Update

If you set this parameter to true , the command resets log settings to factory default and clears contents of all logs maintained by the Service Processor, including:

  • Event logs

  • IPMI logs

  • Forensics logs

Examples

The following command reverts the firmware on the Service Processor of the local node to the version that was packaged with the currently running release of Data ONTAP. A complete install will be performed, clearing all logs maintained by the Service Processor. The second command displays the status of the in-progress firmware install.

cluster1::> system service-processor image update -node local -update-type full -baseline true -clear-logs true
cluster1::>

cluster1::> system service-processor image update-progress show
                 In                           Percent
Node             Progress Start Time          Done    End Time
---------------- -------- ------------------- ------- -------------------
node1            yes      8/28/2012 20:00:34  99      -
node2            no       -                   0       -
2 entries were displayed.

cluster1::>