BMC PATROL Knowledge Module for Event Management User Guide.pdf

PATROL KM for Event Management

User Guide

Supporting

PATROL KM for Event Management 2.7PATROL Configuration Manager 1.6

January 2005

Contacting BMC Software

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

United States and Canada

Address BMC SOFTWARE INC2101 CITYWEST BLVDHOUSTON TX 77042-2827 USA

Telephone 713 918 8800 or800 841 2031

Fax 713 918 8000

Outside United States and Canada

Telephone (01) 713 918 8800 Fax (01) 713 918 8000

Copyright March 8, 2005 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.

IBM is a registered trademark of International Business Machines Corporation.

DB2 is a registered trademark of International Business Machines Corporation.

Oracle is a registered trademark, and the Oracle product names are registered trademarks or trademarks of Oracle Corporation.

All other trademarks belong to their respective companies.

BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices included in this documentation.

Restricted rights legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, 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.

PATROL KM for Event Management 3

Customer support

You can obtain technical support by using the Support page on the BMC Software website or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, please see Before Contacting BMC Software.

Support website

You can obtain technical support from BMC Software 24 hours a day, 7 days a week at http://www.bmc.com/support_home. From this website, 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 or send an e-mail message to [email protected]. Outside the United States and Canada, contact your local support center for assistance.

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

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

4 PATROL Knowledge Module for Event Management User Guide

ContentsChapter 1 Product Components and Capabilities 15

Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Typical Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Notification Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Rules Stored as Pconfig Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Notification Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Sending Notification: Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Sending Alerts to an Enterprise Console: Process Flow . . . . . . . . . . . . . . . . . . . . . 20Sending Pages using AlarmPoint: Process Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Using the PATROL Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22PATROL Configuration Manager Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Usage Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Tasks that Must be Completed Using PATROL KM for Event Management . . . 22

Application Classes and Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Application Class Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Application InfoBox Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Chapter 2 Installing and Migrating PATROL KM for Event Management 25

Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Virtual Machine Support Limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Backing up the Notification Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Checking for Product Patches or Fixes Before Installing. . . . . . . . . . . . . . . . . . . . . 30Determining How to Install Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Installation Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Determining Where to Install the PATROL Agent. . . . . . . . . . . . . . . . . . . . . . . . . . 32Determining Where to Install KMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

PATROL Security Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Checking Security Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Assessing and Implementing a Different Security Level . . . . . . . . . . . . . . . . . . . . 34

Typical and Custom Installation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355

Installing into a PATROL 3.3.x or 3.4.x Unix Environment . . . . . . . . . . . . . . . . . . 36First-Time Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Installing For the First Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Installing on AS/400 (iSeries) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Upgrading from an Earlier Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

6Remove Customized KM Files From the PATROL_CACHE . . . . . . . . . . . . . . . . . 43Remove Existing Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Considerations for Using Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Browser Version Required for Viewing PATROL Console for Unix Help . . . . . . 44Additional Considerations for Using Online Help for Unix . . . . . . . . . . . . . . . . . . 44

Uninstalling PATROL KM for Event Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Determining the Version of the Installation Utility . . . . . . . . . . . . . . . . . . . . . . . . . 47Uninstalling PATROL KM for Event Management on Windows . . . . . . . . . . . . . 47

Chapter 3 Using the PATROL KM for Event Management 49

Preparing to Use the PATROL KM for Event Management . . . . . . . . . . . . . . . . . . . . . 51Loading and Preloading KMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Determining Which KMs to Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51KM Files Preloaded on Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Loading and Unloading KMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Loading Knowledge Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Verifying that PATROL KM for Event Management KM is Loaded . . . . . . . . . . . 55Unloading Knowledge Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Configuration Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Defining Notification Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Defining Notification Targets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Defining Availability Monitors and Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Deciding Where to Place Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Configuring Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Recommended Configuration Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Using Notification Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Testing Notification Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Configuring Notification Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Configuring Remote Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Configuring Alert Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Rewording Notification Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Setting Notification Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Testing Notification Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Disabling Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Configuring Availability Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Configuring an Availability Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Configuring a Backup Availability Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Configuring the Availability Monitor Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Specifying an Availability Monitoring Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Changing the Ping Command Used for Availability Monitoring . . . . . . . . . . . . . 93

Integrating with AlarmPoint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94AlarmPoint Benefits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Notification Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Installing and Configuring AlarmPoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Installing the AlarmPoint Java Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Configuring the AlarmPoint Java Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Testing the Java Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Using Action Scripts for AlarmPoint 5.2.01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98PATROL Knowledge Module for Event Management User Guide

Configuring Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Testing Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Managing Parameter Thresholds and Poll Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Benefits of Using the PATROL KM for Event Management. . . . . . . . . . . . . . . . . 104Setting Collector Poll times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Using Wildcards to Represent PATROL Instance Names. . . . . . . . . . . . . . . . . . . 107Activating and Deactivating Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Applying Thresholds and Poll Time Changes to the Agent . . . . . . . . . . . . . . . . . 111Disabling the use of PATROL KM for Event Management Thresholds and Poll

Times. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Specifying What to Monitor or Exclude from Monitoring . . . . . . . . . . . . . . . . . . . . . 112

Selecting Application Instances to Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Excluding Application Instances from Monitoring . . . . . . . . . . . . . . . . . . . . . . . . 114

Configuring Blackout Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115About Notification Blackout Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Configuring Notification Blackouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Configuring Availability Blackouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Configuring Recovery Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120About Recovery Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Enabling PATROL KM for Event Management Recovery Actions . . . . . . . . . . . 121Specifying a Recovery Action Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Specifying a Recovery Action Command Type . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Using PSL Recovery Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Chapter 4 Usage Scenarios 127

