York NT2000 User Manual

WINDOWS

INDOWS NT/2000

INDOWSINDOWS

IIIINSTALLATION

NSTALLATION G

NSTALLATIONNSTALLATION

NT/2000

NT/2000 NT/2000

GUIDE

G G

UIDE

UIDEUIDE

RRRR EVISION

EVISION/U

EVISIONEVISION

OOOOPERATING

PERATING S

PERATINGPERATING

SSSS OFTWARE

OFTWARE V

OFTWAREOFTWARE

/UPDATE

/U/U

PDATE I

PDATEPDATE

SYSTEM

YSTEM V

S S

YSTEMYSTEM

VERSION

ERSION:

V V

ERSIONERSION

INFORMATION

NFORMATION:

I I

NFORMATIONNFORMATION

VERSION

ERSION:

V V

ERSIONERSION

:::

01/02/2002

:::

WINDOWS NT 4.0 OR LATER

INDOWS 2000

VERSION 1.5-0

TECSYS DEVELOPMENT, INC. 1600 10

TH STREET, SUITE B

LANO, TEXAS 75074

Printed in the United States of America.

TECSys Development Inc. (TDi) makes no representations or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Furthermore, TDi reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of TDi to notify any person of such revision or changes.

No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means electronic, mechanical, magnetic, optical, chemical, or otherwise without the prior written permission of:

TECSys Development, Inc. Phone: 972-881-1553 1600 10th Street FAX: 972-424-9181 Suite B Email: support@tditx.com Plano, TX 75074 USA web: http://www.tditx.com/

Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 52.227-7013.

All product or company names mentioned in this document are trademarks or registered trademarks of their respective owners.

ConsoleWorks NT Telnet JAVA Applet makes use of the public domain Telnet Applet. TECSys Development did not write the Telnet Applet nor does it claim any particular license to the applet excepting those rights given by the GNU Library General Public License. The Telnet Applet credits are listed below:

Unicenter Console Management for OpenVMS (formerly known as PolyCenter Console Manager) is a registered trademark of Computer Associates Inc. Alpha, AXP, OpenVMS, and VAX are registered trademarks of Compaq Computer Corporation. NT is a registered trademark of Microsoft Corporation. Netscape, Internet Explorer, Macintosh, Tru64 Unix, Linux, Solaris, SPARC HP-UX, and PA-RISC are registered trademarks of their respective organizations.

Table of Contents

1.This Guide ...............................................................................................................................................1

1-1.Pu rp ose ................................................................................................................................................1

1-2.Intended Audience ..........................................................................................................................1

1-3. Organization and Chapter Layouts of this Guide ......................................................................1

1-4.. Introduction, Overview and Concepts .......................................................................................1

1-5. Pre-Installation ...................................................................................................................................1

1-6. Installation ..........................................................................................................................................1

1-7. Appendices .......................................................................................................................................1

1-8. Reader Feedback ............................................................................................................................1

1-9. Customer Support ............................................................................................................................2

1-10. Conventions used in the Guide ...................................................................................................2

2. Introduction and Overview ...............................................................................................................3

2-1. Introduction to ConsoleWorks ........................................................................................................3

2-2. Overview of the ConsoleWorks Installation Process ..................................................................3

2-3. Installation Terms ...............................................................................................................................4

2-4. Installation Concepts .......................................................................................................................6

3. Pre-Installation ......................................................................................................................................9

3-1. Host System Criticality and ConsoleWorks Exclusivity ................................................................9

3-2. Host Operating Systems Supported ..............................................................................................9

3-3. ConsoleWorks is available on CD ROM or from the Internet ...................................................9

3-4. Product Authorization Key (PAK) is Required ..............................................................................9

3-5. Files at the TDi Website ....................................................................................................................9

3-6. Release Notes ...................................................................................................................................9

3-7. Host System Requirements ............................................................................................................. 10

3-8. Administrator Account Privileges are Required ........................................................................ 10

3-9. Ongoing Disk Space Requirements ............................................................................................. 10

3-10. Web Browser Requirements ........................................................................................................ 10

4. Installation ............................................................................................................................................ 11

