HP Storage Provisioning Manager (SPM) version 2.3 User Guide

Managed SAN
Managed SAN cannot be imported
Symptom–Managed SAN import fails.
Possible cause–A supported BNA or HP B-Series Network Advisor is not available or configured
incorrectly.
Suggested action–Verify that asupported BNA or HP B-Series Network Advisor 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~”.
Unmanaged Zoned SAN goes offline after update
Symptom–After an unmanaged SAN is updated with a new zone, it goes offline and never returns.
Possible cause–The syntax of XML and/or entries may be unexpected.
Suggested action–Edit the unmanaged SAN XML file for the offline network and verify that all XML
content is correct, including the format of the XML and the opening and closing characters for XML
entries. Checking the SPM log file may also be helpful in this situation. For more information, see
“XML file lifecycle” (page 97)
Managed SAN 71