updatecomp apply

This command updates firmware on a specific device.

Syntax

updatecomp apply  -h

updatecomp apply  -a apply [-m <activate_mode>] [-l <device_list>]
                          [-c <CMMs>] [-s <servers>] [-t <storage_systems>] [-w <switches>]

updatecomp apply  -a applyBundle [-s <servers>]

updatecomp apply  -a cancelapply [-l <device_list>]
                [-c <CMMs>] [-s <servers>] [-t <storage_systems>] [-w <switches>]

updatecomp apply  -a power [-c <cmms>] [-s <servers>] [-w <switches>]

Note

You must specify one or more of the following parameters: –c, –s, –t, and –w.

Options

{-h | --help}

Displays the syntax and brief usage information for this command.

{–a | --action} <action>

Specifies the action to take. This can be one of the following values

apply. (default) Applies the associated firmware to the specified device.
The following set of properties must be specified for each device. Each property is separated by a semicolon, and each set of properties is separated by a comma.
- UUID of the storage system
- Fix (firmware-update) ID of the target package to be applied to the component.
- Component name
For example:
```
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA,lnvgy_fw_storage_1.1.1,Controller A
```
applyBundle. Applies firmware updates to all components of specified ThinkSystem SR635 and SR655 servers that are not compliant with the assigned firmware-compliance policy using a bundled image that contain the applicable firmware update packages. The bundled image is created during the update process by collecting all firmware-update packages from the compliance policy.
The UUID of the ThinkSystem SR635 and SR655 server must be specified.
The updates are applied using immediate activation. During the update process, the target device might be automatically restarted multiple times until the entire process is complete. Ensure that you quiesce all applications on the target device before you proceed.
cancelApply. Cancels the firmware update request on the specified device.
The following set of properties must be specified for each device. Each property is separated by a semicolon, and each set of properties is separated by a comma.
- UUID of the storage system
- Fix (firmware-update) ID of the target package to be applied to the component.
- Component name
For example:
```
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA,lnvgy_fw_storage_1.1.1,Controller A
```
power. Performs a power operation on the specified device.
The following set of properties must be specified for each device. Each property is separated by a semicolon, and each set of properties is separated by a comma.
- UUID of the device
- The power state. This can be one of the following values, depending on the type of device:
  - CMM: reset
  - Server: powerOn, powerOff, powerCycleSoft, powerCycleSoftGrace, powerOffHardGrace
  - Switch: powerOn, powerOff, powerCycleSoft
  - Storage: powerOn, powerOff, powerCycleSoft
For example:
```
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA;powerOn,BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB;powerOn
```

{-c | --cmm} <CMMs>

Specifies a set of properties for one or more CMMs.

{-l | --device_list} <device_list>

Specifies a list of devices and components, in the following JSON format.

To obtain the component names and firmware-update IDs, use the updaterepo query method.

Parameters				Required / Optional	Type	Description
DeviceList				Required	Array of objects	List of devices
	CMMList			Optional	Array of objects	List of CMMs
		Components		Required	Array of strings	List of components in the CMM
			Component	Required	String	Component name
			Fixed	Optional	String	Firmware-update ID of the target package to be applied to the component. Specify if this field if the update is not driven by the firmware-compliance policy. Do not specify if the update is driven by the policy.
		UUID		Required	String	UUID of the chassis CMM
	ServerList			Optional	Array of objects	List of servers
		Components		Required	Array of objects	List of components in the server
			Component	Required	String	Component name
			Fixid	Optional	String	Firmware-update ID of the target package to be applied to the component. Specify if this field if the update is not driven by the firmware-compliance policy. Do not specify if the update is driven by the policy.
		UUID		Required	String	UUID of the server
	StorageList			Optional	Array of objects	List of storage devices
		Components		Required	Array of objects	List of components in the storage device
			Component	Required	String	Component name
			Fixid	Optional	String	Firmware-update ID of the target package to be applied to the component. Specify if this field if the update is not driven by the firmware-compliance policy. Do not specify if the update is driven by the policy.
		UUID		Required	String	WWNN of the storage device
	SwitchList			Optional	Array of objects	List of switches
		Components		Required	Array of objects	List of components in the switch
			Component	Required	String	Component name
			Fixid	Optional	String	Firmware-update ID of the target package to be applied to the component. Specify if this field if the update is not driven by the firmware-compliance policy. Do not specify if the update is driven by the policy.
		UUID		Required	String	UUID of the switch

