Hello,
Efficient (DNS appliance) was added to LibreNMS with this update https://github.com/librenms/librenms/pull/8773
Normally LibreNMS is able to graph the number of DNS queries of the appliance EfficientIP but I can not get anything about DNS query, response …
How can I implement the EfficientIP in LibreNMS ?
Thanks in advance
Best Regards
David
Hello David,
Efficient IP SOLIDserver appliances provides statistics for DNS and DHCP services over SNMP.
They are available immediately after service is enabled and started on appliance or alternatively on package version available for several Linux based distribution (Redhat/Ubuntu).
In case you are interested in particular values like Number of queries, Number of Authoritative / Non-Authoritative answers / Returns Codes, please let me know.
I can pull info you are looking for.
Best Regards,
Peter
Efficient IP Delivery Team
Hello,
Thanks for your answer, Yes that’s what are we looking for.
Best regards
David
Hi,
Please don’t forget to submit your findings back to LibreNMS github 
Thanx !
Hello,
I m interested by this info, but it’s look like the mib is not used by librenms ?
Do you know how I can make it work ?
Best regards
David Schein
Hello David,
You can query DNSstats labels in OID
which give you visibility on different available counters
snmpwalk -v2c -c public 10.10.10.10 .1.3.6.1.4.1.2440.1.4.2.3.1.2
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.3.116.99.112 = STRING: “tcp”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.3.117.100.112 = STRING: “udp”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.5.100.110.115.54.52 = STRING: “dns64”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.6.101.99.115.111.112.116 = STRING: “ecsopt”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.6.115.105.103.48.105.110 = STRING: “sig0in”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.6.116.115.105.103.105.110 = STRING: “tsigin”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.6.120.102.114.114.101.106 = STRING: “xfrrej”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.7.97.117.116.104.97.110.115 = STRING: “authans”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.7.97.117.116.104.114.101.106 = STRING: “authrej”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.7.100.114.111.112.112.101.100 = STRING: “dropped”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.7.101.100.110.115.48.105.110 = STRING: “edns0in”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.7.102.97.105.108.117.114.101 = STRING: “failure”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.7.102.111.114.109.101.114.114 = STRING: “formerr”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.7.110.115.105.100.111.112.116 = STRING: “nsidopt”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.7.110.120.114.114.115.101.116 = STRING: “nxrrset”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.7.114.101.115.95.118.97.108 = STRING: “res_val”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.7.115.105.103.48.111.117.116 = STRING: “sig0out”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.7.115.117.99.99.101.115.115 = STRING: “success”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.7.116.115.105.103.111.117.116 = STRING: “tsigout”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.7.120.102.114.100.111.110.101 = STRING: “xfrdone”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.8.99.111.111.107.105.101.105.110 = STRING: “cookiein”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.8.101.100.110.115.48.111.117.116 = STRING: “edns0out”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.8.110.120.100.111.109.97.105.110 = STRING: “nxdomain”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.8.111.116.104.101.114.111.112.116 = STRING: “otheropt”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.8.114.101.102.101.114.114.97.108 = STRING: “referral”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.8.114.101.115.95.108.97.109.101 = STRING: “res_lame”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.8.114.101.115.112.111.110.115.101 = STRING: “response”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.8.115.101.114.118.102.97.105.108 = STRING: “servfail”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.9.98.97.100.99.111.111.107.105.101 = STRING: “badcookie”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.9.99.111.111.107.105.101.110.101.119 = STRING: “cookienew”
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.2.9.100.117.112.108.105.99.97.116.101 = STRING: “duplicate”
Actual value can be then gathered from 2nd sub-table containing values
snmpwalk -v2c -c public 10.10.10.10 .1.3.6.1.4.1.2440.1.4.2.3.1.3
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.3.3.116.99.112 = INTEGER: 4064
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.3.3.117.100.112 = INTEGER: 3203494
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.3.5.100.110.115.54.52 = INTEGER: 0
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.3.6.101.99.115.111.112.116 = INTEGER: 0
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.3.6.115.105.103.48.105.110 = INTEGER: 0
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.3.6.116.115.105.103.105.110 = INTEGER: 7403
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.3.6.120.102.114.114.101.106 = INTEGER: 0
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.3.7.97.117.116.104.97.110.115 = INTEGER: 2526756
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.3.7.97.117.116.104.114.101.106 = INTEGER: 0
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.3.7.100.114.111.112.112.101.100 = INTEGER: 0
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.3.7.101.100.110.115.48.105.110 = INTEGER: 47290
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.3.7.102.97.105.108.117.114.101 = INTEGER: 0
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.3.7.102.111.114.109.101.114.114 = INTEGER: 0
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.3.7.110.115.105.100.111.112.116 = INTEGER: 22415
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.3.7.110.120.114.114.115.101.116 = INTEGER: 197797
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.3.7.114.101.115.95.118.97.108 = INTEGER: 0
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.3.7.115.105.103.48.111.117.116 = INTEGER: 0
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.3.7.115.117.99.99.101.115.115 = INTEGER: 1014848
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.3.7.116.115.105.103.111.117.116 = INTEGER: 7402
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.3.7.120.102.114.100.111.110.101 = INTEGER: 653
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.3.8.99.111.111.107.105.101.105.110 = INTEGER: 4193
SNMPv2-SMI::enterprises.2440.1.4.2.3.1.3.8.101.100.110.115.48.111.117.116 = INTEGER: 47247
Is OK for having just specific OIDs - which one I can lookup for you?
This works for DNS, but the appliances don’t seem to support anything useful for DHCP service, other than service status (up/down/disabled, etc.). I have walked the entire MIB and the only config data that comes back is from the DNS part of the MIB.
Anyone else have any insights about this? You can’t quesry DHCP pools, sizes, etc. and monitor for potential exhaustion… 