Novell OPEN ENTERPRISE SERVER CLUSTER SERVICES 1.8.2 -... User manual

Novell
www.novell.com
novdocx (ENU) 29 January 2007
OES Novell Cluster Services 1.8.2 Administration Guide for Linux
Open Enterprise Server
April, 2007
NOVELL CLUSTER SERVICESTM 1.8.2
ADMINISTRATION GUIDE FOR LINUX*

novdocx (ENU) 29 January 2007
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.
Please refer to 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.
Copyright © 2007 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.
Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this
document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S.
patents listed at http://www.novell.com/company/legal/patents/ and one or more additional patents or pending patent
applications in the U.S. and in other countries.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
Online Documentation: To access the online documentation for this and other Novell products, and to get
updates, see www.novell.com/documentation.

novdocx (ENU) 29 January 2007
Novell Trademarks
ConsoleOne is a registered trademark of Novell, Inc. in the United States and other countries.
eDirectory is a trademark of Novell, Inc.
GroupWise is a registered trademark of Novell, Inc. in the United States and other countries.
NetWare is a registered trademark of Novell, Inc. in the United States and other countries.
NetWare Core Protocol and NCP are trademarks of Novell, Inc.
Novell is a registered trademark of Novell, Inc. in the United States and other countries.
Novell Authorized Reseller is a Service mark of Novell Inc.
Novell Cluster Services is a trademark of Novell, Inc.
Novell Directory Services and NDS are registered trademarks of Novell, Inc. in the United States and other countries.
Novell Storage Services is a trademark of Novell, Inc.
SUSE is a registered trademark of Novell, Inc. in the United States and other countries.
Third-Party Materials
All third-party trademarks are the property of their respective owners.

novdocx (ENU) 29 January 2007

Contents 5
Contents
novdocx (ENU) 29 January 2007
About This Guide 7
1Overview 9
1.1 Product Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2 Product Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.3 Cluster Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3.1 Cluster Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2What’sNew 15
3 Installation and Setup 17
3.1 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.2 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.3 Shared Disk System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.4 Rules for Operating a Novell Cluster Services SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.5 Installing Novell Cluster Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.5.1 Novell Cluster Services Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.5.2 Installing Novell Cluster Services during the OES Installation . . . . . . . . . . . . . . . . . 19
3.5.3 Installing Novell Cluster Services after the OES Installation . . . . . . . . . . . . . . . . . . . 20
3.5.4 Starting and Stopping Novell Cluster Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.6 Converting a NetWare Cluster to Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.6.1 Changing Existing NetWare Cluster Nodes to Linux (Rolling Cluster Conversion) . . 21
3.6.2 Adding New Linux Nodes to Your NetWare Cluster . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.6.3 Mixed NetWare and Linux Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.6.4 Finalizing the Cluster Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.7 Setting Up Novell Cluster Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.7.1 Creating NSS Shared Disk Partitions and Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.7.2 Creating NSS Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.7.3 Cluster Enabling NSS Pools and Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.7.4 Creating Traditional Linux Volumes on Shared Disks . . . . . . . . . . . . . . . . . . . . . . . . 32
3.7.5 Expanding EVMS Volumes on Shared Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.7.6 Cluster Enabling Traditional Linux Volumes on Shared Disks . . . . . . . . . . . . . . . . . 36
3.7.7 Creating Cluster Resource Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.7.8 Creating Cluster Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.7.9 Configuring Load Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.7.10 Configuring Unload Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.7.11 Setting Start, Failover, and Failback Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.7.12 Assigning Nodes to a Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3.8 Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.8.1 Editing Quorum Membership and Timeout Properties . . . . . . . . . . . . . . . . . . . . . . . 44
3.8.2 Cluster Protocol Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.8.3 Cluster IP Address and Port Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.8.4 Resource Priority. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.8.5 Cluster E-Mail Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.8.6 Cluster Node Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.9 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

