Patrol for Unix and Linux Unix Get Started

PATROL® for Unix and LinuxGetting Started

Supporting

PATROL for Unix and Linux 9.2

March 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 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.

PATROL technology holds U.S. Patent Number 5655081.

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.

http://www.bmc.com

PATROL® for Unix and Linux Getting Started 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

http://www.bmc.com/support_home

mailto:[email protected]

4 PATROL® for Unix and Linux Getting Started

ContentsChapter 1 PATROL for Unix and Linux Components and Capabilities 13

PATROL KM for Unix and Linux Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Built-in Recovery Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

PATROL for Unix and Linux Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15PATROL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15PATROL KM for Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16PATROL KM for Log Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16PATROL KM for Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17PATROL KM for History Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18PATROL Perform Data Collector for Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18PATROL Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Related Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 2 Installing and Migrating PATROL KM for Unix and Linux 21

Verifying Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23System Requirements for PATROL for Unix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Additional Requirements Needed to Install and Use the PATROL Perform Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Checking for Product Patches or Fixes Before Installing. . . . . . . . . . . . . . . . . . . . . 33Determining How to Install Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Determining the Version of the Installation Utility . . . . . . . . . . . . . . . . . . . . . . . . . 34Target Computers and Their Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Determining Where to Install KMs Based on Architecture. . . . . . . . . . . . . . . . . . . 36Mounting a CD on Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

PATROL Security Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Checking Security Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Assessing and Implementing a Different Security Level . . . . . . . . . . . . . . . . . . . . 39

Typical and Custom Installation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39First-Time Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Installing for the First Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Upgrading from an Earlier Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Automatic Migration of Console and Agent Customizations . . . . . . . . . . . . . . . . 49Determining Whether You Can Migrate KM Customizations . . . . . . . . . . . . . . . . 50Conditions for Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Determining the Location of PATROL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Upgrade Scenarios for PATROL KM for Unix and Linux . . . . . . . . . . . . . . . . . . . . . . . 52

Contents 5

Upgrading Without Saving KM Customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Upgrading and Preserving KM Customizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Migrating Your KM Customizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Preparing to Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Migrating Customizations with the PATROL Configuration Manager . . . . . . . . 55Moving Files from the PATROL_CACHE Directories . . . . . . . . . . . . . . . . . . . . . . . 55Migrating Customizations Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Installing Using the Distribution Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Installing PATROL KM for Unix and Linux Using the Distribution Server . . . . . 60

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

Uninstalling PATROL for Unix and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Determining the Version of the Installation Utility . . . . . . . . . . . . . . . . . . . . . . . . . 64Uninstalling PATROL for Unix and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Uninstalling All Product Files Except Log Files and Configuration Files . . . . . . . 66Uninstalling All Products and Associated Log Files and Configuration Files . . . 67

Where to Go from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Chapter 3 Loading and Configuring PATROL KM for Unix and Linux 71

Preparing to Use PATROL KM for Unix and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Migrating Customized Processes from Previous Versions of PATROL KM for Unix . .

73Using the PATROL Configuration Manager to Migrate Customized Processes . 74Using the pconfig Utility to Migrate Customized Processes. . . . . . . . . . . . . . . . . . 74

Manually Starting the PATROL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Loading and Preloading KMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Determining Which KMs to Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Determining Which KMs to Preload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Loading KMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Verifying What You Have Loaded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Preloading KMs on the PATROL Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Removing KMs from Your Console and Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Unloading KMs from a PATROL Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Removing KMs from the Agent Preload List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Configuring PATROL KM for Unix and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Configuring the PATROL KM for Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Specifying a Data Collection Method for the PATROL KM for Unix . . . . . . . . . . 89Enabling the PRINTER and NETWORK Application Classes . . . . . . . . . . . . . . . . 92

Configuring the PATROL KM for Log Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Configuring Recovery Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

About Recovery Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94PATROL Native Recovery Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Configuring PATROL Native Recovery Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

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

Accessing KM Commands and InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Accessing Online Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

6 PATROL for Unix and Linux Getting Started

Appendix B Troubleshooting PATROL for Unix and Linux Problems 103

Troubleshooting PATROL for Unix Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Data Collection and Parameter Population Problems . . . . . . . . . . . . . . . . . . . . . . 104Error Messages in the

$BEST1_HOME/bgs/monitor/log/bgscollect_portnumber.log . . . . . . . . . . . 105

Index 107

Contents 7


FiguresPATROL for Unix and Linux Select Product and Components to Install Screen

(Typical) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42PATROL for Unix and Linux Select Product and Components to Install Screen when

