6.0.3

Table Of Contents
Cause
During normal operation, changes to a VMware Directory Service (vmdir) instance in one
Platform Services Controller instance (node) show up in its direct replication partner within about 60
seconds. Depending on the replication topology, changes in one node might have to propagate through
intermediate nodes before they arrive at each vmdir instance in each node. Information that is replicated
includes user information, certicate information, license information for virtual machines that are created,
cloned, or migrated with VMware VMotion, and more.
When the replication link is broken, for example, because of a network outage or because a node becomes
unavailable, changes in the federation do not converge. After the unavailable node is restored, each node
tries to catch up with all changes. Eventually, all vmdir instances converge to a consistent state but it might
take a while to reach that consistent state if many changes occurred while one node was unavailable.
Solution
Your environment functions normally while replication happens. Do not aempt to solve the problem
unless it persists for over an hour.
Chapter 2 vSphere Authentication with vCenter Single Sign-On
VMware, Inc. 63