Table of Contents
Advertisement
Tuning, Troubleshooting, Security, and Maintenance
Troubleshooting: Specific Problems
returns:
PING 193.1.4.1: 64 byte packets
----193.1.4.1 PING Statistics----
3 packets transmitted, 0 packets received, 100% packet loss
after pressing Ctrl-C. This indicates that no connection was possible
using address 193.1.4.1.
If the following scenario were to exist:
Management Server
lan1:15.136.120.2
arthur.bbn.hp.com
lan0:194.1.1.1
Managed Node
jacko.bbn.hp.com
lan1:15.136.120.1
lan0:193.1.1.1
The managed node and management server both have two LAN
interfaces, but are only connected through the 15.136.120 subnet. There
is no route from the management server to the managed node through
the 193.1.1 subnet, or from the managed node to the management server
through the 194.1.1 subnet respectively.
To use a specific subnet in this environment, you must select the
IP-address of the managed node manually from the GUI. In the above
scenario the communication should be bound to subnet 15.136.120. You
can select the appropriate IP-address from either the Add Node or
Modify Node window of the ITO administrator (the management
server's name service must contain both IP-addresses for the node
jacko.bbn.hp.com).
On the managed node, you must edit the opcinfo file in the platform-
specific install directory (for more information, see Table 10-3 on page
399). To set the path which the managed node uses for communication
with the management server, specify the following parameter in the
opcinfo file: OPC_RESOLVE_IP 15.136.120.2. A corresponding
opcinfo file could then look like the one shown in the following
example:
404
Chapter 10
Advertisement
Table of Contents
Troubleshooting
