Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrade to 4.2 WCS

Has anyone taken the leap yet?

I was going to my WCS today and then do my controllers tomorrow afternoon.

I was going to take Cisco on its' word:

Upgrading to a New Software Release

The Cisco WCS release must be the same or more recent than the controller software release. Upgrade the Cisco WCS first to prevent any unexpected problems. Cisco WCS supports database upgrades only from the following official Cisco WCS releases:

from http://www.cisco.com/en/US/docs/wireless/wcs/release/notes/WCSRN4_2.html#wp44431

but figured I would ask first.

25 REPLIES
Bronze

Re: Upgrade to 4.2 WCS

I'm running it - seems very stable. Creating reports still a bit tedious. But all and all its working very well. Discovered my WISMs and APs very well. We have 18 floors with 4 APs on each floor. Wish there was a copy and paste method in the creation of maps though.

Re: Upgrade to 4.2 WCS

Cool. What sw version are you running on the wisms?

We are running 4.1.185.0 on our 4402 units.

I was planning on upgrading the WCS this am, and then doing the controllers later today when the wireless will not be utilized.

Re: Upgrade to 4.2 WCS

Damn, that was too easy!

Everything carried over except the html formatting on my login message, but that is an easy fix

Re: Upgrade to 4.2 WCS

As we used to say in the Army, keep your head down man. You can be the first Christian thrown to the lions. In other words, thanks for taking the leap and let us know how it goes in a week.

Thanks,

Dennis

Re: Upgrade to 4.2 WCS

So far, so good. I run WCS (as well as most everything else) on Linux and it took only two command strings (with prompts) and about 5 minutes

The 1st command was /opt/WCS4.1/Backup

and the second was ./WCS-STANDARD....bin

Oh yeah, had to do a chmod u+x on the bin file first in order to run it.

The only issue I noticed was the html formatting, but once I went into that menu, I saw that html is no longer allowed, but at least the paragraph formatting is preserved now - which is the reason why I used html in the 1st place!

Now, if only I can figure out how to add external links into the tabs/menus, then I would be all set!

Re: Upgrade to 4.2 WCS

A further note: The login message only retains its formatting in IE but not in Firefox of course. Yeah, I know Cisco does not support Firefox, but it works fine when using FIrefox under Linux (except for the formatting). Firefox under windows will load up on memory and grind to a halt.

Bronze

Re: Upgrade to 4.2 WCS

Hi , we have SVC-WiSMs with software version: 4.1.185.0 as well.

Re: Upgrade to 4.2 WCS

I pushed out 4.2.x to the controllers last night without any issues.

One item of note: When I ran the inventory report from WCS, it showed all radios having 4.1.185.0 rather than 4.2.x. Drilling down into the radio links within WCS as well as WLC (both web & cli) indicate that they have 4.2.x as their firmware. I will run the inv report again this am and see if it has changed

Re: Upgrade to 4.2 WCS

That's interesting. Let me know if they still show the old code version and I will get it over to the BU.

New Member

Re: Upgrade to 4.2 WCS

I had to "Refresh Config from Controllers" in WCS to make my AP list show up correctly after I pushed out the new code.

Re: Upgrade to 4.2 WCS

How long did you wait before you did this? The controllers should automatcally refresh the WCS about every 10 minutes. If this is failing then I suspect we are seeing that same old ARP issues that has haunted us for years.

Hall of Fame Super Silver

Re: Upgrade to 4.2 WCS

You guy's better look at the caveats! Here are some if 4.2 is installed on the WiSM:

• CSCsk09466-After you reboot the Cisco WiSM through the GUI, the controller becomes unresponsive.

o Workaround: To recover, pull out the WiSM module or power cycle the Catalyst 6500 switch.

• CSCsf29783-The Cisco WiSM reboots after experiencing a failure with the reaperWatcher mmMfpTask.

o Workaround: None.

• CSCsi76581-The WiSM controller reboots after running a ping test from the WCS map.

o Workaround: None.

• CSCsk01753-The Cisco WiSM might reboot due to a failure in the sshpmReceiveTask.

o Workaround: None.

• CSCsk09466-After you reboot the Cisco WiSM through the GUI, the controller becomes unresponsive.

o Workaround: To recover, pull out the WiSM module or power cycle the Catalyst 6500 switch.

• CSCsk85757-The Cisco WiSM reboots after operating for 32 days because the sshpmReceiveTask missed the software watchdog.

o Workaround: None.

-Scott
*** Please rate helpful posts ***
New Member

Re: Upgrade to 4.2 WCS

We had it up for a couple of weeks and it never refreshed the AP list data until I did a "Refresh Config from Controllers" command in WCS.

Re: Upgrade to 4.2 WCS

Ran the report this am. All APs are up to proper rev in the report

New Member

Re: Upgrade to 4.2 WCS

Hello,

do you use any 1121G APs on your network?

I have tested 4.2 in my lab and I have following problem (copy/paste from other forum):

Hello,

