SNMPv3 passwords change

Is the device status polled by SNMP? Could be that there's an issue or mismatch with the configuration in SolarWinds compared to the device

Hi sum_giais ,

Sorry, i'm quite new to Solarwinds, how do i check if the device is polled by SNMP?

Hi Zack, did the device poll before the change to your passwords was made? 

Go to the node details view and list the resources, and under status and response time is how status is polled.

documentation.solarwinds.com/.../core-viewing-node-resources-sw2375.htm

Edit: Thinking about this now - if snmpv3 configuration is broke to the node you won't be able to list the resources (unless there's a recent cache of it.)

You'll need to adjust the links below for your environment.

Go to the manage pollers view at https://solarwinds_platform/Orion/Admin/Pollers/ManagePollers.aspx and in the group by drop-down at the left change it to Technology. Then select "Status & Response Time", then in the Assignments column click link for the "Status & Response Time SNMP".

Or a direct link: https://solarwinds_platform/Orion/Admin/Pollers/EnableDisablePollers.aspx?poller=Core.Node.StatusResponseTime.Snmp&groupBy=PollerStatus&groupByValue=Enabled

If you see the node in the list that you're having an issue with and it shows enabled, that'll tell you if the node is polled via SNMP. In which case the credentials in SolarWinds don't match the node and causes it to not respond showing down.

Hi ramaiya2 ,

So the story is like this, correct me if i'm wrong, so this SNMP password change needs to be done on both sides, one done by another engineer on the devices end and myself done on the Solarwind platform, so when this engineer change the password, i noticed that all nodes are down in the Solarwind platform, so back to ur question, i didnt make any changes in the polling

Hi, 

To add on above, after changing the password, should i do a rediscovery or poll now?

just poll now

Hi donrobert5 ,

Even after i click poll now for the devices, in Solarwinds showing node is down, could you advice what is the issue?

how did you try to edit the snmpv3 password in solarwinds? when you changed it, have you tried to re test the credential first?

i edit the passwords individually under the edit properties, fyi, i know i can do it via manage snmpv3 credentials option, issue is as the username are  the same for some other agency, i do not know if i will be changing the correct agency and devices

Start with one device and ensure it is monitored via SNMP in the first place - check that by going to 'Edit Properties' for the node. You will see something like this. Bits picked out in red are what you will have been provided by the change engineer.

Once the details are entered, then just below that is a 'Test' button. Click that. If it doesn't come back as a green box with the word Successful in it then you have an issue. And that issue usually boils down to one of perhaps two (maybe 3) things:

1. one of you has mis-entered the SNMP v3 credential information
2. communication via SNMP is blocked (if this node worked via SNMP v3 before then you can likely ignore this, but don't discount it totally)
3. A 'method' mis-match. This is happening more and more as folks move to more secure "methods" (as SolarWinds calls them, but otherwise known as encryption) that SolarWInds can't yet support. So make sure the encryption methods match.

Bottom Line: it sounds like you now have a mis-match between the device SNMP details and the node in SolarWinds SNMP details.

Start with one device and ensure it is monitored via SNMP in the first place - check that by going to 'Edit Properties' for the node. You will see something like this. Bits picked out in red are what you will have been provided by the change engineer.

Once the details are entered, then just below that is a 'Test' button. Click that. If it doesn't come back as a green box with the word Successful in it then you have an issue. And that issue usually boils down to one of perhaps two (maybe 3) things:

1. one of you has mis-entered the SNMP v3 credential information
2. communication via SNMP is blocked (if this node worked via SNMP v3 before then you can likely ignore this, but don't discount it totally)
3. A 'method' mis-match. This is happening more and more as folks move to more secure "methods" (as SolarWinds calls them, but otherwise known as encryption) that SolarWInds can't yet support. So make sure the encryption methods match.

Bottom Line: it sounds like you now have a mis-match between the device SNMP details and the node in SolarWinds SNMP details.

Should have said - after you get the green test ok you must scroll to the bottom and hit submit. You will get a popup asking you to confirm the change to polling. After that, your device should just continue to poll, but now via the new credentials

Hi stuartd ,

I have done the test and it shows connection failed

Apart from all the information here, try to do an SNMPwalk and if that works while it is still failing on orion web console, then it's time to open an ticket.

https://solarwindscore.my.site.com/SuccessCenter/s/article/Troubleshoot-connectivity-and-MIB-issues-with-SolarWinds-SNMP-walk-IPv4-only?language=en_US

If it also fails on the SNMPWalk, then it would be either credential issue or network