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.
If you chose automatic quorum configuration when you established the cluster, do not perform this procedure. Instead, proceed to How to Verify the Quorum Configuration and Installation Mode.
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.
Before You Begin
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 Oracle Solaris Cluster With Network-Attached Storage Device Manual and your device documentation for requirements and installation procedures for NAS hardware and software.
You intend to use a quorum server.
The public network uses variable-length subnet masking, also called classless inter domain routing (CIDR).
# ipadm show-addr ADDROBJ TYPE STATE ADDR lo0/v4 static ok 127.0.0.1/8 ipmp0/v4 static ok 10.134.94.58/24
Alternatively, if your user account is assigned the System Administrator profile, issue commands as non-root through a profile shell, or prefix the command with the pfexec command.
phys-schost# cluster status -t node
You do not need to be logged in as the root role to run this command.
phys-schost-1# cldevice list -v
Output resembles the following:
DID Device Full Device Path ---------- ---------------- d1 phys-schost-1:/dev/rdsk/c0t0d0 d2 phys-schost-1:/dev/rdsk/c0t6d0 d3 phys-schost-2:/dev/rdsk/c1t1d0 d3 phys-schost-1:/dev/rdsk/c1t1d0 …
Use the cldevice output from Step a to identify the device ID of each shared disk that you are configuring as a quorum device. For example, the output in Step a shows that global device d3 is shared by phys-schost-1 and phys-schost-2.
phys-schost# cldevice show device === DID Device Instances === DID Device Name: /dev/did/rdsk/dN … default_fencing: nofencing …
Alternatively, you can simply disable fencing for the individual disk, which overrides for that disk whatever value the global_fencing property is set to. Skip to Step h to disable fencing for the individual disk.
phys-schost# cluster show -t global === Cluster === Cluster name: cluster … global_fencing: nofencing …
phys-schost# cldevice set \ -p default_fencing=nofencing-noscrub device
phys-schost# cldevice show device
phys-schost# clsetup
The Initial Cluster Setup screen is displayed.
|
For a quorum server, also specify the following information:
The IP address of the quorum server host
The port number that is used by the quorum server to communicate with the cluster nodes
After the clsetup utility sets the quorum configurations and vote counts for the cluster, the message Cluster initialization is complete is displayed. The utility returns you to the Main Menu.
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 the procedure “How to Modify a Quorum Device Node List” in Chapter 6, Administering Quorum, in Oracle Solaris Cluster System Administration Guide .
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:
1. Assume the root role.
2. 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
3. From one node, shut down the cluster.
phys-schost-1# cluster shutdown -g0 -y
4. Boot each node back into the cluster.
Changes to the /etc/system file are initialized after the reboot.