3.7 Setting Up Novell Cluster Services

If you created a new cluster, you now need to create and configure cluster resources. You might also need to create shared disk partitions if they do not already exist and, if necessary, configure all shared disk system pools and volumes to work with Novell Cluster Services. You might also need to cluster enable the shared disk system pools and volumes.

You can use either the server-based NSS Management Utility (NSSMU), iManager, or NetWare Remote Manager to create shared disk partitions, NSS pools, and volumes.

3.7.1 Creating Shared Disk Partitions

Before creating disk partitions on shared storage (storage area network or SAN), Novell Cluster Services must be installed. You should carefully plan how you want to configure your shared storage prior to installing Novell Cluster Services.

Using NSSMU

  1. Start NSSMU by entering NSSMU at the server console of a cluster server.

  2. Select Partitions from the NSSMU main menu.

  3. Press the Insert key and select the device on your shared storage system where you want to create a partition.

    If a device is marked as sharable for clustering, all partitions on that device will automatically be sharable.

    Device names are not changeable and might be labeled something like 0x2 or 0x1.

    If Cluster Services was previously installed and shared disk partitions were already created, the Partitions List will include this information.

  4. Select NSS as the partition type, then specify the parition size and, if desired, an NSS pool name and label.

    If you specify a pool name, a pool by that name will automatically be created on the partition. If no pool name is specified, you will have to create a pool on the partition later.

  5. If you chose to create a pool in Step 4, go to Step 3. If you chose not to create a pool in Step 4 go to Creating NSS Pools.

Using iManager

  1. Start your browser and enter the URL for iManager.

    The URL is http://server_ip_address/nps/imanager.html. Replace server_ip_address with the IP address or DNS name of a NetWare 6.5 server in the cluster, or the IP address for Apache-based services.

  2. Enter your username and password.

  3. In the left column, locate Storage, then click the Pools link.

  4. Type a cluster server name or browse and select one, then click the New link.

  5. Specify the new pool name, then click Next.

  6. Check the box next to the device where you want to create the pool, then specify the size of the pool.

    Because only one pool exists in each partition, the pool size you specify will be the size of the partition that is created.

  7. Choose whether you want the pool to be activated and cluster-enabled when it is created, then click Next.

    The Activate On Creation check box is used to determine if the pool you are creating is to be activated as soon as it is created. The Activate On Creation check box is checked by default. If you uncheck the check box, you must manually activate the pool later before it can be used.

    If you want to cluster-enable the pool at the same time it is created, leave the Cluster Enable on Creation check box checked and continue with Step 8.

    If you want to cluster-enable the pool at a later date, uncheck the check box, click Create, and continue with Cluster Enabling Pools and Volumes.

  8. Specify the Virtual Server Name, Pool IP Address, Advertising Protocols and, if necessary, the CIFS Server Name, then click Finish.

    When you cluster-enable a pool, a virtual Server object is automatically created and given the name of the Cluster object plus the cluster-enabled pool. For example, if the cluster name is cluster1 and the cluster-enabled pool name is pool1, then the default virtual server name will be cluster1_pool1_server. You can edit the field to change the default virtual server name.

    Each cluster-enabled NSS pool requires its own IP address. The IP address is used to provide access and failover capability to the cluster-enabled pool (virtual server). The IP address you assign to the pool remains assigned to the pool regardless of which server in the cluster is accessing the pool.

    You can select one or all of the advertising protocols. NCP™ is the protocol used by Novell clients, CIFS is the protocol used by Microsoft* clients, and AFP is the protocol used by Macintosh* clients. Selecting any of the protocols will cause lines to be added to the pool resource load and unload scripts to activate the selected protocols on the cluster. This lets you ensure that the cluster-enabled pool you just created is highly available to all your clients.

    If you check the CIFS check box, the Server Name field will become active. The CIFS server name is the server name CIFS clients see when they browse the network. A default server name is listed, but you can change the server name by editing the text in the field.

Using Novell Remote Manager