6OES Novell Cluster Services 1.8.2 Administration Guide for Linux
novdocx (ENU) 29 January 2007
4 Managing Novell Cluster Services 49
4.1 Migrating Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4.2 Identifying Cluster and Resource States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4.3 Novell Cluster Services Console Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.4 Customizing Cluster Services Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.5 Novell Cluster Services File Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.6 Additional Cluster Operating Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.6.1 Connecting to an iSCSI Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.6.2 Adding a Node That Was Prevously in the Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.6.3 Cluster Maintenance Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.6.4 Shutting Down Linux Servers When Servicing Shared Storage . . . . . . . . . . . . . . . . 58
4.6.5 Preventing Cluster Node Reboot after Node Shutdown. . . . . . . . . . . . . . . . . . . . . . . 58
4.6.6 Problems Authenticating to Remote Servers during Cluster Configuration . . . . . . . . 59
4.6.7 Reconfiguring a Cluster Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.6.8 Device Name Required to Create a Cluster Partition. . . . . . . . . . . . . . . . . . . . . . . . . 59
4.6.9 Creating a Cluster Partition (SBD Partition) after Installation. . . . . . . . . . . . . . . . . . . 59
4.6.10 Mirroring SBD (Cluster) Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
A Documentation Updates 61
A.1 December 23, 2005 (Open Enterprise Server SP2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

About This Guide
novdocx (ENU) 29 January 2007
7
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,” on page 9
Chapter 2, “What’s New,” on page 15
Chapter 3, “Installation and Setup,” on page 17
Chapter 4, “Managing Novell Cluster Services,” on page 49
Appendix A, “Documentation Updates,” on page 61
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 documentation Web site (http://www.novell.com/documentation/lg/oes).
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.

8OES Novell Cluster Services 1.8.2 Administration Guide for Linux
novdocx (ENU) 29 January 2007

Overview
1
novdocx (ENU) 29 January 2007
9
1
Overview
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 eDirectoryTM and supports failover,
failback, and migration (load balancing) of individually managed cluster resources.
1.1 Product Features
Novell Cluster Services includes several important features to help you ensure and manage the
availability of your network resources. These include:
Support for shared SCSI, iSCSI or fibre channel storage area networks.
Multinode 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 on an as-needed basis.
The ability to automatically notify administrators through e-mail of cluster events and cluster
state changes.
1.2 Product Benefits
Novell Cluster Services allows you to configure up to 32 Linux servers into a high-availability
cluster, where resources can be dynamically switched or moved to any server in the cluster.
Resources can be configured to automatically switch or be moved in the event of a server failure, or
they can be moved manually to troubleshoot hardware or balance the workload.
Novell Cluster Services provides high availability from commodity components. Lower costs are
obtained through the consolidation of applications and operations onto a cluster. The ability 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) are also important benefits of Novell
Cluster Services.
An equally important benefit of implementing Novell Cluster Services is that you can reduce
unplanned service outages as well as planned outages for software and hardware maintenance and
upgrades.
Reasons you would want to implement Novell Cluster Services include the following:
Increased availability
Improved performance
Low cost of operation
Scalability
Disaster recovery

10 OES Novell Cluster Services 1.8.2 Administration Guide for Linux
novdocx (ENU) 29 January 2007
Data protection
Server Consolidation
Storage Consolidation
Shared disk fault tolerance can be obtained by implementing RAID on the shared disk subsystem.
An example of the benefits Novell Cluster Services provides can be better understood through the
following 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 subsystem connected to each of
the servers in the cluster. The following figure depicts how this setup might look.
Figure 1-1 Three-Server Cluster
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 depending on Web
Server 1 for Internet access, e-mail, and information lose their connections. The following figure
shows how resources are moved when Web Server 1 fails.
Figure 1-2 Three-Server Cluster after One Server Fails
Web Server 3
Web Site C
Web Site D
Web Server 2
Fibre Channel Switch
Web Site E
Web Site F
Web Site A
Web Site B
Web Server 1
Web Server 1 Web Server 3
Web Site A
Web Site C
Web Site D
Web Server 2
Fibre Channel Switch
Shared Disk
S
y
stem
Web Site B
Web Site E
Web Site F

Overview 11
novdocx (ENU) 29 January 2007
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.
When you configured the cluster, you decided where the Web sites hosted on each Web server would
go should a failure occur. In the previous example, 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
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 having to log 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 back to the way it was before Web Server 1
failed.
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.3 Cluster Configuration
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.

12 OES Novell Cluster Services 1.8.2 Administration Guide for Linux
novdocx (ENU) 29 January 2007
Typical resources might include data, applications, and services. The following figure shows how a
typical fibre channel cluster configuration might look.
Figure 1-3 Typical Fibre Channel Cluster Configuration
Although fibre channel provides the best performance, you can also configure your cluster to use
shared SCSI or iSCSI. The following figure shows how a typical shared SCSI cluster configuration
might look.
Figure 1-4 Typical Shared SCSI Cluster Configuration
Server 1 Server 2 Server 3 Server 4 Server 5 Server 6
Fibre Channel Switch
Shared Disk
System
Network Hub
Fibre
Channel
Card(s)
Network
Interface
Card(s)
Server 1 Server 2
Shared Disk
S
y
stem
Network Hub
SCSI
Adapte
r
SCSI
Adapter
Network
Interface
Card
Network
Interface
Card

Overview 13
novdocx (ENU) 29 January 2007
iSCSI is another option and is an alternative to fibre channel that can be used to create a low-cost
SAN. The following figure shows how a typical iSCSI cluster configuration might look.
Figure 1-5 Typical iSCSI Cluster Configuration
1.3.1 Cluster Components
The following components make up a Novell Cluster Services cluster:
From 2 to 32 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).
High-speed fibre channel cards, cables, and switch or SCSI cards and cables used to connect
the servers to the shared disk subsystem.
Ethernet
Card(s)
Ethernet
Card(s)
iSCSI
Initiator
iSCSI
Initiator
iSCSI
Initiator
iSCSI
Initiator
iSCSI
Initiator
Ethernet
Storage
System
Server 1 Server 2 Server 3 Server 4 Server 5 Server 6
iSCSI
Initiator
Ethernet Switch
Network Backbone Network Backbone
Ethernet Switch

