HP Storage Provisioning Manager (SPM) Version 2.0 User Guide

XML file lifecycle
The user must provide SPM with an XML file as described in this document which specifies the
features of the unmanaged SANs. When there are changes to the state of the unmanaged SAN,
the user must update the data in the XML file in order for the data within SPM to be consistent with
the state of the SAN. When an unmanaged SAN becomes available, changes, or becomes
unavailable, the user should manually make changes to the XML file describing that SAN. SPM
triggers a refresh when changes are written to XML files within the appropriate directory to keep
its state consistent with the state of the data in the XML file. XML files that are already in use should
not be edited within the <SPM installation path>/state/unmanaged_san/ directory.
Instead, a copy of the file should be made in a different location, and the copy should be used to
overwrite the old file when editing is complete. To change a SAN from unmanaged to managed,
first remove the unmanged SAN within the GUI, then import the managed SAN. It is recommended
that the XML file describing the unmanaged SAN should be removed from the <SPM
installation path>/state/unmanaged_san/ directory before importing the managed
SAN into SPM.
XML file location
SPM reads XML files describing unmanaged SANs from a standard location relative to the location
of the application. All files within the specified folder having a file type of “.xml” will be loaded
by SPM. The location examined by SPM is <SPM installation
path>/state/unmanaged_san/. This location is live and any XML file changes will trigger
reads of files stored there by SPM.
XML errors
In the event that an XML file provided to SPM does not follow the specification, an error will be
posted in the SPM log file, and the file will be ignored. There are nine errors that will be detected
when SPM attempts to read an unmanaged SAN XML file. They are listed below.
Unmanaged SAN XML Errors
File does not have proper XML structure.
Unknown ZoningState or NetworkEndpointKind values.
Duplicate NetworkResource names within a SanResourceCollection.
Duplicate Network names within a SanResourceCollection.
Duplicate zones within a Network.
Duplicate Endpoint addresses within a NetworkResource, Network, or Zone.
ZoneState value of Open when Zones are present.
ZoneState value of Zoned when no Zones are present.
Endpoints and zones
The XML files described in this document specify the endpoints and zones within one or more
unmanaged SANs. SPM does not allow two networks to contain the same endpoint. If a conflict
between two networks is detected, SPM does not allow the second network to contain the endpoint.
Thus, unmanaged SAN users must ensure that an XML file does not contain network endpoints that
are also present in another network, whether the other network is managed or unmanaged.
Network types
As of version 2.0, SPM only handles unmanaged Fibre Channel SANs. While the format of the
XML file allows for the possibility of other SAN networks types, SPM currently does not support
them.
Overview 73