HP Storage Provisioning Manager (SPM) Version 2.0 User Guide

specified within the Fibre Channel Host requirement groups. The presentations of the
matching volumes will not be changed.
2. If all Fibre Channel Host requirement groups contain Pre-presented=FALSE (or do
not contain a Pre-presented requirement) in them, then the resulting services will be
configured to be accessible by the hosts specified by the Fibre Channel Host requirements.
SPM will attempt to configure the volume hostmode, mapping, masking, and SAN zoning to
allow the storage to be accessible from the host interfaces specified by the Fibre Channel
Host requirements.
3. If no Fibre Channel Host groups are specified of any kind, then matching services will
be configured to be inaccessible by all hosts (unmasked, unmapped, and unzoned).
4. Having a mixture of Fibre Channel Host groups with Pre-presented=TRUE and
Pre-presented=FALSE (which is the default) is not supported.
Network Capability requirement
The Network Capability requirements specify the capabilities which a matching service must
be capable of performing after it is provisioned. If a network capability is not specified as required,
then it is optional whether a provisioned service can perform the capability after being provisioned.
For example, a Network Capability requirement with a value of “Automated Zoning” matches
only networks that are capable of performing automated zoning.
RAID Level requirement
The RAID Level requirement specifies the RAID level of volumes matching this requirement. The
RAID level values represent the general concepts of each RAID level, for example the redundancy
and space efficiency characteristics. The actual RAID level chosen on the device is determined
from a mapping of the general concepts to the particular implementation of RAID on the array.
Resource Existence requirement
The Resource Existence requirement is a provisioning time only requirement which matches
resources which already exist, rather than ones which could be created. The only resource class
recognized is the Volume resource class since it is the only resource type creatable in SPM at this
time. Using this requirement with “Must not” enforcement specifies that matching volumes must be
created via on-demand provisioning and will not be pre-existing (pre-provisioned) resources.
Service Deactivation Policy requirement
The Service Deactivation Policy requirement specifies the actions to be taken on
deactivating the service. The available policies are:
• No Action — On service deactivation, nothing will be performed. All SAN zoning, volume
data, and volume presentation will be left as it was. Note that the server consuming the storage
will still be able to access it after the service is deleted.
• Quarantine Resources — On service deactivation, the volume within the service will be
quarantined from server access, ensuring servers can no longer read or write the data, but
the volume and data will be preserved on the array. Volume mapping and masking is removed,
and any SAN zoning is deleted from the SAN. The storage volume is put into a quarantined
state such that it will not be provisionable by future requests in SPM. It is the responsibility of
the storage admin to move the data to a suitable archive before returning the volume to an
enabled state or deleting it manually.
• Destroy Data — On service deactivation, the storage volume will be deleted, destroying
the data it contains and making the capacity available for future data services to provision.
Any SAN zoning that was performed will be removed as well. This policy is only to be used
Requirement types 25