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

BFD tunnel down between Edge and ESXi when Edge uses trunk logical switch (70745)

Last Updated: 3/17/2021Categories: InformationalTotal Views: 10978Language:
Chinese (Simplified)JapaneseEnglish

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Symptoms

The following criteria are met

NSX-T Data Center 2.x

The Edge Node VM is running on an ESXi host prepared for NSX T

The Edge and ESXi TEPs are on separate VLANs

The Edge TEP interface is connected to a trunk logical switch

The BFD tunnel is Down between the Edge and the ESXi host where it is running

The BFD tunnels between the Edge and other ESXi hosts are Up

Cause

When an Edge runs on a prepared host the Edge TEP and Host TEP must be on separate VLANs.
BFD traffic between Edge and host and vice versa must leave the host to be routed externally.
In this case when a VLAN trunk logical switch is used, the BFD packet sent by the ESXi host is not routed to the physical network correctly. Instead the packet is sent directly to the Edge. It arrives on the Edge interface still tagged with the Host TEP VLAN and is dropped by the Edge.

Resolution

This issue is resolved in VMware NSX-T Data Center 2.5.0, available at VMware Downloads .

Note: When an Edge VM runs on a prepared host connected to the same NVDS as the host TEP, all versions of NSX-T continue to require that the Edge TEP is on a separate VLAN to the Host TEP.

Workaround

If the Edge must run on a prepared ESXi host then the Edge TEP interface should not use a VLAN trunk logical switch.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

KB
•
ESXi 6.7 U2 以降でスナップショットの削除中に仮想マシンの停止時間が長くなるか、SvMotion エラーが発生する (77030)

KB
•
无法重新连接虚拟机的网络适配器：设备 "0" 的配置无效 (77134)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware NSX-T Data Center 2.x

VMware NSX-T Data Center

Take Our Survey

Support Assistant