5.4 Upgrading Clusters from BCC 1.1 SP1 to SP2 for NetWare

Use the procedure in this section to upgrade from BCC version SP1 to SP2:

Initial Configuration

Final Configuration

NetWare 6.5 SP6

BCC 1.1 SP1 for NetWare

Identity Manager 2.x or 3.0.x

NetWare 6.5 SP8

BCC 1.1 SP2 for NetWare

Identity Manager 3.5.1

You must perform the upgrade sequence on every node in each peer cluster that is part of your existing business continuity cluster.

IMPORTANT:Before you begin, review Section 4.1, Requirements for BCC 1.1 SP2 for NetWare.

To upgrade BCC 1.1 from SP1 to SP2, perform the following tasks:

5.4.1 Upgrading NetWare and BCC on the Clusters

Perform a rolling cluster upgrade from NetWare 6.5 SP6 to SP8 for all nodes in a peer cluster:

  1. Stop the Identity Manager drivers from running in the Identity Manager node of every peer cluster in the business continuity cluster.

  2. Issue the cluster leave command on one node in the cluster.

  3. Upgrade NetWare 6.5 from version SP6 to SP8, and apply the latest patches for NetWare and Novell Cluster Services.

    You can perform a script upgrade by using NWCONFIG.

    For information, see the NW65 SP8: Installation Guide.

  4. If the node is running iManager, update the storage related plug-ins for iManager.

    After upgrading to NetWare 6.5 SP8, iManager no longer displays the roles for Clusters, Storage, and DirXML. The storage related plug-ins require special handling because some storage features were reorganized in the NetWare 6.5 SP8 release. For information, see Storage Related Plug-Ins Must Be Uninstalled in the NW65 SP8: Readme.

    NOTE:The DirXML plug-ins will be replaced by Identity Manager 3.5.1 plug-ins in Section 5.4.3, Upgrading Identity Manager.

    1. In iManager, uninstall the old iManager plug-ins for Novell Cluster Services (ncsmgmt.npm), NSS (nssmgmt.npm), Archive and Version Services (arkmgmt.npm), and Storage Management, (storagemgmt.npm).

    2. In iManager, install the new set of storage-related plug-ins for iManager 2.7.2 from the NetWare 6.5 SP8 installation media:

      • Novell AFP (afpmgmt.npm)
      • Novell Archive and Version Services (arkmgmt.npm)
      • Novell CIFS (cifsmgmt.npm)
      • Novell Cluster Services (ncsmgmt.npm)
      • Novell Distributed File Services (dfsmgmt.npm)
      • Novell Storage Services (nssmgmt.npm)
      • Storage Management, (storagemgmt.npm)

    3. Stop Tomcat 5 by issuing tc5stop command.

    4. Reset Apache 2 by using the ap2webrs command.

    5. Start Tomcat 5 by using the tomcat command.

    6. Wait at least 5 minutes for the iManager changes to take effect, then restart iManager.

    7. In iManager, verify that BCC tasks are available in the Clusters role.

  5. Repeat Step 2 through Step 4.g for each node in the cluster.

  6. Issue the cluster join command on each node in the cluster.

  7. On each node in the cluster, upgrade Business Continuity Clustering from version 1.1 SP1 to 1.1 SP2 by installing BCC 1.1 SP2.

    IMPORTANT:Do not start BCC at this time.

    For instructions, see Section 4.0, Installing Business Continuity Clustering.

  8. Issue the ldbcc.ncf command on each node to have them join the BCC.

  9. Repeat Step 2 through Step 8 for each peer cluster in your business continuity cluster.

5.4.2 Authorizing the BCC Administrator User

The BCC Administrator user must be a trustee of the Cluster objects in your BCC, and have at least read and write rights to the all attributes rights property.

  1. Start your Internet 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 the server that has iManager and the Identity Manager preconfigured templates for iManager installed.

  2. Specify your username and password, specify the tree where you want to log in, then click Login.

  3. In the left column, click Rights, then click the Modify Trustees link.

  4. Specify the Cluster object name, or browse and select it, then click OK.

  5. If the BCC Administrator user is not listed as a trustee, click the Add Trustee button, browse and select the User object, then click OK.

  6. Click Assigned Rights for the BCC Administrator user, then ensure that the Read and Write check boxes are selected for the All Attributes Rights property.

  7. Click Done to save your changes.

  8. Repeat Step 3 through Step 7 for the other Cluster objects in for every cluster in the business continuity cluster.

5.4.3 Upgrading Identity Manager

On the Identity Manager node in the cluster, upgrade to Identity Manager 3.5.1.

Before you begin:

For information about installing or upgrading Identity Manager, see the Identity Manager 3.51 Installation Guide.

  1. Upgrade Identity Manager to version 3.51.

    IMPORTANT:Do not start the drivers yet.

    The upgrade updates the Identity Manager software and its plug-ins for iManager 2.7.2 on the same node.

  2. Stop Tomcat 5 by issuing tc5stop command.

  3. Reset Apache 2 by using the ap2webrs command.

  4. Start Tomcat 5 by using the tomcat command.

  5. Wait at least 5 minutes for the iManager changes to take effect, then restart iManager.

  6. In iManager, verify that Identity Manager is available.

    IMPORTANT:In iManager, the Identity Manager plug-ins are displayed as version 3.6. The 3.6 version functions properly with Identity Manager 3.5.1.

5.4.4 Deleting and Re-Creating the BCC Driver Sets and Drivers

After completing the upgrade procedures for every node in all clusters of the business continuity cluster, you must delete and re-create the Identity Manager driver sets and drivers with the BCC 1.1 SP2 templates.

On the Identity Manager node in every peer cluster, do the following:

  1. Delete the Identity Manager 2.x or 3.0.x drivers and driver sets on the Identity Manager node of every peer cluster.

  2. Create the new BCC driver sets for Identity Manager.

  3. Create the new Identity Manager drivers with the new BCC 1.1 SP2 templates.

  4. Start the new Identity Manager drivers for each peer cluster.

5.4.5 Verifying the BCC Upgrade

Verify that Novell Cluster Services and BCC 1.1 SP2 appear to be functioning correctly by performing the following tests:

  1. Create a new BCC enabled pool resource, BCC migrate it between peer clusters, and verify that it migrates correctly.

  2. Make a load script change (for example, add a space character and save the change) to an existing BCC resource that was created with 1.0, allow the revised load script to synchronize, then verify that the load script was updated at all eDirectory locations.

  3. BCC migrate the pool resource that you modified in Step 13.b between peer clusters, and verify that it migrates correctly and that the Identity Manager drivers are synchronizing.

  4. Check all SAN scripts ensure that they will perform the desired functions.