Red Hat DIRECTORY SERVER 7.1 - ADMINISTRATOR Administrator's Manual page 363

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
seconds.
300
Each table shows the status of the changes originated from a supplier replica.
Table Header — The table header shows the replica ID of the supplier
H
replica, the replica root, and the maximum Change State Number (CSN) on
the supplier. The important thing is to make sure that each supplier 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
H
supplier (identified in the Table Header).
Max CSN — It is the most recent CSN the consumer has replayed that was
H
originated from the supplier (identified in the Table Header).
Time Lag — It shows the time difference between the supplier and the
H
consumer's max CSNs for the changes originated from the supplier
(identified in the Table Header). A consumer is in sync with its supplier
when its time lag is
Last Modify Time — It is roughly the time when the consumer's max CSN
H
was replayed.
Supplier — This column lists all the suppliers of the consumer.
H
Sent/Skipped — Each supplier lists roughly how many changes originated
H
from the supplier (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
H
implication of the status code. Watch this column for possible deadlock 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.
.
0
Monitoring Replication Status
Chapter 8 Managing Replication 363