13 managed system names – HP Insight Control Software for Linux User Manual
Page 19
1.13 Managed system names
HP Insight Control for Linux command line commands recognize managed systems by the
following name types.
Description
Managed system name type
The name assigned to the managed system when the Linux OS was installed on it, if
a name was assigned.
HP SIM recognizes managed systems by this
Host name
The managed system host name with the domain name appended, for example,
earth.example.com
. In this document, example.com is the domain name used in
command and screen examples.
Fully qualified host name
The internal name HP Insight Control for Linux assigns to a managed system. The
Insight Control for Linux name naming convention is {collection name}{0–9999},
where:
•
collection name
is the Insight Control for Linux default or user-defined name
you assigned as the collection name during the Insight Control for Linux installation
process.
•
0–9999
is a number that is arbitrarily assigned to the managed system during the
Insight Control for Linux installation process. Numbers are assigned sequentially.
For example, if the collection name is icelx, the Insight Control for Linux internal
names are icelx1, icelx2, icelx3, and so on.
For a description of how internal names can change when managed systems are added
to or removed from the Insight Control for Linux collection, see
Insight Control for Linux
internal name
1.13.1 How HP Insight Control for Linux assigns node names
HP Insight Control for Linux internal names are assigned when you configure or reconfigure
management services through the following menu item:
Options
→IC-Linux→Configure Management Services
This task creates a nodenumbers file which stores the associations of managed systems to their
internal name. The location of this file is /opt/hptc/database/etc/collection_name,
where collection_name refers to the Insight Control for Linux collection for the managed
systems.
In general, if you add new managed systems to the Insight Control for Linux collection, the new
managed systems are assigned with the next available name. For example, if the internal names
icelx1
, icelx2, and icelx3 are already assigned to three managed systems, the new managed
system is assigned the internal name icelx4, and so on. If a managed system is removed from
the collection, its internal name is not reused unless it is for the same managed system when it
is added back.
You can influence internal node numbering by understanding and editing or creating the
/opt/hptc/database/etc/collection_name/nodenumbers
file, where collection
refers to the collection for the managed systems. The internal node name is generated by
concatenating the name of the collection and the node number.
When you run the Options
→IC-Linux→Configure 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 existing 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 contents of the file. If there are any new managed systems,
they will be added to the list automatically. Servers that are no longer managed by Insight
Control for Linux remain in the list.
1.13 Managed system names
19