WLC Code Upgrade

We just got a WLC 4002 with 3.2.150.10 software version. I have followed a procedure to upgrade and I know I need to follow this path 3.2.150.10->4.1->4.2.176.0->5.2
However, I have tried to transfer the 4.1.185 on my controller and I get a
TFTP Failure while storing in flash!
error.
Has anybody experience this?? any adive?

1. You could be either using a TFTP server that could not support file transfers greater than 32 MB (if this is the case, go to http://tftpd32.jounin.net/tftpd32_download.html and use TFTP32).
2. Looks like you were upgrading the firmware without upgrading the Bootloader (ER).
Using the same process as the firmware, download and install Bootloader (in the follwoing order)
AIR-WLC4400-K9-4-1-171-0-ER.aes before you install firmware 4.1.185. Then
AIR-WLC4400-K9-4-2-61-0-ER.aes and install AIR-WLC4400-K9-4-2-61-0.aes. Finally, install Bootloader
AIR-WLC4400-K9-5-2-157-0-ER.aes before you install the final 5.x firmware you want.
Sorry, it's a very long process but it's the only way.
Have you seen this documentation:
Wireless LAN Controller (WLC) Software Upgrade
www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00805f381f.shtml

Similar Messages

WLC code upgrade, WCS, ap_3600

i'm going to upgrade a 5508 wlc code from
7.0.116.0
to
7.1.91.0
to add 3600 series access points having it all manageable via WCS ver 7.0.230.0
it seems to be possible, as it is explained in the compatibility matrix found on
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html
now I have to download the file to the controller...
AIR-CT5500-K9-SPECIAL-7-1-91-0.aes
(direct update possible)
before doing that I'd like to know if I will loose my configuration on the controller
i'm concerned about that because the release document is not clear:
- We highly recommend that you back up your controller's configuration files prior to upgrading the controller software. Otherwise, you must manually reconfigure the controller.
- For busy networks, controllers on high utilization, or small controller platforms it is advisable to disable the 802.11a/b/g networks as a precautionary measure.
- Step 5 Disable any WLANs on the controller.
- Step 19 Re-enable the WLANs......
- Step 22 If desired, reload your latest configuration file to the controller. (reload config after reenabling wlans????? why???)
so will I loose my configuration?
what is Field Upgrade Software? should i use that instead?
another controller another question .....: a cisco wlc 2100
found 2 update files
AIR-WLC2100-K9-7-0-230-0-ER.aes
AIR-WLC2100-K9-7-0-230-0.aes
why 2 update files this time? what file to update first?
thank you in advance for your answers

The 5508 has two files when you go to 7.2, which I would for the 3600. You'll also want to download and install the FUS image.
the 'legacy' WLC, like the 2100, have the .aes which is the OS for the WLC. The -ER is an Emergency Recovery image, it's waht you get when you break the boot cycle.
HTH,
Steve
Please remember to rate useful posts, and mark questions as answered

Upload new LWAPP code to LAP before WLC code upgrade

Hello,
I read some where that I can pre-position (upload) the new LWAPP or CAPWAP to access points before I upgrade the WLC code. This will reduce the time it takes for the APs to download and run the new code from the WLC
I am not able to find a document to instaruct me how to do it. I'd appriciate if someone can help me out with a link to a document.
Thanks in advace
BoG

Hey there .. Check out this link
http://www.my80211.com/cisco-wlc-cli-commands/2011/2/20/wlc-predownload-the-image-to-the-access-points-from-the-cont.html

WLC code upgrade path questions

We running WCS 6.0.132(lastest) and our controllers are on 4.2.130, we now want to upgrade to keep up with the times, but don't want to change over to capwap yet.
Question1:What's the latest LWAPP release code??
Question2:Whats the differences between 4.2.207 (cisco's support page says this is the latest release) but there's even releases with much higher versions ie 6.0 how does this work it's very confusing to workout an upgrade path
Cheers

Hi Tyrone,
I'm not an expert on Versioning but here are some basic details in response
to your query
4.2.207 is the latest release on the 4.2 Train and is probably an excellent choice
if you are avoiding CAPWAP for the time being. You will see in the link below that
there are multiple "simultaneous" Trains for the WLC (and most Cisco products). People
were not huge fans of the early 5.x Trains (quite buggy) and CAPWAP was introduced
in 5.2 and forward so this is why 4.2.207 seems like a good fit for you
In controller software release 5.2 or later, Cisco lightweight access points use the IETF standard Control and Provisioning of Wireless Access Points protocol (CAPWAP) in order to communicate between the controller and other lightweight access points on the network. Controller software releases prior to 5.2 use the Lightweight Access Point Protocol (LWAPP) for these communications.
CAPWAP, which is based on LWAPP, is a standard, interoperable protocol that enables a controller to manage a collection of wireless access points. CAPWAP is being implemented in controller software release 5.2 for these reasons:
      To provide an upgrade path from Cisco products that use LWAPP to next-generation Cisco products that use CAPWAP
      To manage RFID readers and similar devices
      To enable controllers to interoperate with third-party access points in the future
LWAPP-enabled access points can discover and join a CAPWAP controller, and conversion to a CAPWAP controller is seamless. For example, the controller discovery process and the firmware downloading process when you use CAPWAP are the same as when you use LWAPP. The one exception is for Layer 2 deployments, which are not supported by CAPWAP.
You can deploy CAPWAP controllers and LWAPP controllers on the same network. The CAPWAP-enabled software allows access points to join either a controller that runs CAPWAP or LWAPP. The only exception is the Cisco Aironet 1140 Series Access Point, which supports only CAPWAP and therefore joins only controllers that run CAPWAP. For example, an 1130 series access point can join a controller that runs either CAPWAP or LWAPP whereas an 1140 series access point can join only a controller that runs CAPWAP.
http://www.cisco.com/en/US/products/ps6366/products_qanda_item09186a008064a991.shtml
4.2.207 was released 24/Jul/2009 which does make it the second newest version available in any train.
http://www.cisco.com/en/US/products/ps6366/prod_release_notes_list.html
Cheers!
Rob

Called-Station-ID attribute and Cisco WLC code 7.4

Hello
I have 2 WLCs configured with 2 SSIDs (one is [WPA2][Auth(802.1X)] and the other is Web-Auth). One of the WLCs is remote and its WLANs are configured with mobility anchors pointing to the other WLC. Both WLCs are configured with Called-Station-ID set to AP Mac Address:SSID. I use this attribute on ACS to authenticate/authorize users based on what SSID they connect to.
This worked fine on WLC code 7.0 but on upgrading to 7.4 I started having some issues:
clients on the remote WLC can still authenticate on the [WPA2][Auth(802.1X)] SSID as the Called-Station-ID attribute is still AP Mac Address:SSID
clients on the remote WLC cannot authenticate on the Web-Auth SSID as the Called-Station-ID attribute now appears to be the Mac Address of the WLC anchor controller
WLC models are 5508 and current code is 7.4.110.0 (APs are AIR-LAP1142N-E-K9). Can anyone tell me why I'm seeing this behaviour on the Web-Auth SSID on the remote WLC?
Thanks
Andy

Since you have two AAA devices that's sending info, you can have your policy for the guest specifying the guest WLC. The SSID policy for the foreign WLC is only really needed if you have multiple 802.1x authentication from the foreign WLC and that's when you can use the regex to defiance the SSID per AD Group.
Look at a successful authentication from one of the guest users. Look at the detailed log and then in that log, you will see all the attributes being sent that the radius can send back to the WLC. You can use any of those attributes in your policies.
Called-Station-ID might not be sent like what your use to, because the foreign WLC has the access point the guest user associates to and tunnels it back to the anchor WLC. So this attribute might not be available. Things do change with code versions so you might just have to adjust your policies. I haven't played around with 7.0.x code with guest anchor and radius in a while, but I have in the past upgraded radius or the WLC and had to tweak my radius policies.
Sent from Cisco Technical Support iPhone App

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 code for point to point bridging

What is the best WLC code for point to point and point to multipoint bridging on a 2504 with 2602 APs? 7.2-7.4 had transparent vlan issues and I'm not sure if they were fixed in 7.5-7.6. We have 5-6 vlans that we are needing to bridge between a large open area. Also, are there any bugs with wireless mesh and ISE?

You do not have many choices now, only 7.0.250.0, 7.4.121.0 & 7.6.110.0 codes are supported by Cisco. All other codes have been deferred by them.
I do not have configured those set-up to advise you specific to that. I would think 7.6.110.0 may have fixed whatever the known bugs in previous versions.
HTH
Rasika
**** Pls rate all useful responses ****

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 code: Mesh-Only vs Non-Mesh

Most of the sites have 1131Indoor and one site has 1522 Outdoor AP. All the AP's will have POE cable. We dont need Mesh technology.
We are trying to evaluate between Mesh Only or Non-Mesh code for WLC. Some of the departments are low budget funded so they cannot afford to have two different WLC's.
What is the loss of functionality if we make Indoor AP like 1131 connect to Mesh Only code?
Is there a link that shows the functionality comparison between Mesh Only and Non-Mesh WLC code?

the mesh code right now is still based on 4.1 code.... so you will only have features as of 4.1 (there is no mesh code based on 4.2 yet)....
if you use mesh release 2, the .24 code... its the first mesh code to support internal ap's like the 1131 in indoor mesh and normal local mode (possibly hreap as well but I dont have a doc in front of me right now)......
but if you want to support the 1522 and 1131 on the same WLC you will have to use mesh release 2 the.24 one...

Intermec 751 Handhelds and WLC code versions

We have Intermec 751 mobile handhelds and three WLAN controllers. A 4404-100, 4402-25, and a 2000-6. The 4404 & 2000 series are running 3.x WLC code and the 4402-25 is running 4.x.
We're using the same SSID & WPA-PSK on all three controllers, and the handheld associates with the controllers that have the 3.x code, but not the WLC with 4.x code. Besides the different code, we have the exact same WLAN's defined. We've also tried creating an Open WLAN with no security, and still nothing. We're using the Intermec Settings app to manage the WLAN settings..
Has anyone run into this before? Other devices - laptops and CK30 scanners can connect, but not the 751's. We're going to open up a TAC as well, but I thought I'd check the boards to see if anyone else has encountered anything similar.

I found this on Intermec's "Knowledge Central". I don't know if this will help but it's worth a shot. It's seems "SR06236001" fixes Cisco LWAPP version 4.x compatibility. Here is the full KC post.
Scope:
7x1 terminals running OSv4.95.1 PSMv4.03 with SR06236001 installed using Funk-WPA-TLS-LWAPP v4.x
Problem Description/Purpose:
The terminal will reauthenticate on the network approximately once every twelve minutes. If hundreds of terminals are deployed, this creates a large amount of unwanted reauthentication traffic on the authentication server.
Answer
Solution/Action Plan:
Intermec Engineering recommends enabling CCKM to reduce frequent and unwanted reauthentication messages on the authentication server.
SR06236001 also offers these enhancements to OS version 4.95.1/4.03 PSM on the 751A, 761A and CN2BA with WM2003:
1. Power managed radio response time is improved (PSP).
2. Roaming performance with LEAP is improved.
3. Fix for Cisco LWAPP version 4.x compatibility.
4. Fixes a CCX association ID problem that was associated with CCKM.
Do not use SR06236001 on devices other than the 751A, 761A, or CN2BA (Samsung radio).
SR06236002 is specifically for the CN30A with Windows Mobile 5 and contains the same enhancements (Samsung radio). This updated has been tested on CN30 OS version 2.47 with version 2.01 SD Card Image.
Installation instructions for either SR listed above:
1. copy the associated CAB file to \CabFiles and warm boot
or
2. copy the CAB file to \Temp folderand double-click on it.
The terminal will automatically warm boot after the SR is installed.

302 Redirect Location Header Rewrite not working with code upgrade

Hi,
Description:
We have a portal webservice hosted by an ACE4710. It has two services (www/https) on the same IP 10.1.1.1.
One is a redirect service that redirects all requests to tcp/80 on this ip to the other which is a 'standard' https proxy service.
The backend servers are http only. Externally everything needs to be https.
So we have an ssl proxy and Location header http to https rewrite on the https service.
The configuration below operates correctly on v5_1_2.
But with a code upgrade to 5_3_1b, the Location header rewrite does not work.
We've tried several different configurations and even 'ssl url location rewrite ".*". It just looks like the ACE is completely ignoring the configuration to rewrite the Location field.
Reverting to the older code fixes the problem.
Problem seen:
Here is the problem as seen on the *client*. The 302 redirect Location header is NOT rewritten:
Response headers:
HTTP/1.1 302 FOUND
Server: nginx
Date: Fri, 20 Mar 2015 10:59:43 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 295
Connection: keep-alive
Location: http://website.liveportal.nhs.uk/homepage/information
Cache-Control: no-cache, no-store
Set-Cookie: information=35a7831d-928d-4122-aef3-39ef48ac4440; Path=/; secure; HttpOnly
X-Frame-Options: DENY
HTTPSampleResult fields:
ContentType: text/html; charset=utf-8
DataEncoding: utf-8
Config extract:
1) Set up the servers (4 normal on tcp/80 and one for a redirect)
rserver host WEBSERVICE-1
ip address 192.168.1.1
conn-limit max 200000 min 160000
inservice
...and the same for the other three
rserver redirect PORTAL_REDIRECT
webhost-redirection https://%h/%p 302
inservice
2) Set up the server farms
serverfarm host PORTAL_LIVE
probe webping
rserver WEBSERVICE-1 80
    inservice
