This deployment example shows the installation of a single Edge complex. However, several complexes are meant to be deployed geographically, and directory information must be shared among them through replication. Each site has a master and two consumer replicas. The master at each site is configured in multi-master replication with the other site masters. The following table shows the Directory Server instances at each site, their type and the unique replica ID chosen for each.
Directory Server Host |
Replica Type |
Value of nsDS5ReplicaId |
---|---|---|
ds-amer-01 |
USR master |
100 |
ds-amer-02 |
USR replica 2 |
200 |
ds-amer-03 |
USR replica 3 |
300 |
ds-euro-01 |
USR master |
101 |
ds-euro-02 |
USR replica 2 |
201 |
ds-euro-03 |
USR replica 3 |
301 |
ds-asia-01 |
USR master |
102 |
ds-asia-02 |
USR replica 2 |
202 |
ds-asia-03 |
USR replica 3 |
302 |
ds-soam-01 |
USR master |
103 |
ds-soam-02 |
USR replica 2 |
203 |
ds-soam-03 |
USR replica 3 |
303 |
Obtain the setup-mmr.ldif and setup-replica.ldif files from your Sun representative. Edit these files to contain the correct host names and replica ID values for your Edge complex.
Set up multi-master replication on the servers designated -01 only. Edit the setup file to contain the suffix name each time prior to running the command:
o=NetscapeRoot
dc=example,dc=com
o=pab
o=PiServerDb
Run the setup command once for each suffix in the directory:
phys-bedge1-2# vi setup-mmr.ldif phys-bedge1-2# ./setup-mmr.ldif |
Set up the consumer replicas on the servers designated -02 and -03. Run the following commands once for each suffix of the same suffixes listed in the previous step. Edit the setup file to contain the suffix name each time prior to running the command:
phys-bedge[23]-2# vi setup-replica.ldif phys-bedge[23]-2# ./setup-replica.ldif |