Chapter 5 Installing and Maintaining a Sun StorEdge D1000 Disk Array

This chapter provides the procedures for installing and maintaining a Sun StorEdge^TM D1000 disk array.

This chapter contains the following procedures:

• "How to Install a StorEdge D1000 Disk Array"

• "How to Add a Disk Drive in a StorEdge D1000 Disk Array in a Running Cluster"

• "How to Replace a Disk Drive in a StorEdge D1000 Disk Array in a Running Cluster"

• "How to Remove a Disk Drive From a StorEdge D1000 Disk Array in a Running Cluster"

• "How to Add a StorEdge D1000 Disk Array to a Running Cluster"

• "How to Replace a StorEdge D1000 Disk Array in a Running Cluster"

• "How to Remove a StorEdge D1000 Disk Array From a Running Cluster"

For conceptual information on multihost disks, see the Sun Cluster 3.0 U1 Concepts document.

Installing a StorEdge D1000 Disk Array

This section provides the procedure for an initial installation of a StorEdge D1000 disk array.

How to Install a StorEdge D1000 Disk Array

Use this procedure for an initial installation of a StorEdge D1000 disk array, prior to installing the Solaris operating environment and Sun Cluster software. Perform this procedure in conjunction with the procedures in the Sun Cluster 3.0 U1 Installation Guide and your server hardware manual.

Multihost storage in clusters uses the multi-initiator capability of the SCSI specification. For conceptual information on multi-initiator capability, see the Sun Cluster 3.0 U1 Concepts document.

1. Ensure that each device in the SCSI chain has a unique SCSI address.

   The default SCSI address for host adapters is 7. Reserve SCSI address 7 for one host adapter in the SCSI chain. This procedure refers to the host adapter you choose for SCSI address 7 as the host adapter on the "second node."

   To avoid conflicts, in Step 7 you change the scsi-initiator-id of the remaining host adapter in the SCSI chain to an available SCSI address. This procedure refers to the host adapter with an available SCSI address as the host adapter on the "first node." Depending on the device and configuration settings of the device, either SCSI address 6 or 8 is usually available.

   ---

   Note -

   Even though a slot in the disk array might not be in use, do not set the scsi-initiator-id for the first node to the SCSI address for that disk slot. This precaution minimizes future complications if you install additional disk drives.

   ---

   For more information, see the OpenBoot 3.x Command Reference Manual and the labels inside the storage device.

2. Install the host adapters in the node that you are connecting to the StorEdge D1000 disk array.

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

3. Connect the cables to the StorEdge D1000 disk arrays, as shown in Figure 5-1.

   Make sure that the entire bus length that is connected to each StorEdge D1000 disk array is less than 25 m. This measurement includes the cables to both nodes, as well as the bus length internal to each StorEdge D1000 disk array, node, and the host adapter.

   Figure 5-1 Example of a StorEdge D1000 Disk Array Mirrored Pair

   
   

4. Connect the AC power cord for each StorEdge D1000 disk array of the mirrored pair to a different power source.

5. Power on the first node and the StorEdge D1000 disk arrays.

   For the procedure on powering on a StorEdge D1000 disk array, see the Sun StorEdge A1000 and D1000 Installation, Operations, and Service Manual.

6. Find the paths to the host adapters.

   {0} ok show-disks

   Identify and record the two controllers that are to be connected to the storage devices and record these paths. Use this information to change the SCSI addresses of these controllers in the nvramrc script in Step 7. Do not include the /sd directories in the device paths.

7. Edit the nvramrc script to change the scsi-initiator-id for the host adapters on the first node.

   For a list of nvramrc editor and nvedit keystroke commands, see Appendix B, NVRAMRC Editor and NVEDIT Keystroke Commands.

   The following example sets the scsi-initiator-id to 6. The OpenBoot PROM Monitor prints the line numbers (0:, 1:, and so on).

   ---

   Caution -

   Insert exactly one space after the first double quote and before scsi-initiator-id.

   ---

   {0} ok nvedit 0: probe-all 1: cd /sbus@1f,0/QLGC,isp@3,10000 2: 6 encode-int " scsi-initiator-id" property 3: device-end 4: cd /sbus@1f,0/ 5: 6 encode-int " scsi-initiator-id" property 6: device-end 7: install-console 8: banner [Control C] {0} ok

