Enhanced replication may not work on VMs and report connection errors.
search cancel

Enhanced replication may not work on VMs and report connection errors.

book

Article ID: 419520

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

  • Enhanced replication may fail for one or more VMs and it may be successful for the rest of the VMs. However, legacy replication may work as expected.

  • Upon checking the replication reconfiguration for the VM, we see errors at the network layer.

  • You may also see warnings as below on vSphere replication UI for connectivity issues.

There are connection errors. Fix the errors before configuring replications.

Fault occurred while performing health check. Details: '503 Service Unavailable from GET
https://##.##.##.##/hbragent/api/v1.0/appPing?broker_ip=##.##.##.##&broker_port=32032&group=PING-G5714e3f0-a2e1-416d-94f5-########'.

 

Environment

  • VMware Live Site Recovery 9.x

Cause

  • The issue is seen when one or more hosts on the DR site is experiencing CRC errors on the network cards. This is resulting in intermittent connectivity between the hosts while configuring the replication.

  • This can be validated using the command below on the hosts reporting connectivity issues.

esxcli network nic stats get -n vmnicX

NIC statistics for vmnic0
Packets received: 52534452769
Packets sent: 14466977718
Bytes received: 69320750193840
Bytes sent: 7583337761970
Receive packets dropped: 0
Transmit packets dropped: 0
Multicast packets received: 316488322
Broadcast packets received: 961798728
Multicast packets sent: 396660
Broadcast packets sent: 32395
Total receive errors: 96106816
Receive length errors: 1
Receive over errors: 0
Receive CRC errors: 96106815 ================>>>> CRC errors on NICs.
Receive frame errors: 0
Receive FIFO errors: 0
Receive missed errors: 728
Total transmit errors: 7694740
Transmit aborted errors: 0
Transmit carrier errors: 7694740
Transmit FIFO errors: 0
Transmit heartbeat errors: 0
Transmit window errors: 0

Resolution

  • Please involve physical network engineer to review the reason for CRC errors on the network and fix it.

  • Fixing the network issue or isolating the affected node from the DR site is expected to resolve the errors and replication to work.