graphing cisco 4400 wireless controllers

[egarnel]

has anyone tried pulling snmp info from the new cisco wcs stuff (airespace)?

[lard]

Hello,

Not yet - but I am just setting up some now - from the initial looks of it they seem to support most parts of the standard mib - certainly the interface stuff and uptime so that is a start,

If you have any more then let me know - I have the SNMP mib so in theory we can graph what we like such as active AP's e.t.c.

Let me know if you'd like a copy,

Thanks,

Lard

[egarnel]

I may have some stuff soon for associated clients, rssi, etc

[sp00f]

Would love to have some more information on this. Can you give us a little insight into what you are working on?

[egarnel]

making some progress. Here is a link that is extremely helpful
ftp://ftp.cisco.com/pub/mibs/oid/AIRESP ... SS-MIB.oid
and
ftp://ftp.cisco.com/pub/mibs/oid/AIRESP ... NG-MIB.oid

I have been able to glean some useful info so far:
bsnSensorTemperature" "1.3.6.1.4.1.14179.2.3.1.13"
bsnTemperatureAlarmLowLimit" "1.3.6.1.4.1.14179.2.3.1.14"
"bsnTemperatureAlarmHighLimit" "1.3.6.1.4.1.14179.2.3.1.15"
"agentTotalMemory" "1.3.6.1.4.1.14179.1.1.5.2"
"agentFreeMemory" "1.3.6.1.4.1.14179.1.1.5.3"

It appears that rssi, client info, etc is bound to the ap listings within snmp on the controller. you would have to identify which oid string is bound to which ap entry on the controller and then append the rest of of the oid string from there

For example: I have 21 APs on 1 controller anf the following OID maps # of users per AP

bsnApIfNoOfUsers" "1.3.6.1.4.1.14179.2.2.2.1.15"

Code: Select all

SNMPv2-SMI::enterprises.14179.2.2.2.1.15.0.11.133.81.138.240.0 = Counter32: 0
SNMPv2-SMI::enterprises.14179.2.2.2.1.15.0.11.133.81.138.240.1 = Counter32: 1
SNMPv2-SMI::enterprises.14179.2.2.2.1.15.0.11.133.81.139.0.0 = Counter32: 0
SNMPv2-SMI::enterprises.14179.2.2.2.1.15.0.11.133.81.139.0.1 = Counter32: 0
SNMPv2-SMI::enterprises.14179.2.2.2.1.15.0.11.133.81.139.112.0 = Counter32: 0
SNMPv2-SMI::enterprises.14179.2.2.2.1.15.0.11.133.81.139.112.1 = Counter32: 0
SNMPv2-SMI::enterprises.14179.2.2.2.1.15.0.11.133.81.140.0.0 = Counter32: 1
SNMPv2-SMI::enterprises.14179.2.2.2.1.15.0.11.133.81.140.0.1 = Counter32: 0
SNMPv2-SMI::enterprises.14179.2.2.2.1.15.0.11.133.81.141.64.0 = Counter32: 0
SNMPv2-SMI::enterprises.14179.2.2.2.1.15.0.11.133.81.141.64.1 = Counter32: 0
SNMPv2-SMI::enterprises.14179.2.2.2.1.15.0.11.133.81.141.144.0 = Counter32: 0
SNMPv2-SMI::enterprises.14179.2.2.2.1.15.0.11.133.81.141.144.1 = Counter32: 0
SNMPv2-SMI::enterprises.14179.2.2.2.1.15.0.11.133.81.141.240.0 = Counter32: 0
SNMPv2-SMI::enterprises.14179.2.2.2.1.15.0.11.133.81.141.240.1 = Counter32: 0
SNMPv2-SMI::enterprises.14179.2.2.2.1.15.0.11.133.81.142.144.0 = Counter32: 0
SNMPv2-SMI::enterprises.14179.2.2.2.1.15.0.11.133.81.142.144.1 = Counter32: 0
SNMPv2-SMI::enterprises.14179.2.2.2.1.15.0.11.133.81.142.160.0 = Counter32: 0
SNMPv2-SMI::enterprises.14179.2.2.2.1.15.0.11.133.81.142.160.1 = Counter32: 0
SNMPv2-SMI::enterprises.14179.2.2.2.1.15.0.11.133.81.143.80.0 = Counter32: 2
SNMPv2-SMI::enterprises.14179.2.2.2.1.15.0.11.133.81.143.80.1 = Counter32: 2

and the OID "bsnAP" "1.3.6.1.4.1.14179.2.2" gives you more info about the APs as well

I don't have enough time at the moment to dig thru the OIDs, but at least it is a start. At this point I am thinking that it would be very difficult to build a template that would include RSSI, client count, etc, but each controller entry in cacti would have to be hand crafted.

[cwahlin]

I know this is an old topic, but has anyone made any progress on this?

My idea is to make some sort of query to get APs and whatnot from the WCS. We already have 6 of these controllers, and I think we might end up with over 10 of them this year. The WCS server does not seem to keep historical data, so getting all this into cacti would be nice.

Although, currently I am trying to get Axxceleras MIB sorted so I can get some usefull info from their WiMAX accesspoints... So... it might be a while before I get started on this...

/Carl

[andys]

We're testing a 4400 controller at the moment and i'm trying to get it working with Cacti. Heres what i've got so far. I've made a host template that polls the 4400 for Temperature,Memory Usage and CPU Usage.

There is an additional Data Query that polls the 4400 for a list of configured WLANS. When you create graphs for the 4400, put a tick against a WLAN and Cacti will poll for the number of associated users.

The Template seems to work OK if anyone wants to try it. To install, import the cacti_host_template_cisco_4400_controller.xml file through the Cacti import utility and copy cisco4400wlanassoc.xml to the \resource\snmp_queries folder on your Cacti server.

The template only seems to work when snmp v1 is used - i had to enable smnp v1 on the 4400 Controller.

Is there anyone else working on templates for the 4400?? How far have you got?

cheers
andy

[andys]

forgot to add that templates were done in 0.8.6j
andy

[egarnel]

Sweet! The templates work like a champ. Thanks for doing them

[egarnel]

added in the following cdef to convert temp to farenheit

cdef=CURRENT_DATA_SOURCE,1.8,*,32,+

[egarnel]

exported temperature template with conversion to Fahrenheit

[andys]

Ive written some PHP scripts to add further functionality to the template. Im using PHP 5.1.6.6 on win2003 server with cacti 0.8.6j. The Host Template now contains:-


Graph Templates:

1) Cisco 4400 - AP Radios
This polls and graphs the 4400 Controller for the number of a/b/g radios associated with the controller . The script for this is called query_4400_APifType.php.

2) Cisco 4400 - CPU Usage
No change from last Host template.

3) Cisco 4400 - Memory Usage
No change from last Host template.

4) Cisco 4400 - Temperature
No change from last Host template.

Data Queries:

1) Cisco 4400 AP Assoc Query
This Script Query Cisco4400_APs.xml calls the PHP script query_cisco4400_aps.php. The script query returns the APs MAC address, Name, IP Address and Serial Number. Placing a tick beside a particular AP will graph the number of associations for that AP.

2) Cisco 4400 Interface Assoc Query
This Script Query Cisco4400_interfaces.xml calls the PHP script query_cisco4400_interfaces.php. The script query returns the Controllers Interfaces Name, VLAN ID and IP Address. Placing a tick beside a particular Interface will graph the number of associations for that Interface.


3) Cisco 4400 WLAN Assoc Query
No change from last Host template.

andys

[andys]

I

[andys]

Ive

[andys]

does anyone have any feedback from using these templates/scripts - any suggestions?
thanks
andy