This chapter contains the procedures about how to install and configure a Sun StorEdgeTM 6130 array. These procedures are specific to a SunTM Cluster environment.
This chapter contains the following main topics:
For detailed information about storage array architecture, features, configuration utilities, and installation, see the Sun StorEdge 6130 Array Getting Started Guide.
For a URL to this storage documentation, see Related Documentation.
This section contains the procedures listed in Table 2–1.
Table 2–1 Task Map: Installing Storage Arrays
Task |
Information |
---|---|
Install a storage array in a new cluster, before the OS and Sun Cluster software are installed. | |
Add a storage array to an existing cluster. |
You can install your storage array in several different configurations: Figure 2–1 and Figure 2–2 are two examples.
Use this procedure to install a storage array in a new cluster. To add a storage array to an existing cluster, use the procedure in How to Add Storage Arrays to an Existing Cluster.
This procedure relies on the following assumptions:
You have not installed the Solaris Operating System.
You have not installed the Sun Cluster software.
Your cluster has not been established.
You have enough host adapters to connect the nodes and the storage array to the service processor panel.
If you need to install host adapters, see How to Replace a Host Adapter. When this procedure asks you to replace the failed host adapter, simply install the new host adapter instead.
Unpack, place, and level the storage array.
For instructions, see the Sun StorEdge 6130 Array Getting Started Guide or the Sun StorEdge online documentation. For a list of array documentation, see Table P–2.
(Optional) Install the Fibre Channel (FC) switch for the storage array if you do not have a switch installed.
For the procedure about how to install an FC switch, see the documentation that shipped with your FC switch hardware.
Connect the nodes to the service processor panel.
(SAN Configuration) Connect the FC switches to the service processor panel.
(Direct-Attached Configuration) Connect each node to the host ports on the array.
For instructions, see the Sun StorEdge 6130 Array Getting Started Guide or the Sun StorEdge online documentation.
Install the storage array.
For instructions, see the Sun StorEdge 6130 Array Getting Started Guide or the Sun StorEdge online documentation.
Power on the storage array and the nodes.
For instructions, see the Sun StorEdge 6130 Array Getting Started Guide or the Sun StorEdge online documentation.
On all nodes, install the Solaris operating system and apply the required Solaris patches for Sun Cluster software and storage array support.
For the procedure about how to install the Solaris operating environment, see How to Install Solaris Software in Sun Cluster Software Installation Guide for Solaris OS.
If you are using Solaris OS software version 8 or version 9, install any required patches or software for Sun StorEdge Traffic Manager software support to nodes and enable multipathing.
For the procedure about how to install the Sun StorEdge Traffic Manager software, see How to Install Sun Multipathing Software in Sun Cluster Software Installation Guide for Solaris OS.
To create a logical volume, see How to Create a Logical Volume.
To continue with Sun Cluster software installation tasks, see your Sun Cluster software installation documentation.
Use this procedure to add a new storage array to a running cluster. To install a new storage array in a Sun Cluster configuration that is not running, use the procedure in How to Install Storage Arrays in a New Cluster.
This procedure relies on the following assumptions:
(VERITAS Volume Manager Only) You have a version of VERITAS Volume Manager that includes Array Support Library (ASL). For more information on this requirement, see Requirements.
You have enough host adapters to connect the nodes and the storage array to the service processor panel.
If you need to install host adapters, see How to Replace a Host Adapter. When this procedure asks you to replace the failed host adapter, simply install the new host adapter instead.
You do not need to install a new node in your cluster.
If you need to add a node to your cluster, see your Sun Cluster system administration documentation. Ensure that you install the required Solaris patches for storage array support.
Unpack, place, and level the storage array.
For instructions, see the Sun StorEdge 6130 Array Getting Started Guide or the Sun StorEdge online documentation. For a list of array documentation, see Table P–2.
(Optional) Install the Fibre Channel (FC) switch for the storage array if you do not have a switch installed.
For the procedure about how to install an FC switch, see the documentation that shipped with your FC switch hardware.
Connect the nodes to the service processor panel.
(SAN Configuration) Connect the FC switches to the service processor panel.
(Direct-Attached Configuration) Connect each node to the host ports on the array.
For instructions, see the Sun StorEdge 6130 Array Getting Started Guide or the Sun StorEdge online documentation.
Install the storage array.
For instructions, see the Sun StorEdge 6130 Array Getting Started Guide or the Sun StorEdge online documentation.
Power on the storage array and the nodes.
For instructions, see the Sun StorEdge 6130 Array Getting Started Guide or the Sun StorEdge online documentation.
To create a logical volume, see How to Create a Logical Volume.
If you added a new node, perform the steps in Install the Solaris Operating System and Configure Multipathing as appropriate. Apply the correct patches for storage array support enable multipathing.
This section contains the procedures about how to configure a storage array in a running cluster. Table 2–2 lists these procedures.
Table 2–2 Task Map: Configuring a Storage Array
Task |
Information |
---|---|
Create a logical volume. | |
Remove a logical volume. |
The following is a list of administrative tasks that require no cluster-specific procedures. See the storage array's online help for the following procedures.
Use this procedure to create a logical volume from unassigned storage capacity.
Sun storage documentation uses the following terms:
Logical volume
Logical device
Logical unit number (LUN)
This manual uses logical volume to refer to all such logical constructs.
This procedure relies on the following prerequisites and assumptions.
All nodes are booted in cluster mode and attached to the storage device.
The storage device is installed and configured. If you are using multipathing, the storage devices is configured as described in the installation procedure.
If you are using Sun StorEdge Traffic Manager, it is installed and configured and the path between Traffic Manager and the storage device is functioning.
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.
Are you using multipathing?
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.
On one node that is connected to the storage device, use the format command to label the new logical volume.
From any node in the cluster, update the global device namespace.
# scgdevs |
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.
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.
To configure a logical volume as a quorum device, see Chapter 5, Administering Quorum, in Sun Cluster System Administration Guide for Solaris OS.
To create a new resource or configure a running resource to use the new logical volume, see Chapter 2, Administering Data Service Resources, in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
Use this procedure to remove a logical volume. This procedure defines Node A as the node with which you begin working.
Sun storage documentation uses the following terms:
Logical volume
Logical device
Logical unit number (LUN)
This manual uses logical volume to refer to all such logical constructs.
This procedure relies on the following prerequisites and assumptions.
All nodes are booted in cluster mode and attached to the storage device.
The logical volume and the path between the nodes and the storage device are both operational.
Identify the logical volume that you are removing.
Refer to your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation for more information.
(Optional) Migrate all data off the logical volume that you are removing. Alternatively, back up that data.
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.
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.
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.
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 |
Disk access name
If you are using multipathing, unconfigure the volume in Sun StorEdge Traffic Manager.
# cfgadm -o force_update -c unconfigure Logical_Volume |
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.
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 |
Move all resource groups and device groups off Node A.
# scswitch -s -h from-node |
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.
On Node A, remove the paths to the logical volume that you removed. Remove obsolete device IDs.
# devfsadm -C # scdidadm -C |
For each additional node that is connected to the shared storage that hosted the logical volume, repeat Step 8 to Step 11.
(Optional) Return the resource groups and device groups that you identified in Step 8 to all cluster nodes.