How to Configure Quorum Devices
-
Quorum servers – To configure a quorum server as a quorum device, do the following:
-
Install the Oracle Solaris Cluster Quorum Server software on the quorum server host machine and start the quorum server. For information about installing and starting the quorum server, see How to Install and Configure Oracle Solaris Cluster Quorum Server Software.
-
Ensure that network switches that are directly connected to cluster nodes meet one of the following criteria:
-
The switch supports Rapid Spanning Tree Protocol (RSTP).
-
Fast port mode is enabled on the switch.
One of these features is required to ensure immediate communication between cluster nodes and the quorum server. If this communication is significantly delayed by the switch, the cluster interprets this prevention of communication as loss of the quorum device.
-
-
Have available the following information:
-
A name to assign to the configured quorum device
-
The IP address of the quorum server host machine
-
The port number of the quorum server
-
-
-
NAS devices – To configure a network-attached storage (NAS) device as a quorum device, do the following:
-
Install the NAS device hardware and software. See Managing Network-Attached Storage Devices in an Oracle Solaris Cluster 4.4 Environment and your device documentation for requirements and installation procedures for NAS hardware and software.
-
Note:
You do not need to configure quorum devices in the following circumstances:-
You chose automatic quorum configuration during Oracle Solaris Cluster software configuration.
-
You installed a single-node global cluster.
-
You added a node to an existing global cluster and already have sufficient quorum votes assigned.
Perform this procedure one time only, after the new cluster is fully formed. Use this procedure to assign quorum votes and then to remove the cluster from installation mode.
Next Steps
Verify the quorum configuration and that installation mode is disabled. Go to How to Verify the Quorum Configuration and Installation Mode.
Troubleshooting
scinstall fails to perform an automatic configuration – If scinstall
fails to automatically configure a shared disk as a quorum device, or If the cluster's installmode
state is still enabled
, you can configure a quorum device and reset installmode
by using the clsetup
utility after the scinstall
processing is completed.
Interrupted clsetup processing – If the quorum setup process is interrupted or fails to be completed successfully, rerun clsetup
.
Changes to quorum vote count – If you later increase or decrease the number of node attachments to a quorum device, the quorum vote count is not automatically recalculated. You can reestablish the correct quorum vote by removing each quorum device and then adding it back into the configuration, one quorum device at a time. For a two-node cluster, temporarily add a new quorum device before you remove and add back the original quorum device. Then remove the temporary quorum device. See How to Modify a Quorum Device Node List in Administering an Oracle Solaris Cluster 4.4 Configuration.
Unreachable quorum device – If you see messages on the cluster nodes that a quorum device is unreachable or if you see failures of cluster nodes with the message CMM: Unable to acquire the quorum device, there might be a problem with the quorum device or the path to it. Check that both the quorum device and the path to it are functional.
If the problem persists, use a different quorum device. Or, if you want to use the same quorum device, increase the quorum timeout to a high value, as follows:
Note:
For Oracle RAC (Oracle RAC), do not change the default quorum timeout of 25 seconds. In certain split-brain scenarios, a longer timeout period might lead to the failure of Oracle RAC VIP failover, due to the VIP resource timing out. If the quorum device being used is not conforming with the default 25–second timeout, use a different quorum device.-
Assume the root role.
-
On each cluster node, edit the
/etc/system
file as the root role to set the timeout to a high value.The following example sets the timeout to 700 seconds.
phys-schost# pfedit /etc/system … set cl_haci:qd_acquisition_timer=700
-
From one node, shut down the cluster.
phys-schost-1# cluster shutdown -g0 -y
-
Boot each node back into the cluster.
Changes to the
/etc/system
file are initialized after the reboot.