Novell Cluster ServicesTM 1.8.7 For Linux Administration Guide
Open Enterprise Server
novdocx (en) 7 January 2010
2 SP2
March 15, 2010
OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide
Legal Notices
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. See the
Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on
exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export
approvals.
12OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide
About This Guide
This guide describes how to install, upgrade, configure, and manage Novell® Cluster ServicesTM. It
is intended for cluster administrators and is divided into the following sections:
Chapter 1, “Overview of Novell Cluster Services,” on page 15
Chapter 2, “What’s New,” on page 23
Chapter 3, “Installing and Configuring Novell Cluster Services on OES 2 Linux,” on page 27
Chapter 4, “Upgrading OES 2 Linux Clusters,” on page 53
Chapter 5, “Upgrading OES 1 Linux Clusters to OES 2 Linux,” on page 55
Chapter 6, “Converting NetWare 6.5 Clusters to OES 2 Linux,” on page 59
Chapter 7, “Configuring Cluster Policies and Priorities,” on page 91
Chapter 8, “Managing Clusters,” on page 97
Chapter 9, “Configuring and Managing Cluster Resources,” on page 117
Chapter 10, “Configuring Cluster Resources for Shared NSS Pools and Volumes,” on page 133
novdocx (en) 7 January 2010
Chapter 11, “Configuring Cluster Resources for Shared Linux POSIX Volumes,” on page 157
Chapter 12, “Configuring Novell Cluster Services in a Xen Virtualization Environment,” on
page 181
Chapter 13, “Troubleshooting Novell Cluster Services,” on page 195
Appendix A, “Console Commands for Novell Cluster Services,” on page 203
Appendix B, “Files for Novell Cluster Services,” on page 209
Appendix C, “Comparing Novell Cluster Services for Linux and NetWare,” on page 213
Appendix D, “Comparing Clustering Support for OES 2 Services on Linux and NetWare,” on
page 219
Audience
This guide is intended for intended for anyone involved in installing, configuring, and managing
Novell Cluster Services.
Feedback
We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comments feature at the bottom of each page of the
online documentation, or go to www.novell.com/documentation/feedback.html and enter your
comments there.
Documentation Updates
The latest version of this Novell Cluster Services for Linux Administration Guide is available on the
OES 2 documentation Web site (http://www.novell.com/documentation/oes2/cluster-services.html).
About This Guide13
Additional Documentation
For information about creating cluster resources for various Linux services on your OES 2 Linux
server, refer to the clustering sections in the individual guides. See the “Clustering Linux Services”
list on the Clustering (High Availability) Documentation Web site (http://www.novell.com/
documentation/oes2/cluster-services.html#clust-config-resources).
®
For information about Novell Cluster Services 1.8.5 for NetWare
, see the “Clustering NetWare
Services” list on the NetWare 6.5 SP8 Clustering (High Availability) Documentation Web site (http:/
/www.novell.com/documentation/nw65/cluster-services.html#clust-config-resources).
Documentation Conventions
In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and
items in a cross-reference path.
®
A trademark symbol (
, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party
trademark.
novdocx (en) 7 January 2010
14OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide
1
Overview of Novell Cluster
novdocx (en) 7 January 2010
Services
Novell® Cluster ServicesTM is a server clustering system that ensures high availability and
manageability of critical network resources including data, applications, and services. It is a multinode clustering product for Linux* that is enabled for Novell eDirectory
failback, and migration (load balancing) of individually managed cluster resources.
Section 1.1, “Why Should I Use Clusters?,” on page 15
Section 1.2, “Benefits of Novell Cluster Services,” on page 15
Section 1.3, “Product Features,” on page 16
Section 1.4, “Clustering for High-Availability,” on page 16
Section 1.5, “Shared Disk Scenarios,” on page 18
1.1 Why Should I Use Clusters?
A server cluster is a group of redundantly configured servers that work together to provide highly
available access for clients to important applications, services, and data while reducing unscheduled
outages. The applications, services, and data are configured as cluster resources that can be failed
over or cluster migrated between servers in the cluster. For example, when a failure occurs on one
node of the cluster, the clustering software gracefully relocates its resources and current sessions to
another server in the cluster. Clients connect to the cluster instead of an individual server, so users
are not aware of which server is actively providing the service or data. In most cases, users are able
to continue their sessions without interruption.
TM
and supports failover,
1
Each server in the cluster runs the same operating system and applications that are needed to provide
the application, service, or data resources to clients. Shared devices are connected to and mounted
on only one server at a time. Clustering software monitors the health of each of the member servers
by listening for its heartbeat, a simple message that lets the others know it is alive.
The cluster’s virtual server provides a single point for accessing, configuring, and managing the
cluster servers and resources. The virtual identity is bound to the cluster’s master node and remains
with the master node regardless of which member server acts the master node. The master server
also keeps information about each of the member servers and the resources they are running. If the
master server fails, the control duties are passed to another server in the cluster.
1.2 Benefits of Novell Cluster Services
Novell Cluster Services provides high availability from commodity components. You can configure
up to 32 OES 2 Linux servers in a high-availability cluster, where resources can be dynamically
relocated to any server in the cluster. Resources can be configured to automatically fail over to one
or multiple different preferred servers in the event of a server failure. In addition, costs are lowered
through the consolidation of applications and operations onto a cluster.
Novell Cluster Services allows you to manage a cluster from a single point of control and to adjust
resources to meet changing workload requirements (thus, manually “load balance” the cluster).
Resources can also be cluster migrated manually to allow you to troubleshoot hardware. For
Overview of Novell Cluster Services
15
example, you can move applications, Web sites, and so on to other servers in your cluster without
waiting for a server to fail. This helps you to reduce unplanned service outages and planned outages
for software and hardware maintenance and upgrades.
Novell Cluster Services clusters provide the following benefits over standalone servers:
Increased availability of applications, services, and data
Improved performance
Lower cost of operation
Scalability
Disaster recovery
Data protection
Server consolidation
Storage consolidation
1.3 Product Features
novdocx (en) 7 January 2010
Novell Cluster Services includes several important features to help you ensure and manage the
availability of your network resources:
Support for shared SCSI, iSCSI, or Fibre Channel storage subsystems. Shared disk fault
tolerance can be obtained by implementing RAID on the shared disk subsystem.
Multi-node all-active cluster (up to 32 nodes). Any server in the cluster can restart resources
(applications, services, IP addresses, and file systems) from a failed server in the cluster.
A single point of administration through the browser-based Novell iManager cluster
configuration and monitoring GUI. iManager also lets you remotely manage your cluster.
The ability to tailor a cluster to the specific applications and hardware infrastructure that fit
your organization.
Dynamic assignment and reassignment of server storage as needed.
The ability to use e-mail to automatically notify administrators of cluster events and cluster
state changes.
1.4 Clustering for High-Availability
A Novell Cluster Services for Linux cluster consists of the following components:
2 to 32 OES 2 Linux servers, each containing at least one local disk device.
Novell Cluster Services software running on each Linux server in the cluster.
A shared disk subsystem connected to all servers in the cluster (optional, but recommended for
most configurations).
Equipment to connect servers to the shared disk subsystem, such as one of the following:
High-speed Fibre Channel cards, cables, and switches for a Fibre Channel SAN
Ethernet cards, cables, and switches for an iSCSI SAN
SCSI cards and cables for external SCSI storage arrays
16OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide
The benefits that Novell Cluster Services provides can be better understood through the following
Fibre Channel Switch
Web Server 1Web Server 2Web Server 3
Shared Disk
System
Web Site E
Web Site F
Web Site C
Web Site D
Web Site A
Web Site B
Fibre Channel Switch
Web Server 1Web Server 2Web Server 3
Shared Disk
System
Web Site B
Web Site E
Web Site F
Web Site A
Web Site C
Web Site D
scenario.
Suppose you have configured a three-server cluster, with a Web server installed on each of the three
servers in the cluster. Each of the servers in the cluster hosts two Web sites. All the data, graphics,
and Web page content for each Web site is stored on a shared disk system connected to each of the
servers in the cluster. Figure 1-1 depicts how this setup might look.
Figure 1-1 Three-Server Cluster
novdocx (en) 7 January 2010
During normal cluster operation, each server is in constant communication with the other servers in
the cluster and performs periodic polling of all registered resources to detect failure.
Suppose Web Server 1 experiences hardware or software problems and the users who depend on
Web Server 1 for Internet access, e-mail, and information lose their connections. Figure 1-2 shows
how resources are moved when Web Server 1 fails.
Figure 1-2 Three-Server Cluster after One Server Fails
Web Site A moves to Web Server 2 and Web Site B moves to Web Server 3. IP addresses and
certificates also move to Web Server 2 and Web Server 3.
Overview of Novell Cluster Services17
When you configured the cluster, you decided where the Web sites hosted on each Web server would
go if a failure occurred. You configured Web Site A to move to Web Server 2 and Web Site B to
move to Web Server 3. This way, the workload once handled by Web Server 1 is evenly distributed.
When Web Server 1 failed, Novell Cluster Services software did the following:
Detected a failure.
Remounted the shared data directories (that were formerly mounted on Web server 1) on Web
Server 2 and Web Server 3 as specified.
Restarted applications (that were running on Web Server 1) on Web Server 2 and Web Server 3
as specified.
Transferred IP addresses to Web Server 2 and Web Server 3 as specified.
In this example, the failover process happened quickly and users regained access to Web site
information within seconds, and in most cases, without logging in again.
Now suppose the problems with Web Server 1 are resolved, and Web Server 1 is returned to a
normal operating state. Web Site A and Web Site B will automatically fail back, or be moved back to
Web Server 1, and Web Server operation will return to the way it was before Web Server 1 failed.
novdocx (en) 7 January 2010
Novell Cluster Services also provides resource migration capabilities. You can move applications,
Web sites, etc. to other servers in your cluster without waiting for a server to fail.
For example, you could have manually moved Web Site A or Web Site B from Web Server 1 to
either of the other servers in the cluster. You might want to do this to upgrade or perform scheduled
maintenance on Web Server 1, or just to increase performance or accessibility of the Web sites.
1.5 Shared Disk Scenarios
Typical cluster configurations normally include a shared disk subsystem connected to all servers in
the cluster. The shared disk subsystem can be connected via high-speed Fibre Channel cards, cables,
and switches, or it can be configured to use shared SCSI or iSCSI. If a server fails, another
designated server in the cluster automatically mounts the shared disk directories previously mounted
on the failed server. This gives network users continuous access to the directories on the shared disk
subsystem.
18OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide
1.5.1 Using Fibre Channel Storage Systems
Network
Interface
Card(s)
Fibre Channel Switch
Network Hub
Fibre
Channel
Card(s)
Server 1Server 2Server 3Server 4Server 5Server 6
Shared Disk
System
Fibre Channel provides the best performance for your storage area network (SAN). Figure 1-3
shows how a typical Fibre Channel cluster configuration might look.
iSCSI is an alternative to Fibre Channel that can be used to create a lower-cost SAN with Ethernet
equipment. Figure 1-4 shows how a typical iSCSI cluster configuration might look.
Figure 1-4 Typical iSCSI Cluster Configuration
novdocx (en) 7 January 2010
20OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide
1.5.3 Using Shared SCSI Storage Systems
Network
Interface
Card
Network
Interface
Card
Network Hub
SCSI
Adapter
SCSI
Adapter
Server 1Server 2
Shared Disk
System
You can configure your cluster to use shared SCSI storage systems. This configuration is also a
lower-cost alternative to using Fibre Channel storage systems. Figure 1-5 shows how a typical
shared SCSI cluster configuration might look.
22OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide
2
What’s New
This section describes changes and enhancements that were made to Novell® Cluster ServicesTM for
Linux since the initial release of Novell Open Enterprise Server (OES) 2 Linux.
Section 2.1, “What’s New (January 2010),” on page 23
Section 2.2, “What’s New (OES 2 SP2),” on page 23
Section 2.3, “What’s New (OES 2 SP1),” on page 25
Section 2.4, “What’s New (OES 2),” on page 26
2.1 What’s New (January 2010)
The January 2010 patch for OES 2 SP1 Linux contains bug fixes for Novell Cluster Services and
Novell Business Continuity Clustering 1.2 for OES 2 SP1 Linux.
The January 2010 patch for OES 2 SP2 Linux contains bug fixes for Novell Cluster Services and
adds support for Novell Business Continuity Clustering 1.2.1 for OES 2 SP2 Linux.
novdocx (en) 7 January 2010
2
2.2 What’s New (OES 2 SP2)
In addition to bug fixes, the following changes and enhancements were made for Novell Cluster
Services for Linux in OES 2 SP2.
Section 2.2.1, “Improved Error Reporting,” on page 23
Section 2.2.2, “Improved Time Calculations,” on page 23
Section 2.2.3, “Specifying the Size of the SBD Partition,” on page 24
Section 2.2.4, “Customizing Translation Syntax,” on page 24
Section 2.2.5, “Migration Tool Support for Cluster Configurations,” on page 24
Section 2.2.6, “New iFolder Resource Template,” on page 24
Section 2.2.7, “Removed MPK Calls from the Code,” on page 24
Section 2.2.8, “Cluster Restart Is No Longer Required in a Rolling Cluster Upgrade,” on
page 24
2.2.1 Improved Error Reporting
This release provides improved error reporting for file protocol errors.
2.2.2 Improved Time Calculations
This release improves the way time is calculated so that the inter-packet gap between two heartbeat
packets is reduced.
This means that you will observe an increase in the instances of packets incrementing the 0x (less
than one second) counter, and a decrease in the instances of packets incrementing the 1x (between
one second and two seconds) counter.
When you configure the SBD partition during the cluster configuration of a new cluster (as
described in “Configuring a New Cluster” on page 48), you can now specify the size of the partition.
2.2.4 Customizing Translation Syntax
Beginning in OES 2 SP2, Novell Cluster Services allows you to customize the translation syntax
that is used for load and unload scripts in mixed-platform situations by defining new syntax
translations in the
create. The
processes them in addition to the normal translations in the Cluster Translation Library. For
information, see Section 6.7, “Customizing the Translation Syntax for Converting Load and Unload
Scripts,” on page 87.
/var/opt/novell/ncs/customized_translation_syntax
clstrlib.py
script reads the additional translation syntax from the syntax file, and
file that you
novdocx (en) 7 January 2010
2.2.5 Migration Tool Support for Cluster Configurations
Support was added for migrating services and data in cluster configurations by using the OES 2 SP2
Migration Tool. For instructions on using the Migration Tool to migrate services and data, see the
OES 2 SP2: Migration Tool Administration Guide.
2.2.6 New iFolder Resource Template
The Novell iFolder 3.x resource template has been modified for OES 2 SP2. For information about
using the new template, see Section 4.3.1, “Updating the iFolder Resource Template,” on page 54.
2.2.7 Removed MPK Calls from the Code
MPK calls were removed from the Novell Cluster Services code. The MPK calls were replaced with
POSIX and Linux functions. These changes were made in support of the MPK calls being removed
from the Novell Storage Services
enhancements for the NSS file system.
TM
(NSS) file system software to achieve performance
2.2.8 Cluster Restart Is No Longer Required in a Rolling Cluster
Upgrade
In the OES 2 SP1 release, a cluster restart was required at the end of a rolling cluster upgrade in
order to properly update the names of the nodes, as described in Section 2.3.3, “Behavior Change for
Adding a Node,” on page 25. This issue was resolved in OES 2 SP2. The rolling cluster upgrade
process no long requires a cluster restart.
24OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide
2.3 What’s New (OES 2 SP1)
In addition to bug fixes, the following changes and enhancements were made for Novell Cluster
Services for Linux in OES 2 SP1.
Section 2.3.1, “Schema Extension,” on page 25
Section 2.3.2, “Installation by Container Administrator,” on page 25
Section 2.3.3, “Behavior Change for Adding a Node,” on page 25
Section 2.3.4, “Attribute NCS: GIPC Config Is No Longer Maintained,” on page 26
Section 2.3.5, “Support for Novell AFP for Linux,” on page 26
Section 2.3.6, “Support for Novell CIFS for Linux,” on page 26
Section 2.3.7, “Support for Domain Services for Windows,” on page 26
2.3.1 Schema Extension
The administrator of a Novell eDirectoryTM tree can now extend the schema for cluster objects
before clusters are installed in the tree. This allows container administrators to install Novell Cluster
Services without needing tree-level administrator rights. See Section 3.3, “Extending the eDirectory
Schema to Add Cluster Objects,” on page 40.
novdocx (en) 7 January 2010
2.3.2 Installation by Container Administrator
Container administrators can install Novell Cluster Services without needing tree-level
administrator rights. Make sure you have the rights needed for the install. See Section 3.4,
“Assigning Install Rights for Container Administrators,” on page 41.
2.3.3 Behavior Change for Adding a Node
In this release, a behavior change was made to address a deadlock defect. After adding a new node
to the cluster, the new node cannot be displayed in the Clusters plug-in to iManager until the
configd.py -init
IMPORTANT: A Novell Cluster Services patch is available in the patch channel and on the Novell
Downloads Web site (http://www.novell.com/downloads) that allows you to add a new node
seamlessly again on a Linux server. For cluster conversions, a cluster restart is still necessary after
all NetWare nodes have been removed from the cluster.
Run one of the following commands in order to make
correctly. It is okay to run
/opt/novell/ncs/bin/ncs-configd.py -init
or
script is run, or until the cluster is restarted.
cluster view
ncs-configd.py
on an active cluster.
display the new node’s name
ncs-
rcnovell-ncs restart
If you are converting a cluster from NetWare to Linux, you must restart the cluster instead so that
clstrlib.ko is reloaded.
2.3.4 Attribute NCS: GIPC Config Is No Longer Maintained
Beginning in OES 2 SP1 Linux, the attribute NCS:GIPC Config in the Cluster object is no longer
maintained. This applies to Linux clusters and mixed NetWare and Linux clusters.
2.3.5 Support for Novell AFP for Linux
This release supports Novell AFP (Apple* Filing Protocol) for Linux in combination with Novell
Storage Services
TM
(NSS) volumes on OES 2 SP1 Linux. See “Novell AFP for Linux” on page 32.
2.3.6 Support for Novell CIFS for Linux
This release supports Novell CIFS for Linux in combination with NSS volumes on OES 2 SP1
Linux. See “Novell CIFS for Linux” on page 32.
2.3.7 Support for Domain Services for Windows
This release supports using clusters in Domain Services for Windows contexts for OES 2 SP1
Linux. See “Novell Domain Services for Windows” on page 32.
2.4 What’s New (OES 2)
The following changes and enhancements were added to Novell Cluster Services for Linux in OES
2.
Resource Monitoring: See Section 9.6, “Enabling Monitoring and Configuring the Monitor
Script,” on page 123.
Support for Xen* Virtualization: See Chapter 12, “Configuring Novell Cluster Services in a
Xen Virtualization Environment,” on page 181.
26OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide
3
Installing and Configuring Novell
novdocx (en) 7 January 2010
Cluster Services on OES 2 Linux
Novell® Cluster ServicesTM can be installed during the Novell Open Enterprise Server (OES) 2
Linux installation or afterwards on an existing OES 2 Linux server.
For information about upgrading a cluster server from OES 1 SP2 Linux to OES 2 Linux, see
Chapter 5, “Upgrading OES 1 Linux Clusters to OES 2 Linux,” on page 55.
®
For information about converting a cluster server from NetWare
see Chapter 6, “Converting NetWare 6.5 Clusters to OES 2 Linux,” on page 59.
Section 3.1, “System Requirements for Novell Cluster Services,” on page 27
Section 3.2, “Novell Cluster Services Licensing,” on page 39
Section 3.3, “Extending the eDirectory Schema to Add Cluster Objects,” on page 40
Section 3.4, “Assigning Install Rights for Container Administrators,” on page 41
Section 3.5, “Installing Novell Cluster Services,” on page 42
Section 3.6, “Configuring Novell Cluster Services,” on page 46
Section 3.7, “Configuring Additional Administrators,” on page 52
Section 3.8, “What’s Next,” on page 52
6.5 SP7 or later to OES 2 Linux,
3
3.1 System Requirements for Novell Cluster
Services
Section 3.1.1, “Hardware Requirements,” on page 27
Section 3.1.2, “Software Requirements,” on page 28
Section 3.1.3, “Configuration Requirements,” on page 34
Section 3.1.4, “Shared Disk System Requirements,” on page 36
Section 3.1.5, “SAN Rules for LUN Masking,” on page 38
Section 3.1.6, “Using Device Mapper Multipath with Novell Cluster Services,” on page 38
3.1.1 Hardware Requirements
The following hardware requirements for installing Novell Cluster Services represent the minimum
hardware configuration. Additional hardware might be necessary depending on how you intend to
use Novell Cluster Services.
A minimum of two Linux servers, and not more than 32 servers in a cluster
At least 512 MB of memory on each server in the cluster
One non-shared device on each server to be used for the operating system
At least one network card per server in the same IP subnet
Installing and Configuring Novell Cluster Services on OES 2 Linux
27
In addition, each server must meet the requirements for Novell Open Enterprise Server 2 Linux. For
information, see “Meeting All Server Software and Hardware Requirements” in the OES 2 SP2:
Installation Guide.
NOTE: Although identical hardware for each cluster server is not required, having servers with the
same or similar processors and memory can reduce differences in performance between cluster
nodes and make it easier to manage your cluster. There are fewer variables to consider when
designing your cluster and failover rules if each cluster node has the same processor and amount of
memory.
If you have a Fibre Channel SAN, the host bus adapters (HBAs) for each cluster node should be
identical.
3.1.2 Software Requirements
Ensure that your system meets the following software requirements for installing and managing
Novell Cluster Services:
“Novell Open Enterprise Server 2 Linux” on page 28
novdocx (en) 7 January 2010
“Novell eDirectory 8.8” on page 29
“Novell iManager 2.7.3” on page 29
“EVMS” on page 30
“Linux POSIX File Systems” on page 30
“NSS File System on Linux” on page 31
“Dynamic Storage Technology Shadow Volume Pairs” on page 31
“NCP Server for Linux” on page 31
“Novell AFP for Linux” on page 32
“Novell CIFS for Linux” on page 32
“Novell Domain Services for Windows” on page 32
“OpenWBEM” on page 32
“SLP” on page 33
“Xen Virtualization Environments” on page 33
Novell Open Enterprise Server 2 Linux
Novell Cluster Services 1.8.5 (or later) for Linux supports Novell Open Enterprise Server 2 Linux or
later. OES 2 Linux must be installed and running on each cluster server in the cluster. Novell Cluster
Services is a component of the OES 2 services for OES 2 Linux.
You cannot mix two versions of OES 2 Linux in a single cluster except to support a rolling cluster
upgrade. For OES 2 Linux cluster upgrade information, see Chapter 4, “Upgrading OES 2 Linux
Clusters,” on page 53.
You cannot mix OES 2 Linux and OES 1 Linux in a single cluster except to support a rolling cluster
upgrade. For OES 1 Linux to OES 2 Linux upgrades, see Chapter 5, “Upgrading OES 1 Linux
Clusters to OES 2 Linux,” on page 55.
28OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide
You cannot mix OES 2 Linux and NetWare 6.5 SP7 (or later) in a single cluster except to support a
rolling cluster conversion. For cluster conversion information, see Chapter 6, “Converting NetWare
6.5 Clusters to OES 2 Linux,” on page 59.
Novell eDirectory 8.8
TM
Novell eDirectory
8.8 or later is required for managing the Cluster object and Cluster Node
objects for Novell Cluster Services. eDirectory must be installed somewhere in the same tree as 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 Novell Cluster Services.
For eDirectory configuration requirements, see “eDirectory Configuration” on page 34.
Novell iManager 2.7.3
Novell iManager 2.7.3 or later is required for configuring and managing clusters for OES 2 SP2.
iManager must be installed on at least one server in your tree.
NOTE: A February 3, 2009 update to the Clusters plug-in for OES 2 SP1 Linux is available that can
be used to manage the Novell Business Continuity Clustering (BCC) 1.2 for OES 2 SP1 Linux. You
can download the update from the Novell Downloads Web site (http://download.novell.com/). For
information about BCC 1.2, see BCC 1.2: Administration Guide for OES 2 SP1 Linux (http://
The OES 2 SP2 Linux release contains a Clusters plug-in that is required when using Novell
Business Continuity Clustering 1.2.1 for OES 2 SP2 Linux. For information about BCC 1.2.1, see
BCC 1.2.1: Administration Guide for OES 2 SP2 Linux (http://www.novell.com/documentation/bcc/
bcc121_admin_lx/data/bookinfo.html).
To use the Clusters role in iManager, the following storage-related plug-ins must be installed:
Clusters (
Common code for storage-related plug-ins (
The
storagemgmt.npm
ncsmgmt.npm
contains code in common with other storage-related plug-ins for OES 2
)
storagemgmt.npm
)
SP1:
ProductPlug-InNPM File
Novell Archive and Version ServicesArchive Versioning
Novell Apple* Filing Protocol (AFP) for OES 2
SP1 Linux and NetWare
Novell CIFS for OES 2 SP1 Linux and NetWareFile Protocols > CIFS
These additional plug-ins are needed when working with the NSS file system. Make sure that you
include the common
storagemgmt.npm
plug-in module when installing any of these storage-related
plug-ins.
Installing and Configuring Novell Cluster Services on OES 2 Linux29
IMPORTANT: If you use more than one of these plug-ins, you should install, update, or remove
them all at the same time to make sure the common code works for all plug-ins.
Make sure to uninstall the old version of the plug-ins before you attempt to install the new versions
of the plug-in files.
These iManager plug-ins support iManager 2.7.2 and later on all operating systems supported by
iManager and iManager Workstation.
The latest Novell storage-related plug-ins can be downloaded as a single zipped download file from
the Novell Downloads Web site (http://download.novell.com). For information about installing
plug-ins in iManager, see “Downloading and Installing Plug-in Modules” in the Novell iManager
2.7.3 Administration Guide.
To update storage-related plug-ins:
1 In iManager, uninstall the currently installed storage-related plug-ins.
2 Copy the new .npm files into the iManager plug-ins location, manually overwriting the older
version of the plug-in in the packages folder with the newer version of the plug-in.
novdocx (en) 7 January 2010
3 In iManager, install all of the storage-related plug-ins, or install the plug-ins you need, plus the
common code.
For information about working with storage-related plug-ins for iManager, see “Understanding
Storage-Related Plug-Ins” in the OES 2 SP2: NSS File System Administration Guide.
For browser configuration requirements, see “Web Browser” on page 36.
EVMS
EVMS (Enterprise Volume Management System) 2.5.5-24.54.5 or later is automatically installed on
the server when you install Novell Cluster Services. It provides the Cluster Segment Manager
(CSM) for shared cluster resources.
®
Updates to EVMS are received through the update channel for SUSE
Linux Enterprise Server 10
SP 2 or later. Make sure that you install the latest patches for EVMS before you create any cluster
resources for this server.
WARNING: EVMS administration utilities (
evms, evmsgui
, and
evmsn
) should not be running
when they are not being used. EVMS utilities lock the EVMS engine, which prevents other EVMSrelated actions from being performed. This affects both NSS and Linux POSIX* volume actions.
NSS and Linux POSIX volume cluster resources should not be migrated while any of the EVMS
administration utilities are running.
Linux POSIX File Systems
Novell Cluster Services supports creating shared cluster resources on Linux POSIX file systems,
such as Ext3, XFS, and ReiserFS. Linux POSIX file systems are automatically installed as part of
the OES 2 Linux installation.
30OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide
Loading...
+ 224 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.