Discovery issues / errors

[Jim Teller]

I am running discovery on specific IP ranges for our F5's.  The team who manages the F5's has entered SNMP credentials on the device side, and our discovery schedule is set up to discover Configuration Items and we have our SNMP version set to 'all' under the Advanced section.  Our discovery output for the large majority of devices is 'Active, couldn't classify' in the 'Completed Activity column'.  When we run the discovery in our dev environment, the majority of the messages in the issues section under the Devices tab are 'no valid credential found' and/or 'SNMP Probe timed out.  When we run the same discoveries in our test environment, the messages are different but still it's not discovering devices that we know are live.... still getting 'Active, couldn't classify' for the majority of devices, and the issues messages are:  "Cannot connect, status is SSH Failure.  Seems odd that we aren't seeing any messages about SNMP in the test environment, but that aside, I'm looking for suggestions as to why we're not seeing the devices.

[RaghavSh]

I have faced this issue, the reason was no complete access to the devices/ports.

The basic communications ports are open so you are able to get through and get device status as active but to classify the devices access to higher ports is required.

If i am not wrong you might ne getting logs like active not classifying? or something similar.

For start get the complete access for a particular IP and run quick discovery on that and check if you can see that in you cmdb table.

Do mark the answer correct/helpful accordingly.

[Jim Teller]

Thanks Raghav.  When you say 'get the complete access for a particular IP', what do you mean exactly?  If the issue is that I need access to higher ports, are we talking about a firewall rule or whitelist?  The only port I thought we needed to have open was 161 for SNMP...?

[RaghavSh]

161 is basic port like 135 for windows, it will help you communicate but not discover or classify them.

I am not exactly sure about the port numbers as of now but that is worth checking in this case.

[Pratik Mehta]

Hi Jim,

Try configuring the discovery with behaviour so that it doesnt attempt SSH connection. i think the port doesnt have issue here since its found as 'Active'. try the 1st option i mentioned and in parallel also check with your network admin if the SNMP settings are done correctly and MID server IP is whitelisted...