Novell Cluster Services can be configured either during or after OES 11 SP1 installation. In a cluster, Novell CIFS for OES 11 SP1, is available only in Active/passive mode, which means that CIFS software runs on all nodes in the cluster. When a server fails, the cluster volumes that were mounted on the failed server fail over to that other node. The following sections give details about using Novell CIFS in a cluster environment:
Before setting up Novell CIFS in a cluster environment, ensure that you meet the following prerequisites:
Novell Cluster Services installed on OES 11 SP1 servers
For information on installing Novell Cluster Services, see OES 11 SP1: Novell Cluster Services 2.1 for Linux Administration Guide.
For information on managing Novell Cluster Services, see OES 11 SP1: Novell Cluster Services 2.1 for Linux Administration Guide.
Novell CIFS is installed on all the nodes in the cluster to provide high availability
Follow the instructions in Section 4.1, Installing CIFS during the OES 11 SP1 Installation andSection 4.2, Installing CIFS after the OES 11 SP1 Installation.
Keep in mind the following considerations when you prepare to use CIFS in a cluster.
Novell CIFS is not cluster-aware and is not clustered by default. You must install and configure Novell CIFS on every node in the cluster where you plan to give users CIFS access to the shared cluster resource.
Novell CIFS runs on all nodes in the cluster at any given time.
Novell CIFS is started at boot time on each node in the cluster. A CIFS command is added to the load script and unload script for the shared cluster resource. This allows Novell CIFS to provide or not to provide access to the shared resource through Virtual server IP.
NOTE:In CIFS, all the nodes should have similar server configuration, such as contexts and authentication mode.
The following process indicates how CIFS is enabled and used in a cluster environment:
Creating Shared Pools: To access the shared resources in the cluster environment through the CIFS protocol, you create the shared pools either by using the NSSMU utility, the iManager tool or the Novell Linux Volume Manager utility.
For requirements and details about configuring shared NSS pools and volumes on Linux, see OES 11 SP1: Novell Cluster Services 2.1 for Linux Administration Guide.
Creating a Virtual Server: When you cluster-enable an NSS pool, an NCS:NCP Server object is created for the virtual server. This contains the virtual server IP address, the virtual server name, and a comment.
Creating a CIFS Virtual Server: When you cluster-enable an NSS pool and enable that pool for CIFS by selecting CIFS as an advertising protocol, a virtual CIFS server is added to eDirectory. This is the name the CIFS clients use to access the virtual server.
Configuring Monitor Script: Configure resource monitoring to let the cluster resource failover to the next node in the preferred nodes list.
“ When rcnovell-cifs monitor is invoked, it:
- returns the status of CIFS, if CIFS is already running
- starts a new instance of CIFS and returns status, if CIFS is not running (dead/etc.)"
Each time the monitor script detects that the CIFS service is down and starts the service, a message in the following format is logged in /var/log/messages file :
CIFS: Monitor routine, in novell-cifs init script, detected CIFS not running,starting CIFS
For details on Configuring a Monitor Script for the Shared NSS Pool, see OES 11 SP1: Novell Cluster Services 2.1 for Linux Administration Guide
IMPORTANT: Set the number ofpermitted to 0. This ensures that if the CIFS server crashes, cluster services will trigger an immediate failover of the resource.
Loading the CIFS Service: When you enable CIFS for a shared NSS pool and when Novell CIFS is started at system boot, the following line is automatically added to the cluster load script for the pool's cluster resource:
novcifs --add --vserver=virtualserverFDN --ip-addr=virtualserverip
For example, novcifs --add '--vserver=".cn=CL-POOL-SERVER.o=novell.t=VALTREE."' --ip-addr=10.10.10.10
This command is executed when the cluster resource is brought online on an active node. You can view the load script for a cluster resource by using the clusters plug-in for iManager. Do not manually modify the load script.
IMPORTANT:If the cluster resource goes comatose on the Linux server, there might be a timing issue for loading Novell CIFS. Add a sleep command before the novcifs -add command. For example:
sleep 5 exit_on_error novcifs --add ‑‑vserver=.CN=NCS1_P1_SERVER.O=novell.T=TREE-188. ‑‑ip-addr=10.10.10.205
Unloading the CIFS Service: When you CIFS-enable for a shared NSS pool, the following line is automatically added to the cluster unload script for the pool's cluster resource:
novcifs --remove --vserver=virtualserverFDN --ip-addr=virtualserverip
For example, novcifs --remove '--vserver=".cn=CL-POOL-SERVER.o=novell.t=VALTREE."' --ip-addr=10.10.10.10
This command is executed when the cluster resource is taken offline on a node. The virtual server is no longer bound to the Novell CIFS service on that node. You can view the unload script for a cluster resource by using the clusters plug-in for iManager. Do not manually modify the unload script.
CIFS Attributes for the Virtual Server: When you CIFS-enable a shared NSS pool, the following CIFS attributes are added to the NCS:NCP Server object for the virtual server:
nfapCIFSServerName (read access)
nfapCIFSAttach (read access)
nfapCIFSComment (read access)
The CIFS virtual server uses these attributes. The CIFS server proxy user must have default ACL access rights to these attributes, access rights to the virtual server, and be in the same context as the CIFS virtual server.
NOTE:If the CIFS server proxy user is in a different context, the cluster administrator should give access to these virtual server attributes for the proxy user.