Operating Environment Software Owner manual

Suggested action–After the upgrade is complete:
1. Open the HP 3PAR Management Console and connect to the array containing the volume in
the nonconformant service.
2. Select the Hosts tab in the console, and select the host for the nonconformant service.
3. Right-click on the host, and select Edit Host.
4. Change the operating system value of the host to match the required operating system and
save the host.
5. In SPM, resynchronize the array containing the volume.
Importing resources
Cannot import HP XP/XP P9000 arrays into SPM
Symptom–No XP arrays show up in the import array wizard, and therefore XP arrays cannot be
imported into SPM.
Possible cause–There is a corrupt command device on an XP array.
Suggested action–On the XP array, un-present the corrupted command device and delete it. Create
a new command device on the XP array and present it to the SPM system. Stop the SPM service.
Restart the SPM service. For more information on command devices and how to determine if a
command device is in a blocked state, see the user’s guide for your array.
HP XP/XP P9000 documentation is available from the Manuals page of the HP Business Support
Center website:
http://www.hp.com/support/manuals
Managed SAN
Managed SAN cannot be imported
Symptom–Managed SAN import fails.
Possible cause–BNA 11.1.3 or 11.1.4 is not available or configured incorrectly.
Suggested action–Verify that BNA 11.1.3 or 11.1.4 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.
Suggested action–Verify that the credentials in use are correct, including the IP address of the BNA
host, the username, and the password.
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–
1. Edit the unmanaged SAN XML file and verify that all XML content is correct, including the
format of XML and the opening and closing characters for XML entries.
2. Check the folder containing the unmanaged SAN XML file. Verify that there are no other files
in the folder with the same name but have an extension of “xml~”.
Managed SAN 67