Linux rpm return codes, Vmware esxi smart-component return codes, Input files – HP Smart Update Manager Version 6.0.0 User Manual
Page 48
Meaning
Return code
The installer cannot run because of an un-met dependency
or installation tool failure.
6
The actual installation operation (not the installation tool)
failed.
7
Linux RPM return codes
Meaning
Return code
The Linux RPM installation was successful.
0
The Linux RPM installation failed.
1
VMware ESXi smart-component return codes
Meaning
Return code
The installation of the deliverable was successful. No reboot
is required.
0
The installation of the deliverable was successful. Reboot
is required for the deliverable to be enabled.
1
The installation was not attempted because the version to
be installed matches the version already installed.
2
The installation was not attempted because of one of the
following:
3
•
The version to be installed is older than the version
already installed.
•
The supported hardware is not present, not enabled,
or in a state that an installation could not be attempted.
•
The smart component does not support the environment.
•
There is nothing for the component to accomplish.
If the component is being installed to a remote node, such
as an OA or other network-based deployment, this return
code indicates that the node cannot be found.
4
A user canceled the installation before anything could be
installed.
5
The installer cannot run because of an un-met dependency
or installation tool failure.
6
The actual installation operation (not the installation tool)
failed.
7
Input files
HP SUM provides the ability to script the update of multiple, individual nodes or groups of nodes
(HP ProLiant and Integrity servers and options) within a single operation through the input file
functionality. To protect your credentials, use a secure server or a management console.
To create an input file, use a text editor. All section headers and trailers must match. Failure to use
the option causes the GUI mode to be used, but the information provided enables you to skip
screens where information has already been provided. You can use the DRYRUN=YES option to
perform dry runs of installations to ensure the scripts are working without deploying the firmware
updates that might be required on each node. Remove the DRYRUN=YES option to perform the
updates.
48
Using legacy scripts to deploy updates