6.4 Adding OES 11 Nodes to an OES 2 Cluster (Rolling Cluster Upgrade)

Performing a rolling cluster upgrade from OES 2 to OES 11 lets you keep your cluster up and running and lets your users continue to access cluster resources while the upgrade is being performed.

During a rolling cluster upgrade, one OES 11 server is added at a time. You should complete the upgrade as soon as possible. Don’t leave the cluster in a mixed-mode state for an extended period.

To perform a rolling cluster upgrade:

  1. Make a note of the OES components that are installed on the OES 2 cluster nodes.

    You will probably want to install the same OES components on the OES 11 nodes that you add to the cluster.

  2. Prepare some OES 11 nodes for the cluster, but do not allow them to join the cluster.

    IMPORTANT:If you are upgrading an OES 2 cluster node to OES 11, leave the cluster before the upgrade and do not rejoin until Step 4.

    1. Install SUSE Linux Enterprise Server (SLES) 11 and the OES Services from the OES Add-on disk, including Novell Cluster Services, but do not configure the node for the cluster at this time.

    2. Verify that the server is functioning properly.

    3. In YaST, go to the Novell Cluster Services Configuration page as described in Section 5.5.4, Accessing the Novell Cluster Services Configuration Page in YaST.

    4. Configure the node for the existing OES 2 cluster as described in Section 5.5.6, Adding a Node to an Existing Cluster.

      Parameter

      Action

      LDAP administrator user password

      Specify the password of the user name shown, then click OK.

      Typically, this is the LDAP administrator identity that was used when the OES Services were installed, or the identity configured after the install in Section 5.5.3, Using Different LDAP Credentials for the Cluster Configuration.

      New or existing cluster

      Select Existing Cluster.

      Directory Server Address

      Select the check box next to the IP address of the LDAP server you want to use as the default for this node. The local LDAP server is selected by default.

      You can add, remove, or change the order of available LDAP servers for the node after the setup is complete. See Section 8.11.1, Changing the Administrator Credentials or LDAP Server IP Addresses for a Cluster.

      Cluster FDN

      Click Browse, navigate the tree to select the existing Cluster object for the OES 2 cluster, click OK, then click Next.

      NCS Proxy User Name

      Specify one of the following users as the NCS Proxy user for this server, then click Next:

      • OES Common Proxy User (default if it was configured for the server)

      • LDAP Admin User

      • Another Administrator User

      IP address of this node

      From the drop-down list, select the IP address that Novell Cluster Services will use for this node.

      Start Cluster Services now

      Deselect the check box.

      Do not start cluster services on this node or join the cluster until Step 4, after all of the Linux POSIX cluster resources have been taken offline.

    5. Click Finish, review the summary, then click Next to complete the configuration.

    6. Click Finish to close the OES Configuration dialog box.

  3. On each OES 2 SP3 node, prepare each of the existing Linux POSIX cluster resources for OES 11 by doing the following:

    1. Take the Linux POSIX cluster resource offline.

    2. Disable the Resource Follows Master option for the resource.

    3. Modify the resource’s load, unload, and monitor scripts.

      Use one of the following methods to prepare the resource, depending on how it is configured:

    4. Modify other resource policy settings as desired, but do not enable the Resource Follows Master option.

    5. Do not bring a Linux POSIX resources online until you are ready to do so in Step 5.b, after its Preferred Nodes list has been modified to use only OES 11 nodes.

    6. Repeat Step 3.a to Step 3.e for each Linux POSIX cluster resource.

  4. For each of the OES 11 nodes, start Novell Cluster services manually by using one of the following methods, and allow the node to join the OES 2 cluster.

    • Reboot the cluster server.

    • At a terminal console prompt, go to the /etc/init.d directory, then enter the following as the root user: 

      ./novell-ncs start

    • At a terminal console prompt, enter the following as the root user:

      rcnovell-ncs start

  5. For each of the Linux POSIX cluster resources in turn, do the following:

    1. In iManager, modify the resource’s Preferred Nodes list to include only OES 11 nodes as described in Section 13.4, Configuring the Preferred Nodes and Cluster Settings for a CSM Cluster Resource.

    2. In iManager, bring the resource online on its first preferred node. Click Clusters > Cluster Manager, select the resource object, then click Online.

      You can also use the cluster online command.

      cluster online <resource_name> <node_name>

    3. Verify that the resource and any related services are working properly for the resource.

    4. Repeat Step 5.a to Step 5.c for each Linux POSIX cluster resource.

  6. If you add more OES 11 nodes, ensure that you modify the Preferred Nodes list accordingly for each of the Linux POSIX cluster resources.

  7. Bring down the OES 2 cluster node that you want to remove from the cluster.

    Any cluster resources that were running on the server should fail over to another server in its preferred nodes list.

    You can also manually migrate the resources to another server in the cluster prior to bringing down the server.

  8. After the last cluster resource has been moved to the OES 11 nodes and all OES 2 nodes have left the cluster, the conversion is complete.