I have seen several aironets reporting that the "Last Activity Time (secs)" of a wireless client is greater than the "Activity TimeOut (sec)" for the same station.
I have seen many clients listed as having a "Last Activity Time" of over 3 weeks.
Is there a way to ensure these inactive associations are pruned effectively? It seems the "Activity TimeOut" option is not taking effect as there are some clients which have considerably passed the configured value.
The Default value for all stations is set to 60 secs (IOS default). And I see some stations with no "Activity TimeOut" value listed in the association, aswell as the aforementioned stations where the "Activity TimeOut" is lower than the "Last Activity Time".
From the options in the Left Hand Side under Assocation Menu you can set the Activity Timeout value. Try setting both the default and Maximum timeout value. If it doesnt work try to reset or upgrade IOS.
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...