installing on Unix (Custom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46PATROL for Unix and Linux Select Product and Components to Install Screen when

installing on Windows (Custom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Application Classes that Appear When UNIX3.kml Is Loaded . . . . . . . . . . . . . . . . . . 79Application Classes that Appear When LOG.kml Is Loaded . . . . . . . . . . . . . . . . . . . . 80Application Classes that Appear When EVENT_MANAGEMENT.kml Is Loaded . 80Application Classes that Appear When HISTORY.kml Is Loaded . . . . . . . . . . . . . . . 81COLLECTORS Icon (PSL Data Collection Method) . . . . . . . . . . . . . . . . . . . . . . . . . . . 90DCM Icon (DCM Data Collection Method) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Perform Home Directory Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Figures 9


TablesSystem Requirements for PATROL KM for Unix and Linux . . . . . . . . . . . . . . . . . . . 23PATROL for Unix User Account Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25PATROL for Unix Components that Require setuid root Permissions . . . . . . . . . . . . 26Additional Requirements for the PATROL Perform Data Collector . . . . . . . . . . . . . . 27Settings for the /etc/system File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Versions That You Can Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Choosing an Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Default Values for PATROL Location Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51PATROL for PATROL KM for Unix and Linux .kml Files . . . . . . . . . . . . . . . . . . . . . 76PATROL for Unix and Linux Recovery Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Selecting a Recovery Action Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Recovery Action Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Accessing KM Commands and InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Tables 11


C h a p t e r 1
1 PATROL for Unix and Linux Components and Capabilities
This chapter provides information about components within the PATROL for Unix and Linux product, and how those components can help you to monitor computers in your environment.

Topics covered in this chapter include

PATROL KM for Unix and Linux Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Built-in Recovery Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

PATROL for Unix and Linux Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15PATROL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15PATROL KM for Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16PATROL KM for Log Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16PATROL KM for Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17PATROL KM for History Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18PATROL Perform Data Collector for Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18PATROL Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Related Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 1 PATROL for Unix and Linux Components and Capabilities 13

PATROL KM for Unix and Linux Features

PATROL KM for Unix and Linux FeaturesPATROL for Unix and Linux provides current and historical information through a centralized console so you can easily view and manage your entire Unix and/or Linux environment. You can drill down to view detailed system metrics on all parts of your environment. PATROL also can take corrective action when things go wrong or are about to go wrong—preventing downtime and its costs to your business.

Product features include:

■ monitors a complete range of Unix and Linux operating system parameters including:

— system-wide CPU usage

— disk and I/O usage—tracks usage to locate overused disks

— file system resources—determines disks that are heavily used or running out of space

— kernel resource usage—monitors use of the kernel i-node table, file table, and process table

— log files—monitors the size and content of specified log files

— memory activity—monitors paging, I/O caching, and swapping

— network activity—monitors TCP/IP traffic level

— network traffic—tracks network traffic related to Remote Procedure Call and Network File System

— SMP application—monitors the use of individual CPUs in an SMP system

— system swap files—monitors the percentage of used and free swap space

— user sessions and processes—tracks users on the system

— process presence—monitors the process table and alerts based on the presence or absence of user-defined command text

— composites—CPU > 90 and Page-Outs > 1 can be used to warn of a physical memory deficit

■ provides annotated data points for drilling down into problems


PATROL for Unix and Linux Components

■ provides time-of-day scheduling for executing system commands, PSL commands, and PATROL reconfiguration

■ allows scheduling of blackouts (periods of time in which PATROL stops monitoring)

■ provides base event management capabilities at the server level

Built-in Recovery Actions

PATROL for Unix and Linux provides automated, built-in recovery actions. Recovery actions are corrective actions taken by PATROL when a parameter reaches a set value. You can configure the following recovery action to run automatically or only with operator intervention.

■ FilesystemCleanup

For more information about specific recovery actions, see the online Help, which you can access from the PATROL console, or see “Configuring Recovery Actions” on page 94.

PATROL for Unix and Linux ComponentsThe following sections briefly describes each of the components of the PATROL for Unix and Linux product.

PATROL Agent

The PATROL Agent for Unix is a core piece of the PATROL architecture and is used to monitor computers. PATROL Agents load information from Knowledge Modules (KMs), gather statistics, and send alerts and requested information to the PATROL consoles. PATROL Agents accept requests from the PATROL console and initiate actions based on those requests.

NOTE PATROL for Log Management also provides built-in recovery actions. See the PATROL for Log Management User Guide for information.



Using information from a PATROL KM, a PATROL Agent can

■ detect the presence and status 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 in local files (history)■ implement predefined actions to correct abnormal conditions (recovery actions)

You must install a PATROL Agent on each computer you want to manage. For more information, see the PATROL Agent Reference Manual.

PATROL KM for Unix

The PATROL KM for Unix allows you to monitor and manage system resources in a Unix environment. The PATROL KM for Unix can:

■ monitor the percentage of used and free swap space on disks■ monitor CPU loads across a network■ automatically spawn recovery actions in your Unix and Linux environment■ monitor processes that are running on the system (process presence monitoring) ■ monitor MEMORY utilization and free memory ■ monitor FILESYSTEM capacity

For information about configuring the PATROL KM for Unix, see “Configuring the PATROL KM for Unix” on page 89. Also, see the PATROL Knowledge Module for Unix User Guide or the PATROL Knowledge Module for Unix online Help for information about using the features of this product.

PATROL KM for Log Management

The PATROL KM for Log Management monitors binary and text log files in your environment. The KM provides the capability to monitor the space utilized by the major system log files and search log files for specific text strings and alarm when that string is found. The KM also can automatically spawn recovery actions that can clear the log file(s) or backup the log file(s) before clearing.

Specific functions include:

■ monitor log files with dynamic log file names

■ select logs to be monitored, including log files that have not yet been created



■ generate an alert when a monitored log file cannot be found

■ use regular expressions to create an exclude alert string that prevents alarms and warnings from occurring by filtering out messages in the log that match specified alarm or warning strings

■ use regular expressions to create an exclude to warn alert string that interprets message text that matches alarm strings and moves the text into a warning

■ alert a specific person or group based on a matched string in the log file

■ reset log alerts which occur as a result of updated text in the log file that matches a specified alert string

■ temporarily stop log monitoring during system maintenance by using external control flags

■ view error strings found in the last log update that caused alert and all entries that match that error string from the last log update.

For information about configuring the PATROL KM for Log Management, see the PATROL for Log Management User Guide. Also, see the PATROL Knowledge Module for Log Management online Help for information about using the features of this product.

PATROL KM for Event Management

PATROL 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 (email, paging, trouble-ticket, or custom notification) 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 email client, paging solution, compiled executable, or script. Sample scripts are provided.

■ integrate with the AlarmPoint enterprise notification software using provided scripts

PATROL KM for History Loader

The PATROL Knowledge Module for History Loader consists of application definitions, commands, and parameters associated with extracting and loading PATROL parameter history into your RDBMS (relational database management system). Once PATROL history data is stored in an RDBMS, you can perform complex analysis and statistical planning on all monitored activity.

By allowing you to export, store, review, and analyze history data, the PATROL Knowledge Module for History Loader helps you detect problems, optimize systems, analyze trends, plan capacity, and manage multiple hosts simultaneously. This ability can help you ensure that your systems run efficiently 24 hours a day.

For information about installing and configuring the PATROL Knowledge Module for History Loader, see the PATROL History Loader Knowledge Module User Guide.

PATROL Perform Data Collector for Unix

The PATROL Perform Data Collector for Unix collects kernel-level operating system data for Unix or Linux computers in your enterprise.

See the following documents for more information about the PATROL Perform Data Collector for Unix:

■ PATROL for Unix Performance Getting Started ■ PATROL for Unix and Linux Release Notes

PATROL Security

This release of the PATROL for Unix and Linux product provides several options to secure your Unix environment. See “PATROL Security Levels” on page 38 for more information on setting up security within your monitored environment.

For detailed information about PATROL security, see the PATROL Security User Guide.


Related Documentation

Related DocumentationFor additional information about PATROL KM for Unix and Linux product components, see the following documentation

■ PATROL Agent Reference Manual■ PATROL Knowledge Module for Unix and Linux User Guide■ PATROL Knowledge Module for Unix and Linux Release Notes■ PATROL Knowledge Module for Event Management User Guide■ PATROL History Loader Knowledge Module User Guide■ PATROL Log Management Knowledge Module User Guide■ PATROL Security User Guide■ PATROL Security Release Notes■ PATROL Knowledge Module for Event Management online Help■ PATROL Knowledge Module for Unix online Help■ PATROL Knowledge Module for Log Management online Help■ PATROL Knowledge Module for History Loader online Help

For information about the PATROL KM for Unix and Linux parameters, see the online Help systems.

For additional information about PATROL, see the following documentation:

■ PATROL Console for Microsoft Windows User Guide, Volume 1■ PATROL Console for Microsoft Windows User Guide, Volume 2■ PATROL Console for Microsoft Windows User Guide, Volume 3■ PATROL Console for Unix User Guide■ PATROL Central Operator - Microsoft Windows Edition Getting Started■ PATROL Central Operator - Web Edition Getting Started■ PATROL Agent Reference Manual■ PATROL Script Language Reference Manual Volume I - PSL Essentials ■ PATROL Script Language Reference Manual Volume 2 - PSL Functions ■ PATROL Script Language Reference Summary ■ PATROL Agent Reference Manual ■ Command Line Interface Reference Manual■ API Reference Manual ■ Installation Utility Reference Manual ■ Help for your PATROL Console


Related Documentation

To view the complete PATROL documentation library, visit the support page on the BMC Software website at http://www.bmc.com/support_home.html. Log on and select a product to access the related documentation. (To log on if you are a first-time user and have purchased a product, you can request a permanent user name and password by registering at the Customer Support page. To log on if you are a first-time user and have not purchased a product, you can request a temporary user name and password from your BMC Software sales representative.)

The complete PATROL documentation library is also available on the PATROL documentation CD that is included with major releases of the PATROL Console and Agent.


http://www.bmc.com/support.html

C h a p t e r 2
2 Installing and Migrating PATROL KM for Unix and Linux
This chapter provides the information that you need to install and migrate PATROL KM for Unix and Linux. For additional information about the PATROL installation process, see the PATROL Installation Reference Manual. The following topics are discussed in this chapter:

Verifying Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23System Requirements for PATROL for Unix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Additional Requirements Needed to Install and Use the PATROL Perform Data

Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Checking for Product Patches or Fixes Before Installing. . . . . . . . . . . . . . . . . . . . . 33Determining How to Install Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Determining the Version of the Installation Utility . . . . . . . . . . . . . . . . . . . . . . . . . 34Target Computers and Their Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Determining Where to Install KMs Based on Architecture. . . . . . . . . . . . . . . . . . . 36Mounting a CD on Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

PATROL Security Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Checking Security Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Assessing and Implementing a Different Security Level . . . . . . . . . . . . . . . . . . . . 39

Typical and Custom Installation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39First-Time Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Installing for the First Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Upgrading from an Earlier Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Automatic Migration of Console and Agent Customizations . . . . . . . . . . . . . . . . 49Determining Whether You Can Migrate KM Customizations . . . . . . . . . . . . . . . . 50Conditions for Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Determining the Location of PATROL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Upgrade Scenarios for PATROL KM for Unix and Linux . . . . . . . . . . . . . . . . . . . . . . . 52Upgrading Without Saving KM Customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Upgrading and Preserving KM Customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Migrating Your KM Customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53


Preparing to Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Migrating Customizations with the PATROL Configuration Manager . . . . . . . . 55Moving Files from the PATROL_CACHE Directories . . . . . . . . . . . . . . . . . . . . . . . 55Migrating Customizations Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Installing Using the Distribution Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Import a CD Image or Customized Installation Package into the Distribution

Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Installing PATROL KM for Unix and Linux Using the Distribution Server . . . . . 60

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

Uninstalling PATROL for Unix and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Determining the Version of the Installation Utility . . . . . . . . . . . . . . . . . . . . . . . . . 64Uninstalling PATROL for Unix and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Uninstalling All Product Files Except Log Files and Configuration Files . . . . . . . 66Uninstalling All Products and Associated Log Files and Configuration Files . . . 67

Where to Go from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69


Verifying Installation Requirements

Verifying Installation RequirementsBefore you install PATROL for Unix, make sure that your systems meet all requirements outlined in this section.

Supported Platforms

See the PATROL for Unix Release Notes for a list of supported platforms. In addition, check the product page for version 8.3.06 of PATROL KM for Unix and Linux on the BMC Software Customer Support website. Technical Bulletins on the product support page may contain information about platforms that were supported after PATROL for Unix 8.3.06 was released.

System Requirements for PATROL for Unix

Before installing the product, verify that the target computers meet the requirements listed in Table 1.

Table 1 System Requirements for PATROL KM for Unix and Linux (Part 1 of 2)

Resource Requirements Comments

browser for installing the product

This product uses Common Installer 7.5.20, which requires a browser.

For a list of supported browsers, see the PATROL Installation Reference Manual.

browser to support online Help for PATROL for Unix Console

Use Netscape Navigator version 3.01–4.78 to use online Help with PATROL for Unix.

see “Browser Version Required for Viewing PATROL Console for Unix Help” on page 61

disk space

219-MB for PATROL Agent for Unix without components and KMs

115-MB for PATROL Console for Unix without components and KMs

less than 2-MB for PATROL KM for Unix NA

less than 1-MB for PATROL KM for Log Management

NA

less than 1-MB for PATROL KM for Event Management

NA

installing into a PATROL 3.6.50 Unix environment

You must launch the installation utility from the command line and use the -releaseversion option.

see “Upgrading from an Earlier Version” on page 49



installing into a Unix environment without a browser

You must launch the installation utility from the command line and use the -serveronly command line option.

See either “To Install Using the Typical Installation Type” on page 41 or “To Install Using the Custom Installation Type” on page 44.

license You must have a valid demonstration license or a permanent license to run your PATROL products. A valid demonstration license is installed automatically and is typically good for 30 days.

If you do not have a permanent license, contact your BMC Software sales representative or the BMC Software Contract Administration department for licensing information.

monitor 256-color display screen resolution should be set to at least 600 x 800 pixels

network TCP/IP network communications must be available

NA

ports If you are installing an agent or console with PATROL KM for Unix and Linux, you must specify the port number to connect to all the agent computers.

The default port number for the PATROL Agent is 3181.

random access memory (RAM)

32-MB for PATROL Agent NA

48-MB for PATROL Console for Unix NA

PATROL Perform Collector

versions 7.1.41 or higher NA

security levels “PATROL Security Levels” on page 38 The PATROL Security Level is set during the installation of the PATROL infrastructure components. If your product contains the PATROL Agent, you will have an opportunity to select the security level. Make sure that the level that you select/accept is compatible with the rest of your enterprise’s PATROL installation.

Knowledge Modules (KM) inherit the security level. Products that consist of only KMs do not provide an opportunity to change the security level during installation.

Do not use Security level 3 or higher if you will be using Enterprise Configuration or the PATROL Advisor. These security levels require passwords to be entered every time the host is accessed.

accounts dedicated PATROL account See “Accounts” on page 25 for information about user account requirements.

Table 1 System Requirements for PATROL KM for Unix and Linux (Part 2 of 2)




Accounts

You must create a dedicated user account before PATROL is installed. Use this account as your PATROL default account. The PATROL account must conform to the following guidelines:

Components that Require setuid Permissions

Table 3 on page 26 lists the components which will require setuid root permissions. The table also provides an explanation of why each component needs setuid root permissions.

Table 2 PATROL for Unix User Account Requirements

Resource Requirements

account file customizations the user account .login, .profile, .cshrc, and .kshrc files should not contain any customizations such as aliases or nondefault prompts

directory permissions the user account must have permission to create directories and write the installation logs to the $HOME and /tmp directories on the computer where you are installing products

file systems (recommended) install PATROL on local partitions

If PATROL is installed on NFS-mounted partitions, the root account must have root access permissions on the NFS server.

IBM AIX computers on AIX computers, the PATROL installation account must be a member of the adm group

root account do not use the root account to install PATROL for Unix and Linux; this could create security risks

The account must have access to a root account on the computer where PATROL will be installed.

setuid root permissions see “Components that Require setuid Permissions” on page 25 for information about PATROL for Unix components that will need setuid root access

umask setting ensure that the umask setting for the installation account is set to 022

NOTE Processes initiated by KM menu commands will prompt you for the root password.


Additional Requirements Needed to Install and Use the PATROL Perform Data Collector


The PATROL Perform Data Collector allows you to collect and analyze kernel-level data from Unix and Linux operating systems in your environment. If you want to install and use the PATROL Perform Data Collector, you must meet the additional system requirements listed in Table 4 on page 27.

For more information about PATROL Perform Data Collector system requirements, see the PATROL for Unix Performance Getting Started.

Table 3 PATROL for Unix Components that Require setuid root Permissions

Component Uses setuid root permissions to

PATROL Foundation Components

PATROL Console validate user name and password information by accessing the /etc/passwd file

PATROL Agentvalidate the user name and password

impersonate (via su) other user accounts to execute various KM commands

SNMP Master Agent (snmpmagt)

listen on privileged port numbers (port numbers that are less than 1024)

PATROL KM for Unix Components

PATROL Perform Data Collector (bgscollect)

read into kernel memory (/dev/mem and /dev/kmem)

read certain device files

procstat command access kernel memory

FILESYSTEM applicationmount and unmount file systems

clean up file systems (this is a recovery action)

NETWORK applicationdelete hosts from the address resolution protocol (ARP) cache

run Unix to Unix copy (UUCP) utilities

NFS application reset NFS counters to zero

PRINTER application

start and stop printers

start and stop print queues

delete print jobs

move print jobs



Table 4 Additional Requirements for the PATROL Perform Data Collector (Part 1 of 2)


Collect Data Repository

25-MB to 100-MB on each node this requirements must be met on all nodes

Space requirements will vary depending on factors in your environment (such as the type of data collected, and the frequency of data collection).

directory (history data repository)

you must specify a name for the history data repository

if a directory name is not specified, you will not be able to use the history features of the investigative node

/etc file system at least 3-MB of free disk space on all systems

all users must have execute (x) permission

These requirements apply to both managing and remote nodes.

file system BMC Software recommends using a local file system for the history and collected data repositories

if the data repositories must reside on a Unix network file system (NFS), make sure that rpc.lockd and rpc.stat are running on the client and the server

History and UDR Repository

at least 75-MB this requirement must be met on all nodes

libraries ensure that the LANG variable for your systems is set to the correct locale that you want to use

By default, the LANG environmental variable for most systems is set to English, unless you are working on an internationalized platform. To use a different locale than the one on your computer, you must manually set the LANG environmental variable to the locale you want to use.

The LANG variable must correspond to the correct locale and alias for your platform. See the PATROL Installation Release Notes for a list of the locales and aliases for supported platforms in this release.

naming conventions

you must use full path names when you specify directories during the installation process

do not use the tilde (~) or relative path names (./.) during the installation



Shared Memory and Semaphore Resources for the PATROL Perform Data Collector

Perform Agent and the Collect programs require semaphores and shared memory segments on all computers. PATROL for Unix collectors require one semaphore and one shared memory segment for each metric group per instance and each collector per instance.

Resource limits may be set to low values on your system, particularly on Solaris. This can be a problem, especially if an RDBMS is running on the same node, because RDBMS systems also use these resources. See your system administrator for help in setting semaphore and memory segment parameters.

On Sun Solaris Systems

On Solaris, you can reconfigure these values without recompiling the kernel by editing the /etc/system file. The following table contains a list of entries in /etc/system and an explanation of each value. All entries in /etc/system must be less than 80 characters, otherwise they might disable the kernel.

Unix shells Bourne shell The installation script uses the Bourne shell; the /bin/sh file must be available for the installation script to run properly.

Korn shell the PATROL Perform Data Collector requires that the Korn shell be installed on all systems it is monitoring

On Linux operating systems the Korn shell is not installed automatically, but it is available in the Linux operating system media. You must install the ksh package.

shared memory segments and semaphores

you must set shared memory segments and semaphores to use the PATROL Perform Data Collector

See “Shared Memory and Semaphore Resources for the PATROL Perform Data Collector” on page 2-28.

NOTE Because these changes alter kernel settings, you must restart the system for the changes to take effect.

Table 4 Additional Requirements for the PATROL Perform Data Collector (Part 2 of 2)




BMC Software recommends that you reset these values after installation, as indicated in Table 5. The values in the /etc/system entry column represent a default system configuration installation. Increasing these limits does not incur any additional overhead, because they are used only when required. If your system is already set to higher values, increase the values by an amount corresponding to the increase shown in the table.

Setting Boot Time Values for Shared Memory and Semaphore Parameters

When setting shared memory and semaphore parameters, if the boot time value is less than the recommended number, you must increase it. To evaluate whether you need to increase the value of a parameter’s boot time value, use the guidelines in (Table 5).

NOTE Instance can be a system or an RDBMS collect.

Table 5 Settings for the /etc/system File (Part 1 of 2)

For Parameter... Which is... Do This... Example

IPC Semaphores

semsys:

seminfo_semmns

Number of semaphore identifiers, system-wide

Add (50 + 50 multiplied by the number of instances of instances) to the current value

If the current value on the machine is 100 and you have one system collector and one Oracle collector running on the machine, set the value to 250

Note: Perform allocates two semaphores per ID so use 50 instead of 25

semsys:

seminfo_semmap

Number of entries in the semaphore map

Set equal to semsys:seminfo_semmni + two

If semsys:

seminfo_semmni was set to 256, set semsys:

seminfo_semmap equal to 258

Note: Obsolete in Solaris 8 and beyond

semsys:

seminfo_semmni

Number of semaphore identifiers (semaphore sets), system-wide

Add (25 + 25 multiplied by the number of instances) to the current value

If the current value of the machine is 100 and you will be running one system collector set the value to 150



On Solaris 2.7 and Later Systems

Issue the /etc/sysdef -i command to view the current settings. See man pages for more information on the sysdef command. For Solaris, you also need to review the settings for the sem-mns and sem-map parameters.

For sem-mns (maximum number of semaphores available on the system, default value =60), increase the value by 140.

semsys:

seminfo_semmnu

Maximum number of undo structures, system-wide

No specific recommendation. PATROL Perform does not use undo structures

As a general rule, you may want to set seminfo_semmnu equal to seminfo_semmni to provide for an undo structure for each semaphore

semsys:

seminfo_semmsl

The maximum number of semaphores per unique identifier

No specific recommendation. PATROL Perform will attach two semaphores per identifier.

semsys:seminfo_semmsl should remain at its current value

semsys:

seminfo_semopmseminfo_semumeseminfo_semvmxseminfo_semaem

No specific recommendations for any of these four semaphore settings. They have no impact on the operation of PATROL Perform.

IPC Shared Memory

shmsys:

shminfo_shmm

The maximum size of a shared memory segment.

No specific recommendation. The default value is high enough for PATROL Perform.

PATROL Perform allocates small segments, so this value will never be a limiting factor.

shmsys:

shminfo_shmmin

Minimum size of an IPC shared memory segment that can be created

The system default of 1 is recommended.

shmsys:shminfo_shmmni should always be set to 1

shmsys:

shminfo_shmmni

System wide limit on the number of shared memory segments


If the current value of the machine is 100 and you will be running one system collector, set the value to 150

shmsys:

shminfo_shmseg

Limit on the number of shared memory segments that one process can create


If the current value of the machine is 100 and you will be running one system collector, set the value to 150

Table 5 Settings for the /etc/system File (Part 2 of 2)

For Parameter... Which is... Do This... Example



For sem-map (maximum number of entries in the semaphore map, default value=10), increase the value by 90.

On Linux Systems

The shared memory and semaphore requirements on Linux are the same as the requirements for other Unix variants.

If there are not other shared memory intensive applications running on the Linux machine (such as Oracle) it will not typically be necessary to change the default IPC kernel settings under Linux. The current shared memory settings on the machine can be seen by running the following command:

ipcs -l

Shared memory and semaphore settings can be changed in the Linux kernel by editing the kernel settings files in /proc/sys/kernel. The files are: sem, shmall, shmmax, shmmni. The shm* files contain a single value that equates to the setting on the machine. The sem file has four values separated by tabs. Updating these files changes the specified setting in the running kernel. However, the default kernel limits are sufficient to run Perform on the machine.

On Hewlett-Packard Systems

On HP-UX you can use the SAM tool to change the settings for resource limits and to reconfigure the kernel. SAM will relink the kernel. See the man pages for more information on using SAM for this purpose. Use the recommended values shown in Table 5 on page 29 to adjust the settings for HP–UX.

On IBM AIX Systems

This does not apply to AIX, because the system dynamically manages resource limits.

On HP Tru64 (Digital UNIX) Systems

On a HP Tru64 (Digital UNIX) system, perform the following steps:

1 Issue /sbin/sysconfigdb -l ipc to view the current settings. See man pages for more information on the sysconfigdb command.

NOTE HP recommends that you do not attempt to edit the /etc/sysconfigtab file. The sysconfigdb utility will automatically make any changes available to the kernel and will preserve the structure of the file so that future upgrades will be correctly merged.


Preparing for Installation

2 Look at the current values, and then refer to Table 5 on page 29 for the recommended values. Increase your values to those recommended in Table 5.

3 Synchronize the file with the systems configuration data base by entering the following command:

/sbin/sysconfigdb -s

4 Restart the system.

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

Installation Prerequisites

Before you install, you must

■ ensure that all system requirements are met (see page 23)■ determine how to install products (see page 33)■ ensure you are using the appropriate version of the installation utility (see page 34)■ understand target machines and their roles (see page 34)■ choose between Typical and Custom installation options (see page 39)■ understand PATROL security options (page 38)

Turn off pop-up blocking software before installing

Before installing the PATROL for Unix and Linux product or any of its components, you must turn off pop-up blocking software. Pop-up blocking software interferes with the functioning of the installation utility.



Checking for Product Patches or Fixes Before Installing

Product fixes or patches are often available through the BMC Software website. Patches correct problems that are found after a product is released. BMC Software recommends that you check the product page for version 8.3.06 of PATROL KM for Unix and Linux on the BMC Software Customer Support Web page to determine whether a patch is available before you begin installing a product.

Determining 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 Unix and Linux and a PATROL Agent on each computer that you want to monitor, and PATROL KM for Unix and Linux 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 for Unix and Linux 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. 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 image’s 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.

Determining the Version of the Installation 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, or may not result in a supported installation.

To determine the version of an installation utility, perform the following steps:

1 Open a command prompt.

2 Navigate to the directory where the installation utility is located.

3 Type setup.sh -v and press Enter.

The installation script displays version information at the command prompt.

Target Computers and Their Roles

The installation utility prompts you to select the roles performed by the computer on which you are installing BMC Software products (the target computer). Before beginning the installation process, review the following definitions of the roles that are presented in the installation utility and decide which of these roles is performed by each computer in your environment.

NOTE ■ To create an installable image that you can install on multiple Windows or Unix operating

systems, you must launch the installation utility from a command line and use the -repository_oslist command line option to specify the operating systems on which you want the image to install. You can also use the -repository_oslist option to create an image on a Windows computer to be installed on Unix computers or create an image on a Unix computer to be installed on Windows computers.

■ You cannot create an installable image that can be installed on both Windows and Unix computers. You must create one image for all Windows operating systems and one image for all Unix operating systems; however, you can create the images from either a Windows or Unix computer.



Roles Performed by Computers in the PATROL Architecture

The roles performed by computers in the PATROL Architecture are

■ Console Systems (also referred to as console computers) host user desktop applications such as consoles, user interfaces, viewers, and browsers. Select this option if the computer to which you are installing will perform any of the following roles:

— monitor, manage, and develop KMs on Unix by using a PATROL Console for Unix (PATROL 3.x architecture)

— monitor, manage, and develop KMs on Windows by using a PATROL Console for Windows (PATROL 3.x architecture)

■ Managed Systems (also referred to as agent computers) host software that manages the resources on the computer, such as a PATROL Agent, and PATROL Knowledge Modules. Select this option if the computer to which you are installing will perform any of the following roles:

— host a PATROL Agent (works with both the PATROL 3.x and PATROL 7.x architecture)

— host KMs and components that contain the knowledge that PATROL uses to monitor the resources on this computer

■ A Common Services (new with PATROL 7.x architecture) computer hosts services that are shared among managed systems and console systems. You can install each of these common services on any computer in the network. Select this option if the computer to which you are installing will perform any of the following roles:

— host the PATROL Central Operator – Web Edition (PATROL 7.x architecture) Web server

— host the PATROL Console Servers

— host the RTservers

Additional Information

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

■ PATROL Central Operator - Web Edition Getting Started

■ PATROL Central Operator - Microsoft Windows Edition 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 Guide

■ PATROL Console Server and RTserver Getting Started

Determining Where to Install KMs Based on Architecture

PATROL 3.x and PATROL 7.x architectures differ as to which target computers store Knowledge Modules and how much KM information is required by each type of system. During installation, ensure that you select the appropriate types of systems according to the following information:

PATROL 3.x

Install KM packages to computers whose roles are defined as Managed Systems and Console Systems.

A PATROL 3.x environment includes the following components:

■ PATROL Agent 3.x runs on Managed Systems.■ PATROL Console for Windows or PATROL Console for Unix 3.x runs on Console

Systems.

PATROL 7.x

For PATROL Central Operator – Microsoft Windows Edition, install KM packages to Console Systems, Common Services Systems, and Managed Systems.

For PATROL Central Operator – Web Edition, install KM packages to Common Services Systems and Managed Systems.

A PATROL 7.x environment includes the following components:

■ PATROL Agent 3.5 or 3.6 runs on Managed Systems.■ RTserver runs on Commons Services Systems.■ PATROL Console Server runs on Common Services Systems.■ PATROL Central Operator – Microsoft Windows Edition, PATROL Central

Operator – Web Edition, or both run on Console Systems.



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

Mixed PATROL 3.x and 7.x Environment

A mixed PATROL 3.x and 7.x environment includes the components from both a PATROL 3.x environment and a PATROL 7.x environment.

Mounting a CD on Unix

The following sections provide information about the mount commands you must use to mount the PATROL product CDs on your Unix system.

Mounting the CD drive

1 Log on as root.

2 Insert the CD into the CD drive.

3 Use the mount command appropriate to your platform to mount the CD.

If a problem occurs, consult your system administrator or read the man page for mount.

4 Log off.

NOTE In this procedure, the root directory for the CD drive is called /cdrom. This directory might be different for your computer, depending on how your system administrator has configured the device. If you have a question about the location or setup of your CD drive, please contact your system administrator.

Platform Mount Command

AIX mount -r -v cdrfs /dev/cd0 /cdrom

Tru64 /sbin/mount -t cdfs /devices/disk/cdrom_device /cdrom

HPUX-PA1.0Version 10.20 or higher

mount -F cdfs -o ro /dev/dsk/drive_for_cdrom/cdrom

Linux mount /dev/cdrom /path_to_target_mount_point

Solaris Volume Manager (/usr/sbin/vold) automatically mounts. Otherwise, use mount -r -F hsfs /dev/sr0 /cdrom


PATROL Security Levels

Mounting the CD Drive for an NFS Client

Before you begin, mount the CD on the NFS Server as described . Ensure that the file system is exported as necessary by the NFS Server.

Most platforms use the exportfs command to export a local file system, including a CD file system. However, Solaris platforms use the share command.

To mount the CD on an NFS client, follow these steps:

1 Log on as root.

2 Create a directory on your local computer (for example, /mnt/cdrom or /mnt/cdrom/cdrom0 for Solaris) as the mount point for the CD on the remote host computer.

3 Use the mount command appropriate to your platform to mount the CD.

If a problem occurs, consult your system administrator or read the man page for mount.

4 Log off.

PATROL 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.

Platform Mount Command

AIX, Tru64, HPUX-PA1.0

mount host:/cdrom /mnt/cdrom

Linux mount host:/path_to_file_system_to_be_exported /path_to_target_mount_point

Solaris mount host:/cdrom/cdrom0 /mnt/cdrom/cdrom0

NOTE 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.


Typical and Custom Installation Types

Checking 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. Your previous PATROL installations will reside in $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.

Assessing 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. If you want to implement a new security level after having previously installed PATROL security, see the PATROL Security User Guide for instructions.

Typical and Custom Installation TypesThe installation utility prompts 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.

esstool policy -a


First-Time Installation

■ 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 Unix and Linux 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 components and KMs that you select.

First-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 39.

Installing for the First Time

You can install PATROL KM for Unix and Linux 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 Unix and Linux. See page 39 for guidelines for using each installation type.

NOTE If you are installing PATROL KM for Unix and Linux 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 for Unix and Linux and overwrite your existing installation.

If you do not want to overwrite your existing installation, use Custom so that you can clear the selection of the agent or console product.



Before you begin

■ 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 and be logged in as the PATROL default account.

■ If you want to install PATROL KM for Unix and Linux on a computer running Unix but that does not have a browser installed, you must have access to a second computer that runs a browser that is supported by the installation utility.

■ Mount the CD-ROM on a Unix or Linux computer. See “Mounting a CD on Unix” on page 37.

To Install Using the Typical Installation Type

1 From the installation PATROL for Unix CD or from an installation image that has been electronically downloaded from an EPD site and extracted, run setup.sh.

If you are installing into a Unix environment without a browser, perform the following steps to launch the installation utility:

A From a command line, change to the directory where the installation utility is located and enter the following command to start the installation Web server:

./setup.sh -serveronly

A message box is displayed that shows the URL to use to connect to the installation Web server.

B On another computer with a browser, start the browser.

C Connect to the installation Web server from the browser to start the installation utility by using the URL that is displayed in the message box on the computer on which you are installing the product.

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

NOTE You can download the complete PATROL for Unix and Linux product solution or individual product components from the product EPD Web site.



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

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

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

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

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

By default, PATROL for Unix will be installed into the /opt/bmc directory.

7 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 PATROL Console for Unix, select Console Systems.

■ If you are installing to a computer that hosts or will host a PATROL Agent or PATROL KMs, 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.

For more information, see “Target Computers and Their Roles” on page 34.

8 From the Select Products and Components to Install window, select the items that you want to install (see Figure 1) and click Next.

See “PATROL for Unix and Linux Components” on page 15 for information about each of the product components you can install. Each computer that you want to monitor must have a PATROL Agent installed on it to collect data. Computers may have one or more PATROL KMs installed on them, depending on what you want to monitor on the computer.

Figure 1 PATROL for Unix and Linux Select Product and Components to Install Screen (Typical)



9 In the Temporary space for installing external components screen, enter or browse to a directory (for example, C:\temp for Windows or /tmp for Unix) on your computer that can serve as a storage location where the product files can be copied temporarily before being installed on your computer and click Next.

If the directory that you enter does not exist, the installation utility will attempt to create it. The installation utility creates then begins to copy the files required for the product installation from the current CD image. This process may take a few moments.

The Additional CDs Needed screen is displayed and lists in sequence the CDs required to complete the installation.

10 Insert the CD that is indicated on the Additional CDs Needed screen, then enter the drive letter or mount volume in the space provided. If you copied the CD to your computer, enter the directory where the image is located and click Next.

11 When the next Additional CDs Needed screen is displayed, follow the directive to place the original product CD back in the CD-ROM drive and click Next.

12 {Unix installations only] If the Provide the System Root Account Properties window is displayed, enter the ID and password for the root account and click Next.

NOTE Make sure that the temporary directory that you specify has adequate disk space to make a copy of all the components required by the product that you are installing.

After the installation is complete, the installation utility removes the copied files and the temporary directory.

NOTE On Unix systems, you cannot eject removable media while the media is being accessed. To swap CDs, you may need to exit the installation utility, then, from a command line, cd to / and restart the utility by specifying the absolute path; for example, /mnt/cdrom/setup.sh.

NOTE ■ If you wish to continue without specifying the root password, then select Next. You

will need to complete the root configuration at a later time before the products you selected will run correctly.

■ If you need to run configuration scripts, you will need to complete the root configuration or use a sudo account and password in instead of root authorization. See the Installation Utility Reference Manual for details.



13 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 25).

14 In the Review Selections and Install window, review the selections carefully to ensure that they are correct:

■ If you want to change your selections, click Back and make those changes. ■ If the selections are correct, click Start Install to start installing.

A status window opens that contains current messages, current milestones, and percentage complete.

15 When the status window reports that the installation is 100% complete, click Next to view the results window. (Next does not appear until the installation is 100% complete.)

16 (Optional) In the results window, click View Log to review the details of the installation.

17 Click Finish to close the installation utility.

To Install Using the Custom Installation Type

1 From the installation PATROL for Unix CD or from an installation image that has been electronically downloaded from an EPD site and extracted, run setup.sh.

If you are installing into a Unix environment without a browser, perform the following steps to launch the installation utility:

A From a command line, change to the directory where the installation utility is located and enter the following command to start the installation Web server:

./setup.sh -serveronly

A message box is displayed that shows the URL to use to connect to the installation Web server.

B On another computer with a browser, start the browser.

NOTE You can download the complete PATROL for Unix and Linux product solution or individual product components from the product EPD Web site.



C Connect to the installation Web server from the browser to start the installation utility by using the URL that is displayed in the message box on the computer on which you are installing the product.

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

3 In the Review License Agreement window, review the license agreement, select Accept, and click Next to continue.

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

5 From the Select Type of Installation Window, select Custom and click Next.

6 In the Specify Installation Directory window, enter the path up to, but not including your current installation directory and click Next.

For example, to install PATROL for Unix into the directory /opt/bmc/PATROL3-4, enter PATROL3-4 in the PATROL 3.x Product Directory field.

If your installation directory is at the root level (such as /opt/bmc), do not enter anything into the PATROL 3.x Product Directory field.

You will specify the PATROL product directory in step 12 on page 47.

7 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 PATROL Console, select Console System.

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

■ 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.

For more information, see “Target Computers and Their Roles” on page 34.

8 From the Select Products and Components to Install screen, select the items that you want to install (see Figure 2 on page 46) and click Next.



See “PATROL for Unix and Linux Components” on page 15 for information about each of the product components you can install. Each computer that you want to monitor must have a PATROL Agent installed on it to collect data. Computers may have one or more PATROL KMs installed on them, depending on what you want to monitor on the computer.

Figure 2 PATROL for Unix and Linux Select Product and Components to Install Screen when installing on Unix (Custom)

Figure 3 PATROL for Unix and Linux Select Product and Components to Install Screen when installing on Windows (Custom)

9 In the Temporary space for installing external components screen, enter or browse to a directory (for example, C:\temp for Windows or /tmp for Unix) on your computer that can serve as a storage location where the product files can be copied temporarily before being installed on your computer and click Next.

NOTE If you are installing PATROL for Unix from a Windows Server, the PATROL Agent is not listed a selectable item in the Select Products and Components to Install screen, as shown in Figure 3 on page 46. The PATROL Agent is not listed because the PATROL Agent that is a component of PATROL for Unix is a Unix agent.

If you want to install the PATROL Agent on Windows Servers, you must install the Windows agent from the PATROL for Microsoft Windows Servers product.



If the directory that you enter does not exist, the installation utility will attempt to create it. The installation utility creates then begins to copy the files required for the product installation from the current CD image. This process may take a few moments.

The Additional CDs Needed screen is displayed and lists in sequence the CDs required to complete the installation.

10 Insert the CD that is indicated on the Additional CDs Needed screen, then enter the drive letter or mount volume in the space provided. If you copied the CD to your computer, enter the directory where the image is located and click Next.

11 When the next Additional CDs Needed screen is displayed, follow the directive to place the original product CD back in the CD-ROM drive and click Next.

12 In the Provide the PATROL 3.x Product Directory window, enter in the PATROL 3.x Product Directory field the directory in which you want to install PATROL KM for Unix and Linux.

This directory is appended to the base directory path that is shown in the BMC Products Installation Directory field. The installation directory was entered in step 6 on page 45.

13 {Unix installations only] If the Provide the System Root Account Properties window is displayed, enter the ID and password for the root account and click Next.

NOTE Make sure that the temporary directory that you specify has adequate disk space to make a copy of all the components required by the product that you are installing.

After the installation is complete, the installation utility removes the copied files and the temporary directory.

NOTE On Unix systems, you cannot eject removable media while the media is being accessed. To swap CDs, you may need to exit the installation utility, then, from a command line, cd to / and restart the utility by specifying the absolute path; for example, /mnt/cdrom/setup.sh.

NOTE If you wish to continue without specifying the root password then select Next. You will need to complete the root configuration at a later time before the products you selected will run correctly.



14 If the PATROL Default Account Properties window appears, 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 25).

15 If the Complete the Confirm BMC Startup Information window appears, perform the following steps:

A In the Specify the Current Agent Port Number field, enter the port number that you want the PATROL Agent to use. The default is 3181.

B In the Restart the PATROL agent automatically? field, select the appropriate option:

■ If you want the installation utility to restart the PATROL Agent after the installation is complete, select Yes.

■ If you want to restart the PATROL Agent manually after the installation is complete, select No.

16 In the Review Selections and Start Install window, review the selections carefully to ensure that they are correct:

■ If you want to change your selections, click Back and make those changes. ■ If the selections are correct, click Start Install to start installing.

A status window opens that contains current messages, current milestones, and percentage complete.

17 When the status window reports that the installation is 100% complete, click Next to view the results window. (Next does not appear until the installation is 100% complete.)

18 (Optional) In the results window, click View Log to review the details of the installation.

NOTE This Complete the Confirm BMC Startup window described in step 15 may not be displayed if you are not installing into a managed system.

NOTE If your previous installation used a different port number, change the default to the current port number for the PATROL Agent.


Upgrading from an Earlier Version

19 Click Exit to close the installation utility.

Where to go from here

See Chapter 3, “Loading and Configuring PATROL KM for Unix and Linux.”

Upgrading from an Earlier VersionIf you have a previous version of PATROL KM for Unix and Linux installed on the target computer, you have the following options for upgrading to the new version of PATROL KM for Unix and Linux:

