Not really - other people having been using SNMPv3 with no problems.
I assume you have made sure you have the security parameters correctly set up. Have you tested the SNMP credential through the UI rather than performing a discovery? What are you trying to discover?
Yes, you are right. we have also discovered more than 1000 + NW devices with same settings.
But for more than 400+ devices we are facing problem. SNMP credential test showing same error. Our network team is sure that they set correct parameter for these devices. Even we have reconfigured couple of devices but facing same SNMP time out error.
What kinds of devices? Printers? Routers? What manufacturer? You are really not giving us anything to be able to help you.
When you say that snmpwalk works, are you doing it from the scanner itself? The reason I ask is because many people who implement v3 usually put on an ACL to block unwanted eyes from even getting a response.
Do they have all have same SNMP V3 Engine ID?
to test this execute below steps:
1) Restart tideway service
2) After restart scan one device which is failing. If it gets discover then go to Device Info on Discovery Access and note down its Engine ID.
3) Restart tideway service once again.
4) Scan different device which was failing. If it gets discover then take a look at its Engine ID same as what you have done in step 2.
If both device has same Engine ID then you will have issue mostly.
Yes we are doing snmpwalk from scanner it self..
Yes I'v checked and found both devices has same engine ID.
How to tackle with the issue.
It's very old issue and there is no solution for the same.
Please ask your network team to change it as it can be changed by NW team only.
Do we have any solution on this SNMP Engine ID issue ?