5.1 Installation/Upgrade/Migration Caveats

IMPORTANT:As support packs are released, there are sometimes new caveats identified. Be sure to always check the OES Readme for items specific to each support pack.

This section discusses the following installation/migration caveats:

5.1.1 Adding a Linux Node to NetWare Cluster

After you add a Linux node to a cluster, you cannot add more NetWare® nodes. For more information, see Converting a NetWare Cluster to Linux in the OES Novell Cluster Services 1.8.2 Administration Guide for Linux .

5.1.2 Cluster Upgrades Must Be Planned Before Installing OES

The only cluster-enabled service that can fail over cross-platform (run on either OES Linux or OES NetWare) is cluster-enabled NSS pools. All other services (iPrint, iFolder, etc.) can only fail over between servers that are the same platform. For example, an iPrint service that is running on an OES Linux server can fail over to another OES Linux server in the cluster, but the service cannot fail over to an OES NetWare server.

5.1.3 Direct Migration of Some File Services from NetWare to Linux Not Provided

Direct migration of CIFS, AFP, and FTP services is not provided in OES. You must carefully plan the manual migration of services prior to installing OES.

For example, if you plan to replace CIFS (Windows) file services on a NetWare server with OES Samba running on OES Linux, you need to plan to have the Samba service in place before shutting down the current CIFS service. For more information on implementing Samba, see the Samba Administration Guide for OES Linux SP2 .

5.1.4 Follow the Instructions for Your Chosen Platforms

Although installing OES services on Linux or NetWare is a straightforward process, the installation processes are platform-specific, requiring different sets of media and different installation programs.

Use the links in the following sections to access instructions for installing OES on your chosen platforms.

5.1.5 iFolder 3. x Considerations

For best results, be sure you read and carefully follow the instructions in the Novell iFolder 3.x Administration Guide , starting with Enterprise Server . This is especially critical if you plan to use NSS for your iFolder 3. x data volume.

5.1.6 Installing into an Existing eDirectory Tree

Novell Support has reported a significant number of installation incidents related to eDirectory™ health and time synchronization. To avoid such problems, do the following prior to installing OES:

Consider Coexistence and Migration Issues

If you are installing a new OES server into an existing eDirectory tree, be sure to read and follow the instructions in Installing OES Servers into an Existing Tree in the OES Coexistence and Migration Guide .

Be Sure That eDirectory Is Healthy

Review and follow the guidelines in Keeping eDirectory Healthy in the Novell eDirectory 8.7.3 Administration Guide .

Be Sure That Network Time Is Synchronized

OES Linux and OES NetWare servers can receive network time from either an existing eDirectory server or from an NTP time source. The critical point is that the entire tree must be synchronized to the same time sources. For example, do not set your new OES server to receive time from an NTP source unless the whole tree is synchronized to the same NTP source.

For an in-depth explanation of OES time synchronization, see Section 31.0, Time Synchronization.

5.1.7 Installing a NetWare Server into an OES Linux Tree

If you have an eDirectory tree that was created on an OES Linux server, and you want to install an OES NetWare server into the tree, you must ensure that you have at least three OES Linux servers with replicas running in the tree prior to installing the NetWare server. Otherwise, the required license containers are not created in the tree and you cannot install a NetWare license.

5.1.8 NetWare 6.5 Servers Must Be Running SP3 or Later

If you are installing OES Linux servers into a tree containing NetWare 6.5 servers, be sure that the following servers have been updated to SP3 or later prior to installing OES Linux.:

  • SLP Directory Agents: If the SLP Directory Agents on your network are not running NetWare 6.5 SP3 or later, installing an OES Linux server into the tree can cause the DA servers to abend.

  • LDAP Servers: If the LDAP servers referenced in your installation are not running NetWare 6.5 SP3 or later, the servers might abend during a schema extension operation.

5.1.9 Novell Distributed Print Services Cannot Migrate to Linux

NDPS® clients are not supported on Linux. You must therefore migrate any NDPS clients to iPrint before you migrate your print services to OES Linux. For more information, see Migrating NDPS Printers to iPrint in the OES iPrint Administration Guide for NetWare .

5.1.10 NSS Features Not Implemented on OES Linux

The following features are not implemented in OES Linux:

For more details about NSS compatibility, see Compatibility Issues for Using NSS Cross-Platform in the Novell Storage Services File System Administration Guide for OES .

5.1.11 Base Context for Samba Users Field Must Usually Be Changed

When you install Samba services on OES Linux, the default value of the Base Context for Samba Users field is the eDirectory context where the server is installed. This causes problems with enabling users for Samba access if the users are not located in the same container as the server or in a sub-context of that container.

For more Samba information, see Samba Enabling Problems and the Base Context for Samba Users Field the Samba Administration Guide for OES Linux SP2 .