Novell Home

Configuring ZENworks for Desktops 2 with NetWare Cluster Services

Novell Cool Solutions: Feature
By Todd Grant

Digg This - Slashdot This

Posted: 31 May 2000
 

Current version: ZENworks 2

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.

This means that if you want to ensure all the services provided by ZENworks for Desktops 2 (ZfD) are highly available at all times, NetWare Cluster Services is the way to go. For example, you may be using ZfD primarily to push software updates out to all your users. If it is important to you that software updates occur even during planned or unplanned server hardware or software outages, you should consider implementing NetWare Cluster Services.

Configuring ZfD to work with NetWare Cluster Services can be a little tricky, so read on to find out how to do it.

ZENworks for Desktops Installation and Configuration

Before running ZfD with NetWare? Cluster Services?, you must have at least two NetWare 5.x servers. You must also have NetWare Cluster Services installed and running on each of the servers that will be part of your cluster. A cluster-enabled shared disk volume (also called a virtual server) is also required prior to installing and configuring ZfD with NetWare Cluster Services. For more information on cluster-enabling shared volumes, see the documentation about NetWare Cluster Services, in the section on how to Cluster-Enable Volumes.

Because of some limitations of the current ZfD installation procedure for installing into a cluster environment, you must change the installation procedure to account for the install location of ZfD files, for the ZENworks Inventory database mechanism and service, and for the behavior of NetWare Clients shipped and installed with ZENworks for Desktops 2.

During the ZfD installation, some files are copied to the SYS:PUBLIC directory of the server where ZfD is installed. These ZfD files must reside on the shared disk volume for ZfD to function properly with NetWare Cluster Services. To avoid problems, copy the entire SYS:PUBLIC directory to the shared disk volume and run all ZfD components from that volume.

An option in the ZfD installation allows you to install the ZENworks Inventory database to the volume of your choice. You must install the Inventory database on the shared disk volume for ZfD to function properly with NetWare Cluster Services. The installation also creates a configuration file (STORER.NCF). This file includes a line specifying the address of the server currently running the Inventory database. You must modify this line to include the address of the shared disk volume.

Application Object Templates (AOTs) must be stored on the shared disk volume. Some AOTs are installed automatically by ZfD. You must move these AOTs to the shared disk volume and update their SOURCE_PATH macro to point to the shared disk volume.

The ZfD installation also adds lines to the server's AUTOEXEC.NCF file that load certain ZENworks services. You must comment these lines in the file and add them to the volume load script. You must also add similar lines to the volume unload script to unload these ZENworks services.

Installing ZENworks for Desktops 2

ZENworks for Desktops 2 must be installed on at least two servers in the cluster.

To install ZENworks for Desktops 2:

  1. Log in as Admin to the NDS tree where your cluster resides. Specify the IP address of the cluster-enabled volume in the Server field.

    If you have trouble accessing the cluster-enabled volume after logging in, ensure you have the client required by NetWare Cluster Services.

  2. Map a drive to the shared disk volume, specifying or selecting the name you assigned the cluster-enabled volume (virtual server).

    The cluster-enabled shared disk volume will host the ZENworks Inventory database. Mapping a drive to the shared disk volume allows the ZfD installation program to access the shared volume and install the Inventory database to it.

  3. Insert the ZENworks for Desktops 2 product CD and install the product.

    Follow the instructions provided in the installation dialog boxes. During the installation, you will be prompted to select an NDS tree and a server. Select the NDS tree where your cluster resides and the cluster- enabled shared disk volume (virtual server).

  4. Migrate the cluster-enabled shared disk volume to another server in your cluster and repeat Step 3 to install ZfD on that server.

    For more information see Migrate Resources in the online documentation.

  5. Repeat Steps 3 and 4 on each server where ZfD is to be installed.

Configuring ZENworks for Desktops 2

After installing ZENworks for Desktops 2, you must modify certain configuration files on each of the servers in the cluster where it was installed.

To modify the configuration files:

  1. Using a text editor, open the STORER.NCF file on one of the cluster servers where ZfD was installed.

    The file can be found at SYS:\PUBLIC\ZENWORKS\JAVA.

  2. Edit the following line in the STORER.NCF file:

    JAVA -NS COM.NOVELL.ZENWORKS.DESKTOP.INVENTORY.STORER.LOADER- DBLOK IP address

    Replace IP address with the IP address of the cluster-enabled shared volume and save the file.

  3. Using a text editor, open the AUTOEXEC.NCF file on the same server.
  4. Copy the lines in the AUTOEXEC.NCF file that were created by the ZfD installation and paste them into a blank text file.

    The ZENworks section in the AUTOEXEC.NCF file starts with

    SEARCH ADD SYS:\PUBLIC\ZENWORKS\JAVA

    and ends with

    SYS:\PUBLIC\ZENWORKS\JAVA\STORER.NCF

    You will later use the text file to add commands to NetWare Cluster Services load and unload scripts.

  5. Comment out or delete the ZENworks lines in the AUTOEXEC.NCF file, and save the file.
  6. Repeat Steps 1, 2, 3, and 5 for all servers in the cluster that have ZfD installed.

NetWare Cluster Services Configuration and Setup

