HP Integrity rx2800 HP Smart Update Manager User Guide - Page 75

Command-line usage of input file, Input file format and rules

Page 75 highlights

perform dry runs of installations to ensure the scripts are working without deploying the firmware updates that might be required on each target. Remove the DRYRUN=YES option to perform the updates. For parameters that can take list values, list separator can be commas, semicolons, or spaces. NOTE: The credentials can be left out of the file for greater security and passed on the command line to HP Smart Update Manager. The only limitation of this is that the userID 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 parameter to a normal 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 it is not stored in the same location as the HP SUM executables. The field can be enclosed in double quotes to enable paths with spaces. Also, the input file itself might contain the same flags on the command line. The usual command-line flags can still be used with the -inputfile flag and takes precedence over any given input file. Command-line usage of input file The form for the HP SUM command line using an input file is hpsum -inputfile . The input file itself can contain the same flags on the command line. The usual command line flags can still be used with the -inputfile flag, and takes precedence over any given input file. The field can be enclosed in double quotes to enable paths with spaces. 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 target section is encountered. This section consists of a number of settings parameters and their values. Each configuration setting must appear on a fresh line in the file along with its value. Comments start with a # character at the beginning of the line. Only one # is allowed on any line. • Target You can provide remote host targets to HP Smart Update Manager. This section can repeat any number of times in the input file, providing a way to organize targets in related sets. The section starts with a special header "TARGETS" enclosed in a pair of square brackets: [TARGETS] Targets section ends with the special string "END" enclosed in a pair of brackets: [END] The keyword TARGETS can be suffixed with an optional arbitrary string. This 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] o Credentials: The TARGETS section allows the targets 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 targets in that section. If you want to use the current host's login credentials Scripted deployment 75

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124

Scripted deployment 75
perform dry runs of installations to ensure the scripts are working without deploying the firmware updates
that might be required on each target. Remove the
DRYRUN=YES
option to perform the updates.
For parameters that can take list values, list separator can be commas, semicolons, or spaces.
NOTE:
The credentials can be left out of the file for greater security and passed on the
command line to HP Smart Update Manager. The only limitation of this is that the userID 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 normal 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 it is not stored in the same location as the HP SUM executables. The
<filename>
field can be
enclosed in double quotes to enable paths with spaces. Also, the input file itself might contain the same
flags on the command line. The usual command-line flags can still be used with the -
inputfile
flag and
takes precedence over any given input file.
Command-line usage of input file
The form for the HP SUM command line using an input file is hpsum
-inputfile <filename>
. The
input file itself can contain the same flags on the command line. The usual command line flags can still be
used with the -
inputfile
flag, and takes precedence over any given input file. The <
filename
> field can
be enclosed in double quotes to enable paths with spaces.
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 target
section is encountered. This section consists of a number of settings parameters and their values.
Each configuration setting must appear on a fresh line in the file along with its value. Comments start
with a # character at the beginning of the line. Only one # is allowed on any line.
Target
You can provide remote host targets to HP Smart Update Manager. This section can repeat any
number of times in the input file, providing a way to organize targets in related sets.
The section starts with a special header "TARGETS" enclosed in a pair of square brackets:
[TARGETS]
Targets section ends with the special string "END" enclosed in a pair of brackets:
[END]
The keyword TARGETS can be suffixed with an optional arbitrary string. This 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]
o
Credentials: The TARGETS section allows the targets 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 targets in that section. If you want to use the current host's login credentials