vSphere Replication shows as Disconnected in Site Recovery UI when eth1 is configured for replication traffic
search cancel

vSphere Replication shows as Disconnected in Site Recovery UI when eth1 is configured for replication traffic

book

Article ID: 412814

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

Symptoms:

  • Multiple replications are reported as Not Active.
    The VRMS shows as Disconnected in the Site Recovery UI.

  • A dedicated replication network (eth1) is configured and in use.
  • DNS lookups fail, further indicating communication issues on the management network.

 

Environment

  • vSphere Replication 8.x
  • vSphere Replication 9.x

Cause

  • The issue occurs because the replication network (eth1) is set as the default gateway instead of the management network (eth0 with Metric=1000). This causes the management network to stop working, making the Site Recovery UI inaccessible and the replications appear disconnected.
  • The routing table confirms the misconfiguration:

admin@vr [ ~ ]$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         _gateway        0.0.0.0         UG    0      0        0 eth1
default         _gateway        0.0.0.0         UG    1000   0        0 eth0

Resolution

  1. Edit the network configuration for eth0

    •  vi /etc/systemd/network/10-eth0.network

    • Remove the Metric line so eth0 can act as the default gateway.

  2. Edit the network configuration for eth1

    • vi /etc/systemd/network/10-eth1.network

    • Under the [Route] section, add:

      Metric=1000

  3. Apply the changes

    • Restart systemd-networkd service or reboot the replication appliance.

# systemctl restart systemd-networkd