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

Deploying NSX Controller fails in NSX-v 6.3.3 and 6.3.4 (51144)

Last Updated: 5/26/2018Categories: TroubleshootingTotal Views: 5376Language:
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

In NSX for vSphere 6.3.3 release, new NSX Controller deployment fails.

You see errors similar to:

In NSX-v 6.3.4 release, the new Controller deployment will succeed until January 1st, 2018 and any new Controller deployment will fail after that date.

The existing NSX-v 6.3.3/6.3.4 release Controller deployment will see a prompt to change the password after login if 90 days have passed after a Controller deployment similar to:

The VTEPs are UP, but it is being reported as Down.

Cause

The photon based Controllers has been set with a default 90 day password expiration (from release date) for the default user accounts (admin/root).

The Controller deployment for any green field deployments or redeployment of existing Controllers or upgrades to NSX 6.3.3 will fail as of Nov 2nd, 2017. However, for the existing NSX 6.3.3/6.3.4 deployments, the user (admin/root) accounts in the Controllers will expire after 90 days from the date it was deployed.

Notes:

NSX-v 6.3.4 will encounter the same issue starting on Jan 1st 2018.

Since the communication between NSX Manager and Controllers are based on certificates, the user account expiration does not cause any communication impact between any component and does not cause any data path outage.

The password expiration does not impact the HW component, but it does impact the status reporting as the NSX Manager cannot communicate with the NSX Controllers.

Resolution

The issue is resolved in the updated/reposted NSX for vSphere 6.3.3, 6.3.4 releases and newer versions of NSX for vSphere, available at VMware Downloads.

As a workaround for the existing NSX-v 6.3.3/6.3.4 deployments, and to avoid encountering this issue while upgrading to newer versions of NSX for vSphere, VMware developed a signed script that sets the password for user accounts on the Controller to never expire and if the password has already expired, it will reset the password to the one set by user during initial Controller deployment.

The workaround requires two signed scripts to be executed sequentially using REST API call to NSX Manager.

Download the attached signed_bsh_download_jar.encoded and signed_bsh_passwd_expiry_napi.encoded files.

Notes:

The same scripts are also mentioned in the workaround section of KB article At times certain controller APIs could fail due to cleanup of API server reference files (2151719). Running the scripts applies the same workaround for both KB articles.

While performing the below steps, the data path will not be impacted;

Run the following POST calls on NSX Manager:

Confirm IP connectivity from NSX Manager to all the NSX Controllers using the ping command. Proceed only after the IP connectivity is established.

Method: POST
URL: https://NSXMGR_IP/api/1.0/services/debug/script
Authentication: Basic authentication (Username : admin)
Headers: content-type - application/xml
Body : copy contents of the attached file signed_bsh_download_jar.encoded.
Expected Response: 200

Note: During copy/paste of the contents into the body, ensure no extra line/characters get added at the end to run the API successfully. Proceed to step-3 only if the response is 200. File a support request with VMware support if the API call fails after multiple attempts. For more information, see How to file a Support Request in Customer Connect (2006985).

Method: POST
URL: https://NSXMGR_IP/api/1.0/services/debug/script
Authentication: Basic authentication (Username : admin)
Headers: content-type - application/xml
Body : copy contents of the attached file signed_bsh_passwd_expiry_napi.encoded.
Expected Response: 200

Note: As a part of Step 3, the script will set a temporary password on the Controller, log in to the root shell and change the password for the user account back to the original password set during initial Controller deployment. If any or all of the Controllers are re-deployed, repeat the preceding steps again.

Related Information

The table below describes the build numbers between the old NSX-v 6.3.3 / 6.3.4 and the new NSX-v 6.3.3 and 6.3.4, along with corresponding NSX Controller build numbers

简体中文：在 NSX-v 6.3.3 和 6.3.4 中部署 NSX Controller 失败

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

signed_bsh_download_jar.encoded

signed_bsh_passwd_expiry_napi.encoded

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:

VMware NSX for vSphere

Related Versions:

Take Our Survey

Support Assistant