HP Storage Provisioning Manager (SPM) Version 2.0 User Guide

4. Save and close the file.
5. Using the Microsoft Services MMC, start SPM service.
Issues with multiple SPM instances pointed to the same storage resources
Symptom–Changes from one SPM server overwrite changes made on another SPM server.
Possible cause–Both SPM servers are attempting to manage the same resources.
Suggested action–Verify that each SPM server is managing distinct instances of the volume resources.
Do not attempt to manage the same volume resources with both SPM servers.
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 doesn’t 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.
3PAR SMI-S connection problems
Symptom–With firmware 2.3.1, UI appears to freeze during in the array discovery wizard. It
eventually times out after 20 minutes.
Possible cause–Likely the username/password configuration is invalid. A known SMI-S agent defect
causes the http request to hang on the client side until it times out.
Suggested action–None.
Service activation fails to present volumes on 3PAR arrays
Symptom–Job status indicates a failure during the volume presentation step on 3PAR array.
Possible cause–One or more ports for the array may be marked as "free", which is not supported
for presentation mapping. This can be discerned by an error message about '"free" ports' in the
SPM log.
Suggested action–Make sure that the array ports in use have at least one active host connecting
in.
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–The software that controls access to the EVA and XP arrays is in a separate service,
which in turn is dependent on a J2EE service. If either of these processes are not running or if the
processes have not started in the correct order, this can lead to communication problems with the
arrays.
Suggested action–There are three relevant services:
• HP SPM Storage Module Service, which communicates with the array
• HP SPM Storage Module J2EE Service, which is an underlying service dependency
• HP Storage Provisioning Manager Service, which is the primary SPM service
Addressing common issues 55