HP Serviceguard Quorum Server Version A.03.00 Release Notes, December 2007

HP Serviceguard Quorum Server Version A.03.00 Release Notes
System Requirements and Recommendations
Chapter 1 11
Network Recommendations
Ideally the Quorum Server and the cluster or clusters it serves
should communicate over a subnet that does not handle other traffic.
(If you are using a version of Serviceguard that supports more than
one subnet for communication with the Quorum Server, this should
be true of both subnets.) This helps to ensure that the Quorum
Server is available when it is needed.
If this is not practical, or if the communication must cover a long
distance (for example, if the Quorum Server is serving an Extended
Distance cluster) heavy network traffic or network delays could
cause Quorum Server timeouts. You can reduce the likelihood of
timeouts by increasing the Quorum Server timeout interval; use the
QS_TIMEOUT_EXTENSION parameter in the cluster configuration file.
See “Configuring Serviceguard to Use the Quorum Server” on
page 18 and “Setting Quorum Server Parameters in the Cluster
Configuration File” on page 20.
If a subnet that connects the Quorum Server to a cluster is also used
for the cluster heartbeat, configure the heartbeat on at least one
other network, so that both Quorum Server and heartbeat
communication are not likely to fail at the same time.