Patrol Infrastructure Planning Guide 19464

PATROL Infrastructure Planning Guide
Version 7.1
September 12, 2002
Copyright 2002 BMC Software, Inc., as an unpublished work. All rights reserved. BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered trademarks or trademarks of BMC Software, Inc. All other registered trademarks or trademarks belong to their respective companies. THE USE AND CONTENTS OF THIS DOCUMENTATION ARE GOVERNED BY THE SOFTWARE LICENSE AGREEMENT ENCLOSED AT THE BACK OF THIS DOCUMENTATION.
Restricted Rights Legend

U.S. GOVERNMENT RESTRICTED RIGHTS. UNPUBLISHEDRIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure by the U.S. Government is subject to restrictions set forth in FAR Section 52.227-14 Alt. III (g)(3), FAR Section 52.227-19, DFARS 252.227-7014 (b), or DFARS 227.7202, as amended from time to time. Contractor/Manufacturer is BMC Software, Inc., 2101 CityWest Blvd., Houston, TX 77042-2827, USA. Any contract notices should be sent to this address.
Contacting BMC Software

You can access the BMC Software Web site at http://www.bmc.com. From this Web site, you can obtain information about the company, its products, corporate offices, special events, and career opportunities.
United States and Canada

Address BMC Software, Inc. 2101 CityWest Blvd. Houston TX 77042-2827 713 918 8800 or 800 841 2031 713 918 8000
Outside United States and Canada

Telephone Fax (01) 713 918 8800 (01) 713 918 8000
Telephone Fax
Customer Support
You can obtain technical support by using the Support page on the BMC Software Web site or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, please see Before Contacting BMC Software.
Support Web Site

You can obtain technical support from BMC Software 24 hours a day, 7 days a week at http://www.bmc.com/support.html. From this Web site, you can read overviews about support services and programs that BMC Software offers find the most current information about BMC Software products search a database for problems similar to yours and possible solutions order or download product documentation report a problem or ask a question subscribe to receive e-mail notices when new product versions are released find worldwide BMC Software support center locations and contact information, including e-mail addresses, fax numbers, and telephone numbers
Support by Telephone or E-mail

In the United States and Canada, if you need technical support and do not have access to the Web, call 800 537 1813. Outside the United States and Canada, please contact your local support center for assistance. To find telephone and e-mail contact information for the BMC Software support center that services your location, refer to the Contact Customer Support section of the Support page on the BMC Software Web site at www.bmc.com/support.html.
Before Contacting BMC Software

Before you contact BMC Software, have the following information available so that Customer Support can begin working on your problem immediately: product information product name product version (release number) license number and password (trial or permanent)
operating system and environment information machine type operating system type, version, and service pack or other maintenance level such as PUT or PTF system hardware configuration serial numbers related software (database, application, and communication) including type, version, and service pack or maintenance level
BMC Software, Inc., Confidential and Proprietary Information
iii
sequence of events leading to the problem commands and options that you used messages received (and the time and date that you received them) product error messages messages from the operating system, such as file system full messages from related software
iv
PATROL Implementation Manual
Contents
Contents
About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Chapter 1 Overview
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 The PATROL Infrastructure Planner . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 The PATROL Infrastructure KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Chapter 2 PATROL Fundamentals
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 What PATROL Is . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 What PATROL Does . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 What is New in PATROL 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 PATROL Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 Console Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 Common Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 Managed Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 PATROL Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 PATROL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10 PATROL KMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11 PATROL Consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15 PATROL Console Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21 RTservers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23 PATROL Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24 Monitoring with PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29 Managing with PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30 Where to Go From Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
Contents
Chapter 3
Examining Your Enterprise
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2 Mapping Your Enterprise Locations . . . . . . . . . . . . . . . . . . . . . . . . .3-3 Defining Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3 Location Mapping Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5 Gathering Detailed Location Information . . . . . . . . . . . . . . . . . . . . .3-7 How many Managed Systems are Present? . . . . . . . . . . . . . . . . .3-8 Additional RTserver services desired? . . . . . . . . . . . . . . . . . . . .3-8 Are PATROL Consoles needed for this location? . . . . . . . . . . . .3-9 What Other Systems can Host Common Services Components? 3-10 Detailed Location Information Worksheet . . . . . . . . . . . . . . . . .3-10 Where to Go From Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-12
Chapter 4 Using the PATROL Infrastructure Planner
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2 Where is the PATROL Infrastructure Planner? . . . . . . . . . . . . . .4-2 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2 Starting the PATROL Infrastructure Planner . . . . . . . . . . . . . . . .4-3 Infrastructure Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-5 Other Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-7 The Infrastructure Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-8 Where to Go From Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-9
Chapter 5 PATROL Installation Overview
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-2 The Installation Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-2 Local Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-2 Remote Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3 Security Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3 Component and Product Requirements . . . . . . . . . . . . . . . . . . . . . . .5-4 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-4 Where to Go From Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-5
Chapter 6 The PATROL Infrastructure KM
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2 KM Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2 KM and Parameter Features . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-4 Alarms and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-4 Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-4 Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-5
vi
Installing the PATROL Infrastructure KM . . . . . . . . . . . . . . . . . 6-6 Configuring the PATROL Infrastructure KM . . . . . . . . . . . . . . 6-11 Application Class Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13 Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15 InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20 Using the KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-31
Appendix A Worksheets and Checklists
Enterprise Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location Mapping Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . Detailed Location Information Worksheet . . . . . . . . . . . . . . . . Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Console Server and RTserver Checklist . . . . . . . . . .
Glossary Index
A-2 A-3 A-4 A-5 A-6
Contents
vii
viii
Figures
Figures
Figure 2-1 Figure 4-1 Figure 4-2 Figure 6-1 Figure 6-2 Figure 6-3 Figure 6-4 Figure 6-5 Figure 6-6 Figure 6-7 PATROL Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Infrastructure Planner Welcome Page . . . . . . . . . . . . Console Server and RTserver Table. . . . . . . . . . . . . . . . . . . . . . KM and Parameter Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . Add/Modify RTserver Information Dialog Box . . . . . . . . . . . . Locate RTserver Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . Locate RTserver Results Dialog Box. . . . . . . . . . . . . . . . . . . . . RTmon Command Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . RTmon Task Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ping Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6 4-4 4-9 6-3 6-12 6-22 6-22 6-24 6-27 6-29
Figures
ix
Tables
Tables
Table 2-1 Table 2-2 Table 2-3 Table 6-1 Table 6-2 Table 6-3 Table 6-4 Table 6-5 Table 6-6 Table 6-7 Table 6-8 Table 6-9 Table 6-10 PATROL Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default PATROL Groups on the PATROL Console Server . . . . Usability versus Security for the Five Security Levels . . . . . . . Installed File List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Class Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameter Summary by Application Class . . . . . . . . . . . . . . . . Parameter Summary by Collector . . . . . . . . . . . . . . . . . . . . . . . Parameter Default Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Infrastructure KM Task List . . . . . . . . . . . . . . . . . . . . RTmon Command Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 2-26 2-28 6-10 6-13 6-14 6-15 6-17 6-19 6-20 6-21 6-24 6-31
Tables
xi
xii
About . . .
About This Book

This manual provides the information that you need to plan the implementation of the PATROL infrastructure in your environment using the PATROL Infrastructure Planner. This book provides basic PATROL knowledge, checklists for gathering information about your environment, planning guidelines, an installation overview, and information about the PATROL Infrastructure Knowledge Module (KM).
Note
This book assumes that you are proficient with the operating systems, networks, protocols, file systems, and all other required facilities necessary to install, deploy, and operate the PATROL Application Management products in your environment.
xiii
How This Book Is Organized

This book is organized as follows.
Chapter/Appendix
Chapter 1, Overview
Description
provides an overview of the how to use this book and the PATROL Infrastructure Planner provides basic PATROL information and information about what is new in PATROL 7.x provides worksheets and describes what you need to know about your enterprise to plan your PATROL infrastructure implementation introduces the PATROL Infrastructure Planner and describes the rules used to plan a PATROL implementation provides an overview of the installation utility for installing PATROL components describes the PATROL Infrastructure KM, which provides visualization of the communication characteristics of the PATROL 7.x infrastructure provides component installation checklists contains PATROL terms and definitions lists index entries for this book
Chapter 2, PATROL Fundamentals
Chapter 3, Examining Your Enterprise
Chapter 4, Using the PATROL Infrastructure Planner Chapter 5, PATROL Installation Overview Chapter 6, The PATROL Infrastructure KM
Appendix A, Worksheets and Checklists Glossary Index
xiv
Documentation
BMC Software products offer several types of documentation: online and printed books online Help release notes
Online and Printed Books

The books that accompany BMC Software products are available in online and printed formats. Online books are formatted as Portable Document Format (PDF) files. Some online books are also formatted as HTML files.
To Access Online Books
To view any online book that BMC Software offers, visit the Customer Support page of the BMC Software Web site at http://www.bmc.com/support.html. You can also access PDF books from the documentation compact disc (CD) that accompanies your product. Use the free Acrobat Reader from Adobe Systems to view, print, or copy PDF files. In some cases, installing the Acrobat Reader and downloading the online books is an optional part of the product-installation process. For information about downloading the free reader from the Web, go to the Adobe Systems Web site at http://www.adobe.com.
To Request Additional Printed Books
BMC Software provides some printed books with your product order. To request additional books, go to http://www.bmc.com/support.html.
Online Help
You can access Help for a product through the products Help menu. The Help provides information about the products graphical user interface (GUI) and provides instructions for completing tasks.
xv
Release Notes
Printed release notes accompany each BMC Software product. Release notes provide up-to-date information such as the following: updates to the installation instructions last-minute product information
The latest versions of the release notes are also available on the Web at http://www.bmc.com/support.html.
Conventions
The following conventions are used in this book: This book includes special elements called notes, warnings, examples, and tips:
Note
Notes provide additional information about the current subject.
Warning
Warnings alert you to situations that can cause problems, such as loss of data, if you do not follow instructions carefully.
Example
An example clarifies a concept discussed in text.
Tip
Tips contain information that might improve product performance or that might make procedures easier to follow.
xvi
All syntax, operating system terms, and literal examples are presented in this typeface. In instructions, boldface type highlights information that you enter. File names, directories, Web addresses, e-mail addresses, and names of GUI elements also appear in boldface type. The symbol => connects items in a menu sequence. For example, Actions => Create Test instructs you to choose the Create Test command from the Actions menu. The symbol
denotes one-step instructions.
In syntax, path names, or system messages, italic text represents a variable, as shown in the following examples: The table tableName is not available.
system/instance/fileName
In syntax, the following additional conventions apply: A vertical bar ( | ) separating items indicates that you must choose one item. In the following example, you would choose a, b, or c: a | b | c An ellipsis ( . . . ) indicates that you can repeat the preceding item or items as many times as necessary. Square brackets ( [ ] ) around an item indicate that the item is optional.
xvii
xviii
Overview
This chapter provides an overview of this book and introduces the PATROL Infrastructure Planner and the PATROL Infrastructure KM. The following topics are discussed in this chapter: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 The PATROL Infrastructure Planner . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 The PATROL Infrastructure KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Overview
1-1
Introduction
The PATROL Infrastructure Planning Guide works with the PATROL Infrastructure Planner (included on the enclosed PATROL Infrastructure Planner CD) to help you plan the PATROL infrastructure for your enterprise quickly and easily. While you can use the PATROL Infrastructure Planner independently to help you plan your PATROL infrastructure, using the planner along with this manual gives you a better understanding of PATROL and prepares you to use the PATROL Infrastructure Planner. In addition to helping you implement the PATROL infrastructure in your enterprise, the PATROL Infrastructure Planner CD contains the PATROL Infrastructure KM to help you visualize and understand how PATROL communication works in your environment after you install the PATROL infrastructure. Implementing the PATROL infrastructure in your environment involves the following steps: 1. Use the PATROL Infrastructure Planning Guide to help you understand PATROL and prepare to use the PATROL Infrastructure Planner. 2. Use the PATROL Infrastructure Planner to plan your PATROL infrastructure. 3. Install the required PATROL components using the plan generated by the PATROL Infrastructure Planner. 4. After you install the infrastructure components, use the PATROL Infrastructure KM to examine and monitor the availability and performance of your PATROL infrastructure. The following sections introduce the PATROL Infrastructure Planner and the PATROL Infrastructure KM.
1-2
The PATROL Infrastructure Planner

The PATROL Infrastructure Planner is a tool that helps you plan your PATROL infrastructure by gathering information from you about your enterprise in an interactive interview. Chapter 3, Examining Your Enterprise, prepares you for the PATROL Infrastructure Planner interview by helping you organize and gather information about your enterprise. The PATROL Infrastructure Planner is included on the PATROL Infrastructure Planner CD. Chapter 4, Using the PATROL Infrastructure Planner, provides detailed information about using the PATROL Infrastructure Planner.
The PATROL Infrastructure KM

The PATROL Infrastructure KM helps you visualize and understand the communication characteristics of the PATROL 7.x infrastructure. The PATROL Infrastructure KM creates a representation of RTservers, PATROL Console Servers, PATROL 7.x Consoles, and PATROL Agents. The KM reflects the component-to-component relationships and the communication and messaging performance of your PATROL 7.x implementation.
Note
The PATROL Infrastructure KM is designed to use after you implement your PATROL infrastructure. You do not use the KM during the PATROL implementation. Chapter 6, The PATROL Infrastructure KM, provides detailed information about using the PATROL Infrastructure KM.
Overview
1-3
Related Publications
See the following BMC Software product documentation for more information about PATROL products and components: PATROL Central Microsoft Windows Edition Help PATROL Central Administration Microsoft Windows Edition Help PATROL Central Operator Microsoft Windows Edition Getting Started PATROL Central Operator Microsoft Windows Edition Help PATROL Central Operator Microsoft Windows Edition Release Notes PATROL Central Operator and PATROL Classic Consoles Diagram PATROL Command Line Interfaces Reference Manual PATROL Configuration Manager User Guide PATROL Console for Microsoft Windows and PATROL Console for Unix Release Notes PATROL Console for Microsoft Windows User Guide Understanding the Basics of PATROL, Volume 1 PATROL Console for Microsoft Windows User Guide Monitoring and Managing with PATROL, Volume 2 PATROL Console for Microsoft Windows User Guide Customizing PATROL, Volume 3 PATROL Console for Unix Help PATROL Console for Unix User Guide PATROL Console for Windows Help
1-4
PATROL Console Server and RTserver Getting Started PATROL Console Server and RTserver Release Notes PATROL Event Manager Console for Unix User Guide PATROL Explorer Getting Started PATROL Explorer Help PATROL Explorer Release Notes PATROL Installation Reference Manual PATROL Installation Workflows PATROL Migration Tools Release Notes PATROL Migration Tools User Guide PATROL Script Language Debugger Reference Manual PATROL Script Language Reference Manual Volume 1PSL Essentials PATROL Script Language Reference Manual Volume 2PSL Functions PATROL Script Language Reference Summary PATROL Security Release Notes PATROL Security User Guide
Overview
1-5
1-6
PATROL Fundamentals
This chapter provides a PATROL overview and includes information about classic PATROL components as well as the new PATROL components. The following topics are discussed in this chapter: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 What PATROL Is . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 What PATROL Does. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 What is New in PATROL 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 PATROL Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 Console Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 Common Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 Managed Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 PATROL Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 PATROL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10 PATROL KMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11 PATROL Consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15 PATROL Console Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20 RTservers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23 PATROL Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24 Monitoring with PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29 Managing with PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30 Where to Go From Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
PATROL Fundamentals
2-1
Introduction
You must understand PATROL before you can plan your PATROL infrastructure. This chapter provides an overview of PATROL its components. If you are new to PATROL, you should read the entire chapter to understand how PATROL works. If you are an experienced PATROL user, you may want to review the following topics that discuss the new PATROL components and the PATROL infrastructure: What is New in PATROL 7 on page 2-4 PATROL Architecture on page 2-5 Common Services on page 2-8 PATROL Central Operator Microsoft Windows Edition on page 2-16 PATROL Central Operator Web Edition on page 2-17 PATROL Console Server on page 2-20 RTservers on page 2-23 PATROL Security on page 2-24
What PATROL Is
PATROL is a suite of products that you can use to monitor computer systems, databases, and applications. In the context of PATROL, applications are any resource used by, or running on, a computer. PATROL provides an object-oriented graphical workspace where you can view the state of every vital resource in the distributed environment that you are managing. Additionally, PATROL can automate user-defined actions for specific computers or applications.
2-2
What PATROL Does

Using PATROL, you can monitor the state of the computers and applications that you use to conduct your business. PATROL represents these resources and indicates their current states with object icons. If PATROL detects a problem with a monitored computer or application, it attempts to correct the problem by performing stored recovery actions. If the problem escalates or requires your attention, PATROL displays the affected resources in a warning or an alarm state. The PATROL Consoles interact with the PATROL Agent on each remote machine through an event-driven dialog. Messages are sent to the PATROL Console when a specific event causes a state change on the monitored computer. Alternately, you can use PATROL Event Manager to access recent events. The PATROL Agent stores events in an event repository that is on the PATROL Agents host computer.
PATROL Fundamentals
2-3
What is New in PATROL 7

PATROL 7.x is the next generation of PATROL built on a new infrastructure. It provides the foundation for future PATROL products under the BMC Software Assuring Business Availability TM (ABA) product strategy. This strategy ensures that business applications are always Available; Performing to meet required business objectives; Recovered as rapidly as possible, should any failures occur.
The PATROL 7.x design is a distributed management solution that maintains flexibility, scalability, and extensibility. PATROL 7.x encompasses the following major architectural advances: a common communication infrastructure a common user-interface infrastructure a common repository the foundation for cross-solution cooperation
The new architecture (as shown in Figure 2-1 on page 2-6) includes the following layers: the new console systems PATROL Central Microsoft Windows Edition PATROL Central Web Edition the new common services components PATROL Console Server RTserver PATROL Central Web Edition Web server
2-4
PATROL Architecture
The PATROL architecture consists of components that interact with each other to monitor your enterprise including databases, networks, applications, and system resources. The components of the architecture can be grouped into the following areas: console systemssystems running a PATROL Console to monitor and manage the enterprise PATROL 3 Consoles PATROL Central common servicessystems running PATROL communication components PATROL Console Server RTservers PATROL Central Web Edition Web server managed systemssystems running PATROL Agents to monitor and manage applications and systems PATROL Agents PATROL KMs
Figure 2-1 on page 2-6 shows the PATROL architecture, and how the different components interact.
PATROL Fundamentals
2-5
Figure 2-1
PATROL Architecture
Console Systems
PATROL Central Microsoft Windows Edition PATROL Central Operator Microsoft Windows Edition Other console modules
PATROL Console for Microsoft Windows or PATROL Console for Unix Install classic console versions of PATROL Solutions (KMs) for systems being managed.
Web browser
Common Services
PATROL Central Web EditionWeb server PATROL Central Operator Web Edition Other console modules RTserver Cloud
PATROL Console Server
Managed Systems
PATROL Agent (version 3.5) Install PATROL solutions (KMs) for resources on each system.
PATROL products and solutions may require additional files installed throughout the infrastructure.
2-6
Console Systems
A console system hosts user desktop applications such as consoles, user interfaces, viewers, and browsers. You can view managed system data with the following PATROL consoles: PATROL Console for Microsoft Windows and PATROL Console Unix To develop PATROL KMs on Unix or Windows (PATROL 3), use PATROL Console for Unix or PATROL Console for Microsoft Windows. PATROL Central Microsoft Windows Edition To monitor and manage on Windows (PATROL 7.x), use PATROL Central Microsoft Windows Edition. PATROL Central Web Edition To monitor and manage on the Web (PATROL 7.x), point a browser to the PATROL Central Web Edition Web server.
Note
PATROL Central Web Edition is sometimes considered a console system, but its functionality is provided by the PATROL Central Web Edition Web server, which is a common services component.
PATROL Fundamentals
2-7
Common Services
A common service processes data from managed systems and facilitates communication between managed systems and console systems. Components in the PATROL 7.x architecture communicate with each other using a set of computers running real time server (RTserver) software. These computers form the RTserver cloud. The common services include the following components: PATROL Console Server Provides console services for the PATROL 7.x consoles. Instead of a console connecting to many managed systems the console server provides managed system data to multiple PATROL 7.x consoles. RTserver Provides a communication infrastructure for the PATROL Console Servers, Agents, and PATROL 7.x Consoles. A set computers running RTservers form the RTserver cloud. PATROL Central Web Edition (Web server) Provides the console functionality to users pointing a browser to the PATROL Central Web Edition Web server.
Managed Systems
A managed system (computer) runs software that manages the applications on the computer and the resources on the system. The following components manage the applications and resources on a managed system: PATROL Agent PATROL KMs
PATROL Agent version 3.5 works with both the PATROL 3 architecture and PATROL 7 architecture.
2-8
PATROL Components
This section provides detailed information about the components that make up the PATROL architecture. Table 2-1 lists the PATROL components described in this section:
Table 2-1 PATROL Components
Component
PATROL Agent
Description
The PATROL Agent is the core piece of the PATROL architecture, which is used to monitor managed systems. PATROL KMs are the data collection instructions use by the agent to monitor an operating system or an application on one ore more managed systems. The following PATROL Consoles are user interfaces that display managed system data: PATROL Central Operator Web Edition PATROL Central Operator Microsoft Windows Edition PATROL Console for Microsoft Windows (operator and developer) PATROL Console for Unix (operator and developer) The PATROL Console Server provides persistent support for user-defined, custom views. RTservers provide a communication infrastructure to the PATROL components. PATROL employs a security system that protects your environment as determined by you. PATROL security secures the PATROL components, not the enterprise running the PATROL components.
Page
2-10
PATROL KMs
2-11
PATROL Consoles
2-15
PATROL Console Server RTservers PATROL Security
2-20
2-23 2-24
PATROL Fundamentals
2-9
PATROL Agent
The PATROL Agent is the core piece of the PATROL architecture that monitors managed systems. PATROL Agents load information from KMs, gather statistics, and send alerts and requested information to the PATROL Consoles. PATROL Agents accept requests from the PATROL Consoles and initiate actions based on those requests. Using information from a PATROL KM, a PATROL Agent can perform the following activities: detect the presence and state of an application instance (discovery) collect data on any measurable aspect of an application instance (parameters) interpret data by using defined rules act as a service provider for event management store collected data locally in files (history) implement predefined actions to correct an abnormal condition (recovery actions)
You must install a PATROL Agent on each system that you want to manage. For more information on the PATROL Agent, see the PATROL Agent Reference Manual.
2-10
PATROL KMs
PATROL KMs contain the data collection instructions for monitoring an operating system or an application. PATROL has two different types of KMs: computer class The basic object class to which an instance of the same computer type belongs. Examples include Solaris, HP, and Microsoft Windows. PATROL includes computer classes for all supported platforms and operating systems. application class The object class to which an instance of the same application type belongs. The application class contains the logic required to monitor and manage instances of the application class. Application classes include the following features: prediscovery and discoverylogic to find application instances parametersmonitoring and data collecting elements for application instances InfoBox itemsinformation about an application instance recovery actionsprocedures that perform corrective actions menusOS and PSL commands or tasks to monitor and manage application instances
Application classes are represented on the console as containers in Unix and folders in Windows. You can use a PATROL Developer Console to add or change application classes. A PATROL Agent receives information from KMs about all the computers and applications in your monitored environment. A KM contains information about how to identify objects, how to represent them in a PATROL Console, and what actions to take when a monitored objects state changes.
PATROL Fundamentals
2-11
A PATROL Agent loads a KM into memory in one of the following ways: A PATROL Console has explicitly requested that the KM be loaded on the managed system. The KM is defined as a preloaded KM that is automatically loaded when the PATROL Agent process starts.
The PATROL Agent discovers applications running on each monitored computer. This activity is called application discovery. Loading a KM on the system stores the following: information that PATROL uses to discover and represent applications KM parameters that run against the applications menu options available in the application pop-up menus.
KMs are available for many software systems and applications. The computer KM is the basic operating system KM and contains information about every class of computer you might manage. You can also build new KMs or customize existing ones by using a PATROL Developer Console.
Data Collection
The first step in monitoring and managing your systems with PATROL is data collection. A PATROL KM uses the following processes to collect data in your enterprise: prediscovery discovery parameter execution
Prediscovery
The PATROL Agent uses the prediscovery process to determine whether or not the proper conditions exist to proceed with application discovery. Prediscovery checks for the following conditions:
2-12
the current operating system supports the application class the PATROL Agent and KM version numbers are compatible other critical conditions required by the PATROL Agent are met
Discovery
After a successful prediscovery cycle, the PATROL Agent proceeds with discovery. Discovery is a PATROL activity that finds the applications and instances that exist on a machine. When instances are discovered, an icon appears on your desktop. Each application class includes rules for discovering its instances. Application definition information is checked against the information in the PATROL Agent process cache, which is periodically updated. Each time the PATROL Agent process cache is refreshed, application discovery is triggered. The PATROL Agent uses one of the following discovery types: simple discovery PSL discovery
Simple Discovery Simple discovery is an easy technique that allows you to set up monitoring of simple application classes. You define simple discovery rules to look for the following items: specific files specific processes a combination of specific files or processes, or both patterns to match with one or more files or processes or both
PATROL Fundamentals
2-13
PSL Discovery PATROL Script Language (PSL) discovery can perform the following tasks for each application class: discover complicated application instances that cant be detected by simple discovery create each monitored application instance determine and set the state of each discovered application instance check whether previously discovered application instances still exist on the monitored machine and destroy obsolete application instances define the execution environment for each application class and set PATROL Agent namespace variables set up validation and error recovery procedures for the discovery process collect data outside the scope of the application class during the application discovery process control synchronization of application discovery when the existence of one application class depends on the existence of another
PATROL discovery can search a variety of system resources to detect the existance of an application class instance. It can discover files, processes, shared memory segments, the state of communication links, or whatever may be appropriate. One of the most common means of detecting active application instances is by searching for their active processes.
Parameter Execution
After the agent creates application instances, it prepares and loads parameter executables and queues the parameters to execute in their scheduled order. As parameter execution occurs, monitoring begins, and the PATROL Agent creates and populates the parameters.
2-14
PATROL Consoles
PATROL Consoles serve as user interfaces into managed systems. From a PATROL Console, you can monitor and manage either an entire enterprise-wide information system or just a collection of workstations, server computers, and single machines. The PATROL Console displays all the monitored resources in a distributed system as icons. The state of an icon indicates the state of the corresponding resource. With the PATROL Console, you can view the status of your distributed environment and perform the following tasks: define the applications that PATROL monitors run predefined or user-defined commands and tasks on managed systems log on to any managed computer customize menu commands and application parameters (by using the PATROL Developer Console) build new KMs (by using the PATROL Developer Console)
The remainder of this section discusses the following consoles in greater detail: PATROL Central Operator Microsoft Windows Edition PATROL Central Operator Web Edition PATROL Console for Microsoft Windows and Unix PATROL Event Manager Console
PATROL Fundamentals
2-15
PATROL Central Operator Microsoft Windows Edition
The Windows Edition of PATROL Central Operator is the native Microsoft Windows console for use with the PATROL 7.x architecture. You can use the console to monitor and manage either an entire enterprise-wide information system or a collection of workstations, server computers, and single computers. You can use PATROL Central Operator to perform the following tasks: view the state of your distributed environment select which managed systems and applications you want to monitor view all the monitored resources in your distributed environment as icons or in lists organize your monitoring environment with shortcuts, custom views, folders, and charts. run predefined and user-defined commands and tasks on managed systems customize select properties of PATROL objects, such as the alarm ranges of parameters view, acknowledge, close, and delete PATROL events query for PATROL objects, based on object type and state run commands when a monitored resource changes state retrieve and delete historical data
Note
PATROL developer functionality is not supported by PATROL Central Operator. For development functionality, you must use the PATROL Console for Windows or PATROL Console for Unix in developer mode. The PATROL Central Operator- Microsoft Windows Edition communicates with managed systems by using the RTserver and the PATROL Console Server. For more information on PATROL Central Operator Microsoft Windows Edition, see the PATROL Central Operator Microsoft Windows Edition Help or PATROL Central Operator Microsoft Windows Edition Getting Started.
2-16
PATROL Central Operator Web Edition
The Web Edition of PATROL Central Operator is a cross-platform, Web-based console for use with the PATROL 7.x architecture. You can use it to monitor and manage either an entire enterprise-wide information system or a collection of workstations, server computers, and single computers. You can use PATROL Central Operator Web Editionto perform the following tasks: view the state of your distributed environment select which managed systems and applications you want to monitor organize your monitoring environment with custom views and folders run predefined and user-defined commands and tasks on managed systems customize select properties of PATROL objects, such as the alarm ranges of parameters view, acknowledge, close, and delete PATROL events query for PATROL objects, based on object type and state run commands when a monitored resource changes state retrieve and delete historical data
Note
PATROL developer functionality is not supported by PATROL Central Operator. For development functionality, you must use the PATROL Console for Microsoft Windows or PATROL Console for Unix in developer mode. For more information on PATROL Central Operator Web Edition, see the PATROL Central Operator Web Edition Help or the PATROL Central Operator Web Edition Getting Started.
PATROL Fundamentals
2-17
PATROL Consoles for Microsoft Windows and Unix
The PATROL Console is a graphical workspace from which you issue commands and monitor and manage your environment. The PATROL Console displays all of the managed systems and applications as icons. The following types of PATROL Consoles are available: PATROL Operator Console PATROL Developer Console
PATROL Operator Console
The PATROL Operator Console displays all of the monitored computers and applications as icons. With the PATROL Operator Console you can perform these tasks: define which applications you want PATROL to monitor monitor and manage computers and applications through the PATROL Agent and PATROL Knowledge Modules monitor the PATROL Agents use of resources run predefined or user-defined commands and tasks on managed systems run commands on the PATROL Console machine when a state change occurs on a monitored computer monitor any managed computer retrieve historical data stored by the PATROL Agent
2-18
PATROL Developer Console
With the PATROL Developer Console, you can do everything you can do with the PATROL Operator Console, plus the following actions: build new KMs customize menu commands and application parameters edit or replace KMs send additional KMs to an agent machine start and stop PATROL Agents remotely modify agent knowledge in memory start the PATROL Agent configuration utility transfer knowledge to an agent specify which changes the agent should commit (save) delete historical data stored by the PATROL Agent
More Information
For more information on the PATROL Console for Unix, see the PATROL Console for Unix Help or the PATROL Console for Unix User Guide. For more information on the PATROL Console for Microsoft Windows, see the PATROL Console for Microsoft Windows Help or one of the following user guides: PATROL Console for Microsoft Windows User Guide Understanding the Basics of PATROL, Volume 1 PATROL Console for Microsoft Windows User Guide Monitoring and Managing with PATROL, Volume 2 PATROL Console for Microsoft Windows User Guide Customizing PATROL, Volume 3
PATROL Event Manager
The PATROL Event Manager records the event messages that the PATROL Agent generates for each managed system and application. You can run the PATROL Event Manager from the PATROL Console, or you can use it as a stand-alone application with the PATROL Event Manager Console (Unix). To avoid the distraction of unimportant events and low-priority alerts for noncritical resources, you can define event filters.
PATROL Fundamentals
2-19
With the PATROL Event Manager, you can select filtering criteria for important events on critical resources. You can also determine the cause of warnings and alarms on managed resources. You can display a PATROL Event Manager window for any computer, application, or parameter. You can also display all the events for all managed computers and applications. Use the PATROL Event Manager to perform the following tasks: view event information manage events define events use events to control your environment trigger events generate event statistics
You use a PATROL Event Manager for the entire monitoring environment or for a single parameter instance. The PATROL Event Manager provides filtering options. For more information on the PATROL Event Manager, see the PATROL Event Manager Console for Unix User Guide or the PATROL Console for Microsoft Windows User GuideMonitoring and Managing with PATROL, Volume 2.
PATROL Console Server

With this release PATROL Agent and PATROL Console communication is changed from two-tiered, direct connections to three-tiered connections with an additional application server in the middle tier. In the case of PATROL Consoles, this middle tier is PATROL Console Server. It creates a bridge between PATROL Agents distributed over the enterprise and new PATROL 7.x Consoles. The following PATROL 7.x consoles supported in this release: PATROL Central Operator Microsoft Windows Edition PATROL Central Operator Web Edition
The PATROL Console Server performs the following responsibilities: stores frequently-accessed files in a centralized location
2-20
caches console-specific agent information for use by the PATROL 7.x consoles sends requests to execute KM commands from consoles to agents creates a centralized location for all users to access agents allows centralization of privilege assignments and access control definitions (for both maintenance of tables and checking at runtime) stores console credentials and impersonation data for console accounts in one central location Centralization allows PATROL administrators to use authentication information through impersonation of user accounts for a given agent. This pocess in turn allows users to authenticate to agents without requiring username and password entry for each agent access or storage of passwords at every individual console system. executes the same queries across all managed systems executes the same event filters and queries across all managed systems executes state change actions as defined by users in their management profiles creates a persistent data cache for static agent attributes such as PATROL Agent versions, operating system names and versions, and preloaded KM lists, allowing you to access and query the information in the absence of agents stores privilege information defined through PATROL 7.x Administration Console Modules stores Access Control List (ACL) definitions as defined through PATROL 7.x Administration Console Modules
PATROL Fundamentals
2-21
stores management profiles for PATROL 7.x consoles so that the same information can be accessed from any PATROL 7.x console from any computer without additional configuration that is local to the computer where the PATROL Consoles are running This feature enables location transparency for the users and allows roaming management profiles. stores KM icons, KM Help files, and lists of KM menu and InfoBox commands stores user preferences for charts; gauges; column order in list views; and view types such as icons, lists, and details stores which PATROL Agents to connect and which KMs to load stores user-defined charts, custom views, folder hierarchies allows centralized access to predefined queries, event filters, configuration options, and charts
For more information on PATROL Console Server, see the PATROL Console Server and RTserver Getting Started.
2-22
RTservers
The RTserver delivers application-related data between the following PATROL components: PATROL Agent PATROL Central Microsoft Windows Edition PATROL Central Web Edition Web server PATROL Console Server
You can install more than one RTserver to form an RTserver cloud. RTserver clouds provide flexibility and load balancing. If an RTserver crashes, another RTserver in the cloud picks up the load and the PATROL components continue to communicate. For additional load balancing, you can divide your PATROL components into groups and have each group communicate with their own RTserver cloud. For more information on RTservers, see PATROL Console Server and RTserver Getting Started.
PATROL Fundamentals
2-23
PATROL Security
All systems in any environment are susceptible to potentially harmful events if the proper security is not in place. Both internal and external users can instigate critical events, either maliciously or unintentionally. Careful implementation of security controls and restrictions minimizes the chance of security violations. PATROL employs a security system that protects your PATROL environment with the options that you choose. You can install the level of security that you want and configure the chosen security level to your specifications.
Types of PATROL Security
The major aspects of PATROL security are communications-level security and the administration of user rights and privileges.
Communications-Level Security
The term security can mean many things, even in the restricted domain of computer networks. Conventional login passwords, for example, address the need for access securityensuring that ly given to legitimate users access computing resources. Just as access security protects access to computing resources, communications security protects information that is transmitted over a communications channel. Communications security protects such information only in the context of a transaction between communicating parties. Once that information is received, it moves from being a transaction requiring communications security into some other format (such as data stored on a disk), where it must be protected by other forms of security.
2-24
For information about how security is implemented at the communications level, see the PATROL Security User Guide. It discusses in detail the ways in which the transactions between PATROL components are secured so that message privacy is secured and the communicating components are authenticated. These two aspects of security (privacy and authentication) are addressed by communications-level security. Verification of the rights and privileges of communicating components (authorization) is addressed by user administration, described below.
User Administration
This section provides a brief overview of user administration. In PATROL, user administration is based on the following: Establishing the user's identity to PATROL (authentication and impersonation) Controlling what functionality users can access (privileges) Controlling what objects users can access (rights)
User authentication and impersonation Verifying a user's identity to PATROL is called authentication. Each PATROL program that you access in the PATROL layered architecture must authenticate your identity. For example, if you use PATROL Central Operator, both the PATROL Console Server and the PATROL Agent must authenticate your identity. A PATROL program, such as PATROL Console Server or PATROL Agent, can only authenticate users with valid operating system accounts that it recognizes. Operating system accounts can be local or domain accounts.
PATROL Fundamentals
2-25
In order to allow a user to access PATROL Agents that do not recognize the users account, middle layers in the PATROL architecture, such as the PATROL Console Server, provide PATROL Agents with account information on behalf of the user. If a PATROL Agent does not recognize the original account of the user, the PATROL Console Server consults an impersonation table that maps users to alias accounts that are recognized by PATROL Agents. The PATROL Console Server then provides the PATROL Agent with the alias account that is configured for the user. About Privileges and Rights The PATROL 7.x architecture uses operating system user accounts and groups on the PATROL Console Server to control privileges and rights for PATROL. A privilege allows a user to access specific functionality. A right allows a user to access specific PATROL objects. A PATROL user cannot access functionality or objects without the appropriate privileges and rights. Users inherit the privileges and rights of the groups that they belong to. Usually it is easier to add users to the appropriate groups in the operating system than to administer privileges and rights directly. Table 2-2 lists the groups with pre-defined privileges and rights. These groups are created when you install the PATROL Console Server if they do not already exist.
Table 2-2 Default PATROL Groups on the PATROL Console Server
Group
patop patpop patwatch patadm patscadm
Description
PATROL operators power operators operators who can only watch console objects PATROL administrators PATROL administrators who can configure security
2-26
How Much Security Do You Need?
This version of PATROL includes more security options by offering five policy levels (the basic security level plus levels 1 through 4). These policies provide a predefined set of security configurations that you select when you install PATROL. The security policies allow you to install the least secure (basic security) up to the most secure (level 4) features of PATROL, depending on your system needs and how much complexity you can allow in securing your systems. High levels of security require additional configuration of the communicating components (the agent and console) and are more difficult to use. Lower levels of security are much easier to configure and use but provide less security. Before installing PATROL, decide how much of a trade-off you are willing to make between security and usability by examining the differences between the five policy levels, as described in Security Levels on page 2-28. Basic security provides a minimal level of security with no configuration requirements. At the highest security level (4), all communicating components must authenticate with each other, and key databases must validate connection requests.
Note
All components in a system, including agents and consoles, must operate at a common level of security. This requirement is automatically ensured when you install PATROL with the basic (default) level of security.
PATROL Fundamentals
2-27
Security Levels
Table 2-3 summarizes usability issues and configuration requirements for each of the five security levels.
Table 2-3 Usability versus Security for the Five Security Levels
Security Level
Basic Security
Description
does not introduce any overhead in performance or configuration does not provide any additional security beyond basic PATROL security features introduces a minimal amount of overhead associated with performance and disk space introduces no overhead in usability or maintenance provides only basic security such as traffic encryption Some security events (like digital signature verification failure) are ignored to simplify the maintenance burden. increases performance overhead and maintenance costs because of the use of SSL and X.509 certificates preconfigured upon installation and does not require any additional configuration efforts introduces SSL-based authentication and requires more configuration due to the requirement of a certificate for each authenticating agent provides substantially increased traffic security and general data integrity provides the tightest security measures by requiring a certificate for each authenticating agent and console requires the most configuration due to the requirement of a certificate for each authenticating agent and console
Level 1
Level 2
Level 3
Level 4
2-28
Monitoring with PATROL

