I am here today to share some of the my experience that face in integrating SRM (SRA 2.2) with RecoverPoint v4.1.2.
Issue:SRA command 'discoverArrays' failed.
Cause:
Failed opening session for user to site mgmt IP.
Please see server logs for further details.
Fix:
enable Https at the vCenter server of both the production and the recovery site,
open a Windows command prompt and go to the directory
C:\Program Files\VMware\VMware vCenter Site Recovery Manager\storage\sra\array-type-recoverpoint
> Run (at production and recovery site):
command.pl --useHttps true
> after the cmd run successfully, we will see the http file on the file directory.
>enable https in recovery Point on Both RPA Cluster
Login to the RPA Cluster with admin account
Tricky part is here, some rpa come with Http & Https both enable. To fixed our issue we need only Https.
If it is already enable don't change anything, Like below
>> Register the RPA's Cluster in SRM with boxmgmt Account
Another issue you might get Issue: Cannot enable the array pairs - option Greyed out
This is because of SRM Manage Mode should be enable at the RecoverPoint CG Level.
If you still face any issues, Comment the post, i will try to answer in best of my knowledge.
Issue:SRA command 'discoverArrays' failed.
Cause:
Failed opening session for user to site mgmt IP.
Please see server logs for further details.
Fix:
enable Https at the vCenter server of both the production and the recovery site,
open a Windows command prompt and go to the directory
C:\Program Files\VMware\VMware vCenter Site Recovery Manager\storage\sra\array-type-recoverpoint
> Run (at production and recovery site):
command.pl --useHttps true
> after the cmd run successfully, we will see the http file on the file directory.
>enable https in recovery Point on Both RPA Cluster
Login to the RPA Cluster with admin account
Tricky part is here, some rpa come with Http & Https both enable. To fixed our issue we need only Https.
If it is already enable don't change anything, Like below
>> Register the RPA's Cluster in SRM with boxmgmt Account
Another issue you might get Issue: Cannot enable the array pairs - option Greyed out
This is because of SRM Manage Mode should be enable at the RecoverPoint CG Level.
If you still face any issues, Comment the post, i will try to answer in best of my knowledge.
I have made the changes recommended on the SRM servers and on the RPAs as well. Still face the issue on SRM 6.1.1. SRA command 'discoverArrays' failed. Cause:Failed opening session for user to site mgmt IP. Please see server logs for further details.
ReplyDeletei have the same issue here, tried to enable https no joy, restarted srm services/servers too no luck
ReplyDeleteGreat thanks to you,
ReplyDeleteI have followed this document and resolved the "session issue" by enable the HTTPS.
i would like brief my issue.
1,Recoverpoint SRA not listed in SRM, even though, RPsra installed,Java installed, .net3 installed.
Error : "storage replication adapter not installed"
ReSolution @ SRM installed server "Add Java path in "system variables - path "
@ Recoverpath (storage) a, " update the Host OS as "Esxi and windows"
b, " External application "SRM"
c, " Managed by "SRM"
2,when adding array pair
Error "SRA command 'discoverArrays' failed. Failed opening session for user to site mgmt IP. Please see server logs for further details"
Resolution 1, performed the A & B in the SRM installed server in both the site
a,CD "c:\Program Files\VMware\VMware vCenter Site Recovery Manager\storage\sra\array-type-recoverpoint"
b,"C:\Program Files\VMware\VMware vCenter Site Recovery Manager\external\perl\perl\bin\perl.exe" command.pl --useHttps true ( update the
correct "perl" path according to the installed folder"
But still session error persist, So followed your document on Storage side to enable @ Recoverpoint for HTTPS
Resolution 2, Another possibility is to enable HTTP access on RPA1 at each site.
-Log into the RPA with the boxmgmt account
-option 2 setup
-option 8 advanced options
-option 2 security options
-option 1 web server mode
(As per your screenshot.)
All issue resolved