Hardware bindings are not getting pushed after recreating new controllers in NSX-V 6.4.4

Products

• VMware NSX

Issue/Introduction

Symptoms:

• Controller to Arista TOR shows the status as up and NSX Manager UI shows the status is down.

• Work loads in the replication cluster cannot reach servers connected to Arista TOR.

 

Environment

VMware NSX Data Center for vSphere 6.4.x

Cause

Observe there is a mismatch between Controller UUID and NSX Manager's DB UUID created for the TOR connection.

Controller: 

nsx-controller # show control-cluster hardware-gateway instances 

ToR-Uuid                                 Bfd-Enabled     UtepProbeInterval 

########-####-####-####-########826e     true            300 

nsx-controller #  

NSX Manager :

secureall=# select objectid, uuid from tor_gateway; 

   objectid   |                 uuid 

--------------+-------------------------------------- 

torgateway-3 | ########-####-####-####-########bc69 

(1 row)

Resolution

This is a known issue affecting NSXv Data Center for vSphere 6.4.4 and currently there is no resolution.

Workaround: