How to Remove a Node From a Disk Device Group (Solstice DiskSuite/Solaris Volume Manager)

Use this procedure to remove a cluster node from the list of potential primaries of a Solstice DiskSuite/Solaris Volume Manager disk device group. Repeat the metaset command for each disk device group from which you want to remove the node.

1. Verify that the node is still a member of the group and that the group is an SDS/SVM device group.

   Device group type SDS/SVM indicates a Solstice DiskSuite/Solaris Volume Manager disk device group.

   phys-schost-1% scconf -pv | grep '(global-galileo)' (global-galileo) Device group type: SDS/SVM (global-galileo) Device group failback enabled: no (global-galileo) Device group node list: phys-schost-1, phys-schost-2 (global-galileo) Diskset name: global-galileo phys-schost-1%

   
   

2. Determine which node is the current primary for the device group.

   # scstat -D

   
   

3. Become superuser on the node that currently owns the disk device group that you want to modify.

4. Delete the node's hostname from the disk device group.

   # metaset -s setname -d -h nodelist

   
   

   -s setname	Specifies the disk device group name
   -d	Deletes from the disk device group the nodes identified with -h
   -h nodelist	Removes the node from the list of nodes that can master the disk device group

   ---

   Note - The update can take several minutes to complete.

   ---

   If the command fails, add the -f (Force) option to the command.

   # metaset -s setname -d -f -h nodelist

   
   

5. Repeat Step 4 for each disk device group from which the node is being removed as a potential primary.

6. Verify that the node has been removed from the disk device group.

   The disk device group name matches the diskset name that is specified with metaset.

   phys-schost-1% scconf -pv |grep Device group node list: phys-schost-1, phys-schost-2, phys-schost-1%

   
   

Example--Removing a Node From a Disk Device Group (Solstice DiskSuite/Solaris Volume Manager)

The following example shows the removal of the host name phys-schost-2 from a disk device group configuration. This example eliminates phys-schost-2 as a potential primary for the designated disk device group. Verify removal of the node by running the scstat -D command. Check that the removed node is no longer displayed in the screen text.

[Determine the Solstice DiskSuite/Solaris Volume Manager
 disk device group(2) for the node:]
# scconf -pv | grep Device
  Device group name:                 dg-schost-1
    Device group type:               SDS/SVM
    Device group failback enabled:   no
    Device group node list:          phys-schost-1, phys-schost-2
    Device group ordered node list:  yes
    Device group diskset name:    	         dg-schost-1
[Determine the disk device group(s) for the node:]
# scstat -D
  -- Device Group Servers --
                       Device Group  Primary        Secondary
                       ------------  -------        ---------
  Device group servers: dg-schost-1  phys-schost-1  phys-schost-2
[Become superuser.]
[Remove the hostname from the disk device group:]
# metaset -s dg-schost-1 -d -h phys-schost-2
[Verify removal of the node:]
phys-schost-1% scconf -pv |grep
 Device Group Servers --
                       Device Group  Primary        Secondary
                       ------------  -------        ---------
Device group node list: dg-schost-1, phys-schost-2,  

How to Create More Than Three Disksets in a Cluster

If you intend to create more than three disksets in the cluster, perform the following steps before you create the disksets. Follow these steps if you are installing disksets for the first time or if you are adding more disksets to a fully configured cluster.

1. Ensure that the value of the md_nsets variable is high enough. The value should accommodate the total number of disksets you intend to create in the cluster.

   1. On any node of the cluster, check the value of the md_nsets variable in the /kernel/drv/md.conf file.

   2. If the number of disksets in the cluster will be greater than the existing value of md_nsets minus one, increase the value of md_nsets on each node.

      The maximum permissible number of disksets is the value of md_nsets minus one. The maximum possible value of md_nsets is 32.

   3. Ensure that the /kernel/drv/md.conf file is identical on each node of the cluster.

      ---

      Caution - Failure to follow this guideline can result in serious Solstice DiskSuite/Solaris Volume Manager errors and possible loss of data.

      ---

   4. From one node, shut down the cluster.

      # scshutdown -g0 -y

      
      

   5. Reboot each node in the cluster.

      • 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

        
        

2. On each node in the cluster, run the devfsadm(1M) command.

   You can run this command on all nodes in the cluster at the same time.

3. From one node of the cluster, run the scgdevs(1M) command.

4. On each node, verify that the scgdevs command has completed before you attempt to create any disksets.

   The scgdevs command calls itself remotely on all nodes, even when the command is run from just one node. To determine whether the scgdevs command has completed processing, run the following command on each node of the cluster.

   % ps -ef | grep scgdevs