rserver WEBSERVICE-2 80
    inservice
rserver WEBSERVICE-3 80
    inservice
rserver WEBSERVICE-4 80
    inservice
serverfarm redirect PORTAL_HTTP_REDIRECT
rserver PORTAL_REDIRECT
    inservice
3) Setup the ssl proxy and a location rewrite to https for responses from the servers
action-list type modify http HTTPS_LOCATION
header rewrite response Location header-value "http://(.*)" replace "https://%1"
ssl-proxy service WEB_SSL_PROXY
key webportal.key
cert webportal.crt
chaingroup root-chain
ssl advanced-options SSL-SECURE-STRONG-WEB
4) Set up the L4 services
class-map match-all PORTAL_HTTP
2 match virtual-address 10.1.1.1 tcp eq www
class-map match-all PORTAL_SSL
2 match virtual-address 10.1.1.1 tcp eq https
5) Setup the policy maps - one for the reals servers with header rewrite for redirects
policy-map type loadbalance http first-match PORTAL_HTTP
class class-default
    serverfarm PORTAL_HTTP_REDIRECT
policy-map type loadbalance http first-match PORTAL_SSL
class class-default
    serverfarm PORTAL_LIVE
    action HTTPS_LOCATION
6) Create the service policy
policy-map multi-match EXTERNAL-SERVICES
class PORTAL_SSL
    loadbalance vip inservice
    loadbalance policy PORTAL_SSL
    loadbalance vip icmp-reply
    appl-parameter http advanced-options PARAM-HTTP
    ssl-proxy server WEB_SSL_PROXY
