Repair VmDir state in Read-only

[VmwareRunner]

Hello,

I have 2 VCSA with embedded PSC in ELM, and one PSC has his VmDir state in Read-only, so his status is unavailable :

On server 1:

Partner: *********
Host available: Yes
Status available: Yes
My last change number: 17350
Partner has seen my change number: 10346
Partner is 7004 changes behind.

On server 2 :

Partner: ******
Host available: Yes
Status available: No

How to repair it ?

Is it possible to fix it with the command vdcadmintool by simply setting the vmdir-state to Normal ?

What happen if on Server 2 I set VmDir state to Normal using vcadmintool, and then I Force start replication cycle with vcadmintool on Server 1 ?

[Ajay1988]

Please contact VMware Support as this requires some time to fix. 

If there are underlying problems to vmdird it will again fall back to null or read-only. Make sure to have backup's and powered off snapshots of both VCSA's before support makes any changes

[MikeStoica]

Highly recommend to engage VMware GSS for this. Had the same issue with replication between partners and fixed it with GSS help.

[Vinay3]

Hi,

Did you get the resolution for this ? 

[Vinay3]

Hey

Did you get any resolution for this issue ? 

Regards,

-Vinay