Skip to main content

Ruckus ICX

Overview​

Ruckus ICX switches work to simplify network set-up and management, enhance security, minimize troubleshooting and make upgrades easy. They seamlessly work together with Ruckus Wi-Fi access points, Ruckus SmartZone network controllers and Ruckus Cloud to deliver the most performance and cost effective unified wired and wireless access solutions.

Monitoring Connector assets​

Monitored objects​

  • Ruckus ICX Switches series

Discovery rules​

Rule nameDescription
Net-Ruckus-Icx-SNMP-Traffic-NameDiscover network interfaces and monitor status and bandwidth utilization

Monitored metrics​

Metric NameDescription
cpu.utilization.5s.percentageCPU usage for the last 5s period. Unit: percentage (%)
cpu.utilization.1m.percentageCPU usage for the last 1m period. Unit: percentage (%)
cpu.utilization.5m.percentageCPU usage for the last 5m period. Unit: percentage (%)

Prerequisites​

Ruckus device configuration​

The SNMP v2 agent has to be configured on the Ruckus ICX devices for the Centreon poller to be allowed to monitor them.

Network flows​

The Centreon poller should be able to reach the UDP SNMP port 161 of the Ruckus ICX device.

Installation​

  1. Install the Plugin on every poller expected to monitor Ruckus ICX SNMP resources:
yum install centreon-plugin-Network-Switch-Ruckus-Icx-Snmp
  1. Install the Ruckus ICX Centreon Monitoring Connector from the Configuration > Monitoring Connector Manager page

Host Configuration​

  • In the Centreon Web interface, add a new Host from the "Configuration > Hosts" page.
  • Set the values of the SNMP community and SNMP version fields then apply the Net-Switch-Ruckus-Icx-SNMP-custom Host template.

When using SNMP v3, use the SNMPEXTRAOPTIONS Macro to add specific authentication parameters More information in the Troubleshooting SNMP section.

MandatoryNameDescription
SNMPEXTRAOPTIONSExtra SNMP options of the Ruckus ICX device

FAQ​

How can I test the Plugin in the CLI and what do the main options mean?​

Once the Plugin is installed, you can test it directly from the command line interface of the Centreon poller with the centreon-engine user:

/usr/lib/centreon/plugins/centreon_ruckus_icx_snmp.pl
--plugin=network::ruckus::icx::snmp::plugin \
--hostname=ruckus.int.centreon.com \
--snmp-version='2c' \
--snmp-community='public' \
--mode='memory' \
--warning-usage='80' \
--critical-usage='90' \
--verbose

The expected result should output something similar to:

OK: memory total: 7.78 GB used: 5.83 GB (75.00%) free: 1.94 GB (25.00%)|
'memory.usage.bytes'=6261946368B;;;0;8349261824; 'memory.free.bytes'=2087315456B;;;0;8349261824; 'memory.usage.percentage'=75.00%;;;0;100

The above command checks a Ruckus ICX switch using the SNMP protocol (--plugin=network::ruckus::icx::snmp::plugin) with the public community (--snmp-community='public') and the 2c version (--snmp-version='2c'). This command checks the current memory usage of the switch (--mode='memory').

This command will trigger a WARNING alarm if the usage increases over 80% (--warning-usage='80') and a CRITICAL alarm over 90% (--critical-usage='90').

The syntax of the different options of the thresholds as well as the list of the options and their usage are detailed in the help of the mode by adding the parameter --help to the command:

/usr/lib/centreon/plugins/centreon_ruckus_icx_snmp.pl \
--plugin=network::ruckus::icx::snmp::plugin \
--mode=memory \
--help

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

/usr/lib/centreon/plugins/centreon_ruckus_icx_snmp.pl \
--plugin=network::ruckus::icx::snmp::plugin \
--list-mode

UNKNOWN: SNMP GET Request : Timeout​

If you get this message, it means that the Centreon poller is unable to contact the Ruckus ICX device on UDP port 161 or that the configured SNMP community is not correct. It is also possible that a firewall is blocking the flows.

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

This error message often refers to the following problems:

  • The Ruckus ICX device does not support the MIB used by the Plugin.
  • The targeted SNMP OID cannot be recovered due to insufficient equipment privileges.