{"id":5309,"date":"2017-12-20T20:57:35","date_gmt":"2017-12-21T02:57:35","guid":{"rendered":"http:\/\/neosmart.net\/wiki\/?p=5309"},"modified":"2017-12-20T20:57:35","modified_gmt":"2017-12-21T02:57:35","slug":"upgrading-vsphere-esxi-from-the-command-line-automatically","status":"publish","type":"post","link":"https:\/\/neosmart.net\/wiki\/upgrading-vsphere-esxi-from-the-command-line-automatically\/","title":{"rendered":"Upgrading ESXi 6.5 automatically from the command line without vSphere"},"content":{"rendered":"

The traditional approach to upgrading vSphere and VMware ESXi involves manually downloading the VIB (short for “vSphere Installation Bundle”) and executing the ESXi esxcli<\/code>\u00a0command line VIB installer from an ESXi console or SSH session. However, not many realize that esxcli<\/code>\u00a0is actually a full-fledged package manager, and can be used to automatically check for updated packages and install them accordingly, in a similar vein to apt<\/code>\u00a0or yum<\/code>.<\/p>\n

<\/p>\n

Using esxcli<\/code>\u00a0in this fashion is actually surprisingly easy, but it does entail typing out the “depot” URL and providing it to esxcli<\/code>\u00a0as a command line argument each time. VMware ESXi and vSphere use this XML file to provide an index of the latest available packages and their version numbers, and can compare the contents against what’s installed locally to upgrade packages as needed.<\/p>\n

The first step is to make sure that the VMware ESXi SSH service is up and running, so that you can log in remotely to run the esxcli<\/code>\u00a0update\/upgrade commands. This can be done from the “Services” menu in the vSphere client, or from the “Security Profile” section of the “Configuration” tab in vSphere Client:<\/p>\n

\"\"<\/a><\/p>\n

Starting the vSphere\/ESXi SSH service via vSphere Client. Click on the image to zoom in.<\/em><\/p>\n<\/div>\n

 <\/p>\n

\"\"<\/a><\/p>\n

Starting the SSH service via the vSphere\/ESXi web management interface.<\/p>\n<\/div>\n

 <\/p>\n

Once the SSH service has been enabled, log on to the ESXi server in question over SSH, typically by running ssh root@IPADDR<\/code>\u00a0where IPADDR<\/code>\u00a0is the address of the vSphere\/ESXi host you would like to upgrade. Windows users will likely use putty<\/a> to establish the SSH connection instead.<\/p>\n

When you’ve logged in to the ESXi machine securely over SSH, enter the following at the terminal prompt. We recommend copy-and-pasting from below to make sure everything is typed in correctly:<\/p>\n

esxcli software vib update -d https:\/\/hostupdate.vmware.com\/software\/VUM\/PRODUCTION\/main\/vmw-depot-index.xml\r\n<\/code><\/pre>\n
Note that running this command may take awhile, during which the process will appear to be hung.\u00a0Do not close the SSH connection or attempt to stop the upgrade!<\/strong> esxcli<\/code>\u00a0will connect to the URL we provided and use that to obtain a list of the latest versions of all packages, then upgrade all outdated packages in the process.<\/p>\n
Once the upgrade has finished, esxcli<\/code>\u00a0will print information about all the updates installed to the terminal. At this point, it’s necessary to reboot the ESXi server to use the updated version of the software. If all guests have already been safely shutdown and the server is in maintenance mode (if needed), the vSphere\/ESXi server may be rebooted from the SSH session by typing in<\/p>\n
reboot\r\n<\/code><\/pre>\n
followed by the Enter key.<\/p>\n","protected":false},"excerpt":{"rendered":"
The traditional approach to upgrading vSphere and VMware ESXi involves manually downloading the VIB (short for “vSphere Installation Bundle”) and executing the ESXi esxcli\u00a0command line VIB installer from an ESXi console or SSH session. However, not many realize that esxcli\u00a0is actually a full-fledged package manager, and can be used to automatically check for updated packages […]<\/p>\n","protected":false},"author":505,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"class_list":["post-5309","post","type-post","status-publish","format-standard","hentry"],"aioseo_notices":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p3SlTq-1nD","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/neosmart.net\/wiki\/wp-json\/wp\/v2\/posts\/5309","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/neosmart.net\/wiki\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/neosmart.net\/wiki\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/neosmart.net\/wiki\/wp-json\/wp\/v2\/users\/505"}],"replies":[{"embeddable":true,"href":"https:\/\/neosmart.net\/wiki\/wp-json\/wp\/v2\/comments?post=5309"}],"version-history":[{"count":9,"href":"https:\/\/neosmart.net\/wiki\/wp-json\/wp\/v2\/posts\/5309\/revisions"}],"predecessor-version":[{"id":5320,"href":"https:\/\/neosmart.net\/wiki\/wp-json\/wp\/v2\/posts\/5309\/revisions\/5320"}],"wp:attachment":[{"href":"https:\/\/neosmart.net\/wiki\/wp-json\/wp\/v2\/media?parent=5309"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}