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

Tier0 removing already installed BGP routes in certain ECMP scenario (79012)

Last Updated: 5/11/2020Categories: TroubleshootingTotal Views: 5197Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

During BGP best path computation, when number of best paths available are more than the 8 maximum paths allowed on Edge Node you experience this symptom:

BGP may delete an already selected path from earlier computation and give preference to a new path even though they both are equally qualified as best paths.

Purpose

This article provides information on the non-standard BGP route selection algorithm in an ECMP corner case.

Cause

For this explanation, consider that the maximum paths allowed are 3, even if on the Edge Node the maximum is in reality 8.

Edge node received a BGP route for prefix a.b.c.d from a neighbor node. Neighbor node has router-id as 10.1.1.103. Edge Node installs this route into Data Plane.

Edge node received another BGP route for the same prefix a.b.c.d from another neighbor node. This neighbor node has router-id as 10.1.1.102 with all attributes like weight, local preference, MED are exactly matching with the earlier selected path. Edge Node installs this route into Data Plane.

a. Edge Node installs this route and existing “old route” (from node 10.1.1.103) is not disturbed.

Edge node received another BGP route for prefix a.b.c.d from another neighbor node. This neighbor node has router-id as as 10.1.1.104 with attributes like weight, local preference, MED matching are exactly matching with earlier two selected paths. Edge Node installs this route into Data Plane.

a. Edge Node installs this route and existing “old routes” are not disturbed.

Even though the BGP routes received in the above two cases are from neighbors with lower router-id and higher router-id, no change to existing/old routes and they were kept intact in data plane.

Edge node received another (fourth) BGP route for prefix a.b.c.d from neighbor node with router-id as 10.1.1.101. For example, now ECMP paths exceeds maximum paths allowed (3).

a. Edge node does not disturb the first ever BGP route installed for this prefix even though the new route is received from lower router-id neighbor. For example: From 10.1.1.101. So, the BGP route received from neighbor with router-id 10.1.1.103 will still be present in FIB.

b. However, now lower router-id check is performed among the remaining BGP routes from 10.1.1.102, 10.1.1.104 and 10.1.1.101. As per this check, FRR selects the remaining two BGP routes from 10.1.1.102 and 10.1.1.101. So the existing BGP route from 10.1.1.104 will be removed from Data Plane and a new BGP route from 10.1.1.101 will be installed into Data Plane.

Resolution

To resolve this issue, avoid having more then 8 best paths for any given network. You could have more than 8 paths, but make sure in this case that the additional paths have a BGP attribute to make them not preferred

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
将 NSX Manager 转换为独立模式时出现“存在通用对象 (Universal objects present)”错误 (2145547)

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

KB
•
Usage 计量器（UM）无法请求 NSX 拓扑 (78840)

Results 1-3 of 3

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

VMware NSX-T Data Center

Take Our Survey

Support Assistant