WebScale™
User's Guide
clicking the Class C button instead of the Single button. This feature ensures that
clients which use multiple proxy servers to access the cluster will have their TCP
connections directed to the same cluster host. The use of multiple proxy servers at the
client's site causes requests from a single client to appear to originate from different
systems. Assuming that all of the client's proxy servers are located within the same
Class C address range, clicking the Class C button ensures that client sessions are
properly handled. If you do not need this capability, click the Single button instead to
maximize scaled performance when using client affinity.
Affinity: Class C
The Class C button specifies that WebScale should direct multiple requests from the
same TCP/IP Class C address range to the same cluster host.
Enabling client affinity ensures that only one cluster host handles all connections that
are part of the same client session. This property is important if the server application
running on the cluster host maintains session state (such as "server cookies") between
connections. However, disabling client affinity improves performance because it allows
multiple connections from the same client to be simultaneously handled by different
cluster hosts. To maximize scaled performance, disable client affinity (by clicking the
None button) when it is not needed.
Clicking the Class C button instead of the Single button ensures that clients which use
multiple proxy servers to access the cluster will have their TCP connections directed to
the same cluster host. The use of multiple proxy servers at the client's site causes
requests from a single client to appear to originate from different systems. Assuming
that all of the client's proxy servers are located within the same Class C address range,
this type of client affinity ensures that client sessions are properly handled. If you do
not need this capability, click the Single button instead to maximize scaled performance
when using client affinity.
Load Percentage
When using multiple hosts filtering mode, this parameter specifies the percentage of
load balanced network traffic that this host should handle for the associated port rule.
Allowed values range from 0 to 100. To prevent a host from handling any network
traffic, set the load percentage to 0.
The sum of the load percentages for all cluster hosts does not have to equal 100 since
hosts may dynamically enter or leave the cluster. The actual fraction of traffic handled
by each host will be computed as the local load percentage value divided by the sum of
all load percentages across the cluster.
You can specify that all hosts distribute the network load equally by using the Equal
parameter instead of the load percentage.
34
Need help?
Do you have a question about the WebScale and is the answer not in the manual?