I need to document which services and virtual machines are running across our VMware environment. The setup includes two rack servers and one tower server, all of which I can access physically. Our RMM tool may not show which virtual machines are hosted on which physical servers. When I connect a monitor and keyboard, the console only displays the ESXi version rather than a normal login screen. The previous administrator did not leave the vCenter credentials, although I do have the root passwords for the ESXi hosts. I need to investigate the environment without rebooting or shutting down any systems.
4 Answers
Connect an approved laptop to the ESXi management network, determine the management addresses, and browse to each host individually. Avoid guessing at network settings or making changes just to gain access. Since the environment and credentials were not properly handed over, bringing in an experienced VMware contractor for a short discovery session may be safer than experimenting on production hypervisors.
The physical console is mainly for local ESXi management and status information; it isn’t the normal place to browse the VM inventory. Once you know the host’s management address, the browser interface should provide the information you need without restarting anything. Identifying the services inside each guest VM is a separate task and may require access to the guests, directory services, or application documentation.
If you can recover access to vCenter, that’s the best place to see the complete inventory and the relationship between virtual machines and physical ESXi hosts. Tools such as RVTools can also export useful inventory details once you have authorized access. If the root credentials don’t work on the web interfaces, verify that you’re using the actual management IP and that the accounts haven’t been changed or restricted.
The ESXi console should normally show the host’s management IP address. Use that address from a browser on the management network and sign in to each host with the ESXi root credentials. The host’s web interface will list the virtual machines currently registered and running there. You shouldn’t need vCenter just to inspect each individual host. Be extremely careful not to change settings, power states, or networking while you’re investigating.
This seems like the safest starting point. I’ll first identify the management IPs and use the host interfaces only for read-only inspection.