Adding A Linux Node To A Cluster Ends Adding More Netware Nodes; Afp File Locking Requires Samba; Always Double-Check Service Configurations Before Installing; Back Button Doesn't Reset Configuration Settings - Novell OPEN ENTERPRISE SERVER 2 SP2 - PLANING AND IMPLEMENTATION GUIDE 11-10-2009 Implementation Manual

3.9.1 Adding a Linux Node to a Cluster Ends Adding More
NetWare Nodes
After you add a Linux node to a cluster, you cannot add more NetWare nodes. For more information,
see "Converting NetWare 6.5 Clusters to OES 2 Linux" in the OES 2 SP2: Novell Cluster Services
1.8.7 for Linux Administration Guide.

3.9.2 AFP File Locking Requires Samba

Cross-protocol file locking between AFP and NCP connections on an OES 2 server requires that you
install Samba on the server, even though Samba file services cannot be run concurrently with AFP
on the same server. (See "Novell AFP" on page 46.) For more information, see the OES 2 SP2:
Novell AFP For Linux Administration Guide
3.9.3 Always Double-Check Service Configurations Before
Installing
It is critical and you double-check your service configurations on the Novell Open Enterprise Server
Configuration summary page before proceeding with an installation. Two reasons for this are
explained in Section 3.9.4, "Back Button Doesn't Reset Configuration Settings," on page 37 and

3.9.4 Back Button Doesn't Reset Configuration Settings

During an installation, after you configure eDirectory and reach the Novell Open Enterprise Server
Configuration summary screen, service configuration settings have been "seeded" from the
eDirectory configuration.
If you discover at that point that something in the eDirectory configuration needs to change, you can
change the settings by clicking the eDirectory link on the summary page or by clicking the Back
button.
In both cases when you return to the summary page, the eDirectory configuration has changed, but
the individual service configurations have the same eDirectory settings you originally entered.
These must each be changed manually.
For example, if you specified the wrong server context while initially configuring eDirectory, the
NSS and LUM configurations still have the wrong context. You must select each service
individually and change the server context in them.
Unless you manually change the services affected by changes to eDirectory, your services will at
best not work as expected and at worst completely fail.
Planning Your OES 2 Implementation 37