Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

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

Last Updated: 5/4/2018Categories: TroubleshootingTotal Views: 3143Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

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.

Purpose

This article provides information and assist on troubleshooting an issue where the secondary NSX Manager VNIs are not seen on the NSX Controllers after adding the secondary NSX Manager to the Primary Manager.

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.

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.

Resolution

This is a known issue affecting VMware NSX for vSphere 6.3.x.

Currently, there is no resolution.

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.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX for vSphere

Related Versions:

VMware NSX for vSphere 6.3.x

Take Our Survey

Support Assistant