HP OpenView Operations Administrator's Reference - filibeto.org

Tuning and Troubleshooting OVO
Solving OVO Installation Problems with Multi-homed Hosts
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 used by the management server has no association to the X.25 IP
address of the managed node, a message sent by this managed node will
be rejected.
Problem
For example, if the managed node jacko.deu.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 following happens:
❏ Managed Node
The name service used by the managed node is displayed as follows:
/etc/hosts
----------
15.136.120.169 jacko.deu.hp.com jacko_15 #
Ethernet
193.1.1.1 jacko.deu.hp.com jacko_x.25 # X.25
❏ Management Server
The name service used by the management server is displayed:
/etc/hosts
----------
15.136.120.169 jacko.deu.hp.com jacko
In this scenario, as the message contains the IP address 193. 1. 1.1 which
is not known on the management server, a message from the managed
node jacko would be rejected.
There are two ways to resolve this problem.
Chapter 11 469