Ruckus Unleashed sysObjectID change

Feature Requests
1

As I see someone defined sysObjectID to ‘.1.3.6.1.4.1.25053.3.1.5.15’ for ruckus unleashed. We using Unleashed clusters on H510 APs with 200.15.6.12 build 304 software version and LibreNMS discover it as generic device because our APs replies ‘.1.3.6.1.4.1.25053.3.1.5.20’ for sysObjectID. I don’t know if the ‘…15’ one OID is correct but we would like to ask to add/change to ‘…20’ in ‘/opt/librenms/includes/definitions/ruckuswireless-unleashed.yaml’, for example:

librenms@lnms-cpe-wifi:~$ git diff
diff --git a/includes/definitions/ruckuswireless-unleashed.yaml b/includes/definitions/ruckuswireless-unleashed.yaml
index e0b0b6145..3b4c3a3ba 100644
--- a/includes/definitions/ruckuswireless-unleashed.yaml
+++ b/includes/definitions/ruckuswireless-unleashed.yaml
@@ -9,7 +9,9 @@ over:
     - { 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.15
+            - .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
1 Like
2

Further investigation about this, I found unleashed-mibs-20230626.zip and in that there is a RUCKUS-PRODUCTS-MIB.txt file which tells:

-- ZD1200 - Access Controller, 2 Ethernet ports, 2048MB Flash, 2048MB DRAM
ruckusZD1200 OBJECT IDENTIFIER  ::= { ruckusWirelessControllerProducts 15 }
    
-- Unleashed
ruckusUnleashed OBJECT IDENTIFIER  ::= { ruckusWirelessControllerProducts 20 }
    
-- Blue
ruckusBlue OBJECT IDENTIFIER  ::= { ruckusWirelessControllerProducts 25 }

So please simply replace the sysObjectID from 15 to 20 in unleashed as 15 is for ZoneDirector 1200

1 Like
3

Same thing for R650 and unleashed version 200.15.6.112.52

I think the OID change with the 200.15 version. Thanks for the solution, it’s working again.

1 Like