Ruckus ZD1200
Ruckus ZD1200 Template (adaptable to other ZD appliances, see notes)
tested on 3.2, but minimum version should be 2.0 as SNMP LLD and trigger dependencies are are available since this version
Tested on ZAbbix 3.2.4
Allow monitoring of ZD1200 and associated AP and WLANs
ZoneDirector items :
- Total Nb of users and authenticated users
- Peer status in case A backup Appliance is available
- Licensed AP quantity
- CPU Utilization
- ZD Interfaces (Retrieve by LLD)
Discover Managed WLAN and AP through SNMP
- Monitor Access Points IP address, Status, and Nb of associated clients
- Monitor Rogue AP detection
- Monitor WLAN SSID (hidden/visible), Encryption and Authentication methods, Nb clients and AP, AP Overusage disassociation, and WLAN type (Guest/Private)
Mapping table
Add 4 mapping tables (could also been download indepently) to translate:
- SSID hidden or Visible
- AP Status
- WLAN guest or private
- ZD eth interfaces status
Mappings table screenshot in attachment
You need to have the 2 following MACROS set :
- {#SNMP_COMMUNITY}
- {#SNMP_PORT}
As they are defined with these macro to be easily portable.
Notes
This Template is easily adaptable to other ZD models :
LLD rules and items do not change
Templates items OID could be modify to adapt to a different ZD model :
ZD1200 "root" OID : 1.3.6.1.4.1.25053.3.1.5.15
Modify it to other model "root" OID (listed heraafter)
ZD1000 : 1.3.6.1.4.1.25053.3.1.5.1
ZD1100 : 1.3.6.1.4.1.25053.3.1.5.2
ZD3000 : 1.3.6.1.4.1.25053.3.1.5.3
ZD5000 : 1.3.6.1.4.1.25053.3.1.5.8
In case you use a backup Appliance, configure only the active one as host and use the actual IP, not the virtual one (SNMP responses come from actual IP and zabbix server see host in red SNMP status if you use the virtual IP)
Edit : Updated with the following
Change default "public" SNMP Community to a macro {#SNMP_COMMUNITY}.
Add {#SNMP_PORT} as a macro too.
Add trigger dependency (Trigger will only react if host is reachable through icmp)