Sending E-mail Notification When Disk Space is Low . . . . . . . . . . . . . . . . . . . . . . . . 128Assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Selecting a Mail Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Loading the PATROL KM for Event Management . . . . . . . . . . . . . . . . . . . . . . . . 130Defining the Notification Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Configuring the Remote Agent NT1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Specifying an E-mail Target for Low Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . 135Rewording the Notification Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Testing Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Sending E-mail Notification for CPU Usage that Includes Parameter Annotations 140Assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Overview of Annotated Data Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Enabling Recovery Actions and Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Creating Recovery Action Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Creating Notification Command Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Testing Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Configuring a Recovery Action that Runs Under a Specified Account. . . . . . . . . . . 144Assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Testing Recovery Action Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Enabling Recovery Actions for ArchFreeSpace on Agent Computer . . . . . . . . . 146Defining the Recovery Action Type for Agent Computer . . . . . . . . . . . . . . . . . . 1467

8Storing the Encrypted Password as a Pconfig Variable . . . . . . . . . . . . . . . . . . . . . 147Configuring the PSL Recovery Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Summary of Rules Created. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Testing the Recovery Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Chapter 5 Rules and Configuration Variables 151

PATROL Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Example: PATROL Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Example: Rule Inheritance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Example: PATROL KM for Event Management E-mail Rule . . . . . . . . . . . . . . . . 154

NOTIFY_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156How the NOTIFY_EVENT and REMOTE_NOTIFY_EVENT are Triggered . . . 156Event Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Order of Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Empty Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Using the Variable userdefined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Event Size Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157NOTIFY_EVENT Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Alert Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161arsAction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161alertSystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162allowOverrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163loginDeniedIgnoredUsers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164useEnvOnlyForCmds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164allowInfoRecoveryActions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165spoolDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165setParameterValue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Local Alert Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166alertResend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167alertLocalCommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167arsCommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168arsCmdType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168alertResetOnInit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Remote Alert Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169NOTIFICATION_SERVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170RemoteAgentCommSettings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Notification Target Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171emailTargets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171pagerTargets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172customTargets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173ttTargets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Blackout Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174blackoutPeriod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174__OVERRIDE__ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Notification Server Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175nsRemoteTargetSetting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Custom Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176msgText . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176msgBody . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177PATROL Knowledge Module for Event Management User Guide

CustomId1 and CustomId2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178allowOperator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180appClassSettingsStatusFlag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180disableNotifyAnnotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181maxEventsToReport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182snmpSettings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182snmpOid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182Updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Blackout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183pingCmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184pingOkString . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184pingPacketSize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185pingAttempts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185pingArgs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185checkerAccount.defaultAccount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Parameter Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186THRESHOLDS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188paramSettingsStatusFlag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188processWildcards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Instance Filtering Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190FilterList Configuration Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190FilterType Configuration Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Chapter 6 Parameters 191

Parameter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Parameter Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Chapter 7 Troubleshooting PATROL KM for Event Management 197

Configuration Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Cannot Send E-mail Notifications to Multiple Targets . . . . . . . . . . . . . . . . . . . . . 198Parameters are Unavailable or are Not Being Updated. . . . . . . . . . . . . . . . . . . . . 200Too Many E-mail Alerts Are Being Generated . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Parameters Show a Negative Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202Parameter Annotations Show Incorrect Targets or Other Errors . . . . . . . . . . . . . 203AgentLoginDenied Parameter is in Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203The Availability Monitor is Not Pinging Frequently Enough . . . . . . . . . . . . . . . 205NOTIFY_EVENTS not Generated when Parameter is in Alarm . . . . . . . . . . . . . 205Parameters Setting Lost After Agent Restart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206Notification Message not Sent from OpenVMS Server . . . . . . . . . . . . . . . . . . . . . 207AS_AVAILABILITY Application Not Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . 207When Using event_trigger2() Statements, Notifications Sent to Wrong Target 207

Gathering Diagnostic Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Where to Find Diagnostic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2089

10Installation Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Determining PATROL KM for Event Management Version Number. . . . . . . . . 209

Appendix A Accessing Menu Commands, InfoBoxes, and Online Help 211

Accessing KM Commands and InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212Accessing Online Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Index 215PATROL Knowledge Module for Event Management User Guide

FiguresTypical PATROL KM for Event Management Architecture . . . . . . . . . . . . . . . . . . . . . 17Select Products and Components to Install - Typical Install . . . . . . . . . . . . . . . . . . . . 39Quick Config - Notification Server Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Notification Server Settings Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Primary Notification Server Settings Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Selecting / to Represent all PATROL Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Set Event Management Alert Variables/Rules Dialog Box . . . . . . . . . . . . . . . . . . . . . 81Selecting Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Selecting Application Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Selecting Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Set Event Management Alert Variables/Rules Dialog Box . . . . . . . . . . . . . . . . . . . . . 83What If Results Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Availability Monitor Add Target Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Choose Primary Monitor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Rules to Apply to the Availability Checker Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Java Client Status Displayed in Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97SET EVENT MANAGEMENT VARIABLE:arsAction Dialog Box . . . . . . . . . . . . . . 101SET EVENT MANAGEMENT ALERT VARIABLES/RULES Dialog Box . . . . . . . . 102Configure Thresholds Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Choose the target classes Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Set Event Management Blackout Variables/Rules Dialog Box . . . . . . . . . . . . . . . . . 117Set Event Management Blackout Variables/Rules Dialog Box . . . . . . . . . . . . . . . . . 119Availability Monitor Add Target Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128QUICK CONFIG - NOTIFICATION SERVER Dialog Box . . . . . . . . . . . . . . . . . . . . . 131NOTIFICATION SERVER SETTINGS Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132EVENT MANAGEMENT ALERT VARIABLE:emailTargetsRemoteALARM Dialog

Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Message Rewording Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137SET EVENT MANAGEMENT VARIABLE: alertLocalCommand dialog box . . . . . 200 11

12 PATROL Knowledge Module for Event Management User Guide

