Device discovery fails with inaccessible state
search cancel

Device discovery fails with inaccessible state


Article ID: 143914


Updated On:


CA Infrastructure Management CA Performance Management - Usage and Administration DX NetOps


DX NetOps Performance Management is not collecting metrics on the device because it is shown as inaccessible in the discovery profile history.


All supported DX NetOps Performance Management releases


Device and/or network issues.


Try the following tests from the Data Collector that will be used to discover and manage the device. If both fail it validates the problem is environmental. Are there firewalls or ACL's or other tools controlling communications that might be causing the problem?

  1. Ping the device
  2. Run a MIB dump against device using the sapwalk2 utility or the snmpwalk command.

See more in the SNMP Querying Tools section of the documentation.

Additional Information

Also you can looking in the Data Aggregator logs:

INFO  | 6dcf-thread-3457 | AAAA-MM-DDTHH:MM:SS,NNN | DeviceDiscoveryTask | scovery.impl.DeviceDiscoveryTask 1723 | .im.aggregator.discovery |       | x.x.x.127 (64691546)'s primary IP was the network ID or broadcast address. It will be deleted.

It seems the IP address of the device (x.x.x.127) matches the broadcast IP address of one of the networks discovered in the device. We consider that as non valid IP address

Device information:

To confirm run snmpwalk:
snmpwalk -v 2c -c <ro_community_name> <ip_address>
Note: A good approach is looking for these 2 classes in karaf.log in Data Aggregator

DeviceDiscoveryTask - This is triggered when a discovery is issued 
ProfileDiscoveryTask - This is triggered when a profile rediscovery is needed because there have been 2 consecutive failed polls