WAAS Problem

Hi all,
I have a problem with WAAS install. Basically, there is 1 CORE 674 wave, which has a vPC into 2 Nexus 7010s. I use L2 forwarding & mask.
There are around 100 remote sites, all over the world.
If I shut down the vPC on the 2nd Nexus 7k, the problem is still there. This to me looks like a problem with vPC, and redirect back from the Server side (at the DC). I have the identical 61/62 Service Group configurations on both Nexus' though...
I am not pointing to any VIP -- just the physical IP of the Nexus 7k.
Basically, one ping makes it, the second does not, the third does, etc. I've posted before and after....any ideas of what is happening?
I thought this is due to assymetrical routing, but accd to WAAS output logs not much asymmetry...

Robert,
It is possible that disk00 is bad/ has failed. Try the following:
1) WAE(config)#no disk disk-name disk00 shutdown force
If you get output similar to below go to option 2.
pdi-574-rtp(config)#no disk disk-name disk00 shutdown force
It takes time spinning up disk0. Please wait.
Disk not insert or not spin up yet. Please check cable or check syslog for RAID rebuild start events!
2) You can try to re-install the software with the recovery CD.
http://www.cisco.com/en/US/partner/docs/app_ntwk_services/waas/waas/v431/configuration/guide/maint.html#wp1173532
If the option "Wipe out disks and install .bin image" fails because it can't find disk00 you most likely need an RMA for a disk and you will need to open a TAC case to get this processed.
Regards,
Mike Korenbaum
Cisco Data Center PDI Help Desk
http://www.cisco.com/go/pdihelpdesk

Similar Messages

Waas: problems with peers identification

good days all.
we have got a problems with peers' identification in waas solution.
topology: 1 central-manager and 2 nme-502, both nme located in different location and subnets, and both see each other (pings are available from nme to nme). Version of solution 4.1.3b
But one device on the central-manager page in point "TFO Peer List Reported ByDevice" show ip for distant device, but distant device in the same point shows "There are currently no Peers to display".
And no any optimization actions
All troubleshooting methodology and guidances are useless....
with hope to help, thanks

Let's start by making sure that interception and redirection are working properly. You can start with the troubleshooting guide here:
http://docwiki.cisco.com/wiki/Cisco_WAAS_Troubleshooting_Guide_for_Release_4.1.3_and_Later_--_Troubleshooting_WCCP
Regards,
Zach

WAAS problem with DISK

