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

eBGP between DLR and Edge may experience a routing loop after upgrading to NSX-v 6.3.5 (53221)

Last Updated: 4/4/2018Categories: TroubleshootingTotal Views: 4952Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

This article applies if your NSX BGP configuration satisfies all of the following conditions:

You are using a private AS range to peer your BGP domain. (AS Numbers 64512 to 65535)

The DLR, ESGs, or upstream routers are peering through eBGP with their private AS.

You are utilizing ECMP between your DLR and ESGs.

You are running NSX for vSphere 6.3.5.

When all of the above conditions are observed, you might experience routing loops in your NSX domain:

Running the show ip bgp command from the DLR or ESG, routes from eBGP neighbors do not display the full AS path.

On one or more ESGs, you observe that northbound routes are pointing to the DLR as the next hop.

Cause

There are two parts to this problem. Together they cause this issue.

In NSX for vSphere 6.3.5 and earlier, the ESG/DLR strips the private AS before advertising to eBGP peers, causing loss of AS-Path information.

In NSX for vSphere 6.3.5, send-side loop detection is disabled for BGP, which can potentially cause a routing loop.

Impact / Risks

Routing loops can occur within the BGP domain, which can cause North/South connectivity issues.

Resolution

This issue is resolved in:

VMware NSX for vSphere 6.3.6, available at VMware Downloads.

VMware NSX for vSphere 6.4.0, available at VMware Downloads.

Workaround

To work around this issue if you do not want to upgrade, either do one of the following:

Allow NSX internal routes to upstream neighbors for your DLR. You can implement the outbound filters on the DLR towards the ESGs to only allow the internal networks.

OR

Configure iBGP between the DLR and ESGs.

Note: For the second workaround, you need to add a default gateway on the DLR, or the network between the ESG and upstream router, with the ESG as the next hop. or, implement default information originate on all of the ESGs. If you implement default information originate on your ESGs, you will need to apply the appropriate filters to block the propagation of the default route on the upstream router.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant