Upgrading ESXi 5.5 U3 to ESXi 6.5

-
This article is for how to upgrade a ESXi 5.5 U3 to ESXi 6.5 via update manager.

I know, upgrading a ESXi host via update manager is very easy task but you may face some issues while upgrading due to some incompatible "VIBs". To overcome from this situation, you need to manually remove these VIBs from ESXi host and then proceed further for upgrade. Below is the screenshots of errors.
Below scan result showing compliance status as "Incompatible" not "non-compliant". As per below screenshot, some vibs are conflicting and needs to be removed before upgrade.

"Remove the conflicting VIBs or use Image Builder to create a custom upgrade ISO image that contains the newer versions of the conflicting VIBs, and try to upgrade again."



1. Check the ESXi host hardware compatibility with ESXi 6.5.
2. Download ESXi 6.5 ISO from VMware portal.
3. Upload ISO in update manager.
4. Create a Host upgrade baseline with the ESXi 6.5 ISO.
5. Put ESX host in maintenance mode.
6. Attached host upgrade baseline and scan the ESX host.
7. Compliance status should be "non-compliant" not Incompatible or any other.
8. SSH to ESX host and search for these conflicting VIBs.
9. Run command like below to find the VIBs

The net-qlcnic is the VIB package containing the Qlogic driver.
Now run the following command to check drivers used on your HBA interfaces:
# esxcli storage core adapter list

Looking at the drivers displayed, Qlogic driver is not in use by any HBA adapters.
The net-qlcnic package can be safely removed from the system through the command:
# esxcli software vib remove -n net-qlcnic

Removed other VIBs as well if required as per above process.

To complete the driver removal procedure, you need to reboot the host. 
Once ESX host rebooted and came UP in vCenter. Re-scan with upgrade baseline and compliance status should be "non-compliant" now.


Now, Remediate the ESX host with upgrade baseline. Click on finish.


A Remediate task will start and it will take 15-20 mins at least to successfully upgrade the ESX host to 6.5 version.

 Once the ESX host upgrade, check the ESXi version, upgrade enic and fnic drivers as well and exit from maintenance mode.

 This is a complete process of a ESXi host upgrade !!! Plz share your views and comments.

Comments

Post a Comment

Popular posts from this blog

How to migrate the N-VDS as the host switch to VDS 7.0 in NSX-T 3.x

-
Image
  Hello There, In this article, i am covering how to migrate the ESXi host switch from N-VDS to VDS 7.0 switch in NSX-T 3.2.x version. When using N-VDS as the host switch,  NSX-T  is represented as an opaque network in  vCenter Server . N-VDS owns one or more of the physical interfaces (pNICs) on the transport node, and port configuration is performed from  NSX-T Data Center . You can migrate your host switch to  vSphere  Distributed Switch (VDS) 7.0 for optimal pNIC usage and manage the networking for  NSX-T  hosts from  vCenter Server . When running  NSX-T  on a VDS switch, a segment is represented as an  NSX-T  Distributed Virtual Port Groups. Any changes to the segments on the  NSX-T  network are synchronized in  vCenter Server. We have an NSX-T environment running with NSX-T 3.2.2.1 version. this environment was designed and implemented with NSX-T 2.x version and that time we used the N-VDS as host switch configuration on the transport nodes bcuz VDS was not supported that time. 
Read more

vROPS appliances password remediation tasks failed from SDDC manager

-
Image
Issue details:-   Password remediation tasks on SDDC manager getting failed with below error. However, we are able to connect SSH with root password on the vROPS appliances, no issues with credentials. I checked Operations logs on SDDC manager and found below logs, indicating the SSH connectivity issues from SDDC to vROPS appliances. Tried to do SSH vROPS appliance from SDDC manager, getting below error... Seems some issue with ECDSA key.. Resolution:- SSH to vROPS appliance and retrieve the ECDSA ssh keys as below. Now, we have 2 options to update the correct SSH keys for vROPS appliance on SDDC manager known_Hosts files located at below location.   /root/.ssh/known_hosts   /etc/vmware/vcf/commonsvcs/known_hosts   /home/vcf/.ssh/known_hosts   /opt/vmware/vcf/commonsvcs/defaults/hosts/known_hosts First option is manually copy and paste the SSH key on all the known_hosts files and restart the SDDC manager services and then try to remediate the password again. it will be successful this
Read more

How to Import/Register a VM into vRA portal

-
Image
You can import an unmanaged virtual machine to a vRealize Automation environment. An unmanaged virtual machine exists in a vCenter but is not managed in a vRealize Automation environment and cannot be viewed in the vRA portal . Once you import an unmanaged virtual machine, the virtual machine is managed by using the vRealize Automation management interface. you can see the virtual machine on the Managed Machines tab or the Items tab. Please follow below steps to Import/Register VM into a vRA portal. Log in to vRealize Automation as a fabric administrator and as a business group manager. If you are importing virtual machines that use static IP addresses, prepare a properly configured address pool.  If you use bulk import to import a virtual machine with a static IP address that is allocated to another virtual machine, the import fails. Create a Blueprint and should not have even network attached as well. See below snapin. Create Network profile that shoul
Read more