test

Open HA Cluster Installation Guide

ProcedureHow to Configure Quorum Devices

Note –

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

If you intend to configure a quorum server as a quorum device, do the following:

  1. If you intend to use a quorum server and the public network uses variable-length subnetting, also called Classless Inter-Domain Subnetting (CIDS), on each node of the cluster modify netmask file entries for the public network.

    If you use classful subnets, as defined in RFC 791, you do not need to perform this step.

    1. Add to the /etc/inet/netmasks file an entry for each public subnet that the cluster uses.

      The following is an example entry that contains a public-network IP address and netmask:


      10.11.30.0	255.255.255.0

    2. Append netmask + broadcast + to the hostname entry in each /etc/hostname.adapter file.


      nodename netmask + broadcast +

  2. On one node, become superuser.

    Alternatively, if your user account is assigned the Primary Administrator profile, execute commands as non-root through a profile shell, or prefix the command with the pfexec command.

  3. To use a shared disk as a quorum device, verify device connectivity to the cluster nodes and choose the device to configure.

    1. From one node of the cluster, display a list of all the devices that the system checks.

      You do not need to be logged in as superuser to run this command.


      phys-schost-1# /usr/cluster/bin/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
…

    2. Ensure that the output shows all connections between cluster nodes and storage devices.

    3. Determine the global device-ID name of each shared disk that you are configuring as a quorum device.

      Note –

      Any shared disk that you choose must be qualified for use as a quorum device.

      Use the scdidadm output from Step a to identify the device–ID name 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.

  4. To use a shared disk that does not support the SCSI protocol, ensure that fencing is disabled for that shared disk.

    1. Display the fencing setting for the individual disk.


      phys-schost# /usr/cluster/bin/cldevice show device

=== DID Device Instances ===
DID Device Name:                                      /dev/did/rdsk/dN
…
  default_fencing:                                     nofencing
…

      • If fencing for the disk is set to nofencing or nofencing-noscrub, fencing is disabled for that disk. Go to Step 5.

      • If fencing for the disk is set to pathcount or scsi, disable fencing for the disk. Skip to Step c.

      • If fencing for the disk is set to global, determine whether fencing is also disabled globally. Proceed to Step b.

        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 c to disable fencing for the individual disk.

    2. Determine whether fencing is disabled globally.


      phys-schost# /usr/cluster/bin/cluster show -t global

=== Cluster ===
Cluster name:                                         cluster
…
   global_fencing:                                      nofencing
…

      • If global fencing is set to nofencing or nofencing-noscrub, fencing is disabled for the shared disk whose default_fencing property is set to global. Go to Step 5.

      • If global fencing is set to pathcount or prefer3, disable fencing for the shared disk. Proceed to Step c.

      Note –

      If an individual disk has its default_fencing property set to global, the fencing for that individual disk is disabled only while the cluster-wide global_fencing property is set to nofencing or nofencing-noscrub. If the global_fencing property is changed to a value that enables fencing, then fencing becomes enabled for all disks whose default_fencing property is set to global.

    3. Disable fencing for the shared disk.


      phys-schost# /usr/cluster/bin/cldevice set \
-p default_fencing=nofencing-noscrub device

    4. Verify that fencing for the shared disk is now disabled.


      phys-schost# /usr/cluster/bin/cldevice show device

  5. Start the clsetup utility.


    phys-schost# /usr/cluster/bin/clsetup

    The Initial Cluster Setup screen is displayed.

    Note –

    If the Main Menu is displayed instead, initial cluster setup was already successfully performed. Skip to Step 10.

  6. At the prompt Do you want to add any quorum disks?, type Yes.

  7. Specify what type of device you want to configure as a quorum device.

    Note –

    NAS devices are not a supported option for quorum devices in an Open HA Cluster 2009.06 configuration. Reference to NAS devices in the following table are for information only.

    Quorum Device Type 

    Description 

    shared_disk

    Sun NAS device or shared disk 

    quorum_server

    Quorum server 

    netapp_nas

    Network Appliance NAS device 

  8. Specify the name of the device to configure as a quorum device.

    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

  9. At the prompt Is it okay to reset "installmode"?, type Yes.

    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.

  10. Quit the clsetup utility.

Next Steps

Verify the quorum configuration and that installation mode is disabled. Go to How to Verify the Quorum Configuration and Installation Mode.

Troubleshooting

Interrupted clsetup processing - If the quorum setup process is interrupted or fails to be completed successfully, rerun clsetup.