When ZENworks for Desktops 2 is installed and configured, you must edit the load and unload scripts for the cluster-enabled volume that was used during the ZfD installation. You must also set Start, Failover and Failback modes for the cluster-enabled volume and assign the volume to specific nodes in your cluster.

Configuring ZENworks for Desktops 2 Cluster Volume Load and Unload Scripts

Load and unload scripts are required by NetWare Cluster Services to mount and dismount cluster-enabled volumes on different servers in the cluster.

To edit the cluster-enabled volume load and unload scripts:

  1. In ConsoleOne?, right-click the Cluster Volume object and select Properties.
  2. Click the Load Script tab on the property page and copy the lines from the text file you created in the previous section. Paste the lines in the load script immediately after the command to mount the cluster volume.

    The following ZENworks specific commands should now appear in the cluster volume load script:

    SEARCH ADD SYS:\PUBLIC\ZENWORKS\JAVA
    LOAD JAVA.NLM
    SYS:\SYSTEM\JVORBCFG.NET
    LOAD ORBCMD.NLM
    LOAD OSAGENT.NLM
    SYS:\PUBLIC\ZENWORKS\JAVA\ALARMMGR.NCF
    SEARCH ADD SHAREDVOL:\ZENWORKS\DATABASE
    SHAREDVOL:\ZENWORKS\DATABASE\SYBASE.NCF
    SYS:\SYSTEM\GATHERE.NCF
    SYS:\PUBLIC\ZENWORKS\JAVA\MASTER.NCF
    SYS:\PUBLIC\ZENWORKS\JAVA\STORER.NCF

    Replace all occurrences of SHAREDVOL with the name of the cluster- enabled volume.

  3. Click the Unload Script tab on the property page and add the following lines immediately prior to the volume dismount command:

    UNLOAD DBSRV6.NLM <<Y
    UNLOAD ZENINV
    UNLOAD SNMPLOG
    UNLOAD OSAGENT
    UNLOAD ORBCMD
    UNLOAD JAVA

    The UNLOAD JAVA command will close all Java processes. This means that all Java-based applications currently running, including ConsoleOne, will be terminated.

Setting Cluster Volume Start, Failover, and Failback Modes

By default, NetWare Cluster Services sets the cluster volume Start Mode and Failover Mode to AUTO, and the Failback Mode to DISABLE. If the cluster volume Start Mode is set to AUTO, the volume automatically mounts on a server when the cluster is first brought up. If the cluster volume Start Mode is set to MANUAL, you can manually mount the cluster volume on a server at your discretionm, rather than having it automatically mount when servers in the cluster are brought up.

If the cluster volume Failover Mode is set to AUTO, the cluster volume automatically mounts on the next server in the Assigned Nodes list in the event of a hardware or software failure. If the cluster volume Failover Mode is set to MANUAL, you can intervene after a failure occurs and before the cluster volume mounts on another server.

If the cluster volume Failback Mode is set to DISABLE, the volume will not fail back to its most preferred node when the most preferred node rejoins the cluster. If the cluster volume Failback Mode is set to AUTO, the volume will automatically fail back to its most preferred node when the most preferred node rejoins the cluster. Set the cluster volume Failback Mode to MANUAL to prevent the volume from moving back to its preferred node when that node is brought back online, until you are ready to allow it to happen.

To view or change cluster volume Start, Failover, and Failback modes:

  1. In ConsoleOne, right-click the Cluster Volume object and select Properties.
  2. Click the Policies tab on the property page.
  3. View or change the Start, Failover or Failback modes for the Cluster Volume.

Setting Cluster Volume Server Assignments

NetWare Cluster Services by default assigns the cluster volume resource to all nodes in the cluster. The order of assignment is the order the nodes appear in the resource list. To view or edit cluster volume resource node assignments or change the server failover order:

  1. In ConsoleOne, right-click the Cluster Volume Resource object and select Properties.
  2. Click the Nodes tab on the property page.
  3. View the current cluster volume resource server assignments, and if necessary, click the right or left arrow button to assign or unassign servers to the cluster volume resource.

    You can click the up or down arrow button to change the failover order of the servers assigned to the cluster volume.

Copying ZENworks for Desktops 2 Directories and Updating Components

After installing and configuring ZENworks for Desktops 2 and NetWare Cluster Services, you must perform some additional configuration to ensure that ZfD will function properly with NetWare Cluster Services.

  1. From one of the cluster servers that has ZfD installed, copy the SYS:PUBLIC directory to the root of the shared cluster volume.

    ZENworks for Desktops 2 installs several files in the SYS:PUBLIC directory. Most of these files must reside on the shared cluster volume for ZfD to function properly with NetWare Cluster Services. To save time and avoid potential problems, copy the entire SYS:\PUBLIC directory rather than trying to determine exactly which files are necessary.

  2. Use NetWare Administrator to modify the AOT files that were installed by ZfD.

    The AOT files must be modified to point to the shared cluster volume.

  3. Reboot or restart each cluster server where ZfD was installed.

Additional NetWare Cluster Services Configuration Information

For additional information on setting up and configuring NetWare Cluster Services, see the documentation.

About the Author

Todd Grant is a technical writer for Novell with 13 years experience working in the software testing and technical documentation fields. Todd enjoys toying around with computer hardware, which is one reason he has an interest in NetWare Cluster Services.


Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com

© 2014 Novell