Phase 5: vshare configuration – HP VMA-series Memory Arrays User Manual
Page 26

26
AM456-9007B Rev 02
HP VMA SAN Gateway Installation and User Guide
Phase 4, HP VMA SAN Gateway Configuration, includes the following
procedures:
•
Configuring the Master HP VMA SAN Gateway: The first step is to
configure the master node of the HP VMA SAN Gateway cluster and define
the global cluster parameters, which are inherited by each node subsequently
added to cluster.
•
Configuring additional HP VMA SAN Gateways: Connect to each
remaining HP VMA SAN Gateway node to set its hostname and local system
parameters.
All Phase 4 configuration procedures are described in CHAPTER 3,
Phase 5: vSHARE Configuration
During this phase you configure the HP VMA SAN Gateway cluster to support
block storage with vSHARE.
vSHARE
vSHARE configuration includes the following steps:
•
Configuring Containers: The first step is to format the VMA Array to
manage block storage and create one or more containers to manage the LUNs.
•
Configuring the Target Ports: The second step is to configure the target
ports. Target ports may be used to control access to LUNs, which is useful for
security and bandwidth management.
If using Fibre Channel, the target ports are automatically configured when you
create the storage container on the Memory Array.
•
Configuring Initiator Groups and Initiators: The third step is to configure
the initiator groups and add one or more initiators to each initiator group.
Access to LUNs may be restricted by initiator group or on an initiator-by-
initiator basis.
•
Configuring LUNs: LUNs are created within the storage containers on the
Memory Arrays. LUNs inherit attributes from the container in which they are
created.
•
Exporting LUNs: The LUNs must be exported to the initiator groups or
initiators via target ports. Only those initiator groups or initiators to which the
LUN is exported may access the LUN. Access may be further restricted to a
specific target port.