Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
2111
Views
0
Helpful
13
Replies

WAAS 4.2(1) is now available on CCO!

Zach Seils
Level 7
Level 7

‎06-22-2010 03:15 AM

It is our sincere pleasure to announce:

WAAS 4.2(1) is now available on CCO!

The 4.2(1)  software images can be found here:

http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=4.2.1&mdfid=280484571&sftType=Wide+Area+Application+Services+%28WAAS%29+Software&optPlat=&nodecount=2&edesignator=null&modelName=Cisco+Wide+Area+Application+Services+%28WAAS%29+Software&t...

The  release notes & docs can be found here:

WAAS  4.2(1) Release Notes

http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v421/release/notes/ws421xrn.html

WAAS  4.2(1) Command Reference

http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v421/command/reference/cmdref.html

WAAS  4.2(1) Configuration Guide

http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v421/configuration/guide/cnfg.html

If you have any questions, please let us know.

Regards,

Zach

0 Helpful
13 Replies 13

Jan Rockstedt
Level 1
Level 1

‎06-22-2010 05:02 AM

Hi Zach,

Is the 4.1.7 the last version of 4.1x and will open caveats be fixed in 4.2.x?

Jan

0 Helpful

Zach Seils
Level 7
Level 7
In response to Jan Rockstedt

‎06-22-2010 06:28 AM

Hi Jan,

Yes, 4.1(7) is the latest release in the 4.1 train.  In general, the 4.2 train will include fixes for known issues in 4.1.  Do you have specific defects you are concerned about?

Regards,

Zach

0 Helpful

Jan Rockstedt
Level 1
Level 1

‎06-22-2010 06:41 AM

Hi Zach,

I dont have any specific defects.

I am just wondring as we are expanding with new WAE every week.
So it is not that easy to upgrade any more, as we are seeing an flap on the inline interface when we reboot the WAE.

Jan

0 Helpful

Zach Seils
Level 7
Level 7
In response to Jan Rockstedt

‎06-22-2010 06:46 AM

As far as defects are concerned, 4.1(7) and 4.2(1) should be pretty close, since they were released so close together.  It's possible that some more complex fixes went into 4.2(1), but I'd need to check to be sure.  I'll look at the numbers more closely this afternoon and post an update.

Zach

0 Helpful

ltroutman
Level 1
Level 1

‎06-22-2010 08:00 AM

It looks like the config guide and release notes links lead to the 4.1.7 version, not 4.2.1.

Can you let us know when the 4.2.1 docs will be availabble?

Also, it looks like the binary image for 4.2.1 is about half the size of 4.1.x - have some older features been cut, or have the programmers just been able to squeeze everything into a smaller package?

0 Helpful

Zach Seils
Level 7
Level 7
In response to ltroutman

‎06-22-2010 10:50 AM

The full set of documentation should be available in the next day or so.

One of the features in the 4.2(1) release is a reduction in the binary image size.  This is why the 4.2(1) image is much smaller than previous versions.

Regards,

Zach

0 Helpful

Zach Seils
Level 7
Level 7
In response to ltroutman

‎06-22-2010 10:53 AM

I just updated the links in the original post.  Please let me know if you continue to have problems.

Thanks,

Zach

0 Helpful

wrobbin
Level 1
Level 1

‎06-22-2010 08:20 AM

What is prerequisite for 4.2(1) ? Also  i just finished a little over a month and a half ago upgrading all my WAAS unit casue of a CIFS issue in 4.1.3b now we are running 4.1.5f. Is the any advanatage to upgrading to 4.2(1) ?

0 Helpful

Zach Seils
Level 7
Level 7
In response to wrobbin

‎06-22-2010 10:54 AM

The release notes are the best place to understand any prerequisites and what has changed in the 4.2(1) release.

Regards,

Zach

0 Helpful

Ryan Posey
Level 1
Level 1
In response to Zach Seils

‎06-24-2010 05:09 AM

Word of Warning.  4.2.1 and TACACS KEY

I upgraded Central Manager from 4.1.5f to 4.2.1 this morning.  After a reboot, I was unable to authenticate via TACACS.  Looking at ACS v4.2 failed authentication logs, the shared key no longer matched.  I was able to create a black-hole route on the ACS box, get into the Central Manager over a local account and reapply the TACACS KEY ****.  Once that was complete and the black-hole route was removed, I was able to get back into the Central Manager via my TACAS credentials.

With this being said my upgrade process will now include creating black-hole routes in TACACS (ACS) for all WAAS boxes, upgrade to 4.2.1, locally authenticate, reenter the TACACS KEYS again, and then remove the black-hole routes in ACS.

FYI...My TACACS KEY does contain special characters and that may be lending a hand to this problem.  However if 4.2.1 has added any new restrictions on the TACACS KEY characters, then it would not have allowed me to reenter the same key successfully.

0 Helpful

Zach Seils
Level 7
Level 7
In response to Ryan Posey

‎06-24-2010 06:10 AM

Thanks for the update, Ryan.  I'll take a look at this today.

Zach

0 Helpful

Zach Seils
Level 7
Level 7
In response to Zach Seils

‎06-29-2010 05:35 AM

Looks like this is a new bug: CSCth55027.

Regards,

Zach

0 Helpful

Ryan Posey
Level 1
Level 1
In response to Zach Seils

‎06-29-2010 06:37 AM

So as a prize for finding this, is there any chance of getting the next patch named after me!

4.2.1rp  It has a nice ring to it

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents