HP Surestore Disk Array 12h - And FC60 Advanced User's Manual page 294

Does the primary path selected using LVM impact LUN ownership?
Note
Yes. The primary path established using LVM defines the owning controller for
the LUN. This may override the controller ownership defined when the LUN
was bound. For example, if controller A was identified as the owning controller
when the LUN was bound, and LVM subsequently established the primary path
to the LUN through controller B, controller B becomes the owning controller.
To change the controller ownership of a LUN, type:
amcfg -M <LUN> -c <cntrlrID> <ArrayID>
•
cntrlrID identifies the controller (A or B) that is being assigned LUN ownership
Command Example
The following example changes the ownership of LUN 3 to controller B on disk array
0000005EBD20.
amcfg -M 3 -c B 0000005EBD20
Replacing a LUN
It is possible to replace an existing LUN. This operation unbinds the LUN and then rebinds
it using the new parameters specified. This is useful if you wish to change the settings of an
existing LUN, such as its size or RAID level, using a single command.
All data on a LUN is lost when it is replaced. Make sure you backup any
C
AUTION
important data on the LUN before replacing it.
Can I replace any LUN on the disk array?
Note
Although you can replace any LUN, the replace command is intended to be used
with LUN 0. LUN 0 is unique in that it must exist on the disk array to permit
communication with the host. Consequently, you cannot unbind LUN 0. If you
want to alter LUN 0, you must use the replace command. For all other LUNs, it
is recommended that you use the unbind and bind commands to alter LUN
configuration.
Managing the Disk Array Using Array Manager 60
294