When adding a VM to be monitored via SNMP into observium if the VM is on the same cluster it will not be fully discovered.

Mike Stupalov added a comment - 2025/02/18 02:38 PM - edited Device have troubles with bulk requests. Not sure why on same VMs different behavior. But you need disable or reduce SNMP max-repetition value for this device (on device edit page -> SNMP). 0 - for disable, or 20/30/50 for reduce.. CMD[/usr/bin/snmpbulkwalk -Cr'100' -v2c -c *** -Pud -OQUs -m IF-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'host':'161' ifDescr]   CMD EXITCODE[1] CMD RUNTIME[6.0517s] STDOUT[   ] STDERR[ Timeout: No Response from udp:host:161 ] SNMP STATUS[FALSE] SNMP ERROR[#1004 - Bulk Request timeout]

Stephen Stogner added a comment - 2025/02/17 06:37 PM I attached the discoveries, with the server that is not being discovered as expected, I also re-configured the snmpd.conf file to be the same as the observium recommended one and I did not see any changes in what is being graphed.

Mike Stupalov added a comment - 2025/02/14 08:08 PM pls note, default snmpd.conf in debian/ubuntu have 2 default views: full for localhost requests and system for all others (with very limited output). That why we promote own variant of snmpd config.

Mike Stupalov added a comment - 2025/02/14 08:00 PM you missed discovery debug outputs, this is more actual for this case.

Stephen Stogner added a comment - 2025/02/11 06:40 PM Ok, I installed 2 fresh Debian VM's, the only difference is they are located on different clusters, I also included screen shots of what is displayed by observium when they are being monitored. I also included the snmpwalks for both.    They are using the exact same snmpd config, the underlying hardware and hypervisor versions are also the same.