User guide

Key Considerations 103
Problems Importing from HP OpenView
If you encounter problems importing from HP OpenView, ensure that you
have HP OpenView services running so that 3Com Network Administrator
can connect to the HP OpenView database.
If the import operation encounters this problem it will be reported in the
Import report.
Refresh Problems Any problems encountered during refresh are listed in the Refresh report.
These all relate to problems encountered when reading live information
from the devices on the network.
■ Devices did not respond to a ping — if this occurs:
■ During a refresh operation which is running as a result of an
import, the device will not be added to the inventory.
■ During a refresh on a device already in the inventory, its details will
not be modified.
Check that the part of the network to which the device is attached is
accessible from your workstation. From the command prompt, try
pinging the device and its neighboring devices. The Tracert command
may also help in determining where the problem is in trying to contact
the device.
■ Failed to establish the device as being a 3Com device — a failure
can occur if:
■ The device did not respond to SNMP — this is most likely due to
the read community string being incorrect. It was either incorrectly
specified in the CSV file or (if importing from HP OpenView) it has
changed since it was last discovered in HP OpenView.
■ The device responded to SNMP but was detected as being a
non-3Com device — this is either because you inadvertently
included a non-3Com device in the CSV file or (if importing from
HP OpenView) you have replaced the device since it was last
discovered in HP OpenView.
In either case, if this was detected during a refresh operation as a
result of an import, the device will not be added to the inventory. If
this was a refresh on a device already in the inventory, its details will
not be modified.
3Com Network Administrator for HP OpenView.book Page 103 Wednesday, November 12, 2003 2:33 PM