Hi Quanah,

Thanks for the swift reponse! I think I do, yes, see, from consumer one:

olcSyncrepl: {0}rid=202 provider=ldap://master-acc-02.ldap.infra.com:389 bindmethod=simple filter="(objectClass=*)" scope=sub binddn="cn=mirrormode,ou=Directory Access,o=infra,c=com" credentials=XYZ searchbase="o=infra,c=com" schemachecking=on type=refreshAndPersist retry="60 +" attrs="*,+" starttls=critical tls_reqcert=demand olcSyncrepl: {1}rid=201 provider=ldap://master-acc-01.ldap.infra.com:389 bindmethod=simple filter="(objectClass=*)" scope=sub binddn="cn=mirrormode,ou=Directory Access,o=infra,c=com" credentials=XYZ searchbase="o=infra,c=com" schemachecking=on type=refreshAndPersist retry="60 +" attrs="*,+" starttls=critical tls_reqcert=demand olcUpdateRef: ldap://provider-acc-02.ldap.infra.com:389 olcUpdateRef: ldap://provider-acc-01.ldap.infra.com:389

And the second consumer looks similar.

Thanks again!

On Mon, 12 Jun 2023 at 15:56, Quanah Gibson-Mount quanah@fast-mail.org wrote:

--On Monday, June 12, 2023 3:23 PM +0200 cYuSeDfZfb cYuSeDfZfb cyusedfzfb@gmail.com wrote:

...

Is there any explanation, why I would be unable to obtain these contextCSN attributes through an ldapsearch?

Do you have the syncprov overlay instantiated on the database on the consumers?

--Quanah