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

The Distributed Logical Router cannot be used as the default gateway when using L2VPN to stretch two VXLAN networks (67555)

Last Updated: 12/2/2020Categories: InformationalTotal Views: 1055Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

When using L2VPN to stretch two VXLAN networks, the distributed logical router (DLR) is used as the default gateway

VMs on the remote side of the VPN in relation to the DLR instance cannot reach IPs on remote subnets

VMs on the remote side of the VPN in relation to the DLR instance cannot ping the DLR IP

VMs that are local to the DLR instance are able to ping the DLR IP and reach IPs on remote subnets

Cause

The VMs on the remote side of the L2VPN will resolve the vMAC of the DLR instance successfully but will not be able to reach the DLR IP and will be unable to reach IPs on other subnets as a result.  Because the DLR vMAC is the same for all DLR instances, the packets destined for the DLR are forwarded to the DLR port on the DVS at the remote site instead of being forwarded across the L2VPN where the correct DLR instance resides.

Resolution

Consider one of the following solutions:

Use cross-VC NSX and universal logical switch and logical router features as opposed to L2VPN.

Locate the default gateway for the stretched networks on an Edge gateway VM as opposed to using the distributed logical router.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
基于 VMware Validated Design 5.0 的 SAIC SDI (67677)

KB
•
将旧元数据解决方案迁移到新的 Edge 群集解决方案 (67554)

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:

VMware NSX for vSphere

Related Versions:

VMware NSX for vSphere 6.4.x

VMware NSX for vSphere 6.3.x

Take Our Survey

Support Assistant