Cross-Protocol File Locking Has Changed; Do Not Create Local (Posix) Users - Novell OPEN ENTERPRISE SERVER - PLANNING AND IMPLEMENTATION GUIDE 12-2010 Implementation Manual

Service Failover in a Mixed Cluster
The only cluster-enabled service that can fail over cross-platform (run on either OES 2 or NetWare
6.5 SP8) 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
2 server can fail over to another OES 2 server in the cluster, but the service cannot fail over to an
NetWare 6.5 SP8 server.
Working with Mixed Node Clusters
The following points apply to working with mixed NetWare and OES clusters:

You cannot uses EVMSGUI to create a Linux POSIX file system as a cluster resource until the
entire cluster is migrated to Linux.

You cannot migrate or fail over a Linux POSIX file system cluster resource to a NetWare
cluster node.

Only NSS pool cluster resources that are created on a NetWare cluster node can be failed over
between Linux and NetWare nodes.

NetWare NSS to Linux NSS failover requires that the Linux node be configured for NSS and
that the version of NSS supports the NSS media format and features being used by the NSS
pool cluster resource.

The new NSS media format in OES 2 is not available for OES 1 SP2 Linux and earlier. After a
volume has been upgraded to the new media format, you cannot fail it over to a node that is
running OES 1 SP2 Linux or earlier.

3.9.6 Cross-Protocol File Locking Has Changed

If you plan to use Novell CIFS, Novell AFP and/or NCP file services in combination with each
other, be sure to read

3.9.7 Do Not Create Local (POSIX) Users

During the OES 2 install you are prompted by the SLES portion of the install to create at least one
user besides
Creating local users is not recommended on OES 2 servers because user management in OES 2 is
managed entirely in eDirectory. The only local user you need on the server is the
other local users can, in fact, cause unnecessary confusion and result in service-access problems that
are difficult to troubleshoot.
eDirectory users are enabled for POSIX access through the Linux User Management (LUM)
technology installed by default on every OES 2 server.
Also be aware that not all OES services require that users are LUM-enabled. Novell Client users, for
example, can access NCP and NSS volumes on OES 2 servers just as they do on NetWare without
any additional configuration.
For more information about this topic, see
for eDirectory Users," on page
36 OES 2 SP3: Planning and Implementation Guide
Section 1.3.5, "Cross-Protocol File Locking Change," on page
and you are warned if you bypass the prompt.
root
147.
Section 15.2, "Linux User Management: Access to Linux
18.
user. Creating
root