CLUSTERS
Follow this procedure to set up a private network for your cluster.
1. Install an additional network interface card in each server in the cluster. These cards should be connected through a private hub or switch.
2. Configure the LAN to use TCP/IP.
3. Assign a second IP address to each server. In a cluster using two servers, for example, you could use the addresses 192.168.64.1 and 192.168.64.2.
4. Assign host names for the new IP addresses, and place entries in the HOSTS file or the DNS. In a cluster using two servers, for example, you could assign the host names Acme_clu.acme.com and Acme2_clu.acme.com. The entries in the HOSTS file might then be:
192.168.64.2 Acme2_clu.acme.com
6. On each server in the cluster, add a new network port for the private LAN, and edit the Server document to enable the port.
PORT2_TcpIPAddress=0,e.f.g.h:1352
where PORT1 and PORT2 are the port names and a.b.c.d and e.f.g.h are the IP addresses for the ports.
If you have ports named TCPIP and CLUSTER, for example, these lines might be:
TCPIP_TcpIPAddress=0,192.114.32.5:1352
CLUSTER_TcpIPAddress=0,192.168.64.1:1352
where Cluster Port is the port you created for the cluster. In this example, this line would be:
Server_Cluster_Default_Port=CLUSTER
This ensures that all cluster traffic uses this port for cluster communications no matter what order the ports are in.
Making sure Domino is using the private LAN
To verify that IBM® Lotus® Domino® is using the private LAN, you can do the following:
1. At the server console, type show cluster.
2. In the results, look for the line "Server cluster default port: Cluster Port"
It is also a good idea to check the cluster to be sure that cluster replication is using the private LAN. To do this, you can look at some of the cluster statistics.
1. From the Domino Administrator or the Web Administrator, click the Server - Statistics tab.
2. In the list of statistics, expand NET.
3. Expand the port name you gave to the cluster.
4. Look for the following statistics for the private LAN port:
BytesSent
6. Expand SessionBytes, and look for the following replication statistics for the cluster:
Out