ISR654606-00 A
7-1
7
Using the HP MSA2012fc
Storage Array
This chapter discusses the following considerations for using the HP Modular
Storage Array 2012fc (MSA2012fc):
“MSA2012fc Array Behavior” on page 7-1
“Using Array-based Licenses for MSA2012fc Array” on page 7-1
“Workaround for Using a Single Array License for MSA2012fc” on page 7-2
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.