4-1. Make Backup of System Disk(s) .................................................................................................... 11

4-2. Installation Process .......................................................................................................................... 11

4-3. State of Installation after Completion ......................................................................................... 16

4-4. Installing ConsoleWorks License(s) ............................................................................................... 16

4-5. Starting the ConsoleWorks Server ................................................................................................. 17

4-6. ConsoleWorks and the Services Control Panel ......................................................................... 17

4-7. Add ConsoleWorks to the System Startup .................................................................................. 17

4-8. ConsoleWorks Manual Starts and Manual Shutdowns ............................................................ 17

4-9. Adding Functionality ....................................................................................................................... 18

4-10. Importing POLYCENTER Console Manager (PCM) Port Files ................................................. 18

4-11. ConsoleWorks Databases ............................................................................................................ 18

4-12. Editing ConsoleWorks Default Templates ................................................................................. 18

5. Software Update ................................................................................................................................. 21

5-1. Stop the ConsoleWorks Server and License Manager ............................................................. 21

5-2. Remove the ConsoleWorks Client and Server Programs ......................................................... 21

5-3. Re-install the ConsoleWorks Server and Client Programs ........................................................ 21

5-4. Install ConsoleWorks License(s) ..................................................................................................... 21

5-5. Start the ConsoleWorks Server ...................................................................................................... 21

5-6. Add ConsoleWorks to the system startup ................................................................................... 22

Appendix 1—Profile Rules and Examples ...........................................................................................23

Appendix 2—HTML Directory Edits ......................................................................................................25

Appendix 2—Directory Listing ............................................................................................................... 27

Appendix 3—ConsolleWorks Version 1.4-0 to 1.5-0 Directory Cross-Reference .......................... 35

iii

1. This Guide

1-1. Purpose

This guide describes how to install and configure ConsoleWorks on a host using Windows NT version 4.0 with Service Pack 3 or later or Windows 2000 operating system.

1-2. Intended Audience

This guide is written for system administrators and managers installing and configuring the ConsoleWorks application on a Windows NT or Windows 2000 host.

1-3. Organization and Chapter Layouts of This Guide

This section describes the purpose of the guide, intended audience, organization and features of this guide, reader feedback, customer support, and conventions used in this guide.

1-4. Introduction, Overview and Concepts

This section introduces the ConsoleWorks application. It also describes an overview of the installation process, terms and concepts used during the installation, some of the concepts used in configuration and has a special note for Polycenter Console Manager (PCM) users.

1-5. Pre-Installation

This section helps the installer prepare to install ConsoleWorks by listing the hardware and software needed to install and run ConsoleWorks and by suggesting some installation design hints and techniques.

1-6. Installation

This section contains the first stage of the installation procedure for installing ConsoleWorks onto a host machine. Once the default installation file set is installed, optional functions, such as:

• importing supplied event definitions, and/or

• adding ConsoleWorks to the system startup,

are added based on the desired ConsoleWorks functionality.

The second stage of the installation procedure for installing ConsoleWorks onto a host machine is called Configuration and is covered in the document: ConsoleWorks Administrator and User Guide.

1-7. Appendices

The appendices include a additional information that may be useful during installation.

1-8. Reader Feedback

TDi welcomes comments to this guide and other products. Readers are encouraged to send feedback to TDi at:

TECSys Development Inc (TDi) Phone: 972.881.1553 1600 10th Street FAX: 972.424.9181 Suite B Email: support@tditx.com Plano, TX 75074 USA WEB: http://www.tditx.com/ attn: ConsoleWorks Customer Feedback

1-9. Customer Support

TDi customer support is offered through several venues: internet website, email, phone and fax. When requesting customer support, an active Service Agreement and the following information will be needed from the customer:

• Name and Contact Information

• Company Name

• Customer ID

• Model of host running ConsoleWorks

• Host operating system version and patch level

• ConsoleWorks version

• Description of problem

Customer support offices are staffed Monday through Friday, 8:00am to 5:00pm Central Time. TDi customer support can be reached as follows:

internet website: http://www.tditx.com/ email: support@tditx.com phone: 972.881.1553 fax: 972.424.9181

