HP-UX Directory Server 8.1 administrator guide

1. Prepare a configuration file following the guidelines provided in the "repl-monitor.pl (Monitor
replication status)" section of the HP-UX Directory Server configuration, command, and file
reference.
2. Open the Administration Server URL in a web browser.
http://hostname:admin_port
3. Click HPDS Administration Express, and, when prompted, log in.
4. Select a supplier Directory Server instance, and click Replication Status.
This brings up a page for specifying the runtime parameters of the replication-monitoring
tool.
5. In the Configuration file field, type the path to the configuration file 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 supplier replica.
DescriptionTable
The table header shows the replica ID of the supplier 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 Header
Each row represents a direct or indirect consumer of the supplier (identified in the
Table Header).
Table Row
It is the most recent CSN the consumer has replayed that was originated from the
supplier (identified in the Table Header).
Max CSN
It shows the time difference between the supplier and the consumer's max CSNs for
the changes originated from the supplier (identified in the Table Header). A consumer
is synchronized with its supplier when its time lag is 0.
Time Lag
It is roughly the time when the consumer's max CSN was replayed.Last Modify Time
This column lists all the suppliers of the consumer.Supplier
Each supplier lists roughly how many changes originated 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.
Sent/Skipped
The number is the status code, and the string is the implication of the status code. Watch
this column for possible deadlock if all the suppliers complain that they cannot acquire
the busy replica. It is normal if one of the suppliers is doing an update while the others
cannot acquire the busy replica.
Update Status
8.18 Solving common replication conflicts
Multi-master replication uses a loose consistency replication model. This means that the same
entries can be changed on different servers. When replication occurs between the two servers,
the conflicting changes need to be resolved. Mostly, resolution occurs automatically, based on
the timestamp associated with the change on each server. The most recent change takes
precedence.
However, there are some cases where change conflicts require manual intervention in order to
reach a resolution. Entries that have a change conflict that cannot be resolved automatically by
the replication process contain a conflict marker attribute nsds5ReplConflict. The
nsds5ReplConflict attribute is an operational attribute that is indexed for presence and
equality, so it is simple to search for entries that contain this attribute. For example:
ldapsearch -D adminDN -w password
-b "dc=example,dc=com" "nsds5ReplConflict=*" \* nsds5ReplConflict
386 Managing replication