In these scenarios, a NetWare-based tree exists and the task at hand is to introduce a new OES server into that tree. No existing servers are to be replaced.
If you have an eDirectory tree that already contains at least one NetWare 6.5 server, most of the preparatory tasks necessary for OES NetWare have already been completed.
Depending on the eDirectory version in the existng tree, you might need to apply some updates and schema extensions to prepare the tree for the version of eDirectory 8.7.3 that comes with OES. See Section 2.2.1, Directory Services for more information.
Installing a new OES SP2 NetWare server into the tree is the same as installing a new NetWare 6.5 SP5 server. See NetWare 6.5 Installation Program for OES NetWare Servers for more information.
For detailed installation instructions, see Installing
OES NetWare
in the OES NetWare Installation
Guide.
If you have an eDirectory tree that already contains at least one NetWare 6.5 server, most of the preparatory tasks necessary for OES Linux have already been completed.
Depending on the eDirectory version in the existing tree, you might need to apply some updates and schema extensions to prepare the tree for the version of eDirectory 8.7.3 that comes with OES. See Section 2.2.1, Directory Services for more information.
HINT:To help ensure a successful OES Linux installation into an
existing NetWare tree, Novell recommends that you apply the eDirectory
core schema and OES product extensions, and then allow the schema
to synchronize throughout the tree before installing the first OES
Linux server. In OES SP2, you can do this by running the Prepare
for New eDirectory and Schema Update tasks in the Novell Deployment
Manager utility. For more information, see Prepare
the Network with Deployment Manager
in the OES
for NetWare Installation Guide.
The OES for Linux installation procedure installs both SUSE® LINUX Enterprise Server 9 (SLES 9) with Support Pack 2 and OES components at the same time. See YaST Installation Program for OES Linux Servers for more information.
For detailed installation instructions, see Installing
Open Enterprise Server (OES) Linux
in the OES
for Linux Installation Guide.
If you have a NetWare 5.1 tree with NDS® 7 or 8, follow these steps to install the first OES NetWare or OES Linux server into the tree.
Keep in mind that Novell recommends upgrading to eDirectory 8.7.3 as a long-term OES deployment strategy. Compatibility of OES with earlier versions of eDirectory and NDS is provided as an interim solution only.
Ensure that all NetWare 5.1 servers have Support Pack 8 applied.
You can download NetWare Support Packs from the Novell Downloads page.
Using Novell Deployment Manager, complete the Search Tree for eDirectory/NDS Versions task which updates NDS on the NetWare 5.l servers to version 7.62c or 8.85c.
In Deployment Manager, complete the Prepare for New eDirectory task to extend the core schema for compatibility with eDirectory 8.7.3.
Install OES NetWare servers as outlined
in Installing
OES NetWare
in the OES for NetWare Installation
Guide.
Install OES Linux servers as outlined
in Installing
Open Enterprise Server (OES) Linux
in the OES
for Linux Installation Guide, paying particular attention
to the following:
See SLP Coexistence and Migration Issues for more information about SLP DA synchronization in OES.
Although the NetWare 5.1 Timesync NLM™ program is not fully NTPv3 compatible, it can provide NTP time to OES Linux NTP-based servers. The only difference noticed in Novell's testing is that it takes longer for time to synchronize when using timesync.nlm.
After the OES Linux server installation is complete, you can reconfigure all servers to obtain time from the Linux NTPv3 time source. See Section 2.2.6, Time Synchronization for more information.
Do not change the LDAP address to the IP address of a NetWare 5.1 server. The version of NDS in NetWare 5.l contains a pre-eDirectory LDAP implementation that does not understand all of the LDAP calls the OES components make.
To upgrade your NetWare 5.1 servers to OES NetWare, see Section 3.3, Upgrading or Migrating Existing Servers to OES.
If you have a NetWare 4.11 or 4.2 tree with NDS 6, follow these steps to install the first OES NetWare server into the tree.
An OES NetWare server must be installed first to prepare the tree and provide IPX™ communication with the NetWare 4 servers. After the network is sufficiently updated to support OES NetWare and TCP/IP communication, you can install OES Linux servers.
WARNING:NetWare 4.10 is not supported in a mixed environment with OES NetWare. Any NetWare 4.10 servers should be either upgraded or removed from the tree before you start installing OES servers.
Keep in mind that Novell recommends upgrading to eDirectory 8.7.3 as a long-term OES deployment strategy. Compatibility of OES with earlier versions of eDirectory and NDS is provided as an interim solution only.
Ensure that all NetWare 4.11 servers have Support Pack 9 applied.
You can download NetWare Support Packs from the Novell Downloads page.
Make sure the Novell Client™ software on the Windows workstation you use to run Novell Deployment Manager is configured to support IPX.
IPX support is not installed by default in the Novell Client.
Using the Novell Deployment Manager, complete the Search for NDS/eDirectory Versions task and update NDS on the NetWare 4 servers to version 6.21.
To verify the NDS version, enter modules ds.nlm at the server console.
In Deployment Manager, complete the Prepare for New eDirectory task to extend the core schema for compatibility with eDirectory 8.7.3.
In Deployment Manager, complete the Generate GUIDs on NetWare 4 Servers task.
On the NetWare 4 server holding the Master replica of the [Root] partition, run DSRepair > Advanced Options > Global Schema Operations > Post NetWare 5 Schema Update, and then run Local DSRepair > Rebuild Operational Schema.
Install the first OES NetWare server
as outlined in Installing
OES NetWare
in the OES for NetWare Installation
Guide.
Be sure to enable IPX during the server installation.
Install OES Linux servers as outlined
in Installing
Open Enterprise Server (OES) Linux
in the OES
for Linux Installation Guide.
Because there is no support for IPX or IPX compatilibty mode (SCMD) on Linux, the OES Linux servers cannot communicate with any of the NetWare 4 servers.
After this OES coexistence configuration is in place, you should plan to migrate your NetWare 4 servers to OES NetWare as quickly as possible. You have the following options for NetWare 4 servers:
For instructions on running Migration Wizard, see the Novell Server Consolidation and Migration Toolkit Administration Guide.
Verify that users can access the migrated data on your new OES NetWare servers, then remove the NetWare 4 source servers from the tree.
For instructions on running the Server Consolidation Utility, see the Novell Server Consolidation and Migration Toolkit Administration Guide.
Down-server upgrades are no longer officially supported by Novell. However, in certain situations, customers can work with Novell Technical ServicesSM staff to complete a down-server upgrade. Contact Novell Technical Services for assistance.
After all of your NetWare 4 servers have been removed from the tree, support for IPX is no longer needed on the OES NetWare servers. Remove the IPX modules and bindings from the autoexec.ncf files or disable the IPX bindings using the inetcfg utility.
If your OES network uses NTPv3 for time synchronization, convert the time synchronization method on your upgraded NetWare servers from timesync.nlm to NTPv3. See Section 2.2.6, Time Synchronization for more information.