HP Storage Provisioning Manager (SPM) version 2.1 User Guide

Issues with multiple SPM servers managing the same volumes
Symptom–Changes from one SPM server overwrite changes made on another SPM server.
Possible cause–Both SPM servers are attempting to manage the same volumes.
Suggested action–Verify that each SPM server is managing distinct volume resources. Do not attempt
to manage the same volume resources with two or more SPM servers. Two SPM servers may
manage the same arrays or pools.
Cannot import 3PAR Storage Systems
Symptom–Importing a 3PAR Storage System fails.
Possible cause 1–The 3PAR InServ floating IP is not accessible from the Matrix Central Management
Server.
Suggested action 1–Ping the 3PAR InServ Node address. Verify that the InServ Node IP Address
is accessible from the Matrix Central Management Server.
Possible cause 2–SMI-S is not active on the 3PAR Storage System.
Suggested action 2–Verify SMI-S is running on the 3PAR Storage System by logging onto the node
floating IP. At the command prompt, type showcim and verify that SMI-S is enabled and running.
If it is not, run startcim.
Possible cause 3–Inaccurate credentials (user does not exist or password does not match) has
caused CIMOM not to respond.
Suggested action 3–Wait for 30 minutes until the request time outs or restart SPM, then verify that
the credentials are correct.
Removing initiators from an existing 3PAR volume presentation may fail
Symptom–An existing service in SPM is modified to remove an initiator from a host presentation.
Activating the updated service fails during the update presentation job step. The log indicates that
DeleteStorageHarwareID for the WWN failed with Error Code=4.
Possible cause–3PAR array does not allow active initiator paths to be removed from host entries.
Suggested action–Make sure that the host is shut down or not actively connected to the array before
reactivating the service.
EVA arrays and/or XP arrays are marked as Offline when they appear to be functioning correctly
outside of SPM
Symptom–EVA and/or XP arrays may be marked Offline within SPM, but appear fine outside of
SPM. Additionally, looking at the SPM logs may reveal software exceptions associated with “HP
SPM Storage Module”. Connection issues are most likely associated with this problem.
Possible cause 1–Occasionally, timeout issues in the communication between SPM and the array
can cause the array to be marked offline temporarily.
Suggested action 1–Using the SPM GUI, manually resynchronize the array and see if that brings
the array back online.
Possible cause 2–The software that controls access to the EVA and XP arrays is in a separate
service. This process should be started up automatically when SPM is started. If it is not running,
then SPM cannot communicate with the array.
Suggested action 2–If SPM is shutdown and restarted, this should restart all of the necessary
processes. SPM can be shut down by stopping the HP Storage Module Provisioning Manager
Service. When the service is restarted, the HP Storage Module Service should be started
automatically. Note that it is recommended that SPM be idle when shutting down so active user
interactions are not affected.
Possible cause 3–SPM is not able to communicate with the XP array through the command device.
Suggested action 3–If the log includes a line similar to No Arrays found. Please verify
username, password and array connectivity, verify that the credentials defined for
the XP arrays are correct and that the command device is presented and available to the server
Addressing common issues 57