In Novell Remote Manager, the process for creating a shared disk partition is also used to create an NSS pool, and volume. Novell Remote Manager will create the partition, NSS pool, and volume and, if desired, it will also cluster enable the NSS pool all at the same time.

  1. In the left column under the Manage Server section, click Partition Disks.

    A screen appears displaying a list of devices that are currently accessible to servers in the cluster. For each device, the list displays the partitions, NSS pools, volumes, and free space on that device.

  2. Find the device that corresponds to your shared storage system and click Create on the free space where you want to create the partition.

  3. Select Novell Storage Services as the partition type and click Create a New Pool and Volume.

  4. Specify the pool size and name, the volume name, and volume attributes.

    Because only one pool exists in each partition, the pool size you specify will be the size of the partition that gets created. The volume that is created will be allowed to grow to the pool size.

  5. Choose whether you want the pool to be cluster enabled when it is created.

    The default is to cluster enable the pool at the time it is created. If you want to cluster enable the pool at the same time it is created, leave the Cluster Enable Pool check box checked and continue with Step 6.

    If you want to cluster enable the pool at a later date, uncheck the check box, click Create, and continue with Cluster Enabling Pools and Volumes.

  6. Specify the Virtual Server Name, Pool IP Address, Advertising Protocols and, if necessary, the CIFS Server Name and whether you want the pool to be activated upon creation.

    When you cluster enable a pool, a virtual Server object is automatically created and given the name of the Cluster object plus the cluster-enabled pool. For example, if the cluster name is cluster1 and the cluster-enabled pool name is pool1, then the default virtual server name will be cluster1_pool1_server. You can edit the field to change the default virtual server name.

    Each cluster-enabled NSS pool requires its own IP address. The IP address is used to provide access and failover capability to the cluster enabled-pool (virtual server). The IP address you assign to the pool remains assigned to the pool regardless of which server in the cluster is accessing the pool.

    You can select one or all of the advertising protocols. NCP is the protocol used by Novell clients, CIFS is the protocol used by Microsoft clients, and AFP is the protocol used by Macintosh clients. Selecting any of the protocols will cause lines to be added to the pool resource load and unload scripts to activate the selected protocols on the cluster. This lets you ensure that the cluster-enabled pool you just created is highly available to all your clients.

    If you check the CIFS check box, the CIFS Server Name field will become active. The CIFS server name is the server name CIFS clients see when they browse the network. A default server name is listed, but you can change the server name by editing the text in the field.

    The Auto Pool Activate check box is used to determine if the pool you are creating is to be activated as soon as it is created. The Auto Pool Activate check box is checked by default. If you uncheck the check box, you will have to manually activate the pool later before it can be used.

  7. Click Create to create the partition, NSS pool, and volume and to cluster enable the NSS pool.

3.7.2 Creating NSS Pools

The Storage Pools feature in NSS gives you more flexibility in planning and configuring your storage to work with Novell Cluster Services. More than one cluster-enabled volume can be part of a single cluster resource, and volumes can dynamically grow as needed to take advantage of free disk space.

Only one NSS pool can be created on a partition. Storage pools can be cluster enabled at the same time they are created or they can be cluster enabled at a later time after they are created. To learn more about NSS pools, see Managing NSS Pools in the Novell Storage Services Administration Guide.

Using NSSMU

  1. From the NSSMU main menu, select Pools, press Insert, and then type a name for the new pool you want to create.

  2. Select the partition on your shared storage where you want the pool created.

  3. Choose whether you want the pool to be activated and cluster enabled when it is created.

    The Activate on Creation feature is enabled by default. This causes the pool to be activated as soon as it is created. If you choose not to activate the pool, you will have to manually activate it later before it can be used.

    The Cluster Enable on Creation feature is also enabled by default. If you want to cluster enable the pool at the same time it is created, accept the default entry (Yes) and continue with Step 4. If you want to cluster enable the pool at a later date, change the default entry from Yes to No, select Create, then go to Creating Cluster Volumes.

  4. Specify the Virtual Server Name, IP Address, Advertising Protocols and, if necessary, the CIFS Server Name.

    When you cluster enable a pool, a virtual Server object is automatically created and given the name of the Cluster object plus the cluster-enabled pool. For example, if the cluster name is cluster1 and the cluster-enabled pool name is pool1, then the default virtual server name will be cluster1_pool1_server. You can edit the field to change the default virtual server name.

    Each cluster-enabled NSS pool requires its own IP address. The IP address is used to provide access and failover capability to the cluster-enabled pool (virtual server). The IP address you assign to the pool remains assigned to the pool regardless of which server in the cluster is accessing the pool.

    You can select one or all of the advertising protocols. NCP is the protocol used by Novell clients, CIFS is the protocol used by Microsoft clients, and AFP is the protocol used by Macintosh clients. Selecting any of the protocols will cause lines to be added to the pool resource load and unload scripts to activate the selected protocols on the cluster. This lets you ensure that the cluster-enabled pool you just created is highly available to all your clients.

    If you select CIFS as one of the protocols, a CIFS Server Name is also required. This is the server name CIFS clients see when they browse the network. A default server name is listed, but you can change the server name by editing the text in the field.

  5. Select Create to create and cluster enable the pool.

    Repeat the above steps for each additional pool you want to create on shared storage.

    Continue with Creating Cluster Volumes.

Using iManager

The same procedure for creating shared disk partitions using iManager is used to create NSS pools. To create an NSS pool on shared storage using iManager go to Step 1.

Using Novell Remote Manager

The same procedure for creating shared disk partitions using Novell Remote Manager is used to create NSS pools. To create an NSS pool on shared storage using Novell Remote Manager go to Step 1.

3.7.3 Creating Cluster Volumes

If you plan on using a shared disk system in your cluster and need to create new NetWare pools or volumes after installing Novell Cluster Services, the server used to create the volumes should already have NSS installed and running. NSS is the default file system for NetWare 6.5.

Using NSSMU

  1. From the NSSMU main menu select Volumes, press Insert, then type a name for the new volume you want to create.

    Each shared volume in the cluster must have a unique name.

  2. Select the pool where you want the volume to reside.

  3. Review and change volume attributes as necessary.

    You might want to enable the Flush Files Immediately feature. This will help ensure the integrity of volume data. Enabling the Flush Files Immediately feature improves file system reliability but hampers performance. You should consider this option only if necessary.

  4. Either specify a quota for the volume or accept the default of 0 to allow the volume to grow to the pool size, then select Create.

    The quota is the maximum possible size of the volume. If you have more than one volume per pool, you should specify a quota for each volume rather than allowing multiple volumes to grow to the pool size.

  5. Repeat the above steps for each cluster volume you want to create.

Depending on your configuration, the new volumes will either mount automatically when resources that require them start or will have to be mounted manually on individual servers after they are up.

Using iManager

  1. Start your browser and enter the URL for iManager.

    The URL is http://server_ip_address/nps/imanager.html. Replace server_ip_address with the IP address or DNS name of a NetWare 6.5 server in the cluster or the IP address for Apache-based services.

  2. Enter your username and password.

  3. In the left column, locate Storage, then click the Volumes link.

  4. Type a cluster server name or browse and select one, then click the New link.

  5. Specify the new volume name, then click Next.

  6. Check the box next to the cluster pool where you want to create the volume and either specify the size of the volume (Volume Quota) or check the box to allow the volume to grow to the size of the pool, then click Next.

    The volume quota is the maximum possible size of the volume. If you have more than one volume per pool, you should specify a quota for each volume rather than allowing multiple volumes to grow to the pool size.

  7. Review and change volume attributes as necessary.

    The Flush Files Immediately feature helps ensure the integrity of volume data. Enabling the Flush Files Immediately feature improves file system reliability but hampers performance. You should consider this option only if necessary.

  8. Choose whether you want the volume activated and mounted when it is created, then click Finish.

Using NetWare Remote Manager

The same procedure for creating shared disk partitions using NetWare Remote Manager is used to create cluster volumes. To create a cluster volume on shared storage using NetWare Remote Manager go to Step 1.

3.7.4 Cluster Enabling Pools and Volumes

If you have a shared disk system that is part of your cluster and you want the pools and volumes on the shared disk system to be highly available to NetWare clients, you will need to cluster enable those pools and volumes. Cluster enabling a pool or volume allows it to be moved or mounted on different servers in the cluster in a manner that supports transparent client reconnect.

With this release of Cluster Services, cluster-enabled volumes no longer appear as cluster resources. NSS pools are resources, and load and unload scripts apply to pools and are automatically generated for them. Each cluster-enabled NSS pool requires its own IP address. This means that each cluster-enabled volume does not have an associated load and unload script or an assigned IP address.

NSS pools can be cluster enabled at the same time they are created. If you did not cluster enable a pool at creation time, the first volume you cluster enable in the pool automatically cluster enables the pool where the volume resides. Once a pool has been cluster enabled, you will need to cluster enable the other volumes in the pool if you want them to be mounted on another server during a failover.

When a server fails, any cluster-enabled pools being accessed by that server will fail over to other servers in the cluster. Because the cluster-enabled pool fails over, all volumes in the pool will also fail over, but only the volumes that have been cluster enabled will be mounted. Any volumes in the pool that have not been cluster enabled will have to be mounted manually. For this reason, volumes that aren't cluster enabled should be in separate pools that are not cluster enabled.

If you want each cluster-enabled volume to be its own cluster resource, each volume must have its own pool.

Some server applications don't require NetWare client access to volumes, so cluster enabling pools and volumes might not be necessary. Pools should be deactivated and volumes should be dismounted before being cluster enabled.

Using iManager

  1. Start your browser and enter the URL for iManager.

    The URL is http://server_ip_address/nps/imanager.html. Replace server_ip_address with the IP address or DNS name of a NetWare 6.5 server in the cluster, or the IP address for Apache-based services.

  2. Enter your username and password.

  3. In the left column, locate Clusters, then click the Cluster Options link.

    iManager displays four links under Clusters that you can use to configure and manage your cluster.

  4. Type the cluster name or browse and select it, then click the New link.

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

  6. Type the name of the pool you want to cluster-enable, or browse and select one.

  7. (Optional) Change the default name of the virtual Server object.

    When you cluster-enable a pool, a virtual Server object is automatically created and given the name of the Cluster object plus the cluster-enabled pool. For example, if the cluster name is cluster1 and the cluster-enabled pool name is pool1, then the default virtual server name will be cluster1_pool1_server.

    If you are cluster-enabling a volume in a pool that has already been cluster-enabled, the virtual Server object has already been created, and you can't change the virtual Server object name.

  8. (Optional) Change the default name of the CIFS server name.

    If you check the CIFS check box in the Advertising Protocols section of this page, the CIFS Server Name field will become active. The CIFS server name is the server name CIFS clients see when they browse the network. A default server name is listed, but you can change the server name by editing the text in the field.

  9. Type an IP address for the pool.

    Each cluster-enabled NSS pool requires its own IP address. The IP address is used to provide access and failover capability to the cluster-enabled pool (virtual server). The IP address assigned to the pool remains assigned to the pool regardless of which server in the cluster is accessing the pool.

  10. Select one or more advertising protocols.

    You can select one or all of the advertising protocols. NCP is the protocol used by Novell clients, CIFS is the protocol used by Microsoft clients, and AFP is the protocol used by Macintosh clients. Selecting any of the protocols causes lines to be added to the pool resource load and unload scripts to activate the selected protocols on the cluster. This lets you ensure that the cluster-enabled pool is highly available to all your clients.

  11. (Optional) Check the Online Resource after Create check box.

    This will cause the volume to automatically mount once it is created.

  12. Ensure the Define Additional Properties check box is checked, then click Next and continue with Set Start, Failover, and Failback Modes.

NOTE:Cluster resource load and unload scripts are automatically generated for pools when they are cluster-enabled.