With PATROL, information about your managed systems is obtained using a PATROL Console to access the following information: instance icons menu command reports task reports InfoBox items parameter graphs and gauges parameter warnings and alarms events error messages
Depending on the PATROL Console you are using to monitor your managed systems, information is presented and accessed in slightly different ways. For more information on PATROL Consoles and monitoring and managing systems with PATROL, see the following publications: PATROL Central Operator Microsoft Windows Edition Getting Started PATROL Central Operator Web Edition Getting Started PATROL Console for Microsoft Windows User Guide Monitoring and Managing with PATROL, Volume 2 PATROL Console for Unix User Guide PATROL Central Operator Microsoft Windows Edition Help PATROL Central Operator Web Edition Help
PATROL Fundamentals
2-29
Managing with PATROL

With PATROL, you can manage and change your systems by using a PATROL Console to perform management tasks. Management tasks can be manual or automated and may include the following types of actions: menu commands parameter recovery actions state change actions PATROL Agent setup commands
Depending on the PATROL Console you are using to manage your systems, tasks may be performed in slightly different ways. For more information on PATROL Consoles and monitoring and managing systems with PATROL, see the following publications: PATROL Central Operator Microsoft Windows Edition Getting Started PATROL Central Operator Web Edition Getting Started PATROL Console for Microsoft Windows User Guide Monitoring and Managing with PATROL, Volume 2 PATROL Console for Unix User Guide PATROL Central Operator Microsoft Windows Edition Help PATROL Central Operator Web Edition Help
Where to Go From Here

After you have familiarized yourself with PATROL and the new PATROL infrastructure components, you are ready to start gathering information to use with the PATROL Infrastructure Planner. See Chapter 3, Examining Your Enterprise to start gathering information to plan your PATROL Implementation.
2-30
This chapter discusses what you must consider before planning your PATROL infrastructure and what information you need to complete your infrastructure plan. This chapter includes the following topics: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Mapping Your Enterprise Locations. . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 Defining Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 Location Mapping Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 Gathering Detailed Location Information . . . . . . . . . . . . . . . . . . . . . 3-7 How many Managed Systems are Present? . . . . . . . . . . . . . . . . . 3-8 Additional RTserver services desired?. . . . . . . . . . . . . . . . . . . . . 3-8 Are PATROL Consoles needed for this location? . . . . . . . . . . . . 3-9 What Other Systems can Host Common Services Components? 3-10 Detailed Location Information Worksheet. . . . . . . . . . . . . . . . . . 3-10 Where to Go From Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
3-1
Introduction
Before you can plan your PATROL infrastructure implementation you, must examine your enterprise and gather the information you need to use the PATROL Infrastructure Planner. Examining your environment before planning your PATROL infrastructure involves the following tasks: mapping your enterprise locations gathering detailed location information
The following sections help you gather the required information for your enterprise and provide sample worksheets you can use.
Note
While you can use the PATROL Infrastructure Planner without providing all the detailed information about your enterprise, it will be easier to plan your implementation and your plan will be more detailed, and more valuable, if you gather this information before using the planner.
3-2
Mapping Your Enterprise Locations

Before you can plan your PATROL infrastructure implementation you will map or define the locations that make up your enterprise. When you map your enterprise you consider the following: location type (logical and physical) firewalls location function
Defining Locations
The first step in defining your enterprise is to define the locations that make up your enterprise. A location is a (physical or logical) grouping of systems that are managed or that manage other systems. Normally, the locations in an enterprise are defined by the following criteria: a physical or geographical location region city building floor
For example, you may want to create a location for each city in your enterprise. a logical or functional group of an enterprise that could span physical or geographical locations accounting sales application management For example, you might have an accounting department that spans several physical locations but shares common file servers that you want to manage as one logical location.
3-3
Under the following circumstances, consider creating your infrastructure plan defining your entire enterprise as one location: If you have a small enterprise, you may consider the entire enterprise as one location. If you have a physical location that does not communicate with the rest of your enterprise, you can plan the infrastructure implementation for that location as though it is a small, independent enterprise with one location.
Note
Your enterprise can be a mix of physical and logical locations.
Location Function
When you are defining your locations, you may consider the function of a location. While location function is not directly related to the grouping of systems into locations, it is an important consideration for the implementation plan. Each location fits into one of the following categories: managed locationsmonitored and managed by another location in the enterprise management locationsmonitors and manages other locations in the enterprise botha managed and management location
Firewalls
One limitation to grouping your locations into physical and logical locations is the use of firewalls in your enterprise. While you may want to create a logical location that includes several physical locations that perform similar tasks or share resources, you may be limited by the presence of a firewall between the physical locations.
3-4
For example, you could have accounting departments in two cities that share file servers, and you may want to create one logical management location called accounting. If the two physical locations are separated by a firewall, you cannot make them one logical location.
Note
No location can include an internal firewall.
Location Mapping Worksheet

Use the Location Mapping Worksheet on page A-3 to record the following information for each location in your enterprise: What is the location name? Is the location a physical or logical location? Is the location a managed or management location, or is it both? Is the location separated from other locations by a firewall?
See the Location Mapping WorksheetExample on page 3-6 to see how you can use the Location Mapping Worksheet to define all the locations in your enterprise.
Note
Only the location name, description, and firewall information is used by the PATROL Infrastructure Planner, but the location type and function can be recorded on the worksheet for future reference.
3-5
Location Mapping WorksheetExample
Name
Management 1
Description
Primary management location.
Type
physical logical physical logical physical logical physical logical physical logical physical logical physical logical physical logical physical logical physical logical
Function
managed management both managed management both managed management both managed management both managed management both managed management both managed management both managed management both managed management both managed management both
Firewall
Yes No Yes No Yes No Yes No Yes No Yes No Yes No Yes No Yes No Yes No
Management 2
Secondary management location with a few managed systems. Example managed location...
Managed 1
Managed 2
Example managed location...
Managed 3
Managed 4
Managed 5
Managed 6
Managed 7
Managed 8
Note
The number of locations is not limited. You can define as many locations as you need.
3-6
Gathering Detailed Location Information

After you define your enterprise locations, you gather detailed information about the locations. Answer the following questions for each location: How many Managed Systems are Present? Additional RTserver services desired? Are PATROL Consoles needed for this location? If the answer is yes, you will need to answer the following questions: Number of concurrent users to monitor using a Web browser? Number of PATROL Central Windows Edition consoles required? What Other Systems can Host Common Services Components?
These question are discussed in detail the following sections.
3-7
How many Managed Systems are Present?

A managed system is a computer that you monitor and manage. If a location is a management location, it is possible that you will not have any managed systems in the location. Each managed system requires a PATROL Agent and PATROL KMs for the applications and resources that you manage. When planning a PATROL implementation, you must consider which PATROL KMs you will require for the applications you monitor and manage. After you decide what applications you will monitor, you can consult specific KM getting started guides for detailed information on installing specific KMs. The number of managed systems influences the number of console servers and RTservers that your implementation requires. For more information on managed systems, see the following topics: Managed Systems on page 2-8 PATROL Agent on page 2-10 PATROL KMs on page 2-11
Additional RTserver services desired?

If a server is unable to deliver your status messages, messaging failover protection provides another server to prevent an interruption in monitoring. To implement effective messaging failover protection, install additional RTservers in your enterprise. For more information on RTservers, see RTservers on page 2-23.
3-8
Are PATROL Consoles needed for this location?

Do you have users monitoring managed systems from this location? If this location uses PATROL Consoles to monitor and manage resources, the answer is yes. The managed systems that you monitor may or may not be in this location. See PATROL Consoles on page 2-15 for more information on the PATROL Consoles. If this location requires PATROL Consoles, answer the following questions about the console users. Number of concurrent users to monitor using a Web browser? You do not have to install a desktop application with the PATROL CentralWeb Edition, but the number of users influences the number of PATROL Central Operator Web Edition Web servers, console servers, and RTservers that are required. Record the number of concurrent users in the Detailed Location Information Worksheet on page A-4. For more information on PATROL Central Operator Web Edition, see PATROL Central Operator Web Edition on page 2-17. Number of PATROL Central Windows Edition consoles required? Each Windows user requires the PATROL Central Operator Microsoft Windows Edition console to be installed on their desktop. In addition to the desktop application, the number of Windows users influences the number of console servers and RTservers that are required. Record the number of users and the hostname for each user in the Detailed Location Information Worksheet on page A-4. For more information on PATROL Central Operator Microsoft Windows Edition, see PATROL Central Operator Microsoft Windows Edition on page 2-16.
3-9
What Other Systems can Host Common Services Components?

In addition to the managed systems and console systems that you install, you may require additional systems to host the following components: PATROL Central Web Edition servers PATROL Console Servers RTservers
Record the hostnames of available systems in the Detailed Location Information Worksheet on page A-4.
Detailed Location Information Worksheet

Use the Detailed Location Information Worksheet on page A-4 to record the detailed information for each location in your enterprise. You should create one worksheet for each location. If your location has more hostnames than the worksheet provides room for, use more than one worksheet for the location. See Detailed Location Information WorksheetExample on page 3-11 for an example of a completed worksheet. You use the completed worksheets for the PATROL Infrastructure Planner interview. The more detailed your information, the easier it will be to complete you plan and the more detailed your infrastructure plan will be. The PATROL Infrastructure Planner uses this data to develop your PATROL implementation plan based on guidelines developed by BMC Software performance and scalability testing. For more information on implementation guidelines, see Infrastructure Guidelines on page 4-5.
3-10
Detailed Location Information WorksheetExample
Location Name: Management 2

How many Managed Systems are Present? Additional RTserver services desired? Are PATROL Consoles needed for this location? Number of PATROL Central Windows Edition consoles required?
250
yes / no yes / no
15
Windows Console users hostnames operator_1 operator_3 operator_5 operator_2 operator_4 operator_6 operator_8 operator_10 admin_12 admin_14
Record the hostnames of the users that require Windows consoles installed on their desktops. This information is not required to complete the PATROL infrastructure Planner, but you can use this information as a reference when you install the PATROL Central OperatorWindows Edition Consoles in your enterprise.
operator_7 operator_9 admin_11 admin_13 admin_15
Number of concurrent users to monitor using a Web browser? What Other Systems can Host Common Services Components?
Record the hostnames of the systems that are available to host PATROL infrastructure components. If you record this information and use it to complete the PATROL Infrastructure Planner, your implementation plan will include detailed installation steps that include the hostnames.
10
server_2 server_4 server_6
hostnames of available systems server_1 server_3 server_5 server_7
3-11

After you have examined and collected the detailed information about your enterprise, you are ready to use the PATROL Infrastructure Planner. See Chapter 4, Using the PATROL Infrastructure Planner to start planning your PATROL Implementation.
3-12
Using the PATROL Infrastructure Planner
This chapter describes the infrastructure plan, how to get started with the PATROL Infrastructure Planner, and the guidelines the planner uses to create your infrastructure plan. This chapter covers the following topics: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Where is the PATROL Infrastructure Planner? . . . . . . . . . . . . . . 4-2 System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Starting the PATROL Infrastructure Planner . . . . . . . . . . . . . . . . 4-3 Infrastructure Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 Other Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 The Infrastructure Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8 Where to Go From Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
4-1
Introduction
This section describes how to get started using the PATROL Infrastructure Planner. Review the following information before you begin: Chapter 2, PATROL Fundamentals for information on PATROL Experienced PATROL users review What is New in PATROL 7 on page 2-4. Chapter 3, Examining Your Enterprise for information on what information you need to complete the PATROL Infrastructure Planner
Where is the PATROL Infrastructure Planner?

The PATROL Infrastructure Planner can be accessed from the CD enclosed with the hardcopy PATROL Infrastructure Planning Guide (this book) or on the Web at the following URL: http://epd.bmc.com/downloads/piplanner/index.html
System Requirements
The PATROL Infrastructure Planner is supported on the following operating systems: Windows (all versions) Unix (with JRE v1.4 installed) Solaris (7, 8, and 9) Linux (with JRE v1.4 installed) Red Hat (6.1, 6.2, 7.0, 7.1, 7.2) Suse (6.4, 7.0, 7.1, 7.2. 7.3)
4-2
Starting the PATROL Infrastructure Planner

The procedure for starting the PATROL Infrastructure Planner depends on the operating system. Use the following procedure that corresponds to your operating system.
Windows
To start the PATROL Infrastructure Planner on Windows, insert the PATROL Infrastructure Planner CD into the CD-ROM drive and perform the following steps:
Step 1
Change to the IPlanner directory with the following command: cd IPlanner
Step 2
Start the PATROL Infrastructure Planner with the following command: IPlanner.bat
Linux and Unix
To start PATROL Infrastructure Planner on Linux and Unix, insert the PATROL Infrastructure Planner CD into the CD-ROM drive and perform the following steps:
Step 1
Change to the IPlanner directory with the following command: cd IPlanner
Step 2
Start the PATROL Infrastructure Planner with the following command: ./IPlanner.sh
Note
On Windows, JRE v1.4 is included on the CD, and the PATROL Infrastructure Planner will use that JRE. On Unix, you must have JRE v1.4 installed to run the PATROL Infrastructure Planner.
4-3
When the PATROL Infrastructure Planner starts the Welcome screen opens as shown in Figure 4-1.
Figure 4-1 PATROL Infrastructure Planner Welcome Page
Follow the on screen instructions to plan your PATROL infrastructure.
4-4
Infrastructure Guidelines
Recommendations generated by the infrastructure planner are based on best practices developed by BMC Software through product scalability testing of our products. The infrastructure planner uses the data that you provide during the interactive interview to determine the infrastructure components you will require. The infrastructure planner determine how many of the following components are required: PATROL Console Servers RTservers PATROL Central Web Edition Web servers
The following sections discuss the general guidelines that determine the number of infrastructure components required for your enterprise.
PATROL Console Server Guidelines
One PATROL Console Server is implemented for each location. An additional PATROL Console Server and RTserver pair is required for every 25-35 concurrent PATROL 7.x Console users.
Note
The number of PATROL Console Servers required can be affected by heavy user loads. You could require additional console servers under certain conditions.
4-5
RTserver Guidelines
The following rules determine how many RTservers you require. One RTserver is required for each PATROL Console Server. Normally, console servers and RTservers are installed in a pair for each location. When a location requires message failover protection, the total number of RTservers is multiplied by 1.5. For example, if your location requires four RTservers without failover protection, it will require six RTservers to supply effective failover protection. One additional RTserver is implemented when the location is separated from other locations by a firewall. One additional RTserver is required for every 200 managed systems. In large environments of over 500 PATROL Agents, you may require an additional RTserver to handle console connections.
PATROL Central Web Edition Web Server Guidelines
One PATROL Central Web Edition server is required for every 25 concurrent PATROL Central Web Edition users.
4-6
Other Components
Since they are not part of the PATROL infrastructure, the infrastructure plan does not include specific recommendations for the following components: PATROL Central Operator Windows Edition PATROL 3.5 Agents KMs for managed systems PATROL 3.5 Consoles
Generally, you install these components where they are required. The PATROL 3.5 components can be installed on the same system with any PATROL 7.x component.
4-7
The Infrastructure Plan

When you complete the PATROL Infrastructure Planner, you can view the recommended infrastructure plan for your environment. The infrastructure plan assists you with the installation of the recommended PATROL infrastructure components in your environment. In addition to determining the required number of components, the PATROL Infrastructure Planner provides instructions for implementing the infrastructure. The plan includes the following instructions: RTserver configuration information installation CD information component requirements firewall information
The infrastructure plan is divided into individual sections for each location in your enterprise. that includes the PATROL components Each location section of the infrastructure plan contains sections related to specific components that must be installed for that location. The component sections describe the component and provide installation information. The following component sections are provided for each location when: Planner Interactive Responses Console Servers and RTservers Firewall Policy PATROL Central Operator Web Edition PATROL Central Operator Microsoft Windows Edition
4-8
In the Console Server and RTserver section for each location, there is a table, like the one shown in Figure 4-2, that shows you where the RTservers and console servers should be installed. The table contains generic host names, but you can click the host name in the Host Name column to specify the actual host names for the components in your locations.
Figure 4-2 Console Server and RTserver Table
Note
To edit a host name in the table, click the name to select it and type in the new name.

After you complete your implementation plan using the PATROL Infrastructure Planner, you are ready to install PATROL using your infrastructure plan. See Chapter 5, PATROL Installation Overview for an overview of the PATROL installation process.
4-9
4-10
PATROL Installation Overview

This chapter introduces and provides an overview of the PATROL installation. This chapter contains the following topics:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 The Installation Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 Local Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 Remote Installations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Security Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Component and Product Requirements . . . . . . . . . . . . . . . . . . . . . . . 5-4 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 Where to Go From Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
5-1
Introduction
Before you install PATROL, you should be familiar with the following aspects of PATROL: the BMC Installation Utility security migration product and component requirements where to find more information
The Installation Utility

The installation utility allows you to perform a local installation of or to uninstall BMC Software products on computers running either Windows or Unix operating systems. The installation utility also provides an option that allows you to create a product image that can be transferred to and installed locally on remote computers.
Local Installations
For most BMC Software products, you can choose between a Typical or Custom installation path to install products. The Typical path allows you to select only product groups, and requires only mandatory product configuration information. The Custom path allows you to select or deselect product groups and individual products or components within a group. The Custom path requires the same configuration information as the Typical path, but it also allows you to enter optional or advanced product configuration information. See the Installation Utility Reference Manual for more information on local installation.
5-2
Remote Installations
If you want to install products to more than one computer, you can use the installation utility to create an installable image of products, distribute that image to remote computers, and use the image to install the products on the remote computers.
When you create an installable image, the product configuration information that you enter must be the same for all computers on which the image is installed. If you want to specify different settings for different computers, you must either create a separate image for each set of values that you want to implement or edit the variables in the images control file. See the Installation Utility Reference Manual for more information on remote installation images.
Security Considerations
You must consider security before you install PATROL because the security level that your PATROL components use to communicate is specified during PATROL installation. For more information on security, see PATROL Security on page 2-24. For detailed security information, review the PATROL Security User Guide to plan your security implementation for PATROL.
5-3
Component and Product Requirements

Before you install your PATROL products and components, review the product and component installation requirements. Appendix A, Worksheets and Checklists contains installation checklists for the RTserver and PATROL Console Server. Installation requirements for other PATROL components are in the product release notes and getting started guides for those components.
Migration
If you are an existing PATROL user, you may have to consider migration of your existing PATROL environment when you install PATROL. For PATROL Console migration information, see PATROL Central Operator Microsoft Windows Edition Getting Started. For PATROL KM migration information see the following PATROL documentation: PATROL Migration Tools Release Notes PATROL Migration Tools User Guide
5-4

