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 Node (Edge or hypervisor) connectivity to NSX Manager is Down (76230)

Last Updated: 1/7/2020Categories: TroubleshootingTotal Views: 9239Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

Transport Node (Edge or hypervisor) connectivity to NSX Manager is Down.

The NSX Manager "publish_fqdns" setting is set to true

GET /api/v1/configs/management
{
"publish_fqdns" : true, <---
"_revision": 1
}

NSX Manager logs (syslog.log) display message(s) indicating DNS reverse queries were failing when  "publish_fqdns" was set to true, similar to:

2019-09-09T09:23:55.369Z ERROR ExecutorChannel-1814785934 BrokerManager - SYSTEM [nsx@6876 comp="nsx-manager" errorCode="MP2119" subcomp="manager"] Reverse DNS lookup for IP 192.168.120.12 failed due to timeout or missing DNS configuration

Transport Node logs (syslog.log) repeatedly display message(s) similar to:

<179>1 2019-10-01T08:48:20.030750Z edge01.corp.local NSX 1554 - [nsx@6876 comp="nsx-edge" subcomp="mpa" tid="17006" level="ERROR" errorCode="MPA111"] Heartbeat message: configuration_hash mismatch new [d5c9aa2842c58ddf14119dcee626a4948eb5c4ff] -> old [798331249130c958689ede2c53748cb2b41d0e17]
<179>1 2019-10-01T08:48:20.030768Z edge01.corp.local NSX 1554 - [nsx@6876 comp="nsx-edge" subcomp="mpa" tid="17006" level="ERROR" errorCode="MPA110"] Missed or failed heartbeat. Signal ERROR to FE & Restart
<182>1 2019-10-01T08:48:20.030862Z edge01.corp.local NSX 1554 - [nsx@6876 comp="nsx-edge" subcomp="mpa" tid="1554" level="INFO"] Error/Cleanup handler. Signaling FE to restart

Cause

When setting "publish_fqdns" the NSX Managers perform reverse DNS queries to resolve the FQDN of the other NSX Managers. If an NSX Manager is not able to resolve DNS queries at this point, this will result in a configuration mismatch between the NSX Manager and the Transport Nodes connecting to it.
This configuration mismatch will cause the connection between the Transport Node and NSX Manager to flap and eventually result in the Transport Node been disconnected from the NSX Manager.

Resolution

To Resolve the issue:

1. Ensure all the NSX Manager can perform forward and reverse DNS lookups successfully for all NSX Managers (including self).
Example:
root@nsx-mngr-01:~# nslookup 192.168.120.10
Server:         192.168.110.10
Address:        192.168.110.10#53

10.120.168.192.in-addr.arpa     name = nsx-mngr-01.corp.local.

root@nsx-mngr-01:~# nslookup 192.168.120.11
Server:         192.168.110.10
Address:        192.168.110.10#53

11.120.168.192.in-addr.arpa     name = nsx-mngr-02.corp.local.

root@nsx-mngr-01:~# nslookup 192.168.120.12
Server:         192.168.110.10
Address:        192.168.110.10#53

12.120.168.192.in-addr.arpa     name = nsx-mngr-03.corp.local.

2. Set the "publish_fqdns" back to false and to true again using the following REST API:
GET /api/v1/configs/management
PUT /api/v1/configs/management
Example Request:
{
"publish_fqdns" : true,
"_revision": 0 <-- match the number is the GET API
}

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
NSX クラスタから非 NSX クラスタに ESXi を移動する際に、VTEP VMKernel ポートが削除されない (76170)

KB
•
适用于 vRA 8.0.0 HA 环境的修补程序解决了阻止某些服务在数据库故障切换事件后恢复的问题 (76222)

KB
•
Horizon 7 on VMware Cloud on AWS - Horizon 接続サーバから vCenter に対して断続的に SSL 接続できない問題が発生する (76145)

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

Take Our Survey

Support Assistant