WLC 4404 Upgraded to 7.0.235.3 (WPA HandShake Timeout) not availbale

Greetings,
Just upgraded my Cisco 4404 WLC's to 7.0.235.3, the upgrade went just fine. My problem is when I either Telnet or SSH to my Lightweight AP's and run the "DOT11 WPA Handshake Timeout 1000" command the AP doesn't recognized this command. This is one of the reasons I upgrade my WLC's.I have several wireless printers that are passive and are heavily used and keep getting disassociated because they don't respond in time.
Any Help would be greatly appreciated.

that command is for IOS AP, not for the WLC.
Q.    How do you change the Wi-Fi Protected Access (WPA) handshake timeout   value on a Wireless LAN Controller (WLC) through CLI? I know I can do this on   Cisco IOS® Access Points (APs) with the dot11 wpa handshake   timeout value command, but how do you   perform this on a WLC?
A. The ability to configure the WPA-Handshake timeout through the WLCs was       integrated in software release 4.2 and later. You do not need this option in       earlier WLC software versions.
These commands can be used to change the WPA Handshake timeout:
    config advanced eap eapol-key-timeout
    config advanced eap eapol-key-retries
The default values continue to reflect the WLCs current       behavior.
   - the default value for eapol-key-timeout is 1 second.
   - the default value for eapol-key-retries is 2 retries
Note: On IOS APs, this setting is configurable with the dot11           wpa handshake command.
HTH,
Steve
Please remember to rate useful posts, and mark questions as answered

Similar Messages

What impacts has the extension of WPA Handshake timeout

Hello folks,
we use barcode scanner via WLAN. Unfortunately I have trouble with the authentication of the WLAN clients. The manufacturer of the barcode scanner recommended that I should extend the WPA handshake timeout to 2000 ms.
All the APs in our network are managed by WLAN controller. My investigation shows me that the EAPOL-Key Timeout is already set to 1000 ms. This value is set on all APs which are managed by the controller. I have other SSIDs and applications running via WLAN. I looked for a description about the impacts of the extension of the WPA handshake timeout. But I couldn't find any.
Has anybody here in the community experiences with the extension of the WPA handshake timeout and the possible impacts (e.g. to roaming)?
Thanks for your support in advance.
Peter

Q. How do you change the Wi-Fi Protected Access (WPA) handshake timeout value on a Wireless LAN Controller (WLC) through CLI? I know I can do this on Cisco IOS® Access Points (APs) with the dot11 wpa handshake timeout value command, but how do you perform this on a WLC?
A. The ability to configure the WPA-Handshake timeout through the WLCs was integrated in software release 4.2 and later. You do not need this option in earlier WLC software versions.
These commands can be used to change the WPA Handshake timeout:
    config advanced eap eapol-key-timeout
    config advanced eap eapol-key-retries
The default values continue to reflect the WLCs current behavior.
   - the default value for eapol-key-timeout is 1 second.
   - the default value for eapol-key-retries is 2 retries
Note: On IOS APs, this setting is configurable with the dot11 wpa handshake command.
You can also configure the other EAP parameters with the options under the config advanced eap command.
(Cisco Controller) >config advanced eap ?
eapol-key-timeout
   Configures EAPOL-Key Timeout in seconds.
eapol-key-retries
   Configures EAPOL-Key Max Retries.
identity-request-timeout
   Configures EAP-Identity-Request Timeout in seconds.
identity-request-retries
   Configures EAP-Identity-Request Max Retries.
key-index
   Configure the key index used for
   dynamic WEP(802.1x) unicast key (PTK).
max-login-ignore-identity-response
   Configure to ignore the same username count
   reaching max in the EAP identity response
request-timeout
   Configures EAP-Request Timeout in seconds.
request-retries
   Configures EAP-Request Max Retries.

Wlc 4404 upgrade

Hi, looking for advice on which code to upgrade to. We have a wlc 4404 using mostly AIR-AP1231G-A-K9 access points. The current code is 4.2.130.0. We would like to use some of the 1141 APs and I understand they need at least 5.2. My plan would be to go to 6. I believe I need to go to 4.2.176.0 first and then to 6. The question would be what version of 6 would be the best? Right now 6.0.182.0 (ED), 6.0.188.0 (ED), and 6.0.196.0 (ED) are available.