The following example applies firmware updates to multiple devices and components.

{   
   "DeviceList": [{
      "ServerList": [{
         "UUID": "8BFBADCC33CB11E499F740F2E9903640",
         "Components": [{
            "Fixid": "lnvgy_fw_imm2_tcoo17g-3.00_anyos_noarch",
            "Component": "IMM2 (Backup)"
         },
         {
            "Fixid": "lnvgy_fw_imm2_tcoo17g-3.00_anyos_noarch",
            "Component": "IMM2 (Primary)"
         }]
      }]
   },
   {
      "CMMList": [{
         "UUID": "8BFBADCC33CB11E499F740F2E9903640",
         "Components": [{
            "Fixid": "lnvgy_fw_imm2_tcoo17g-3.00_anyos_noarch",
            "Component": "CMM”)"
         }]
      }]
   },
   {
      "SwitchList": [{
         "UUID": "8BFBADCC33CB11E499F740F2E9903640",
         "Components": [{
            "Fixid": "lnvgy_fw_scsw_en4093r-8.3.9.0_anyons_noarch",
            "Component": "Main Application"
         }]
      }]
   },
   {
      "StorageList": [{
         "UUID": "8BFBADCC33CB11E499F740F2E9903640",
         "Components": [{
            "Fixid": "lnvgy_fw_storage_1.1.1",
            "Component": "Controller a"
         }]
      }]
   }]
}

{-m | --mode} <activate_mode>

Indicates when to activate the update. This can be one of the following values.

immediate. (default) During the update process, the target device might be automatically restarted multiple times until the entire process is complete. Ensure that you quiesce all applications on the target device before you proceed.
delayed. The firmware update process starts immediately; however, some but not all update operations are performed. Devices must be restarted to continue the update process. Additional restarts are then performed until the update operation completes. This rule is supported only for servers and rack switches.
For ThinkSystem V4 servers, the applicable update packages are pushed to the server, but the update process does not start until the next time the server is restarted. No additional power actions are performed after the update process is complete. Updating firmware on the backup management controller is not supported.
prioritized. Firmware updates on the baseboard management controller are activated immediately; all other firmware updates are firmware updates are activated the next time the device is restarted. Additional restarts are then performed until the update operation completes. This rule is supported only for servers.
For ThinkSystem V4 servers, firmware updates on the management controller are activated immediately; other firmware updates are pushed to the server, and applied and activated the next time the devices is restarted. XClarity Administrator does not perform additional power actions after the update process on device is complete.
onReset. The applicable update packages are downloaded to the server, but the update process does not start until the next time the server is restarted. Additional restarts are then performed until the update operation completes. No additional power actions are performed after the update process is complete. This option is only supported on ThinkSystem v4 serves. Updating firmware on the backup management controller is not supported.

{-s | --server} <servers>

Specifies a set of properties for one or more servers.

{-t | --storage} <storage_systems>

Specifies a set of properties for one or more storage devices.

{-w | --switch} <switches>

Specifies a set of properties for one or more switches.

{-v | --view} <filter>

Identifies the view to use for the returned data. If a filter is not specified, the default view is used.

You can also create custom views (see Creating custom views).

Examples

The following example applies a firmware update on a storage device and immediate activates the update.

connect --url https://192.0.2.0 --user ADMIN --noverify
updatecomp apply -a apply -m immediate -t AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA;lnvgy_fw_storage_1.1.1;Controller A

The following example applies bundled firmware updates to a ThinkSystem SR635 or SR655 server and immediate activates the update.

connect --url https://192.0.2.0 --user ADMIN --noverify
updatecomp apply -a applyBundle -s AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

The following example powers off a server and a storage system.

connect --url https://192.0.2.0 --user ADMIN --noverify
updatecomp apply -a power –s AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA;powerOff –t BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB;powerOff

Give documentation feedback

updatecomp apply

Syntax​

Options​

Examples​

Related links​

Syntax

Options

Examples

Related links