This section describes how to configure a Linux POSIX file system for clustering with OES Cluster Services for Linux, then how to set up a clustered NCP volume on the cluster resource. You can set up NCP volumes at the root of the cluster resource, or for subdirectories on it. You can create multiple NCP volumes on a Linux POSIX cluster resource. To provide NCP access to the share, you must create an NCS:NCP Server object and associate it with one or multiple NCP volumes, and bind the object to the IP address of the Linux POSIX cluster resource.
For prerequisites, see Section 11.1, Planning for NCP Volumes in a Cluster Environment.
IMPORTANT:NCP Server does not support cross-protocol locks across a cluster migration or failover of the resource. If a file is opened with multiple protocols when the migration or failover begins, the file should be closed and reopened after the migration or failover to acquire cross-protocol locks on the new node.
Section 11.2.1, Gathering Information for Clustering the NCP Volume
Section 11.2.2, Creating and Cluster-Enabling a Linux LVM Volume Group Clustered Resource
Section 11.2.3, Creating a Shared NCP Volume on the Linux POSIX Cluster Resource
Section 11.2.4, Configuring an LVM Cluster Resource with NSSMU
Section 11.2.5, Modifying the Load Script for the LVM Volume Group Cluster Resource
Section 11.2.6, Modifying the Unload Script for the LVM Volume Group Cluster Resource
Gather the information that you will use as you follow the steps to cluster an NCP volume.
IMPORTANT:On Linux, all names are case sensitive in the tools and cluster scripts.
|
Cluster Information |
Example |
Description |
|---|---|---|
|
RESOURCE_IP |
10.10.10.44 |
IP address of the Linux POSIX cluster resource. The cluster resource must have a unique static IP address that is in the same subnet as the IP addresses that are used for the cluster and cluster nodes. |
|
VOLGROUP_NAME |
myclustervg01 |
Name of the LVM volume group. The name must be one word, must consist of standard alphanumeric characters, and must not be any of the following reserved words:
|
|
MOUNT_DEV |
/dev/$VOLGROUP_NAME/volume_name |
The Linux path for the LVM volume. For example: /dev/$VOLGROUP_NAME/myclustervol01 |
|
MOUNT_FS |
ext3 |
The file system type you specify when you mount the volume. |
|
MOUNT_POINT |
/mnt/lxvol44 |
The mount location for the LVM volume. You can mount the LVM volume anywhere. It can have the same or different name than the underlying LVM volume. For example: /mnt/lxvol44 /mnt/users /home |
|
NCP_VOLUME |
USERS |
The name you give to the NCP volume. This is the share name seen by the users. |
|
NCP_mount_point |
/path_to_mount_point |
The NCP share mount point must be the same as that for the LVM volume (that is, at the root of the LVM volume), or it can be a subdirectory below that location. |
|
NCP_SERVER |
cluster1-lxvol44-server |
The virtual server object (NCS:NCP Server) name for the NCP volume. This example uses a naming convention based on the one used by NSS pool resources (clustername-poolname-server), but the Linux POSIX cluster resource name is used instead. clustername-resourcename-server |
|
LVM logical volume |
mycluster_lxvo44 |
Name of the LVM logical volume that you create on the volume group. |
The following procedure assumes that you are using a disk (or LUN) that does not contain data that you want to keep. You will initialize the disk and remove all segment managers.
WARNING:Initializing a disk destroys all data on it.
On the first OES node in the cluster, log in as the root user, then open a terminal console.
In NSSMU, initialize the disk that you want to use. Ensure that the device is not marked as shareable.
Create a Linux LVM volume group cluster resource as described in Requirements for Creating LVM Cluster Resources
in the OES 2018 SP3: OES Cluster Services for Linux Administration Guide.
Use the sample values that are provided in the Section 11.2.1, Gathering Information for Clustering the NCP Volume to do the following:
Create a clustered Linux LVM volume group.
Create a an LVM logical volume on the volume group.
Make a file system on the logical volume.
Create a cluster resource for the volume group by using the Generic_FS template for OES Cluster Services.
Create a Virtual Server object for the cluster resource.
Bring the LVM volume group cluster resource online.
After you have configured the Linux POSIX cluster resource, continue with Section 11.2.3, Creating a Shared NCP Volume on the Linux POSIX Cluster Resource.
After you create the NCP volume by using the procedure in this section, you must restart the NetIQ eDirectory (ndsd) daemon on this node. Stopping ndsd sends a notification that the server is down to NCP users of the local volumes and existing cluster volumes that are mounted on the server.
Two best practices for clusters should be observed:
Perform maintenance tasks during non-peak hours so that users are minimally affected.
When performing maintenance on a node, cluster migrate existing cluster resources to another node if you want the related users to be undisturbed.
If NCP users are connected to local or exiting cluster volumes on the node when you stop ndsd, they receive a "Server is down" notification from the NCP client.
When you start ndsd, NCP users of local volumes on the node are automatically reconnected and their sessions continue.
If you do not cluster migrate the existing cluster resources to another node, when you start ndsd, NCP users of existing cluster volumes on the node are not automatically reconnected because their cluster resources are no longer bound to NCP. You can offline the resources and then online the resources, or issue the ncpcon bind command for each resource at a terminal console (same as the command used in each of their respective load scripts). After a cluster resource is bound to NCP, its NCP users are automatically reconnected and their sessions continue.
To prevent NCP users from receiving any broadcast messages while you are performing these tasks, you can disable the NCP broadcast message support for the server. For instructions, see Section 9.3.1, Enabling or Disabling Broadcast Message Support.
Use the following procedure to create one or more shared NCP volumes on the Linux POSIX cluster resource.
On one node in the cluster, create the NCP volume in order to create its Volume object in NetIQ eDirectory. You do not create the NCP volume on every server.
For detailed instructions, see Section 10.2, Creating NCP Volumes on Linux File Systems.
In OES Remote Manager, click Manage NCP Services > Manage Shares, then click Create New Share.
In Volume Name, type the name of the NCP volume you want to create, such as USERS.
In Path, specify the Linux path of the cluster-enabled Linux POSIX file system or one of its subdirectories, then select the Create If Not Present check box if the subdirectory in the path does not already exist.
For example, if the mount point for the cluster-enabled Linux POSIX file system is /mnt/lxvol44, you can create the NCP volume at its root by specifying /mnt/lxvol44 as the share path, or you can create the NCP volume for a subdirectory on it, such as /mnt/lxvol44/USERS.
For the ongoing example, the NCP volume is created at the root of the Linux POSIX cluster resource. The mount point of the LVM volume and the NCP volume is the same, such as /mnt/lxvol44.
In Shadow Path, leave the field blank and do not select the Create If Not Present check box beneath it.
IMPORTANT:Dynamic Storage Technology does not support using NCP volumes in shadow volume pairs for OES. This field is a placeholder for future capabilities.
Make sure the Inherit POSIX Permissions option is disabled by deselecting the check box.
In OES 2 SP1 Linux and earlier versions, the Inherit POSIX Permissions setting is disabled by default. Enabling the setting here has no effect when you mount the clustered NCP volume in the cluster load script. The setting also cannot be enabled later for clustered NCP volumes as you can for unclustered volumes.
Click OK to confirm the creation of the NCP volume (share).
This creates the Volume object for the NCP volume on the server, such as cn=servername_USERS,ou=context,o=mycompany. This object is renamed later when you create the virtual NCP server (NCS:NCP Server) object.
This also creates a mount point to the volume (share) name you specified, and mounts the NCP volume to make it accessible to NCP clients.
Verify that the share was created successfully by clicking Manage NCP Services > Manage Shares to see a list of NCP shares.
The NCP volume should appear in the list, and be mounted. Mounted volumes appear with the name hyperlinked, and an Unmount button next to it.
Dismount the share from the node by clicking Manage NCP Services > Manage Shares, then clicking the Unmount button next to it.
Repeat Step 1 through Step 3 for each NCP volume that you want to create on the Linux POSIX cluster resource.
Remove the NCP volume names that you created in the previous steps from the /etc/opt/novell/ncpserv.conf file, or comment out the lines.
You want the load and unload scripts for the cluster to control the mounts and dismounts for the NCP volumes. You will modify the cluster scripts later.
If an NCP volume line is present and active in the ncpserv.conf file, the node tries to mount the volume on system startup, even if the cluster resources are not loaded on the node. Mounting and dismounting volumes that are on clustered resources should be done in the cluster load and unload scripts, or at the command line after the resource is loaded. The names of the NCP volumes on the cluster resource should not appear in the ncpserv.conf file on any of the nodes.
On the cluster node where you created the NCP volumes, open a terminal console, then log in as the root user.
Open the /etc/opt/novell/ncpserv.conf file in a text editor.
gedit /etc/opt/novell/ncpserv.conf
Remove or comment out the line. Volume entries look like this:
VOLUME volumename /path_to_mount_point
For example, change
VOLUME USERS /mnt/lxvol44
to this:
;VOLUME USERS /mnt/lxvol44
Save your changes and close the file.
Restart the NetIQ eDirectory (ndsd) daemon by entering the following commands:
rcndsd stop
rcndsd start
If NSS is installed on the server, restart the NCP/NSS IPC daemon by entering
systemctl restart ncp2nss.service
For information about why this is necessary, see Section 3.5, Restarting the OES NCP/NSS IPC (ncp2nss) Daemon.
For each of the other nodes in the cluster where you want to mount the shared cluster resource, create the path for the mount points of each of the NCP volumes that you created in Step 1 through Step 4:
On a cluster node, open a terminal console as the root user.
At the terminal console prompt, enter
mkdir /path_to_mount_point
For example, if the mount point is /mnt/lxvol44, enter
mkdir /mnt/lxvol44
NSSMU automatically uses the Generic File System template (Generic_FS_Template) to create a volume group cluster resource. After you create the resource, you can add lines to its load script, unload script, and monitor script to customize the resource for other uses. Compare the Generic_FS_Template to the resource template for your product to determine which lines need to be added or modified. For more information, see Configuring an LVM Volume Group Cluster Resource with NSS Management Tools
in the OES 2018 SP3: OES Cluster Services for Linux Administration Guide.
After you have created the NCP volume and an NCS:NCP Server object, you must modify the load script so that it mounts the NCP volume path as the Linux POSIX cluster resource is brought online. You must also bind the NCS:NCP Server object to the resource. For an example load script, see Section 11.3.1, Sample Load Script for an NCP Volume Cluster Resource.
In iManager, select Clusters > Cluster Options, then select the cluster.
Click the name link of the Linux POSIX cluster resource to open its Cluster Resource Properties page.
Click the Scripts tab to open the load script.
In the definition area, add the following lines to define the NCP volume and the virtual NCP server name:
# define NCP volume NCP_VOLUME=USERS # define NCP server name NCP_SERVER=cluster1-lxvol44-server
Replace USERS with the name of the NCP volume you created. Replace the NCP server name with the name for your virtual NCP server.
Above the exit line, add a line to mount the NCP volume:
# mount the NCP volume exit_on_error ncpcon mount $NCP_VOLUME=VOL_ID,PATH=$MOUNT_POINT
The volume ID uniquely identifies the volume and is a value between 0 and 254 (up to 255 volumes per server) that you specify so that the same volume ID is used by the NCP volume on all nodes in the server. Cluster volumes are typically numbered from 254 and downward to avoid conflicts with the automatic volume ID assignments that begin with 0.
Under the mount line, add a line to bind the NCP server name to the resource IP address:
# bind the NCP volume exit_on_error ncpcon bind --ncpservername=$NCP_SERVER --ipaddress=$RESOURCE_IP
Click Apply to save your changes.
The script changes are not active until the next time the cluster resource is taken offline, then brought online. Do not activate the script changes at this time.
Continue with Section 11.2.6, Modifying the Unload Script for the LVM Volume Group Cluster Resource.
After you have created the NCP volume and an NCS:NCP Server object, you must modify the unload script so that it dismounts the NCP volume path as the Linux POSIX cluster resource is brought offline. You must also unbind the NCS:NCP Server object from the resource. For an example unload script, see Section 11.3.2, Sample Unload Script for an NCP Volume Cluster Resource.
In iManager, select Clusters > Cluster Options, then select the cluster.
Click the name link of the Linux POSIX cluster resource to open its Cluster Resource Properties page.
Click the Scripts tab, then click Unload to open the unload script.
In the definition area, add the following lines to define the NCP volume and the virtual NCP server name:
# define NCP volume NCP_VOLUME=USERS # define NCP server name NCP_SERVER=cluster1-lxvol44-server
Replace USERS with the name of the NCP volume you created. Replace the NCP server name with the name for your virtual NCP server. Use the same values for variables that you did in the load script.
Under the definition, add a line to unbind the NCP server name from the resource IP address:
# unbind the NCP volume ignore_error ncpcon unbind --ncpservername=$NCP_SERVER --ipaddress=$RESOURCE_IP
Under the unbind line, add a line to dismount the NCP volume:
# dismount the NCP volume ignore_error ncpcon dismount $NCP_VOLUME
Click Apply to save your changes.
The script changes are not active until the next time the cluster resource is taken offline, and then brought online.
Continue with Section 11.2.7, Activating the Script Changes.
The script changes are not active until the next time the cluster resource is taken offline, and then brought online.
In iManager, select Clusters > Cluster Manager, then select the cluster.
Select the check box next to the Linux POSIX cluster resource, then click Offline.
Wait until the resource reports an Offline status before continuing.
Select the check box next to the Linux POSIX cluster resource, then click Online.
Wait until the resource reports an Online status before continuing.
Verify that an NCP user can access the volume. On a workstation, use the Client for Open Enterprise Server to map a drive to the NCP volume.