Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

Failed to create Transport Node on NSX-T 2.1 and 2.2 (56148)

Last Updated: 11/17/2018Categories: AlertsTotal Views: 5476Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

ESXi hosts fail to convert into transport nodes when the ESXi Advance System Setting titled Security.PasswordQualityControl is set to "disabled,disabled,disabled,disabled,8". This can be observed in the NSX GUI under Fabric --> Nodes -- Transport Nodes. The Configuration Status will show "Failed" and the following error message or similar message can be observed:

"=Host configuration: Failed to handle the HostConfig reply message from host dfff5403-971b-4111-a8a0-9b3ec24771dd [TN=TransportNode/dfff5403-971b-4111-a8a0-9b3ec24771dd]. Reason: RPC request timed out. App Init configuration: Failed to handle the AppInit configuration reply message from host dfff5403-971b-4111-a8a0-9b3ec24771dd [TN=TransportNode/dfff5403-971b-4111-a8a0-9b3ec24771dd]. Reason: RPC request timed out. LogicalSwitch full-sync: Failed to execute the LogicalSwitch full-sync RPC on host dfff5403-971b-4111-a8a0-9b3ec24771dd[TN = TransportNode/dfff5403-971b-4111-a8a0-9b3ec24771dd]. Reason: LogicalSwitchBulkMsg waiting for reply from MPA node:dfff5403-971b-4111-a8a0-9b3ec24771dd timeout."

ESXi host nsxa.log

2018-05-18T21:40:57Z nsxa: [nsx@6876 comp="nsx-esx" subcomp="NSXA[MainThread:485159947520]" tid="74986" level="DEBUG"] [WriteData] fd [7] byteWrite [40]
2018-05-18T21:40:57Z nsxa: [nsx@6876 comp="nsx-esx" subcomp="NSXA[MainThread:485159947520]" tid="74986" level="VERBOSE"] [ClosePipeEsx] closed ESX pipe [7]
2018-05-18T21:40:57Z nsxa: [nsx@6876 comp="nsx-esx" subcomp="NSXA[MainThread:485159947520]" tid="74986" level="VERBOSE"] [ClosePipeEsx] waitpid returned [75031]
2018-05-18T21:40:57Z nsxa: [nsx@6876 comp="nsx-esx" subcomp="NSXA[MainThread:485159947520]" tid="74986" level="ERROR" errorCode="MPA42054"] [SetPassword] update user [nsx-user] password failed with [14] retryCount:
2018-05-18T21:40:58Z nsxa: [nsx@6876 comp="nsx-esx" subcomp="NSXA[MainThread:485159947520]" tid="74986" level="DEBUG"] [WriteData] fd [7] byteWrite [40]
2018-05-18T21:40:58Z nsxa: [nsx@6876 comp="nsx-esx" subcomp="NSXA[MainThread:485159947520]" tid="74986" level="VERBOSE"] [ClosePipeEsx] closed ESX pipe [7]
2018-05-18T21:40:58Z nsxa: [nsx@6876 comp="nsx-esx" subcomp="NSXA[MainThread:485159947520]" tid="74986" level="VERBOSE"] [ClosePipeEsx] waitpid returned [75034]
2018-05-18T21:40:58Z nsxa: [nsx@6876 comp="nsx-esx" subcomp="NSXA[MainThread:485159947520]" tid="74986" level="ERROR" errorCode="MPA42054"] [SetPassword] update user [nsx-user] password failed with [15] retryCount:
2018-05-18T21:40:58Z nsxa: [nsx@6876 comp="nsx-esx" subcomp="NSXA[MainThread:485159947520]" tid="74986" level="CRIT"] [CreateNsxUser] Failed to setup [nsx-user].
2018-05-18T21:40:58Z nsxa: [nsx@6876 comp="nsx-esx" subcomp="NSXA[MainThread:485159947520]" tid="74986" level="CRIT"] [SetUp] Failed to create [nsx-user]. exit the nsxa process.

Purpose

This is a known issue affecting NSX-T 2.1 and 2.2

Cause

Password generated by nsxa for 'nsx-user' uses 3 character classes. ESXi 6.5 default password requirement is 4 character classes.

Resolution

This issue is fixed in NSX T 2.3 release.

Workaround

​To work around this issue edit the Security.PasswordQualityControl property under the Advanced System Settings for the host(s) that need to be converted to transport nodes. The compatible value is "disabled,disabled,disabled,7,7". Note that is setting may not match the required security policy for some organizations. You may need to delete the failed transport nodes and recreate them after changing the value of the Security.PasswordQualityControl property.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

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