Index: trunk/server/doc/install-ldap
===================================================================
--- trunk/server/doc/install-ldap	(revision 1818)
+++ trunk/server/doc/install-ldap	(revision 1983)
@@ -162,5 +162,5 @@
             M1 <---> M2 <---> S
 
-    3. Set up the rest of the replication agreements at your leisure.
+    3. Set up the rest of the replication agreements.
 
                 M1 <---> M2
@@ -169,5 +169,20 @@
                 +--> S <--+
 
+    4. Push a change from every existing server (to the new server), and
+       then a change from the new server to (all) the existing servers.
+       In addition to merely testing that replication works, this will
+       set up the servers' changelogs properly.
+
+       Until this step is complete, no changes (other than the replica
+       refresh, to initially populate the new server) should be sent, or
+       you risk the cluster's replication agreements falling apart.
+       Possibly disabling Pony for the duration of this setup is a good
+       plan.
+
   Here's how you do it.
+
+    0. Disable Pony (we don't have a particularly good way of doing
+       this at the moment), and tell -c scripts you're doing this and
+       not to go off and make changes to the database until you're done.
 
     1. Pull open the replication part of the database. It's fairly empty
@@ -286,4 +301,22 @@
     then try again.
 
+    7. Repeat step 6 to complete the graph of replications (i.e., from
+    every other server to the new server, and from the new server to
+    every other server).
+
+    Note the only difference between steps 5 and 6 is the lack of
+    nsDS5ReplicaRefresh: start. That only needs to be done once, to the
+    new server.
+
+    8. If at this point you look at the new server's changelog with
+    cl-dump (preferably /mit/scripts/admin/cl-dump.pl, to not prompt you
+    for a password), you won't see the servers you added in step 7. So,
+    from each of those servers, make a change to some record so it gets
+    propagated to the new server, and then one from the new server so it
+    gets propagated to all the existing servers' changelogs. This is
+    also good for making sure the replication agreements actually work.
+
+    9. Re-enable Pony and celebrate on -c scripts.
+
 Troubleshooting
 ===============