For more information on installing PATROL, see the following documentation: Installation Utility Reference Manual product release notes product getting started guides
After you install PATROL you can use the PATROL Infrastructure KM to visualize and understanding the communication characteristics of your PATROL infrastructure. See Chapter 6, The PATROL Infrastructure KM for information on using the PATROL Infrastructure KM.
5-5
5-6
This chapter describes the characteristics of the PATROL Infrastructure KM and user tasks that you can perform with it. This chapter contains the following topics: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 KM Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 KM and Parameter Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 Alarms and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5 Installing the PATROL Infrastructure KM. . . . . . . . . . . . . . . . . . 6-6 Configuring the PATROL Infrastructure KM . . . . . . . . . . . . . . . 6-11 Application Class Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13 Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15 InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20 Using the KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-31
6-1
Introduction
The PATROL Infrastructure KM monitors RTservers and the clients that are connected to them. RTservers are a key part of the communications infrastructure of the PATROL 7 product release. See PATROL Console Server and RTserver Getting Started and release notes for more information. In this chapter, a client can be any of the following components: a PATROL Console Server a PATROL Central Microsoft Windows Edition Console a PATROL Agent version 3.5 or later
In PATROL 7, a client connects to an RTserver to communicate with other clients. If more than one RTserver is installed, the RTservers communicate with each other, allowing all clients to communicate regardless of the RTserver they are connected to. The RTserver API allows clients to query the status of the RTserver network. The PATROL Infrastructure KM uses this API to acquire information and present it in a PATROL Console.
KM Hierarchy
The PATROL Infrastructure KM comprises the following application classes: The PATROL7 application class instantiates once and is the top-level container for instances of the other classes. P7_RTSERVERS creates one instance per RTserver as a child of the PATROL7 application. P7_RTCLIENTS creates one instance per client as a child of the P7_RTSERVERS application instance that represents the RTserver that the client is connected to.
Figure 6-1 on page 6-3 illustrates the hierarchy of KMs and parameters:
6-2
Figure 6-1
KM and Parameter Hierarchy
PATROLMainMap
top-level container
PATROL7
P7_coll instantiates once per RTserver P7_RTSERVERS
TotalRTservers TotalConsoles TotalConsoleServers TotalPatrolAgents
RTServer_coll
ClientCount
ConsoleServerCount
PatrolAgentCount
clientdis_coll instantiates once per client P7_RTCLIENTS
ConsoleCount
DisconnectedClients
TotalMsgsQueued
MsgsQueued
6-3
KM and Parameter Features

The PATROL7 application class contains parameters that display the aggregated numbers of RTservers and clients in the monitored network. The P7_RTSERVERS application class contains parameters that display totals for the server represented by the application instance. The P7_RTCLIENTS application class has one parameter, MsgsQueued, that displays the number of messages in the queue waiting for delivery to the client. The queue is located on the RTserver that the client is connected to.
Alarms and Events

The PATROL7 application class generates a warning event when a client disconnects from the RTserver network. This behavior is activated by default; you can deactivate it by using a menu command. If the client reconnects, a state change event is generated with the description Client Reconnected to RTserver. The ClientCount parameter of P7RTSERVERS goes into alarm when the total number of clients connected to the server approaches the defined limit. A large number of messages in the queue can indicate performance problems, so the MsgsQueued parameter of P7RTCLIENTS is set to alarm on certain threshold values.
Menu Commands
You can troubleshoot problems by using the menu commands of the application classes and instances. See Menu Commands on page 6-14 and Using the KM on page 6-21 for details.
6-4
Installation and Configuration

You install the PATROL Infrastructure KM on an agent host computer after installing the PATROL base components and at least one RTserver. After installing the PATROL Infrastructure KM you must configure it. In general, the PATROL Infrastructure KM is installed on a console and agent that are used by the system administrator responsible for maintaining PATROL. You should not install it on other host computers unless you have a specific reason to do so.
6-5
Installing the PATROL Infrastructure KM Summary:

Perform this task to install the PATROL Infrastructure KM on an agent or classic PATROL Console. This task is the same on Windows and Unix except for the initial steps.
Before You Begin
The following prerequisites must be installed and working: PATROL Agent version 3.5 or later PATROL Console version 3.5 or later or PATROL Central Microsoft Windows Edition and a console server
On Windows you must be logged on to the computer using an account in the Administrators group. On Unix you must be logged on to the computer using the same account that was used to install the existing PATROL installation. A TCP port above 50000 must be available on the computer.
Note
If you are installing the PATROL Infrastructure KM on a computer that has an RTserver installed, you must stop the RTserver before installing the PATROL Infrastructure KM.
To Start the Installation Utility on Windows Platforms Step 1 Step 2
Insert the product CD. Navigate to the CD-ROM drive and run setup.exe. Continue with To Continue Installing on page 6-7.
6-6
To Start the Installation Utility on Unix Platforms Step 1 Step 2 Step 3
Insert the product CD. Change (cd) to the drive that contains the product CD. Execute the shell script setup.sh. The following message appears:
Beginning installation using netscape and port 5000x URL to connect to is http://xxx.xxx.xxx.xxx:5000x/
A Web server begins running on the computer where you perform the installation. The URL given is the address of the Web server, where xxx.xxx.xxx.xxx is the computers IP address and 5000x is a TCP port selected by the installation program.
To Continue Installing
After you start the utility, three Web browser windows open. The third window displays a splash screen and then the Welcome page. Depending upon the speed of your computerand the speed of the network if you are installing from a network drivethis process can take up to two minutes. You can click Exit in the Welcome page or any subsequent page to cancel the installation.
Step 1
Click Next. The Review License Agreement page opens.
Step 2
Take the appropriate action: Click Accept and then Next to accept the license agreement and continue with installation. Click Exit to reject the license agreement and exit the installation program.
6-7
If you accept the license agreement, the Select Installation Option page opens.
Step 3
Select I want to install products on the computer now and Click Next. (To create an installable image, see To Create an Installable Image on page 6-9.) The Select Type of Installation page opens.
Step 4
Select Custom or Typical. The Typical path does not contain Step 11 though Step 13 on page 6-9, but the default directories will work for most users.
Step 5
Click Next. The Specify Installation Directory page opens.
Step 6
Confirm that the parent directory for PATROL products is displayed (for example, C:\Program Files\BMC Software). The PATROL Infrastructure KM must be installed in the existing PATROL directory structure. Click Next. The Select System Roles page opens.
Step 7
Step 8
Take the appropriate action: Select Managed System if you are installing on an agent host computer. Select Console System if you are installing on a console host computer.
You must select at least one option and you can select both.
Step 9
Click Next. The Select Products and Components page opens.
6-8
Step 10
Expand the tree by clicking the plus sign

Infrastructure Monitoring. Click Next.
and select PATROL
The Provide the PATROL 3.x Product Directory page opens.

Step 11
Confirm that the BMC Products Installation Directory field contains the parent directory of the PATROL Agent and Console file. If the directory is incorrect, click Back and return to Step 6 on page 6-8. Confirm that the PATROL 3.x Product Directory field contains the parent directory of the PATROL 3.x product files. Click Next. The Review Selections page opens.
Step 12
Step 13
Step 14
Confirm that the displayed information is correct. Click Back to change information. Click Start Install to continue. The Installation Status page opens.
Step 15
When the messages indicate that installation is 100% complete, click Next. The SUCCESS! page opens displaying log file information.
Step 16
Click Finish. The Web browser closes. Installation is complete.
To Create an Installable Image
You can create an installable image that installs the product silently (without user input) on computers with the identical configurations.
Step 1 Step 2
Begin with the Step 1 on page 6-7. In Step 3 on page 6-8 select I want to create an installable image to be installed later and select a destination directory for the image.
6-9
Step 3 Step 4
Continue with the rest of the procedure. In Step 14 on page 6-9 click Create Image. (Start Install does not appear when you are creating an image.) The installation image is created in the destination directory.
Step 5
Run install.exe or install.sh to install the product. The product is installed. On Windows a Command Prompt window opens and closes but it does not require user input.
List of Installed Files
Table 6-1 lists the installed files of the PATROL Infrastructure KM. The directories listed are subdirectories of PATROL_HOME. The KM uses other files such as icons that are installed with the console.
Table 6-1 Installed File List
File Name
lib/knowledge/PATROL7.kml lib/knowledge/PATROL7.km lib/knowledge/P7_RTSERVERS.km lib/knowledge/P7_RTCLIENTS.km lib/psl/p7acc.lib lib/help/winhelp/kmp.hlp ib/help/winhelp/kmp.cnt ib/help/winhelp/km_help_kmp lib/help/kmp.hlp lib/help/km_help_kmp lib/help/kmp (directory)
Purpose
KM list file KM files
Operating System
all all
function library Help files for PATROL Console for Microsoft Windows Help files for PATROL Console for Unix
all Windows
Unix
Where to Go from Here
After installing the PATROL Infrastructure KM you must configure it. Continue with the task on the next page.
6-10
Configuring the PATROL Infrastructure KM Summary:

Use this task to configure the PATROL Infrastructure KM by entering information about an RTserver on your network. This is usually a one-time task. If the RTserver used by this KM is removed from your network later, you must reconfigure the KM to connect to an active RTserver.
Before You Begin
You must have a PATROL Console and Agent running. The PATROL Infrastructure KM must be installed and loaded. (The list file to load is PATROL7.kml.) At least one RTserver must be running on your network, and you must know its DNS host name and port number. You can use any RTserver on your network, but the best choice is an RTserver running on the same host computer as the agent or on the same network segment.
To Enter RTserver Information in the PATROL Infrastructure KM Step 1
Run the menu command Administration => Identify RTserver Information of the PATROL7 application. The Add/Modify RTserver Information dialog box opens, as shown in Figure 6-2 on page 6-12.
6-11
Figure 6-2
Add/Modify RTserver Information Dialog Box
Step 2 Step 3
Enter the host name and port number of the RTserver. Select the protocol that the RTserver uses:
TCP is the default. UDP is used in some environments. Select Auto if you do not know which protocol is used.
Step 4
Click Apply. The Add/Modify RTserver Information dialog box closes and a confirmation dialog box opens.
Step 5
In the confirmation dialog box click OK. The dialog box closes and the P7_RTSERVERS application class instantiates, usually within a minute. The file $PATROL_HOME/common/smartsockets/standard/rtmon.cm (%PATROL_HOME%\common\smartsockets\standard\rtmon.cm on Windows) is created. This file contains configuration information for the PATROL Infrastructure KM.
6-12
If a Problem Occurs
If the P7_RTSERVERS application class does not instantiate, check the following items: Confirm that the host name, port number, and protocol are correct. Confirm that you can reach the host by using the ping command. Confirm that the RTserver is running; see PATROL Console Server and RTserver Getting Started.
Application Class Summary

Table 6-2 describes some key characteristics of the application classes of the PATROL Infrastructure KM:
Table 6-2 Application Class Summary
Create Icon for Class
Propagate State
Name
PATROL7
Icon
Status
active
Custom Discovery
5 min. 1 min. 1 min.
Discovery Action
creates a single instance of the class
yes
no
P7_RTSERVERS (child of PATROL7)
active
yes
yes
creates an instance for each RTserver on the network
P7_RTCLIENTS (child of P7_RTSERVERS)
active
yes
yes
creates an instance for each client on the network instantiate only when one or more clients are connected to the RTserver
6-13
Menu Commands
This section describes the menu commands of the PATROL Infrastructure KM. The functions of these menu commands are described in detail in Using the KM on page 6-21.
Table 6-3 Menu Commands (Part 1 of 2)
Menu Command
Action
PATROL7 Application Class

Administration => Identify RTserver Information Locate a Client's RTserver connection Show Current Warning Status Turn Off - Disconnect Warnings Turn On - Disconnect Warnings Debugging Utilities => RTmon Command RTmon Task Close Shared Channels Show Shared Channel Status DEBUG Flags => Show Current Flag Settings RTservers - ON RTservers - Off RTclients - ON RTclients - Off opens a dialog box that contains the current status of debugging flags turns on debugging of RTservers turns off debugging of RTservers turns on debugging of RTclients turns off debugging of RTclients opens the RTmon Command dialog box opens the RTmon Task dialog box closes all shared channels with RTservers; see To Close Shared Channels on page 6-27 for more information displays the status of shared channels opens the Add/Modify RTserver Information dialog box; see Configuring the PATROL Infrastructure KM on page 6-11 identifies the RTserver that a particular client is directly connected to opens a dialog box that indicates whether disconnect warnings are on or off turns off disconnect warnings turns on disconnect warnings
P7RTSERVERS Application Class

Remove this RTserver destroys the selected instance of P7RTSERVERS
6-14
Table 6-3
Menu Commands (Part 2 of 2)
Menu Command
Action
P7RTCLIENTS Application Class

Ping RTClient Host Machine runs a ping command against the host computer that the application instance is associated with and displays connection statistics destroys the selected instance of P7RTCLIENTS
Remove this RTclient
Parameters
This section contains detailed information about the parameters of the PATROL Infrastructure KM. Table 6-4 contains a brief description of each parameter grouped by application class:
Table 6-4 Parameter Summary by Application Class (Part 1 of 2)
Parameter
Description

P7_coll TotalConsoles collector parameter that calculates aggregated values and sets the values of the consumer parameters of this application class displays the total number of PATROL Central Microsoft Windows Edition consoles on the network This total does not include classic PATROL Consoles version 3.5 or earlier because these consoles do not communicate with RTservers. TotalConsoleServers TotalPatrolAgents TotalRTservers displays the total number of console servers on the network displays the total number of agents (version 3.5 or later) on the network displays the total number of RTservers on the network
P7_RTSERVERS Application Class

RTServer_coll collector parameter that gathers data gathers data by sending queries to RTservers, calculates aggregated values for a single RTserver, and sets the values of the consumer parameters of this application class
6-15
Table 6-4
Parameter Summary by Application Class (Part 2 of 2)
Parameter
clientdis_coll
Description
collector parameter that gathers information about the clients connected directly to a particular RTserver, creates instances of P7RTCLIENTS, and sets the value of MsgsQueued displays the number of clients that are directly connected to the RTserver that this instance of the application class represents displays the number of PATROL Central Microsoft Windows Edition consoles that are directly connected to the RTserver that this instance of the application class represents displays the number of console servers that are directly connected to the RTserver that this instance of the application class represents displays the total number of clients that have directly connected to the RTserver since initial discovery but currently are not connected displays the total number of agents that are directly connected to the RTserver that this instance of the application class represents displays the total number of queued messages for all clients that are directly connected to the RTserver that this instance of the application class represents
ClientCount ConsoleCount
ConsoleServerCount DisconnectedClients PatrolAgentCount TotalMsgsQueued
P7_RTCLIENTS Application Class

MsgsQueued displays the number of number of messages in the queue on the RTserver waiting for delivery to the client that this instance of the application class represents
6-16
Table 6-5 describes the collector parameters and their associated consumer parameters:
Table 6-5 Parameter Summary by Collector
Collector
P7_coll
Consumer
TotalRTservers TotalConsoles TotalConsoleServers TotalPatrolAgents ClientCount ConsoleCount ConsoleServerCount DisconnectedClients PatrolAgentCount TotalMsgsQueued MsgsQueued
Collector Description
aggregates all of the client counts and individual client type counts for all RTserver objects currently communicating with the PATROL environment and sets the values of the consumer parameters aggregates all of the client counts and individual client type counts for each RTserver object currently communicating with the PATROL environment and sets the values of the consumer parameters gathers information about the clients connected directly to a particular RTserver and sets the value of the consumer parameter
RTServer_coll
clientdis_coll
6-17
The following property definitions explain the meaning of each column heading in Table 6-6 on page 6-19:
Parameter Active? Type Border specifies the parameter name specifies whether the parameter is active when the application instance is created. specifies whether the parameter is a standard (std), consumer (con), or collector (coll) parameter specifies thresholds for a border range of values, if it is possible for the parameter to return a value outside of the Alarm1 range or the Alarm2 range This information is not applicable to collectors. Alarm1 Alarm2 Scheduling specifies thresholds for the first-level alarm which usually represents a warning or an alarm state specifies thresholds for the second-level alarm which usually represents a warning or alarm state specifies the time interval in the polling cycle for collectors Consumer parameters show the values that they inherit from their collector parameter. Icon Units History Level specifies which icon type the parameter uses, if it has output specifies the type of unit in which the parameter output is expressed, such as a percentage, a number, or bytes specifies the history retention period This information is not applicable to collector parameters.
Table 6-6 on page 6-19 provides default values for each parameter. If information is not applicable for a parameter, it is denoted by NA. If a parameter border or alarm range has not been set, it is denoted by the word undef (undefined) in the table.
6-18
Table 6-6
Parameter Default Values
Parameter

P7_coll TotalConsoles TotalConsoleServers TotalPatrolAgents TotalRTservers
Y Y Y Y Y coll con con con con NA undef undef undef undef NA undef 00 ALARM undef 00 ALARM NA undef 1100 OK undef 1100 OK 45 seconds 45 seconds 45 seconds 45 seconds 45 seconds NA gauge gauge gauge gauge NA number of consoles number of console servers number of PATROL Agents number of RTservers NA inherited inherited inherited inherited
P7_RTSERVERS Application Class

RTServer_coll clientdis_coll ClientCount ConsoleCount ConsoleServerCount DisconnectedClients PatrolAgentCount TotalMsgsQueued
Y Y Y Y Y Y Y Y coll coll con con con con con con NA NA 0250 OK 0100 OK 0100 OK undef 0250 OK undef NA NA 201230 WARN undef undef undef undef 3040 WARN NA NA 230250 ALARM undef undef undef undef 4050 ALARM 45 seconds 2 minutes 45 seconds 45 seconds 45 seconds 45 seconds 45 seconds 45 seconds NA NA gauge gauge gauge gauge gauge gauge NA NA number of clients number of consoles number of console servers number of clients that disconnected number of PATROL Agents number of messages in queue NA NA inherited inherited inherited inherited inherited inherited
P7_RTCLIENTS Application Class

MsgsQueued
Y con 020 OK 1015 WARN 1520 ALARM 2 minutes gauge number of messages in queue inherited
History Level
6-19
Scheduling
Active?
Alarm1
Alarm2
Border
Units
Type
Icon
InfoBoxes
Table 6-7 describes the information provided in the P7_RTCLIENTS and P7_RTSERVERS InfoBoxes:
Table 6-7 InfoBoxes
Item
Type
Description
P7RTSERVERS Application Class

Process ID RTserver Messaging Name dynamic dynamic the process ID of the client process on its host computer the PATROL object name of the RTserver corresponding to the application instance This name is formed by concatenating the host name and process ID, for example _hostname_1234.
P7RTCLIENTS Application Class

