I am not sure if this would answer your query, but this is what I managed to find -
The location appliance can track up to 2,500 elements. You can track the following elements: client stations, active asset tags and rogue clients and access points.Updates on the locations of elements being tracked are provided to the location server from the Cisco wireless LAN controller.
Only those elements designated for tracking by the controller are viewable in Cisco WCS maps, queries and reports. No events and alarms are collected for non-tracked elements and they are not used in calculating the 2,500 element limit.
You can modify the following tracking parameters using Cisco WCS:
â¢Enable and disable which element locations (client stations, active asset tags; and rogue clients and access points) you actively track
â¢Set limits on how many of a specific element you want to track
You can set limits on how many of a specific element you wish to track. For example, given a limit of 2,500 trackable units, you could set a limit to track only 1,500 client stations. Once the tracking limit is met, the number of elements not being tracked is summarized on the Tracking Parameters page.
â¢Disable tracking and reporting of ad hoc rogue clients and access points
In addition to this I found a resolved issue in release 220.127.116.11 -
CSCse76683-Previous to this release, once the 2,500 limit of supported elements for the location appliance was met, no new location calculations were reported for any element beyond the 2,500 limit. Location calculations were reported once an element within the recognized 2,500 elements aged out. This condition occurred even when polling was turned "off."
The location calculation is not happenning for some of the elements. There are ERROR events saying 'Location limit hit, can not add any more location elements'. Even if the polling is turned OFF for the type of element that are too many, the location is not calculated for new elements.
Transferring Crash file from standby:
Login to the Active WLC in HA.
(Cisco Controller) >transfer upload datatype crash
(Cisco Controller) >transfer upload filename <Desired filename>
(Cisco Controller) >transfer up...
This is the start of a display filter cross reference between Wireshark and OmniPeek.
The 1st installment is a table of advanced filters. More filters will be added as time allows.
It is a living doc, so check back for changes every so often
Please feel ...
I have created a Powershell script to automatically add a Wireless Guest User on Cisco WLCs. (tested on 2500 Series)
The script should be completely self explanatory.
Powershell SNMP Module (Install-Module -Name SNMP)
SNMP Write Access to...