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

VMware Directory Service (VMDIRD) going to unrecoverable state due to CEIP settings mismatch during vCenter Server deployment (76646)

Last Updated: 5/11/2020Categories: TroubleshootingTotal Views: 6218Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

VMDIRD is going to unrecoverable state post deploying a new vCenter with embedded PSC or a new external PSC, pointing to an existing vSphere domain in ELM (Enhanced Linked Mode)

You will see entries similar to below in VMDIRD log

For Windows log location : %PROGRAMDATA%\VMware\vCenterServer\logs\vmdird\vmdir.log
For vCenter Server Appliance : /var/log/vmware/vmdird/vmdird-syslog.log

2019-07-25T14:24:57.790173+00:00 warning vmdird t@140488925480704: ReplDeleteEntry/VmDirInternalDeleteEntry: 66 (Operation not allowed on non-leaf). DN: cn=ConsentConfigContainer,cn=PhoneHome,cn=Services,dc=vsphere,dc=local, first attribute: cn, it's meta data: '59961:2:a1c1ae76-bb38-4414-9d56-164fe0554594:20190724200208.654:55550'. NOT resolving this possible replication CONFLICT. For this object, system may not converge. Partner USN 0

2019-07-25T14:24:58.094808+00:00 warning vmdird t@140488925480704: ReplDeleteEntry/VmDirInternalDeleteEntry: 66 (Operation not allowed on non-leaf). DN: cn=ConsentConfigContainer,cn=PhoneHome,cn=Services,dc=vsphere,dc=local, first attribute: cn, it's meta data: '60105:2:a1c1ae76-bb38-4414-9d56-164fe0554594:20190724200208.654:55550'. NOT resolving this possible replication CONFLICT. For this object, system may not converge. Partner USN 0

2019-07-25T14:24:59.912616+00:00 warning vmdird t@140488925480704: ReplDeleteEntry/VmDirInternalDeleteEntry: 66 (Operation not allowed on non-leaf). DN: cn=ConsentConfigContainer,cn=PhoneHome,cn=Services,dc=vsphere,dc=local, first attribute: cn, it's meta data: '61248:2:a1c1ae76-bb38-4414-9d56-164fe0554594:20190724200208.654:55550'. NOT resolving this possible replication CONFLICT. For this object, system may not converge. Partner USN 0

2019-07-25T14:25:06.605939+00:00 warning vmdird t@140488925480704: ReplDeleteEntry/VmDirInternalDeleteEntry: 66 (Operation not allowed on non-leaf). DN: cn=ConsentConfigContainer,cn=PhoneHome,cn=Services,dc=vsphere,dc=local, first attribute: cn, it's meta data: '65002:2:86bd65ad-2897-4e41-b201-80087e8c8c2a:20190724153438.014:55372'. NOT resolving this possible replication CONFLICT. For this object, system may not converge. Partner USN 0

Cause

This issue is caused due to Replication Conflicts of CEIP entries in VMDIRD Database

Resolution

This issue is resolved in vCenter Server 6.7 Update 3b, available at VMware Downloads.

Workaround

To workaround this issue:

Check the CEIP setting of the vCenter Server where new vCenter Server deployment is trying to point to in enhanced linked mode (replication partner)

Redeploy the PSC/VCSA with the current CEIP state of existing vCenter Server

You may follow below steps to get the CEIP information of existing vCenter server:

Login to vCenter webclient as SSO administrator or with an account with Global Permissions
Navigate to Home -> Administration -> Customer Experience Improvement Program

OR

ssh to vCenter Server Appliance/ PSC and run below command
/usr/lib/vmware-cis-license/bin/ceip-cli.py get-ceip

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
清理已逐出群集节点的遗留配置 (76662)

KB
•
削除されたクラスタ ノードの構成の残りをクリーンアップする (76662)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.7.x

Take Our Survey

Support Assistant