Product Documentation

Step 2: Configuring Load Balancing of Backend Servers

Oct 06, 2014

When deployed in front of application servers, NetScaler ensures optimal distribution of traffic by the way in which it directs client requests. Administrators can segment application traffic according to information in the body of an HTTP or TCP request, and on the basis of L4-L7 header information such as URL, application data type, or cookie.

Numerous load balancing algorithms and extensive server health checks improve application availability by ensuring that client requests are directed to the appropriate servers.

To configure load balancing of servers, do the following:

  1. Enable the load balancing feature and the use source IP (USIP) mode of the NetScaler.

    Navigate to Configuration > System > Settings and under Modes and Features do the following:

    1. Click Configure basic features and select the Load Balancing checkbox.
    2. Click Configure modes and select the Use Source IP checkbox.
      Note: With vPath integration, Source NAT is not required and server return traffic is redirected to NetScaler by vPath service attached to the server VM port. The original source IP is preserved for all connections.
  2. Add the required servers as services on the NetScaler .

    Navigate to Configuration > Traffic Management > Load Balancing > Services, click Add and configure the details (IP address, port, protocol) of each of the servers as services on the NetScaler .

    Note: NetScaler is tightly integrated with the vPath architecture, and will not work without a vPath port-profile attached to the servers. Therefore, till the port profile configuration (provided in step 3) is done, the service state may appear as Down.
  3. Create a virtual server that will bind these services to the virtual server IP address.

    Navigate to Configuration > Traffic Management > Load Balancing > Virtual Servers, click Add and configure the name, virtual IP address (VIP), protocol, load balancing method, and the services to be bound to the virtual server.

  4. Save the configurations. Click Save in the upper right hand corner of the interface.