tcp_remote Mode

In this setting Quorum is determined by checking the ability to connect to TCP/IP services on remote hosts. Connections are done via TCP/IP to a specific port on a host and are done independent of any of the defined communication paths. Being able to connect to the majority of the specified hosts will determine if the node has quorum. Host and port combinations are defined via the QUORUM_HOSTS setting discussed below. This mode is also available with a two-node cluster, however, three nodes are required when using a witness node for remote_verify.

*Note: Due to majority-based quorum, it is recommended that the hosts always be specified with an odd number of nodes.

*Note: Due to the inherent flexibility and complexity of this mode, it should be used with caution by someone experienced with both LifeKeeper and the particular network/cluster configuration involved.

tcp_remote Mode Configuration

Set QUORUM_MODE> to tcp_remote in /etc/default/LifeKeeper. The following configuration settings are required when using tcp_remote:

• QUORUM_HOSTS – This is a comma delimited list of host:port values used to define the hosts and ports to connect to when checking for quorum.

• QUORUM_TIMEOUT_SECS – This is the time allowed for TCP/IP connections to complete. It defaults to 20 seconds.

See “Quorum Parameter List” for more information.

Available Witness Mode setting with tcp_remote mode

The following witness mode settings are available with tcp_remote. Refer to “Available Witness Mode” for more details on each mode.

• remote_verify

• none or off