HP Storage Provisioning Manager (SPM) version 2.1 User Guide

2. Select the desired unmanaged network from the Import Networks screen, and complete the
import performing the same steps used for a new unmanaged network.
Unmanaged network management
Once an unmanaged network has been created or imported, it can be edited later by selecting
the network and selecting Edit Network in the Networks pane. Unmanaged networks can also be
removed from SPM within the Networks pane. The XML file for networks removed from SPM remain
in the SPM state folder, and the network can be re-imported at a later date.
The XML files for simple unmanaged networks defined within SPM may be edited outside SPM. If
such files are edited in a way that changes an open network into a zoned network, or if any
Endpoint objects are added to an XML network, those networks can no longer be edited using the
SPM user interface.
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, the unmanaged network should be removed
from SPM and 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. When a SAN is no longer needed within SPM, the XML file describing it can be
removed from the directory already mentioned.
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 read 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 XML files stored there.
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. The errors listed in the following table will
be detected when SPM attempts to read an unmanaged SAN XML file.
Unmanaged SAN XML Errors
File does not have proper XML structure
Unknown ZoningState or NetworkEndpointKind values
Duplicate Network names
Duplicate zones within a Network
Duplicate Endpoint addresses
ZoneState value of Open when Zones are present.
Overview 81