SRM Configuration and Site Pairing fails with "error id = 32" due to latency in the environment

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

• The vCenters are configured in enhanced linked mode, with sites located far apart, resulting in latency within the environment.
• The following error can occur when registering SRM or performing a Site Pair:

2020-09-25T20:42:26.709Z error drconfig[01747] [SRM@6876 sub=Default opID=312e9e50-e51c-450d-ada5-9d0bd58be471-validateConnection] Failed to send response to the client
--> N7Vmacore11IOExceptionE System exception while trasmitting HTTP Response:
--> error id = 32
-->
--> [context]zKq7AVECAAQAANKIAQEMZHJjb25maWcAAK7XFmxpYnZtYWNvcmUuc28AAG+dHgC+tR4Ab7YeAcQpF2xpYnZtb21pLnNvAAKfqgVsaWJkci12bW9taS5zbwACYrAFALWeKwC41isAD904A5V0AGxpYnB0aHJlYWQuc28uMAAEDwMPbGliYy5zby42AA==[/context]
--> [backtrace begin] product: VMware vCenter Site Recovery Manager, version: 8.3.1, build: build-16877778, tag: drconfig, cpu: x86_64, os: linux, buildType: release
--> backtrace[03] libvmacore.so[0x0016D7AE]
--> backtrace[04] libvmacore.so[0x001E9D6F]
--> backtrace[05] libvmacore.so[0x001EB5BE]
--> backtrace[06] libvmacore.so[0x001EB66F]
--> backtrace[07] libvmomi.so[0x001729C4]
--> backtrace[08] libdr-vmomi.so[0x0005AA9F]
--> backtrace[09] libdr-vmomi.so[0x0005B062]
--> backtrace[10] libvmacore.so[0x002B9EB5]
--> backtrace[11] libvmacore.so[0x002BD6B8]
--> backtrace[12] libvmacore.so[0x0038DD0F]
--> backtrace[13] libpthread.so.0[0x00007495]
--> backtrace[14] libc.so.6[0x000F030F]
--> [backtrace end]
2020-09-25T20:44:47.658Z verbose drconfig[01754] [SRM@6876 sub=DrConfigSRAManager opID=b137502a-7396-4b37-a041-c95652fb569f-getSraImages:3c91:87fe] Deactivating drConfig.ConfigurationTask:b7f5c5a9-b043-4316-9e51-170ffa55f030:DrConfigConfigurationTask1

Environment

VMware Site Recovery Manager 8.x

Cause

This is caused due to default timeout value of 30 seconds set in SRM

Resolution

• Ensure that all necessary ports are open between the sites.
• Verify the file /etc/vmware-rhttpproxy/endpoints.conf.d/vpxd-rhttpproxy-endpoint.conf on the vCenter and confirm that the vCenter FQDN is in lowercase.
• If any uppercase entries are found, add corresponding lowercase entries at the bottom.
• On the SRM Appliance, edit the file /opt/vmware/dr-client/lib/h5dr.properties and increase the following values to 90000 (90s), 120000 (120s), or even 150000 (150s)

responseTimeout=90000
connectTimeout=90000
socketTimeout=90000