4.6 Software Requirements for Cluster Services

Ensure that your system meets the following software requirements for installing and managing OES Cluster Services:

4.6.1 Open Enterprise Server 2023

OES Cluster Services for Linux supports Open Enterprise Server 2023. OES Cluster Services is one of the OES Services patterns.

We recommend having uniform nodes in the cluster. The same release version of OES must be installed and running on each node in the cluster.

Mixed-mode clusters with different operating system platforms are supported during rolling cluster upgrades or conversions for the following scenarios:

Upgrading from

See:

OES 11 SP2 or later

Section 7.0, Upgrading OES Clusters

NetWare 6.5 SP8

OES 2015 SP1: Novell Cluster Services NetWare to Linux Conversion Guide

4.6.2 OES Cluster Services

OES Cluster Services is required for creating and managing clusters and shared resources on your OES servers. Cluster Services is one of the OES Services patterns on OES.

4.6.3 NetIQ eDirectory 9.2.6

NetIQ eDirectory 9.1 is required for managing the Cluster object and Cluster Node objects for Cluster Services. eDirectory must be installed and running in the same tree where you create the cluster. eDirectory can be installed on any node in the cluster, on a separate server, or in a separate cluster. You can install an eDirectory master replica or replica in the cluster, but it is not required to do so for Cluster Services.

For information about using eDirectory, see NetIQ eDirectory Administration Guide.

IMPORTANT:Because the cluster objects and their settings are stored in eDirectory, eDirectory must be running and working properly whenever you modify the settings for the cluster or the cluster resources.

In addition, ensure that your eDirectory configuration meets the following requirements:

eDirectory Tree

All servers in the cluster must be in the same eDirectory tree.

eDirectory Context

If you are creating a new cluster, the eDirectory context where the new Cluster object will reside must be an existing context. Specifying a new context during the Cluster Services configuration does not create a new context.

Cluster Object Container

We recommend that the Cluster object and all of its member Server objects and Storage objects be located in the same OU context. Multiple Cluster objects can co-exist in the same eDirectory container. In iManager, use Directory Administration > Create Object to create a container for the cluster before you configure the cluster.

If the servers in the cluster are in separate eDirectory containers, the user that administers the cluster must have rights to the cluster server containers and to the containers where any cluster-enabled pool objects are stored. You can do this by adding trustee assignments for the cluster administrator to a parent container of the containers where the cluster server objects reside. See eDirectory Rights in the NetIQ eDirectory Administration Guide for more information.

Renaming a pool involves changing information in the Pool object in eDirectory. If Server objects for the cluster nodes are in different containers, you must ensure that the shared pool is active on a cluster node that has its NCP server object in the same context as the Pool object of the pool you are going to rename. For information about renaming a shared pool, see Section 12.12, Renaming a Clustered NSS Pool.

Cluster Objects Stored in eDirectory

Table 4-1 shows the cluster objects that are automatically created and stored in eDirectory under the Cluster object () after you create a cluster:

Table 4-1 Cluster Objects

Icon

eDirectory Object

Master_IP_Address_Resource

Cluster Node object (servername)

Resource Template objects. There are some default templates:

  • AV_Template
  • DHCP_Template
  • DNS_Template
  • Generic_FS_Template
  • Generic_IP_Service
  • iFolder_Template
  • iPrint_Template
  • MySQL_Template
  • Samba_Template
  • Xen_Template
  • XenLive_Template
  • CIS_Scale_Template
  • CIS_Template

Table 4-2 shows the cluster objects that are added to eDirectory when you add nodes or create cluster resources:

Table 4-2 Cluster Resource Objects

Icon

eDirectory Object

Cluster Node object (servername)

NSS Pool Resource object (poolname_SERVER)

Resource object

Table 4-3 shows the cluster objects that are added to eDirectory when you add nodes or create cluster resources in a OES Business Continuity Cluster, which is made up of OES Cluster Services clusters:

Table 4-3 BCC Cluster Resource Objects

Icon

eDirectory Object

BCC NSS Pool Resource object

BCC Resource Template object

BCC Resource object

LDAP Server List

If eDirectory is not installed on a node, it looks to the LDAP server list for information about which LDAP server to use. As a best practice, you should list the LDAP servers in the following order:

  • Local to the cluster

  • Closest physical read/write replica

For information about configuring a list of LDAP servers for the cluster, see Section 8.13.1, Changing the Administrator Credentials or LDAP Server IP Addresses for a Cluster.

4.6.4 SLP

SLP (Service Location Protocol) is a required component for Novell Cluster Services on Linux when you are using NCP to access file systems on cluster resources. NCP requires SLP for the ncpcon bind and ncpcon unbind commands in the cluster load and unload scripts. For example, NCP is needed for NSS volumes and for NCP volumes on Linux POSIX file systems.

SLP is not automatically installed when you select Novell Cluster Services. SLP is installed as part of the eDirectory configuration during the OES installation. You can enable and configure SLP on the eDirectory Configuration - NTP & SLP page. For information, see Specifying SLP Configuration Options in the OES 23.4: Installation Guide.

When the SLP daemon (slpd) is not installed and running on a cluster node, any cluster resource that contains the ncpcon bind command goes comatose when it is migrated or failed over to the node because the bind cannot be executed without SLP.

The SLP daemon (slpd) must also be installed and running on all nodes in the cluster when you manage the cluster or cluster resources.

NCP Server re-registers cluster resource virtual NCP servers with SLP based on the setting for the eDirectory advertise-life-time (n4u.nds.advertise-life-time) parameter. The parameter is set by default to 3600 seconds (1 hour) and has a valid range of 1 to 65535 seconds.

You can use the ndsconfig set command to set the n4u.nds.advertise-life-time parameter. To reset the parameter in a cluster, perform the following tasks on each node of the cluster:

  1. Log in to the node as the root user, then open a terminal console.

  2. Take offline all of the cluster resources on the node, or cluster migrate them to a different server. At a command prompt, enter

    cluster offline <resource_name>

or

cluster migrate <resource_name> <target_node_name>

  3. Modify the eDirectory SLP advertising timer parameter (n4u.nds.advertise-life-time), then restart ndsd and slpd. At a command prompt, enter

    ndsconfig set n4u.nds.advertise-life-time=<value_in_seconds>

rcndsd restart

rcslpd restart

  4. Bring online all of the cluster resources on the node, or cluster migrate the previously migrated resources back to this node.

    cluster online <resource_name>

or

cluster migrate <resource_name> <node_name>

  5. Repeat the previous steps on the other nodes in the cluster.

OpenSLP stores the registration information in cache. You can configure the SLP Directory Agents to preserve a copy of the database when the SLP daemon (slpd) is stopped or restarted. This allows SLP to know about registrations immediately when it starts.

For more information about configuring and managing SLP, see Configuring OpenSLP for eDirectory in the NetIQ eDirectory Administration Guide.

4.6.5 iManager 3.2.6

iManager is required for configuring and managing clusters on OES.

iManager must be installed on at least one computer in the same tree as the cluster. It can be installed in the cluster or not in the cluster. For information about using iManager, see the iManager documentation website.

For SFCB (Small Footprint CIM Broker) and CIMOM requirements, see Section 4.6.8, SFCB and CIMOM.

For browser configuration requirements, see Web Browser.

4.6.6 Clusters Plug-in for iManager

The Clusters plug-in for iManager provides the Clusters role where you can manage clusters and cluster resources with OES Cluster Services. The plug-in can be used on all operating systems supported by iManager and iManager Workstation.

The following components must be installed in iManager:

If iManager is also installed on the server, these files are automatically installed in iManager when you install Cluster Services.

The Clusters plug-in also provides an integrated management interface for OES Business Continuity Clustering (BCC). The additional interface is present only if BCC is installed on the server. See the following table for information about the versions of BCC that are supported. BCC is sold separately from OES. For purchasing information, see the BCC product page.

BCC Release

OES Support

iManager and Clusters Plug-In

BCC 2.6

OES 2018 SP1 or later

Novell iManager 3.1 or later

Requires the Clusters plug-in for OES 2018 SP1 or later with the latest patches applied.

See the BCC administration guide.

4.6.7 Storage-Related Plug-Ins for iManager

In OES 11 and later, the following storage-related plug-ins for iManager share code is common in the storagemgmt.rpm file:

Product

Plug-In

NPM File

OES CIFS

File Protocols > CIFS

cifsmgmt.rpm

OES Cluster Services

Clusters

