Specifications

Configuring LSNAT
September 8, 2010 Page 12 of 28
•WhendifferentVIPsaccessthesamerealserverindifferentserverfarms,thepersistencelevel
mustbesetthesame.
Inordertousestickiness,thefollowingconfigurationcriteriaarerequired:
•Stickinessmustbeconfiguredforthevirtualserver.
•Therealserversinthisserverfarmaretobeusedforall
services.Theserversarenotallowed
tobeusedwithotherserverfarmstosupportothervirtualserverservices.Thereisone
exceptiontothisrule,describedinthenextbulletitem.
•StickinessmeansallTCPportsorallUDPportsonthevirtualserveraresupported,butnot
both.You
cancreatetwovirtualserverswitheitherthesameIPaddressanddifferentports,or
differentIPaddresses(oneforTCPprotocols/portsandoneforUDPprotocols/ports)anduse
thesamerealservers(withdifferentserverfarmnames).ThatwayallTCPandUDPportsare
supportedbythesameset
ofrealservers.
•Port0inthevirtualserverhastobeusedtosupportthisserviceandisreservedforthis
purpose.
Configuring an LSNAT Server Farm
Procedure 1describeshowtoconfigureanLSNATserverfarm.
Configuring an LSNAT Real Server
Procedure 2describeshowtoconfigureanLSNATrealserver.
Procedure 1 LSNAT Server Farm Configuration
Step Task Command(s)
1. In global router configuration command mode,
specify a name for this server farm.
ip slb serverfarm serverfarmname
2. In SLB server farm configuration command
mode, specify the load balancing algorithm for
this server farm.
predictor [roundrobin | leastconns]
3. In SLB server farm configuration command
mode, enable the this server farm. The default
setting for server farms is inservice.
inservice
Procedure 2 Configuring an LSNAT Real Server
Step Task Command(s)
1. In SLB server farm configuration command
mode, configure the real server members for this
server farm and enter real server configuration
command mode.
real ip-address [port number]
2. In SLB real server configuration command
mode, optionally configure the error handling on
this real server.
faildetect {type {both | ping | app [tcp | udp]
| acv [tcp | udp] | none}} | ping-int seconds
ping-retries number | app-int seconds
app-retries number