Novell OPEN ENTERPRISE SERVER 2 SP 2 - CLUSTER SERVICES 1.8.7 FOR LINUX Manual

Table of Contents

Advertisement

Quick Links

AUTHORIZED DOCUMENTATION
Novell Cluster Services
1.8.7 For Linux Administration Guide
TM
Novell
®
Open Enterprise Server
2 SP2
March 15, 2010
www.novell.com
OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide

Advertisement

Table of Contents
loading

Summary of Contents for Novell OPEN ENTERPRISE SERVER 2 SP 2 - CLUSTER SERVICES 1.8.7 FOR LINUX

  • Page 1 AUTHORIZED DOCUMENTATION Novell Cluster Services 1.8.7 For Linux Administration Guide Novell ® Open Enterprise Server 2 SP2 March 15, 2010 www.novell.com OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 2: Legal Notices

    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.
  • Page 3 Novell Trademarks For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/ trademarks/tmlist.html). Third-Party Materials All third-party trademarks are the property of their respective owners.
  • Page 4 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 5: Table Of Contents

    System Requirements for Novell Cluster Services........27...
  • Page 6 Managing File Systems in Mixed-Node Clusters ......62 6.1.10 Using Novell iManager in Mixed-Node Clusters ......62 6.1.11 Using Novell Remote Manager Is Not Supported in Mixed-Node Clusters .
  • Page 7 Starting and Stopping Novell Cluster Services ........
  • Page 8 Novell Storage Services ........
  • Page 9 What’s Next ............. . 179 12 Configuring Novell Cluster Services in a Xen Virtualization Environment 12.1...
  • Page 10 E.1.4 Troubleshooting Novell Cluster Services ....... . . 227 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 11 E.4.4 Troubleshooting Novell Cluster Services ....... . . 229 E.4.5 What’s New .
  • Page 12 E.18.11 Overview of Novell Cluster Services ........249 E.18.12 Troubleshooting Novell Cluster Services ....... . . 249 E.18.13 Upgrading OES 2 Clusters .
  • Page 13: About This Guide

    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 Guide...
  • Page 14: Additional Documentation

    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 ( , etc.) denotes a Novell trademark.
  • Page 15: Overview Of Novell Cluster Services

    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).
  • Page 16: Product Features

    Server consolidation Storage consolidation 1.3 Product Features 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.
  • Page 17 The benefits that 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 system connected to each of the servers in the cluster.
  • Page 18: Shared Disk Scenarios

    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.
  • Page 19: Using Fibre Channel Storage Systems

    Fibre Channel cluster configuration might look. Typical Fibre Channel Cluster Configuration Figure 1-3 Network Hub Network Fibre Interface Channel Card(s) Card(s) Server 1 Server 2 Server 3 Server 4 Server 5 Server 6 Fibre Channel Switch Shared Disk System Overview of Novell Cluster Services...
  • Page 20: Using Iscsi Storage Systems

    Initiator Initiator Initiator Initiator Initiator Initiator Ethernet Ethernet Card(s) Card(s) Server 1 Server 2 Server 3 Server 4 Server 5 Server 6 Ethernet Ethernet Switch Storage System OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 21: Using Shared Scsi Storage Systems

    SCSI cluster configuration might look. Typical Shared SCSI Cluster Configuration Figure 1-5 Network Hub Network SCSI Network SCSI Interface Adapter Interface Adapter Card Card Server 1 Server 2 Shared Disk System Overview of Novell Cluster Services...
  • Page 22 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 23: What's New

    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.
  • Page 24: Specifying The Size Of The Sbd Partition

    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 2.2.7 Removed MPK Calls from the Code...
  • Page 25: What's New (Oes 2 Sp1)

    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,”...
  • Page 26: Attribute Ncs: Gipc Config Is No Longer Maintained

    (NSS) volumes on OES 2 SP1 Linux. See “Novell AFP for Linux” on page 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 2.3.7 Support for Domain Services for Windows...
  • Page 27: Installing And Configuring Novell Cluster Services On Oes 2 Linux

    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.
  • Page 28: Software Requirements

    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.
  • Page 29 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/).
  • Page 30 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 Novell Downloads Web site (http://download.novell.com). For information about installing plug-ins in iManager, see “Downloading and Installing Plug-in...
  • Page 31 Novell Cluster Services supports creating shared cluster resources by using Novell Storage Services file system on Linux. NSS is not a required component for Novell Cluster Services on Linux unless you want to create and cluster-enable NSS pools and volumes. You can also use NSS for the SBD partition.
  • Page 32 Novell Cluster Services supports using Novell AFP for Linux as an advertising protocol for cluster- enabled NSS pools and volumes on OES 2 SP1 Linux and later. Novell AFP is not required to be installed when you install Novell Cluster Services, but it must be installed and running when you create and cluster-enable the shared NSS pool in order for the AFP option to be available as an advertising protocol for the cluster resource.
  • Page 33 “Configuring Novell Cluster Services in a Xen Virtualization Environment,” on page 181. Novell Cluster Services is supported to run on a Xen host server where it can be used to cluster the virtual machine configuration files on Linux POSIX file systems. Only the Xen and XenLive templates are supported for use in the XEN host environment.
  • Page 34: Configuration Requirements

    8.8 Administration Guide for more information. 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 Novell Cluster Services install configuration does not create a new context.
  • Page 35 Give the user the Supervisor right to the Server object of each of the servers in the cluster. Linux-enable the user account with Linux User Management. Make the user a member of a LUM-enabled administrator group that is associated with the servers in the cluster. Installing and Configuring Novell Cluster Services on OES 2 Linux...
  • Page 36: Shared Disk System Requirements

    Web Browser The browser that will be used to manage Novell Cluster Services must be set to a supported language. For information about supported languages, see the Novell iManager documentation (http://www.novell.com/documentation/imanager27/). The Cluster 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.
  • Page 37 Before installing Novell Cluster Services or creating a new SBD partition, you must initialize the partition, and mark its device as shareable for clustering. If you plan to mirror the SBD, you must also initialize the partition you want to use as the mirrored SBD, and mark its device as shareable for clustering.
  • Page 38: San Rules For Lun Masking

    I/O errors occur. The default setting in DM-MP is to queue I/O if one or more HBA paths is lost. Novell Cluster Services does not migrate resources from a node set to the Queue mode because of data corruption issues that can be caused by double mounts if the HBA path is recovered before a reboot.
  • Page 39: Novell Cluster Services Licensing

    Link Down Retry=5 3.2 Novell Cluster Services Licensing Novell Cluster Services supports up to 32 nodes in a single cluster. Novell Open Enterprise Server 2 customers receive a Novell Cluster Services entitlement that covers an unlimited number of two- node clusters. Customers who want to add nodes to any cluster can purchase a paper license for them for an additional fee.
  • Page 40: Extending The Edirectory Schema To Add Cluster Objects

    3.3 Extending the eDirectory Schema to Add Cluster Objects When you install Novell Cluster Services in a tree, the eDirectory schema for the tree is extended to include the following types of objects: Cluster objects (containers) Cluster Node objects Cluster Resource objects...
  • Page 41: Extending The Schema

    2 In a text editor, create a text file, specify the configuration information for the Novell Cluster Services cluster in it, then save the file. The following lines are an example of the content of the file with sample values. The directives are self-explanatory.
  • Page 42: Installing Novell Cluster Services

    3.5 Installing Novell Cluster Services Novell Cluster Services for Linux is included on the add-on media for OES 2 Linux (or later). It is necessary to install OES 2 Linux on every server that you want to add to a cluster.
  • Page 43 Repeat the following procedure for each server that you want to add to the cluster: 1 If you have a shared disk system and the server where you are installing Novell Cluster Services is the second node in a cluster, verify that a cluster partition for the cluster’s Split Brain Detector exists on the first cluster node before you begin the install on the second node.
  • Page 44: Installing Novell Cluster Services On An Existing Oes 2 Linux Server

    3.5.2 Installing Novell Cluster Services on an Existing OES 2 Linux Server If you did not install Novell Cluster Services during the OES 2 Linux installation, you can install it later by using YaST > Open Enterprise Server > OES Install and Configuration.
  • Page 45 Repeat the following procedure for each server that you want to add to the cluster: 1 If you have a shared disk system and the server where you are installing Novell Cluster Services is the second node in a cluster, verify that a cluster partition for the cluster’s Split Brain Detector exists on the first cluster node before you begin the install on the second node.
  • Page 46: Configuring Novell Cluster Services

    Creates a special cluster partition for the Split Brain Detector (SBD) if you have a shared disk system. If you are adding a server to an existing cluster, the Novell Cluster Services configuration does the following: Creates a new Cluster Node object in eDirectory.
  • Page 47: Using Different Ldap Credentials For The Cluster Configuration

    2 In YaST, select Open Enterprise Server > OES Install and Configuration. 3 On the Software Selection page under OES Services, verify that the Novell Cluster Services option is already installed as indicated by a blue check mark, then click Accept.
  • Page 48: Enabling The Novell Cluster Services Configuration Page In Yast

    The sentence changes to Configure is enabled. 2 Click the Novell Cluster Services link to open the Novell Cluster Services Configuration page. 3 If you are prompted for credentials, specify the password of the specified Administrator user, then click OK.
  • Page 49 SBD (Split Brain Detector) Partition If you have a shared disk system attached to your cluster servers, Novell Cluster Services creates a small cluster partition for the Split Brain Detector (SBD) on that shared disk system.
  • Page 50: Adding A Node To An Existing Cluster

    Some servers have multiple IP addresses. This step lets you choose which IP address Novell Cluster Services uses. 4 If this is an existing server, choose whether to start Novell Cluster Services software on this node after configuring it, then click Next.
  • Page 51 Some servers have multiple IP addresses. This step lets you choose which IP address Novell Cluster Services uses. 5 If this is an existing server, choose whether to start Novell Cluster Services software on this node after configuring it, then click Next.
  • Page 52: Configuring Additional Administrators

    Chapter 11, “Configuring Cluster Resources for Shared Linux POSIX Volumes,” on page 157 If you install Novell Cluster Services at the host level of an OES 2 Linux (Xen) server, you can create cluster resources for the virtual machines. For information, see Section 12.2, “Virtual...
  • Page 53: Upgrading Oes 2 Linux Clusters

    Make sure that any services that are available only in OES 2 SP1 or later (such as Novell CIFS or Novell AFP) are set up with preferred nodes for failover that are running OES 2 SP1 or later.
  • Page 54: Upgrade Issues For Oes 2 Sp2

    OES 2 SP2. Section 4.3.1, “Updating the iFolder Resource Template,” on page 54 4.3.1 Updating the iFolder Resource Template In OES 2 SP2 Linux, the Novell Cluster Services resource template for Novell iFolder 3.x has changed. The revised template is . You /opt/novell/ncs/templates/iFolder_template.xml...
  • Page 55: Upgrading Oes 1 Linux Clusters To Oes 2 Linux

    Upgrading OES 1 Linux Clusters to OES 2 Linux ® This section provides information to help you upgrade a Novell Open Enterprise (OES) 1 Linux cluster to OES 2 Linux, and how to manage the temporarily mixed cluster during the upgrade.
  • Page 56: Upgrading Existing Oes 1 Linux Cluster Nodes To Oes 2 (Rolling Cluster Upgrade)

    NOTE: NSS, eDirectory, and NCP Server are not required components for Novell Cluster Services on OES 2, but are required components for Novell Cluster Services on OES 1 Linux. Ensure that you install these components on OES 2 Linux servers when you upgrade your OES 1 Linux cluster servers.
  • Page 57: Adding New Oes 2 Linux Cluster Nodes To Your Oes 1 Linux Cluster

    OES 1 cluster node to an OES 1 Linux cluster and adding a new OES 2 cluster node to an existing OES 2 cluster. See Section 3.5, “Installing Novell Cluster Services,” on page However, you should be aware of the rules that apply to mixed OES 1 and OES 2 clusters. See Section 5.1, “Requirements and Guidelines for Upgrading Clusters from OES 1 Linux and OES 2...
  • Page 58 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 59: Converting Netware 6.5 Clusters To Oes 2 Linux

    ® NetWare 6.5 SP8 to Novell Open Enterprise Server (OES) 2 SP1 Linux. This section describes how to prepare for and perform the conversion, and how to manage the temporarily mixed cluster during the conversion. Section 6.1, “Guidelines for Converting Clusters from NetWare to OES 2 Linux,” on page 59 Section 6.2, “Guidelines for Converting NSS Pool Resources from NetWare to Linux,”...
  • Page 60: Supported Mixed-Node Clusters

    6.1.2 SBD Devices Must Be Marked as Shareable for Clustering Novell Cluster Services for Linux requires that the devices used for the SBD partition be explicitly marked as Shareable for Clustering. When converting a NetWare cluster, make sure that the SBD device, or both devices for a mirrored SBD, are marked as Shareable for Clustering before you add the first Linux node to the cluster.
  • Page 61: Case Sensitivity Issues

    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 them in the /var/ file that you create. The opt/novell/ncs/customized_translation_syntax clstrlib.py script reads the additional translation syntax from the syntax file. For information, see Section 6.7,...
  • Page 62: Converting Nodes That Contain The Edirectory Master Replica

    6.1.10 Using Novell iManager in Mixed-Node Clusters Use Novell iManager 2.7.2 or later for all cluster administration in the mixed-node cluster. Using the Clusters plug-in to iManager is required to manage the cluster after the first OES 2 Linux node is added to the cluster.
  • Page 63: Using Novell Remote Manager Is Not Supported In Mixed-Node Clusters

    OES 2 Linux. Because different time formats are used in the NCS Event log for NetWare and Linux, Novell Remote Manager might have difficulty displaying the time of logged events. To avoid this problem in a mixed-node cluster, use iManager to access the NCS Event log.
  • Page 64: Nss File System Migration To Ncp Volumes Or Linux Posix File Systems

    Section 6.3.7, “DHCP Server,” on page 69 Section 6.3.8, “DNS Server,” on page 71 Section 6.3.9, “eDirectory Server Certificates,” on page 72 Section 6.3.10, “iPrint,” on page 74 Section 6.3.11, “QuickFinder Server,” on page 75 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 65: Overview Of All Netware 6.5 Sp8 Services

    6.3.1 Overview of All NetWare 6.5 SP8 Services Table 6-1 for information about converting cluster resources for NetWare 6.5 SP8 services: Guidelines for Converting Service Cluster Resources from NetWare to Linux Table 6-1 Service on NetWare 6.5 Cluster Migrate the Converting the Service to OES 2 Linux Resource Apache Web Server...
  • Page 66 For information, see “Configuring QuickFinder Server for Novell Cluster Services” in the NW 6.5 SP8 Novell QuickFinder Server 5.0 Administration Guide. Tomcat Not applicable Use the standard Tomcat service for Linux. OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 67: Apache Web Server

    6 Online the cluster resource. 6.3.3 Apple Filing Protocol (AFP) Novell AFP for Linux is available beginning in OES 2 SP1 Linux. After you set up Novell AFP on the Linux node and before you finalize the NetWare-to-Linux conversion, use the AFP migration tool to convert the configuration.
  • Page 68: Cifs

    Novell CIFS for Linux is available beginning in OES 2 SP1 Linux. After you set up Novell CIFS on the Linux node and before you finalize the NetWare-to-Linux conversion, use the CIFS migration tool to convert the configuration. For information, see “Migrating CIFS from NetWare to OES 2 SP2...
  • Page 69: Dhcp Server

    Use this method if you want to use a different shared disk for the VLDB on Linux. You can do this by adding a DFS replica site on Linux. 1 Install OES 2 Linux on the server that you want to add to the cluster. Make sure Novell Storage Services and any dependent services are installed.
  • Page 70 OES 2 SP2: Novell DNS/DHCP Administration Guide for Linux. After you set up Novell DHCP Server on the Linux server, you can use the DHCP Migration utility to convert the configuration from NetWare to Linux. You cannot directly reuse the data. Use one of the following scenarios to migrate your DNS server data, then perform the post-migration tasks to set up clustering.
  • Page 71: Dns Server

    6.3.8 DNS Server You can migrate the data from the Novell DNS Server on NetWare to a Novell DNS Server on Linux after you have installed and set up DNS services on an OES 2 SP1 Linux node in the cluster. You cannot directly reuse the data.
  • Page 72: Edirectory Server Certificates

    2 Linux, and therefore, there are no cluster-specific tasks for them. Novell Certificate Server provides a Server Certificates service for NetWare and Linux. The service is not clustered. However, clustered applications that use the server certificates must be able to use the same server certificates on whichever cluster node they happen to be running.
  • Page 73 X.509 requirements as specified in RFC 2459 and RFC 3280. To address the difference, Novell Certificate Server offers an install option for OES 2 Linux called Use eDirectory Certificates that automatically exports the default eDirectory certificate SSL Certificate DNS and its key pair to the local file system in the following files: /etc/ssl/servercerts/servercert.pem...
  • Page 74: Iprint

    IMPORTANT: Do not modify the load and unload scripts for the Linux shared NSS pool resource at this time. 8 Use the Migration tool to migrate data from the NetWare shared NSS pool to the Linux shared NSS pool. OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 75: Quickfinder Server

    Guide. 6.3.11 QuickFinder Server In a Novell Cluster Services cluster, you must install QuickFinder on each node in the cluster. This registers QuickFinder Server with each of the Web servers and application servers running on each server. On OES 2 Linux, QuickFinder is installed by default in the directory.
  • Page 76 Linux server. You could copy it to /var/opt/SearchSites/PartnerSite /var/lib/ qfsearch/Sites/PartnerSite 10 Edit all NetWare paths in to reflect the new /var/lib/qfsearch/SiteList.properties Linux paths. For example, change sys:/qfsearch /var/lib/qfsearch. OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 77 Or, as in the example in Step 9, change sys:/SearchSites/PartnerSite /var/opt/ SearchSites/PartnerSite Some paths might have one or two backslashes (\) that must be replaced with one forward slash (/). For example, needs to be changed to sys:\\qfsearch\\docs /var/lib/qfsearch/ docs 11 Update all NetWare paths in the properties and configuration files copied in the steps above to the Linux paths, and update any DNS names.
  • Page 78: Converting Netware Cluster Nodes To Oes 2 Linux (Rolling Cluster Conversion)

    IMPORTANT: Before you begin, make sure you system meets the following requirements and caveats: Section 3.1, “System Requirements for Novell Cluster Services,” on page 27 Section 6.1, “Guidelines for Converting Clusters from NetWare to OES 2 Linux,” on page 59...
  • Page 79 6 Run DSRepair from another server in the eDirectory tree to fix any directory problems. If DSRepair finds errors or problems, run it multiple times until no errors are returned. 7 Install OES 2 Linux on the server, but do not install the Novell Cluster Services option in OES Services at this time.
  • Page 80 The sentence changes to Configuration is enabled. 9h Click the Novell Cluster Services link to open the Novell Cluster Services Configuration page. 9i Click Existing Cluster, specify the fully distinguished name (FDN) of the cluster, then click Next.
  • Page 81: Adding New Oes 2 Linux Nodes To Your Netware Cluster

    Shareable for Clustering. 1g Press Esc to exit NSSMU. 2 Install OES 2 Linux on the new node, but do not install the Novell Cluster Services option from OES Services at this time. See the “OES 2 SP2: Installation...
  • Page 82: Translation Of Cluster Resource Scripts For Mixed Netware And Linux Clusters

    IMPORTANT: Beginning in OES 2 SP2, Novell Cluster Services allows you to customize the translation syntax that us used for load and unload scripts in mixed-platform situations by defining new syntax translations to be used in addition to the normal translations.
  • Page 83: Comparing Master Ip Address Scripts

    Cluster Script Command Comparison Table 6-2 Action NetWare Cluster Command Linux Cluster Command Replace IGNORE_ERROR add secondary ignore_error ipaddress add_secondary_ipaddress Replace IGNORE_ERROR del secondary ignore_error ipaddress del_secondary_ipaddress Replace del secondary ipaddress ignore_error del_secondary_ipaddress Replace add secondary ipaddress exit_on_error add_secondary_ipaddress Delete IGNORE_ERROR NUDP (deletes the entire line) Delete...
  • Page 84: Comparing Nss Pool Resource Scripts

    This section provides examples of the NSS pool resource load scripts on NetWare and Linux. NetWare nss /poolactivate=HOMES_POOL mount HOMES VOLID=254 CLUSTER CVSBIND ADD BCC_CLUSTER_HOMES_SERVER 10.1.1.180 NUDP ADD BCC_CLUSTER_HOMES_SERVER 10.1.1.180 add secondary ipaddress 10.1.1.180 CIFS ADD .CN=BCC_CLUSTER_HOMES_SERVER.OU=servers.O=lab.T=TEST_TREE. OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 85: Comparing File Access Protocol Resource Script Commands

    Linux #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs exit_on_error nss /poolact=HOMES_POOL exit_on_error ncpcon mount HOMES=254 exit_on_error add_secondary_ipaddress 10.1.1.180 exit_on_error ncpcon bind --ncpservername=BCC_CLUSTER_HOMES_SERVER --ipaddress=10.1.1.180 exit 0 NSS Pool Resource Unload Script This section provides examples of the NSS pool resource unload scripts on NetWare and Linux.
  • Page 86 Novell CIFS exit_on_error novcifs --add --vserver=.CN=NCS1_P1_SERVER.O=novell.T=TREE-188. --ip- addr=$CIFS_IP File Access Protocol Resource Unload Scripts This section provides examples of the Novell AFP commands for unload scripts on NetWare and Linux. NetWare Protocol Script Command for Unload Scripts NUDP DEL NCS1_P1_SERVER 10.10.10.194 Novell AFP AFPBIND DEL NCS1_P1_SERVER 10.10.10.204...
  • Page 87: Customizing The Translation Syntax For Converting Load And Unload Scripts

    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...
  • Page 88: Finalizing The Cluster Conversion

    Novell Cluster Services for Linux. In addition to generating Linux cluster resource templates, this command deletes all NetWare cluster resource templates that have the same name as Linux cluster resource templates.
  • Page 89 Enter the following command as the user on every node in the cluster: root /opt/novell/ncs/bin/ncs-configd.py -init This removes the NetWare nodes from the list of nodes in the cluster so they are not displayed in iManager. Converting NetWare 6.5 Clusters to OES 2 Linux...
  • Page 90 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 91: Configuring Cluster Policies And Priorities

    Description Cluster IP address Specifies the IP address for the cluster. You specify the IP address when you install Novell Cluster Services on the first node of the cluster. Rarely, you might need to modify this value. Port Specifies the port used for cluster communication.
  • Page 92: Cluster Protocols Properties

    1 In iManager, select Clusters, then select Cluster Options. 2 Specify the cluster name, or browse and select the Cluster object. 3 Click the Properties button under the cluster name. 4 Click the Policies tab. OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 93: Quorum Triggers (Number Of Nodes)

    The number of nodes required to form a cluster quorum is the number of nodes that must be running in the cluster before resources start to load. When you first bring up servers in your cluster, Novell Cluster Services reads the number specified in this field and waits until that number of servers is up and running in the cluster before it starts loading resources.
  • Page 94: Heartbeat

    Test the failover time of the MPIO solution you are using, then adjust the watchdog setting upward accordingly. 7.3.5 Maximum Retransmits This value is set by default, and should not be changed. OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 95: Configuring Cluster Event E-Mail Notification

    IMPORTANT: Novell Cluster Services uses Postfix to send e-mail alerts. If you have a cluster resource that uses SMTP, that resource might not work in the cluster unless you change the Postfix configuration.
  • Page 96: Modifying The Cluster Ip Address And Port Properties

    7.6 Modifying the Cluster IP Address and Port Properties The cluster IP address is assigned when you install Novell Cluster Services. The cluster IP address normally does not need to be changed, but it can be if needed. The default cluster port number is 7023, and is automatically assigned when the cluster is created.
  • Page 97: Managing Clusters

    IMPORTANT: If you are using iSCSI for shared disk system access, ensure that you have configured iSCSI initiators and targets to start prior to starting Novell Cluster Services. You can do this by entering the following at the Linux terminal console:...
  • Page 98: Starting Novell Cluster Services

    8.1.3 Enabling and Disabling the Automatic Start of Novell Cluster Services Novell Cluster Services automatically starts by default after it is installed and on server reboot. To cause Novell Cluster Services to not start automatically after a server reboot: 1 Open a terminal console, then log in as the user.
  • Page 99: Monitoring Cluster And Resource States

    8.2 Monitoring Cluster and Resource States The Cluster Manager link in iManager gives you important information about the status of servers and resources in your cluster. 1 In iManager, click Cluster, then click Cluster Manager. 2 Type the name of the desired cluster, or browse to locate and select the Cluster object. A list of resources and resource states displays.
  • Page 100 Unloading The resource is in the process None. of unloading from the server it was running on. 100 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 101: Generating A Cluster Configuration Report

    8.3 Generating a Cluster Configuration Report A cluster configuration report can help you diagnose problems with the cluster nodes and resources. The report contains the following information for the selected cluster: Field Description Cluster name The dot delimited distinguished name of the selected cluster (clustername.context).
  • Page 102: Onlining And Offlining (Loading And Unloading) Cluster Resources From A Cluster Node

    2 Browse to locate and select the Cluster object of the cluster you want to manage. A list of resources and resource states displays. 3 Select the check box next to the resource you want to manage, then click Online or click Offline. 102 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 103: Removing (Leaving) A Node From The Cluster

    8.8 Configuring the EVMS Remote Request Timeout Novell Cluster Services for Linux uses the EVMS Cluster Segment Manager for shared devices. When load and unload scripts run, EVMS mounts or dismounts shared devices. The default timeout for remote requests for EVMS is 12 seconds. If you have many shared devices to be mounted or dismounted and the timeout is exceeded, you might see EVMS locking errors and some cluster resources can go comatose.
  • Page 104: Shutting Down Linux Cluster Servers When Servicing Shared Storage

    This is normal cluster operating behavior, and it prevents the lost node from trying to load cluster resources because it cannot detect the other cluster nodes. 104 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 105: Renaming A Pool For A Pool Cluster Resource

    8.12 Renaming a Pool for a Pool Cluster Resource When a cluster-enabled NSS pool is used as a Novell Cluster Services cluster resource, special steps must be followed if you decide to rename the pool. 1 Cluster migrate the pool resource to the node in the cluster where the pool was initially created.
  • Page 106 Adding LDAP servers to the list of ones that the cluster can use You can modify these settings at any time. Novell Cluster Services can be running or not running. To modify the LDAP server IP address or administrator credentials in the Novell Cluster Services...
  • Page 107: Moving A Cluster Or Changing Ip Addresses Of Cluster Nodes And Resources

    If you start the servers in the different IP subnet with the old IP addresses, the cluster does not come up until you make the changes described in this section. To modify the IP addresses of servers being used in a Novell Cluster Services cluster, perform the following tasks in the order given: “Prerequisites”...
  • Page 108 Step 6 by making similar changes to the Unload Script and Monitor Script. 3 Stop Novell Cluster Services for every node in the cluster by entering the following at the terminal console prompt as the user: root rcnovell-ncs stop 4 Continue with “Changing the IP Addresses of Servers in a Cluster”...
  • Page 109: Adding A Node That Was Previously In The Cluster

    8.14 Adding a Node That Was Previously in the Cluster 1 If your storage array and devices are not configured, configure them before you install Novell Cluster Services. 2 If necessary, install OES 2 Linux and Novell Cluster Services, including the latest Service Pack on the server using the same node name and IP address of the node that was previously in the cluster.
  • Page 110: Creating Or Deleting Cluster Sbd Partitions

    2 In a Web browser, open iManager, then log in to the Novell eDirectory tree that contains the cluster you want to manage. IMPORTANT: Log in as an administrator user who has sufficient rights in eDirectory to delete and modify eDirectory objects.
  • Page 111: Prerequisites For Creating An Sbd Partition

    8.16.3 Creating a Non-Mirrored Cluster SBD Partition If you did not create a cluster partition during the Novell Cluster Services installation on the first node of the cluster, you can create one on it later by using the SBDUTIL utility ( /opt/novell/ ).
  • Page 112: Creating A Mirrored Cluster Sbd Partition

    Novell Cluster Services uses the NSS software RAID capability to mirror the SBD partition. You can mirror the SBD partition when you install Novell Cluster Services on the first node, or you can create it afterwards by using the sbdutil utility or the evmsgui utility to create a mirrored cluster partition.
  • Page 113: Deleting A Non-Mirrored Cluster Sbd Partition

    8.16.5 Deleting a Non-Mirrored Cluster SBD Partition You must delete an existing SBD partition for the cluster before you attempt to create (or re-create) an SBD partition. The existing SBD partition might have been created during the Novell Cluster Services installation, or later by using the...
  • Page 114: Deleting A Mirrored Cluster Sbd Partition

    The existing mirrored SBD partition might have been created during the Novell Cluster Services installation, or later by using the SBDUTIL or the EVMS GUI tool. 1 At a Linux terminal console of a cluster server, log in as the user.
  • Page 115: Customizing Cluster Services Management

    7 Join the nodes to the cluster. 8.17 Customizing Cluster Services Management Some portions of Novell Cluster Services management can be performed and customized by using virtual XML files that exist in the directory on Linux.
  • Page 116 Write-then-read command file used in conjunction with a Perl script to issue Resource.cmd resource-specific commands to the cluster and retrieve resulting resource status and configuration information. 116 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 117: Configuring And Managing Cluster Resources

    Configuring and Managing Cluster Resources ® After you create and configure a Novell Cluster Services cluster, you are ready to create and configure cluster resources for the cluster. This section provides general instructions for creating cluster resources and configuring their behavior in the cluster.
  • Page 118: Default Resource Templates

    Third-party templates See your vendor documentation. Novell Cluster Services provides the following templates for use by the Xen VM host server (Dom0). They are the only two templates supported for the host, and they are not supported for use by a VM guest server.
  • Page 119: Creating A Resource Template

    4 Browse to locate and select the Cluster object of the cluster you want to manage. A list of available resources and resource templates are displayed. You can also view the templates outside of iManager. They are cached as /var/opt/novell/ncs/ files on the master node of the cluster. *_Template.* 9.2.2 Creating a Resource Template...
  • Page 120: Creating Cluster Resources

    12b Edit or add the necessary commands to the script to monitor the resource on the server. You can use the same commands that are used at the Linux terminal console. The resource templates included with Novell Cluster Services for Linux include resource monitoring scripts that you can customize.
  • Page 121: Configuring A Load Script For A Cluster Resource

    6 Specify the name of the resource you want to create. NOTE: Do not use periods in cluster resource names. Novell clients interpret periods as delimiters. If you use a space in a cluster resource name, that space is converted to an underscore.
  • Page 122: Configuring An Unload Script For A Cluster Resource

    5 Edit or add the necessary commands to the script to unload the resource on the server. You can add any lines to the unload script that are required to unload services that are loaded by this cluster resource. 122 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 123: Enabling Monitoring And Configuring The Monitor Script

    Section 9.6.3, “Monitoring Services Critical to Clustering,” on page 125 9.6.1 Configuring Resource Monitoring Although Novell Cluster Services can detect a node failure, it also has the ability to detect when an individual resource on a node has failed. If you want Novell Cluster Services to check the health status of a resource, you must enable and configure resource monitoring for that resource.
  • Page 124: Example Monitoring Scripts

    10 Edit or add the necessary commands to the script to monitor the resource on the server. You can use the same commands that would be used at the Linux terminal console. The resource templates included with Novell Cluster Services for Linux include resource monitoring scripts that you can customize.
  • Page 125: Setting Start, Failover, And Failback Modes For Cluster Resources

    9.6.3 Monitoring Services Critical to Clustering Monitoring scripts can also be used for monitoring critical services needed by the resources, such as Linux User Management (namcd) and Novell eDirectory (ndsd). However, the monitoring is in effect only where the cluster resource is running.
  • Page 126: Viewing Or Modifying The Start, Failover, And Failback Modes For A Resource

    6 (Conditional) Select the Ignore Quorum check box if you don't want the cluster-wide timeout period and node number limit enforced. The quorum default values were set when you installed Novell Cluster Services. You can change the quorum default values by accessing the properties page for the Cluster object.
  • Page 127: Assigning Nodes To A Resource

    9.8 Assigning Nodes to a Resource If you are creating a new cluster resource, the Preferred Nodes page should already be displayed. If you are assigning nodes for an existing resource, the Preferred Nodes page is displayed as part of the Resource Policies page.
  • Page 128: Changing The Ip Address Of A Cluster Resource

    For shared NSS pools and volumes, use NSSMU or the Storage plug-in to iManager. Deleting the pool automatically deletes the volumes on it. For shared Linux POSIX volumes, use evmsgui. 128 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 129: Deleting A Cluster Resource On A Non-Master Node

    2 If the cluster resource is online, offline it by entering cluster offline resource 3 At the terminal console prompt on the non-master node, enter /opt/novell/ncs/bin/ncs-configd.py -init 4 Look at the file to verify that it has the /var/opt/novell/ncs/resource-priority.conf same information (REVISION and NUMRESOURCES) as the file on the master node.
  • Page 130: Additional Information For Creating Cluster Resources

    You need to restart Cluster Services to force the update, which also removes the phantom resource. 14 If the revision number did not automatically update in the previous steps, restart Novell Cluster Services by entering the following on one node in the cluster: cluster restart 9.12 Additional Information for Creating Cluster...
  • Page 131: Creating Virtual Machine Cluster Resources

    9.12.3 Creating Virtual Machine Cluster Resources If you install Novell Cluster Services at the host level of an OES 2 Linux (Xen) server, you can create cluster resources for the virtual machines. For information, see Section 12.2, “Virtual Machines as Cluster Resources,” on page 182.
  • Page 132 132 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 133: Configuring Cluster Resources For Shared Nss Pools And Volumes

    This section describes how to create shared disk partitions and Novell Storage Services (NSS) pools if they do not already exist and to configure the shared pools to work with Novell Cluster Services by cluster-enabling the pools. Section 10.1, “Planning for Shared NSS Pools and Volumes,” on page 133 Section 10.2, “Considerations for Working with Shared NSS Pools and Volumes in the...
  • Page 134: Shared Storage

    In order to use NSS pools and volumes in cluster resources, NSS must be installed and running on each server in the cluster. You can use the Storage plug-in for Novell iManager or the server-based NSSMU (NSS Management Utility) tool to create and cluster-enable a shared NSS pool, and to create NSS volumes on those pools.
  • Page 135: Ip Address

    Common Internet File System (CIFS) is the Windows networking protocol. The Novell CIFS for Linux service is available beginning in the OES 2 SP1 Linux release. Novell CIFS is required when you want to give clients access via CIFS to volumes on the shared NSS pool.
  • Page 136: Considerations For Working With Shared Nss Pools And Volumes In The Cluster

    Apple Filing Protocol (AFP) is the Macintosh* networking protocol. The Novell AFP for Linux service is available beginning in the OES 2 SP1 Linux release. Novell AFP is required when you want to give Macintosh clients access via AFP to volumes on the shared NSS pool.
  • Page 137: Creating Nss Shared Disk Partitions And Pools

    NSS supports Fibre Channel SAN and iSCSI SAN environments. External SCSI device arrays can also be configured for multiple server access. Before enabling sharing on shared storage, Novell Cluster Services must be installed and running on your servers.
  • Page 138: Creating Shared Nss Pools

    Selected (default): If you want to cluster-enable the pool at the same time it is created, leave the Cluster Enable on Creation check box selected, click Next, then continue with Step 10 on page 139. 138 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 139 Select the check boxes of the protocols you want to enable for data requests to this shared pool. If Novell CIFS or Novell AFP are not installed and running, selecting the CIFS or AFP check box has no effect. NOTE: For OES 2 Linux and earlier, Novell CIFS and Novell AFP are not available.
  • Page 140 This lets you ensure that the cluster-enabled pool you are creating is highly available to Novell clients and that authentication and access to the file system is enforced according to the Novell Trustee Model. 11 Click Finish. For NSS on Linux, the create time might take longer than expected. Typically, the pool creation takes less than a minute, and the volume creation takes less than 10 seconds.
  • Page 141 Specify Yes next to the protocols that you want to enable for data requests to this shared pool. If Novell CIFS or Novell AFP are not installed and running, selecting the CIFS or AFP check box has no effect. NOTE: On Linux, Novell CIFS and Novell AFP are available beginning in OES 2 SP1.
  • Page 142: Creating Nss Volumes On A Shared Pool

    NSSMU and enter the password. NSS uses the password to create a key. Instead of storing it in the server memory as it does for non-shared volumes, NSS asks Novell Cluster Services to store the key and to pass it to the other nodes. After all servers hold the key, the volume is available for access as long as any one of the servers is still participating actively in the cluster.
  • Page 143: Using Nssmu To Create Nss Volumes

    The volume quota is the maximum possible size of the volume. If you have more than one volume per pool, you can specify a quota for each volume rather than allowing multiple volumes to grow to the pool size. 8 Review and change volume attributes by selecting or deselecting the check boxes next to the attributes.
  • Page 144: Cluster-Enabling An Existing Nss Pool And Its Volumes

    If the objects are missing, you can use the Update eDirectory options in the Storage plug-in for NSS to create them in eDirectory. For information, see “Updating eDirectory Pool Objects” “Updating eDirectory Volume Objects” in the OES 2 SP2: NSS File System Administration Guide. 144 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 145 9 If Novell CIFS is running on the cluster server and you want to enable it for this pool, specify the CIFS Virtual Server Name (up to 15 characters), which is the name assigned to the virtual server for handling CIFS requests.
  • Page 146 11 Select the check boxes of the advertising protocols you want to enable for data requests to this shared pool. If Novell CIFS or Novell AFP are not installed and running, selecting the CIFS or AFP check box has no effect.
  • Page 147: Adding Advertising Protocols

    Novell CIFS. You can add Novell AFP or Novell CIFS as advertising protocols for an existing pool cluster resource. You must install Novell CIFS or Novell AFP on all the servers where you want to fail over the pool resource, but you set up the advertising protocol only once on the pool cluster resource. Before you begin, make sure the pool is migrated back to the server where it was originally created.
  • Page 148 IMPORTANT: In OES 2 SP1 Linux, the Novell CIFS commands are not automatically added to the load and unload scripts for the NSS pool resource when you add Novell CIFS as an advertising protocol on an existing cluster-enabled pool. You must run the script to add commands for Novell CIFS.
  • Page 149: Configuring A Load Script For The Shared Nss Pool

    Pool name SHPOOL43 Volume name SHVOL43 Volume ID 252 (valid values are 0 to 254) #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs exit_on_error nss /poolact=SHPOOL43 exit_on_error ncpcon mount SHVOL43=252 exit_on_error add_secondary_ipaddress 10.10.10.43 exit_on_error ncpcon bind --ncpservername=NCS1_SHPOOL43_SERVER -- ipaddress=10.10.10.43 exit 0 If you change the name space for an existing shared volume by using NSSMU or the NSS plug-in for iManager, you must modify the load script for the pool cluster resource to add the name space to command for the volume.
  • Page 150: Configuring An Unload Script For The Shared Nss Pool

    Section 10.10.2, “Requirements for NSS Mirroring,” on page 152 Section 10.10.3, “Creating and Mirroring NSS Pools on Shared Storage,” on page 152 Section 10.10.4, “Verifying the NSS Mirror Status in the Cluster,” on page 154 150 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 151: Understanding Nss Mirroring

    10.10.1 Understanding NSS Mirroring NSS mirroring is a checkpoint-based synchronous mirroring solution. Data blocks are written synchronously to multiple storage devices. It is an alternative to synchronous replication options that are provided by a SAN array. Hardware configuration and placement for NSS mirroring can vary depending on geography and fault tolerance requirements.
  • Page 152: Requirements For Nss Mirroring

    Novell Cluster Services should be installed and running prior to creating and mirroring partitions on shared storage. 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 device, whether in the cluster or not, have access to all of the volumes on the shared storage space unless you specifically prevent such access.
  • Page 153 All servers in the cluster are connected to a shared storage system One or more drive arrays are configured on the shared storage system At least 20 MB of free space on the shared storage system for a special cluster partition To ensure disaster recovery, the device you select to mirror should be in a different storage array.
  • Page 154: Verifying The Nss Mirror Status In The Cluster

    100%. 10.10.4 Verifying the NSS Mirror Status in the Cluster After you have configured NSS mirroring with Novell Cluster Services, you should check to ensure that it is working properly in a cluster environment. 1 Ensure that the volumes on the cluster-enabled pool are mounted on an assigned server by entering at the terminal console.
  • Page 155: Changing The Volume Id

    128. 10.12 Changing the Volume ID Novell Cluster Services supports NCP client access to cluster-enabled NSS volumes by using a unique volume ID to mount the volume in the cluster. The volume ID is used by an NCP client only for automatic reconnects to the volume after failover or migration of a cluster resource.
  • Page 156 156 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 157: Configuring Cluster Resources For Shared Linux Posix Volumes

    Volumes EVMS must be installed and running on each server in the cluster. You must install Novell Cluster Services before you create shared disk partitions on shared storage (storage area network, or SAN). Cluster Segment Manager (CSM) containers require Novell Cluster Services to be running on all nodes that access the CSM container.
  • Page 158: Creating Linux Posix Volumes On Shared Disks

    EVMS to create Linux partitions, volumes, and file systems on shared storage for use with Novell Cluster Services. EVMS virtual volumes can more easily be expanded and failed over to different cluster servers than can physical devices. You can create partitions and volumes for any of the journaled Linux file systems (such as Ext3 and ReiserFS).
  • Page 159: Creating A Cluster Segment Manager Container

    If the shared disk that you plan to use with your cluster is configured with segment managers other than the Cluster Segment Manager, you must also delete the other segment managers so that the CSM is the first one on the partition. 1 At a Linux terminal console, log in as the user, then enter root...
  • Page 160: Adding A Non-Csm Segment Manager Container

    IMPORTANT: CSM containers require Novell Cluster Services to be running on all nodes that access the CSM container. Make sure Novell Cluster Services is running before you continue. 1 In evmsgui, click Actions > Create > Container. 2 On the Create Storage Container page, select Cluster Segment Manager, then click Next.
  • Page 161: Creating An Evms Volume

    4 On the Configurable Options page, select the disk type (Linux is the default), click Add, then click OK. 5 Click Save, then click Save again to save your changes. 6 If you added a DOS segment manager, create a segment for it: IMPORTANT: Some segment managers such as the DOS segment manager require you to create a segment before creating an EVMS volume.
  • Page 162: Cluster-Enabling A Linux Posix Volume On A Shared Disk

    Section 11.3.3, “Configuring a Load Script for a Linux POSIX Volume Cluster Resource,” on page 164 Section 11.3.4, “Configuring an Unload Script for a Linux POSIX Volume Cluster Resource,” on page 165 162 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 163: Logging In To Imanager

    CLUS1_SHVOL44_SERVER Do not use periods in cluster resource names. Novell clients interpret periods as delimiters. If you use a space in a cluster resource name, that space is converted to an underscore. 6 In the Inherit From Template field, browse to the Cluster container object, then locate and select the Generic_FS_Template in that container.
  • Page 164: Configuring A Load Script For A Linux Posix Volume Cluster Resource

    If you later need to modify the IP address, administrator credentials, or other attributes of an existing resource, follow the procedure in Section 8.13, “Moving a Cluster, or Changing IP Addresses, LDAP Server, or Administrator Credentials for a Cluster,” on page 105. 164 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 165: Configuring An Unload Script For A Linux Posix Volume Cluster Resource

    #! /bin/bash . /opt/novell/ncs/lib/ncsfuncs # define the IP address RESOURCE_IP=a.b.c.d # define the file system type MOUNT_FS=reiserfs #define the container name container_name=name # define the device MOUNT_DEV=/dev/evms/$container_name/volume_name # define the mount point MOUNT_POINT=/mnt/mount_point # activate the container exit_on_error activate_evms_container $container_name $MOUNT_DEV...
  • Page 166: Enabling Monitoring And Configuring A Monitor Script For A Linux Posix Volume Cluster Resource

    Use the same values for the defined variables that you used in the load script in Section 11.3.3, “Configuring a Load Script for a Linux POSIX Volume Cluster Resource,” on page 164. 166 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 167: Configuring Policies For A Linux Posix Volume Cluster Resource

    Modify the variable values in the definition lines. For an example of the customized monitor script, see Section 11.5.3, “Sample Monitor Script for a Linux POSIX Volume Cluster Resource,” on page 176. #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs # define the IP address RESOURCE_IP=a.b.c.d # define the file system type MOUNT_FS=reiserfs #define the container name...
  • Page 168 2 (Conditional) Select the Ignore Quorum check box if you don't want the cluster-wide timeout period and node number limit enforced. The quorum default values were set when you installed Novell Cluster Services. You can change the quorum default values by accessing the properties page for the Cluster object.
  • Page 169: Creating A Virtual Server Name For The Cluster Resource

    Cluster Resource After you cluster-enable the Linux POSIX volume, you can create a virtual NCP Server object ) for the volume in Novell eDirectory. You bind this virtual server name with the NCS:NCP Server cluster resource IP address in order to make it possible for clients to access the cluster-enabled volume via the assigned name instead of the resource’s IP address.
  • Page 170 /opt/novell/ncs/bin 3 At the terminal console prompt, enter ./ncs_ncpserv.py -c ncs_ncp_server_name -i ncp_ip_address -v ncp_volumename Replace the ncp_server_name, ip_address, and volumes with the information for your particular solution. 170 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 171: Using Imanager To Create An Ncs:ncp Server Object

    For example, to include the NCP volume on the cluster resource where the IP USERS SHVOL44 address is 10.10.10.44, enter ./ncs_ncpserv.py -c CLUS1_SHVOL44_SERVER -i 10.10.10.44 -v USERS 4 In iManager, view the load script for the Linux POSIX volume cluster resource to verify that the load script was automatically updated with lines that define and bind the virtual NCP server name and its IP address.
  • Page 172: Sample Scripts For A Linux Posix Volume Cluster Resource

    Sample Value Description RESOURCE_IP a.b.c.d 10.10.10.44 IP address of the virtual cluster server for this cluster resource container_name name csm44 The name you gave to the cluster segment manager. 172 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 173 Variable Template Value Sample Value Description MOUNT_DEV The Linux path for the /dev/evms/ /dev/evms/ EVMS volume you $container_name/ $container_name/ created, such as volume_name shvol44 shvol44 MOUNT_FS reiserfs ext3 The file system type you made on the EVMS volume. MOUNT_POINT /mnt/mount_point /mnt/shvol44 The mount location for the EVMS volume you...
  • Page 174: Sample Load Script For The Linux Posix Volume Cluster Resource

    $container_name $MOUNT_DEV $NCS_TIMEOUT # mount the file system ignore_error mkdir -p $MOUNT_POINT exit_on_error mount_fs $MOUNT_DEV $MOUNT_POINT $MOUNT_FS # add the IP address exit_on_error add_secondary_ipaddress $RESOURCE_IP exit 0 174 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 175: Sample Unload Script For The Linux Posix Volume Cluster Resource

    11.5.2 Sample Unload Script for the Linux POSIX Volume Cluster Resource The following is an example unload script for the cluster resource for a Linux POSIX volume: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs # define the IP address RESOURCE_IP=10.10.10.44 # define the file system type...
  • Page 176: Sample Monitor Script For A Linux Posix Volume Cluster Resource

    4 Select Drive Linking Feature, then click Next. 5 Provide a name for the drive link, click Add, then save your changes. 6 Click Actions, select Create, and then select Container. 176 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 177: Moving A Volume To A Larger Disk

    7 Select the Cluster Segment Manager, click Next, then select the disk you want to expand the volume to. The entire disk is used for the expansion, so you must select a disk that does not have other volumes on it. 8 Provide the same settings information (same name, type (Private), owning node, and so on) as the existing container for the volume, the save your changes.
  • Page 178: Deleting Shared Storage

    11.8.2 Cluster Services Must Be Running When Using EVMS Novell Cluster Services must be running on all nodes in the cluster whenever you make any modifications to the cluster or cluster resources by using the EVMS management tools or the Clusters plug-in in iManager.
  • Page 179: Do Not Migrate Resources When Evms Tools Are Running

    Chapter 8, “Managing Clusters,” on page IMPORTANT: You can create an NCP volume on the shared Linux POSIX volume and cluster- enable the shared NCP volume. For information, see “Configuring NCP Volumes with Novell Cluster Services” in the OES 2 SP2: NCP Server for Linux Administration Guide.
  • Page 180 180 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 181: Configuring Novell Cluster Services In A Xen Virtualization Environment

    When using Novell Cluster Services to create cluster resources in a Xen host server environment, one network adapter on each cluster node must be available without Xen bridging to allow Novell Cluster Services to monitor for network state changes in the cluster. You need at least one other network adapter on each cluster node to use as a bridge for the virtual servers that will be hosted on the Xen host.
  • Page 182: Virtual Machines As Cluster Resources

    In this scenario, you have an OES 2 Linux cluster configured on physical machines. OES 2 Linux and Xen are installed and configured on each node along with Novell Cluster Services. This part of the Novell Cluster Services configuration does not differ from that of an OES 2 Linux cluster without virtualization.
  • Page 183: Creating A Xen Virtual Machine Cluster Resource

    Make sure that your Xen setup is working properly before you attempt to set up the Novell Cluster Services clustering for your virtual machines in the Xen host environment. Refer to the Virtualization with Xen (http://www.novell.com/documentation/sles10/book_virtualization_xen/...
  • Page 184: Configuring Virtual Machine Load, Unload, And Monitor Scripts

    “Sample XenLive_Template Load Script” on page 185 2 Click Next and continue with “Configuring the Unload Script” on page 185. Sample Xen_Template Load Script The Xen_Template load script appears similar to the following example: 184 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 185 1 View and, if necessary, edit the lines in the script for your specific directory structure, mount point, configuration files, and file system type (in the Xen_Template). Use the same values that you specified in the load script. Configuring Novell Cluster Services in a Xen Virtualization Environment 185...
  • Page 186 Xen # umount the file system ignore_error ocf_stop Filesystem # return status exit 0 Sample XenLive_Template Unload Script The XenLive_Template unload script appears similar to the following example: 186 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 187 5 For the polling interval, specify how often you want the resource monitoring script for this resource to run. You can choose to specify the number in minutes or seconds. Configuring Novell Cluster Services in a Xen Virtualization Environment 187...
  • Page 188 Sample Xen_Template Monitor Script The Xen_Template monitor script appears similar to the following example: 188 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 189: Setting Up Live Migration

    You also must ensure that all cluster nodes where the virtual machine will run have access to the OCFS2 file system on the shared disk system. Configuring Novell Cluster Services in a Xen Virtualization Environment 189...
  • Page 190: Virtual Machines As Cluster Nodes

    In this scenario, you have OES 2 Linux (Xen) installed and configured on each node (physical machine). You then create either a NetWare or a Linux virtual machine on each physical machine and install and configure Novell Cluster Services on each virtual machine. The combined virtual machines (cluster nodes) comprise one cluster.
  • Page 191: Virtual Cluster Nodes In Separate Clusters

    You then create multiple NetWare or Linux virtual machines on each physical machine and install and configure Novell Cluster Services on each virtual machine. During the Novell Cluster Services installation, you create separate clusters of virtual cluster nodes, with each virtual cluster node residing on a separate physical machine.
  • Page 192 Shared Disk System Another method is to install Novell Cluster Services on physical NetWare nodes and create a separate cluster for each node. You then install an OES 2 Linux (Xen) server (physical machine) and create NetWare virtual machines and install Novell Cluster Services on each virtual machine. You can then add one virtual NetWare cluster node to each cluster to create multiple two-node clusters, each containing one physical and one virtual cluster node.
  • Page 193: Additional Information

    OES 2 SP2: Installation Guide guide. For information on setting up virtualized OES 2 Linux, see “Installing, Upgrading, or Updating OES on a Xen-based VM” in the OES 2 SP2: Installation Guide guide. Configuring Novell Cluster Services in a Xen Virtualization Environment 193...
  • Page 194 194 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 195: Troubleshooting Novell Cluster Services

    Section 13.14, “Can’t Find the Prevent Cascading Failover Option,” on page 199 Section 13.15, “Is there a way to uninstall Novell Cluster Services from a server?,” on page 200 Section 13.16, “Cluster Resource Is Stuck in "NDS Sync" or "eDirectory Sync" State,” on page 200 13.1 File Location Information...
  • Page 196: Diagnosing Cluster Problems

    Resource templates /opt/novell/ncs/templates 13.2 Diagnosing Cluster Problems To help Novell Technical Support diagnose your cluster problems, some or all of the following information might be requested: Cluster statistics. A report created by the cluster statistics gathering tool. Cluster configuration. An HTML report created by the Clusters > Cluster Manager > Run Report option in the Clusters plug-in to iManager.
  • Page 197: Cluster Search Times Out (Bad Xml Error)

    SLP. For information, see “SLP” on page 13.6 smdr.novell Is Not Registered with SLP for a New Cluster Resource You might get an error after creating a cluster resource indicating that is not smdr.novell...
  • Page 198: Cluster View Displays The Wrong Cluster Node Name

    1 On the master node of the cluster, open a terminal console prompt as the user, then enter root the following commands: opt/novell/ncs/bin/ncs-configd.py -init echo -n "exec rm -f /var/opt/novell/ncs/data_server.*" > /proc/ncs/cluster 198 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 199: Problem Authenticating To Remote Servers During Cluster Configuration

    To avoid this problem, offline the cluster resource before attempting to delete either the cluster resource or the clustered pool. 13.13 Version Issues Knowing the location and purpose of the files that make up Novell Cluster Services can be useful in helping you troubleshoot problems and resolve version issues. For information, see Appendix B, “Files for Novell Cluster Services,”...
  • Page 200: Is There A Way To Uninstall Novell Cluster Services From A Server

    13.15 Is there a way to uninstall Novell Cluster Services from a server? There is not a utility to remove Novell Cluster Services and the related eDirectory objects. For information, see How to remove Clustering Services and the Clustering DS Objects (TID 3317095) (http://www.novell.com/support/php/...
  • Page 201: Security Considerations

    This section describes security issues and recommendations for Novell Cluster Services Novell Open Enterprise Server 2 Linux. It is intended for security administrators or anyone who is responsible for the security of the system. It requires a basic understanding of Novell Cluster Services.
  • Page 202: Log Files

    Section 7.4, “Configuring Cluster Event E-Mail Notification,” on page 14.4 Log Files Look for events in the NCS Event Log in the Clusters plug-in to Novell iManager 2.7.2 or later. Log files for cluster resources are written to the directory. Output log files are named /var/run/ncs with the resource name, load or unload to indicate which script, and the .out extension.
  • Page 203: A Console Commands For Novell Cluster Services

    Removes all cluster nodes from the cluster. Has the same DOWN effect as executing the command on CLUSTER LEAVE every server in the cluster. Executes the specified script on all nodes in the cluster. EXEC "path_to_script" Console Commands for Novell Cluster Services...
  • Page 204 Lists all resources that currently exist in the cluster. The RESOURCES resources do not need to be online or running. Restarts Novell Cluster Services software on all servers in RESTART {seconds} the cluster. 204 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 205 EMAILOPTIONS Specify XML as the value to receive e-mail notification in XML format. Not specifying any value with this parameter turns notification in XML format off. Console Commands for Novell Cluster Services 205...
  • Page 206: Business Continuity Clustering Commands

    A.2 Business Continuity Clustering Commands If Novell Business Continuity Clustering (BCC) 1.2 for OES 2 SP1 Linux is installed and running on the cluster, you can use the following additional commands to manage the BCC cluster cluster environment.
  • Page 207: Sbd Utility

    /opt/novell/oes-install/util/extend_schema --port 636 cn=admin,o=example pas5W0rd 10.1.1.1 /opt/novell/ncs/schema/ncpserver.preldif A.4 SBD Utility The SBD utility (sbdutil) allows you to create, find, or view a Novell Cluster Services SBD partition. IMPORTANT: The cluster SBD partition is not required unless you have shared storage in the cluster.
  • Page 208 Assume the device is a shared disk system instead of checking . An optional cluster.xml partition size (in MB) can also be specified when creating a partition (-c). The default size is 8 208 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 209: B Files For Novell Cluster Services

    Table B-1 lists the path and purpose for some of the files that are part of Novell Cluster Services. Location and Purpose of Novell Cluster Services Files Table B-1 NCS Filename and Path Purpose /etc/init.d/novell-ncs...
  • Page 210 SBDUTIL man page /var/opt/novell/ncs/hangcheck-timer.conf hang check option (comparable to CPU hog) Kernel module. Replace kernel_dir with the /lib/modules/kernel_dir/ncs/clstrlib.ko current kernel directory. Use uname -r see the current kernel directory. 210 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 211 Kernel module. Replace kernel_dir with the /lib/modules/kernel_dir/ncs/vipx.ko current kernel directory. Use uname -r see the current kernel directory. Kernel module. Replace kernel_dir with the /lib/modules/kernel_dir/ncs/vll.ko current kernel directory. Use uname -r see the current kernel directory. Files for Novell Cluster Services 211...
  • Page 212 212 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 213: C Comparing Novell Cluster Services For Linux And Netware

    Novell Open Enterprise Server (OES) 2 Linux to Novell Cluster Services 1.8.5 for NetWare NetWare 6.5 Support Pack 7 or later. Comparison of Novell Cluster Services for OES 2 Linux and NetWare 6.5 SP7 or Later Table C-1 Feature or Capability...
  • Page 214 NetWare 6.5 SP6 to OES 2 Linux or later NetWare 6.0 with latest service packs and patches to OES 2 Linux. Uses the same process as NetWare 6.5 to OES 2 Linux. 214 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 215 Yes; NCP is the default file Protocol installed if you create cluster access protocol on NetWare. resources that use NCP, such as NSS pools, NCP volumes, and Dynamic Storage Technology shadow volume pairs. Comparing Novell Cluster Services for Linux and NetWare 215...
  • Page 216 Section 12.2, “Virtual Machines as Cluster Resources,” on page 182. iManager 2.7 Clusters plug-in and Storage Management plug-in for iManager Cluster-enabling NSS pools by using the NSS plug-in for iManager 216 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 217 Linux POSIX file NCP users and Linux Samba/ systems CIFS users to concurrently access data. Requires users to be Linux- enabled with Linux User Management. Requires Universal Password. Comparing Novell Cluster Services for Linux and NetWare 217...
  • Page 218 “Managing Multipath I/O for Devices” in the Multipath I/O to Devices SLES 10 SP3: Storage (NetWare)” in the OES 2 SP2: Administration Guide. NSS File System Administration Guide. 218 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 219: D Comparing Clustering Support For Oes 2 Services On Linux And Netware

    Comparing Clustering Support for OES 2 Services on Linux and NetWare ® Table D-1 compares clustering support for Novell Open Enterprise Server (OES) 2 services when ® using Novell Cluster Services 1.8.5 on OES 2 Linux and NetWare 6.5 SP7 or later.
  • Page 220 SP1) for the cluster DHCP Administration resource. Guide for Linux. For information about converting a cluster resource from NetWare to Linux, see Section 6.3.7, “DHCP Server,” on page 220 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 221 “Creating a Cluster- “Configuring DNS the NCP Server must Enabled DNS Server” in with Novell Cluster be changed manually NW 6.5 SP8: Novell Services” in the OES 2 after the cluster DNS/DHCP Services SP2: Novell DNS/DHCP conversion. It is not done Administration Guide.
  • Page 222 2.1x is replace by iFolder 3.6 and later in “Configuring iFolder OES 2 Linux. on Novell Cluster Services” in the OES 2 SP1: Novell iFolder 2.1 Installation and Administration Guide. 222 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 223 Service OES 2 NetWare OES 2 Linux Comments Novell iFolder 3.6 Not applicable “Clustering iFolder 3.8 Servers with Novell Cluster Services for Linux”in the Novell iFolder 3.8 Administration Guide. Printing See iPrint. QuickFinder See Search. Search (QuickFinder) Yes; requires Yes; requires For information about QuickFinder 4.2.0.
  • Page 224 181. Xen virtual machines on Not applicable Yes; use the Xen and Section 12.2, the host server XenLive templates. “Virtual Machines as Cluster Resources,” on page 182. 224 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 225: E Documentation Updates

    Documentation Updates This section contains information about documentation content changes made to the Novell Cluster ® Services 1.8.5 for Linux Administration Guide since the initial 1.8.5 release for Novell Open Enterprise Server 2. If you are an existing user, review the change entries to readily identify modified content.
  • Page 226: Configuring And Managing Cluster Resources

    Unload Script for a Linux POSIX Volume Cluster Resource,” on page 165 Section 11.3.5, “Enabling Monitoring and Configuring a Monitor Script for a Linux POSIX Volume Cluster Resource,” on page 166 226 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 227: Configuring Novell Cluster Services In A Xen Virtualization Environment

    195 E.2 February 19, 2010 Updates were made to the following sections. The changes are explained below. Section E.2.1, “Installing and Configuring Novell Cluster Services on OES 2 Linux,” on page 227 Section E.2.2, “Managing Clusters,” on page 227 E.2.1 Installing and Configuring Novell Cluster Services on...
  • Page 228: February 10, 2010

    Updates were made to the following sections. The changes are explained below. Section E.4.1, “Converting NetWare 6.5 Clusters to OES 2 Linux,” on page 228 Section E.4.2, “Installing and Configuring Novell Cluster Services on OES 2 Linux,” on page 229 Section E.4.3, “Managing Clusters,”...
  • Page 229: Installing And Configuring Novell Cluster Services On Oes 2 Linux

    You can install an eDirectory master replica or replica in the cluster, but it page 29 is not required to do so for Novell Cluster Services. (eDirectory must be installed somewhere in the same tree.) “SBD Partitions” on page 37...
  • Page 230: January 20, 2010

    140, if you choose to cluster-enable the pool later, you Shared NSS Pools” on must create a volume on the shared pool before you attempt to cluster- page 140 enable the pool. 230 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 231: Converting Netware 6.5 Clusters To Oes 2 Linux

    Cluster” on page 73 E.7 December 15, 2009 Updates were made to the following section. The changes are explained below. Section E.7.1, “Installing and Configuring Novell Cluster Services on OES 2 Linux,” on page 231 E.7.1 Installing and Configuring Novell Cluster Services on...
  • Page 232: Converting Netware 6.5 Clusters To Oes 2 Linux

    E.9 November 2009 (OES 2 SP2) Updates were made to the following sections. The changes are explained below. Section E.9.1, “Configuring Novell Cluster Services in a Xen Host Environment,” on page 233 232 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 233: Configuring Novell Cluster Services In A Xen Host Environment

    Section E.9.2, “Converting NetWare 6.5 Clusters to OES 2 Linux,” on page 233 Section E.9.3, “Console Commands for Novell Cluster Services,” on page 233 Section E.9.4, “Installing Novell Cluster Services on OES 2 Linux,” on page 234 Section E.9.5, “Managing Clusters,” on page 234 Section E.9.6, “Troubleshooting Novell Cluster Services,”...
  • Page 234: Installing Novell Cluster Services On Oes 2 Linux

    New Cluster Resource,” on page 197 E.9.7 Upgrading OES 2 Linux Clusters Location Change Section 4.3, “Upgrade Issues This section is new. for OES 2 SP2,” on page 54 234 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 235: What's New

    Section E.10.2, “Console Commands for Novell Cluster Services,” on page 235 Section E.10.3, “Converting NetWare 6.5 Clusters to OES 2 Linux,” on page 236 Section E.10.4, “Installing Novell Cluster Services on OES 2 Linux,” on page 236 Section E.10.5, “Managing Clusters,” on page 236 Section E.10.6, “Security Considerations,”...
  • Page 236: Converting Netware 6.5 Clusters To Oes 2 Linux

    Change Section 6.1.10, “Using Novell This section is new. iManager in Mixed-Node Use Novell iManager 2.7.2 or later for all cluster administration in the Clusters,” on page 62 mixed-node cluster. Section 6.1.11, “Using Novell Do not use Novell Remote Manager when managing mixed-node clusters.
  • Page 237: Troubleshooting Novell Cluster Services

    E.10.7 Troubleshooting Novell Cluster Services Location Change Section 13.2, “Diagnosing This section is new. Cluster Problems,” on page 196 Section 13.9, “Could Not This section is new. Delete This Resource Data_Server (Error 499),” on page 198 E.10.8 What’s New Location Change Section 2.3.4, “Attribute...
  • Page 238: June 5, 2009

    Section E.12.3, “Console Commands for Novell Cluster Services,” on page 238 Section E.12.4, “Converting NetWare 6.5 Clusters to OES 2 Linux,” on page 239 Section E.12.5, “Installing Novell Cluster Services on OES 2 Linux,” on page 239 Section E.12.6, “Managing Clusters,” on page 239 E.12.1 Configuring Cluster Policies and Priorities...
  • Page 239: Converting Netware 6.5 Clusters To Oes 2 Linux

    OES 2 Linux Nodes to Your necessary only if the cluster has a shared disk system. NetWare Cluster,” on page 81 E.12.5 Installing Novell Cluster Services on OES 2 Linux Location Change Section 3.1.4, “Shared Disk The following statement was added for clarification: System Requirements,”...
  • Page 240: May 6, 2009

    Section E.13.2, “Configuring and Managing Cluster Resources,” on page 240 Section E.13.3, “Converting NetWare 6.5 Clusters to OES 2 SP1 Linux,” on page 241 Section E.13.4, “Installing Novell Cluster Services on OES 2 Linux,” on page 241 Section E.13.5, “Troubleshooting Novell Cluster Services,” on page 241 Section E.13.6, “Upgrading OES 2 Linux Servers,”...
  • Page 241: Converting Netware 6.5 Clusters To Oes 2 Sp1 Linux

    Clusters,” on page 62 temporarily remove all Linux cluster nodes by issuing the cluster command prior to making any NSS changes. leave E.13.4 Installing Novell Cluster Services on OES 2 Linux Location Change Section 3.3, “Extending the Removed references to .
  • Page 242: Upgrading Oes 2 Linux Servers

    Upgrade),” on page 53 Make sure that any services that are available only in OES 2 SP1 (such as Novell CIFS or Novell AFP) are set up with preferred nodes for failover that are running OES 2 SP1. Several guidelines are provided about the mixed-version cluster.
  • Page 243: Converting Netware 6.5 Clusters To Oes 2 Linux

    Node,” on page 109 E.14.5 What’s Next Location Change Section 2.3.3, “Behavior IMPORTANT: A Novell Cluster Services patch is available in the patch Change for Adding a Node,” channel and on the Novell Downloads Web site (http://www.novell.com/ on page 25...
  • Page 244: Converting Netware 6.5 Clusters To Oes 2 Linux

    Section E.16.2, “Configuring Cluster Resources for Shared NSS Pools and Volumes,” on page 244 Section E.16.3, “Converting NetWare 6.5 Clusters to OES 2 Linux,” on page 245 Section E.16.4, “Installing Novell Cluster Services on OES 2 Linux,” on page 245 E.16.1 Configuring and Managing Cluster Resources Location...
  • Page 245: Converting Netware 6.5 Clusters To Oes 2 Linux

    Section E.18.1, “Comparison of Clustering OES 2 Services for Linux and NetWare,” on page 246 Section E.18.2, “Comparison of Novell Cluster Services for Linux and NetWare,” on page 246 Section E.18.3, “Configuring and Managing Cluster Resources,” on page 246 Section E.18.4, “Configuring Cluster Resources for Shared Linux POSIX Volumes,” on page 246 Section E.18.5, “Configuring Cluster Resources for Shared NSS Pools and Volumes,”...
  • Page 246: Comparison Of Clustering Oes 2 Services For Linux And Netware

    Volumes Location Change Section 10.3, “Creating NSS Added information about using Novell CIFS for Linux and Novell AFP for Shared Disk Partitions and Linux when cluster-enabling pools on OES 2 SP1 Linux and later. Pools,” on page 137 Section 10.4, “Creating NSS IMPORTANT: When adding volumes on a shared pool, make sure that Volumes on a Shared Pool,”...
  • Page 247: Configuring Novell Cluster Services In A Virtualization Environment

    Location Change Section 10.5, “Cluster- Added information about using Novell CIFS for Linux and Novell AFP for Enabling an Existing NSS Linux when cluster-enabling pools on OES 2 SP1 Linux and later. Pool and Its Volumes,” on page 144 Section 10.6, “Adding This section is new.
  • Page 248: Converting Netware 6.5 Cluster To Oes 2 Linux

    This section is new. It explains a new feature for extending the schema in eDirectory Schema to Add a Novell eDirectory tree before clusters are installed. Cluster Objects,” on page 40 248 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 249: Managing Clusters

    Addresses, LDAP Server, or The procedure has been updated for clarity. Administrator Credentials for a Cluster,” on page 105 E.18.11 Overview of Novell Cluster Services Location Change Section 1.1, “Why Should I This section is new.
  • Page 250: What's New

    Pool and Its Volumes,” on page 144 Section 10.10, “Mirroring and This section is new. Cluster-Enabling Shared NSS Pools and Volumes,” on page 150 250 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 251: Configuring Cluster Resources For Shared Linux Posix Volumes

    Chapter 11, “Configuring Cluster Resources for Shared Linux POSIX Volumes,” on page 157 The following additional changes were made: Location Change Section 3.1, “System This section is new. Requirements for Novell Cluster Services,” on page 27 Section 3.2, “Novell Cluster This section was updated. Services Licensing,” on page 39 Documentation Updates 251...
  • Page 252: Managing Novell Cluster Services

    Cluster,” on page 103 Section 8.15, “Deleting a The procedure was edited for clarity. Cluster Node from a Cluster, or Reconfiguring a Cluster Node,” on page 109 252 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...
  • Page 253: May 2, 2008

    E.20 May 2, 2008 Updates were made to the following sections. The changes are explained below. Section E.20.1, “Installation and Setup,” on page 253 Section E.20.2, “Managing Novell Cluster Services,” on page 253 E.20.1 Installation and Setup Location Change Section 3.5.1, “Installing...
  • Page 254 254 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide...

Table of Contents