
Chapter 6. Migrating from Previous Versions
84
nsslapd-plugin-depends-on-type: database
nsslapd-pluginId: Distributed Numeric Assignment
nsslapd-pluginVersion: 8.1.0
nsslapd-pluginVendor: Red Hat, Inc.
nsslapd-pluginDescription: Distributed Numeric Assignment plugin
adding new entry cn=Distributed Numeric Assignment Plugin,cn=plugins,cn=config
dn: cn=MemberOf Plugin,cn=plugins,cn=config
objectClass: top
objectClass: nsSlapdPlugin
objectClass: extensibleObject
cn: MemberOf Plugin
nsslapd-pluginPath: libmemberof-plugin
nsslapd-pluginInitfunc: memberof_postop_init
nsslapd-pluginType: postoperation
nsslapd-pluginEnabled: off
nsslapd-plugin-depends-on-type: database
memberofgroupattr: member
memberofattr: memberOf
nsslapd-pluginId: memberof
nsslapd-pluginVersion: 8.1.0
nsslapd-pluginVendor: Red Hat, Inc.
nsslapd-pluginDescription: memberof plugin
adding new entry cn=MemberOf Plugin,cn=plugins,cn=config
Hit
Enter
twice or type
Ctrl-D
to close the
ldapmodify
operation.
NOTE
If you edit the
dse.ldif
file directly, you need to stop the server first.
8. Restart the Directory Server. You must always restart the Directory Server after editing the plug-in
configuration.
service dirsrv restart
The process for upgrading servers in replication is the same as for a single server, but the order in
which the Directory Server instances is important to keep from interrupting replication. First upgrade all
supplier servers, then all hubs, and then all consumers.
•
Always
stop directory writes to the master or hub server before beginning the upgrade process.
• After upgrading all of the supplier servers, then upgrade all of the hubs and, last, all of the consumer
replicas.
• Then, after the Directory Server instances is upgraded, test replication to make sure it is working
correctly.
• A supplier, hub, or consumer can be migrated to a different or platform as described in
Section 6.3.2, “Migrating an 8.0 Directory Server to 8.1 on Another Machine”
.