I am having issues with clients re-associating to corporate network after Aging time expires, once laptops are connected the first time (through AD group that I place laptops in it). We are using ACS, under Windows EAP settings, Machine Authentication and PEAP machine authentication is enabled. So I have to reboot the device in order to re-connect corporate which is using WPA2, AES, CCKM in Layer 2.
You could adjust the session timeout under the WLAN--SSID on the controller to 28800secs. This is equal to 8 hr working day. If this doesn't resolve your problem then you also alter the PEAP session timeout on the ACS. You would have to tell me which version of ACS you have so that I can tell you the menu to find PEAP sesseion timeout.
my main goal is to have the laptops maintain connectivity once the aging time elapsed, and that`s the issue wether aging time is set to 12hrs (default) or higher, laptops will not re-conect (re-associate).
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
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 f...