This article contains information about NetScaler client, virtual server, and server timeouts.

The following is a list of four different connection timeouts that can be set on NetScaler virtual servers and services:

• Content Switching virtual server cltTimeout parameter specifies the time in seconds that a connection from a client to a Content Switching virtual server must be idle, before a NetScaler appliance closes the connection.

• Load Balancing virtual server cltTimeout parameter specifies the time in seconds that a connection from a client to a Load Balancing virtual server must be idle, before the appliance closes the connection.

• Service svrTimeout parameter specifies the time in seconds that a connection from the appliance to a service or server must be idle, before the appliance closes the connection.

• Service cltTimeout parameter specifies the time in seconds that a connection from a client to a service must be idle, before the appliance closes the connection.
  Note: The service cltTimeout parameter is applicable in transparent mode only, that is when the client accesses the service directly, not going through the virtual IP (VIP) address or virtual server.

When a Content Switching virtual server is bound to a Load Balancing virtual server for all HTTP and SSL virtual servers, then the timeout for the Content Switching virtual server takes precedence, and the timeout for the Load Balancing virtual server is ignored.

In a typical deployment of Content Switching VIP, Load Balancing VIP, and Service, only two timeouts are relevant:

• Client timeout on the Content Switching virtual server.

• Server timeout on the service.
  
  Note: Modifying the timeout values will take effect for new TCP connections. Existing connections will continue with the previous timeout values until termination.

Apart from the NetScaler timeouts, the following timeouts are configured on the actual client and the back end server host:

• The client timeout is set on the client host and can be of any value.

• The server timeout is set on the back end server host and can be of any value.