Novell BrainShare 2002 Achieving High Availability for ZENworks® Solutions with Novell Cluster Services™ Mark S Schouls Consultant Novell, Inc. mschouls@novell.com Peter W Henneberry Senior Consultant phenneberry@novell.com TUT310—Achieving High Availability for ZENworks Solutions with Novell Cluster Services

Vision…one Net Mission A world where networks of all types—corporate and public, intranets, extranets, and the Internet—work together as one Net and securely connect employees, customers, suppliers, and partners across organizational boundaries Mission To solve complex business and technical challenges with Net business solutions that enable people, processes, and systems to work together and our customers to profit from the opportunities of a networked world

What Is Novell ZENworks®? Novell BrainShare 2002 What Is Novell ZENworks®? The Novell ZENworks family of products… Automates and personalizes content and applications to increase productivity for end users and network managers alike Allows you to minimize costs by reducing redundancies, effectively leveraging your resources and precisely tracking their use TUT310—Achieving High Availability for ZENworks Solutions with Novell Cluster Services

The ZENworks Family ZENworks for Desktops ZENworks for Servers Novell BrainShare 2002 The ZENworks Family ZENworks for Desktops Manages the complete workstation lifecycle and provides personalized workstation service to end users ZENworks for Servers Provides cross-platform server consistency, content distribution, and management of critical resources, alarms, SNMP, and inventory assets ZENworks Preboot Services Enables PXE integration for ZENworks for Desktops workstation disk imaging ZENworks for Handhelds Automates management for wireless and handheld devices ZENworks OnDemand Services Automates digital asset provisioning to users wherever they are; tracks and reports usage; manages and personalizes terminal services ZENworks Synergy Extends the managed, personalized work environment to any location from any Windows machine TUT310—Achieving High Availability for ZENworks Solutions with Novell Cluster Services

Purpose of the Presentation… Demonstrate how to achieve high availability with your ZENworks solutions (ZENworks for Desktops and ZENworks for Servers) using clustering technologies provided by Novell Discuss the benefits of cluster-enabling your ZENworks solutions

This Session Covers… High availability of your ZENworks for Desktops solutions using Novell Cluster Services™ High availability of your ZENworks for Servers Solutions using Novell Cluster Services Demonstration of installation and configuration processes—most of the time will be spent here Question and answer period

This Session Does Not Cover… Cluster-enabling any other Novell or Microsoft technology Installation and configuration of Novell Cluster Services In-depth analysis of Novell Cluster Services

Novell Cluster Services Novell Cluster Services is software that permits you to combine a number of individual network servers into a cluster, thereby providing users with virtually uninterrupted access to their critical network resources such as data, applications, server licenses, and other services If one network server (cluster node) in the cluster happens to fail, another will automatically take over the resources and services it provided Novell Cluster Services promises higher levels of availability than other Intel-based clustering systems: you can provide true multi-node clustering with support for up to 32 server nodes in a cluster In addition, Novell Cluster Services does not require any proprietary hardware: you can install it on off-the-shelf Intel architecture systems

ZENworks for Desktops Overview of services Application distribution services Workstation inventory services Automatic workstation import/removal services ZEN imaging services Policies What can be cluster-enabled?

ZENworks for Servers Policy and distribution services Server policies Enforce configurations or actions by an event or schedule Tiered Electronic Distribution (TED) Efficiently distributes data between servers Monitoring and management services Monitors Novell NetWare®, Windows NT, and Windows 2000 servers Manages SNMP devices Creates reports and data-trending charts (Successor to Novell ManageWise®) What can be cluster-enabled?

ZENworks for Desktops Installation Prerequisites At least two NetWare 5.1 or NetWare 6 servers Novell Cluster Services installed on a minimum of two NetWare servers A cluster volume created and cluster-enabled (this is referred to as the virtual server) Minimum JVM 1.1.7b on each node in the cluster

ZENworks for Desktops Installation Prerequisites—CVSBIND Set up CVSBIND on each node in the NetWare cluster (required by ZENworks for Desktops inventory services) Copy CVSBIND to the SYS:\SYSTEM directory on each node in the cluster Modify SYS:\SYSTEM\LDNCS.NCF to include the following command cvsbind Modify SYS:\SYSTEM\ULDNCS.NCF to include the following command unload cvsbind

ZENworks for Desktops Installation Prerequisites—CVSBIND (cont.) Modify the virtual server load and unload scripts using Novell ConsoleOne® Add the following command to the virtual server load script cvsbind add SERVER_NAME IP_address Add the following command to the virtual server unload script cvsbind del SERVER_NAME IP_address Note: The CVSBIND command is not case sensitive, but the server name should be entered in upper-case letters

General Configuration of ZENworks for Desktops The ZENworks for Desktops installation process copies files to the SYS:\PUBLIC directory…these files need to reside on the cluster volume To avoid any problems, and hours of troubleshooting, copy the entire SYS:\PUBLIC directory to the cluster volume

Cluster-Enabling ZENworks for Desktops Application Distribution Services Application Object Templates (AOT) must be stored on the cluster volume If this is a fresh/new installation of ZENworks for Desktops, and it is on the cluster, you will have to move the “canned” applications to the cluster volume, and modify the “SOURCE_PATH” macro for each of the application objects in Novell eDirectory™ to point to the cluster volume, rather than the volume where ZENworks for Desktops was installed

Cluster-Enabling ZENworks for Desktops Automatic Workstation Import/Removal Services Not much to do in this area…the only task to do here is to install the automatic workstation and/or removal services directly to the virtual server You are done

Cluster-Enabling ZENworks for Desktops Imaging Services Simply install the IMGSERV back-end services on the virtual server Remember…the ZEN image server needs to be loaded from the virtual server load script Issue: If an image is being pushed to a workstation, and the server hosting the image server fails over to another node, the image process will need to be restarted on the workstation

Cluster-Enabling ZENworks for Desktops Inventory Services Configure the database object using ConsoleOne and specify the virtual server or the IP address of the virtual server Edit the Sybase startup file located in SYS:\SYSTEM (called MGMTDBS.NCF) to point to the IP address of the virtual server Copy this file to all nodes in the cluster Comment out the ZENworks for Desktops lines, added to AUTOEXEC.NCF on each node in the cluster These lines will be added to the cluster load script Modify the cluster load script to load ZENworks for Desktops components and the Sybase database Modify the cluster unload script to unload the ZENworks for Desktops components and the Sybase database

Cluster-Enabling ZENworks for Desktops Inventory Services (cont.) On each of the cluster nodes, configure the inventory server property file if the role of the inventory server is either of the following Root server Root server with workstations attached Intermediate server Intermediate server with workstations attached Intermediate server with database Intermediate server with database and workstations attached

Cluster-Enabling ZENworks for Desktops Inventory Services (cont.) The server properties file is located in the following directory \PUBLIC\ZENWORKS\WMINV\PROPERTIES The stand-alone inventory server does not require any modifications to its properties file due to the fact that it does not role up inventory data Assign the [ROOT] as a trustee of the \PUBLIC\ZENWORKS directory, with read and file scan rights

Cluster-Enabling ZENworks for Desktops Inventory Services (cont.) This part is important: remember that because the inventory service is cluster-enable, you need to use ONLY ONE inventory service object in eDirectory/NDS when making modifications, and changes, as this ONE object will be used and referenced by all nodes in the cluster Modify the CONFIG.PROPERTIES file on each node in the cluster to point to the ONE inventory service object that you have designated as the object referenced by the cluster This file can be found in the following location on each node in the cluster \PUBLIC\ZENWORKS\WMINV\PROPERTIES\ Configure the inventory policy settings for the virtual server

ZENworks for Servers Installation Prerequisites At least two NetWare 5.1 or NetWare 6 servers Novell Cluster Services installed on a minimum of two NetWare servers A cluster volume created and cluster-enabled (this is referred to as the virtual server)

Cluster-Enabling ZENworks for Servers Distributor Service Ensure that the eDirectory schema has been extended for ZENworks for Servers If it has not, do this first Run the Installation Wizard, and select the following Location of the ZENworks for Servers license objects Each node in the cluster, as well as the virtual server (this process is outlined in detail, including screen shots, in the January 2002 version of AppNotes)

Cluster-Enabling ZENworks for Servers Distributor Service (cont.) Patch the nodes in the cluster with ZENworks for Servers 2, SP1a Please note that you need to run the patch from the server console, for each node in the cluster, unless you are also running the ZENworks for Servers subscriber service on each of the nodes as well, and you can automate the distribution and installation of the service pack from another distributor in the tree Remember to use the right patch This is based on what version of the JVM you are using JVM 1.1.7b use POLYDISTJVM1.NCF JVM 1.2.2 or 1.3 use POLYDISTJVM2.NCF If the server is also hosting a Sybase database for logging (zfslog.db), make sure it is up and running when you run the patch installation or else the database will not get upgraded

Cluster-Enabling ZENworks for Servers Distributor Service (cont.) Clean up the eDirectory directory objects You will only require ONE Distributor object for the cluster; therefore you will delete the distributor objects that reference each of the physical nodes, leaving only the distributor object that references the virtual server Modify DIST.NCF located in the SYS:\TED2\ directory, to point to the DN of the distributor object for the virtual server You will need to do this on each of the servers in cluster (the server reference can be found at the bottom of the file) Modify MGMTDBS.NCF located in the SYS:\SYSTEM directory, changing the IP address listed to the IP address of the virtual server where the database is being hosted

Cluster-Enabling ZENworks for Servers Distributor Service (cont.) Modify the distributor object to include the IP address of the virtual server—this is done using ConsoleOne, and selecting the “Other” tab, as part of the properties of the distributor object Configure the load and unload scripts for the virtual server, ensuring that all the necessary ZENworks for Servers load and unload commands are included in the scripts Create all your necessary ZENworks policy packages… which include the following Container package (enabling the search policy) Server package Service location package (enabling the database location policy and license location policy, specifically)

Cluster-Enabling ZENworks for Servers Distributor Service (cont.) Now that the servers are patched, all modifications have been made, and policy packages created, you can start the distributor service for the first time This will create the KEYPAIR.OBJ file located in the following directory of the node which you just started the distributor from SYS:\TED2\SECURITY\PRIVATE Copy the KEYPAIR.OBJ file from this directory on the server currently hosting the distributor service to each of the physical nodes in the cluster This is required for ZENworks for Servers certificates and distributions to work properly Modify the routing hierarchy for the distributor, in the properties of the distributor object

Cluster-Enabling ZENworks for Servers (Parent) Subscriber Services Installing the subscriber service on Novell Cluster Services is done in the exact same fashion as outlined in the steps to install the distributor service and database to a Novell cluster, with a few key differences The ZENworks for Servers subscriber service can be installed on the virtual server as well as each physical node participating in the cluster This is accomplished by deploying ZENworks for Servers to each of the nodes (physical and virtual) as outlined in the steps above, but you will not need to delete any objects from eDirectory The subscriber service is a passive service and does not actively become involved in TED communications on its own All communications and transmissions are instigated by the distributor service The subscriber service simply sits and waits for instructions from the distributor service It does not read eDirectory for any of its own configuration parameters; the distributor reads the parameters and pushes them to the subscriber service

Cluster-Enabling ZENworks for Servers (Parent) Subscriber Services In this case, the subscriber service can actively run on the virtual server, so you can deploy software and data to the virtual volumes It can also run on each of the physical servers, so you can deploy to the servers’ physical volumes (such as SYS) This exposes the physical servers to participate in the automatic deployment of NetWare support packs You will not be deploying the ZENworks for Servers database to any of the servers participating in the TED infrastructure as a parent subscriber or subscriber You will not need to perform the steps to modify any .NCF files on the subscriber The subscriber does not authenticate to eDirectory; it simply waits for instructions from the distributor service

See It in Action