Determine which image profiles are available in the depot. Esxcli -server= software sources profile list -depot=You can specify a proxy server by using the -proxyoption. Update the existing image profile to include the VIBs or install new VIBs. Hi, this post describes an ESXi Host Upgrade from Version 6.0 to 6.7 with an offline (bundle) zip file. The procedure for other version should be the same. I used the image provided by the 'Vendor'. First of all, download the image form the Vendors Website and copy the VMware/Vendor image via ssh to the host, for example to esxdatastore0. If possible move all VMs to another ho. Sep 28, 2018 I manage ESXi 6.5.0 Update 1 (Build 7967591) under free license. I would like to upgrade it to 6.7 (because better macOS client support).
Perform the following tasks to upgrade the ESXi and SDC versions on the node:
-
To optionally list the profile of the ESXi zip archive, run:
For example:The following output appears:
-
Upgrade the ESXi version:
NOTE: The command assumes the path is under /tmp.After the upgrade has completed successfully, the following output appears, followed by a list of the upgraded packages:
-
On the ESXi system where you are installing the SDC, set the acceptance level::
where
<SERVER_NAME>
is the ESXi system where you are installing the SDC. -
Install the SDC:
NOTE:You can also use this procedure to upgrade from ESXi 6.x to a later ESXi 6.x version or patch, without the need to upgrade the SDC. In this case, skip the steps for the ESXi 5.5 SDC and proceed directly to reboot.where <Full_Path> is the full path to the location of the SDC upgrade zip archive.For example:
- Reboot the node.
Proceed to the next task to return the node to operational state.
Most of the time you would want to use VMware Update Manager when doing upgrade. Its part of vCenter and is necessary tool when having to maintain your environment. But for smaller deployments, with standalone hosts and no vCenter the following upgrade methods are desired and can help the upgrade time. Instead of having to upgrade with IPMI and an ISO.
Online mode:
This method is for getting the update online, no need to download ISO/offline bundles, etc. This will work for most of the upgrade use cases.
1: Connect to your ESXi host via the host client and enable SSH. Afterward ssh to the ESXi host and enable ESXi firewall rule to allow the host to access the internet.
2: With the beneath command you will get a list of available ESXi packaged that are on the VMware repos. Enter this command to list all available profiles. We filter only those which are relevant to our case – upgrade to ESXi 6.7
Esxcli Software Profile List
3. Chose the desired profile and use the following command for choosing and upgrading the ESXi version. Before upgrade its a good idea to enter maintenance mode.
4. After it’s done, you will need to restart the host, after its rebooted you will run on the new ESXi version.
Custom, with Offline bundle:
This method is for when you desire to install a custom update, or that your hosts down have access to the internet.
Esxcli Software Update
1: Download the offline bundle from the VMware webpage, in this upgrade I will use an HPE custom version. But if you run a generic version, that will also work.
2: After downloading the “VMware-ESXi-6.7.0-8169922-depot.zip” file, place it (upload it) to a datastore which is visible by your ESXi host. Best would be a local datastore if this host has some. If not, it can also be a shared datastore too.
3: Find the profile name from the depot offline bundle
Put your host into maintenance mode, enable SSH if you haven’t done yet.
3: Execute this command to upgrade your ESXi 6.x to 6.7
esxcli software profile update -p ESXi-6.7.0-13006603-standard -d /vmfs/volumes/your_datastore/VMware-ESXi-6.7.0-13006603-depot.zip
After checking that your upgrade was successful, reboot your host. You should see a message saying that the upgrade completed successfully.
Troubleshooting
I have tried to get an error with:
Failed updating the bootloader: Execution of command /usr/lib/vmware/bootloader-installer/install-bootloader failed: non-zero code returned…. return code: 1”
Error when upgrading, due to “insufficient space”.
This problem is due to the SWAP is but on the installation of the ESXi, not a good thing. So let’s change it.
Go to the UI of the ESXi Hosts https://IP/ui, login and proceed to the following:
Manage > System > Swap > Edit Settings
Chose the dropdown and select a datastore. Apply and the swap space is not freed from the ESXi install device so that you can try to upgrade again.
Conclusion:
After the upgrade, it’s a good idea to disable the ESXi firewall rule for “HTTP outside access”. Stop and disable SSH again, but it’s optional ?
Now you should have an upgraded host.