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

Transport Nodes Status in the NSX-T UI displays "Not Available" (76382)

Last Updated: 9/8/2020Categories: TroubleshootingTotal Views: 11263Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

Transport Nodes Status in the NSX-T UI displays "Not Available"

Rebooting the Transport Node doesn't resolve the issue.

The Transport Node connections the NSX Manager and NSX Controller are "Up".

The REST API to retrieve the status of the Transport Node display error similar to:

GET api/v1/transport-nodes/{TRANSPORT_NODE_ID}/status'
{
"httpStatus" : "NOT_FOUND",
"error_code" : 600,
"module_name" : "common-services",
"error_message" : "The requested object : TransportNodeStatus/XXXXXXXXX-XXXX-XXXX-XXXX-XXXX could not be found. Object identifiers are case sensitive."
}

There is no impact and everything is working as expected on the Transport Node.

In case of an Upgrade, NSX-T precheck will report errors on the affected Edge Transport Nodes:

Edge transport node status information not found from MP data for edge node <Edge TN ID>

Cause

The issue is caused by a race condition that may occur when the Transport Node is created or modified.
When a Transport Node is created or modified, a notification is sent to the NSX Manager which in turn queries the status of the Transport Node via API. Under some circumstances, the notification doesn't reach the NSX Manager and the status of the Transport Node is not queried and this result in this TN status displaying "Not Available".

Resolution

This issue is resolved in:

VMware NSX-T Data Center 2.5, available at VMware Downloads .
VMware NSX-T Data Center 3.0, available at VMware Downloads .

Workaround

To workaround this issue, restart the proton service on all 3 NSX Managers to force the status of the Transport Nodes to be queried again:
1.  Connect to the one NSX Manager in root mode.
2.  Run the following command to restart proton:
#/etc/init.d/proton restart
3.  Wait for the cluster to stabilize
#nsxcli -c get cluster status
4.  Once the cluster is stable repeat from step 1. for the next NSX Manager.

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)

KB
•
在 NSX-T 环境中执行 vMotion 后，虚拟机断开网络连接 (74767)

KB
•
在 VC 融合、跨域重新指向和全新部署期间，出现“install.vmafd.vmdir_vdcpromo_error_21”错误 (74678)

KB
•
使用单元管理工具停止或静默 vCloud Director 服务后，其他单元上未重新启动已调度的作业 (78620)

KB
•
HTML5 ユーザー インターフェイスを使用してメディア ファイルをカタログにアップロードすると、「入力が長すぎます (Input is too long)」というエラーが表示される (78640)

Results 1-5 of 5

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