Comments
-
It shouldn't be stuck on v7.2.2, since you said you recently upgraded, are the initializing requests from the previous version? Either way, close all processes, you can go into the database and delete them. I found the exact directions on one of the discussions which I can't find right now, but this discussion also talks…
-
For SolarWinds to use for polling and also download configs, but the only way I know of to do that is with SNMP R/W access. Is there another way?
-
shawn_b, I am having the same issue with my Cisco switch. I'm using SNMPv3 which passes the test, but do I also need to set up a connection profile?
-
Thank you for your fast response, unfortunately, it still did not fix the issue and I'm getting the same error. I even tried changing port # to see if it would resolve any but still no luck and getting the same error message.
-
If you can't use Engineer's Toolset, what can you use to schedule backup
-
That worked, thank you so much!
-
The NCM devices were discovered using SNMPv3, and Engineering toolset also used SNMPv3. Do I need to change the device information?
-
Did you ever find a solution to this problem? I am running into the same error message while trying to finish Orion Configuration Wizard.
-
I have been trying to enable SNMP access on the ASA firewalls but can only get read access. Is there a way make it read/write access, perhaps through ASDM? Sorry for asking the question here but it is a predecessor to your question.
-
Just a suggestion, you can export the IP list, in an Excel file, change what you need to change in the excel sheet and import it back.
-
Were you able to resolve the problem? I am getting the same error message while trying to do Orion Configuration for NCM
-
If you're asking about downloading configs when they're changed in real time, they have it in the manual: http://www.solarwinds.com/documentation/orionNCM/docs/OrionNCMAdministratorGuide.pdf on page 135. It's quite a read but if you read through it carefully it becomes easy.
-
Also, you can open up the SQL server configuration manager and delete the old database and when going through the configuration just create a new one