WLC upgrade to 7.0.98.0, WCS & Location Appliance to upgrade - Building maps location

Hi,
We recently upgraded about 24 WLCs (4402s and 5508s) from 6.x to 7.0.98.0. In order to support these WLCs through WCS, we also need to upgrade the WCS to 7.0.164 which is currently running at 6.0.132.0 (Linux OS). Same is the case with Wireless Location Appliance 2700 to be upgraded as well. Wireless Management system has number of building maps with AP locations.
Prior to upgrade the WCS / Location appliance we need to take the backup of these building maps, already stored to export after the upgrade. Kindly let us know the directory where all these maps are being stored, as during upgrade we will loose all the stored data / maps.
Thanks for your kind assistance.
Regards.
Shuja

Hi Shuja:
Who says you're going to lose all your maps and stored data during a WCS upgrade? The installer for WCS 7.0.164.0 will see the 6.0.132.0 installation and upgrade it in place, modifying the existing data to work in the new 7.0 format. The installer for WCS 7.0.164.0 will even ask you if you want to make a backup of this data before the upgrade process even starts, although it would be a good idea to pull a backup of everything before you start. (One can never have too many backups, right?) The backup application in your existing install should be at /opt/WCS6.0.132.0/backup . Run that application and it will prompt you for a location to put the .nmsbackup file.
The .nmsbackup file that results from a WCS backup is what gives WCS its portability across platforms (physical/virtual) and operating systems (Windows/Linux). It's essentially the lifeboat of WCS, containing the database, the maps, the licenses and other supporting files.
Performing Maintenance Operations chapter of the WCS Configuration Guide:
http://tools.cisco.com/squish/08725
Sincerely,
Rollin Kibbe
Network Management Systems Team

Similar Messages

5508 WLC Upgrade steps

Single 5508 WLC with 8 x 1142 APs.
5508 is running FUS 1.3, software version 7.0.116.0, field recovery image 6.0.182.0.
I need to bring the software version up to at least 7.2.115 to support 2 new 2602 AP i need to install.
Question is; do I install FUS 1.9 then update my controller to 7.6.120 or do I need to do any intermediate steps?
This is my first time upgrading a WLC so I'm fresh and this is a production WLC.
Cheers

Hi Fisher.
Normally It doesn't matter as long as you get it done but make sure that you reboot the WLC before doing the next.
Here is the procedure for FUS upgrade:
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/fus_rn_OL-31390-01.html
WLC Software upgrade Procedure:
http://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/68835-wlc-upgrade.html
Regards
Dont forget to rate helpful posts

WLC upgrade due to Advisory

Hi,
We have a 5508 WLC running 7.2.110.0 and need to upgrade according to the advisory released today.
It seems we have three upgrade choices:
7.2.110.0 to 7.2.111.3
7.2.110.0 to 7.3.110.0
7.2.110.0 to 7.4.x
I've not upgraded one of these 5508's before, but if they are anything like ASAs then I need to be careful.
Can anyone advise if upgrading from our current version to 7.4 requires planning. Same for 7.3.
How will the WLC upgrades affect the APs (3502i) ?
How does one recover from a failed upgrade on these WLCs?
Thanks.

WLC version 7.4.100 will need Prime Infrastructure Version 1.3 to be managed, but Version 1.3 is not yet available to download at this time.
Huh? What is Prime Infrastructure and why do I need it?

P780 signal issue after upgrading build number

Recently i had upgraded build number P780_ROW_8G_S227_141121 after upgradation both sim card showing no sim signal on handset
how to solve this problem please suggest .even factory restore password not accepting .
Regards
Wasi

I think you confuse standalone dbconsole with centralized gridcontrol. There's only ONE command to start database control: emctl start dbconsole. This command will start the integrated agent,too. No need to start the agent separately.
Werner

WCS/WLC upgrade options

Hi,
I'm currently running both a WCS appliance and a windows server WCS on version 4.2.62.11
They are managing around 1000 AP's that are in a Hospital environment. They are using Vocera badges.
The controllers are all running v4.2.61.0
What are my best upgrade options for both WCS and the controllers? I'm looking for stability, improvements and fixes.

