Before configuring a LifeKeeper for Windows communication path between servers, verify the hardware and software setup. See the Configuration section for requirements.
Configuration Notes
- You should configure no more than one shared disk comm path between servers.
- Shared Disk comm paths are supported for two-server clusters only.
- The shared disk comm path supports only shared disks initialized with MBR selected as the partition style. Do not select a shared disk initialized with GPT.
- For greater than two-server clusters, use multiple TCP/IP comm paths for heartbeat redundancy. A priority value is used to tell LifeKeeper for Windows the order in which TCP/IP paths to a given remote server should be used.
- IMPORTANT: Supported configurations require that you define redundant comm paths so that the failure of a single communication line will not cause an unnecessary failover. If a single comm path is used and the comm path fails, LifeKeeper for Windows hierarchies may come in service on multiple servers simultaneously. This is known as “split-brain”. Additionally, heavy network traffic on a TCP/IP comm path can result in unexpected behavior, including false failovers and LifeKeeper for Windows initialization problems.
Creating a Comm Path
- Select one of the servers, and then select Create Comm Path from the server context menu or server context toolbar.
- Select one or more Remote Servers in the list box. If a remote server is not listed in the list box (i.e. it is not yet connected to the cluster), you may enter it using Add Server. You must make sure that the network addresses for both the local and remote servers are resolvable (for example, with DNS or added to the /etc/hosts file). Click Next.
- Select either TCP or DISK for Device Type and click Next.
- Provide all required information for the Device Type that you selected and click Next after each step. Refer to the table below for additional information on each configuration field.
Field | Tips | |||||||
---|---|---|---|---|---|---|---|---|
For TCP/IP Comm Path… | ||||||||
Heartbeat Interval | Enter a value between 4 and 15 for the heartbeat interval, which is the number of seconds between heartbeat signals that verifies the servers are alive). The default = 6. | |||||||
Maximum Heartbeat Misses | Enter a value between 3 and 99. This is the number of consecutive heartbeat signals that can be missed before the comm path is marked as dead. The default = 5. | |||||||
Local IP Address | Enter the IP address to be used by the local server for this comm path. | |||||||
Priority | Enter the priority for the comm path on the local server. The priority will be used to determine the order that the comm paths between the two servers will be used. Priority 1 is the highest, 99 is the lowest. | |||||||
Remote IP Address | Enter the IP address to be used by the remote server for this comm path. | |||||||
Port Number | Enter a unique port number to be used by the TCP/IP service. This number must be between 1500 and 10000. LifeKeeper for Windows offers a default which you can change. | |||||||
For Shared Disk Comm Path… | ||||||||
Heartbeat Interval | Enter a value between 4 and 15 for the heartbeat interval, which is the number of seconds between heartbeat signals that verifies the servers are alive). The default = 6. | |||||||
Maximum Heartbeat Misses | Enter a value between 3 and 99. This is the number of consecutive heartbeat signals that can be missed before the comm path is marked as dead. The default= 5. | |||||||
Priority | Enter the priority for the comm path on the local server. The priority will be used to determine the order that the comm paths between the two servers will be used. Priority 1 is the highest, 99 is the lowest. | |||||||
Drive Letter | The drive letter associated with the shared volume to be used for the shared disk comm path. This must be the same letter on both servers. |
- Click Create. The dialog should display a message indicating the network connection is successfully created. If the output panel is enabled, the message will be displayed there as well. Click Next.
- If you selected multiple Local IP Addresses or multiple Remote Servers and the Device Type was set to TCP, then you will be taken back to Step 4 to continue with the next Comm Path. If you selected multiple Remote Servers and the Device Type was set to DISK, then you will be taken back to Step 3 to continue with the next Comm Path.
- Click Done when presented with the concluding message.
Verifying the Comm Path
You can verify the comm path by viewing the Server Properties dialog. You should see an Alive status.
- In addition, check the server icon in the right pane of the GUI. If this is the first comm path that has been created, the server icon shows a yellow heartbeat indicating that one comm path is ALIVE but there is no redundant comm path.
If the comm path does not activate after a few minutes, verify that the paired server’s computer name is correct.
Post your comment on this topic.