- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2020 11:49 PM
Device is discovered. but getting error in discoverey logs
(empty) | IP Switch | Classified | Identifying |
| Completed 3 |
Solved! Go to Solution.
- Labels:
-
Discovery
-
Multiple Versions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2021 11:49 PM
Hi Everyone,
Thanks for all your input. The provided solution are already check for the reference what we have found.
In windows server some time port exhaustion happen cause this issue in my case.
Best Regards
Gin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2020 12:28 AM
Kindly make sure correct SNMP credential are added.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2020 12:42 AM
i am getting OID in ecc
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2020 12:32 AM
Hi,
Kindly make sure that the device is up and is reachable for the vm where the concerned mid is added. Try using snmp browser too or snmp walk to query the device using the snmp credential that ia added in servicenow. This will confirm wether your device is reachable from the mid or not.
Agreed with Aditya, so make sure correct snmp community credentials are present.
Hoe this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2020 12:43 AM
i have tested the credentials & getting OID's & in device details it is showing ip switch. rest i will try for walk as well