This Readme identifies known issues for Business Continuity Clustering (BCC) 2.6 for your Open Enterprise Server (OES) 2023 servers that are running Novell Cluster Services (NCS).
Business Continuity Clustering supports up to four peer clusters that are running OES 2023 and Novell Cluster Services.
The BCC operating environment requires the versions of OES and NetIQ products listed in Table 1, with the latest patches applied.
Table 1 BCC Operating Environment
|
Supported Product |
For documentation, see: |
|---|---|
|
eDirectory 9.2.7 This product is included with OES 2023. |
eDirectory 9.2.7 documentation Web site on NetIQ.com |
|
Open Enterprise Server 2023 |
OES 2023 documentation Web site on MicroFocus.com |
|
Novell Cluster Services |
For information about clustering OES 2023 services and storage, see the product documentation on the OES 2023: OES Cluster Services for Linux Administration Guide |
|
iManager 3.2.6 This product is included with OES 2023. |
iManager 3.2.6 documentation Web site on NetIQ.com |
|
Clusters plug-in for iManager This product is included with OES 2023. |
|
|
Identity Manager 4.8.6 The credential to activate IDM is included in the BCC license. |
Identity_Manager_4.8.6 documentation Web site on NetIQ.com |
Beginning with OES 2018 SP1, Novell Business Continuity Cluster (BCC) is available as a pattern in the OES installation pattern list. However, BCC continues to be a separate product with its own license.
Download the Open Enterprise Server 2023 through Downloads. Apply the latest OES 2023 maintenance patches on all nodes in every peer cluster. Patches are available through the OES 2023 patch channel.
In addition, you must download the following product:
Identity_Manager_4.8 for OES 2023
The credential that you need to use Identity Manager drivers beyond the evaluation period is found in the BCC license.
You must apply all maintenance patches for Identity_Manager_4.8.6 on the Identity Manager node in each of the peer clusters before you install or upgrade BCC on any of the nodes in any peer cluster. Patches are available on Micro Focus Patch Finder.
This section identifies known issues for BCC on OES 2023 clusters running NCS.
BCC enabled cluster resource migration fails between the BCC peer clusters. The resource goes to unassigned state after migration. To troubleshoot this issue, before initiating the migration process, perform nlvm rescan on all the nodes of the target cluster, where the BCC cluster resource has to be up and running.
In OES 2023 with BCC installed and configured, enabling only the TLS v1.3 protocol in the sfcb.cfg file makes the BCC cluster connections to break. To avoid this and maintain stable connections, enable TLS v1.2 as well.
After the set up of BCC and enabling it on peer clusters, the cluster view report on one of the node in the first cluster shows only one peer cluster as configured instead of showing all the peer clusters. However, the cluster view report on all the other nodes correctly shows all the peer clusters configured. To view the correct cluster view report on the node in first cluster where the issue is seen, execute the command cluster refresh -p.
When a BCC-enabled pool cluster resource is brought online in a peer cluster other than where it was originally created, you cannot add a new volume on the pool. The volume is created on the disk, but the Volume object fails to be added to Novell eDirectory with Error 613: Error adding volume to NDS.
We recommend that you create only one volume per pool cluster resource. If you need to add a volume on a BCC-enabled pool cluster resource, you must BCC-migrate the resource back to the peer cluster where the pool was originally created.
In some disaster situations, it is possible that the pool cluster resource has been permanently relocated to the current peer cluster. To cluster-enable the pool in its current cluster, see Permanently Relocating a Cluster Resource to a Peer Cluster in the OES 2023: BCC Administration Guide.
In the BCC 2.6 release, multiple-tree configurations of business continuity clusters are not supported. All peer clusters must reside in the same tree.
BCC 2.6 does not support mixed peer clusters of NetWare and Linux. A cluster in mixed-mode that contains both NetWare and Linux servers is supported in a BCC peer cluster only as a temporary means to convert a cluster from NetWare to Linux. The cluster is considered a NetWare cluster, and only NetWare nodes are enabled for BCC. Resources running on Linux nodes in the mixed cluster cannot fail over to a peer cluster.
Before you begin the conversion of a BCC from NetWare to Linux, ensure that you understand the sequence of tasks and the limitations of working in mixed-mode in a BCC. For information, see “Converting BCC Clusters from NetWare to Linux” in the OES 2023: BCC Administration Guide.
This Readme lists all known issues for BCC for OES 2023. For information about installing and managing BCC, see the OES 2023: BCC Administration Guide.
For information about installing and managing Identity_Manager_4.8.6, see the Identity_Manager_4.8.6_Engine documentation Web site.
For information about iManager 3.2.6, see the iManager documentation Web site.
For information about OES 2023 services, see the OES 2023 documentation Web site.
For information about OES Cluster Services for Linux, see the OES 2023: OES Cluster Services for Linux Administration Guide.
© Copyright 2022 Micro Focus or one of its affiliates.
The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are as may be set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.