This section lists the important requirements that must be verified before attempting eDirectory migration.
The target server must run OES 2 and should have the eDirectory 8.8 SP6 RPMs already installed.
If the target OES 2 server has a default eDirectory 8.8 SP6 instance already configured, thisinstance should be active. This instance will be overwritten after the migration.
OES 2 does not support multiple instances of eDirectory on the same server, so any non-default instances should not be running during migration.
The source NetWare server should be running and should not be part of any partition operation. For more information on supported source NetWare server versions, refer to eDirectory Coexistence and Migration.
The eDirectory migration utility will run only on the target server and must be able to access the NetWare server remotely.
The eDirectory migration utility is designed to run on the Linux version of OES 2, which is the target platform for migration. The following table lists the compatible eDirectory versions at source and the corresponding target servers:
Table 9-1 eDirectory Versions at Source and Target Servers
IP address and DNS migrations are not performed by this migration utility.
Only the eDirectory instance will be migrated. Applications depending on eDirectory will not be migrated.
You should not use this migration methodology if you want both the servers to be available during the migration operation.
NOTE:Only the target server will be available after the migration.The source server will be locked. Other service migrations cannot be performed after completing eDirectory migration.