VNIs are not seen on NSX controllers after adding the secondary NSX Manager to the Primary Manager

Products

• VMware NSX

Issue/Introduction

• VNIs are not seen on NSX Controllers after adding the secondary NSX Manager to the Primary Manager.
• In the vsm.log file of the secondary NSX Manager, you see entries similar to:
  
  2018-04-20 12:56:31.398 GMT INFO TaskFrameworkExecutor-9 ControllerSyncJobTrackerTask:109 - Starting ControllerSyncJobTrackerTask...
  2018-04-20 12:56:31.399 GMT INFO TaskFrameworkExecutor-9 ControllerServiceImpl:3718 - Synchronizing transport zone
  2018-04-20 12:56:31.412 GMT ERROR TaskFrameworkExecutor-9 ControllerServiceImpl:3722 - Unable to find TransportZone
  2018-04-20 12:56:31.413 GMT ERROR TaskFrameworkExecutor-9 ControllerSyncJobTrackerTask:144 - Failed to complete Synchronize Controller Tracker task
  com.vmware.vshield.vsm.vdn.exceptions.XvsException: core-services:837:Unable to create transport zone.
          at com.vmware.vshield.vsm.vdn.nvpcontroller.service.impl.ControllerServiceImpl.syncTransportZone(ControllerServiceImpl.java:3723)
          at com.vmware.vshield.vsm.vdn.nvpcontroller.service.impl.ControllerServiceImpl.createControllerSyncJobs(ControllerServiceImpl.java:3746)
          at com.vmware.vshield.vsm.vdn.nvpcontroller.service.task.ControllerSyncJobTrackerTask.run(ControllerSyncJobTrackerTask.java:117)
          at com.vmware.vshield.vsm.task.service.Worker.runtask(Worker.java:184)
          at com.vmware.vshield.vsm.task.service.Worker.executeAsync(Worker.java:122)
          at com.vmware.vshield.vsm.task.service.Worker.run(Worker.java:99)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
          at java.lang.Thread.run(Thread.java:748)
  2018-04-20 12:56:31.415 GMT INFO TaskFrameworkExecutor-9 ControllerSyncJobTrackerTask:152 - Force sync took: 0.015 sec
  2018-04-20 12:56:31.419 GMT ERROR TaskFrameworkExecutor-9 Worker:219 - BaseException thrown while executing task instance taskinstance-10807
  
  Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware NSX for vSphere 6.3.x

Cause

This issue occurs when the secondary NSX Manager is added to Primary NSX Manager, the three NSX Controllers are added to the secondary NSX Manager and a force sync for the NSX Controller is started. This force sync operation may fail because a Transport Zone UUID is not found. This is due to a race condition where the force sync operation is started before the Transport Zone UUID is created.

Resolution

This issue is resolved in VMware NSX for vSphere 6.4.2.

Workaround:

To work around this issue, start a manual force sync operation of the NSX Controllers by selecting the "Update controller State"on the Secondary NSX Manager in the Installation and Upgrade > Management.

 

Additional Information

Impact/Risks:
Secondary NSX Manager VNIs are not seen on the NSX Controllers after adding the secondary NSX Manager to Primary Manager hence data plane for those VNIs are impacted.