■ “Upgrading Without Saving KM Customizations” on page 53■ “Upgrading and Preserving KM Customizations” on page 53

Installation Script Information for the Perform Data Collector

If you manually run the configuration script for the Perform Data Collector after you have completed an over-the-top installation, be sure to use the b1config installation script. Be careful not to use an older configuration script that the over-the-top installation may have left behind.

Automatic Migration of Console and Agent Customizations

Only customizations to Knowledge Modules must be migrated.

Whether you choose to save and migrate your KM customizations or not, the customizations you have made to

■ agents—stored in the agent configuration file■ consoles—stored in the console cache files

are preserved and incorporated into the new version automatically.

NOTE Customized Knowledge Modules and PSL files are also stored in the cache but they are not automatically preserved and incorporated.



Determining Whether You Can Migrate KM Customizations

Before migrating customizations, you must determine whether or not your customizations to PATROL KM for Unix and Linux can be migrated to the new version of PATROL KM for Unix and Linux. See Table 6 to determine whether migration is supported for your current version of PATROL KM for Unix and Linux. If migration is supported, choose one of the following installation procedures to migrate your customizations:

■ migrating customizations using the PATROL Migration Tools (page 55)■ migrating customizations manually (page 57)

NOTE The PATROL KM for Event Management has no migration path from versions prior to 2.6.00. Migration of the PATROL KM for Event Management is not required because the configuration information, including parameter settings, is stored in the PATROL Agent configuration database and is backward compatible. See the PATROL Knowledge Module for Event Management User Guide for more information about upgrading the PATROL KM for Event Management.

Table 6 Versions That You Can Migrate

Component Versions

PATROL KM for Unix 8.3.06 or later

PATROL KM for Event Management N/A

PATROL KM for Log Management 1.1.00 or later

PATROL Knowledge Module for History Loader

1.4.06 or later



Conditions for Upgrading

Use Table 7 to help you choose an upgrade procedure.

Determining the Location of PATROL

During the installation process, the PATROL Installation Utility records where it installs PATROL components in environment variables. To function properly, various components of the PATROL product, such as the migration tools, require the information stored in these variables. Two important variables are PATROL_HOME and PATROL_CACHE.

Throughout this section, all references to PATROL_HOME represent $PATROL_HOME and all references to PATROL_CACHE represent $HOME/patrol.

Default Values for PATROL Location Variables

If you do not specify a location for the PATROL installation, the installer uses the following preprogrammed default locations and stores these locations in environment variables.

Table 7 Choosing an Upgrade Procedure

Use This Procedure If You Have This Situation

Upgrading Without Saving KM Customizations

■ have not made any customizations to the KM files in your previous version of PATROL KM for Unix and Linux

■ want to overwrite customizations you made to the KM files with the default values of the new version of PATROL KM for Unix and Linux

■ have a currently installed version of PATROL KM for Unix and Linux that cannot be migrated (See “Table 6Versions That You Can Migrate” on page 50)

Upgrading and Preserving KM Customizations

made customizations to the KM files in your previously installed version of PATROL KM for Unix and Linux and want to save those customizations and migrate them to the new version of PATROL KM for Unix and Linux

Table 8 Default Values for PATROL Location Variables

Variable Default Value

PATROL_HOME /opt/bmc/<patrol_directory>a/$TARGETb

PATROL_CACHE $HOME/<patrol_directory> a/$TARGETb


Upgrade Scenarios for PATROL KM for Unix and Linux

Viewing Environment Variables Set by PATROL

To view the value of PATROL_HOME, PATROL_CACHE, and other environment variables, perform the appropriate procedure for your shell type:


There are several different scenarios for upgrading PATROL KM for Unix and Linux. These scenarios include

■ not migrating customizations■ migrating customizations using PATROL Configuration Manager■ migrating customizations manually■ migrating customizations using the PATROL Migration Tools and then installing

the product using— the Common Installation Utility for local installations— the Distribution Server for remote installations

a Depending upon which PATROL architecture you are using, the <patrol_directory> is /PATROL3 or /PATROL7.b$TARGET is the output of the target script, indicating the system type and OS version.

Type of Shell Procedure

Bourne and Korn At the shell command prompt, type export and press ENTER.

The shell displays a list of environment variables and their values.

Note: If PATROL_HOME is not set, source patrolrc.sh by entering the following command: . ./patrolrc.sh

C At the shell command prompt, type setenv and press ENTER.

The shell displays a list of environment variables and their values.

Note: If PATROL_HOME is not set, source patrolrc.sh by entering the following command: source .patrolrc



Upgrading Without Saving KM Customizations

If you do not want to save any customizations of .km files, PSL code, alarm thresholds, or events, you can simply install the new version of PATROL KM for Unix and Linux over your previous version after moving or deleting PATROL KM for Unix and Linux files from the PATROL_CACHE. See “First-Time Installation” on page 40 for instructions.

Upgrading and Preserving KM Customizations

Use the appropriate task in this section if you want to upgrade to the new version of PATROL KM for Unix and Linux and you want to preserve any customizations you have made to the .km files in the previous version of PATROL KM for Unix and Linux.

You must first migrate your customizations from the old version of PATROL KM for Unix and Linux to the new version, and then install the result into your environment. You should complete this process on a limited number of computers in the test environment first, test the merged KMs thoroughly, and then deploy them to your production environment.

Migrating Your KM Customizations

Customizations made to PATROL KM for Unix and Linux can include changes to the parameter alarm ranges, states, or other parameter properties.

You can migrate customizations using the PATROL Configuration Manager, manually, or using the PATROL migration tools. Migration of .km files with the migration tools is automated, with the following exceptions:

■ modified PSL code, whether it is embedded in .km files or in .psl files■ new Knowledge Modules that you created

The results from the migration tools can be installed using either the PATROL Installation Utility or the Distribution Server. For more information about the PATROL migration tools, see the PATROL Migration Tools User Guide.

NOTE Customizations applied using PATROL Configuration Manager or operator overrides are automatically saved in the agent configuration database. They will take effect automatically unless the parameter name or application name has changed.



Preparing to Upgrade

Whether you are upgrading and migrating customizations or simply upgrading, you must first back up the current installation. If the .kml file or any of the .km files for the new version of PATROL KM for Unix and Linux has a different file name from the previous version, you must remove those files from the list of KMs that are preloaded on the PATROL Agent.

Before you begin

If you plan to migrate your customizations, determine whether you can migrate from a previous version of PATROL KM for Unix and Linux. See Table 6 on page 50 to determine whether migration is supported for your current version of PATROL KM for Unix and Linux.

To Back Up the Current Installation

Use the following instructions to back up your customizations so that you can restore the current installation if you want to roll back your upgrade.

1 Shut down any PATROL Agents, consoles, and related services that are currently running.

2 Ensure that no one is accessing any PATROL files or directories.

3 Perform a full backup of the directories where PATROL files are typically stored. These directories are listed in the following table:


If you are migrating customizations using the PATROL Configuration Manager (recommended), see “Migrating Customizations with the PATROL Configuration Manager” on page 55.

If you are moving files from the PATROL_CACHE directories, see “Moving Files from the PATROL_CACHE Directories” on page 55.

If you are migrating customizations manually, see “Migrating Customizations Manually” on page 57.

File Type Directory

executables and data PATROL_HOME/.. for agent and console installation directories

console customizations PATROL_CACHE for the console working cache



Migrating Customizations with the PATROL Configuration Manager

BMC Software recommends that if you have customized KMs that these customizations should be migrated to PATROL Configuration Manager rulesets. PATROL Configuration Manager rulesets allow you to manage customizations to KMs, depending on the type of customization.

■ If you have localized parameters or global parameters that have customized poll times or thresholds, use the AS_CHANGESPRING KM to migrate these customizations into PATROL Configuration Manager rulesets as described in the PATROL Configuration Manager User Guide.

■ If you have created custom recovery actions, follow these steps:

1 Ensure that you have made a record of your customizations and have backed up the customized files in the PATROL_HOME and PATROL_CACHE directories.

2 Uninstall the old version of PATROL KM for Unix and Linux.

3 Install the new version of PATROL KM for Unix and Linux as described in the section “Installing for the First Time” on page 40.

4 Ensure that you have made a record of your custom recovery actions.

5 Use the Recovery Action Event Management commands as described in the PATROL Configuration Manager User Guide to migrate your custom recovery actions to the PATROL Configuration Manager.

All other customizations must be migrated manually, as described in “Migrating Customizations Manually” on page 57.

Moving Files from the PATROL_CACHE Directories

Before you install, you must move the current PATROL KM for Unix and Linux files from the PATROL_CACHE directory for the console. If you do not, old product files in PATROL_CACHE are loaded instead of the new files from PATROL_HOME.

Copy the PATROL KM for Unix and Linux files with the following naming patterns to a directory outside the PATROL installation and delete them from PATROL_CACHE\knowledge and PATROL_CACHE\psl.



Naming Patterns for the PATROL KM for Unix

Naming Patterns for the PATROL KM for Log Management:

■ LOG*■ PMG*

■ add_* ■ aix_* ■ all_*

■ apilib* ■ appclass* ■ BASE3*

■ bds_* ■ blackout* ■ boot_*

■ bsd_* ■ Capture* ■ cat_*

■ ChkUnldDcm* ■ COLLECTORS* ■ COMPOSITE*

■ Composites* ■ Configure* ■ cpu*

■ CPU* ■ DCM* ■ debug_*

■ DISK* ■ display_* ■ edit_*

■ FILESYS* ■ Filesys* ■ fs_*

■ FSDebug* ■ get_* ■ HAAG*

■ haag_* ■ HP* ■ hp_*

■ internal_* ■ KERN* ■ kern*

■ Linux* ■ linux_* ■ list_*

■ make_* ■ mem_* ■ MEMORY*

■ most_* ■ net_* ■ NETWORK*

■ network_* ■ NFS* ■ nfs_*

■ nis_* ■ not_* ■ OSF*

■ osf_* ■ PATROL* ■ pkmunix*

■ PRINTER* ■ printer_* ■ prn_*

■ PROC* ■ proc* ■ response_*

■ RS6000* ■ SCHEDULER* ■ sec_*

■ SECURITY* ■ sequent_* ■ set*

■ SINIX* ■ SMP* ■ SNMP*

■ SOLARIS* ■ solaris_* ■ statvfs_*

■ stop_* ■ svr4_* ■ SWAP*

■ tcp_* ■ toggle_* ■ uname_*

■ UNIX* ■ unix_* ■ USERS*

■ usr_* ■ uu*



Naming Patterns for the PATROL Knowledge Module for History Loader:

■ H*.km■ H*.psl

■ History-*■ History_Loader*■ Hist*■ COM_DEB_*■ COM_STAT_*

See the PATROL Knowledge Module for History Loader User Guide for more information about migrating the PATROL Knowledge Module for History Loader.

Migrating Customizations Manually

If you have only a few customizations, you might find manual migration easier than migrating using the PATROL migration tools. If you have made customizations to the PATROL Script Language (PSL) code, you must manually migrate those customizations. This task contains a procedure for manually migrating each kind of customization.

To Migrate Customizations to KM Files Manually

1 Ensure that you have made a record of your customizations and have backed up the customized files in the PATROL_HOME and PATROL_CACHE directories.

2 Uninstall the old version of PATROL KM for Unix and Linux.

3 Install the new version of PATROL KM for Unix and Linux as described in the section “Installing for the First Time” on page 40.

4 Identify and record the coding changes, which represent your customizations, in PATROL KM for Unix and Linux by comparing the content of the ASCII files in the newly installed PATROL KM for Unix and Linux version with the content of the customized ASCII files with the same name that is saved in the directory to which you moved the old version.

5 Incorporate your customizations to the new PATROL KM for Unix and Linux by performing the following steps:

A Restart the PATROL console.

B Load the newly installed PATROL KM for Unix and Linux.


Installing Using the Distribution Server

C Using a PATROL console in developer mode, enter the customizations that you identified in step 4 on page 57, one by one.

