Upgrading an existing vSphere environment to vSphere 6.7 is a fairly simple process, and can be completed with minimal impact to production with the proper planning.

In this recipe, we will look at the steps required to properly plan an upgrade to vSphere 6.7. We will not cover the specifics of upgrading vCenter Server, ESXi hosts, or any other component of the virtual data center. Specific recipes for upgrading vCenter Server and ESXi host have been included in Chapter 4, vSphere Management Design, and recipes for upgrading virtual machines to the latest hardware are included in Chapter 9, Virtual Machine Design.

The following tasks should be completed when planning a vSphere 6.7 upgrade:

1. Verify existing hardware is on the VMware Hardware Compatibility List (HCL) at https://www.vmware.com/go/hcl.
2. Check for interoperability between VMware products using the VMware Product Interoperability Matrix at http://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.php.
3. Determine interoperability and support between VMware vSphere 6.7 and third-party hardware and software products.
4. Determine the proper upgrade path and sequence.
5. Note that direct upgrades from vSphere 5.x to 6.7 are not supported. You'll need to upgrade your 5.x environment to 6.0 or 6.5 before upgrading to 6.7.

Completing these steps to properly plan a vSphere 6.7 upgrade will ensure the upgrade can be completed successfully.

With each release of vSphere, VMware adds support for new hardware and firmware for devices such as disk controllers, server platforms, and Network Interface Cards (NICs). VMware also removes support for older hardware and firmware. It is important to verify that the hardware is on the supported compatibility list prior to attempting an upgrade. Using the VMware Hardware compatibility list is covered in more detail in Chapter 8, vSphere Physical Design. Failure to validate support for hardware on the HCL can cause significant issues after the upgrade; unsupported hardware may not be available for use or may cause instability in the environment. Replacing unsupported hardware or upgrading firmware on current hardware to a supported configuration may be required as part of the upgrade process.

Checking for interoperability between vSphere products will help to ensure there is minimal impact on functionality during and after the upgrade process. Just like the hardware and firmware, the interoperability between vSphere products changes with each version. New support is added for newer products and features, while support may be removed for older, end-of-support products and features. Details on using the VMware Product Interoperability can be found in Chapter 4, vSphere Management Design.

The virtual data center may contain many third-party products that integrate with the vSphere environment. These products often include backup and recovery software, replication software, and management and monitoring applications. Before upgrading to vSphere 6.7, check with each third-party product vendor to validate support for vSphere 6.7 or to determine the requirements for vSphere 6.7 support. This is the step I see missed most often, typically due to not fully understanding dependencies with these products. It is critical to understand what products require integration with the vSphere environment and the impact changes to the environment may have on this products. Again, this is where proper planning from the beginning ensures a successful vSphere 6.7 upgrade.

The final step is to determine the proper upgrade path. If validation of support and interoperability has been completed correctly, this step will likely be the easiest aspect of the process. Once hardware, VMware product, and third-party product interoperability have been validated, a plan can be formulated for upgrading.

Details are important when it comes to the support of hardware and software in the virtual data center. Spending time Spending time to properly plan will ensure a successful upgrade to vSphere 6.7.