This issue is resolved in VMware NSX for Data Center 6.4.5.
Workaround:
To workaround the issue you can either:
- Delete one NSX controller on the Primary NSX Manager and redeploy a new Controller.
- Remove Secondary Role from the Secondary NSX Manager and re-add it as Secondary.
Both workarounds will clear the inconsistent state of the Secondary NSX Manager and the file
/etc/vmware/netcpa/config-by-vsm.xml on the ESXi hosts managed by the Secondary NSX Manager will be updated with the NSX controllers information and the connections to the NSX controllers will be restored.
Verify on the ESXi host using:
#grep -E 'connectionList|server|port' /etc/vmware/netcpa/config-by-vsm.xml
#esxcli network ip connection list | grep 1234