To Migrate Customized PSL Code

Customizations made to PATROL Script Language (PSL) code are not automatically migrated. These customizations may be embedded in .km files or stored in separate .psl files. Migrate these customizations manually, using the following guidelines:

■ If you modified .psl files that were shipped by BMC Software, you must manually re-edit the PSL code in the new KM by using a PATROL console in developer mode to reapply your changes.

■ If you modified PSL code embedded in a .km file, that code will be overwritten when you install a new version of the product. You must manually edit the new .km files by using a PATROL console in developer mode to reapply your changes.

■ If you created a new PSL file (not shipped by BMC Software) outside of a .km file, or if you created new PSL code (not shipped by BMC Software) and embedded it in a .km file that was shipped by BMC Software, use the pslsearch utility to search your .km, .psl, and .ctg files for terms that you may have used that have since been adopted by BMC Software as PSL keywords. Rename any terms that pslsearch identifies as matching existing keywords. Reapply your changes by using a PATROL console in developer mode. For instructions about using the pslsearch utility, see the PATROL Migration Tools User Guide.

Installing Using the Distribution ServerPATROL for Unix and Linux can be installed locally to a single computer or remotely to multiple computers using BMC Software’s Distribution Server.

You use the Distribution Server to perform remote installations or uninstallations of BMC Software distributed systems products across multiple systems from a central location.

With the Distribution Server you can

■ Install, uninstall, upgrade, and reinstall products on remote systems from one central location.

■ Create collections of products and system groups to distribute multiple products to multiple systems in one distribution.

■ Schedule a distribution for a specific date and time.



■ Maintain multiple product versions to be distributed.

■ View reports to check distribution status, gather distribution data, and diagnosis problems.

Import a CD Image or Customized Installation Package into the Distribution Server

This task describes how to import components into the Distribution Server for deployment to multiple locations.

Before you begin

Ensure that you use the Distribution Server version 7.1.10.01 or later and apply any available patches.

To Import Components in to the Distribution Server

1 Using the Distribution Server Manager, start the Distribution Server and connect to it.

2 In the Distribution Server tab area, click the Components tab.

3 In the list area, click the Import button.

4 Navigate to the location where the components are located and click Next.

5 Select the directory that contains the Products directory (do not select the Products directory itself).

If the components are not accessible on a local drive, you can specify them by using the NFS name and path.

6 Select the check boxes for the components that you want to import and click OK.

7 On the Import Components screen, click Import to import the selected components.

8 When the Import Status screen is displayed, click Close.

EXAMPLE Assuming that you copied the CD image into a directory called merged_CD and then, after migrating your customizations and creating a customized installation package, you copied the updated package to the directory containing the CD image, the resultant directory structure would resemble merged_CD/Products/pukchm. You would select the directory merged_CD.



9 If the components you are importing are located on another CD, the Import External Dependencies screen is displayed. Enter or browse to the location of the CD listed on the Import External Dependencies screen click Next.

10 On the Import Components screen, click Import to import the selected components.

11 When the Import Status screen is displayed, click Close.


To remotely install PATROL KM for Unix and Linux throughout your enterprise, use the instructions in the Distribution Server Getting Started Guide. For an overview of that process, see “Installing PATROL KM for Unix and Linux Using the Distribution Server.”

Installing PATROL KM for Unix and Linux Using the Distribution Server

Once you have imported PATROL for Unix and Linux into the Distribution Server, you must perform the following tasks within the tool. The tasks can be grouped into three stages.

To Set Up Products

1 Import components into the Distribution Server repository on the Components tab of the Distribution Manager.

2 Arrange components in collections on the Collections tab of the Distribution Manager.

3 Configure the collections on the Configurations tab of the Distribution Manager.

To Set Up Systems

1 Create accounts in the operating system of the computers to which you want to distribute PATROL KM for Unix and Linux.

2 Add accounts and create profiles for the systems on the Systems tab of the Distribution Manager.

3 Add the systems and install the Distribution Client on the Systems tab of the Distribution Manager.

4 Arrange systems in system groups on the Systems tab of the Distribution Manager.


Considerations for Using Online Help

To Distribute Products

1 Distribute configurations of collections to system groups on the Distributions tab of the Distribution Manager.

2 Run reports to review distributions on the Reports tab of the Distribution Manager.

For detailed instructions about how to perform remote installations with the Distribution Server, see the Distribution Server Getting Started Guide.

Considerations for Using Online HelpIf you plan to install PATROL KM for Unix and Linux on a PATROL Console for Unix, you must install the supported version of the Help browser separately if it is not already installed.

Browser Version Required for Viewing PATROL Console for Unix Help

One of the following browsers is required to view PATROL Help in a PATROL Console for Unix version 3.x:

■ Unix: Netscape Navigator version 3.01 through 4.78■ Red Hat Linux: Netscape Navigator version 4.x

PATROL Help does not support Netscape Navigator 6.0.

Installation Requirement

You must install Netscape Navigator on the computer where the PATROL console resides. You can install Netscape anywhere on your Unix computer as long as the binary is in the path.

Download Location

Netscape Navigator is supplied by Netscape Communications Corp. You can locate the browser at http://ftp.netscape.com/pub/communicator/.


http://ftp.netscape.com/pub/communicator/


Additional Considerations for Using Online Help for Unix

When you select Help from the PATROL Console for Unix, it may take a few seconds for the Help browser to launch. Two windows will be displayed. First, the Netscape Navigator window is displayed as an icon, and then a browser window that contains the Help is displayed.

In addition, you must be aware of the following restrictions:

■ Netscape Navigator displays warning messages when it is invoked multiple times within the same user account because of its file-locking mechanism. It will, however, continue functioning.

■ By default, when Netscape Navigator starts, it uses a private color map. As a result, you might experience color flashing on your workstation. If so, you can set the value of PATROL_BROWSER so that the colormap option is not specified. However, some subsequent color requests might fail and the online Help will be improperly displayed.

■ The Exceed for Windows NT X Window Server product by Hummingbird Communication Ltd. may not always display the Help files properly.

Consult your Netscape Navigator documentation for specific platform requirements and restrictions.

Required Environment Variables Settings for the Browser

The LANG, PATH, and PATROL_BROWSER environment variables must be set for the Help browser to run properly. The following sections describe these variables.

LANG Variable

The Unix LANG environment variable must be set to C so that Netscape Navigator will work properly. Otherwise, you might experience product failures.

Type of Shell Export Command for LANG Variable

Bourne LANG=Cexport LANG

Korn export LANG=C

C setenv LANG=C



PATH Variable

The PATROL user account PATH variable must contain the location of the directory containing the Netscape files. If the directory containing the Netscape files is not in the path, add the directory to the PATROL user account path.

This requirement applies only to the PATROL user account on the PATROL console computer.

PATROL_BROWSER Variable

When PATROL starts the Help browser, it uses the command in the PATROL_BROWSER environment variable. As a default, the PATROL_BROWSER environment variable contains the following command:

To use different arguments, set the value of PATROL_BROWSER to the appropriate string.

Type of Shell Export Command for PATH Variable

Bourne PATH=$PATH:/netscape_locationexport PATH

Korn export PATH=$PATH:/netscape_location

C setenv PATH=$PATH:/netscape_location

Type of Shell Export Command for PATROL_BROWSER Variable

Bourne PATROL_BROWSER=netscape -display $DISPLAY -install -iconicexport PATROL_BROWSER

Korn export PATROL_BROWSER=netscape -display $DISPLAY -install -iconic

C setenv PATROL_BROWSER=netscape -display $DISPLAY -install -iconic

EXAMPLE For a Korn shell:

export PATROL_BROWSER=/usr/local/bin/netscape -raise


Uninstalling PATROL for Unix and Linux

Uninstalling PATROL for Unix and LinuxTo uninstall PATROL for Unix and Linux you must use the same version of the installation utility that you used to install the product. Run the installation utility in uninstall mode to uninstall PATROL for Unix and Linux from your system.

Determining the Version of the Installation Utility

To determine the version of the installer, perform the following procedure.

1 Access a command prompt and navigate to the appropriate location:

BMC_ROOT/Uninstall

where BMC_ROOT is the root directory of your BMC product installation. By default this is /opt/bmc.

2 Type ./uninstall.sh -v and press ENTER.


The following procedure describes how to uninstall PATROL for Unix and Linux from a Unix environment with or without a browser installed.

To Uninstall Individual Products Using the Installation Utility

1 Change to the Uninstall directory in your BMC Software product installation directory and type ./uninstall.sh to launch the installation utility in uninstall mode.

2 The Welcome window is displayed. Click Next.

NOTE Before you can uninstall PATROL products, you may need to stop any PATROL processes that are running on the computers where you want to uninstall PATROL. For information about stopping PATROL processes, see the

■ Distribution Server Getting Started■ PATROL Knowledge Module for Unix User Guide ■ PATROL Agent Reference Manual



3 Select the installation directory from which you want to remove a product, and click Next.

4 Select the product or products that you want to uninstall, and click Next.

5 Review your selections and click Uninstall.

After the uninstallation is complete, a window is displayed that tells you whether the uninstallation was successful.

To Uninstall Individual Products in a Unix Environment without a Browser

1 If you are uninstalling from a Unix environment without a browser perform the following steps to launch the installation utility:

A From a command line, change to the Uninstall directory and type /cdrom./uninstall.sh -serveronly to start the installation Web server.

B A message box is displayed that shows the URL to use to connect to the installation Web server.

C On another machine with a browser, start the browser.

D Connect to the installation Web server from the browser to start the installation utility by using the URL that is displayed in the message box.

2 The Welcome window is displayed. Click Next.

3 Select the installation directory from which you want to remove a product, and click Next.

4 Select the product or products that you want to uninstall, and click Next.

5 Review your selections and click Uninstall.

After the uninstallation is complete, a window is displayed that tells you whether the uninstallation was successful.



Uninstalling All Product Files Except Log Files and Configuration Files

This task describes how to uninstall the PATROL product but retain log files, which contain history for future analysis, and configuration files for redeployment.

1 Uninstall all products as described in “Uninstalling PATROL for Unix and Linux” on page 64.

2 Locate the uninstall.ctl file in the following directory.

BMC_ROOT/Uninstall/Install/instdata

3 Open the uninstall.ctl file in a text editor, and edit the /BMC/BASE variable to specify the name of the directory from which you removed the products in step 1.

4 Open a command line prompt.

5 Change to the following directory.

BMC_ROOT/Uninstall/Install/ instbin

6 Enter the following commands:

thorinst.sh -uninstall path_to_control_file -log path_to_log_file -output path_to_output_log_file

Use the following table to help determine the log file and output log file locations:

Option Description Value

-log sends the log information to a standard log file

This file contains all installation status information.

path to log file; any valid path and file name (with a .txt extension)

If a space exists in the path, the entire path must be enclosed in quotation marks.

-output sends the log information to an output log file

This file contains all messages about the progress of the installation that are normally sent to standard output.

path to output log file; any valid path and file name (with a .txt extension)




Example

If /opt/bmc is your product installation directory, you would change to the /opt/bmc/Uninstall/Install/instbin directory and enter the following command:

This action removes all installation files and directories except those that are used by the utility at the time the uninstallation is performed. Log files, configuration files, and user-modified files would also be retained.

Uninstalling All Products and Associated Log Files and Configuration Files

This task describes how to remove all PATROL products and related log files and configuration files from your Unix computer. Once these files have been removed, you cannot recover them unless you have made a back-up copy of the installation.

1 Uninstall all products as described in “Uninstalling PATROL for Unix and Linux” on page 64.

2 Locate the uninstall-all.ctl file in the following directory.

BMC_ROOT/Uninstall/Install/instdata

3 Open the uninstall-all.ctl file in a text editor, and edit the /BMC/Base variable to specify the name of the directory from which you removed the products in step 1.

4 Open a command line prompt.

5 Change to the following directory.

BMC_ROOT/Uninstall/Install/instbin

6 Enter the following command.

thorinst.sh -uninstall path_to_control_file -log path_to_log_file -output path_to_output_log_file

thorinst.sh -uninstall “/opt/bmc/Uninstall/Install/instdata/uninstall.ctl” -log /var/logs/NetworkLogs/MyLogs.txt -output /var/adm/NetworkLogs/MyLogs.out



Use the following table to help determine the log file and output log file locations:

Example

If /opt/bmc is your product installation directory, you would change to the /opt/bmc/Uninstall/Install/instbin directory and enter the following command:

This action removes all installation files and directories. The files that were used to perform the uninstallation will be marked for deletion and will be removed when the computer on which the products were uninstalled is rebooted.

Option Description Value

-log sends the log information to a standard log file

This file contains all installation status information.



-output sends the log information to an output log file

This file contains all messages about the progress of the installation that are normally sent to standard output.



thorinst.sh -uninstall “/opt/bmc/Uninstall/Install/instdata/uninstall-all.ctl” -log /var/logs/NetworkLogs/MyLogs.txt -output /var/adm/NetworkLogs/MyLogs.out


Where to Go from Here

Where to Go from HereThe following table lists other topics and where you can find them:

Topic Source of Information

overview of PATROL KM for Unix and Linux and its features

Chapter 1, “PATROL for Unix and Linux Components and Capabilities” and PATROL KM for Unix and Linux online Help

setting up and configuring PATROL KM for Unix and Linux

Chapter 3, “Loading and Configuring PATROL KM for Unix and Linux” and PATROL KM for Unix and Linux online Help

instructions about how to access the KM menu commands, InfoBoxes and online Help

Appendix A, “Accessing Menu Commands, InfoBoxes, and Online Help”

troubleshooting information Appendix B, “Troubleshooting PATROL for Unix and Linux Problems”

using PATROL for Unix and Linux functionality to monitor and manage Unix and Linux operating systems

PATROL Knowledge Module for Unix User Guide and PATROL for Unix and Linux online Help

PATROL Agent configuration variables pertaining to PATROL KM for Unix and Linux

PATROL Knowledge Module for Unix User Guide and PATROL for Unix and Linux online Help

definitions and default values for parameters

PATROL Knowledge Module for Unix User Guide and PATROL Knowledge Module online Help systems

consumer and collector parameter dependencies

PATROL Parameter Reference Manual and PATROL Knowledge Module online Help systems

step-by-step procedures and detailed descriptions of the applications, menu commands, parameters, and InfoBoxes

PATROL Knowledge Module for Unix and Linux User Guide and PATROL KM for Unix and Linux online Help


Where to Go from Here


C h a p t e r 3
3 Loading and Configuring PATROL KM for Unix and Linux
This chapter provides information about how to begin configuring and using PATROL KM for Unix and Linux. In this chapter, the term Knowledge Module (KM) is usually equivalent to a .kml file. A .km file is equivalent to an application class, which is a subset of a KM or .kml file.

