Discovery SNMP devices - Getting 'Active couldnt classify'

[jasonbrough]

Getting some strange behaviour when discovering SNMP devices. In this case, I am trying to discover any switch / router device on a subnet. I have created a schedule using the 'SNMP only' behaviour and allocated the subnet range.

Taking a random device found on the network as an example, when I run the schedule it finds the device and tries to classify it but fails with 'Active couldnt classify'.

However, when I run a quick discovery against the device, it classifies it fine and the status changes to 'Update CI'. It is as though when running a schedule, it cant complete the classification properly. Any thoughts anyone?

*** I'm also seeing a lot of these:

SNMP probe timed out. Target is either unreachable or there are no valid credentials for it.

[jasonbrough]

OK. I increased the snmp timeout values so that it has longer to query the devices. I also changed the max.threads value to 5, instead of 25. So its now taking longer, but most of the errors above have gone.

However, I'm getting a few devices which cannot classify because it appears as though the oid's are missing. Here is an example of an snmp classification input:

But there are no oid's starting with 1.3.6.1.2 in our instance and I'm assuming that is why it cannot classify. Any thoughts?

[cyked]

Can you post the entire XML input you posted above.   You pulled the probe input that likely says SNMP Classify - 0 OIDs, correct?

[jasonbrough]

I cant paste all the XML as it has customer info but this is the output from the discovery. As you can see it found 137 oid's:

[cyked]

Fair enough.   What kind of device is this, do you know the organization OID structure for the device and is that showing up in the 137 OIDs where you'd see manufacturer and model type detail a line or two below the OID?   That OID would allow you to create a new SNMP OID entry and specific Manufacturer/model.

If its not classifying you either don't have an OID for it, or the OID used in the SNMP OID record isn't the correct one.