ClientType dynamic the type of client: Agent Console ConsoleServer the IP address of the client host computer the process ID of the client process on its host computer the host name of the RTserver that the client is connected to an identifier formed by concatenating host name process ID MAC address of the host IP address of the host (for example, _hostname_10385_4273b0:12.23.5.20) Note: The format of this ID may change in future releases.
IPAddress PID RTserver RTClient
dynamic dynamic dynamic dynamic
The PATROL7 application class has no customized information in its InfoBox. See Help for general information about InfoBoxes.
6-20
Using the KM
This section describes the procedures the you can perform by using the PATROL Infrastructure KM. Procedures are listed in Table 6-8:
Table 6-8 PATROL Infrastructure KM Task List
Tasks
To Identify the RTserver That a Client Is Connected To To Display Disconnect Warning Status To Turn On Disconnect Warnings To Turn Off Disconnect Warnings To Run an RTmon Command To Run an RTmon Task To Close Shared Channels To Show Shared Channel Status To Display the Status of Debug Flags To Turn Debugging On or Off To Ping an RTclient Host Computer To Remove an Inactive Instance of P7RTSERVERS To Remove an Inactive Instance of P7RTCLIENTS
Page
6-21 6-23 6-23 6-23 6-23 6-27 6-27 6-28 6-28 6-28 6-29 6-30 6-30
Before you Begin
The PATROL Infrastructure KM must be installed and configured. You must have a PATROL Console running or a connection to a PATROL Central Web Edition Web server.
To Identify the RTserver That a Client Is Connected To Step 1
Run the menu command Locate a Clients RTserver connection of the PATROL7 application. The Locate the RTserver dialog box opens as shown in Figure 6-3 on page 6-22:
6-21
Figure 6-3
Locate RTserver Dialog Box
Step 2
Enter the host name of the client that you want to locate, in the form by which it is known to PATROL. This name is the label of the computer icon in the console and is the value of the hostname variable in the agent namespace on the host computer.
Step 3
Select a client object type and click Apply. The dialog box closes and a results dialog box opens, as shown in Figure 6-4:
Figure 6-4 Locate RTserver Results Dialog Box
Step 4
Click OK to close the dialog box.
6-22
To Display Disconnect Warning Status Step 1
Run the menu command Show Current Warning Status of the PATROL7 application. A dialog box containing the disconnect warning status (on or off) appears.
Step 2
To Turn On Disconnect Warnings Step 1
Run the menu command Turn On - Disconnect Warnings of the PATROL7 application. Warnings are turned on and a confirmation dialog box appears.
Step 2
To Turn Off Disconnect Warnings Step 1
Run the menu command Turn Off - Disconnect Warnings of the PATROL7 application. Warnings are turned off and a confirmation dialog box appears.
Step 2
To Run an RTmon Command Step 1
Run the menu command Debugging Utilities => RTmon Command of the PATROL7 application. The RTmon Command dialog box opens as shown in Figure 6-5 on page 6-24.
6-23
Figure 6-5
RTmon Command Dialog Box
Note
This dialog box is a common PATROL component. The lower box has functions such as Check PSL which are not used when entering an RTmon command or task.
Step 2
Table 6-9
Enter one of the commands listed in Table 6-9 and click Apply.
RTmon Command Options (Part 1 of 3)
Command
poll poll client_buffer client
Function
makes a single request for information from an RTserver or client; add one of the following command options: polls the named client for buffer information RTserver and client names used in these commands must be in the form obtained from the InfoBoxes described on page 6-20. Note: RTserver and client names have different formats.
poll client_cb client poll client_general client poll client_msg_traffic client poll client_msg_type client msg_type poll client_names
polls the named client for callback information polls the named client for general information polls the named client for message traffic information polls the named client for message type information polls the RTserver for client process names
6-24
Table 6-9
Command
poll client_option client option poll client_subject client subject poll client_subscribe client poll client_time client poll project_names poll server_buffer server process poll server_conn poll server_general server poll server_msg_traffic server process poll server_names poll server_option server option poll server_route server dest_server poll server_time server poll subject_names poll subject_subscribe subject watch
Function
polls the named client for option information polls the named client for subject information polls the RTserver for the subjects that the named client is subscribing to polls the named client for time information polls the RTserver for project names polls the named server for information on its buffer to the named process polls the RTserver for connection information about all RTservers polls the named server for general information polls the named server for message traffic information on the named process polls the RTserver for RTserver process names polls the named server for option information polls the named server for route information polls the named server for time information polls the RTserver for subject names polls the RTserver for the client processes that are subscribing to the named subject begins monitoring information continuously The watch command with no options displays all categories that are currently being watched.
watch client_buffer client watch client_msg_recv client msg_type watch client_msg_send client msg_type watch client_names watch client_subscribe client watch client_time client
watches buffer information in the named client watches for messages of the named type being received by the named client watches for messages of the named type being sent by the named client watches client process names watches the subjects that the named client is subscribing to watches time in the named client
6-25
Table 6-9
Command
watch project_names watch server_conn watch server_names watch subject_names watch subject_subscribe subject unwatch options
Function
watches project names watches connection information about all RTservers watches RTserver process names watches subject names watches the client process that are subscribing to the named subject stops watching the named category The unwatch command takes the same command-line options as the watch command.
The command is executed and the dialog box closes. Output similar to the following example appears in the System Output window. This is the output of the command poll server_conn:
POLL> Server Conns: server1 = /_houperfms010.bmc.com_4438, server2 = /_houperfms084_2440 conn name = /_houperfms084_2440, weight = 1 server1 = /_houperfms010.bmc.com_4438, server2 = /_houperfms083_2148 conn name = /_houperfms083_2148, weight = 1 server1 = /_houperfms010.bmc.com_4438, server2 = /_houperfms088_2008 conn name = /_houperfms088_2008, weight = 1 server1 = /_houperfms010.bmc.com_4438, server2 = /_walperfsun04_9566 conn name = /_walperfsun04_9566, weight = 1 server1 = /_houperfms010.bmc.com_4438, server2 = /_houperfsun02_5422 conn name = /_houperfsun02_5422, weight = 1 server1 = /_houperfms010.bmc.com_4438, server2 = /_houperfsun01_481 conn name = /_houperfsun01_481, weight = 1 server1 = /_houperfms010.bmc.com_4438, server2 = /_houperfms030_2404 conn name = /_houperfms030_2404, weight = 1 server1 = /_HOUPERFMS001_3168, server2 = /_houperfms010.bmc.com_4438 conn name = /_HOUPERFMS001_3168, weight = 1 Processed a mon_server_conn_poll_result message. This process is now exiting.
6-26
To Run an RTmon Task
This procedure is identical to running an RTmon command, except that the output appears in a separate window and can be saved to a file.
Step 1
Run the menu command Debugging Utilities => RTmon Task of the PATROL7 application. The RTmon Task dialog box opens, as shown in Figure 6-6:
Figure 6-6 RTmon Task Dialog Box
Step 2
Continue with Step 2 on page 6-24. The output of an RTmon task appears in a separate window instead of the System Output window of the host computer.
To Close Shared Channels
A shared channel is a process that communicates between the PATROL Infrastructure KM and the RTserver. This process can hang up or freeze. You can troubleshoot this problem by closing all shared channels. New channels will be created as required.
Run the menu command Debugging Utilities => Close Shared Channels of
the PATROL7 application. All shared channels are closed.
6-27
To Show Shared Channel Status
Run the menu command Debugging Utilities => Show Shared Channel
Status of the PATROL7 application.
A list of shared channels similar to the following example appears in the System Output window:
20020717130423 houperfms014.bmc.com OPEN 2268 PIPE SHARED 25 clientDis_coll -1 <NONE> 20020717130423 houperfsun01 OPEN 2588 PIPE SHARED 19 clientDis_coll -1 <NONE> 20020717130423 logd_chan OPEN 2496 PIPE SHARED -1 <NONE> -1 <NONE> 20020717130423 houperfms088 OPEN 2336 PIPE SHARED 27 clientDis_coll -1 <NONE> 20020717130423 tbrady2w2k OPEN 828 PIPE SHARED 31 clientDis_coll -1 <NONE> 20020717130423 houperfms083 OPEN 932 PIPE SHARED 29 clientDis_coll -1 <NONE>
To Display the Status of Debug Flags Step 1
Run the menu command Debugging Utilities => DEBUG Flags => Show Current Flag Settings of the PATROL7 application. A dialog box displaying the settings opens.
Step 2
To Turn Debugging On or Off
Run the appropriate menu command of the PATROL7 application:

Debugging Utilities => DEBUG Flags => RTservers - ON Debugging Utilities => DEBUG Flags => RTservers - Off Debugging Utilities => DEBUG Flags => RTclients - ON Debugging Utilities => DEBUG Flags => RTlclients - Off
6-28
The flag is set. When debugging is on, messages appear in the System Output window.
To Ping an RTclient Host Computer Step 1
Run the menu command Debugging => Ping RTClient Host Machine of the P7_RTCLIENTS application instance corresponding to the computer that you want to ping. The KM runs the ping command against the computer and displays the results in the Ping dialog box, as shown in Figure 6-7:
Figure 6-7 Ping Dialog Box
Step 2
6-29
To Remove an Inactive Instance of P7RTSERVERS
When an RTserver has disconnected and you know that it will not reconnect, you can remove the corresponding instance of P7RTSERVERS:
Run the menu command Remove this RTserver of the instance of

P7RTSERVERS that you want to remove. The instance is destroyed and an event is generated: State Change: OK OFFLINE Update status for instance P7_RTSERVERS.RTserverName. Reason: Manual remove requested. The following exceptions can occur: If the instance is active and has children (instances of P7RTCLIENTS), you cannot remove it. If the instance is active and has no children, you will receive a confirmation dialog box.
To Remove an Inactive Instance of P7RTCLIENTS
When a client has disconnected and you know that it will not reconnect, you can remove the corresponding instance of P7RTCLIENTS:
Run the menu command Remove this RTclient of the instance of

P7RTCLIENTS that you want to remove. The instance is destroyed and an event is generated: State Change: OK OFFLINE Update status for instance P7_RTCLIENTS.RTclientName. Reason: Manual remove requested. The following exception can occur: If the instance is active you will receive a confirmation dialog box.
6-30
Troubleshooting
Table 6-10 lists symptoms of problems that can occur and their causes and resolutions:
Table 6-10 Troubleshooting (Part 1 of 2)
Symptom
PATROL7 does not instantiate. P7_RTSERVERS does not instantiate.
Cause
The PATROL7 KM is not loaded on the agent. The RTserver specified in the Add/Remove RTserver Information dialog box is not running or cannot be reached.
Resolution
Install the KM on the agent and confirm that it is loaded. Confirm that the host name, port number, and protocol are correct. Confirm that you can reach the host by using the ping command. Confirm that the RTserver is running; see PATROL Console Server and RTserver Getting Started. Try a different RTserver. This is the expected behavior of this KM when no clients are directly connected to the RTserver. Expand the KM hierarchy to locate the source of the alarm, then investigate the source.
P7_RTCLIENTS does not instantiate. PATROL7 is in alarm.
No clients are directly connected to the RTserver. One of the parameters of PATROL7 is in alarm or the state has propagated from an application instance that is lower in the hierarchy. No console servers are connected to the network. No RTservers are running.
TotalConsoleServers is in alarm. TotalRTservers is in alarm. P7_RTSERVERS is in alarm.
Determine why console servers are not running; see PATROL Console Server and RTserver Getting Started. Determine why RTservers are not running; see PATROL Console Server and RTserver Getting Started. Expand the KM hierarchy to locate the source of the alarm, then investigate the source.
One of the parameters of P7_RTSERVERS is in alarm or the state has propagated from an application instance that is lower in the hierarchy.
6-31
Table 6-10
Troubleshooting (Part 2 of 2)
Symptom
P7_RTSERVERS is in alarm (continued).
Cause
The RTserver represented by this application instance has disconnected from the network.
Resolution
Confirm that the RTserver has disconnected by examining the event log. Investigate why the RTserver disconnected. Run the Remove this RTserver command to destroy the instance. Refer to page 6-30. Determine whether the number of messages is excessive. If the number of messages is acceptable, increase the alarm limits. Check DisconnectedClients to see if the queued messages are for a client that has disconnected. Determine whether the number of clients is excessive. If the number of clients is acceptable, increase the alarm limits. Raise the limit of the RTserver; see PATROL Console Server and RTserver Getting Started. Install another RTserver. Redirect some clients to other RTservers to balance the load. Confirm that the client has disconnected by examining the event log. Investigate why client disconnected. Run the Remove this RTclient command to destroy the instance. Refer to page 6-30. Investigate why MsgsQueued is in alarm. Determine whether the number of messages is excessive. If the number of messages is acceptable, increase the alarm limits.
TotalMsgsQueued is in alarm.
The number of messages in the queue is above the limits set in the parameter.
ClientCount is in the WARNING state.
The number of clients connected to the RTserver exceeds the Alarm1 limit set in the parameter. The number of clients connected to the RTserver is near the upper limit allowed (default value 250).
ClientCount is in the ALARM state.
P7_RTCLIENTS is in alarm.
The client represented by this application instance has disconnected.
MsgsQueued is in alarm. MsgsQueued is in alarm. The number of messages in the queue for this client is above the limits set in the parameter.
6-32
Worksheets and Checklists
This appendix contains worksheets and checklists for planning and installing PATROL 7.x infrastructure components. This appendix contains the following worksheets and checklists: Enterprise Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location Mapping Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . Detailed Location Information Worksheet. . . . . . . . . . . . . . . . . Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Console Server and RTserver Checklist . . . . . . . . . . . A-2 A-3 A-4 A-5 A-6
A-1
Enterprise Worksheets
The following worksheets are to help you examine, arrange, and gather information about your enterprise. This section contains the following enterprise worksheets: Location Mapping Worksheet Detailed Location Information Worksheet
Reproduce the worksheets as needed to define all the locations in your enterprise.
A-2
Location Mapping Worksheet

Name Description Type
physical logical physical logical physical logical physical logical physical logical physical logical physical logical physical logical physical logical physical logical physical logical physical logical
Function
managed management both managed management both managed management both managed management both managed management both managed management both managed management both managed management both managed management both managed management both managed management both managed management both
Firewall
Yes No Yes No Yes No Yes No Yes No Yes No Yes No Yes No Yes No Yes No Yes No Yes No
A-3
Detailed Location Information Worksheet

Location Name:
How many Managed Systems are Present? Additional RTserver services desired? Are PATROL Consoles needed for this location? Number of PATROL Central Windows Edition consoles required? yes / no yes / no Windows Console users hostnames
Number of concurrent users to monitor using a Web browser? What Other Systems can Host Common Services Components? hostnames of available systems
A-4
Installation Requirements
To help you ensure that your systems meet the minimum requirements of the PATROL components, you should review the installation requirements for each component. The following table provides a reference to the installation requirements for PATROL components.
Component
Console Server RTserver PATROL Central Microsoft Windows Edition PATROL Central Web Edition PATROL Classic Console PATROL Agent
Installation Requirements
See PATROL Console Server and RTserver Checklist on page A-6 See PATROL Console Server and RTserver Checklist on page A-6 See PATROL Central Operator Microsoft Windows Edition Getting Started See PATROL Central Operator Web Edition Getting Started See the PATROL Console for Microsoft Windows and PATROL Console for Unix Release Notes See the PATROL Agent Reference Manual
A-5
PATROL Console Server and RTserver Checklist

You should review the information listed in this checklist before installing PATROL Console Servers or RTservers. The requirements in this checklist are based on best practices developed by BMC Software through product scalability testing of our products. The hosting resource requirements can be affected by the following factors: number of managed systems (agent nodes) number objects being monitored on each system (parameters, applications, and instances) number of consoles connected console activity Heavy console activity can put a greater load on the RTserver and the console server connections.
Description
The name of the system where you will install the RTserver and console server components.
Item
Computer Name
Value
Component Role of Computer Location of Computer Hardware Requirements
PATROL Console Server and RTserver

