vCenter loses network after VCHA has been destroyed

Products

• VMware vCenter Server

Issue/Introduction

• vCenter stops responding to pings.
• vCenter services will be down except observability, vmware-vdtc and vmware-vmon.
• vCenter repair using the vami config tool also reverts the IP changes back to null and vCenter would lose network.
• vCenter contains 10-eth0.network.manual file instead of 10-etho.network file under /etc/systemd/network.

 

Environment

7.x, 8.x

Cause

VCHA destroy has left stale entries or has not been done properly.

Resolution

Change the name of the file 10-eth0.network.manual to 10-eth0.network by removing .manual from the file name. The file can be found under /etc/systemd/network in the vCenter web console.

Example: mv /etc/systemd/network/10-eth0.network.manual /etc/systemd/network/10-eth0.network

Or from within the network folder: mv 10-eth0.network.manual 10-eth0.network

 

Additional Information

japaneseKB:VCHA構成の削除後、vCenter への疎通不可事象が発生する