class PORTAL_HTTP
    loadbalance vip inservice
    loadbalance policy PORTAL_HTTP
    loadbalance vip icmp-reply
7) Apply to the interface
interface vlan 211
description External Access
ip address x.x.x.x 255.255.255.0
alias x.x.x.x 255.255.255.0
peer ip address x.x.x.x 255.255.255.0
access-group input PERMIT-ALL
service-policy input EXTERNAL-SERVICES
no shutdown

I found that the v5_3_1b code seems to need a bit of extra configuration and it now works ok.
parameter-map type http PARAM_HTTP
header modify per-request
no persistence-rebalance
case-insensitive

Some C1242 Radios are disabled after WLC 5508 upgrade to 7.3.101.0

          One week ago I use a WLC 5508 to place and replace another WLC 5508 with version 6.0.199.4, when I conect the new WLC all AP´s works OK only 10 dont work and not are recognizes from the WLC with version 7.3.101.0. The fail is the radios stay disabled. All ap´s are AIR-AP1242G-AK9 . See the image below, the only difference this ten AP´s are conected in switches cisco all the rest are connected in switches of ohter vendor.
If possible some command in the configuration is not neccesary and make the bad function?
This is tipically config apllied by the customer in they cisco switches
interface   GigabitEthernet0/22
description PB-RS-A22
switchport access vlan 5
switchport mode access
switchport port-security
switchport port-security aging time 2
switchport port-security violation restrict
switchport port-security aging type   inactivity
macro description cisco-desktop
spanning-tree portfast
spanning-tree bpduguard enable
I reed some documents but i don´t found the right solution can any help me?
Thank

