Troubleshooting guide

1-44
Cisco Wide Area Application Services Configuration Guide
OL-26579-01
Chapter 1 Configuring Traffic Interception
Using Inline Mode Interception
• WAE-674/7341/7371—Support up to two installed four-port Cisco WAE Inline Network Adapters,
providing a total of eight inline ports.
• WAVE-294—Supports one installed Cisco Interface Module with 2, 4, or 8 ports.
• WAVE-594/694/7541/7571/8541—Support one installed Cisco Interface Module with 2, 4, or 8
ports or a Cisco AppNav Controller Interface Module with 4 or 12 ports.
Note The two-port 10-Gigabit Cisco Interface Module cannot be used in inline mode. The four-port
10-Gigabit Cisco AppNav Controller Interface Module is supported only on the WAVE-594.
You have the option of assigning an IP address to an inline interface, but it is not required. For more
information, see the “Configuring an IP Address on an Inline Interface” section on page 1-51.
Traffic that flows through an inline group is transparently intercepted for optimization. Traffic that does
not need to be optimized is bridged across the LAN/WAN interfaces. If a power, hardware, or
unrecoverable software failure occurs, the network adapter automatically begins operating in bypass
mode (fail-close), where all traffic is mechanically bridged between the LAN and WAN interfaces in
each group. The Cisco WAE Inline Network Adapter and Cisco Interface Module also operate in bypass
mode when the WAE is powered off or starting up. Additionally, you can manually put an inline group
into bypass mode.
Note AppNav Controller Interface Modules do not support automatic bypass mode to continue traffic flow in
the event of a failure. For high availability, two or more AppNav Controller Interface Modules should
be deployed in an AppNav cluster. For more information on using inline mode with the AppNav solution,
see Chapter 1, “Configuring AppNav.”
Inline mode is configured by default to accept all TCP traffic. If the network segment in which the WAE
is inserted is carrying 802.1Q tagged (VLAN) traffic, initially traffic on all VLANs is accepted. Inline
interception can be enabled or disabled for each VLAN. However, optimization policies cannot be
customized based on the VLAN.
You can serially cluster WAE devices operating in inline mode to provide higher availability if a device
fails. For details, see the “Information About Clustering Inline WAEs” section on page 1-53.
Note When a WAE inline group enters bypass mode, the switch and router ports to which it is connected may have
to reinitialize, which may cause an interruption of several seconds in the traffic flow through the WAE.
If the WAE is deployed in a configuration where the creation of a loop is not possible (that is, if it is
deployed in a standard fashion between a switch and a router), configure PortFast on the switch port to
which the WAE is connected. PortFast allows the port to skip the first few stages of the Spanning Tree
Algorithm (STA) and move more quickly into a packet forwarding mode.
Enabling Inline Operation on WAEs
This section describes how to enable and configure inline settings on WAEs configured as application
accelerators and that are not part of an AppNav Cluster (WAEs that are part of an AppNav Cluster use
only the appnav-controller interception method). If you want to configure the inline settings on WAEs
configured as AppNav Controllers, see the “Configuring Inline Operation on ANCs” section on
page 1-49.