Q: 8
An administrator is tasked to install a new VMware ESX host to an existing cluster. When the
installation is completed, the host is not able to be reached from the vCenter.
When testing the host's management network, the default gateway, primary DNS, and secondary
DNS are all unreachable, and the host name cannot be resolved. The VLAN for the management
network is set correctly and the adapters are all connected.
What is the first step in troubleshooting this connectivity issue?
Options
Discussion
Wouldn’t checking the management network TCP/IP config be first? If the gateway and both DNS are unreachable, that usually points to a bad IP, subnet, or gateway setting on the host. I remember seeing similar in practice exams. Anything else would just waste time if IP settings are wrong anyway.
C here
Could flip to D if adapters were showing down, but here all adapters are up so I think A is more likely.
Its A here. If the host can't reach anything (gateway, DNS) but VLAN is good and cables are connected, that's a classic sign the TCP/IP config is off. D can be tempting but if all physicals are connected, doesn't add up. Seen this trip folks up on labs.
A imo, had something like this in a mock before. If the host can't hit gateway or DNS and VLAN's fine, it's usually a TCP/IP config issue. Checking IP, subnet mask, gateway is always the first move. Agree?
Be respectful. No spam.
