PDF(899.4 KB) View with Adobe Reader on a variety of devices
ePub(893.5 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(1.0 MB) View on Kindle device or Kindle app on multiple devices
Updated:September 18, 2018
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes how to upgrade Business Edition Esxi from 5.5 to 6.X not via command line but through offline bundle.
Cisco recommends that you have knowledge of these topics:
Unified Computing System (UCS) with VMware ESXi hypervisor version 5.5
Terminal access to ESXi hypervisor
Access to Cisco Integrated Management Controller (CIMC) web page on a java-enabled browser
The information in this document is based on these software and hardware versions:
Unified Computing System (UCS C240 M4SX) or BE7H.
ESXi hypervisor version 5.5.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
VMware published the deadlines for the End of General Support and End of Technical Guidance for ESXi 5.5:
It is a good practice to upgrade the virtualized infrastructure to ESXi 6.0 and 6.5.
Step 1. Download the Offline Bundle(.zip file) through this link:
~ # esxcli software vib update -d /vmfs/volumes/datastore1/Vmware-ESXi-6.0.0-338
Message: The update completed successfully, but the system needs to be reboot ed for the changes to be effective.
Reboot Required: true
VIBs Installed: Adaptec_Inc_bootbank_scsi-aacraid_126.96.36.199.1.52011-1OEM.600.0. 0.2494585, Avago_bootbank_lsi-mr3_6.610.19.00-1OEM.600.0.0.2768847, Avago_bootba nk_lsi-msgpt3_14.00.03.00-1OEM.600.0.0.2768847, CSCO_bootbank_net-enic_188.8.131.52- 1OEM.600.0.0.2494585, CSCO_bootbank_scsi-fnic_184.108.40.206-1OEM.600.0.0.2494585, CSC O_bootbank_scsi-snic_0.0.1.26-1OEM.600.0.0.2494585, VMWARE_bootbank_mtip32xx-nat ive_3.8.5-1vmw.600.0.0.2494585, VMware_bootbank_ata-pata-amd_0.3.10-3vmw.600.0.0 .2494585, VMware_bootbank_ata-pata-atiixp_0.4.6-4vmw.600.0.0.2494585, VMware_boo tbank_ata-pata-cmd64x_0.2.5-3vmw.600.0.0.2494585, VMware_bootbank_ata-pata-hpt3x 2n_0.3.4-3vmw.600.0.0.2494585, VMware_bootbank_ata-pata-pdc2027x_1.0-3vmw.600.0.
Step 4. The display on the Esxi CLI after a successful upgrade of the file is shown in the image.
Step 5. Reboot the server as shown in the image.
Once you reboot the server, the Esxi client shows this on the screen.
Step 6. Exit from the Maintenance mode:
Or CLI. In order to do so, run the command:
Use this section in order to confirm that your configuration works properly.
To verify that the upgrade was completed successfully, you can use vSphere client. Navigate to the ESXi host and the new version can be seen at the top. Or use CLI. In order to do so, run the command: