esxtop command shows that the management vmk (in this case vmk0) doesn't have any vmnic associated and shows void as in below screenshot
As for any network connectivity, it is crucial for the management VMkernel to have an uplink associated with it. Since in this case there was no uplink attached to the DVS/Management vmk, host lost network connectivity
esxtop command and confirm it has a valid uplink associated with it and required vLANs are allowed on the uplink esxcfg-vswitch -Q vmnicX -V dvPort_ID_of_vmnic "dvSwitch" # Remove/unlink a vDS uplinkesxcfg-vswitch -P vmnicX -V unused_dvPort_ID "dvSwitch" # Add/link a vDS uplink
For more troubleshooting steps, refer: Troubleshooting an ESXi host in a "not responding"/"disconnected" state