TablesE-mail Notification Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Sending Alerts to Enterprise Console Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Sending Pages using AlarmPoint Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Application Classes and KM File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23AS_EVENTSPRING InfoBox Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24AS_AVAILABILITY InfoBox Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24System Requirements for Installing and Using PATROL KM for Event Management

26System Role Packages Available for Product Components . . . . . . . . . . . . . . . . . . . . . 38EVENT_MANAGEMENT.kml File and Associated KM Files) . . . . . . . . . . . . . . . . . . 53Notification Target Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Recommended Rule Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Recommended Configuration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Notification Script Location on Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Requirements for Using Scripts on Unix Notification Server . . . . . . . . . . . . . . . . . . . . 65Notification Script Location on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Requirements for Notification Server When Using Windows e-mail Clients . . . . . . 66Editing Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Notification Script Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Quick Config - Notification Server Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Notification Server Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75REMOTE AGENT COMMUNICATION SETTINGS dialog box . . . . . . . . . . . . . . . . . 79Message Length Limitations by Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Availability Target Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Threshold Setting Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Wildcard Usage in Threshold Rules: Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Blackout Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118PATROL KM for Event Management Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Sending E-mail Notification for Low Disk Space: Configuration Overview . . . . . . 129Sending E-mail Notification for Low Disk Space: Configuration Overview . . . . . . 145Rules Created: Oracle Recovery Action Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149PATROL Objects Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Example: PATROL Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Example: Rule Inheritance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154PATROL KM for Event Management Variable Definition . . . . . . . . . . . . . . . . . . . . . 155 13

NOTIFY_EVENT Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Notification Server Message Replacement Variables . . . . . . . . . . . . . . . . . . . . . . . . . 160Notification Server Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161arsAction Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161alertSystem Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

14Notification System Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163allowOverrides Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163LoginDeniedIgnoredUsers Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164useEnvOnlyForCmds Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164useEnvOnlyForCmds Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165SpoolDirectory Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165SetParameterValue Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166alertResend Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167alertLocalCommand Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167arsCommand Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168arsCmdType Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169alertResetOnInit Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Remote Alert Settings: Configure Notification Servers Configuration Variable . . . 170Remote Alert Settings: Configure Notification Servers Configuration Variable . . . 170Remote Alert Settings: Remote Communication Settings Configuration Variable . 170Notification Targets: Email Target Configuration Variable . . . . . . . . . . . . . . . . . . . . 172Notification Targets: Pager Target Configuration Variable . . . . . . . . . . . . . . . . . . . . 172Notification Targets: Custom Target Configuration Variable . . . . . . . . . . . . . . . . . . 173Notification Targets: TT Targets Configuration Variable . . . . . . . . . . . . . . . . . . . . . . 173Blackout Periods Configuration Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Overrides Configuration Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Notification Server Settings: Remote Target Setting Configuration Variable . . . . . 175msgText Configuration Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176msgBody Configuration Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Custom Configuration Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178allowOperator Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179active Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180appClassSettingsStatusFlag Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180disableNotifyAnnotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181disableNotifyAnnotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Add Target Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182Add Target: Updated Flag Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Primary Configuration Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Blackout Configuration Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184PingCmd Configuration Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184pingOKString Configuration Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184pingPacketSize Configuration Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185pingAttempts Configuration Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185pingArgs Configuration Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186Checker Account Configuration Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186Parameter Settings: Thresholds Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Understanding the THRESHOLDS Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Parameter Settings: poll times Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Parameter Settings: Status Flags Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Parameter Settings: poll times Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Filter List Configuration Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190Filter Type Configuration Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190PATROL KM for Event Management Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192PATROL KM for Event Management Parameter Defaults . . . . . . . . . . . . . . . . . . . . . 194PATROL Knowledge Module for Event Management User Guide

1 PCC h a p t e r 1roduct Components and apabilities

This chapter provides an overview of the PATROL Knowledge Module for Event Management (also referred to as PATROL KM for Event Management).

Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Typical Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Notification Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Rules Stored as Pconfig Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Notification Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Sending Notification: Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Sending Alerts to an Enterprise Console: Process Flow . . . . . . . . . . . . . . . . . . . . . 20Sending Pages using AlarmPoint: Process Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Using the PATROL Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22PATROL Configuration Manager Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Usage Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Tasks that Must be Completed Using PATROL KM for Event Management . . . 22

Application Classes and Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Application Class Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Application InfoBox Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Chapter 1 15

Features

16

F

AeaturesPATROL KM for Event Management provides event notification, message rewording, and centralized alert management features. With the PATROL KM for Event Management, you can:

configure notification (e-mail, paging, trouble-ticket, or custom) for PATROL alerts

configure PATROL to send notifications to an enterprise console

configure recovery actions for PATROL alerts

reword notification messages and customize message content

configure PATROL to monitor the availability of hosts

manage PATROL parameter thresholds and polling schedules

configure blackout periods for notification and for availability monitoring

integrate with any command line e-mail client, paging solution, compiled executable, or script. Sample scripts are provided.

integrate with AlarmPoint enterprise notification software using provided scripts

rchitectureThe PATROL KM for Event Management architecture consists of monitored hosts (remote agents) and notification servers. Notification servers collect and process events from monitored systems according to notification rules that you define. Notification rules specify:

who gets notified when they get notified the content of the notification message

Both the monitored hosts and the notification servers require a PATROL Agent and the PATROL KM for Event Management. Figure 1 on page 17 shows an PATROL KM for Event Management environment with several monitored hosts and two notifications servers (a primary and a backup).PATROL Knowledge Module for Event Management User Guide

Architecture

Ty

N

Rpical Configuration

In the typical configuration, monitored hosts forward events to a primary notification server. The backup notification server is used only when the primary notification server is unavailable. Failover is automatic. If the primary and the backup notification servers are unavailable, the monitored host queues its events. When communication is restored, the monitored host forwards queued events to the notification servers.

Figure 1 Typical PATROL KM for Event Management Architecture

otification Servers

