How to cleanly remove a Sun StorEdge[TM] A5x00 array from a system without downtime

Asset ID:	1-71-1005088.1
Update Date:	2009-02-18
Keywords:

Solution Type Technical Instruction Sure

Solution 1005088.1 : How to cleanly remove a Sun StorEdge[TM] A5x00 array from a system without downtime

Related Items


Sun Storage A5000 Array
 Sun Storage A5200 Array

Related Categories


GCS>Sun Microsystems>Storage - Disk>Modular Disk - Other

PreviouslyPublishedAs
207150

Description
The procedure for removing an A5x00 array from a system is actually very simple, and can be performed without interrupting system operation. However, it's not clearly explained in the product documentation.

Steps to Follow
How to cleanly remove a Sun StorEdge[TM] A5x00 array from a system without downtime

1. Stop all I/O to the array:
Unmount any filesystems residing on the array. Delete any software raid volumes built using disks in the array (with Veritas Volume Manager, Solaris[TM] Volume Manager, Solstice DiskSuite[TM], or similar products). If any applications (such as databases) are using raw slices on the disks, stop those applications or reconfigure them to use space elsewhere. Remember to remove any references to the array and to deleted volumes from the /etc/vfstab file.

2. Remove the device paths for the disk array:
luxadm remove_device <array name>
This will give some output and then ask you to "hit <Return> after removing the devices". Do not hit return yet.

3. Power off the array.

4. Go back to the terminal window where the luxadm command is waiting (from step 2) and press return.

5. Disconnect the cables from the array to the host.

6. Verify you know longer see the array:
luxadm probe

Product
Sun StorageTek A5200 Array
Sun StorageTek A5100 Array
Sun StorageTek A5000 Array

photon, a5100, a5200, a5000, detach, move, migrate
Previously Published As
81145

Change History
Date: 2005-05-05
User Name: 25440
Action: Approved
Comment: Publishing.
Version: 3
Date: 2005-05-05
User Name: 25440
Action: Accept
Comment:
Version: 0
Date: 2005-05-05

Attachments

This solution has no attachment