Ruckus AP being detected as generic device

Help
1

Added my ruckus unleashed master AP, Device is added but seen as “generic device”.
This is how it shows up in web gui:

Screenshot_2024-05-11_12-30-09
Screenshot_2024-05-11_12-30-09739×310 12.7 KB

Further to this the logo is not changing to ruckus:
Screenshot_2024-05-11_12-31-31

here is the output of vlidate.php:

here is the output of ./discovery.php -h 26 -d -m os

Here is output of ./poller.php -h 26 -r -f -d | ./pbin.sh:
https://p.libren.ms/view/546238a0

I’ve tried deleting and re-adding it many times but it just remains as a generic device event though it is clearly picking up it is a ruckus unleashed R510

2

Ruckus “fixed” the system object ID for Unleashed with 200.15. The Ruckus SNMP spec said “.1.3.6.1.4.1.25053.3.1.5.20”, but 200.14 incorrectly used “.1.3.6.1.4.1.25053.3.1.5.15”.

This addresses the issue with librenms:

--- includes/definitions/ruckuswireless-unleashed.yaml.org      2024-04-28 17:43:26.135737508 -0700
+++ includes/definitions/ruckuswireless-unleashed.yaml  2024-04-28 16:59:41.572914085 -0700
@@ -9,7 +9,7 @@
     - { graph: device_wireless_clients, text: 'Number of Clients' }
 discovery:
     -
-        sysObjectID: .1.3.6.1.4.1.25053.3.1.5.15
+        sysObjectID: .1.3.6.1.4.1.25053.3.1.5.20
         snmpget_except:
             oid: '.1.3.6.1.4.1.25053.1.2.1.1.1.1.9.0'
             op: starts
3

Thanks dennypage.

Can you explain how I use this please?

4

You would apply that diff to the librenms code. You will need to rediscover after application.

5

no idea how to do that but searched a bit deeper and edited the relevant yaml file.
(/opt/librenms/includes/definitions/ruckuswireless-unleashed.yaml)

Much easier than assuming I know how to apply a diff to code, Sorry I’m not a programmer.

6

I assume you got it working though?

7

Hi - There was a PR that got merged 2 days ago about this change. So next release should hopefully fix it, see

1 Like