Convincing TrueNAS to be compliant with Zabbix monitoring is apparently quite a process. It should be easy — both ends speak SNMP — but that doesn’t seem to mean it actually is.

  • TrueNAS System ⇒ Services ⇒ SNMP:
    • Set Location field
    • Contact field blank
    • Community field set
    • SNMPv3 support enabled
    • Username set to ABCD (dummy value)
    • Authentication type set to SHA
    • Password set to EFGH (dummy)
    • Privacy protocol set to AES
    • Privacy passphrase set to IJKL (dummy)
    • Auxiliary parameters blank
    • Expose zlstat via SNMP enabled
    • Log level set to Error
  • Zabbix host configuration
    • IP and DNS name set (connect to IP)
    • Port 161
    • SNMP version set to SNMPv3
    • Max repetition count set to 10
    • Context name blank
    • Security name set to ABCD (the Username field on TrueNAS)
    • Security level set to authPriv
    • Authentication protocol set to SHA1
    • Authentication passphrase set to EFGH (Password field on TrueNAS)
    • Privacy protocol set to AES128
    • Privacy passphrase set to IJKL (Privacy passphrase field on TrueNAS)
    • Use combined requests enabled
  • Zabbix template settings
    • Using one template: TrueNAS CORE by SNMP
      • Templates/Applications

See also

  • Installed snmpget (Gentoo: emerge -a net-analyzer/net-snmp)
  • snmpget -v 3 -u <user> -l authPriv -a SHA -A <authpw> -x AES -X <privpw> <ip> .1.3.6.1.4.1.2021.4.4.0 works, returns UCD-SNMP-MIB::memAvailSwap.0 = INTEGER: 0 kB
  • Playing with -a and -x options indicate -a SHA and -a SHA1 work, no others. -x AES seems to be only option recognized by snmpget.

Broken pool status SNMP

See also

zabbix