This Readme applies to Novell® Business Continuity Clustering (BCC) 1.1 Support Pack (SP) 1 for Novell Open Enterprise Server (OES) 1 SP2 Linux and for NetWare 6.5 SP5 or SP6.
To download BCC 1.1 SP1, go to The Novell Business Continuity Clustering download site.
For information on Business Continuity Clustering 1.1 SP1 for OES 1 SP2 Linux and for NetWare 6.5 SP5/SP6, see the BCC Documentation Web site.
The latest OES Linux patches from the patch channel are required prior to installing BCC 1.1. For instructions on updating OES Linux with the latest patches, see Patching an OES Linux Server in the OES Linux Installation Guide.
For more information on applying patches using the YaST online update or Red Carpet, see the Novell Linux Registration and Updates page.
The following OES NetWare patches are required prior to installing BCC1.1:
The NetWare 6.5 post Support Pack 5 Update. See OES SP2, NW6.5 SP5 Update 1: TID # 2974185.
This patch is required only for NetWare 6.5 Support Pack 5. If you have upgraded to NetWare 6.5 Support Pack 6, this patch is not required.
The nwcs18pt3 or later cluster patch. See Netware Cluster Services Field Test: TID # 2974985.
This patch can be applied only to NetWare 6.5 Support Pack 5. If you have upgraded to NetWare 6.5 Support Pack 6, this patch is not required.
LIBC (libcsp6X or later) See LIBC Update NetWare 6.5 SP6 9.00.05: TID # 5003460.
OpenWBEM. See CIMOM Update for NetWare 6.5 SP6: TID # 5004180.
You must remove the existing iManager plug-in for Novell Cluster Services and replace it with the plug-in that is on the Novell download Web site. Updating the iManager plug-in for cluster services resolves sporadic iManager problems specific to Novell Cluster Services.
To remove the old plug-in, start iManager and then perform the following steps:
Click thebutton, then click .
Click, then select .
IMPORTANT:If you have installed the iManager plug-in for Archive and Versioning Services, you must remove it. If you have installed the Storage Management plug-in (nssmgmt.npm) and/or the Shared Storage plug-in (storagemgmt.npm), you must remove and resinstall them.
Select these additional plug-ins to remove them.
Click Uninstall to remove the selected plug-ins.
Sometimes the plug-ins may not be correctly removed. To ensure that the plug-ins are removed, complete the following steps for iManager on either NetWare or Linux as indicated:
Go to the sys:\tomcat\4\webapps\nps\portal\modules directory on NetWare, or the /var/opt/novell/tomcat4/webapps/nps/portal/modules directory on Linux, and ensure the following folders are no longer present. If the folders are present, delete them.
Go to the sys:\tomcat\4\webapps\nps\WEB-INF directory on NetWare, or the /var/opt/novell/tomcat4/webapps/nps/WEB-INF directory on Linux, and ensure the following files are no longer present. If the files are present, delete them.
Go to the sys:\tomcat\4\webapps\nps\WEB-INF\modules directory on NetWare, or the /var/opt/novell/tomcat4/webapps/nps/WEB-INF/modules directory on Linux, and ensure the following folders are no longer present. If the files are present, delete them.
Go to the sys:\tomcat\4\webapps\nps\WEB-INF\lib directory on NetWare, or the /var/opt/novell/tomcat4/webapps/nps/WEB-INF/lib directory on Linux, and ensure that the following folders are no longer present. If the folders are present, delete them. (The * character used here is a wildcard character used to represent additional characters in the filename, and is not actually part of the filename.)
Go to the sys:\tomcat\4\webapps\nps\packages directory on NetWare, or the /var/opt/novell/tomcat4/webapps/nps/packages directory on Linux, and ensure the following files are no longer present. If the files are present, delete them.
Go to the SYS:\tomcat\4\work\STANDALONE\LOCALHOST\NPS\portal\modules directory on NetWare, or the /var/opt/novell/tomcat4/work/Standalone/localhost/nps/portal/modules directory on Linux, and ensure that the following folders are no longer present. If the folders are present, delete them.
Go to the sys:\tomcat\4\webapps\nps\UninstallerData directory on NetWare, or the /var/opt/novell/tomcat4/webapps/nps/UninstallerData directory on Linux, and ensure that the following folders are no longer present. If the folders are present, delete them.
To install the new plug-ins:
Go to the iManager plug-in download site and download the iManager plug-ins to a directory.
In iManager, click thebutton, select , select , then click .
Browse to the directory where you downloaded the plug-ins and add the storage management (storagemgmt.npm) plug-in by selecting it, clicking , and then clicking .
Repeat Step 3 to add the NSS plug-in (nssmgmt.npm) and the Novell Cluster Services plug-ins (ncsmgmt.npm).
Select the Storage Management plug-in (storagemgmt.npm), click , and then click on the message screen with the text informing you to restart your Web server.
Click Step 5 for both the NSS plug-in (nssmgmt.npm) and the Novell Cluster Services plug-in (ncsmgmt.npm).and then repeat
The plug-ins must be installed in the following order:
Restart the Apache Web server.
One way to do this is by restarting your server.
During the installation and uninstallation processes, a message might appear stating that requisite software is not installed and asking you if you want to resolve conflicts. Click, and then on the Dependency Conflict screen, select , click -- , and then .
You might also encounter software dependency conflicts unrelated to Novell Business Continuity Clustering or Novell Cluster Services™ software. You should resolve these conflicts on a case-by-case basis.
The drive mappings to all NetWare mapped volumes are removed if you enter invalid credentials for administrator/password in the BCC install wizard.
Clusters containing NetWare and Linux* nodes are only supported in a BCC as a temporary means to convert a cluster from NetWare to Linux. Part of the temporary conversion state includes a restriction that only one mixed cluster can exist in your BCC. For example, Cluster A can have both NetWare and Linux nodes, but Cluster B cannot. All nodes in Cluster B must be either NetWare or Linux.
The same restrictions that apply to migrating or failing over resources between nodes within a single cluster also apply to migrating or failing over resources between clusters in a mixed BCC. You can only migrate or fail over NSS pool/volume resources between clusters in a mixed BCC. See Converting a NetWare Cluster to Linux in the OES Novell Cluster Services 1.8.2 Administration Guide for Linux
Do not install IDM 3.x management utilities with the IDM 2.x engine. If you do, the IDM Driver for eDirectory will be converted to version 3.x, and the IDM 2.x engine will no longer be able to get the driver information.
When existing clusters are configured and enabled within the same business continuity cluster, the volume IDs (VOLIDs) for the existing shared volumes might also share the same VOLIDs. To correct this problem, manually edit the load script for each volume that has been enabled for business continuity and change the VOLIDs to unique values for each volume in the business continuity cluster.
When you enable a cluster resource for business continuity, that resource might take up to 30 seconds to appear as enabled for business continuity in iManager. After Business Continuity Clustering refreshes its status information, the resource will appear as enabled.
Due to MSAP (Multiple Server Activation Protocol), the NSS pools on a cluster might take up to 30 seconds per pool to fail over from a cluster to one node in another cluster. If you have several pools in a cluster, the failover process will be faster if those pools fail over to multiple nodes (fan-out failover) rather than to just a single node.
If you are migrating a pool to a cluster in another tree and you want to maintain that pool's volume trustee assignments, you must migrate the pool to a server with an eDirectory™ replica that holds all objects that have trustee assignments on any of the volumes in the pool. After migrating the pool to a server with an eDirectory replica, enter the following console command on that server for each volume in the pool:
This command updates all volume trustee assignments and should be run at night, on a weekend, or during a period of low network and disk utilization. Trustee assignments will not appear in management utilities until you run the command.
If you migrate the pool to a server in another tree without an eDirectory replica, within 90 days you must migrate that pool to a server with an eDirectory replica and then run the command for each volume.
Trustee assignments are always enforced, but after migrating a volume from a cluster in one tree to a cluster in another tree, volume trustee assignments might not be displayed correctly in ConsoleOne®, Novell Remote Manager (NRM), or on an NCP™ client. This issue exists when the migrated pool is active on a nonreplica server node.
The trustees are in place and correct. Users with trustee assignments from the original tree can map drives and access data with no issues. If a pool is migrated to a server node that contains a replica, the trustee assignments are presented correctly.
See Migrating Volume Trustee Assignments above for more information.
If you rename a volume on a shared pool in a business continuity cluster, the changed volume name will not replicate to a cluster in another eDirectory tree. This does not affect user access to the volume in either tree.
You cannot use iManager on Linux to set eDirectory credentials for BCC. You must use iManager on NetWare or Windows (the server must be in the same eDirectory tree), or use the Linux BCC command line interface from a shell prompt to set credentials.
After filling in the values on the SAN Management Script Details page and clicking Apply and OK, you are returned to the Resource Properties page (with the Business Continuity tab selected). You must click OK on the Resource Properties page or your script changes will not be saved.
Occasionally after migrating a resource to another cluster, the resource will be in an offline-primary state on the destination cluster. If this occurs, online the resource on the destination cluster using either iManager or cluster commands at the server console.
After upgrading from BCC 1.0 to BCC 1.1 the cluster and peer clusters in your BCC might not appear in the connections list in iManager. To work around this problem:
Deselect thecheck box in iManager and save your changes.
Re-enable Business Contintuity by selecting the peer clusters and selecting thecheck box.
For more information, see Configuring Clusters for Business Continuity in the Novell Business Continuity Clustering 1.1 Administration Guide for NetWare.
The node in each cluster where the IDM engine and drivers are running must be up before creating a new cluster resource in your BCC. This requirement does not apply for configuring existing cluster resources, just for creating new resources.
If you disable BCC for a cluster using either iManager or the Cluster Disable console command, BCC will also be disabled for those cluster resources that have been BCC-enabled. If you re-enable BCC for the cluster, you must re-enable each individual cluster resource that you want to be BCC-enabled.
This can be a time-consuming process if you have many BCC-enabled cluster resources. For this reason, you should use caution when disabling BCC for an entire cluster.
The Cluster Restart command currently does not work on NetWare clusters. To restart your cluster:
At the NetWare server console of a cluster server, enter unload ncscon.
Enter cluster restart.
Enter load ncscon.
This problem will be fixed for NetWare 6.5 Support Pack 7 and later. Unloading ncscon will then no longer be required.
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2007–2010 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.