Upgrade vSphere 6.0 to 6.5 by Offline Bundle

In previous post, we have learnt how to upgrade vSphere 6.5 via vSphere 6.5 installation ISO and Update Manager 6.5 (VUM). Now we will learn how to upgrade vSphere 6.0 to 6.5 via Office Bundle.

Firstly you need to enable SSH on the vSphere 6.0, then upload ESXi 6.5 offline bundle into one datastore on vSphere 6.0.

NOTE: Before the upgrade, you need to move virtual machine into the standby vSphere host by vMotion and put this vSphere host into maintenance mode.



Login into vSphere 6.0 by SSH, now you can see the current version is 6.0.0 build-362759.


Now you need to execute the following command to upgrade vSphere 6.0 to 6.5

esxcli software profile update -p ESXi-6.5.0-4564106-standard -d /vmfs/volumes/your_datastore/VMware-ESXi-6.5.0-4564106-depot.zip

After that you need to reboot vSphere 6.0 host and makes the change to be effective.


After reboot, you need to let vSphere host exits the maintenance mode. Login into vSphere host by SSH again, you can see the running version is 6.5.0 build-4564106.




Upgrade ESXi 6.0 to 6.5 via VMware Update Manager

VMware vSphere Update Manager 6.5 is now embedded into the vCenter Server Appliance (VCSA). If you have more ESXi hosts to upgrade patch or version upgrade, VMware suggest that choose VMware Update Manager (VUM) for upgrading hosts. The following demonstration, I will upgrade one vSphere 6.0 to 6.5 via VMware Update Manager 6.5.

NOTE: You need to move all working virtual machines to the standby vSphere hosts by vMotion when you apply any ESXi patch or version upgrade, then you start to upgrade task.

Firstly go to the Update Manager in the home page.


Go to ESXi Images tab, then clicks “Import ESXi Image” button to import 6.5 Image into Update Manager.



Then Create baseline.


Input the Upgrade Baseline Name, eg vShpere 6.5.


Click compliance view button after you created the baseline.


Clicks Attach Baseline button.


Select vSphere 6.5 Upgrade Baseline and OK.


Then clicks Remediate button.


Select the upgrade baseline, then Next.


Select which host needs to upgrade version 6.5, then Next.

13 1415

And the option where you can save as the default host remediation options for future use.


After clicks Finish button, it executes to host upgrade.


The host will enter to maintenance mode automatically then starts to host upgrade.

NOTE: It exits the maintenance mode automatically after the upgrade is successfully completed.


Image Builder in VMware vSphere 6.5 – Cloning a Image Profile


In previous post Image Builder in VMware vSphere 6.5, we have learnt how to setup the Image Builder in vSphere 6.5. Some of the features provided through AutoDeploy GUI included the ability to add/remove Depots, list/create/modify Image Profiles, check compliance of hosts against these rules and remediate hosts etc. All these featuers are now bundled with vSphere 6.5 and AutoDeploy GUI.


Now we will learn how to clone a Image Profile from the existing Image Profile througth AutoDeploy GUI. In the following demonstration,  will clone a new profile from the existing Image Profile “New ESXi 6.5 Image”.


You need to enter a unique image profile name, then Next.


If we want to add/remove packages (VIBs) from this image profile, you can select/unselect you wanted the VIB in avaiable software package list. Then Next.


vSphere ESXi Image Builder verifies that the change does not invalidate the profile, then Finish.

NOTED: If there is any dependency between VIBs, it lists out the all related VIB in this configuration wizard.


After a few times, you can see a new Image Profile “Clone of New ESXi 6.5 Image” is created.


EMC RecoverPoint for Virtual Machine – Protection Copy


Consistency Groups (CG) are the container for Production and Replica copies. A consistency group is needed if we want to protect one Production VM or multiple Production VMs that are in an application relationship. A single consistency group holds multiple copies of a VM – the Production VM copy and up to an additional four copies (Replica copies).

In first example there is a local copy for data protection which is protected by the same RecoverPoint cluster as the Production VM in Site A. The second copy of this Production VM is a remote copy for disaster recovery in Site B. Only one local copy is possible.

In second example we find the Production VM in Site C that has two remote copies – one in Site B and the other in Site A  which is used for testing or development, and the other for disaster recovery.

In third example, the Production VM is on a VMware cluster in Site B protected by RecoverPoint cluster. Two remote Replicas were created, both in the same remote Site C. Both copies to be in Site C for DR, backup, testing, or other reasons.


These various and flexible replication topologies can coexist in one RecoverPoint for VMs 4.3 system. In a vRP system, Production VMs can have Fan-out protection to two different sites from any location. Production VMs can be remotely protected to a central site for DR or a Production VM can be replicated twice to one remote site – for DR and extended image access.

Deploying VMware NSX Components


Following is the sequence of steps an administrator needs to perform for deploying VMware NSX components.
1. Deploy the VMware NSX Manager
2. Register the VMware NSX Manager with the vCenter Server.
3. Deploy three VMware NSX Controllers using the vSphere Web Client of the NSX API.
4. Prepare the clusters (ESXi hosts) through the NSX Manager.
5. Deploy logical network services depending on the application requirements.

Management Component of VMware NSX


The following diagram is listed each management component of VMware NSX. VMware NSX Manager is the management component of the VMware NSX deployment. NSX manager is registered with the vCenter Server. A plug-in is injected into the vSphere Web Client, which allows the deployment and management of the all the logical networks and services through the vSphere Web Client.


Blog at WordPress.com.

Up ↑