HP Insight Control for Linux 6.0 Installation Guide

fixed-address 192.0.2.27;
option host-name "server001-cp";
}
# iLO2 console port from server 2
host server002-cp {
hardware ethernet 00:1E:0B:76:54:9C;
fixed-address 192.0.2.22;
option host-name "server002-cp";
}
}
1
This host name must agree with the DNS look up name or the host name entry if it exists in
the /etc/hosts file. If this server is the CMS, this value must match the output of the
hostname --fqdn command.
2
-cp means this is the "console port". You are not required to use this naming convention,
but you must be able to identify the console port.
4.3.2.1 Network modifications required by SLES OSs
On SLES OSs, you must modify a network configuration file in order for the managed system
to accept the host-name parameter as the host name. To make this modification on the managed
systems, follow this procedure:
1. Use a text editor to open the /etc/sysconfig/network/dhcp file.
2. Find the line that looks like this:
DHCLIENT_SET_HOSTNAME="no"
NOTE: The Insight Control for Linux installation process automatically set this value to
no.
3. Change the value to yes:
DHCLIENT_SET_HOSTNAME="yes"
4. Save your changes and exit the text editor.
4.3.2.2 Translating IP Addresses to host names
In addition to configuring DHCP to provide fixed addresses, those fixed addresses must translate
to valid host names, either in DNS or in a local /etc/hosts file on the CMS. This enables
Systems Insight Manager to be able to properly identify the managed systems and display their
host names rather than just their IP addresses.
If managed systems are on a public network with a DNS server, you can configure that server
to map the assigned addresses to the appropriate names.
If the managed systems are on a private network, similar to the two-tier topology shown in
Figure 4-1 (page 31), or if your network does not have a DNS server, add the managed system
IP addresses and names to the local /etc/hosts file on the CMS.
The sample /etc/hosts file shown in Example 4-3 corresponds to the dhcpd.conf
configuration file shown in Example 4-2 (page 34).
Example 4-3 /etc/hosts file with managed system names
# Sample /etc/hosts file
127.0.0.1 localhost.localdomain localhost
192.0.2.1 icelinux-cms
192.0.2.21 server001
192.0.2.22 server002
4.3 Configuring a DHCP server 35