BMC Software recommends the use of notification servers. The PATROL KM for Event Management architecture does not require a notification server to perform notifications. Any monitored host running the PATROL KM for Event Management can be configured to perform its own notifications, event filtering, and alert control. However, there are advantages to using a notification server. For more information, see Why use a Notification Server? on page 58.

ules Stored as Pconfig Variables

PATROL KM for Event Management rules are stored in pconfig variables, not in the KM. Pconfig variables override KM settings. Thus, if you upgrade a KM, you dont need to reconfigure the rules. The pconfig variable settings are retained.

Primary BackupNotification Server 1 Notification Server 2

Agent 1 Agent 2 Agent 3Chapter 1 17

Notification Process

18

Notification Process The following diagrams show how notification occurs in the following configuration:

e-mail notification using a notification server alert notification using the PATROL Enterprise Manager (PEM) paging notification using AlarmPoint

The PATROL KM for Event Management rules that apply at each step are shown. For detailed rule descriptions, see Chapter 5, Rules and Configuration Variables. PATROL Knowledge Module for Event Management User Guide


Sending Notification: Process Flow

Table 1 shows how a notification is processed by the PATROL KM for Event Management when the notification server sends an e-mail notification. The same process applies to paging, trouble-ticket, or custom notification.

Table 1 E-mail Notification Process

Step Rule or Variable

1. Alert occurs on remote agent - parameter exceeds threshold and enters WARN/ALARM state, generating PATROL standard event 11 or 39.

NA

2. Recovery action initiated (if configured) arsActionarsCommandarsCmdType

3. The remote agent triggers a PATROL NOTIFY_EVENT (if arsAction = 4 or 6)

arsAction

4. CustomID values are set (if configured) customId1customId2

5. Notification message reworded (if configured)

msgTextmsgBody

6. PATROL determines if a blackout period applies. If so, NOTIFY_EVENT is not sent to the notification server.

blackoutPeriod

7. The alert is queued. alertResetOnInitalertResend

8. Determine whether notification is local or remote. If local, notification sent from remote agent. If remote, notification sent from notification server.

alertSystem

9. Determine the notification targets. emailTargets

10. Remote agent NotifiedEvent parameter is annotated with alert information.

NA

11. A REMOTE_NOTIFY_EVENT is sent to notification server (if arsAction = 4 or 6)

NA

12. The notification server parses REMOTE_NOTIFY_EVENT event details, which contains the same information as the original NOTIFY_EVENT.

NA

13. Repeat steps 4 through 10 on the notification server (except step 7).

Multiple. See steps 4 through 10.

14. The notification server executes the script to send e-mail message to targets.

emailTargetsalertLocalCommandChapter 1 19


20

Sending Alerts to an Enterprise Console: Process Flow

Table 2 shows how an alert processed by the PATROL KM for Event Management is sent to the PATROL Enterprise Manager (PEM). The PATROL KM for Event Management rules associated with each step are shown.

Table 2 Sending Alerts to Enterprise Console Process

Step Rule

1. Alert occurs on remote agent (parameter exceeds defined threshold and enters WARN or ALARM state, generating PATROL event 11 or 39)

NA

2. Notification processing occurs on the remote agent as previously discussed in Table 1 on page 19.

The message rewording (msgText) must be done on the remote agent so that when the PATROL Event Translator (PET) pulls the event, the event contains the host specific information.

arsActionarsCommandmsgTextmsgBodyblackoutPeriodalertResetOnInitalertResendalertSystem

3. The NOTIFY_EVENT is sent to the notification server.

NA

4. The notification server process the REMOTE_NOTIFY_EVENT as previously discussed in Table 1 on page 19.

arsActionarsCommandblackoutPeriodalertSystem

5. PATROL Event Translator (PET) pulls REMOTE_NOTIFY_EVENT from the notification server

NA

6. The PET processes the REMOTE_NOTIFY_EVENT and sends it to the PATROL Enterprise Manager.

You can also send events to third-party enterprise consoles, such as Tivoli.

NA

7. The event is received by the PATROL Enterprise Manager.

NAPATROL Knowledge Module for Event Management User Guide


Sending Pages using AlarmPoint: Process Flow

The following diagram shows how a page is processed by the PATROL KM for Event Management. This process assumes the use of the enterprise notification software AlarmPoint. However, you can use any third-party paging software that has a command-line interface. The PATROL KM for Event Management rules associated with each step are shown

Table 3 Sending Pages using AlarmPoint Process

Step Rule

1. Alert occurs on remote agent (parameter exceeds defined threshold and enters WARN or ALARM state, generating PATROL standard event 11 or 39)

NA

2. Notification processing occurs on the remote agent as previously discussed in Table 1 on page 19.

arsActionarsCommandmsgTextblackoutPeriodalertResetOnInitalertResendalertSystemcustomTargets

3. The NOTIFY_EVENT is sent to the notification server.

4. The notification server process the REMOTE_NOTIFY_EVENT as previously discussed in Table 1 on page 19.

arsActionarsCommandblackoutPeriodalertSystemcustomTargets

5. The notification server executes the script that calls the AlarmPoint Java client.

6. The AlarmPoint java client sends the paging request to the AlarmPoint server.

7. The AlarmPoint server processes the paging request and sends the page request to the paging device. The paging device could be a paging server, the internet, or whatever your enterprise is using for paging.

8. The paging device sends the page to the defined target. Chapter 1 21

Using the PATROL Configuration Manager

22

U

PA

U

TaMsing the PATROL Configuration ManagerThe PATROL KM for Event Management is designed to be used with the PATROL Configuration Manager, which allows you to manage and globally deploy agent configuration settings.

TROL Configuration Manager Tasks

sage Examples

For a brief example of how to use the PATROL Configuration Manager to copy settings, see Sending E-mail Notification When Disk Space is Low on page 128.

For detailed instructions on using PATROL Configuration Manager, see the PATROL Configuration Manager User Guide.

