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

Some operations fail in VMware Cloud Foundation 3.0 when the NSX Manager VM's hostname is in mixed case (59577)

Last Updated: 10/29/2018Categories: InformationalTotal Views: 4509Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

One or more NSX Manager VM's hostname is in mixed-case

Update or Precheck operations fail

Add host or cluster operations fail.

You see errors similar to the following in the SDDC Manager UI:

[4PU1C8] Failed to validate host spec [NSXMANAGER_NOT_ACTIVE:Addition of hosts into not active NSX manager NSXMANAGER-1.VCF.VxRack.Local is not allowed.]

You see errors similar to the following in the /var/log/vmware/vcf/commonsvcs/vcf-commonsvcs.log file on the SDDC Manager VM:

2018-10-09 18:56:32.478 INFO [http-nio-127.0.0.1-7100-exec-7] [com.vmware.evo.sddc.inventory.services.EntityInventoryServiceImpl] Update Entity type - NSXMANAGER Entity id - bbe3027e-97dd-45f9-8cb8-4922b2a35ce6 Status - ERROR

You see messages similar to the following in the /var/log/vmware/vcf/lcm/lcm.log file on the SDDC Manager VM:

2018-10-09 18:56:32.475 [pool-3-thread-8] ERROR [com.vmware.evo.sddc.lcm.primitive.impl.nsx.NsxAuditImpl] auditId=a53e1c5e-149a-4509-bfca-7ef36543029a,resourceType=NSX_MANAGER,resourceId=bbe3027e-97dd-45f9-8cb8-4922b2a35ce6, error auditing nsx manager bbe3027e-97dd-45f9-8cb8-4922b2a35ce6
org.springframework.web.client.ResourceAccessException: I/O error on GET request for "https://ESXI-04.VCF.VxRack.Local/api/1.0/appliance-management/summary/system": Host name 'NSXMANAGER-1.VCF.VxRack.Local' does not match the certificate subject provided by the peer (CN=NSXMANAGER-1.VCF.VxRack.Local, O=VMware, OU=VMware Engineering, L=Palo Alto, ST=California, C=US); nested exception is javax.net.ssl.SSLPeerUnverifiedException: Host name 'NSXMANAGER-1.VCF.VxRack.Local' does not match the certificate subject provided by the peer (CN=NSXMANAGER-1.VCF.VxRack.Local, O=VMware, OU=VMware Engineering, L=Palo Alto, ST=California, C=US)

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue is caused when the NSX Manager's hostname is not in lowercase characters.

Resolution

This is a known issue affecting VMware Cloud Foundation 3.0. To resolve this issue, ensure that the NSX Manager VM's hostname is specified in all lowercase letters.

Workaround

To workaround this issue, the following steps can be used:

Note: Take a snapshot of the SDDC Manager VM prior to starting.

Log in to the SDDC Manager VM as the vcf user.

Issue a command similar to the following to determine the id value for the offending NSX Manager:

cqlsh --cqlversion=3.4.4 -e "select id,vmhostname from inventory.nsxmanager where vmhostname='NSXMANAGER-1.VCF.VxRack.Local' ALLOW FILTERING"

Notes:

Replace NSXMANAGER-1.VCF.VxRack.Local with the name of the offending NSX Manager, ensuring that the case matches exactly.

You will see output similar to the following:

id                                   | vmhostname
--------------------------------------+-----------------------------
bbe3027e-97dd-45f9-8cb8-4922b2a35ce6 | NSXMANAGER-1.VCF.VxRack.Local

Issue a command similar to the following to update the NSX Manager hostname such that it is in all lowercase letters:

cqlsh --cqlversion=3.4.4 -e "update inventory.nsxmanager set vmhostname='nsxmanager-1.vcf.vxrack.local' where id='bbe3027e-97dd-45f9-8cb8-4922b2a35ce6'"

Wait at least five minutes and then retry the failing operation in the SDDC Manager UI.

Note: Remove any snapshots taken on the SDDC Manager VM.

Related Information

To be alerted when this article is updated, click the Subscribe to Article link in the Actions box.

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:

VMware Cloud Foundation

Related Versions:

VMware Cloud Foundation 3.0.x

Take Our Survey

Support Assistant