Jump to content

Global schema mismatch


MattDsa

Recommended Posts

Hi. I have 2 pods of 4 servers each. Within each pod the replication is fine but inter-site the global replication is show lots of errors and in all cases there is a schema mismatch being reported between the servers in one pod and the servers in the second pod. 

In the Admin console the dashboard in one site shows healthy and sees all the servers in the other site. However from the second site, the admin console health shows that only 3 of the 4 servers can be seen and one is unreachable. 

We are not actually using the cloud pod architecture and would like to remove it but Omnissa support have themselves said they prefer the replication fixed first. Has anyone had a schema mismatch and fixed it? Thanks. 

Link to comment
Share on other sites

  • Replies 2
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

I have not seen a global schema mismatch before. I’m not sure how you would fix that.  Typically schema and replication error recovery requires an authoritative restore of the LDAP instance. I’m not sure if there is a process for that in a Cloud Pod environment. 
 

I’m sure you’ve looked at it, but I’m going to ask anyway. Have you ruled out any firewall issues at site 2 that might be blocking traffic back to site 1?

Sean Massey
Independent Consultant/Analyst/Blogger | VCDX-EUC 247
Vice Chairman of the Board - World of EUC
Blog: thevirtualhorizon.com  Mastodon: @seanpmassey@vmst.io Instagram/Thread:
@seanpmassey LI: https://www.linkedin.com/in/seanpmassey/

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...