WCCP Interception
WCCP interception, WCCP GRE or WCCP L2, is supported for all vWAAS on Hyper-V deployments.
To select WCCP as the interception method for a WAE, follow these overview steps. For a full description of each step, see the Cisco Wide Area Application Services Configuration Guide.
Note Before you do the following procedure, you should have already configured your router for basic WCCP, as described in the Cisco Wide Area Application Services Configuration Guide.
Step 1 From the WAAS Central Manager menu, choose Devices > device-name.
Step 2 Choose Configure > Interception > Interception Configuration. The Interception Configuration window appears.
Interception Method Settings area
Step 3 From the Interception Method drop-down list, choose WCCP to enable the WCCP interception on the vWAAS device.
WCCP Settings area
Step 4 To enable WCCP on the device, check the Enable WCCP Service check box.
Step 5 With WCCP selected, the Service Type field displays TCP Promiscuous.
Step 6 In the Service ID1 field, specify the first service ID of the WCCP service pair, with an ID number of 1 to 99. After you submit, the Service ID2 field is filled in with the second service ID of the pair, which is one greater than Service ID1, with an ID number of 2 to 100.
Step 7 To use the default gateway of the WAE as the router to associate with the WCCP TCP promiscuous service, check the Use Default Gateway as WCCP Router check box.
If you leave this box unchecked, you can use the WCCP Routers field to specify a list of one or more routers by their IP addresses, separated by spaces.
WCCP Assignment Settings for Load Balancing area
Step 8 (Optional) From the Assignment Method drop-down list, choose the type of WAE load-balancing assignment method to use (Mask or Hash).
- Mask assignment method selected—To use a custom mask, enter a value for the source ID mask in the Source IP Mask field. The range, in hexadecimal, is 00000000–FE000000. The default is F00. Enter a value for the destination IP mask in the Destination IP Mask field. The range, in hexadecimal, is 0000000–FE000000. The default is 0.
- Hash assignment method selected—To specify the hash assignment method for the source IP address, check Hash on Source IP: either Service ID1 or Service ID2. After you check a source IP, the complementary destinantion IP is automatically selected, Hash on Destination IP: check box either Service ID2 or Service ID1.
WCCP Redirect and Egress Settings area
Step 9 From the Redirect Method drop-down list, choose WCCP GRE or WCCP L2.
Step 10 From the Egress Method drop-down list, choose L2 or IP Forwarding.
Advanced WCCP Settings area
Step 11 Check the Enable Flow Protection check box to keep the TCP flow intact and to avoid overwhelming the device when it comes up or is reassigned new traffic. For more information on flow redirection, see the Information about WCCP Flow Redirection on WAEs” section of the Cisco Wide Area Application Services Configuration Guide.
Step 12 In the Flow Protection Timeout field, specify the amount of time (in seconds) that flow protection should be enabled. The default is 0, which means flow protection stays enabled with no timeout.
Step 13 In the Shutdown Delay field, enter a maximum amount of time (in seconds) that the chosen device waits to perform a clean shutdown of WCCP. The range is 0 to 86400 seconds. The default is 120 seconds.
Step 14 From the Failure Detection Timeout drop-down list, choose a failure detection timeout value: 30, 15, or 9 seconds. The default is 30 seconds. The failure detection timeout determines the length of time for the router to detect a WAE failure.
Step 15 In the Weight field, specify the weight to be used for load balancing. The weight value range is 0 to 10000.
- If the total of all the weight values of the WAEs in a service group is less than or equal to 100, the weight value represents a literal percentage of the total load redirected to the device for load-balancing purposes.
- If the total of all the weight values of the WAEs in a service group is between 101 and 10000, the weight value is treated as a fraction of the total weight of all the active WAEs in the service group.
Step 16 In the Password field, specify the password to be used for secure traffic between the WAEs within a cluster and the router for a specified service. Be sure to enable all other WAEs and routers within the cluster with the same password. Passwords must not exceed eight characters in length. Do not use the following characters: space, backwards single quote (‘), double quote (“”), pipe (|), or question mark (?).
Re-enter the password in the Confirm Password field.
Step 17 Click Submit to save the settings.
AppNav Controller Interception
AppNav interception is supported for all vWAAS on Hyper-V deployments, and works as in the current ESXi vWAAS models.
AppNav interception enables a vWAAS node to receive traffic optimization from an AppNav controller (ANC) in an AppNav deployment. If vWAAS VMs are part of an AppNav deployment and are configured as WAAS nodes (WNs) in an AppNav cluster, you must configure the AppNav-controller interception method. These WNs receive traffic only from the ANCs; they do not receive traffic directly from routers.
To select AppNav as the interception method, follow these steps:
Step 1 From the WAAS Central Manager menu, choose Devices > device-name.
Step 2 Choose Configure > Interception > Interception Configuration. The Interception Configuration window appears.
Step 3 From the Interception Method drop-down list, choose appnav-controller to enable appnav-controller interception on hte vWAAS device.
Step 4 Click Submit.