Dear,
My WAAS have a issue I will apreciate your help .
When I switch on my WAAS show the next messages:
Cisco Wide Area Application Services Software (WAAS)
Copyright (c) 1999-2010 by Cisco Systems, Inc.
Cisco Wide Area Application Services Software Release 4.2.3 (build b7 Jul 29 2010)
INIT: Entering runlevel: 3
Node Health Manager started...
Nodemgr started!
2011 Jun 7 14:58:30 (none) kernel: %WAAS-SYS-3-900000: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
2011 Jun 7 14:58:30 (none) kernel: %WAAS-SYS-3-900000: sd 2:0:0:0: [sdb] Assuming drive cache: write through
2011 Jun 7 14:58:30 (none) kernel: %WAAS-SYS-3-900000: sd 2:0:0:0: [sdb] Assuming drive cache: write through
2011 Jun 7 14:58:30 (none) kernel: %WAAS-SYS-3-900000: Attached scsi removable disk sdb at scsi2, channel 0, id 0, lun 0
BOOT-100: disk apply
/ruby/bin/ruby_disk: First disk is missing, bad, marked bad, disabled via shutdown, or it has unknown data.
/ruby/bin/ruby_disk: Second disk is bad, missing, or shutdown; bailing out
ssmgr: open(/state/safestate, O_WRONLY|O_CREAT) failed: No such file or directory
ssmgr: op_open or media_open
IQ¥ failed: No such file or directoryñ=}
ssmgr: open(/state/safestate, O_WRONLY|O_CREAT) failed: No such file or directory
ssmgr: op_create or media_init
SSMGR RETURNING: 10 (No such file or directory)
2011 Jun 7 14:58:33 (none) memconfig: %WAAS-NODEMGR-3-330106: Memconfig: Cannot open /state/dre-diskspace file, errno: 2
2011 Jun 7 14:58:33 (none) memconfig: %WAAS-NODEMGR-3-330109: Memconfig: disk space allocated to DRE is 0, assuming DRE memory allocation of 100MB
One or more system software partitions are not mounted.
Check if disk00 is bad.
Initializing kernel random number generator...
/ruby/bin/ruby_startup_pre200.sh : Start KDUMP functionality...
Starting kdump failed.
/sw or /swstore doesn't exist! Won't turn on swap.
Creating Linux Strong Password files...
Running pre-200 hooks...
/ruby/bin/samba.pre-200: failed
grep: /sw/manifest: No such file or directory
ls: /sw/linuxapps/lib/: No such file or directory
/ruby/bin/ruby_startup_pre200.sh: Found no vmlinux file, skipping kdump vmcore analysis
BOOT: entering runlevel 200 (full operations)!
BOOT: System Initializing, please wait.Start service execve error: No such file or directory
2011 Jun 7 14:58:43 (none) Nodemgr: %WAAS-NODEMGR-3-330041: Start service execve error: No such file or directory
.Start service execve error: No such file or directory
Service start program '/sw/merlot/bin/spen' does not exist, err: No such file or directory
Service start program '/sw/merlot/bin/spen' does not exist, err: No such file or directory
.Service start program '/sw/unicorn/bin/uen' does not exist, err: No such file or directory
Service start program '/sw/unicorn/bin/aoim' does not exist, err: No such file or directory
WAAS-ARENALES#sh flash
Your software installation appears to be incomplete.
(could not access /sw/UP-TO-DATE or /swstore/manifest)
Please run 'copy ftp/cdrom install' to install a new image.
System image on flash:
Version: 4.2.3.b
System flash directory:
System image: 195 sectors
Bootloader, rescue image, and other reserved areas: 41 sectors
256 sectors total, 20 sectors free.
WAAS-ARENALES#sh disks details
Physical disk information:
disk00: Not used (*)
(*) Disk drive won't be used until replaced.
Mounted file systems:
MOUNT POINT TYPE DEVICE SIZE INUSE FREE USE%
No RAID devices present.
Disk encryption feature is disabled.
WAAS-ARENALES#
I will apreciate your help for my issue, I will probably is issue with the disk or It is neccesary a RMA for the HARDWARE?.
I hope your answer.
Regards,

Robert,
It is possible that disk00 is bad/ has failed. Try the following:
1) WAE(config)#no disk disk-name disk00 shutdown force
If you get output similar to below go to option 2.
pdi-574-rtp(config)#no disk disk-name disk00 shutdown force
It takes time spinning up disk0. Please wait.
Disk not insert or not spin up yet. Please check cable or check syslog for RAID rebuild start events!
2) You can try to re-install the software with the recovery CD.
http://www.cisco.com/en/US/partner/docs/app_ntwk_services/waas/waas/v431/configuration/guide/maint.html#wp1173532
If the option "Wipe out disks and install .bin image" fails because it can't find disk00 you most likely need an RMA for a disk and you will need to open a TAC case to get this processed.
Regards,
Mike Korenbaum
Cisco Data Center PDI Help Desk
http://www.cisco.com/go/pdihelpdesk

TCP resets with WAAS 7341?

We're running v4.4.1 on both remote and data center WAE 7341s and we're seeing TCP resets during some of our HTTP connections.
I'm just now beginning to look into the problem and noticed this the reset counters in 'show statistics tcp' such as:
IKA-7341-K9#sh statistics tcp
TCP statistics
Server connection openings                         = 2323
Client connection openings                         = 1850
Failed connection attempts                         = 111
Connections established                            = 68
Connections resets received                        = 57
Connection resets sent                             = 119
Segments received                                  = 365727
Segments sent                                      = 362292
Bad segments received                              = 0
Segments retransmitted                             = 642
I just rebooted the device an hour before doing the show command, and at this time there are only 12 connections being optimized.
Are these reset statistics of concern?

Hi Jeff,
TCP RST Packets is a counter of all TCP RST Packets over a period of time. This variable counts the number of RST responses to monitor resets in TCP/IP.
RST packets are a sign that the TCP connections are half open. One station or the other stopped sending information or ACKs for some reason. There are acceptable times for RST packets, however, if there are a large number of RST packets in a conversation, this is definitely something to troubleshoot.
This is not a WAAS problem but WAAS is showing up something that is going on in the network. These are some statistics that WAAS collects over the period from the network traffic.
Hope this helps.
Regards,
PS: Please mark this as Answered, if this answers your question.

CIFSAO-- error replying to client

I am getting continual messages as below in my syslog server:
Local7.Error chiwad01 2011 Aug 12 00: java: %WAAS-CIFSAO-3-131207: (288163) Error replying to client 172.16.6.167.
How do I find out what the problem is ? only get this on this one server
regards

Hi,
Is 172.16.6.167 client or server? Whatever it is, this server / pc is either virus infected / is opening constant CIFS connections, may cause slowness across device. These kind of error messages arise in the situation where :
1. A PC is infected wit hVirus / trojen and opening "n" number of remote connections.
2. A server that has AntiVirus software installed may cause this when it pushes AV signature updates to the clients.
3. A server that has any sort of security scanning software installed can cause "n" number of connections to open.
3. A server that has any sort of inventory management software installed can also cause this sort of situation.
In otehr words, this PC / server needs to be analyzed to find out why it is opening so many connections. Is it suppose to open so many connections?
This is not WAAS problem but rather that particular PC / server problem. You may want to run CLI command --> sh stat conn | inc 172.16.6.167
to find out how many open connections this client has.
Hope this helps.
Regards.
PS: If this answers your question, please mark this as Answered.

WAAS Optimization problem

Hello experts,
I have a problem about the WAAS optimization.
The topology is...
Center: 7200 Router working with WCCP (512 WAE)
Edge: 2800 Router working with WCCP (612 WAE)
When i tried to reach the Database (behind the 7200 Router) from the Edge site. its working! but during this time, when i look the Current Connection status, there is no optimization traffic(you can see the attach file).
I have done this setup, demo etc. too many times, but the first time i encountered such a problem.
you can see the configuration at the below.
By the way, when i look the "show ip wccp" command output. there is no traffic on Service identifier 62. Do we need to see increased this traffic?
Thanks in advance for your help.
BM-7206-METRO#show ip wccp
Global WCCP information:
    Router information:
        Router Identifier:                   10.200.200.193
        Protocol Version:                    2.0
    Service Identifier: 61
        Number of Service Group Clients:     1
        Number of Service Group Routers:     1
        Total Packets s/w Redirected:        37207
          Process:                           0
          Fast:                              0
          CEF:                               37207
        Service mode:                        Open
        Service access-list:                 -none-
        Total Packets Dropped Closed:        0
        Redirect access-list:                199
        Total Packets Denied Redirect:       1074214
        Total Packets Unassigned:            0
        Group access-list:                   -none-
        Total Messages Denied to Group:      0
        Total Authentication failures:       0
        Total Bypassed Packets Received:     0
    Service Identifier: 62
        Number of Service Group Clients:     1
        Number of Service Group Routers:     1
        Total Packets s/w Redirected:        0
          Process:                           0
          Fast:                              0
          CEF:                               0
        Service mode:                        Open
        Service access-list:                 -none-
        Total Packets Dropped Closed:        0
        Redirect access-list:                -none-
        Total Packets Denied Redirect:       0
        Total Packets Unassigned:            0
        Group access-list:                   -none-
        Total Messages Denied to Group:      0
        Total Authentication failures:       0
        Total Bypassed Packets Received:     0
CORE_WAE
configure terminal
primary-interface gigabitEthernet 1/0
device mode application-accelerator
central-manager address 10.10.10.10
cms enable
wccp version 2
wccp router-list 1 2.2.2.1 (ROUTER IP add)
wccp tcp-promiscuous router-list-num 1
EDGE_WAE
configure terminal
primary-interface gigabitEthernet 1/0
device mode application-accelerator
central-manager address 10.10.10.10
cms enable
wccp version 2
wccp router-list 1 1.1.1.1
wccp tcp-promiscuous router-list-num 1
CORE_ROUTER
ip wccp version 2
ip wccp 61
ip wccp 62
interface gi 2/0 (LAN)
ip wccp 61 redirect in
interface gi 3/0.26 (WAN) (Note: also this interface have a Tunnel int. connect to edge router tunnel int.)
ip wccp 62 redirect in
interface gi 1/0 (WAE LAN)
ip wccp redirect exclude in
ip cef
EDGE_ROUTER
ip wccp version 2
ip wccp 61
ip wccp 62
interface gi 1/0 (LAN)
ip wccp 61 redirect in
interface ATM 2/0.1 (WAN) (Note: also this interface have a Tunnel int. connect to central router tunnel int.)
ip wccp 62 redirect in
interface gi 2/0 (WAE LAN)
ip wccp redirect exclude in
ip cef

Hi Zach
Center router IOS version is c7200-advipservicesk9_li-mz.124-11.T.bin
Edge router IOS version is c2800nm-adventerprisek9-mz.124-9.T2.bin
Also you can see the configurations at the attach
Thanks,
My best.
CORE WAE CONFIG:
Based on the input, the following configurations will be done:
       central-manager address 10.166.0.10
       interface GigabitEthernet 1/0
         ip address 10.166.0.20 255.255.0.0
         autosense
       exit
       ip default-gateway 10.166.0.1
       ip name-server 10.201.0.201
       ip domain-name tcmb.gov.tr
       primary-interface GigabitEthernet 1/0
       hostname CORE
       clock timezone UTC 0 0
       wccp version 2
       wccp router-list 8 10.166.0.1
       wccp tcp-promiscuous router-list 8
       cms enable
EDGE WAE CONFIG:
Based on the input, the following configurations will be done:
        central-manager address 10.166.0.10
        interface GigabitEthernet 1/0
          ip address 10.126.2.20 255.255.255.0
          autosense
        exit
        ip default-gateway 10.126.2.1
        ip name-server 10.201.0.201
        ip domain-name tcmb.gov.tr
        primary-interface GigabitEthernet 1/0
        hostname EDGE
        clock timezone UTC 0 0
        wccp version 2
        wccp router-list 8 10.126.2.1
        wccp tcp-promiscuous router-list 8
        cms enable

Waas caching problem with zip files

hi,
When we send same zipped file to branches, waas does not cache that file, without zipping waas caches the file. Is there any restrictions for zip file?

Hi Muhammed,
When you say that WAAS is not caching, I guess you mean that the optimization achieved is much lower than without zipping the file. Am I correct?
If that is the case, then, I'm afraid it's the expected behavior. The cause for this is DRE
In general terms, the way DRE works is by caching small chunks of a file. Later on, when these chunks are seen again in the file (either in the same connection or subsequent ones), they will not be transferred through the WAN link and instead, a chunk identifier (very small) will be sent. The problem is that all compression algorithms work in a similar way, removing repeating parts of the file to make it smaller.
The result is that, any file that is encrypted/compressed has almost no repeating patterns in it, and therefore, even though DRE is applied, the reduction ratios are minimal, sometimes even getting to the point of making transfer even slower than without it.
As a general good practice, if you are using WAAS to optimized your data transfers, make sure that the files you are transferring are neither compressed nor encrypted. This way you will get the maximum optimization ratios out of WAAS.
I hope this answers your question
Daniel

WAAS / CIFS Problems

Hello all,
We recently deployed WAAS (4.1) system in our datacenter / remote office. The setup is fairly basic from what i'm being told. 2 application accelerators, and one central management device, nothing too tricky. We've opted to use WCCP redirection instead of inline mode.
All WAE's are registered to my CM, the problem i'm running into is at my remote site, after turning on WCCP redirection on my routers, all CIFS file shares stop working between sites. I have file servers at both locations, and after redirecting the traffic to my accelerator, I can no longer access file shares from my remote site to my central office, and vice versa.
The configs are very much default on the WAE's, everything is using automatic discovery, which I was assuming wouldn't cause any problems like this, and I admit that i'm not up to speed on the in's and out's of WAAS.
Any help is appreciated as always!
Thanks -
Jon

Sure:
The servers are Windows Server 2k3, no DFS here at all. These are dell SAN's that we use for storage.
I did see traffic hitting the WAE's, before I stopped redirecting traffic at my remote site, http / https, & domain services & exchange traffic were being optimzed. Basically what happens is after I start redirecting traffic to my remote site WAE's, file shares stop working, so I can't leave them running very long :).
I can post some of the config requests below, but since I'm no longer redirecting traffic to my WAE's, this is going to "skew" the results of the commands.
I did find a post in this forum that said I should upgrade my WAE's to 4.1.5(f), because an MS hotfix KB980232 possibly breaks CIFS accelerated connections. I'm working on downloading & upgrading my accelerators now & will let you know if this fixes my issue.
"We have seen the problems first hand and I would recommend against this patch if accelerating CIFS connections."
http://www.microsoft.com/technet/security/bulletin/MS10-020.mspx
Attached are the show commands you requested.
Thanks!
Jon

Urgent ! Router-WAAS WCCP problem

I have dot1q enabled 7507 connecting frame relay branch to data centre.
Core WAAS sits on a VLAN subinterface.
As soon as I enable "ip wcccp redirect 61 in" on VLAN trunked interface, I am loosing connection to the branch.
the config is here..
interface GigabitEthernet4/0/0
description Core Data Centre Trunk VLAN 3,120 to SWDC03 3/16
no ip address
no ip redirects
no ip unreachables
no ip proxy-arp
load-interval 30
negotiation auto
no cdp enable
interface GigabitEthernet4/0/0.3
description Core Data Centre VLAN
encap dot1q 3
ip address xxxx
ip wccp 61 redirect in
no ip redirects
no ip unreachables
no ip proxy-arp
ip nbar protocol-discovery
ip route-cache flow
no cdp enable
standby 3 ip 10.64.205.17
standby 3 priority 150
standby 3 preempt
interface GigabitEthernet4/0/0.120
description Core WAAS VLAN120
encap dot1q 120
ip address yyyyyyy
ip wccp redirect exclude in
no ip redirects
no ip unreachables
interface Serial0/0/3.64 point-to-point
ip wccp 62 redirect in
The IOS version is rsp-jsv-mz.123-17b and WAAS version 4.0.13.I have tested this before without VLAN trunking on another router using a seperate interface and it was working.Any idea ?
thanks

thanks guys. I will explain the problem a bit more.When WAAS sits on a seperate i/f on WAN router, it works fine. i.e "wccp redirect 61 in " on interface connecting WAN router to Data Centre and "wccp redirect 62 in" on WAN frame relay. Then I configured the i/f connecting WAN router to Data Centre as dot1q trunk and a dedicated VLAN is created for WAAS. The default gateway for WAAS is HSRP address in 6509s. The WCCP router address configured in WAAS is the loopback0 address of the WAN router. The "wccp redirect 62 in" on WAN frame relay stays same. However, " wccp redirect 61 in " carried to a new subinterface on the same access as WAAS VLAN.
All WCCP commands show that there is a connection between WAAS and WAN router, packet count goes up. However, all TCP sessions to the brach (initiated from the Data Centre) fail. I have also tested with and without "wccp redirect exclude in" on WAAS VLAN subinterface without success. Since I had to install the branch the WAAS on the weekend, I moved WAAS back to dedicated interface on WAN router. It works fine but I can not implement redundancy.
The suggestion was to make WAN router subinterface HSRP active rather than 6509 MSFCs.So WAAS talks to WAN routers loopback address and default gateway also points to the same router rather than MSFC. I have not had a chance to test this but I will test in the coming weeks. I was also suggested to use layer2 redirection on 6509 but did not have any chance to look at it closely.
thanks
Serhat

Skype on WAAS and FWSM problem

The customer network has two kind of situations, behind the FWSM or not.Skype already normally operated under these two kind of network construction.When WAAS disposition,behind FWSM's client to use skype , it has very heavy detention even connection error.Another network does not have the FWSM's client to be possible at the same time to use Skype normally as before.
I use wireshack to sniffer the packet.Skype behind FWSM will use tcp to replace udp.WAAS will intercept tcp and causes voice to create the detention .
I set client's skype software setting to use 14676 port for connection and disable 80/443 as substitution.And I make classifier on WAAS to pass-through the port 14676 and 443. I see the transaction-logs on WAAS,some APP CFG bypass can see,but some not.
I sniffer client again.Skype behind FWSM use 443 port and 14676 or other random port to connection.When skype use 443 or 14676 port,he can use happyly,but when skype random other port,it fail again.
How should I solve this problem ,WAAS cannot bypass Skype voice traffic.

Ivan,
Are all of the necessary ports open on the FWSM? Does Skype work when FWSM is removed? WAAS is not doing anything specific to Skype traffic, it is just being handled at the TCP layer. If possible, a packet capture from the client and WAEs may help point us down the right path.
Zach

WAAS 4.1.1.c problems

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.

performed as suggested:
sho run
wccp tcp-promiscuous router-list-num 8 l2-redirect assign-method-strict
wccp version 2
#sho wccp routers
Router Information for Service: TCP Promiscuous 61
Routers Seeing this Wide Area Engine(0)
-NONE-
Routers not Seeing this Wide Area Engine
1.1.9.251
Routers Notified of from other WAE's
-NONE-
Multicast Addresses Configured
-NONE-
performed 'sho ip wccp 61 det' on router:
WCCP Client information:
WCCP Client ID: 1.1.9.101
Protocol Version: 2.0
State: NOT Usable
Initial Hash Info: 00000000000000000000000000000000
00000000000000000000000000000000
Assigned Hash Info: 00000000000000000000000000000000
00000000000000000000000000000000
Hash Allotment: 0 (0.00%)
Packets s/w Redirected: 0
Connect Time: 00:00:20
Bypassed Packets
Process: 0
Fast: 0
CEF: 0
Errors: 0
Note 'State: NOT Usable'
I've bounced router. Removed WCCP from router, added it back in, no change in WCCP state.

WAAS cluster problem when WAAS reload

Hello,
I have a datacentre with a 2 * 6500 and a WAAS cluster. When the WAAS are reloaded in the datacentre, I have a lot of applications problem. We need to turn off wccp on the switches and turn on wccp again to have applications work again. Would anybody know why and provide a link to cisco website which could explain this issue?
Thanks

Hi,
it's difficult to point you to the right direction without knowing more details about the problem. I suggest to check the following:
- what are the applications impacted? (all the apps / specific ones)
- only some sources/destinations or all the traffic?
- are the apps slow or simply not working?
- does the problem happen when reloading both central WAE's or just one of them?
after you narrowed down the issue, you might want to look into a specific area to troubleshoot on. Here you have a good starting point:
http://docwiki.cisco.com/wiki/Cisco_WAAS_Troubleshooting_Guide_for_Release_4.1.3_and_Later
You might want to look into the "Troubleshooting WCCP" section of that document.
Depending on your findings you might also need to grab sys-reports from the WAE's involved and tcpdump on core/edge location.
hope this helps,
Fabrizio

WAAS report problem

hi...
i have a problem with my waas NME WAE302
there is no data traffic in the report.
i still can ping and telnet to my waas, please help me what i have to do.

