Hi,
I looked at the two links that you had provided. For the first one, I did try resetting the System Configuration from dcui and when the ESXi host rebooted, it came back up with what appeared to be the same configuration along with the same issue.
Regarding the second link, I did check out my gateway and it appears to be correct. I found a command to list the routes table and I was able to ping the gateway without any issues:
I was also able to ping Google and perform a traceroute:
The only thing with the traceroute that I wasn't sure of was hope 2 and hope 10 as they both had * * * instead of information. I don't normally use traceroute so I'm not sure if that is normal or not. I figure that since the ESXi host was able to get out on the internet then it wasn't a gateway issue.
I did some more searching and came across this command: esxcli network ip route ipv4 list
I thought it might be similar to the esxcfg-route command but when I ran it, I got this error message:
I don't know if the esxcli commands use a local service that might not be running similar to the issue that I am having with the hostd service. I went back into dcui and ran the Test Management Network and something was different. It failed the lookup check:
In the past all three options reported OK. I checked /etc/hosts and it looks fine to me:
Even though the dcui test failed to resolve the hostname localhost, I was still able to ping it and perform a nslookup on it both returning the correct results:
I've done another re-install of the ESXi host just to make sure that me testing different things wasn't breaking anything and even with a fresh install I still get the 503 Server Unavailable and 503 Service Unavailable messages.
Is there a way to increase the log details to maybe shed some light as to what is going on? Is there anything else I can try to see why this isn't working?
Thanks!