VMware Cloud Foundation Post MR2 NSX-T Aliasing Gap Analysis

Products

• VMware Cloud Foundation

Issue/Introduction

Symptoms:

• MR2 target BOM is based of VCF 4.4 but with a higher NSX-T version (3.1.3.7.0-19380457) than standard VCF 4.4 (3.1.3.5.0-19068434).
• Post MR2, upgrade to VCF 4.4.1 and above will not get NSX-T bundles as this version is not known as a required pre-requisite (bundle alias missing)

Environment

VMware Cloud Foundation 4.4.x

Resolution

Currently there is no resolution.

Workaround:

Possible actions at the end of MR2 and test outcome

	Alias	Good	Bad
Option 1	"bundleComponentType": "NSX_T_MANAGER", "versionAliases": [ { "version": "3.1.3.5.0-19068434", "aliases": [ "3.1.3.7.0-19380457"	Works universally for upgrades to 4.4.1 and 4.5 (with additional step of 2 hop NSX-T BOM upgrade from VCF 4.40 -> 4.4.1 -> 4.5 and not direct )	Notes: Need to ensure old NSX-T bundle used for MR2 is removed prior. It is already part of runbook. Bundle - 378ee892-20d5-4a8d-a47f-9111a60234cd If skip upgrade to VCF 4.5, NSX-T upgrade bundle to 4.4.1 will show up as an additional step (effectively it doesn't skip upgrade from NSX-T 3.1.3.7.0 directly to 3.2.1.x.
Option 2	"bundleComponentType": "NSX_T_MANAGER", "versionAliases": [ { "version": "3.1.3.7.4-19762317", "aliases": [ "3.1.3.7.0-19380457"	Works for VCF 4.5 upgrade only	VCF 4.4.1 upgrade will skip NSX-T 3.1.3.7.4 bundle

Proposed runbook step at the end of MR2 migration (after bundle cleanup step) - Option 1

Notes:

• Before applying the below steps, please ensure that NSX-T upgrade bundle used by MR2 is cleaned up - Bundle ID:378ee892-20d5-4a8d-a47f-9111a60234cd
• Please make sure to take a snapshot of SDDC Manager before applying the below steps.

1. In SDDC MGR UI, navigate to Developer Center -> API Explorer -> APIs for managing Version Alias Configuration
2. Expand the 2nd API -> PUT: /v1/system/settings/version-aliases
3. Paste the following in the Value field for versionAliasesForBundleComponentTypeSpec

{
"forceUpdate": true,
"versionAliasesForBundleComponentTypes": [
{
"bundleComponentType": "NSX_T_MANAGER",
"versionAliases": [
{
"version": "3.1.3.5.0-19068434",
"aliases": [
"3.1.3.7.0-19380457"
]
}
]
}
]
}

4. Click 'Execute'. You should get a response with the latest alias. Expand each one and look for the NSX-T Manager component and ensure the alias is populated as above. It is usually the 2nd last entry.

Additional Information

Please see Understanding the VersionAlias.yml file in SDDC Manager (89291)