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

Data plane outage during control plane outage (55738)

Last Updated: 6/19/2018Categories: TroubleshootingTotal Views: 5320Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

In an environment where the DLR Control VM is deployed either in HA mode or standalone with dynamic routing is configured, you see these symptoms:

Data plane experiences outage, no more dynamic routes on the ESXi hosts.

DLR Control VM sending explicit ‘leave’ message to the Controller will remove dynamic routes on the ESXi hosts. No route situation on the hosts will cause data plane outage in the North-South direction.

In the NSX Controller logs, you see entries similar to:

2018-01-19 20:45:08,525 62097502 [vdr worker 0] INFO com.vmware.controller.apps.vdr.VdrService  - VSE Connection [ip=10.254.33.27:44761, cnnId=2] leave vdr 0x23a8 locale 00000000-0000-0000-0000-000000000000, explicit leave true

2018-05-10 03:52:37,947 43058651830 [vdr worker 3] INFO com.vmware.controller.apps.vdr.config.RouteConfig  - vdrId <vdr_id> is in softflush state and EOM is received

2018-01-19T20:45:39.950105+00:00 2018-05-10 03: 52:39,949 43058653832 [vdr worker 3] INFO com.vmware.controller.apps.vdr.VdrService  - Closing vdr <vdr_id> for connection Connection [ip=10.254.33.24:40435, cnnId=1790]

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue occurs if the DLR Control VM is disconnected (For example: Shutdown, switchover, etc.) from the NSX Controller Cluster, the NSX Controllers cluster will initiate a flush of the dynamic routes on all the ESXI hosts (related to that DLR Control VM).

Impact / Risks

Control plane outage can affect data plane by removing dynamically learned routes from DLR instance.

Resolution

This issue is resolved in:

VMware NSX for vSphere 6.3.5 and later versions, available at VMware Downloads.

VMware NSX for vSphere 6.4.0 and later versions, available at VMware Downloads.

Note: After the fix, the NSX Controllers cluster keep the routes even if the DLR Control VM is disconnected to the Controller or switchover to standby DLR Control VM.

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

VMware NSX for vSphere 6.2.x

Take Our Survey

Support Assistant