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

Additional NSX-T manager nodes are stuck at "VM Clustering in Progress" (71125)

Last Updated: 9/29/2023Categories: InformationalTotal Views: 6292Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

After attempting to add one or more manager nodes to an NSX-T 2.4 installation, the additional node never move past the "VM Clustering in Progress" state in the UI.

Refreshing the UI, rebooting one or more manager nodes or deleting one more manager nodes does not change the behavior in the UI.

You see that all manager nodes are UP when you run get cluster status from the command line on one of the manager nodes.

Resolution

To resolve this issue, delete the nodes that were added and remove their deployments.

Log in to the original NSX-T manager node (console or SSH) as the admin user.

Issue the following command to retrieve the UUID values for each of the manager nodes:

get cluster status

Note: You will see output similar to the following:

Cluster Id: axxxxxx2-5xx3-4xx6-bxx5-9xxxxxxxxxx2
Group Type: DATASTORE
Group Status: STABLE

Members:
UUID                                       FQDN                                       IP               STATUS
6xxxxxx2-3xx2-axx8-5xxc-2xxxxxxxxxxb       nsxmgr-01a                                 192.168.xx.42   UP
5xxxxxxe-3xx8-4xxa-8xxd-1xxxxxxxxxx6       nsxmgr-02a                                 192.168.xx.43   UP
3xxxxxx9-bxxd-4xxb-9xx1-2xxxxxx7       nsxmgr-03a                                 192.168.xx.44   UP

Group Type: CLUSTER_BOOT_MANAGER
Group Status: STABLE

Members:
UUID                                       FQDN                                       IP               STATUS
5xxxxxxe-3xx8-4xxa-8xxd-1xxxxxxxxxx6       nsxmgr-02a                                 192.168.xx.43   UP
6xxxxxx2-3xx2-axx8-5xxc-2xxxxxxxxxxb       nsxmgr-01a                                 192.168.xx.42   UP
3xxxxxx9-bxxd-4xxb-9xx1-2xxxxxx7       nsxmgr-03a                                    192.168.xx.44   UP

Group Type: CONTROLLER
Group Status: STABLE

Members:
UUID                                       FQDN                                       IP               STATUS
bxxxxxx4-cxxb-4xxb-axxf-5xxxxxxxxxx0       nsxmgr-02a                                 192.168.xx.43   UP
9xxxxxxd-exx9-4xxc-bxx9-4xxxxxxxxxx0       nsxmgr-03a                                 192.168.xx.44   UP
cxxxxxx2-3xx0-4xxb-bxxd-9xxxxxxxxxx2       nsxmgr-01a                                 192.168.xx.42   UP

Group Type: MANAGER
Group Status: STABLE

Members:
UUID                                       FQDN                                       IP               STATUS
5xxxxxxe-3xx8-4xxa-8xxd-1xxxxxxxxxx6       nsxmgr-02a                                 192.168.xx.43   UP
6xxxxxx2-3xx2-axx8-5xxc-2xxxxxxxxxxb       nsxmgr-01a                                 192.168.xx.42   UP
3xxxxxx9-bxxd-4xxb-9xx1-2xxxxxx7       nsxmgr-03a                                    192.168.xx.44   UP

Group Type: POLICY
Group Status: STABLE

Members:
UUID                                       FQDN                                       IP               STATUS
5xxxxxxe-3xx8-4xxa-8xxd-1xxxxxxxxxx6       nsxmgr-02a                                 192.168.xx.43   UP
6xxxxxx2-3xx2-axx8-5xxc-2xxxxxxxxxxb       nsxmgr-01a                                 192.168.xx.42   UP
3xxxxxx9-bxxd-4xxb-9xx1-2xxxxxx7       nsxmgr-03a                                    192.168.xx.44   UP

Group Type: HTTPS
Group Status: STABLE

Members:
UUID                                       FQDN                                       IP               STATUS
5xxxxxxe-3xx8-4xxa-8xxd-1xxxxxxxxxx6       nsxmgr-02a                                 192.168.xx.43   UP
6xxxxxx2-3xx2-axx8-5xxc-2xxxxxxxxxxb       nsxmgr-01a                                 192.168.xx.42   UP
3xxxxxx9-bxxd-4xxb-9xx1-2xxxxxx7           nsxmgr-03a                                    192.168.xx.44   UP

Note:  Make a note of the UUID values corresponding to any manager nodes that are stuck at "VM Clustering in Progress".

Issue a command similar to the following to remove one of the problematic manager nodes.nodes:

detach node 3xxxxxx9-bxxd-4xxb-9xx1-2xxxxxx7

Note: Replace 3xxxxxx9-bxxd-4xxb-9xx1-2xxxxxx7  with the appropriate UUID value noted in Step 2.

Repeat Step 3 if there is another node that is also stuck.

From a system with the curl command installed and access to the original NSX-T manager VM, issue a command similar to the following to delete the deployment of one of the problematic manager nodes:

curl -k -u admin:VMware1! -X POST https://192.168.xx.42/api/v1/cluster/nodes/deployments/3xxxxxx9-bxxd-4xxb-9xx1-2xxxxxx7?action=delete&force_delete=true"

Note: Replace 192.168.xx.42 with the IP address of the original NSX-T manager VM and replace 3xxxxxx9-bxxd-4xxb-9xx1-2xxxxxx7  with the appropriate UUID value noted in Step 2.

Repeat Step 5 if there is another node that is also stuck.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

KB
•
Download and Install VMware Fusion (2014097)

KB
•
Resultado de la comprobación previa a la actualización con advertencias y errores durante la actualización a vCenter Server 7.0 Update 1 (79741)

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

VMware NSX-T Data Center

Take Our Survey

Support Assistant