HP OpenView Operations Administrator's Reference - filibeto.org

Maintaining OVO
Changing Hostnames and IP Addresses in a Cluster Environment
Changing Hostnames and IP Addresses in a
Cluster Environment
It is not uncommon for a node in a cluster environment to have more
than one IP address and hostname. If a node becomes a member of
another subnet, you may need to change its IP addresses. In this case,
the IP address or fully qualified domain name may change.
NOTE For the HTTPS-based Windows nodes, you can also specify the IP
address as dynamic. You can do this from the Add/Modify Node window.
In general, on HP-UX and Solaris systems, the IP address and the
related hostname are configured in one of the following:
❏ /etc/hosts
❏ Domain Name Service (DNS)
❏ Network Information Service (NIS on HP-UX, NIS+ on Solaris)
OVO also configures the hostname and IP address of the management
server for the managed node in the management server database.
If you are moving from a non-name-server environment to a name-server
environment (that is, DNS or BIND), make sure the name server can
access the new IP address.
Hostnames work within IP networks to identify a managed node. While a
node may have many IP addresses, the hostname is used to pinpoint a
specific node. The system hostname is the string returned when you use
the UNIX hostname(1) command.
NOTE Using virtual nodes in OVO/UNIX requires that all nodes (physical and
virtual) are of the same platform type (DCE or HTTPS).
Changing the agent type when upgrading from DCE to HTTPS must be
done in a very short time frame for all nodes (minutes!). Note that all
agent types must be of the same type also after the migration.
Chapter 13 563