Should only be installed on a computer that serves as a Common Services System Where is the computer located? The network location of the Computer Minimum 800Mhz processor 1Gb Memory 200 Mb of disk space Recommended (processor) Solaris UltraSPARC 220R@450/02 or Dual Processor Intel Pentium III 800 Mhz
A-6
Item
Operating System
Description
Recommended Solaris v.6, 7, 8 Windows NT, W2K, XP Linux 4.2.x Supported Solaris v.6, 7, 8 Windows NT, W2K, XP Linux 4.2.x
Value
User Accounts
PATROL components required an identified account at installation time.
User Name
Password Have you set up the account and password? You must do this before the installation. Permissions/ Privileges Dependency on Configuration Information Certain environments require root privilege when installing to Unix. A PATROL Console Server requires a valid connection to an RTserver. During the installation you will be prompted to enter a lookup variable value similar to the following value: tcp:hostname:2059 See the PATROL Infrastructure Planner Report for details prior to installing Console Servers. Recommended Port Number TCP or UDP Deployment Mechanism 2059 TCP Writing the password here is not recommended.
Network Requirements
Select one of the following installation types: Local Install Installable Image Other
A-7
Item
Security
Description
If you are implementing a security level greater than the Basic PATROL Security, review the PATROL Security Users Guide before installing your PATROL components. Select one of the following security levels: Basic 1 2 3 4 Windows: Unix:
Value
Installation Directory
A-8
Glossary
1 1Review copyRrr
Glossary
Note: In this glossary, the names of all Microsoft Windows products are referred to as Microsoft Windows or simply Windows. No distinctions are made between various Windows Servers, Windows 2000, and Windows NT.
access control list
A list that is set up by using a PATROL Agent configuration variable and that restricts PATROL Console access to a PATROL Agent. A PATROL Console can be assigned access rights to perform console, agent configuration, or event manager activities. The console server uses access control lists to restrict access to objects in the COS namespace. See PATROL Agent namespace. A PATROL Console feature that constructs SQL-like statements for querying PATROL Agents connected to the console. Agent Query produces a tabular report that contains information about requested objects and can be used to perform object management activities, such as disconnecting and reconnecting computers. Queries can be saved, reissued, added, or changed. PATROL offers built-in queries in the Quick Query command on the Tools menu from the PATROL Console main menu bar. See also Quick Query.
agent namespace Agent Query
Glossary
alarm
An indication that a parameter for an object has returned a value within the alarm range or that application discovery has discovered that a file or process is missing since the last application check. An alarm state for an object can be indicated by a flashing icon, depending on the configuration of a console preference. See also warning. A range of values that serve as thresholds for a warning state or an alarm state. Alert range values cannot fall outside of set border range values. See also border action, border range, and recovery action. The highest-level computer class in PATROL. Attributes assigned to this class will be inherited by all computer classes known to PATROL. See also class and computer class. A specially marked point on a parameter graph that provides detailed information about a parameter at a particular moment. The associated data is accessed by double-clicking the data point, which is represented by a user-specified character (the default is an asterisk) in PATROL 3.x and earlier or by a set bitmap in PATROL Central 7.x. See also parameter. An account that you define at KM setup and that you can change for an application class or instance. An application account is commonly used to connect to an RDBMS on a server where the database resides or to run SQL commands. The interval at which application discovery occurs. The PATROL Agent process cache (as opposed to the system process table) is checked to ensure that all application instances and files previously discovered still exist there. See also application discovery, application discovery rules, prediscovery, process cache refresh, PSL discovery, and simple discovery. The object class to which an application instance belongs; also, the representation of the class as a container (Unix) or folder (Windows) on the PATROL Console. You can use the developer functionality of a PATROL Console to add or change application classes. See also class.
alert range
ALL_COMPUTERS class
annotated data point
application account
application check cycle
application class
application discovery
A PATROL Agent procedure carried out at preset intervals on each monitored computer to discover application instances. When an instance is discovered, an icon appears on the PATROL interface. The application class includes rules for discovering processes and files by using simple process and file matching or PSL commands. Application definition information is checked against the information in the PATROL Agent process cache, which is periodically updated. Each time the PATROL Agent process cache is refreshed, application discovery is triggered. See also application check cycle, application discovery rules, PATROL Agent process cache, prediscovery, PSL discovery, and simple discovery. A set of rules stored by the PATROL Agent and periodically evaluated to find out whether a specific instance of an application class exists in the monitored environment. The rules describe how a PATROL Agent can detect instances of the application on a computer. There are two types of application discovery: simple and PSL; PSL discovery can include prediscovery rules as well as discovery rules. See also application check cycle, application discovery, prediscovery, PSL discovery, and simple discovery. A feature used from the PATROL Console to hide all instances of selected application classes for a particular computer. The PATROL Agent continues to monitor the application instances by running parameter commands and recovery actions. A system resource that is discovered by PATROL and that contains the information and attributes of the application class that it belongs to. See also application class and instance. The condition of an application class or an application instance. The most common application states are OK, warning, and alarm. An application class or instance icon can also show additional conditions. See also computer state and parameter state.
application discovery rules
application filter
application instance
application state
Glossary
attribute
A characteristic that is assigned to a PATROL object (computer class, computer instance, application class, application instance, or parameter) and that you can use to monitor and manage that object. Computers and applications can have attributes such as command type, parameter, menu command, InfoBox command, PATROL setup command, state change action, or environment variable. Parameters can have attributes such as scheduling, command type, and thresholds. An attribute can be defined globally for all instances of a class or locally for a particular computer or application instance. An instance inherits attributes from a class; however, an attribute defined at the instance level overrides inherited attributes. See also global level and local level.
border action
A command or recovery action associated with a parameter border range and initiated when that range has been breached. Border actions can be initiated immediately when the parameter returns a value outside the border range, after a warning or alarm has occurred a specified number of times, or after all other recovery actions have failed. See also border range. A range of values that serve as thresholds for a third-level alert condition when it is possible for a parameter to return a value outside of the alarm range limits. When a border range is breached, border actions can be initiated. See also border action. An internal command available from the PATROL Agent that monitors and manages functions such as resetting the state of an object, refreshing parameters, and echoing text. The command is identified by the naming convention %command_name. See also built-in macro variable. An internal variable created and maintained by PATROL for use in built-in commands and PSL. The naming convention for the variable is %{variable_name}. See also built-in command. A plot of parameter data values made by the PATROL Console Charting Server. See also multigraph container and PATROL Console Charting Server.
border range
built-in command
built-in macro variable
chart
charting server class
See PATROL Console Charting Server. The object classification in PATROL where global attributes can be defined; the attributes are then inherited by instances of the class. An instance belongs to a computer class or an application class. See also application class, computer class, and event class. A type of parameter that contains instructions for gathering values for consumer parameters to display. A collector parameter does not display any value, issue alarms, or launch recovery actions. See also consumer parameter, parameter, and standard parameter. An option for starting a PATROL Agent or a PATROL Console at the operating system command line. PATROL Agent arguments include names of KMs to load and port numbers for agent-console connection. PATROL Console arguments include connection mode (developer or operator), user ID to start the PATROL Console, names of KMs to load, and names of the files to use. See PATROL Command Line Interface (CLI). The component that provides basic text editing functions for a PATROL Console. It is commonly used to add or change commands (menu commands, parameter data collection and recovery actions, InfoBox commands, setup commands, and state change actions). The designation assigned to a command according to its manner of execution. This attribute must be defined for a parameter command, a parameter recovery action, a menu command, an InfoBox command, a setup command, or a state change action. The PATROL Agent provides two command types: operating system (OS) and PSL. PATROL KMs provide additional command types. The developer functionality of a PATROL Console can be used to add or change command types.
collector parameter
command line argument
command line interface command text editor
command type
Glossary
commit
The process of saving to PATROL Agent computers the changes that have been made to a KM by using a PATROL Console. A PATROL user can disable a PATROL Consoles ability to commit KM changes. A computer that processes data from managed systems and facilitates communications between managed systems and console systems. See also console system and managed system. The basic object class to which computer instances of the same type belong. Examples include Solaris, OSF1, HP, and RS6000. PATROL provides computer classes for all supported computers and operating systems; a PATROL Console with developer functionality can add or change computer classes. A computer that is running in an environment managed by PATROL and that is represented by an icon on the PATROL interface. A computer instance contains the information and attributes of the computer class that it belongs to. See also instance. The condition of a computer. The main computer states are OK, warning, and alarm. A computer icon can show additional conditions that include no output messages pending, output messages pending, void because a connection cannot be established, and void because a connection was previously established but now is broken. See also state. See KM configuration file. See PATROL Agent configuration file. The mode in which the PATROL Console is connected to the PATROL Agent. The mode can be developer or operator and is a property of the Add Host dialog box (PATROL 3.x and earlier), an Add Managed System wizard, or other connecting method. The connection mode is a global (console-wide) property that can be overridden for a computer instance. See also PATROL Console.
common service
computer class
computer instance
computer state
configuration file, KM configuration file, PATROL Agent connection mode
console module
A program that extends the functionality of PATROL Central. Console modules can collect data, subscribe to events, access Knowledge Module functions, authenticate users, and perform security-related functions. A server through which PATROL Central communicates with managed systems. A console server handles requests, events, data, communications, views, customizations, and security. A computer that hosts user desktop applications, such as consoles, viewers, and Web browsers. See also common service and managed system. A type of parameter that displays a value that was gathered by a collector parameter. A consumer parameter never issues commands and is not scheduled for execution; however, it has alarm definitions and can run recovery actions. See also collector parameter, parameter, and standard parameter. A custom object that you can create to hold any other objects that you selectsuch as computers, applications, and parametersin a distributed environment. In Windows, a container is referred to as a folder. You can drag and drop an object into and out of a container icon. However, objects from one computer cannot be dropped inside another computer. Once a container is defined, the object hierarchy applies at each level of the container. That is, a container icon found within a container icon assumes the variable settings of the container in which it is displayed. See also object hierarchy and PATROL Console Charting Server. To modify properties or attributes locally or globally. See also global level and local level. See override a parameter. A grid-like view that can be created in PATROL Central to show user-selected information.
console server
console system
consumer parameter
container
customize a KM
customize a parameter custom view
Glossary
deactivate a parameter
To stop running a parameter for selected computer or application instances. In PATROL Consoles for Microsoft Windows environments, deactivating a parameter stops parameter commands and recovery actions and deletes the parameter icon from the application instance window without deleting the parameter definition in the KM tree. A deactivated parameter can be reactivated at any time. See also snooze an alarm and suspend a parameter. To stop monitoring an application class and all of its instances on selected computer instances. In PATROL Consoles for Microsoft Windows environments, deactivating an application class deletes the application class and all of its instance icons from the computer window without deleting the application class or definition in the KM tree. A deactivated application class can be reactivated at any time. See also application filter and deactivate a parameter. In PATROL 3.x and earlier, a A file that stores your desktop layout, the computers that you monitor, the KMs that you loaded, and your PATROL Console user accounts for monitored objects. You can create multiple desktop files for any number of PATROL Consoles. By default, desktop files always have a .dt extension. Desktop files are replaced by management profiles in PATROL 7.x. See also desktop template file. In PATROL 3.x and earlier, a A file that stores information about the desktop setup of one computer. You can create multiple desktop template files for any number of PATROL Consoles. Each PATROL Console user can apply a template to selected computers on the desktop. By default, desktop template files always have a .dtm extension. See also desktop file. A feature of PATROL for Microsoft Windows only. One of the views of folders available with PATROL for Microsoft Windows environments, the Desktop tree displays the object hierarchy. See also KM tree.
deactivate an application class
desktop file
desktop template file
Desktop tree
developer mode
An operational mode of the PATROL Console that can be used to monitor and manage computer instances and application instances and to customize, create, and delete locally loaded Knowledge Modules and commit these changes to selected PATROL Agent computers. See also PATROL Console. To temporarily or permanently block an application or KM from loading and to block the PATROL Agent from using that KM. When a KM is disabled (added to the disabled list) in the agent configuration file, the KM files are not deleted from the PATROL Agent computers, but the PATROL Agent stops using the KM to collect parameter data and run recovery actions. The default is that no KMs are disabled. Most KMs are composed of individual application files with a .km extension. See also preloaded KM, static KM, and unload a KM. See application discovery. A CD or tape that contains a copy of one or more BMC Software products and includes software and documentation (user guides and online help systems). A variable used to specify settings, such as the program search path for the environment in which PATROL runs. You can set environment variables for computer classes, computer instances, application classes, application instances, and parameters. The occurrence of a change, such as the appearance of a task icon, the launch of a recovery action, the connection of a console to an agent, or a state change in a monitored object (computer class, computer instance, application class, application instance, or parameter). Events are captured by the PATROL Agent, stored in an event repository file, and forwarded to an event manager (PEM) if an event manager is connected. The types of events forwarded by the agent are governed by a persistent filter for each event manager connected to a PATROL Agent. A command that is triggered by the PATROL Agent when an event is acknowledged in an event manager (PEM). See also event escalation command and event notification command.
disable an application, disable a KM
discovery distribution CD or tape
environment variable
event
event acknowledgment command
Glossary
event catalog
A collection of event classes associated with a particular application. PATROL provides a Standard Event Catalog that contains predefined Standard Event Classes for all computer classes and application classes. You can add, customize, and delete an application event catalog only from a PATROL Console in the developer mode. See also event class and Standard Event Catalog. A category of events that you can create according to how you want the events to be handled by an event manager and what actions you want to be taken when the event occurs. Event classes are stored in event catalogs and can be added, modified, or deleted only from a PATROL Console in the developer mode. PATROL provides a number of event classes in the Standard Event Catalog, such as worst application and registered application. See also event catalog and Standard Event Catalog. A command that is run by the PATROL Agent when certain events occur and that is used in conjunction with an event manager (PEM). The commands are specified for the event class that the event is associated with. A command can be one of three types: escalation, notification, or acknowledgment. See also event acknowledgment command, event escalation command, and event notification command. The part of an event manager (PEM) where you can store or change comments about any event in the event log. You can enter commands at any time from the PATROL Event Manager Details window. A command that is triggered by the PATROL Agent when an event is not acknowledged, closed, or deleted within an event manager (PEM) by the end of the escalation period. See also event acknowledgment command, event escalation period, and event notification command.
event class
event class command
Event Diary
event escalation command
10
event escalation period
A period during which the severity of an event is increased as a result of the events persistence. Escalation actions are part of escalation command definitions for event classes and can be triggered only by the PATROL Agent. See also event escalation command. A circular file where events are stored by the PATROL Agent and accessed by an event manager, such as the PEM. The file resides on the PATROL Agent computer and retains a limited number of events. When the maximum number of events is reached and a new event is stored, the oldest event is removed in a cyclical fashion. See also parameter history repository. A graphical user interface for monitoring and managing events. The event manager can be used with or without the PATROL Console. See also PATROL Event Manager (PEM). A command that is triggered by the PATROL Agent when an event is logged into an event manager (PEM). See also event acknowledgment command and event escalation command. The PATROL-provided category for an event according to a filtering mechanism in an event manager. Event types include information, state change, error, warning, alarm, and response. See view filter. A kind of scheduling that starts a parameter when certain conditions are met. See also periodic scheduling. Comments about or instructions for dealing with PATROL events as reported by the agent. Expert advice is defined in the Event Properties dialog box in a PATROL Console in the developer mode. PATROL Consoles in an operator mode view expert advice in the PATROL Event Manager. See application filter. See view filter.
event history repository
event manager
event notification command
event type
event view filter event-driven scheduling expert advice
filter, application filter, event view
Glossary
11
filter, persistent global channel
See persistent filter. A single dedicated connection through which PATROL monitors and manages a specific program or operating system. The PATROL Agent maintains this connection to minimize the consumption of program or operating system resources. In PATROL hierarchy, the level at which object properties and attributes are defined for all instances of an object or class. An object at the local level inherits characteristics (properties) and attributes from the global level. See also local level. A periodic message sent between communicating objects to inform each object that the other is still alive. For example, the PATROL Console checks to see whether the PATROL Agent is still running. The interval (in seconds) at which heartbeat messages are sent. The longer the interval, the lower the network traffic. See also message retries, message time-out, and reconnect polling. Parameter and event values that are collected and stored on each monitored computer. Parameter values are stored in binary files for a specified period of time; events are stored in circular log files until the maximum size is reached. The size and location of parameter history files are specified through either the PATROL Console or the PATROL Agent; size and location of event history files are specified through an event manager, such as the PEM, or the PATROL Agent. A binary file in which parameter values (except those that are displayed as text) are stored by the PATROL Agent and accessed by the PATROL Console for a specified number of days (the default is one day). When the number of storage days is reached, those values are removed in a cyclical fashion.
global level
heartbeat
heartbeat interval
history
history repository
12
history retention level
The specified level (global or local) where the parameter history retention period for an object is set. The period can be inherited from the next higher level in the object hierarchy or set at the local level. If the history retention level is local, the number of days that history is stored (retention period) must be set. See also history retention period. The number of days that parameter values are stored in the history database before they are automatically purged by PATROL. The period can be specified at the class (global) or instance (local) level. History retention can be set for all parameters of a computer class, a computer instance, an application class, or an application instance. History for an individual parameter on an application instance can be manually cleared at any time by using a PATROL Console. See also history retention level. The combined settings for a parameters history retention level and history retention period. See also history retention level and history retention period. A dialog box that contains a static list of fields and displays current information about an object, such as the version number of an RDBMS and whether the object is online or offline. Commands are run when the InfoBox is opened. Information can be manually updated if the InfoBox remains open for a period of time. PATROL provides a number of commands for obtaining and displaying object information in an InfoBox. Only a PATROL Console in the developer mode can be used to add or change commands. Any event that is not a state change or an error. Typical information events occur when a parameter is activated or deactivated, a parameter is suspended or resumed, or application discovery is run. The default setting for PATROL is to prevent this type of event from being stored in the event repository. To store and display this type of event, you must modify the persistent filter setting in the PATROL Agent configuration file.
history retention period
history span
InfoBox
information event
Glossary
13
instance
A computer or discovered application that is running in an environment managed by PATROL. An instance has all the attributes of the class that it belongs to. A computer instance is a monitored computer that has been added to the PATROL Console. An application instance is discovered by PATROL. See also application discovery, application instance, and computer instance. See Knowledge Module (KM). A file in which the characteristics of a KM are defined through KM menu commands during KM installation and setup (if setup is required). See also Knowledge Module (KM) and PATROL Agent configuration file. A list of KMs used by a PATROL Agent or PATROL Console. See also Knowledge Module (KM). See PATROL KM Migrator. See also Knowledge Module (KM). See Knowledge Module package. A feature of PATROL for Microsoft Windows only. One of two views of folders available in Windows. The KM tree displays computer classes, application classes, and their customized instances in the knowledge hierarchy and also displays the Standard Event Catalog. A PATROL Console in operator mode can only view the KM tree; only a PATROL Console in the developer mode can change KM properties and attributes. See also Desktop tree and Knowledge Module (KM). The rules by which objects inherit or are assigned attributes. (In PATROL Consoles for Microsoft Windows environments, classes of objects are represented in the Computer Classes and Application Classes sets of folders on the KM tree.) Properties and attributes of a customized instance override those defined for the class to which the instance belongs.
KM KM configuration file
KM list
KM Migrator KM package KM tree
knowledge hierarchy
14
Knowledge Module (KM)
A set of files from which a PATROL Agent receives information about resources running on a monitored computer. A KM file can contain the actual instructions for monitoring objects or simply a list of KMs to load. KMs are loaded by a PATROL Agent and a PATROL Console. KMs provide information for the way monitored computers are represented in the PATROL interface, for the discovery of application instances and the way they are represented, for parameters that are run under those applications, and for the options available on object pop-up menus. A PATROL Console in the developer mode can change KM knowledge for its current session, save knowledge for all of its future sessions, and commit KM changes to specified PATROL Agent computers. See also commit, KM configuration file, KM list, KM Migrator, KM tree, load KMs, and version arbitration.
Knowledge Module package
A package of PATROL KM files that can be distributed by an installation program or stored in and distributed by the PATROL KMDS. The package file has a .pkg file extension. KM packages are created by using a PATROL Console in the developer mode. See also Knowledge Module (KM), PATROL Console, PATROL Knowledge Module Deployment Server (PATROL KMDS), and PATROL Knowledge Module Deployment Server Manager (PATROL KMDS Manager). Same as load KMs. Most KMs are composed of application files with a .km extension. To place KM files into memory for execution. After configuration and during startup, the PATROL Agent loads the KM files that are listed in its configuration file and that reside on the PATROL Agent computer. When a PATROL Console connects to the PATROL Agent, the KM versions that the agent executes depend on whether the console has developer or operator functionality. See also Knowledge Module (KM) and version arbitration. The history (stored parameter values) for an object or instance. See also global level and local level.
load applications
load KMs
local history
Glossary
15
local history retention period local level
The length of time set by the user during which stored parameter values for an object or instance are retained. In PATROL hierarchy, the level of a computer instance or an application instance. An object (instance) at the local level inherits properties and attributes that are defined globally. When properties and attributes are customized locally for an individual instance, they override inherited attributes. See also global level. Any object that PATROL manages. See object. A systemusually a computer on which a PATROL Agent is runningthat is added (connected) to a PATROL Console to be monitored and managed by PATROL and that is represented by an icon on the PATROL interface. A system with resources that are managed or monitored by a BMC Software product, such as a computer on which a PATROL Agent is running. See also console system and common service.
managed object managed system
management profile
A user profile for PATROL Central that is stored by the console server. A management profile is similar to a session file and contains information about custom views, your current view of the PATROL environment, information about systems that you are currently managing, Knowledge Module information, and console layout information for PATROL Central. Management profiles replace desktop files and session files that were used in PATROL 3.x and earlier. See PATROL SNMP Master Agent. A feature of UDP only. The number of times that the PATROL Console will resend a message to the PATROL Agent. The greater the number of message retries, the more time the PATROL Console will give the PATROL Agent to respond before deciding that the agent connection is down and timing out. The number of message retries multiplied by message time-out (in seconds) is the approximate time allowed for a connection verification. See also heartbeat, heartbeat interval, message time-out, and reconnect polling.
master agent message retries
16
message time-out
A feature of UDP only. The time interval (in seconds) that the PATROL Console will give the PATROL Agent to respond to a connection verification before deciding that the Agent connection is down. The number of message retries multiplied by message time-out is the approximate time allowed for a connection verification. See also heartbeat, heartbeat interval, message retries, and reconnect polling. A window that displays command output and error messages from the PATROL Console graphical user interface. See also response window, system output window, and task output window. A custom object into which you can drop parameter objects to be plotted as charts. See also PATROL Console Charting Server. A computer class, computer instance, application class, application instance, parameter, or container (folder) in an environment managed by PATROL. Objects have properties and are assigned attributes (command types, parameters, menu commands, InfoBox commands, setup commands, state change actions, and environment variables). Parameter objects use data collection commands to obtain values from classes and instances. See also object class, object hierarchy, object icon, and object window. A computer class or application class. See also class, object, and object hierarchy. The structure of object levels in PATROL. On the PATROL interface, computers contain application folders (containers) representing a loaded KM, application folders contain one or more application instances, and application instances contain parameters. A graphic that represents a computer instance, application class, application instance, parameter, or container (folder) in an environment managed by PATROL. See also object, object hierarchy, and object window.
message window
multigraph container
object
object class
object hierarchy
object icon
Glossary
17
object window
An open object container (folder) that may contain application class icons, application instance icons, parameter icons, custom containers (folders), and shortcuts. The object window is displayed when you double-click the object icon. See also application instance, computer instance, object, and object icon. An operational mode of the PATROL Console that can be used to monitor and manage computer instances and application instances but not to customize or create KMs, commands, and parameters. See also PATROL Console. An account that is set up at installation to grant the PATROL Agent access to a computer. Operating system commands executed by the PATROL Agent and PATROL Console use this account. The PATROL Agent configuration specifies a default operating system account, which can be changed. To disable or change the behavior of a local PATROL application parameter. The changes to the parameter are local to the managed system running the parameter and are stored in the agent configuration database. You must be granted specific permissions by a PATROL Administrator through the PATROL User Roles file in order to override parameters. Override a parameter is replaced by customize a parameter in PATROL 7.x. See also PATROL roles. The monitoring element of PATROL. Parameters are run by the PATROL Agent; they periodically use data collection commands to obtain data on a system resource and then parse, process, and store that data on the computer that is running the PATROL Agent. Parameters can display data in various formats, such as numeric, text, stoplight, and Boolean. Parameter data can be accessed from a PATROL Console, PATROLVIEW, or an SNMP console. Parameters have thresholds and can trigger warnings and alarms. If the value returned by the parameter triggers a warning or an alarm, the PATROL Agent notifies the PATROL Console and runs any recovery actions associated with the parameter. See also parameter history repository and parameter state.
operator mode
operating system account
override a parameter
parameter
18
parameter cache
The memory location where current parameter data is kept. In the PATROL Agents configuration file, you can set the size of the cache, the maximum number of data points that can be stored, and the interval (in seconds) for emptying the cache. Also known as parameter history file. See history repository. See override a parameter. The condition of a parameter. The most common parameter states are OK, warning, and alarm. In PATROL 3.x and earlier, a A parameter icon can show additional conditions that include no history, offline, and suspended. In PATROL 7.x, the suspended state is shown in the labelfor example, MyParam (suspended)rather than in the icon. A parameter can also be deactivated; when a parameter is deactivated, no icon is displayed. See also state. The core component of PATROL architecture. The agent is used to monitor and manage host computers and can communicate with the PATROL Console, a stand-alone event manager (PEM), PATROLVIEW, and SNMP consoles. From the command line, the PATROL Agent is configured by the pconfig utility; from a graphical user interface, it is configured by the xpconfig utility for Unix or the wpconfig utility for Windows. See also PATROL SNMP Master Agent. A file in which you can define the characteristics of the PATROL Agent by setting PATROL Agent configuration variables. You can edit the configuration file by using the pconfig utility, the wpconfig utility, or the xpconfig utility. See also KM configuration file, PATROL Agent configuration variable, pconfig, wpconfig, and xpconfig. The means by which the characteristics of a PATROL Agent are defined. PATROL provides default variable values that can be customized. Configuration variables determine such characteristics as how errors are handled, which KMs are loaded and how, how SNMP support is configured, and how events trigger SNMP traps. See also PATROL Agent configuration file.
Glossary 19
parameter history repository parameter override parameter state
PATROL Agent
PATROL Agent configuration file
PATROL Agent configuration variable
PATROL Agent Manager PATROL Agent namespace
A feature of PATROL for Microsoft Windows only. The graphical user interface used to install and run the PATROL Agent. A memory array that contains an internal representation of the PATROL object hierarchy. Values in the agent namespace are available to PSL scripts, eliminating the need to develop code to collect this data. A snapshot of the operating system process table on a monitored computer. The agent process cache is updated periodically. A periodic process of the PATROL Agent that issues a platform-dependent system query to obtain a list of the active processes. This data is used to update the PATROL Agent process cache. A time-ordered schedule of actions, such as application discovery and parameter execution, to be carried out by the PATROL Agent. See also PSL run queue. An interface program that you can access from the command line of a monitored computer and through which you can run some PATROL products and utilities. With the CLI, you can monitor the state of PATROL Agents remotely, execute PSL functions, and query and control events. The CLI is used in place of the PATROL Console when memory and performance constraints exist.
PATROL Agent process cache PATROL Agent process cache refresh
PATROL Agent run queue
PATROL Command Line Interface (CLI)
20
PATROL Console
The graphical user interface from which you launch commands and manage the environment monitored by PATROL. The PATROL Console displays all of the monitored computer instances and application instances as icons. It also interacts with the PATROL Agent and runs commands and tasks on each monitored computer. The dialog is event-driven so that messages reach the PATROL Console only when a specific event causes a state change on the monitored computer. A PATROL Console with developer functionality can monitor and manage computer instances, application instances, and parameters; customize, create, and delete locally loaded Knowledge Modules and commit these changes to selected PATROL Agent computers; add, modify, or delete event classes and commands in the Standard Event Catalog; and define expert advice. A PATROL Console with operator functionality can monitor and manage computer instances, application instances, and parameters and can view expert advice but not customize or create KMs, commands, and parameters. See also developer mode and operator mode.
PATROL Console Charting Server
A PATROL function that creates charts and graphs of actual values returned by more than one parameter. Charts and graphs are created by dragging and dropping various parameters into a multigraph container (folder) and plotting the results into a chart. Parameter data is plotted either in real time or from history sets and can be presented in a number of chart styles, including line graphs, pie charts, 3-D bar charts, and area plots. Charts can be viewed through the PATROL Console and printed to a local printer or PostScript file. An event management system that gathers, filters, translates, and prioritizes messages from the managed systems in an enterprise and displays them as alerts in a single console. The PATROL EM consolidates alerts from different vendors and different geographical locations into a single display for fast identification and resolution of potential problems.
PATROL Enterprise Manager (PATROL EM)
Glossary
21
PATROL Event Manager (PEM)
An event manager that you can use to view and manage events that occur on monitored system resources and that are sent by PATROL Agents. You can access the PEM from the PATROL Console or use it as a stand-alone facility. It works with the PATROL Agent and user-specified filters to provide a customized view of events. See also event manager. A PATROL utility used to convert PATROL parameter history data into an ASCII data file or to store parameter history data directly into a particular relational database management system. Formerly PATROLVIEW or PATROLINK. Products that can be used to view events and to monitor and display all the parameters provided by the PATROL Agents and KMs in a network or enterprise management console. See PATROL Knowledge Module Deployment Server (PATROL KMDS). See PATROL Knowledge Module Deployment Server Manager (PATROL KMDS Manager). A PATROL utility used to propagate KM user customizations to newly released versions of PATROL Knowledge Modules. The change and version control tool for KMs. A repository for storage of PATROL KMs and changes to those KMs.
PATROL History Loader KM
PATROLVIEW
PATROL KMDS
PATROL KMDS Manager PATROL KM Migrator
PATROL Knowledge Module Deployment Server (PATROL KMDS) PATROL Knowledge Module Deployment Server Manager (PATROL KMDS Manager) PATROL roles
The graphical interface for the PATROL KMDS that can be used to manage and deploy or distribute KM changes in the production environment.
In PATROL 3.x and earlier, a A set of permissions that grant or remove the ability of a PATROL Console or PATROL Agent to perform certain functions. PATROL roles are defined in the PATROL User Roles file, which is read when the console starts.
22
PATROL Script Language (PSL)
A scripting language (similar to Java) that is used for generic system management and that is compiled and executed on a virtual machine running inside the PATROL Agent. PSL is used for writing application discovery procedures, parameters, recovery actions, commands, and tasks for monitored computers within the PATROL environment. The agent through which a PATROL Agent interacts with an SNMP agent and SNMP manager. The PATROL Master Agent configuration file contains the community name and port number for all agents in such a multiple-agent architecture. In PATROL 3.x and earlier, a A domain group that can be set up by a Windows system administrator to restrict user access to a PATROL Developer Console. When a user tries to start a PATROL Console with developer functionality, PATROL checks whether the user is in the patroldev group. If the user is not in the group, a PATROL Console with operator functionality is started instead. See also ptrldev. The command line utility for setting PATROL Agent configuration variables. See also PATROL Agent configuration file, PATROL Agent configuration variable, wpconfig, and xpconfig. See PATROL Event Manager (PEM). A kind of scheduling that starts a parameter at a certain time and reruns the parameter at certain intervals. See also event-driven scheduling. A filter maintained by the PATROL Agent for each PATROL Console or event manager that connects to it. The filter is used to minimize network traffic by limiting the number and types of events that are forwarded from a PATROL Agent to a PATROL Console or an event manager (PEM). The schedule on which a parameter starts running and the intervals at which it reruns; the cycle is expressed in seconds. See also event-driven scheduling and periodic scheduling.
PATROL SNMP Master Agent
patroldev
pconfig
PEM periodic scheduling
persistent filter
polling cycle
Glossary
23
pop-up menu
The menu of commands for a monitored object; the menu is accessed by right-clicking the object. A quick one-time test written in PSL to determine whether a resource that you want to monitor is installed or running on a monitored computer. If the results are affirmative, the PATROL Agent runs the discovery script. Prediscovery helps reduce PATROL Agent processing requirements. A KM that is loaded by the PATROL Agent at startup and run as long as the Agent runs. See also disable an application, disable a KM and static KM. See PATROL Agent process cache refresh. A characteristic or attribute of an object, such as its icon. See PATROL Script Language (PSL).
prediscovery
preloaded KM
process cache refresh property PSL PSL Compiler
A PATROL utility that compiles PSL scripts into a binary byte code that can be executed by the PSL virtual machine. The PSL Compiler can also be used to check a PSL script for syntax errors. The compiler is embedded in the PATROL Agent and PATROL Console (PATROL 3.x and earlier) and can also be run as a command-line utility.
A PATROL Console utility that is used to debug PSL scripts. The PSL debugger is accessed through a computers pop-up menu. A type of application discovery in which the discovery rules are defined by using PSL. PSL discovery can consist of prediscovery and discovery PSL scripts. A PATROL utility that is used to tune the CPU usage and minimize child processes or file operations of a newly created KM. When the PSL Profiler is enabled, the PATROL Agent starts accumulating and recording profile statistics.
PSL Debugger
PSL discovery
PSL Profiler
24
PSL run queue
A queue of the currently executing PSL processes. The PSL run queue is used to distribute processing time between PSL processes in a round-robin fashion. In PATROL 3.x and earlier, a A form of patroldev that can be used in environments that support domain names no larger than eight characters. See also patroldev. In PATROL 3.x and earlier, a A command on the Tools menu from the PATROL Console main menu bar that contains built-in predefined commands that you can use to query the agent for frequently needed information. For example, you can query the agent regularly about all computer instances, application instances, and parameters that are in a warning or alarm state. See also Agent Query. The time interval (in seconds) at which the PATROL Console will try to reconnect to a PATROL Agent that has dropped the previous connection. The longer the interval, the lower the network traffic. See also heartbeat, heartbeat interval, message retries, message time-out. A procedure that attempts to fix a problem that caused a warning or alarm condition. A recovery action is defined within a parameter by a user or by PATROL and triggered when the returned parameter value falls within a defined alarm range. An action that forces the PATROL Agent to run one or more parameters immediately, regardless of their polling cycle. Refreshing does not reset the polling cycle but gathers a new data point between polling cycles. Refresh parameter is also called update in PATROL 7.x. The filter used by the PATROL Agent when transmitting events to consoles (event cache) from the event repository (located at the agent) for statistical reports.
ptrldev
Quick Query
reconnect polling
recovery action
refresh parameter
reporting filter
Glossary
25
response window
An input and output display for many KM menu commands that provides a customizable layout of the information (for example, the sort method for outputting system process IDs). See also system output window and task output window. The Real Time server (RTserver) delivers application-related data between the following PATROL Components: PATROL Agent PATROL Central Microsoft Windows Edition PATROL Central Web Edition PATROL Console Server
RTserver
You can install more than one RTserver to form an RTserver cloud. RTserver clouds provide flexibility and load balancing. If an RTserver fails, another RTserver in the cloud picks up the load and the PATROL components continue to communicate.
run queue self-polling parameter
See PATROL Agent run queue. A standard parameter that starts a process that runs indefinitely. The started process periodically polls the resource that it is monitoring and emits a value that is captured by the PATROL Agent and published as the parameter value. Self-polling avoids the overhead of frequently starting external processes to collect a monitored value. A self-polling parameter differs from most other parameters that run scripts for a short time and then terminate until the next poll time. In PATROL 3.x and earlier, any Any of the files that are saved when changes are made and saved during the current PATROL Console session. A session file includes the session-1.km file, which contains changes to KMs loaded on your console, and the session-1.prefs file, which contains user preferences. Session files are replaced by management profiles in PATROL 7.x.
session file
26
setup command
A command that is initiated by the PATROL Console and run by the PATROL Agent when the PATROL Console connects or reconnects to the agent. For example, a setup command can initialize an application log file to prepare it for monitoring. PATROL provides some setup commands for computer classes. Only a PATROL Console with developer functionality can add or change setup commands. An alias or copy of an object icon in the PATROL hierarchy. A type of application discovery that uses simple pattern matching for identifying and monitoring files and processes. See Simple Network Management Protocol (SNMP). A communications protocol that is supported by the PATROL Agent. SNMP allows network management systems to access PATROL Agents and allows PATROL Agents to monitor and manage SNMP devices. A condition which, when satisfied, results in an SNMP agent issuing a trap message to other SNMP agents and clients. Within the PATROL Agent, all events can be translated to SNMP traps and forwarded to SNMP managers. To temporarily suspend an alarm so that a parameter does not exhibit an alarm state. During the user-set snooze period, the parameter continues to run commands and recovery actions, and the parameter icon appears to be in an OK state. See also deactivate a parameter and suspend a parameter. A PATROL-provided collection of predefined event classes for all computer classes and application classes. To add, modify, or delete event classes and commands in the Standard Event Catalog, you must use a PATROL Console with developer functionality. See also event catalog and event class.
shortcut simple discovery
SNMP Simple Network Management Protocol (SNMP)
SNMP trap
snooze an alarm
Standard Event Catalog
Glossary
27
standard parameter
A type of parameter that collects and displays data and can also execute commands. A standard parameter is like a collector parameter and consumer parameter combined. See also collector parameter, consumer parameter, and parameter. See setup command. The condition of an object (computer instance, application instance, or parameter) monitored by PATROL. The most common states are OK, warning, and alarm. Object icons can show additional conditions. See also application state, computer state, parameter state, and state change action. A parameter output style that represents the on or yes state of a monitored object as a check mark and the off or no state as the letter x. Parameters with this output style can have alerts (warning and alarm) and recovery actions. Numeric data output for the monitored object can be displayed as a graph. See also stoplight. An action that is stored, maintained, and initiated by the PATROL Console when the console is notified by the PATROL Agent that a monitored object has changed state. The action, or command, executes on the computer on which the console is running, not the computer on which the agent is running. A KM that is not loaded by the PATROL Agent before a PATROL Console with a loaded KM of the same name connects to the Agent. Once loaded by the agent, a static KM is never unloaded but continues to run as long as the agent runs, even if all PATROL Consoles with a registered interest disconnect from the PATROL Agent. If the PATROL Agent stops, static KMs will not be reloaded. See also disable an application, disable a KM and preloaded KM.
startup command state
state Boolean
state change action
static KM
28
stoplight
A parameter output style that displays OK, warning, and alarm states as green, yellow, and red lights, respectively, on a traffic light. Parameters with this output style can have alerts (warning and alarm) and recovery actions. Numeric data output for the monitored object can be displayed as a graph. See also state Boolean. To stop running a parameter for selected computers or application instances. Suspending a parameter stops parameter commands and recovery actions but does not delete the parameter icon from the application instance window and does not delete the parameter definition from the KM tree in PATROL Consoles for Microsoft Windows environments. A suspended parameter can be resumed at any time. You can suspend a parameter from its pop-up menu. See also deactivate a parameter and snooze an alarm. A message window that displays the output of commands and tasks that the PATROL Console or the PATROL Agent execute on an instance. The window also displays error messages, commit status messages, and so forth. When the system output window contains unread messages in PATROL 3.x and earlier, the instance icon displays a yellow triangle for Windows; for Unix, it displays a blue screen with white text. A command or group of commands that can execute on one object or several objects simultaneously. A task runs in the background and is not part of the PATROL Agent run queue; a task icon is displayed for each running task. A window that contains command output generated by a task (for example, a KM menu command or a parameter warning or alarm). While executing, each task has its own icon, which usually appears in the PATROL interface or main window but may appear in an appropriate object window. A point or points that define a range of values, outside of which a parameter is considered to be in a warning or alarm range.
suspend a parameter
system output window
task
task output window
threshold
Glossary
29
unload a KM
To delete a KM from a PATROL Console session in order to stop monitoring the KM-defined objects on all computers. The KM files are not deleted from the directories on the PATROL Console or the PATROL Agent computers, and the PATROL Agent will continue to run the KM, collect parameter data, and run recovery actions until no connected console has the KM loaded. To prevent the PATROL Agent computer from collecting parameter data and running recovery actions for a KM, disable the KM. If a KM has been flagged as static, then it will not be unloaded. See also disable an application, disable a KM, preloaded KM, and static KM. In PATROL 3.x and earlier, a A connectionless network protocol that allows the PATROL Console to connect to many agents simultaneously. TCP requires an open file for each connection, and the number of files that a process can have open is generally limited. The PATROL Console settings that designate the account that you want to use to connect to monitored host computers, prevent a console with developer functionality from downloading its version of a KM to a PATROL Agent upon connection, disable the commit process for a console with developer functionality, determine certain window and icon display characteristics, specify the event cache size, and indicate whether startup and shutdown commands are enabled. A PATROL Console with either developer or operator functionality can change user preferences. In PATROL 3.x and earlier, the The KM version comparison that PATROL makes when a PATROL Console connects to a PATROL Agent. By default, KM versions from PATROL Consoles with developer functionality are loaded rather than PATROL Agent KM versions, and PATROL Agent KM versions are loaded rather than KM versions from PATROL Consoles with operator functionality. A filter that can be created in an event manager (PEM) and that screens events forwarded from PATROL Agents. Views can be created, stored, and reapplied to host computers.
User Datagram Protocol (UDP)
user preferences
version arbitration
view filter
30
warning
An indication that a parameter has returned a value that falls within the warning range. See also alarm. A feature of PATROL for Microsoft Windows only. The graphical user interface utility for setting PATROL Agent configuration variables. The wpconfig utility can be accessed from a computer pop-up menu on a computer running a PATROL Agent or a computer running a PATROL Console with developer functionality. See also PATROL Agent configuration file and PATROL Agent configuration variable. A feature of PATROL for Unix only. The graphical user interface utility for setting PATROL Agent configuration variables. You can access the xpconfig utility from an xterm session command line on a computer running a PATROL Agent or from a pop-up menu or an xterm session command line on a PATROL Console with developer functionality. See also PATROL Agent configuration file and PATROL Agent configuration variable.
wpconfig
xpconfig
Glossary
31
32
Index
Index
A
ABA 2-4 Access Control List 2-22 accounts 2-26 ACL 2-22 Add/Modify RTserver Information dialog box 6-12 Alarm1 6-18 Alarm2 6-18 alarms 6-4 application class 2-11 application instance 2-10 applications running 2-12 architectural advances 2-4 architecture 2-5 Assuring Business Availability 2-4 authentication 2-25 available 2-4
C
centralized 2-21 client disconnect warnings 6-4 client, definition 6-2 ClientCount 6-4 ClientCount parameter 6-16, 6-19 clientdis_coll parameter 6-16, 6-17, 6-19 clouds 2-23 common service 2-8 communication 2-23 communications-level security 2-24 component installation requirements 5-4 components 2-5, 2-9 computer class 2-11 configuring PATROL Infrastructure KM 6-11 to 6-13 console choosing the right console 3-1, 3-2 console system 2-7 ConsoleCount parameter 6-16, 6-19 ConsoleServerCount parameter 6-16, 6-19 conventions, document xvi creating an installable image 6-9 creating policy 5-1, A-1 credentials 2-21
B
BMC Products Installation Directory 6-9 book 1-xiv border 6-18
Index
D
data collection 2-11 debug flags 6-28 to 6-29 default security 2-27 developer 2-16, 2-17, 2-19 development 2-16, 2-17 disconnect warnings 6-23 DisconnectedClients parameter 6-16, 6-19 discovery 2-10, 2-11, 2-13 document conventions xvi documentation 1-4
H
historical data 2-16, 2-17, 2-19 host 2-3 host names 4-9
I
impersonation 2-21, 2-25, 2-26 implementation application-specific aspects 3-2 planning 3-1 policy 5-1, A-1 requirements 3-1 implementing 1-2 InfoBox 2-11 InfoBoxes 6-20 Infrastructure KM 1-2 installable image 6-9 installation 5-3 creating an installable image 6-9 custom 5-2 local 5-2 PATROL Infrastructure KM 6-6 to 6-10 requirements A-5 typical 5-2 Installation Status page 6-9 installed files, PATROL Infrastructure KM 6-10 installing 2-27 introduces 1-1 IPlanner.bat 4-3
E
enterprise A-2 environment 1-2, 3-2 event messages 2-20 events 2-20, 6-4 examine 3-2
F
firewalls 3-3 flags debugging 6-28 to 6-29
G
group patop 2-26 patpop 2-26 patscadm 2-26 patwatch 2-26 groups 2-26
K
KMs 2-11 build 2-19 data collection 2-11, 2-12
edit 2-19 InfoBox 2-11 parameters 2-11 preddiscovery 2-11 preloaded 2-12 send 2-19
O
online documentation xv operating systems 4-2 organized 1-xiv overhead 2-28
L
layers 2-4 Linux 4-3 Locate the RTserver for an Object dialog box 6-22 location function 3-3 locations 3-2, A-2 common services 3-10 failover 3-7 firewalls 3-4 managed 3-4 managed systems 3-8 management 3-4 messaging failover 3-8 mix 3-4 monitoring managed systems 3-9 questions 3-7 type 3-3
P
P7_coll parameter 6-15, 6-17, 6-19 P7_RTCLIENTS KM 6-2, 6-4, 6-13 P7_RTSERVERS KM 6-2, 6-4, 6-13 parameters 2-11 active property 6-18 alarm state 6-18 border property 6-18 icon property 6-18 polling cycle 6-18 scheduling property 6-18 type property 6-18 units property 6-18 warning state 6-18 passwords 2-21 patadm 2-26 patop 2-26 patpop 2-26 PATROL description of 2-2 functions of 2-3 planning an implementation 3-1 PATROL 3.x Product Directory 6-9 PATROL 7 2-4 PATROL Agent description 2-3 PATROL architecture 2-5 PATROL Console description of 2-3 PATROL Developer Console 2-15 PATROL Event Manager (PEM) 2-3
M
managed system 2-8 management profiles 2-22 mapping 3-2 message queue 6-4 middle tier 2-21 migration 5-4 minimum requirements A-5 MsgsQueued parameter 6-4, 6-16, 6-19
Index
PATROL Infrastructure KM configuring 6-11 to 6-13 installed files 6-10 user tasks 6-21 to 6-30 PATROL KMs 2-11 PATROL_HOME 6-10 PATROL7 KM 6-2, 6-4, 6-13 PatrolAgentCount parameter 6-16, 6-19 patscadm 2-26 patwatch 2-26 performing 2-4 ping command 6-29 Ping dialog box 6-29 planning documentation 3-2 planning process 3-2 policy setting 5-1, A-1 policy levels 2-27 poll commands 6-24 polling cycle, parameters 6-18 prediscovery 2-11 preloaded 2-12 privileges 2-24 Process ID 6-20 product planning 3-1 Provide PATROL 3.x Product Directory page 6-9 PSL discovery 2-13
remote 5-3 Review Selections page 6-9 rights 2-24 RTMon Command dialog box 6-24 RTMon commands 6-23 to 6-26 RTMon Task dialog box 6-27 RTMon tasks 6-27 RTserver 2-23 configuration 4-8 RTserver clouds 2-23 RTserver messaging name 6-20 RTServer_coll parameter 6-15, 6-17, 6-19 runtime 2-21
S
scalability 4-5 Scheduling 6-18 security 2-9 security levels 2-27 security policies 2-27 server 2-7, 2-8 setting policy 5-1, A-1 shared channels 6-27 to 6-28 Specify Installation Directory page 6-8 starting 4-3 supported 2-21
Q
queue 6-4
T
testing 4-5 TotalConsoles parameter 6-15, 6-19 TotalConsoleServers parameter 6-15, 6-19 TotalMsgsQueued parameter 6-16, 6-19 TotalPatrolAgents parameter 6-15, 6-19 TotalRTservers parameter 6-15, 6-19 transaction 2-24
R
recommendations 4-5, 4-7 recovered 2-4 recovery actions 2-11 release notes xvi
U
Unix 2-16, 4-3 unwatch command 6-26 usability 2-28 user groups 2-26 user rights and privileges 2-26 user tasks PATROL Infrastructure KM 6-21 to 6-30
V
visualize 1-3
W
warnings client disconnect 6-4 disconnect 6-23 watch command 6-25 Web server 2-7, 2-8 worksheets A-2
Index
END USER LICENSE AGREEMENT NOTICE

