HP Matrix Operating Environment Software - Manual (Page 59)

•
SPM deletes any PP presentations for the volume.
•
For initiators in the presentation constraint that are not already mapped to the volume, SPM
always uses MS to map those initiators.
•
For initiators that are already mapped to the volume using MS, SPM deletes MS mappings
for array ports that are not connected to the same SAN as the initiator and creates new MS
mappings for array ports that are connected to the same SAN as the initiator.
•
For initiators that are already mapped to the volume using HS, SPM deletes the existing HS
mapping and creates new MS mapping unless the same SAN ID is assigned to all array ports
in the catalog, in which case SPM leaves the existing HS mapping in place.
Creating hosts on a 3PAR Storage System
When SPM attempts to present a volume to an initiator, it first probes the array to detect whether
this initiator is known to the array. If it is not, a new host is created for that initiator. The name
given to that host is always “SPM_” followed by the WWN of the initiator.
SPM can show presentations that contain hosts with multiple initiator ports, but when creating hosts,
SPM always creates a host with a single initiator port. If SPM must present a volume to an initiator
that is already referenced on the array, and if that initiator belongs to a multiple-initiator host, then
all initiators for that host will be mapped to the volume. This could potentially result in a
non-conformant service.
Working with 3PAR Storage System active VLUNs and VLUN templates
On 3PAR Storage Systems, active VLUNs are the paths through which hosts that have logged on
to the fabric can see a given volume. VLUN templates are similar to “declarations” that volumes
are presented to hosts that are currently unknown to the array (for example, offline hosts). SPM
creates VLUN templates, which become active VLUNs when the host is powered on.
For more information, refer to the 3PAR Storage System user guide.
Working with autonomic groups
Autonomic groups are a unique feature of 3PAR Storage Systems that allow storage administrators
to group volumes, hosts, or virtual domains together. Those groups (also known as sets) allow
batch operations on a collection of objects – for instance, presenting a volume to a set of hosts in
one operation – and provide a level of automation by automatically adjusting the way volumes
are exported when objects are added to or removed from sets. For more information, please refer
to the array user guide.
This version of SPM is not fully compatible with autonomic groups and it is recommended to not
use them on arrays managed by SPM. It is however ok to use autonomic groups within the following
guidelines:
•
Importing volumes that belong to one or more volume sets is supported. SPM will not reflect
the containment of those volumes in volume sets.
•
Presenting volumes to hosts that belong to one or more host sets is supported. SPM will not
reflect the containment of those hosts in host sets.
•
Importing volumes that are presented to one or more host sets is NOT supported: SPM will
not be able to reflect that presentation and doing so will lead to errors and inconsistencies
during goal binding.
•
Likewise, using non-SPM tools (e.g. 3PAR GUI or CLI) to present an already-imported volume
to a host set will result in unpredictable behavior during goal binding.
Creating hosts on a 3PAR Storage System 59