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

Logical Span Port mirroring result in GENEVE mac table "poisoning" (75201)

Last Updated: 1/27/2020Categories: TroubleshootingTotal Views: 9745Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Logical Span Port mirroring with direction "Egress" is used.

The ESXi host GENEVE mac table shows discrepancy between the entries learnt by the NSX Controllers and the entries learnt by Datapath learning.

Example:
#nsxcli -c get logical-switch e740ad8d-c06d-4cb6-b5f2-786f171451e7 mac-table

Logical Switch MAC Table
---------------------------------------------------------------------------

Host Kernel Entry
===========================================================================
Inner MAC            Outer MAC            Outer IP      Flags
00:50:56:88:96:7a    00:50:56:66:3d:2c      192.168.141.11    0xb <--- Datapath entry pointing to the incorrect TEP

LCP Remote Entry
===========================================================================
Inner MAC            Outer MAC            Outer IP
00:50:56:88:96:7a    00:50:56:6c:d2:3d      192.168.141.12 <--- Controller entry pointing to the correct TEP

VMs located on the ESXi host where the Logical Span Port mirroring destination VM is running loose connectivity to VMs with inconsistent GENEVE mac table entries.

Cause

This issue occurs because datapath learning is applied to mirrored packets while it should be skipped to avoid GENEVE mac table "poisoning".

Resolution

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

Workaround

To work around this issue, do one of the following:

Place the Logical Span Port mirroring source and destination VMs on the same ESXi host.

Do not use Logical Span Port mirroring with direction "Egress" ("Ingress" can be used as it will not cause the issue highlighted in this KB article).

Use Remote L3 Span instead of Logical Span for mirroring.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
无法在 vCloud Director 中选择硬件版本 15 (75198)

KB
•
Google 搜索提示和技巧 (75226)

KB
•
ベアラー トークンの利用 - ユーザー情報の取得：ユーザー データを含むデコードされた base64 ベアラー トークンに不整合がある (75137)

KB
•
vSphere Client プラグインを vCSA 6.7 U2 以降で登録した後、ユーザー インターフェイスに表示されない (75243)

KB
•
任意のノードで Docker サービスを再起動すると、サービスの状態が健全でなく、デプロイが失敗する (75183)

Results 1-5 of 5

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