SOLVED
Hi Chang Che-Lun,
You can use 'upgradesys' for upgrade related operations.
From CLI guide >>>
SYNTAX (HIDDEN)
upgradesys [options] [staged_kit]
OPTIONS (HIDDEN)
-abort
Aborts the upgrade when all nodes are at the old version, or if the
upgrade never reached the point of rebooting nodes.
-auto [<kitpackage>]
Performs an online upgrade with minimal manual intervention; after first
running with either the name of a previously staged Upgrade Tool kit or
the path to a package file, repeat with just -auto until the upgrade is
complete. The -allow_singlepathhost option is disallowed with this
option in order to prevent ignoring temporarily single path hosts that
are expected to still have multiple paths. This option is only used for
full packages.
-checkrunadmithw <staged_kit>
Checks if admithw should be run after the specified upgrade completes.
Returns 1 if admithw should be run, 0 if not.
-checksignature <kit>
Verifies the signature of the signed package contained within the kit.
-cleanup
Returns system to normal running state at the conclusion of an upgrade.
-continue [<node>]
Verify that it is safe to reboot a node to the new version, reboot that
node, and verify that it has rebooted. If no node is specified, one is
automatically chosen; this is the recommended method. Keep specifying
this option with a given node until the command indicates that the
system is ready to proceed with another node. Note that because the
system starts an internal timer after requesting a node reboot command,
this command should be re-issued shortly after requesting a node reboot.
See -resettimer if a timeout does occur.
-d
Display detailed output. Only valid with -status.
-f
Do not prompt for confirmation. Also indicates to proceed with an
upgrade even if warnings are encountered.
-finish
After all nodes have been rebooted and the system has validated that the
system is in a good state to proceed, this enters the new userspace
running with the new version.
-full
Displays detailed kit information for currently staged kits. Only valid
when following -liststaged.
-getproperty <staged_kit>
Returns the property information from the specified staged kit.
-getresults [<locale>]
Retrieve the structured log of the most recent upgrade with an optional
two-character international code specifying the locale. The default
locale is English.
-info <kitpackage>
Given the name of a previously staged kit or path to a legacy package,
describes its contents.
-liststaged [<filespec>]
Lists available upgrade kits in the staging folder on the storage
system. An optional file specification in glob format may be passed to
constrain the listing, or one of the following special keywords:
FULL = List all uninstalled OS packages
UPDATE = List all uninstalled updates.
-kitname <staged_kit>
Used only with -getresults or -postcheck. For -getresults, selects the
structured log data corresponding to the upgrade of the given kit,
rather than the most recent one performed overall. For -postcheck, this
is the kitname of the most recent upgrade.
-load <kitpackage>
Given the name of a previously staged Upgrade Tool kit or path to a
package, prepares the system for the upgrade or installs the patch. If
-offline is specified with a full OS kit or package, the cluster reboots
as part of this command. This option is only used for full OS kits or
packages.
-offline
Performs an offline upgrade. The default is to do an online upgrade.
-policycheck
Returns a summary of the number of kits staged by type and the maximum
allowable number of kits that can be staged by type.
-postcheck
This runs check scripts after an upgrade. It requires the kitname of the
most recent upgrade to be specified via the -kitname option.
-postupgrade
After all nodes have rebooted and -finish has been run, this command
completes the upgrade.
-resettimer
Resets the timer related to node reboot requests. This option is useful
if the timer associated with the -continue option expires.
-resume <staged_kit>
Resumes a previously failed patch update.
-revert
Removes the most recent patch, or reboots to the previous full install.
-revertnode <node_number>
Reboots a node to the old version. Used when aborting an online upgrade
already in progress.
-revertversion
Describes the resulting version upon successful execution of the -revert
command.
-stage <kitpath>
Copies the specified upgrade kit to the staging folder on the storage
system.
-status
Describes the current online upgrade status.
-unstage <staged_kit>
Removes the specified previously staged kit from the staging folder on
the storage system.
-workarounds <workarounds_list>|all
Provides a list of workarounds approved by the user to be run during the
upgrade. The list is a comma-separated list of workaround codes, or the
keyword "all", which indicates all workarounds. This is only valid with
the -auto or -load options, or if a kit is specified.
Regards,
Veeyaarvi
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Hi Chang Che-Lun,
Array gets image directly from DSCC; manual upgrade using CLI is not available for customers. Image also not available for download publically.
Regards,
Veeyaarvi
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]