14 OES Novell Cluster Services 1.8.2 Administration Guide for Linux
novdocx (ENU) 29 January 2007

What’s New
2
novdocx (ENU) 29 January 2007
15
2
What’s New
The following changes and enhancements were added to Novell®Cluster ServicesTM for Linux for
Novell Open Enterprise Server (OES) Support Pack 2.
It is now possible to choose a device for the SBD partition from a list rather than entering it
manually. See Section 3.5, “Installing Novell Cluster Services,” on page 18.
Some iManager cluster option names and locations have changed to make cluster configuration
and management easier.
It is now possible to upgrade a cluster node directly from NetWare 6.0 to OES Linux without
first upgrading to NetWare 6.5. See Section 3.6, “Converting a NetWare Cluster to Linux,” on
page 21.

16 OES Novell Cluster Services 1.8.2 Administration Guide for Linux
novdocx (ENU) 29 January 2007

Installation and Setup
3
novdocx (ENU) 29 January 2007
17
3
Installation and Setup
Novell®Cluster ServicesTM can be installed during the Open Enterprise Server (OES) installation or
after. OES is now part of the SUSE®Linux Enterprise Server (SLES) 9 installation. During the
Novell Cluster Services part of the OES installation, you are prompted for configuration information
that is necessary for Novell Cluster Services to function properly. This chapter contains information
to help you install, set up, and configure Novell Cluster Services.
3.1 Hardware Requirements
The following list specifies hardware requirements for installing Novell Cluster Services. These
requirements 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
At least 512 MB of memory on each server in the cluster.
NOTE: While 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.2 Software Requirements
Novell Cluster Services is installed as part of the OES installation. OES must be installed and
running on each cluster server. In addition to OES, ensure that the following requirements are met:
All servers in the cluster are configured with a static IP address and are on the same IP subnet
There is an additional IP address for the cluster and for each cluster resource and cluster-
enabled pool
All servers in the cluster are in the same Novell eDirectoryTM tree
If the servers in the cluster are in separate eDirectory containers, each server must have rights
to the other server's containers and to the containers where any cluster enabled pool objects are
stored. You can do this by adding trustee assignments for all cluster servers to a parent
container of the containers where the cluster server objects reside. See eDirectory Rights (http:/
/www.novell.com/documentation/edir873/edir873/data/fbachifb.html#fbachifb) in the
eDirectory 8.7.3 Administration Guide for more information.
The browser that will be used to manage Novell Cluster Services is set to a supported language.
The iManager plug-in for Novell Cluster Services 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. To avoid problems, in your Web browser, click Tools > Options >
Languages, and then set the first language preference in the list to a supported language.

18 OES Novell Cluster Services 1.8.2 Administration Guide for Linux
novdocx (ENU) 29 January 2007
3.3 Shared Disk System Requirements
A shared disk system (Storage Area Network, or SAN) is required for each cluster if you want data
to be highly available. If a shared disk subsystem is used, ensure the following:
At least 20 MB of free disk space on the shared disk system for creating a special cluster
partition
The Novell Cluster Services installation automatically allocates one cylinder on one drive of
the shared disk system for the special cluster partition. Depending on the location of the
cylinder, the actual amount of space used by the cluster partition may be less than 20 MB.
The shared disk system is properly set up and functional according to the manufacturer's
instructions before installing Novell Cluster Services.
We recommend that the disks contained in the shared disk system are configured to use
mirroring or RAID to add fault tolerance to the shared disk system.
If you are using iSCSI for shared disk system access, ensure you have configured iSCSI
intiators and targets prior to installing Novell Cluster Services. See Accessing iSCSI Targets on
NetWare Servers from Linux Initiators (http://www.novell.com/documentation/iscsi1_nak/
iscsi/data/bswmaoa.html#bt8cyhf) for more information.
3.4 Rules for Operating a Novell Cluster Services
SAN
When you create a Novell Cluster Services system that utilizes shared storage space (a Storage Area
Network, or SAN), it is important to remember that all servers attached to the shared disks, whether
in the cluster or not, have access to all of the data on the shared storage space unless you specifically
prevent such access. Novell Cluster Services arbitrates access to shared data for all cluster nodes,
but cannot protect shared data from being corrupted by noncluster servers.
3.5 Installing Novell Cluster Services
It is necessary to install SLES 9/OES on every server you want to add to a cluster. You can install
Novell Cluster Services and create a new cluster, or add a server to an existing cluster either during
the SLES 9/OES installation or afterwards, using YaST.
If you are creating a new cluster, the YaST setup tool
Creates a new Cluster object and Cluster Node object in eDirectory.
Installs Novell Cluster Services software on the server.
Creates a special cluster partition if you have a shared disk system.
If you are adding a server to an existing cluster, the YaST setup tool
Creates a new Cluster Node object in eDirectory.
Installs Novell Cluster Services software on the server.
You can install up to 32 nodes in each cluster.

Installation and Setup 19
novdocx (ENU) 29 January 2007
3.5.1 Novell Cluster Services Licensing
You can add up to 32 nodes to a cluster. Novell Cluster Services for Linux includes licenses for two
cluster nodes. You only need additional Cluster Server Licenses if you have a three-node or larger
cluster. A paper license for additional cluster nodes can be obtained from Novell or from your
Novell Authorized ResellerSM.
3.5.2 Installing Novell Cluster Services during the OES
Installation
1Start the SUSE Linux Enterprise Server 9 (SLES 9) installation and continue until you get to
the Installation Settings screen, then click Software.
OES is part of the SLES 9 install.
The SLES 9/OES installation includes several steps not described here because they do not
directly relate to Novell Cluster Services. For more detailed instructions on installing OES with
SLES 9, see the OES Linux Installation Guide.
2On the Software Selection screen, click Detailed Selection.
3In the Selection window, click Novell Cluster Services and any other OES components that you
want to install, then click Accept.
NSS is a required component for Novell Cluster Services and it is automatically selected when
you select Novell Cluster Services. Installing NSS also allows you to create cluster-enabled
NSS pools (virtual servers).
iManager is required to configure and manage Novell Cluster Services, and must be installed
on at least one server.
4Continue through the installation process until you reach the Installation Settings screen, then
click the Cluster Services link.
5Choose whether eDirectory is installed locally or remotely, accept or change the Admin name
and enter the Admin password, then click Next.
eDirectory is automatically selected when NSS is selected.
6Choose to either create a new cluster, configure Novell Cluster Services on a server that you
will add to an existing cluster, or configure Novell Cluster Services later.
7Enter the fully distinguished name (FDN) of the cluster.
IMPORTANT: Use the dot format illustrated in the example. Do not use commas.
If you are creating a new cluster, this is the name you will give the new cluster and the
eDirectory context where the new Cluster object will reside. You must specify an existing
context. Specifying a new context does not create a new context.
If you are adding a server to an existing cluster, this is the name and eDirectory context of the
cluster that you are adding this server to.
Cluster names must be unique. You cannot create two clusters with the same name in the same
eDirectory tree.
8(Conditional) If you are creating a new cluster, enter a unique IP address for the cluster.
The cluster IP address is separate from the server IP address, is required to be on the same IP
subnet as the other cluster servers, and is required for certain external network management

20 OES Novell Cluster Services 1.8.2 Administration Guide for Linux
novdocx (ENU) 29 January 2007
programs to get cluster status alerts. The cluster IP address provides a single point for cluster
access, configuration, and management. A Master IP Address resource that makes this possible
is created automatically during the Cluster Services installation.
The cluster IP address will be bound to the master node and will remain with the master node
regardless of which server is the master node.
9(Conditional) If you are creating a new cluster, select the device where the SBD partition will
be created.
For example, the device might be something similar to sdc.
If you have a shared disk system or SAN attached to your cluster servers, Novell Cluster
Services will create a small cluster partition on that shared disk system. This small cluster
partition is referred to as the Split Brain Detector (SBD) partition. Specify the drive or device
where you want the small cluster partition created.
If you do not have a shared disk system connected to your cluster servers, accept the default
(none).
IMPORTANT: You must have at least 20 MB of free space on one of the shared disk drives to
create the cluster partition. If no free space is available, the shared disk drives can't be used by
Novell Cluster Services.
10 (Conditional) If you want to mirror the SBD partition for greater fault tolerance, select the
device where you want to mirror to, then click Next.
You can also mirror SBD partitions after installing Novell Cluster Services. See Section 4.6.10,
“Mirroring SBD (Cluster) Partitions,” on page 60.
11 Select the IP address Novell Cluster Services will use for this node.
Some servers have multiple IP addresses. This step lets you choose which IP address Novell
Cluster Services will use.
12 Choose whether to start Novell Cluster Services software after configuring it, then click Next.
This option applies only to installing Novell Cluster Services after the OES installation,
because it starts automatically when the server reboots during the OES installation.
If you choose to not start Novell Cluster Services software, you need to either manually start it
after the installation, or reboot the cluster server to automatically start it.
You can manually start Novell Cluster Services by going to the /etc/init.d directory and
entering ./novell-ncs start at the server console of the cluster server.
13 Continue through the rest of the OES installation.
3.5.3 Installing Novell Cluster Services after the OES
Installation
If you did not install Novell Cluster Services during the OES installation, you can install it later by
completing the following steps:
1At the Linux server console, type yast2 ncs.
This installs the Novell Cluster Services software component and takes you to the cluster
configuration screen.
You must be logged in as root to access the cluster configuration screen.