Chapter 3. Configuring multi-supplier replication using the command line

Procedure

1. Enable replication for the dc=example,dc=com suffix:

   # dsconf <supplier1_instance_name> replication enable --suffix "dc=example,dc=com" --role "supplier" --replica-id 2 --bind-dn "cn=replication manager,cn=config" --bind-passwd "<password>"

   This command configures the supplier1.example.com host as a supplier for the dc=example,dc=com suffix, and sets the replica ID of this entry to 2. Additionally, the command creates the cn=replication manager,cn=config user with the specified password and allows this account to replicate changes for the suffix to this host.

   Important

   The replica ID must be a unique integer between 1 and 65534 for a suffix across all suppliers in the topology.

2. Add the replication agreement and initialize the new server:

   # dsconf <supplier1_instance_name> repl-agmt create --suffix "dc=example,dc=com" --host "supplier2.example.com" --port 389 --conn-protocol LDAP --bind-dn "cn=replication manager,cn=config" --bind-passwd "<password>" --bind-method SIMPLE --init example-agreement-supplier1-to-supplier2

   This command creates a replication agreement named example-agreement-supplier1-to-supplier2. The replication agreement defines settings, such as the new supplier’s host name, protocol, and authentication information that the supplier uses when connecting and replicating data to the new supplier.

   After the agreement was created, Directory Server initializes supplier2.example.com. Depending on the amount of data to replicate, initialization can be time-consuming.

Verification

1. Display the replication configuration:

   # dsconf <supplier1_instance_name> replication get --suffix "dc=example,dc=com"

   dn: cn=replica,cn=dc\3Dexample\2Cdc\3Dcom,cn=mapping tree,cn=config
   ...
   nsDS5ReplicaBindDN: cn=replication manager,cn=config
   nsDS5ReplicaRoot: dc=example,dc=com
   nsDS5ReplicaType: 3
   ...

   These parameters indicate:

   • nsDS5ReplicaBindDN specifies the replication manager account.
   • nsDS5ReplicaRoot sets the suffix that is replicated.
   • nsDS5ReplicaType set to 3 defines that this host is a supplier.

2. Verify whether the initialization was successful:

   # dsconf <supplier1_instance_name> repl-agmt init-status --suffix "dc=example,dc=com" example-agreement-supplier1-to-supplier2

   Agreement successfully initialized.

3. Display the replication status:

   # dsconf <supplier1_instance_name> repl-agmt status --suffix "dc=example,dc=com" example-agreement-supplier1-to-supplier2

   Status For Agreement: "example-agreement-supplier1-to-supplier2" (supplier2.example.com:389)
   Replica Enabled: on
   Update In Progress: FALSE
   Last Update Start: 20210331071545Z
   Last Update End: 20210331071546Z
   Number Of Changes Sent: 2:1/0
   Number Of Changes Skipped: None
   Last Update Status: Error (0) Replica acquired successfully: Incremental update succeeded
   Last Init Start: 20210331071541Z
   Last Init End: 20210331071544Z
   Last Init Status: Error (0) Total update succeeded
   Reap Active: 0
   Replication Status: Not in Synchronization: supplier (6064219e000100020000) consumer (Unavailable) State (green) Reason (error (0) replica acquired successfully: incremental update succeeded)

   Verify the Replication Status and Last Update Status fields.

Procedure

1. Add the replication agreement to the existing instance:

   # dsconf <supplier2_instance_name> repl-agmt create --suffix "dc=example,dc=com" --host "supplier1.example.com" --port 389 --conn-protocol LDAP --bind-dn "cn=replication manager,cn=config" --bind-passwd "<password>" --bind-method SIMPLE example-agreement-supplier2-to-supplier1

2. Add the replication agreement to the new instance by using the --init option:

   # dsconf <supplier1_instance_name> repl-agmt create --suffix "dc=example,dc=com" --host "supplier2.example.com" --port 389 --conn-protocol LDAP --bind-dn "cn=replication manager,cn=config" --bind-passwd "<password>" --bind-method SIMPLE --init example-agreement-supplier1-to-supplier2

Verification

1. Display the agreement status:

   # dsconf <supplier2_instance_name> repl-agmt init-status --suffix "dc=example,dc=com" example-agreement-supplier2-to-supplier1

   Agreement successfully initialized.

2. Display the replication status:

   # dsconf <supplier2_instance_name> repl-agmt status --suffix "dc=example,dc=com" example-agreement-supplier2-to-supplier1

   Status For Agreement: ""example-agreement-supplier2-to-supplier1 (supplier1.example.com:389)
   Replica Enabled: on
   Update In Progress: FALSE
   Last Update Start: 20210331073540Z
   Last Update End: 20210331073540Z
   Number Of Changes Sent: 7:1/0
   Number Of Changes Skipped: None
   Last Update Status: Error (0) Replica acquired successfully: Incremental update succeeded
   Last Init Start: 20210331073535Z
   Last Init End: 20210331073539Z
   Last Init Status: Error (0) Total update succeeded
   Reap Active: 0
   Replication Status: Not in Synchronization: supplier (60642649000000070000) consumer (Unavailable) State (green) Reason (error (0) replica acquired successfully: incremental update succeeded)
   Replication Lag Time: Unavailable

   Verify the Replication Status and Last Update Status fields.