HP Storage Provisioning Manager (SPM) version 2.3 User Guide

Possible cause 1–The HP 3PAR StoreServ Storage System floating IP is not accessible from the
Matrix Central Management Server.
Suggested action 1–Ping the HP 3PAR StoreServ Storage System Node address. Verify that the HP
3PAR StoreServ Storage System Node IP Address is accessible from the Matrix Central Management
Server.
Possible cause 2–SMI-S is not active on the HP 3PAR StoreServ Storage System.
Suggested action 2–Verify SMI-S is running on the HP 3PAR StoreServ 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–Incorrect credentials (user does not exist or password does not match) caused
CIMOM not to respond.
Suggested action 3–Wait for 30 minutes until the request times out or restart SPM, then attempt the
import again using a verified correct set of credentials.
Removing initiators from an existing HP 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–HP 3PAR StoreServ Storage System 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.
HP P6000/EVA arrays and/or HP XP/P9000 arrays are marked as Offline when they appear to
be functioning correctly outside of SPM
Symptom–HP P6000/EVA arrays and/or HP XP/P9000 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 HP P6000/EVA arrays and/or HP
XP/P9000 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 HP XP/P9000 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 HP XP/P9000 arrays are correct and that the command device is presented and available to
the server running SPM. The command device may be checked using the p9000info/xpinfo
tool available at the following location:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?
lang=en=us=329290=5202488=5158164=1110=13=2=135=co-94081-2=18964=4309961
Using this tool should show the type of the CU/LDEV as OPEN-V-CM.
Addressing common issues 67