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

NSX T "Get Cluster Status" commands fail (79297)

Last Updated: 9/29/2023Categories: TroubleshootingTotal Views: 3245Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

This symptom can occur when querying the cluster status of an NSX T Management cluster if the cluster recently recovered from a period of time in which the nodes were unable to properly communicate with one another.  Example return is below.

nsxapp-01a> get cluster status

% The get cluster status operation cannot be processed currently, please try again later

While in this state, it is likely that detaching a node from the cluster will also fail to function.

nsxapp-01a> detach node <UUID>

% An error occurred while detaching the specified node. Reason: [CBM110] Detach cluster node is not allowed because it will cause datastore to lose cluster quorum. Please use 'deactivate cluster' operation to get single node datastore cluster.

Activity framework failures can be viewed within the nsxapi.log  on the NSX Manager.

2020-05-19T06:03:31.450Z ERROR L2TaskExecutor5 L2MessagingServiceImpl$LocalRpcRouter - SWITCHING [nsx@6876 comp="nsx-manager" errorCode="MP100" level="ERROR" subcomp="manager"] L2MsgService.handleMessage: Failed to handle message

com.vmware.nsx.management.container.activityframework.exceptions.ActivityFailedToCompleteException: Activity com.vmware.nsx.management.switching.sync.host.TransportNodeSyncNotifyActivity/4xxxxxx1-9xxx-xxxx-axx8-dxxxxxxxxxx4 failed to complete during the specified time duration 300 sec.

Cause

After cluster recovery, the activity framework is encumbered by a large amount of tasks. This large amount of tasks leads to queued tasks which are never accomplished within their 5 minute allocation. This cycle creates additional tasks to clean up the failed tasks.

The amount of tasks currently in the activity framework's queue can be observed with the following API call:

GET  https://<NSX-Manager-IP>/api/v1/operational/activityframework/scheduler/statistics

Resolution

This issue is fixed in NSX T 3.0 and as well as will be included in the upcoming 2.5.2 release.

Workaround

To reduce load on the activity framework and expedite it's self recovery, one may enact the following steps:

1.) Check activity framework load on each NSX Manager: GET  https://<NSX-Manager-IP>/api/v1/operational/activityframework/scheduler/statistics

2) Login to all transport nodes and stop ops-agent service (/etc/init.d/nsx-opsagent on ESXi hosts , /etc/init.d/nsx-opsagent-appliance on Edge Nodes).  Ops-Agent is a heart beat service that is especially taxing to the activity framework prior to NSX T 3.0.0 and NSX T 2.5.2.

3.) Reboot NSX T Managers one by one.

4.) 1.) Check activity framework load on each NSX Manager once more: GET  https://<NSX-Manager-IP>/api/v1/operational/activityframework/scheduler/statistics

It should be much lower now, allowing cluster activities to be completed.

5.) Start ops-agent on all Transport Nodes once more.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
AGGL-5282：Android の [プロキシ設定] ペイロードに、機能しないオプションが含まれている (79231)

KB
•
AAGNT-187402：Workspace ONE Intelligent Hub for Android アプリを組織グループを介して移動すると、そのアプリは再インストールされない (79410)

KB
•
AAGNT-188571：COPE モード デバイスの仕事用プロファイルで、アプリの位置情報サービスがすぐに有効にならない (79182)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX Transformers

Related Versions:

Take Our Survey

Support Assistant