Edge cluster deployment fails with error: "The requested object : vmnicX could not be found. Object identifiers are case sensitive. (Error code: 600)"

Products

• VMware NSX

Issue/Introduction

• You are setting up a new Edge cluster from scratch, and adding nodes directly into the cluster from the NSX UI wizard.
• The Edge nodes are configured over more than one DVS.
• Each DVS uses different physical interfaces (vmnics) on the underlying ESXi hosts.
• When saving the cluster with its preconfigured Edge nodes, the UI displays a red banner with the error message:
  The requested object : vmnic2 could not be found. Object identifiers are case sensitive. (Error code: 600)

Note: the exact name of the uplink reporting missing will vary and should correspond to the first uplink of the second DVS in use

Environment

VMware NSX 9.1 as a component of VCF 9.1

Cause

During validation of the Edge cluster and nodes, one of the API calls performed by the UI for verifying the physical uplinks erroneously limits its search scope to the first DVS only, thus failing to find the physical uplinks for the other DVS present in the setup.

Resolution

The permanent fix for this UI bug will be released as part of an upcoming version of VCF.

Workaround:

To avoid triggering the validation check error, you can deploy the Edge cluster without any nodes in it at first, then add Edge nodes to the cluster separately.