You can also run ESXCLI commands from the PowerCLI shell by using the Get-EsxCli cmdlet. See the vSphere PowerCLI Administration Guide and the vSphere PowerCLI Reference.The set of ESXCLI commands available on a host depends on the host configuration. The vSphere Command-Line Interface Reference lists help information for all ESXCLI commands. Run esxcli --server <MyESXi> --help before you run a command on a host to verify that the command is defined on the host you are targeting.
■ dispatcher options. Predefined options for connection information such as target host, user name, and so on. See Common Options for vCLI Execution. Not required when you run the command in the ESXi Shell.
■ namespace. Groups ESXCLI commands. vSphere 5.0 supports nested namespaces.
■ command. Reports on or modifies state on the system.
■ options. Many commands support one or more options, displayed in the help or the vCLI Reference. For some commands, multiple option values, separated by spaces, are possible.
■ Deploy the vMA appliance on an ESXi system and authenticate against a set of target servers. You can then run ESXCLI commands against any target server by specifying the --host dispatcher option. No additional authentication is required. See the vSphere Management Assistant Guide.
■ Each time you run a command, you must specify authentication information. See Using the vSphere Command-Line Interface.When you run an ESXCLI vCLI command, you must know the commands supported on the target host specified with --server or as a vMA target.Run esxcli --server <target> --help for a list of namespaces supported on the target. You can drill down into the namespaces for additional help.
Important ESXCLI on ESX 4.x hosts does not support targeting a vCenter Server system. You can therefore not run commands with --server pointing to a vCenter Server system even if you install vCLI 5.0 or vCLI 5.1.