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

Removing a host without first removing it as a replication node can lead to stale entries in NSX Manager (52418)

Last Updated: 3/24/2018Categories: TroubleshootingTotal Views: 3562Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

If a host serves as a replication node for a HW VTEP and it needs to be removed from its parent cluster, ensure first that it is no longer a replication node before removing it from the cluster. If that is not done, in some cases its status as a replication node is maintained in the NSX Manager database which can cause errors when further manipulating replication nodes.

Resolution

To resolve this issue, run the API call:

PUT https://NSXMGR_IP/api/4.0/vdn/hardwaregateways/replicationcluster?force=true

Note: A new API at NSX-v 4.0 has been added to NSX Manager that allows entries in the tor_ptep_cluster table to be manipulated without throwing an error in case stale entries are present.

Under some circumstances, one of NSX Manager tables, tor_ptep_cluster can come to contain entries for hosts that were once members of the PTEP cluster, but which no longer exist in VC inventory. Because the logic to manipulate these entries involves validating against inventory, operations start failing once a stale entry appears in the table. The tor_ptep_cluster table defines membership of hosts in the PTEP cluster. Once a stale entry appears in the table, the UI starts throwing errors and neither the UI nor the API seem able to add or delete hosts to the PTEP cluster.

with a body that is identical to the 2.0 API. Without the force=true query parameter, the call should behave identically with the 2.0 API. For example: It should fail when stale entries are present in the tor_ptep_cluster table.

Workaround

To work around this issue, remove a host as a replication node (if needed) before removing it from its parent cluster or the vCenter Server inventory.

To recover from this issue, contact VMware Support and note this Knowledge Base article ID (52418) in the problem description. To contact VMware support, see Filing a Support Request in Customer Connect (2006985) or How to Submit a Support Request.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
VMware Cloud Foundation LCM インベントリから ESXi 6.5 EP5 への参照を削除する方法 (52402)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX for vSphere

Related Versions:

VMware NSX for vSphere 6.4.x

VMware NSX for vSphere 6.3.x

VMware NSX for vSphere 6.2.x

Take Our Survey

Support Assistant