The following topics are discussed in this chapter:

Preparing to Use PATROL KM for Unix and Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Migrating Customized Processes from Previous Versions of PATROL KM

for Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Using the PATROL Configuration Manager to Migrate Customized Processes . 74Using the pconfig Utility to Migrate Customized Processes . . . . . . . . . . . . . . . . . 74

Manually Starting the PATROL Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Loading and Preloading KMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Determining Which KMs to Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Determining Which KMs to Preload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Loading KMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Verifying What You Have Loaded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Preloading KMs on the PATROL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Removing KMs from Your Console and Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Unloading KMs from a PATROL Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Removing KMs from the Agent Preload List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Configuring PATROL KM for Unix and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Configuring the PATROL KM for Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Specifying a Data Collection Method for the PATROL KM for Unix . . . . . . . . . . 89

NOTE ■ For information about configuring the PATROL Knowledge Module for History Loader,

see the PATROL Knowledge Module for History Loader User Guide.

■ For information about configuring the PATROL Knowledge Module for Event Management, see the PATROL Knowledge Module for Event Management User Guide.


Configuring the PATROL KM for Log Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Enabling the PRINTER and NETWORK Application Classes . . . . . . . . . . . . . . . . 92

Configuring Recovery Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94About Recovery Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94PATROL Native Recovery Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Configuring PATROL Native Recovery Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 95


Preparing to Use PATROL KM for Unix and Linux

Preparing to Use PATROL KM for Unix and Linux

Before configuring PATROL KM for Unix and Linux, verify that the following software requirements are met:

■ The PATROL console version 3.5.x or later and PATROL KM for Unix and Linux are installed on the computer you that want to use for the PATROL console.

■ The PATROL Agent version 3.5.x or later and PATROL KM for Unix and Linux are installed on the computer that you want to monitor and manage.

■ PATROL KM for Unix and Linux is installed on the PATROL console computers and the PATROL Agent computers.

■ If you are using PATROL Central Operator – Microsoft Windows Edition, PATROL KM for Unix and Linux is installed on the PATROL Console Server.

■ If you are using PATROL Central Operator – Web Edition, PATROL KM for Unix and Linux is installed on the PATROL Console Server and PATROL Web Server.

Migrating Customized Processes from Previous Versions of PATROL KM for Unix

If you defined custom processes to monitor in earlier versions of the PATROL Knowledge Module for Unix, these processes are automatically migrated the first time that you load the KM; however, if you add customized processes after the KM is first loaded, these processes are not migrated and will not show up under the PROCESS_PRESENCE application class.

The workaround for this issue depends on whether or not you are using the PATROL Configuration Manager to manage your customizations. Select the process below that fits your scenario.


Migrating Customized Processes from Previous Versions of PATROL KM for Unix

Using the PATROL Configuration Manager to Migrate Customized Processes

To use the PATROL Configuration Manager to migrate customized processes that have been added after you have loaded the PATROL KM for Unix, follow these steps:

1 Add the PROCCONT.km to the /AgentSetup/disabledKMs variable.

2 Delete the /PUK/9.1.00/migration variable.

3 Reinitialize the PATROL Agent.

4 Apply the PCM rulesets to be migrated.

5 Remove the PROCCONT.km from the /AgentSetup/disabledKMs variable.

6 Reinitialize the PATROL Agent.

Using the pconfig Utility to Migrate Customized Processes

To use the pconfig utility to migrate customized processes that have been added after you have loaded the PATROL KM for Unix, follow these steps:

1 Ensure that the PATROL KM for Unix is not on the Agent preload KMs list.

2 Close the PATROL Console.

3 Using the pconfig utility, delete the /PUK/9.1.00/migration variable, if it exists.

4 Using the pconfig utility, insert the agent configuration variables pertaining to the new customized processes that you have created.

5 Using a PATROL Console, which already has the PATROL KM for Unix loaded, connect to the PATROL Agent.

This will cause the Unix KM to load the Agent, or add the UNIX3.kml to the Agent preload list and reinitialize the agent.


Manually Starting the PATROL Agent

Manually Starting the PATROL AgentUse the following procedure to manually start the PATROL Agent:

1 Navigate to the directory where the PATROL Agent is installed.

2 Type ./PatrolAgent -p portnumber and press Enter.

See the PATROL Agent Reference Manual for more information about using the PATROL Agent.

Loading and Preloading KMsWhen you load a KM from the PATROL console, the KM files are loaded on all the PATROL Agents to which your console is connected. The KM icons appear in your console, usually under each agent icon, during discovery. Each PATROL Agent then collects data based on the instructions defined in the KM.

Preloading KMs is a PATROL Agent feature that causes KM files to continue to run on the agent when no consoles are connected. KMs that are not preloaded collect data only while a PATROL console is connected to the PATROL Agent.

Determining Which KMs to Load

Before you can configure and use PATROL KM for Unix and Linux, its KM files must be loaded into the PATROL console so that the product’s applications, commands, and parameters appear in the PATROL console. Table 9 on page 76 lists the KM files in this product that you can load. You can find the steps for loading KM files in “Loading KMs” on page 76.

Determining Which KMs to Preload

Preloaded KMs collect data as long as the PATROL Agent runs, even when no PATROL console is connected. When you view a preloaded KM’s data collection history, you will not see any gaps that would otherwise occur (because of the console’s absence).


Loading and Preloading KMs

You can find the steps for loading and preloading KMs in the following sections:

■ “Loading KMs.”■ “Preloading KMs on the PATROL Agent” on page 81

If you use certain KM files regularly and want to maintain their data collection history without gaps, preload the .kml files (listed in Table 9) on the appropriate PATROL Agents as described in “Preloading KMs on the PATROL Agent” on page 81.

Loading KMs

Before you can begin using KMs that you have installed, you must first load them with a PATROL console. In this task, follow the instructions that apply to your console.

To Load KMs from PATROL Central – Microsoft Windows Edition

PATROL Central – Microsoft Windows Edition has a Loading KMs wizard with which you can specify the KMs to load and the computers on which to load them.

1 On the Common Tasks tab of the taskpad, click the Load Knowledge Modules icon.

PATROL Central – Microsoft Windows Edition displays the wizard.

2 Click Next to start the wizard.

The wizard lists each computer on which a PATROL Agent has been installed.

Table 9 PATROL for PATROL KM for Unix and Linux .kml Files

.kml Files Description

UNIX3.kml PATROL KM for Unix: loads application classes to monitor Unix and Linux operating systems.

LOG.kml PATROL KM for Log Management: loads application classes to monitor log files.

EVENT_MANAGEMENT.kml PATROL KM for Event Management: loads application classes to provide event notification and filtering, and centralized alert management features. See the PATROL Knowledge Module for Event Management User Guide for more information.

HISTORY.kml PATROL Knowledge Module for History Loader: contains a list of the history loader components for each supported database, as well as the history propagator component. Loads all of the application files. See the PATROL Knowledge Module for History Loader User Guide for more information.



3 Select the check boxes for the computers on which you want to load KMs, and click Next.

The wizard displays a list of available .kml files for each selected computer. Each .kml file is listed once for each computer. You can display .km files instead (equivalent to application classes) by changing the filter.

The KMs available in this product are listed in Table 9 on page 76.

4 Select the check boxes for the KM and computer pair that you want to load.

5 Click Next and click Finish.

PATROL loads the selected KMs on the selected computers.

To Load KMs from PATROL Central – Web Edition

PATROL Central – Web Edition has a Loading KMs feature with which you can specify the KMs to load and the computers on which to load them.

1 From the Monitored Systems page, click Load/Unload KMs.

The Load KMs page opens, listing each computer on which a PATROL Agent has been installed.

2 Select each computer on which you want to load the same KMs, and click Next.

The Load KMs page displays a list of available .km and .kml files.

If you selected more than one computer, the Load KMs page displays only the .km and .kml files that have been installed on all of the selected computers. If you want to load a particular .km or .kml file on a particular computer, select that computer by itself to load the file.

3 Select the .km or .kml files that you want to load.

See Table 9 on page 76 for a list of the KMs that are available in this product.

4 Click Finish.

PATROL loads the selected KMs on the selected computers.



To Load KMs from the PATROL Console for Microsoft Windows

1 From the PATROL Console for Microsoft Windows menu bar, choose File => Load KM.

The Load KMs dialog box displays a list of available .kml files. You can display .km files instead (equivalent to application classes) by selecting KM Files (*.km) from the drop-down list box.


2 Select one or more of the .kml (or .km) files, and click Open.

PATROL loads the selected KMs on all of the computers listed under PATROLMainMap in the tree view.

To Load KMs from the PATROL Console for Unix

1 From the PATROL Console for Unix menu bar, choose File => Load KM.

The Load KMs dialog box displays a list of available .kml files. You can display .km files instead (equivalent to application classes) by changing the filter.


2 Select one or more of the .kml (or .km) files, and click Open.

PATROL loads the selected KMs on all of the computers to which your console is connected.

Verifying What You Have Loaded

The application classes that appear in your console depend on which components of PATROL for Unix and Linux that you have loaded.

Verifying that the PATROL KM for Unix Is Loaded

If you loaded the UNIX3.kml file for the PATROL KM for Unix, you will see the application classes that are listed in Figure 4 on page 79 in your console after application discovery is finished. However, the NETWORK and PRINTER application classes appear only after you enable them. See the PATROL KM for Unix and Linux User Guide for more information. This example shows the loaded application classes in a tree view. If your PATROL console does not have a tree view, double-click the agent computer icon to view the application classes that are loaded.



If you loaded UNIX3.kml, waited for application discovery to finish, and do not see all the application classes that are listed Figure 4, view the System Output Window from the agent computer icon’s menu and look for error messages. The figure should show only what appears after discovery; it should not include objects that appear only after being configured.

Figure 4 Application Classes that Appear When UNIX3.kml Is Loaded

Verifying that the PATROL KM for Log Management Is Loaded

If you loaded the LOG.kml file for the PATROL KM for Log Management, you will see the application classes that are listed in Figure 5 on page 80 in your console after application discovery is finished. This example shows the loaded application classes in a tree view. If your PATROL console does not have a tree view, double-click the agent computer icon to view the application classes that are loaded.

If you loaded LOG.kml, waited for application discovery to finish, and do not see all the application classes that are listed Figure 5 on page 80, view the System Output Window from the agent computer icon’s menu and look for error messages. The figure should show only what appears after discovery; it should not include objects that appear only after being configured.



Figure 5 Application Classes that Appear When LOG.kml Is Loaded

Verifying that the PATROL KM for Event Management Is Loaded

If you loaded the EVENT_MANAGEMENT.kml file for the PATROL KM for Event Management, you will see the application classes that are listed in Figure 6 in your console after application discovery is finished. This example shows the loaded application classes in a tree view. If your PATROL console does not have a tree view, double-click the agent computer icon to view the application classes that are loaded.

If you loaded EVENT_MANAGEMENT.kml, waited for application discovery to finish, and do not see all the application classes that are listed Figure 6, view the System Output Window from the agent computer icon’s menu and look for error messages. The figure should show only what appears after discovery; it should not include objects that appear only after being configured.

Figure 6 Application Classes that Appear When EVENT_MANAGEMENT.kml Is Loaded



Verifying that the PATROL Knowledge Module for History Loader Is Loaded

If you loaded the HISTORY.kml file for the PATROL Knowledge Module for History Loader, you will see the application classes that are listed in Figure 7 in your console after application discovery is finished. This example shows the loaded application classes in a tree view. If your PATROL console does not have a tree view, double-click the agent computer icon to view the application classes that are loaded.

If you loaded HISTORY.kml, waited for application discovery to finish, and do not see all the application classes that are listed Figure 7, view the System Output Window from the agent computer icon’s menu and look for error messages. The figure should show only what appears after discovery; it should not include objects that appear only after being configured.

Figure 7 Application Classes that Appear When HISTORY.kml Is Loaded

Preloading KMs on the PATROL Agent

If you want your KMs to continue collecting data even when there is no console running, preload your KMs. A preloaded KM is a KM that is loaded by the PATROL Agent at startup and runs as long as the PATROL Agent runs. To preload a KM, add it to the agent’s preload list by using the wpconfig or xpconfig utility, as described in this task.

For information about the wpconfig or xpconfig utility, see the PATROL Agent Reference Manual.

NOTE When you load the PATROL Knowledge Module for History Loader HISTORY.kml file, applications for all supported RDBMS types are automatically loaded. If you are not using all of these RDBMS types, you can delete the unused applications to save memory and other resources.



Before you begin

■ The PATROL Agent must be running.

■ You must be running a PATROL console in developer mode (PATROL Console for Windows or Unix).

■ You must have permission to modify the configuration change file (.cfg).

To Use wpconfig to Preload a KM from the PATROL Console for Microsoft Windows

1 Access the PATROL Agent’s pop-up menu and choose Development => Agent Configuration.

The console starts the wpconfig utility and displays the wpconfig window.

2 In the left pane, click the AgentSetup folder.

The variables in the AgentSetup folder are displayed in the right pane.

3 Scroll down the variable list and double-click the preloadedKMs variable.

The Modify Variable dialog box is displayed.

4 In the Change Entries field, double-click the highlighted REPLACE line.

The Change Entry dialog box is displayed.

5 In the Type field, leave REPLACE.

6 In the Value field, use the comma-separated format without spaces to type the names of the .kml files that you want to preload. See Table 9 on page 76 for a list of the KMs that are available in this product.

For example, a valid and typical preloaded KMs list is as follows:

UNIX3.kml,EVENT_MANAGEMENT.kml,AS_EVENTSPRING.km

7 Click OK.

The Change Entry dialog box closes.

8 In the Modify Variable dialog box, click OK to close the box.



9 From the Tools menu, choose Apply Configuration.

The Apply Configuration dialog box is displayed, listing the PATROL Agent host name to which you are connected.

10 Click OK to apply your updated configuration to the PATROL Agent.

11 Save your changes to the configuration change file by clicking the Save button.

12 Close the wpconfig window.

To Use xpconfig to Preload a KM from the PATROL Console for Unix


The console starts the xpconfig utility and displays the xpconfig window.

2 From the Host column in the left pane of the xpconfig window, click a PATROL Agent computer name to highlight it.

3 Click Get Configuration.

The configuration variables for the selected computer are displayed in the Variables column in the right pane.

4 In the Filter field, type the following string:

/AgentSetup/pre*

The filter displays all the variables that begin with this character string.

5 Double-click the preloadedKMs variable.

The Edit Variable dialog box is displayed.

6 Click Change.

An Edit window is displayed.

