SRA Command "discoverDevices" Error "Failed to connect to array management host" on the Primary Site

Summary: Storage Replication Adapter (SRA) command "discoverDevices" fails with message "Failed to connect to array management host" on the primary site.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Error in SrdfSRA logs from either site:

[03/23 16:12:54  08332                      0114  SymapiSession::Init                      ] Initializing SYMAPI session for remote server [1xx.1x.2.1:2707]
[03/23 16:12:54  08332                      0120  SymapiSession::Init                      ] SymInit() [ReadModifyNowrite]
[03/23 16:12:58  08332                      0130  SymapiSession::Init                      ] [ERROR]: Failed to perform SymInit().
 
[ERROR]: [SYMAPI_C_NET_OPR_ERROR : A remote send or receive operation failed]
[03/23 16:12:58  08332                      0025  SymapiSession::SymapiSession             ] [ERROR]: Failed to initialize Symapi session

Error in the Solutions Enabler storsrvd log:

03/23/2022 16:12:55.835  : ANR0151E Common Name in client certificate not valid: expected "SrmHostname", received "storsrvd fac838c410cd"

Or

03/23/2022 16:12:55.835  : ANR0151E Common Name in client certificate not valid: expected "SrmHostname", received "storsrvd 1xx.1x.2.1"

Cause

Causes of this issue may be:
  • A blocked firewall-Each Site Recovery Manager (SRM) or SRA docker host must be able to connect to both Solutions Enabler (SE) hosts' storsrvd daemon. The default port is 2707.
  • The Domain Name System (DNS) hostname or IP is not resolved correctly.
  • An incorrect client certificate
  • All Remote Data Facility (RDF) devices are in adaptive copy mode. SRA ignores all RDF devices in adaptive copy.

Resolution

The User's firewall team must open port 2707 (or another port if the user has changed the default storsrvd port).

There are three options to resolve the client certificate:
  • Set the storsrvd on the server to not verify (ignore) client certificate variables in the command-line prompt:
  1. Open installdir/symapi/config/daemon_options and set the variable as shown below, then restart storsrvd daemon:
storsrvd:SECURITY_CLT_SECURE_LVL  = NOVERIFY
  • Set the storsrvd on the server to use Nonsecure connections:
  1. Open installDir/symapi/config/options, and set the variable as shown below, then restart storsrvd daemon:
SYMAPI_SECURITY_LEVEL = NONSECURE
  • Update the Solutions Enabler certificate on the SRA docker:
  1. Log in to the SRM docker as 'admin'.
  2. Switch to root user
su root
  1. Connect to the docker
Screenshot of connecting to docker
  1. Check the current hostname of the SE certificate
Check current hostname
  1. If the certificate does not list the hostname, create a new certificate
Create a new certificate
  1. Lockbox password is 'dockerID@SELockbox1'. In this example, it is '0c6837ce4e7b@SELockbox1'.

Additional Information

Troubleshooting Checks:
  • Check array configuration.
  • Try using IP and hostname to rule out DNS issues.
  • Verify that RDF daemon is up and running on both sides and enabled in the options file.
  • Verify vCenter user credentials are present
symcfg auth list -vmware
  • Verify that the environment has an open network.
  • Check that port 2707 is listening, rule out firewall issues.
  • Ensure that there are no RDF link issues.
Article Properties
Article Number: 000167652
Article Type: Solution
Last Modified: 14 Feb 2024
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.