Configuring Multi-Master Replication334 Red Hat Directory Server Administrator’s Guide • May 2005d. In the Common Settings section, specify a Replica ID.The replica ID must be an integer between 1 and 254, both inclusive, andmust be unique for a given suffix. Make sure you specify an ID that isdifferent from the IDs used for read-write replicas on this server and onother servers.e. In the Common Settings section, specify a purge delay in the “Purgedelay” field.This option indicates how often the state information stored in thereplicated entries is purged.f. In the Update Settings section, specify the supplier bind DN or entry DNthat the supplier will use to bind to the replica.This supplier bind DN should correspond to the entry created in Step 2.The supplier bind DN corresponds to a privileged user because it is notsubject to access control.g. Specify the supplier server to which you want to refer updates (the othersuppliers in the multi-master set).Only specify the URL for the supplier server. If you want clients to bindusing SSL, you must specify a URL beginning with ldaps://.h. Click Save to save the replication settings for the database.4. Set up replication agreements on all the supplier servers:m On server M1, set up the following replication agreements: one withsupplier server M2, where server M2 is configured as a consumer for thereplica; one with supplier server M4, where server M4 is configured as aconsumer for the replica; and one for each consumer servers, Server C1through Server C8.m On server M2, set up the following replication agreements: one withsupplier server M1, where server M1 is declared as a consumer for thereplica; one with supplier server M3, where server M3 is declared as aconsumer for the replica; and one for each consumer servers, Server C1through Server C8.m On server M3, set up the following replication agreements: one withsupplier server M2, where server M2 is declared as a consumer for thereplica; one with supplier server M4, where server M4 is declared as aconsumer for the replica; and one for each consumer, Server C1 throughServer C8.
