Specifications

2-6 Sun StorEdge A1000 and A3x00/A3500FC Best Practices Guide November 2002
2.2 AddingorMovingArraystoaHostWith
Existing A3x00 Arrays
When moving a disk array, ensure that the array being moved has firmware levels
that match with the new host. See "Upgrading Controller Firmware" in the Sun
StorEdge RAID Manager 6.22 Release Notes. Since the firmware on the controller
cannot be downgraded, except in the case of a universal FRU, you should not move
an array to a host with a lower RAID Manager release. If the array being moved has
more than 8 LUNs, be sure the new host has greater than 8 LUN support turned on.
See “Maximum LUN Support in Solaris 2.6 and Solaris 7 Environments” in the Sun
StorEdge RAID Manager 6.22 Release Notes. Also, refer to “Adding or Moving Arrays
Under VERITAS” on page 4-13 for information pertaining to VERITAS volumes.
You can move an A1000 or an A3x00 array from one server to another and still be
able to access the data after the move.
You can perform most but not all of the RAID Manager 6 array management
commands after the move. In particular, you will not be able to execute commands
such as LUN creation or deletion. This can only be done on the host where the array
was originally connected. This is because there is host ownership information
stored in DacStore and on the LUNs that prevent these types of commands from
being executed. The workaround involves using either the storutil command to
update the host ownership information in the DacStore region or the RAID Manager
6 GUI Select Module -> Edit function to change the module name both of which
updates the DacStore with the new owning host information. See the man page
storutil (1M) to view the available command line options.
2.3 Adding Disks or Disk Trays
This section contains the following topics:
Section 2.3.1, “Adding or Moving Disk Trays to Existing Arrays” on page 2-7
Section 2.3.2, “Adding or Moving Disk Drives to Existing Arrays” on page 2-7