46 Barracuda Load Balancer Administrator’s Guide
Enabling Persistence
The Barracuda Load Balancer supports session persistence using one of the following methods:
•
Layer 4 - Client IP.
All traffic from a particular IP address after the initial incoming connection
will be directed to the same Real Server.
•
Layer 7 - HTTP Cookie.
A cookie placed on the connecting system identifies returning
connections so that all subsequent traffic from that system will go to the same Real Server. This
option is not available for Real Servers using Direct Server Return.
•
Layer 7 - Session Directory Integration.
Session Directory or Terminal Services
on page 46 for more information.
To configure persistence:
1.
From the
Basic > Services
page, click
Edit
for the Service you wish to configure. The
Service
Detail
page will pop up.
2.
In the Session Persistence section, enter the number of seconds that a session is to last. A
session
is the period of time during which all incoming connections from a connecting system
are to go to the same Real Server.
3.
In the Service Persist Type pulldown, select how persistence is to be determined:
3a.
If
Layer 4 - Client IP
is selected, then enter the L4 Persistence Netmask that is to be
used to determine a unique connecting client.
3b.
If
Layer 7 - HTTP Cookie
is selected, then enter the L7 Cookie name that contains the
session data, or any other connection identifiers. This is typically the name of the
cookie used or created by the application on the Real Server, to ensure that users always
connect back to the same Real Server. Leave this field blank to create cookies only to
identify connections between a client browser and the Barracuda Load Balancer. In
either case, the Real Server will not see the appended data or added cookies.
4.
Click
Save Changes
.
Persistence lasts until either the persist time specified has elapsed since the last communication
between the connecting system and the Real Server, or until the identifying cookie is unset by the
application being accessed.
Session Directory or Terminal Services Integration
Session persistence may be maintained by using Windows Server 2003 Session Directory or
Windows Server 2008 Terminal Services Session Broker. The Barracuda Load Balancer queries the
Terminal Server to check if each connecting client already had a session open. If the client had an
open session, the Barracuda Load Balancer forwards that user to the appropriate Terminal Server.
To configure Session Directory:
1.
Using the
Basic > Services
page, create a Service on port 3389.
2.
Set the Enable Session Directory Integration option to
Yes
.
3.
Click
Save Changes
.
Note that Session Directory Integration does not work if the Barracuda Load Balancer is in Bridge-
Path mode.
Содержание Load Balancer
Страница 6: ...vi Barracuda Load Balancer Administrator s Guide...
Страница 14: ...14 Barracuda Load Balancer Administrator s Guide...
Страница 18: ...18 Barracuda Load Balancer Administrator s Guide Figure 2 2 A physical network layout using Route Path...
Страница 28: ...28 Barracuda Load Balancer Administrator s Guide...
Страница 42: ...42 Barracuda Load Balancer Administrator s Guide...
Страница 62: ...62 Barracuda Load Balancer Administrator s Guide...
