Where to Go From Here
For an overall list of tasks for adding a cluster node, see Table 7-2, "Task Map: Adding a Cluster Node."
To add a node to an existing resource group, see the Sun Cluster 3.1 Data Service Planning and Administration Guide.
How to Remove a Node From the Cluster Software Configuration
Perform this procedure to remove a node from the cluster.
Be sure you have correctly completed all prerequisite tasks listed in the "Removing a Cluster Node" task map in Adding and Removing a Cluster Node.
Note - Be sure you have removed the node from all resource groups, disk device groups, and quorum device configurations and placed it in maintenance state before you continue with this procedure.
Become superuser on a node in the cluster other than the node to remove.
Remove the node from the cluster.
# scconf -r -h node=node-name
Verify the node removal by using scstat(1M).
# scstat -n
Do you intend to uninstall Sun Cluster software from the removed node?
If yes, go to How to Uninstall Sun Cluster Software From a Cluster Node. Or instead, you can reinstall Solaris software on the node.
If no, to physically remove the node from the cluster, remove the hardware connections as described in the Sun Cluster 3.x Hardware Administration Manual .
Example--Removing a Node From the Cluster Software Configuration
This example shows how to remove a node (phys-schost-2) from a cluster. All commands are run from another node of the cluster (phys-schost-1).
[Remove the node from the cluster:]
phys-schost-1# scconf -r -h node=phys-schost-2
[Verify node removal:]
phys-schost-1# scstat -n
-- Cluster Nodes --
Node name Status
--------- ------
Cluster node: phys-schost-1 Online
|
Where to Go From Here
To uninstall Sun Cluster software from the removed node, see How to Uninstall Sun Cluster Software From a Cluster Node
For hardware procedures, see theSun Cluster 3.x Hardware Administration Manual .
For an overall list of tasks for removing a cluster node, see Table 7-3.
To add a node to an existing cluster, see How to Add a Node to the Authorized Node List.
How to Remove Connectivity Between an Array and a Single Node, in a
Cluster With Greater Than Two-Node Connectivity
Use this procedure to detach a storage array from a single cluster node, in a cluster that has three- or four-node connectivity.
Back up all database tables, data services, and volumes that are associated with the storage array that you are removing.
Determine the resource groups and device groups that are running on the node to be disconnected.
# scstat
If necessary, move all resource groups and device groups off the node to be disconnected.
Caution - If your cluster is running OPS/RAC
software, shut down the OPS/RAC database instance that is running on the node
before you move the groups off the node. For instructions see the Oracle Database Administration Guide.# scswitch -S -h from-node
Put the device groups into maintenance state.
For the procedure on acquiescing I/O activity to Veritas shared disk groups, see your VERITAS Volume Manager documentation.
For the procedure on putting a device group in maintenance state, see the "Administering the Cluster" in Sun Cluster 3.1 10/03 System Administration Guide.
Remove the node from the device groups.
If you use VERITAS Volume Manager or raw disk, use the scconf(1M) command to remove the device groups.
If you use Solstice DiskSuite, use the metaset command to remove the device groups.
If the cluster is running HAStorage or HAStoragePlus, remove the node from the resource group's nodelist.
# scrgadm -a -g resource-group -h nodelist
See the Sun Cluster 3.1 Data Service Planning and Administration Guide for more information on changing a resource group's nodelist.
Note - Resource type, resource group, and resource property names are case insensitive when executing scrgadm.
If the storage array you are removing is the last storage array that is connected to the node, disconnect the fiber-optic cable between the node and the hub or switch that is connected to this storage array (otherwise, skip this step).
Do you want to remove the host adapter from the node you are disconnecting?
If yes, shut down and power off the node.
If no, skip to Step 11.
Remove the host adapter from the node.
For the procedure on removing host adapters, see the documentation that shipped with your node.
Without allowing the node to boot, power on the node.
Boot the node into non-cluster mode.
ok boot -x
Caution - The node must be in non-cluster mode
before you remove OPS/RAC software in the next step or the node will panic
and potentially cause a loss of data availability.If OPS/RAC software has been installed, remove the OPS/RAC software package from the node that you are disconnecting.
# pkgrm SUNWscucm
Caution - If you do not remove the OPS/RAC software
from the node you disconnected, the node will panic when the node is reintroduced
to the cluster and potentially cause a loss of data availability.Boot the node into cluster mode.
ok> boot
On the node, update the device namespace by updating the /devices and /dev entries.
# devfsadm -C # scdidadm -C
Bring the device groups back online.
For procedures on bringing a VERITAS shared disk group online, see your VERITAS Volume Manager documentation.
For the procedure on bringing a device group online, see the procedure on putting a device group into maintenance state.