Well that is a tricky question and really depends on a lot of variables. We have installs with all three versions of the software. Currently I would have to say that 6.0.188.0 is one to try. We have upgraded some clients to 6.0.196.0 because of issue with the 6.0.188..0, but again, it all depends what equipment you have and if you see any issues with the 6.0.188.0. Some people I know have just went right to the 6.0.196.0 code and have not seen any issues. The 6.x is still pretty new in my book, but like you already did..... review the caveats on the different versions and if you have a spare WLC,do some testing.

WLC 4402 upgrade to 7.0.235.3 -- high latency

Hi All,
Since we've upgraded the 4402 (from 4-2-176-0) to 7.0.235.3 many client facing very high latency.
We're having 12 x 1142 APs and they are connected in local mode to WLC.
Before the upgrade performance was good. Now, when I ping from LAN to WLAN clients it takes from 0.1ms - 20s.
64 bytes from 10.123.60.210: icmp_seq=58 ttl=127 time=4711 ms
64 bytes from 10.123.60.210: icmp_seq=59 ttl=127 time=3711 ms
64 bytes from 10.123.60.210: icmp_seq=60 ttl=127 time=2712 ms
64 bytes from 10.123.60.210: icmp_seq=61 ttl=127 time=1713 ms
64 bytes from 10.123.60.210: icmp_seq=62 ttl=127 time=754 ms
64 bytes from 10.123.60.210: icmp_seq=63 ttl=127 time=3.12 ms
64 bytes from 10.123.60.210: icmp_seq=64 ttl=127 time=1109 ms
64 bytes from 10.123.60.210: icmp_seq=65 ttl=127 time=109 ms
64 bytes from 10.123.60.210: icmp_seq=66 ttl=127 time=0.949 ms
I cant find any pattern..seems to happen to random clienst at radom time.
Any ideas..or further checks I can do?
Thanks a lot,
Stefan

All is set to auto.

Wlc 4404 upgrade software version

I have two wireless controllers ( software version 5.1.151.0 ) . Is this vesion supports AP 1142 N .
also what is the required version to support AP 1142 N .
If the controllers upgraded to new version , will it affect the APs license for existing software version or no .
regards,

But I would recommend you going to the latest 7.0.230.0.
Using this now. During the upgrade from 7.0.220.0 to this version, I nearly had a heart attack! The upgrade of the "ER" was fast, no worries. The upgrade of the firmware, took AGES! Next, when the WAPs rebooted, they downloaded and rebooted TWICE!

Upgrade BootLoader on Cisco WLC 4404

What is the latest Bootloader for the Cisco WLC 4404? And where can I download it?
My current versions are:
Product Version.................................. 5.2.178.0
RTOS Version..................................... 5.2.178.0
Bootloader Version............................... 4.0.206.0
Also is there a reason to upgrade the bootloader image?
On this webpage http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00805f381f.shtml it shows the steps to upgrade WLC are :
This sequence is recommended for your WLC software upgrade:
Upload a backup of your controller configuration to a TFTP server.
Disable the 802.11a and 802.11b/g networks on your controller.
Upgrade the primary image on your controller.
Upgrade the boot image on your controller.
Note: This is a required step for upgrades to 4.1 on the WiSM, 3750G Wireless LAN Controller, and 4400 Series Controllers.
Re-enable the 802.11a and 802.11b/g networks on your controller.
I get the primary image is just going to be AIR-WLC4400-K9-6-0-196-0.aes. But where do i download the Bootloader and it looks like i just do the same thing i did with the primary image.
I think I am missing something.
Thanks

The boot software image consists of the controller boot kernel and boot menu script. that is.. when you use the WLC for the first time. then you will be able to use this while entering the username, mobility information.. interfaces informations etc.. the Software version is the one which you issue CLI commands...or even simple example wil be.. reboot the WLC and hit ESC.. the software that you access at this time will be boot loader..
to upgrade the bootloader...
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00805f381f.shtml#hw
Regards
Surendra

Upgrade from 7.0.235 to 7.0.240 5508 WLC

