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

Similar Messages

  • 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

    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

  • 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

  • Upgrading WCS to Prime

    I'm in the process of upgrading a customer's WCS server to Prime. I know before I can upgrade the WCS server to Prime. I must first upgrade the WCS sever to NCS. My problem is the customer's WCS server is running software version 7.0.230 and I need to upgrade it to 7.0.240 before I can extract the WSC database. My question is, if I upgrade the WCS server  from 7.0.230 to 7.0.240 will that cause the customer's  Wireless Lan Controllers that are being managed by WLC server to also upgrade?

    Maurice, I had a devil of a time upgrading WCS to NCS to Prime.
    Long story short, I found the time taken on a very unsuccessful WCS->NCS->Prime migration was 4-8 times longer than the time it took to just install Prime, add the WLCs, and manually rebuild the maps.
    YMMV.
    PS, Cisco Prime LMS is probably replacing their wired management software (often LMS, Cisco Works+ RME, etc). I believe every best-practice guide I've seen from Cisco says to have one Prime for wireless, and one Prime for wired... even though Prime looks like it could handle both.

  • Upgrading WCS to v7.0

    I plan on upgrading WCS from version 6.0.181.0 to 7.0230.0
    Is there any reason not to or concerns?

    As Steve pointed out you should be fine. Here is a WLC and WCS software matrix if you want that warm and fuzzy ..
    http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html

  • 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 ****

  • How to upgrade WCS Plus 500 to 700?

    To upgrade WCS Plus 500 lic to support 200 more APs, which one is the correct choice?
    1. Add WCS Plus 100 lic x 2; or
    2. Add WCS Enterprise 1000 lic
    Refer to ordering guide
    http://www.cisco.com/en/US/prod/collateral/wireless/ps5755/ps6301/ps6305/product_data_sheet0900aecd804b4646.html
    Cisco WCS is licensed as either a single server or enterprise deployment.
    Single Server License Overview
    • Licenses: WCS-STANDARD-K9, WCS-PLUS-UPG-K9, and WCS-WLSE-UPG-K9
    • License increments: 50, 100, 500 (Up to 1500 for WLSE-to-WCS conversion only)
    • Single server deployment
    • Suitable for customers deploying up to 500 (Up to 1500 for WLSE-to-WCS conversion) Cisco Aironet lightweight access points
    • One license file per Product Authorization Key (PAK) certificate
    • Available in WCS Base and WCS PLUS configurations
    Enterprise Server License (Multiple Servers) Overview (release 4.1 or later)
    • License: WCS-ENT-PLUS-K9
    • License increments: 1000, 2500, 10000, 50000
    • Single or multiple server deployment (Cisco WCS Navigator included in 10000, and 50000 licenses)
    • Suitable for customers deploying 500 or more Cisco Aironet lightweight access points
    • Multiple license files linked to a single PAK certificate
    • Server decrements available number of access points as licenses are allocated within the network
    BUT
    All Cisco WCS licenses of the same option (Base or PLUS) are additive. Cisco WCS licenses can be combined to support an incremental number of access points (such as 300, 700, 900) beyond the distinct license increments (such as 50, 100, 500) offered.
    Example 1: To purchase a new single server license for 800 access points
    Purchase: WCS-STANDARD-K9, (1) WCS-APBASE-500, and (3) WCS-APBASE-100
    contradiction in the doc.

    Existing
    1
    x
    WCS-PLUS-500
    Cisco WCS with PLUS License for 500 APs, Windows/Linux
    Target upgrade to monitor
    700 APs

  • Upgrading WCS 7.0.164.0 to 7.0.172.0

    I'm trying to upgrade my WCS from 7.0.164.0 to 7.0.172.0 but it keeps throwing me into the manual process because it detects multiple versions.  Seems a previous upgrade from 6.0.132 to 7.0.164 did dot remove the 6.0.132 directory or files.
    Am I safe to delete the 6.0.132 directory/files and trying again?
    Thanks!

    Surendra,
    Thanks for the reply.  By "clean upgrade" I presume you mean "manual upgrade" because the automated upgrade does not work?
    Cisco Wireless Control System Configuration
    Guide
    Manually Upgrading WCS on Windows
    Follow these steps to manually upgrade WCS on a Windows server. This type of upgrade is not recommended.
    Step 1 If possible, stop all WCS user interfaces to stabilize the database.
    Step 2 Back up the WCS database by following the instructions in the "Backing Up the WCS Database (for Windows)" section.
    Step 3 Uninstall the WCS application by following the instructions in the "Uninstalling WCS on Windows" section.
    Step 4 Install the new version of WCS by following the instructions in the "Installing WCS for Windows" section on page 2-6.
    Step 5 Restore the WCS database by following the instructions in the "Restoring the WCS Database (for Windows)" section.
    Going from 7.0.164.0 to 7.0.164.3 didn't work either.

  • Upgrading WCS 7 to Cisco Prime (CPI) 2

    Hello,
    I have read a few article and posts about upgrading WCS 7 to CPI 1.2 via NCS. However now with Prime 2.0 I was hopping I didn't have to use NCS.
    I can't find any migration guides or documents about migrating to 2.0 instead of 1.x.
    Can anyone point me in the right direction.

    Direct migration from WCS 7.x to Cisco Prime Infrastructure 2.0 is NOT possible.
    in my work I had this problem.
    the only solution was to first install the NCS 1.1, after the patch 1.1.1.24 and then migrate to 2.0
    Backup WCS data , upgrade to NCS 1.1  and restore de data...
    install patch 1.1.1.24 , only then you can do the upgrade to version 2
    CISCO:
    "We strongly recommend upgrading your WCS to 7.0.230.0 (for data integrity) or higher before attempting to migrate to NCS.
    Users will first need to do an intermediary migration to NCS 1.1.1.24, and then do an inline upgrade (or migration) to Cisco Prime Infrastructure 2.0"

  • Generate a Local net user Report from WLC or through WCS

    Need advice regarding downloading the Local net user list from Anchor WLC or through WCS. In WCS I could not find any menu to generate a report on Local net users in other words Guest account list.
    Please advice Thanks
    Jacob

    I don't know aobut using WCS, but you can always run a command through the cli:
    show netuser summary

  • 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...

Maybe you are looking for