If requesting fax support, please be sure to include a return fax number in the Contact Information.

1-10. Conventions used in this Guide

Enter Indicates a key on a PC or terminal keyboard, this example indicates pressing the Enter key.

Ctrl-X A hyphen between keyboard keys indicates a combination of keys on a PC or terminal key-

board to be pressed simultaneously, this example indicates pressing the Ctrl key and the X key simultaneously.

cw_add_invo Italics indicates a filename, command, variable name or other screen text.

cw_add_invo Boldface type in examples indicates input the user types.

[ ] Indicates optional information to be included with the command at the installers discretion.

[Y] or [N] Items contained within square brackets [] are default settings in the ConsoleWorks applica-

tion. For example, when queried with a Yes or No answer the default setting will show a [Y] or [N].

 Continuation. Usually used when the script responses being shown in the text or body of the

guide continue beyond what is shown on the page.

2. Introduction and Overview

2-1. Introduction to ConsoleWorks

ConsoleWorks is an application built to monitor console port text or SYSLOG messages and to directly manage any device supporting console port connections. It runs on OpenVMS, Unix and NT/2000 platforms. In addition, ConsoleWorks can manage devices indirectly by using script-initiated management applications running on the ConsoleWorks host.

ConsoleWorks accomplishes this management with three major components:

• a standard web browser (or a command line user interface)

• a specialized web server, and

• a host connected via cable to the device’s serial console port (direct management) or by network

(indirect management).

Other than the original installation and some preliminary configurations, most ConsoleWorks operations are managed and configured using a standard web browser.

ConsoleWorks' flexibility provides the capability:

• to manage any device allowing management from a console port from any workstation on the net- work connected to the ConsoleWorks host,

• to manage hosts on a network remotely, either via the internet or a dialup network,

• for a ConsoleWorks server to use host-based utilities to contact a person based on event driven criteria,

and

• to organize managed devices into logical groupings.

♦ note: The V1.5-0 ConsoleWorks server for the Windows NT/2000 platform supports one server invocation. Fu-

ture releases will provide the capability for multiple invocations on one server. Each ConsoleWorks invocation is a separate entity. Two concurrently running invocations do not share resources (profiles, users or console ports).

ConsoleWorks Windows NT/2000 server requires a system running Windows NT 4.0 with at least Service Pack 3 or Windows 2000. ConsoleWorks also requires a TCP/IP protocol stack.

The V1.5-0 ConsoleWorks Product Kit contains the files required for installing the following ConsoleWorks components:

1. ConsoleWorks Web Server, and

2. ConsoleWorks public domain scan and event definitions.

This guide describes how to install ConsoleWorks on a Windows NT/2000 host.

♦ note: ConsoleWorks requires a valid license to operate.

2-2. Overview of the ConsoleWorks Installation Process

It is strongly recommended that installers design and plan their implementation of a ConsoleWorks installation. ConsoleWorks components require configuration that proceeds much more smoothly when an installation plan is followed. Suggestions and recommendations can be found in the Installation Concepts section of this chapter.

ConsoleWorks installs in two stages.

1) The first stage of the installation includes:

• downloading ConsoleWorks from the internet or mounting the CD,

• installing ConsoleWorks from the distribution kit,

and optionally,

• adding ConsoleWorks to the system startup,

• editing templates to customize event and user templates, and

• importing existing Users, Consoles, Scans, Events and/or Databases.

♦ note: Technically, ConsoleWorks has created an invocation after this stage of installation is completed.

However, the invocation has no configured Ports, Profiles, Users, or Events. These components must be configured to make ConsoleWorks useful.

2) The second stage of installation uses a web browser to add/delete/configure items such as:

• accounts,

• consoles,

• profiles,

• scans,

• events, and

• actions.

2-3. Installation Terms

The following terms are provided as reference. It is recommended these terms be studied in conjunction with the next section in this document: Installation Concepts.

Agent

If the device being managed has Windows NT/2000 as its operating system, that Windows NT or Windows 2000 system requires an agent to gather and transmit its events since Windows does not have a serial console.

Alpha

A host running an Alpha processor as its primary CPU.

Refers to a Compact Disc.

Console

Console refers to a representation created and configured within ConsoleWorks, corresponding to a man- aged device. The console may be physically attached to a device console port or it may be mapped to Syslog events. Privileges are read, write, acknowledge and control.

ConsoleWorks Root Directory

The base directory on the ConsoleWorks server system in which all ConsoleWorks directories reside. On Windows NT/2000, this directory is C:\Program Files\TECSys Development, Inc\ConsoleWorks Server\.

Device Console Port

A Device Console Port is a serial port on a device that is used to manage that device.

Default Files

Default Files are a basic set of files created by ConsoleWorks installation kits when ConsoleWorks is first in- stalled. Those files are subsequently used to make invocation directory trees. Each invocation has its own directory tree based from the ConsoleWorks root directory.

Display

Display refers to a particular Window or Splash Screen displayed during a step in the installation. Screen, Window and Display are used interchangeably in this guide.

Distribution Kit or Package

A Distribution Kit or Package is a file or files that enable a person to install the ConsoleWorks application. Each operating system (Windows NT/200 OpenVMS, Tru64, Linux, HP UX and Solaris) uses a unique distribution kit.

Events

Events are conditions occurring on devices which cause the devices to post status messages to their console ports or onto the network with Syslog. ConsoleWorks scans console text and Syslog messages for information and to use as triggers to initiate actions.

Installer

An Installer is the person installing the ConsoleWorks application and configuring the invocations and pro- files. The installer is required to have Administrator access privileges.

Intel

A host running an Intel processor as its primary CPU.

Invocation

An Invocation is a copy of the ConsoleWorks application running on the host. Each invocation is an application/web server hybrid that allows remote management of devices. Each invocation uses a private set of consoles, profiles, and user accounts.

♦ note: Each invocation is required to have a unique name since two invocations using the same invoca-

tion name cannot operate concurrently on the same host system.

Linux

A host running Redhat Linux 6.0 (or later) as its operating system.

PCM

POLYCENTER Console Manager in this document refers to Computer Associates’ Unicenter Console Management for OpenVMS which includes technologies formerly available as: CommandIT Enterprise Edition,

Unicenter TNG for OpenVMS Console Manager, POLYCENTER Console Manager

Product Authorization Key (PAK)

ConsoleWorks licenses are composed of ConsoleWorks Product Authorization Keys (PAK). The Base PAK includes five connections. Extra connections can also be added. Additional features such as Telnet and Syslog capabilities can be added with additional PAKs.

Profile

Profile refers to a set of privileges to consoles and/or ConsoleWorks server administration.

Some aspects of a profile are:

• a profile may contain some or all of the privileges available on a console port,

• multiple users may have the same profile,

• multiple profiles can provide privileges to the same console port(s), and

• a user may have access to one or more profiles, but may use only one profile at a time.

In addition, profiles are used to access ConsoleWorks invocation management as well. ConsoleWorks management has the ability to read, write, control and delete console ports, profiles and user accounts.

Scans

A scan is a collection of events, other scans or a combination of the two. As a result, a scan could contain only events, only other scans or both scans and events.

Screen

Screen refers to a particular Window or Splash Screen displayed during a step in the installation. Screen, Window and Display are used interchangeably in this guide.

Solaris

A host running SUN Solaris 7.0 (or later) as its operating system.

SPARC

A host running a SUN SPARC processor as its primary CPU.

TCP/IP or Transmission Control Protocol/ Internet Protocol port

The Transmission Control Protocol/ Internet Protocol port(s) each host controls. Each invocation is assigned a specific TCP/IP port to use.

User Account

User account refers to the access a person receives when logging into ConsoleWorks. A user's access to a console port and to ConsoleWorks management is defined by what profiles the user is given permission to use.

♦ note: Users may have access to more than one profiles, but may only use one profile at a time.

VMS

A host running Compaq OpenVMS V7.2 (or later) as its operating system

Web Browser

Commonly used Web Browsers such as Netscape Navigator 4.7 or Internet Explorer 5.0 (or later) web browsers are required to complete the configuration of the installed elements.

Window

Window refers to a particular Window or Splash Screen displayed during a step in the installation. Screen, Window and Display are used interchangeably in this guide.

2-4. Installation Concepts

The following describe the relationships between some of the functional components used by ConsoleWorks. Understanding the following concepts will:

• assist in designing an installation,

• prepare the installer for the installation and configuration processes, and

• reduce the need for large scale configuration changes and installation redesigns after installation.

Installation Phases

Pre-Installation

The period prior to Installation where the installer collects required software and verifies the host system meets the requirements for ConsoleWorks installation and operation.

Installation

This phase includes the steps involving installing the ConsoleWorks application on the target host, setting up a basic invocation, add-

ConsoleWorks on

drive

invoked copy of ConsoleWorks in host's memory

Figure 1 - Invocation

Invoc ation setup files

on drive

ing ConsoleWorks to the system startup and selectively adding prepackaged event definitions.

ConsoleWorks invocations are highly configurable. During the installation phase the installer is presented opportunities to edit files that will be used globally by each invocation, such as event template files. Most of these changes can also be made later.

Configuration

Configuration is the period after Installation involving creating and configuring consoles, profiles, and user accounts. Invocations are in a default mode after installation and are not fully functional until configured. Configuration operations are performed using a web browser and are described in the ConsoleWorks Administration and User Guide.

Invocation Components (Figure 2)

Invocation

users

user 01

user 02

rule1: only one set of privileges per console port to a profile rule 2: only one active profile at a time for each user rule 3: more than one user m ay have access to and use a profile rule 4: p rivileges to a console po rt may vary between profiles

user 03

profiles

console port 01 RW AC

console por t 02 RW

console por t 03 R

console port 01 RW AC

console port 03 RW

console port 04 R

console port 01 RW

console port 02 RW AC

ConsoleWorks management

Concept of a ConsoleWorks invocation

ConsoleWorks management

read

delete

write

profile

console port 01

read write

control

acknowledge control

access privileges to a console port or to

Consol eWor ks mana gemen t

A copy of the ConsoleWorks application running on the host. Users, profiles, and consoles are exclusive to each

Figure 2 - Invocation Components

invocation.

Device Console Port

The physical connection between the host and the external device.

Console

The representation within ConsoleWorks of the a device console including all the parameters necessary to communicate with that console. A console has four privileges: Read, Write, Acknowledge and Control (RWAC). Access to a console is controlled via profiles. Each user is given access to a specific profile or profiles.

Profile

A configured set of privileges providing access to consoles and/or to ConsoleWorks administration within an invocation. Users are given profile access by user(s) with access to ConsoleWorks management profile (s). Console privileges are Read, Write, Acknowledge and Control (RAWC). ConsoleWorks administration privileges are Read, Write, Delete and Control (RWDC).

Some rules for configuring and using profiles per invocation are:

rule 1: each profile has only one set of privileges per console, rule 2: each profile may have access to one or more console, rule 3: each user may have only one active profile at a time, rule 4: more than one user may have access to and use a profile, and rule 5: privileges to a console may vary between profiles.

A tabular example of these rules is shown below in Table 1. In Table 1, the profiles User 1, User 2, Manager 1 and Manager 2 were created solely for the purpose of the example and are not standard profiles in ConsoleWorks.

User

A person logging into a ConsoleWorks invocation's user account. Generally speaking, the difference between an administrative account and a user account is the access to ConsoleWorks management profiles. All users are permitted to have access to more than one profile, but can only use one profile at a time per invocation.

ConsoleWorks Manager

A person logging into a ConsoleWorks invocation with the ConsoleWorks Administrative privileges which are the ability to Read, Write, Delete and Control (RWDC) user accounts, profiles and console ports. ConsoleWorks Managers are permitted to access more than one profile, but

profiles device a device b device c consolew orks app

user 1 R R - -

user 2 RW - R R

manager 1 RW RWAC RW RWDC

manager 2 RWAC - - RWDC

Table 1. Profiles to devi ce mapping example

can only use one profile at a time per invocation.

device

consol e

port(s) (physical) or Syslog

Event

Installation Tips and Recommendations

