![Radware Alteon Application Manual Download Page 207](http://html.mh-extra.com/html/radware/alteon/alteon_application-manual_781134207.webp)
Alteon Application Switch Operating System Application Guide
Server Load Balancing
Document ID: RDWR-ALOS-V2900_AG1302
207
this mode, the Application Service Engine will perform TCP optimizations without SYN attack
protection (which is performed when the delayed binding mode is set to enabled), function as a full
TCP proxy, reorder TCP packets, and so on.
The Application Service Engine can work in both Alteon delayed binding modes. In enabled delayed
binding mode, the Application Service Engine only provides SYN attack protection. In force proxy
mode, it only provides TCP optimizations.
Configuring Force Proxy
To configure force proxy
IP Address Ranges Using imask
The imask option lets you define a range of IP addresses for the real and virtual servers configured
under SLB. By default, the imask setting is 255.255.255.255, which means that each real and
virtual server represents a single IP address. An imask setting of 255.255.255.0 means that each
real and virtual server represents 256 IP addresses.
Consider the following example:
•
A virtual server is configured with an IP address of 172.16.10.1.
•
Real servers 172.16.20.1 and 172.16.30.1 are assigned to service the virtual server.
•
The imask is set to 255.255.255.0.
If the client request is set to virtual server IP address 172.16.10.45, the unmasked portion of the
address (0.0.0.45) gets mapped directly to whichever real server IP address is selected by the SLB
algorithm. This results in the request being sent to either 172.16.20.45 or 172.16.30.45.
Session Timeout Per Service
This feature allows for the configuration of session timeout based on a service timeout instead of the
real server timeout. With this feature, by default the timeout value for the service is set to 0. When
the value is 0, the service uses the real server timeout value. Once the timeout value for the service
is configured, the new configuration is used instead.
The timeout for aging of persistent sessions is prioritized. According to the priority, persistent
timeout is the highest followed by virtual service and real server timeout.
Note:
Persistent timeout must be greater than the virtual service and real server timeout.
This is useful when sessions need to be kept alive after their real server configured timeout expires.
An FTP session could be kept alive after its server defined timeout period, for example.
>> # /cfg/slb/virt <virtual server number> /service <service type> /dbind
Current delayed binding: disabled
Enter new delayed binding [d/e/f]:f