WAAS upgrade 4.0.13 to 4.1.3.55

Can I do this? should I got to a 4.1.1 version first then to 4.1.3.55?
thanks

Release Note for Cisco Wide Area Application Services (Software Version 4.1.3x)
Upgrading from Version 4.0.x or 4.1.1x to 4.1.3
http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v413/release/notes/ws413xrn.html#wp42041
Upgrading to version 4.1.3 is supported only from version 4.0.13 and later. If you want to upgrade WAAS devices running earlier versions, first upgrade them to version 4.0.13, 4.0.17 or 4.0.19, then to 4.1.3.
-Dan Laden

Similar Messages

WAAS upgrade help

Hi Guys,
I am doing WAAS upgrade from version 5.1.1 to 5.4.1a on the Central Manager. This would be my first time. I uploaded an image from ftp://xx.x.77.166/waas-universal-5.4.1a.17-k9.bin to the CM. I haven't enabled the Auto Reload. Once I enable Auto Reload check does that software installation is done completely?. After the upgrade is done for CM can i push the image and upgrade the SRE engines?
Thanks for your reply.

Hi Vishnu,
Basically you should follow the procedure outlined here :
http://www.cisco.com/c/en/us/td/docs/app_ntwk_services/waas/waas/v541/configuration/guide/cnfg/maint.html#26348
Since you've already have uploaded the software to the CM (and I assume that you want to use the CM as the "software repository" ) you should do the following :
Remember to create a backup of the CMS database and copy it somewhere outside the CM
enable ftp server on the CM (inetd enable ftp)
optionally create username for ftp usage (pointing to the CM itself)
Register the software image on the CM (see guide) - click "Auto Reload" if desired
on the CM device - click updatenow the software will be installed on the CM and the CM will reload (if Auto Reload is enabled)
Perform the same for your remaining WAAS devices - however I would recommend that :
You use the "Accelerator image only" for non-CM devices (it's "only" 290 MB vs 395MB) and thus reduces the transfer time
Upload and register this image similiar to the universal image
and follow the same procedure for each SRE/WAE/WAVE
If you haven't click the "Auto Reload" you'll need to reload the device yourself ... after the upgrade.
Remember that WAAS 5.4.x is not supported on 274/474/574/674/7341/7371
Best Regards
Finn Poulsen

WAAS Upgrade CM path from 4.4.7 WAE-512 to 5.4 vCM

I have a deployed WAAS system running 4.4.7 and the old WAE hardware is all on the EOL clock or not supporting 5.4 at all. The budge fairies had money at the end of the year so I've got new WAVE boxes and vCM 5.4 DVDs to deploy.
My question is what is the upgrade process for the CMs?
Can I simply spin up two 5.4 vCMs as a secondary CMs to the 4.4.7 primary CM on a WAE-512, then make one the primary? That would assume that a 5.4 secondary could sync to and then take over directly from a 4.4.7 primary. That's the bit that I have doubts about.
Or would I have to start with vCMs at 4.4.7 to get them to sync, then take over as primary and upgrade them? Is there a 4.4.7 vCM image?
If that's a dead end, I saw another discussion about downgrading a WAVE-294. I'm thinking one could be downgraded to 4.4.7, joined as a secondary CM, promoted to primary, and then upgraded as a stepping stone to vCMs at 5.4. Then the '294 would be deployed back as accelerator as originally intended. Any pitfalls with this?
Or is there a simpler path that I'm missing entirely?
Also can anyone confirm that the RJ-45 console ports on the WAVE-*94 have the same pin-out as traditional Cisco switch RJ-45 console ports?
Thanks.

Hi Edward,
For the upgrade process, you'll have to follow this procedure :
http://www.cisco.com/c/en/us/td/docs/app_ntwk_services/waas/waas/v541/release/note/waas541xrn.html#pgfId-171257
So either down grade your vCM to 4.4.7 (this requires that it is a vCM-100 or -2000)
- there probably is a vCM 4.4.7 image out there somewhere, but these could be hard to get.
- or just use the "copy ... install" on your vCM, to get it downgraded.
or use the 294 method (same methodology applies)
But as I see it, there is no need to play around wit ha secondary CM, you don't need the CM to ensure optimization, when things are up and running.
You can easily change a CM to an accellerator by configuration and a reload, unless we're taking vWAAS, where the ova image is locked.
remember to take a backup of your CMS database and place it somewhere else, before starting upgrading.
Best Regards
Finn Poulsen

Looking for the Proper WAAS Upgrade Path

A while back I started upgrading some of our WAAS 274/574 devices and once I got halfway through I relized I was on the wrong path to get the devices to accelerate and compress Native ICA for our Citrix sessions.
So Currently I have half our devices at 4.3.3c and the other half at 4.4.7
So my questions are....
What is the latest greatest version that I should be at for Native ICA Acceleration?
What is the best upgrade/downgrade path I should take to get there?

Dan,
It is recommended/required to run 4.2.1 (or a later version) before you install Version 5.3.1
You cannot upgrade from 4.0, 4.1, or 4.2 to 5.3.1 since it is NOT supported
Here you have a link about it:
http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v531/release/notes/ws531xrn.html#wp63349
Please see the hardware specifications
Hope this helps!
Jorge

Cisco WAAS Upgrade HW Support

Hi.
I need to upgrade my WAAS solution from Release 5.3.5 to 5.4.1, but I do not find any information about my Hardware in version 5.4.1.
Is this hardware supported on version 5.4.1?
WAE-674
WAE-574
SM-SRE-700-K9
Regards,
Paulo Soares

I have Upgraded the image, and still I get the following:
sabf-0004-centraloff-wae-1#sh accelerator
Accelerator     Licensed        Config State    Operational State
cifs            Yes             Enabled         Shutdown
epm             Yes             Enabled         Shutdown
http            Yes             Enabled         Shutdown
mapi            Yes             Disabled        Shutdown
nfs             Yes             Enabled         Shutdown
ssl             Yes             Enabled         Shutdown
video           No              Enabled         Shutdown
sabf-0004-centraloff-wae-1#sh alarms
Critical Alarms:
        Alarm ID                 Module/Submodule               Instance
   1 svcdisabled               nodemgr                      sodre_stats
Major Alarms:
None
Minor Alarms:
None
sabf-0004-centraloff-wae-1#sh version
Cisco Wide Area Application Services Software (WAAS)
Copyright (c) 1999-2011 by Cisco Systems, Inc.
Cisco Wide Area Application Services Software Release 4.4.3c (build b9 Nov 29 2011)
Version: oe7371-4.4.3c.9
Compiled 16:12:50 Nov 29 2011 by damaster
Device Id: 00:1a:64:c9:a2:0c
System was restarted on Fri Dec 30 07:00:47 2011.
The system has been up for 17 minutes, 50 seconds.

WAAS - Upgrade from transport to enterprise license

Hi
I have a WAE that has a Transport license, and is currently running on version 4.0.17
I need to upgrade it 4.1, and upgrade to an enterprise license (We have bought the license)
Does any1 have a documentation that shows the steps needed to upgrade from transport license to enterprise license?

Licenses are installed and managed only on individual WAE devices, not device groups. Not all licenses are supported on all devices.
To add a license from the WAAS Central Manager, follow these steps:
Step 1 From the WAAS Central Manager GUI navigation pane, choose My WAN > Manage Devices.
Step 2 Click the Edit icon next to the device that you want to modify.
Step 3 In the navigation pane, choose Admin > License Management.
Step 4 Check the check box next to each license that you want to add.
Step 5 Click Submit.
To add licenses from the CLI, you can use the license add EXEC command.
To remove licenses from the CLI, you can use the clear license EXEC command.
To display the status of all licenses from the CLI, you can use the show license EXEC command.
The setup utility also configures licenses when you first set up a new WAAS device

Waas upgrade via gui - schedule upgrade

Hi,
it is possible to upgrade remote waas via gui, scheduling the time for the upgrade?
Central Manager version 4.1.7a
Thanks
Andrea

Hi,
You can do the upgrade from the GUI without any reload.
Then scheduled an reload from the CLI.
Jan

WAAS upgrade to 4.4.3c and Isilon

Hi
Upon upgrading from WAAS 4.3.3 to 4.4.3c, we have had to disable the CIFS acceleration as there seems to be an incompatibility between the CIFS accelerator and our Isilon NAS (running their version of samba/OneFS). A TAC case is open on this. Users are unable to connect to the shares; whereas on 4.3.3 everything was ok.
Just asking if anyone has successfully upgraded to 4.4.x code and is using the CIFS accelerator on samba share targets.
Cheers
Cameron

This ended up being a problem on the Isilon nodes which a SMB patch solved. It appears as if some slight change in the CIFS implementation in 4.4.x caused the SMBD process to crash on the Isilon nodes when clients attempted to browse shares on the Isilon nodes. This effect was not seen on 4.3.3.
Isilon applied a patch which resolved the issue.

Waas upgrade

hi guys!
am upgrading waas 4.0.19 to 4.1.1.
are the licenses (enterprise, transport and cm) affected? or i have to reload them again on the upgraded devices?
thanks

In 4.0.x the license is a paper based and system don't check anything. But, in 4.1.x you need to have appropriate license configured to use the WAE properly. Pl look at this URL (especially under 'Licensing' heading)
http://www.cisco.com/en/US/prod/collateral/contnetw/ps5680/ps6870/data_sheet_c78-445372.html
From the above URL
"Upgrade from Cisco WAAS Software Version 4.0
Customers who have an active Software Application Support plus Upgrades (SASU) contract in place can upgrade from Cisco WAAS Software Version 4.0 to Version 4.1 with no additional cost. "
thanks
Nat

When trying to download 4.1.5f WAE stays in pending mode

in the process of upgradinf from 4.13b to 4.1.5f
, CM is at 4.1.5f, when start a software upgrade most of the WAEs upgrade ok, but a couple stay in pending mode and when I look at the syslog i see the following message:
2010 May 5 21:54:54 BATWAD01 java: %WAAS-CMS-4-700002: ce(DataFeedPoll): java.l
ang.IllegalStateException: Managed store key does not exists, which is needed to
process SslCertificateKey objects. Rejecting updates from CM: java.lang.Illegal
StateException: Managed store key does not exists, which is needed to process Ss
lCertificateKey objects. Rejecting updates from CM      at com.cisco.unicorn.dir
ector.DataFeedAgent.storeUpdateInternal(DataFeedAgent.java:251)         at com.c
isco.unicorn.server.ADataFeedAgent.storeUpdate(ADataFeedAgent.java:755)        a
t com.cisco.unicorn.server.ADataFeedAgent.onUpdate(ADataFeedAgent.java:510)    a
t com.cisco.unicorn.server.ADataFeedAgent.getUpdatesFromCurrentCdm(ADataFeedAgen
t.java:1230)    at com.cisco.unicorn.server.ADataFeedAgent.getUpdates(ADataFeedA
gent.java:956) at com.cisco.unicorn.director.DataFeedAgent.getUpdates(DataFeedA
gent.java:1248)         at com.cisco.unicorn.server.ADataFeedAgent.runImpl(AData
FeedAgent.java:678)     at com.cisco.unicorn.server.AModule.run(AModule.java:177
)       at java.lang.Thread.ru
I do not use SSL so not have any keys
How do I download the new code and get rid of thepending message
can I just do the CLI "copy ftp install" command?

Hi,
Do you have any alarms in the box. I faced the same issue and it had an SSLAO alarm. I downgraded to 4.1.3b, disabled SSLAO and upgraded 4.1.5f .It worked. I am not sure thats a perfect solution, but it worked for me

Wae-574 single disk system replacement

Hello,
We've had a wae-574 lose it's only disk. Can someone confirm the steps I need to do to replace it? I know I need to power off the unit and replace the drive. Do I need to do a disk shutdown beforehand?
Do I need to do anything to have it recognize the replacement drive and rebuild it? All of the documentation I've found talks about replacing a drive in a multidrive raid 1 or raid 5 system but I'm not finding what steps I need to take in a single disk system scenario.
The system is still up and running it's just not accelrating any traffic at the moment.
Thanks,
Elliott

No problem. Mine knew the exact procedure but I had a hard time at the beginning convencing him the drive was actually dead since I could not generate the standard sysreprt or diagnostic report. There are no and apparently never were any drive lights. Once I got started I just had to figure out the missing pieces such as the de-register / re-register force stuff.. Also some of these did not apply as I do not have multiple drives for mirroring but the system let me know that. Here are the details he started me with...
++You need to burn this file into a disk and then follow these steps :
http://www.cisco.com/en/US/docs/app_ntwk_services/waas/wae/troubleshooting/recoverycd/guide/17088rcd.html
There are 8 steps here, out of which you need to use 2,3,5 & 7 with the disk inserted and step 8 after manually removing the device. Step 7 should be repeated twice to make sure no file remains corrupted. Leave 1st,4th & 6th step entirely in this case.
++If you don’t have physical access to the device and the device is accessible remotely, you can download this file in accelerator.bin format from the Cisco website to your FTP server and install the software directly from there. In that case use this command on the CLI of the device :
#copy ftp install ftpserver / waas-image.bin
(This example assumes that the file is in the root directory of the FTP server. Provide the correct path if needed.)
You can go through this document to refer how to install from FTP server:
http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/upgrade/guide/waas_upgrade-44.html
Brent

Upgrade waas 4.1

we have a customer with 2 different versions of cisco waas
one is running 4.1 the other 4.0 both with their own CM
the CM of the 4.0 network should disappear and the sites should be migrated to the CM 4.1
the question is how to do this as for 4.0 you first have to do the devices before upgrading the CM and in 4.1 this is the other way around, first CM then the devices
is it possible that i first upgrade the devices, reboot and then assign them the new CM?

With WAAS 4.1, the upgrade procedure has changed. The procedure described below should be followed:
1. Upgrade the standby Central Managers first (if any)
2. Upgrade the primary Central Manager
3. Upgrade all other WAEs.
In 4.1 upgrading devices configured for optimizatoin (Application Accelerator) to higher version than CM is not supported or recommended. So, pl follow the procedure described above.

WAAS OS upgrade issue

Hi ,
I upgarded the WAAS os from 4.2.3 to 4.3.3 on a WAE-274 . The "sh ver" ," sh flash" result shows the WAAS OS as 4.3.3. But in WAAS CM, under s/w version the device shows "4.3.3 {update failed} " error .
I also tried to reload the device after upgrading the WAAS OS but still Iam getting the same error message.
Please advice.

Hi Ameen,
What is the CM OS current version?
Have you upgraded your device through the CM or using copy ftp install commnad directly?
It would be a good step to check the syslog in the CM and the device you have upgraded, use "type syslog.txt" command to it.
Best regards,
Ahmad

WAAS 4.4.5 upgrade to 4.5.1?

My WAAS deployment is currently at 4.4.5 and I just got a hold of 4.5.1 through my account manager. Not sure if I can do a direct upgrade or not since the release notes for 4.5.1 states the following:
Upgrading to Version 4.5.1 is supported only from Versions 4.1.1d, 4.1.3, 4.1.3b, 4.1.5c, 4.1.5f, 4.1.7, 4.1.7a, 4.1.7b, 4.2.1, 4.2.3, 4.2.3c, 4.3.1, 4.3.3, 4.3.5, 4.4.1, 4.4.3, and 4.4.3a. If you want to upgrade a WAAS device running a different version, first upgrade to the next supported version in the list, and then upgrade to the current 4.5.1 version.
From what I understand 4.5.1 is built off of 4.4.3 with the only added functionality being the Citrix ICA optimizer (which is what I want). Does anyone have any experience with this or know for a fact that it can be done without causing any issues?
Thanks, Jan

Actually I found the answer after reading the release notes for the current version I am using. The following is from those notes:
Downgrading from Version 4.4.5x to a Previous Version
Note the following guidelines and considerations for downgrading:
•A downgrade is supported only to Versions 4.5.1,
Makes sense considering 4.5 is based on 4.4.3.

How do I upgrade from WAAS CM on WAE-7326 to vWAAS CM

My WAAS network comprises of WAE-612 and WAE-7326 Running Sotware version 4.3.3.1, these are old and we are now going to Cisco 3945 Routers with SRE WAAS and the vWAAS as Central Manager.
The problem is how do I get the configuration across from the 7326 that is a CM to the vWAAS CM?
Can the vWAAS run software version 4.4? if so my standyby CM is a WAE612 which can be upgraded to 4.4, so I would make that the primary CM the new vWAAS as standby, so then the configuration would go across to the new vWAAS. once done make the vWAAS primary again, then install a second vWAAS as standby.
is the above possible?
I can't find any documentation about upgrading the WAAS nework

Hi Edward,
For the upgrade process, you'll have to follow this procedure :
http://www.cisco.com/c/en/us/td/docs/app_ntwk_services/waas/waas/v541/release/note/waas541xrn.html#pgfId-171257
So either down grade your vCM to 4.4.7 (this requires that it is a vCM-100 or -2000)
- there probably is a vCM 4.4.7 image out there somewhere, but these could be hard to get.
- or just use the "copy ... install" on your vCM, to get it downgraded.
or use the 294 method (same methodology applies)
But as I see it, there is no need to play around wit ha secondary CM, you don't need the CM to ensure optimization, when things are up and running.
You can easily change a CM to an accellerator by configuration and a reload, unless we're taking vWAAS, where the ova image is locked.
remember to take a backup of your CMS database and place it somewhere else, before starting upgrading.
Best Regards
Finn Poulsen

WAAS upgrade 4.0.13 to 4.1.3.55

Similar Messages

Maybe you are looking for