This step by step guide shows how to configure the SNMP to monitor Access Points, Switches and Gateway/Firewall while the devices are being managed by Nebula, including a list of OIDs supported to monitor port status, CPU, etc.
3. Application example: querying device CPU current usage
1. Nebula SNMP configuration
Enable SNMP V1/V2c on NCC allows third party to monitor and configure Nebula devices according to the specified community string. This SNMP Community string with GET behaviors will apply to all the Nebula devices that are registered in the site, including AP, switches and Firewall.
The configuration procedure is as follow:
a. Go to Site Wide > Configure > General setting > SNMP
b. Set the SNMP Access to V1/V2c which are the versions supported on the devices while managed on Nebula.
c. Set the community string. This should also match in the SNMP server.
d. Click Save button
These are all the steps needed on the Nebula and the devices side. Now it's important to know what are the supported OIDs to know what can be monitored.
2. Supported OIDs
The MIB files for each device are included in the Firmware files available for each device. You can download the files here. Make sure you use the MIB files from the same firmware the device is running.
The following OIDs are the most common generally supported per device type:
Monitor information | Description | OID | Results example | Device supported |
Firmware version | The firmware version running by the device | .1.3.6.1.4.1.890.1.15.3.1.6.0 | V6.25(ABIN.2) | All |
Product model | The product model name | .1.3.6.1.4.1.890.1.15.3.1.11.0 | NWA1123-AC-HD | All |
Serial Number | The serial number of the device | .1.3.6.1.4.1.890.1.15.3.1.12.0 | S156N539012901 | All |
Country code | The country code set on the radio settings of device | .1.3.6.1.4.1.890.1.15.3.1.16.0 | Germany | All |
CPU usage | The current usage of device's CPU | .1.3.6.1.4.1.890.1.15.3.2.4.0 | 59 | All |
Memory Usage | The Memory current usage percentage | .1.3.6.1.4.1.890.1.15.3.2.5.0 | 57 | All |
Flash memory usage | The flash (non-volatile) usage percentage | .1.3.6.1.4.1.890.1.15.3.2.6.0 | 14 | AP / Firewall |
2.4Ghz Current Channel | The current channel being used on 2.4Ghz radio | .1.3.6.1.4.1.890.1.15.3.5.1.1.1.1 | channel-06_2437mhz (6) | AP |
2.4Ghz Channel | The channel set on 2.4Ghz radio | .1.3.6.1.4.1.890.1.15.3.5.1.1.6.1 | channel-06_2437mhz (6) | AP |
5Ghz Current Channel | The current channel being used on 5Ghz radio | .1.3.6.1.4.1.890.1.15.3.5.1.1.1.2 | channel-40_5200mhz (40) | AP |
5Ghz Channel | The channel set on 5Ghz radio | .1.3.6.1.4.1.890.1.15.3.5.1.1.6.2 | channel-40_5200mhz (40) | AP |
Total stations connected | The number of total wireless stations connected to the AP | .1.3.6.1.4.1.890.1.15.3.5.15.0 | 30 | AP |
More information can be obtained, to get this data, you might use an SNMP walk from the root OID: .1.3.6.1.4.1.890.1.15 (covered on next section).
Note: while the devices such switches and firewalls are being managed on the cloud, only the OIDs that are common (CPU, firmware, memory, etc) are supported.
3. Application example: querying device CPU current usage
For this example, we will query what's the status of the CPU on one of the AP in the network.
First the SNMP community is configured on Nebula Control Center here:
Configure -> Site settings
Then, we identify the IP address of the AP that we wish to monitor, in this case, 192.168.1.37. We need to make sure that the devices' configuration is already up-to-date.
Devices - Access Points
- We can then use one SNMP monitoring software in our local network to get the information needed. For this example, we will use the iReasoning MIB Browser. Once we get the software open, it is needed to type the IP address of the device we want to query, and also input the OID of the value we wish to monitor. It is also necessary to configure the SNMP community that we have set on Nebula Control center and the supported SNMP version:
- Click the Go button and the value will display the current CPU usage on the Access Point:
- If other values are needed, the firmware file that contains the MIB files can be downloaded and imported into the MIB Browser to check more parameters: