Specifications

3-216
Cisco Wide Area Application Services Command Reference
OL-11817-01
Chapter 3 CLI Commands
show wccp
Connections bypassed due to load Number of connection flows that are bypassed when the WAE is
overloaded. When the overload bypass option is enabled, the
WAE bypasses a bucket and reroutes the overload traffic. If the
load remains too high, another bucket is bypassed, and so on, until
the WAE can handle the load.
Packets sent back to router Number of requests that are passed back by the WAE to the
WCCP-enabled router from which the request was received. The
router then sends the flow toward the origin web server directly
from the web browser, which bypasses the WAE.
Packets sent to another WAE Number of packets that are redirected to another WAE in the
WCCP service group. Service groups consist of up to 32
WA Es
and 32 WCCP-enabled routers. In both packet-forwarding
methods, the hash parameters specify how redirected traffic
should be load balanced among the WAEs in the various WCCP
service groups.
GRE fragments redirected Number of GRE packets received by the WAE that are
fragmented. These packets are redirected back to the router.
GRE encapsulated fragments
received
Number of GRE encapsulated fragments received by the WAE.
The tcp-promiscuous service does not inspect port information
and therefore the router or switch may GRE encapsulate IP
fragments and redirect them to the WAE. These fragments are
then reassembled into packets before being processed.
Packets failed encapsulated
reassembly
Number of reassembled GRE encapsulated packets that were
dropped because they failed the reassembly sanity check.
Reassembled GRE encapsulated packets are composed of two or
more GRE encapsulated fragments. This field is related to the
previous statistic.
Packets failed GRE encapsulation Number of GRE packets that are dropped by the WAE because
they could not be redirected due to problems while encapsulating
the packet with a GRE header.
Packets dropped due to invalid
fwd method
Number of GRE packets that are dropped by the WAE because it
was redirected using GRE but the WCCP service was configured
for Layer 2 redirection.
Packets dropped due to
insufficient memory
Number of GRE packets that are dropped by the WAE due to the
failure to allocate additional memory resources required to handle
the GRE packet.
Packets bypassed, no conn at all Number of packets that failed to be associated with an existing
flow because no TCP port was listening. WCCP can also handle
asymmetric packet flows and always maintains a consistent
mapping of web servers to caches regardless of the number of
switches or routers used in a WCCP service group (up to 32
routers or switches communicating with up to 32 WAEs in a
cluster).
Packets bypassed, no pending
connection
Number of packets that failed to be associated with a pending
connection because the initial handshake was not completed.
Table 3-88 Field Descriptions for the show wccp gre Command (continued)
Field Description