Ubiquiti Wave Device(s) Request

Device Requests
1

Ubiqiuiti 60GHz/Wave Devices.

Including, but not limited to:

  • Wave AP
  • Wave AP micro
  • Wave Nano
  • Wave LR
  • Wave AP (without SFP+)
  • AF60 LR

MIB: https://ui.com/downloads/firmwares/wave/v3.2.0/ui-mib.zip

2

2nd this, waiting patiently, wave support would be epic!

Thanks in Advance

1 Like
3

If you want someone to write support for these devices, we need an snmpwalk/snmpsim file with the correct MIB. A MIB alone isn’t enough.

4

SNMP Walk here.

5

Okay, that snmpwalk file is very short. It’s probably missing a lot of OIDs.
Could you give me SNMP access to the device?

And what kind of support would you like to see? (which sensors, modules, etc)

6

Could you recommend a Windows SNMP Walk tool? I used Manage Engine MIB Browser but it wouldn’t read one of the MIB files correctly.

7

I’ve managed to get a more comprehensive output from Solarwinds, I’ve exported it to a CSV file. Where/who/how can I send this please?

8

Hi @ecdc
Please check here : https://github.com/librenms/librenms/blob/master/doc/Support/FAQ.md#-what-information-do-you-need-to-add-a-new-os

And the exact snmpwalk command is given.

That one allows to replicate your device (like a clone) and work on the support.

1 Like
9

Ah yes, thank you, I shall attempt to do this.

10

./discovery.php -h 10.20.158.45 -d | ./pbin.sh
https://p.libren.ms/view/155d1eb8

lnms device:poll 10.20.158.45 -vv | ./pbin.sh
https://p.libren.ms/view/56a7e01d

snmpbulkwalk -OUneb -v2c -c public 10.20.158.45 . | ./pbin.sh
https://p.libren.ms/view/0c306c80

Hope this is what you need, please let me know if not.

11

What would you like to have implemented for this device? I took a look at your snmpwalk, but it’s quite short. Doesn’t have a lot of information.

12

I’ve ran the commands again and it’s giving me the same info.

The full MIB file is in the first post.

Implementation should be the same as Ubiquiti AirFiber 60.

13

Could you test for me if this is all it takes?

edit /opt/librenms/includes/definitions/airos-af.yaml

Change:

 discovery:
     -
         sysObjectID: .1.3.6.1.4.1.10002.1

into:

 discovery:
     -
         sysObjectID:
             - .1.3.6.1.4.1.10002.1
             - .1.3.6.1.4.1.41112

Leave the rest untouched.

After that, run disovery on your device again

14

Are you sure that’s correct?

I now get “Whoops something went wrong” when clicking on any page.

UPDATE: My bad - I used tab indentations in YAML ://

Device page shows this:

    2024-02-11 07:22:42		Error discovering core module. Check log file for more details.
	2024-02-11 07:22:42		Error discovering os module. Check log file for more details.
	2024-02-11 07:22:42		Error discovering processors module. Check log file for more details.
	2024-02-11 07:22:42		Error discovering mempools module. Check log file for more details.
	2024-02-11 07:22:42		Error discovering sensors module. Check log file for more details.
	2024-02-11 07:22:42		Error discovering storage module. Check log file for more details.
	2024-02-11 07:22:42		Error discovering vminfo module. Check log file for more details.
	2024-02-11 07:22:42		Error discovering wireless module. Check log file for more details.
15

UPDATE2: Sorted it.

Added the OID to the airos-AF60.yaml file rather than the airos-af.yaml file.

Rediscovered all is now showing as Ubiquiti AF60 variant.

Can we add this to the next roll please?