appliances in a WCCP cluster has the following limitations:
All appliances within a
cluster must be the same model and use the same software release.
between appliances within the cluster is not automatic. Use Command Center to
manage the appliances as a group.
CloudBridge traffic shaping
is not effective, because it relies on controlling the entire link as a unit,
and none of the appliances are in a position to do this. Router QoS can be used
load-balancing algorithms do not vary dynamically with load, so achieving a
good load balance can require some tuning.
The hash method of cache
assignment is not supported. Mask assignment is the supported method.
While the WCCP standard
allows mask lengths of 1-7 bits, the appliance supports masks of 1-6 bits.
Multicast service groups
are not supported; only unicast service groups are supported.
All routers using the same
service group pair must support the same forwarding method (GRE or L2).
The forwarding and return
method negotiated with the router must match: both must be GRE or both must be
L2. Some routers do not support L2 in both directions, resulting in an error of
"Router's forward or return or assignment capability mismatch." In this case,
the service group must be configured as GRE.
CloudBridge VPX does not
support WCCP clustering.
The appliance supports (and
negotiates) only unweighted (equal) cache assignments. Weighted assignments are
Some older appliances, such
as the CloudBridge 700, do not support WCCP clustering.
only) Two accelerator instances are required per interface in L2 mode. No more
than three interfaces are supported per appliance (and then only on appliances
with six or more accelerator instances.)
only) WCCP control packets from the router must match one of the router IP
addresses configured on the appliance for the service group. In practice, the
router's IP address for the interface that connects it to the appliance should
be used. The router's loopback IP should not be used.