6.5

Running Host Management
Commands in the ESXi Shell 3
Usually, installing vCLI and running commands from a remote system, with one or more hosts as targets, is
recommended. However, for maintenance and troubleshooting tasks you might prefer to run ESXCLI
commands in the ESXi Shell or connect to the ESXi Shell with SSH.
To run commands, you must rst establish access to the ESXi Shell.
This chapter includes the following topics:
n
“ESXi Shell Access with the Direct Console,” on page 25
n
“Remote ESXi Shell Access with SSH,” on page 27
n
“Lockdown Mode,” on page 28
n
“Run an ESXCLI Command in the ESXi Shell,” on page 28
ESXi Shell Access with the Direct Console
An ESXi system includes a Direct Console User Interface (DCUI) that you can use to start and stop the
system and to perform a limited set of maintenance and troubleshooting tasks.
You can use the direct console to access the ESXi Shell, which is disabled by default. You can enable the
ESXi Shell in the direct console or by using the vSphere Web Client. You can enable local shell access or
remote shell access.
n
With local shell access, you can log in to the shell directly from the Direct Console. See “Enabling Local
ESXi Shell Access,” on page 26.
n
With remote shell (SSH) access you can connect to the host by using a shell such as PuTTY, specify a
user name and password, and run commands in the shell. See “Remote ESXi Shell Access with SSH,” on
page 27.
The ESXi Shell includes all ESXCLI commands, a set of deprecated esxcfg- commands, and a set of
commands for troubleshooting and remediation.
I All ESXCLI commands that are available in the ESXi Shell are also included in the vCLI
package.
You can install the vCLI package on a supported Windows or Linux system or deploy the vMA virtual
appliance, and run commands against your ESXi hosts. Run commands in the ESXi Shell directly or through
SSH only in troubleshooting situations.
VMware, Inc.
25