Netscape DIRECTORY SERVER 6.2 - ADMINISTRATOR Administrator's Manual page 343

In the URL field, enter the Administration Server URL in this format:
3.
http://hostname:admin_port
Click Netscape Administration Express and, when prompted, log in.
4.
Select a master Directory Server instance, and click Replication Status.
5.
This brings up a page for specifying the runtime parameters of the
replication-monitoring tool.
In the "Configuration file" field, type the path to the configuration file you
6.
created in Step 1 and click OK.
The replication-status page appears; by default, the page gets refreshed every
300 seconds.
Each table shows the status of the changes originated from a master replica.
Table Header: The table header shows the replica ID of the master replica, the
replica root, and the maximum Change State Number (CSN) on the master.
The important thing is to make sure that each master LDAP server has its
unique replica ID. Multiple replica roots on one LDAP server, however, could
share the same replica ID.
Table Row: Each row represents a direct or indirect consumer of the master
(identified in the Table Header).
Max CSN: It is the most recent CSN the consumer has replayed that was
originated from the master (identified in the Table Header).
Time Lag: It shows the time difference between the master and the consumer's
max CSNs for the changes originated from the master (identified in the Table
Header). A consumer is in sync with its master when its time lag is 0.
Last Modify Time: It is roughly the time when the consumer's max CSN was
replayed.
Supplier: This column lists all the suppliers of the consumer.
Sent/Skipped: Each supplier lists roughly how many changes originated from
the master (identified in the Table Header) have been replayed or skipped by
the consumer. The numbers are kept in suppliers' memory only. They will be
cleared if the supplier is restarted.
Update Status: The number is the status code and the string is the implication
of the status code. Watch this column for the possible dead lock if all the
suppliers complain that they cannot acquire busy replica. It is normal if one of
the suppliers is doing an update while the others can't acquire busy replica.
Monitoring Replication Status
Chapter 8 Managing Replication 343