Home » HP Manuals » Servers » HP ProLiant ML10 » Manual Viewer

HP ProLiant ML10 HP Smart Update Manager 6.0.0 User Guide - Page 49

Input file format and rules, File encoding, Credentials:

Add to My Manuals
Save this manual to your list of manuals

Page 49 highlights

For parameters that can take list values, list separators can be commas, semicolons, or spaces. NOTE: The credentials can be omitted from the file for greater security and passed on the command line to HP SUM. The only limitation that the user ID and credentials must be the same on all. When the file has been created, to use it with HP SUM, add it as the inputfile 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 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. File encoding To allow for the inclusion of double-byte characters, the input file is in UTF-8 format. Input files 49

Section	Page
HP Smart Update Manager User Guide	1
Contents	3
1 Introduction	7
HP SUM overview	7
About the graphical user interface	8
Status icon descriptions	9
HP SUM new terms	9
2 Downloading, installing, and launching HP SUM	10
Downloading HP SUM	10
Downloading HP SUM from the HP SUM website	10
Downloading HP SUM from the SDR website	10
Migrating nodes from HP SUM 5.x to HP SUM 6	10
Deploying HP SUM	11
Running HP SUM	11
Deploying firmware for HP ProLiant servers using the HP Service Pack for ProLiant	11
Deploying HP Integrity firmware bundles with HP SUM	12
Deployment modes	12
Deployment scenarios	12
Disabling BitLocker to permit firmware updates (Windows only)	13
Launching and logging into HP SUM	14
Launching HP SUM	14
Logging into HP SUM	15
Logging out of the HP SUM GUI	15
3 Using the HP SUM GUI	16
Using the Home screen	16
Using the Activity screen	16
Using Guided Update	16
Using the Baseline Library screen	18
Adding a baseline	18
Creating a custom baseline	19
Deleting a baseline	21
Configuring components	21
Using the Nodes screen	21
Selecting multiple nodes	22
Adding a node	22
Editing a node	25
Aborting a node update	25
Node inventory	25
Deploying a node	26
Deploying all partitions in an HP Integrity BL870c i4 or BL890c i4 node	27
Node reports	28
Deleting a node	28
Server overview	29
Integrity node overview	29
Using the Enclosures screen	29
Adding an enclosure	29
Editing an enclosure	29
Aborting an enclosure update	29
Enclosure inventory	30
Deploying an enclosure	30
Enclosure reports	30
Deleting an enclosure	30
Using the Servers screen	30
Adding a server	30
Editing a server	30
Aborting a server update	30
Server inventory	30
Deploying a server	31
Server reports	31
Deleting a server	31
Using the Switches screen	31
Adding a switch	31
Editing a switch	31
Aborting a switch update	31
Switch inventory	31
Deploying a switch	31
Switch reports	32
Deleting a switch	32
Using the VM Hosts screen	32
Adding a VM host	32
Editing a VM host	32
Aborting a VM host update	32
VM hosts inventory	32
Deploying a VM host	32
VM host reports	32
Deleting a VM host	33
Using the iLO screen	33
Adding an iLO	33
Editing an iLO	33
Aborting an iLO update	33
iLO inventory	33
Deploying an iLO	33
iLO reports	33
Deleting an iLO	33
Using the Intelligent Power Distribution Units screen	33
Adding an iPDU	34
Editing an iPDU	34
Aborting an iPDU update	34
iPDU inventory	34
Deploying an iPDU	34
iPDU reports	34
Deleting an iPDU	34
Using the Virtual Connects screen	34
Adding a Virtual Connect	34
Editing a Virtual Connect	35
Aborting a Virtual Connect update	35
Virtual Connect inventory	35
Deploying a Virtual Connect	35
Virtual Connect reports	35
Deleting a Virtual Connect	35
4 Using legacy scripts to deploy updates	36
Command-line interface	36
Command-line syntax	36
Using Linux root credentials	36
Prerequisites for using Linux root credentials	36
Switch update commands	37
Command-line arguments	37
Command-line examples	45
Return codes	46
Windows smart-component return codes	47
Linux smart-component return codes	47
Linux RPM return codes	48
VMware ESXi smart-component return codes	48
Input files	48
Input file format and rules	49
File encoding	49
Error reporting	50
Input file parameters	50
Reports	61
Downloading HP SUM and components from the SDR	62
5 Advanced topics	63
Configuring IPv6 networks	63
Network ports used by HP SUM	63
GatherLogs	64
6 Troubleshooting	65
Collecting trace directories	65
Baseline troubleshooting	66
HP SUM lists SUSE Enterprise Linux dependencies for Red Hat Enterprise Linux systems	66
HP SUM displays two versions of the same component when creating a custom baseline	66
HP SUM stops responding when performing inventory on large baselines	66
HP SUM does not return an error when you enter incorrect credentials forDownload from hp.com	66
Node troubleshooting	66
HP SUM does not respond when editing a node with sudo	66
HP SUM does not display the Deploy button on the Deploy Nodes screen	67
An HP-UX node displays the error Inventory failed. The pciinfo module requires manual update on remote target	67
HP SUM does not detect solid state hard drives	67
After HP SUM finishes an inventory, the inventory screen does not close	67
Cannot add a Windows node when running HP SUM on a Linux host	67
HP SUM does not display the Reboot button after it finishes a deployment	67
HP SUM does not automatically reboot a node	67
HP SUM does not display a reboot message in Guided Update	67
When multiple nodes are selected, HP SUM does not display the most correct status	67
HP SUM displays message Unable to locate the item you requested	67
HP SUM stops responding when performing inventory on multiple nodes	67
HP SUM displays the message Unable to login or identify node as a supported device when HP SUM cannot find a node	67
HP SUM displays the message Ready for deployment while HP SUM is performing inventory on a node	68
HP SUM does not display an entire screen	68
HP SUM displays extra credentials boxes on the Edit Node screen	68
You can edit a node while HP SUM is deploying updates to the node	68
HP SUM displays an associated node multiple times	68
HP SUM automatically performs inventory on a node after editing the node	68
Activity screen troubleshooting	68
HP SUM does not update the Activity screen accurately	68
VMware troubleshooting	68
HP SUM displays an inventory error on a VMware node	68
Reports troubleshooting	68
HP SUM does not generate reports for nodes that are offline	68
HP SUM displays only requested reports in CSV and XML format	68
HP SUM service troubleshooting	69
HP SUM service stops running when HP SUM is mounted from a virtual media source	69
HP SUM allows all users to log in	69
Some screens are not translated from English	69
Legacy CLI commands troubleshooting	69
HP SUM does not deploy multiple components at in one command	69
The /use_web Legacy CLI command does not work	69
7 Support and other resources	70
Contacting HP	70
Subscription service	70
Related information	70
Typographic conventions	71
HP Insight Remote Support software	72
HP Insight Online	72
8 Documentation feedback	73
Glossary	74

Match case Limit results 1 per page

For parameters that can take list values, list separators can be commas, semicolons, or spaces.

NOTE:

The credentials can be omitted from the file for greater security and passed on the

command line to HP SUM. The only limitation that the user ID and credentials must be the same

on all.

When the file has been created, to use it with HP SUM, add it as the

inputfile

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

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

host's login credentials to log in to one or more remote nodes, you can do so by setting

the variable

USECURRENTCREDENTIAL

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.

File encoding

To allow for the inclusion of double-byte characters, the input file is in UTF-8 format.

Input files