I had working lab with 4402 controller, 1121G AP and 4.1.185.0 sw.

After upgrade to 4.2.61.0 it looks like AP won't load new image, on WLC is a lot of AP Associated / AP Disassociated messages in log. I have tried same thing with 2106 controller and same thing happens. I have looked in Bug tool but there isn't any similar bug. Any ideas?

Re: Upgrade to 4.2 WCS

Nope. We have 1020 APs, but we are looking into replacing all APs with 1252 LAPs in the near future

New Member

Re: Upgrade to 4.2 WCS

Problem installing WCS 4.2.62.0 upgrade.

Has anyone run into a problem installing this version? I downloaded the Windows .exe file from Software Downloads to my server. I un-installed 4.1.83.0 and then ran the installer. It begins the installation and then I get the error file seen in the attached document.

I've deleted the exe file I downloaded from Cisco, thinking maybe it was corrupted, but had the same problem when I downloaded it again. Any suggestions are welcome.

New Member

Re: Upgrade to 4.2 WCS

Issue resolved.

I had to download WCS Navigator 1.1.62.0 in order to get the actual WCS 4.2.62.0 exe file to load properly.

Did anyone else find this documentation confusing?

Hall of Fame Super Silver

Re: Upgrade to 4.2 WCS

just make sure you backu the WCS in case you decide to go back. One of my clients upgraded to 4.2 on the WCS and WLC. WCS has some bugs but not as bad as when we upgraded the WLC. AP's were loosing connection to the WLC and users were not able to associate if idle timeout was set to 10000 or higher... TAC told me that they will come out with a newer code.... within 3 months.

-Scott
*** Please rate helpful posts ***
Silver

Re: Upgrade to 4.2 WCS

There are other "unresolved caveats" in 4.2 (a list that is growing significantly faster and larger than the "resolved caveats" list):

WLC 4.2.61 Release notes: http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn4200.html

WCS 4.2.62 Release Notes http://www.cisco.com/en/US/docs/wireless/wcs/release/notes/WCSRN4_2.html

Specifically, the following was of concern to me:

CSCsk16314-Access points start downloading new software before the controller has been rebooted.

Workaround: None.

Since the LWAPs immediately begin downloading code prior to the WLC's reboot as the final stage of its upgrade.

This results in the possible interruption of up to 10 LWAPs in mid-upgrade. According to Cisco, you really do not want to interrupt the LWAP in the middle of an upgrade. If you do, you may have to reload the APs from scratch which could take some time... if you can still communicate with them. If not, you may have to get physical access to them.

If you have multiple controllers, then the potential problem can be quite significant.

It would seem to make sense to isolate the controllers from the LWAPs during the upgrade to the controller(s) and, once the controllers upgrade and reboot, then re-establish connection to the access points.

On the flip side, I had a customer decide to "go for it" on his 300-LWAPP, multi-controller system and he ran the gauntlet successfully without isolating the LWAPs... but as they say, Caveat Emptor (which means, when loosely translated, "we have been sold a bunch of caveats").

- John

New Member

Re: Upgrade to 4.2 WCS

Hi John,

This explains why I saw the APs on one of my controllers dissassociate during the s/w download to the controllers. Fortunately they all came back up without any intervention.

I initially saw the misreporting of the APs' s/w version but that has now gone after doing a few "refresh from controller"s. Also a few other problems have gone since I upgraded to 4.2, the worst of which was that all of the APs on a controller would dissassociate from it for no apparent reason even when AP fallback / mobility groups were correctly configured.

Regards

Scott

New Member

Re: Upgrade to 4.2 WCS

Hi all,

I am really concerned about the caveats that fella5 pointed out in the release notes. Problem is I have no idea what half of them mean.

In particular:

• CSCsf29783-The Cisco WiSM reboots after experiencing a failure with the reaperWatcher mmMfpTask.

o Workaround: None.

- What is reaperWatcher mmMfpTask?

• CSCsk85757-The Cisco WiSM reboots after operating for 32 days because the sshpmReceiveTask missed the software watchdog.

o Workaround: None.

• CSCsk01753-The Cisco WiSM might reboot due to a failure in the sshpmReceiveTask.

o Workaround: None.

- What is sshpmReceiveTask?

Thanks.

New Member

Re: Upgrade to 4.2 WCS

Anyone else seeing a lot of disassociations/reassociations with 4.2.61.0? If so any fix?

New Member

Re: Upgrade to 4.2 WCS

Yes, but only with 1121 APs which were (unsuccessfully) converted to LAP and trying join WLC...

Silver

Re: Upgrade to 4.2 WCS

Further feedback:

Although not a surpise, running 4.2 WCS and 4.1.185 WiSM code is a very BAD idea. There were a number of very strange behaviors (even for the WCS) that indicated we were having synchornization issues (that is, more than usual) between the WCS and WiSM. Once we upgraded the WiSMs to 4.2 there were many fewer problems.

- John

334
Views
13
Helpful
25
Replies
CreatePlease to create content