Veritas cluster heartbeat configuration file

On the General tab, verify that you have selected a static IP address that is not on the same subnet or network as another one of the public network adapters. An example of good IP addresses to use for the private adapters is If your public network uses the Verify that there are no values defined in the Use the following DNS server addresses box.

If the cluster nodes are also DNS servers, " On the DNS tab, verify that there are no values defined. When you close the dialog box, you may receive the following prompt.

If you receive this prompt, click Yes :. Click the cluster name at the root of Administrator. On the File menu, click Properties. On the Network Priority tab, verify that the private network is listed at the top. If it is not, use the Move Up button to increase its priority. Click Internal cluster communications only private Network. For more information, see How to use Windows Server cluster nodes as domain controllers.

On the IP Address tab, verify that you have selected a static IP address that is not on the same subnet or network as another one of the public network adapters. If you have a network adapter that can transmit at multiple speeds and can specify a speed and duplex mode, manually specify a speed and duplex mode. With network adapters that can manually specify a speed and duplex mode, make sure that you hard set them to the same on all nodes and according to the manufacturer's specifications.

To add a new low priority link utilizing a public interface , use the following command on each node:. Example using qfe4 again for a low-pri link:.

Note also, that "low-priority" connections are not recommended for use in Oracle RAC clusters for data security reasons. The commands above add a link to the running configuration. The process for the permanent change will be explained later in this document. Once the heartbeat is added, the new link configuration can be verified with the following command:. The newly configured link will show in the output.

The process to make the change to the cluster configuration permanent follows. If a high priority private link on qfe4 is desired, an additional line is added to the end of the links listed in the file, as shown below:. Private network: Links are used for heartbeat communication, as well as sharing status and update information between clustered nodes. These private links are used for cluster communication only. No other application or resource should be configured to share these links.

This may interfere with cluster communication and cause issues with cluster functionality. Do not assign IP addresses to private heartbeats network adapters. Ensure that all adapters, and switch ports, are set to auto-negotiate, or are set to use matching speed settings. All private heartbeats should be connected via a network hub or a switch.

The best practice is to use only one hub, or switch, per heartbeat connection. This avoids a single point of failure. Although cross-linked cables can be used for heartbeat purposes, we recommend that hubs, or switches, be used to ensure reliable connection. Ensure that the same driver revision is used across all NICs.

Ensure that the same make and model of NICs are used throughout the network, to promote consistency. Yes No Rating submitted. Please provide additional feedback optional :. Cancel Submit. You are using Microsoft Internet Explorer! Microsoft no longer supports this browser. As a result, some of the functionality on this website may not work for you.

For an optimal experience on our website, please consider changing to Microsoft Edge, Firefox, Chrome or Safari. Article Languages. Translated Content Please note that this document is a translation from English, and may have been machine-translated. GAB Group membership and Atomic Broadcast provides the global message order required to maintain a synchronised state among the systems, and monitors disk comms such as that required by the VCS heartbeat utility.