Novell Documentation: ZENworks 6.5 - Getting Started with Clustering

Getting Started with Clustering

Before you install a ZENworks Server Management component in a clustered environment, you must install Novell Cluster Services and perform some preparatory tasks:

Meeting System Requirements for Clustering

ZENworks Server Management components can be installed in a cluster that meets the following requirements:

DNS
DNS must be functioning reliably throughout your network so that DNS hostnames and IP addresses can always be successfully resolved.
NetWare 6.5 with SP1a or SP2
or

NetWare 6 with SP4 or SP5

or

NetWare 5.1 with SP6, SP7, or SP8 (SP8 if SP1 or SP2 is applied to ZENworks 6.5)

With NetWare 5.1, you need to meet the following additional requirements:
- Novell Cluster Services Support Pack 2 or 3 or later
- The latest Novell Cluster Services snap-in to ConsoleOne^®
  You can download the latest snap-in, along with the version of ConsoleOne that supports it, from Novell Software Downloads. This version includes changes that enable you to modify cluster-related object names.
IMPORTANT: Novell Cluster Services does not support mixed NetWare versions within a cluster.

Cluster-Enabling Shared Volumes for Use with ZENworks Server Management Components

Cluster-enabling the shared volumes where ZENworks Server Management components are installed is required.

Understanding Cluster-Enabling

To review the concept of cluster-enabled shared volumes, see the applicable section of Novell Cluster Services Overview and Installation for your version of NetWare:

NetWare 6.5: Cluster-Enabling Shared Volumes for Use with ZfS Components
NetWare 6: "Cluster Enable Pools and Volumes"
NetWare 5.1: "Cluster-Enable Volumes "

When you cluster-enable a volume, additional eDirectory objects are created:

Object	Object Name and Description
	cluster_name_volume_name (default object name) A new Volume object represents the cluster-enabled volume. It is created by renaming the original Volume object that was tied to a physical server and associating it with a virtual server instead. For example, if your cluster name is ZFSCLUSTER and your original volume name is ZFSVOL1, the new Volume object representing the cluster-enabled volume is named ZFSCLUSTER_ZFSVOL1.
	cluster_name_volume_name_SERVER (default object name) A new Server object represents the virtual server to which the new cluster-enabled volume is tied. Continuing with the above example, the new Server object representing the virtual server is named ZFSCLUSTER_ZFSVOL1_SERVER.
	volume_name_SERVER.clustername (default object name) A new Volume Resource object stores property information for the cluster-enabled volume. The Volume Resource object is created in the Cluster container object. Continuing with the above example, the new Volume Resource object is named ZFSVOL1_SERVER.ZFSCLUSTER.

Object

Object Name and Description

New Volume object

cluster_name_volume_name (default object name)
A new Volume object represents the cluster-enabled volume. It is created by renaming the original Volume object that was tied to a physical server and associating it with a virtual server instead.

For example, if your cluster name is ZFSCLUSTER and your original volume name is ZFSVOL1, the new Volume object representing the cluster-enabled volume is named ZFSCLUSTER_ZFSVOL1.

New Server object

cluster_name_volume_name_SERVER (default object name)
A new Server object represents the virtual server to which the new cluster-enabled volume is tied.

Continuing with the above example, the new Server object representing the virtual server is named ZFSCLUSTER_ZFSVOL1_SERVER.

New Volume Resource object

volume_name_SERVER.clustername (default object name)
A new Volume Resource object stores property information for the cluster-enabled volume. The Volume Resource object is created in the Cluster container object.

Continuing with the above example, the new Volume Resource object is named ZFSVOL1_SERVER.ZFSCLUSTER.

IMPORTANT: The default object names include the underscore (_) character. However, DNS name servers cannot resolve object names that include underscore characters. If you have met the requirements described in Meeting System Requirements for Clustering, you can rename these objects as needed when you cluster-enable the volume.

Cluster-Enabling a Shared Volume

To cluster-enable a shared volume for use with a ZENworks Server Management component:

Complete the steps in the applicable section of Novell Cluster Services Overview and Installation for your version of NetWare:
- NetWare 6.5: Cluster-Enabling Shared Volumes for Use with ZfS Components
- NetWare 6: "Cluster Enable Pools and Volumes"
- NetWare 5.1: "Cluster-Enable Volumes "
If necessary, rename cluster-related objects to eliminate the underscore (_) characters that are included by default.
Repeat Step 1 and Step 2 above for the other shared volumes that need to be cluster-enabled for use with ZENworks Server Management components.
Install a ZENworks Server Management component in the cluster, following the instructions in:
- Installing Policy and Distribution Services and Server Inventory in a Cluster
- Installing Management and Monitoring Services in a Cluster

Installing Novell Cluster Services

Install Novell Cluster Services by following the instructions provided in NetWare Cluster Services Overview and Installation for your version of NetWare:

NetWare 6.5: Installing ZENworks for Servers in a Clustered Environment
NetWare 6: "Installation and Setup"
NetWare 5.1: "Installation and Setup"

The installation process includes:

Meeting hardware and software requirements for Novell Cluster Services
Setting up a shared disk system
Creating a new Cluster object to represent the cluster in eDirectory
Adding servers to the cluster
Installing the Novell Cluster Services software on all nodes in the cluster
Mounting the shared volumes where you will install ZENworks Server Management components

As you install Novell Cluster Services, record key information about the cluster. You need this information as you install ZENworks Server Management components in the cluster:

eDirectory tree where you create the Cluster object
Name of the Cluster object
Context of the Cluster object