HP XP24000 HP Replication Adapter for VMware vCenter Site Recovery Manager Adm - Page 44

Troubleshooting RMSRA20, Known problems, HP disk arrays do not appear in Site Recovery Manager - default password

Get HP XP24000 PDF manuals and user guides View all HP XP24000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 44 highlights

5 Troubleshooting RMSRA20 Known problems The following problems and solutions are typical: HP disk arrays do not appear in Site Recovery Manager Solution: If HP disk arrays do not appear in the Site Recovery Manager, make sure that the Site Recovery Manager has been restarted (see "Installation procedure" (page 23)). Also make sure that the array manager that SRM is connected to is actively managing arrays. RMSRA20 does not install Solution: Make sure that SRM is installed. RMSRA20 will not install if SRM is not on the disk array. Virtual machines do not start at the recovery site after failover Cause: The ESX recovery hosts are not configured with the correct HBA port WWN on the recovery HP disk array. The replicated LUNs used in failover were not presented to the recovery ESX servers. Solution: Correctly map the replicated LUNSs to the recover ESX server. Virtual machines do not start at the recovery site during testFailover Cause: The volume used for CoW/QS is set as a NO Read attribute (PAIR or SMPL state). Solution: Make sure that the ESX server can boot after changing to the PSUS state (Read/Write enable). Error Messages on SRM log files RMSRA20 logs the following error messages that identify a cause of a failure as [RMSRA20] in the SRM log files. Remove the cause of the error by referring to the error messages in the SRM log files. The SRM log directory is : %ALLUSERSPROFILE%\VMware\VMware vCenter Site Recovery Manager\Logs. • On a Windows 2003 system, this translates to: C:\Documents and Settings\All Users\VMware\VMware vCenter Site Recovery Manager\Logs\. • On a Windows 2008 system, this translates to: C:\ProgramData\VMware\VMware vCenter Site Recovery Manager\Logs\. Logs roll over after reaching 5 MB by default. The file vmware-dr-index contains the most recent Log File number. Errors in XML passed from SRM 1002 Cause: A HORCM instance does not start with the specified connection address. Action: Confirm that the HORCM instance# specifying the connection address is appropriate, and whether the horcm*.conf file is exists. 1003 Cause: Authentication failed with User/Password for the specified connection address. Action: Confirm that the User/Password for the connection address is appropriate. 44 Troubleshooting RMSRA20

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
5 Troubleshooting RMSRA20
Known problems
The following problems and solutions are typical:
HP disk arrays do not appear in Site Recovery Manager
Solution:
If HP disk arrays do not appear in the Site Recovery Manager, make sure that the Site
Recovery Manager has been restarted (see
“Installation procedure” (page 23)
). Also make sure
that the array manager that SRM is connected to is actively managing arrays.
RMSRA20 does not install
Solution:
Make sure that SRM is installed. RMSRA20 will not install if SRM is not on the disk array.
Virtual machines do not start at the recovery site after failover
Cause:
The ESX recovery hosts are not configured with the correct HBA port WWN on the recovery
HP disk array. The replicated LUNs used in failover were not presented to the recovery ESX servers.
Solution:
Correctly map the replicated LUNSs to the recover ESX server.
Virtual machines do not start at the recovery site during testFailover
Cause:
The volume used for CoW/QS is set as a NO Read attribute (PAIR or SMPL state).
Solution:
Make sure that the ESX server can boot after changing to the PSUS state (Read/Write
enable).
Error Messages on SRM log files
RMSRA20 logs the following error messages that identify a cause of a failure as
[RMSRA20]
in
the SRM log files.
Remove the cause of the error by referring to the error messages in the SRM log files.
The SRM log directory is :
%ALLUSERSPROFILE%\VMware\VMware vCenter Site Recovery
Manager\Logs
.
•
On a Windows 2003 system, this translates to:
C:\Documents and Settings\All
Users\VMware\VMware vCenter Site Recovery Manager\Logs\
.
•
On a Windows 2008 system, this translates to:
C:\ProgramData\VMware\VMware
vCenter Site Recovery Manager\Logs\
.
Logs roll over after reaching 5 MB by default.
The file
vmware-dr-index
contains the most recent Log File number.
Errors in XML passed from SRM
1002
Cause:
A HORCM instance does not start with the specified connection address.
Action:
Confirm that the HORCM instance# specifying the connection address is appropriate, and
whether the
horcm*.conf
file is exists.
1003
Cause:
Authentication failed with User/Password for the specified connection address.
Action:
Confirm that the User/Password for the connection address is appropriate.
44
Troubleshooting RMSRA20