McAfee FIREWALL 2.10 Uživatelský manuál stáhnout pdf (Strana 5)

Persistence - aka Server Affinity

Persistence may or may not be required and depends on the specific Web Gateway being used. Two

possible methods are described in the following sections.

Source IP Address (Recommended)

Source IP persistence is the standard method and is appropriate for most requirements. When set, clients

connecting from the same source IP address within the persistence timeout period (the default is 5 mins) will

always be sent to the same Web Gateway.

Destination Hash

Another option at Layer 4 is to change the load balancing algorithm (i.e. the “scheduler”) to destination hash

(DH). This causes the load balancer to select the proxy based on a hash of the destination IP address. This

causes session requests to be directed at the same server based solely on the destination IP address of a

packet which therefore makes client connections persistent for a particular Internet host.

Since this setting is a scheduler, the way connections are load balanced will also change. However it should

still provide a well balanced distribution of client sessions between Web Gateway servers.

Web Gateway Deployment Modes

There are two implementation methods that are typically used – Proxy Mode & Transparent (Routed) Proxy

Mode.

1 – Proxy Mode (Recommended)

This mode requires the load balancers VIP address to be defined in users browsers. This means that the

load balancer will receive client requests and distribute these requests across the back-end Web Gateways.

2 – Transparent Routed Proxy Mode

With this mode, client requests must be routed to the load balancer / Web Gateway cluster. This can be

achieved by either setting the default gateway on the client PCs to be the load balancer, or by adding rules to

the default gateway device. Rules would typically be configured for HTTP & HTTPS traffic on ports 80 and

443.

1 2 3 4 5 6 7 8 9 10 ... 25 26

Žádné komentáře

McAfee FIREWALL 2.10 Uživatelský manuál Strana 5