Ad Widget

Collapse

snmp community name setting keeps reverting back to the default 'public' value

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • luxfx
    Junior Member
    • Dec 2024
    • 3

    #1

    snmp community name setting keeps reverting back to the default 'public' value

    I have a Dell PowerEdge iDRAC8 server and several Mikrotik devices that I wish to monitor via SNMPv2. I have the hosts configured and everything works ... briefly. I get data for at least one pull, so I know the basic configuration is working ok, and the service on the device works.

    But then they revert to a "Not Available - Timeout while connecting to ..." state. When this happens, I can open up the host snmp configuration and the 'SNMP community' has reverted to the 'public' default value. The other configuration stays updated as best I can tell.

    If I change it back to my custom SNMPv2 community name it will work for a while again, but eventually goes back to the timeout state.

    Is this a bug?

    Zabbix v7.0.4 (on Proxmox)
    using this template: https://git.zabbix.com/projects/ZBX/...5a58ea161aa037 5821
    (template seems to work great, it's only the snmp setting that has trouble I think)
  • luxfx
    Junior Member
    • Dec 2024
    • 3

    #2
    I take back my statement that other configuration stays updated. I think all of the SNMP settings get reset. I have another device I had set to SNMP v3 and it kept working - so I thought it was ok. It turns out the SNMP configuration had reset and the device was also offering SNMP v2 with the default 'public' community name. Disabling that access on my device caused the connection to fail in the same way, with a timeout message.

    Comment

    • luxfx
      Junior Member
      • Dec 2024
      • 3

      #3
      It was a Discovery rule that was overwriting my config! Thanks Reddit.

      Comment

      Working...