Using ConsoleOne

  1. Browse and select the Cluster object.

  2. Click File > New > Cluster > Cluster Volume.

  3. Browse and select a volume on the shared disk system to cluster enable.

  4. Type an IP address for the volume.

    This is only required for the first volume to be cluster enabled in the pool. This IP address will be assigned to the pool where the volume resides.

    Checking the Online Resource after Create check box will cause the volume to automatically mount after it is created.

  5. (Optional) Change the default name of the virtual Server object.

    When you cluster enable a pool, a virtual Server object is automatically created and given the name of the Cluster object plus the cluster-enabled pool. For example, if the cluster name is cluster1 and the cluster-enabled pool name is pool1, then the default virtual server name will be cluster1_pool1_server.

    If you are cluster enabling a volume in a pool that has already been cluster enabled, the virtual Server object has already been created, and you can't change the virtual Server object name.

  6. (Optional) Change the default name of the cluster-enabled Volume object.

    When you cluster enable a volume, a new object is automatically created and given the name of the Cluster object and the volume name. For example, if the cluster name is cluster1 and the volume name is vol1, then the default cluster-enabled Volume object name will be cluster1_vol1.

  7. Ensure that the Define Additional Properties check box is checked, click Create, then continue with Set Start, Failover, and Failback Modes.

Using Novell Remote Manager

  1. In Novell Remote Manager, in the left column under the Clustering section, select Cluster Config.

  2. At the bottom of the screen under Create New Objects, click New Cluster Volume.

  3. Select the volume you created in the previous section and click Select.

  4. Type the IP address you want to assign to the cluster-enabled volume.

    All other fields on this screen should be automatically updated. You can change or edit the information in the fields as desired. See Step 5 and Step 6 for more information.

    This is only required for the first volume to be cluster enabled in the pool. This IP address will be assigned to the pool where the volume resides.

    Checking the Auto-Online check box will cause the resource to automatically start once it is created.

  5. Click the Save button to create the volume resource and then continue with Set Start, Failover, and Failback Modes.

When the volume resource is brought online, the pool will automatically be activated. You don't need to activate the pool at the server console.

If you delete a cluster-enabled volume, Novell Cluster Services will automatically remove the volume mount command from the resource load script. If you delete a cluster-enabled pool, Novell Cluster Services will automatically remove the pool resource object and the virtual server object from eDirectory. If you rename a cluster-enabled pool, Novell Cluster Services will automatically update the pool resource load and unload scripts to reflect the name change. Also, NSS will automatically change the pool object name in eDirectory.

3.7.5 Creating Cluster Resource Templates

Templates simplify the process of creating similar or identical cluster resources. For example, templates are helpful when you want to create multiple instances of the same resource on different servers. You can create templates for any server application or resource you want to add to your cluster.

Novell Cluster Services currently provides templates for DHCP, iFolder®, and MySQL*, as well as a generic IP SERVICE template. The generic IP SERVICE template can be used when configuring certain server applications to run on your cluster. You can edit and customize any of the templates for your specific needs.

Using iManager

  1. Start your browser and enter the URL for iManager.

    The URL is http://server_ip_address/nps/imanager.html. Replace server_ip_address with the IP address or DNS name of a NetWare 6.5 server in the cluster or the IP address for Apache-based services.

  2. Enter your username and password.

  3. In the left column, locate Clusters, then click the Cluster Options link.

    iManager displays four links under Clusters that you can use to configure and manage your cluster.

  4. Type the cluster name or browse and select it, then click the New link.

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

  6. Type the name of the template you want to create.

  7. Ensure that the Define Additional Properties check box is checked, then continue with Configuring Load Scripts.

    To finish creating a cluster resource template, you need to configure load and unload scripts, set failover and failback modes and, if necessary, change the node assignments for the resource template.

