HP Insight Control for Linux 6.2 User Guide

When you run the OptionsIC-LinuxConfigure Management Services task, it determines
if this file exists:
If the file does not exist, it creates the file and assigns numbers based on the managed systems
and the current numbering scheme. The Central Management Server (CMS) is always node
number 1.
If the file already exists, the configuration task reads the nodenumbers file and assigns the
node numbers according to the file contents. If there are any new managed systems, they
are added to the list automatically. Servers that Insight Control for Linux no longer manages
remain in the list.
Removing a managed system does not change the numbering scheme.
If you want to reuse a node number, remove it from this file and reconfigure the Insight Control
for Linux Management Services with the OptionsIC-LinuxConfigure Management Services
menu item.
There are three fields in each non-blank or non-comment line in this file; they are:
number name GUID
Where:
number
Is the node number of the managed system. This number must be nonnegative.
name Is the name HP SIM uses to identify the managed system, for example, mars.
GUID
Is the globally unique identifier for that managed system. This field is optional but,
if provided, it overrides the name field. This is particularly effective if you want to
ensure that a specific managed system always has the same internal node name, even
if it is renamed.
You can obtain the GUID for a given managed system with the following command:
$ mxnode -ld nodename | grep GUID
GUID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
The following rules apply:
The managed systems can be listed in any order in the file; that is, order does not matter.
The configuration task reorders the file.
You are allowed to have gaps in the numeric sequence.
If a number is repeated with different names or GUIDs, only the first instance in the file is
used. Subsequent entries with that number are lost.
If two entries have the same GUID, only the first entry is used.
Comment lines begin with a nonnumeric character, usually #, in the first field.
Blank lines and comments are ignored and, thus, are not preserved.
The following is an example of an edited nodenumbers file:
# Nodenumbers file
1 earth xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
3 mercury
4 mars
5 pluto nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn
The configuration task assigns these managed systems internal node names as follows:
earth icelx1
mercury icelx3
mars icelx4
pluto icelx5
Where icelx is the collection name.
1.11 Managed system names 21