38 OES 2 SP2: Planning and Implementation Guidenovdocx (en) 22 June 20093.9.5 Cluster Upgrades Must Be Planned Before Installing OES2Because of differences between Novell Cluster Services on NetWare 6.5 SP8 and OES 2, there areimportant issues to consider before combining them into a mixed node cluster, as explained in thefollowing sections. “Service Failover in a Mixed Cluster” on page 38 “Working with Mixed Node Clusters” on page 38Service Failover in a Mixed ClusterThe only cluster-enabled service that can fail over cross-platform (run on either OES 2 or NetWare6.5 SP8) is cluster-enabled NSS pools. All other services (iPrint, iFolder, etc.) can only fail overbetween servers that are the same platform. For example, an iPrint service that is running on an OES2 server can fail over to another OES 2 server in the cluster, but the service cannot fail over to anNetWare 6.5 SP8 server.Working with Mixed Node ClustersThe 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 theentire cluster is migrated to Linux. You cannot migrate or fail over a Linux POSIX file system cluster resource to a NetWarecluster node. Only NSS pool cluster resources that are created on a NetWare cluster node can be failed overbetween Linux and NetWare nodes. NetWare NSS to Linux NSS failover requires that the Linux node be configured for NSS andthat the version of NSS supports the NSS media format and features being used by the NSSpool cluster resource. The new NSS media format in OES 2 is not available for OES 1 SP2 Linux and earlier. After avolume has been upgraded to the new media format, you cannot fail it over to a node that isrunning OES 1 SP2 Linux or earlier.3.9.6 Do Not Create Local (POSIX) UsersDuring the OES 2 install you are prompted by the SLES portion of the install to create at least oneuser besides root and you are warned if you bypass the prompt.Creating local users is not recommended on OES 2 servers because user management in OES 2 ismanaged entirely in eDirectory. The only local user you need on the server is the root user. Creatingother local users can, in fact, cause unnecessary confusion and result in service-access problems thatare 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, forexample, can access NCP and NSS volumes on OES 2 servers just as they do on NetWare withoutany additional configuration.
