Anyone ever dealt with this KB Refresh API for Edge VM deployed using NSX-T Manager hits error 16047

[jeffj2000]

The KB is

https://kb.vmware.com/s/article/80957

We had this happen when we powerOFF our ELM vCenter to take snapshots before replacing SSL certs. We noticed several days later the alarms in the local managers.

[alarm]

The VM xxx-edge with moref id vm-24615 corresponding to the Edge Transport node a492c3aa-eb25-4e3a-af45-fee0646b45d1 vSphere placement parameters is found in NSX inventory but is not present in vCenter. Please check if the VM has been removed in vCenter or is present with a different VM moref id.

[alarm]

We checked the moref id and that is what the edge node is in vCenter. We saw pretty much the exact log messages in /var/log/proton/nsxapi.log they are a bit different wording but pretty much teh same. We did not remove any edge from vCenter we just took it down.

The local manager say this is the resolution:

[alarm]

The managed object reference moref id of a VM has the form vm-number, which is visible in the URL on selecting the Edge VM in vCenter UI. Example vm-12011 in https://<vc-url>/ui/app/vm;nav=h/urn:vmomi:VirtualMachine:vm-12011:164ff798-c4f1-495b-a0be-adfba337e5d2/summary Please find the VM xxx-edge with moref id vm-24615 in vCenter for this Edge Transport Node a492c3aa-eb25-4e3a-af45-fee0646b45d1. If the Edge VM is present in vCenter with a different moref id, please follow the below action. Use NSX add or update placement API with JSON request payload properties vm_id and vm_deployment_config to update the new vm moref id and vSphere deployment parameters. POST https://<manager-ip>/api/v1/transport-nodes/<tn-id>?action=addOrUpdatePlacementReferences. If the Edge VM with name xxx-edge is not present in vCenter, use the NSX Redeploy API to deploy a new VM for the Edge node. POST https://<manager-ip>/api/v1/transport-nodes/<tn-id>?action=redeploy.

[alarm]

this is confusing as the moref id has not changed. We are running NSX-T v3.2.1 in a Federated state with 2 edge at each site. Each edge has this error since taking vCenter down and I gues the local managers lost communication maybe for 20 minutes. I cant believe we would need to redeploy. Just looking for any advice. We are awaiting a support call back. Thank you.

[psheard]

We have seen this same issue with the same version of NSX-T / Federated / 2 edges at each site. We did have VCSA's unavailable while we patched the VCSA's.

The moref id has not changed so the workaround is not of any use.

What did you hear back from VMware GSS?

We only saw the error at our 2nd DC, although we did patch DC1 and DC2.

[jeffj2000]

Hello. We had GSS help us and use this API. Since I am unfamiliar with your environment, you should run this by your support engineer.

POST https://local-manager-vip/api/v1/transport-nodes/<tn-id>?action=refresh_node_configuration&resource_type=EdgeNode&read_only=true

To verify that is safe to do though you have to lookup the moref ids by clicking on the Edge and looking at the URL so you can compare the moref id. 

I also have these in my notes from the SR:

"As long as the moref id is intact on the VCSA and is in sync with NSX manager, there's nothing to worry about. You can check the moref id and compare with the alarm by clicking on the Edge VM within VCSA and looking at the URL. The URL will contain the moref id after the :VirtualMachine: part."

We ran this api after verifying all information and it fixed the issue. 

Thank you.