several questions regarding waas inline mode.

[syjeon]

hi. all.

we have two cisco waas, one is wae-274 and another device is wae-474. and two devices has inline network card.

however, wae-274 supports only 2M wan connection speed, so if traffic is exceed, some application can not take application acceleration.

cisco wae inline card default accepts all traffic. according the configuration document, if the network interface has trunk interface,

only filter vlan which is needed traffic acceleration.

however, in our topology, there is no trunk interface between wan router and cisco switch, and it is hard to change trunk interface at this time.

wccp is too hard to deploy at this time. so we have to archive this project as inline mode on cisco waas.

except filter vlan on cisco waas, is there any other way to pass the traffic which we need to make acceleration on cisco waas.?

any idea on cisco centeral manager? for example access-list on cisco waas to accpet traffic only we needed.

there is our major concern, we are looking for many consultant and searching the document.

help us.

[Bhavin Yadav]

Hello,

Yes, there is a way to bypass the traffic that you do not want to optimize.

Please create a policy on WAE where you have this bandwidth issue.

Let's say you have VLAN100, VLAN200......VLAN800 going thru WAE in inline mode and you only want to optimzie VLAN 100 traffic.  Please create a policy like this one on CM and push it to this site's WAE.

The policy should read like this:

Type: Basic

Application: Other

Application Classifier: Click on New Classifier, put in name - PassThru for ...., create two conditions, revers of each other. in first condition, put in VLAN200 as source and in second condition put VLAN200 as destination. Please use subnet mask, (Please note that subnet mask is to be put in as wildcard mask i.e. for /24, put in 0.0.0.255). Repeat the process for creating conditions for the rest of the VLANs.

Now hit submit and you will be back to Applciation Policy Page.

Select Action: Pass Through

Select Accelerate : Do not Set

Position : First

Enabled : enabled (checked).

Please make sure to put in the pass thru policies at the top of the page.

This will bypass the traffic for policies created. Because we are using reverse conditions, creating these conditions on one side of WAE should suffice. There is no need to create these policies on the other side (data centre).

If you are still hitting the bandwidth issue, you may want to make sure that traffic being optimized is not eating up whole lot of bandwidth. You can verify this fro mCM by going to My WAN -> Devices -> Edit device -> Monitor -> Optimization -> Optimization Summary report and click on Throughput tab.

Hope this helps.

Regards.

PS: Please mark this question as Answered, if this resolves your issue.

[Bhavin Yadav]

BTW, you can also create Static bypass list for WAEs.

Here is the method:

To centrally configure a static bypass list for a WAE (or group of WAEs), follow these steps:

From the WAAS Central Manager GUI navigation pane, choose My WAN > Manage Devices (or Manage Device Groups).
Click the Edit icon next to the name of the device (or device group) for which you want to create a static  bypass list.
From the navigation pane, choose Configure > Interception > Bypass Lists.
In the taskbar, click the Create New WCCP/Inline Bypass List icon. The Creating new WCCP/Inline  Bypass List window appears.
Enter the IP address for the client in the Client Address field.
Enter the IP address for the server in the Server Address field.
Check Submit to save the settings.

to make sure the traffic is in pass thru, please use cli command : sh stat conn | in and it should show up as PT App Cfg.

[Michael Korenbaum]

Hi,

As mentioned in your other thread, use the Interception ACL feature to permit only interesting traffic to be intercepted by the policy engine on the inline WAVE.

http://www.cisco.com/en/US/partner/docs/app_ntwk_services/waas/waas/v431/configuration/guide/traffic.html#wpxref37095

WAAS does not impose any software limitation on the WAN bandwidth, there is however a limit on the number of concurrent TCP sessions that can be optimized.

Here is a note from our sizing guide about WAN bandwidth.

WAN bandwidth is not limited in software or by any other system limit; rather it is provided as guidance for deployment sizing purposes and is based on possible WAN usage using multiple TCP connections. WAN link utilization will be determined by compression ratio and client/server behavior.

As per the sizing guide a 274 can handle up to 200 concurrent optimized TCP sessions.  If this number is reached the WAVE will go into TFO overload mode and all subsequent TCP connections will be placed into pass through (not optimized).  Once some of the optimized flows are closed by the client/server, the WAVE will exit TFO overload and will optimize new TCP sessions.

Regards,

Mike Korenbaum

Cisco WAAS PDI Help Desk

http://www.cisco.com/go/pdihelpdesk