HP 2000sa Deployment Manual page 30

The controller and its storage are configured using the Storage Management Utility (SMU) or
Command Line Interface (CLI).
◦ For information about configuring storage in the SMU, see the HP StorageWorks 2000
G2 Modular Smart Array reference guide.
For information about configuring storage in the CLI, see the HP StorageWorks 2000
◦
G2 Modular Smart Array CLI reference guide.
(Optional but strongly recommended) Map each MSA2000sa storage volume to ports on the
server blades. This is called explicit mapping. Other HP utilities use a similar concept termed
Selective Storage Presentation (SSP) or Access Control Lists (ACL).
When you set up explicit maps, you specify for each volume, the hosts that can access it. If
a new server is installed in the c-Class enclosure, storage volumes will not be visible to that
server until explicitly mapped.
When you do not set up explicit maps for each volume, all server blades with P700m
Controllers that are contained in the same SAS zone can access the storage. If a new server
is installed in the BladeSystem c-Class enclosure, the storage volumes will be immediately
visible to that server.
◦ For information about mapping volumes using the SMU, see "Managing Host Access to
Volumes" in the HP StorageWorks 2000 G2 Modular Smart Array reference guide.
◦ For information about mapping volumes using the CLI, see the "Map volume" section in
the HP StorageWorks 2000 G2 Modular Smart Array CLI reference guide.
When mapping, be sure to choose all MSA2000sa G2 controller ports (A1, A2, A3, A4, B1,
B2, B3, and B4), to guarantee access in the event of a controller, port, or cable failure. During
a failover, if access is granted to all MSA2000sa G2 controller ports, I/O will fail over to
ports on the surviving controller.
30 Device information