Cisco Wide Area Virtualization Engine 274 Troubleshooting Guide download pdf (Page 64)

1-20

Cisco Wide Area Application Services Configuration Guide

OL-26579-01

Chapter 1 Planning Your WAAS Network

Supported Methods of Traffic Redirection

You can serially cluster WAE devices (not AppNav Controllers) in inline mode to provide higher

availability in the event of a device failure. If the current optimizing device fails, the second WAE device

in the cluster provides the optimization services. Deploying WAE devices in a serial inline cluster for

the purposes of scaling or load balancing is not supported.

Any combination of traffic interception mechanisms on peer WAEs is supported. For example, you can

use inline interception on the branch WAE and WCCP on the data center WAE. For complex data center

deployments, we recommend that you use hardware-accelerated WCCP interception or load balancing

with the Cisco Application Control Engine (ACE) and a WAAS AppNav deployment.

For more information on inline interception, see the “Using Inline Mode Interception” section on

page 1-42.

Three elements can help ease traffic interception in data centers without using a WCCP-based approach:

• Multiple pairs of inline interfaces are available on certain WAE models:

–

WAVE-294/594/694/7541/7571/8541 models support one installed Cisco Interface Module,

which can be configured with up to 16 inline ports in 8 inline groups, or one installed AppNav

Controller Interface Module, which can be configured with up to 12 inline ports in 5 bridge

groups.

–

WAE-674/7341/7371 models support dual inline Cisco WAE Inline Network Adapters,

providing a total of 8 ports in 4 inline groups.

• Serial inline clustering of two WAEs (not AppNav Controllers) to support high availability.

• Interception ACLs to control what traffic is intercepted and what is passed through. For more

information on interception ACLs, see the “Configuring Interception Access Control Lists” section

on page 1-28.

Advantages and Disadvantages of Using WCCP-Based Routing

WCCP specifies interactions between one or more routers (or Layer 3 switches) and one or more

application appliances, web caches, and caches of other application protocols. The purpose of the

interaction is to establish and maintain the transparent redirection of selected types of traffic flowing

through a group of routers. The selected traffic is redirected to a group of appliances.

WCCP allows you to transparently redirect client requests to a WAE for processing. The WAAS software

supports transparent intercept of all TCP traffic.

To configure basic WCCP, you must enable the WCCP Version 2 service on the router and WAE or ANC

in the data center and the router and WAE in the branch office. You do not need to configure all of the

available WCCP features or services in order to get a WAE up and running.

Note You must configure the routers and WAEs to use WCCP Version 2 instead of WCCP Version 1 because

WCCP Version 1 only supports web traffic (port 80).

WCCP is much simpler to configure than PBR. However, you need to have write access to the router in

order to configure WCCP on the router, which typically resides in the data center and on the edge of the

branch office. Another advantage of using WCCP is that you only need to perform a basic configuration

of WCCP on your routers and WAEs in order to get your WAE up and running.

The WCCP Version 2 protocol also has a set of useful features built-in, for example, automatic failover

and load balancing between multiple devices. The WCCP-enabled router monitors the liveliness of each

WAE or ANC that is attached to it through the WCCP keepalive messages. If a WAE goes down, the

1 ... 63 64 65 ... 594

Comments to this Manuals

No comments

Cisco Wide Area Virtualization Engine 274 Troubleshooting Guide Page 64

Comments to this Manuals

Related products and manuals for Networking Cisco Wide Area Virtualization Engine 274