Operating Environment Software Owner manual

The HP 3PAR StoreServ Storage System may have hosts with multiple initiator ports. SPM may
create hosts with multiple initiator ports (for example, if the requirement specifies this). If an initiator
port is already referenced on the array, then a presentation request might indicate that the initiator
port's host grouping should change. This could happen if a single host contained two initiator ports
and the presentation request referenced one of the ports but not the other (meaning that the initiator
port should not be part of the host anymore). If these presentation requests would affect presentation
for another existing volume, SPM will not change the array's configuration, resulting in a
nonconformant service.
For example: Volume1 is presented to Host1 (WWN1) and SPM requests presentation of Volume2
to Host1 (WWN1, WWN2). Adding an initiator endpoint address to the
StorageHardwareIdCollection associated with WWN1 would mean that Volume1 would be
presented to WWN2, which is a side effect. SPM presentation changes will not generate side
effects.
Working with HP 3PAR StoreServ Storage System active VLUNs and VLUN
templates
On HP 3PAR StoreServ 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 HP 3PAR StoreServ Storage System User Guide.
Working with autonomic groups
Autonomic groups are a unique feature of HP 3PAR StoreServ 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. However autonomic groups can be used 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 requirement binding.
• Likewise, using non-SPM tools (for example, HP 3PAR Management Console or CLI) to present
an already-imported volume to a host set will result in unpredictable behavior during
requirement binding.
Volume migration (Tiering)
With HP 3PAR StoreServ Storage Systems, it is common for volumes to be migrated from tier to
tier. Volume migration can be performed manually using the HP 3PAR Management Console or
CLI, or it can be automated using licensed software such as Adaptive Optimization and Peer
Motion. Either way, SPM must pick up on those changes and ensure that the catalog is as up to
date as possible. To that end, there are three ways SPM will update the catalog to take volume
migration into account:
1. When the storage administrator manually re-synchronizes a volume, SPM will verify that the
parent pool has not changed. If it has, SPM will either:
Working with HP 3PAR StoreServ Storage System active VLUNs and VLUN templates 81