HP Smart Update Manager - Manual (Page 82)

To create an input file, use a text editor. All section headers and trailers must match. 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: 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 nodes.
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.
Input file format and rules
The input file is divided into two sections:
•
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.
•
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.
82 Using legacy scripts to deploy updates