Why is this OS detected as generic?

Dejan · 30 November 2023 12:14

When running discovery through web gui of librenms i collected following:

DEBUG!
Updating os_def.cache
SQL[SELECT * FROM devices WHERE disabled = 0 AND hostname LIKE ‘10.10.11.115’ ORDER BY device_id DESC 1.59ms]

10.10.11.115 42 generic SQL[select * from devices where device_id = ? limit 1 [42] 1.06ms]

SQL[select * from devices_attribs where devices_attribs.device_id = ? and devices_attribs.device_id is not null [42] 0.34ms]

[FPING] ‘/usr/bin/fping’ ‘-e’ ‘-q’ ‘-c’ ‘3’ ‘-p’ ‘500’ ‘-t’ ‘500’ ‘-O’ ‘0’ ‘10.10.11.115’

response: xmt/rcv/%loss = 3/3/0%, min/avg/max = 3.75/5.34/8.19
SNMP[‘/usr/bin/snmpget’ ‘-M’ ‘/home/librenms/mibs’ ‘-m’ ‘SNMPv2-TC:SNMPv2-MIB:IF-MIB:IP-MIB:TCP-MIB:UDP-MIB:NET-SNMP-VACM-MIB’ ‘-v2c’ ‘-c’ ‘COMMUNITY’ ‘-OQXUte’ ‘udp:HOSTNAME:161’ ‘SNMPv2-MIB::sysObjectID.0’]
SNMPv2-MIB::sysObjectID.0 = SNMPv2-SMI::enterprises.6527

Modules status: Global+
OS
Device

Load disco module core

Attempting to initialize OS: generic
OS initialized: LibreNMS\OS\Generic
SNMP[‘/usr/bin/snmpget’ ‘-M’ ‘/home/librenms/mibs’ ‘-m’ ‘SNMPv2-TC:SNMPv2-MIB:IF-MIB:IP-MIB:TCP-MIB:UDP-MIB:NET-SNMP-VACM-MIB’ ‘-v2c’ ‘-c’ ‘COMMUNITY’ ‘-OQXUte’ ‘-On’ ‘udp:HOSTNAME:161’ ‘SNMPv2-MIB::sysObjectID.0’ ‘SNMPv2-MIB::sysDescr.0’ ‘SNMPv2-MIB::sysName.0’]
...0 = .*.4.1.6527

When i compare this to ‘includes/definitions/timos.yaml’ i can see that enterprise id is matching e.g. 6527

Whats the reason for librenms to go for generic?

laf · 30 November 2023 17:04

can you post the full output of the discovery with debug enabled.

Dejan · 30 November 2023 18:14

its to big to paste here. i captured it in a txt file but its not allowed to upload. I shared it here

gist.github.com

https://gist.github.com/dejantep/8017fd23276f4e48a0372cb77398adde

gistfile1.txt

LibreNMS Discovery
SQL[select `migration` from `migrations` order by `id` desc limit 1 [] 0.58ms] 
  
SQL[select count(*) as aggregate from `migrations` [] 0.39ms] 
  
SQL[select version() [] 0.32ms] 
  
===========================================
Component | Version
--------- | -------

This file has been truncated. show original

laf · 30 November 2023 22:35

Can you get the output of the following:

/usr/bin/snmpget -M /home/librenms/mibs -m SNMPv2-TC:SNMPv2-MIB:IF-MIB:IP-MIB:TCP-MIB:UDP-MIB:NET-SNMP-VACM-MIB -v2c -c COMMUNITY -OQXUte -On udp:HOSTNAME:161 SNMPv2-MIB::sysObjectID.0 SNMPv2-MIB::sysDescr.0 SNMPv2-MIB::sysName.0

Replace COMMUNITY and HOSTNAME with the relevant details.

Dejan · 30 November 2023 23:03

.1.3.6.1.2.1.1.2.0 = .1.3.6.1.4.1.6527
.1.3.6.1.2.1.1.1.0 = TiMOS-B-14.2.private both/ppc Nokia 7710 ISAM Copyright (c) 2000-2020 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Build on Thu May 28 16:19:55 IST 2020 by bmc in /repo/ef/nante/sw/vobs/dsl/IPD/main

.1.3.6.1.2.1.1.5.0 = kbga1-dist-olt-01

Thanks for helping out

laf · 1 December 2023 21:45

Oddly this is because the response from TiMOS is normally .1.3.6.1.4.1.6527.x.x.x.x so the regex is expecting a . after the 6527.

The definition needs updating and tests generating, do you think you could do that?

Dejan · 1 December 2023 22:10

Are you familiar with Nokia OLT? They have two OS and one of them is Timos but somewhat limited compared to say 7750 SR. Could be the reason but still, it should be detected.

Unfortunatly my knowledge is limited but i’m willing to learn and help in any way i can.

laf · 1 December 2023 22:26

I’m not I’m afraid.

the output from your tests suggest this is a TiMOS OS based device so I think it should updated. If you can do this then edit the yaml file includes/definitions/timos.yaml. Remove the trailing . from the line with 6527 on it.

Then follow: Test Units - LibreNMS Docs

system · 29 February 2024 22:26

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.