HP Storage Provisioning Manager (SPM) version 2.3 User Guide

features. In either case SPM will handle the change automatically, as long as the fabric’s
identify as tracked by Brocade’s Network Advisor, remains intact.
Any change, regardless if it is a repair or re-configuration, that is severe enough to change
the identity of the fabric as tracked by Brocade Network Advisor will require administrator
intervention on SPM’s part to recover and will not be automatically handled
Zoning policy
SPM defaults to using the Single Initiator Zoning (SIZ) policy. Only candidates capable of being
connected using the SIZ policy or that are already connected are offered to the user during candidate
generation time. Using the SIZ policy, SPM creates zones on network capable of zoning automation
such that there is a single initiator per zone and only one zone per initiator. However, target
endpoints may be in more than one zone as needed by initiators. For example, the initiator's zone
is expanded to include the new targets as required. Targets that need presented to an initiator are
placed by SPM in that initiator's zone such that the zone may contain one or more targets and
expand or shrink as needed.
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,
74 Working with Brocade Fibre Channel networks