[VMC on AWS] Failed to pair on-premise Site Recovery Manager (SRM)

Products

• VMware Cloud on AWS

Issue/Introduction

Best practices regarding DNS to pair on-premise SRM to VMC SRM

Symptoms:
SRM site pairing fails 




SRM logs 

2019-12-17 04:20:03,821 [srm-reactive-thread-1] WARN  com.vmware.srm.client.reactive.impl.PromiseIm
pl 3448735673820395734 0c56c9e4-5cfe-4e57-b502-0808fe53be7b probeServices - Function 'com.vmware.dr
.client.shared.pairing.ProbeServicesRequestHandler$$Lambda$532/752947785@4e0a973f' failed.
java.lang.IllegalArgumentException: host
        at org.apache.commons.lang.Validate.notEmpty(Validate.java:321)
        at com.vmware.dr.client.shared.pairing.utils.CertInfo.<init>(CertInfo.java:32)
        at com.vmware.dr.client.shared.pairing.ProbeServicesRequestHandler.lambda$null$157(ProbeSer
vicesRequestHandler.java:357)
        at com.vmware.srm.client.reactive.impl.PromiseImpl$ApplyCompletion.complete(PromiseImpl.jav
a:244)

srms = {
         LsppService {
         _serviceNameDefault = vCenter DR service
         _serviceVersion = 8.2.0.14761908
         _endpoints = [LsppService.LsppServiceEndpoint {
            protocol = vmomi
            type = com.vmware.dr.vcDr.configure
            url = https://vsphere_srm.xxxxxxxx.local:5480/configureserver/sdk
            }, LsppService.LsppServiceEndpoint {
            protocol = vmomi
            type = com.vmware.dr.extApi
            url = https://vsphere_srm.xxxxxxxx.local:443/drserver/vcdr/extapi/sdk
            }, LsppService.LsppServiceEndpoint {
            protocol = vmomi
            type = com.vmware.dr.vcDr
            url = https://vsphere_srm.xxxxxxxx.local:443/drserver/vcdr/vmomi/sdk
            }]
         _type = vcDr
         _siteId = default-site
         _id = 74755a30-58e8-4372-932c-aae455d62a33
         _nodeId = 212ab706-d7a3-4720-9515-05e280a56d92
         _product = com.vmware.dr
         _attributes = {vmodlVersion=/drserver/vcdr/vmomi/drversion.xml, supportedVmodlVersions=/drserver/vcdr/vmomi/drserviceversions.xml, extensionKey=com.vmware.vcDr, vcInstanceUuid=bedcd8fa-8c0f-4c83-abdc-8a1dc13e5893}
         _ownerId = [email protected]
         }
   }

Cause

This is caused because of the ( _ ) in the hostname. Example : vsphere_srm.xxxxxxxx.local

Resolution

Remove the special character from the hostname and replace it with the supported character. Review Microsoft's documentation regarding the allowed special characters in the DNS: Naming conventions inactive directory