Print Download PDF Send Feedback

Previous

Next

Implementing Planning Considerations

Included Topics

High Availability or Load Sharing

Choosing the Load Sharing Mode

IP Address Migration

High Availability or Load Sharing

Whether to choose a Load Sharing (Active/Active) or a High Availability (Active/Standby) configuration depends on the need and requirements of the organization. A High Availability cluster ensures fail-safe connectivity for the organization. Load Sharing provides the additional benefit of increasing performance.

Note - When working on a sync network, it is recommended to use a NIC with the same bandwidth as the NICs that are used for general traffic.

Choosing the Load Sharing Mode

Load Sharing Multicast mode is an efficient way to handle a high load because the load is distributed optimally between all cluster members. However, not all routers can be used for Load Sharing Multicast mode. Load Sharing Multicast mode associates a multicast MAC with each unicast cluster IP address. This ensures that traffic destined for the cluster is received by all members. The ARP replies sent by a cluster member will therefore indicate that the cluster IP address is reachable via a multicast MAC address.

Some routing devices will not accept such ARP replies. For some routers, adding a static ARP entry for the cluster IP address on the routing device will solve the issue. Other routers will not accept this type of static ARP entry.

Another consideration is whether your deployment includes routing devices with interfaces operating in promiscuous mode. If on the same network segment there exists two such routers and a ClusterXL Security Gateway in Load Sharing Multicast mode, traffic destined for the cluster that is generated by one of the routers could also be processed by the other router.

For these cases, use Load Sharing Unicast mode, which does not require the use of multicast for the cluster addresses.

IP Address Migration

If you wish to provide High Availability or Load Sharing to an existing Security Gateway configuration, it is recommended to take the existing IP addresses from the active Security Gateway, and make these the cluster addresses (cluster virtual addresses), when feasible. Doing so will avoid altering current IPSec endpoint identities, as well keep Hide NAT configurations the same in many cases.