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

  • VMware ESXi 5 home lab upgrade

    In the past I’ve been using a single server to run my VMware ESXi home lab. it was slow, old, big and loud. I’ve been meaning to upgrade my home lab for a while and just never got around to it, until now! When looking for new hardware I wanted the servers to be as compact as possible, quiet, and low energy usage as possible while still having some horsepower.

    I debated on going the whitebox solution as I build all my own desktops anyway, I also looked at several other solutions such as the HP ML310e server, Shuttle XH61V barebones machine, but ultimately decided to go with two Intel NUC i5’s.

    Intel NUC i5 and 16GB ram

    Intel NUC i5 DC53427HYE Features:

    • Uses very little energy
    • Completely quiet
    • Supports up to 16GB RAM
    • A dual core CPU that scores nearly 3,600 in PassMark benchmarking
    • Includes vPro which allows me to easily run both NUC’s headless
    • Extremely small, nearly 4 1/2″ inch square footprint

    Read More “VMware ESXi 5 home lab upgrade”

  • How to easily add an ESXi SSH login message banner

    ESXi issues message

    Preparing for some upcoming audits, I noticed one of the checkpoints was to ensure each ESXi host was configured with a warning banner stating the machine is being monitored and audited when someone logs into the ESXi host via SSH. This type of message is something you see on most any company or government computer before you login.

    There are two message types that can be used to achieve this, the first being login banner (/etc/issue) and MOTD (/etc/motd). The difference between the two are where they are shown. The login banner is shown between the username and password inputs during login, while the MOTD is displayed after a user has successfully logged into SSH.

    Read More “How to easily add an ESXi SSH login message banner”

  • VMware vCenter 5.0 Update 1a released

    VMware vCenter 5.0 Update 1a has just been released and is the first major update since version 5.0.

    The main improvements being:

    • vCenter Server 5.0 Update 1a introduces support for the following vCenter Databases
      • Oracle 11g Enterprise Edition, Standard Edition, Standard ONE Edition Release 2 [11.2.0.3] – 64 bit
      • Oracle 11g Enterprise Edition, Standard Edition, Standard ONE Edition Release 2 [11.2.0.3] – 32 bit
    • vCenter Server Appliance Database Support: The DB2 express embedded database provided with the vCenter Server Appliance has been replaced with VMware vPostgres database. This decreases the appliance footprint and reduces the time to deploy vCenter Server further.

    Read More “VMware vCenter 5.0 Update 1a released”

  • VMware View client now availabe for Android!

    VMware has announced that they have released a View Client for Android tablets available on the Android Market now. Here are just a few of the features found on the new client.

    • A new look and feel – The View Client for Android features the NEW blue look and feel of the VMware View clients!
    • Multiple broker support – If you have more than one VMware View broker in your organization, you can can easily access your desktop from all of them via the Android client
    • Desktop Shortcuts – Quickly connect with as many as four recent desktop via shortcuts
    • Virtual trackpad – Control your desktop on a granular level just like you would control the mouse on a laptop
    • Custom keyboard toolbar – Super easy access to all of the special keys not found on the Android default keynboard
    • Honeycomb 3.x support – Made from the ground up for the new generation of Android tablets
    • Custom gestures – Invoke keyboard, scrolling, etc are as easy as ever and simple to use
    • VMware View Security Server support (best experience) – No need to have VPN when you use VMware View Security Server
    • Background tasking – Switch between apps on your tablet and come right back

Leave a Reply

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

2 Comments