We ran a pretty stable 4.0.217 for about a year with no big issues that I can remember. We started getting 1252s and needed to upgrade. We finally jumped in with 4.2.130 and had some pain. We started having issues with Vocera roaming, and Dell 1470/90 adapters had issues also. We've seen the following issues (CSCsm65043, CSCsi26248, CSCsi72578, CSCsq57697, CSCsu44970, CSCsr40109, CSCsv21441, and CSCsv21464). Some have been fixed in 4.2.173/176, but with the latest security advisory, it makes sense to run 4.2.176.
With 19 pages of open caveats in 4.2.176, it's a crap shoot for sure, but probably the best you can do as it's a MD release. Also we have depreciated the Spectralink and only run 7921 and Vocera.

WLC Upgradation / Degradation

I have one WCS running 3.0.101.0. Currently there are few WLC's(inturn supporting Cisco 1010 AP's) associated with it which are running 3.2.150.6 and 3.2.195.10. I have one more WLC which is running 4.2.61.0 which is not getting added in WCS. I came to know the reason was WCS is running one revision older firmware. The solution is to upgrade WCS to 4.0 or 5.0, but if i upgrade the same then will WCS support the existing WLC's running 3.2.X.X ? Also if i degrade the 4.2.61.0 WLC to 3.2 then will there be any impact to the connected AP's (Cisco 1010 and 1242AG both running on 4.2.61.0. Please let me know the best solution so that all my WLC's get added to WCS successfully.

There should be no reason for the WCS to be upgraded to a higher firmware than the WLC. The only question I would like to ask is why are your WLC running different firmware (3.2.150.6 and 3.2.195.10)?
WLC's running different firmwares will force the AP's to up/downgrade the IOS everytime the AP's swing from one WLC to another.

Wireless Clients can't connect post WLC Upgrade to version 7.4.100.0

Upgraded WLC Flex 7500 controller to: 7.4.100.0
Previous WLC Controller version: 7.2.111.3
After the upgrade, all AP's reported back to the controller and looked like working. We have 50+ branch sites that connect back via Layer 2 to the main office. The main office SSID's were broadcasting and users could connect and get the proper IP's. Users that connected back through FlexConnect AP's couldn't obtain an IP address. The client would authenticate to the WLC and accept the SSID key, but would not get an IP address. I see with the 7.4.100.0 upgrade there are more options for DHCP for each interface, which we don't use interfaces for all sites as we did in the early days, now we make sure the flex connect tab has the vlan identifier in the tab and the traffic goes out the local firewall etc. Each remote site has a Linux based firewall and DHCP server.
Looking for any insight with the 7.4.100.0 upgrade that may cause clients to not connect and obtain an IP address.
We have since back dated our WLC Software to: 7.2.111.3 to allow things to work pre upgrade which everything worked fine.
Any suggestions would be great, we had to upgrade version 7.4.100.0 to support our AP 1602.
Thanks in advance.
Matt

Verify that you have an upgraded FUS image. Second, make sure your WLAN to vlan mapping on the FlexConnect AP's have the correct vlan mapping. I have seen these change to the default vlan mapping.
Sent from Cisco Technical Support iPhone App

IP Phone 7921 / 7925 roaming issues after WLC upgrade from Version 7.2 to 7.3 and / or 7.4

Hi,
We have a customer which is using a Cisco WLC 5508 and 3502I APs. As he used the 7.2.103 release, There were no issues with VoWLAN. Now he needed new APs and ordered the 2602I. To use them he needed to upgrade the WLC to a 7.3 or later release. After the upgrade, he now encounters problems while roaming with the phones. The phones were tested with FW 1.4.1, 1.4.2 and 1.4.3.
Configuration is set according to wireless voice design guides (VoWLAN DG 4.1, 7921 Deployment Guide). A Cisco TAC is also in progress, but they seem to be uncertain whether it is a wireless or CUCM issue, but I don't see a reason why it should be the CUCM when the only thing changed is the WLC Software Version.
Is there anybody who is aware of such issues and can offer help?
Thank you in advance.
Best regards,
Patrick

Hi,
we had a TAC ticket open with this customer and after some time, the TAC gave us the advise to use this release and the problems are now solved.
So for others having the same issue: If you only need to support the 2600 APs, stay with the latest 7.2 release as there are some issues with the 7.3 and 7.4 release. If the customer requires HA, AVC or any of the new features + wireless voice, be very careful as it seems that the newer releases are having problems with that. I hope that Cisco will fix this very soon.
regards,
Patrick

602-OEAP Access Point broken after WLC upgrade to 7.4.100.0

Hey all,
I have a TAC case open, but it doesn't seem to be making any progress....
I upgraded my 5508 controller from 7.2.111.3 up to 7.4.100.0
Most of my APs are fine. 3500s, 1100s etc.except for 602i APs. The APs associate, they update software etc, but they won't broadcast the WLAN.
An interesting thing, on the 602 AP, in the log, I see this:
*Mar 06 15:08:12.667: SSID remote, WLAN Profile Name: RemoteOEAP, added to the slot[0], disabled
So the AP is definately talking to the WLC and being pushed the correct WLAN profile.
Another thing I noticed:
On the controller, the AP shows the the Admin status of the radios is showing DOWN, but the Admin status on the AP itself shows UP
I've done a factory reset on the APs to no avail. I have a 2504 WLC as well that i'm in the process of implementing in a DMZ specificially for these APs, and for testing purposes, I associated the 602 Ap to that WLC as well. This one is running 7.4.100.0 too, same results. It would appear to be a problem with this version of software?
Anyone else had this problem?

Hey, thanks for taking a look at this. Unfortenately, that's not the issue in this case. The AP is set to "United States" and the WLC is only configured for US. Just so I'm looking in the correct place:
On the AP in the WLC, it's under the "Advanced" tab
On the WLC, its under Wireless -> Country correct?
The frustrating part is that the 600 really doesn't have anything that can be configured on it, which means troubleshooting is also limited.

WLC Upgrades to 7.5.102.0 from 7.4.100.0 Question

We went through an upgrade from 7.4.100.0 for all of our WLC's this morning. One of the interesting features, that we wanted to take advantage of, was the BYOD profiling that the release notes talk about. I'm going through the controllers and see that there is now a tab under the SSID called "policy mapping". However, when I look for where I can create the local policy, I cannot find anything on the WLC for completing that task. I've been looking for instructions and notes on how to do this, but cannot seem to find any. Would anyone be able to point me in the right direction? Thanks!

Please
follow the below steps to create Local Policies.
Step 1
Choose Security > Local   Policies.
Step 2
Click New to create a new policy.
Step 3
Enter the policy name and click Apply.
Step 4
On the Policy List page, click the   policy name to be configured.
Step 5
On the Policy > Edit page,   follow these steps:
In the Match Criteria area,        enter a value for Match Role String. This is the user type or user group        of the user, for example, student, teacher, and so on.
From the Match EAP Type drop-down        list, choose the EAP authentication method used by the client.
From the Device Type        drop-down list, choose the device type.
Click Add to add the device        type to the policy device list.
The   device type you choose is listed in the Device List.
In the Action area, specify        the policies that are to be enforced. From the IPv4 ACL drop-down list,        choose an IPv4 ACL for the policy.
Enter the VLAN ID that should        be associated with the policy.
From the QoS Policy drop-down        list, choose a QoS policy to be applied.
Enter a value for Session        Timeout. This is the maximum amount of time, in seconds, after which a        client is forced to reauthenticate.
Enter a value for Sleeping        Client Timeout, which is the timeout for sleeping clients.
Sleeping   clients are clients with guest access that have had successful web   authentication that are allowed to sleep and wake up without having to go   through another authentication process through the login page.
This   sleeping client timeout configuration overrides the WLAN-specific sleeping   client timeout configuration.
In the Active Hours area,        from the Day drop-down list, choose the days on which the policy has to        be active.
Enter the Start Time and End        Time of the policy.
Click Add.
The   day and start time and end time that you specify is listed.
Click Apply.

TX Power Levels are low after WLC upgrade to 7.0.98.0

I recently upgraded our WLC 4404 to release 7.0.98.0. The process was very smooth with no
issues. The controller manages access points in two buildings. Prior to the upgrade the access points were maintaining high TX power levels...typically between 1 and 3. After the upgrade the power levels all droped to 6 and 8. I have confirmed that the correct external antenas have been set for each access point. I have not done a site survey to see if the lower power levels are acceptable. But the environment has been very consistent for the past year with regards to TX power levels. For the time being I have manually set a power level of 2 to prevent any service outages. Is there any explanation as to why the power levels have changed so drastically?

My customer is having a simlar problem with 2106 controller and 1131 AG access point.
After I upgrade the controller for 7.0.98.218, the access points was setting automaticly by controller with power level "0".
When its happening I see the follwing logs
Thu Dec 15 12:19:15 2011 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:3a:98:19:e7:c0 Cause=Heartbeat Timeout Status:NA
70 Thu Dec 15 12:19:15 2011 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:3a:98:19:e7:c0 Cause=Heartbeat Timeout Status:NA
Can You help me?
thanks, Murilo

WLC upgrade license and access point

Hi everyone,
I need suggestion regarding wlc 5508 upgrade license. Right now i have 150 license for access points. There will be upgrade around 300 access points. So we are planning to buy new license until the maximum capacity of 5508 (500 licenses).
Our management ip address is 192.168.50.x/24 . so all the access point are pointed to this management ip address (in the same subnet)
First question,
Because there will be an upgrade to around 450 access point. The current management ip address will not be enough.
Please, give me the best suggestion ?
Should i create another management ip address ? or I need to make a bigger subnet using the current management ip address ?
if i create a bigger ip address, the current access points must be set again yups ?
Second question
There will be a new link connected to the wlc, and i want to create new user subnets.
what is the best practices for this matter ?
if there are better suggestion, please let me know, i am still learning about wireless
I have attached the topology.
Thank you
Fanie

For an example, a 5508 can support up to 500 AP's, and the AP's can be in one large subnet or be in many different subnets and or even different locations. As long as the ap knows how to discover the WLC or the ap already had joined the WLC, then the AP's don't have to be on the same subnet as the WLC. The easiest way to have AP's join is to stage them on the same subnet as the WLC management and then move them to a different subnet. I would probably have no more than 100 AP's per subnet, but that's me. Stage some AP's on the management subnet that the WLC is on and then when the AP's join and complete downloading code, change the switch port Vlan and shut and no shut the port. The ap will come back up and join the WLC.
Sent from Cisco Technical Support iPhone App

5508 WLC upgrade

Looking to upgrade our 5508 WLC to the newest code AIR-CT5500-K9-7-2-103-0-FUS
We are currently running an older code 6.0.196.0
Are there any issues that I need to worry about with this upgrade ?
Do I need to upgrade the AP's at the same time ?
Any help would be appreciated.
Cheers
Dave

Looking to upgrade our 5508 WLC to the newest code AIR-CT5500-K9-7-2-103-0-FUS
Is the WLC going to be used in RUSSIA? That's what this code is for. If not, use the "AIR-CT5500-K9-7-2-103-0.aes" file instead.
Do I need to upgrade the AP's at the same time ?
The WLC will do it for you.

5508 WLC Upgrade from 7.0.116 to 7.2.111.3

I am planing to upgrade 2 of my 5508 series WLC from 7.0.116 to version 7.2.111.3. I understand that legacy AP's are no longer supported. Is there any other issues I should be aware of that others have experienced? Is the upgrade straight-forward just like other code upgrades? Thank you.

Thanks so much for all the information. Afterr reading throught this, it makes sense now. I do have one more question. After doing a show sysinfo on these controllers, it does look like the FUS does need to be updated. Should I perform this before I upgrade to version 7.2 code, or after I have peformed the upgrade to 7.2, or does it matter?
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.0.116.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

LWAPs stuck in downloading state after WLC upgrade

So I upgraded our WLC from version 4.0.155.0 to 4.0.217.0. Out of 98 LWAPs 8 didn't take the upgrade pushed out by the WLC. They seem to be stuck in a "downloading" operational status.
When I tried to add another LWAP from my workstation it seems to constantly try to upgrade but just ends up rebooting in a never ending cycle. The following is a capture:
*Mar 1 00:00:05.152: soap_prepare_new_image_crash: mini ios flash:/c1130-rcvk9w8-mx/c1130-rcvk9w8-mx
*Mar 1 00:00:05.153: set boothlpr to mini ios
*Mar 1 00:00:05.438: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self test passed
*Mar 1 00:00:06.715: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 0
*Mar 1 00:00:07.068: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Mar 1 00:00:08.041: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 1
*Mar 1 00:00:09.143: %SYS-6-LOGGERSTART: Logger process started
*Mar 1 00:00:09.183: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C1130 Software (C1130-K9W8-M), Version 12.3(11)JX, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2006 by Cisco Systems, Inc.
Compiled Mon 05-Jun-06 16:41 by pwade
*Mar 1 00:00:09.184: %SNMP-5-COLDSTART: SNMP agent on host ap is undergoing a cold start
*Mar 1 00:00:10.080: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to up
*Mar 1 00:00:11.080: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to up
*Mar 1 00:00:22.639: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
*Mar 1 00:00:28.198: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
*Mar 1 00:00:40.592: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned DHCP address 10.34.171.71, mask 255.255.255.0, hostname AP001b.d40b.107a
Translating "CISCO-LWAPP-CONTROLLER.nation.radix"...domain server (10.16.241.100)
*Mar 1 00:00:49.685: LWAPP_CLIENT_ERROR: lwapp_name_lookup - Could Not resolve CISCO-LWAPP-CONTROLLER.nation.radix
examining image...
extracting info (286 bytes)
Image info:
Version Suffix: k9w8-.123-11.JX
Image Name: c1130-k9w8-mx.123-11.JX
Version Directory: c1130-k9w8-mx.123-11.JX
Ios Image Size: 3072512
Total Image Size: 3072512
Image Feature: WIRELESS LAN|LWAPP
Image Family: C1130
Wireless Switch Management Version: 4.0.155.0
Extracting files...
c1130-k9w8-mx.123-11.JX/ (directory) 0 (bytes)
extracting c1130-k9w8-mx.123-11.JX/info (286 bytes)
extracting c1130-k9w8-mx
*Mar 1 00:00:59.710: %LWAPP-5-CHANGED: LWAPP changed state to JOIN
*Mar 1 00:00:59.710: %LINK-5-CHANGED: Interface Dot11Rad.123-11.JX/6701.img (131328 bytes)io0, changed state to administratively down
*Mar 1 00:00:59.711: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Nov 28 03:44:00.887: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Nov 28 03:44:00.887: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Nov 28 03:44:01.153: %LWAPP-5-CHANGED: LWAPP changed state to IMAGE
extracting c1130-k9w8-mx.123-11.JX/c1130-k9w8-mx.123-11.JX (2800592 bytes)
extracting c1130-k9w8-mx.123-11.JX/7101.img (131328 bytes)
extracting info.ver (286 bytes)
Deleting existing version...
Deleting flash:/c1130-k9w8-mx.123-11.JX...done.
New software image installed in flash:/c1130-k9w8-mx.123-11.JX
Configuring system to use new image...done.archive download: takes 53 seconds
*Nov 28 03:44:54.879: image upgrade successfully, system is now reloading
*Nov 28 03:44:54.917: %SYS-5-RELOAD: Reload requested by lwapp image download proc. Reload Reason: NEW IMAGE DOWNLOAD.
*Nov 28 03:44:54.917: %LWAPP-5-CHANGED: LWAPP changed state to DOWN
Then it reboots and repeats the process.
I have read through other conversations similar to this but have found no solution. Does anyone have any ideas?
Thanks

Did you find a solution? I have the same problem.
Edit: Seems my AP keeps switches between 2 controllers with different software versions. However only 1 is in the DHCP option.

WLC upgrade to 7.0.98.0, WCS & Location Appliance to upgrade - Building maps location

Similar Messages

Maybe you are looking for