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

T0 Logical Routers stop receiving routes from T1 Logical Routers (77060)

Last Updated: 12/11/2020Categories: TroubleshootingTotal Views: 7825Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

NSX-T version in use is either 2.4.0, 2.4.1 or 2.4.2.

T0 Logical Routers stop receiving routes from T1 Logical Routers.

NSX Manager logs (nsxapi.log) display message(s) similar to:

2020-01-16T02:39:47.177Z  INFO ActivityWorkerPool-1-2 Tier1ToTier0AttachmentActivity - ROUTING [nsx@6876 comp="nsx-manager" subcomp="manager"] Existing advertised networks {10.10.10.0/24=T1_DOWNLINK, 10.10.20.0/24=T1_DOWNLINK} on TIER0 LogicalRouter/XXXXX-XXXXX-XXXXX-XXXXX-XXXXX from TIER1 LogicalRouter/XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

2020-01-16T02:39:47.177Z  INFO ActivityWorkerPool-1-2 Tier1ToTier0AttachmentActivity - ROUTING [nsx@6876 comp="nsx-manager" subcomp="manager"] Processing network AdvertiseNetworkInfo [routeType=CONNECTED, advertiseRouteType=T1_DOWNLINK, network=10.10.10.0/24, isAdvertiseAllow=true] for advertisement on TIER0 LogicalRouter/6e9424e7-b689-4240-bb1e-e3b8bd990ca5 from TIER1 LogicalRouter/a8bd6c32-68eb-4f22-8a19-0154294a6230

Note that the first message list subnets 10.10.10.0/24 and 10.10.20.0/24 but there is no "Processing network AdvertiseNetworkInfo" operation for subnet 10.10.20.0/24.

As a result the route is cleared from the T0 and NSX Manager logs (syslog) display message(s) similar to:

<182>1 2020-01-16T02:39:47.179Z nsx-manager-1 NSX 10058 ROUTING [nsx@6876 comp="nsx-manager" subcomp="manager"] Clearing advertise route for networks 10.10.20.0/24 on TIER1 router LogicalRouter/XXXXX-XXXXX-XXXXX-XXXXX-XXXXX from TIER0 router XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

Cause

The issue is caused by a software bug on the NSX Manager.

Resolution

This issue is resolved in NSX-T 2.4.3 and NSX-T 2.5.0.

Note: If you encounter this issue in NSX-T 2.4.2, upgrading to the newer version will not resolve this issue. You will need to first apply one of the workarounds. Once this is completed, the issue should no longer occur once you upgrade to NSX-T Data Center 2.4.3 and 2.5.0.

Workaround

As a workaround (and preventive workaround) you can use one of the following steps.

Manually add static routes for T1 subnets on the T0, the next hop should be the T1 router-link IP (by default it would be similar to 100.64.0.1):

In the Advanced UI: Advanced Network & Security > Networking > Routers > select the T0 > Routing > Static Routes > click "+ ADD" under Static Routes

In the Simplified UI: Networking > Tier-0 Gateways > Select the T0 and click Edit > Expand Routing > select Static Routes > click ADD STATIC ROUTE

Use reprocess LR API:

Check if T1 LR reporting this issue has an edge cluster associated

If not, associate a edge cluster to it and save. If you already have edge cluster associated to this T1 LR, this step can be skipped.

Run the reprocess API -/api/v1/logical-routers/<logical-router-id>?action=reprocess

POST https://x.x.x.x/api/v1/logical-routers/75ff754d-db47-4465-a880-1c06ec86b687?action=reprocess

This step should re-create desired routes in the T0 LR from T1 LR

Remove the edge cluster from the Tier1 if edge services are not needed.

Enable/Disable route advertisement flag on the T1 Logical Router:

This can be done from NSX GUI under T1 router>routing>Route Advertisement.

Check if global route advertisement is enabled on the T1 LR (It should be enabled) and disable it.

Enable the flag again - this will re-create desired routes again.

Note: With workaround#3 there will be a momentary loss of existing data traffic if there are other VM's attached and have N-S connectivity.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

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