Creating a Communication Path

Before configuring a SIOS Protection Suite 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.

• For greater than two-server clusters, use multiple TCP/IP comm paths for heartbeat redundancy. A priority value is used to tell SIOS Protection Suite 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, SIOS Protection Suite 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 SIOS Protection Suite initialization problems.

Creating a Comm Path

1. Select one of the servers, and then select Create Comm Path from the server context menu or server context toolbar.

2. 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.

3. Select either TCP or DISK for Device Type and click Next.

4. 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.

5. 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.

6. 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.

7. 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.

• The server icon will display a green heartbeat when there are at least two comm paths ALIVE.

If the comm path does not activate after a few minutes, verify that the paired server’s computer name is correct.