You can also run ESXCLI commands from the PowerCLI shell by using the Get-EsxCli cmdlet. See the vSphere PowerCLI User’s Guide and the vSphere PowerCLI Cmdlet Reference.The set of ESXCLI commands that are available on a host depends on the host configuration. The vSphere Command-Line Interface Reference lists help information for all ESXCLI commands. You can run esxcli --server <MyESXi> --help before you run a command on a host to make sure 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 Running vCLI Host Management Commands. Not required when you run the command in the ESXi Shell. If the target server is a vCenter Server system, specify the target ESXi host before any ESXCLI namespaces, commands, and supported options.Many ESXCLI commands generate output you might want to use in your application. You can run esxcli with the --formatter dispatcher option and send the resulting output as input to a parser.
■
■
■ namespace. Groups ESXCLI commands. vSphere 5.0 and later support 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.
■
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. For example:Run esxcli --server <target> --help for a list of namespaces supported on the target. You can drill down into the namespaces for additional help.