sks that Must be Completed Using PATROL KM for Event anagement

Tasks that you must complete using the PATROL KM for Event Management, and cannot be completed using the PATROL Configuration Manager, are also noted. These tasks are listed below.

Configuring Notification Servers on page 71 Configuring Remote Agents on page 73 Specifying an Availability Monitoring Account on page 92

You can accomplish many of the tasks described in this manual using either the PATROL KM for Event Management or the PATROL Configuration Manager. In this manual, only the PATROL KM for Event Management method is described. However, for some tasks, the PATROL Configuration Manager method is more efficient. For example, configuring multiple agents at one time. Rather than configure each agent individually, you can configure one agent and then use the PATROL Configuration Manager to copy the agent settings to the other agents. Tasks such as these that are easier to accomplish with the PATROL Configuration Manager are denoted by an icon in the margin (shown at left). PATROL Knowledge Module for Event Management User Guide

Application Classes and Instances

A

A

Tapplication Classes and InstancesThe PATROL KM for Event Management contains two application classes:

AS_EVENTSPRING AS_AVAILABILITY

Table 4 describes the PATROL KM for Event Management application classes, icons and KM files.

pplication Class Hierarchy

The AS_EVENTSPRING application class icon resides at the application level beneath the computer icon. The AS_EVENTSPRING application class has only a single instance which is Event Management.

The AS_AVAILABILITY icon represents the Availability application class and resides at the application level beneath the computer icon. All monitored hosts appear beneath the Availability container and are accessed by double-clicking the AS_AVAILABILITY icon.

ble 4 Application Classes and KM File

Application Class KM File DescriptionAS_EVENTSPRING.km menu commands, parameters, and InfoBox

items for managing and reporting on events managed by the KM

AS_AVAILABILITY.km instances, menu commands, parameters, and InfoBox items for monitored hosts and agents

NOTE The AS_AVAILABILITY application class icon is not displayed in the PATROL Console until availability targets are added.Chapter 1 23

Application Classes and Instances

24

Application InfoBox Items

The status of an application instance can be reviewed by accessing the application instance InfoBox. To view an InfoBox, use the following procedure.

To View the InfoBox on the PATROL Console for Unix

1 Double click the application instance icon under the computer icon.

2 Using the middle mouse button, click the instance icon.

To View the InfoBox on the PATROL Console for Windows

1 Double click the application instance icon under the computer icon.

2 Right-click the instance icon to display a pop-up menu.

3 Choose InfoBox.

Table 5 shows the InfoBox items for the AS_EVENTSPRING application class.

Table 6 shows the InfoBox items for the AS_AVAILABILITY application instances.

Table 5 AS_EVENTSPRING InfoBox Items

Item Description

KM Version the version of the PATROL KM for Event Management

Spool Directory

directory used to store output files generated by parameter reports and recovery actions executed by the PATROL KM for Event Management

Table 6 AS_AVAILABILITY InfoBox Items

Item Description

Primary Monitor agent with primary responsibility for performing availability monitoring

Ping Command command used to perform ping checks

Ping Host (ICMP)? whether the host is being pinged using the ICMP protocol

Ping PATROLAgent?

whether the PATROL Agent is being monitored for availability

Ping SNMP Agent? whether the SNMP agent is being monitoring for availability

Blacked Out? indicates whether the selected instance is currently being blacked out

KM Version the version of the PATROL KM for Event ManagementPATROL Knowledge Module for Event Management User Guide

2 IfC h a p t e r 2nstalling and Migrating PATROL KM or Event Management

This chapter provides the information that you need to install PATROL KM for Event Management. For additional information about the PATROL installation process, see the PATROL Installation Reference Manual or the PATROL for Microsoft Windows Servers Getting Started. The following topics are discussed in this chapter:

Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Virtual Machine Support Limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Backing up the Notification Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Checking for Product Patches or Fixes Before Installing. . . . . . . . . . . . . . . . . . . . . 30Determining How to Install Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Installation Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Determining Where to Install the PATROL Agent. . . . . . . . . . . . . . . . . . . . . . . . . . 32Determining Where to Install KMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

PATROL Security Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Checking Security Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Assessing and Implementing a Different Security Level . . . . . . . . . . . . . . . . . . . . 34

Typical and Custom Installation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Installing into a PATROL 3.3.x or 3.4.x Unix Environment . . . . . . . . . . . . . . . . . . 36

First-Time Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Installing For the First Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Installing on AS/400 (iSeries) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Upgrading from an Earlier Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Chapter 2 25

Remove Customized KM Files From the PATROL_CACHE . . . . . . . . . . . . . . . . . 43Remove Existing Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Considerations for Using Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Browser Version Required for Viewing PATROL Console for Unix Help . . . . . . 44Additional Considerations for Using Online Help for Unix. . . . . . . . . . . . . . . . . . 44

Uninstalling PATROL KM for Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Determining the Version of the Installation Utility . . . . . . . . . . . . . . . . . . . . . . . . . 47Uninstalling PATROL KM for Event Management on Windows . . . . . . . . . . . . . 47

Installation Overview

26

In

S

In

YMcomSe

Yth

YPP

Ta

R

osy

Ppstallation OverviewThis chapter contains instructions for installing PATROL KM for Event Management. For additional installation instructions, see the following documents:

ystem Requirements

Before installing the PATROL KM for Event Management, verify

the target computer meets the system requirements noted in Table 7 on page 26, including supported OS platforms and PATROL product versions.

the account that you use to install the product has sufficient privileges

formation Document

ou are installing the PATROL KM for Event anagement along with many other PATROL mponents and you need information about igrating customizations or using the Distribution rver (DS).

PATROL for Microsoft Windows Servers Getting Started

PATROL for Unix Getting Started PATROL for OpenVMS Installation Guide PATROL for AS/400 Getting Started

