- There are two issues seen when Edge prechecks failed:
Error1:
Edge node "UUID" vmId is not found on NSX Manager. Please refer to https://kb.vmware.com/s/article/90072
There is a known KB related to this issue: Edge node UUID vmId is not found on NSX Manager but even after following the resolution still the same issue
Error2:
"The VM <edge_vm_name> with moref id <vm_moref_id> corresponding to the Edge Transport node <edge_node_uuid> vSphere placement parameters is found in NSX inventory but is not present in vCenter. Check if the VM has been removed in vCenter or is present with a different VM moref id."
There is a known KB related to this issue: Edge VM present in NSX inventory not present in vCenter alarm but even after following the resolution still the same issue
VMware NSX 3.2.1
Operations where the host is unregistered and registered back with vCenter with all VMs present result in the VMs having new moref ids.
Similar operations with VM unregister and reregister due to some other failure/recovery workflows result in VMs having a new moref id but NSX inventory and the Edge Transport node configuration still has a reference to the old moref id.
To solve this we will need to remove and deploy a new Edge:
**Please make sure to take NSX back up and also its recommended to perform this during a change window**
1. If there are more than 2 Edges in the Edge cluster, then remove the service interfaces and BGP references from the T0 Gateway (if this problematic Edge is being used in this T0 Gateway) relating to this specific Edge
2. Then remove the Edge from the Edge cluster
3. Delete this Edge VM from disk on vCenter and then initiate a Delete for this Edge from NSX UI
4. Once this Edge is removed, create a new Edge with same configurations from the NSX UI (reference doc: Create a New Edge Transport Node)
5. Once this new Edge is successfully deployed, perform the prechecks to see that there are no more precheck errors and no more alarms referring to Edge VM not present in vCenter
6. Edge can then be placed back in the cluster, and lastly configure back any related configurations that were removed in the first step like the service interfaces and BGP configurations and make sure Edge is in good state