HP Storage Provisioning Manager (SPM) version 2.3 User Guide

A Troubleshooting
Viewing operational logs
SPM maintains an operational log for the storage catalog, listing all operations performed and all
error events and an audit log listing all operations and permissions events. All users can review
the operational log using the following procedure:
1. Open a browser window and enter
https://SPM_Server_Name_or_IP_Address:8000/logs.
2. To view operational logs or audit logs, click the appropriate file name.
The file opens. Operational log entries can be copied for pasting content into another window
on the desktop.
NOTE: The logs are located in the <SPM install directory>/logs folder.
As a best practice, enable a lower level of SPM logging. Higher logging levels consume more log
space due to more detailed entries, but can be helpful when diagnosing problems with SPM. To
enable a higher logging level:
1. Navigate to C:\Program Files (x86)\HP\Storage Provisioning Manager\state.
NOTE: The SPM installation path will be different in a Federated Clustered CMS environment.
2. Use a text editor to open the file ApplicationConfig.xml.
3. Change the line <LoggingThreshold>Informational</LoggingThreshold>to
<LoggingThreshold>Tracing</LoggingThreshold>.
4. Save the file and close the text editor.
There is no need to restart the SPM service. This change occurs immediately.
NOTE: If issues do occur, search the operational.log and look for lines that contain [E].
These lines indicate that exceptions have occurred and help to pinpoint the problem.
Addressing common issues
The following sections describe common issues you may encounter while configuring or using the
SPM. They are either related to SPM itself, or have to do with using HP Matrix OE storage pool
entries.
Limitations
Presenting an in-use storage volume to an unintended consumer may result in data loss
IMPORTANT: Pay special attention when importing pre-presented volumes into SPM because all
storage volumes imported into SPM are made available to fulfill storage services requested by SPM
consumers such as Matrix Operating Environment. Import only storage volumes intended to fulfill
storage requests serviced by this instance of SPM. If you have multiple instances of SPM (either
independent or in a federated configuration), you may wish to have each instance manage different
storage array pools or completely different arrays.
When importing pre-presented storage volumes, ensure the volume is not already in use. DO NOT
import volumes that are in use, are intended for use by other systems or services, or that have been
imported into any other instance of SPM. Doing so may result in data loss.
Storage volumes must be managed by one SPM
Large data center environments may make use of multiple CMS configurations (either independent
or in a federated configuration). Any individual storage volume/LUN should be managed by only
one SPM. This can be done by having different SPM instances on different CMSs manage different
storage array pools, different arrays, different virtual domains, or disjoint sets of volumes.
64 Troubleshooting