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

Tier-0 Tier-1 communication down in an NSX-T 2.4.0 environment (68072)

Last Updated: 5/8/2019Categories: InformationalTotal Views: 5010Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The following criteria are all met

NSX-T 2.4.0 environment

The T0-T1 transit subnet is non default and is part of the 169.254.0.0/16 range

T1 connected networks are not visible on the active Edge T0 DR vrf when running "get forwarding"

T0 DR and T1 DR LinkedPort interfaces show no IPv4 address configured, only IPv6 e.g.

Edge1(vrf)> get int
Interface     : 98147703-a33d-4023-9d34-558832bdc09c
Ifuid         : 307
Name          : LinkedPort_T0
Mode          : lif
IP/Mask       : fe80::50:56ff:fe56:4455/64;fc66:c650:9440:e800::2/64
MAC           : 02:50:56:56:44:55
VNI           : 71683
LS port       : dcf2124f-a792-4bb1-946f-c05e6d9b5b46
Urpf-mode     : NONE
Admin         : up
Op_state      : up
MTU           : 1500

Cause

NSX-T 2.4.0 introduced support for IPv6.
This code change involved new handling of interfaces with link local addresses.
IPv4 link local subnet is 169.254.0.0/16.
Any transit subnet interface in the range 169.254.0.0/16 will be removed and not readded preventing communication between the T0 and T1 routers.
This issue is not present in earlier releases and can impact upgraded or newly installed environments.

Resolution

This is a known issue affecting NSX-T Datacenter 2.4.0. There is currently no resolution.

Workaround

The T0-T1 transit subnet must be re-configured to use a different subnet which is not part of 169.254.0.0/16.
The subnet is sepcified on the T0 router. To make the change the T1 routers must be detached from the T0. Once the change is complete the T1 routers can be readded.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
在具有 IPv6 子网的网络上启动的实例无法从 VDS 支持的 VIO 环境中的 DHCP 服务器收到地址 (68031)

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

KB
•
Download and Install VMware Fusion (2014097)

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

VMware NSX-T Data Center

Take Our Survey

Support Assistant