After you have modified the CSM cluster resources’ scripts and added at least one OES 11x node to the cluster, the CSM resources are ready to run only on OES 11x nodes in the cluster. You must modify the preferred nodes for each cluster resource so that it fails over only to other nodes running OES 11x. You should also disable the Resource Follows Master option until the upgrade is complete and all of the OES 2 SP3 nodes have left the cluster. The most preferred node is the first server in the Preferred Nodes list for the resource.
NOTE:Resources fail back only to the first node in their Preferred Nodes list. So if a resource has failed over to three servers since it originally ran on its preferred node, and the second server the resource was running on comes back up, the resource will not failback to that second server.
Resources do not automatically move from node to node just because a node higher in the Preferred Nodes list rejoins the cluster, unless the Failback mode is set to AUTO and the first node in the Preferred Nodes list rejoins the cluster.
To verify the policy settings and modify the preferred nodes:
Ensure that you have offlined the CSM resources from OES 2 SP3 nodes and converted the load, unload, and monitor scripts as described in the following:
Ensure that you have added one or more OES 11x nodes to the OES 2 SP3 cluster as described in Section 14.6, Configuring and Adding OES 11x Nodes to the OES 2 SP3 Cluster, but do not bring the CSM resources online at this time.
In iManager, select Clusters > My Clusters, then select the cluster.
Click the cluster resource name to open its properties pages.
In a mixed-mode cluster, deselect the Resource Follows Master check box to prevent the resource from inadvertently trying to fail over to a non-OES 11 node.
After the conversion to OES 11x is finalized (no longer a mixed-mode cluster), you can enable this option if you want the resource to always run on the master node. 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 Preferred 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.10, Configuring Preferred Nodes and Node Failover Order for a Resource, then click Finished.
IMPORTANT:Ensure that the preferred nodes list contains only OES 11x nodes.
Configure resource priorities for load order as described in Section 10.11, Configuring Resource Priorities for Load Order.
(Optional) Assign the resource to a Resource Mutual Exclusion Group as described in Section 10.12, Configuring Resource Mutual Exclusion Groups.
Continue with Section 14.8, Verifying the Load and Unload Scripts.