Tag Archives: Upgrade

The VMware vSAN 6.6 has been released today. In this post, I am going to run through the 3 steps to upgrade vSAN 6.5 to vSAN 6.6. Upgrading Virtual SAN is a multistage process, in which you must perform the upgrade procedures in the order described here:

Beside Server Hardware, also double check if your IO Devices (eg. NIC, HBA,..) are supported when updating ESXi hosts from VMware vSphere 6.0 to 6.5. The following devices were supported in vSphere 6.0 but are according to VMwares HCL not (yet) supported in vSphere 6.5.

Double check your vendor support when updating ESXi hosts from VMware vSphere 6.0 to 6.5. Some systems have not been certified by their vendor yet. The following servers were supported in vSphere 6.0 but are according to VMwares HCL not yet supported in vSphere 6.5.

Your server is listed and you want to upgrade?

Usually, the list gets smaller a couple of weeks after a new vSphere version has been released. I will update this post when I notice changes.

Not supported does not say that it does not work.

Servers get certified by their vendor, not VMware. If you want a server to get certified, ask your vendor.

Vendor support matrices sometimes differ from VMware HCL. Please ask your vendor or VMware whether you are allowed to upgrade.

The list only includes common vendors: Apple, HP, Cisco, DELL, Fujitsu, Hitachi, IBM, Lenovo and Nutanix.

vCenter Server Virtual Appliance (vCSA) is the future. If you are still running the Windows-based vCenter, it's time to migrate to the appliance with vSphere 6.5.

Since vSphere 6.0, the appliance offers the same feature and scale as the windows based vCenter. vSphere 6.5 adds an X-Large deployment size, the update manager and a fully supported migration assistant to the appliance.Read more »

VMware has released an update for their network virtualization platform NSX. The updated fixes the Distributed Firewall Issue that forced VMware to pull NSX 6.2.3 from distribution. This update also fixes the SSL-VPN Issue announced in Security Advisory VMSA-2016-0007.2 (CVE-2016-2079).

VMware has release an update for their network virtualization platform NSX. Together with some minor changes to the product itself, VMware announced that all users with a NSX 6.2.3 (and beyond) license are now entitled to vRealize Log Insight for NSX at no additional charge.

What's new in VMware NSX 6.2.3

Double check your vendor support when updating ESXi hosts from VMware vSphere 5.5 to 6.0. There are a lot of systems that are no longer supported. The following servers were supported in 5.5 but are according to the VMware HCL no longer supported in vSphere 6.0.

Your server is listed and you want to upgrade? Don't panic.

Usually, the list gets smaller a couple of weeks after a new vSphere version has been released. I will update this post when I notice changes.

Not supported does not mean that it does not work.

Servers get certified by their vendor, not VMware. If you want a server to get certified, ask your vendor.

Vendor support matrices and VMware HCL have some mismatches at the moment (HP and IBM). Servers are listed at the bottom. Pleask ask your vendor or VMware if you are allowed to upgrade.

The upgrade from vCenter Server 5.1 to vCenter Server 5.5 (5.5.0 and 5.5.0a) fails during the SSO installation with the following error message:

The existing ssl certificate is invalid

After verifying the certificate i could confirm that it is valid and not expired. After troubleshooting the update log I figured out that the problem was caused by a wrong registry entry. The old 5.1 installation was using an IP address instead of the vCenters FQDN.

When you are updating VMware vCenter Server 5.1 to version 5.5 you always get that "Warning 25000" message. This post shows how to check that the certificate is valid, and how to replace a expired certificate

Warning 25000. Please verify that the SSL certificate for your vCenter Single Sign-On 5.1 SSL is not expired. If it did expire, please replace it with a valid certificate before upgrading to vCenter Single Sign-On 5.5.