this is an example from cli : show statistics application :
Email-and-Messaging
Opt TCP Plus:
Bytes 358404161 356242072
Packets 950713 924082
Orig TCP Plus:
Bytes 469316526 1096436713
Packets 1005181 1221799
Opt Preposition:
Bytes 0 0
Packets 0 0
Orig Preposition:
Bytes 0 0
Packets 0 0
Opt TCP Only:
Bytes 56575705 13229371
Packets 65943 56822
Orig TCP Only:
Bytes 11524146 48232552
Packets 48284 65187
Internal Client:
Bytes 0 0
Packets 0 0
Internal Server:
Bytes 0 0
Packets 0 0
PT Client:
Bytes 694966
Packets 3511
PT Server:
Bytes 210670
Packets 3097
Active Completed
Opt TCP Plus 0 1736
Preposition 0 0
Opt TCP Only 1 291
Internal Client 0 0
Internal Server 0 0
PT No Peer 0 1062
PT Config 0 0
PT Intermediate 0 0
PT_Other 0 58

Waas - ftp - checksum problem

Hi,
I've a server configured for http and ftp services in DC. HTTP service is working correctly but ftp not. On wae there is a session for ftp traffic but for customer there is no any result. In branch there is PBR and in DC - wccp. I noticed by server side "tcp checksum error", but I cannot find out why only for ftp? I've branches for which there is no problem at all. Configuration is the same for all branches (PBR). Other issue is that in the same connection (branch-DC) there is lotus optymalization and http on others servers working well in production.
I've 4.1.1c.16 version.
any idea?
Thanks

ACE can perform deep packet inspection on HTTP, FTP, DNS, ICMP, and RTSP traffic. Inspections include port 80 misuse, RFC compliance, content/header/URL checksum, FTP reply spoofing, and many others. ACE can also analyze traffic for malformed packets and take corrective action. In a ACE load balanced WAAS context, ACE is in the optimization path, so these deep packet inspections cannot be performed. ACE contexts outside the optimization path can be configured with the deep packet inspection.

A problem with RDP when WAEs was connected to the network

The customer has a problem with RDP sessions on one Microsoft cluster server. The problem started when the WAEs (management and acceleration WAEs) are connected to a network (where a cluster is connected). Did anybody have the similar problem? The sessions are connected, but after some different times these sessions are frozen. This problem is only with this Microsoft cluster, the RDP on other servers are good. The WAAS is 4.0.17b14.

Hi,
I have the same problem as I write. RDP seems to get slower when I connect the WAEs and the login timesout before the user can type the username and password.
I have ensured that "EPM Classification" is disbled.
Check and see if Term-services are well configured on the TS server side. Maybe some config is conflicting with WAAS TS optimization.
What happens when you set TS to passthrough?
Also try this for your case;
" HOW-TO: Configuring RDP and Terminal Services for Full WAAS Optimization
Microsoft RDP and Terminal Services are, by default, compressed and encrypted. As such, the default Cisco WAAS policy for these applications is to apply TCP optimizations only. RDP and Terminal Services can be configured to allow Cisco WAAS to provide full optimization (DRE, LZ, TFO) which is a 2X-10X improvement over native WAN and 2X-3X improvement over the compression provided by Microsoft.
Configuring Microsoft RDP and Terminal Services to support Cisco WAAS full optimization requires a change to the client and a change to the server.
On the client, disable compression by editing the .RDP file for the connection using Notepad or a similar text editor. Identify a line in the file that shows "compression:i:1". Modify this line to say "compression:i:0". This disables compression for the RDP/TS connection.
On the server, open the Terminal Services Configuration found under Start > Programs > Administrative Tools. From here, expand Terminal Services Configuration to Connections. Double-click the "RDP-Tcp" entry found in the workspace. Change the encryption level to "Low", which specifies that only login will be encrypted. Then, click "Ok" and close Terminal Services Configuration.
Then, modify the Cisco WAAS policy on the configured device group (or explicitly on each of the WAEs) called "MS-Terminal-Services". Set this policy to "Optimize Full". "
Anyone out there with a clue why RDP gets disconnected?

WAAS Problem

Similar Messages

Maybe you are looking for