Start your Internet browser and enter the URL for iManager.

http://server_ip_address/nps/iManager.html

Replace server_ip_address with the IP address or DNS name of an OES 2 Linux server in the cluster that has iManager installed or with the IP address for Apache-based services.

Specify your user name and password.

Specify the tree where the cluster is located, the click Login.

Continue with Creating a Cluster Resource for a Linux POSIX Volume.

In iManager, click Clusters, then click Cluster Options.

Browse and select the Cluster object of the cluster where you want to add a cluster resource.

When the page refreshes, a list of existing cluster resources is displayed.

Click New.

Specify Resource as the resource type you want to create by clicking the Resource radio button, then click Next.

Specify the name of the resource you want to create.

This is the name of the resource for the cluster-enabled Linux POSIX volume. For example, lxvol44_server.

Do not use periods in cluster resource names. Novell clients interpret periods as delimiters. If you use a space in a cluster resource name, that space is converted to an underscore.

In the Inherit From Template field, browse to the Cluster container object, then locate and select the Generic_FS_Template in that container.

Deselect Online on creation.

This option is deselected by default.

Whenever you modify cluster resource settings, you must offline, then online the resource in order for the changes to take effect.

Select the Define Additional Properties check box, then click Next.

This takes you through several pages where you can define the load, unload, and monitoring scripts, then configure the cluster resource properties. Each of these are described in later sections as you continue with the cluster resource configuration.

Continue with Configuring a Load Script for the Linux POSIX Volume Cluster Resource.

On the Load Script page, view the definition section that was pulled from the Generic_FS_Template:

# define the IP address
RESOURCE_IP=a.b.c.d
# define the file system type
MOUNT_FS=reiserfs
#define the container name
container_name=name
# define the device
MOUNT_DEV=/dev/evms/$container_name/volume_name
# define the mount point
MOUNT_POINT=/mnt/mount_point

Modify the variable values in the definition lines with the values for your Linux POSIX volume.

For example:

# define the IP address
RESOURCE_IP=10.10.10.44
# define the file system type
MOUNT_FS=ext3
#define the container name
container_name=csm44
# define the device
MOUNT_DEV=/dev/evms/$container_name/lxvol44
# define the mount point
MOUNT_POINT=/mnt/lxvol44

(Optional) Modify the mount command to add mount options that are available for the file system.

Check the function mount_fs in the /opt/novell/ncs/lib/ncsfuncs file for additional mount options that are available for the file system you are using.

For example, the Ext3 file system supports mount options for access control lists (ACL) and extended attributes (USER_XATTR). You could add the following to the load script for a shared Ext3 volume to take advantage of those options:

#define mount options
MOUNT_OPTIONS=acl,user_xattr

# mount the file system
exit_on_error mount_fs $MOUNT_DEV $MOUNT_POINT $MOUNT_FS $MOUNT_OPTIONS

If the path to the mount point does not exist on other nodes, you can add the following lines in the script before the line to mount the file system:

# create the mount point path when loading on a new node
ignore_error mkdir -p $MOUNT_POINT

Below the script editing area, specify the Load Script Timeout value, then click Next.

The timeout value determines how much time the script is given to complete. If the script does not complete within the specified time, the resource becomes comatose. Cluster Services marks the process as failed right after the defined timeout expires, but it must wait for the process to conclude before it can start other resource operations.

Continue with Section 13.4.4, Configuring an Unload Script for a Linux POSIX Volume Cluster Resource.

On the Unload Script page, view the definition section that was pulled from the Generic_FS_Template:

# define the IP address
RESOURCE_IP=a.b.c.d
# define the file system type
MOUNT_FS=reiserfs
#define the container name
container_name=name
# define the device
MOUNT_DEV=/dev/evms/$container_name/volume_name
# define the mount point
MOUNT_POINT=/mnt/mount_point

Modify the variable values in the definition lines with the values for your Linux POSIX volume.

For example:

# define the IP address
RESOURCE_IP=10.10.10.44
# define the file system type
MOUNT_FS=ext3
#define the container name
container_name=csm44
# define the device
MOUNT_DEV=/dev/evms/$container_name/lxvol44
# define the mount point
MOUNT_POINT=/mnt/lxvol44

Below the script editing area, specify the Unload Script Timeout value, then click Next.

The timeout value determines how much time the script is given to complete. If the script does not complete within the specified time, the resource becomes comatose when migrating to another node. Cluster Services marks the process as failed right after the defined timeout expires, but it must wait for the process to conclude before it can start other resource operations.

Continue with Section 13.4.5, Enabling Monitoring and Configuring a Monitor Script for a Linux POSIX Volume Cluster Resource.

On the Monitor Scripts page, select the Enable Resource Monitoring check box to enable resource monitoring for the selected resource.

Resource monitoring is disabled by default.

On the Monitoring Script page, view the definition section that was pulled from the Generic_FS_Template:

# define the IP address
RESOURCE_IP=a.b.c.d
# define the file system type
MOUNT_FS=reiserfs
#define the container name
container_name=name
# define the device
MOUNT_DEV=/dev/evms/$container_name/volume_name
# define the mount point
MOUNT_POINT=/mnt/mount_point

Modify the variable values in the definition lines with the values for your Linux POSIX volume.

For example:

# define the IP address
RESOURCE_IP=10.10.10.44
# define the file system type
MOUNT_FS=ext3
#define the container name
container_name=csm44
# define the device
MOUNT_DEV=/dev/evms/$container_name/lxvol44
# define the mount point
MOUNT_POINT=/mnt/lxvol44

Below the script editing area, specify the Monitor Script Timeout value, then click Next.

The timeout value determines how much time the script is given to complete. If the script does not complete within the specified time, the resource becomes comatose. Cluster Services marks the process as failed right after the defined timeout expires, but it must wait for the process to conclude before it can start other resource operations.

Continue with Configuring Policies for a Linux POSIX Cluster Resource to configure the cluster resource behavior for the Linux POSIX volume cluster resource.

(Optional) Select the Resource Follows Master check box if you want to ensure that the resource runs only on the master node in the cluster.

If the master node in the cluster fails, the resource fails over to whichever node becomes the master.

(Optional) Select the Ignore Quorum check box if you don't want the cluster-wide timeout period and node number limit enforced.

The quorum default values were set when you installed Novell Cluster Services. You can change the quorum default values by accessing the properties page for the Cluster object.

Selecting this box ensures that the resource is launched immediately on any server in the Assigned Nodes list as soon as any server in the list is brought online.

Specify the Start, Failover, and Failback modes for this resource.

The default for both Start and Failover modes is AUTO, and the default for Failback mode is DISABLE.

Click Next.

Assign nodes to the resource as described in Section 10.8, Configuring Preferred Nodes for a Resource, then click Finished.

When you are done, verify that the resource was created by viewing its entry in the Cluster Objects list on the Cluster Options page.

Configure resource priorities for load order as described in Section 10.9, Configuring Resource Priorities for Load Order.

(Optional) Assign the resource to a Resource Mutual Exclusion Group as described in Section 10.10, Configuring Resource Mutual Exclusion Groups.

Continue with Section 13.5, Verifying the Load and Unload Scripts.