Citrix ByteMobile T1010, Installation, Configuration And Administration

Page: 93 / 172

T-Series Traffic Director Installation, Configuration and Administration Guide 3-19
Configuring T1000 Load Balancing
Creating Services
After the load balancing feature is enabled, at least one service must be created for each
application server that is to be included in your load balancing setup. The following
examples show how to define services per server for firewall or server load balancing.
To create services for Firewall Load Balancing from the CLI:
The add service command has the following general syntax:
add service name { IP | serverName } serviceType port [ -clearTextPort port]
[ -cacheType cacheType ] [ -maxClient positive_integer ] [ -healthMonitor {YES |
NO}] [ -maxReq positive_integer ] [ -cacheable {YES | NO}] [ -cip {ENABLED |
DISABLED} [ cipHeader ]] [ -usip {YES | NO}] [ -useproxyport {YES | NO}] [ -sc
{ON | OFF}] [- sp {ON | OFF}] [ -rtspSessionidRemap {ON | OFF}] [ -cltTimeout
secs ] [ -svrTimeout secs ] [ -serverID positive_integer ] [ -CKA {YES | NO}]
[ -TCPB {YES | NO}] [ -CMP {YES | NO}] [ -maxBandwidth positive_integer ]
[ -accessDown {YES | NO}] [ -monThreshold positive_integer ] [ -state
{ENABLED | DISABLED}] [ -downStateFlush {ENABLED | DISABLED}]
[ -tcpProfileName string ] [ -httpProfileName string ] [ -hashId positive_integer ]
[ -comment string ] [ -appflowLog {ENABLED | DISABLED}]
The following example uses the sample configuration to add the appropriate services
(service type ANY).
> add serviceGroup ingress_osn_service ANY -maxClient 0 -maxReq 0 -cip DISABLED
-usip YES -useproxyport NO -cltTimeout 120 -svrTimeout 120 -CKA NO -TCPB NO -CMP
NO
Done
> bind serviceGroup ingress_osn_service OSN1-ingress [-weight <positive_integer>]
Done
>
bind serviceGroup ingress_osn_service OSN2-ingress [-weight <positive_integer>]
Done
> bind serviceGroup ingress_osn_service OSN3-ingress [-weight <positive_integer>]
Done
>
add service server1service server1 ANY * -gslb NONE -maxClient 0 -maxReq 0 -cip
DISABLED -usip YES -useproxyport NO -sp OFF -cltTimeout 120 -svrTimeout 120 -CKA
NO -TCPB NO -CMP NO
Done
The optional [-weight <positive_integer>] parameter allows for integer values in the [1 ...
100] range and should only be used in non-uniform Unison clusters — for example, a mixed
cluster with both IBM HS22 and HS23 blades. Its purpose is to reflect the relevant traffic
handling capability of the respective node.
Note that the relevant ratio depends not only on the hardware mix but additional parameters
like traffic profile, optimizations applied, subscriber device mix, and so on. In case of a
mixed Unison cluster one should use the Bytemobile capacity calculator to gauge the
respective capacity of each hardware node, then adjust the weights configured on the T1000.