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

NSX-T workflows may fail if the ESXi hostnames are added in SDDC Manager with uppercase FQDNs (76553)

Last Updated: 3/29/2021Categories: TroubleshootingTotal Views: 3677Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

The follow workflows may fail in SDDC Manager if an ESXi Host was added to the inventory with an upper case FQDN.

Add host(s) to an NSX-T cluster.

Remove host(s) to an NSX-T cluster.

Add a cluster to a NSX-T Workload Domain.

Remove a cluster from a NSX-T Workload Domain.

Remove a NSX-T Workload Domain.

Cause

As vCenter will automatically change the case of the FQDN to lower case once an ESXi host has been added to the the inventory, this leads to a case sensitivity discrepancy and results in the workflow failure.

Resolution

This is a known issue, please use the below workarounds for the specific workflow failure.

Workaround

Add ESXi host(s) to a NSX-T cluster

Open an SSH to the SDDC Manager VM and change to the root user:

su -

With the below command, fetch all the ESXI hosts from SDDC Manager inventory and output to esxi-host-inventory.json file :

curl -k https://{sddc-manager-ip}/inventory/extensions/vi/esxis -u ' : ' | json_pp > esxi-host-inventory.json

Open esxi-host-inventory.json with a text editor and identify the host(s), which belong to the NSX-T cluster, which the host(s) are to be added.

Identify the hosts to be added to the cluster.

Rename the identified hostnames into lowercase and save the file.

Run the below command to update ESXi hostnames to lowercase in SDDC Manager inventory.

curl -k -H "Content-Type: application/json" -X PUT -d @esxi-host-inventory.json https://{sddc-manager-ip}/inventory/extensions/vi/esxis -u 'UserName:Password'

Execute the Add Host workflow.

After the workflow has been completed successfully, revert the hostname to the original name:

Fetch all the ESXI from SDDC Manager inventory into a nsxt-host-revert.json file.

curl -k https://{sddc-manager-ip}/inventory/extensions/vi/esxis -u 'UserName:Password' | json_pp > esxi-host-inventory-revert.json

Open esxi-host-inventory-revert.json with a text editor and identify the hosts for the NSX-T cluster, which have been added.

Rename the ESXi hosts hostname to the original case and save the file.

Run the command below to update SDDC Manager inventory:

curl -k -H "Content-Type: application/json" -X PUT -d @esxi-host-inventory-revert.json https://{sddc-manager-ip}/inventory/extensions/vi/esxis -u 'UserName:Password'

Remove ESXi host(s) to a NSX-T cluster

Open an SSH to the SDDC Manager VM and change to the root user:

su -

With the below command, fetch all the ESXI hosts from the SDDC Manager inventory and output to a deleteHost.json file:

curl -k https://{sddc-manager-ip}/inventory/extensions/vi/esxis -u 'UserName:Password' | json_pp > deleteHost.json

Open deleteHost.json with a text editor and identify the host(s) to be removed.

Rename the identified host(s) hostname(s) to the lowercase and save the file.

Update the ESXi entries by executing the below command.

curl -k -H "Content-Type: application/json" -X PUT -d @deleteHost.json https://{sddc-manager-ip}/inventory/extensions/vi/esxis -u 'UserName:Password'

Execute remove host workflow.

Add cluster to a NSX-Workload Domain

In this workflow, it's required to rename all hostnames which belongs to NSXT Workload domain to lowercase:

Open an SSH to the SDDC Manager VM and change to the root user:

su -

Using the command below, fetch all ESXi hosts from the SDDC Manager inventory to a nsxt-vi-hosts-lower.json file

curl -k https://{sddc-manager-ip}/inventory/extensions/vi/esxis -u 'UserName:Password' | json_pp > nsxt-vi-hosts-lower.json

Open nsxt-vi-hosts-lower.json with a text editor and Identify all the ESXi hosts which belong to the NSX-T workload domain.

Identify all the ESXi hosts to be selected during the add cluster workflow.

Rename the identified ESXi hosts hostnames to lowercase and save the file.

Update modified hostname in the SDDC Manager inventory by executing below command:

curl -H "Content-Type: application/json" -X PUT -d @nsxt-vi-hosts-lower. json https://{sddc-manager-ip}/inventory/extensions/vi/esxis -u 'UserName:Password'

Execute the add cluster workflow

Rename all ESXi hostnames, which belongs to the NSXT Workload domain, to the original case:

Fetch all ESXi hosts from the SDDC Manager inventory to a nsxt-vi-hosts-revert.json file:

curl -k https://{sddc-manager-ip}/inventory/extensions/vi/esxis -u 'UserName:Password' | json_pp > nsxt-vi-hosts-revert.json

Open the nsxt-vi-hosts-revert.json with a text editor and identify all the hosts which belong to the NSX-T workload domain.

Rename identified hostname to the original case and save it.

Update modified hostname in SDDC Manager inventory by executing below command

curl -H "Content-Type: application/json" -X PUT -d @nsxt-vi-hosts-revert. json https://{sddc-manager-ip}/inventory/extensions/vi/esxis -u 'UserName:Password'

Remove cluster from a NSX-T Workload Domain

Rename hostnames to lowercase, where host belongs to the cluster, the user intends to delete

Open an SSH to the SDDC Manager VM and change to the root user:

su -

Using the command below, fetch all the ESXI hosts from the SDDC Manager inventory and output to nsxt-cluster-host.json:

curl -k https://{sddc-manager-ip}/inventory/extensions/vi/esxis -u 'UserName:Password' | json_pp > nsxt-cluster-host.json

Open nsxt-cluster-host.json with a text editor and identify the hosts which belong to the NSX-T cluster that is intended to be deleted.

Rename the identified ESXi hostnames to lower case and save the file.

Update the hostnames in the SDDC Manager inventory by executing the below command:

curl -k -H "Content-Type: application/json" -X PUT -d @nsxt-cluster-host. json https://{sddc-manager-ip}/inventory/extensions/vi/esxis -u 'UserName:Password' Execute delete cluster workflow

Remove a NSX-T Workload Domain

Rename all hostnames ( which belongs to NSXT Workload domain) to lowercase

Open an SSH to the SDDC Manager VM and change to the root user:

su -

Using the command below, fetch all the ESXi hosts from  inventory to nsxt-vi-hosts-lower.json file

curl -k https://{sddc-manager-ip}/inventory/extensions/vi/esxis -u 'UserName:Password' | json_pp > nsxt-vi-hosts-lower.json

Open nsxt-vi-hosts-lower.json with a text editor and identify all the ESXi hosts which belong to the NSX-T workload domain.

rename identified hostname to the lowercase and save it.

Update modified hostname in VCF inventory by executing below command

curl -H "Content-Type: application/json" -X PUT -d @nsxt-vi-hosts-lower. json https://{sddc-manager-ip}/inventory/extensions/vi/esxis -u 'UserName:Password'

Execute Remove VI workflow.

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)

Result 1 of 1

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

Take Our Survey

Support Assistant