SOLVED SNMP Daemon not responding

[ian351c]

AAARG - typo in community string - nothing to see here...


I've run into an issue where my FreeNAS server won't respond to SNMP requests. I had it configured previously with a Location, Contact, and Community String. I monitor it using Cacti and that has been working fine for years. I started a project to start monitoring data reported by IPMI via SNMP, which involved setting some config options in "Auxiliary parameters" field. Once I did that, SNMP stopped responding.

During troubleshooting, I noticed that /etc/local/snmpd.conf would contain ONLY the parameters set in "Acusiliary parameters" if I used them (so those parameters are not appended to snapped.conf, they replace whatever is already there). So I rolled the configuration back by removing all the auxiliary parameters. I then

Code:

agentAddress udp:161,udp6:161,unix:/var/run/snmpd.sock
sysLocation XXXXXX
sysContact XXXXXXX
sysDescr Hardware: amd64 Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz running at 3500 Software: FreeBSD 9.3-RELEASE-p5 (revision 199506)

rocommunity xxxxxxx default
pass .1.3.6.1.4.1.25359.1 /usr/local/bin/freenas-snmp/zfs-snmp

This config "works" in that it doesn't throw any errors and it looks to be the standard config generated by FreeNAS. However, snmpd is no longer responding to queries. The query is received but no response is sent. I ran snmpd in the foreground and saw this:

Code:

[root@nas1] /# snmpd -f -V -Lo -c /etc/local/snmpd.conf
NET-SNMP version 5.7.2
Connection from UDP: [172.16.100.200]:56360->[172.16.100.112]:161
Received SNMP packet(s) from UDP: [172.16.100.200]:56360->[172.16.100.112]:161
  GETNEXT message
    -- SNMPv2-SMI::mib-2
Connection from UDP: [172.16.100.200]:56360->[172.16.100.112]:161
Received SNMP packet(s) from UDP: [172.16.100.200]:56360->[172.16.100.112]:161
  GETNEXT message
    -- SNMPv2-SMI::mib-2
Connection from UDP: [172.16.100.200]:56360->[172.16.100.112]:161
Received SNMP packet(s) from UDP: [172.16.100.200]:56360->[172.16.100.112]:161
  GETNEXT message
    -- SNMPv2-SMI::mib-2
Connection from UDP: [172.16.100.200]:56360->[172.16.100.112]:161
Received SNMP packet(s) from UDP: [172.16.100.200]:56360->[172.16.100.112]:161
  GETNEXT message
    -- SNMPv2-SMI::mib-2
Connection from UDP: [172.16.100.200]:56360->[172.16.100.112]:161
Received SNMP packet(s) from UDP: [172.16.100.200]:56360->[172.16.100.112]:161
  GETNEXT message
    -- SNMPv2-SMI::mib-2
Connection from UDP: [172.16.100.200]:56360->[172.16.100.112]:161
Received SNMP packet(s) from UDP: [172.16.100.200]:56360->[172.16.100.112]:161
  GETNEXT message
    -- SNMPv2-SMI::mib-2

Anyone out there that can help? I suspect that snmpd can't find its MIBs, but I'm not sure about that.

Thanks.