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

In the Update Settings section, specify the bind DN that the supplier will
f.
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 not
subject to access control.
You can specify multiple supplier bind DNs per replica but only one
supplier DN per replication agreement. To specify your supplier bind DN,
enter your supplier bind DN in the "Enter a new Supplier DN" field, and
click Add. You supplier bind DN will appear in the Current Supplier DNs
list. Repeat the operation for every supplier bind DN you want to include
in the list.
Specify any supplier servers to which you want to refer updates.
g.
By default, all updates are first referred to the supplier servers that you
specify here. If you specify none, updates are referred to the supplier
servers that have a replication agreement that includes the current replica.
In the case of cascading replication, referrals are automatically sent to the
hub supplier, which in turn refers the request to the original supplier.
Therefore, you should set a referral to the original supplier to replace the
automatically generated referral.
On the supplier server, set up the replication agreement between this server
4.
and the hub supplier.
In the navigation tree of the Configuration tab, right-click the database to
a.
replicate, and then select New Replication Agreement.
Or highlight the database, and select New Replication Agreement from the
Object menu. This will start the Replication Agreement Wizard.
Go through the steps in the replication wizard by clicking Next to move to
b.
the following step.
You can initialize the read-only replicas from the Replication Agreement
Wizard or at anytime afterwards. For information on initializing read-only
replicas, refer to "Initializing Consumers," on page 345.
On the hub supplier, set up the replication agreement between this server and
5.
the consumer.
Configuring Cascading Replication
Chapter 8 Managing Replication 339