OS discovery without sysObjectID or sysDescr

Help
,
1

Hi Folks,
is there a manual way to assign an OS to an SNMP device not returning any sysObjectID or sysDescr value?

Janitza Power Meters are having a very inconsistent SNMP deployment and I would like to assign an OS in a manual way.

UMG604:

‘/usr/bin/snmpget’ ‘-M’ ‘/opt/librenms/mibs:/opt/librenms/mibs/janitza’ ‘-m’ ‘SNMPv2-TC:SNMPv2-MIB:IF-MIB:IP-MIB:TCP-MIB:UDP-MIB:NET-SNMP-VACM-MIB’ ‘-v2c’ ‘-c’ ‘public’ ‘-OQXUte’ ‘-Pu’ ‘-On’ ‘-t’ ‘3’ ‘udp:jan-uvt-01:161’ ‘SNMPv2-MIB::sysObjectID.0’ ‘SNMPv2-MIB::sysDescr.0’ ‘SNMPv2-MIB::sysName.0’

.1.3.6.1.2.1.1.2.0 = .1.3.6.1.4.1.34278.10.1

.1.3.6.1.2.1.1.1.0 = Janitza Power Analyzer umg604-7

.1.3.6.1.2.1.1.5.0 = jan-uvt-01

UMG806:

root@thor-odd:/home/wriedel# ‘/usr/bin/snmpget’ ‘-M’ ‘/opt/librenms/mibs:/opt/librenms/mibs/janitza’ ‘-m’ ‘SNMPv2-TC:SNMPv2-MIB:IF-MIB:IP-MIB:TCP-MIB:UDP-MIB:NET-SNMP-VACM-MIB’ ‘-v2c’ ‘-c’ ‘public’ ‘-OQXUte’ ‘-Pu’ ‘-On’ ‘-t’ ‘3’ ‘udp:jan-hvt-01:161’ ‘SNMPv2-MIB::sysObjectID.0’ ‘SNMPv2-MIB::sysDescr.0’ ‘SNMPv2-MIB::sysName.0’

.1.3.6.1.2.1.1.2.0 = No Such Object available on this agent at this OID

.1.3.6.1.2.1.1.1.0 = No Such Object available on this agent at this OID

.1.3.6.1.2.1.1.5.0 = No Such Object available on this agent at this OID

I tried to add as a non SNMP device, so I can select an OS manually but when switching on SNMP afterwards the manual setting are being overridden and it becomes a generic device.

Thank you,
Wolfgang

2

We need some way to identify it, does any of the snmp output for that device help us identify the os?

3

laf,

No not in a meaningful way a they just return power values.
It’s a bug on the Janitza side but the only solution would be to replace the power meters.
Yes I understand that we need to identify the device OS somehow but why no allow me to select the OS in a manual way like for non SNMP devices and afterwards don’t permit the poller to override my manual decision?

4

If you set it to ping only, you can set an arbitary OS.

5

I think wriedel is saying if he can set it for snmp devices then the rest of the information gets collected ok, it’s just OS discovery that isn’t working.

I don’t know what the other maintainers think on this subject but I’m not a fan of allowing people to override the OS as it can lead to two things

  1. People working around outdated device support so we don’t hear about what needs updating or adding to improve things for everyone.
  2. An increase in issues because users are now marking devices as varying OSes incorrectly leading to people asking for more help.
6

yes, but then can can’t pull SNMP values, right :wink:

7

I partially agree with you but I am an adult and should be able to decide on my own :wink: If I am able to decide on an OS for an IP device why not for an SNMP device?
And yes, sometimes we need to deal with outdated hardware and OS but that’s the drawback of SNMP and like in case of Janitza they understand it’s a bug on their side but nobody knows when it ever will getting fixed and until that I can’t monitor it via Librenms :wink:

8

I appreciate your pain but unfortunately we’re the ones that give up our free time to help support the project, I’d like to not making that harder or more unclear to do.

9

You are more than welcome to modify your local LibreNMS as you see fit.

A change that allows arbitrary OS setting is unlikely to be accepted upstream.
But if you can come up with a different fix to allow identification of this device, it may be accepted upstream.

You are allowed to just run your changes locally and be happy though.