How to fix “SRA command discoverArrays failed” in SRM with RecoverPoint

Recoverpoint SRA command discoverArrays failed

We’ve ran into an issue trying to get VMware SRM and SRA 2.2.0.3 along with EMC Recoverpoint 4.1.2 to communicate with one another and would receive this error in SRM:

SRA command discoverArrays failed. Failed opening session for user to site mgmt IP.

Please see server logs for further details.

After some digging around a bit and talking with the Storage Team and EMC we found out that this is due to the SRA’s using HTTP by default and Recoverpoint 4.1.2 does not accept HTTP, but instead only accepts HTTPS or port 443. The steps below is how to get everything to default HTTPS and then communication will resume.

How to enable HTTPS on EMC SRA

  1. Log into the server where SRM is currently installed.
  2. Open a Windows command prompt and move to the following directory:
    c:\Program Files\VMware\VMware vCenter Site Recovery Manager\storage\sra\array-type-recoverpoint
  3. Now type in the following command:
    "c:\Program Files\VMware\VMware vCenter Site Recovery Manager\external\perl\bin\perl.exe" command.pl --useHttps true

    useHTTPS command.pl

You will also need to perform the above steps on both the protected and recovery sites.

Enable only HTTPS on each RecoverPoint Appliance (RPA) Cluster

  1. Log into the RPA cluster with the admin account.
  2. Select option 2 for Setup.
  3. Select option 8 for Advanced Settings.
  4. Select option 2 for Security Options.
  5. Then finally option 1 to change Web Server Mode.
  6. You will then get the following message:
    The web server is currently in both HTTPS and HTTP available mode. Do you want to disable the HTTP server (y/n) ?

    You want to answer Y to disable HTTP.

Again you’ll want to ensure both RPA’s at the protected and recovery sites are configured the same.

After completing the steps at both sites, ensuring only HTTPS is used throughout the errors have gone away and SRM is happy once more and the dreaded “SRA command discoverArrays failed” and “Failed opening session for user to site mgmt IP” are gone.

srm sra success

Similar Posts

  • How to change vCenter Operations Manager session timeout

    I’ve been using vCenter Operations Manager for a while now at work for all the great information that can be found about our environment so I tend to log into vCOp at the start of the morning and then come back to as I may or may not need it thoughout the day. One thing that has kind of annoyed me is having to constantly log into the standard UI multiple times a day due to the default 30 minute timeout value.

    Luckily, with a bit of SSH and a few commands we can increase this timeout to anything we like or even disable it all together!

    Read More “How to change vCenter Operations Manager session timeout”

  • VCP5 Exam: Passed

    Pass

    This morning I took the VCP510 exam and passed it on my first go at it!

    Overall I felt the exam was a nice challenge, while I can’t go into details of the exam, per the NDA. I will say I was surprised at the number of multiple answer questions and the VPC510 was certainly more “real-world” based and not so much memorizing config maximums.

    That said, I’ll do as others have done and list what I used in my preparation for the VCP510 exam…

    Read More “VCP5 Exam: Passed”

  • HTML5 Embedded Host Client, this looks promising

    It’s no secret many people have really disliked the vSphere web client, it’s very sluggish, clunky, and based on flash (flash comes with it’s own security issues). It was rumored and highly hoped that vSphere 6 might be re-written in HTML5, but sadly this didn’t and hasn’t happened yet. While vSphere 6 did improve a bit on the web client the issues many people have had with it in the past still remain today.

    Enter the VMware HTML5 Embedded Host Client fling. I’ve been using and following this fling for a while now and have really enjoyed it and with each release it keeps getting better and better.

    The Embedded Host Client fling is based on HTML5 which allows it works great across all kinds of platforms, it’s fast, responsive, and doesn’t require any plug-ins – YES the VM console works great. If this happens to be a look of what’s to come in a new VMware vSphere web client, then a client is looking very promising!

    If you haven’t tried it yet, you should. It’s extremely easy to install and doesn’t even require a reboot just follow these simple instructions.

    Read More “HTML5 Embedded Host Client, this looks promising”

  • ESXi 5.5 free edition removes 32GB memory limit

    There have been a ton of exciting announcements coming out of VMword 2013, one of which is vSphere 5.5 and all of it’s improvements and additions. Along that note, VMware has changed ESXi 5.5 free version to remove the physical RAM limit which was limited to only 32GB in version 5.1.

    The new virtual hardware, version 10, we can now grow our home labs into more powerful VM’s as most all configuration maximums have been doubled:

    Read More “ESXi 5.5 free edition removes 32GB memory limit”

  • vSphere 5.1 Release Date leaked, maybe?

    Looks like Sammy Bogaert over at Boerlowie’s Blog has possibly found the release date of vSphere 5.1… maybe?

    I was about to download vSphere Update Manager PowerCLI 5.0.

    I followed the main site and wanted to check the documentation first. So I clicked the Documentation button.

    vmware update manager

    This lead me to the Docs of Update Manager PowerCLI 5.1! That’s right, 5.1! With a release date of 10 September 2012.

    vsphere5.1 release date

    None of the links for 5.1 work, so no news on any new features…

    Guess somebody at VMware was a bit too fast to update the website

    Nice find Sammy, guess time will tell if the Sept. 10th date is the actual release date or not.

  • Upgrade VCSA 6.5 to VCSA 6.7 Update 1

    VMware vCenter 6.7 U1 has recently been released. Last week I posted how to upgrade VCSA 6.7 to 6.7 Update 1, this post will walk you though upgrading VMware vCenter Server Appliance 6.5 to VCSA 6.7 Update 1!

    When doing a VCSA version upgrade the upgrade process is much different, than going from say 6.7 to 6.7 U1. When going from 6.5 to 6.7 the upgrade is actually broken up into two stages.

    The first stage involves deploying a brand new vCenter 6.7 appliance. Then the second stage will copy the data from your 6.5 VCSA into the newly deployed 6.7 VCSA from stage 1.

    Read More “Upgrade VCSA 6.5 to VCSA 6.7 Update 1”

Leave a Reply to GokhanK Cancel reply

Your email address will not be published. Required fields are marked *

2 Comments