vSphere replica VM's are not reachable after reboot.

 vSphere replica VM's are not reachable after reboot

This article describes how to troubleshooting Virtual machines (VMs) by using console.

Recently I encountered the issue, vSphere replica (VRA & VRS) are not reachable after reboot.

Before troubleshooting the VM's. Take a offline snapshot of vm's.

Login console page and enter admin credentials on console.

$ sudo su

sudo su - command to go for root and administrator fully privileges. 

Go for network configuration details.

# cd /etc/systemd/network

# cd /etc/systemd/network# ls -l

List of network details with privileges. observed eth0 changed to root. 

And routing table information is not getting on command.

# cd /etc/systemd/network # route

As part of troubleshooting change the owner from root to systemd-network.

# cd /etc/systemd/network ] # chmod 644 10-eth0.network

# cd /etc/systemd/network ] # chown systemd-network:systemd-network

Now verify the network details by using below command

# cd /etc/systemd/network# ls -l

Now remove route column on eth0-network table.

# cd /etc/systemd/network# vi eth0-network

remove route line on edit (yellow highlighted) and saving the file (:wq!)

# systemctl restart systemd-networkd

# systemctl restart systemd-resolved

Issue has been fixed after remove the route column on eth0-netwok. Now IP is pinging from outside.