Excessive snmp requests with a community string I am not using

Okay I figured this out and it was a housekeeping thing on my part - I was able to find that I had these switches in my portal a second time using a different IP. They weren't in my hierarchy and had no community string set, I deleted them and now the messages are gone.
Thanks everyon!

Check if you have the snmp.community property set anywhere including at the root group level. Properties get inherited so it can be easy for some properties (especially when using the Wizard) to get set at a higher level and flow down. It's also possible that ProperySources might do a snmp check but it wouldn't be nearly that frequently.

Also if you were doing v3 previously, verify that is still working. If v3 stops working LM might attempt to downgrade to v2 and perhaps use a "public" default value.

You may have to troubleshoot which DataSource may be causing it by trial and error. Like disabling snmp checks on a device until it goes away. You can also try doing packet traces on the collector (if not too loaded down) to look for "public" attempts since snmpv2 is not encrypted.

Prepare for disappointment. LM defaults to "public" if no community is configured and it's not trivial to disable SNMP polling (e.g. there isn't a NoSNMP like there is a NoPING).


https://community.logicmonitor.com/discussions/lm-exchange/custom-property---disable-snmp-polling-/13178