Does anyone see a reason to upgrade from 7.0.235 to 7.0.240? I can't go any higher right because we are still using WCS. I read the white papers but as far as I can tell there are no new features..

Leo is a risky Australian.... beware
You might be able to get it to work, just Cisco will not support it. They need to keep the LifeCycle going $$$$$$$
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"

What settings need to be set for the fastest roaming on my wlc 4404

Hi all
I notice that on my WLC 4404 when walking around with my laptop, I am dropping pings when it roams to another access point, Is there anything on the controller I need to check, and can I optimize these settings for roaming?
cheers
carl

Hello Carl,
to have romaing working fine you need to be sure of following:
1) RF designed correctly , and enough overlapping is availble between the AP's.
in addition for environment to be free from external noise..
this can be confirmed with spectrum expert site survey
2) what authentication and encryption used ( WEP , or WPA-PSK no need to check this point ->> skip :-) )
if you are using any authentication like 802.1x ->> then enable CCKM on the WLAN to make more seamless roaming.
3) if more than one WLC availble on site , configure mobility group between them,
so if client roam from one AP in WLC 1 to AP on WLC 2 ->> no disocnnection observed....
Kind regards
Talal
===========
please rate answers that you find useful , and mark as answered - when it is :-) - so others can find it easily

Decrypt Errors - WLC 4404

Hello,
We recently had a few clients being locked down with countermeasures by our WLC 4404 due to TKIP-MIC errors. After doing some reading on the benefits of AES over TKIP I switched our WLAN security settings to AES, and pushed a new wireless policy to our client machines. Every thing appeared to work well, except now the trap log on the 4404 is showing a LOT of WPA decrypt errors. I've checked a few of the clients that appear to have problems, but they've got the right policy and WPA settings to match what is on the WLC.
It's not one particular NIC, it's various clients.
Any thoughts on how I might clear these up?
Rob

One reason for that is configuration of two WEP keys on a single WLAN is not supported. Currently WLAN can only take one WEP key.

WLC 5508 upgrade

Hi All,
We currently have 4 x WLC 5500 (AIR-CT5508-K9) V01 and V02
So two in one datacenter and the other two in another datacenter. They are connected via Mobility group to and BOYD open wifi with an Anchor WLC the other 1.
All four of them are 7.4.110.0 and the APs we use are AIR-LAP1142N-E-K9 and AIR-CAP2602I-E-K9.
We are looking to get 2700 or 3700 AP so we can use 802.11ac, but we need to upgrade all WLC to 7.6.130.0.
1. is it a direct upgrade from 7.4.110.0 to 7.6.130.0?
2. If I upgrade one datacenter one weekend and the other next weekend, during that week two WLC would be 7.4 and other two 7.6 would it break or cause issue with Mobility group to and BOYD open wifi with an Anchor WLC?
3. Can any please provide step to step guide for the upgrade from 7.4 to 7.6?
Many Thanks
appreciate it :)

Hi Rasika,
Many Thanks for your reply and help!
1. In regards to Upgrade the FUS, is it required to be upgraded once the WLC are upgraded to 7.6 or is just good practice?
2. Or I can I upgrade the FUS another time?
Here is our sysinfo
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.4.110.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS
System Name...................................... bupa-sw_sta-un1-dcwlc
System Location.................................. Unit1 DC
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Redundancy Mode.................................. Disabled
IP Address....................................... 10.96.5.10
Last Reset....................................... Software reset
System Up Time................................... 448 days 13 hrs 9 mins 12 secs
System Timezone Location......................... (GMT) London, Lisbon, Dublin, Edinburgh
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
Configured Country............................... GB - United Kingdom
Operating Environment............................ Commercial (0 to 40 C)
--More-- or (q)uit
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +39 C
External Temperature............................. +26 C
Fan Status....................................... OK
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 7
Number of Active Clients......................... 572
Memory Current Usage............................. Unknown
Memory Average Usage............................. Unknown
CPU Current Usage................................ Unknown
CPU Average Usage................................ Unknown
Burned-in MAC Address............................ 64:00:F1:F1:1E:40
Power Supply 1................................... Present, OK
Power Supply 2................................... Absent
Maximum number of APs supported.................. 175
3. Also once Ive upgraded the WLCs from 7.4 to 7.6, should I reboot the WLC and let it upgrade all APs, the upgrade the FUS or upgrade FUS after upgrading the WLC without the reboot which is required?
Many Thanks,
Zilad

