topic WAAS 4.1.1.c problems in Application Networking

WAAS 4.1.1.c problems

elliottreyes — Mon, 12 Jan 2009 18:49:57 GMT

Does anyone have as many problems as I do with these WAAS appliances. It seems as if I have a problem every week with these things.

Re: WAAS 4.1.1.c problems

steven-dunn — Tue, 13 Jan 2009 04:52:10 GMT

what is/are the problems ?

Re: WAAS 4.1.1.c problems

elliottreyes — Tue, 13 Jan 2009 04:56:03 GMT

1. tfo accelerator overloads

2. dropping offline for no reason (Need to power cycle)

3. mapi accelerator issues with exchange 2007

4. cifs window shares disappear or problems with the accelerator restarting.

Re: WAAS 4.1.1.c problems

Patrick Murphy — Thu, 15 Jan 2009 21:19:42 GMT

So far, I've found two issues:

1. Randomly sending email in Outlook 2003 users will get the below message. I have TAC case open for this.

---

This message could not be sent. Try sending the message again later, or contact your network administrator. The client operation failed. Error is [0x80004005-0x0004b9-0x000501].

---

2. Issue with using the Outlook viewmail plugin for the cisco phones. Outlook will freeze when the user hits the play button.

The odd thing is issue one only happens at site x and issue to happens at site y. Putting the specific flow in bypass seems to resolve the issue. I will let you know more once I resolve issue 1.

Thanks,

Patrick

Re: WAAS 4.1.1.c problems

nchidamb — Tue, 27 Jan 2009 18:48:24 GMT

Patrick,

Are the above problem happened only after upgrading to 4.1.1c? If so, did you get a chance to open a TAC case to resolve it?

thanks

Nat

Re: WAAS 4.1.1.c problems

nchidamb — Tue, 27 Jan 2009 18:56:33 GMT

1. TFO accelerator overloads may happen due to the fact that there are many more TCP connections are hitting the WAE than it is designed to handle. What type of WAE (or) NME you are using?

2. Is CM showing you that a specific WAE is in offline status (or) you are unable to console/telnet into that WAE? If CM is showing that a specific WAE is offline are able to console or telnet into it? Are you able to ping that WAE at the time of 'offline' status? Is it happening only after you upgraded the WAE to 4.1.1c? What version of CM are you running?

3. What is the issue you are running with MAPI accelerator with Exchange 2007? Do you have encryption ON or OFF for the exchange mail traffic?

4. Are you using CIFS AO that was introduced in 4.1.1 or the older WAFS ( which is based on tunnel over port 4050?)

Re: WAAS 4.1.1.c problems

elliottreyes — Tue, 27 Jan 2009 19:05:55 GMT

Does it matter whether encryption is on or off ?

I know how to turn off encryption on the client is there a overall setting on the server as well.

Re: WAAS 4.1.1.c problems

ckolasinski — Wed, 11 Feb 2009 17:12:27 GMT

You can turn off encryption via a GPO...

We ran into the issue of exchange clients opening hundreds of connections to their exchange server and keeping the connections open. At first we thought this was a WAAS problem, but upon further investigation we were able to determine that clients at both Accelerated and Non Accelerated sites were having the issue. We are in the process of investigating the following MS KB948496

Re: WAAS 4.1.1.c problems

Richard Bradfield — Mon, 16 Feb 2009 07:07:38 GMT

we have similar problems to you,

Cisco TAC were online to our system for a good 4 hours the other day, and from the traces they think some of the problems are to do with WCCP, and have passed info higher up the Cisco support chain

Re: WAAS 4.1.1.c problems

Patrick Murphy — Wed, 25 Feb 2009 15:20:33 GMT

Nat:

The issues existed in 4.1.1a. Cisco recommended upgrading to 4.1.1c, but that did not fix the issue. I've sent in captures and sysreports to Cisco, but haven't pinpointed the issue yet. It is very random and sometimes resolves itself before I get to it.

Re: WAAS 4.1.1.c problems

jorjes1984 — Thu, 23 Apr 2009 12:30:10 GMT

Hi All

I have also many problem in the WAAS

it is running now on 4.1.1a

can you please advise if any had the same problems and how it was resolved??

REgards,

Re: WAAS 4.1.1.c problems

dstolt — Thu, 23 Apr 2009 12:59:00 GMT

Georges,

I think most of those issues would be resolved in that latest version of code (4.1.1d). I would try loading that as between 4.1.1a and 4.1.1d, there are a lot of bug fixes dealing with the new App Optimizers, etc. which is part of what you are seeing in your alarms.

You can see the resolved caveats in each version in the release notes: http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v411/release/notes/ws411rn.html

Dan

Re: WAAS 4.1.1.c problems

JHaynes4 — Thu, 23 Apr 2009 13:19:44 GMT

I can attest to 4.1.1d fixing most of our issues. I am waiting to see the feedback on the new 4.1.3 before upgrading to that code.

Re: WAAS 4.1.1.c problems

todd.martin — Tue, 28 Apr 2009 16:02:37 GMT

I did see some issues with certian applications and even filed a bug.

Go to 4.1.3 was a good move for us and resoled our bug and also resoved other things that we were not expecting.

Central manager reporting is improved too.

Re: WAAS 4.1.1.c problems

kmr — Wed, 06 May 2009 15:24:46 GMT

I upgraded to 4.1.3 last night after reading this thread. My core WAE does not show any entries in the Connections Summary table (monitor, connection statistics), the remote WAE shows connections, but no acceleration, no applied policy for connections. Bounced the core and no changes. Very frustrating.

Re: WAAS 4.1.1.c problems

nchidamb — Wed, 06 May 2009 16:16:18 GMT

This sounds to me that the core device is not intercepting the traffic. Are you using inline or WCCP for redirecting the traffic to WAE? If you are using inline card did you ensure that the inline interface is not in shutdown mode or you do not have 'no inline vlan all' command ( 'no inline vlan all' under inline interface means that do not intercept any traffic ).

In essence, the core WAE is not intercepting the traffic for some reason. So, you must ensure that the redirection technique you use properly redirects the traffic to WAE.

If WAE doesn't intercept the traffic then you will not see any 'connections' under WAE->Monitor->Connection Statistics.

Regards

-Nat

Re: WAAS 4.1.1.c problems

kmr — Wed, 06 May 2009 16:26:02 GMT

Traffic was being redirected as expected before upgrading the code. No changes made except WAE code upgrade. "sh wccp routers" on core WAE does not have an entry for "Router(s) seeing this Wide Area Engine" but does list the IP of the router for "Routers not seeing" this wae. sho ip wccp 61 det and 62 det on the router indicates the "State: NOT useable". Looks like WCCP has stopped working on the router. NO changes were made to the router.

Re: WAAS 4.1.1.c problems

nchidamb — Wed, 06 May 2009 16:42:35 GMT

From which version on WAE you upgraded to 4.1.3? I have done several times from 4.0.19 and 4.1.1x to 4.1.3 and I have never faced this problem because of upgrade.

Are you able to ping from WAE to router and vice versa?

Regards

-Nat

Re: WAAS 4.1.1.c problems

kmr — Wed, 06 May 2009 16:46:15 GMT

ICMP working properly in both directions. router sho ver:

Cisco IOS Software, 3800 Software (C3825-ADVENTERPRISEK9_IVS-M), Version 12.4(15)T7, RELEASE SOFTWARE (fc3)

System image file is "flash:c3825-adventerprisek9_ivs-mz.124-15.T7.bin"

Cisco 3825 (revision 1.2) with 487424K/36864K bytes of memory.

Processor board ID FTX1303A00T

2 Gigabit Ethernet interfaces

27 Serial interfaces

3 Channelized T1/PRI ports

1 Virtual Private Network (VPN) Module

DRAM configuration is 64 bits wide with parity enabled.

479K bytes of NVRAM.

125440K bytes of ATA System CompactFlash (Read/Write)

Re: WAAS 4.1.1.c problems

nchidamb — Wed, 06 May 2009 17:01:36 GMT

Now that I know you are using 38xx router as your traffic redirecting router could you tell me what is the redirect, egress & return method configured on the WAE? Perhaps, WCCP specific config from WAE might help to isolate the issue.

Regards

Nat