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;
Attachments
Activity
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...
Yeah, I'm not being presented with "wireless" under "graphs" for either the WISM or the WLC4402, thus maybe the device isn't providing the information via whatever OID is being polled. I seem to recall an OID that presented that information, but I'll have to walk the unit to figure it out.
Did not quite understand what you mean.
Wireless graphs should be here: Device -> Graphs -> Wireless
If nothing here, than your device not provide this data.
Dunno about that, just svn upped to 6096, rediscovered and re-polled, and:
0. 4400 Series WLAN Controller:25 APs
4400 Series WLAN Controller:25 APs
0. Cisco Wireless Access Point
Cisco Wireless Access Point
0. Cisco Wireless Access Point
Cisco Wireless Access Point
0. 802.11N 2.4GHz Radio
802.11N 2.4GHz Radio
0. 802.11N 5GHz Radio
802.11N 5GHz Radio
0. Cisco Wireless Access Point
Cisco Wireless Access Point
0. 802.11N 2.4GHz Radio
802.11N 2.4GHz Radio
0. 802.11N 5GHz Radio
802.11N 5GHz Radio
0. Cisco Wireless Access Point
Cisco Wireless Access Point
0. 802.11N 2.4GHz Radio
802.11N 2.4GHz Radio
0. Cisco Wireless Access Point
Cisco Wireless Access Point
0. 802.11N 2.4GHz Radio
802.11N 2.4GHz Radio
0. 802.11N 5GHz Radio
802.11N 5GHz Radio
0. Cisco Wireless Access Point
Cisco Wireless Access Point
0. 802.11N 2.4GHz Radio
802.11N 2.4GHz Radio
0. 802.11N 5GHz Radio
802.11N 5GHz Radio
0. Cisco Wireless Access Point
Cisco Wireless Access Point
0. Cisco Wireless Access Point
Cisco Wireless Access Point
0. 802.11N 2.4GHz Radio
802.11N 2.4GHz Radio
0. 802.11N 5GHz Radio
802.11N 5GHz Radio
So yeah, I'm using older equipment but hey, it still works... 
On a WLC4402, I don't see any graphs at all. Inventory is showing:
0. 4400 Series WLAN Controller:25 APs
4400 Series WLAN Controller:25 APs
0. Cisco Wireless Access Point
Cisco Wireless Access Point
0. Cisco Wireless Access Point
Cisco Wireless Access Point
0. 802.11N 2.4GHz Radio
802.11N 2.4GHz Radio
0. 802.11N 5GHz Radio
802.11N 5GHz Radio
Conversely, I also have a WISM that I'm monitoring... it likewise doesn't show any graphs, but at least it's showing inventory correctly:
WS-SVC-WISM-1-K9 (Chassis)
Cisco Wireless Controller [Serial: xxxxxxxxxxx]
AIR-LAP1142N-A-K9 (Cisco AP)
Cisco Wireless Access Point [Serial: xxxxxxxxxxx]
2. UNKNOWN (Dot11Radio0)
802.11N 2.4GHz Radio [Serial: xxxxxxxxxxx]
1. UNKNOWN (Dot11Radio1)
802.11N 5GHz Radio [Serial: xxxxxxxxxxx]
AIR-LAP1142N-A-K9 (Cisco AP)
Cisco Wireless Access Point [Serial: xxxxxxxxxxx]
2. UNKNOWN (Dot11Radio0)
802.11N 2.4GHz Radio [Serial: xxxxxxxxxxx]
1. UNKNOWN (Dot11Radio1)
802.11N 5GHz Radio [Serial: xxxxxxxxxxx]
AIR-LAP1242AG-A-K9 (Cisco AP)
Cisco Wireless Access Point [Serial: xxxxxxxxxxx]
AIR-LAP1131AG-A-K9 (Cisco AP)
Cisco Wireless Access Point [Serial: xxxxxxxxxxx]
AIR-LAP1220-IOS-UPGRD (Cisco AP)
Cisco Wireless Access Point [Serial: xxxxxxxxxxx]
But `Wireless Clients` graph seems to draw count of APs, connected to the WLC, not clients.
Great thanks, Mike. I've upgraded to r6095, WLC monitoring is much more granular now 
I'd also note that there's a way to determine number of client devices per access point, but personally I really don't want to go there... especially when you're dealing with an environment that may contain a couple THOUSAND access points instead of the few tens of access points that we may have.