EasyManua.ls Logo

Check Point R80.20 - Persistent Server Timeout; Load-Balancing Methods

Check Point R80.20
626 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
ConnectControl - Server Load Balancing
Next Generation Security Gateway Guide R80.20 | 293
Persistency by service is useful if you are load balancing multiple services in your server
group. For example, in a redundant environment of two servers, each running HTTP and FTP,
ConnectControl directs traffic from one client to the server of the correct service. This
prevents heavy load on one server, which can happen with Persistency by server.
Item
Description
1 Multiple client requests for HTTP and FTP.
2 Internet
3 Security Gateway - The service requests arrive at the destination public IP address of
the Logical Server, which is on the Security Gateway. The gateway directs the
requests to the internal IP address of the Logical Server group.
4 Logical Server group with two servers, each with FTP and HTTP services.
ConnectControl balances the load between the servers.
Persistent Server Timeout
If you enable Persistent server mode, you can set a timeout for a client to use one server. If a
server becomes unavailable, ConnectControl directs new connections to a new, available server.
This bypasses the persistency and optimizes load balancing.
To set persistent server mode timeout:
1.
Open Global Properties.
2.
Click ConnectControl.
3.
In Persistent server timeout, enter the timeout in seconds.
Load-Balancing Methods
ConnectControl distributes network traffic to load-balanced servers according to predefined
balancing methods:
Domain: Directs service requests based on domain name.
Important - This method is
not
supported for Logical Servers.
Random: Directs service requests to servers at random. The random method is a good choice
when all the load-balanced servers have similar RAM and CPU and are located on the same
segment.
Round Robin: Directs service requests to the next server in the sequence. The round robin
method is a good choice when all the load balanced servers have similar RAM and CPU and are
on the same segment.
Round Trip: Directs incoming requests to the server with the fastest response time.
ConnectControl calculates the fastest server from average round-trip time to respond to ICMP
echo requests. The round trip method is a good choice if there are large variations in the traffic
load on your network or when load balancing over WAN connections.
Important - This method is
not
supported for Logical Servers.
For more information, see sk31162 http://supportcontent.checkpoint.com/solutions?id=sk31162.

Table of Contents

Related product manuals