6.5
Table Of Contents
- Getting Started with vSphere Command-Line Interfaces
- Contents
- About This Book
- Managing vSphere with Command-Line Interfaces
- Installing vCLI
- Running Host Management Commands in the ESXi Shell
- Running vCLI Host Management Commands
- Overview of Running vCLI Host Management Commands
- Protecting Passwords
- Authenticating Through vCenter Server and vCenter Single Sign-On
- Authenticating Directly to the Host
- Trust Relationship Requirement for ESXCLI Commands
- Common Options for vCLI Host Management Command Execution
- Using vCLI Commands in Scripts
- Run Host Management Commands from a Windows System
- Run Host Management Commands from a Linux System
- Running DCLI Commands
- Index
Uninstall the vCLI Package on Windows
You can uninstall the vCLI package by following the standard Windows procedure.
Procedure
1 Find the option for adding and removing programs on the Windows operating system that you are
using.
2 In the panel that appears, select VMware vSphere CLI and click Remove.
3 Click Yes when prompted.
The system uninstalls vCLI and vSphere SDK for Perl.
Enabling Certificate Verification
You can enable certicate verication by using variables.
The vSphere SDK for Perl and vCLI use Crypt::SSLEay to support certicate verication. Crypt::SSLEay
enables verication of certicates signed by a Certicate Authority (CA) if you set the following two
variables.
n
HTTPS_CA_FILE – The CA le.
n
HTTPS_CA_DIR – The CA directory.
See the Crypt::SSLEay documentation for details on setup.
C If the two environment variables HTTPS_CA_FILE and HTTPS_CA_DIR are set incorrectly or if a
problem with the certicate exists, vCLI commands do not complete, and do not display error or warning
messages. Use HTTPS_DEBUG for troubleshooting before running vCLI commands.
Deploying vMA
As an alternative to a package installation, you can deploy vMA on an ESXi host and run vCLI commands
from there.
vMA is a virtual machine that you can use to run scripts to manage ESXi systems. vMA includes a Linux
environment, vCLI, and other prepackaged software.
Seing up vMA consists of several tasks. For details about each task, see the vSphere Management Assistant
Guide.
1 Deploy vMA to an ESXi system that meets the hardware prerequisites.
See the vSphere Management Assistant Guide for prerequisites and deployment details.
2 Congure vMA.
When you boot vMA, you must specify the following required conguration information when
prompted.
n
Network information (the default is often acceptable)
n
Host name for vMA
n
Password for the vi-admin user. The vi-admin user has superuser privileges on vMA. You cannot
log in to vMA as the root user.
3 (Optional) Add a vCenter Server system or one or more ESXi systems as targets. You congure vMA for
Active Directory authentication and can then add ESXi and vCenter Server systems to vMA without
having to store passwords in the vMA credential store. See the vSphere Management Assistant Guide.
Getting Started with vSphere Command-Line Interfaces
24 VMware, Inc.