- 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 06:35 AM
Try to increase the mid.snmp.request.timeout parameter of a mid server, restart the mid, and run a quick discovery using that mid server.
Last time I fixed the "same" error by setting mid.snmp.request.timeout to 10000.
Hope this helps.
- 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