OID's Used by LibreNMS

<%- if @topic_view.topic.tags.present? %>
<%= t 'js.tagging.tags' %>: <%- @topic_view.topic.tags.each do |t| %> <%= t %> <%- end %>
<% end %>

Hi,

I noticed that distro uses a “custom OID” (for lack of a better term) to transfer information to LibreNMS. I have found other occurences of this - it’s fine, but is a list of these OID’s captured somewhere? Asking because I can see that conflicts could easily arise, want to avoid that.

Thanks!

A conflict isn’t very likely unless you use the same extend name. distro is a bit older and uses the old ucd-snmp mib tree. I don’t why 1.3.6.1.4.1.2021.7890 was used instead of the 1.3.6.1.4.1.2021.8 extTable but even so, because it uses extend the name is built into the OID.

extend .1.3.6.1.4.1.2021.7890.1 distro /usr/bin/distro

$ snmpwalk HHHHHHHH -On -v2c -c CCCCCCCC .1.3.6.1.4.1.2021.7890.1
UCD-SNMP-MIB::ucdavis.7890.1.1.0 = INTEGER: 1
UCD-SNMP-MIB::ucdavis.7890.1.2.1.2.6.100.105.115.116.114.111 = STRING: “/usr/bin/distro”
UCD-SNMP-MIB::ucdavis.7890.1.2.1.3.6.100.105.115.116.114.111 = “”
UCD-SNMP-MIB::ucdavis.7890.1.2.1.4.6.100.105.115.116.114.111 = “”
UCD-SNMP-MIB::ucdavis.7890.1.2.1.5.6.100.105.115.116.114.111 = INTEGER: 5
UCD-SNMP-MIB::ucdavis.7890.1.2.1.6.6.100.105.115.116.114.111 = INTEGER: 1
UCD-SNMP-MIB::ucdavis.7890.1.2.1.7.6.100.105.115.116.114.111 = INTEGER: 1
UCD-SNMP-MIB::ucdavis.7890.1.2.1.20.6.100.105.115.116.114.111 = INTEGER: 4
UCD-SNMP-MIB::ucdavis.7890.1.2.1.21.6.100.105.115.116.114.111 = INTEGER: 1
UCD-SNMP-MIB::ucdavis.7890.1.3.1.1.6.100.105.115.116.114.111 = STRING: “RedHat 7.6”
UCD-SNMP-MIB::ucdavis.7890.1.3.1.2.6.100.105.115.116.114.111 = STRING: “RedHat 7.6”
UCD-SNMP-MIB::ucdavis.7890.1.3.1.3.6.100.105.115.116.114.111 = INTEGER: 1
UCD-SNMP-MIB::ucdavis.7890.1.3.1.4.6.100.105.115.116.114.111 = INTEGER: 0
UCD-SNMP-MIB::ucdavis.7890.1.4.1.2.6.100.105.115.116.114.111.1 = STRING: “RedHat 7.6”

decimal value  character
  100            d
  105            i
  115            s
  116            t
  114            r
  111            o

Application monitoring scripts that use SNMP extend in LibreNMS will work the same way but use the newer more standard net-snmp-extend-mib (1.3.6.1.4.1.8072.1.3) instead of ucd-snmp.

Yes, agreed. But, I am finding several devices that don’t support extend … rather only exec. Then, using your example line, modified for exec,
exec .1.3.6.1.4.1.2021.7890.1 /usr/bin/distro

Now I have to be careful not to reuse that OID. I just found an app using an OID that I was about to use.

Make sense?

Thanks!

Sure, but it’s unlikely anything else is using UCD-SNMP-MIB::ucdavis.7890.1, so that may work for distro. For other applications, the documentation specifically says snmpd extend. I wouldn’t expect exec to be supported. I think your options there are to upgrade snmpd (if possible) or use the check_mk agent.

Yes, agreed - won’t be an issue outside of LibreNMS, those aren’t used OID’s (I think). I found this on a Tomato based router I have - snmp there is too old for extend, only has exec.

Thanks!

1 Like