We are actually planning a large scale WAAS solution. We found many descriptions how the WCCP flows is protected in redundant design against a WAE failure. We learnt that the Lead WAE is necessary to redirect the WCCP flow to the remaining WAEs. Our question is what will happen when the Lead WAE fails. How will the WAE farm recover the WCCP flows.
The lead WAE is responsible for instructing all of the WCCP-enabled routers/switches how traffic should be distributed across the cluster of WAE devices. It does this by communictaing an assignment table of buckets/masks. The lead WAE does not actually handle the flows, they are redirected directly from the router/switch to the target WAE.
In the event that the lead WAE fails, another WAE in the service group takes over the lead role and updates the assignment for all of the routers/switches.
thanks for your quick response. The answer clearifies the role of the Lead WAE. But one issue is still not clear for me. When the new Lead WAE takes over will the buckets be assigned as before or may active flows switch from one WAE to another.
Whenever there is a change in the service group membership, there is no guarantee that the buckets will be reassigned the same way. However, in the event that they aren't, the WCCP Flow Protection feature will ensure that the WAE that was originally handling the flow will receive it.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...