Linux Rpm Return Codes; Input Files - HP ProLiant DL320e User Manual

Error level
2
3
4
5
6
7

Linux RPM return codes

Error level
0
1

Input files

HP SUM provides the ability to script the update of multiple, individual targets or groups of targets
(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 SILENT=YES 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 target. Remove the DRYRUN=YES option to
perform the updates.
For parameters that can take list values, list separators can be commas, semicolons, or spaces.
NOTE: The credentials can be omitted from the file for greater security and passed on the
command line to HP SUM. The only limitation that the user ID and credentials must be the same
on all.
When the file has been created, to use it with HP SUM, add it as the inputfile <filename>
parameter to a HP SUM command line. For example, if the name of the input file is hpsum.in,
the command-line syntax is hpsum -inputfile hpsum.in. Full paths can be added to the
input file location if the file is not stored in the same location as the HP SUM executables. The
<filename> field can be enclosed in double quotes to enable paths with spaces. Also, the input
file itself might contain the same options on the command line. The usual command-line options
can still be used with the -inputfile option and they take precedence over any given input file.
Meaning
The installation was not attempted because the version to
be installed matches the version already installed.
The installation was not attempted because of one of the
following:
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 target, such
as an OA or other network-based deployment, this return
code indicates that the target cannot be found.
A user canceled the installation before anything could be
installed.
The installer cannot run because of an un-met dependency
or installation tool failure.
The actual installation operation (not the installation tool)
failed.
Meaning
The Linux RPM installation was successful.
The Linux RPM installation failed.
Input files 43