8. Store 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 {0} ok

   • To discard the changes, type:

     {0} ok nvquit {0} ok

9. Verify the contents of the nvramrc script you created in Step 7, 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 /sbus@1f,0/QLGC,isp@3,10000 6 encode-int " scsi-initiator-id" property device-end cd /sbus@1f,0/ 6 encode-int " scsi-initiator-id" property device-end install-console banner {0} ok

10. Instruct 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 {0} ok

11. Power on the second node, but do not allow it to boot. If necessary, halt the system to continue with OBP Monitor tasks.

12. 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 /sbus@1f,0/QLGC,isp@3,10000 {0} ok .properties scsi-initiator-id 00000007 differential isp-fcode 1.21 95/05/18 device_type scsi ...

13. Continue with the Solaris operating environment, Sun Cluster software, and volume management software installation tasks.

    For software installation procedures, see the Sun Cluster 3.0 U1 Installation Guide.

Maintaining a StorEdge D1000 Disk Array

This section provides the procedures for maintaining a StorEdge D1000 disk array. The following table list these procedures.

How to Add a Disk Drive in a StorEdge D1000 Disk Array in a Running Cluster

Use this procedure to add a disk drive to a running cluster. Perform the steps in this procedure in conjunction with the procedures in the Sun Cluster 3.0 U1 System Administration Guide and your server hardware manual. "Example--Adding a StorEdge D1000 Disk Drive" shows how to apply this procedure.

For conceptual information on quorum, quorum devices, global devices, and device IDs, see the Sun Cluster 3.0 U1 Concepts document.

1. Locate an empty disk slot in the StorEdge D1000 disk array for the disk drive you are adding.

   Identify the disk slot in the StorEdge D1000 disk array for the disk drive that you are adding and note the target number. Refer to the documentation that shipped with your StorEdge D1000 disk array.

2. Install the disk drive.

   For the procedure on installing a disk drive, see the Sun StorEdge D1000 Storage Guide.

3. On all nodes attached to the StorEdge D1000 disk array, configure the disk drive.

   # cfgadm -c configure cN # devfsadm

4. On all nodes, verify that entries for the disk drive have been added to the /dev/rdsk directory.

   # ls -l /dev/rdsk

5. If necessary, use the format(1M) command or the fmthard(1M) command to partition the disk drive.

6. From any node, update the global device namespace.

   If a volume management daemon such as vold is running on your node, and you have a CD-ROM drive that is connected to the node, a device busy error might be returned even if no disk is in the drive. This error is an expected behavior.

   # scgdevs

7. On all nodes, verify that a device ID (DID) has been assigned to the disk drive.

   # scdidadm -l

   ---

   Note -

   As shown in "Example--Adding a StorEdge D1000 Disk Drive", the DID 35 that is assigned to the new disk drive might not be in sequential order in the disk array.

   ---

8. Perform volume management administration to add the new disk drive to the configuration.

   For more information, see your Solstice DiskSuite^TM or VERITAS Volume Manager documentation.

Example--Adding a StorEdge D1000 Disk Drive

The following example shows how to apply the procedure for adding a StorEdge D1000 disk array disk drive.

# scdidadm -l
16       phys-circinus-3:/dev/rdsk/c2t0d0 /dev/did/rdsk/d16    
17       phys-circinus-3:/dev/rdsk/c2t1d0 /dev/did/rdsk/d17    
18       phys-circinus-3:/dev/rdsk/c2t2d0 /dev/did/rdsk/d18    
19       phys-circinus-3:/dev/rdsk/c2t3d0 /dev/did/rdsk/d19    
...
26       phys-circinus-3:/dev/rdsk/c2t12d0 /dev/did/rdsk/d26    
30       phys-circinus-3:/dev/rdsk/c1t2d0 /dev/did/rdsk/d30    
31       phys-circinus-3:/dev/rdsk/c1t3d0 /dev/did/rdsk/d31    
32       phys-circinus-3:/dev/rdsk/c1t10d0 /dev/did/rdsk/d32    
33       phys-circinus-3:/dev/rdsk/c0t0d0 /dev/did/rdsk/d33    
34       phys-circinus-3:/dev/rdsk/c0t6d0 /dev/did/rdsk/d34    
8190     phys-circinus-3:/dev/rmt/0     /dev/did/rmt/2
# cfgadm -c configure c1 
# devfsadm
# scgdevs
Configuring DID devices
Could not open /dev/rdsk/c0t6d0s2 to verify device id.
        Device busy
