Upgrading WLC 4404

I need to upgrade our Wireless Lan Controller to support new APs. I was able to get the new code due to a security advisory on the code we are running now. I am upgrading from 6.0.196.0 to 7.0.220.0 (MD). I have read in some of the technical docs that the WCS has to match the WLC. I cannot find any documentation as to what this entails on the WCS. I need some direction, please!
WCS version is 6.0.132.0 running on Windows.
Thank you!

Okay.. Well when you download the WCS software from CCO, most likely the .exe, there is a release note for that WCS code that has all the steps to upgrading your WCS to the appropriate version. Just look for the release note prior to downloading the WCS .exe file.
Thanks,
Scott Fella
Sent from my iPhone

Similar Messages

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.

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

Recommended to upgrade WLC to software version 4.0.179.8?

Hi Sir,
I'm deploying a few WLC 4404-100 in a Mobility Group. They are installed with software version 4.0.155.5.
I understand that the latest version is 4.0.179.8. Is it recommended to upgrade the WLCs to this version?
Please advise.
Thank you.
B.Rgds,
Lim TS

Hi,
I'm having a WLC 4404-100 running software version 4.0.179.8. Doing functional test now.
Created a WLAN with 802.1x and WEP 104-bits.
My wireless card is 3Com 3CRWE62092B. Windows XP SP2. Associated to the Lightweight AP and passed my EAP PEAP-MSCHAPv2 authentication with a backend Microsoft domain controller.
The connection is fine. However, every about 15 minutes, XP prompts the username/password dialog box again. My connection is cut off until I re-authenticate.
I never faced this problem before using Odyssey client previously with a WLC running software version 155.5.
Please advise.
Thank you.
B.Rgds,
Lim TS

Duration of upgrade WLC with 75 AP

I'm planning to upgrade a 4404 WLC with 75 LWAPP's, from 5.1 to 5.2.193.
I read that after the WLC upgrade the AP's are automatically upgraded in groups of 10 and that the upgrade can last as long as 30 minutes. Does this mean some AP's are not functional for 30 minutes? Or do the AP's work while they still have the lower software version, and only are not functional during their own upgrade of about 3 minutes? And is there a way to choose these AP groups yourself? I can't find this in the documentation.
Thanks in advance,
Albert

(Assuming you have one controller) I think the AP's will go offline when you reboot the controller after the controller upgrade. The APs will not come back online until they have upgraded their firmware and re-joined the controller. On our last upgrade (controllers running 4.2, upgrading to a later rev of 4.2, we use 1242 AP's), it took about 5 minutes for a given AP to complete an upgrade. 2 controllers and ~250 AP's took less than an hour.

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

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

Upgrade WLC 5508 Ver. 7.0.98.0 to Ver 7.6.110.0

i will upgrade WLC 5508 Ver 7.0.98.0 with License 50 AP. to Ver 7.6.110.0 will it ask to install license ?

No, It will not ask for again.
Just upgrade the software.
Regards
Dont forget to rate helpful posts

Upgrade WLC 5508 to 7.4.121.0 problem

After I upgraded WLC 5508 from 7.2.111.3 to 7.4.121.0, all 3602i APs don't associate with the controller. All APs were working/associating with controller on 7.2.111.3 at same setting. IP address of APs are setup as DHCP.
The error message is "AP couldn't get IP address".
Any one has this type of problem when you upgrade WLC 5508 from 7.2.111.3 to 7.4.121.0.
Thanks,

Hi,
This doesn't look like software issue.
You have to check why the APs are not able to get ip address. Try connecting a PC to a swtich port where one of these APs are connected and see if you are able to get IP on PC.
Also check if the DHCP server is reachable and if there are IP address in the pool assigned for APs.
HTH,
Thanks & Regards,
Ishant
*** Please rate the post if you find it useful ***

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.

Replacing WLC 4404 with 5508

Hi Friends,
I am new to Cisco wireless and would appreicate any help with replacing WLC 4404 with 5508. I mean any link or doc (best practices).
Thansk,
Nav
[email protected]

Yup, what said Scoot said .. Add the 5508 to the aps high availability. If you have WCS/NCS you can push this to the APs.
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."

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.

Upgrading WLC 4400

Hi,
How is the correct steps for the upgrade of the WLC4400 from a version 4.1 to 4.2 version?
I backup the configuration running in the version 4.1.
I download, and put the file of the Software 4.2 in the TFTP directory.
I start the transfer from the TFTP to WLC.
The copy was succesfull.
I restart the WLC and Save the config.
But, the WLC lost the configuration (running the version 4.2), I connect to the console port and this showed the Wizard to start the initial configuration :S
What is the correct steps to upgrade WLC.

Hi Ricardo,
This is a good doc with Step by Step info
Wireless LAN Controller (WLC) Software Upgrade
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00805f381f.shtml
Cheers!
Rob
Please support CSC Helps Haiti
https://supportforums.cisco.com/docs/DOC-8895
https://supportforums.cisco.com/docs/DOC-8727

Upgrading WLC 4404

Similar Messages

Maybe you are looking for