Sun Cluster 3.1 - 3.2 With Network-Attached Storage Devices Manual for Solaris OS

ProcedureHow to Prepare the Cluster for Network Appliance NAS Device Maintenance

Follow the instructions in this procedure whenever the Network Appliance NAS device maintenance you are performing might affect the device's availability to the cluster nodes.

Before You Begin

This procedure provides the long forms of the Sun Cluster commands. Most commands also have short forms. Except for the forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix A, Sun Cluster Object-Oriented Commands, in Sun Cluster 3.1 - 3.2 Hardware Administration Manual for Solaris OS.

To perform this procedure, become superuser or assume a role that provides solaris.cluster.read and solaris.cluster.modify RBAC authorization.

  1. Stop I/O to the NAS device.

  2. On each cluster node, unmount the Network Appliance NAS device directories.

  3. Determine whether a LUN on this Network Appliance NAS device is a quorum device.

    • If you are using Sun Cluster 3.2, use the following command:


      # clquorum show
      
    • If you are using Sun Cluster 3.1, use the following command:


      # scstat -q
      
  4. If no LUNs on this Network Appliance NAS device are quorum devices, you are finished with this procedure.

  5. If a LUN is a quorum device, perform the following steps:

    1. If your cluster uses other shared storage devices, select and configure another quorum device.

    2. Remove this quorum device.

      See Chapter 6, Administering Quorum, in Sun Cluster System Administration Guide for Solaris OS for instructions about adding and removing quorum devices.


      Note –

      If your cluster requires a quorum device (for example, a two-node cluster) and you are maintaining the only shared storage device in the cluster, your cluster is in a vulnerable state throughout the maintenance procedure. Loss of a single node during the procedure causes the other node to panic and your entire cluster becomes unavailable. Limit the amount of time for performing such procedures. To protect your cluster against such vulnerability, add a shared storage device to the cluster.