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

Replacing cluster certificate or node certificate on NSX Unified Appliance (78317)

Last Updated: 7/29/2020Categories: TroubleshootingTotal Views: 8022Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

When using CA signed certificates on NSX Unified appliance AND certificate not being a full chain, including Root, Intermediate and leaf certificate. Post installation, you experience these symptoms:

Deploying NSX Intelligence appliance fails.

While accessing NSX Intelligence from Discover & Take Action page in Plan & Troubleshoot tab in NSX-T Datacenter using CA signed certificates, you see this error similar to:

The application server is unable to fulfill your request due to insufficient privileges. You do not have the privileges to access NSX Intelligence. (403 Forbidden)

In the /var/log/pace/token-registration.log file of the NSX Intelligence appliance, you see entries similar to:

"ERROR: PACE Invalid cluster certificate used. Please use self-signed cert or upload FULL chain of CA signed cert including ROOT authority public cert!!'"

Cause

This issue may occur due to these reasons:

The cluster certificate is a partial chain (including Intermediate and leaf certificate), but not the Root CA certificate.

Certificate pem_encoded field contains extra Bag Attributes. (For example, non-base64 characters).

There is a time drift between NSX UA and NSX Intelligence appliance. This may happen if you are using different NTP servers or no NTP servers.

Resolution

This is a known issue in how chain certificate export is done at the Certificate Authority (CA). It affects all releases of NSX-T Data Center and NSX Intelligence.

Currently, there is no resolution.

Workaround

To work around this issue:

Note: All workaround steps require that the unsuccessfully deployed NSX Intelligence appliance is deleted.

For the cluster certificate that is a partial chain (including Intermediate and leaf certificate), but not the Root CA certificate

Export your CA signed certificate as a full chain. This includes root, Intermediate and leaf certificate.

Import and set the CA signed full certificate chain as your cluster certificate. For more information, see the Replace the Certificate for an NSX Manager Node or an NSX Manager Cluster Virtual IP section of the NSX Data Center Administration Guide.

Delete the old partial certificate that was uploaded.

For the cause of Certificate pem_encoded field containing extra Bag Attributes (For example, non-base64 characters)

Identify the certificates on NSX Unified Appliance which contain BagAttributes or non-base64 characters.

Follow steps in NSX-T Intelligence deployment stuck at message "The NSX Intelligence appliance deployment is in progress" (78048).

Upload the same certificates as new certs without the extra attributes/characters and only containing the actual cert starting and ending with:

-----BEGIN CERTIFICATE-----
.
.
-----END CERTIFICATE-----

Set the newly uploaded cert as node certificate or cluster certificate, as appropriate. For more information, see the Replace the Certificate for an NSX Manager Node or an NSX Manager Cluster Virtual IP section of the NSX-T Data Center Administration Guide.

Delete the old certificates with extra attributes/characters.

Redeploy NSX Intelligence appliance.

For the cause of a time drift between NSX UA and NSX Intelligence appliance

Delete the NSX Intelligence appliance.

Redeploy NSX Intelligence appliance.

As part of config provided during deployment, set NTP Servers to match the same servers as the ones configured on NSX UA.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
vRealize Log Insight で vCenter Server 収集アラートが毎日生成される (78107)

KB
•
Download and Install VMware Fusion (2014097)

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 2.5.x

VMware NSX-T Data Center

Take Our Survey

Support Assistant