Deployment Example 1: Access Manager 7.1 Load Balancing, Distributed Authentication UI, and Session Failover

5.2 Enabling Multi-Master Replication of the User Data Instances

This section contains the instructions to enable multi-master replication (MMR) between two directory masters. This includes creating replication agreements between the masters and initializing the second directory master with the data and schema from the first directory master. The previously created am-users instances will serve as the two masters. An illustration of the architecture can be seen in Figure 4–1.

Use the following list of procedures as a checklist for completing the tasks.

To Enable Multi-Master Replication for User Data Instance on Directory Server 1

As a root user, log in to the DirectoryServer–1 host machine.

(Optional) Run dsconf list-suffixes to verify that the instance is not already enabled for replication.

# cd /var/opt/mps/serverroot/ds6/bin
# ./dsconf list-suffixes -p 1489 -v
Enter "cn=Directory Manager" password: d1rm4n4ger
...
dc=company,dc=com 	1		not-replicated		N/A		N/A		29
The "list-suffixes" operation succeeded on "DirectoryServer-1.example.com:1489"

The base suffix of the instance is not-replicated as displayed in the resulting list.

Run dsconf enable-repl to enable replication.

# ./dsconf enable-repl -h DirectoryServer-1.example.com 
  -p 1489 -d 11 master dc=company,dc=com
Enter "cn=Directory Manager" password: d1rm4n4ger
Use "dsconf create-repl-agmt" to create replication agreements on
"dc=company,dc=com".

The -d option takes as input a randomly chosen identifier to represent the Directory Server 1 configuration data instance; in this case, 11. master indicates that the instance is a master and not a replica. The base suffix is specified as dc=company,dc=com.

Run dsconf list-suffixes again to verify that the instance is now enabled for replication.

# ./dsconf list-suffixes -p 1489 -v
Enter "cn=Directory Manager" password: d1rm4n4ger
...
dc=company,dc=com 	1		master(11)		N/A		N/A		29
The "list-suffixes" operation succeeded on 
"DirectoryServer-1.example.com:1489"

The base suffix of the instance is master(11) as displayed in the resulting list, indicating that the master was successfully enabled.

Log out of the DirectoryServer–1 host machine.

To Enable Multi-Master Replication for User Data Instance on Directory Server 2

As a root user, log in to the DirectoryServer–2 host machine.

(Optional) Run dsconf list-suffixes to verify that the instance is not already enabled for replication.

# cd /var/opt/mps/serverroot/ds6/bin
# ./dsconf list-suffixes -p 1489 -v
Enter "cn=Directory Manager" password: d1rm4n4ger
...
dc=company,dc=com 	1		not-replicated		N/A		N/A		29
The "list-suffixes" operation succeeded on "DirectoryServer-2.example.com:1489"

The base suffix of the instance is not-replicated as displayed in the resulting list.

Run dsconf enable-repl to enable replication.

# ./dsconf enable-repl -h DirectoryServer-2.example.com 
  -p 1489 -d 22 master dc=company,dc=com
Enter "cn=Directory Manager" password: d1rm4n4ger
Use "dsconf create-repl-agmt" to create replication agreements on
"dc=company,dc=com".

The -d option takes as input a randomly chosen identifier to represent the Directory Server 1 configuration data instance; in this case, 22. master indicates that the instance is a master and not a replica. The base suffix is specified as dc=company,dc=com.

Run dsconf list-suffixes again to verify that the instance is now enabled for replication.

# ./dsconf list-suffixes -p 1489 -v
Enter "cn=Directory Manager" password: d1rm4n4ger
...
dc=company,dc=com 	1		master(22)		N/A		N/A		29
The "list-suffixes" operation succeeded on "DirectoryServer-2.example.com:1489"

The base suffix of the instance is master(22) as displayed in the resulting list, indicating that the master was successfully enabled.

Log out of the DirectoryServer–2 host machine.

To Change the Default Replication Manager Passwords for Each User Data Instance

The replication manager is the user that suppliers use to bind to the consumer server when sending replication updates. (In MMR the consumer server refers to whichever master happens to be the consumer for that particular operation.) It is recommended by the Directory Server documentation to change the default password created during the process of enabling replication.

As a root user, log in to the DirectoryServer–1 host machine.

Create a temporary file that contains the new replication manager password.

This file is read once, and the password is stored for future use.
# cd /var/opt/mps/serverroot/ds6/bin # echo replm4n4ger > pwd.txt

Verify that the file was successfully created.
# cat pwd.txt replm4n4ger

Run dsconf set-server-prop to set the replication manager password using pwd.txt as input.

# ./dsconf set-server-prop -h DirectoryServer-1.example.com 
  -p 1489 def-repl-manager-pwd-file:pwd.txt
Enter "cn=Directory Manager" password: d1rm4n4ger

Remove the pwd.txt file.

Log out of the DirectoryServer–1 host machine.

As a root user, log in to the DirectoryServer–2 host machine.

Create a temporary file that contains the new replication manager password.

This file is read once, and the password is stored for future use.
# cd /var/opt/mps/serverroot/ds6/bin # echo replm4n4ger > pwd.txt

Verify that the file was successfully created.
# cat pwd.txt replm4n4ger

Run dsconf set-server-prop to set the replication manager password using pwd.txt as input.

# ./dsconf set-server-prop -h DirectoryServer-2.example.com 
  -p 1489 def-repl-manager-pwd-file:pwd.txt
Enter "cn=Directory Manager" password: d1rm4n4ger

Remove the pwd.txt file.

Log out of the DirectoryServer–2 host machine.

To Create Replication Agreements for Each User Data Instance