7 Use the comma-separated format without spaces to type the names of the .kml files that you want to preload. See Table 9 on page 76 for a list of the KMs that are available in this product.

For example, a valid and typical preloaded KMs list is as follows:

LM_KIT,EVENT_MANAGEMENT.kml,AS_EVENTSPRING.km


Removing KMs from Your Console and Agent

8 Choose File => Exit to close the Edit window and save your changes.

9 In the Edit Variable dialog box, click OK to close the box.

10 Click Apply Configuration and close the xpconfig window.

The xpconfig utility sends the updated configuration to the selected PATROL Agent.

Removing KMs from Your Console and AgentIf you want to remove a KM from being displayed in your PATROL console, you can unload its corresponding application classes (.km files) as described in “Unloading KMs from a PATROL Console.”

When you unload a .km file, its corresponding application class no longer appears in your console. Unloading a .km file does not delete the file from the lib\knowledge or psl directories on the PATROL console or PATROL Agent computer. If you want to delete a KM completely from your system, you must uninstall the KM.

If a .km file was preloaded (whether as part of a .kml file or not), unloading it does not stop the PATROL Agent from collecting data for that .km file. However, if the .km file was not preloaded, then unloading it does stop the file from running and collecting data on the PATROL Agent.

If you no longer want the PATROL Agent to run a KM that was preloaded, you can remove its corresponding .kml file or .km files from the PATROL Agent preload list as described in “Removing KMs from the Agent Preload List” on page 87.

When you remove a KM from the PATROL Agent preload list, the agent does not run the KM unless you load it with a running console. KMs that are not preloaded do not run when no console is running.

Unloading KMs from a PATROL Console

If you no longer want to view a KM that currently appears in your console, you can unload the corresponding application classes (.km files) that make up the KM.

To Unload KMs from PATROL Central – Microsoft Windows Edition

PATROL Central – Microsoft Windows Edition has a wizard with which you can unload specified .km files from specified computers.



1 On the Common Tasks tab of the taskpad, click the Unload Knowledge Modules icon.

PATROL Central – Microsoft Windows Edition displays the wizard.

2 Click Next to start the wizard.

The wizard lists each computer on which a PATROL Agent has been installed.

3 Select the check boxes for the computers from which you want to unload .km files, and click Next.

The wizard displays a list of application class names (that correspond to .km file names) for each computer selected. Each application class name is listed once for each computer.

4 Select the check boxes for the .km and computer pair that you want to unload, and click Next. To unload an entire KM, select all the .km files that make up the KM. See “Table 9PATROL for PATROL KM for Unix and Linux .kml Files” on page 76 for a list of the .km files in each KM.

5 Click Finish.

The console removes the selected .km files from the current management profile.

To Unload KMs from PATROL Central – Web Edition

PATROL Central – Web Edition has a feature with which you can unload specified .km files from specified computers.

1 From the Managed Systems page, click the Load/Unload KMs button.

The Load KMs page opens, listing each computer on which a PATROL Agent has been installed.

2 Select the computers from which you want to unload .km files, and click Next.

The Load KMs page displays a list of .km files. Currently loaded .km files are highlighted (selected) in the list.

3 Cancel the selection of the .km files that you want to unload by clicking them in the list. To unload an entire KM, cancel the selection of all the .km files that make up the KM.

4 Click Finish.

The console removes the .km files that you specified from the current management profile.



To Unload KMs from the PATROL Console for Microsoft Windows

Unloading a KM is also referred to as deleting a KM in the PATROL Console for Microsoft Windows. However, the files are actually unloaded from the console’s memory rather than deleted from your hard drive.

1 From the KM tab of the tree view, right-click the application class name that you want to delete and choose Delete from the pop-up menu.

The console displays a dialog box that asks if you want to delete the selected application.

2 Click Yes to delete the application class.

The application class is removed from your console, and its corresponding .km file is removed from your console session file when you save your changes.

3 Repeat Step 1 and Step 2 until you have deleted all of the application classes (.km files) associated with the KM that you want to delete.

4 From the console menu bar, choose File => Save KM to save your changes.

To Unload KMs from the PATROL Console for Unix

Unloading a KM is also referred to as deleting a KM in the PATROL Console for Unix. However, the files are actually unloaded from the console’s memory rather than deleted from your hard drive.

1 From the PATROL Main window, choose Attributes => Application Classes.

The console displays the List of Application Classes window.

2 Click the name of the application class that you want to delete.

The console highlights the application class name.

3 From the List of Application Classes menu bar, choose Edit => Delete.

The application class is removed from your console, and its corresponding .km file is removed from your console session file when you save your changes.

4 Repeat Step 2 and Step 3 until you have deleted all of the application classes associated with the KM that you want to delete.

5 From the List of Application Classes menu bar, choose File => Save KM to save your changes.



Removing KMs from the Agent Preload List

If you want to remove a KM or application class so that it no longer runs on the PATROL Agent, remove the corresponding .kml or .km file from the agent preload list, as described in this task.

Before you begin

■ The PATROL Agent must be running.

■ You must be running a PATROL console in developer mode (PATROL Console for Windows or Unix).

■ You must have permission to modify the configuration change file (.cfg).

To Use wpconfig to Remove a KM from the Preload List in the PATROL Console for Microsoft Windows


The console starts the wpconfig utility and displays the wpconfig window.

2 In the left pane, click the AgentSetup folder.

The variables in the AgentSetup folder are displayed in the right pane.

3 Scroll down the variable list and double-click the preloadedKMs variable.

The Modify Variable dialog box is displayed.

4 In the Change Entries field, double-click the highlighted REPLACE line.

The Change Entry dialog box is displayed.

5 In the Type field, leave REPLACE.

6 In the Value field, delete the .kml file names that you want to remove from the preload list. See Table 9 on page 76 for a list of the KMs that are available in this product.

7 Click OK to close the Change Entry dialog box.

8 Click OK to close the Modify Variable dialog box.



9 From the Tools menu, choose Apply Configuration.

The Apply Configuration dialog box is displayed, listing the PATROL Agent host name to which you are connected.

10 Click OK to apply your updated configuration to the PATROL Agent.

11 Save your changes to the configuration change file by clicking the Save button.

12 Close the wpconfig window.

To Use xpconfig to Remove a KM from the Preload List in the PATROL Console for Unix


The console starts the xpconfig utility and displays the xpconfig window.

2 From the Host column in the left pane of the xpconfig window, click a PATROL Agent computer name to highlight it.

3 Click the Get Configuration button.

The configuration variables for the selected computer are displayed in the Variables column in the right pane.

4 In the Filter field, type the following string:

/AgentSetup/pre*

The filter displays all the variables that begin with that character string.

5 Double-click the preloadedKMs variable.

The Edit Variable dialog box is displayed.

6 Click the Change button.

An Edit window is displayed.

7 Delete the .kml file names that you want to remove from the preload list. See Table 9 on page 76 for a list of the KMs that are available in this product.

8 Choose File => Exit to close the Edit window and save your changes.

9 In the Edit Variable dialog box, click OK to close the box.


Configuring PATROL KM for Unix and Linux

10 Click Apply Configuration, and close the xpconfig window.

The xpconfig utility sends the updated configuration to the selected PATROL Agent.

Configuring PATROL KM for Unix and LinuxThis section provides instructions for configuring PATROL for Unix components.

Configuring the PATROL KM for Unix

The PATROL KM for Unix needs no special configuration before it begins collecting data after you load it. However, there are a few configuration options that you might want to set up, depending on the needs of your environment.

Specifying a Data Collection Method for the PATROL KM for Unix

The PATROL KM for Unix has two collection methods: PATROL Scripting Language (PSL) or Data Collection Manager (DCM).

1 Access the UNIX OS application menu as described in “Accessing KM Commands and InfoBoxes” on page 100.

2 Select Debug and Diagnostics => Toggle PSL/DCM Collection from the pop-up menu.

A confirmation dialog box is displayed. The dialog box states that you are about to toggle the collection method, and that the agent will be reinitialized to use the new collection method.

3 Click Yes.

PATROL changes the collection method and reinitializes the agent. In the process of changing collection methods, PATROL destroys some existing parameters, and creates others.



Determining Which Collector is Being Used

This section tells you how to determine which collector is currently being used in your environment.

If you are using the PSL data collection method, a COLLECTORS icon (shown in Figure 8) is displayed in the computer window.

Figure 8 COLLECTORS Icon (PSL Data Collection Method)

If you are using the DCM data collection method, a DCM icon (shown in Figure 9) is displayed in the computer window.

Figure 9 DCM Icon (DCM Data Collection Method)

Configuring PATROL to Use an Existing Perform Collector

This procedure tells you how to configure PATROL to use an existing Perform collector. If you have already installed Perform, you can configure PATROL to use an existing supported Perform Collector if Perform 7.1.41 or later is installed in your environment.

Variables

PATROL can store the location of the Perform installation in two different variables:

■ BEST1_HOME—an environment variable■ /UNIX_OS/PERFORM_HOME—a PATROL Configuration Database variable

(pconfig)

NOTE Neither collection method gathers data for every available parameter in the KM. Refer to “DCM Collection Exceptions” and “PSL Collection Exceptions” in the PATROL Knowledge Module for Unix User Guide for parameter availability information.



To Specify the Location of the Perform Home Directory

1 Access the Unix OS application menu commands as described in “Accessing KM Commands and InfoBoxes” on page 100.

2 Select Specify PERFORM Home Directory.

PATROL displays the Perform Home Directory dialog box (Figure 10).

Figure 10 Perform Home Directory Dialog Box

3 Enter the path where the Perform installation is located and click Apply.

PATROL stores the information in the PATROL Configuration Database variable (pconfig), /UNIX_OS/PERFORM_HOME.

You can also store this information in the BEST1_HOME environment variable. However, you must set up this variable outside of PATROL and source the variable or restart PATROL if it is running.

How PATROL Searches for an Existing Perform Installation

The DCMCollect.psl uses the following methods, in the following order, to search for the location of the Perform installation.

1. PATROL checks for the existence of the pconfig variable /UNIX_OS/PERFORM_HOME. If the variable does not exist or is invalid, PATROL proceeds to Step 2.

2. PATROL checks for the existence of the environment variable, BEST1_HOME. If the variable does not exist or is invalid, PATROL proceeds to Step 3.

3. PATROL checks for the $PATROL_HOME/BEST1 directory. If the directory doesn't exist or is invalid, PATROL proceeds to Step 4.

4. PATROL checks for the BEST1 directory anywhere under the PATROL installation directory. If the BEST1 directory does not exist or is invalid, PATROL proceeds to Step 5.


Configuring the PATROL KM for Log Management

5. PATROL checks for the BEST1 directory under the current directory and its sub-directories. If the BEST1 directory does not exist or is invalid, the DCM process fails to start bgscollect.

Enabling the PRINTER and NETWORK Application Classes

By default, the PRINTER and NETWORK application classes are disabled in the PATROL KM for Unix. To turn on monitoring for these application classes, follow these steps:

1 Access the application class properties as described in Appendix A, “Accessing Menu Commands, InfoBoxes, and Online Help”.

2 Check the Active checkbox.

3 Click OK.

PATROL closes the dialog box, runs discovery for this application, and creates the associated collector, consumer, and standard parameters.


Either before or after loading the PATROL KM for Log Management, you must load the PATROL KM for Unix. The PATROL KM for Log Management application classes appear beneath the Unix OS application class. If the PATROL KM for Unix is not loaded, you will not be able to view the application classes for the PATROL KM for Log Management.

The PATROL KM for Log Management needs no special configuration to begin collecting data immediately after it has been installed and loaded.

For details about using the PARTOL KM for Log Management, see the PATROL for Log Management User Guide.

NOTE Almost all the functionality of the PATROL KM for Log Management must be accessed using a PATROL Console in developer mode. If a configuration task requires a console in developer mode, it will be noted in the instructions for that task.



Configure Recovery Actions for a Log File

The PATROL KM for Log Management allows you to define recovery actions when a log file reaches a specified size. The available recovery actions for log files are:

■ reduce the log file to 0 MB by deleting all the messages in the log file when the file reaches the size limit

■ back up the file into the pmg_backup subdirectory located in the same directory as the monitored log file and reduce the log file to 0 MB

The backup file is written to the same directory with an incremental number appended to the log file name each time the file is backed up. For example, the first time that the error_log.txt reaches its size limit, PATROL creates a backup file named error_log.txt1. The next time that it reaches its limit, PATROL creates a backup file named error_log.txt2 and so on.

Recovery actions run automatically by default; however, they can be configured to require user confirmation if the Run Attended option button is set to Yes.

Before You Begin

■ If you are adding a new log file to be monitored, follow the steps in the PATROL Knowledge Module for Log Management User Guide.

■ If you want to configure a recovery action for an existing log file, follow the steps in the PATROL Knowledge Module for Log Management User Guide.

■ You must be logged into a PATROL Console running in developer mode

Configure a Recovery Action for a Log File Based on File Size

To define a recovery action that will take place when the log file exceeds a defined file size, follow these steps:

1 Type a value in the Size Limit field (the value is in bytes – for example, 100 equals 100 bytes).

2 Select an Action option button to specify a recovery action for PATROL to take when the log file reaches the specified size limit

NOTE It is recommended that you periodically move the backup files to another location. The PATROL recovery action checks to make sure that the backup file name is not already in use. If hundreds or even thousands of backup files exist in the log directory, PATROL may take some time to complete this recovery action.


Configuring Recovery Actions

■ Nothing—PATROL continues monitoring the log file but does not attempt to reduce its size.

■ Delete—PATROL reduces the log file to 0 MB by deleting all the messages in the log file when the file reaches the size limit.

■ Backup and Delete— PATROL backs up the existing log file and reduces the log file to 0 MB

3 Click the Yes or No option button to indicate whether PATROL should Run Attended (prompt an operator for confirmation before performing a recovery action).

Configuring Recovery ActionsThis task describes how to configure the PATROL for Unix and Linux built-in recovery actions, which are corrective actions taken by PATROL when a parameter reaches a set value or is in a warning or alarm state.

About Recovery Actions

For the sake of discussion, the recovery actions that you define in the KM using the PATROL console are referred to as PATROL native recovery actions. The following sections explain the differences between PATROL native recovery actions and PATROL for Unix and Linux recovery actions.

PATROL Native Recovery Actions

When you define PATROL native recovery actions in the PATROL console, you associate the recovery actions with alarm and border ranges. These recovery actions run when the PATROL parameter value enters the specified range. The parameter may be in an OK, WARN, or ALARM state when the recovery action runs, depending on how you configure the parameter.

PATROL KM for Unix Recovery Actions

Unlike PATROL native recovery actions, the PATROL KM for Unix recovery actions run only when a parameter changes status. For example, when a parameter goes from an OK state to a WARN or ALARM state, or even when a parameter goes from an ALARM to an OK state.



