Sun Cluster 3.0-3.1 With Sun StorEdge 6120 Array Manual for Solaris OS

Configuring Storage Arrays

This section contains the procedures about how to configure a storage array in a running cluster. Table 1–2 lists these procedures.

Table 1–2 Task Map: Configuring a Storage Array

Task 

Information 

Create a LUN 

How to Create a Logical Volume

Remove a LUN 

How to Remove a Logical Volume

The following is a list of administrative tasks that require no cluster-specific procedures. See the Sun StorEdge 6020 and 6120 Array System Manual for the following procedures.

ProcedureHow to Create a Logical Volume

Use this procedure to create a logical volume from unassigned storage capacity.


Note –

Sun storage documentation uses the following terms:

This manual uses logical volume to refer to all such logical constructs.


Before You Begin

This procedure relies on the following prerequisites and assumptions.

Steps
  1. Follow the instructions in your storage device's documentation to create and map the logical volume. For a URL to this storage documentation, see Related Documentation.

    • Completely set up the logical volume. When you are finished, the volume must be created, mapped, mounted, and initialized.

    • If necessary, partition the volume.

    • To allow multiple clusters and nonclustered nodes to access the storage device, create initiator groups by using LUN masking.

  2. Are you using multipathing?

  3. Are any devices that are associated with the volume you created at an unconfigured state?


    # cfgadm -al | grep disk
    
    • If no, proceed to Step 4.

    • If yes, configure the Traffic Manager paths on each node that is connected to the storage device.


      cfgadm -o force_update -c configure controllerinstance
      

      For the procedure about how to configure Traffic Manager paths, see the Sun StorEdge Traffic Manager Installation and Configuration Guide.

  4. On one node that is connected to the storage device, use the format command to label the new logical volume.

  5. From any node in the cluster, update the global device namespace.


    # scgdevs
    

    Note –

    You might have a volume management daemon such as vold running on your node, and have a CD-ROM drive connected to the node. Under these conditions, a device busy error might be returned even if no disk is in the drive. This error is expected behavior. You can safely ignore this error message.


  6. To manage this volume with volume management software, use the appropriate Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager commands to update the list of devices on all nodes that are attached to the new volume that you created.

    For more information, see your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation.

See Also

ProcedureHow to Remove a Logical Volume

Use this procedure to remove a logical volume. This procedure defines Node A as the node with which you begin working.


Note –

Sun storage documentation uses the following terms:

This manual uses logical volume to refer to all such logical constructs.


Before You Begin

This procedure relies on the following prerequisites and assumptions.

Steps
  1. Identify the logical volume that you are removing.

    Refer to your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation for more information.

  2. (Optional) Migrate all data off the logical volume that you are removing. Alternatively, back up that data.

  3. Check if the logical volume that you are removing is a quorum device.


    # scstat -q
    

    If yes, choose and configure another device as the quorum device. Then remove the old quorum device.

    For procedures about how to add and remove quorum devices, see Chapter 5, Administering Quorum, in Sun Cluster System Administration Guide for Solaris OS.

  4. If you are using volume management software, use that software to update the list of devices on all nodes that are attached to the logical volume that you are removing.

    For instructions about how to update the list of devices, see your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation.

  5. If you are using volume management software, run the appropriate Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager commands to remove the logical volume from any diskset or disk group.

    For more information, see your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation.


    Note –

    Volumes that were managed by VERITAS Volume Manager must be completely removed from VERITAS Volume Manager control before you can delete them from the Sun Cluster environment. After you delete the volume from any disk group, use the following commands on both nodes to remove the volume from VERITAS Volume Manager control.


    # vxdisk offline Accessname
    # vxdisk rm Accessname
    
    Accessname

    Disk access name


  6. If you are using multipathing, unconfigure the volume in Sun StorEdge Traffic Manager.


    # cfgadm -o force_update -c unconfigure Logical_Volume
    
  7. Access the storage device and remove the logical volume.

    For the procedure about how to remove the volume, see your storage documentation. For a list of storage documentation, see Related Documentation.

  8. Determine the resource groups and device groups that are running on all nodes.

    Record this information because you use it in Step 13 of this procedure to return resource groups and device groups to these nodes.


    # scstat
    
  9. Move all resource groups and device groups off Node A.


    # scswitch -s -h from-node
    
  10. Shut down and reboot Node A.

    For the procedure about how to shut down and power off a node, see Chapter 3, Shutting Down and Booting a Cluster, in Sun Cluster System Administration Guide for Solaris OS.

  11. On Node A, remove the paths to the logical volume that you removed. Remove obsolete device IDs.


    # devfsadm -C
    # scdidadm -C
    
  12. For each additional node that is connected to the shared storage that hosted the logical volume, repeat Step 8 to Step 11.

  13. (Optional) Return the resource groups and device groups that you identified in Step 8 to all cluster nodes.