VMware Live Recovery 9.0.3 resource mappings error "There is no network connectivity between the source host ... and target broker ... "
search cancel

VMware Live Recovery 9.0.3 resource mappings error "There is no network connectivity between the source host ... and target broker ... "

book

Article ID: 411584

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

Getting following error in resource mapping after converging to 9.0.3:
There is no network connectivity between the source host (id: 'host-######'. name: '<hostname>') and the target broker '##.##.##.##' Details: 'Connect Input/output error'.

Running command in SSH gives the IP of the old replication appliance:
/opt/vmware/vpostgres/current/bin/psql -U admin -d vrmsdb -c "SELECT vsrv_certificate, vsrv_thumbprint, replicationtrafficaddress FROM hbrserverentity WHERE vsrv_address LIKE '127.0.0.1'"

Environment

Vmware Live Recovery 9.0.3

Cause

IP address and broker certificate did not get updated.

Resolution

Perform following steps:

1. Take snapshot of the appliances at both sites

2. Execute following commands on both sites to update IP & broker certificate:

Update IP address:
opt/vmware/vpostgres/current/bin/psql -U admin -d vrmsdb -c "UPDATE hbrserverentity SET replicationtrafficaddress='<IP of the replication appliance>' WHERE vsrv_address LIKE '127.0.0.1';"

Update certificate:
Execute command to obtain certificate to update:
echo -e "\n""Run the following command after verifying:\n""#/opt/vmware/vpostgres/current/bin/psql -U admin -d vrmsdb -c \"UPDATE hbrserverentity SET vsrv_certificate='`sudo cat /opt/vmware/etc/hbr/hbrsrv.crt`', vsrv_thumbprint='`sudo openssl x509 -sha256 -noout -fingerprint -in /opt/vmware/etc/hbr/hbrsrv.crt | sed s'#sha256 Fingerprint=##'`', replicationtrafficaddress='`ifconfig eth0 | grep inet | awk '{print $2}'`' WHERE vsrv_address LIKE '127.0.0.1';\""
From the above command execute the update command it provides to update the database.

3. Repeat above for other site.
4. Reboot the appliances
5. Allow 24 hours for resource mappings to update status.