HP Network Direr Software Products manual Discovery Report Errors and Warnings

Discovery Report Errors and Warnings 145

Network Director failed to detect any routers whose ARP caches contained entries for the MAC addresses, possibly because they are outside the ranges of addresses you specified. Alternatively, the appropriate router may have been discovered as an IP-only node if a valid read community string was not provided for the router in the Network Discovery wizard.

The consequences of this failure are that any IP-only nodes will appear at the top of their submap, not connected to anything. Another node may also appear within the map that just has the correct MAC address of the node and is connected to the correct switch port.

3Com Network Director was unable to determine the write community string for the following SNMP devices

As part of the Device Capability Stage, 3Com Network Director attempts to validate the write community strings for certain devices. See “Device Capability Detection ” on page 93 for further information. 3Com Network Director only attempts to do this for devices that it thinks it will need write access to in the future (e.g. to set up the trap table for monitoring for use by administrative tools such as Agent Update). If all attempts to validate the write community strings fail then this message is logged.

Multiple responses were detected during discovery from the IP addresses listed below

During the IP Ping stage, 3Com Network Director sends an ICMP ping message to each device IP address in the ranges specified for the subnet it is currently detecting. It does not send ICMP ping messages to the subnet address or broadcast address. If 3Com Network Director receives more than one response from an ICMP ping message then it assumes that this must be a broadcast address on the subnet and does not attempt to discover or manage any devices using that IP address.

This may occur if one or more devices on the subnet have their subnet mask configured incorrectly, or if the subnet address and mask were entered incorrectly in the Specify Subnets pane of the Network Discovery wizard.