HP -UX B6941-90001 Administrator's Reference Manual page 402

Tuning, Troubleshooting, Security, and Maintenance
Troubleshooting: Specific Problems
Using /etc/hosts on :
Name: jacko.bbn.hp.com
Address: 15.136.123.138
Aliases: jacko
Note that this command only returns the first IP-address when using
/etc/hosts as the name service.
The managed node uses the IP-address of the first network interface
card it finds (by scanning the internal network interface list). The order
of the network interfaces depends on the interface type installed on the
managed node. For example, if an X.25 and an Ethernet interface are
installed, the IP-address of the X.25 interface is used by the managed
node, since this interface comes before the Ethernet interface in the
internal network interface list.
If the management server has stored the IP-address bound to the
Ethernet interface of this managed node in its database, but the name
service the management server uses has no association to the X.25
IP-address of the managed node, a message sent by this managed node
will be rejected.
For example, if the managed node jacko.bbn.hp.com has the
IP-addresses 193.1.1.1 for the X.25 interface, and 15.136.120.169 for the
Ethernet interface. The name service used by the managed node is
displayed as follows:
/etc/hosts
----------
15.136.120.169 jacko.bbn.hp.com jacko_15
193.1.1.1 jacko.bbn.hp.com jacko_x.25
The name service used by the management server has the following
entry for jacko. bbn.hp.com:
/etc/hosts
----------
15.136.120.169 jacko.bbn.hp.com jacko
In the above scenario, as the message contains the IP-address 193. 1. 1.1
which is not known on the management server, a message to the
managed node jacko would be rejected. There are two ways to resolve
this problem:
1. Add the second X.25 IP-address to the management server's name
service:
402
jacko
# Ethernet
# X.25
Chapter 10