Are the APs being powered through POE or perhaps an injector (if injector, do you have the injector override enabled for joined APs with their radios down?) What's the disparity of the models; are all 1242s in this "down radio" state, or only the 1242s plugged in to the Cisco Switches?
When you say the 10 don't work and are not "recognized" by the WLC, are you indicating that they have not re-joined the newer WLC or are they joined but their radios are not operationally up? Please clarify the state of these APs.
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn73.html#wp965532
Please note that a version prior to 7.0.98.0 cannot be upgraded directly to 7.3.101.0 from the WLC perspective, but it's possible your 1242 AP's image (used from the 6.0.199.4 release) is not able to properly join and download code for the 7.3.101.0 WLC that was put in to place. The 1242 APs in your scenario would still be running the old 6.0.199.4 image.
I'm curious what all is or isn't happening from the questions above, but you may need to load a newer recovery release on the 1242s to have them join properly - or - downgrade the WLC to a version that allows a direct upgrade from 6.0.199.4 such as 7.0.240.0. Let the APs join the downgraded WLC and finish up any image downloads and re-join, then upgrade the WLC back to 7.3.101.0 (would recommend latest 7.3.112.0 instead) and see if they rejoin and radios are online.

WLC 5508 - upgrade image + H-REAP

All, good day.
I have a bug reported (CSCsy23704) for the H-REAP functionality. This sunday I will perform an image upgrade to try to solve this issue.
What would it be the best image to go for?.
After the upgrade, what will happen with the APs?, should I reconfigure them or they will enter in contact with the WLC automatically?.
Current image is 6.0.199.0
The WLC is a 5508
Thanks in advance!!