ou need more technical details about how to use e installation program.

PATROL Installation Reference Manual

ou need more information on distributing the ATROL KM for Event Management or other ATROL components using the Distribution Server.

Distribution Server Getting Started Guide

NOTE For a current list of the supported operating systems, see the release notes for the PATROL solution. For example, the PATROL for Microsoft Windows Servers Release Notes.

ble 7 System Requirements for Installing and Using PATROL KM for Event Management (Part 1 of 2)

esource Requirements Comments

perating stems

For a current list of the supported operating systems, see the release notes for the PATROL solution. For example, the PATROL for Microsoft Windows Servers Release Notes.

ATROL roducts

For a current list of the supported PATROL products, see the release notes for the PATROL solution. For example, the PATROL for Microsoft Windows Servers Release Notes. PATROL Knowledge Module for Event Management User Guide


A

se

li

p

(UbsuHPU

b

Ta

Rccounts

This section describes how to set up a PATROL installation account for Windows and Unix platforms.

Windows Environment

PATROL requires a dedicated user account, known as the PATROL default account, in the Windows environment. The PATROL default account must be created before you install PATROL. The PATROL default account can be either a local or a domain account:

curity levels For information on security, see PATROL Security Levels on page 34.

The PATROL Security Level is set during the installation of the PATROL infrastructure components. If your product contains the PATROL Agent, you have an opportunity to select the security level. Make sure that the level that you select/accept is compatible with the rest of your enterprises PATROL installation.

On iSeries, only security levels 0 and 1 are supported.

cense You must have a valid demonstration license (typically good for 30 days) or a permanent license to run your PATROL products. If you do not have a permanent license, contact your BMC Software sales representative or the BMC Software Contract Administration department.

orts If you are installing an agent or console with PATROL KM for Event Management, you must specify the port number to connect to all the agent computers.

The default port number is 3181 for agents.

nix only)rowser to pport online elp for ATROL for nix Console

Use Netscape Navigator version 3.014.78 to use online Help with PATROL for Unix.

Browser Version Required for Viewing PATROL Console for Unix Help on page 44

rowser This product uses Common Installer 7.5.20, which requires a browser. For a list of supported browser, see the PATROL Installation Reference Manual.

ble 7 System Requirements for Installing and Using PATROL KM for Event Management (Part 2 of 2)

esource Requirements CommentsChapter 2 27


28 Stand-alone workgroup servers must use a local user account as a PATROL default account.

Servers that are trusted members of a domain may use either a local or domain account.

PATROL default accounts on domain controllers should be only domain accounts.

Administrative Rights

BMC Software recommends that you make the PATROL default account a member of the local Administrators group of the computer where the agent will reside. On a domain controller, BMC Software recommends that you make the account a member of the domain Administrators group. However, you can choose to remove the PATROL default account from the Administrators group. If you do so, the PATROL Agent may not be able to perform all of its administrative tasks. For example, the PATROL Agent may not be able to execute recovery actions or perform other activities that requires administrative rights on the monitored machine.

Creating a Separate Account

Although you can use an existing Windows user account, BMC Software recommends that you create a separate Windows user account for PATROL.

Console Connection Accounts

BMC Software recommends that you create a separate account, in addition to the PATROL default account, for PATROL console operators who dont need administrative privileges. Operators can use this account to connect the console to the agent. To configure KMs from the console, however, you need to give the console connection account administrative rights.

Unix Environments

BMC Software recommends that if you require a Unix account, the account that you create should meet the following conditions:

WARNING Do not use a built-in Windows domain or local Administrator account as the PATROL default account. Such account usage causes files created by PATROL to be owned by the Administrator, which could result in security or file access problems.PATROL Knowledge Module for Event Management User Guide


V The account .login, .profile, .cshrc, and .kshrc files should contain as little user customization as possible. Specifically, be sure that the account has no aliases and that no commands in these files can change the unmask setting. The recommended umask setting for the installation account is 022. In addition, verify that the prompt is set to the default.

Do not use the root account to install PATROL products because this may create security risks.

Ensure that the account has permission to create directories in the directory where you will install PATROL products.

Ensure that the computers on which you want to install PATROL have ftp and telnet enabled.

PATROL configuration requires permissions usually reserved for the system administrator. These permissions include access to a root account on the computer where you want to install PATROL.

BMC Software recommends that you install PATROL on local partitions, not on NFS-mounted partitions. If you do install PATROL on NFS-mounted partitions, the root account must have been granted root access permissions on the NFS server.

The account that you use to install PATROL must have permission to write the installation logs to the $HOME and /tmp directories on the computer where you are installing products.

Your PATROL product may have other restrictions with regard to the logon accounts and the default PATROL account. Check with your developers for text that more fully describes the logon and PATROL account requirements for your product. Many products require, for example, that the default PATROL account have the same rights as the third-party product that your KM monitors.

irtual Machine Support Limitation

VMware provides technology that creates virtual infrastructures by providing a layer of abstraction between the computing, storage, and networking hardware, and the software that runs on it. This technology enables customers to run additional operating systems in multiple windows called virtual machines.

BMC Software does not anticipate problems with the PATROL product families in virtual infrastructure implementations, but these products have not been specifically tested in this scenario. Therefore, BMC Software will provide support only for problems that are reproducible without these complementary technologies.Chapter 2 29

Preparing for Installation

30

P

B

Creparing for InstallationBMC Software recommends that you first install PATROL KM for Event Management on a limited number of development or test machines, then configure and test PATROL KM for Event Management before installing it onto production machines.

Before you install, you must

back up the notification script, if upgrading (see page 30) check for product patches (see page 30) determine how to install products (see page 31) ensure you are using the appropriate version of the installation utility (see page 31) understand where to install the PATROL Agent and KMs (see page 32) choose between Typical and Custom installation options (see page 35) understand PATROL security options (page 34)