Configuring the /dev/global directory (global devices)
obtaining access to all attached disks
reservation program successfully exiting
# scdidadm -l
16       phys-circinus-3:/dev/rdsk/c2t0d0 /dev/did/rdsk/d16    
17       phys-circinus-3:/dev/rdsk/c2t1d0 /dev/did/rdsk/d17    
18       phys-circinus-3:/dev/rdsk/c2t2d0 /dev/did/rdsk/d18    
19       phys-circinus-3:/dev/rdsk/c2t3d0 /dev/did/rdsk/d19    
...
26       phys-circinus-3:/dev/rdsk/c2t12d0 /dev/did/rdsk/d26    
30       phys-circinus-3:/dev/rdsk/c1t2d0 /dev/did/rdsk/d30    
31       phys-circinus-3:/dev/rdsk/c1t3d0 /dev/did/rdsk/d31    
32       phys-circinus-3:/dev/rdsk/c1t10d0 /dev/did/rdsk/d32    
33       phys-circinus-3:/dev/rdsk/c0t0d0 /dev/did/rdsk/d33    
34       phys-circinus-3:/dev/rdsk/c0t6d0 /dev/did/rdsk/d34    
35       phys-circinus-3:/dev/rdsk/c2t13d0 /dev/did/rdsk/d35    
8190     phys-circinus-3:/dev/rmt/0     /dev/did/rmt/2       

Where to Go From Here

To configure a disk drive as a quorum device, see the Sun Cluster 3.0 U1 System Administration Guide for the procedure on adding a quorum device.

How to Replace a Disk Drive in a StorEdge D1000 Disk Array in a Running Cluster

Use this procedure to replace a StorEdge D1000 disk array disk drive. Perform the steps in this procedure in conjunction with the procedures in the Sun Cluster 3.0 U1 System Administration Guide and your server hardware manual. Use the procedures in your server hardware manual to identify a failed disk drive. "Example--Replacing a StorEdge D1000 Disk Drive" shows how to apply this procedure.

For conceptual information on quorum, quorum devices, global devices, and device IDs, see the Sun Cluster 3.0 U1 Concepts document.

1. Identify the disk drive that needs replacement.

   If the disk error message reports the drive problem by device ID (DID), use the scdidadm -l command to determine the Solaris logical device name. If the disk error message reports the drive problem by the Solaris physical device name, use your Solaris documentation to map the Solaris physical device name to the Solaris logical device name. Use this Solaris logical device name and DID throughout this procedure.

   # scdidadm -l deviceID

2. Determine if the disk drive you are replacing is a quorum device.

   # scstat -q

   • If the disk drive you are replacing is a quorum device, put the quorum device into maintenance state before you go to Step 3. For the procedure on putting a quorum device into maintenance state, see the Sun Cluster 3.0 U1 System Administration Guide.

   • If the disk is not a quorum device, go to Step 3.

3. If possible, back up the metadevice or volume.

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

4. Perform volume management administration to remove the disk drive from the configuration.

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

5. Identify the failed disk drive's physical DID.

   Use this physical DID in Step 12 to verify that the failed disk drive has been replaced with a new disk drive.

   # scdidadm -o diskid -l cNtXdY

6. If you are using Solstice DiskSuite as your volume manager, save the disk partitioning for use when partitioning the new disk drive.

   If you are using VERITAS Volume Manager, go to Step 7.

   # prtvtoc /dev/rdsk/cNtXdYsZ > filename

   ---

   Note -

   Do not save this file under /tmp because you will lose this file when you reboot. Instead, save this file under /usr/tmp.

   ---

7. Replace the failed disk drive.

   For the procedure on replacing a disk drive, see the Sun StorEdge D1000 Storage Guide.

8. On one node attached to the StorEdge D1000 disk array, run the devfsadm(1M) command to probe all devices and to write the new disk drive to the /dev/rdsk directory.

   Depending on the number of devices that are connected to the node, the devfsadm command can require at least five minutes to complete.

   # devfsadm

