HP-UX Directory Server 8.1 administrator guide

nsds5ReplicaBindDN give the DN as which the supplier will bind to the hub to make
changes.
nsds5flags sets whether the replica writes to the changelog. For a hub, this value
must be 1.
The replica entry attributes are described in Table 8-2 “Replica attributes”. These attributes are
described in more detail in the HP-UX Directory Server configuration, command, and file reference.
8.7.4 Configuring replication agreements from the command line
When setting up replication agreements, first set them up between all suppliers, then between
the suppliers and the hubs, and last between the hub and the consumers.
The replication agreement has to define seven things:
The consumer host (nsds5replicahost) and port (nsds5replicaport).
The DN for the supplier to use to bind with the consumer (nsds5ReplicaBindDN), the
way that the supplier binds (nsds5replicabindmethod), and any credentials required
(nsds5replicabindcredentials).
The subtree being replicated (nsds5replicaroot).
The replication schedule (nsds5replicaupdateschedule).
Any attributes that will not be replicated (nsds5replicatedattributelist).
Use ldapmodify to add a replication agreement to every supplier for every consumer which it
will update. For example:
dn: cn=ExampleAgreement,cn=replica,cn="dc=example,dc=com",cn=mapping tree,cn=config
changetype: add
objectclass: top
objectclass: nsds5replicationagreement
cn: ExampleAgreement
nsds5replicahost: consumer1
nsds5replicaport: 389
nsds5ReplicaBindDN: cn=replication manager
nsds5replicabindmethod: SIMPLE
nsds5replicaroot: dc=example,dc=com
description: agreement between supplier1 and consumer1
nsds5replicaupdateschedule: 0000-0500 1
nsds5replicatedattributelist: (objectclass=*) $ EXCLUDE authorityRevocationList
nsds5replicacredentials: {DES}UXRbhvozeN9LWdueOEbPeQ==
nsds5BeginReplicaRefresh: start
The replication agreement attributes are listed in Table 8-3 “Replication agreement attributes”.
These attributes are described in more detail in the HP-UX Directory Server configuration, command,
and file reference.
After creating every replication agreement, begin initializing consumers.
Table 8-3 Replication agreement attributes
ValuesDescriptionObject class or attribute
Required object class for every entry.
objectclass: top
An operational object class that
contains the replication agreement
attributes.
objectclass:
nsds5replicationagreement
Any string.The naming attribute for the
replication agreement.
cn: agreement_name
Any host name. For example:
nsds5replicahost: consumer1
Gives the host name of the consumer
server; the host name can be the fully
qualified host and domain name. If
TLS/SSL is enabled, the fully-qualified
domain name is required.
nsds5replicahost: hostname
368 Managing replication