Radware Alteon, Инструкция по применению

Страница: 585 / 842

Alteon Application Switch Operating System Application Guide
Persistence
Document ID: RDWR-ALOS-V2900_AG1302
585
HTTPS traffic only) from the same client to map to the same server, as long as the same group is
configured for both services. In Alteon, when the metric configured is hash, phash, or minmisses,
persistence may also be maintained to the real server port (rport), in addition to the real server.
You should disable persistence to the rport on the following conditions:
• When there are two different services, such as TCP and UDP, that must maintain persistence to
the same real server.
• When client IP-based persistence is not dependent on the load balancing metric.
To configuring Client IP address-based persistence
1. Configure real servers and services for basic SLB:
— Define each real server and assign an IP address to each real server in the server pool.
— Define a real server group and set up health checks for the group.
— Define a virtual server on the virtual port for HTTP (port 80) and HTTPS (port 443) and
assign both services to the same real server group. HTTP and HTTPS are supported only on
their default service port numbers.
— Enable SLB.
— Enable client processing on the port connected to the client.
For information on how to configure your network for SLB, see Server Load Balancing, page 165
2. If a proxy IP address is not configured on the client port, enable DAM for real servers.
3. Select Client IP-based persistence as the persistent binding option for the virtual port.
If multiple real server ports are configured for this service, you may choose whether to maintain
persistence to the rport on the real server.
4. Enable client processing on the client port.
Cookie-Based Persistence
Cookies are a mechanism for maintaining the state between clients and servers. When the server
receives a client request, the server issues a cookie, or token, to the client, which the client then
sends to the server on all subsequent requests. Using cookies, the server does not require
authentication, the client IP address, or any other time-consuming mechanism to determine that the
user is the same user that sent the original request.
In the simplest case, the cookie may be just a "customer ID" assigned to the user. It may be a token
of trust, allowing the user to skip authentication while his or her cookie is valid. It may also be a key
that associates the user with additional state data that is kept on the server, such as a shopping cart
>> # /cfg/slb/adv/direct ena
>> # /cfg/slb/virt 1/service <virtual port> pbind clientIP
Current persistent binding mode: disabled
Enter clientip|cookie|sslid|disable persistence mode: clientIP
Use Rport? (y/n) [y]y
>> # /cfg/slb/port <port number> /client ena