Upgrading SDDC Manager when incompatible Edge clusters are present

Products

• VMware SDDC Manager
• VMware NSX

Issue/Introduction

As part of SDDC Manager upgrade, a "configuration drift" step is run to update system configuration data so it works with the newer VCF version.
In this process some configuration values are inferred from the existing configuration. If the existing configuration has been modified in unexpected ways, this can cause configuration drift application to fail. In turn this blocks the SDDC Manager upgrade.


This KB explains how to deal with config drift failures caused by unexpected Edge cluster configurations. This applies only when the Edge clusters were deployed by SDDC Manager and so are listed in VCF inventory. This KB does not apply to Edge clusters deployed directly through NSX, since SDDC Mgr config drift does not examine them. 

Environment

VCF 4.2 or higher, when upgrading to any VCF version less than 4.5

Resolution

When config drift reports a failure trying to determine usable Edge uplinks, in the ideal case the Edge node VM uplink PG connections could be restored to the expected one active and one standby uplink.

When this isn't possible, then the SDDC Mgr inventory may be temporarily modified to skip examination of the offending Edge cluster.
This is especially likely to be needed if using segments in place of trunked uplink PGs (e.g., using the same VLAN for host and Edge TEPs.). Please contact Broadcom support referencing this KB to implement the required steps.