HP MPX200 Multifunction Router - Manual (Page 144)

8 Using the HP MSA2012fc storage array
MSA2012fc Array Behavior
The controllers A and B of the MSA2012fc expose a completely independent set of LUNs that
cannot be accessed through other controllers. ControllerA-port0 and ControllerA-port1 form one
array, and ControllerB-port0 and ControllerB-port1 form another array. The MSA2012fc array
appears as two independent arrays on the MPX200.
Zoning: After data LUNs are assigned to the MPX200 ports, zone MPX200 ports (FC1 and FC2)
with MSA2012fc (ControllerA-port0 and ControllerA-port1). This zoning creates an array entity
that allows you to migrate data to and from LUNs owned by ControllerA. You must zone in
ControllerB-port0 and ControllerB-port1 to be able to migrate data to and from LUNs owned by
ControllerB. By doing so, you create a separate array entity for the ports belonging to ControllerB.
To understand the physical connections required, refer to the MSA documentation on Fibre Channel
port interconnect mode settings.
Using Array-based Licenses for MSA2012fc Array
As indicated in the preceding, each controller of the MSA2012fc array presents different LUNs to
the MPX200 ports and hence appears as two separate arrays.
Using array-based licenses to migrate LUNs owned by both controllers requires two array licenses.
If, however, all LUNs requiring migration are owned by a single controller, one array license should
suffice.
MSA2012fc allows a maximum of 128 volumes (LUNs) to be accessed through one controller from
any host. If you need to migrate data to and from more than 128 LUNs, you must present LUNs
in batches with a maximum of 128 LUNs at a time.
To unpresent old LUNs and present new LUNs to the MPX200 ports, follow the steps in
“Reconfiguring LUNs on a storage array” (page 146) .
Workaround for Using a Single Array License for MSA2012fc
To use a single license for an MSA2012fc array where data needs to be migrated to and from
LUNs owned by both ControllerA and ControllerB, use the following workaround:
1.
Add array-based licenses (a Single Array or Three Array License) as required.
2. Present LUNs that need to be used by data migration jobs from the storage array to the
MPX200 ports.
3. Make sure that the LUNs are presented with the same LUN ID for both MPX200 ports.
4. Zone in only ControllerA ports with the MPX200. The MPX200 creates one array entity for
the zoned in ports, because they belong to the same controller.
5. Apply array-based licenses to the array entity using the set array CLI command, or in the
License Array dialog box.
6. Configure data migration jobs as described in “Scheduling an individual data migration job”
(page 56) or “Scheduling data migration jobs in batch mode” (page 58) .
7. After the data migration jobs for all the LUNs belonging to ControllerA are completed and
acknowledged, perform a reconfiguration.
8. Zone out the MSA2012fc ports and the MPX200 ports.
9. Unpresent the LUNs presented in Step 2 .
10. Change the ownership of LUNs from ControllerB to ControllerA for all the LUNs that belong
to Controller B and need to be used in data migration jobs.
11. Present LUNs from Step 10 from the storage array to the MPX200 ports.
12. Make sure that the LUNs are presented with the same LUN ID for both MPX200 ports.
13. Rezone the MSA2012fc ports and the MPX200 ports that were zoned out in
Step 8 .
144 Using the HP MSA2012fc storage array