HP Storage Provisioning Manager (SPM) version 2.1 User Guide

Firmware for 3PAR storage systems
3PAR storage systems must have InForm OS 3.1.1 MU1 or higher installed in order to work properly
with SPM. SPM does not allow 3PAR arrays with earlier versions to be imported into the SPM
catalog.
No matching candidates found
Symptom–Requirements do not match the available catalog resources.
Suggested action–Verify that the Matrix storage requirements are correct. Also verify available
SPM catalog entries meet the requirements from Matrix.
NOTE: If you do not obtain candidates in the storage pool entry user interface, the storage service
may be labeled as unassigned or the storage service may be nonconformant. If this is the case,
you can verify the requirements by highlighting the storage service in question, then clicking on
the configure requirements button. At the candidates screen you can then click on the modify
requirements link and change requirements to see which requirement is causing the problem.
Symptom–The Matrix Default Storage Template has not been altered for on-demand provisioning
and no volumes are imported.
Suggested action–
1. Import volumes into the catalog for provisioning.
2. Modify the HP Matrix Default Storage Template to allow on-demand provisioning.
a. Highlight the HP Matrix Default Storage Template and click the edit button.
b. Change the Read-only requirement “Resource Existence” with value “Volume” from
“Required” to “Recommended”.
c. Add a capacity constraint to the template if the size of on-demand provisioned volumes
should be limited.
Symptom–Using a 3PAR array with autonomic group configured, HSET or MSET errors are displayed
in the SPM log.
Suggested action–SPM cannot use volumes assigned to hosts sets. To correct this, import and use
volumes that are not assigned to host sets.
Managed SAN
Managed SAN cannot be imported
Symptom–Managed SAN import fails.
Possible cause–BNA 11.1.3 or greater is not available or configured incorrectly.
Suggested action–Verify that BNA 11.1.3 is installed on the server that you are attempting use for
SAN management. Verify that the SMI Agent is configured and is running.
Suggested action–Ping the SAN Management server to verify that you can communicate with it via
TCP/IP. Log onto the SAN Management server and start the “Server Management Console” in the
BNA “All Programs” section. Verify that the CIMOM server is running. If not, configure and start
it.
Unmanaged SAN
Unmanaged SAN cannot be imported
Symptom–Unmanaged SAN fails to appear in the list of importable SANs.
Possible cause–XML syntax errors or XML schema errors were detected.
Suggested action–Check SPM log to determine the syntax/schema validation error and correct it.
Symptom–Unmanaged SAN fails appears in the list of importable SANs but does not import.
Possible cause–Some editors leave another copy of the file in the folder with a different extension.
Suggested action–
Managed SAN 61