When it comes time to upgrade a VMware Product, your first stop should be the VMware Compatibility Guide. Why, you ask? A VMware environment contains a number of components beyond VMware vSphere, and it is important to make sure all these components work together in your environment. The VMware Compatibility Guide, which some may refer to as the VMware Compatibility Matrix is the result of a ton of hard work between VMware and their various partners. VMware and their partners spend hours upon hours validating specific VMware software versions and specific partner hardware and software versions.
Ensuring your configuration is supported is the first step for a successful vSphere Upgrade. If you run into issues, you will want to call VMware support, or support of a VMware partner. The first thing they will review with you is all of your hardware and software versions, beyond just VMware vSphere. Guess what? If the combination you are running is not listed on the VMware Compatibility Matrix, you may not be able to receive support. The last thing you want to do is to hear that customer support cannot help you, or that there will be extra costs associated with support.
Now that we know why ensuring our configuration is listed on the VMware Compatibility Guide is so important, we are going to take a closer look at how we can ensure our configuration is supported on the VMware compatibility matrix.
Two Ways to Determine VMware Product Interoperability
There are two ways to determine VMware product interoperability, and it depends on what components you are looking at. These two ways are by examining the following VMware compatibility products:
The VMware Compatibility guide is what we have been talking about so far. It is what we use when we need to make sure that a VMware product is compatible with something else in our IT infrastructure, such as the servers we are going to install it on, or the storage array we are going to connect it to.
The VMware Product Interoperability Matricies are used when we want to check which versions of VMware products are compatible with each other. For example, if we are running VMware vSphere 6.7, and we want to run VMware Horizon 7, we would check THIS matrix to make sure they work together.
((I have noticed that all vendors have a different name for their tools of this type which is why it gets confusing. It is important to know where to look based on the components you are panning on upgrading. The terms “compatibility matrix” and “interoperability matrix” are pretty generic and mean almost the same thing, so it is important to know what the vendor you are dealing with refers to when they are talking about compatibility and interoperability of their products)))
Using The VMware Compatibility Guide aka VMware Compatibility Matrix
Now, we are going to take a look at how to use the VMware Compatibility Guide. You can access it by clicking this link.
The default view of the VMware Compatibility Guide is Systems/Servers. You would use this view to take a look at your server hardware to ensure it is supported by the VMware product you would like to upgrade. There are also many other views available, which you can see below:
All of the areas listed here are very important integration points for VMware vSphere and infrastructure components of their partners. Remember, VMware is a software company, and software always requires hardware to run on.
First and foremost, I want to make sure my server hardware is supported. Since I am using Cisco UCS for my ESXi hosts, I have entered the information as follows into the VMware Compatibility Guide. I have made sure to select the ESXi version I want to upgrade to (vSphere 6.7), the system type (Blade), the Partner Name (Cisco) and made sure to include all features.
Next, the Compatibility guide provides me with an interoperability matrix for VMware and Cisco UCS Blade servers as shown below:
As we can see, there are 12 UCS blade models supported in this list, including the one I was looking for, great!
Now, we are going to take a closer look at the interoperability vSphere 6.7 and the Cisco UCS B200 M4.
This details page lists things like BIOS versions we will need, and any caveats there are for interoperability of vSphere 6.7 and the Cisco UCS B200 M4. For example, you can see that Wake-on-Lan or WOL is not supported with the Cisco UCS B200 M4. There is also a note that you should also check the vendor’s corresponding compatibility matrix.
This is a good reminder, because beyond checking the VMware Compatibility Guide for the Cisco UCS B200 M4, we should also check the Cisco equivalent (which is the called the Cisco UCS Hardware and Software Compatibility tool) for Cisco’s stated computability with ESXi 6.7.
When to Check The VMware Compatibility Matrix
As I mentioned earlier, it is important to check the VMware Compatibility Tool before upgrading your vSphere infrastructure, or anything that interacts with it directly, such as your storage array or backup software. While it is tempting to immediately upgrade to the newest vSphere version using vSphere Update Manager, the fact is that not all partners will support the new vSphere release the day it arrives.
If you do not already have a chart or list of the components of your VMware vSphere Environment, now would be a good time to make one. This way, you can always verify each and every component on the list before you attempt a VMware vSphere Upgrade, or a component of it.
Are you looking for step by step instructions to help you upgrade to vSphere 6.7? Check out detailed instructions on how to use vSphere Update Manager to upgrade from ESXi 6.5 to 6.7 here.
If you are running vSphere 5.5 and want to upgrade to vSphere 6.7, you must make a stop at vSphere 6.5. Follow these instructions for using vSphere Update Manager to upgrade ESXi 5.5 to 6.5, then use the instructions above to upgrade ESXi 6.5 to 6.7.