Make sure your system satisfies the required software and configuration settings that are specified in this section.
NCP Server for Linux supports OES 2 Linux and later.
The NetWare Core Protocol (NCP) Server for Linux provides the NCP services for NSS volumes on Linux and for NCP volumes on Linux POSIX file systems. Dynamic Storage Technology (DST) is a component of NCP Server. Using DST is optional, but NCP Server must be installed and running in order for DST to work.
For information about managing Dynamic Storage Technology, see the OES 2 SP3: Dynamic Storage Technology Administration Guide.
During the OES 2 Linux install, you assign a static IP address (IPv4 or IPv6), a hostname, and domain name to the server. NCP Server uses the server hostname (such as server1) as the NCP File Server Name, and generally considers that the hostname never changes. If you modify the hostname after the install, you must also modify the NCP File Server Name parameter. For information, see Section 3.12, Modifying the NCP File Server Name.
IMPORTANT:Modifying the IP address or hostname for an existing server impacts most services, not just NCP Server.
Selecting NCP Server as part of a 64-bit installation automatically installs 64-bit NCP server.
NCP Server manages data access for NCP volumes, Dynamic Storage Technology (DST) shadow volumes, and Novell Storage Services (NSS) volumes. NCP Server restricts data access to users who have User objects defined in Novell eDirectory. For information about configuring eDirectory and users, see the Novell eDirectory 8.8 Administration Guide.
IMPORTANT:The server’s root user is the only local user who can access data without authenticating in eDirectory.
A container administrator (or non-administrator user) needs the following eDirectory rights to install and manage the NCP and Dynamic Storage Technology service on an OES 2 SP3 Linux server:
Object Create right on the container where the NCP Server objects are.
Object Create right where the cluster container will be.
A container administrator (or non-administrator user) needs the following eDirectory rights to manage an NCP volume on an OES 2 SP3 Linux server:
Object Write and Modify rights on the Volume object.
For example, to create an NCP volume NCPVOL1 in the container sales.mycompany.com, the administrator must have Create right on the Container object sales and the Write and Modify rights on the Volume object NCPVOL1.
The container administrator must be Linux-enabled with Linux User Management (LUM) and be added to the LUM admingroup for the server.
NOTE:If the eDirectory administrator username or password contains special characters (such as $, #, and so on), make sure to escape each special character by preceding it with a backslash (\) when you enter credentials.
Novell Storage Services (NSS) requires NCP Server; however, NSS is not required for using NCP Server with NCP volumes on Linux file systems.
In its initial release, Dynamic Storage Technology supports only NSS volumes being used as shadow volumes. If you plan to use DST, you need to install NSS when you install NCP Server and Dynamic Storage Technology.
For information about installing NSS, see Installing and Configuring Novell Storage Services
in the OES 2 SP3: NSS File System Administration Guide for Linux.
You can install and configure Novell Samba to provide file access for CIFS/Samba users to NCP volumes. For information about configuring Samba services, see the OES2 SP3: Samba Administration Guide.
If both NCP users and Samba/CIFS users access the same NCP volume or NSS volume, you should enable cross-protocol file locking for NCP. For information, see Section 3.11, Configuring Cross-Protocol File Locks for NCP Server.
NCP uses the sambasharemodes.so library file to support the cross-protocol file locking capability that coordinates access to files by NCP users and CIFS/Samba users. NCP updates that are released through the OES 2 Linux and later update channels and in support packs include the sambasharemodes.so library file that you need for NCP. Patches for Linux Samba are also released separately through the SUSE Linux Enterprise Server 10 SP1 and later update channels. For 32-bit OES 2 Linux and later, it is okay to accept Samba updates separately. However, for 64-bit OES 2 Linux and later, there is a risk of breaking the cross-protocol locks functionality if the sambasharemodes.so library file is modified from the version released with NCP.
Users must be Linux-enabled with Linux User Management in order to access data via CIFS/Samba protocols. Linux User Management is selected and installed automatically when you install NCP Server and Dynamic Storage Technology. For information about Linux-enabling users with Linux User Management, see the OES 2 SP3: Novell Linux User Management Administration Guide.
Cross-protocol file locking is supported for the Novell Apple Filing Protocol (AFP) service that provides AFP access for Macintosh users to NSS volumes. This allows NCP users and AFP users to access files on an NSS volume and prevents them from concurrently modifying files by locking the file across protocols. It requires the following setup:
NCP Server for Linux is installed and running.
NSS for Linux is installed and running.
Novell AFP is installed and running.
Linux Samba is installed. It can be running or not running.
The NCP cross-protocol file locking attribute is enabled. For information, see Section 3.11, Configuring Cross-Protocol File Locks for NCP Server.
For information about installing and using Novell AFP for Linux, see the OES 2 SP3: Novell AFP For Linux Administration Guide.
NCP Server supports the sharing of NSS volumes on Linux, NCP volumes on Linux POSIX file systems, and DST shadow volumes in clusters with Novell Cluster Services for Linux. NCP Server itself is not clustered, and must be installed and configured on each OES 2 Linux node in the cluster where you plan to fail over these volumes.
For information about configuring NCP volumes in cluster resources, see Section 11.0, Configuring NCP Volumes with Novell Cluster Services.
For information about configuring DST shadow volumes in cluster resources, see Configuring DST Shadow Volumes with Novell Cluster Services for Linux
in the OES 2 SP3: Dynamic Storage Technology Administration Guide.
For information about configuring NSS volumes in cluster resources, see Configuring Cluster Resources for Shared NSS Pools and Volumes
in the OES 2 SP3: Novell Cluster Services 1.8.8 Administration Guide for Linux.
For information about installing and managing Novell Cluster Services for Linux, see OES 2 SP3: Novell Cluster Services 1.8.8 Administration Guide for Linux.
SLP (Service Location Protocol) is a required component for Novell Cluster Services on Linux when you are using NCP to access file systems on cluster resources. NCP requires SLP for the ncpcon bind and ncpcon unbind commands in the cluster load and unload scripts. For example, NCP is needed for NSS volumes and for NCP volumes on Linux POSIX file systems.
SLP is not automatically installed when you select Novell Cluster Services. SLP is installed as part of the Novell eDirectory configuration during the OES 2 Linux install. You can enable and configure SLP on the eDirectory Configuration - NTP & SLP page. For information, see Specifying SLP Configuration Options
in the OES 2 SP3: Installation Guide.
When the SLP daemon (slpd) is not installed and running on a cluster node, any cluster resource that contains the ncpcon bind command goes comatose when it is migrated or failed over to the node because the bind cannot be executed without SLP.
The SLP daemon (slpd) must also be installed and running on all nodes in the cluster when you manage the cluster or cluster resources.
NCP Server re-registers cluster resource virtual NCP servers with SLP based on the setting for the eDirectory advertise-life-time (n4u.nds.advertise-life-time) parameter. The parameter is set by default to 3600 seconds (1 hour) and has a valid range of 1 to 65535 seconds.
You can use the ndsconfig set command to set the n44.nds.advertise-life-time parameter. To reset the parameter in a cluster, perform the following tasks on each node of the cluster:
Log in to the node as the root user, then open a terminal console.
Take offline all of the cluster resources on the node, or cluster migrate them to a different server. At a command prompt, enter
cluster offline <resource_name> or cluster migrate <resource_name> <target_node_name>
Modify the eDirectory SLP advertising timer parameter (n4u.nds.advertise-life-time), then restart ndsd and slpd. At a command prompt, enter
ndsconfig set n4u.nds.advertise-life-time=<value_in_seconds>
rcndsd restart
rcslpd restart
Bring online all of the cluster resources on the node, or cluster migrate the previously migrated resources back to this node.
cluster online <resource_name> or cluster migrate <resource_name> <node_name>
Repeat the previous steps on the other nodes in the cluster.
OpenSLP stores the registration information in cache. You can configure the SLP Directory Agents to preserve a copy of the database when the SLP daemon (slpd) is stopped or restarted. This allows SLP to know about registrations immediately when it starts.
For more information about configuring and managing SLP, see Configuring OpenSLP for eDirectory
in the Novell eDirectory 8.8 SP7 Administration Guide.
Novell iManager 2.7 for Linux is required for managing eDirectory users, Samba services, Universal Password, Linux User Management, Novell Storage Services, and Novell Cluster Services for Linux. It is not necessary to install iManager on every server, but it must be installed somewhere on the network. For information about installing and using Novell iManager, see the Novell iManager 2.7 Installation Guide.
Novell Remote Manager for Linux is required for managing NCP Server services, NCP volumes, and Dynamic Storage Technology. It is installed by default when you install NCP Server and Dynamic Storage Technology.
For information about using Novell Remote Manager for Linux, see the OES 2 SP3: Novell Remote Manager for Linux Administration Guide. For information about management options for NCP Server, see Section 7.1.4, Quick Reference for the NCP Server Plug-In for Novell Remote Manager for Linux.
In OES 2 Linux, OpenWBEM is a PAM-enabled Linux utility that must be enabled and running on the OES 2 Linux server when managing services with Novell Remote Manager for Linux and Novell iManager. During the install, make sure you enable OpenWBEM (the default) when configuring Linux services. For information, see Services in OES 2 That Require LUM-Enabled Access
in the .OES 2 SP3: Planning and Implementation Guide
Make sure to install and configure additional OES 2 Linux services that might be required by each of the other services mentioned in this section. Refer to the individual guides for those services for information about how to install and manage them.