9. If you are using Solstice DiskSuite as your volume manager, from any node that is connected to the StorEdge D1000 disk array, partition the new disk drive by using the partitioning you saved in Step 6.

   If you are using VERITAS Volume Manager, go to Step 10.

   # fmthard -s filename /dev/rdsk/cNtXdYsZ

10. One at a time, shut down and reboot the nodes that are connected to the StorEdge D1000 disk array.

    # scswitch -S -h nodename # shutdown -y -g0 -i6

    For more information on shutdown procedures, see the Sun Cluster 3.0 U1 System Administration Guide.

11. From any node that is connected to the disk drive, update the DID database.

    # scdidadm -R deviceID

12. From any node, confirm that the failed disk drive has been replaced by comparing the new physical DID to the physical DID that was identified in Step 5.

    If the new physical DID is different from the physical DID that was identified in Step 5, you successfully replaced the failed disk drive with a new disk drive.

    # scdidadm -o diskid -l cNtXdY

13. On all nodes, upload the new information to the DID driver.

    If a volume management daemon such as vold is running on your node, and you have a CD-ROM drive that is connected to the node, a device busy error might be returned even if no disk is in the drive. This error is an expected behavior.

    # scdidadm -ui

14. Perform volume management administration to add the disk drive back to its diskset or disk group.

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

15. If you want this new disk drive to be a quorum device, add the quorum device.

    For the procedure on adding a quorum device, see the Sun Cluster 3.0 U1 System Administration Guide.

Example--Replacing a StorEdge D1000 Disk Drive

The following example shows how to apply the procedure for replacing a StorEdge D1000 disk array disk drive.

# scdidadm -l d20
20       phys-schost-2:/dev/rdsk/c3t2d0 /dev/did/rdsk/d20
# scdidadm -o diskid -l c3t2d0
5345414741544520393735314336343734310000
# prtvtoc /dev/rdsk/c3t2d0s2 > /usr/tmp/c3t2d0.vtoc
... 
# devfsadm
# fmthard -s /usr/tmp/c3t2d0.vtoc /dev/rdsk/c3t2d0s2
# scswitch -S -h node1
# shutdown -y -g0 -i6
...
# scdidadm -R d20
# scdidadm -o diskid -l c3t2d0
5345414741544520393735314336363037370000
# scdidadm -ui

How to Remove a Disk Drive From a StorEdge D1000 Disk Array in a Running Cluster

Use this procedure to remove a disk drive from a StorEdge D1000 disk array in a running cluster. Perform the steps in this procedure in conjunction with the procedures in the Sun Cluster 3.0 U1 System Administration Guide and your server hardware manual.

For conceptual information on quorum, quorum devices, global devices, and device IDs, see the Sun Cluster 3.0 U1 Concepts document.

1. Determine if the disk drive you want to remove is a quorum device.

   # scstat -q

   • If the disk drive you want to replace is a quorum device, put the quorum device into maintenance state before you go to Step 2. For the procedure on putting a quorum device into maintenance state, see the Sun Cluster 3.0 U1 System Administration Guide.

   • If the disk is not a quorum device, go to Step 2.

2. If possible, back up the metadevice or volume.

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

3. Perform volume management administration to remove the disk drive from the configuration.

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

4. Identify the disk drive that needs to be removed and the slot that the disk drive needs to be removed from.

   If the disk error message reports the drive problem by DID, use the scdidadm -l command to determine the Solaris device name.

   # scdidadm -l deviceID # cfgadm -al

5. Remove the disk drive.

   For the procedure on removing a disk drive, see the Sun StorEdge D1000 Storage Guide.

6. On all nodes, remove references to the disk drive.

   # cfgadm -c unconfigure cN::dsk/cNtXdY # devfsadm -C # scdidadm -C

How to Add a StorEdge D1000 Disk Array to a Running Cluster

Use this procedure to install a StorEdge D1000 disk array in a running cluster. Perform the steps in this procedure in conjunction with the procedures in the Sun Cluster 3.0 U1 System Administration Guide and your server hardware manual.

For conceptual information on multi-initiator SCSI and device IDs, see the Sun Cluster 3.0 U1 Concepts document.

