The ESXi Embedded Host Client Fling got an upgrade today, and in addition to new features it now works properly on ESXi 5.5. In addition to this, it’s also available as an offline bundle so you can distribute it with Update Manager.
Since I’ve spent most of my day in esxcli, here is a quick post on how to perform the upgrade from a local http repository hosting the .vib file.
Install .vib file
- Download the esxui-3015331.vib file and place it somewhere accessible via http.
- SSH to your ESXi host, and run the following command (remember to enable maintenance mode if needed).
esxcli software vib install -v http://[yourip:port/path]/esxui-3015331.vib
- Wait for the installation to finish
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed: VMware_bootbank_esx-ui_0.0.2-0.1.3015331
VIBs Removed: VMware_bootbank_esx-ui_0.0.2-0.1.2976804
- Access the updated Embedded Host Client via http://hostip/ui/
I was recently involved with consulting for a Norwegian shipping company who has quite a few remote vSphere installations, most of them with a couple of ESXi hosts, but no vCenter and hence no Update Manager. While looking at methods for managing these installations, in particular how to facilitate patching and upgrading scenarios, I remembered that way back in 2013, I posted Quick and Dirty HTTP-based Deployment which shows how to use the Python to run a simple http daemon, and serve files from it.
Surely something similar can be used to maintain a central repository for vSphere patches? While I don’t recommend using your MacBook as a permanent source for these updates, you really should set up a proper http server in your network and utilize that, it works as a proof of concept.
So here it is, a recipe for using a simple http daemon to host your own ESXi Offline Bundles, and how to upgrade from 5.5 to 6.0 from the command line.
- Download the offline bundle you want to use, in my case I used ESXi600-201507001.zip (ESXi 6.0.0b).
- Extract the .zip file into it’s own directory, served by the http daemon, and rename it for simplicity.
- Connect to your target ESXi host via SSH
- Check the current running ESXi version by running esxcli system version get
The time and date of this login have been sent to the system logs.VMware offers supported, powerful system administration tools. Please
see www.vmware.com/go/sysadmintools for details.The ESXi Shell can be disabled by an administrative user. See the
vSphere Security documentation for more information.
~ # esxcli system version get
Product: VMware ESXi
- Enable outgoing http requests from the ESXi host by running esxcli network firewall ruleset set -e true -r httpClient
- Determine which profile to use by running esxcli software sources profile list -d [http://daemon-ip:port/directory/]
~ # esxcli software sources profile list -d http://172.29.100.248:8000/6.0/
Name Vendor Acceptance Level
-------------------------------- ------------ ----------------
ESXi-6.0.0-20150701001s-standard VMware, Inc. PartnerSupported
ESXi-6.0.0-20150701001s-no-tools VMware, Inc. PartnerSupported
ESXi-6.0.0-20150704001-no-tools VMware, Inc. PartnerSupported
ESXi-6.0.0-20150704001-standard VMware, Inc. PartnerSupported
- Run vim-cmd hostsvc/maintenance_mode_enter to put ESXi host into maintenance mode.
- Run esxcli software profile update -d [http://daemon-ip:port/directory/] -p [profilename] to fetch and install from http daemon
# esxcli software profile update -d http://172.29.100.248:8000/6.0/ -p ESXi-6.0.0-20150704001-standard
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: [long list of vibs removed for brevity]
- Disable outgoing http client traffic by running esxcli network firewall ruleset set -e false httpClient
- Reboot host by running the reboot command
- When host has rebooted, connect to ESXi host again via SSH and run esxcli system version get
[root@localhost:~] esxcli system version get
Product: VMware ESXi
- Verify that it runs the correct version, and run vim-cmd hostsvc/maintenance_mode_exit to put the host out of maintenance mode.
And that’s it, the host has now been upgraded from ESXi 5.5 to 6.0, from a local centralized http-based repository without the need to connect to the outside world. All done via the command line, and without a vCenter with Update Manager. Pretty neat.
I almost choked on my coffee this morning when I saw William Lam announcing a new VMware Fling called ESXi Embedded Host Client. Finally the day when we can get a local vSphere Web Client on a standalone host is here, and it’s not a moment too soon. This feature has been missing since ESX 3 and it’s VMware Infrastructure Web Access. For now, this is a Fling (which means unsupported and so on), but I really hope that this ends up being built-in to ESXi very soon — even on the free vSphere Hypervisor.
So, what does it look like? Well, to be honest it looks pretty darn awesome, and you know what? No Flash! Yes, it’s HTML5 baby!
If you are running ESXi 6, installation is as easy as installing a .vib (in ESXi 5.5 there is a workaround to get it running, highlighted in Williams post). So, give it a spin and make sure to provide feedback on the Flings site to help ensure VMware sees that we as users of their products want this feature to be core to vSphere in upcoming releases. Make your voice heard, and make sure the team who is behind this get the credit they deserve.