How to easily update your VMware Hypervisor from 6.5.x to 6.5 Update 1 (ESXi 6.5 U1)
Important Update - On Mar 20 2018, VMware VMSA-2018-0004.3 announced that CVE-2017-5715 (Spectre-2) mitigation is now included in the latest patch that you should be using instead of the older patch featured in the original article below. You'll find the newer article that features an even easier update method here:
- How to easily update your VMware Hypervisor from 6.x to 6.5 Update 1 Patch Release ESXi650-201803001 (ESXi Build 7967591) with Spectre mitigation
Article below as it originally appeared.
VMware ESXI 6.5 U1
Release Notes. The simple update method that this article details means you won't need the ISO Download Page for:
ESXi 6.5 U1 | 27 JULY 2017 | Build 5969303
This upgrade is also known as version 6.5.0 Build 5969303 or 6.5U1.
More about this update in KB 2149910:
- VMware ESXi 6.5, Patch Release ESXi-6.5.0-update01 (2149910)
VMware Security Advisory
Advisory ID: VMSA-2017-0013
Synopsis: VMware vCenter Server and Tools updates resolve multiple security vulnerabilities
- vCenter/VCSA 6.5 should be upgraded to 6.5 Update 1 (aka U1) before upgrading your host(s) to ESXi 6.5 U1 Build 5969303, see:
How to easily update your VMware vCenter Server Appliance from 6.5.x to 6.5 Update 1 (VCSA 6.5 U1)
Jul 28 2017
- I have only tested this method when upgrading from 6.5.0a Build 5224934 to Build 5969303, your experience from earlier 6.x versions may vary.
- I have been able to replicate that the Xeon D 10GbE X552/X557 driver VIB needs to be re-installed right after the upgrade, simple one line workaround is documented here, with details below.
- This is not official VMware documentation, it's merely a convenient upgrade technique that may help in lab tests, a little simpler than the official procedure VMware documents and demonstrates in KB2008939. It's up to you to adhere to the backup-first advice detailed below, full Disclaimer found at below-left, at the bottom of very TinkerTry page.
- See also the Drawbacks section below.
All the background story on how this easy ESXCLI upgrade method came about was covered in my earlier articles about updating 6.0 U2 and 6.5.
If you're in production, beware, this code just came out yesterday. This article is for the lab, where you may want to give this critical patch a try.
- No new license needed to go from 6.0.x or 6.5.x to 6.5 U1 Build 5973321
- Users of the free hypervisor and folks who can't download the GA Offline bundle now have a path forward as well, without needing to read TinkerTry's My VMware's "You either are not entitled or do not have permissions to download this product." error, and what to do about it.
- See also Differences Between vSphere Upgrades and Updates and Upgrade or Update a Host with Image Profiles:
esxcli software profile updatecommand brings the entire contents of the ESXi host image to the same level as the corresponding upgrade method using an ISO installer. However, the ISO installer performs a pre-upgrade check for potential problems, and the
esxcliupgrade method does not. The ISO installer checks the host to make sure that it has sufficient memory for the upgrade, and does not have unsupported devices connected. For more about the ISO installer and other ESXi upgrade methods, see Upgrade Options for ESXi 6.0.
- See also Upgrading Hosts by Using esxcli Commands and Overview of the ESXi Host Upgrade Process.
- Before proceeding, you should read Overview of the ESXi Host Upgrade Process. This article below is just about the quick and easy way, effective and safe for most folks. For those more interested in "clean installs", where you login to My VMware, download the ESXi 6.5U1 ISO, shut down the ESXi on USB that you're already running, eject that USB flash drive and label it and set it aside, then boot from another USB drive like the SanDisk Ultra Fit with a fresh install of 6.5U1 imaged onto it. This clean install is much more time consuming than the easy method outlined below. Why? This is because once ESXi 6.5U1 is freshly installed, at a minimum you'll also have to use Datastore Browser to locate your VMs on your VMFS datastores, then add those files with *.vmx extensions back into your inventory, then add the host back to your cluster that should already be at 6.5U1. While this extra work may help you be sure that you don't have any drivers or changes carried over from your previous build, for many users, that's not a concern.
Once you've completed ALL of the following preparation steps:
- upgraded to VCSA 6.5 U1
- ensured your ESXi 6.5.x host has a working internet connection
- reviewed the release notes
- reviewed How to easily update your VMware Hypervisor to ESXi 6.0 Update 2 for the full back story that includes some warnings about potential gotchas/driver issues
- backed up the ESXi 6.5.x you've already got, if its on USB or SD, then use something like one of the home-lab-friendly and super easy methods such as USB Image Tools under Windows, as detailed by Florian Grehl here
you can now continue with this simple approach to upgrading your lab environment. Unsupported, at your own risk, see the full disclaimer at below-left.
You should wind up with the same results after this upgrade as folks who upgrade by downloading the full ESXi 6.5 U1 ISO / creating bootable media from that ISO / booting from that media (or mounting the ISO over IPMI/iLO/iDRAC/IMM/iKMV) and booting from it:
File size: 332.63 MB
File type: iso
Release Date: 2017-07-27
Build Number: 5969303
Download and upgrade to 6.5 U1 update using the patch directly from the VMware Online Depot
The entire process including reboot is usually well under 10 minutes. Triple-clicking on a line of code below highlights the whole thing, so you can then right-click and copy it into your clipboard:
- Open an SSH session (eg. PuTTY) to your ESXi 6.0.x server
(if you forgot to enable SSH, here's how)
- Turn on maintenance mode, or ensure you've set your ESXi host to automatically gracefully shutdown all VMs upon host reboot, or shutdown all the VMs gracefully that you care about, including VCSA.
- Firewall allow outbound http requests - Paste the one line below into into your SSH session, then press enter:
esxcli network firewall ruleset set -e true -r httpClient
More details about the firewall here.
- Pull down ESXi Image Profile using https and run patch script - Paste the line below into into your SSH session, then hit enter and wait while nothing seems to happen, taking somewhere between roughly 3 to 10 minutes before the completion screen (sample below) appears:
esxcli software profile install -p ESXi-6.5.0-20170702001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
If this command fails, you may want to try changing
install, details below, see also Douglas' comment. Wait time for the successful install depending mostly on the the speed of the ESXi's connection to the internet, and somewhat on the write speed of the storage media that ESXi is installed on.
- If you have Xeon D X552/X557, to regain the 10GbE driver VIB that the upgrade process removed, simply paste the easy one-liner fix described below before proceeding
- Firewall disallow outbound http requests - Paste the line below into into your SSH session:
esxcli network firewall ruleset set -e false -r httpClient
- If you turned on maintenance mode earlier, remember to turn maintenance mode off.
- If you normally leave SSH access off, go ahead and disable it now.
- Type reboot and hit return (to restart your ESXi server), or use your favorite ESXi UI to restart the host.
- After the reboot is done, it would be a good idea to test login using ESXi host client, pointing your browser to the IP or hostname of your just-graded server, to be sure everthing seems to be working right.
Special thanks to VMware ESXi Patch Tracker by Andreas Peetz at the VMware Front Experience Blog. This upgrade test was performed on a TinkerTry'd VMware HCL system. Yes, on both the very popular 8 core and the rather special 12 core version of the beloved Supermicro SuperServer SYS-5028D-TN4T system.
That's it! When the reboot is complete, you'll see for yourself that you now have the latest ESXi, Build 5969303, as pictured above. Now you have more spare time to read more TinkerTry articles!
Depending upon your ESXi firewall configuration, if the above command results in a network related error such as:
'NoneType' object has no attribute 'close'
then you skipped the firewall configuration step above, try again!
- Notice that the command recommended you use when clicking on the ESXi-6.5.0-20170304101-standard link at VMware ESXi Patch Tracker:
esxcli software profile update -p ESXi-6.5.0-20170702001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
doesn't work, says:
Message: Host is not changed.
but simply changing from
installworked for me, but your results may vary. See also the interesting comment below.
Potential SATA and Realtek NIC gotcha
- If you find some of your SATA/AHCI datastores disappear from view after this upgrade, worry not, the VMFS datastores are still there, you just can't see them. This article should still save you:
For ESXi 6.0, those ESXi 5.1 VIBs for ASMedia SATA ports and Realtek NICs still seem to be working (but unsupported)
Mar 04 2015
Potential Intel Xeon D X552/X557 10GbE Driver gotcha
Apr 19 2017 Update
Getting past this issue was straight-forward, just re-installed my Intel's 4.5.1 X552/X557 10GbE VIB, see:
then rebooted. Everything working fine again.
Potential Intel Xeon D I-350 1GbE Driver gotcha
Added Apr 19 2017 Update
If you encounter the service console networking problem, the fix is reported below.
Alternatively, you could have used VMware Update Manager on a Windows system or VM, but for one-off upgrades typical in a small home lab, pasting these 3 or 4 lines of code is pretty darn easy.
Looking ahead, since VUM is now built into VCSA 6.5, this adds another way to do future upgrades and patches, even in a small home lab environment.
Jul 30 2017 Update
Helpful information, care of gbX who left this comment below:
I've got a problem with online depot update (from 6.5.0d to 6.5.0 U1). If you encounter "[ErrNo 28] Not enough space", just download the patch *zip from myvmware:
Store the *zip package on your datastore and install with following command:
esxcli software profile install -d="zip location"
Seems like downloading update from online depot fills up your tmp storage resulting in above error.
Soon, Todd Taylor stepped in with this reply:
Same error. I hammered on it for about an hour trying to track down the space issue, deleting logs, etc. and then found a reference on reddit about changing the swap datastore which worked for me first time. I didn't have a datastore set in the web UI under Host | Manage | System | SWAP. When I chose a datastore in the dropdown and retried the update it worked first try. All props to cpierr03 for his helpful post here:
Aug 15 2017
When the upgrade is complete, on the ESXi Host Client UI, under Host / Configuration, you should see the following "Image profile"
(Updated) ESXi-6.5.0-20170702001-standard (VMware, Inc.)
See also at TinkerTry
How to easily update your VMware vCenter Server Appliance from 6.5.x to 6.5 Update 1 (VCSA 6.5 U1)
Jul 28 2017
Order a TinkerTry'd Supermicro SuperServer Bundle - powerful and efficient home virtualization lab solutions
- VMware vSphere Taskbar Shortcuts Unleashed - profile switcher isolated and uncluttered Chrome Browser UIs act like native Windows apps!
VMware vSAN 6.6 GA - Download Links Available
Apr 18 2017 by Florian Grehl
ESXi 6.5 Release Notes for free license and white box users
Nov 24 2016 by Andreas Peetz at VMware Front Experience
VMware ESXi Patch Tracker
Nov 24 2016 by Andreas Peetz at VMware Front Experience
- VMware vSphere 6.5 Documentation Center - Upgrade or Update a Host with Image Profiles
Below, I've pasted the full text of my upgrade, helps you see what drivers were touched, use the horizonal scroll bar or shift + mousewheel to look around, and Ctrl+F to Find stuff quickly:
login as: root Using keyboard-interactive authentication. Password: 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. [root@xd-1541-5028d:~] esxcli network firewall ruleset set -e true -r httpClient [root@xd-1541-5028d:~] esxcli software profile install -p ESXi-6.5.0-20170702001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml Installation Result Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective. Reboot Required: true VIBs Installed: VMW_bootbank_i40en_1.3.1-5vmw.6184.108.40.20669303, VMW_bootbank_igbn_0.1.0.0-14vmw.6220.127.116.1169303, VMW_bootbank_ixgben_1.4.1-2vmw.618.104.22.16869303, VMW_bootbank_misc-drivers_6.5.0-1.26.5969303, VMW_bootbank_ne1000_0.8.0-16vmw.622.214.171.12469303, VMW_bootbank_net-ixgbe_126.96.36.199.14iov-20vmw.6188.8.131.5264106, VMW_bootbank_ntg3_184.108.40.206-1vmw.6220.127.116.1169303, VMW_bootbank_nvme_18.104.22.168-4vmw.622.214.171.12469303, VMW_bootbank_pvscsi_0.1-1vmw.6126.96.36.19969303, VMW_bootbank_qlnativefc_188.8.131.52-1vmw.6184.108.40.20669303, VMW_bootbank_sata-ahci_3.0-26vmw.6220.127.116.1169303, VMW_bootbank_usbcore-usb_1.0-3vmw.618.104.22.16869303, VMW_bootbank_vmkata_0.1-1vmw.622.214.171.12469303, VMW_bootbank_vmkusb_0.1-1vmw.6126.96.36.19969303, VMW_bootbank_vmw-ahci_1.0.0-39vmw.6188.8.131.5269303, VMware_bootbank_esx-base_6.5.0-1.26.5969303, VMware_bootbank_esx-tboot_6.5.0-1.26.5969303, VMware_bootbank_esx-ui_1.21.0-5724747, VMware_bootbank_esx-xserver_6.5.0-0.23.5969300, VMware_bootbank_lsu-hp-hpsa-plugin_2.0.0-5vmw.6184.108.40.20669303, VMware_bootbank_lsu-lsi-lsi-mr3-plugin_1.0.0-10vmw.6220.127.116.1169303, VMware_bootbank_lsu-lsi-lsi-msgpt3-plugin_1.0.0-7vmw.618.104.22.16869303, VMware_bootbank_lsu-lsi-megaraid-sas-plugin_1.0.0-8vmw.622.214.171.12469303, VMware_bootbank_lsu-lsi-mpt2sas-plugin_2.0.0-6vmw.6126.96.36.19969303, VMware_bootbank_vmware-esx-esxcli-nvme-plugin_188.8.131.52-1.26.5969303, VMware_bootbank_vsan_6.5.0-1.26.5912915, VMware_bootbank_vsanhealth_6.5.0-1.26.5912974, VMware_locker_tools-light_6.5.0-0.23.5969300 VIBs Removed: INT_bootbank_net-ixgbe_4.5.1-1OEM.600.0.0.2494585, VMW_bootbank_i40en_1.1.0-1vmw.6184.108.40.20664106, VMW_bootbank_igbn_0.1.0.0-12vmw.6220.127.116.1164106, VMW_bootbank_ixgben_18.104.22.168-9vmw.622.214.171.12446846, VMW_bootbank_misc-drivers_6.5.0-0.14.5146846, VMW_bootbank_ne1000_0.8.0-11vmw.6126.96.36.19946846, VMW_bootbank_ntg3_188.8.131.52-1vmw.6184.108.40.20664106, VMW_bootbank_nvme_220.127.116.11-2vmw.618.104.22.16864106, VMW_bootbank_pvscsi_0.1-1vmw.622.214.171.12464106, VMW_bootbank_qlnativefc_126.96.36.199-11vmw.6188.8.131.5264106, VMW_bootbank_sata-ahci_3.0-22vmw.6184.108.40.20664106, VMW_bootbank_usbcore-usb_1.0-3vmw.6220.127.116.1164106, VMW_bootbank_vmkata_0.1-1vmw.618.104.22.16864106, VMW_bootbank_vmkusb_0.1-1vmw.622.214.171.12446846, VMW_bootbank_vmw-ahci_1.0.0-34vmw.6126.96.36.19946846, VMware_bootbank_esx-base_6.5.0-0.19.5310538, VMware_bootbank_esx-tboot_6.5.0-0.0.4564106, VMware_bootbank_esx-ui_1.18.0-5270848, VMware_bootbank_esx-xserver_6.5.0-0.0.4564106, VMware_bootbank_lsu-hp-hpsa-plugin_2.0.0-3vmw.6188.8.131.5264106, VMware_bootbank_lsu-lsi-lsi-mr3-plugin_1.0.0-7vmw.6184.108.40.20664106, VMware_bootbank_lsu-lsi-lsi-msgpt3-plugin_1.0.0-6vmw.6220.127.116.1164106, VMware_bootbank_lsu-lsi-megaraid-sas-plugin_1.0.0-7vmw.618.104.22.16864106, VMware_bootbank_lsu-lsi-mpt2sas-plugin_2.0.0-5vmw.622.214.171.12464106, VMware_bootbank_vmware-esx-esxcli-nvme-plugin_126.96.36.199-0.0.4564106, VMware_bootbank_vsan_6.5.0-0.19.5310540, VMware_bootbank_vsanhealth_6.5.0-0.19.5310541, VMware_locker_tools-light_6.5.0-0.0.4564106 VIBs Skipped: VMW_bootbank_ata-libata-92_3.00.9.2-16vmw.6188.8.131.5264106, VMW_bootbank_ata-pata-amd_0.3.10-3vmw.6184.108.40.20664106, VMW_bootbank_ata-pata-atiixp_0.4.6-4vmw.6220.127.116.1164106, VMW_bootbank_ata-pata-cmd64x_0.2.5-3vmw.618.104.22.16864106, VMW_bootbank_ata-pata-hpt3x2n_0.3.4-3vmw.622.214.171.12464106, VMW_bootbank_ata-pata-pdc2027x_1.0-3vmw.6126.96.36.19964106, VMW_bootbank_ata-pata-serverworks_0.4.3-3vmw.6188.8.131.5264106, VMW_bootbank_ata-pata-sil680_0.4.8-3vmw.6184.108.40.20664106, VMW_bootbank_ata-pata-via_0.3.3-2vmw.6220.127.116.1164106, VMW_bootbank_block-cciss_3.6.14-10vmw.618.104.22.16864106, VMW_bootbank_char-random_1.0-3vmw.622.214.171.12464106, VMW_bootbank_ehci-ehci-hcd_1.0-4vmw.6126.96.36.19946846, VMW_bootbank_elxnet_188.8.131.52-1vmw.6184.108.40.20664106, VMW_bootbank_hid-hid_1.0-3vmw.6220.127.116.1164106, VMW_bootbank_ima-qla4xxx_2.02.18-1vmw.618.104.22.16864106, VMW_bootbank_ipmi-ipmi-devintf_39.1-4vmw.622.214.171.12464106, VMW_bootbank_ipmi-ipmi-msghandler_39.1-4vmw.6126.96.36.19964106, VMW_bootbank_ipmi-ipmi-si-drv_39.1-4vmw.6188.8.131.5264106, VMW_bootbank_lpfc_184.108.40.206-1vmw.6220.127.116.1164106, VMW_bootbank_lsi-mr3_6.910.18.00-1vmw.618.104.22.16864106, VMW_bootbank_lsi-msgpt2_20.00.01.00-3vmw.622.214.171.12464106, VMW_bootbank_lsi-msgpt3_12.00.02.00-11vmw.6126.96.36.19964106, VMW_bootbank_misc-cnic-register_1.78.75.v60.7-1vmw.6188.8.131.5264106, VMW_bootbank_mtip32xx-native_3.9.5-1vmw.6184.108.40.20664106, VMW_bootbank_nenic_220.127.116.11-1vmw.618.104.22.16864106, VMW_bootbank_net-bnx2_2.2.4f.v60.10-2vmw.622.214.171.12464106, VMW_bootbank_net-bnx2x_1.78.80.v60.12-1vmw.6126.96.36.19964106, VMW_bootbank_net-cdc-ether_1.0-3vmw.6188.8.131.5264106, VMW_bootbank_net-cnic_1.78.76.v60.13-2vmw.6184.108.40.20664106, VMW_bootbank_net-e1000_220.127.116.11-5vmw.618.104.22.16864106, VMW_bootbank_net-e1000e_22.214.171.124-2vmw.6126.96.36.19964106, VMW_bootbank_net-enic_188.8.131.52-2vmw.6184.108.40.20664106, VMW_bootbank_net-fcoe_220.127.116.11.3-7vmw.618.104.22.16864106, VMW_bootbank_net-forcedeth_0.61-2vmw.622.214.171.12464106, VMW_bootbank_net-igb_126.96.36.199.1-5vmw.6188.8.131.5264106, VMW_bootbank_net-libfcoe-92_184.108.40.206.4-8vmw.6220.127.116.1164106, VMW_bootbank_net-mlx4-core_18.104.22.168-1vmw.622.214.171.12464106, VMW_bootbank_net-mlx4-en_126.96.36.199-1vmw.6188.8.131.5264106, VMW_bootbank_net-nx-nic_5.0.621-5vmw.6184.108.40.20664106, VMW_bootbank_net-tg3_3.131d.v60.4-2vmw.6220.127.116.1164106, VMW_bootbank_net-usbnet_1.0-3vmw.618.104.22.16864106, VMW_bootbank_net-vmxnet3_22.214.171.124-3vmw.6126.96.36.19964106, VMW_bootbank_nhpsa_2.0.6-3vmw.6188.8.131.5264106, VMW_bootbank_nmlx4-core_184.108.40.206-1vmw.6220.127.116.1164106, VMW_bootbank_nmlx4-en_18.104.22.168-1vmw.622.214.171.12464106, VMW_bootbank_nmlx4-rdma_126.96.36.199-1vmw.6188.8.131.5264106, VMW_bootbank_nmlx5-core_184.108.40.206-1vmw.6220.127.116.1164106, VMW_bootbank_nvmxnet3_18.104.22.168-1vmw.622.214.171.12464106, VMW_bootbank_ohci-usb-ohci_1.0-3vmw.6126.96.36.19964106, VMW_bootbank_qedentv_188.8.131.52-1vmw.6184.108.40.20664106, VMW_bootbank_qfle3_220.127.116.11-1vmw.618.104.22.16864106, VMW_bootbank_qflge_22.214.171.124-1vmw.6126.96.36.19964106, VMW_bootbank_sata-ata-piix_2.12-10vmw.6188.8.131.5264106, VMW_bootbank_sata-sata-nv_3.5-4vmw.6184.108.40.20664106, VMW_bootbank_sata-sata-promise_2.12-3vmw.6220.127.116.1164106, VMW_bootbank_sata-sata-sil24_1.1-1vmw.618.104.22.16864106, VMW_bootbank_sata-sata-sil_2.3-4vmw.622.214.171.12464106, VMW_bootbank_sata-sata-svw_2.3-3vmw.6126.96.36.19964106, VMW_bootbank_scsi-aacraid_188.8.131.52-9vmw.6184.108.40.20664106, VMW_bootbank_scsi-adp94xx_220.127.116.11-6vmw.618.104.22.16864106, VMW_bootbank_scsi-aic79xx_3.1-5vmw.622.214.171.12464106, VMW_bootbank_scsi-bnx2fc_1.78.78.v60.8-1vmw.6126.96.36.19964106, VMW_bootbank_scsi-bnx2i_2.78.76.v60.8-1vmw.6188.8.131.5264106, VMW_bootbank_scsi-fnic_184.108.40.206-3vmw.6220.127.116.1164106, VMW_bootbank_scsi-hpsa_18.104.22.168-1vmw.622.214.171.12464106, VMW_bootbank_scsi-ips_7.12.05-4vmw.6126.96.36.19964106, VMW_bootbank_scsi-iscsi-linux-92_188.8.131.52-3vmw.6184.108.40.20664106, VMW_bootbank_scsi-libfc-92_220.127.116.11.3-5vmw.618.104.22.16864106, VMW_bootbank_scsi-megaraid-mbox_22.214.171.124-6vmw.6126.96.36.19964106, VMW_bootbank_scsi-megaraid-sas_6.603.55.00-2vmw.6188.8.131.5264106, VMW_bootbank_scsi-megaraid2_2.00.4-9vmw.6184.108.40.20664106, VMW_bootbank_scsi-mpt2sas_19.00.00.00-1vmw.6220.127.116.1164106, VMW_bootbank_scsi-mptsas_4.23.01.00-10vmw.618.104.22.16864106, VMW_bootbank_scsi-mptspi_4.23.01.00-10vmw.622.214.171.12464106, VMW_bootbank_scsi-qla4xxx_5.01.03.2-7vmw.6126.96.36.19964106, VMW_bootbank_shim-iscsi-linux-9-2-1-0_6.5.0-0.0.4564106, VMW_bootbank_shim-iscsi-linux-9-2-2-0_6.5.0-0.0.4564106, VMW_bootbank_shim-libata-9-2-1-0_6.5.0-0.0.4564106, VMW_bootbank_shim-libata-9-2-2-0_6.5.0-0.0.4564106, VMW_bootbank_shim-libfc-9-2-1-0_6.5.0-0.0.4564106, VMW_bootbank_shim-libfc-9-2-2-0_6.5.0-0.0.4564106, VMW_bootbank_shim-libfcoe-9-2-1-0_6.5.0-0.0.4564106, VMW_bootbank_shim-libfcoe-9-2-2-0_6.5.0-0.0.4564106, VMW_bootbank_shim-vmklinux-9-2-1-0_6.5.0-0.0.4564106, VMW_bootbank_shim-vmklinux-9-2-2-0_6.5.0-0.0.4564106, VMW_bootbank_shim-vmklinux-9-2-3-0_6.5.0-0.0.4564106, VMW_bootbank_uhci-usb-uhci_1.0-3vmw.6188.8.131.5264106, VMW_bootbank_usb-storage-usb-storage_1.0-3vmw.6184.108.40.20664106, VMW_bootbank_vmkplexer-vmkplexer_6.5.0-0.0.4564106, VMW_bootbank_xhci-xhci_1.0-3vmw.6220.127.116.1164106, VMware_bootbank_cpu-microcode_6.5.0-0.0.4564106, VMware_bootbank_emulex-esx-elxnetcli_18.104.22.168-0.0.4564106, VMware_bootbank_esx-dvfilter-generic-fastpath_6.5.0-0.0.4564106, VMware_bootbank_native-misc-drivers_6.5.0-0.0.4564106, VMware_bootbank_rste_2.0.2.0088-4vmw.622.214.171.12464106 [root@xd-1541-5028d:~] [root@xd-1541-5028d:~] esxcli network firewall ruleset set -e false -r httpClient [root@xd-1541-5028d:~] reboot