Product Documentation
ADC
14.1 - Current Release 13.1 13.0 12.1
View PDF

Support for load balancing profile

June 12, 2023
Contributed by: 
C

A load balancing configuration has many parameters, so setting the same parameters on several virtual servers can become tedious. From release 11.1, a load balancing (LB) profile makes this task easier. You can now set load balancing parameters in a profile and associate this profile with virtual servers, instead of setting these parameters on each virtual server.

The following parameters are presently supported in an LB profile:

  • HTTPonlyflag—Include the HttpOnly attribute in persistence cookies. The HttpOnly attribute limits the scope of a cookie to HTTP requests and helps mitigate the risk of cross-site scripting attacks.
  • UseSecuredPersistenceCookie—Encrypt the persistence cookie values by using the SHA2 hash algorithm.
  • Cookiepassphrase—Specify the passphrase used to generate a secured persistence cookie value.
  • DBS_LB—Enable database specific load balancing for MySQL and MSSQL service types.
  • Cl_process_local—Packets destined to a virtual server in a cluster are not steered. Enable the option for single packet request response mode or when the upstream device is performing a proper RSS for connection based distribution.
  • lbHashAlgorithm—Specify the hashing algorithm to be used for the following hash-based load balancing methods:
    • URL hash method
    • Domain hash method
    • Destination IP hash method
    • Source IP hash method
    • Source IP Destination IP hash method
    • Source IP Source Port hash method
    • Call ID hash method
    • Token method

    Possible values: DEFAULT, PRAC, JARH Default value: DEFAULT

  • lbHashFingers—Specify the number of fingers to be used in PRAC and JARH algorithms for hash-based LB methods. Increasing the number of fingers provides better distribution of traffic at the expense of additional memory.

    Default value: 256 Minimum value: 1 Maximum value: 1024

  • proximityFromSelf-Enable to use the Netscaler’s loopback IP address instead of the client’s IP address to fetch the closest server location for static proximity load balancing or GSLB decision.

Note

You can set DBS_LB and Cl_process_local parameters on a virtual server and in the profile. If you enable these parameters on a virtual server and then set a profile to this virtual server, the parameters appear as disabled in the output of the "show lb vserver" command for that virtual server. Check the profile to see the actual status of these parameters. In addition, if you set and then unset a profile to a virtual server, the parameters are set with default values for that virtual server.

To create an LB profile by using the CLI

At the command prompt, type:

add lb profile <lbprofilename> -dbsLb ( ENABLED | DISABLED ) -processLocal ( ENABLED | DISABLED ) -httpOnlyCookieFlag ( ENABLED | DISABLED ) -cookiePassphrase -useSecuredPersistenceCookie ( ENABLED | DISABLED ) -lbHashAlgorithm <lbHashAlgorithm> -lbHashFingers <positive_integer>- proximityFromSelf <NO/YES>
<!--NeedCopy-->

Example:

> sh lb profile p1
LB Profile name:  p1
DBS LB : DISABLED   Process Local: DISABLED
Persistence Cookie HttpOnly Flag: ENABLED
Use Encrypted Persistence Cookie: DISABLED
Proximity From Self: ENABLED
No of vservers bound: 0
Store MQTT clientid and username in transactional logs: NO
Hash LB algorithm used in LB decision: DEFAULT
Number of fingers for Hash LB algorithm: 256
Done

<!--NeedCopy-->

To create an LB profile by using the GUI

Navigate to System > Profiles > LB Profile, and add a profile.

To associate an LB profile with an LB virtual server by using the CLI

At the command prompt, type:

set lb vserver <name> -lbprofilename <string>
<!--NeedCopy-->

Example

set lbvserver lbvip1 -lbprofile p1

Done

sh lb vserver lbvip1

lbvip1 (203.0.113.1:80) - HTTP       Type: ADDRESS
State: UP
Last state change was at Wed May 25 12:36:20 2016
Time since last state change: 0 days, 00:01:26.140
Effective State: UP  ARP:DISABLED
Client Idle Timeout: 180 sec
Down state flush: ENABLED
Disable Primary Vserver On Down : DISABLED
Appflow logging: ENABLED
Port Rewrite : DISABLED
No. of Bound Services :  2 (Total)       2 (Active)
Configured Method: LEASTCONNECTION      BackupMethod: ROUNDROBIN
Mode: IP
Persistence: NONE
Vserver IP and Port insertion: OFF
Push: DISABLED  Push VServer:
Push Multi Clients: NO
Push Label Rule: none
L2Conn: OFF
Skip Persistency: None
Listen Policy: NONE
IcmpResponse: PASSIVE
RHIstate: PASSIVE
New Service Startup Request Rate: 0 PER_SECOND, Increment Interval: 0
Mac mode Retain Vlan: DISABLED
DBS_LB: DISABLED
Process Local: DISABLED
Traffic Domain: 0
LB Profile: p1
Done
<!--NeedCopy-->

To associate an LB profile with an LB virtual server by using the GUI

  1. Navigate to Traffic Management > Load Balancing > Virtual Servers.
  2. Select a virtual server, and click Edit.
  3. In Advanced Settings, click Profiles.
  4. In the LB Profile list, select the profile to associate with this virtual server.

To configure the Proximity from Self parameter in the load balancing profile by using the GUI

Configure the Proximity from Self parameter in the profile so that when the profile is attached to the entity the parameter is enabled for the entity.

  1. Navigate to System > Profile > LB Profile.
  2. Click Add.
  3. Select Proximity from Self.
  4. Click OK.
Support for load balancing profile
June 12, 2023
Contributed by: 
C
June 12, 2023
Contributed by: 
C

In this article

Site feedback | Your privacy choices footer linkYour Privacy Choices | Privacy and legal terms | Cookie preferences | Consent settings | docs.cloud.com
© 1999- Cloud Software Group, Inc. All rights reserved.