| |
If you created a new cluster, you now need to create and configure cluster resources, and if necessary, configure all shared disk system volumes to use Novell Storage Services and create cluster volumes.
While ConsoleOne is required for most cluster-related tasks, you can use NetWare Administrator to modify trustee assignments on files, directories, and cluster-enabled volumes. To use NetWare Administrator to modify trustee assignments, you will first need to establish a connection to the server or cluster-enabled volume.
If you plan on using a shared disk system in your cluster and need to create new NetWare volumes after installing NetWare Cluster Services, the server used to create the volumes should already have NSS installed and running.
IMPORTANT: Earlier versions of NetWare Cluster Services (1.0 and 1.01) required all nodes in the cluster except one to be down when creating volumes on shared storage. After creating the volumes, you needed to bring up the other servers in the cluster. Depending on your configuration, the new volumes either mounted automatically when resources that required them started or would have to be mounted manually on individual servers after they were up.
If you have a volume that is not being managed by NetWare Cluster Services, the volume will need to be mounted before you can access it. The MOUNT ALL command in AUTOEXEC.NCF will no longer mount all NSS volumes by default. Add separate MOUNT commands for each of the volumes you want to mount (from AUTOEXEC.NCF). Add the MOUNT command followed by the volume name to the AUTOEXEC.NCF file of the server where the volume is to be mounted.
If you have a shared disk system that is part of your cluster and want the volumes on the shared disk system to be highly available to NetWare clients, you will need to cluster-enable those volumes. Cluster-enabling a volume allows it to be moved or mounted on different servers in the cluster in a manner that supports transparent client reconnect.
Some server applications don't require NetWare client access to volumes, so cluster-enabling volumes might not be necessary.
In ConsoleOne, browse and select the Cluster object.
Click File > New > Cluster > Cluster Volume.
Browse and select a volume on the shared disk system to cluster-enable.
Enter an IP address for the volume.
Each volume you cluster-enable requires its own IP address.
Click Create, then continue with Set Start, Failover, and Failback Modes.
To complete the process for cluster-enabling a volume, you now need to set failover and failback modes and if necessary, change the node assignments for the volume (See Assign Nodes to a Resource).
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.
NetWare Cluster Services currently provides templates for GroupWise®, Oracle*, and Netscape Enterprise Server*, 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.
In ConsoleOne, browse and select the Cluster object where you want to create a cluster resource template.
From the menu bar, click File > New > Cluster > Cluster Resource.
Enter a name for the new cluster resource template.
Check the Create Cluster Resource Template check box.
This option lets you create a cluster resource template instead of a cluster resource.
Check the Define Additional Properties check box, then continue with Configure 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.
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.
In ConsoleOne, browse and select the Cluster object you want to create resources for.
Click File > New > Cluster > Cluster Resource.
Enter a name for the new cluster resource.
If a template exists for the resource you are creating, enter 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.
Click Create.
(Conditional) If you are not using a template for the resources, continue with Configure 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 change 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 cluster resource configuration is available at Novell's documentation Web site.
A load script is required for each resource, service, or volume 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 an .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.
Select the Load Script tab on the property page.
Edit or add the necessary commands to the script to load the resource on the server.
Some commands may 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 there are more inputs required, they can be continued on subsequent lines, as follows:
LOAD SLPDA <<Y
<<Y
<<N
The string can be up to 32 characters.
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.
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.
Select the Unload Script tab on the property page.
Edit or add the necessary commands to the script to unload the intended resource on the server
You can use any commands used in an .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.
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.
You can configure start, failover and failback of cluster resources to happen manually or automatically. With the resource Start Mode set to AUTO, the resource will automatically start on a server when the cluster is first brought up. If the resource Start Mode is set to MANAUL, 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 will automatically start 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 will not failback to its most preferred node when the most preferred node rejoins the cluster. If the resource Failback Mode is set to AUTO, the resource will automatically failback 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.
To set resource Start, Failover, and Failback modes:
In ConsoleOne, right click the resource object and select Properties, then select the Policies tab on the property page.
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 NetWare Cluster Services. You can change the quorum default values by accessing the properties page for the Cluster object.
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.
When you create a resource on a cluster or cluster-enable a volume, the nodes in the cluster are automatically assigned to the resource or volume. The order of assignment is the order the nodes appear in the resource list. You can assign or unassign nodes to the resource or volume, or change the failover order.
Select the Nodes tab on the property page.
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.
Click the up and down arrow buttons to change the failover order of the servers assigned to the resource or volume.
| |