Using ConsoleOne

  1. Browse and select the Cluster object where you want to create a cluster resource template.

  2. From the menu bar, click File > New > Cluster > Cluster Resource.

  3. Type a name for the new cluster resource template.

  4. Check the Create Resource Template check box.

    This option lets you create a cluster resource template instead of a cluster resource.

  5. Check the Define Additional Properties check box, and then continue with Configuring Load Scripts.

    To finish creating a cluster resource template, you need to configure load and unload scripts, set failover and failback modes and, if necessary, change the node assignments for the resource template.

Using Novell Remote Manager

  1. On the left column under the Clustering section, click Cluster Config.

  2. At the bottom of the screen above Create New Objects, click New Cluster Resource.

  3. Type a name for the new cluster resource template.

  4. Check the Create Resource and the Define Additional Properties check boxes, then click Apply.

  5. Continue with Configuring Load Scripts.

3.7.6 Creating Cluster Resources

Cluster resources must be created for every resource or application you run on servers in your cluster. Cluster resources can include Web sites, e-mail servers, databases, and any other server-based applications or services you want to make available to users at all times.

Using iManager

  1. Start your browser and enter the URL for iManager.

    The URL is http://server_ip_address/nps/imanager.html. Replace server_ip_address with the IP address or DNS name of a NetWare 6.5 server in the cluster or the IP address for Apache-based services.

  2. Enter your username and password.

  3. In the left column, locate Clusters, then click the Cluster Options link.

    iManager displays four links under Clusters that you can use to configure and manage your cluster.

  4. Type the cluster name or browse and select it, then click the New link.

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

  6. Type the name of the resource you want to create.

    IMPORTANT:Do not use periods in cluster resource names. NetWare and NetWare clients interpret a period as a delimiter.

  7. If a template exists for the resource you are creating, type the template name in the Inherit From Template field, or browse and select it from the list. If a template does not exist, check the Define Additional Properties check box.

  8. (Conditional) If you are not using a template for the resource, continue with Configuring Load Scripts.

Using ConsoleOne

  1. Browse and select the Cluster object you want to create resources for.

  2. Click File > New > Cluster > Cluster Resource.

  3. Type a name for the new cluster resource.

    IMPORTANT:Do not use periods in cluster resource names. NetWare and NetWare clients interpret a period as a delimiter.

  4. If a template exists for the resource you are creating, type the template name in the Inherit From Template field, or browse and select it from the list. If a template does not exist, check the Define Additional Properties check box.

  5. (Conditional) Check the Online Resource after Create check box if you want the resource to automatically start on the master node as soon as it is created and configured.

  6. Click Create.

  7. (Conditional) If you are not using a template for the resources, continue with Configuring Load Scripts.

Using Novell Remote Manager

  1. On the left column under the Clustering section, click Cluster Config.

  2. At the bottom of the screen under Create New Objects, click New Cluster Resource.

  3. Type a name for the new cluster resource.

  4. If a template exists for the resource you are creating, select it from the list and then click Apply. If a template does not exist, check the Define Additional Properties check box, then click Apply.

    The default selection for this field is No Template.

  5. (Conditional) If you are not using a template for the resource, continue with Configuring Load Scripts.

If you are not using a template, you must complete the process for creating the cluster resource by configuring load and unload scripts, setting failover and failback modes and, if necessary, changing the node assignments for the resource.

If you are using a template for this resource, additional resource configuration is performed automatically by the template.

More information on configuring GroupWise, NDPS®, iFolder and many other applications is available at the Novell Cluster Services Documentation Web site .

3.7.7 Configuring Load Scripts

A load script is required for each resource, service, or disk pool in your cluster. The load script specifies the commands to start the resource or service on a server, or to mount the volume on a server.

You can use any commands in the load script that would be used in a .ncf file run from the server console. If you don't know which commands to add to your load script, consult the documentation for the application or resource.

Load scripts are automatically created for disk pools when you cluster enable them. Because of this, it might not be necessary to configure or change the load script for a pool.

Using iManager

