Maintaining Storage Arrays
This section provides cluster-specific procedures about how to maintain a storage array. See the documentation that shipped with your storage array for general maintenance procedures.
Table 1-1 Task Map: Maintaining a Storage Array
| Task | For Instructions, Go To |
|---|---|
Add an storage array. | |
Remove an storage array. | |
Replace an storage array.
To replace a failed storage array, remove the failed storage array and add a new storage array to the configuration. | |
Replace a chassis. | |
Add a disk drive. | |
Remove a disk drive. | |
Replace a disk drive. | |
Replace an Environmental Service Module (ESM). | |
Upgrade disk drive firmware. | |
Update host adapter firmware. | |
Replace a host adapter card. |
How to Add a Storage Array
Use this procedure to add a storage array to a running cluster. Perform the steps in this procedure in conjunction with the procedures in the Sun Cluster system administration documentation and your server hardware manual.
This procedure uses an updated method for setting the scsi-initiator-id. This new method must be used with the StorEdge PCI Dual Ultra3 SCSI host adapter. If you are adding this storage array to a cluster configuration that uses the previous method of setting the scsi-initiator-id, you will need to update the nvramrc script and set the scsi-initiator-id by using this procedure. The previous method relied on setting each node's scsi-initiator-id for shared storage in the nvramrc script.
Note - To determine if the cluster configuration uses the previous method of setting the scsi-initiator-id, run the following command on the two nodes that you plan to connect to this storage array.
# eeprom scsi-initiator-id |
For conceptual information on multi-initiator SCSI and device IDs, see the Sun Cluster concepts documentation document.
This procedure defines Node 1 as the node with which you begin working. Node 2 is the remaining node.
Verify that the storage array is configured for the split-bus or single-bus configuration.
See the Sun Storage D2 Array Installation, Operation, and Service Manual for procedures about how to configure the ESMs.
Shut down Node 1.
For the procedure about how to shut down and power off a node, see your Sun Cluster system administration documentation.
If necessary, install the host adapters in Node 1.
For the procedure about how to install host adapters, see the documentation that shipped with your host adapters and nodes.
Connect the SCSI cable between Node 1 and the storage array, as shown in Figure 1-3 for split-bus configurations. See Figure 1-4 for the single-bus configuration cabling diagram.
Make sure that the entire bus length that is connected to the storage array is less than 12m. The bus length includes the cables from the ESM to the host adapter. See the documentation that shipped with your hardware for internal bus length.
Figure 1-3 Adding a Split-Bus Configuration: Part I
Figure 1-4 Adding a Single-Bus Configuration: Part I
Ensure that each device in the SCSI chain has a unique SCSI address.
To avoid SCSI-chain conflicts, this procedure instructs you to reserve SCSI address 7 for one host adapter in the SCSI chain and change the other host adapter's global scsi-initiator-id to an available SCSI address. Then the procedure instructs you to change the scsi-initiator-id for local devices back to 7.
Note - A slot in the storage array might not be in use. However, do not set the scsi-initiator-id to a SCSI address for that disk slot. This precaution minimizes future complications if you install additional disk drives.
If necessary, power on the storage devices.
For the procedure on powering on a storage device, see the service manual that shipped with your storage device.
If necessary, power on a node, but do not allow it to boot. If necessary, halt the system to continue with OBP Monitor tasks.
Set the scsi-initiator-id for one node to 6.
{1} ok setenv scsi-initiator-id 6 scsi-initiator-id = 6Find the paths to the host adapters that connect to the local disk drives.
{0} ok show-disksUse this information to change the SCSI addresses in the nvramrc script. Do not include the /sd directories in the device paths.
Edit the nvramrc script to set the scsi-initiator-id for the local devices on the first node to 7.
For a full list of commands, see the OpenBoot 2.x Command Reference Manual.
Caution - Insert exactly one space after the first double quote and before scsi-initiator-id.{0} ok nvedit 0: probe-all 1: cd /pci@1f,4000/scsi@2 2: 7 " scsi-initiator-id" integer-property 3: device-end 4: cd /pci@1f,4000/scsi@3 5: 7 " scsi-initiator-id" integer-property 6: device-end 7: install-console 8: banner[Control C] {0} okStore the changes.
The changes you make through the nvedit command are recorded on a temporary copy of the nvramrc script. You can continue to edit this copy without risk. After you complete your edits, save the changes. If you are not sure about the changes, discard them.
To store the changes, type:
{0} ok nvstore {1} ok
To discard the changes, type:
{0} ok nvquit {1} ok
Verify the contents of the nvramrc script that you created, as shown in the following example.
If the contents of the nvramrc script are incorrect, use the nvedit command to make corrections.
{0} ok printenv nvramrc nvramrc = probe-all cd /pci@1f,4000/scsi@2 7 " scsi-initiator-id" integer-property device-end cd /pci@1f,4000/scsi@3 7 " scsi-initiator-id" integer-property device-end install-console banner {1} okInstruct the OpenBoot PROM (OBP) Monitor to use the nvramrc script, as shown in the following example.
{0} ok setenv use-nvramrc? true use-nvramrc? = true {1} ok
Perform a reconfiguration boot on Node 1 to create the new Solaris device files and links.
If necessary, format and label the disks.
On Node 1, verify that the DIDs have been assigned to the disk drives in the storage array.
# scdidadm -l
Shut down Node 2.
For the procedure about how to shut down and power off a node, see your Sun Cluster system administration documentation.
If necessary, install the host adapters in Node 2.
For the procedure about how to install a host adapter, see the documentation that shipped with your host adapter and node.
Connect the storage array to the host adapters by using SCSI cables.
See Figure 1-5 for a split-bus configuration diagram and Figure 1-6 for a single-bus configuration diagram.
Figure 1-5 Adding a Split-Bus Configuration: Part II
Figure 1-6 Adding a Single-Bus Configuration: Part II
Verify that the scsi-initiator-id is set correctly on the second node.
If necessary, power on the second node, but do not allow it to boot. If necessary, halt the system to continue with OBP Monitor tasks.
Verify that the scsi-initiator-id for each host adapter on the second node is set to 7
Use the show-disks command to find the paths to the host adapters that are connected to these enclosures. Select each host adapter's device tree node, and display the node's properties to confirm that the scsi-initiator-id for each host adapter is set to 7.
{0} ok cd /pci@6,4000/pci@3/scsi@5 {0} ok .properties scsi-initiator-id 00000007 ...
Perform a reconfiguration boot on Node 2 to create the new Solaris device files and links.
On Node 2, verify that the DIDs have been assigned to the disk drives in the storage array.
# scdidadm -L
Perform volume management administration to add the disk drives in the storage array to the volume management configuration.
For more information, see your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation.