Go to main content

Administering an Oracle® Solaris Cluster 4.4 Configuration

Exit Print View

Updated: November 2019

How to Put a Node Into Maintenance State

Put a global-cluster node into maintenance state when taking the node out of service for an extended period of time. This way, the node does not contribute to the quorum count while it is being serviced. To put a node into maintenance state, the node must be shut down with the clnode evacuate and shutdown commands. For more information, see the clnode(8CL) and cluster(8CL) man pages.

Note -  You can also use the Oracle Solaris Cluster Manager browser interface to evacuate a node and switch all resource groups and device groups to the next-preferred node. For Oracle Solaris Cluster Manager log-in instructions, see How to Access Oracle Solaris Cluster Manager.

When a cluster node is shut down and put in maintenance state, all quorum devices that are configured with ports to the node have their quorum vote counts decremented by one. The node and quorum device vote counts are incremented by one when the node is removed from maintenance mode and brought back online.

Note -  The Oracle Solaris shutdown command shuts down a single node, while the cluster shutdown command shuts down the entire cluster.

Use the clquorum disable command from another node that is still a cluster member to put a cluster node into maintenance state. For more information, see the clquorum(8CL) man page.

The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.

This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.

  1. Assume the root role or a role that provides solaris.cluster.modify authorization on the global-cluster node that you are putting into maintenance state.
  2. Evacuate any resource groups and device groups from the node.

    The clnode evacuate command switches over all resource groups and device groups from the specified node to the next-preferred node.

    phys-schost# clnode evacuate node
  3. Shut down the node that you evacuated.
    phys-schost# shutdown -g0 -y -i0
  4. Assume a role that provides solaris.cluster.modify authorization on another node in the cluster and put the node that you shut down in Step 3 in maintenance state.
    phys-schost# clquorum disable node
  5. Verify that the global-cluster node is now in maintenance state.
    phys-schost# clquorum status node

    The node that you put into maintenance state should have a Status of offline and 0 (zero) for Present and Possible quorum votes.

Example 76  Putting a Global-Cluster Node Into Maintenance State

The following example puts a cluster node into maintenance state and verifies the results. The clnode status output shows the Node votes for phys-schost-1 to be 0 (zero) and the status to be Offline. The Quorum Summary should also show reduced vote counts. Depending on your configuration, the Quorum Votes by Device output might indicate that some quorum disk devices are offline as well.

[On the node to be put into maintenance state:]
phys-schost-1# clnode  evacuate phys-schost-1
phys-schost-1# shutdown -g0 -y -i0

[On another node in the cluster:]
phys-schost-2# clquorum disable phys-schost-1
phys-schost-2# clquorum status phys-schost-1

-- Quorum Votes by Node --

Node Name           Present       Possible       Status
---------           -------       --------       ------
phys-schost-1       0             0              Offline
phys-schost-2       1             1              Online
phys-schost-3       1             1              Online

See Also

To bring a node back online, see How to Bring a Node Out of Maintenance State.