Details
-
New Feature
-
Resolution: Fixed
-
Minor
-
None
-
None
Description
Update to include more parameters for Cisco WLCs.
Current state of support shows only:
- Interfaces traffic;
- Temperature.
I've discovered Cisco WLC MIBs and how it is implemented in Observium and can supply following info:
- file "includes/definitions/os.inc.php" contains only "$config['os'][$os]['mibs'][] = "AIRESPACE-WIRELESS-MIB";" parameter for WLCs and config seciton for Cisco WLCs doesn't map it to "$config['os'][$os]['group'] = "cisco";" maybe that'll aid in monitoring of some WLC resources;
- MIB file called CISCO-LWAPP-SYS-MIB does containg "clsSysApConnectCount" - number of access points, currently connected to the WLC; I've verified, OID .1.3.6.1.4.1.9.9.618.1.8.4.0 to be working on WLCs w/ SW 7.4 and to be not working w/ SW 7.0, so this feature will be only for new WLCs; also It'll be nice to display this graph at the main page of device to track AP disappearing from WLC;
- MIB file called AIRESPACE-SWITCHING-MIB does contain info about CPU and Memory usage - agentCurrentCPUUtilization, agentTotalMemory, agentFreeMemory;
Ok, what I've found... At least with the 7.0 firmware, I don't find a list of "total" wireless clients associated using that WLC. However....
if we walk AIRESPACE-WIRELESS-MIB::bsnDot11EssSsid, we get a list of WLANs (ESSIDs) that are configured on the controller. Example:
root@observium:/opt/observium/mibs/cisco# snmpwalk -v 2c -c readstring -M +/opt/observium/mibs:/opt/observium/mibs/cisco -m AIRESPACE-WIRELESS-MIB:AIRESPACE-SWITCHING-MIB 172.20.1.203 AIRESPACE-WIRELESS-MIB::bsnDot11EssSsid
AIRESPACE-WIRELESS-MIB::bsnDot11EssSsid.1 = STRING: RRWireless
AIRESPACE-WIRELESS-MIB::bsnDot11EssSsid.2 = STRING: DirectBytes
AIRESPACE-WIRELESS-MIB::bsnDot11EssSsid.6 = STRING: WVOIP
Then, if we walk AIRESPACE-WIRELESS-MIB::bsnDot11EssNumberOfMobileStations, we get a count of clients associated to each of those WLAN/SSIDs. Example:
root@observium:/opt/observium/mibs/cisco# snmpwalk -v 2c -c readstring -M +/opt/observium/mibs:/opt/observium/mibs/cisco -m AIRESPACE-WIRELESS-MIB:AIRESPACE-SWITCHING-MIB 172.20.1.203 AIRESPACE-WIRELESS-MIB::bsnDot11EssNumberOfMobileStations
AIRESPACE-WIRELESS-MIB::bsnDot11EssNumberOfMobileStations.1 = Counter32: 0
AIRESPACE-WIRELESS-MIB::bsnDot11EssNumberOfMobileStations.2 = Counter32: 10
AIRESPACE-WIRELESS-MIB::bsnDot11EssNumberOfMobileStations.6 = Counter32: 2
These are obviously both from the same host WLC.
Now, if we can create a graph that uses this information, not unlike how the graph for disk i/o works under a storage device, we might have a winner? Of course this will also need to be checked against newer firmware controllers too...