Table of Contents
Advertisement
Quick Links
Advertisement
Table of Contents
Summary of Contents for Novell D7171A - NetServer - LPr
- Page 2 Novell, Inc. makes no representations or warranties with respect to the d i s c l a i m e r contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
-
Page 3: Table Of Contents
ontents Introduction to Cluster Services Introduction to Cluster Services ......Overview Product Features ........Product Benefits. - Page 4 Cluster Protocol Properties ......Heartbeat ....... . Tolerance .
-
Page 5: Introduction To Cluster Services
Introduction to Cluster Services Novell Cluster Services is a server clustering system that ensures high availability and manageability of critical network resources including data (volumes), applications, server licenses, and services. It is a multinode, NDS- enabled clustering product for NetWare 5 that supports failover, failback, and migration (load balancing) of individually managed cluster resources. - Page 6 Overview and Installation...
-
Page 7: Overview
c h a p t e r Overview ® NetWare Cluster Services is a server clustering system that ensures high availability and manageability of critical network resources including data (volumes), applications, server licenses, and services. It is a multinode clustering product for NetWare 5 that is enabled for NDS and supports failover, failback, and migration (load balancing) of individually managed cluster resources. -
Page 8: Product Benefits
Product Benefits NetWare Cluster Services allows you to configure up to 32 NetWare 5 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 can be moved manually to troubleshoot hardware or balance the workload. - Page 9 two Web sites. All the data, graphics, and e-mail messages 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. Web Server 1 Web Server 2 Web Server 3 Web Site A...
- Page 10 Web Site A moves to Web Server 2 and Web Site B moves to Web Server 3. IP addresses and applicable licenses 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.
-
Page 11: Cluster Configuration
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 fiber channel cards, cables, and switches, or be configured to use shared SCSI. If a server fails, another designated server in the cluster automatically mounts the shared subsystem volumes previously mounted on the failed server. -
Page 12: Cluster Components
Network Hub Server 1 Server 2 Network Network SCSI SCSI Interface Interface Adapter Adapter Card Card Shared Disk System Cluster Components The following components make up a NetWare Cluster Services cluster: • From 2 to 32 NetWare 5 servers configured to use IP, each containing at least one local disk device (used for a local SYS: volume). -
Page 13: Installation And Setup
c h a p t e r Installation and Setup Hardware Requirements ® The following list specifies hardware requirements for installing NetWare Cluster Services . These requirements represent the minimum hardware configuration. Additional hardware might be necessary depending on how you intend to use NetWare Cluster Services. -
Page 14: Shared Disk System Requirements
® The Novell Client included on the NetWare Cluster Services product CD installed on the workstations used to manage and access your cluster. ConsoleOne installed (from the NetWare Cluster Services product CD) on the workstation used to manage your cluster. Shared Disk System Requirements A shared disk system is required for each cluster if you want data to be highly available. -
Page 15: Installing Netware Cluster Services
Installing NetWare Cluster Services The NetWare Cluster Services installation • Creates a new Cluster object in NDS. • Installs NetWare Cluster Services software on the servers you specify to be part of your cluster. • Updates the AUTOEXEC.NCF file on each of the servers in your cluster. Note changes to AUTOEXEC.NCF: •... - Page 16 The server base license upgrade is installed when you install NetWare Cluster Services and is placed in the same context as its Server object. • All server connection licenses for each cluster server are deleted and are all replaced with one or more Cluster User Access Licenses (CUAL). You need one or more CUALs to equal the number of connections for the server connection licenses that are deleted.
-
Page 17: Begin The Installation
Begin the Installation To begin the installation, insert the NetWare Cluster Services CD and complete the following steps: From the initial splash screen, launch the NetWare Cluster Services installation. Continue through the installation screens until you get to the screen that prompts you to create a new cluster or edit an existing cluster. - Page 18 I m p o r t a n t You must have at least 10 MB of free space that is not part of an NSS partition 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 NetWare Cluster Services.
-
Page 19: Add Servers To The Cluster
Add Servers to the Cluster After creating your cluster, you will need to run the NetWare Cluster Services installation again each time you want to add additional servers to your cluster. If you plan to add new nodes to an existing cluster in the future, you should reserve those nodes before bringing up your cluster. -
Page 20: Setting Up Netware Cluster Services
begin to failover from servers that have left the cluster to servers that are still in the cluster. Type ULDNCS at the server console on every server in the cluster. This will unload NetWare Cluster Services software on each server. On a server in your NDS tree, Run DSRepair >... -
Page 21: Create Cluster Volumes
Create Cluster Volumes If you plan on using a shared disk system in your cluster and need to create new NetWare volumes, those volumes must be created with only one server up in the cluster. The server used to create the volumes should already have NSS installed and running. -
Page 22: Create Cluster Resource Templates
Click Create, then continue with “Set Failover and Failback Modes” on page 19. To complete the process for cluster-enabling a volume, you now need to set failover and failback modes and if necessary, change the node assignments for the volume (See “Assign Nodes to a Resource” on page 20). -
Page 23: Create Cluster Resources
Create Cluster Resources Cluster resources must be created for every resource or application you run on servers in your cluster. Cluster resources can include Web sites, e-mail servers, databases, and any other server-based applications or services you want to make available to users at all times. In ConsoleOne, browse and select the Cluster object you want to create resources for. -
Page 24: Configure Unload Scripts
Edit or add the necessary commands to the script to load the resource on the server. Some commands may require command line input. You can add << to a command to indicate command-line input. For example, a script command might read: LOAD SLPDA <<Y This means that when SLPDA is loaded, it will receive a Y at the command-line, presumably to a question that needs a yes answer. -
Page 25: Set Failover And Failback Modes
Specify a timeout value. The default is 600 seconds, or 10 minutes. The timeout value determines how much time the script is given to complete. If the script does not complete within the specified time, the resource becomes idle. Set Failover and Failback Modes You can configure failover and failback of cluster resources to happen manually or automatically. -
Page 26: Assign Nodes To A Resource
Assign Nodes to a Resource When you create a resource on a cluster or cluster-enable a volume, the nodes in the cluster are automatically assigned to the resource or volume. The order of assignment is the order the nodes appear in the resource list. You can assign or unassign nodes to the resource or volume, or change the failover order. -
Page 27: Edit Quorum Membership And Timeout Properties
Select the Advanced Settings tab. Verify or change the settings to the following: Auto Reconnect Level=3 Auto Reconnect Timeout=default Handle Net Errors=ON Name Cache Level=0 Net Status Timeout=60 Netware Protocol=NDS For Windows NT* clients: In the Control Panel, select Network, then select Services. Select Novell Client for NT and verify or change the following settings. -
Page 28: Timeout
value to 4, there must be four servers up in the cluster before any resource will load and start. Timeout Timeout specifies the amount of time to wait for the number of servers defined in the Membership field to be up and running. If the timeout period elapses before the quorum membership reaches its specified number, resources will automatically start loading on the servers that are currently up and running in the cluster. -
Page 29: Master Watchdog
Master Watchdog Master Watchdog specifies the amount of time between transmits for the master node in the cluster. For example, if you set this value to one, the master node in the cluster will transmit an "I’m alive" signal to all the other nodes in the cluster every second. -
Page 30: Number+Ip Address
Number+IP Address Number+IP Address specifies the cluster node number and IP address for the selected node. If the cluster node number or IP address changes for the selected node, the new information is not automatically updated in NDS. Edit the information and click Apply to update the information in NDS. -
Page 31: Identify Cluster And Resource States
unloaded until you load it again. This option is useful for editing resources since resources can’t be edited while loaded or running on a server. Identify Cluster and Resource States The Cluster State view in ConsoleOne gives you important information about the status of servers and resources in your cluster. - Page 32 Resource State Description Possible Actions Alert Either the Start, Failover, Click the Alert status or Failback mode for the indicator and depending resource has been set to on the resource state, you Manual. The resource is will be prompted to Start, waiting to start, failover, or Failover, or Failback the failback on the specified...
-
Page 33: Netware Cluster Services Console Commands
Resource State Description Possible Actions NDS_Sync The properties of the None. resource have changed and the changes are still being synchronized in NDS. Offline Offline status indicates the Click the Offline status resource is shutdown or is indicator and if desired, in a dormant or inactive click the online button to state. - Page 34 a user or group was deleted without removing trustee rights to files on the volume, or because NDS didn’t synchronize soon enough after new users with trustee assignments were added to the tree. Occasional problems occur if a volume fails over immediately after a user is deleted who had trustee rights to that volume.