HP ProLiant ML10 HP Smart Update Manager 6.0.0 User Guide - Page 48
Linux RPM return codes, VMware ESXi smart-component return codes, Input files
View all HP ProLiant ML10 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 48 highlights
Return code 6 7 Linux RPM return codes Meaning The installer cannot run because of an un-met dependency or installation tool failure. The actual installation operation (not the installation tool) failed. Return code 0 1 Meaning The Linux RPM installation was successful. The Linux RPM installation failed. VMware ESXi smart-component return codes Return code 0 1 2 3 4 5 6 7 Meaning The installation of the deliverable was successful. No reboot is required. The installation of the deliverable was successful. Reboot is required for the deliverable to be enabled. 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 node, such as an OA or other network-based deployment, this return code indicates that the node 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. 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