Latest Posts



Translate

Total Pageviews

Wednesday, 3 December 2014

Supported Protocols and Platforms for Commands in VMware

The resxtop command requires an HTTPS connection. All other commands support HTTP and HTTPS.
Most vCLI commands can run against an ESXi system or against vCenter Server. vCenter Server support means that you can connect to a vCenter Server system and use - -vihost to specify the ESXi host to run the command against. The only exception is svmotion, which you can run against vCenter Server systems, but not against ESXi systems.
You cannot run the vihostupdate command against an ESXi 5.0 or later system.
You cannot run the vihostupdate and vicfg-mpath commands that are in a vCLI 4.0 or later installation against ESX/ESXi 3.5 or vCenter 2.5 systems. Instead, run vihostupdate35 and vicfg-mpath35, included in the vCLI 4.x installation, against those systems. vihostupdate35 is supported for ESXi, but not for ESX.
You cannot run vicfg-syslog --setserver or vicfg-syslog --setport with an ESXi 5.0 or later target.

See the VMware Infrastructure Remote Command-Line Interface Installation and Reference Guide for ESX/ESXi 3.5 Update 2 for a list of supported options. To access that document, select Resources > Documentation from the VMware web site. Find the vSphere documentation set and open the archive. A few vCLI 4.x options are supported against hosts running ESX/ESXi 3.5 Update 2 or later even though they were not supported in RCLI version 3.5.
Run a vCLI 4.x command with - -help for information about option support with ESX/ESXi 3.5 Update 2, or see the VMware knowledge base article at http://kb.vmware.com/kb/1008940 for more detail.
Platform Support for vCLI 5.x Commands lists platform support for the different vCLI 5.x commands. These commands have not been tested against VirtualCenter 2.5 Update 2 systems. You can, however, connect to a vCenter Server 4.x system and target ESX/ESXi 3.5 Update 2 hosts.
Use vicfg-mpath35 instead.
Use esxcli software vibinstead.
Use vihostupdate35instead
Info taken from VMware Documentation