If you don’t want the parameter to alarm until the recovery actions have been attempted, you must use PATROL native recovery actions, rather than PATROL KM for Unix recovery actions. However, you can use both types. For example, you could define PATROL native recovery actions and specify that the parameter enters a WARN or ALARM state only after all recovery actions fail. Then you could create a PATROL KM for Unix recovery action that runs only if the PATROL native recovery actions fail.

For more information about using PATROL KM for Unix recovery actions, see the PATROL Knowledge Module for Unix User Guide.

PATROL Native Recovery Actions

The following recovery actions, associated with the specified parameter, are provided by default with PATROL for Unix and Linux.

Configuring PATROL Native Recovery Actions

This section describes how to configure the PATROL for Unix and Linux built-in recovery actions, which are corrective actions taken by PATROL when a parameter reaches a set value or is in a warning or alarm state.

Before you begin

The recovery actions that are available to be configured depend on the KMs that you have loaded.

Table 10 PATROL for Unix and Linux Recovery Actions

Recovery Action & Description Parameter Auto Run?

FilesystemCleanup

Removes files once the percentage of the file system currently in use exceeds the threshold established in either Alarm1 or Alarm2 for the FSCapacity parameter. Also attempts to remove core dump files, and if the file system is /tmp or /tmp is mounted off this file system, attempts to remove from /tmp files that are 30 days or older.

FILESYSTEM\FSCapacity Requires Configuration

You must reboot to run this command.



To Configure Recovery Actions

1 Access the host application class menu as described in Appendix A, “Accessing Menu Commands, InfoBoxes, and Online Help” on page 99.

2 From the list of recovery actions, select the desired recovery action and click Accept.

3 From the list of recovery action instances, select the instance and click Edit. For information about which instance to select, see Table 11.

4 From the Edit Recovery Action dialog box, choose from the settings described in Table 12.

Table 11 Selecting a Recovery Action Instance

Purpose Recovery Action to Select

Remove files once the percentage of the file system currently in use exceeds the threshold established in either Alarm1 or Alarm2 for the FSCapacity parameter. Also attempts to remove core dump files, and if the file system is /tmp or /tmp is mounted off this file system, attempts to remove from /tmp files that are 30 days or older.

FilesystemCleanup

Table 12 Recovery Action Configuration Options

Setting Description Configuration Result

Run Unattended

If you select this setting, use the slide bar to set the amount of time PATROL waits for user input before it cancels the recovery action.

PATROL runs the recovery action automatically, without prompting you.

This recovery action applies to all FILESYSTEM instances.

Run Attended PATROL prompts you before running the recovery action.

This recovery action applies to all FILESYSTEM instances.

Do Not Execute PATROL does not perform the recovery action.

This mode is the default setting.



5 To save your changes, click Accept.

If a Problem Occurs

If you experience a problem when configuring recovery actions, see Appendix B, “Troubleshooting PATROL for Unix and Linux Problems.”.

NOTE For more information about the recovery action and its configuration options, click the Help button.




A p p e n d i x A
A Accessing Menu Commands, InfoBoxes, and Online Help
BMC Software offers several PATROL consoles from which you can view a PATROL Knowledge Module (KM). Because of the different environments in which these consoles run, each one uses a different method to display and access information in the KM. This appendix provides instructions for accessing the KM menu commands, InfoBoxes, and online Help on each of the PATROL consoles. See the online Help for specific PATROL for Unix and Linux components to view more detailed information about navigation in the PATROL Consoles.

Accessing KM Commands and InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101


Accessing KM Commands and InfoBoxes

Accessing KM Commands and InfoBoxesTable 13 provides information about how to access KM commands and InfoBoxes from the various PATROL consoles.

Table 13 Accessing KM Commands and InfoBoxes

ConsoleTo access menu commands

To accessInfoBoxes

PATROL Console for Microsoft Windows Servers

In either the Desktop tree tab or work area, right-click a computer or application icon and choose KM Commands from the pop-up menu.

In either the Desktop tree tab or the work area, right-click an application class or parameter icon and choose InfoBox from the pop-up menu.

PATROL Console for Unix In the work area, right-click a computer or application icon to display a pop-up menu that contains KM-specific commands.

With the middle mouse button, click an application class or parameter icon.

PATROL Central Operator - Windows Edition

In the navigation pane, right-click a managed system or application icon and choose Knowledge Module Commands from the pop-up menu.

In the navigation pane, right-click a PATROL object and choose InfoBox from the pop-up menu.

PATROL Central Operator - Web Edition

In the tree view area, right-click an application icon and choose Knowledge Module Commands from the pop-up menu.

In the tree view area, right-click a PATROL object and choose Infobox from the pop-up menu.


Accessing Online Help

Accessing Online HelpThis section provides instructions about accessing online Help from your PATROL console.

Table 14 provides information about how to access Help from each console.

NOTE If you are trying to access Help from a PATROL Console for Unix, see the PATROL Installation Reference Manual for specific instructions about installing and setting up a browser in the Unix environment.

Table 14 Accessing Online Help (Part 1 of 2)

ConsoleTo access product help

To access application class help To access parameter help

PATROL Console for Microsoft Windows Servers

■ Right-click the application icon for the PATROL KM on which you need help and choose KM Commands => Product Help.

■ From the console menu bar, choose Help => Help Topics => PATROL Knowledge Modules.

Double-click an application class in the KM tab of the console. From the Application Properties dialog box, click the Help tab. Then click Show Help.

■ Right-click a parameter icon and choose Help On from the pop-up menu.

■ Double-click a parameter icon; click the ? icon or Help button in the parameter display window.

■ Double-click a parameter in the KM tab of the console; from the properties dialog box, click the Help tab; then click Show Help.

PATROL Console for Unix

■ Right-click the application icon for the PATROL KM on which you need help and choose KM Commands => Product Help.

■ From the console menu bar, choose Help On => Knowledge Modules.

Choose Attributes => Application Classes and double-click the application name. Click Show Help in the Application Definition dialog box.

Right-click a parameter icon and click Help On.


Accessing Online Help

PATROL Central Operator - Windows Edition

From the console menu bar, choose Help => Help Topics. In the Contents tab, click the name of your product.

In the Operator tab of the navigation pane, select an application icon and press F1.

In the Operator tab of the navigation pane, select a parameter icon and press F1.

PATROL Central Operator - Web Edition

In the upper right corner of PATROL Central, click Help and choose PATROL KM Help.

In the tree view, right-click an application class and choose Help.

In the tree view, right-click a parameter and choose Help.

Table 14 Accessing Online Help (Part 2 of 2)

ConsoleTo access product help

To access application class help To access parameter help


A p p e n d i x B
B Troubleshooting PATROL for Unix and Linux Problems
This appendix describes some common problems you may experience while using PATROL KM for Unix, and provides suggestions resolutions for these problems.

Data Collection and Parameter Population Problems . . . . . . . . . . . . . . . . . . . . . . 104Error Messages in the

$BEST1_HOME/bgs/monitor/log/bgscollect_portnumber.log . . . . . . . . . . 105


Troubleshooting PATROL for Unix Problems

Troubleshooting PATROL for Unix ProblemsThe following sections describe some common problems you may encounter while running PATROL for Unix, and provide suggested resolutions for the problems.

Data Collection and Parameter Population Problems

If the PATROL KM for Unix does not seem to be collecting process data or populating parameters correctly, you may have entered an incorrect root password during installation. If you do not supply the correct root password, the installation program proceeds normally and installs all the necessary files successfully.

On HP-UX, you will not lose process data unless DCM/bgscollect is disabled.

This failure to collect data can also adversely affect other PATROL components and application classes, such as the ERP and database products, which rely on operating system process information.

Solution

If you entered the root password incorrectly, use the following procedure to resolve this problem:

1 Log onto the computer as root.

2 Type ./configure.sh.

3 Type ./b1config7120.sh.

NOTE The installation program prompts you for the root password, regardless of the target platform. However, only the HP-UX platform uses this information.

NOTE The name of b1confignnnn.sh script contains the nnnn variable, which always reflects the current version of the Perform Data Collector. In the example shown in step 3, the variable refers to version 7.1.20.



Error Messages in the $BEST1_HOME/bgs/monitor/log/bgscollect_portnumber.log

If the following error messages are displayed in the $BEST1_HOME/bgs/monitor/log/bgscollect_portnumber.log, you may be experiencing shortages with shared memory settings:

Sun Jun 25 00:00:08 2000 bgscollect (18871) Adding group <Group Name>

Sun Jun 25 00:00:08 2000 bgscollect (18871) SemLock::createSem() - semget(-1056834788) failed, Error = No space left on device

Sun Jun 25 00:00:08 2000 bgscollect (18871) SemLock::SemLock cannot create semaphore

Sun Jun 25 00:00:08 2000 bgscollect (18871) SemLock::lock() - semID_ invalid

Sun Jun 25 00:00:08 2000 bgscollect (18871) BaseQue::WriteGrab() - WRITE_LOCK failed

Sun Jun 25 00:00:08 2000 bgscollect (18871) BaseData::Open - ERROR: Open for write failed for group <Group Name>

Sun Jun 25 00:00:18 2000 bgscollect (18871) Removing group with name = <Group Name>

Solution

If you see these error messages in the $BEST1_HOME/bgs/monitor/log/bgscollect_portnumber.log, increase the shared memory segment and semaphore settings for the computer. See the following documentation for information about increasing shared memory and semaphore settings on your computer:

■ Unix man pages■ documentation for any other applications that are running on the computer■ “Shared Memory and Semaphore Resources for the PATROL Perform Data

Collector” on page 28.




A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Index

Symbols$PATROL_HOME 51%PATROL_CACHE% 51

Aaccounts

local partition requirements 25permissions needed for PATROL 25requirements, AIX computers 25requirements, customizations 25root access requirements 25umask settings 25

agentinstalling a KM to 35

AIX 37, 38AIX platforms

PATROL account requirements 25AIX systems

shared memory and semaphores 31

Bbacking up

current installation before migration 54BMC Software, contacting 2Bourne shell 62browsers

installing PATROL without one 41, 44uninstalling without one 65

CC shell 62collection method

changing 89determining type used 90specifying 89

colormap option 62console

installing a KM to 35console systems

overview 35custom installation option 40

custom processes, migrating 73–74customer support 3customizations

migrating 53migrating manually 57

customized PSLmigrating 58

Ddata

collection, specifying method 89data collection

troubleshooting 104DCM collection method 89deleting old version 55Digital UNIX 37, 38directory

PATROL installation default 42documentation library 20documentation, related 19

Eenvironment variable

PATROL_HOME 51environment variables

LANG 62PATH 62, 63PATROL_BROWSER 63setting for Help browser 62setting for the browser 62

eXceed 62exportfs command 38

Ffeatures, product 14–15first time installation 40first-time installation

typical installation option 39

Index 107


HHP Tru64 (Compaq Tru64 UNIX) systems

shared memory and semaphores 31HP Tru64 systems

shared memory and semaphores 31HPUX 37, 38HP–UX systems

shared memory and semaphores 31

Iinstallable images

creating for each platform 34installation

backing up before migration 54choosing a target machine 34creating vendor-specific installation images 34custom option 40default PATROL directory 42password troubleshooting 104preparing for 32-serveronly option 41, 44system requirements 23typical option 39verifying requirements 23without a browser 41, 44

installingclearing cache 55for the first time 40upgrading from an earlier version 49

KKM customizations

migrating manually 57KMs

determining if migratable 50installing individual 40upgrading from an earlier version 49

Korn shell 62

LLANG environment variable 62

Mmanaged systems

overview 35manual

migration of KM customizations 57manually starting a PATROL Agent 75migrating


customizations 53customized PSL 58determining if KM is migratable 50from an earlier version of the KM 49KM customizations manually 57

migrationbacking up current installation before 54

mounting the CD-ROM 38

NNetscape Navigator 61new PATROL user

installing for the first time 40new PATROL users

easy install option 39NFS Mount

a CD-ROM 38

Oonline Help

installing 35

Ppassword

supplying for installation 104troubleshooting 104

PATH environment variable 63PATROL

default installation directory 42PATROL account requirements

AIX platforms 25customizations 25

PATROL accountslocal partition requirements 25permissions needed 25root access requirements 25umask settings 25

PATROL Agentinstalling a KM to 35port number default 41starting manually 75

PATROL Agent for Unix 15PATROL Central Operator - Web Edition

installing 35PATROL Configuration Manager

migrating customized processes 74PATROL Console

and Netscape Navigator 61installing a KM to 35

PATROL KM for Event Management 17–18PATROL KM for Log Management 16–17PATROL KM for Unix 16


PATROL Knowledge Module for History Loader 18PATROL Perform Data Collector 18PATROL Security 18PATROL security

overview of levels 38PATROL_BROWSER

variable 63PATROL_BROWSER environment variable 63PATROL_CACHE 51, 55PATROL_HOME 51PCM

migrating customized processes 74pconfig utility

migrating customized processes 74Perform collector, existing 90planning

for installation 32platforms

creating vendor-specific installable images 34pop-up blocking software 32port number

default for PATROL Agent 41preparing

for installation 32product components

PATROL Agent for Unix 15PATROL KM for Unix 16

product features 14–15product support 3products

uninstalling in Unix environments 64PSL

collection method 89migrating 58

Rrecovery actions

built-in 15file system clean-up 15

remote installationcreating vendor-specific images 34

requirementsoverview 23privileges 37, 38system 23

Ssecurity

overview of levels 38selecting a collection method 89semaphores and shared memory segments 28-serveronly command

uninstalling 65

-serveronly option for installation 41, 44setting environment variables for Help browser 62share command 38shared memory and semaphores

AIX systems 31Digital UNIX (HP Tru64) systems 31HP Tru64 systems 31HP–UX 31Solaris systems 28

shellsBourne 62C 62Korn 62

Solaris 37, 38Solaris systems

shared memory and semaphores 28starting

PATROL Agent, manually 75support, customer 3system

requirements 23system roles

console systems 35managed systems 35overview of target machines 34

TTable 3, “PATROL for Unix Components that Require

setuid root Permissions,” on page 2-26 25target machines

overview 34technical support 3troubleshooting

data collection failures 104passwords for installation 104

typical installation option 39

Uumask setting, PATROL account 25uninstalling

without a browser 65uninstalling products

in Unix environments 64upgrading 49

backing up current installation before 54choosing a procedure 51from an earlier version of the KM 49

user account 63

Vvariable

PATROL_BROWSER 63

Index 109



Notes

*54132**54132**54132**54132*

*54132*

Documents

Patrol for Unix and Linux Unix Get Started