Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

VXLAN packet drops when using nested VXLAN encapsulation (52936)

Last Updated: 6/15/2018Categories: InformationalTotal Views: 6916Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

You see unexplained packet drops on VXLAN networks using VXLAN port 4789.

Some packets on a given datapath will successfully reach their destination whereas others along the same datapath get dropped by the ESXi host.

You see the dropped packets when you capture packets on the "Drop" capture point despite the fact that DVS teaming and routing is configured correctly.

Your environment is configured as follows:

You are using NSX-v 6.2.3 or newer and VXLAN is configured on UDP port 4789.

You have hardware switches upstream.

The hardware switches have VXLAN tunnelling configured on them.

Cause

This issue occurs because the hardware switches are using port 4789 for VXLAN and NSX-v uses the same port for VXLAN. This means that within the physical infrastructure, you will find nested VXLAN.

Resolution

This is a known issue affecting VMware NSX for vSphere 6.2.x, 6.3.x and 6.4.x.

Currently, there is no resolution.

Note: Your physical hardware switch may not have support for nested VXLAN with both the inner and outer VXLAN encapsulation using the same port (4789).

Workaround

To work around this issue, change the VXLAN port either in NSX or in the physical switches so that they are both not using port 4789.

Note: Starting with NSX 6.2.3, the default VXLAN port is 4789, the standard port assigned by IANA. Before NSX 6.2.3, the default VXLAN UDP port number was 8472.

For more information on instructions to change the port in NSX-v to port 8472, see the Change VXLAN Port section of the NSX Upgrade Guide. If you are using Cross-vCenter NSX, see the Change VXLAN Port in Cross-vCenter NSX section of the NSX Upgrade Guide.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
vSphere 4.x でコマンド ライン インターフェイス (CLI) を使用してストレージを管理する (1029301)

Results 1-2 of 2

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.4.x

VMware NSX for vSphere 6.3.x

VMware NSX for vSphere 6.2.x

Take Our Survey

Support Assistant