WLC 4404 Wireless users getting disabled

Currently Being Moderated
Wireless users getting disabled
Hi,
I have WLC 4404 with 7.0.116.0 version. I was getting following messages for particular APs
*Dec 20 14:11:13.875: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Dec 20 14:11:13.908: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Dec 20 14:11:29.383: %LWAPP-5-RLDP: RLDP stopped on slot 0.
*Dec 20 14:11:29.674: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Dec 20 14:11:29.678: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Dec 20 14:11:29.700: %LWAPP-5-RLDP: RLDP started on slot 0.
*Dec 20 14:11:29.707: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Dec 20 14:11:29.752: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Dec 20 14:11:29.757: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Dec 20 14:11:29.790: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Dec 20 14:11:45.396: %LWAPP-5-RLDP: RLDP stopped on slot 0. *Dec 20 14:11:13.875: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
After seeing one of the cisco forum, I have disabled RLDP for that particular APs
so above messages are rectified.
But right now we are not able to identify Rogue IP and it is not contained.
So please give any suggetion so that i can rectify the above messages as well as i can identify the rogue IP.
Thanks & Regards
Gaurav Pandya

Hi Scott,
You are right i am not able to detect rogue APs because i disabled the RLDP. but when i enable the RLDP for that particular AP. i got the following messages with interface go up and down
*Dec 20 14:11:13.875: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Dec 20 14:11:13.908: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Dec 20 14:11:29.383: %LWAPP-5-RLDP: RLDP stopped on slot 0.
*Dec 20 14:11:29.674: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Dec 20 14:11:29.678: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Dec 20 14:11:29.700: %LWAPP-5-RLDP: RLDP started on slot 0.
So please suggest me the mid way so that i can enable the RLDP (Detect the rogue APs) with out interface going up and down frequently.
Regards
Gaurav

Wireless clients load balancing on the APs on WLC 4404

Hi Experts,
I'm just wondering if the WLC 4404 with firmware 4.2.207.0 can load balance the wireless clients on different WAPs. Let's say that an AP is already handling 15 Wireless devices. When the 16th is trying to join, the controller somehow puts it on another nearby AP, even the signal from this AP is weaker. I heard the similar feature on other Wireless solution vendors. I'm just wondering if Cisco has the similar feature or not.
Thanks!

Yes it is known as aggressive load balancing sending a code 17 making the wireless client to loook at another nearby AP.
here it is the documentation:
http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00809c2fc3.shtml

WLC Firmware upgrade

I am working on a firmware upgrade on WLC 5508 and WLC 2100 from 7.2.111.3 to 7.4.121. I have 10 forign controllers and 2 anchor controllers. My question are:
(1) Should I upgrade the forign controllers first or anchor controllers first?
(2) Should I or do I need to upgrade Cisco NCS, 1.1.1.24, after the WLC firmware upgrade?
(3) SHould I or do I need to upgrade CIsco MSE to latest version?
Thanks,

(1) Should I upgrade the foreign controllers first or anchor controllers first?
Does not matter the order.
Make sure you upgrade the FUS to 1.9.0.0 version as well
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/fus_rn_OL-31390-01.html
(2) Should I or do I need to upgrade Cisco NCS, 1.1.1.24, after the WLC firmware upgrade?
Refer the below link (table 4) compatibility matrix, you should have NCS/Prime 1.3.x
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html#wp142297
(3) Should I or do I need to upgrade CIsco MSE to latest version?
Refer the table 7 of the above link, you should have MSE 7.4.121.0 as well for compatibility
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html#wp142297
HTH
Rasika
**** Pls rate all useful responses ****

WLC 4404 %OSAPI-3-FILE_OPEN_FAILED

the WLC 4404 present this logs:
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-FILE_OPEN_FAILED: osapi_file.c:370 Failed to open the file : /proc/927/stat.(erno 24)
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-TASK_GETTIME_FAILED: osapi_task.c:3431 Failed to retrieve statistics (/proc/<pid>/stats) for task 'gccp_t'
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-FILE_OPEN_FAILED: osapi_file.c:370 Failed to open the file : /proc/926/stat.(erno 24)
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-TASK_GETTIME_FAILED: osapi_task.c:3431 Failed to retrieve statistics (/proc/<pid>/stats) for task 'dot1dTimer'
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-FILE_OPEN_FAILED: osapi_file.c:370 Failed to open the file : /proc/925/stat.(erno 24)
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-TASK_GETTIME_FAILED: osapi_task.c:3431 Failed to retrieve statistics (/proc/<pid>/stats) for task 'dot1dRecv'
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-FILE_OPEN_FAILED: osapi_file.c:370 Failed to open the file : /proc/921/stat.(erno 24)
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-TASK_GETTIME_FAILED: osapi_task.c:3431 Failed to retrieve statistics (/proc/<pid>/stats) for task 'fdbTask'
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-FILE_OPEN_FAILED: osapi_file.c:370 Failed to open the file : /proc/920/stat.(erno 24)
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-TASK_GETTIME_FAILED: osapi_task.c:3431 Failed to retrieve statistics (/proc/<pid>/stats) for task 'nPCSL_timer'
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-FILE_OPEN_FAILED: osapi_file.c:370 Failed to open the file : /proc/916/stat.(erno 24)
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-TASK_GETTIME_FAILED: osapi_task.c:3431 Failed to retrieve statistics (/proc/<pid>/stats) for task 'tFrameReceive'
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-FILE_OPEN_FAILED: osapi_file.c:370 Failed to open the file : /proc/913/stat.(erno 24)
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-TASK_GETTIME_FAILED: osapi_task.c:3431 Failed to retrieve statistics (/proc/<pid>/stats) for task 'tFrameReceive'
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-FILE_OPEN_FAILED: osapi_file.c:370 Failed to open the file : /proc/917/stat.(erno 24)
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-TASK_GETTIME_FAILED: osapi_task.c:3431 Failed to retrieve statistics (/proc/<pid>/stats) for task 'tFrameSend'
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-TASK_GETTIME_FAILED: osapi_task.c:3431 Failed to retrieve statistics (/proc/<pid>/stats) for task 'Gmac Link Task'
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-FILE_OPEN_FAILED: osapi_file.c:370 Failed to open the file : /proc/905/stat.(erno 24)
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-TASK_GETTIME_FAILED: osapi_task.c:3431 Failed to retrieve statistics (/proc/<pid>/stats) for task 'tDapiTxTask'
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-FILE_OPEN_FAILED: osapi_file.c:370 Failed to open the file : /proc/904/stat.(erno 24)
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-TASK_GETTIME_FAILED: osapi_task.c:3431 Failed to retrieve statistics (/proc/<pid>/stats) for task 'RMONTask'
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-FILE_OPEN_FAILED: osapi_file.c:370 Failed to open the file : /proc/903/stat.(erno 24)
when present this loggs the device present those symptoms:
lost GUI session
Lost console conection
Lost SSH and Telnet conecction
the WLC 4404 not work is stopedd

Almost looks like it could be defect ID CSCtx02515. SHows that it's fixed in 7.2.110.0, but if you have a 4404, you can't run 7.2 code.
Symptom:
High CPU on webJavaTask
Alternatively: large number of TCP connections, leading to file descriptor problems like:
osapi_file.c:370 Failed to open the file : /proc/1054/stat.(erno 24)
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtx02515
HTH,
Steve
Please remember to rate useful posts, and mark questions as answered

WLC 4404 - Clearing the Load Balancing Statistics?

Does anyone know of a way to clear the load balancing statistics from a WLC 4404? I've looked through the gui and CLI and can't seem to find a way to do it.
Thanks,
Rob

You can do a 'show summary' to see the number of connections that have been sent to each servers.
You can't see the number of bytes so.
I would suggest to collect this info on the server.
Regards,
Gilles.

WLC 4404 Upgraded to 7.0.235.3 (WPA HandShake Timeout) not availbale

Similar Messages

Maybe you are looking for