Radware Alteon Application Manual page 170

Alteon Application Switch Operating System Application Guide
Server Load Balancing
Figure 28: SLB Client/Server Traffic Routing
• Identical content must be available to each server in the same pool. Either of the following
methods can be used:
— Static applications and data are duplicated on each real server in the pool.
— Each real server in the pool has access to the same data through use of a shared file system
or back-end database server.
• Some services require that a series of client requests go to the same real server so that
session-specific state data can be retained between connections. Services of this nature include
Web search results, multi-page forms that the user fills in, or custom Web-based applications
typically created using cgi-bin scripts. Connections for these types of services must be
configured as persistent (see
metrics (see Metrics for Real Server Groups, page
• Clients and servers can be connected through the same Alteon port. Each port in use can be
configured to process client requests, server traffic, or both. You can enable or disable
processing on a port independently for each type of Layer 4 traffic:
— Layer 4 client processing—Ports that are configured to process client request traffic
provide address translation from the virtual server IP to the real server IP address.
— Layer 4 server processing—Ports that are configured to process server responses to
client requests provide address translation from the real server IP address to the virtual
server IP address. These ports require real servers to be connected to Alteon directly or
through a hub, router, or another switch.
Note: Ports configured for Layer 4 client/server processing can simultaneously provide Layer 2
switching and IP routing functions.
170
Persistence, page 583), or must use the minmisses, hash, phash
180).
Document ID: RDWR-ALOS-V2900_AG1302