Configure geographical HA configuration with Lucent CM servers on separate networks
		GO

Purpose

This topic describes the steps to bypass the internal Lucent CM load balancer for geographical HA configurations.

Reason for bypass

The internal Lucent CM load balancer must be bypassed for geographical HA configurations, where the IP network for each location uses different external IP address ranges.

The normal desire is to place the active load balancer at one location, and the standby load balancer at another location. However, the internal load balancer failover mechanism requires both load balancers to use the same external IP address range.

Instead, bypass the internal load balancer and use one to the following load balancing options for geographical HA configurations:

External load balancing

FS 5000-based load balancing

Bypass solution

The host files on the Lucent CM nodes must be updated to map the Lucent CM system virtual host name (the host name associated with the virtual IP address) to an unused IP, but valid, external IP address.

The internal load balancer keeps on running, but waits for connections request that never come. This waiting state does not use CPU time and uses little system memory.

Before you begin

Before you update the /etc/hosts files, ensure that the DNS servers are updated to resolve the user client URL host names according to the alternate load balancing option you selected.

Update host files

This procedure must be performed on all Lucent CM nodes.

Perform the following steps to bypass the Lucent CM load balancer:

		GO
© Lucent Technologies