A replication agreement is a set of parameters on a supplier that controls how updates are sent to a given consumer. In this case, we are making the user data instances aware of each other.

As a root user, log in to the DirectoryServer–1 host machine.

Run dsconf create-repl-agmt to create the replication agreement.

# cd /var/opt/mps/serverroot/ds6/bin
# ./dsconf create-repl-agmt -h DirectoryServer-1.example.com 
  -p 1489 dc=company,dc=com DirectoryServer-2.example.com:1489
Enter "cn=Directory Manager" password: d1rm4n4ger

Use "dsconf init-repl-dest dc=company,dc=com DirectoryServer-2.example.com:1489" 
to start replication of "dc=company,dc=com" data.

Run dsconf list-repl-agmts to verify that the replication agreement was successfully created.
# ./dsconf list-repl-agmts -p 1489 Enter "cn=Directory Manager" password: d1rm4n4ger dc=company,dc=com DirectoryServer-2.example.com:1489
This response indicates that the Directory Server 1 base suffix will be replicated to Directory Server 2.

Log out of the DirectoryServer–1 host machine.

As a root user, log in to the DirectoryServer–2 host machine.

Run dsconf create-repl-agmt to create the replication agreement.

# cd /var/opt/mps/serverroot/ds6/bin
# ./dsconf create-repl-agmt -h DirectoryServer-2.example.com 
  -p 1489 dc=company,dc=com DirectoryServer-1.example.com:1489
Enter "cn=Directory Manager" password: d1rm4n4ger

Use "dsconf init-repl-dest dc=company,dc=com DirectoryServer-1.example.com:1489" 
to start replication of "dc=company,dc=com" data.

Run dsconf list-repl-agmts to verify that the replication agreement was successfully created.
# ./dsconf list-repl-agmts -p 1489 Enter "cn=Directory Manager" password: d1rm4n4ger dc=company,dc=com DirectoryServer-1.example.com:1489
This response indicates that the Directory Server 2 base suffix will be replicated to Directory Server 1.

Log out of the DirectoryServer–2 host machine.

To Initialize the User Data Instance Replication Agreements

In this procedure, initialize the user data instance on Directory Server 1. The previously created agreements will replicate the data to Directory Server 2.

Note –

Initialization is not required on both instances when configuring for MMR.

As a root user, log in to the DirectoryServer–1 host machine.

Run dsconf show-repl-agmt-status to verify that the replication agreements are not yet initialized.

# cd /var/opt/mps/serverroot/ds6/bin
# ./dsconf show-repl-agmt-status -h DirectoryServer-1.example.com 
  -p 1489 dc=company,dc=com DirectoryServer-2.example.com:1489
Enter "cn=Directory Manager" password: d1rm4n4ger

Configuration Status 		: OK
Authentication Status		: OK
Initialization Status		: NOT OK

Status:										: Dest. Not Initialized

Run dsconf init-repl-dest to initialize the replication agreements.

# ./dsconf init-repl-dest -h DirectoryServer-1.example.com 
  -p 1489 dc=company,dc=com DirectoryServer-2.example.com:1489
Enter "cn=Directory Manager" password: d1rm4n4ger

Sent 1 entries...
Sent 2 entries...
Completed initialization of "DirectoryServer-2.example.com:1489"; 
May 15, 2007 1:53:32 PM

Run dsconf show-repl-agmt-status again to verify that the replication agreements are now initialized.

# cd /var/opt/mps/serverroot/ds6/bin
# ./dsconf show-repl-agmt-status -h DirectoryServer-1.example.com 
  -p 1489 dc=company,dc=com DirectoryServer-2.example.com:1489
Enter "cn=Directory Manager" password: d1rm4n4ger
Configuration Status 		: OK
Authentication Status		: OK
Initialization Status		: OK

Status:										: Enabled
Last Update Date						: Jul 12, 2007 8:47:42 PM

Log out of the DirectoryServer–1 host machine.

To Verify that User Data Replication Works Properly

As a root user, log in to the DirectoryServer–1 host machine.

Run ldapmodify to create a new directory entry.

# ldapmodify -a -h DirectoryServer-1.example.com -p 1489 
  -D cn=admin,cn=Administrators,cn=config -w d1rm4n4ger

dn: ou=People,dc=company,dc=com
objectclass: top
objectclass: organizationalUnit
ou: People
description: Container for user entries

Hit ENTER to indicate end of input.

adding new entry ou=People,dc=company,dc=com

Hit Control C to terminate the command.

^C

This step creates a new organizational unit on Directory Server 1.

After the entry is created, as a root user, log in to the DirectoryServer–2 host machine.

Run ldapsearch on Directory Server 2 to verify that the directory entry was successfully replicated.

# ldapsearch -b "dc=company,dc=com" -p 1489 -D "cn=Directory Manager" 
  -w d1rm4n4ger "objectclass=organizationalUnit"

version: 1
dn: ou=People,dc=company,dc=com
objectClass: top
objectClass: organizationalUnit
ou: People
description Container for user entries

Now run ldapdelete on Directory Server 2 to delete the entry just created.

# ldapdelete -h DirectoryServer-2.example.com -p 1489 
  -D "cn=Directory Manager" -w d1rm4n4ger "ou=People,dc=company,dc=com"

As a root user on Directory Server 1, run ldapsearch to verify that the entry was deleted.
# ldapsearch -b "dc=company,dc=com" -p 1489 -D "cn=Directory Manager" -w d1rm4n4ger "objectclass=organizationalUnit"
If the delete was successfully replicated to Directory Server 1, the search will return no results.

Log out of the Directory Server host machines.