SRA logs on the VLSR appliance indicate that the SRA is trying to connect to the vCenter with the wrong FQDN. This can be validated from the VLSR appliance's /opt/vmware/support/logs/srm/SRAs/sha256_########/EmcSrdfSra_###.log:
[20260219131446 55883 471 [email protected]] vCenter server details are: FQDN [<vCenter_FQDN_1>] Username [<vcenter_username>][20260219131446 55883 59 [email protected] ] Connect to Virtual Client fails. Reason: An SSL related error has occurred.[20260219131446 55883 2292 [email protected]] [WARNING]: Failed to connect to virtual center. Please check if you have provided valid vcenter credential in symmetrix authorization DB.[20260219131446 55883 2293 [email protected]] [WARNING]: SRA will continue without filtering NON VMWare devices.Due to this it reports that the SRA will continue without filtering the non VMware devices.
The vCenter's actual FQDN is <vCenter_FQDN_2>.
VMware Live Site Recovery 9.x with Dell SRDF Storage Replication Adapter
The vCenter server details (FQDN and username) with the wrong FQDN is stored within the SRA's configuration file.
The Dell SRA installation on VLSR/SRM appliance involves:
Installing the SRA to the VLSR/SRM appliance.
Running the Dell provided script "enableAutoSSLCertGen.sh".
In this script the vCenter FQDN and credentials are provided for vCenter authorization and to enable the "FilterNonVMwareDevices" SRA feature.
During installation of the SRA the vCenter's FQDN would have been "<vCenter_FQDN_1>", and it may have been changed to "<vCenter_FQDN_2>" later on.
Since this has not been changed within the SRA after the vCenter's FQDN changed, the SRA continues to try and connect to the previous FQDN.
Contact the SRA vendor, Dell, to update the vCenter credentials within the SRA's configuration file.
Kindly refer the below 3rd party documents from Dell regarding the SRA installation: