Discovery SNMP devices - Getting 'Active couldnt classify'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-25-2016 06:33 AM
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.
- Labels:
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-25-2016 07:46 AM
Hi Jason,
Could you tell me where should we increase the time out value for SNMP Probe. Also by doing so aren't you seeing the warning message "SNMP probe timed out. Target is either unreachable or there are no valid credentials for it" now. I am also seeing lot of warning messages as this in my instance.
Best Regards
Chowdhary
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-25-2016 09:22 AM
Hi Chowdhary
http://wiki.servicenow.com/index.php?title=MID_Server_Configuration#SNMP_Discovery_Parameters
thanks
Jason
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-25-2016 09:49 AM
Thank you Jason!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-16-2016 02:39 AM
Hi Kumar
Try this way
Follow these instructions(may be it will be helpful)
1) first check the snmp is installed or not in your system
2) check the snmp is enable/disable at target mission(if it is disable we cannot discover)
2) ask to your admin, is there any changed community string password(if it is not a public)
3) check the snmp devices are connected same network(some companies uses different networks for OS Devices and Network Devices)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-16-2016 05:07 AM
Thank you very much Vamsi for the info.
Best Regards
Chowdhary