Ranges are not always working for discovery

Document ID : KB000092984
Last Modified Date : 25/04/2018
Show Technical Document Details
Issue:

Range based discovery does not discover all devices in that range provided.

Environment:
CAPM 3.x
Cause:

ACRONYMS:

MF - Metric Family

VC - Vendor Certification

MIB - Management Information Base

OID - Object Identifier - part of a MIB

Cause: 

During discovery we discover the Network Address MF, which results in 1 of 4 VC being supported.  We read the OIDs in the supported VC.  This table is read into NetworkAddressInfo.IP Addresses attribute.  We use this to check against the primary IP discovered during range discovery.  The primary must exist in the IP address list.

..

In targeted (by address) discovery, we do not make that check.

Resolution:

1.    Make sure that the management IP is not loopback and is in the ‘IP address list’ for the device.

2.    Use address discovery and add all the addresses from the range to the profile.