Specifications

Option Description
Update the image profile from a ZIP
file on the target server, copied into
a datastore
esxcli --server=server_name software profile update --
depot=“[datastore_name]profile_ZIP_file" --
profile=profile_name
Update the image profile from a ZIP
file copied locally and applied on
the target server
esxcli --server=server_name software profile update --
depot=/root_dir/path_to_profile_ZIP_file/profile_ZIP_file
--profile=profile_name
Install all new VIBs in a specified
profile accessible by URL
esxcli --server=server_name software profile install --
depot=http://webserver/depot_name --profile=profile_name
Install all new VIBs in a specified
profile from a ZIP file stored locally
on the target
esxcli --server=server_name software profile install --
depot=file:///<path_to_profile_ZIP_file>/<profile_ZIP_file>
--profile=profile_name
Install all new VIBs from a ZIP file
on the target server, copied into a
datastore
esxcli --server=server_name software profile install --
depot=“[datastore_name]profile_ZIP_file" --
profile=profile_name
Install all new VIBs from a ZIP file
copied locally and applied on the
target server
esxcli --server=server_name software profile install --
depot=/root_dir/path_to_profile_ZIP_file/profile_ZIP_file
--profile=profile_name
NOTE Options to the update and install commands allow you to perform a dry run, to specify a
specific VIB, to bypass acceptance level verification, and so on. Do not bypass verification on
production systems. See the vSphere Command-Line Interface Reference.
4 Verify that the VIBs are installed on your ESXi host.
esxcli --server=server_name software vib list
Update ESXi Hosts by Using Zip Files
You can update hosts with VIBs or image profiles by downloading a ZIP file of a depot.
VMware partners prepare third-party VIBs to provide management agents or asynchronously released
drivers.
IMPORTANT If you are updating ESXi from a zip bundle in a VMware-supplied depot, either online from the
VMware Web site or downloaded locally, VMware supports only the update method specified for VMware-
supplied depots in the topic “Upgrade or Update a Host with Image Profiles,” on page 206.
The esxcli software vib update and esxcli software vib install commands are not supported for
upgrade operations. See “Differences Between vSphere Upgrades and Updates,” on page 12 and “Upgrade
or Update a Host with Image Profiles,” on page 206.
When you specify a target server by using --server=server_name in the procedure, the specified server
prompts you for a user name and password. Other connection options, such as a configuration file or
session file, are supported. For a list of connection options, see Getting Started with vSphere Command-Line
Interfaces, or run esxcli --help at the vCLI command prompt.
Prerequisites
n
Install vCLI or deploy the vSphere Management Assistant (vMA) virtual machine. See Getting Started
with vSphere Command-Line Interfaces. For troubleshooting, run esxcli commands in the ESXi Shell.
n
Download the ZIP file of a depot bundle from a third-party VMware partner.
n
Determine whether the update requires the host to be in maintenance mode or to be rebooted. If
necessary, place the host in maintenance mode.
See “Determine Whether an Update Requires the Host to Be in Maintenance Mode or to Be Rebooted,”
on page 203. See “Place a Host in Maintenance Mode,” on page 204.
vSphere Upgrade
208 VMware, Inc.