After you load the code on the WLC you can use the pre download feature. Tis will allow you to push the new image to the ap before you reboot.
Steve
Sent from Cisco Technical Support iPad App

Cisco 4402 WLC IOS Upgradation using CLI and Web Interface

Hi,
I would like to know how to upgrade IOS of Cisco 4402 WireLess LAN Controller using CLI and Web interface ?
Can any one help me regarding the same.
Please answer as soon as possible.
Thanks in advance.

Here are the instructions for upgrading the controllers via GUI:
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn52.html#wp472449
Instructions via cli:
Cisco recommends that a direct CLI console port connection is used to update the controller software.
1. Make sure a TFTP server is available for the Operating System (OS) software download. Also, keep these guidelines in mind when the TFTP server is set up:
If a download is performed through the service port, the TFTP server must be on the same subnet as the service port because the service port is not routable.
If a download is performed through the Distribution System (DS) network port, the TFTP server can be on the same or a different subnet because the DS port is routable.
The TFTP server cannot run on the same computer as the Cisco Wireless Control System (WCS) because WCS and the TFTP server use the same communication port.
2. Download the desired OS software update file from the Cisco website to the default directory on the TFTP server.
3. Log into the WLC CLI.
4. Issue the ping server-ip-address command to verify that the WLC can contact the TFTP server.
5. Issue the transfer download start command and answer n when prompted to view the current download settings.
This example shows the command output:
transfer download start
Mode........................................... TFTP
Data Type...................................... Code
TFTP Server IP.................................
xxx.xxx.xxx.xxx
6. TFTP Path...................................... TFTP Filename.................................. AS_2000_3_0_x_x.aes --OR-- AS_4100_3_0_x_x.aes --OR-- AS_4400_3_0_x_x.aes Are you sure you want to start? (y/n) n Transfer Canceled Issue these commands to change the download settings:
* transfer download mode tftp
* transfer download datatype code
* transfer download serverip tftp-server-ip-address
* transfer download filename filename
* transfer download path absolute-tftp-server-path-to-file
Note: All TFTP servers require the full pathname. For example, in Windows, the path is C:\TFTP-Root. (In UNIX forward slashes (/) are required.)
7. Issue the transfer download start command to view the updated settings, and answer y when prompted to confirm the current download settings and start the OS code download.
This example shows the download command output:
transfer download start
Mode........................................... TFTP
Data Type...................................... Code
TFTP Server IP.................................
xxx.xxx.xxx.xxx
TFTP Path......................................
path>
TFTP Filename..................................
AS_2000_3_0_x_x.aes --OR--
AS_4100_3_0_x_x.aes --OR--
AS_4400_3_0_x_x.aes
Are you sure you want to start? (y/n) y
TFTP Code transfer starting.
TFTP receive complete... extracting components.
Writing new bootloader to flash.
Making backup copy of RTOS.
Writing new RTOS to flash.
Making backup copy of Code.
Writing new Code to flash.
TFTP File transfer operation completed successfully. Please
restart the switch (reset system) for update to complete.
8. The WLC now has the code update in active volatile RAM, but the reset system command must be issued to save the code update to non-volatile RAM (NVRAM) and reboot the WLC.
This is a sample output:
The system has unsaved changes.
Would you like to save them now? (y/n) y
The controller completes the bootup proce

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 Code Upgrade

Similar Messages

Maybe you are looking for