BY OPENING THE PACKAGE, INSTALLING, PRESSING "AGREE" OR "YES" OR USING THE PRODUCT, THE ENTITY OR INDIVIDUAL ENTERING INTO THIS AGREEMENT AGREES TO BE BOUND BY THE FOLLOWING TERMS. IF YOU DO NOT AGREE WITH ANY OF THESE TERMS, DO NOT INSTALL OR USE THE PRODUCT, PROMPTLY RETURN THE PRODUCT TO BMC OR YOUR BMC RESELLER, AND IF YOU ACQUIRED THE LICENSE WITHIN 30 DAYS OF THE DATE OF YOUR ORDER CONTACT BMC OR YOUR BMC RESELLER FOR A REFUND OF LICENSE FEES PAID. IF YOU REJECT THIS AGREEMENT, YOU WILL NOT ACQUIRE ANY LICENSE TO USE THE PRODUCT. This Agreement ("Agreement") is between the entity or individual entering into this Agreement ("You") and BMC Software Distribution, Inc., a Delaware corporation located at 2101 CityWest Blvd., Houston, Texas, 77042, USA or its affiliated local licensing entity ("BMC"). "You" includes you and your Affiliates. "Affiliate" is defined as an entity which controls, is controlled by or shares common control with a party. THIS AGREEMENT WILL APPLY TO THE PRODUCT, UNLESS (1) YOU AGREED TO A WEB BASED LICENSE AGREEMENT WITH BMC WHEN ORDERING THE PRODUCT, IN WHICH CASE THAT WEB BASED LICENSE AGREEMENT GOVERNS THE USE OF THE PRODUCT, OR (2) IF YOU DID NOT AGREE TO A WEB BASED LICENSE AGREEMENT WITH BMC WHEN ORDERING THE PRODUCT AND YOU HAVE A WRITTEN LICENSE AGREEMENT WITH BMC, THEN THAT WRITTEN AGREEMENT GOVERNS THE USE OF THE PRODUCT. THE ELECTRONIC AGREEMENT PROVIDED WITH THE PRODUCT AS PART OF THE INSTALLATION OF THE PRODUCT WILL NOT APPLY. In addition to the restrictions imposed under this Agreement, any other usage restrictions contained in the Product installation instructions or release notes shall apply to Your use of the Product. PRODUCT AND CAPACITY. "Software" means the object code version of the computer programs provided, via delivery or electronic transmission, to You. Software includes computer files, enhancements, maintenance modifications, upgrades, updates, bug fixes, and error corrections. "Documentation" means all written or graphical material provided by BMC in any medium, including any technical specifications, relating to the functionality or operation of the Software. "Product" means the Software and Documentation. "License Capacity" means the licensed capacity for the Software with the pricing and other license defining terms, including capacity restrictions, such as tier limit, total allowed users, gigabyte limit, quantity of Software, and/or other capacity limitations regarding the Software. For licenses based on the power of a computer, You agree to use BMCs current computer classification scheme, which is available at http://www.bmc.com or can be provided to You upon request. ACCEPTANCE. The Product is deemed accepted by You, on the date that You received the Product from BMC. LICENSE. Subject to the terms of this Agreement, as well as Your payment of applicable fees, BMC grants You a non-exclusive, non-transferable, perpetual (unless a term license is provided on an order) license for each copy of the Software, up to the License Capacity, to do the following: (a) install the Software on Your owned or leased hardware located at a facility owned or controlled by You in the country where You acquired the license; (b) operate the Software solely for processing Your own data in Your business operations; and (c) make one copy of the Software for backup and archival purposes only (collectively a "License"). If the Software is designed by BMC to permit you to modify such Software, then you agree to only use such modifications or new software programs for Your internal purposes or otherwise consistent with the License. BMC grants You a license to use the Documentation solely for Your internal use in Your operations. LICENSE UPGRADES. You may expand the scope of the License Capacity only pursuant to a separate agreement with BMC for such expanded usage and Your payment of applicable fees. There is no additional warranty period or free support period for license upgrades. RESTRICTIONS: You agree to NOT: (a) disassemble, reverse engineer, decompile or otherwise attempt to derive any Software from executable code; (b) distribute or provide the Software to any third party (including without limitation, use in a service bureau, outsourcing environment, or processing the data of third parties, or for rental, lease, or sublicense); or (c) provide a third party with the results of any functional evaluation or benchmarking or performance tests, without BMCs prior written approval, unless prohibited by local law.
TRIAL LICENSE. If, as part of the ordering process, the Product is provided on a trial basis, then these terms apply: (i) this license consists solely of a non-exclusive, non-transferable evaluation license to operate the Software for the period of time specified from BMC or, if not specified, a 30 day time period ("Trial Period") only for evaluating whether You desire to acquire a capacity-based license to the Product for a fee; and (ii) Your use of the Product is on an AS IS basis without any warranty, and BMC, ITS AFFILIATES AND RESELLERS, AND LICENSORS DISCLAIM ANY AND ALL WARRANTIES (INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT) AND HAVE NO LIABILITY WHATSOEVER RESULTING FROM THE USE OF THIS PRODUCT UNDER THIS TRIAL LICENSE ("Trial License"). BMC may terminate for its convenience a Trial License upon notice to You. When the Trial Period ends, Your right to use this Product automatically expires. If You want to continue Your use of the Product beyond the Trial Period, contact BMC to acquire a capacity-based license to the Product for a fee. TERMINATION. This Agreement shall immediately terminate if You breach any of its terms. Upon termination, for any reason, You must uninstall the Software, and either certify the destruction of the Product or return it to BMC. OWNERSHIP OF THE PRODUCT. BMC or its Affiliates or licensors retain all right, title and interest to and in the BMC Product and all intellectual property, informational, industrial property and proprietary rights therein. BMC neither grants nor otherwise transfers any rights of ownership in the BMC Product to You. BMC Products are protected by applicable copyright, trade secret, and industrial and intellectual property laws. BMC reserves any rights not expressly granted to You herein. CONFIDENTIAL AND PROPRIETARY INFORMATION. The BMC Products are and contain valuable confidential information of BMC ("Confidential Information"). Confidential Information means non-public technical and non-technical information relating to the BMC Products and Support, including, without limitation, trade secret and proprietary information, and the structure and organization of the Software. You may not disclose the Confidential Information to third parties. You agree to use all reasonable efforts to prevent the unauthorized use, copying, publication or dissemination of the Product. WARRANTY. Except for a Trial License, BMC warrants that the Software will perform in substantial accordance with the Documentation for a period of one year from the date of the order. This warranty shall not apply to any problems caused by software or hardware not supplied by BMC or to any misuse of the Software. EXCLUSIVE REMEDY. BMCs entire liability, and Your exclusive remedy, for any defect in the Software during the warranty period or breach of the warranty above shall be limited to the following: BMC shall use reasonable efforts to remedy defects covered by the warranty or replace the defective Software within a reasonable period of time, or if BMC cannot remedy or replace such defective copy of the Software, then BMC shall refund the amount paid by You for the License for that Software. BMCs obligations in this section are conditioned upon Your providing BMC prompt access to the affected Software and full cooperation in resolving the claim. DISCLAIMER. EXCEPT FOR THE EXPRESS WARRANTIES ABOVE, THE PRODUCT IS PROVIDED "AS IS." BMC, ITS AFFILIATES AND LICENSORS SPECIFICALLY DISCLAIM ALL OTHER WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. BMC DOES NOT WARRANT THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR FREE, OR THAT ALL DEFECTS CAN BE CORRECTED. DISCLAIMER OF DAMAGES. IN NO EVENT IS BMC, ITS AFFILIATES OR LICENSORS LIABLE FOR ANY SPECIAL, INDIRECT, INCIDENTAL, PUNITIVE OR CONSEQUENTIAL DAMAGES RELATING TO OR ARISING OUT OF THIS AGREEMENT, SUPPORT, AND/OR THE PRODUCT (INCLUDING, WITHOUT LIMITATION, LOST PROFITS, LOST COMPUTER USAGE TIME, AND DAMAGE OR LOSS OF USE OF DATA), EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND IRRESPECTIVE OF ANY NEGLIGENCE OF BMC OR WHETHER SUCH DAMAGES RESULT FROM A CLAIM ARISING UNDER TORT OR CONTRACT LAW. LIMITS ON LIABILITY. BMCS AGGREGATE LIABILITY FOR DAMAGES IS LIMITED TO THE AMOUNT PAID BY YOU FOR THE LICENSE TO THE PRODUCT. SUPPORT. If Your order includes support for the Software, then BMC agrees to provide support (24 hours a day/7 days a week) ("Support"). You will be automatically re-enrolled in Support on an annual basis unless BMC receives notice of termination from You as provided below. There is a free support period during the one year warranty period. (a) Support Terms. BMC agrees to make commercially reasonable efforts to provide the following Support: (i) For malfunctions of supported versions of the Software, BMC provides bug fixes, patches or workarounds in order to cause that copy of the Software to operate in substantial conformity with its then-current operating specifications; and (ii) BMC provides new releases or versions, so long as such new releases or versions are furnished by BMC to all other enrolled Support customers without additional charge. BMC may refuse to provide Support for any versions or releases of the Software other than the most recent version or release of such Software made available by BMC. Either party may terminate Your enrollment in Support upon providing notice to the other at least 30 days prior to the next applicable Support anniversary date. If You re-enroll in Support, BMC may charge You a reinstatement fee of 1.5 times what You would have paid if You were enrolled in Support during that time period. (b) Fees. The annual fee for Support is 20% of the Softwares list price less the applicable discount or a flat capacity based annual fee. BMC may change its prices for the Software and/or Support upon at least 30 days notice prior to Your support anniversary date.
VERIFICATION. If requested by BMC, You agree to deliver to BMC periodic written reports, whether generated manually or electronically, detailing Your use of the Software in accordance with this Agreement, including, without limitation, the License Capacity. BMC may, at its expense, audit Your use of the Software to confirm Your compliance with the Agreement. If an audit reveals that You have underpaid fees, You agree to pay such underpaid fees. If the underpaid fees exceed 5% of the fees paid, then You agree to also pay BMCs reasonable costs of conducting the audit. EXPORT CONTROLS. You agree not to import, export, re-export, or transfer, directly or indirectly, any part of the Product or any underlying information or technology except in full compliance with all United States, foreign and other applicable laws and regulations. GOVERNING LAW. This Agreement is governed by the substantive laws in force, without regard to conflict of laws principles: (a) in the State of New York, if you acquired the License in the United States, Puerto Rico, or any country in Central or South America; (b) in the Province of Ontario, if you acquired the License in Canada (subsections (a) and (b) collectively referred to as the "Americas Region"); (c) in Singapore, if you acquired the License in Japan, South Korea, Peoples Republic of China, Special Administrative Region of Hong Kong, Republic of China, Philippines, Indonesia, Malaysia, Singapore, India, Australia, New Zealand, or Thailand (collectively, "Asia Pacific Region"); or (d) in the Netherlands, if you acquired the License in any other country not described above. The United Nations Convention on Contracts for the International Sale of Goods is specifically disclaimed in its entirety. ARBITRATION. ANY DISPUTE BETWEEN YOU AND BMC ARISING OUT OF THIS AGREEMENT OR THE BREACH OR ALLEGED BREACH, SHALL BE DETERMINED BY BINDING ARBITRATION CONDUCTED IN ENGLISH. IF THE DISPUTE IS INITIATED IN THE AMERICAS REGION, THE ARBITRATION SHALL BE HELD IN NEW YORK, U.S.A., UNDER THE CURRENT COMMERCIAL OR INTERNATIONAL, AS APPLICABLE, RULES OF THE AMERICAN ARBITRATION ASSOCIATION. IF THE DISPUTE IS INITIATED IN A COUNTRY IN THE ASIA PACIFIC REGION, THE ARBITRATION SHALL BE HELD IN SINGAPORE, SINGAPORE UNDER THE CURRENT UNCITRAL ARBITRATION RULES. IF THE DISPUTE IS INITIATED IN A COUNTRY OUTSIDE OF THE AMERICAS REGION OR ASIA PACIFIC REGION, THE ARBITRATION SHALL BE HELD IN AMSTERDAM, NETHERLANDS UNDER THE CURRENT UNCITRAL ARBITRATION RULES. THE COSTS OF THE ARBITRATION SHALL BE BORNE EQUALLY PENDING THE ARBITRATORS AWARD. THE AWARD RENDERED SHALL BE FINAL AND BINDING UPON THE PARTIES AND SHALL NOT BE SUBJECT TO APPEAL TO ANY COURT, AND MAY BE ENFORCED IN ANY COURT OF COMPETENT JURISDICTION. NOTHING IN THIS AGREEMENT SHALL BE DEEMED AS PREVENTING EITHER PARTY FROM SEEKING INJUNCTIVE RELIEF FROM ANY COURT HAVING JURISDICTION OVER THE PARTIES AND THE SUBJECT MATTER OF THE DISPUTE AS NECESSARY TO PROTECT EITHER PARTYS CONFIDENTIAL INFORMATION, OWNERSHIP, OR ANY OTHER PROPRIETARY RIGHTS. ALL ARBITRATION PROCEEDINGS SHALL BE CONDUCTED IN CONFIDENCE, AND THE PARTY PREVAILING IN ARBITRATION SHALL BE ENTITLED TO RECOVER ITS REASONABLE ATTORNEYS FEES AND NECESSARY COSTS INCURRED RELATED THERETO FROM THE OTHER PARTY. U.S. GOVERNMENT RESTRICTED RIGHTS. The Software under this Agreement is "commercial computer software" as that term is described in 48 C.F.R. 252.227-7014(a)(1). If acquired by or on behalf of a civilian agency, the U.S. Government acquires this commercial computer software and/or commercial computer software documentation subject to the terms of this Agreement as specified in 48 C.F.R. 12.212 (Computer Software) and 12.211 (Technical Data) of the Federal Acquisition Regulations ("FAR") and its successors. If acquired by or on behalf of any agency within the Department of Defense ("DOD"), the U.S. Government acquires this commercial computer software and/or commercial computer software documentation subject to the terms of this Agreement as specified in 48 C.F.R. 227.7202 of the DOD FAR Supplement and its successors. MISCELLANEOUS TERMS. You agree to pay BMC all amounts owed no later than 30 days from the date of the applicable invoice, unless otherwise provided on the order for the License to the Products. You will pay, or reimburse BMC, for taxes of any kind, including sales, use, duty, tariffs, customs, withholding, property, value-added (VAT), and other similar federal, state or local taxes (other than taxes based on BMCs net income) imposed in connection with the Product and/or the Support. This Agreement constitutes the entire agreement between You and BMC and supersedes any prior or contemporaneous negotiations or agreements, whether oral, written or displayed electronically, concerning the Product and related subject matter. No modification or waiver of any provision hereof will be effective unless made in a writing signed by both BMC and You. You may not assign or transfer this Agreement or a License to a third party without BMCs prior written consent. Should any provision of this Agreement be invalid or unenforceable, the remainder of the provisions will remain in effect. The parties have agreed that this Agreement and the documents related thereto be drawn up in the English language. Les parties exigent que la prsente convention ainsi que les documents qui sy rattachent soient rdigs en anglais.
SW EULA Int 030102
Notes

*19464*

Patrol Infrastructure Planning Guide 19464

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Patrol Infrastructure Planning Guide 19464

Enviado por

Direitos autorais:

Formatos disponíveis

PATROL Infrastructure Planning Guide

September 12, 2002

Restricted Rights Legend

Contacting BMC Software

United States and Canada

Outside United States and Canada

Support Web Site

Support by Telephone or E-mail

Before Contacting BMC Software

BMC Software, Inc., Confidential and Proprietary Information

BMC Software, Inc., Confidential and Proprietary Information

PATROL Implementation Manual

BMC Software, Inc., Confidential and Proprietary Information

Examining Your Enterprise