Skip to main content

Ruckus Zonedirector


Ruckus Wireless ZoneDirector is RUCKUS’ centrally managed Smart Wireless LAN (WLAN) system developed specifically for small-to-medium enterprises (SMEs).

Plugin-Pack assets​

Monitored objects​

  • Ruckus Access Point
  • Ruckus Controllers

Discovery rules​

Rule nameDescription
Net-Ruckus-Zonedirector-SNMP-Ap-NameDiscover access point attached to your controller

Monitored metrics​

Metric nameDescription
zd_connection_statusThe connection status with Zonedirector controller.
accesspoint.cpu.utilization.percentageCpu utilization by AP. Unit: %
accesspoint.memory.usage.bytesMemory used by AP. Unit: Bytes free by AP. Unit: Bytes
accesspoint.memory.usage.percentageMemory used by AP. Unit: %
accesspoint.connection.accesspointsNumber of APs. Unit: Count
accesspoint.connection.client.devices.authorized.countTotal number of authenticated terminal which is using currently on this AP. Unit: Count
accesspoint.connection.rogue.devices.countNumber of rogue devices. Unit: Count traffic going through the access point. Unit: bits/second
accesspoint.traffic.out.bitspersecondOutgoing traffic going through the access point. Unit: bits/second


Ruckus device configuration​

To use this Plugin, the SNMP service must be properly configured on your Ruckus device. Ruckus provides an official documentation to achieve this:

Network flow​

Your Centreon Poller must be able to reach the Ruckus device over UDP/161 SNMP port.


  1. Install the Centreon Plugin package on every Poller expected to monitor Ruckus Zonedirector ressources:
yum install centreon-plugin-Network-Ruckus-Zonedirector-Snmp
  1. On the Centreon Web interface, install the 'Ruckus Zonedirector' Centreon Plugin-Pack on the "Configuration > Plugin Packs > Manager" page


  • Log into Centreon and add a new Host through "Configuration > Hosts".
  • Apply the template "Net-Ruckus-Zonedirector-SNMP-custom" and configure the 'SNMP Community' and 'SNMP Version' fields to match the device configuration.

When using SNMP v3, set extra parameters with SNMPEXTRAOPTIONS macro :

SNMPEXTRAOPTIONSAny extra option you may want to add to the command (eg. a --verbose flag)


How do I test my configuration through the CLI and what do the main parameters stand for ?​

Once the Centreon Plugin installed, you can test it logging with the centreon-engine user:

/usr/lib/centreon/plugins// \
--plugin=network::ruckus::zonedirector::snmp::plugin \
--mode=system \ \
--snmp-version='2c' \
--snmp-community='ruckus_zonedirector' \

The command above checks the system utilization on your Ruckus box (--mode=system). You must always define the IP address/FQDN of the device ( as well as the SNMP versions and community (--snmp-version='2c' --snmp-community='ruckus_zonedirector')

You can display all modes that come with the Plugin with the command below:

/usr/lib/centreon/plugins// \
--plugin=network::ruckus::zonedirector::snmp::plugin \

You can display options of a specific mode by using the --help flag. Here is an example to display system mode parameters:

/usr/lib/centreon/plugins// \
--plugin=network::ruckus::zonedirector::snmp::plugin \
--mode=system \

UNKNOWN: SNMP GET Request : Timeout​

This message generally means that you are not using the right SNMP version or community. It could also indicate that a third-party device like a firewall is blocking the SNMP UDP/161 request.

UNKNOWN: SNMP GET Request : Cant get a single value.​

This error message often refers to the following issues:

  • the Ruckus device doesn't support the MIB used by the plugin
  • the targeted SNMP OID cannot be fetched because of insufficient privileges on the device. SNMP Agent must be capable of accessing to the enterprise branch Ruckus : .