Scenario: An application that uses HTTP for connections and other protocols for different types of content has
been deployed. Load balancing virtual servers have been created for each protocol and the engineer now
needs to ensure that once a load balancing decision has occurred, further requests for different content are
served from the same server.
How could the engineer achieve this?
A.
Create a persistency group.
B.
Set the Spillover method to DYNAMICCONNECTION.
C.
Add a new virtual server for each protocol that is not directly addressable.
D.
Set each virtual server to use Source IP Hash as the load balancing method.
Explanation:
Summary
A Web application may use HTTP and HTTPS in the same session. This article describes the configuration
necessary to ensure persistence is maintained across both HTTP and HTTPS connections.
Background
The NetScaler allows us to configure persistency groups to accommodate exactly such a need. A practical
example of this might be a shopping cart where items are browsed over HTTP, but purchased over HTTPS. If
persistency were not maintained, it’s possible the shopping cart might be lost, the user logged out, or other
adverse actions. By using persistency groups, the HTTP and HTTPS vServers are grouped together into one
persistent entity.
Procedure
From the GUI:
1. Click and expand the Load Balancing node.
2. Click Persistency Groups.
3. Click Add.
4. Populate the Group Name field.
5. Choose between COOKIEINSERT, SOURCEIP or RULE from the Persistence dropdown and configure a
timeout.
6. Choose a backup persistence method if desired.
7. Select the vServers to be grouped from the Available Virtual Servers list.
8. Click Add to move the vServers from the available list to the configured list.
From the command line interface (CLI):
Issue the following commands:
1. bind lb group <name of group> <vserver 1>
2. bind lb group <name of group> <vserver 2>
3. ….
4. set lb group <name of group> -persistenceType <persistence method> –
persistenceBackup <backup persistence method>