Configure advanced settings
Steps
-
Use Assignment Method to specify the parameters used to distribute intercepted traffic among multiple nodes in a cluster. For a description of the WCCP load
distribution feature, see WCCP load distribution.
HASH applies a hash operation to the selected distribution attributes.
- With HASH, more than one distribution attribute can be selected.
- The result of the hash operation determines the cluster member that receives the traffic.
MASK applies a mask operation to the selected distribution attribute.
- Only one distribution attribute can be selected, typically the destination IP address.
- The result of the mask operation determines the cluster member that receives the traffic.
- The following distribution attributes can be selected:
- Destination IP address
- Destination Port
- Source IP address
- Source Port
The MASK value is applied up to 6 significant bits (in a cluster, a total of 64 buckets are created). See your WCCP documentation for more information about assignment method HASH and MASK operations. Use the value recommended in the manufacturer’s documentation for your device.
-
For proportional load distribution, specify a weight value from 0-255. The value determines the proportional distribution of load among servers in a cluster.
Weight is only useful when Synchronize in the Cluster is disabled.
- All cluster members have a value of 0 by default, which results in a balanced distribution of traffic.
- If weight is set to 1 or higher, the value guides proportional distribution among the nodes.
For example, if there are 3 nodes in a cluster and Proxy1 has a weight of 20, Proxy2 has a weight of 10, and Proxy3 has a weight of 10, Proxy1 will get one half of the traffic, Proxy2 will get one-quarter of the traffic, and Proxy3 will get one-quarter of the traffic.
Important: When the value of weight is greater than 0 on any member of the cluster, any member of the cluster with a weight of 0 receives no traffic. If you plan to use weight, be sure to set a weight on every member of the cluster.For more information about load distribution, see WCCP load distribution.
-
Specify a Reverse Service Group ID for IP spoofing.
When IP spoofing is enabled, you must define a reverse service group for each HTTP and HTTPS forward service group.
Note: Only HTTP and HTTPS are supported for IP Spoofing.Using the specified ID, Content Gateway creates a reverse service group that is a mirror of the forward service group. For example, if the forward service group has assignment method based on destination IP address, the reverse service has an assignment method based on the source IP address.
Note: IP spoofing is not supported with service groups that use a hashing assignment method with both destination and source attributes. If IP spoofing is enabled on such a service group, an alarm is raised and IP spoofing is disabled.