Just a small ESXi Pro tip this time. I recently had a host that was experiencing issues and the management services were unresponsive. This is a major problem for troubleshooting as the esxcli commandset won’t work anymore at this stage.

Now by accident I came across a tip from the Getting Started with vSphere Command-Line Interfaces documentation over at the VMware {code} website.

On the overview of vSphere Command-Line Interfaces the various methods of managing a host are explained. And as most of you will recoginise the majority of these methods use the API. There are however some exceptions and for this article I’d like to specifically point out localcli.


The use of this tool comes with a big disclaimer. You should only use this tool for troubleshooting purposes and NOT to make changes to the configuration of a host as this can lead to an inconsistent system state.

At first glance the command seems to support the complete list of namespaces available in esxcli.

I only used localcli to do a few harmless checks. And when I knew for sure there’s no way I was going to recovery this host myself I decided to wait for VMware Technical Support to contact me.

Leave a Reply

Your email address will not be published. Required fields are marked *