Configuration recommendations for Veritas Cluster Server Heartbeat communication within Storage Foundation for Windows with High Availability (SFW-HA)
| Article:TECH84157 | | | Created: 2008-01-22 | | | Updated: 2010-01-26 | | | Article URL http://www.symantec.com/docs/TECH84157 |
Problem
Configuration recommendations for Veritas Cluster Server Heartbeat communication within Storage Foundation for Windows with High Availability (SFW-HA)
Solution
DESCRIPTION:
Veritas Cluster
Server (VCS) utilizes both Public and Private Network connections for
communication between clustered nodes and applications available to the
public.
Public Network
Links are utilized for access to clustered applications.
Private Network
Links utilize Heartbeat communication in order to provide status and update
information between clustered nodes. These links are used for cluster
communication only. No other application or resource should be configured
to share the links, as it may cause issues with cluster communication, thereby
causing issues with the ability for the cluster to function properly.
Heartbeat
communication allows for the cluster's Low Latency Transfer (LLT) protocol to
transmit information regarding the cluster's status and configuration
information between nodes, which in turns allows the Global Atomic Broadcast
(GAB) component of the cluster to send and receive these updates among all
clustered nodes. This communication is vital to the well being of the cluster.
If at any time an active node in the cluster is unable to communicate with the
other passive nodes, this may cause minor to severe issues with cluster behavior
and performance, as well as access to the clustered applications.
Recommended
Veritas Cluster Heartbeat Configurations:
Use the following recommended configuration to
setup Veritas Cluster Server (VCS) Heartbeat communication to ensure that
there is no single point of failure and that this private communication will
function in the most optimal manner:
- Ensure that all private heartbeats network adapters do not have a IP address assigned to them.
- All private heartbeat network adapters should be set to either 10 or 100 Megabit consistently, not a mixture of both.
- All private heartbeats should be connected via a HUB or Switch. It is suggested to use only one (1) HUB / Switch per Heartbeat connection in order to remove any single point of failure.
- Please ensure that the same speed of the Network Adapter (10 or 100 Megabit) is set at the switch level.
- Network cards (NICs) and all HUBs / Switches used for private heartbeats should have Auto-Negotiation set to disabled.
- Cross-linked cables can be used for heartbeat purposes; however, it is suggested that HUBs / Switches be the preferred method of reliable connection.
- Ensure that the same driver revision is used across all NICs.
- Ensure that the same make and model of NICs are used to promote consistency on the network.
- As Heartbeat connections should each have their own NIC and HUB / Switch for their private network links; likewise, the Public Network connection should have its own NIC and HUB / Switch. Though it is suggested that the same NIC and NIC driver be used as the private Heartbeat connection, this is not as necessary.
- If using 3 or more network adapters, set at least 2 of them as private Heartbeat adapters within any manual configuration, or when using the Veritas Cluster Configuration Wizard. If required set the 3rd as a 'lowpri' Heartbeat Adapter (i.e. over the public link) in case both private heartbeats fail, this will allow for cluster communication to take place over the public network as a low priority.
Important Notice:
- Network Routers are not supported for private heartbeat network, or any other Layer 3 Protocol devices.
- NIC Teaming is NOT supported on the Private Network Heartbeat links; however NIC Teaming can be implemented on the Public Network Adapters ONLY and be supported by Symantec Enterprise Support.
While this is not to say NIC
Teaming has never been configured within a clustered environment for Heartbeat
communication, Symantec Enterprise Support DOES NOT test, document,
support, or assist in the configuration of NIC Teaming for Heartbeat
communication. Should an issue arise from attempts to use NIC teaming for
Heartbeat communication on the Private Network, it is required to remove the
teamed NICs and attempt to configure the Private Network Links using a single
NIC prior to contact Symantec Enterprise Support for assistance.
|
|
Legacy ID
300382
Article URL http://www.symantec.com/docs/TECH84157
Terms of use for this information are found in Legal Notices
Thank you.