1. /cfg/slb/group <group number>/metric hash
a. For Application Redirection, the client destination IP address is
used. All requests for a
specific IP destination address will be sent to the same server. This
is particularly useful
for maximizing successful cache hits.
b. For SLB, the client source IP address is used. All requests from a
specific client will be
sent to the same server. This option is useful for applications where
client information
must be retained between sessions.
2. /cfg/slb/filt <filter number>/adv/thash
Allows you to choose hash parameter to use for filter redirection.
The Default is auto. The sip
option allows you to perform tunable hash on source IP address for this
filter. The option dip
allows you to perform tunable hash on destination IP address for this
filter. The option both
allows you to perform tunable hash on both source IP address and the
destination IP address at the same time. The option sip+sport allows
you to perform tunable hash on both source IP address and source port
at the same time.
So, Alteon uses source IP to calculate each session and redirects it to
a real server. We can't know which sever will be assigned by Alteon on
the first session from a client but can control every session from the
same 24-bit source IP address will be redirected to the same real
server as the first session.
Alteon always keeps source IP of every packets unless you enable proxy
IP function or NAT. No matter what metric you choose, Alteon never
changes the source IP of every packets. It only uses source IP,
destination IP, or source port to make a load balance or redirecting
decision.
Yes, in your case, Alteon uses source IP to make and maintain a session
table to keep load balance function properly.