ncsmgmt.rpm

OES Distributed File Services

Distributed File Services

dfsmgmt.rpm

OES Storage Services

Storage

nssmgmt.rpm

These additional plug-ins are needed when working with the NSS file system. Ensure that you include the common storagemgmt.rpm plug-in module when installing any of these storage-related plug-ins.

IMPORTANT:If you use more than one of these plug-ins, you should install, update, or remove them all at the same time to ensure that the common code works for all plug-ins.

Ensure that you uninstall the old version of the plug-ins before you attempt to install the new versions of the plug-in files.

The plug-in files are included on the installation disk. The latest storage-related plug-ins can be downloaded as a single zipped download file from the Downloads website. For information about installing plug-ins in iManager, see Downloading and Installing Plug-in Modules in the NetIQ iManager Administration Guide.

For information about working with storage-related plug-ins for iManager, see Understanding Storage-Related Plug-Ins in the OES 23.4: NSS File System Administration Guide for Linux.

4.6.8 SFCB and CIMOM

The Small Footprint CIM Broker (SFCB) replaces OpenWBEM for CIMOM activities in OES 11 and later. SFCB provides the default CIMOM and CIM clients. When you install any OES components that depend on WBEM, SFCB and all of its corresponding packages are installed with the components. See Small Footprint CIM Broker (SFCB) in the OES 23.4: Planning and Implementation Guide.

IMPORTANT:SFCB must be running and working properly whenever you modify the settings for the cluster or the cluster resources.

Port 5989 is the default setting for Secure HTTP (HTTPS) communications. If you are using a firewall, the port must be opened for CIMOM communications. Ensure that the CIMOM broker daemon is listening on port 5989. Log in as the root user on the cluster master node, open a terminal console, then enter the following at the command prompt:

netstat -an |grep -i5989

The Clusters plug-in (and all other storage-related plug-ins) for iManager require CIMOM connections for tasks that transmit sensitive information (such as a user name and password) between iManager and the _admin volume on the OES server that you are managing. Typically, CIMOM is running, so this should be the normal condition when using the server. CIMOM connections use Secure HTTP (HTTPS) for transferring data, and this ensures that sensitive data is not exposed.

IMPORTANT:SFCB is automatically PAM-enabled for Linux User Management (LUM) as part of the OES installation. Users not enabled for LUM cannot use the CIM providers to manage OES. The user name that you use to log in to iManager when you manage a cluster and the BCC cluster must be an eDirectory user name that has been LUM-enabled.

For more information about the permissions and rights needed by the administrator user, see Section 4.1, Cluster Administration Requirements.

IMPORTANT:If you receive file protocol errors, it might be because SFCB is not running.

You can use the following commands to start, stop, or restart SFCB:

To perform this task

At a command prompt, enter as the root user

To start SFCB

rcsblim-sfcb start or systemctl start sblim-sfcb.service

To stop SFCB

rcsblim-sfcb stop or systemctl stop sblim-sfcb.service

To check SFCB status

rcsblim-sfcb status or systemctl status sblim-sfcb.service

To restart SFCB

rcsblim-sfcb restart or systemctl restart sblim-sfcb.service

For more information, see Web Based Enterprise Management using SFCB in the SUSE Linux Enterprise Server Administration Guide.

4.6.9 OES Credential Store

OES Cluster Services requires OES Credential Store to be installed and running on each node in the cluster.

To check that OES Credential Store is running correctly, at the command prompt enter oescredstore -l as the root user.

4.6.10 Web Browser

For information about supported web browsers for iManager, see System Requirements for iManager Server in the NetIQ iManager Installation Guide.

The Clusters plug-in for iManager might not operate properly if the highest priority Language setting for your web browser is set to a language other than one of the supported languages in iManager. To view a list of supported languages and codes in iManager, select the Preferences tab, click Language. The language codes are Unicode (UTF-8) compliant.

To avoid display problems, in your web browser, select Tools > Options > Languages, and then set the first language preference in the list to a supported language. You must also ensure the Character Encoding setting for the browser is set to Unicode (UTF-8) or ISO 8859-1 (Western, Western European, West European).

  • In a Mozilla browser, select View > Character Encoding, then select the supported character encoding setting.

  • In an Internet Explorer browser, select View > Encoding, then select the supported character encoding setting.