KEMP Technologies LoadMaster 1500 Installation And Configuration Manual page 53

This command specifies which type of connection persistence should be used for a Virtual Service. In no
persistency should be specified for the Virtual Service, the command <no persist> should be specified. The
following persistency types can be specified. If the L7 option has not been enabled, only the <src> persistency
is allowed.
ssl
cookie
active-cookie
url
host
src
cookie- src
active- cook-src
cookie- hash
6.13. Port <Port spec>
Specifies the IP port to be used for the Virtual Service. If no health check mechanism has been specified and
the port is a well-known port, the relevant health check mechanism will be selected.
6.14. Precedence <rule-name> <number>
The precedence of the rule <rule-name> is set to <number>. A value of 1 moves the rule to the start of the
rule list. I.e. this rule is checked first. A higher value moves the rule to the respective position in the rule. If a
<default> rule is specified for a Real Server, its precedence will always be lower than any user defined rules.
I.e. a <default> rule will always be checked after every other rule.
6.15. Protocol <tcp/udp>
Protocol to be used for the Virtual Service. This may be <tcp> or <udp>. By default the protocol will be set to
<tcp>.
6.16. Ptimeout <Integer>
Specifies how long the LoadMaster should remember the persistency information associated with a connection.
This value is specified in seconds.
6.17. Schedule <schedule method>
This allows the scheduling method between the Real Servers to be specified.
The following scheduling methods may be specified:
rr round robin (default).
wrr weighted round robin.
lc least connection.
llc weighted least connection.
6.18. Server <IPspec>
This command enters the Real Server command level for the specified Real Server.
The Real Server must already be assigned to the Virtual Service.
6.19. Show
Displays all the parameters of the current Virtual Service.
Copyright © 2000 - 2005 KEMP Technologies, Inc. All Rights Reserved.
The Session ID in an SSL connection is used to maintain client to real server
persistency.
Server generated cookies will be used.
LoadMaster generated cookies will be used.
A request for a specific URL will always go to the same real server.
A request to the same virtual host will go to the same real server.
Enables IP based persistency.
Server generated cookies will be used. If the client does not return a cookie, the
clients' IP address will be used.
A LoadMaster generated cookie will be used. If the client does not return the cookie,
the clients' IP address will be used.
All connections with the same set of cookies will always be sent to the same real
server. If no cookies are sent, normal scheduling will occur.
53