sun.com   |  docs.sun.com
How To Buy  |   My Sun  |   Worldwide Sites
        
 
Sun Microsystems
 Products & Services
 		 Support & Training
 
 
Sun Cluster System Administration Guide for Solaris OS >> 7.  Administering the Cluster >> Adding and Removing a Cluster Node >> How to Add a Node to the Authorized Node List 

Previous Previous     Contents     Index     Next Next

Example--Adding a Cluster Node to the Authorized Node List

The following example shows how to add a node named phys-schost-3 to the authorized node list in an existing cluster.

[Become superuser and execute the scsetup utility.]
# scsetup
Select New nodes>Specify the name of a machine which may add itself.
Answer the questions when prompted.
Verify that the scconf command completed successfully.
 
scconf -a -T node=phys-schost-3
 
    Command completed successfully.
Select Prevent any new machines from being added to the cluster.
Quit the scsetup New Nodes Menu and Main Menu.
[Install the cluster software.]

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 Data Services Planning and Administration Guide for Solaris OS.

ProcedureHow to Remove a Node From the Cluster Software Configuration

Perform this procedure to remove a node from the cluster.

  1. 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.

  2. Become superuser on a node in the cluster other than the node to remove.

  3. Remove the node from the cluster.
    # scconf -r -h node=node-name

  4. Verify the node removal by using scstat(1M).
    # scstat -n

  5. 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 Hardware Administration Manual for Solaris OS .

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 Hardware Administration Manual for Solaris OS .

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.

ProcedureHow 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.

  1. Back up all database tables, data services, and volumes that are associated with the storage array that you are removing.

  2. Determine the resource groups and device groups that are running on the node to be disconnected.

    # scstat

  3. If necessary, move all resource groups and device groups off the node to be disconnected.

    <b>Caution (SPARC only) - </b> Caution (SPARC only) - If your cluster is running Oracle Parallel Server/Real Application Clusters software, shut down the Oracle Parallel Server/Real Application Clusters 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

  4. 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".

  5. 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.

  6. 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 Data Services Planning and Administration Guide for Solaris OS 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.

  7. 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).

  8. 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.

  9. Remove the host adapter from the node.

    For the procedure on removing host adapters, see the documentation that shipped with your node.

  10. Without allowing the node to boot, power on the node.

  11. Boot the node into non-cluster mode.

    • SPARC: 
      ok boot -x

    • x86: 
                            <<< Current Boot Parameters >>>
Boot path: /pci@0,0/pci8086,2545@3/pci8086,1460@1d/pci8086,341a@7,1/
sd@0,0:a
Boot args:

Type    b [file-name] [boot-flags] <ENTER>  to boot with options
or      i <ENTER>                           to enter boot interpreter
or      <ENTER>                             to boot with defaults

                  <<< timeout in 5 seconds >>>
Select (b)oot or (i)nterpreter: b -x

    <b>Caution (SPARC only) - </b> Caution (SPARC only) - The node must be in non-cluster mode before you remove Oracle Parallel Server/Real Application Clusters software in the next step or the node panics and potentially causes a loss of data availability.

  12. SPARC: If Oracle Parallel Server/Real Application Clusters software has been installed, remove the Oracle Parallel Server/Real Application Clusters software package from the node that you are disconnecting.

    # pkgrm SUNWscucm

    <b>Caution (SPARC only) - </b> Caution (SPARC only) - If you do not remove the Oracle Parallel Server/Real Application Clusters 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.

  13. Boot the node into cluster mode.

    • SPARC: 
      ok boot

    • x86: 
                            <<< Current Boot Parameters >>>
Boot path: /pci@0,0/pci8086,2545@3/pci8086,1460@1d/pci8086,341a@7,1/
sd@0,0:a
Boot args:

Type    b [file-name] [boot-flags] <ENTER>  to boot with options
or      i <ENTER>                           to enter boot interpreter
or      <ENTER>                             to boot with defaults

                  <<< timeout in 5 seconds >>>
Select (b)oot or (i)nterpreter: b

  14. On the node, update the device namespace by updating the /devices and /dev entries.

    # devfsadm -C 
# scdidadm -C

  15. Bring the device groups back online.

    For procedures about 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.

Previous Previous     Contents     Index     Next Next
 
Copyright 1994-2004 Sun Microsystems