05-15-2006 09:07 AM - edited 07-04-2021 12:04 PM
I've not been able to find any OIDs on a controller to be able to tell what clients are associated to what APs in a lightweight system.
Anyone know if this is possible and if so what are they?
thanks,
05-19-2006 09:13 AM
show client summary
show client detail
05-23-2006 03:33 PM
Hi...maybe this would meet your needs?:
.1.3.6.1.4.1.9.9.273.1.2.1.1
cDot11ClientConfigInfoEntry OBJECT-TYPE
-- FROM CISCO-DOT11-ASSOCIATION-MIB
INDEXES { ifIndex, cd11IfAuxSsid, cDot11ClientAddress }
DESCRIPTION "Each entry is the device specification of a client
of this device on the IEEE 802.11 radio interfaces.
Clients are grouped according to the SSIDs of the
interfaces they use for associations and the MAC
address of their parent devices if the clients are
repeat APs."
05-24-2006 04:14 AM
not sure. snmpwalk returns end of mib (v1) or no such object available... (v2c) when run against a controller running the latest rev.
Perhaps that mib is for the aironet radios and not for the lwapp solution?
I have been digging around on the adventnet site for similar info. The WCS server is/was an adventnet product and is snmp based, so the values must be pulled from somewhere. Haven't had time to mull through the MIB files from Cisco
05-24-2006 05:53 AM
TAC pointed me to the Airespace mibs, which are under CCO within the wireless controller section (Cisco-WLC-MIBS).
Also, snmpwalk was not showing me the Airespace private vars until I specified to walk that section which is .1.3.6.1.4.1.14179.
I did note that the bsnwras MIB tries to import what I assume is a now deprecated MIB (?) as I could not find any related info on it.
airespace
FROM AIRESPACE-REF-MIB;
07-14-2006 05:12 AM
after some digging, I found this:
ftp://ftp.cisco.com/pub/mibs/oid/
it has entries for airspace among other devices as well
10-16-2006 08:48 PM
Just to add to the previous posts, here is a great link for surfing down the MIB tree:
I found some good client info at:
1.3.6.1.4.1.14179.2.1.4.1
Nothing was exactly what you needed, but you could probably assemble a script to merge several columns. .4 shows the MAC of the AP each client is on, but you would have to merge it with another oid such as .1, .2, or .3 to make the client info meaningful.
Oh, this is all in 3.x. I haven't confirmed the oids are the same in 4.x.
-Eric
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide