SNMP Poll issues
-
Why does netxms continually try snmp communities when the community is already known ? I have a few different community strings and netxms will still try all others even though the correct string is already configured in the node settings. This causes issues with switches that have security measures to block snmp if failed snmp attemps are reached. As well as causing bloated logs with auth failed attempts.
-
The only situation when this might be happening - if during configuration poll device did not answer to a packet with currently stored community string. In this case server thinks that community string might have changed and starts trying all available ones. You can do tcpdump from your server filtering by device IP and SNMP port, then we will have some more information. The command is
tcpdump -s 0 -w traffic.pcap host = IP_ADDRESSOr you can just set checkbox "Prevent automatic SNMP configuration changes" in node properties, it should prevent trying community strings.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login