Product Documentation

Overriding LSN configuration with Load balancing Configuration

Aug 17, 2015

A global layer 3 parameter, override LSN, has been introduced for overriding the large scale networking (LSN) configuration with the load balancing configuration for traffic matching both configurations. USNIP or USIP settings of the load balancing configuration are applied to the traffic, instead of applying the LSN IP address of the LSN configuration. When this option is disabled (the default), an LSN configuration takes precedence over any load balancing configuration.

This option is useful in an LSN deployment that includes NetScaler appliances and value added services, such as firewall and optimization devices (for example, Citrix Bytemobile and Citrix CloudBridge appliances). In this type of deployment, the ingress traffic on the NetScaler appliance is required to pass through these value-added services before an LSN configuration on the appliance is applied to the traffic. For the NetScaler appliance to send the ingress traffic to a value added service, a load balancing configuration is created and override LSN is enabled on the appliance. The load balancing configuration includes value added services, represented as load balancing services, bound to a virtual server of type ANY. The virtual server is configured with listen policies for identifying the traffic to be sent to the value added service.

To override LSN configurations with by using the NetScaler command line

At the command prompt, type:

set L3Param [-overrideLsn ( ENABLED | DISABLED )]

Example

set L3ParamoverrideLSN ENABLED