Easy ESXi 6.0 upgrade via command line

VMware has released ESXi 6.0 back in March and I recently posted a guide on how to upgrade your vCenter Server Appliance from 5.x to 6.0 – Now we’re going to look at two ways to upgrade a VMware ESXi 5.x host to ESXi 6.0 via command line.

The first method will show you how to have each ESXi host download the update directly from VMware and then upgrade itself while the second method shows how to download the update, place it on a datastore accessible to the host, then upgrade the host.

Upgrade ESXi 6.0 via command line using VMware Online Depot

Using the VMware Online Depot is a simple way to upgrade if you only have 1 or 2 ESXi hosts to do, perfect for a small home lab setup.

  1. Place the host you want to upgrade into Maintenance Mode.
  2. On the host you’re about to upgrade, go to the Configuration tab > Security Profile and Enable SSH under Services.
    ssh enabled
  3. Open PuTTY (or any other SSH client) and SSH into your host.
  4. Type the following command to open the firewall for outgoing HTTP requests:
    esxcli network firewall ruleset set -e true -r httpClient
  5. Type the following command to download and upgrade to the latest version of ESXi 6.0 (as of April 10, 2015)
    esxcli software profile update -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml -p ESXi-6.0.0-20150404001-standard
  6. Once the above completes reboot your host by typing:
    reboot
  7. After the host has been rebooted PuTTy back into the host and disable the HTTP firewall rule by typing:
    esxcli network firewall ruleset set -e false -r httpClient
  8. Doesn’t hurt to also disable SSH when you’re done for security purposes.

That’s it, your ESXi host has how been upgraded to the latest ESXi 6.0 build, as of April 10, 2015, which does include the newest set of patches found in KB 2111975.

Use the Offline Bundle zip file to upgrade ESXi 6.0 using command line.

Using this process will allow you upgrade your ESXi hosts fairly quickly without the need of having to download the update each time on every host as the above process does.

  1. Download the ESXi 6.0 offline bundle zip file.
    ESXi 6.0 offline bundle
  2. Upload the VMware-ESXi-6.0.0-2494585-depot.zip file to a datastore accessible by the host.
    ESXi 6 bundle uploaded to datastore
  3. Now place the host you want to upgrade into Maintenance Mode.
  4. Then on the host you’re about to upgrade, go to the Configuration tab > Security Profile and Enable SSH under Services.
    ssh enabled
  5. Open PuTTY (or any other SSH client) and SSH into your host.
  6. Type the following command, replace “DATASTORE” with the name of your datastore you uploaded the VMware-ESXi-6.0.0-2494585-depot.zip file to.
    esxcli software vib update -d /vmfs/volumes/DATASTORE/VMware-ESXi-6.0.0-2494585-depot.zip
  7. Once the above completes reboot your host by typing:
    reboot

That’s it, now enjoy your newly upgraded ESXi hosts to ESXi 6.0.

If you have a lot of hosts to upgrade the faster way would most likely be to use VMware Update Manager (VUM). For more details about VUM be sure to check out my post on how to upgrade ESXi host to ESXi 5.5 using VMware Update Manager 5.5 – the process is largely the same minus using an ESXi 6.0 ISO obviously.

Similar Posts

  • Shrink a thin provisioned VMDK disk

    When maintaining a Horizon View environment I like to keep my parent images as small as possible and over time a thin provision disk can start to grow on you if you don’t watch it – be it from downloading installers, updates, or even running disk defrag. While there isn’t a simple, one click button in the View Administrator Console there is a fairly easy manual method using vmfkstools.

    Before we can use “vmkfstools” to shrink the VMDK file we must zero out any unused space on the thin provisioned disk. A simple way of doing this is by using a free utility called SDelete from Sysinternals.

    Read More “Shrink a thin provisioned VMDK disk”

  • Upgrade vCenter Server Appliance 6.0 to 6.5

    VMware vSphere 6.5 has been released as general available and earlier this week I posted about Installing VMware vCenter Server Appliance 6.5 as a new install, this post will walk through upgrading an existing vCenter Server Appliance 6.0 to 6.5!

    Similar to a fresh VCSA 6.5 install, the VCSA 6.5 upgrade is also broken up into two stages. The first stage is deploying a new vCenter Server Appliance and the second stage is copying data from the 6.0 VCSA to the newly deployed 6.5 VCSA.

    Read More “Upgrade vCenter Server Appliance 6.0 to 6.5”

  • vSphere 5.1 Release Date leaked, maybe?

    Looks like Sammy Bogaert over at Boerlowie’s Blog has possibly found the release date of vSphere 5.1… maybe?

    I was about to download vSphere Update Manager PowerCLI 5.0.

    I followed the main site and wanted to check the documentation first. So I clicked the Documentation button.

    vmware update manager

    This lead me to the Docs of Update Manager PowerCLI 5.1! That’s right, 5.1! With a release date of 10 September 2012.

    vsphere5.1 release date

    None of the links for 5.1 work, so no news on any new features…

    Guess somebody at VMware was a bit too fast to update the website

    Nice find Sammy, guess time will tell if the Sept. 10th date is the actual release date or not.

  • VMware Workstation 8.0.4 released

    VMware has just released it’s forth minor update for VMware Workstation 8, bringing it up to 8.0.4. The looks to contain mostly a few bug and security fixes.

    General Issues

    • Linux guests running the Linux kernel version 2.6.34 or later could not be pinged from the host via an IPv6 address.
    • On rare occasions, Linux guests would suddenly fail to Autofit or enter Unity.
    • Unity mode would exit if the title bar of an application contained certain non UTF-8 encoded extended ASCII characters.
    • On Windows hosts, the VMware Workstation user interface sometimes became unresponsive when minimized from full-screen mode if the suggestion balloon was being displayed.
    • On Windows hosts, the user interface sometimes became unresponsive if the application was rendered on an extended display that was abruptly disconnected.

    Read More “VMware Workstation 8.0.4 released”

  • Increase incremental backup speed by enabling CBT

    In a recent VMware environment I was working in, we noticed that our incremental backups was taking a long time (like up to 7-8 hours) to complete. After digging around it was found that VMware actually has a feature built-in since version 4 called Change Block Tracking (CBT). CBT will track any blocks that were changed since the last backup and tag them and stores the information in a -CTK file. The obvious benefit is that now the third party software only backs up the changed block and not the entire VM each time, reducing the amount of data being backed thus speeding up backups and even lowers the CPU utilization on the VM host.

    CBT is disabled by default though there are some backup tools that will enable it automatically or you can enable it manually which can easily be done following these steps:

    Read More “Increase incremental backup speed by enabling CBT”

  • VMUG EVALExperience, the new VMware VMTN

    VMUG EVALExperience

    Long ago VMware offered a program called VMware Technology Network (VMTN) which was very similar to Microsoft’s TechNet, which allowed you to download and run various VMware software within your home lab for a small yearly fee. Just like the Microsoft TechNet, the VMware VMTN program was eventually closed. From the time the VMTN program closed many people have begged and pleaded with VMware to bring the program back, there is even a long forum thread asking VMware to bring VMTN back. Though it never did… until now.

    Read More “VMUG EVALExperience, the new VMware VMTN”

Leave a Reply

Your email address will not be published. Required fields are marked *

One Comment

  1. You say ‘april 10’ a few times, but you appear to be updating to april 1: ‘ESXi-6.0.0-20150404001’ . Probably that’s the last one before the 10th, but if you’re choosing an arbitrary date you may want to explain that it’s not a typo (10 vs 01) . :-D