acking up the Notification Script

If you are upgrading, make sure you have copied your notification script to a directory outside of the installation directory. This action prevents the script from being overwritten during a new install or upgrade.

hecking for Product Patches or Fixes Before Installing

Product fixes or patches are often available through the BMC Software Web site. Patches correct problems that are found after a product is released. BMC Software recommends that you check the PATROL for Microsoft Windows Servers product page on the BMC Software Customer Support Web site to determine whether a patch is available before you begin installing a product. PATROL Knowledge Module for Event Management User Guide


D

Inetermining How to Install Products

You can install products on the computer on which you are running the installation utility (local installation), or you can create an installable image of products so that you can install them at a later time using the Distribution Server (remote installation functionality). An installable image is a fully configured product image that you can use to install products to multiple computers. With an installable image, you can create one product image with one pass through the installation utility and then use that image to install to remote computers in your environment.

Local Installation

If you install locally, you must install PATROL KM for Event Management and a PATROL Agent on each computer that you want to monitor, and PATROL KM for Event Management and a PATROL Console for Windows or Unix on each computer from which you want to view results. If you install locally in a PATROL 7.x environment, you must install PATROL KM for Event Management on the computer that hosts the PATROL Console Server.

Details for installing products locally are contained in this chapter.

Remote Installation

If you create an installable image, the product configuration information that you enter, such as the BMC Software products installation directory, account names, passwords, PATROL Agent port number, and security options, must be the same for all computers on which the image is to be installed. 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 by using the ctltool.

For more information about creating, distributing, and installing installable images, and about using the ctltool, see the PATROL Installation Reference Manual.

stallation Utility

The installation instructions contained in this book pertain to version 7.5.20 of the installation utility. This version of the installation utility might be different from the version included on another product CD or from a version that you downloaded from the BMC Software Electronic Product Download (EPD) site. If you use a version of the installation utility other than version 7.5.20, the instructions in this book may not accurately describe what you see on your screen.Chapter 2 31


32

D

Determining Where to Install the PATROL Agent

Install the PATROL Agent on each computer that you want to monitor.

When installing the PATROL Agent, select Managed System as the system role during the installation.

etermining Where to Install KMs

Where KMs are installed depends on which system roles you have assigned to a computer and which PATROL infrastructure components are installed on that computer.

This section explains where KMs must be installed.

PATROL 3.x

In a PATROL 3.x environment, you must install KMs on the following computers:

Computers hosting the PATROL AgentSelect Managed Systems as the System Role in the installation utility when installing KMs. This selection installs KM files that run on the PATROL Agent.

Computers hosting the PATROL Console for Windows or PATROL Console for UnixSelect Console Systems as the System Role in the installation utility when installing KMs on computers hosting the PATROL Console for Windows or PATROL Console for Unix. This selection installs KM files for use by the console.

PATROL 7.x

In a PATROL 7.x environment, you must install KMs on the following computers:

Computers hosting the PATROL Console ServerSelect Common Services Systems as the System Role in the installation utility. This selection installs KM icons, Help files, and resource files used by PATROL Central Operator Microsoft Windows Edition and PATROL Central Operator Web Edition.

NOTE If you do not install each KM on the computer hosting the PATROL Console Server and select Common Services Systems as the System Role in the installation utility, no KM icons or KM Help files will be available in either PATROL Central Operator Microsoft Windows Edition or PATROL Central Operator Web Edition.PATROL Knowledge Module for Event Management User Guide

Preparing for Installation Computers hosting the PATROL AgentSelect Managed Systems as the System Role in the installation utility. This selection installs KM files that run on the PATROL Agent.

When using PATROL Central Operator Web Edition, install KMs on computers hosting the PATROL Console Server using the Common Services Systems role and computers hosting the PATROL Agent using the Managed Systems role.

If you are using older versions of the following components:

PATROL Console Server prior to version 7.2.36 PATROL Central Operator Web Edition prior to version 7.1.10

You must also install KMs on the computer hosting the PATROL Central Operator Web Edition web server using the Common Services Systems role.

For more information about the PATROL 7.x architecture, see the PATROL Infrastructure Planning Guide.

Additional Information

For more information about the PATROL consoles and PATROL Console Server or RTserver, see the products respective online help systems and the following documents:

PATROL Central Operator - Web Edition Getting Started PATROL Central Operator - Microsoft Windows Edition Getting Started PATROL Console Server and RTserver Getting Started PATROL Configuration Manager User Guide PATROL Console for Microsoft Windows User Guide - Understanding the Basics of

PATROL, Volume 1 PATROL Console for Unix User GuideChapter 2 33

PATROL Security Levels

34

P

C

AATROL Security LevelsYou can secure the data passed between PATROL components and restrict unauthorized users from accessing your data by implementing PATROL security. You can select from five security levels when you install PATROL.

hecking Security Levels

To check the security level of a previously installed agent, console server, or console, perform the following steps:

1 From the command line switch to the path on the computer that you want to check:

%BMC_ROOT\..\common\security\bin\OS

2 Run the following command to display the security policy of the current machine:

The security level is displayed in the security level field of the output.

ssessing and Implementing a Different Security Level

Review the security level definitions in the PATROL Security User Guide before installing PATROL to determine the appropriate security level for your components. To implement a new security level after having previously installed PATROL security, see the PATROL Security User Guide for instructions.

WARNING The PATROL Agent, console server, and consoles must operate at the same security level to communicate with each other. When you install agents, console servers, or consoles that need to communicate with previously installed versions of these components, check the security level of the previously installed components and be sure to install the new ones at the same level.

esstool policy -a PATROL Knowledge Module for Event Management User Guide

Typical and Custom Installation Types

