A Non embedded OVA is used when deploying an embedded deployment of NSX-T

Products

• VMware NSX

Issue/Introduction

• NSX-T has been deployed in the vCenter using the embedded deployment option with the non-embedded OVF.
• You encounter errors similar to the one below when attempting to make certificate changes or enabling "Create Service Account" on your Compute Manager:

• Entries similar to the below can be observed in var/log/syslog on the NSX Manager:

2022-12-20T08:50:10.390Z nsx-mgr-01 NSX 9270 - [nsx@6876 comp="nsx-manager" level="WARNING" reqId="########-####-####-####-############" subcomp="manager" username="admin"] API result did not pass validationField level validation errors: {value 0 of property results[0].reverse_proxy_https_port has violated the minimum valid value 1}, {value of property results[0].access_level_for_oidc is not one of the allowed values [FULL, LIMITED]}

• Entries similar to the below can also be observed when trying to register a compute manager in the NSX manager UI 

"Compute Manager VcLink registration failed because of Unknown error in processing request for CM vcenter###.####.####### with id #####-######-#####-#################."

Environment

VMware NSX-T Data Center

Cause

This issue occurs when the unified OVA is used to deploy NSX as oppsed to the embedded unified OVF.
Please see the following guide for details on deploying NSX-T in vCenter as a plugin Install NSX Manager from vSphere Client.
In particular the section related to the OVF and which one to use:

If you enter a URL to download the OVF file, ensure the URL points to a secure HTTPS server. For example, https://<OVF-URL>. There is a separate OVF file available for NSX Manager deployed from vSphere Client. You must select a OVF file name using the following convention: nsx-embedded-unified-appliance-<releaseversion.buildversion>.ovf. Do not use the nsx-unified-appliance-<releaseversion.buildversion>.ova file.

Resolution

This is a known issue impacting NSX-T.

Workaround:
Should you encounter this issue, please raise a support request with Broadcom and refer to this KB article.