HP Matrix Operating Environment 7.3 Recovery Management User Guide

6 Troubleshooting
This chapter provides troubleshooting information in the following categories:
• “Configuration troubleshooting” (page 52)
• “Configuration error messages” (page 54)
• “Warning messages” (page 57)
• “Matrix recovery management Job troubleshooting” (page 58)
• “Failover error messages” (page 61)
• “Matrix recovery management log files” (page 62)
• “DR Protected IO serivces troubleshooting” (page 62)
Configuration troubleshooting
To troubleshoot Matrix recovery management configuration operations, take note of any error
messages that appear, then review this section for relevant information. You can also view the
mxdomainmgr log files for additional information.
The following troubleshooting issues are addressed in this section:
• Unable to add or edit Site information
Possible causes include:
◦ The local or remote CMS name provided is not valid (not a fully qualified domain name
or locatable in the DNS).
◦ The local or remote CMS name does not include a fully qualified name associated with
the local host.
• Unable to add or edit Storage Management Server information
Possible causes include:
◦ The Storage Management Server is not discovered in the HP Matrix Operating Environment
user interface.
◦ The credentials associated with the Storage Management Server in the HP Matrix
Operating Environment user interface do not include the user name provided as part of
a Storage Management Server configuration that has been added or edited.
◦ The HP Matrix Operating Environment user interface is unable to communicate with the
Storage Management Server.
Communication Failure with Storage Management Servers may result if Open SSH is not being
installed or configured on the target system.
• Unable to add or modify HP P6000 Storage Management Server
Possible causes include:
◦ The CIMOM Server is not running on the Storage Management Server.
◦ The CIMOM server is configured to use a different port than the one specified for add
or edit operations.
◦ The specified user does not have valid login credentials on the Storage Management
Server with appropriate privileges.
52 Troubleshooting