If you are creating a new cluster resource, the load script page should already be displayed. You can start with Step 4.

  1. In the left column of the main iManager page, locate Clusters and click the Cluster Options link.

  2. Type the cluster name or browse and select it, check the box next to the resource whose load script you want to edit, then click the Details link.

  3. Click the Scripts tab, then click the Load Script link.

  4. Edit or add the necessary commands to the script to load the resource on the server.

    For more details on load script commands, see the instructions below on configuring load scripts using ConsoleOne.

  5. Specify the Load Script Timeout value, then click Apply to save the script; or, if you are creating a new cluster resource, 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.

Using ConsoleOne

  1. Select the Load Script tab on the resource property page.

  2. Edit or add the necessary commands to the script to load the resource on the server.

    Some commands might require command line input. You can add << to a command to indicate command line input. For example, a script command might read

    LOAD SLPDA <<Y
    

    This means that when SLPDA is loaded, it will receive a Y at the command line, presumably to a question that needs a Yes answer. If more inputs are required, they can be continued on subsequent lines, as follows:

    LOAD SLPDA <<Y
    
    <<Y
    
    <<N
    

    The string can be up to 32 characters.

  3. Specify a timeout value.

    The default is 600 seconds, or 10 minutes. 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.

Using Novell Remote Manager

  1. On the left column under the Clustering section, click Cluster Config.

  2. From the list of Resources, select the desired resource or resource template.

  3. On the Resource Information screen, click Loading.

  4. Edit or add the necessary commands to the script to load the resource on the server.

    For more details on load script commands see the instructions above on configuring load scripts using ConsoleOne.

  5. Specify the Load Timeout and click Apply to save the script.

    This is the same as the timeout value described in the above instructions on configuring load scripts using ConsoleOne.

3.7.8 Configuring Unload Scripts

Depending on your cluster application or resource, you can add an unload script to specify how the application or resource should terminate. An unload script is not required by all resources or applications, but it can ensure that during a failback or manual migration, a resource unloads before it loads on another node. Consult your application vendor or documentation to determine if you should add commands to unload the resource.

Unload scripts are automatically created for disk pools when you cluster enable them. Because of this it might not be necessary to configure or change the load script for a pool.

Using iManager

If you are creating a new cluster resource, the unload script page should already be displayed. You can start with Step 4.

  1. In the left column of the main iManager page, locate Clusters, then click the Cluster Options link.

  2. Type the cluster name or browse and select it, check the box next to the resource whose unload script you want to edit, then click the Details link.

  3. Click the Scripts tab, then click the Unload Script link.

  4. Edit or add the necessary commands to the script to unload the resource on the server.

    You can use any commands used in a .ncf file run from the server console. If you don't know which commands to add, consult the documentation for the application or resource you want to unload.

  5. Specify the Unload Script Timeout value, then click Apply to save the script; or, if you are creating a new cluster resource, 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.

Using ConsoleOne

  1. Select the Unload Script tab on the resource property page.

  2. Edit or add the necessary commands to the script to unload the intended resource on the server.

    You can use any commands used in a .ncf file run from the server console. If you don't know which commands to add, consult the documentation for the application or resource you want to unload.

  3. Specify a timeout value and click Apply to save the script.

    The default is 600 seconds, or 10 minutes. 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.

Using Novell Remote Manager

  1. In the left column under the Clustering section, click Cluster Config.

  2. From the list of resources, select the desired resource.

  3. On the Resource Information screen, click Unloading.

  4. Edit or add the necessary commands to the script to unload the intended resource on the server.

  5. Specify the Load Wait Time and click Apply to save the script.

3.7.9 Set Start, Failover, and Failback Modes

You can configure the start, failover, and failback of cluster resources to happen manually or automatically. With the resource Start Mode set to AUTO, the resource automatically starts on a server when the cluster is first brought up. If the resource Start Mode is set to MANUAL, you can manually start the resource on a server when you want, instead of having it automatically start when servers in the cluster are brought up.

With the resource Failover Mode set to AUTO, the resource automatically starts on the next server in the Assigned Nodes list in the event of a hardware or software failure. If the resource Failover Mode is set to MANUAL, you can intervene after a failure occurs and before the resource is moved to another node.

With the resource Failback Mode set to DISABLE, the resource does not fail back to its most preferred node when the most preferred node rejoins the cluster. If the resource Failback Mode is set to AUTO, the resource automatically fails back to its most preferred node when the most preferred node rejoins the cluster. Set the resource Failback Mode to MANUAL to prevent the resource from moving back to its preferred node when that node is brought back online, until you are ready to allow it to happen.

The preferred node is the first server in the list of the assigned nodes for the resource.

Using iManager

If you are creating a new cluster resource, the Resource Policies page should already be displayed. You can start with Step 4.

  1. In the left column of the main iManager page, locate Clusters, then click the Cluster Options link.

  2. Type the cluster name or browse and select it, check the box next to the resource whose start, failover, or failback modes you want to view or edit, then click the Details link.

  3. Click the General tab.

  4. (Conditional) Check 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 will fail over to whichever node becomes the master.

  5. (Conditional) Check 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.

    Checking this box will ensure 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.

  6. Choose 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.

  7. Continue with Assign Nodes to a Resource, or if you are creating a new cluster resource, click Next, then continue with Assign Nodes to a Resource.

Using ConsoleOne

  1. In ConsoleOne, right-click the resource object and select Properties, then select the Policies tab on the property page.

  2. (Conditional) Check 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.

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

  3. Choose 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.

  4. Check the Master Only check box to ensure the resource runs only on the master node in the cluster.

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

  5. Click Apply to save changes.

Using Novell Remote Manager

  1. In the left column under the Clustering section, click Cluster Config.

  2. From the list of resources, select the desired resource.

  3. On the Resource Information screen, click Policies.

  4. Check or uncheck the Ignore Quorum check box as desired.

    See the instructions above on setting resource Start, Failover, and Failback modes using ConsoleOne for more details.

  5. Select the Start, Failover, and Failback modes for this resource.

  6. Check or uncheck the Master Only check box.

    If the Master Only box is checked, the resource will run only on the server designated as the Master node in the cluster.

  7. Click Apply.

3.7.10 Assign Nodes to a Resource

When you create a resource on a cluster or cluster enable a volume or pool, the nodes in the cluster are automatically assigned to the resource or the volume or pool. The order of assignment is the order the nodes appear in the resource list. You can assign or unassign nodes to the resource or the volume or pool, or change the failover order.

Using iManager

If you are creating a new cluster resource, the Preferred Nodes page should already be displayed. If you have just set start, failover, and failback modes, the Preferred Nodes page will be displayed as part of the Resource Policies page. You can start with Step 4.

  1. In the left column of the main iManager page, locate Clusters, then click the Cluster Options link.

  2. Type the cluster name or browse and select it, check the box next to the resource whose assigned nodes you want to change, then click the Details link.

  3. Click the Preferred tab.

  4. From the list of unassigned nodes, select the server you want the resource assigned to, then click the right-arrow button to move the selected server to the Assigned Nodes list.

    Repeat this step for all servers you want assigned to the resource. You can also use the left-arrow button to unassign servers from the resource.

  5. Click the up-arrow and down-arrow buttons to change the failover order of the servers assigned to the resource or volume.

  6. Click Apply or Finish to save node assignment changes.

Using ConsoleOne

  1. Select the Nodes tab on the resource property page.

  2. From the list of unassigned nodes, select the server you want the resource assigned to, and click the right-arrow button to move the selected server to the Assigned Nodes list.

    Repeat this step for all servers you want assigned to the resource. You can also use the left-arrow button to unassign servers from the resource.

  3. Click the up-arrow and down-arrow buttons to change the failover order of the servers assigned to the resource or volume.

  4. Click Apply to save node assignment changes.

Using Novell Remote Manager

  1. In the left column under the Clustering section, click Cluster Config.

  2. From the list of resources, select the desired resource.

  3. On the Resource Information screen, click Nodes.

  4. Select or type the nodes that you want assigned to this resource.

  5. Click Apply to save node assignment changes.