HP Storage Provisioning Manager (SPM) version 2.3 User Guide

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.
Unmanaged networks
SANs that have no automated management path from SPM (unmanaged networks) can still be
imported into the SPM catalog. Using unmanaged networks with large numbers of devices may
require considerable effort to maintain the unmanaged network XML file.
For additional information regarding unmanaged networks, please refer to Working with
unmanaged networks.
Connectivity services 75