HP Storage Provisioning Manager (SPM) version 2.2 User Guide

NOTE: In a Federated CMS type environment with parallel instances of SPM acting on the same
network, it is required that the initiators being used in the separate SPMs be distinct, allowing the
SPMs via the SIZ policy to be acting on distinct zones in the same network. Networks imported
into SPM must have distinct addresses across all imported networks.
Zoning naming convention
Zones created by SPM are named using the following convention:
• All capital letters starting with SPM_ followed by the WWN without colons of the initiator
involved in the process (for example, SPM_1012EF3400123401).
This naming convention allows SPM and network administrators to identify zones created by SPM.
Zone modification
Pre-existing zones (zones that SPM did not create) are used by SPM if they meet the requirements
of the desired Connectivity Service, but they will not be modified if they do not meet the desired
requirements. Instead, a new zone is created. Additionally if a pre-existing zone was used as is
when the service is deactivated/removed the pre-existing zone will not be touched by SPM.
However, SPM-created zones that have the same initiator as the given requirements but need
modification to include additional targets are modified as necessary. They are also removed from
the underlying device when SPM no longer needs them. This occurs as soon as all Connectivity
Services that depended on it are deactivated/removed.
Zone destruction
Zones are destroyed when all Connectivity Services that depended on it are deactivated/removed.
This only applies to SPM-created zones. Pre-existing zones are not affected. In either case, the
zone is removed from SPM's storage catalog and is no longer visible in the GUI.
Requirements
When creating a Connectivity Service there are two use cases:
Standard Use Case
In the standard case, one or more FCInitiatorEndpoint requirements are given in conjunction with
one or more FCTargetEndpoint requirements. For every endpoint requirement, the sub-requirement
FCWWN is required.
SPM interprets these requirements as follows.
• SPM checks that all the given endpoints are on the same network. Then it checks that each
initiator can communicate with each of the targets (the network is open, they are already
zoned together, or zoning automation can take place to put then in a zone together). However,
because the SIZ policy is being used, SPM does not check connectivity between the initiators
only the initiator to all targets.
• If the endpoints as described above can be connected or already are, then only one candidate
is returned to signify that the desired endpoints requirements can be or are already connected
together.
Proxy Use Case
The proxy case is much like the standard case with a couple of caveats. First the sub-requirement
FCProxyWWN is given in addition to the FCWWN for a FCInitiatorEndpoint requirement.
Because FCWWN does not have to exist yet (for example, the host may not have logged into the
fabric as of yet), SPM uses the given FCProxyWWN requirement, which is the WWN of another
endpoint that has already logged into the fabric and is known to SPM (typically this is the uplink
port of a Blade enclosure, but could be any known port). The FCProxyWWN is used to identify
where the FCWWN will live once it is powered up and allows SPM to generate candidates for it
as if it already exists.
Connectivity services 71