This section lists the important requirements that must be verified before attempting eDirectory migration.
The target server must run OES 2018 and should be installed with pre-migration service.
The eDirectory instance configured on the target server should be active. This instance will be overwritten after the migration.
The source NetWare server should be running and should not be part of any partition operation.
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 2018, which is the target platform for migration. The following table lists the compatible eDirectory versions at source and the corresponding target servers:
Table 12-1 eDirectory Versions at Source and Target Servers
|
Source Server |
Target Server |
|---|---|
|
NetWare 5.1 SP8 + eDirectory 8.7.3.6 |
Physical or Virtualized OES2018 Linux 64-bit |
|
NetWare 5.1 SP8 + eDirectory 8.7.3.7 |
Physical or Virtualized OES2018 Linux 64-bit |
|
NetWare 6.5 SP6 + eDirectory 8.7.3.9 |
Physical or Virtualized OES2018 Linux 64-bit |
|
NetWare 6.5 SP6 + eDirectory 8.8 |
Physical or Virtualized OES2018 Linux 64-bit |
|
NetWare 6.5 SP6 + eDirectory 8.8 SP1 |
Physical or Virtualized OES2018 Linux 64-bit |
|
NetWare 6.5 SP6 + eDirectory 8.8 SP3 |
Physical or Virtualized OES2018 Linux 64-bit |
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.