After updating vCenter Server via SDDC Manager, all ESXi hosts enter a 'Not Responding' state.

Products

• VMware vCenter Server 8.0
• VMware SDDC Manager

Issue/Introduction

After updating the vCenter Server via the SDDC UI, all ESXi hosts display a status of "Not Responding" within the vCenter inventory.

1. Attempting to ping an ESXi host from the vCenter appliance fails with the following error:

ping: connect: Network is unreachable

2. Inspecting the network configuration file (/etc/systemd/network/10-eth0.network) on the affected vCenter reveals that the Gateway IP entry is missing.

Problematic Output (Current State) Note the absence of the Gateway parameter under the [Network] section.

root@vCenter [ ~ ]# cat /etc/systemd/network/10-eth0.network
[Match]
Name=eth0

[DHCPv4]
SendRelease=false

[Network]
Address=XXX.XXX.XXX.XXX
LinkLocalAddressing=no
DHCP=no

[DHCP]
UseDNS=false

Healthy Output (Expected State) The correct configuration includes the Gateway IP.

root@vCenter [ ~ ]# cat /etc/systemd/network/10-eth0.network
[Match]
Name=eth0

[DHCPv4]
SendRelease=false

[Network]
Gateway=XXX.XXX.XXX.XXX
Address=XXX.XXX.XXX.XXX
LinkLocalAddressing=no
DHCP=no

[DHCP]
UseDNS=false

Environment

vCenter 8.x

SDDC 5.x

Resolution

Update Default Gateway IP

 

• Run "/opt/vmware/share/vami/vami_config_net".

• Select Option 2 (Default Gateway).

• Input the correct Gateway IP.

• Verify ESXi hosts reconnect automatically.