Eventhough credential is working for Network device but getting active but couldn't classify
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hi all
I am facing error during discovery of one of network device for my client.
When testing the credential for that ip credential is showing working.
Now when I run the discovery against that IP i am getting the below error
Please suggest me the solution if any to this so that i can resolve it
Thankyou.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @Dipakkumar123 ,
The Active, couldn't classify error in ServiceNow Discovery typically indicates issues with credential configuration, port accessibility, SNMP classification criteria, concurrent discovery attempts, MID Server configuration, or device specific settings......
To resolve this, verify that the correct credentials are configured and accessible, ensure necessary ports are open, check the SNMP Classifications table for the device's sysObjectID, and review the Discovery logs for detailed error messages........
If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.
Kaushal Kumar Jha - ServiceNow Consultant - Lets connect on Linkedin: https://www.linkedin.com/in/kaushalkrjha/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I have checked that 161 port is opened and credential is working if checked for that IP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Are you using the same MID server to validate credentials and to run discovery?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Also consider the device while may answer sysdescr (the test) it may not be able to handle all the other queries that come from the classification probe. Work with the network admin to confirm their SNMP is running correctly and/or look at a packet capture to see if there are any rejects when trying classification.