This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

NPM is using SNMP community="public"

greg.gutman.nih.2018 over 5 years ago

We are seeing a strange behavior, where Solarwinds NPM 12.2 is using SNMP community string "public" even after it is explicitly configured for something else. Meaning it is polling the device using the right community string, but from time to time it also tries and fails using the "public"

NPM is successfully polling the devices, but then for sometime, periodically tries SNMP v2c Community String: public about 4 times a day, every day, 4-5 hours apart.

Splunk records the event from the device, where this failure happens. Solarwinds Event logs do not show this happening.

logdesc="SNMP query failed" community="public"

Question for the community and Solarwinds gurus

Why would NPM utilize public string on a devices that is explicitly configured for a different string?

How or what needs to be tweaked to stop this non-critical but undesired NPM behavior?

Top Replies

0 dgsmith80 over 5 years ago

Hi Greg,
Is it possible that you have a scheduled discovery setup which scans this device, but you have the public string higher in the priority order than the current string?
Like this:
In the above scenario, SolarWinds would be scanning your device every time that discovery runs and attempting to connect using the public SNMP credentials. When it fails it will move down the list to the next entry until the connection is successful.
This would show an SNMP Failure on your device
Cancel
Vote Up 0 Vote Down

Cancel
0 greg.gutman.nih.2018 over 5 years ago in reply to dgsmith80

Hello David,
This is a good idea! However in this scenario, this is not the case.
It could be other users are running ad-hoc discovery scans, searching through the Solarwinds Events (Discovery Profile *) that turns out to not be the case either.
Cancel
Vote Up 0 Vote Down

Cancel
0 pratikmehta003 over 5 years ago

i had similar issue when i ran the discovery for a set of devices... the string public had higher priority and it was taken first... in 1-2 nodes i could see the device having public as the comm string when i clicked on edit properties..
You may want to re-check this again...
Cancel
Vote Up +1 Vote Down

Cancel
0 jamison.jennings over 5 years ago

Do you also have Network Topology Mapper? Similar type of discovery happens with it to make maps
Cancel
Vote Up +1 Vote Down

Cancel
0 greg.gutman.nih.2018 over 5 years ago

Stumbled on the the setting it was under the Admin settings for IPAM. I appears to be the culprit, but time will tell.
Cancel
Vote Up 0 Vote Down

Cancel