1. Ensure that each device in the SCSI chain has a unique SCSI address.

   The default SCSI address for host adapters is 7. Reserve SCSI address 7 for one host adapter in the SCSI chain. This procedure refers to the host adapter you choose for SCSI address 7 as the host adapter on the "second node."

   To avoid conflicts, in Step 7 you change the scsi-initiator-id of the remaining host adapter in the SCSI chain to an available SCSI address. This procedure refers to the host adapter with an available SCSI address as the host adapter on the "first node." Depending on the device and configuration settings of the device, either SCSI address 6 or 8 is usually available.

   ---

   Note -

   Even though a slot in the disk array might not be in use, do not set the scsi-initiator-id for the first node to the SCSI address for that disk slot. This precaution minimizes future complications if you install additional disk drives.

   ---

   For more information, see the OpenBoot 3.x Command Reference Manual and the labels inside the storage device.

2. Shut down and power off the first node.

   # scswitch -S -h nodename # shutdown -y -g0 -i0

   For more information on shutdown procedures, see the Sun Cluster 3.0 U1 System Administration Guide.

3. Install the host adapters in the first node.

   For the procedure on installing host adapters, see the documentation that shipped with your host adapters and nodes.

4. Connect the differential SCSI cable between the node and the StorEdge D1000 disk array, as shown in Figure 5-2.

   Make sure that the entire SCSI bus length to each enclosure is less than 25 m. This measurement includes the cables to both nodes, as well as the bus length internal to each enclosure, node, and host adapter. Refer to the documentation that shipped with the enclosure for other restrictions about SCSI operation.

   Figure 5-2 Example of a StorEdge D1000 Disk Array Mirrored Pair

   
   

5. Power on the first node and the StorEdge D1000 disk arrays.

   For the procedure on powering on a StorEdge D1000 disk array, see the Sun StorEdge A1000 and D1000 Installation, Operations, and Service Manual.

6. Find the paths to the SCSI host adapters.

   {0} ok show-disks

   Identify and record the two controllers that are to be connected to the StorEdge D1000 disk arrays, and record these paths. Use this information to change the SCSI addresses of these controllers in the nvramrc script in Step 7. Do not include the /sd directories in the device paths.

7. Edit the nvramrc script to change the scsi-initiator-id for the host adapters of the first node.

   For a list of Editor nvramrc editor and keystroke commands, see Appendix B, NVRAMRC Editor and NVEDIT Keystroke Commands.

   The following example sets the scsi-initiator-id to 6. The OpenBoot PROM Monitor prints the line numbers (0:, 1:, and so on).

   ---

   Caution -

   Insert exactly one space after the double quote and before scsi-initiator-id.

   ---

   {0} ok nvedit 0: probe-all 1: cd /sbus@1f,0/QLGC,isp@3,10000 2: 6 encode-int " scsi-initiator-id" property 3: device-end 4: cd /sbus@1f,0/ 5: 6 encode-int " scsi-initiator-id" property 6: device-end 7: install-console 8: banner [Control C] {0} ok

8. Store 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 have completed your edits, save the changes. If you are not sure about the changes, discard them.

   • To store the changes, type:

     {0} ok nvstore {0} ok

   • To discard the changes, type:

     {0} ok nvquit {0} ok

9. Verify the contents of the nvramrc script you created in Step 7, 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 /sbus@1f,0/QLGC,isp@3,10000 6 encode-int " scsi-initiator-id" property device-end cd /sbus@1f,0/ 6 encode-int " scsi-initiator-id" property device-end install-console banner {0} ok

10. Instruct the OpenBoot PROM Monitor to use the nvramrc script, as shown in the following example:

    {0} ok setenv use-nvramrc? true use-nvramrc? = true {0} ok

11. Boot the first node, and wait for it to join the cluster.

    {0} ok boot -r

    For more information, see the Sun Cluster 3.0 U1 System Administration Guide.

12. On all nodes, verify that the DIDs have been assigned to the disk drives in the StorEdge D1000 disk array.

    # scdidadm -l

13. Shut down and power off the second node.

    # scswitch -S -h nodename # shutdown -y -g0 -i0

    For more information on shutdown procedures, see the Sun Cluster 3.0 U1 System Administration Guide.

14. Install the host adapters in the second node.

    For the procedure on installing a host adapter, see the documentation that shipped with your host adapter and node.

15. Connect the StorEdge D1000 disk array to the host adapters by using differential SCSI cables (see Figure 5-3).

    Figure 5-3 Example of a StorEdge D1000 Disk Array Mirrored Pair

    
    

16. Power on the second node, but do not allow it to boot. If necessary, halt the system to continue with OpenBoot PROM (OBP) Monitor tasks.

17. Verify that the second node checks for the new host adapters and disk drives.

    {0} ok show-disks

18. Verify that the scsi-initiator-id for the host adapters 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 /sbus@1f,0/QLGC,isp@3,10000 {0} ok .properties scsi-initiator-id 00000007 ...

19. Boot the second node, and wait for it to join the cluster.

    {0} ok boot -r

20. On all nodes, verify that the DIDs have been assigned to the disk drives in the StorEdge D1000 disk array.

    # scdidadm -l

21. Perform volume management administration to add the disk drives in the array to the volume management configuration.

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

How to Replace a StorEdge D1000 Disk Array in a Running Cluster

Use this procedure to replace a StorEdge D1000 disk array in a running cluster. This procedure assumes that you are retaining the disk drives in the disk array you are replacing and you are retaining the references to these same disk drives.

If you are replacing your disk drives, see "How to Replace a Disk Drive in a StorEdge D1000 Disk Array in a Running Cluster".

1. If possible, back up the metadevices or volumes that reside in the disk array.

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

2. Perform volume management administration to remove the StorEdge D1000 disk array from the configuration.

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

3. Disconnect the SCSI cables from the StorEdge D1000 disk array, removing them in the order that is shown in Figure 5-4.

   Figure 5-4 Disconnecting the SCSI Cables

   
   

4. Power off and disconnect the StorEdge D1000 disk array from the AC power source.

   For the procedure on powering off a StorEdge D1000 disk array, see the Sun StorEdge A1000 and D1000 Installation, Operations, and Service Manual.

5. Connect the new StorEdge D1000 disk array to an AC power source.

6. Connect the SCSI cables to the new StorEdge D1000 disk array, reversing the order they were disconnected, as shown in Figure 5-4.

7. Move the disk drives one at a time from the old StorEdge D1000 disk array to the same slots in the new StorEdge D1000 disk array.

8. Power on the StorEdge D1000 disk array.

   For the procedure on powering on a StorEdge D1000 disk array, see the Sun StorEdge A1000 and D1000 Installation, Operations, and Service Manual.

9. On all nodes that are attached to the StorEdge D1000 disk array, run the devfsadm(1M) command.

   # devfsadm

10. One at a time, shut down and reboot the nodes that are connected to the StorEdge D1000 disk array.

    # scswitch -S -h nodename # shutdown -y -g0 -i6

    For more information on shutdown procedures, see the Sun Cluster 3.0 U1 System Administration Guide.

11. Perform volume management administration to add the StorEdge D1000 disk array to the configuration.

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

How to Remove a StorEdge D1000 Disk Array From a Running Cluster

Use this procedure to remove a StorEdge D1000 disk array from a cluster. This procedure assumes that you are removing the references to the disk drives in the enclosure.

1. Perform volume management administration to remove the StorEdge D1000 disk array from the configuration.

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

2. Disconnect the SCSI cables from the StorEdge D1000 disk array, removing them in the order that is shown in Figure 5-5.

   Figure 5-5 Disconnecting the SCSI cables

   
   

3. Power off and disconnect the StorEdge D1000 disk array from the AC power source.

   For the procedure on powering off a StorEdge D1000 disk array, see the Sun StorEdge A1000 and D1000 Installation, Operations, and Service Manual.

4. Remove the StorEdge D1000 disk array.

   For the procedure on removing a StorEdge D1000 disk array, see the Sun StorEdge A1000 and D1000 Installation, Operations, and Service Manual.

5. Identify the disk drives you need to remove.

   # cfgadm -al

6. On all nodes, remove references to the disk drives in the StorEdge D1000 disk array you removed in Step 4.

   # cfgadm -c unconfigure cN::dsk/cNtXdY # devfsadm -C # scdidadm -C

7. If necessary, remove any unused host adapters from the nodes.

   For the procedure on removing a host adapter, see the documentation that shipped with your host adapter and node.