DNS resolution error during SRM site pairing

DNS resolution error during SRM site pairing

During SRM Site pairing from OnPrem to VMC SDDC, below error might be seen

pastedImage_0.png

This document assumes that you have fresh deployment of OnPrem SRM and it has not been configured/paired with any site. If you have an existing configured/paired production/development/test OnPrem SRM instance, please contact support and do not proceed.

In the above screenshot you should have registered OnPrem vSphere Replication appliance as well however this document focuses on SRM DNS error.

Cloud SRM reaches out to OnPrem PSC and checks for OnPrem SRM url, to setup site pairing with.

If the OnPrem SRM is registered with hostname and not FQDN, above error might come up.

High level steps that we need to follow

  • Verify OnPrem SRM is registered with OnPrem PSC via hostname.
  • Unregister OnPrem SRM with OnPrem PSC
  • Change the OnPrem hostname to fqdn
  • Generate new self signed cert for OnPrem SRM
  • Register OnPrem SRM with OnPrem PSC via FQDN
  • Complete SRM site pairing operation

To verify if the OnPrem SRM is registered with hostname and not with FQDN ; navigate to OnPrem PSC by editing below url

https://vcsa11.home.local/lookupservice/mob?moid=ServiceRegistration&method=List

Change the value field as below and click on Invoke method

pastedImage_2.png

Try to search via OnPrem SRM hostname, FQDN registration is not seen.

pastedImage_4.png

Now we need to unregister OnPrem SRM from PSC. Login to SRM VAMI page >> summary tab and click on unregister

pastedImage_0.png

Check all the options and click on unregister

pastedImage_1.png

When it completes, you should see similar screen

pastedImage_4.png

We now need to change OnPrem SRM hostname to FQDN. Navigate to networking tab on SRM VAMI portal and click edit >> enter FQDN and hit save.

pastedImage_5.png

You should see new hostname on portal.

pastedImage_6.png

To generate new self signed OnPrem SRM cert, navigate to access tab on SRM VAMI portal and click on cert change.

pastedImage_7.png

Make sure SRM FQDN is seen with FQDN and right IP. Enter the organization details and click on change

pastedImage_8.png

Post changing the default cert, we need to refresh the browser and accept new cert. On the browser we should now see cert with FQDN.

pastedImage_9.png

Let's proceed registering OnPrem SRM with PSC. Click on the summary tab on SRM VAMI portal and click on configure appliance.

Enter OnPrem PSC details and hit next. Enter the details for name/extension ; make sure that hostname comes as FQDN and finish the wizard

pastedImage_0.png

We can verify now if the SRM registration on PSC comes up with FQDN

pastedImage_7.png

SRM site pairing now should not return initial error message and would go through.

Version history
Revision #:
1 of 1
Last update:
‎04-07-2020 12:13 AM
Updated by: