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

More than one IP is visible on a VM in NSX-T when using Segment profile with "ARP snooping is enabled with Trust on every use" (79266)

Last Updated: 7/31/2022Categories: TroubleshootingTotal Views: 4436Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

Network Traffic is impacted when a Segment profile is applied where

ARP Snooping = enabled
VMware tool =  disabled
TOFU = disabled
ARP Binding Limit = 1
ARP ND Binding Limit Timeout = 10 (Minutes)

Scenario

VM1 - web-sv-02a
IP - 172.16.10.18
VNI - 67589
Mac -  00:50:56:ae:92:cd
Host - sa-esxi-05.vclass.local

VM2 - web-sv-01a
IP - 172.16.10.19
VNI - 67589
Mac - 00:50:56:ae:11:91
Host- sa-esxi-04.vclass.local

ARP entries on both the hosts respectively

sa-esxi-05.vclass.local> get logical-switch 67589 arp-table
Logical Switch ARP Table
--------------------------------------------------
Host Kernel Entry
==================================================
IP                 MAC          Flags
LCP Remote Entry
==================================================
IP                 MAC
172.16.10.19     00:50:56:ae:11:91
LCP Local Entry
==================================================
IP                 MAC
172.16.10.18     00:50:56:ae:92:cd

sa-esxi-04.vclass.local> get logical-switch 67589 arp-table
Logical Switch ARP Table
--------------------------------------------------
Host Kernel Entry
==================================================
IP                 MAC          Flags
LCP Remote Entry
==================================================
IP                 MAC
172.16.10.18     00:50:56:ae:92:cd
LCP Local Entry
==================================================
IP                 MAC
172.16.10.19     00:50:56:ae:11:91

With changed IP as below -- (This is the scenario where both VM1 and VM2 IP's are changed respectively as below)

VM1 172.16.10.18 - 172.16.10.19 (Changed IP) - 00:50:56:ae:92:cd
VM2 172.16.10.19 - 172.16.10.20 (Changed IP) - 00:50:56:ae:11:91

Now initiate the traffic by pinging default G/W from respective VM's.

Below are updated ARP entries on both the  hosts respectively  --

sa-esxi-05.vclass.local> get logical-switch 67589 arp-table
Logical Switch ARP Table
--------------------------------------------------
Host Kernel Entry
==================================================
IP                 MAC          Flags
LCP Remote Entry
==================================================
IP                 MAC
172.16.10.20     00:50:56:ae:11:91
LCP Local Entry
==================================================
IP                 MAC
172.16.10.18     00:50:56:ae:92:cd   --->> Stale entry as this shall take 10 minutes to expire according to ARP ND Binding Limit Timeout = 10
172.16.10.19     00:50:56:ae:92:cd   --->> Correct entry

sa-esxi-04.vclass.local> get logical-switch 67589 arp-table
Logical Switch ARP Table
--------------------------------------------------
Host Kernel Entry
==================================================
IP                 MAC          Flags
LCP Remote Entry
==================================================
IP                 MAC
172.16.10.18     00:50:56:ae:92:cd  --->> Stale entry as this shall take 10 minutes to expire according to ARP ND Binding Limit Timeout = 10
172.16.10.19     00:50:56:ae:92:cd  --->> Correct entry
LCP Local Entry
==================================================
IP                 MAC
172.16.10.19     00:50:56:ae:11:91  --->> Stale entry as this shall take 10 minutes to expire according to ARP ND Binding Limit Timeout =  10
172.16.10.20     00:50:56:ae:11:91  --->> Correct entry

With these ARP entries on respective hosts, VM traffic will be impacted until the old ARP entries are expired.
The behavior is expected, i.e. we have to wait until the old IP entry expires, in the case of TOEU.

Purpose

Expected behavior

Cause

With the scenario shown above, Since the same MAC exists for 2 IP, if the users ping 172.16.10.20 from one of the vm on host 4, the ping will not be completed and VM traffic will be impacted until the old ARP entries are expired.

Resolution

This is an expected behavior where Segment profile is applied on a Segment with ARP ND Binding Limit Timeout = 10 (Minutes) and TOEU.

This value can be set between 5-120 Minutes.

Workaround

The workaround in order to avoid the 10 or 5 minutes waiting do the following before the user changes IP:

1. On ESX hosts, where 67589 is the VNI:
net-vdl2 -l -s nsxvswitch -n 67589  -M  ARP -r
2. On VM:
ip neighbor flush all

Once the user does the above, the user can change IP and start to ping.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
[解決済み] CRSVC-11739：Workspace ONE UEM コンソールで Chrome (83.0.4103.61) から証明書をアップロードできない (79296)

Result 1 of 1

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

VMware NSX-T

Take Our Survey

Support Assistant