cn=monitor Virtual Status Entries
There are also a set of status entries held as virtual entries in the directory under cn=replication,cn=monitor. These entries can be examined using the ldapsearch command or by using the WindchillDS control-panel. To use the control-panel, first start the control-panel, then click Manage Entries in the left pane. This opens the Manage Entries window. Choose All Base DN’s in the Base DN: dropdown list. Open the cn=monitor entry, then the replication entry (cn=replication).
Under this cn=replication entry there are a set of entries associated with each baseDN. For example the following three entries might be seen the baseDN being replicated is o=ptc:
cn=cn_admin data
cn=cn_schema
cn=o_ptc
Further, under the cn=o_ptc entry (or similar entry at your site) you should see several entries, two of which will be similar to:
cn=Replication Domain 29597
cn=Replication Server 8989 host1 19468
The first entry gives information about the embedded LDAP server and its associated replication information. The second entry (and its subordinates) give information about the embedded Replication Server and its connections.
The following shows some of the content of the first entry:
cn=Replication Domain 29597
status: Normal
resolved-naming-conflicts: 8
unresolved-naming-conflicts: 4
resolved-modify-conflicts: 6
received-updates: 19
replayed-updates: 19
domain-name: o=ptc
connected-to: host1/192.168.11.186:8989
generation-id: 8425
lost-connections: 0
replayed-updates-ok: 17
Some of the content of the second entry:
cn=Replication Server 8989 host1 19468
generation-id: o=ptc 8425
domain-name: o=ptc
missing-changes: 0
replication-server-port: 8989
The first entry, the Replication Domain entry, shows an overall status and the Replication Server (connected-to attribute) to which the LDAP server is connected. This should normally be the embedded Replication Server. This entry also contains helpful information regarding conflicts and conflict resolution. If unresolved conflicts have occurred, the administrator can examine these to see if a conflict needs to be resolved differently, or if the losing entry(ies) simply need to be deleted. Refer to
Searching for conflict entries.
Both entries contain the generation ID. As noted earlier, for a given baseDN, (or domain-name as shown above), the generation ID should be the same on all servers. If this is not the case, then the servers need to be synchronized. Refer to the section
Servers no longer in sync in
Recovery.