HP Smart Update Manager CLI Help Version 6.0 Copyright (c) 2009, 2013 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgments Microsoft(R), Windows(R), Windows(R) XP, and Windows NT(R) are U.S. registered trademarks of Microsoft Corporation. September 2013 Abstract This document describes how to use HP SUM to apply firmware updates to HP ProLiant and HP Integrity servers, and apply software updates to HP ProLiant servers. This document is intended for individuals who understand the configuration and operations of Microsoft Windows, Windows Server, Linux, smart components, HP-UX, VMware, and the risk of data loss from performing updates. ---------------------------------------------------------------------- Chapter 1 Using legacy scripts to deploy updates 1.1 Command-line interface You can use the HP SUM command-line interface to script custom installations. For more information on using HP SUM, see the HP Smart Update Manager User's Guide HP SUM documentation website at http://www.hp.com/go/hpsum/documentation. 1.1.1 Command-line syntax The general command-line syntax for HP SUM is as follows: hpsum [/h] [/f]:bundle] [/r[eboot] HP SUM with OA requires a user ID and password to log in. The user ID must be an administrator equivalent ID and not an operator or user equivalent level ID. On Windows, use a slash before each argument. On Linux, use a hyphen before each argument. If the /s[ilent] argument is not included on the command line, the HP SUM GUI appears. [Note] Note: Command-line syntax does not support double-byte character sets. Any messages entered through the command line via a double-byte character set will not be displayed correctly. 1.1.1.1 Using Linux root credentials If you run HP SUM from a Linux system where you have not logged in to the system as a root user, you can still update nodes from the CLI/Input file if you use Access level options sudo or super user. 1.1.1.1.1 Prerequisites for using Linux root credentials If you have run HP SUM as a root user, remove the temp directory created by HP SUM.Make sure you have read/write access permissions to the /tmp and /var directories.If you create a sudo user, make sure that you add that user to the /etc/sudoers file. The following table shows the privileges and specifications for users.UserPrivilegeSpecificationRootALL= (ALL)ALLSudo_userALL= (ALL)ALLEdit the entry in the /etc/sudoers file so the system asks for the sudo user password instead of root user password when you run the sudo command.The following table shows the privileges to comment or remove from /etc/sudoers.UserPrivilegeSpecificationAllALL= (ALL)ALLThis often occurs in SUSE Linux systems.#Defaults targetpw # ask for the password of the target user. For example,Only use this option with Defaults targetpw.To use super user functionality, configure the user as a super user with all root privileges. You can also use non-root user with a root user to update components. o If you have run HP SUM as a root user, remove the temp directory created by HP SUM. o Make sure you have read/write access permissions to the /tmp and /var directories. o If you create a sudo user, make sure that you add that user to the /etc/sudoers file. The following table shows the privileges and specifications for users. +----------------------------------------+ | User | Privilege | Specification | |-----------+------------+---------------| | Root | ALL= (ALL) | ALL | |-----------+------------+---------------| | Sudo_user | ALL= (ALL) | ALL | +----------------------------------------+ o Edit the entry in the /etc/sudoers file so the system asks for the sudo user password instead of root user password when you run the sudo command. The following table shows the privileges to comment or remove from /etc/sudoers. +-----------------------------------+ | User | Privilege | Specification | |------+------------+---------------| | All | ALL= (ALL) | ALL | +-----------------------------------+ This often occurs in SUSE Linux systems. #Defaults targetpw # ask for the password of the target user. For example, [Warning] Warning! Only use this option with Defaults targetpw. o To use super user functionality, configure the user as a super user with all root privileges. You can also use non-root user with a root user to update components. 1.1.1.2 Switch update commands G7 and earlier servers do not support AMS agents. The following tables show what updates occur when you use the switch agent commands. [Note] Note: To find out if you have any switches installed, use HP SUM to create the Firmware Details Report. The following table shows what updates occur if no switches are currently installed. +------------------------------------------------------------------------+ | Command | G7 and earlier | Gen8 servers | | | servers | | |---------------------------+----------------------+---------------------| | no switches | SNMP | AMS | |---------------------------+----------------------+---------------------| | /no_mgmt | Nothing | Nothing | |---------------------------+----------------------+---------------------| | /use_ams | SNMP | AMS | |---------------------------+----------------------+---------------------| | /use_snmp | SNMP | SNMP | |---------------------------+----------------------+---------------------| | /use_wmi | SNMP and WBEM | WBEM | |---------------------------+----------------------+---------------------| | /use_ams /use_snmp | SNMP | AMS and SNMP | |---------------------------+----------------------+---------------------| | /use_ams /use_wmi | SNMP and WBEM | AMS and WBEM | |---------------------------+----------------------+---------------------| | /use_wmi /use_snmp | WBEM and SNMP | WBEM and SNMP | |---------------------------+----------------------+---------------------| | /use_ams /use_wmi | WBEM and SNMP | AMS, SNMP, and WBEM | | /use_snmp | | | +------------------------------------------------------------------------+ [Note] Note: G7 and earlier servers do not support AMS. 1.1.2 Command-line arguments HP SUM recognizes the following command-line arguments. If you specify the node and credentials, use the /s[ilent] parameter to proceed with the installation. You cannot use some arguments, such as /romonly and /softwareonly, together. +---------------------------------------------------------+ | Help | Description | |---------------+-----------------------------------------| | /h[elp] or /? | Displays command line help information. | +---------------------------------------------------------+ +------------------------------------------------------------------------+ | Installation options | Description | |---------------------------------------+--------------------------------| | | Overrides or downgrades an | | | existing component | | /f[orce] | installation. This produces | | | the same results as | | | /f:software. | |---------------------------------------+--------------------------------| | | Overrides or downgrades the | | /f[orce]:bundle | existing installation of | | | components in the selected | | | bundle. | |---------------------------------------+--------------------------------| | | Overrides or downgrades the | | /f[orce]:rom | existing installation of the | | | selected firmware components | | | (applies to firmware only). | |---------------------------------------+--------------------------------| | | Overrides or downgrades the | | /f[orce]:software | existing installation of the | | | selected software components. | |---------------------------------------+--------------------------------| | | Overrides or downgrades the | | | existing installation of the | | /f[orce]:all | selected software components, | | | firmware components, and | | | bundles. | |---------------------------------------+--------------------------------| | | Downgrades to an earlier | | | version of firmware for | | /g or /downgrade | multi-node devices such as | | | hard drives and array | | | controllers (applies to | | | firmware only). | |---------------------------------------+--------------------------------| | | Rewrites the current version | | | of firmware for multi-node | | /e or /rewrite | devices such as hard drives | | | and array controllers (applies | | | to firmware only). | |---------------------------------------+--------------------------------| | /gui | Starts a GUI session of HP | | | SUM. | |---------------------------------------+--------------------------------| | /offline_automatic | Runs an HP SUM update | | | automatically in offline mode. | |---------------------------------------+--------------------------------| | /offline_interactive | Runs an HP SUM update in | | | interactive (GUI) mode. | |---------------------------------------+--------------------------------| | | Causes the installation to run | | | silently with no GUI output. | | | All data writes to the log | | | file. Any generated prompts | | | use the default option and | | | continue the installation | | | without user input. If a | | | component requires input | | | before installation (such as | | /s[ilent] | configuration information), | | | the component installation | | | fails, and an error message | | | writes to the log file. | | | | | | Failed dependencies are not | | | reported to the user when you | | | are using the /s[ilent] | | | argument. To check for failed | | | dependencies, run HP SUM in | | | GUI mode.. | |---------------------------------------+--------------------------------| | | Specifies which components to | | | install. Components to install | | | can be specified with or | | | without the /c[omponent] | | | argument. | | | | | | If you are using the | | | /c[omponent] argument, then | | | only one component can | | | specified with the argument. | | | However, multiple /c arguments | | | and components can be | | | specified on the same line.If | | | you do not use the | | | /c[omponent] argument, | | | multiple components can be | | | specified at the same time, | | | but the components must be | | | separated by a blank and | | | listed after all the arguments | | | on the command line.The | | | components are installed in | | | the order provided unless | | | dependencies between | | | components require | | | installation in a different | | | order. If so, the utility | | | changes the installation order | | | based on the component | | | dependencies to ensure the | | | successful installation of as | | | many components as | | | possible.Multiple components | | | and bundles can be specified | | | on the same command line. When | | | you are mixing components and | | | bundles on the command line, | | | the filter switches control | | | what components and bundles | | | are installed.HP SUM only uses | | | the component name. If you | | | type the entire directory | | | path, HP SUM will ignore the | | | path. If you use /use_location | | | and /c, HP SUM checks both the | | | default repository and the | | | directory provided. | | | o If you are using the | | | /c[omponent] argument, | | /c[omponent]<component_to_install> or | then only one component | | <component1_to_install> | can specified with the | | <component2_to_install> | argument. However, | | | multiple /c arguments and | | | components can be | | | specified on the same | | | line. | | | | | | o If you do not use the | | | /c[omponent] argument, | | | multiple components can be | | | specified at the same | | | time, but the components | | | must be separated by a | | | blank and listed after all | | | the arguments on the | | | command line. | | | | | | o The components are | | | installed in the order | | | provided unless | | | dependencies between | | | components require | | | installation in a | | | different order. If so, | | | the utility changes the | | | installation order based | | | on the component | | | dependencies to ensure the | | | successful installation of | | | as many components as | | | possible. | | | | | | o Multiple components and | | | bundles can be specified | | | on the same command line. | | | When you are mixing | | | components and bundles on | | | the command line, the | | | filter switches control | | | what components and | | | bundles are installed. | | | | | | o HP SUM only uses the | | | component name. If you | | | type the entire directory | | | path, HP SUM will ignore | | | the path. If you use | | | /use_location and /c, HP | | | SUM checks both the | | | default repository and the | | | directory provided. | |---------------------------------------+--------------------------------| | | This argument specifies an | | /group "group_name" | already defined group name in | | | the HP SUM GUI. | |---------------------------------------+--------------------------------| | | This argument specifies | | | bundles to install. Bundles to | | | install can be specified with | | | or without the /b[undle] | | | argument. | | | | | | If you are using the /b[undle] | | | argument, only one bundle can | | | specified with the argument. | | | However, multiple /b arguments | | | and bundles can be specified | | | on the same line.If you do not | | | use the /b[undle] argument, | | | multiple bundles can be | | | specified at the same time, | | | but the bundles must be | | | separated by a blank and | | /b[undle] <bundle_to_install> or | listed after all the arguments | | <bundle1_to_install> | on the command line. | | <bu/use_latestndle2_to_install> | o If you are using the | | | /b[undle] argument, only | | | one bundle can specified | | | with the argument. | | | However, multiple /b | | | arguments and bundles can | | | be specified on the same | | | line. | | | | | | o If you do not use the | | | /b[undle] argument, | | | multiple bundles can be | | | specified at the same | | | time, but the bundles must | | | be separated by a blank | | | and listed after all the | | | arguments on the command | | | line. | |---------------------------------------+--------------------------------| | | This argument is a filter | | | switch. It enables you to | | | install newer versions of | | | components defined in a PSP, | | | ISP, or firmware bundle. | | /allow_update_to_bundle | | | | This argument enables these | | | components to replace the | | | older versions of the same | | | component that might have | | | shipped with the bundles. | |---------------------------------------+--------------------------------| | | This argument is a filter | | | switch. It enables you to | | /allow_non_bundle_components | install components that are | | | not included in the bundle but | | | reside in the directory with | | | the components in the bundle. | |---------------------------------------+--------------------------------| | | This argument is a filter | | | switch for use with bundles. | | | The argument enables the | | | latest version of the bundle | | | to be used when multiple | | | versions of bundles are listed | | /use_latest | on the command line. If there | | | are no bundles specified on | | | the command line, and multiple | | | bundles are in the directory, | | | the /use_latest argument | | | allows HP SUM to use the | | | bundle that has the latest | | | version for installation. | |---------------------------------------+--------------------------------| | | Specifies a directory or file | | | share that contains the SPP, | | | HP Integrity Smart Update | | | Firmware Bundles, and | | | components for use with HP | | | SUM. The file_share format | | | must be a mapped file share or | | | UNC format. If this argument | | | is not specified, the | | | directory that contains | | | hpsum.exe or HP SUM is used by | | /use_location "file_share" | default. | | | | | | The logged-in account must | | | have access to this location. | | | | | | The /user and /passwd | | | arguments do not have any | | | effect when you are attempting | | | to access the file share. Use | | | those arguments only when you | | | are connecting to a node | | | system. | |---------------------------------------+--------------------------------| | | Selects Download from hp.com | | | on the Add Baseline screen. | | /use_web | This enables HP SUM to | | | download updates from | | | ftp.hp.com. | |---------------------------------------+--------------------------------| | | Enables the inclusion of a | | | proxy server (and port number) | | | to access ftp.hp.com. This | | /use_proxy <Proxy server> | parameter must be used with | | | /use_web. For example, | | | /use_web /use_proxy | | | <1.22.33.44:80>. | |---------------------------------------+--------------------------------| | | Enables the inclusion of a | | | proxy script to access | | /proxy_script <Proxy script> | ftp.hp.com. This parameter | | | must be used with /use_web. | | | For example, /use_web | | | /proxy_script <autoproxy.com>. | |---------------------------------------+--------------------------------| | | Sets the password to be used | | /proxy_password <password> | for an authenticating proxy | | | server. | |---------------------------------------+--------------------------------| | | Specifies that the check box | | | for Use last downloaded | | | repository from ftp.hp.com on | | | the Source Selection screen in | | /use_d[ownloaded] | the GUI is selected. This | | | enables the previously | | | downloaded components to be | | | included in the list of | | | possible updates. | |---------------------------------------+--------------------------------| | | Specifies that AMS, SNMP, and | | | WBEM Providers management | | | components are optional on the | | /no_mgmt | Components Selection screen. | | | In silent mode, HP SUM will | | | not update any management | | | components. | |---------------------------------------+--------------------------------| | | Specifies that components that | | | use SNMP protocol and the AMS | | | components are available for | | /use_snmp | installation by default. When | | | the /use_snmp argument is | | | used, the AMS components are | | | required, but the WMI | | | components are optional. | |---------------------------------------+--------------------------------| | | Specifies that components that | | | use the WMI protocol are | | | available for installation. | | | These components are optional | | | and are not installed unless | | | this argument is used. When | | /use_wmi | the /use_wmi argument is used, | | | and the /use_snmp & /use_ams | | | arguments are not, the SNMP | | | and AMS components are | | | optional. This argument does | | | not apply to HP Integrity | | | servers. | |---------------------------------------+--------------------------------| | | Specifies which AMS components | | | can be installed along with | | | SNMP components. The AMS and | | | SNMP components are available | | /use_ams | to select by default. When the | | | /use_ams argument is used, the | | | SNMP components are required, | | | and the WMI components are | | | optional. | |---------------------------------------+--------------------------------| | | This filter switch allows you | | | to see only the firmware | | | components needed for | | | installation. When you are | | | using this filter switch, you | | | must exit and restart HP SUM | | /romonly | if you want to return to an | | | unfiltered state. | | | | | | Do not use the /romonly | | | argument with the | | | /softwareonly argument. | | | (Applies to firmware only.) | |---------------------------------------+--------------------------------| | | This filter switch allows you | | | to see only the software | | | components needed for | | | installation. When you are | | | using this filter switch, you | | /softwareonly | must exit and restart HP SUM | | | if you want to return to an | | | unfiltered state. | | | | | | Do not use the /softwareonly | | | argument with the /romonly | | | argument. | |---------------------------------------+--------------------------------| | | HP SUM 6.x does not support | | | /express command. If you | | /express | scripts contain this command, | | | HP SUM will execute this | | | command the same way it runs | | | /silent. | +------------------------------------------------------------------------+ +------------------------------------------------------------------------+ | Overriding errors | Description | |-------------------------------+----------------------------------------| | | Specifies that if a TPM is enabled, | | | the warning message should be ignored | | /tpmbypass or /ignore_tpm | and component installation can | | | continue. For more information about | | | TPM, see the HP Smart Update Manager | | | User Guide. | |-------------------------------+----------------------------------------| | | Allows the installation to proceed on | | /ignore_warnings | a Superdome 2 node even when warnings | | | are returned during analysis. | |-------------------------------+----------------------------------------| | | Causes the installation to continue | | | and ignore errors. Valid values are as | | | follows: | | | | | | * <error>=ServerNotFound and | | | | | | * <error>=BadPassword. | | /continue_on_error <error> | | | | * <error>=FailedDependencies | | | | | | You can use the ServerNotFound option | | | to bypass inactive or unavailable | | | remote hosts when you are deploying | | | firmware or software to multiple | | | remote hosts at the same time. | |-------------------------------+----------------------------------------| | | Defines the behavior when a remote | | | node has an existing HP SUM session in | | /override_existing_connection | progress. It overrides the session in | | | progress and re-initializes the | | | installation framework on the remote | | | host. | |-------------------------------+----------------------------------------| | | Provides HP SUM <parameter> the | | | information on how to proceed when a | | | component has a failed dependency. The | | | supported parameters for this argument | | | are OmitHost (default), OmitComponent | | /On_failed_dependency: | , and Force. OmitHost causes the host | | <parameter> | to be put into a failure state, and no | | | installation is attempted. | | | OmitComponent deselects the affected | | | components and proceeds with any | | | updates that do not have dependency | | | failures. Force attempts all updates, | | | even if they have dependency failures. | +------------------------------------------------------------------------+ +------------------------------------------------------------------------+ | Reboot options | Description | |-------------------------+----------------------------------------------| | | If the following conditions are met, this | | | argument causes the server (or host server | | | in a remote installation) to reboot: | | | | | | The /reboot option is selected or given as a | | | command-line argument.All components | | | selected for installation are successfully | | | installed.At least one of the installed | | | components requires a reboot to complete its | | /r[eboot] | installation. | | | o The /reboot option is selected or given | | | as a command-line argument. | | | | | | o All components selected for installation | | | are successfully installed. | | | | | | o At least one of the installed components | | | requires a reboot to complete its | | | installation. | |-------------------------+----------------------------------------------| | | Displays the specified reboot message on | | /reboot_message "reboot | remote consoles connected to the server that | | message" | you want to reboot. You must use this | | | argument with the /reboot option, or the | | | argument is ignored. | |-------------------------+----------------------------------------------| | | Delays the reboot of the server for the | | | length of time that the timeout_in_seconds | | | variable specifies. You must use this | | | argument with the /reboot option, or the | | | argument is ignored. Acceptable values are | | | between 15 and 3600. | | | | | | The default timeout value is 15 seconds for | | | Microsoft Windows operating systems and 60 | | | seconds for Linux.For Linux, the reboot | | /reboot_delay | delay time is converted from seconds to | | timeout_in_secs | minutes, and any value under a full minute | | | (59 seconds or less) rounds to the next | | | minute. | | | o The default timeout value is 15 seconds | | | for Microsoft Windows operating systems | | | and 60 seconds for Linux. | | | | | | o For Linux, the reboot delay time is | | | converted from seconds to minutes, and | | | any value under a full minute (59 | | | seconds or less) rounds to the next | | | minute. | |-------------------------+----------------------------------------------| | | If the following conditions are met, this | | | argument forces the server to reboot:The | | | /reboot_always option is selected or given | | | as a command-line argument.All components | | | selected for installation are successfully | | | installed. | | | | | /reboot_always | If the following conditions are met, this | | | argument forces the server to reboot: | | | | | | o The /reboot_always option is selected or | | | given as a command-line argument. | | | | | | o All components selected for installation | | | are successfully installed. | +------------------------------------------------------------------------+ +---------------------------------------------------------------+ | Simulating HP SUM | Description | |-------------------+-------------------------------------------| | /dryrun | HP SUM 6.0 does not support this command. | +---------------------------------------------------------------+ +------------------------------------------------------------------------+ | Nodes | Description | |----------------------+-------------------------------------------------| | | Use this argument to log in to the remote nodes | | | by using the user ID. For the OA node, use the | | /user<username> or | /oa_username argument. | | /username <username> | | | | The user name needs to belong to the root or | | | administrator group. | |----------------------+-------------------------------------------------| | /password <password> | Use this argument to use this password for the | | | user ID specified in the /user parameter | | HP SUM also supports | (except for the OA node). The password is used | | passwd and pwd | to log in to remote nodes. For the OA node, use | | | the /oa_password argument. | |----------------------+-------------------------------------------------| | | Use root (super user) username to start a | | | session, and inventory and update components | | | when the credentials specified in /username and | | | /passwd do not have root privileges to update | | | components. | | | | | /su_username | /su_username cannot be used with /use_sudo | | | access level. | | | | | | [Note] Note: | | | Specifying /targettype linux reduces | | | inventory time for deployments. This is | | | an optional command line argument. | |----------------------+-------------------------------------------------| | | Use root (super user) password to start a | | | session, and inventory and update components | | | when the credentials specified in /username and | | | /passwd do not have root privileges to update | | | components. | | | | | /su_password | /su_password cannot be used with /use_sudo | | | access level. | | | | | | [Note] Note: | | | Specifying /targettype linux reduces | | | inventory time for deployments. This is | | | an optional command line argument. | |----------------------+-------------------------------------------------| | | Specifies that username and passwd are sudo | | | user credentials. | | | | | | When you specify /use_sudo in the CLI along | | | with username and passwd, then username and | | | passwd are considered as sudo credentials. | | /use_sudo | | | | /use_sudo cannot be used with /su_username and | | | /su_password access level. | | | | | | [Note] Note: | | | Specifying /targettype linux reduces | | | inventory time for deployments. This is | | | an optional command line argument. | |----------------------+-------------------------------------------------| | | This is the IP address or the DNS name of a | | | remote host, which can be a remote server, | | | remote iLO NIC port, Virtual Connect Ethernet | | | or Fibre Channel Module for c-Class | | /target "netAddress" | BladeSystem, or BladeSystem OA. | | | | | | When two OAs are in an enclosure, this argument | | | should be the active OA. When specifying the IP | | | address, use either the IPv4 or IPv6 format. | |----------------------+-------------------------------------------------| | | Reduces inventory time for scripted | | | deployments. This is an optional command line | | | argument. | | | | | | The following are valid node types: | | | | | | ServerWindowsLinuxHPUXEVA or Command View for | | | EVAFC Switch or Fibre Channel SwitchOA or | | | Onboard AdministratorSUPERDOME 2 or SUPERDOME2 | | | or Superdome 2 Onboard AdministratoriLOVC or | | | Virtual ConnectHP SAS or HP SAS B/L | | | Interconnect SwitchVMware or VMware HostiPDU or | | | Intelligent Power Distribution Unit (iPDU) | | | o Server | | | | | | o Windows | | | | | | o Linux | | | | | | o HPUX | | | | | | o EVA or Command View for EVA | | | | | | o FC Switch or Fibre Channel Switch | | | | | /targettype "type" | o OA or Onboard Administrator | | | | | | o SUPERDOME 2 or SUPERDOME2 or Superdome 2 | | | Onboard Administrator | | | | | | o iLO | | | | | | o VC or Virtual Connect | | | | | | o HP SAS or HP SAS B/L Interconnect Switch | | | | | | o VMware or VMware Host | | | | | | o iPDU or Intelligent Power Distribution Unit | | | (iPDU) | | | | | | Use /targettype with /target parameter. You can | | | interchange the sequence of /targettype and | | | /target. If the node name includes spaces, make | | | sure you enclose the name in quotation marks, " | | | ". | | | | | | [Note] Note: | | | /targettype is an optional command line | | | argument. Use /targettype and /target | | | together. | |----------------------+-------------------------------------------------| | | Enables the credential of the local host to be | | | used as the credential to access the nodes | | /current_credential | instead of providing the user name and password | | | explicitly for each node. The assumption is | | | that the current credential is valid for the | | | nodes being accessed. (Applies to Windows only) | |----------------------+-------------------------------------------------| | | This argument provides the user name credential | | | for OA associated with VC specified with the | | | target command-line parameter. Only one set of | | | OA credentials can be specified with | | | command-line parameters. You can add multiple | | | VC nodes to command-line parameters with the | | | target parameter only if the credentials of OAs | | | associated with specified VCs are the same. The | | /oa_username | argument oa_username is not required if VC has | | | the same credentials as the associated OA. You | | | do not need to provide an OA network address | | | associated with VC. HP SUM queries it from a | | | specified VC node. | | | | | | To update multiple VCs with different user | | | names and passwords, or VCs with OAs that have | | | different credentials, use the corresponding | | | input files OAUID and OAPWD. | |----------------------+-------------------------------------------------| | | Provides the password credential for OA | | | associated with VC specified with the "node" | | | command-line parameter. Only one set of OA | | | credentials can be specified with command-line | | | parameters. You can add multiple VC nodes to | | | command-line parameters with the "node" | | | parameter only if the credentials of OAs | | | associated with specified VCs are the same. The | | /oa_password | argument oa_password is not required if VC has | | | the same credentials as the associated OA. You | | | do not need to provide an OA network address | | | associated with VC. HP SUM queries it from a | | | specified VC node. | | | | | | To update multiple VCs with different user | | | names and passwords, or VCs with OAs that have | | | different credentials, use the corresponding | | | input files OAUID and OAPWD . | +------------------------------------------------------------------------+ +------------------------------------------------------------------------+ | Log files | Description | |----------------+-------------------------------------------------------| | | Redirects the output from HP SUM or the HP | | | BladeSystem c-Class OA flash utility to a different | | | directory than the default location. | | | | | | For Windows components, the default location is | | | %SYSTEMDRIVE%\CPQSYSTEM\hp\log<netAddress> and the | | | redirected location is <path>\hp\log\<netAddress>.For | | | Linux components, the default location is | | /logdir "path" | /var/hp/log/<netAddress> and the redirected location | | | is <path>/hp/log/<netAddress>. | | | o For Windows components, the default location is | | | %SYSTEMDRIVE%\CPQSYSTEM\hp\log<netAddress> and | | | the redirected location is | | | <path>\hp\log\<netAddress>. | | | | | | o For Linux components, the default location is | | | /var/hp/log/<netAddress> and the redirected | | | location is <path>/hp/log/<netAddress>. | |----------------+-------------------------------------------------------| | | Sets the verbosity level for the HP SUM execution log | | /v[erbose] or | file, hpsum_execution_log_<date>_<time>.log. It | | /veryv[erbose] | increases the level of detail that is retained in the | | | log file. The default value is normal verbosity. | +------------------------------------------------------------------------+ +------------------------------------------------------------------------+ | Generating reports | Description | |--------------------+---------------------------------------------------| | | Generates a report listing of the node summary | | | and describes how the components in the | | | repository affect the node; for example, whether | | | each component applies to the node. The report is | | | generated in HTML and XML with file name formats | | | of HPSUM_Report_<date>_<time>.html and | | /report | HPSUM_Report_<date>_<time>.xml. | | | | | | By default, the files are located in the present | | | working directory where HP SUM is initiated. If | | | that location is write-protected, you can find | | | the files in the same directory as the HP SUM log | | | files. | |--------------------+---------------------------------------------------| | | Generates a report listing of the components in | | | the specified repository. The report is generated | | | in HTML and XML with file name formats of | | | HPSUM_Inventory_Report_<date>_<time>.html and | | | HPSUM_Inventory_Report_<date>_<time>.xml. | | /inventory_report | | | | By default, the report is located in the present | | | working directory where HP SUM is initiated. If | | | that location is write-protected, you can find | | | the report in the same directory as the HP SUM | | | log files. | |--------------------+---------------------------------------------------| | | Generates a report listing of the firmware | | | installed and details of the node. The report is | | | generated in HTML and XML with file names of | | | HPSUM_Firmware_Report.html and fwreport.xml in | | | the directory named | | /firmware_report | HPSUM_Firmware_Report_<date>_<time>. | | | | | | By default, the report is located in the present | | | working directory where HP SUM is initiated. If | | | that location is write-protected, you can find | | | the report in the same directory as the HP SUM | | | log files. | |--------------------+---------------------------------------------------| | /dependency_report | Generates a report listing of the failed | | | dependencies for all nodes. | |--------------------+---------------------------------------------------| | | Generates a report that lists all installed | | /installed_report | firmware, software, and driver versions installed | | | on all nodes. | +------------------------------------------------------------------------+ [Note] : HP SUM does not install any updates when you generate a report. +------------------------------------------------------------------------+ | Using input files | Description | |-----------------------+------------------------------------------------| | | Enables you to script the deployment of | | /inputfile "filename" | firmware and software to multiple remote | | | systems at one time. For more information, see | | | the HP Smart Update Manager User Guide. | |-----------------------+------------------------------------------------| | /deleteinputfile | Enables you to instruct HP SUM to delete the | | | input file after it has been read. | +------------------------------------------------------------------------+ +------------------------------------------------------------------------+ | Superdome 2 server | Description | | commands | | |----------------------+-------------------------------------------------| | | Determines which Superdome 2 firmware is | | | updated. You can choose ALL, COMPLEX, or | | /update_type <type> | PARTITIONS. The default selection is ALL. | | | | | | Example: /update_type PARTITIONS | |----------------------+-------------------------------------------------| | | Use this argument when the /update_type | | | argument is PARTITIONS. This argument specifies | | | the subset of partitions or unassigned blades | | | to update when you do not want to update all | | /device_list | partitions or unassigned blades. Valid devices | | <device[,device]...> | are: npar(number) and blade(enc)/(bay). Do not | | | put any spaces between the parameters. | | | | | | Example: /device_list | | | npar1,npar2,blade1/1,blade1/2 | |----------------------+-------------------------------------------------| | | Use this argument when the /update_type is ALL | | | or PARTITIONS. This argument specifies specific | | | partitions to reboot after the partition | | /reboot_list | firmware has been updated. Valid npar values | | <npar[,npar]...> | are npar(number). Do not put any spaces between | | | parameters. | | | | | | Example: /reboot_list npar1,npar2 | +------------------------------------------------------------------------+ 1.1.3 Command-line examples The following command-line parameter examples can be executed within these environments: Firmware:System ROMSmart Array controllerHard drivesiLOSoftware-later version of:HP Insight Diagnostics Online Edition for Windows Server 2003 (cp008097.exe)HP System Management Homepage (HP SMH) for Windows (cp008257.exe)HP SUMDefined groups: Management Servers-three servers (Management Server1, Management Server2, Management Server3) o Firmware: System ROMSmart Array controllerHard drivesiLO o System ROM o Smart Array controller o Hard drives o iLO o Software-later version of: HP Insight Diagnostics Online Edition for Windows Server 2003 (cp008097.exe)HP System Management Homepage (HP SMH) for Windows (cp008257.exe) o HP Insight Diagnostics Online Edition for Windows Server 2003 (cp008097.exe) o HP System Management Homepage (HP SMH) for Windows (cp008257.exe) o HP SUM Defined groups: Management Servers-three servers (Management Server1, Management Server2, Management Server3) o Defined groups: Management Servers-three servers (Management Server1, Management Server2, Management Server3) Example 1: This command-line input deploys the latest PSP and firmware components: hpsum /use_latest /allow_non_bundle_components /silent Results: All software components and firmware components from the update bundle, which HP SUM determined must be installed, were installed. Example 2: Either of the following command-line inputs can deploy the previous version of the PSP only and force all the components to be installed: hpsum /f:bundle /softwareonly BP000315.xmlhpsum /b BP000315.xml /f:bundle /softwareonly o hpsum /f:bundle /softwareonly BP000315.xml o hpsum /b BP000315.xml /f:bundle /softwareonly Results: All software components and firmware components from the update bundle, which HP SUM determined must be installed, were installed. No firmware was installed. Example 3: This command-line input deploys firmware: hpsum /romonly Results: All firmware components that must be installed, were installed. No software was installed. Example 4: Either of the following command-line inputs can deploy two software components: hpsum /f:software cp008097.exe cp008257.exehpsum /c cp008097.exe /c cp008257.exe /f:software o hpsum /f:software cp008097.exe cp008257.exe o hpsum /c cp008097.exe /c cp008257.exe /f:software Results: The two components were installed. No firmware or other software was installed. Example 5: Either of the following command-line inputs can deploy the latest PSP, later versions of components in the bundle, and firmware to three remote hosts and force all components to be installed: hpsum /group "Management Servers" /current_credential /use_latest /allow_update_to_bundle /allow_non_bundle_components /force:all /override_existing_connection /continue_on_error ServerNotFound /silent /logdir "Management_Server_Files"hpsum /target "Management Server1" /target "Management Server2" /target "Management Server3" /user administrator /passwd letmein /use_latest /allow_update_to_bundle /allow_non_bundle_components /force:all /override_existing_connection /continue_on_error ServerNotFound /silent /logdir "Management_Server_Files" o hpsum /group "Management Servers" /current_credential /use_latest /allow_update_to_bundle /allow_non_bundle_components /force:all /override_existing_connection /continue_on_error ServerNotFound /silent /logdir "Management_Server_Files" o hpsum /target "Management Server1" /target "Management Server2" /target "Management Server3" /user administrator /passwd letmein /use_latest /allow_update_to_bundle /allow_non_bundle_components /force:all /override_existing_connection /continue_on_error ServerNotFound /silent /logdir "Management_Server_Files" Example 6: To use sudo to update components: /hpsum / target 10.0.1.7 /targetype linux /username userid /passwd password /use_sudo /silent To use super user to update components: /hpsum /target 10.0.1.7 /targetype linux /username userid /passwd password /silent /su_username root /su_password rootpwd Results: All software components and firmware components from the update bundle, cp008097.exe, and cp008257.exe were installed on Management Server1, Management Server2, and Management Server3. 1.1.4 Return codes HP SUM has consolidated return codes from Linux and Windows smart components into a new, enhanced return-code mapping. These return codes determine the status of the component installation. You can also use return codes in a script to control the execution of the script and determine any required branching. In Linux, the negative return codes are reported. These return codes are determined by subtracting the negative value from 256. +------------------------------------------------------------------------+ | Return code | Value | Linux | Windows | Text | |--------------------------+-------+-------+---------+-------------------| | SUCCESS_NO_REBOOT | 0 | 0 | 0 | The installation | | | | | | was successful. | |--------------------------+-------+-------+---------+-------------------| | | | | | The installation | | SUCCESS_REBOOT | 1 | 1 | 1 | was successful, | | | | | | but a reboot is | | | | | | required. | |--------------------------+-------+-------+---------+-------------------| | | | | | The component was | | SUCCESS_NOT_REQUIRED | 3 | 3 | 3 | current or not | | | | | | required. | |--------------------------+-------+-------+---------+-------------------| | | | | | A general failure | | FAILURE_GENERAL | -1 | 255 | -1 | occurred. For | | | | | | details, see the | | | | | | error log. | |--------------------------+-------+-------+---------+-------------------| | | | | | A bad input | | FAILURE_BAD_PARM | -2 | 254 | -2 | parameter was | | | | | | encountered. | |--------------------------+-------+-------+---------+-------------------| | | | | | The installation | | FAILURE_COMPONENT_FAILED | -3 | 253 | -3 | of the component | | | | | | failed. | +------------------------------------------------------------------------+ 1.1.5 Windows smart-component return codes +------------------------------------------------------------------------+ | Return code | Meaning | |-------------+----------------------------------------------------------| | 0 | The smart component was not installed. For more | | | information, see the log file. | |-------------+----------------------------------------------------------| | 1 | The smart component was installed successfully. | |-------------+----------------------------------------------------------| | 2 | The smart component was installed successfully, but the | | | system must be restarted. | |-------------+----------------------------------------------------------| | | The installation was not attempted because the required | | 3 | hardware is not present, the software is current, or | | | there is nothing to install. | +------------------------------------------------------------------------+ 1.1.6 Linux smart-component return codes Single-node servers: +------------------------------------------------------------------------+ | Return code | Meaning | |-------------+----------------------------------------------------------| | 0 | The smart component was installed successfully. | |-------------+----------------------------------------------------------| | 1 | The smart component was installed successfully, but the | | | system must be restarted. | |-------------+----------------------------------------------------------| | | The installation was not attempted because the required | | 2 | hardware is not present, the software is current, or | | | there is nothing to install. | |-------------+----------------------------------------------------------| | 3 | The smart component was not installed. For more | | | information, see the log file. | +------------------------------------------------------------------------+ Multi-node servers: +------------------------------------------------------------------------+ | Return code | Meaning | |-------------+----------------------------------------------------------| | 0 | The installation of the deliverable was successful. No | | | reboot is required. | |-------------+----------------------------------------------------------| | 1 | The installation of the deliverable was successful. | | | Reboot is required for the deliverable to be enabled. | |-------------+----------------------------------------------------------| | 2 | 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. | | 3 | o The version to be installed is older than the | | | version already installed. | | | | | | o The supported hardware is not present, not enabled, | | | or in a state that an installation could not be | | | attempted. | | | | | | o The smart component does not support the | | | environment. | | | | | | o There is nothing for the component to accomplish. | |-------------+----------------------------------------------------------| | | If the component is being installed to a remote node, | | 4 | such as an OA or other network-based deployment, this | | | return code indicates that the node cannot be found. | |-------------+----------------------------------------------------------| | 5 | A user canceled the installation before anything could | | | be installed. | |-------------+----------------------------------------------------------| | 6 | The installer cannot run because of an un-met dependency | | | or installation tool failure. | |-------------+----------------------------------------------------------| | 7 | The actual installation operation (not the installation | | | tool) failed. | +------------------------------------------------------------------------+ 1.1.7 Linux RPM return codes +----------------------------------------------------------+ | Return code | Meaning | |-------------+--------------------------------------------| | 0 | The Linux RPM installation was successful. | |-------------+--------------------------------------------| | 1 | The Linux RPM installation failed. | +----------------------------------------------------------+ 1.1.8 VMware ESXi smart-component return codes +------------------------------------------------------------------------+ | Return code | Meaning | |-------------+----------------------------------------------------------| | 0 | The installation of the deliverable was successful. No | | | reboot is required. | |-------------+----------------------------------------------------------| | 1 | The installation of the deliverable was successful. | | | Reboot is required for the deliverable to be enabled. | |-------------+----------------------------------------------------------| | 2 | 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. | | 3 | o The version to be installed is older than the | | | version already installed. | | | | | | o The supported hardware is not present, not enabled, | | | or in a state that an installation could not be | | | attempted. | | | | | | o The smart component does not support the | | | environment. | | | | | | o There is nothing for the component to accomplish. | |-------------+----------------------------------------------------------| | | If the component is being installed to a remote node, | | 4 | such as an OA or other network-based deployment, this | | | return code indicates that the node cannot be found. | |-------------+----------------------------------------------------------| | 5 | A user canceled the installation before anything could | | | be installed. | |-------------+----------------------------------------------------------| | 6 | The installer cannot run because of an un-met dependency | | | or installation tool failure. | |-------------+----------------------------------------------------------| | 7 | The actual installation operation (not the installation | | | tool) failed. | +------------------------------------------------------------------------+ 1.2 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. For parameters that can take list values, list separators can be commas, semicolons, or spaces. [Note] 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 executable files. 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. 1.2.1 Input file format and rules The input file is divided into two sections: ConfigurationThe configuration section starts from the beginning of the file and proceeds until the first node section is encountered. This section consists of a number of settings and their values. Each configuration setting must appear on a fresh line in the file, along with its value. Comments start with a pound (#) character at the beginning of the line. Only one pound character is allowed on any line.Target You can provide remote host nodes to HP SUM. This section can repeat any number of times in the input file, providing a way to organize nodes in related sets.The section starts with the following special header enclosed in brackets: [TARGETS]The section ends with the following special string enclosed brackets: [END]The keyword TARGETS can be suffixed with an optional arbitrary string. This string enables you to tag the purpose of the TARGETS section. Other than the visible difference in the header, the contents of such a section are not treated any differently. For example:[TARGETS_WIN2003]... [END]Credentials: The TARGETS section allows the nodes to be grouped according to the credentials needed for logging in remotely. Each TARGETS section must have a set of login credentials, which applies to all nodes in that section. If you want to use the current host's login credentials to log in to one or more remote nodes, you can do so by setting the variable USECURRENTCREDENTIAL to YES. You can supply login credentials for one or more hosts by using the variables UID and PWD. If you want to provide the variables at the beginning of a TARGETS section, use both of them. If you want to provide the variables in the middle of a TARGETS section, use one or the other to override the selected variable and continue using the active value for the remaining variable.Remote node: You can specify a remote node by using the variable HOST. Possible values are a DNS name or an IP address. o Configuration The configuration section starts from the beginning of the file and proceeds until the first node section is encountered. This section consists of a number of settings and their values. Each configuration setting must appear on a fresh line in the file, along with its value. Comments start with a pound (#) character at the beginning of the line. Only one pound character is allowed on any line. o Target You can provide remote host nodes to HP SUM. This section can repeat any number of times in the input file, providing a way to organize nodes in related sets. The section starts with the following special header enclosed in brackets: [TARGETS] The section ends with the following special string enclosed brackets: [END] The keyword TARGETS can be suffixed with an optional arbitrary string. This string enables you to tag the purpose of the TARGETS section. Other than the visible difference in the header, the contents of such a section are not treated any differently. For example: [TARGETS_WIN2003] ... [END] Credentials: The TARGETS section allows the nodes to be grouped according to the credentials needed for logging in remotely. Each TARGETS section must have a set of login credentials, which applies to all nodes in that section. If you want to use the current host's login credentials to log in to one or more remote nodes, you can do so by setting the variable USECURRENTCREDENTIAL to YES. You can supply login credentials for one or more hosts by using the variables UID and PWD. If you want to provide the variables at the beginning of a TARGETS section, use both of them. If you want to provide the variables in the middle of a TARGETS section, use one or the other to override the selected variable and continue using the active value for the remaining variable.Remote node: You can specify a remote node by using the variable HOST. Possible values are a DNS name or an IP address. o Credentials: The TARGETS section allows the nodes to be grouped according to the credentials needed for logging in remotely. Each TARGETS section must have a set of login credentials, which applies to all nodes in that section. If you want to use the current host's login credentials to log in to one or more remote nodes, you can do so by setting the variable USECURRENTCREDENTIAL to YES. You can supply login credentials for one or more hosts by using the variables UID and PWD. If you want to provide the variables at the beginning of a TARGETS section, use both of them. If you want to provide the variables in the middle of a TARGETS section, use one or the other to override the selected variable and continue using the active value for the remaining variable. o Remote node: You can specify a remote node by using the variable HOST. Possible values are a DNS name or an IP address. 1.2.2 File encoding To allow for the inclusion of double-byte characters, the input file is in UTF-8 format. 1.2.3 Error reporting If errors occur in the input file, HP SUM exits with a return value of -2 (bad parameter). The details of the location and nature of the error are recorded in hpsum_execution_log_<date>_<time>.raw. 1.2.4 Input file parameters +------------------------------------------------------------------------------------------------------+ | Parameter | Description | Possible values | |-----------------------+------------------------------------------+-----------------------------------| | |This parameter causes the installation to | | | |run silently without GUI or console | | | |output. All data is written to the log | | | |file. Any generated prompts use the | | | |default option and continue the | | | |installation without user input. | | |SILENT | |YES, NO | | |If a component requires input before | | | |installation (such as configuration | | | |information), the component installation | | | |fails (unless the IGNOREERRORS = | | | |"FailedDependencies" parameter is | | | |supplied), and an error message is written| | | |to the log file. | | |-----------------------+------------------------------------------+-----------------------------------| | | |/targettype vc | | | | | | | |The following are valid node types:| | | | | | | |ServerWindowsLinuxHPUXEVA or | | | |Command View for EVAFC Switch or | | | |Fibre Channel SwitchOA or Onboard | | | |AdministratorSUPERDOME 2 or | | | |SUPERDOME2 or Superdome 2 Onboard | | | |AdministratoriLOVC or Virtual | | | |ConnectHP SAS or HP SAS B/L | | | |Interconnect SwitchVMware or VMware| | | |HostiPDU or Intelligent Power | | | |Distribution Unit (iPDU) | | | | o Server | | | | | | | | o Windows | | | | | | | | o Linux | | | | | | | | o HPUX | | | | | | | | o EVA or Command View for EVA | | |This parameter specifies the node type and| | |TARGETTYPE |can shorten the inventory process. | o FC Switch or Fibre Channel | | | | Switch | | | | | | | | o OA or Onboard Administrator | | | | | | | | o SUPERDOME 2 or SUPERDOME2 or | | | | Superdome 2 Onboard | | | | Administrator | | | | | | | | o iLO | | | | | | | | o VC or Virtual Connect | | | | | | | | o HP SAS or HP SAS B/L | | | | Interconnect Switch | | | | | | | | o VMware or VMware Host | | | | | | | | o iPDU or Intelligent Power | | | | Distribution Unit (iPDU) | | | | | | | |If you use the command with a | | | |group, the HP SUM assumes all nodes| | | |in the group are the same node | | | |type. | |-----------------------+------------------------------------------+-----------------------------------| |FORCEALL |Forces updates to both firmware and |YES, NO | | |software components. | | |-----------------------+------------------------------------------+-----------------------------------| |FORCEROM |Forces updates to firmware components. |YES, NO | |-----------------------+------------------------------------------+-----------------------------------| |FORCESOFTWARE |Forces updates to software components. |YES, NO | |-----------------------+------------------------------------------+-----------------------------------| | |Enables you to override or downgrade an | | |FORCEBUNDLE |existing installation of components in the|YES, NO | | |selected bundle. | | |-----------------------+------------------------------------------+-----------------------------------| | |Downgrade to an earlier version of | | |DOWNGRADE |firmware for multi-node devices such as |YES, NO | | |hard drives and array controllers. | | | |(Applies to firmware only.) | | |-----------------------+------------------------------------------+-----------------------------------| | |Rewrite the same version of firmware only | | |REWRITE |for multi-node devices such as hard drives|YES, NO | | |and array controllers. (Applies to | | | |firmware only.) | | |-----------------------+------------------------------------------+-----------------------------------| |REBOOTALLOWED |Enables you to reboot, if required. |YES, NO | |-----------------------+------------------------------------------+-----------------------------------| |REBOOTMESSAGE |Create a message to be displayed prior to |Any string (not exceeding 256 | | |rebooting. |characters) | |-----------------------+------------------------------------------+-----------------------------------| |REBOOTDELAY |Delay before rebooting. |Time in seconds | |-----------------------+------------------------------------------+-----------------------------------| |COMPONENTSLIST |Limit the list of components to be |Component names with file | | |updated. |extensions (.exe, .rpm, or .scexe) | |-----------------------+------------------------------------------+-----------------------------------| |BUNDLESLIST |Limit the list of bundle xml files to be |Bundle file names | | |filtered. | | |-----------------------+------------------------------------------+-----------------------------------| | |This is a filter switch and enables you to| | | |install newer versions of components | | | |defined in a PSP, ISP, or bundle. | | |ALLOWUPDATEBUNDLE | |YES, NO | | |This parameter enables these components to| | | |replace the older versions of the same | | | |component that might have shipped with the| | | |bundles. | | |-----------------------+------------------------------------------+-----------------------------------| | |Defines the behavior when a remote node | | | |has an existing HP SUM session in | | | |progress. | | | | | | | |Use this parameter to skip the host if an | | | |existing HP SUM session already exists. A | | | |value of NO overrides the session in | | |SKIPTARGET |progress and reinitializes the |YES, NO | | |installation framework on the remote host.| | | | | | | |[Note] Note: | | | | If an HP SUM session discovers a | | | | remote node is running HP SUM | | | | locally, HP SUM ignores the | | | | SKIPTARGET command and skips the | | | | remote node. | | |-----------------------+------------------------------------------+-----------------------------------| | |Causes the installation to continue and | | | |ignore errors. | | | | | | | |The ServerNotFound option can be used to | | | |bypass inactive or unavailable remote |ServerNotFound, BadPassword, | |IGNOREERRORS |hosts when deploying firmware or software |FailedDependencies | | |to multiple remote hosts at the same time.| | | | | | | |Use FailedDependencies to ignore any | | | |failed dependencies and proceed with the | | | |ones that are ready to be installed. | | |-----------------------+------------------------------------------+-----------------------------------| | |Provide a single local baseline path. This| | |SOURCEPATH |action creates an inventory from the given|Directory path | | |path instead of the local or default | | | |baseline. | | |-----------------------+------------------------------------------+-----------------------------------| | |This is a filter switch for use with | | | |bundles. The parameter enables you to use | | | |the latest version of the bundle when | | | |multiple versions of bundles are listed on| | | |the command line. | | |USELATEST | |YES, NO | | |If no bundles are specified on the command| | | |line, and multiple bundles are in the | | | |directory, this parameter enables HP SUM | | | |to use the bundle that has the latest | | | |version for installation. | | |-----------------------+------------------------------------------+-----------------------------------| |DRYRUN |Simulates the installation for a test run.|YES, NO | | |Nothing is installed. | | |-----------------------+------------------------------------------+-----------------------------------| | |Specify the HP SUM CLI options inside the | | | |input file, which overrides the | | | |configuration settings. Parameters can be | | | |separated by a semi-colon, comma, or a | | |OPTIONS |space. |One or more CLI switch | | | | | | |This parameter replaces the LSPOPTIONS | | | |parameter that was previously supported | | | |with LDU. | | |-----------------------+------------------------------------------+-----------------------------------| | |Specifies that components that use AMS and| | | |WBEM Providers listed as optional updates | | | |on the Components Selection screen. | | | | |Yes | |NOMGMT |In silent mode, HP SUM does not update AMS| | | |or WBEM Providers. |No | | | | | | |[Note] Note: | | | | You can only configure SNMP in HP | | | | SUM GUI mode. | | |-----------------------+------------------------------------------+-----------------------------------| | |Specifies that components that use WMI | | | |protocol are available to be selected for | | | |installation. | | | | | | |USEWMI |These components are optional by default |YES, NO | | |and are not installed unless this | | | |parameter is used. When the /usewmi | | | |parameter is used. This parameter does not| | | |apply to HP Integrity servers. | | |-----------------------+------------------------------------------+-----------------------------------| | |Specifies that AMS agentless management | | | |service components are available to be | | | |selected for installation. | | | | | | | |This option will only apply to Gen8 and | | | |later servers. If this parameter is set | | |USEAMS |for a ProLiant G7 and earlier server |YES, NO | | |model, it will be ignored. | | | | | | | |These components are only installed by | | | |default on Gen8 and later servers. This | | | |parameter does not apply to HP Integrity | | | |servers. | | |-----------------------+------------------------------------------+-----------------------------------| | |This is a filter switch that allows you to| | | |view only the firmware components required| | |ROMONLY |for installation. |YES, NO | | | | | | |Do not use the /romonly parameter with the| | | |/softwareonly parameter. | | |-----------------------+------------------------------------------+-----------------------------------| | |This is a filter switch that allows you to| | | |view only the software components required| | |SOFTWAREONLY |for installation. |YES, NO | | | | | | |Do not use the /softwareonly parameter | | | |with the /romonly parameter. | | |-----------------------+------------------------------------------+-----------------------------------| | |Enables the credentials of the local host | | | |to be used as the credentials to access | | | |the nodes instead of providing the user | | | |name and password explicitly for each | | |USECURRENTCREDENTIAL |node. |YES, NO | | | | | | |The assumption is that the current | | | |credentials are valid for the nodes that | | | |are being accessed. (Applies to Windows | | | |only.) | | |-----------------------+------------------------------------------+-----------------------------------| | |Instructs HP SUM to include the components| | |WEBUPDATENEEDED |from the HP FTP site (ftp://ftp.hp.com) in|YES, NO | | |the list of possible updates. | | |-----------------------+------------------------------------------+-----------------------------------| | |Use a proxy server (and port number) to |String value | |USEPROXYSERVER |access the HP FTP site (ftp://ftp.hp.com).| | | | |For example, 11.22.33.44:80 | |-----------------------+------------------------------------------+-----------------------------------| |USEPROXYSCRIPT |Include a proxy script to access the HP |Web URL (for example, | | |FTP site (ftp://ftp.hp.com). |autoproxy.com) | |-----------------------+------------------------------------------+-----------------------------------| |DELETEINPUTFILE |Instructs HP SUM to delete the input file |YES, NO (default) | | |after it has been read. | | |-----------------------+------------------------------------------+-----------------------------------| | |This parameter instructs HP SUM how to | | | |proceed when a component has a failed | | | |dependency. | | | | | | | |The default of OmitHost causes the host to| | | |be put in a failure state, and no |OmitHost (default), OmitComponent, | |ONFAILEDDEPENDENCY |installation is attempted on it. |Force | | | | | | |OmitComponent clears the affected | | | |components and proceeds with any updates | | | |that do not have dependency failures. | | | |Force attempts all updates, even if they | | | |have dependency failures. | | |-----------------------+------------------------------------------+-----------------------------------| | |This parameter is the IP address or the | | | |DNS name of a remote server, remote iLO | | | |NIC port, Virtual Connect Ethernet or | | | |Fibre Channel Module for c-Class | | | |BladeSystem, or BladeSystem OA. | | | | | | |HOST |When two OAs are in an enclosure, this |IP address, DNS name | | |parameter is the active OA. When | | | |specifying the IP address, you can use | | | |either the IPv4 or IPv6 format. | | | | | | | |This parameter specifies an already | | | |defined group name in the HP SUM GUI. | | |-----------------------+------------------------------------------+-----------------------------------| | |This parameter is the IP address or the | | | |DNS name of a remote server, remote iLO | | | |NIC port, Virtual Connect Ethernet or | | | |Fibre Channel Module for c-Class | | | |BladeSystem, or BladeSystem OA. | | | | | | |NODE |When two OAs are in an enclosure, this |IP address, DNS name | | |parameter is the active OA. When | | | |specifying the IP address, you can use | | | |either the IPv4 or IPv6 format. | | | | | | | |This parameter specifies an already | | | |defined group name in the HP SUM GUI. | | |-----------------------+------------------------------------------+-----------------------------------| |UID |Logs in to the nodes with your user ID. |<username> | |-----------------------+------------------------------------------+-----------------------------------| | |Uses the password for the user ID | | |PWD |specified in the UID. |<password> | | | | | | |The password is used to log in to nodes. | | |-----------------------+------------------------------------------+-----------------------------------| | |Redirects the output from HP SUM or the HP| | | |BladeSystem c-Class OA flash utility to a | | | |different directory than the default | | | |location. | | | | | | | |* For Windows components, the default | | | |location is | | |LOGFILENAME = "path" |%SYSTEMDRIVE%\CPQSYSTEM\hp\log<netAddress>|Log file name | | |and the redirected location is | | | |<path>\hp\log\<netAddress>. | | | | | | | |* For Linux components, the default | | | |location is /var/hp/log/<netAddress> and | | | |the redirected location is | | | |<path>/hp/log/<netAddress>. | | |-----------------------+------------------------------------------+-----------------------------------| | |Specifies the IP address or DNS host name | | | |of a system with read/write access to | | |CMAMGMTSTATIONRWIPORDNS|serve as a management station. You can |IP address, DNS name | | |specify multiple locations separated by a | | | |space. (Applies to Linux SPP only.) | | |-----------------------+------------------------------------------+-----------------------------------| | |Specifies the IP address or DNS host name | | | |of a system with read-only access to serve| | |CMAMGMTSTATIONROIPORDNS|as a management station. You can specify |IP address, DNS name | | |multiple locations separated by a space. | | | |(Applies to Linux SPP only.) | | |-----------------------+------------------------------------------+-----------------------------------| | |Specifies a person or phone number for | | |CMASYSCONTACT |administration of this system. (Applies to|String value | | |Linux SPP only.) | | |-----------------------+------------------------------------------+-----------------------------------| |CMASYSLOCATION |Designates the location of this system. |String value | | |(Applies to Linux SPP only.) | | |-----------------------+------------------------------------------+-----------------------------------| | |Determines whether the HP Systems Insight |YES (start the web agent)NO (do not| | |Manager Web Agent is started when the |start the web agent) | |CMASTARTWEBAGENT |health application loads. (Applies to | o YES (start the web agent) | | |Linux SPP only.) | | | | | o NO (do not start the web agent)| |-----------------------+------------------------------------------+-----------------------------------| | | |YES (start the storage agent)NO (do| | |Determines whether the HP Systems Insight |not start the storage agent) | |CMASTARTSTORAGEAGENT |Manager Storage Agent is started when the | o YES (start the storage agent) | | |health application loads. (Applies to | | | |Linux SPP only.) | o NO (do not start the storage | | | | agent) | |-----------------------+------------------------------------------+-----------------------------------| | | |YES (start the web agent)NO (do not| | |Determines whether the HP Systems Insight |start the web agent) | |CMASTARTNICAGENT |Manager NIC agent is started. (Applies to | o YES (start the web agent) | | |Linux SPP only). | | | | | o NO (do not start the web agent)| |-----------------------+------------------------------------------+-----------------------------------| | | |YES (start the HP Lights-Out | | | |management driver)NO (do not start | | |Determines whether the HP Lights-Out |the HP Lights-Out management | | |management driver is started when the |driver) | |CMANOTAINTEDKERNEL |health application loads. (Applies to | o YES (start the HP Lights-Out | | |Linux SPP only.) | management driver) | | | | | | | | o NO (do not start the HP | | | | Lights-Out management driver) | |-----------------------+------------------------------------------+-----------------------------------| | |Informs the VCA of the name of the VCRM to| | |HPVCAVCRMSERVER |use as a software distribution baseline. |VCRM name | | |(Applies to Linux SPP only.) | | |-----------------------+------------------------------------------+-----------------------------------| | |HP Systems Management Homepage (hpsmh) | | |FORCE-OVERWRITE |uses this parameter to force overwrite the|YES, NO (default) | | |SMH settings of an existing configuration | | | |file. | | |-----------------------+------------------------------------------+-----------------------------------| | |HP Systems Management Homepage (hpsmh) |Up to five Linux groups, separated | |ADMIN-GROUP |uses this parameter to set up security for|by spaces or semicolons, to enable | | |the web server. (Applies to Linux SPP |administrative access to the web | | |only.) |services. | |-----------------------+------------------------------------------+-----------------------------------| | |HP Systems Management Homepage uses this |Up to five Linux groups, separated | |USER-GROUP |parameter to set up security for the web |by spaces or semicolons, to enable | | |server. (Applies to Linux SPP only.) |user-level access to the web | | | |servers. | |-----------------------+------------------------------------------+-----------------------------------| | |HP Systems Management Homepage uses this |Up to five Linux groups, separated | |OPERATOR-GROUP |parameter to set up security for the web |by spaces or semicolons, to enable | | |server. (Applies to Linux SPP only.) |operator-level access to the web | | | |servers. | |-----------------------+------------------------------------------+-----------------------------------| | |Determines whether an anonymous user can | | |ANONYMOUS-ACCESS |access HP Systems Management Homepage. |YES, NO (default) | | |(Applies to Linux SPP only.) | | |-----------------------+------------------------------------------+-----------------------------------| | |HP Systems Management Homepage uses this | | | |parameter to determine whether HP SMH can | | |IP-BINDING |use all available NICs and detect subnets |YES, NO (default) | | |for its web services. (Applies to Linux | | | |SPP only.) | | |-----------------------+------------------------------------------+-----------------------------------| | |HP Systems Management Homepage uses this | | | |parameter to restrict the NICs and subnets|IP address pairs separated by | | |to use for its web servers. |semicolons (for example, | |IP-BINDING-LIST | |10.1.1.1/255.255.255.0; | | |The IP-BINDING parameter must be set to | | | |yes for this parameter to be used during |10.2.2.2/255.255.255.0) | | |installation. (Applies to Linux SPP only.)| | |-----------------------+------------------------------------------+-----------------------------------| | | |YES, NO (default) | | | | | | |HP Systems Management Homepage uses this |To enable restrictions on who can | |IP-RESTRICTED-LOGINS |parameter to restrict login access. |log in to the web server, this | | |(Applies to Linux SPP only.) |parameter must be set to yes, and | | | |values must be provided to the | | | |IP-RESTRICTED-EXCLUDE or | | | |IP-RESTRICTED-INCLUDE parameters. | |-----------------------+------------------------------------------+-----------------------------------| | |HP Systems Management Homepage uses this | | | |parameter to exclude specific IP | | | |address/netmask pairs from logging into |List of IP address ranges separated| | |the web services. (Applies to Linux PSP |by semicolons (for example, | |IP-RESTRICTED-EXCLUDE |only.) |10.1.1.1-10.1.1.10; | | | | | | |This parameter is ignored unless the |10.2.2.2-10.2.2.10) | | |IP-RESTRICTED-LOGINS parameter is set to | | | |yes. | | |-----------------------+------------------------------------------+-----------------------------------| | |HP Systems Management Homepage uses this | | | |parameter to enable login only from the IP|List of IP address ranges separated| | |address/netmask pairs specified. (Applies |by semicolons (for example, | |IP-RESTRICTED-INCLUDE |to Linux SPP only.) |10.1.1.1-10.1.1.10; | | | | | | |This parameter is ignored unless the |10.2.2.2-10.2.2.10) | | |IP-RESTRICTED-LOGINS parameter is set to | | | |yes. | | |-----------------------+------------------------------------------+-----------------------------------| | | |YES (default to include anonymous | | |HP Systems Management Homepage uses this |access)NO | |LOCALACCESS-ENABLED |parameter to determine whether to enable | o YES (default to include | | |local anonymous access to the web | anonymous access) | | |services. (Applies to Linux SPP only.) | | | | | o NO | |-----------------------+------------------------------------------+-----------------------------------| | | |Anonymous | | | |(default)AdministratorCAUTION: | | | |Selecting local access with | | | |administrator privileges as the | | | |login provides full access to any | | | |user who has access to the local | | | |console, without prompting for a | | |HP Systems Management Homepage uses this |user name or password. | | |parameter to determine the type of access | o Anonymous (default) | |LOCALACCESS-TYPE |granted to local users. (Applies to Linux | | | |SPP only.) | o Administrator | | | | | | | | CAUTION: Selecting local access| | | | with administrator privileges | | | | as the login provides full | | | | access to any user who has | | | | access to the local console, | | | | without prompting for a user | | | | name or password. | |-----------------------+------------------------------------------+-----------------------------------| | | |TrustByCert-If you use this value, | | | |you must define the CERTLIST | | | |parameter to enable access to the | | | |server.TrustByName-If you use this | | | |value, you must define the | | | |XENAMELIST.TrustByAll-HP does not | | | |recommend using this value because | | | |of possible negative security | | | |consequences.The accepted values | | | |are case-sensitive and must be | | | |capitalized as shown. Failure to do| | | |so prevents the trust relationship | | | |from being set up properly during | | | |installation and might affect | | | |access to the web server. | | | | o TrustByCert-If you use this | | | | value, you must define the | | | | CERTLIST parameter to enable | | | | access to the server. | | |HP Systems Management Homepage uses this | | |TRUSTMODE |parameter to set up the trust relationship| o TrustByName-If you use this | | |mode. (Applies to Linux SPP only.) | value, you must define the | | | | XENAMELIST. | | | | | | | | o TrustByAll-HP does not | | | | recommend using this value | | | | because of possible negative | | | | security consequences. | | | | | | | | [Caution] Caution: | | | | The accepted values | | | | are case-sensitive | | | | and must be | | | | capitalized as shown.| | | | Failure to do so | | | | prevents the trust | | | | relationship from | | | | being set up properly| | | | during installation | | | | and might affect | | | | access to the web | | | | server. | |-----------------------+------------------------------------------+-----------------------------------| | |Enables you to provide a list of | | | |certificate files or servers where | | |CERTLIST |certificates can be obtained for trust |Certificate file name or Server DNS| | |relationships for the HP Systems |name | | |Management Homepage. (Applies to Linux SPP| | | |only.) | | |-----------------------+------------------------------------------+-----------------------------------| | |Enables you to provide a list of servers, | | | |separated by semicolons, for trust | | | |relationships for the HP Systems | | | |Management Homepage. (Applies to Linux SPP| | |XENAMELIST |only.) |Server DNS name | | | | | | |This parameter is valid only if the | | | |TRUSTMODE parameter is set to TrustByName.| | | |(Applies to Linux SPP only.) | | |-----------------------+------------------------------------------+-----------------------------------| | | |SinglePathSecurePathQLogicFailureNo| | | |default value | | | | o SinglePath | | |The hp_qla2x00 QLogic Fibre Channel Driver| | |HPQLA2X00FO |uses this parameter to determine the | o SecurePath | | |failover mode to use. (Applies to Linux | | | |SPP only.) | o QLogicFailure | | | | | | | | [Note] Note: | | | | No default value | |-----------------------+------------------------------------------+-----------------------------------| | |The hp_qla2x00 QLogic Fibre Channel Driver| | |HPQLA2X00FORCE |uses this parameter to determine whether |Y, N (default) | | |to skip detection of third-party storage. | | | |(Applies to Linux SPP only.) | | |-----------------------+------------------------------------------+-----------------------------------| | |Provides the user name credentials for the| | | |OA associated with VC. You must define a | | | |value of these variables before the HOST |User can define the OAUID variable | |OAUID |variable in the [TARGETS] section. This |multiple times before each HOST | | |parameter applies only for VC firmware. |variable. | | | | | | |You can also use OAUSER or OAUSERNAME. | | |-----------------------+------------------------------------------+-----------------------------------| | |Provides the password credentials for the | | | |OA associated with VC. You must define a | | | |value of these variables before the HOST |User can define OAPWD variable | |OAPWD |variable in the [TARGETS] section. This |multiple times before each HOST | | |parameter applies only for VC firmware. |variable. | | | | | | |You can also use OAPASSWORD. | | |-----------------------+------------------------------------------+-----------------------------------| | |Allows the installation to proceed on a |YES, NO | |IGNOREWARNINGS |Superdome 2 node even when warnings are | | | |returned during analysis. |Superdome 2 servers only | |-----------------------+------------------------------------------+-----------------------------------| | |This argument determines which Superdome 2|ALL, COMPLEX, PARTITIONS | |UPDATETYPE |firmware is updated. | | | | |Superdome 2 servers only | |-----------------------+------------------------------------------+-----------------------------------| | |Use this argument when the |For example: | | |UPDATETYPE=PARTITIONS. This argument |DEVICELIST=npar1,blade1/1 | | |specifies the subset of partitions or | | |DEVICELIST |blades to update when you do not want to |Do not put spaces between the | | |update all partitions. Valid devices are: |parameters | | |npar(number) and blade(enc)/(bay). | | | | |Superdome 2 servers only | |-----------------------+------------------------------------------+-----------------------------------| | |Use this argument when the UPDATETYPE= ALL|For example: REBOOTLIST=npar1,npar2| | |or UPDATETYPE= PARTITIONS. This argument | | |REBOOTLIST |specifies specific partitions to reboot |Do not put spaces between the | | |after the partition firmware has been |parameters | | |updated. Valid npar values are | | | |npar(number). |Superdome 2 servers only | |-----------------------+------------------------------------------+-----------------------------------| | |Use this argument to provide a superuser | | | |username. | | | | | | | |SUUSERNAME cannot be used with USESUDO | | | |access level. | | |SUUSERNAME | |<superusername> | | |[Note] Note: | | | | Specifying TARGETTYPE = linux | | | | reduces inventory time for | | | | deployments. This is an optional | | | | input file argument. | | |-----------------------+------------------------------------------+-----------------------------------| | |Use this argument to provide a superuser | | | |password. | | | | | | | |SUPASSWORD cannot be used with USESUDO | | | |access level. | | |SUPASSWORD | |<superuserpassword> | | |[Note] Note: | | | | Specifying TARGETTYPE = linux | | | | reduces inventory time for | | | | deployments. This is an optional | | | | input file argument. | | |-----------------------+------------------------------------------+-----------------------------------| | |Use this argument to use the sudo command.| | | | | | | |When you specify USESUDO = YES in the | | | |input file, along with UID and PWD, UID | | | |and PWD are considered sudo users. | | | | | | |USESUDO |USESUDO cannot be used with SUUSERNAME and|Yes, No | | |SUPASSWORD access level. | | | | | | | |[Note] Note: | | | | Specifying TARGETTYPE = linux | | | | reduces inventory time for | | | | deployments. This is an optional | | | | input file argument. | | +------------------------------------------------------------------------------------------------------+ Examples of the HP SUM input file include the following: REBOOTALLOWED = YES REBOOTREQUIRED = NO REBOOTMESSAGE = "Server is going down for a reboot" REBOOTDELAY = 15 COMPONENTSLIST = cp001234.exe, cp001235.exe BUNDLESLIST = bp001234.xml ALLOWUPDATEBUNDLE = YES SKIPTARGET = NO IGNOREERRORS = ServerNotFound, FailedDependencies SOURCEPATH = c:\pkgsource1 USELATEST = YES SILENT = YES OPTIONS = /f:rom [TARGETS] HOST = schinta1 HOST = schinta2 UID = root PWD = root123 HOST = 234.567.765.432 [END] USAGE: hpsum /inputfile <path:\inputfile.txt> Examples of inputfile.txt file: Example: The two nodes are passed to be updated. The nodes do not necessarily have to be OAs. They can be any node that HP SUM supports. DRYRUN = YES SILENT = YES [TARGETS] HOST = BL465C-01 HOST = 192.168.1.2 [END] Example A host DNS is passed along with the user ID and password to use for the hosts in the group. DRYRUN = YES SILENT = YES [TARGETS] HOST = BL685cG6 UID = Bigboss2 PWD = password [END] Example SILENT = YES IGNOREERRORS = ServerNotFound,BadPassword, FailedDepedencies SKIPTARGET = NO SOURCEPATH = C:\fwcd\firmware-8.70-0\hp\swpackages [GROUPS] HOST=winserver UID=Userid PWD=password [END] Example SILENT = YES IGNOREERRORS = ServerNotFound,BadPassword, FailedDepedencies SKIPTARGET = NO SOURCEPATH = C:\ fwcd\firmware-8.70-0\hp\swpackages FORCEALL = YES REBOOTALLOWED = YES REBOOTDELAY = 30 REBOOTMESSAGE = "Install complete, server will reboot in 30 seconds" [TARGETS] HOST=16.83.62.141 UID=Userid PWD=password [END] [TARGETS] HOST=16.83.61.48 UID=Userid PWD=password [END] [TARGETS] HOST=16.83.62.196 UID=Userid PWD=password [END] [TARGETS] HOST=16.83.61.24 UID=Userid PWD=password [END] Example: Superdome 2 input files: IGNOREWARNINGS = TRUE [TARGET] HOST = 10.0.0.206 UID = Userid PWD = password UPDATETYPE = PARTITIONS DEVICELIST=npar1,npar2,blade1/4,blade 1/5 REBOOTLIST=npar1,npar2 [END] Usage example of access level. USAGE: hpsum /inputfile <path:\inputfile.txt> Example: Using sudo to update components on Linux: SILENT = YES [TARGETS] HOST = 10.0.1.7 UID = Userid PWD = password [END] Example: To update multiple targets using sudo in an input file: SILENT = YES USESUDO = YES [TARGETS] HOST = 10.0.1.7 UID = Userid PWD = password [END] [TARGETS] HOST = 10.0.1.73 UID = Userid PWD = password [END] Example: Using super user to update Linux components: SILENT = YES [TARGETS] HOST = 10.0.1.7 UID = Userid PWD = password SUUSERNAME = root SUPASSWORD = rootpwd [END] Example: To update multiple targets using super user in an input file when all targets have the same super user credentials: SILENT = YES SUUSERNAME = root SUPASSWORD = rootpwd [TARGETS] HOST = 10.0.1.7 UID = Userid PWD = password [END] [TARGETS] HOST = 10.0.1.73 UID = Userid PWD = password [END] 1.3 Reports HP SUM generates three types of reports about the specified system or repository. HP SUM generates these reports by using the command-line arguments. If no additional arguments are specified on the command line, HP SUM uses the local host and default repository locations (the directory where HP SUM was initiated). You can specify a node if you provide the appropriate credentials. You can specific a repository by using other command-line parameters to generate reports. For specific commands, see "Command-line interface" (page ). +-----------------------------------------------------------------------------------------------------------------------------------------+ | Report type | Description | Report file information* | |------------------+-----------------+----------------------------------------------------------------------------------------------------| | |This argument | | | |generates a | | | |report listing, a| | | |node summary, and| | | |description of |The following report files are generated: | | |how the | | | |components in the|hpsum_Report_<date>.htmlhpsum_Report_<date>.xmlhpsum_Report_<date>.csv | |/report |repository affect| o hpsum_Report_<date>.html | | |the node. For | | | |example, whether | o hpsum_Report_<date>.xml | | |each component | | | |applies to the | o hpsum_Report_<date>.csv | | |node. | | | | | | | |Usage: hpsum | | | |/report | | |------------------+-----------------+----------------------------------------------------------------------------------------------------| | |This argument |The following report files are generated: | | |generates a | | | |report listing of|hpsum_Inventory_Report_<date>.htmlhpsum_Inventory_Report_<date>.xmlhpsum_Inventory_Report_<date>.csv| | |the components in| o hpsum_Inventory_Report_<date>.html | |/inventory_report |the specified | | | |repository. | o hpsum_Inventory_Report_<date>.xml | | | | | | |Usage: hpsum | o hpsum_Inventory_Report_<date>.csv | | |/inventory_report| | |------------------+-----------------+----------------------------------------------------------------------------------------------------| | |This argument | | | |generates a |The following report files are generated: | | |report listing of| | | |the firmware in |HPSUM_Firmware_Report_<date>fwreport.xml is placed in a folder named HPSUM_Firmware_Report_<date> | |/firmware_report |the specified | o HPSUM_Firmware_Report_<date> | | |repository. | | | | | o fwreport.xml is placed in a folder named HPSUM_Firmware_Report_<date> | | |Usage: hpsum | | | |/firmware_report | | |------------------+-----------------+----------------------------------------------------------------------------------------------------| | |This argument | | | |generates a |The following report file is generated: | |/dependency_report|report that lists| | | |failed |HPSUM_FailedDependency_Reports_<datatime>.xml, .html, or .csv. | | |dependencies for | | | |all nodes. | | |------------------+-----------------+----------------------------------------------------------------------------------------------------| | |This argument | | | |generates a | | | |report that lists| | | |all installed |The following report file is generated: | |/installed_report |firmware, | | | |software, and |HPSUM_Installed_Report_<datatime>.xml , .html, or .csv. | | |driver versions | | | |installed on | | | |nodes. | | +-----------------------------------------------------------------------------------------------------------------------------------------+ HP SUM generates the reports as XML or HTML files that you can view in a JavaScript-enabled web browser. The supported browsers for viewing the report files are Microsoft Internet Explorer 6.0 and Mozilla Firefox 3.5 and later. By default, the reports are located in the current working directory from where HP SUM was initiated. If that current location is write-protected, the reports are located in the same directory as the HP SUM log files. HP SUM generates reports in CSV format that you can open in any application that supports CSV format. The HP SUM log files are located in these folders: On Windows operating systems: C:\cpqsystem\hp\logOn Linux: /var/hp/log o On Windows operating systems: C:\cpqsystem\hp\log o On Linux: /var/hp/log When HP SUM generates the report, the HP SUM GUI does not appear. When the report is generated, HP SUM displays the report file location. 1.4 Downloading HP SUM and components from the SDR If you are using a Linux system, you can download HP SUM as an RPM from the HP SDR. This allows you to download and install HP SUM and components from the SDR using common YUM commands. For more information about downloading and installing HP SUM as an RPM, see the document Linux best practices using HP Service Pack for ProLiant (SPP) and Software Delivery Repository (SDR) at http://h20000.www2.hp.com/bc/docs/support/SupportManual/c03479393/c03479393.pdf. For information on using the SDR, go to http://www.hp.com/go/sdr.