Radware Alteon Application Manual page 227

— If the host header is "www.company-a.com," Alteon directs requests to the server group
containing one of the Servers 1 through 4.
— If the host header is "www.company-b.com," Alteon directs requests to the server group
containing one of the Servers 5 through 8.
Cookie-Based Preferential Load Balancing
Cookies can be used to provide preferential services for customers, ensuring that certain users are
offered better access to resources than other users when site resources are scarce. For example, a
Web server could authenticate a user via a password and then set cookies to identify them as
"Gold," "Silver," or "Bronze" customers. Using cookies, you can distinguish individuals or groups of
users and place them into groups or communities that get redirected to better resources and receive
better services than all other users.
Note: Cookie-based persistent load balancing is described in
Cookie-based preferential services enables, among others, the following supported use cases:
• Redirect higher priority users to a larger server or server group.
• Identify a user group and redirect them to a particular server group.
• Serve content based on user identity.
• Prioritize access to scarce resources on a Web site.
• Provide better services to repeat customers, based on access count.
Clients that receive preferential service can be distinguished from other users by one of the
following methods:
• Individual User—A specific individual user can be distinguished by IP address, login
authentication, or permanent HTTP cookie.
• User Communities—A set of users, such as "Premium Users" for service providers who pay
higher membership fees than "Normal Users", can be identified by source address range, login
authentication, or permanent HTTP cookie.
• Applications—Users can be identified by the specific application they are using. For example,
priority can be given to HTTPS traffic that is performing credit card transactions versus HTTP
browsing traffic.
• Content—Users can be identified by the specific content they are accessing.
Based on one or more of these criteria you can load balance requests to different server groups.
To configure cookie-based preferential load balancing
1. Before you can configure header-based load balancing, ensure that Alteon is configured for basic
SLB with the following tasks:
— Assign an IP address to each of the real servers in the server pool.
— Define an IP interface.
— Define each real server.
— Assign servers to real server groups.
— Define virtual servers and services.
For information on how to configure your network for SLB, see
2. Configure the Layer 7 content classes to match the various cookie values by which you need to
load balance.
Document ID: RDWR-ALOS-V2900_AG1302
Alteon Application Switch Operating System Application Guide
Persistence, page 583
Server Load Balancing, page
Server Load Balancing
.
165.
227