Typical and Custom Installation TypesThe installation utility may prompt you to select one of the following installation types:

The Typical installation type uses defaults values for all optional configuration information. It prompts you only for mandatory configuration information. This type is for any or all of the following situations:

You are new to the PATROL product that you are installing and you have an agent or console already installed in the default directories.

You are performing a first-time installation (you are not upgrading), and you are installing into the default product installation directories.

With the Custom installation type, you can install individual components of the product. It requires that you specify all configuration information. This type is for any or all of the following situations:

You want to install individual components rather than the entire product. You want to specify

the port numbers that components use to communicate with each other a security level greater than basic security any other product settings that a user might want to change

You are upgrading PATROL KM for Event Management from a previously installed version.

You are installing into an existing PATROL environment that is not in the default installation directory.

The Custom installation type installs the KMs that you select.

With each installation type, you can deselect any components that you dont want to install.

NOTE If you are installing PATROL KM for Event Management to an existing PATROL Agent or Console environment that is not in the default installation directory, use Custom. Do not use Typical. Typical will automatically install the agent or console with PATROL KM for Event Management and overwrite your existing installation.

NOTE If you choose the typical installation type, the PATROL KM for Event Management is automatically installed when you select the operating system KM. For example, if you select the PATROL KM for Windows Operating System, the PATROL KM for Event Management is automatically installed. Chapter 2 35

Typical and Custom Installation Types

36

Installing into a PATROL 3.3.x or 3.4.x Unix Environment

If you are installing PATROL KM for Event Management into a Unix environment that has PATROL 3.3.x or PATROL 3.4.x installed, you must launch the installation utility from the command line using the -releaseversion option as described in Upgrading from an Earlier Version on page 43.

If you have a PATROL Agent installed on the computer where you are installing PATROL KM for Event ManagementPreload component, the installation script designates PATROL KM for Event Management as a preloaded KM in the agent configuration file. When a KM is designated as a preloaded KM on a PATROL Agent, it automatically loads and begins to monitor resources and applications whenever the agent is started.

If you have a PATROL Console installed on the computer where you are installing the PATROL KM for Event ManagementPreload component, the installation script loads the PATROL KM for Event Management into the console.

For more information about preloading, see the PATROL Agent Reference Manual.PATROL Knowledge Module for Event Management User Guide

First-Time Installation

F

Inirst-Time InstallationThe installation utility offers two types of installations: Typical and Custom. For a description of the two types of installations, see Typical and Custom Installation Types on page 35.

If you are installing on AS/400 (iSeries), see Installing on AS/400 (iSeries) on page 42.

stalling For the First Time

You can install PATROL KM for Event Management using either the Typical or Custom installation type. Regardless of the type of installation you choose, you must repeat this installation process for each computer on which you want to install PATROL KM for Event Management.

Before You Begin

You first should install on a limited number of computers in the test environment, test the installation thoroughly, and then install in your production environment.

You must have created the PATROL default account.

To Install Using the Typical Installation Type

1 Close the Service Control Manager window and the Control Panel window.

2 From the PATROL for Microsoft Windows Servers CD or from an installation image that has been electronically downloaded from an EPD site and extracted, run setup.exe.

3 In the Welcome to the Installation Utility window, click Next to begin your installation.

4 Review the license agreement, select Accept, and click Next to continue.

NOTE By default, the Typical installation type configures the PATROL Agent to connect through port 3181. To connect the agent from a different port, you must use the Custom installation type.Chapter 2 37

First-Time Installation

38

Ta

Pr

PM5 In the Select Installation Option window, select I want to install products on this computer now and click Next to continue.

6 In the Select Type of Installation window, select Typical and click Next to continue.

7 In the Specify Installation Directory window, accept the default directory and click Next to continue.

8 In the Select System Roles window, select any or all of the following roles to indicate the components that you want to install and click Next:

If you are installing to a computer that hosts or will host a (Windows only) PATROL Console for Window (Unix only) PATROL Console for Unix, select Console Systems.

If you are installing to a computer that hosts or will host a PATROL Agent, select Managed Systems.

If you are installing to a computer that hosts or will host the PATROL Central Operator Web Edition (PATROL 7.x architecture) Web server, the PATROL Console Servers, or the RTservers, select Common Services.

Fore more information, see Determining Where to Install the PATROL Agent on page 32.

ble 8 System Role Packages Available for Product Components

oduct Component/Selectable Entity

System Role to Select

Console System Managed System

Common Servicesa

aPATROL Central Operator Web Edition. This console is available when you select the common services role.

PCO-Winb

bPATROL Central Operator Microsoft Windows Edition. This console is available when you select the console system role.

PATROL 3c

cPATROL Console for Windows and PATROL Console for Unix are PATROL 3 console systems. They are available when you select the console system role.

ATROL Knowledge Module for Event anagement

no yes yes yesPATROL Knowledge Module for Event Management User Guide

First-Time Installation9 From the Select Products and Components to Install window, select components that you want to install (see Figure 2 on page 39) and click Next.

Figure 2 Select Products and Components to Install - Typical Install

10 In the PATROL Default Account Properties window, enter the user name and password that you want to use for your PATROL default account and click Next. You should have created this account manually before you began to install PATROL. (For more information about the PATROL account, see Accounts on page 27.) This window is displayed only when you are installing a product that requires a PATROL logon.

11 In the Confirm BMC Product Startup Information window, specify whether to restart the PATROL Agent after installation. This window is displayed only if you are installing to a PATROL Agent system.

NOTE If you choose the typical installation type, the PATROL KM for Event Management is automatically installed when you select the operating system KM. For example, if you select the PATROL KM for Windows Operating System, the PATROL KM for Event Management is automatically installed.

NOTE The actual selectable components may be different that what is

Documents

BMC PATROL Knowledge Module for Event Management User Guide.pdf