vSphere Live Recovery replications are experiencing numerous Not Active errors.

Products

• VMware Live Recovery

Issue/Introduction

Virtual Machines are not replicating and showing as Not Active and their RPO is showing violated.

Environment

vSphere Live Recovery (all versions)

Cause

vSphere Replication appliance is not able to connect to the local ESXi hosts over port 443.

This is appearing inside the vmkernel.log of the ESXi host as not being able to connect to 127.0.0.1. For example:

2024-08-02T09:53:47.758Z Wa(180) vmkwarning: cpu66:4651443)WARNING: Hbr: 5362: Failed to establish connection to [127.0.0.1]:32032 (groupID=GID-####-####-####-####-############): Broken pipe

Verifying the issue with ping tests as well as curl tests between the ESXi host and the vSphere Replication appliance will fail without port 443 open.

Resolution

When vSphere Live Recovery is deployed, it is important to ensure that the subnet is correct for the appliance. Please check on the appliance and correct this if the subnet is wrong.