ConsoleWorks supports customizing an invocation's templates. Each invocation has its own directory and subdirectories. The original templates created during installation are located in the Config subdirectory under the installation directory specified during the installation process. For Windows NT/2000, the default is C:\Program Files\TECSys Development, Inc\ConsoleWorks Server\Config.

An installer intending to use the same modifications to the templates across several invocations could save significant effort by editing the templates made during the original installation, make the modifications to the ConsoleWorks root directory templates. This may be especially useful when the HTML templates are modified with company specific data, company policy comments or HTML jumps to company specific files (such as networked documentation).

Each invocation opens all of its device consoles when it is invoked, therefore the installer should make sure invocations expected to run concurrently do not attempt to access the same devices.

Special Note for Polycenter Console Manager (PCM) owners

ConsoleWorks comes with an array of predefined scans/events, many exported from PCM. These events can be imported during the installation process or later. The procedures for importing the events for are in the chapter on Installation in the Adding Functionality section.

3. Pre-Installation

This section contains information on the fundamentals required for installation.

Note: 1) When installing the ConsoleWorks Server on Windows an error will be displayed if you try to install V1.5 when a previous version is installed. You must uninstall the previous version before attempting to install V1.5.

2) the ConsoleWorks directory structure for Version 1.5-0 is significantly different from Version 1.4-0. The base directory for Version 1.4-0 was C:\Cwks where there base directory for Version 1.5-0 is C:\Program Files \TECSys Development, Inc\ConsoleWorks Server.

3-1. Host System Criticality and ConsoleWorks Exclusivity

ConsoleWorks' primary function is to monitor the health and status of chosen devices, at all times. As a monitoring application, ConsoleWorks requires unobstructed access to host system resources at all times. It is the strongest recommendation that ConsoleWorks be hosted on a dedicated, independent machine. Interfer- ence from other applications, for example email or printer server support, may interrupt support at critical times, delaying and possibly precluding recovery efforts.

3-2. Host Operating Systems Supported

ConsoleWorks is written for hosting on OpenVMS, Unix and Windows platforms. This guide is the manual for the Windows platform hosts running the following (or later) versions: Windows NT 4.0 with Service Pack 3 or Windows 2000 (right click on the My Computer icon and choose Properties to verify current version of the operating system).

♦ note: ConsoleWorks can run under its own account or under the Administrator account.

3-3. ConsoleWorks is available on CD ROM or from the Internet

ConsoleWorks is available on CD ROM or the latest version can be downloaded from the TDi website at http:// www.tditx.com/. Contact TDi to obtain ConsoleWorks in another format.

3-4. Product Authorization Key (PAK) is required

A Product Authorization Key (PAK) is not required for installation, but is required to activate a ConsoleWorks in- vocation. TDi will supply the appropriate permanent license with receipt of a purchase order. A temporary demo license may be downloaded from the same place the ConsoleWorks kit was downloaded.

3-5. Files at the TDi Website

Table 2 has a list files that will be referenced during installation. These ConsoleWorks installation files are available at the TDi Website (http://www.tditx.com/).

Windows NT Intel (4.0+) or Windows 2000

3-6. Release Notes

Table 2. List of available ConsoleWorks installation files at the TDi Website (http://www.tditx.com)

ConsoleWorks release notes contain information updated since the written manuals were published. These release notes are stored as installation CD, and once ConsoleWorks is installed, via the web browser. The locations of the RELNOTES- 1_5.*** files are shown in Table 3.

3-7. Host System Requirements

On CD before installation ConsoleWorks version and kit type Filename on website*

Location on CD ROM from root directory:

C:\Program Files\TECSys Development,

Inc\ConsoleWorks Server\Doc

Hard Disk require-

host system ConsoleWorks version and kit type Filename on website*

ConsoleWorks (v1.5-0) kit ConsoleWorksServer.

Location on host after installing kit:

C:\Program Files\TECSys Development,

Inc\ConsoleWorks Server\Doc

Table 3. Location of the RELNOTES-1_5*** files

From the ConsoleWorks home page:

HELP(left panel): Online Doc (left panel lower): Click either Text or HTML (description: ConsoleWorks V1.5-0 release notes)

exe

+ 29 hidden pages