Skip to main content

ArubaOS-CX SNMP

Plugin Pack Assets​

Monitored Objects​

The Plugin Pack ArubaOS-CX SNMP collects metrics for:

  • Hardware
  • Interfaces
  • Vsf
  • Vsx

Discovery rules​

Rule nameDescription
Net-Aruba-Aoscx-SNMP-Interface-NameDiscover network interfaces and monitor bandwidth utilization

Collected Metrics​

Metric nameDescriptionUnit
fan_name#hardware.fan.speed.rpmSpeed of the fanrpm
fan tray statusStatus of the fan tray
psu statusStatus of the power supply
psu_name#hardware.psu.power.wattPower consumption of the power supplyW
temperature statusStatus of the sensor
sensor_name#hardware.temperature.celsiusTemperature of the sensorC

Prerequisites​

To monitor your Aruba, the SNMP must be configured. The Poller should be able to perform SNMP requests toward the Infoblox device over SNMP UDP/161 port.

Setup​

  1. Install the Centreon Plugin on every Poller:
yum install centreon-plugin-Network-Aruba-Aoscx-Snmp
  1. On the Centreon Web interface in "Configuration > Plugin packs > Manager", install the ArubaOS-CX SNMP Plugin Pack

Host configuration​

  • Add a new Host and fill the IP Address/FQDN, SNMP Version and SNMP Community fields according to the device's configuration
  • Apply the Net-Aruba-Aoscx-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
SNMPEXTRAOPTIONSConfigure your own SNMPv3 credentials combo

How to test the Plugin and what are the main options for?​

Once the plugin installed, log into your Centreon Poller CLI using the centreon-engine user account and test the Plugin by running the following command:

/usr/lib/centreon/plugins/centreon_aruba_aoscx_snmp.pl \
--plugin=network::aruba::aoscx::snmp::plugin \
--mode=vsf \
--hostname=10.30.2.114 \
--snmp-version='2c' \
--snmp-community='aruba_ro' \
--warning-cpu-utilization='90' \
--critical-cpu-utilization='95' \
--verbose

Expected command output is shown below:

OK: vsf operational status: no_split - All stack members are ok | '1#member.cpu.utilization.percentage'=16.00%;0:90;0:95;0;100 '1#member.memory.usage.percentage'=24.00%;;;0;100 '2#member.cpu.utilization.percentage'=4.00%;0:90;0:95;0;100 '2#member.memory.usage.percentage'=14.00%;;;0;100 '3#member.cpu.utilization.percentage'=4.00%;0:90;0:95;0;100 '3#member.memory.usage.percentage'=8.00%;;;0;100 '4#member.cpu.utilization.percentage'=4.00%;0:90;0:95;0;100 '4#member.memory.usage.percentage'=8.00%;;;0;100
checking stack member '1'
role: master [status: ready]
cpu usage: 16.00%
memory used: 24.00 %
checking stack member '2'
role: standby [status: ready]
cpu usage: 4.00%
memory used: 14.00 %
checking stack member '3'
role: member [status: ready]
cpu usage: 4.00%
memory used: 8.00 %
checking stack member '4'
role: member [status: ready]
cpu usage: 4.00%
memory used: 8.00 %

The command above monitors Aruba (--plugin=network::aruba::aoscx::snmp::plugin --mode=vsf) identified by the IP address 10.30.2.114 (--hostname=10.30.2.114). As the Plugin is using the SNMP protocol to request the device, the related community and version are specified (--snmp-version='2c' --snmp-community='aruba_ro').

This command would trigger a WARNING alarm if cpu utilization over 90% (--warning-cpu-utilization='90') and a CRITICAL alarm over 95% (--critical-cpu-utilization='95').

All the options as well as all the available thresholds can be displayed by adding the --help parameter to the command:

/usr/lib/centreon/plugins/centreon_aruba_aoscx_snmp.pl \
--plugin=network::aruba::aoscx::snmp::plugin \
--mode=vsf \
--help

Troubleshooting​

UNKNOWN: SNMP GET Request : Timeout​

If you get this message, you're probably facing one of theses issues:

  • The SNMP agent of the device isn't started or is misconfigured
  • An external device is blocking the request (firewall, ...)

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

This error message often refers to the following issues:

  • The agent 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: .1.3.6.1.4.1.47196.4