Enhanced Replication Mapping Errors and failed health check tasks.
Article ID: 441402
Updated On:
Products
Issue/Introduction
Multiple failed health check tasks:
Fault occurred while performing health check. Details: "connection timed out: /###.###.##.###:443; nested exception is io.netty.channel.ConnectTimeoutException: connection timed out: /###.###.##.###443'.
Failed Enhanced Replication mappings tests.
Environment
vSphere Replications 9.0.2.3
vCenter 8.0 U3
Cause
vCenter Appliance was set p with two management vmkernels. Only one of the used network can be pinged from VR.
The vSphere Replication HMS service automatically attempts to connect to the first management vmkernel IP reported by vCenter. In this multi-homed configuration, the unreachable .## subnet is prioritized over the functional .# subnet.
Resolution
Permanent Fix
Upgrade to vSphere Replication 9.1.1.0 after is relesed. This version includes a code fix to properly resolve the selection logic for multi-homed management networks, ensuring the service can identify and use the correct functional path.
Workaround
Perform the following steps to reorder the VMkernel interfaces:
1 Identify the reachable management network required for replication.
2 Reconfigure the ESXi host networking so that the reachable interface is assigned as vmk0 (the first interface in the sequence).
3 Ensure that vMotion traffic is not enabled on the same interface as Management traffic if that interface is the primary vmk0.
Feedback
