You can use connection options that are available for all vCLI host management commands and common options that you can use when you run a vicfg- vCLI command.
The following table lists options that are available for all vCLI host management commands in alphabetical order. The table includes options for use on the command line and variables for use in configuration files. Options for executing DCLI commands are different.
See Run Host Management Commands from a Windows System and Run Host Management Commands from a Linux System.
Used to specify the CA (Certificate Authority) certificate file, in PEM format, to verify the identity of the vCenter Server system or ESXi system to run the command on. In vCLI 6.0 and later, you can only run ESXCLI commands if a trust relationship exists between the host you are running the command on and the system you are targeting with the --server option (ESXi host or vCenter Server system). You can establish the trust relationship by specifying the CA certificate file or by passing in the thumbprint for each target server (ESXi host or vCenter Server system). |
|
Name of a credential store file. Defaults to <HOME>/.vmware/credstore/vicredentials.xml on Linux and <APPDATA>/VMware/credstore/vicredentials.xml on Windows. Commands for setting up the credential store are included in the vSphere SDK for Perl, which is installed with vCLI. The vSphere SDK for Perl Programming Guide explains how to manage the credential store. |
|
If you specify this option, the system uses the Microsoft Windows Security Support Provider Interface (SSPI) for authentication. Trusted users are not prompted for a user name and password. See the Microsoft Web site for detailed information on SSPI. This option is supported only if you are connecting to a vCenter Server system. |
|
Use this option with --passthroughauth to specify a domain-level authentication protocol to be used by Windows. By default, SSPI uses the Negotiate protocol, which means that client and server try to negotiate a protocol that both support. If the vCenter Server system to which you are connecting is configured to use a specific protocol, you can specify that protocol by using this option. This option is supported only if you are running vCLI on a Windows system and connecting to a vCenter Server system. |
|
Uses the specified password (used with --username) to log in to the server. Use the empty string (' ' on Linux and " " on Windows) to indicate no password. If you do not specify a user name and password on the command line, the system prompts you and does not echo your input to the screen. |
|
Host name or IP address of the Platform Services Controller instance that is associated with the vCenter Server system that manages the host. In many cases, the Platform Services Controller is embedded in the vCenter Server system, but external Platform Services Controller instances are supported as well. For those cases, use the --server option to specify the vCenter Server system that manages the host. This option implies user authentication with vCenter Single Sign-On. The user you specify must be able to authenticate to vCenter Single Sign-On. |
|
Uses the specified ESXi or vCenter Server system. Default is localhost. If - -server points to a vCenter Server system, you can also specify the --psc option to log in to the vCenter Server system with vCenter Single Sign-On. Use the --vihost option to specify the ESXi host that you want to run the command against. See Authenticating Through vCenter Server and vCenter Single Sign-On. |
|
If you do not specify a user name and password on the command line, the system prompts you and does not echo your input to the screen. |
|