Wrong UBNT Switch discovery

Help
,
1

When asking for help and support, please provide as much information as possible. This should include:

  • Steps to reproduce an issue.
  • The output of ./validate.php

If it’s an issue with the WebUI then please consider including a screenshot and the browser version you are using.

If you are having troubles with discovery/polling include the pastebin output of:

./discovery.php -h HOSTNAME -d | ./pbin.sh
./poller.php -h HOSTNAME -r -f -d | ./pbin.sh

If you need to post any text longer than a few lines, please use a pastebin service such as https://p.libren.ms using non-expiring pastes.

Hi,
My network has several Unifi equipment from UBNT (USG, USW-16-150W, US-8, UAP-AC-M, UAP-AC-Pro) all was discovered OK, but USW-16-150W alway discoverd as Inteno GW and icon is Inteno Group. Not sure whether it is the way USW answer the snmp qurey or there is something wrong in LibreNMS itself.

Screenshot_2020-09-18 192 168 1 2 Overview LibreNMS

result of ./validate.php

    librenms@librenms:~$ ./validate.php
    ====================================
    Component | Version
    --------- | -------
    LibreNMS  | 1.67-43-g941037e44
    DB Schema | 2020_08_28_212054_drop_uptime_column_outages (173)
    PHP       | 7.4.3
    Python    | 3.8.2
    MySQL     | 10.3.22-MariaDB-1ubuntu1
    RRDTool   | 1.7.2
    SNMP      | NET-SNMP 5.8
    ====================================

    [OK]    Composer Version: 1.10.13
    [OK]    Dependencies up-to-date.
    [OK]    Database connection successful
    [OK]    Database schema correct
    librenms@librenms:~$

this is the result of ./discovery.php -h 2 -d |./pbin.sh
https://p.libren.ms/view/6a2b4607
this is the result of ./poller.php -h 2 -r -f -d |./pbin.sh
https://p.libren.ms/view/734c699b
this is the result of snmpbulkwalk -OUneb -v2c -c kenny 192.168.1.2
https://p.libren.ms/view/d4085f5d

Thanks,
Kanok

2

I had te same with a UniFi AP-HD and a UniFi Switch 8. Both reporting it’s a Linux device. After a reboot they showed up as the correct device again. We have dozens of the same access points, all with the same firmware version, but only that one gave SNMP problems. I think it’s more as a UBNT issues than a LibreNMS issue.

3

In my case, even reboot didn’t change the incorrect discovery. However, digging in the process how LibreNMS detect the os. I found that it didn’t look for a switch that the model starts with US. I add one line to look for US- and it now it discovers correctly. Hope my pull request will be accepted soon.

librenms@librenms:~/includes/definitions$ cat edgeswitch.yaml
os: edgeswitch
text: EdgeSwitch
type: network
icon: ubiquiti
ifname: true
bad_snmpEngineTime: true
over:
    - { graph: device_bits, text: 'Device Traffic' }
    - { graph: device_processor, text: 'CPU Usage' }
    - { graph: device_mempool, text: 'Memory Usage' }
discovery:
    -
        sysObjectID:
            - .1.3.6.1.4.1.4413
            - .1.3.6.1.4.1.41112
        sysDescr_regex:
            - '/^EdgeSwitch/'
            - '/^EdgePoint/'
            - '/^USW[ -]/'
            - '/^UBNT US/'
            - '/^US[ -]/'
    -
        sysObjectID:
            - .1.3.6.1.4.1.8072.3.2.10
            - .1.3.6.1.4.1.27282.3.2.10
        sysDescr_regex:
            - '/^Linux UBNT/'
            - '/^RTL8380/'
4

Code merged #12167

1 Like