PATROL Getting Started

PATROL Getting Started
for UNIX and Linux
Supporting
PATROL version 9.5 for UNIX and Linux
August 2007
www.bmc.com
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 INC 2101 CITYWEST BLVD HOUSTON TX 77042-2827 USA Telephone 713 918 8800 or 800 841 2031 Fax 713 918 8000
Outside United States and Canada

Telephone (01) 713 918 8800 Fax (01) 713 918 8000
Copyright 2004-2007 BMC Software, Inc. BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners. IBM is a registered trademark of International Business Machines Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Oracle is a registered trademark of Oracle Corporation. Solaris and Sun are trademarks or registered trademarks of Sun Microsystems, Inc., in the U.S. and several other countries. UNIX is a registered trademark of The Open Group. 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.
Customer support
You can obtain technical support by using the BMC Software Customer Support website or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, see Before contacting BMC.
Support website
You can obtain technical support from BMC 24 hours a day, 7 days a week at http://www.bmc.com/support_home. From this website, you can
s s s s s s s
read overviews about support services and programs that BMC offers find the most current information about BMC products search a database for issues similar to yours and possible solutions order or download product documentation report an issue or ask a question subscribe to receive proactive e-mail alerts when new product notices are released find worldwide BMC 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 customer_support@bmc.com. (In the subject line, enter SupID:<yourSupportContractID>, such as SupID:12345). Outside the United States and Canada, contact your local support center for assistance.
Before contacting BMC

Have the following information available so that Customer Support can begin working on your issue immediately:
s
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
s s s
sequence of events leading to the issue 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
PATROL Getting Started for UNIX and Linux
Contents
Chapter 1 PATROL for UNIX and Linux Components and Capabilities 13 13 15 15 15 16 16 17 18 18 18 19 21 22 22 23 26 28 29 33 33 33 34 35 35 37 38 39 39 40 40 41 41 50 50 51 52
5
PATROL for UNIX and Linux Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Built-in Recovery Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL for UNIX and Linux Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL KM for UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL KM for Log Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL KM for Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL KM for History Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Perform Data Collector for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 2 Installing and Migrating PATROL for UNIX and Linux
Verifying Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Requirements for PATROL KM for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Requirements for the PATROL Perform Data Collector . . . . . . . . . . . . . . Shared Memory and Semaphore Resources for the PATROL Perform Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Boot Time Values for Shared Memory and Semaphore Parameters . . . . Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking for Product Patches or Fixes Before Installing. . . . . . . . . . . . . . . . . . . . . Determining How to Install Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the Version of the Installation Utility . . . . . . . . . . . . . . . . . . . . . . . . . Target Computers and Their Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining Where to Install KMs Based on Architecture. . . . . . . . . . . . . . . . . . . Mounting a CD on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Security Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking Security Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assessing and Implementing a Different Security Level . . . . . . . . . . . . . . . . . . . . Default and Custom Installation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . First-Time Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing for the First Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading from an Earlier Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automatic Migration of Console and Agent Customizations . . . . . . . . . . . . . . . . Determining Whether You Can Migrate KM Customizations . . . . . . . . . . . . . . . . Conditions for Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Determining the Location of PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Upgrade Scenarios for PATROL KM for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Upgrading Without Saving KM Customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Upgrading and Preserving KM Customizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Migrating Your KM Customizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Preparing to Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Migrating Customizations with the PATROL Configuration Manager . . . . . . . . 56 Moving Files from the PATROL_CACHE Directories . . . . . . . . . . . . . . . . . . . . . . . 56 Migrating Customizations Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Installing Using the Distribution Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Installing PATROL KM for UNIX Using the Distribution Server . . . . . . . . . . . . . 61 Considerations for Using Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Browser Version Required for Viewing PATROL Console for UNIX Help . . . . . 62 Additional Considerations for Using Online Help for UNIX . . . . . . . . . . . . . . . . . 62 Uninstalling PATROL for UNIX and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Determining the Version of the Installation Utility . . . . . . . . . . . . . . . . . . . . . . . . . 65 Uninstalling PATROL for UNIX and Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Uninstalling All Product Files Except Log Files and Configuration Files . . . . . . . 67 Uninstalling All Products and Associated Log Files and Configuration Files . . . 68 Where to Go from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Chapter 3 Loading and Configuring PATROL KM for UNIX 71
Preparing to Use PATROL KM for UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Migrating Customized Processes from Previous Versions of PATROL KM for UNIX . 72 Using the PATROL Configuration Manager to Migrate Customized Processes . 73 Using the pconfig Utility to Migrate Customized Processes. . . . . . . . . . . . . . . . . . 73 Manually Starting the PATROL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Loading and Preloading KMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Determining Which KMs to Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Determining Which KMs to Preload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Loading KMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Verifying What You Have Loaded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Preloading KMs on the PATROL Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Removing KMs from the Console and Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Unloading KMs from a PATROL Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Removing KMs from the Agent Preload List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Configuring PATROL KM for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Configuring the PATROL KM for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Specifying a Data Collection Method for the PATROL KM for UNIX . . . . . . . . . 89 Enabling the PRINTER and NETWORK Application Classes . . . . . . . . . . . . . . . . 92 Configuring the PATROL KM for Log Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Configuring Recovery Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 About Recovery Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 PATROL Native Recovery Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Configuring PATROL Native Recovery Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Appendix A
Accessing Menu Commands, InfoBoxes, and Online Help
99
Accessing KM Commands and InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Appendix B Troubleshooting PATROL for UNIX and Linux Problems 103
Troubleshooting PATROL KM for UNIX Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Data Collection and Parameter Population Problems . . . . . . . . . . . . . . . . . . . . . . 103 Error Messages in the $BEST1_HOME/bgs/monitor/log/bgscollect_portnumber.log . . . . . . . . . . . 105 Index 107
Contents
Figures
PATROL for UNIX and Linux Select Product and Components to Install Screen (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL for UNIX and Linux Select Product and Components to Install Screen when installing on UNIX (Custom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL for UNIX and Linux Select Product and Components to Install Screen when installing on Windows (Custom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Classes that Appear When UNIX3.kml Is Loaded . . . . . . . . . . . . . . . . . . Application Classes that Appear When LOG.kml Is Loaded . . . . . . . . . . . . . . . . . . . . Application Classes that Appear When EVENT_MANAGEMENT.kml Is Loaded . Application Classes that Appear When HISTORY.kml Is Loaded . . . . . . . . . . . . . . . COLLECTORS Icon (PSL Data Collection Method) . . . . . . . . . . . . . . . . . . . . . . . . . . . DCM Icon (DCM Data Collection Method) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Perform Home Directory Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 47 47 78 79 79 80 90 90 91
Figures
10
Tables
System Requirements for PATROL KM for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 PATROL KM for UNIX User Account Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 25 PATROL KM for UNIX Components that Require setuid root Permissions . . . . . . . 25 Additional Requirements for the PATROL Perform Data Collector . . . . . . . . . . . . . . 27 Settings for the /etc/system File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Versions That You Can Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Choosing an Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Default Values for PATROL Location Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 PATROL for UNIX and Linux.kml Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Rule Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Apply RuleSet Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 PATROL for UNIX and Linux Recovery Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Selecting a Recovery Action Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Recovery Action Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Accessing KM Commands and InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Parameters for ./agent_configure.sh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Tables
11
12
Chapter
1
13 15 15 15 16 16 17 18 18 18 19
PATROL for UNIX and Linux Components and Capabilities

1
This chapter provides information about components within the PATROL product for UNIX and Linux, and how those components can help you to monitor computers in your environment. The following topics are discussed in this chapter: PATROL for UNIX and Linux Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Built-in Recovery Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL for UNIX and Linux Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL KM for UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL KM for Log Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL KM for Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL KM for History Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Perform Data Collector for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PATROL for UNIX and Linux Features

PATROL for UNIX and Linux provides current and historical information through a centralized console so you can easily view and manage your entire UNIX and Linux environments. 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 wrongpreventing downtime and its costs to your business.
Chapter 1
13
PATROL for UNIX and Linux Features
Product features include:

s
monitors a complete range of UNIX and Linux operating system parameters including: system-wide CPU usage disk and I/O usagetracks usage to locate overused disks file system resourcesdetermines disks that are heavily used or running out of space kernel resource usagemonitors use of the kernel i-node table, file table, and process table log filesmonitors the size and content of specified log files memory activitymonitors paging, I/O caching, and swapping network activitymonitors TCP/IP traffic level network traffictracks network traffic related to Remote Procedure Call and Network File System SMP applicationmonitors the use of individual CPUs in an SMP system system swap filesmonitors the percentage of used and free swap space user sessions and processestracks users on the system process presencemonitors the process table and alerts based on the presence or absence of user-defined command text compositesCPU > 90 and Page-Outs > 1 can be used to warn of a physical memory deficit
provides annotated data points for drilling down into problems 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
14
PATROL for UNIX and Linux Components
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
NOTE
The PATROL Knowledge Module for Log Management product also provides built-in recovery actions. See the PATROL Knowledge Module for Log Management User Guide for information.
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.

The following sections briefly describes each of the components of the PATROL for UNIX and Linux product.
PATROL Agent
The PATROL Agent product 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. Using information from a PATROL KM, a PATROL Agent can
s s s s s s
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.
Chapter 1
15
PATROL KM for UNIX

The PATROL Knowledge Module (KM) product for UNIX allows you to monitor and manage system resources in a UNIX and Linux environments. The PATROL KM for UNIX can
s s s s s s s
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 file system capacity monitor virtualization technology on IBM AIX micropartitioned POWER5 servers and Sun Solaris 10 systems
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 Knowledge Modules (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
s
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
16
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:
s
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
Chapter 1
17
PATROL KM for History Loader

The PATROL History Loader Knowledge Module 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 History Loader Knowledge Module 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 History Loader Knowledge Module, see the PATROL History Loader Knowledge Module User Guide.
PATROL Perform Data Collector for UNIX

The PATROL Perform Data Collector product 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:
s s
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 39 for more information on setting up security within your monitored environment. For detailed information about PATROL security, see the PATROL Security User Guide.
18
Related Documentation
For additional information about PATROL for UNIX and Linux product components, see the following documentation:
s s s s s s s s s s s s
PATROL Agent Reference Manual PATROL Knowledge Module for UNIX User Guide PATROL for UNIX and Linux Release Notes PATROL Knowledge Module for Event Management User Guide PATROL History Loader Knowledge Module User Guide PATROL Knowledge Module for Log Management 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 History Loader Knowledge Module online Help
For information about the PATROL for UNIX and Linux parameters, see the online Help systems and the PATROL Parameter Reference Database. PATROL for UNIX and Linux parameter information is now available online in the Parameter Reference Database. This database contains reports in the CSV file format that you can download and use to help you gather default settings and plan for installation and customization. You can download parameter reports for up to three versions of a product. To access the Parameter Reference Database, visit the Customer Support website at http://www.bmc.com/support_home and click Product Documentation => Parameter Reference Database.
Chapter 1
19
For additional information about PATROL, see the following documentation:

s s s s s s s s s s s s s s s
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
To view the complete PATROL documentation library, visit the support page on the BMC website at http://www.bmc.com/support_home. 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.
20
Chapter
Installing and Migrating PATROL for UNIX and Linux

2
This chapter provides the information that you need to install and migrate the PATROL product 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Requirements for PATROL KM for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Requirements for the PATROL Perform Data Collector . . . . . . . . . . . . . . Shared Memory and Semaphore Resources for the PATROL Perform Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Boot Time Values for Shared Memory and Semaphore Parameters . . . . Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking for Product Patches or Fixes Before Installing. . . . . . . . . . . . . . . . . . . . . Determining How to Install Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the Version of the Installation Utility . . . . . . . . . . . . . . . . . . . . . . . . . Target Computers and Their Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining Where to Install KMs Based on Architecture. . . . . . . . . . . . . . . . . . . Mounting a CD on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Security Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking Security Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assessing and Implementing a Different Security Level . . . . . . . . . . . . . . . . . . . . Default and Custom Installation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . First-Time Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing for the First Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading from an Earlier Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automatic Migration of Console and Agent Customizations . . . . . . . . . . . . . . . . Determining Whether You Can Migrate KM Customizations . . . . . . . . . . . . . . . . Conditions for Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the Location of PATROL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade Scenarios for PATROL KM for UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading Without Saving KM Customizations . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2 Installing and Migrating PATROL for UNIX and Linux
22 22 23 26 28 29 33 33 33 34 35 35 37 38 39 39 40 40 41 41 50 50 51 52 52 53 54
21
Verifying Installation Requirements
Upgrading and Preserving KM Customizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Migrating Your KM Customizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Preparing to Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Migrating Customizations with the PATROL Configuration Manager . . . . . . . . 56 Moving Files from the PATROL_CACHE Directories . . . . . . . . . . . . . . . . . . . . . . . 56 Migrating Customizations Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Installing Using the Distribution Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Import a CD Image or Customized Installation Package into the Distribution Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Installing PATROL KM for UNIX Using the Distribution Server . . . . . . . . . . . . . 61 Considerations for Using Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Browser Version Required for Viewing PATROL Console for UNIX Help . . . . . 62 Additional Considerations for Using Online Help for UNIX . . . . . . . . . . . . . . . . . 62 Uninstalling PATROL for UNIX and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Determining the Version of the Installation Utility . . . . . . . . . . . . . . . . . . . . . . . . . 65 Uninstalling PATROL for UNIX and Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Uninstalling All Product Files Except Log Files and Configuration Files . . . . . . . 67 Uninstalling All Products and Associated Log Files and Configuration Files . . . 68 Where to Go from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Before you install PATROL for UNIX and Linux, make sure that your systems meet all requirements outlined in this section.
Supported Platforms
See the PATROL for UNIX and Linux Release Notes for a list of supported platforms. In addition, check the product page for version 9.4.00 of PATROL KM for UNIX on the BMC Software Customer Support website. Technical Bulletins on the product support page may contain information about platforms that were supported after the last release.
22
System Requirements for PATROL KM for UNIX

Before installing the product, verify that the target computers meet the requirements listed in Table 1.
NOTE
For specific versions of the products and operating systems that are supported, see the Release Notes for the version of the product that you are installing.
Table 1
Resource
System Requirements for PATROL KM for UNIX (Part 1 of 2)

Requirements This product uses Common Installer, which requires a browser. Comments For a list of supported browsers, see the PATROL Installation Reference Manual.
browser for installing the product browser to support online Help for PATROL for UNIX Console
Use Netscape Navigator version 3.014.78 see Browser Version Required for Viewing to use online Help with PATROL for PATROL Console for UNIX Help on page 62 UNIX.
219-MB for PATROL Agent for UNIX 115-MB for PATROL Console for UNIX disk space less than 1-MB for PATROL KM for Log Management
without components and KMs without components and KMs NA
less than 2-MB for PATROL KM for UNIX NA
less than 1-MB for PATROL KM for Event NA Management installing into a PATROL 3.6.50 UNIX environment installing into a UNIX environment without a browser license You must launch the installation utility from the command line and use the -releaseversion option. You must launch the installation utility from the command line and use the -serveronly command line option. see Upgrading from an Earlier Version on page 50
See either To Install Using the Default Installation Type on page 42 or To Install Using the Custom Installation Type on page 45. If you do not have a permanent license, contact your BMC Software sales representative or the BMC Software Contract Administration department for licensing information.
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. 256-color display TCP/IP network communications must be available
monitor network
screen resolution should be set to at least 600 x 800 pixels NA
Chapter 2
23
Table 1
Resource ports
System Requirements for PATROL KM for UNIX (Part 2 of 2)

Requirements If you are installing an agent or console with PATROL KM for UNIX, you must specify the port number to connect to all the agent computers. 32-MB for PATROL Agent 48-MB for PATROL Console for UNIX versions 7.1.41 or later Comments The default port number for the PATROL Agent is 3181.
random access memory (RAM) PATROL Perform Collector security levels
NA NA NA
PATROL Security Levels on page 39
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 enterprises 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 24 for information about user account requirements.
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:
24
Table 2
Resource
PATROL KM for UNIX User Account Requirements

Requirements the user account .login, .profile, .cshrc, and .kshrc files should not contain any customizations such as aliases or nondefault prompts 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 (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.
account file customizations
directory permissions
file systems
IBM AIX computers root account
on AIX computers, the PATROL installation account must be a member of the adm group 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 KM for UNIX components that will need setuid root access ensure that the umask setting for the installation account is set to 022
umask setting
Components that Require setuid Permissions

Table 3 on page 25 lists the components which will require setuid root permissions. The table also provides an explanation of why each component needs setuid root permissions.
NOTE
Processes initiated by KM menu commands will prompt you for the root password.
Table 3
Component
PATROL KM for UNIX Components that Require setuid root Permissions (Part 1 of 2)
Uses setuid root permissions to validate user name and password information by accessing the /etc/passwd file validate the user name and password impersonate (via su) other user accounts to execute various KM commands
PATROL Foundation Components PATROL Console PATROL Agent
Chapter 2
25
Additional Requirements for the PATROL Perform Data Collector
Table 3
Component
PATROL KM for UNIX Components that Require setuid root Permissions (Part 2 of 2)
Uses setuid root permissions to listen on privileged port numbers (port numbers that are less than 1024)
SNMP Master Agent (snmpmagt) PATROL Perform Data Collector (bgscollect) procstat command FILESYSTEM application NETWORK application NFS application
PATROL KM for UNIX Components read into kernel memory (/dev/mem and /dev/kmem) read certain device files access kernel memory mount and unmount file systems clean up file systems (this is a recovery action) delete hosts from the address resolution protocol (ARP) cache run UNIX to UNIX copy (UUCP) utilities reset NFS counters to zero start and stop printers PRINTER application start and stop print queues delete print jobs move print jobs PUKSERVER.XPC (applicable only for Solaris non-global zones) for access to processes in /proc filesystem for retrieving full command-name from processs address space and CPU utilization of other users processes

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.
26
Table 4
Resource

Requirements 25-MB to 100-MB on each node Comments 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).
Collect Data Repository
directory (history data repository) /etc file system
you must specify a name for the history data repository at least 3-MB of free disk space on all systems
if a directory name is not specified, you will not be able to use the history features of the investigative node 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 this requirement must be met on all nodes
History and at least 75-MB UDR Repository libraries
ensure that the LANG variable for your By default, the LANG environmental variable systems is set to the correct locale that you for most systems is set to English, unless you are working on an internationalized platform. want to use 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 UNIX shells
you must use full path names when you specify directories during the installation process Bourne shell
do not use the tilde (~) or relative path names (./.) during the installation The installation script uses the Bourne shell; the /bin/sh file must be available for the installation script to run properly. All the scripts are converted to use Bourne shell. See Shared Memory and Semaphore Resources for the PATROL Perform Data Collector on page 2-28.
Korn shell shared memory segments and semaphores you must set shared memory segments and semaphores to use the PATROL Perform Data Collector
Chapter 2
27
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 KM 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.
NOTE
Occasionally, a system may not require an increase to the shared memory or semaphores. After PATROL KM for UNIX is installed, two binaries help you to determine the amount of resource available:
s s
/usr/adm/best1_default/bgs/bin/getseminfo /usr/adm/best1_default/bgs/bin/getshminfo
If the total amount available meets the recommended total before bsgcollect is run on the system, then it is not necessary to increase the shared memory or semaphores values.
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.
NOTE
Because these changes alter kernel settings, you must restart the system for the changes to take effect.
BMC Software recommends that you reset these values after installation, as indicated in Table 5 on page 29. 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.
28
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 parameters boot time value, use the guidelines in Table 5 on page 29.
NOTE
Instance can be a system or an RDBMS collect.
Table 5
Settings for the /etc/system File (Part 1 of 3)

Which is... Number of semaphore identifiers, systemwide Do This... Add (50 + 50 multiplied by the number of instances) to the current value Example If the current value on the computer is 100 and you have one system collector and one Oracle collector running on the computer, set the value to 250. Note: Perform allocates two semaphores per ID, so use 50 instead of 25.This semaphore is obsolete in Solaris 10 and later.
For Parameter... IPC Semaphores semsys: seminfo_semmns
semsys: seminfo_semmap
Number of entries in Set equal to the semaphore map semsys:seminfo_semmni + two
If semsys: seminfo_semmni was set to 256, set semsys: seminfo_semmap equal to 258 Note: This semaphore is obsolete in Solaris 8 and later.
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.
Chapter 2
29
Table 5
semsys:

Which is... Do This... Example As a general rule, you may want to set seminfo_semmnu equal to seminfo_semmni to provide for an undo structure for each semaphore. This semaphore is obsolete in Solaris 10 and later. Maximum number of No specific recommendation. undo structures, PATROL Perform does not use system-wide undo structures
For Parameter...
seminfo_semmnu
semsys: seminfo_semmsl semsys: seminfo_semopm seminfo_semume seminfo_semvmx seminfo_semaem IPC Shared Memory shmsys: shminfo_shmm
The maximum number of semaphores per unique identifier
No specific recommendation. semsys:seminfo_semmsl PATROL Perform will attach two should remain at its current value. semaphores per identifier. No specific recommendations for any of these semaphore settings. They have no impact on the operation of PATROL Perform. seminfo_semume, seminfo_semvmx, and seminfo_semaem are obsolete in Solaris 10 and later.
The maximum size of a shared memory segment.
No specific recommendation. The PATROL Perform allocates default value is high enough for small segments, so this PATROL Perform. value will never be a limiting factor. Note: This semaphore is obsolete in Solaris 10 and later.
shmsys: shminfo_shmmin
Minimum size of an IPC shared memory segment that can be created
The system default of 1 is recommended.
shmsys:shminfo_shmmin should always be set to 1. Note: This semaphore is obsolete in Solaris 9 and later.
30
Table 5
shmsys:

Which is... Do This... Example If the current value of the machine is 100 and you will be running one system collector, set the value to 150. Note: This semaphore is obsolete in Solaris 10 and later. System wide limit on Add (25 + 25 multiplied by the the number of shared number of instances) to the memory segments current value
For Parameter...
shminfo_shmmni
shmsys: shminfo_shmseg
Limit on the number Add (25 + 25 multiplied by the number of instances) to the of shared memory current value 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. Note: This semaphore is obsolete in Solaris 9 and later.
On Solaris 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. 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
Chapter 2
31
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 HPUX.
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.
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.
32
Preparing for Installation

BMC Software recommends that you first install PATROL KM for UNIX on a limited number of development or test machines, then configure and test PATROL KM for UNIX before installing it onto production machines.
Installation Prerequisites
Before you install, you must
s s s s s s
ensure that all system requirements are met (see page 22) determine how to install products (see page 34) ensure you are using the appropriate version of the installation utility (see page 35) understand target machines and their roles (see page 35) choose between Default and Custom installation options (see page 40) understand PATROL security options (page 39)
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. Before you begin installing PATROL KM for UNIX, BMC Software recommends that you check the BMC Software Customer Support Web page for the version that you are installing to determine whether a patch is available.
Chapter 2
33
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 a PATROL Agent on each computer that you want to monitor, and PATROL KM for UNIX 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 images control file by using the ctltool.
NOTE
s
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 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 a single 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.
For more information about creating, distributing, and installing installable images, and about using the ctltool, see the PATROL Installation Reference Manual.
34
Determining the Version of the Installation Utility

This version of the installation utility shipped with the product 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 the one shipped with the product you are installing, 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.
Roles Performed by Computers in the PATROL Architecture

The roles performed by computers in the PATROL Architecture are
s
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)
Chapter 2
35
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
s
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 products respective online help systems and the following documents:
s
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
36
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:
s s
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:
s s s s
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.
Chapter 2
37
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

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.
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.
Platform AIX Tru64 HP-UX PA1.0 Version 10.20 or later Linux Solaris Mount Command mount -r -v cdrfs /dev/cd0 /cdrom /sbin/mount -t cdfs /devices/disk/cdrom_device /cdrom mount -F cdfs -o ro /dev/dsk/drive_for_cdrom/cdrom mount /dev/cdrom /path_to_target_mount_point Volume Manager (/usr/sbin/vold) automatically mounts. Otherwise, use mount -r -F hsfs /dev/sr0 /cdrom
If a problem occurs, consult your system administrator or read the man page for mount.
4 Log off.
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:
38
PATROL Security Levels
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.
Platform AIX, Tru64, HP-UX PA1.0 Linux Solaris Mount Command mount host:/cdrom /mnt/cdrom mount host:/path_to_file_system_to_be_exported /path_to_target_mount_point mount host:/cdrom/cdrom0 /mnt/cdrom/cdrom0
If a problem occurs, consult your system administrator or read the man page for mount.
4 Log off.
PATROL Security Levels

You 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.
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.
Checking Security Levels

To check the security level of a previously installed agent, console server, or console, perform the following steps:
Chapter 2
39
Default and Custom Installation Types
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:
esstool policy -a
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.
Default and Custom Installation Types

The installation utility prompts you to select one of the following installation types:
s
The Default installation type uses default values for all optional configuration information. It prompts you only for mandatory configuration information. This type is for any 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.
NOTE
If you are installing PATROL KM for UNIX to an existing PATROL Agent or Console environment that is not in the default installation directory, use Custom. Do not use Default. Default 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.
40
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 of the following situations: You want to install individual components rather than the entire product. You want to specify s the port numbers that components use to communicate with each other s a security level greater than basic security s any other product settings that a user might want to change. You are upgrading PATROL KM for UNIX 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.
The installation utility offers two types of installations: Default and Custom. For a description of the two types of installations, see Default and Custom Installation Types on page 40.
Installing for the First Time

You can install PATROL KM for UNIX using either the Default or Custom installation type. Regardless of the type of installation that you choose, you must repeat this installation process for each computer on which you want to install PATROL KM for UNIX. See page 40 for guidelines for using each installation type.
NOTE
By default, the Default 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.
Before you begin

s
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.
Chapter 2
41
If you want to install PATROL KM for UNIX 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 38.
To Install Using the Default Installation Type 1 From the installation PATROL KM for UNIX CD or from an installation image that
has been electronically downloaded from an EPD site and extracted, run setup.sh.
NOTE
You can download the complete PATROL for UNIX and Linux product solution or individual product components from the product EPD Web site.
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.
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 Install products on this computer
now and click Next to continue.
5 In the Specify Installation Directory window, accept the default directory and click
Next to continue.
By default, PATROL KM for UNIX will be installed into the /opt/bmc directory.
42
6 In the Select Type of Installation window, select Default and click Next to continue. 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:
s
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 35.
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 (Default)
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.
Chapter 2
43
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.
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.
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.
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.
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
s
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 24).
14 In the Kernel Data Collector Properties Unix - General window, select Default Link
and click Next.
44
15 In the Review Selections and Install window, review the selections carefully to
ensure that they are correct:
s s
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.
16 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.)
17 (Optional) In the results window, click View Log to review the details of the
installation.
18 Click Finish to close the installation utility. To Install Using the Custom Installation Type 1 From the installation PATROL KM for UNIX CD or from an installation image that
has been electronically downloaded from an EPD site and extracted, run setup.sh.
NOTE
You can download the complete PATROL for UNIX and Linux product solution or individual product components from the product EPD Web site.
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.
2 In the Welcome to the Installation Utility window, click Next to begin your
installation.
Chapter 2 Installing and Migrating PATROL for UNIX and Linux 45
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 Install products on this computer
now and click Next to continue.
5 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 KM 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 48.
6 From the Select Type of Installation Window, select Custom and click Next. 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:
s
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 35.
8 From the Select Products and Components to Install screen, select the items that
you want to install (see Figure 2 on page 47) and click Next.
46
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.
NOTE
If you are installing PATROL KM 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 47. The PATROL Agent is not listed because the PATROL Agent that is a component of PATROL KM 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.
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.
Chapter 2
47
If the directory that you enter does not exist, the installation utility attempts to create it. The installation utility then begins to copy the files required for the product installation from the current CD image. This process may take a few moments.
NOTE
Ensure 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.
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 and click Next. If you copied the CD to your computer, enter the directory where the image is located and click Next.
NOTE
On UNIX systems, you cannot eject removable media while the media is being accessed. To swap CDs, you might need to exit the installation utility and then, from a command line, cd to / and restart the utility by specifying the absolute path; for example, /mnt/cdrom/setup.sh.
11 When the next Additional CDs Needed screen is displayed, follow the instruction 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. 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 5 on page 46.
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
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.
48
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 24).
NOTE
The Confirm BMC Product Startup Information window described in step 15 may not be displayed if you are not installing into a managed system.
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.
NOTE
If your previous installation used a different port number, change the default to the current port number for the PATROL Agent.
B In the Restart the PATROL agent automatically? field, select the appropriate
option:
s
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 Kernel Data Collector Properties Unix - General window, select Default Link
and click Next.
17 In the Review Selections and Start Install window, review the selections carefully
to ensure that they are correct:
s s
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.
18 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.)
Chapter 2
49
Upgrading from an Earlier Version
19 (Optional) In the results window, click View Log to review the details of the
installation.
20 Click Exit to close the installation utility. Where to go from here

See Chapter 3, Loading and Configuring PATROL KM for UNIX.

If you have a previous version of PATROL KM for UNIX installed on the target computer, you have the following options for upgrading to the new version:
s s
Upgrading Without Saving KM Customizations on page 54 Upgrading and Preserving KM Customizations on page 54
NOTE
You can migrate using only configuration-based customizations. There is no migration path that carries forward custom modifications to the KM files, PSL files, and event catalogs.
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
s s
agentsstored in the agent configuration file consolesstored in the console cache files
are preserved and incorporated into the new version automatically.
50
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 can be migrated to the new version. See Table 6 to determine whether migration is supported for your current version of PATROL KM for UNIX. If migration is supported, choose the installation procedure Migrating Customizations Manually on page 58 to migrate your customizations.
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
Component
Versions That You Can Migrate

Versions 8.3.06 or later N/A 1.1.00 or later
PATROL KM for UNIX PATROL KM for Event Management PATROL KM for Log Management
PATROL History Loader Knowledge Module 1.4.06 or later
Chapter 2
51
Conditions for Upgrading

Use Table 7 to help you choose an upgrade procedure. Table 7 Choosing an Upgrade Procedure
If You Have This Situation
s
Use This Procedure Upgrading Without Saving KM Customizations
have not made any customizations to the KM files in your previous version of PATROL KM for UNIX want to overwrite customizations you made to the KM files with the default values of the new version of PATROL KM for UNIX have a currently installed version of PATROL KM for UNIX that cannot be migrated (See Table 6 Versions That You Can Migrate on page 51)
Upgrading and Preserving KM Customizations
made customizations to the KM files in your previously installed version of PATROL KM for UNIX and want to save those customizations and migrate them to the new version
Determining the Location of PATROL

During the installation process, the PATROL Installation Utility records where it installs PATROL components in environment variables.
NOTE
Throughout this section, all references to PATROL_HOME represent and all references to $PATROL_HOME 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. See Table 8 Default Values for PATROL Location Variables on
page 53
52
Upgrade Scenarios for PATROL KM for UNIX
Table 8
Variable
Default Values for PATROL Location Variables

Default Value /opt/bmc/<patrol_directory>a/$TARGETb $HOME/<patrol_directory> a/$TARGETb
PATROL_HOME PATROL_CACHE
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.
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:
Type of Shell Bourne and Korn Procedure 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

There are several different scenarios for upgrading PATROL KM for UNIX. These scenarios include
s s s
not migrating customizations migrating customizations using PATROL Configuration Manager migrating customizations manually
Chapter 2
53
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 over your previous version after moving or deleting PATROL KM for UNIX files from the PATROL_CACHE. See First-Time Installation on page 41 for instructions.
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.
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 you want to preserve any customizations you have made to the .km files in the previous version of PATROL KM for UNIX. You must first migrate your customizations from the old version of PATROL KM for UNIX 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 can include changes to the parameter alarm ranges, states, or other parameter properties. You can manually migrate customizations using the PATROL Configuration Manager.
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 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.
54
Before you begin

If you plan to migrate your customizations, determine whether you can migrate from a previous version of PATROL KM for UNIX. See Table 6 on page 51 to determine whether migration is supported for your current version.
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:
File Type executables and data console customizations Directory PATROL_HOME/.. for agent and console installation directories PATROL_CACHE for the console working cache
Where to go from here

If you are migrating customizations using the PATROL Configuration Manager (recommended), see Migrating Customizations with the PATROL Configuration Manager on page 56. If you are moving files from the PATROL_CACHE directories, see Moving Files from the PATROL_CACHE Directories on page 56. If you are migrating customizations manually, see Migrating Customizations Manually on page 58.
Chapter 2
55
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.
s
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. 3 Install the new version of PATROL KM for UNIX as described in the section
Installing for the First Time on page 41.
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 58.
Moving Files from the PATROL_CACHE Directories

Before you install, you must move the current PATROL KM for UNIX 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 files with the following naming patterns to a directory outside the PATROL installation and delete them from PATROL_CACHE\knowledge and PATROL_CACHE\psl.
56
Naming Patterns for the PATROL KM for UNIX

s s s s s s s s s s s s s s s s s s s s s s s s s s s s s
add_* apilib* bds_* bsd_* ChkUnldDcm* Composites* CPU* DISK* FILESYS* FSDebug* haag_* internal_* Linux* make_* most_* network_* nis_* osf_* POOL* prn_* response_* sec_* set* SNMP* statvfs_* SWAP* uname_* USERS* VIR*
s s s s s s s s s s s s s s s s s s s s s s s s s s s s s
aix_* appclass* blackout* Capture* COLLECTORS* Configure* DCM* display_* Filesys* get_* HP* KERN* linux_* mem_* net_* NFS* not_* PATROL* PRINTER* PROC* RS6000* SECURITY* SINIX* SOLARIS* stop_* tcp_* UNIX* usr_* ZONE*
s s s s s s s s s s s s s s s s s s s s s s s s s s s s
all_* BASE3* boot_* cat_* COMPOSITE* cpu* debug_* edit_* fs_* HAAG* hp_* kern* list_* MEMORY* NETWORK* nfs_* OSF* pkmunix* printer_* proc* SCHEDULER* sequent_* SMP* solaris_* svr4_* toggle_* unix_* uu*
Naming Patterns for the PATROL KM for Log Management

s s
LOG* PMG*
Chapter 2
57
Naming Patterns for the PATROL History Loader Knowledge Module

s s s s s s s
H*.km
H*.psl
History-* History_Loader* Hist* COM_DEB_* COM_STAT_*
See the PATROL History Loader Knowledge Module User Guide for more information about migrating the PATROL History Loader Knowledge Module.
Migrating Customizations Manually

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. 3 Install the new version of PATROL KM for UNIX as described in the section
Installing for the First Time on page 41.
4 Identify and record the coding changes, which represent your customizations, in
PATROL KM for UNIX by comparing the content of the ASCII files in the newly installed PATROL KM for UNIX 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 by performing

the following steps:
A Restart the PATROL console. B Load the newly installed PATROL KM for UNIX. C Using a PATROL console in developer mode, enter the customizations that you
identified in step 4 on page 58, one by one.
58
Installing Using the Distribution Server
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:
s
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.

PATROL for UNIX and Linux can be installed locally to a single computer or remotely to multiple computers using BMC Softwares 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
s
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.
Chapter 2
59
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.
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.
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. 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.
60
11 When the Import Status screen is displayed, click Close. Where to go from here
To remotely install PATROL KM for UNIX 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 Using the Distribution Server.
Installing PATROL KM for UNIX 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.
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. 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.
Chapter 2
61
Considerations for Using Online Help
For detailed instructions about how to perform remote installations with the Distribution Server, see the Distribution Server Getting Started Guide.

If you plan to install PATROL KM for UNIX 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:
s s
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/.
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.
62
In addition, you must be aware of the following restrictions:

s
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 Bourne Korn C Export Command for LANG Variable LANG=C export LANG export LANG=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.
Chapter 2
63
Type of Shell Bourne Korn C
Export Command for PATH Variable PATH=$PATH:/netscape_location export PATH export PATH=$PATH:/netscape_location setenv PATH=$PATH:/netscape_location
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:
Type of Shell Bourne Korn C Export Command for PATROL_BROWSER Variable PATROL_BROWSER=netscape -display $DISPLAY -install -iconic export PATROL_BROWSER export PATROL_BROWSER=netscape -display $DISPLAY -install iconic setenv PATROL_BROWSER=netscape -display $DISPLAY -install iconic
To use different arguments, set the value of PATROL_BROWSER to the appropriate string.
EXAMPLE
For a Korn shell: export PATROL_BROWSER=/usr/local/bin/netscape -raise
64
Uninstalling PATROL for UNIX and Linux

To 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. 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
s s s
Distribution Server Getting Started PATROL Knowledge Module for UNIX User Guide PATROL Agent Reference Manual

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.
Chapter 2
65
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.
66
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 65.
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 -log Description 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 Value 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. path to output log file; any valid path and file name (with a .txt extension)
This file contains all messages about the If a space exists in the path, the entire path must be enclosed in quotation progress of the installation that are marks. normally sent to standard output.
Chapter 2
67
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:
thorinst.sh -uninstall /opt/bmc/Uninstall/Install/instdata/uninstall.ctl -log /var/logs/NetworkLogs/MyLogs.txt -output /var/adm/NetworkLogs/MyLogs.out
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 65.
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
68
Use the following table to help determine the log file and output log file locations:
Option -log Description 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 Value 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. path to log file; any valid path and file name (with a .txt extension)
This file contains all messages about the If a space exists in the path, the entire progress of the installation that are path must be enclosed in quotation normally sent to standard output. marks.
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:
thorinst.sh -uninstall /opt/bmc/Uninstall/Install/instdata/uninstall-all.ctl -log /var/logs/NetworkLogs/MyLogs.txt -output /var/adm/NetworkLogs/MyLogs.out
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.
Chapter 2
69
Where to Go from Here
Where to Go from Here

The following table lists other topics and where you can find them:
Topic Source of Information
overview of PATROL KM for UNIX and Chapter 1, PATROL for UNIX and Linux its features Components and Capabilities and PATROL KM for UNIX online Help setting up and configuring PATROL KM for UNIX Chapter 3, Loading and Configuring PATROL KM for UNIX and PATROL KM for UNIX online Help
instructions about how to access the KM Appendix A, Accessing Menu Commands, menu commands, InfoBoxes and online InfoBoxes, and Online Help Help troubleshooting information using PATROL for UNIX and Linux functionality to monitor and manage UNIX and Linux operating systems Appendix B, Troubleshooting PATROL for UNIX and Linux Problems PATROL Knowledge Module for UNIX User Guide and PATROL for UNIX online Help
PATROL Agent configuration variables PATROL Knowledge Module for UNIX User Guide pertaining to PATROL KM for UNIX and PATROL for UNIX online Help definitions and default values for parameters consumer and collector parameter dependencies step-by-step procedures and detailed descriptions of the applications, menu commands, parameters, and InfoBoxes PATROL Knowledge Module for UNIX User Guide and PATROL Knowledge Module online Help systems PATROL Parameter Reference Manual and PATROL Knowledge Module online Help systems PATROL Knowledge Module for UNIX User Guide and PATROL KM for UNIX online Help
70
Chapter
Loading and Configuring PATROL KM for UNIX

3
This chapter provides information about how to begin configuring and using PATROL KM for UNIX. 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.
NOTE
s
For information about configuring the PATROL History Loader Knowledge Module, see the PATROL History Loader Knowledge Module User Guide. For information about configuring the PATROL Knowledge Module for Event Management, see the PATROL Knowledge Module for Event Management User Guide.
The following topics are discussed in this chapter: Preparing to Use PATROL KM for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrating Customized Processes from Previous Versions of PATROL KM for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the PATROL Configuration Manager to Migrate Customized Processes . Using the pconfig Utility to Migrate Customized Processes . . . . . . . . . . . . . . . . . Manually Starting the PATROL Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading and Preloading KMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining Which KMs to Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining Which KMs to Preload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading KMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying What You Have Loaded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preloading KMs on the PATROL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing KMs from the Console and Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unloading KMs from a PATROL Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing KMs from the Agent Preload List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring PATROL KM for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the PATROL KM for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying a Data Collection Method for the PATROL KM for UNIX . . . . . . . . . 72 74 73 73 74 74 74 74 75 77 80 85 85 88 89 89 89
Chapter 3
71
Preparing to Use PATROL KM for UNIX
Configuring the PATROL KM for Log Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Enabling the PRINTER and NETWORK Application Classes . . . . . . . . . . . . . . . . 92 Configuring Recovery Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 About Recovery Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 PATROL Native Recovery Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Configuring PATROL Native Recovery Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Preparing to Use PATROL KM for UNIX

Before configuring PATROL KM for UNIX, verify that the following software requirements are met:
s
The PATROL console version 3.5.x or later and PATROL KM for UNIX 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 are installed on the computer that you want to monitor and manage. PATROL KM for UNIX 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 is installed on the PATROL Console Server. If you are using PATROL Central Operator Web Edition, PATROL KM for UNIX 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.
72
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.
Chapter 3
73
Manually Starting the PATROL Agent
Manually Starting the PATROL Agent

Use 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 KMs

When 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, its KM files must be loaded into the PATROL console so that the products applications, commands, and parameters appear in the PATROL console. Table 9 on page 75 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 75.
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 KMs data collection history, you will not see any gaps that would otherwise occur (because of the consoles absence).
74
You can find the steps for loading and preloading KMs in the following sections:
s s
Loading KMs. Preloading KMs on the PATROL Agent on page 80
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 80. Table 9
.kml Files UNIX3.kml LOG.kml EVENT_MANAGEMENT.kml
PATROL for UNIX and Linux.kml Files

Description PATROL KM for UNIX: loads application classes to monitor UNIX and Linux operating systems. PATROL KM for Log Management: loads application classes to monitor log files. 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. PATROL History Loader Knowledge Module: 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 History Loader Knowledge Module User Guide for more information.
HISTORY.kml
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.
Chapter 3
75
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 75.
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 75 for a list of the KMs that are available in this product.
4 Click Finish.
PATROL loads the selected KMs on the selected computers.
76
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. See Table 9 on page 75 for a list of the KMs that are available in this product.
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. See Table 9 on page 75 for a list of the KMs that are available in this product.
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 78 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 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.
Chapter 3
77
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 icons 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
NOTE
The VIRTUALIZATION application class is displayed on an AIX 5.3 micropartitioned system as an AIX_VIRTUALIZATION instance, and the POOL and ZONE application classes are displayed on a Solaris 10 system in the SOLARIS_VIRTUALIZATION instance.
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 79 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.
78 PATROL Getting Started for UNIX and Linux
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 79, view the System Output Window from the agent computer icons 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 icons 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
Chapter 3
79
Verifying that the PATROL History Loader Knowledge Module Is Loaded

If you loaded the HISTORY.kml file for the PATROL History Loader Knowledge Module, 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.
NOTE
When you load the PATROL History Loader Knowledge Module 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.
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 icons 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 the KMs to continue collecting data even when no console is running, preload the 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 agents preload list by using the PATROL Configuration Manager rule, as described in this task. For information about how to create, edit, and manage rules, RuleSets, and configurations with the PATROL Configuration Manager, see the PATROL Configuration Manager User Guide.
80
Based on the application name, the /AgentSetup/preloadedKMs configuration variable specifies which KMs the PATROL Agent automatically loads for all operating systems and machine types when the agent starts up.
EXAMPLE
"/AgentSetup/preloadedKMs" = {REPLACE="HISTORY.kml, EVENT_MANAGEMENT.kml, LOG.kml"}
Format and Type of Data Default Value
item_1,item_2,item_n (does not support wildcards), Knowledge Modules none By default, the PATROL Agent does not load any of the application KMs; however, the ALL_COMPUTERS.km and the KM for the current machine type are always preloaded and always static.
Minimum and Maximum Dependencies Recommendation
not applicable none The file names must be on the same line.
Before you begin

s
The PATROL Agent and PATROL Configuration Manager 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 Create a Rule for Preloading KMs 1 In the RuleSets tree view of PATROL Configuration Manager, right-click on a
RuleSet and choose New Rule.
2 Enter the rule properties by typing or selecting a value.

The rule properties are described in Table 10 on page 82.
Chapter 3
81
Table 10
Property Variable
Rule Properties
Description the PATROL Agent configuration variable name: /AgentSetup/preloadedKMs Variable names are case sensitive, must start with a forward slash (/), and cannot contain quotation marks (). If you want to use a Rule Alias, the alias name must be enclosed in percent signs (%), such as %alias_name%. The PATROL KM for Event Management stores Event Management Rules as PATROL Agent configuration variables.
Operation
the action that the rule performs on the variable using the specified value The following operations are available:
s
DELETEdeletes the value of the variable and leaves it blank on the agent (The value is deleted only if it exists and is not null.) REPLACEreplaces the current value of the variable on the agent with the specified value MERGEmerges the specified value with the existing value of the variable on the agent APPENDadds the specified value to the existing value of the variable on the agent DELVARdeletes the variable from the PATROL Agent configuration database (This operation is a shortcut for DELETE and REPLACE with a null value.)
Value
the value that is used with the operation If you want to use a Rule Alias, the alias name must be enclosed in percent signs (%), such as %alias_name%.
NOTE
DELETE, MERGE, and APPEND operations work with lists of values only when the list is comma separated. These operations do not work when the list items are separated by new lines.
3 Click OK to save the new rule.
82
To Apply a RuleSet to an Agent for Preloading KMs 1 In the PATROL Configuration Manager toolbar, click Apply Configuration
from the menu bar choose Queue => Apply. or
2 Use the Apply RuleSet dialog box to specify how rules are applied. The properties
are described in Table 11. Table 11
Option Agents Selected
Apply RuleSet Properties (Part 1 of 2)

Description allows you to review which agents the rules are scheduled to be applied to and remove agents; to view the list of agents you must click Show. On the Apply RuleSets: Agent Lists dialog box, you can remove agents from the list by selecting the agent and clicking Remove Agent. When an agent is removed from the list, the rules that are waiting to be applied are also cleared for the agent.
Apply All ApplyOnApply Items In Current Group Parent Tree Group applies the ApplyOnApply RuleSets that are activated for the group in which the agent resides applies the ApplyOnApply RuleSets that are activated for the immediately preceding group (or the top group, the Agents group)
Apply Options Overwrite Localized Settings If an agent that you are applying RuleSets to has a localized rule that is the same as one of the rules you are applying, you can select this option to overwrite the localized rule with the applied rule. This option is inactive if the agent or agents do not possess any localized rules. Report Localized Rules Before Apply If the agent that you are applying RuleSets to has localized rules, the configuration manager creates a report that list the localized rules. These localized rules will take precedence over the global rules that you are about to apply unless you select the Overwrite Localized Settings check box. This option is inactive if the agent or agents do not possess any localized rules.
Chapter 3
83
Table 11
Option
Apply RuleSet Properties (Part 2 of 2)

Description remove all previous configuration changes before applying the RuleSets Purging agents before applying RuleSets is useful when you are resetting an agent configuration to a previous version. If the purge option is not selected, the applied rules are combined with the agents current rules. Purging an agents configuration reverts the agent back to its default configuration, deleting any changes that have been previously applied. If both options are selected, the backup occurs before the purge.
Purge Agents Before Apply
Backup Agents Before Apply retrieve agent configurations and save them to the PATROL Configuration Manager backup folder prior to the application of new rules If you make an error applying RuleSets, you can use backups to restore an agent to a previous configuration.
3 Click OK.
PATROL Configuration Manager places the rules in the job queue and displays the Job Status Information dialog box. You can identify the job by the time-date stamp, the agent against which the action will be performed, and the action (in this case, APPLY). If you have requested that a backup or purge be performed before rules are applied, jobs with those statuses (GET and PURGE) will appear prior to the APPLY job. If you want to be notified of the outcome (success or failure) of the APPLY jobs, select the Redisplay When Updated check box.
4 Click OK.
PATROL Configuration Manager closes the Job Status Information dialog box.
84
Removing KMs from the Console and Agent

If you want to remove a KM from being displayed in the 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 88. 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.
Chapter 3
85
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 9 on page 75 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 consoles memory rather than deleted from your hard drive.
86
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 consoles 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.
Chapter 3
87
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. Based on the application name, the /AgentSetup/disabledKMs configuration variable prevents KMs from being loaded by the agent regardless of whether a console is a developer console, and the /AgentSetup/loadOnlyPreloadedKMs configuration variable specifies that only KMs designated as preloaded are loaded. All others are prevented from being loaded.
EXAMPLE
If you want to disable everything that begins with NT and VMS, use NT.* and VMS.*, not NT*. and VMS*. "/AgentSetup/disabledKMs" ={REPLACE="NT.*,VMS.*,bad_APPL"}
Format and Type of Data Default Value Minimum \ Maximum Dependencies Recommendation
item_1,item_2,item_n, Knowledge Modules none not applicable none The ALL_COMPUTERS.km and the KM for the current machine type cannot be disabled. The file names must be on the same line.
Before you begin

s
The PATROL Agent and PATROL Configuration Manager 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). You must have RuleSets to delete.
To Remove a KM from the Agent Preload list by Removing the RuleSet 1 In the RuleSets tree view of PATROL Configuration Manager, select the RuleSets
that you want to delete. To select multiple RuleSets, press and hold Ctrl while you click the RuleSets you want to delete.
2 Continue to hold Ctrl and right-click on one of the selected RuleSets.

88 PATROL Getting Started for UNIX and Linux
Configuring PATROL KM for UNIX
3 In the RuleSet menu, choose Delete. 4 In the Confirm Delete Items dialog box, click Yes.
PATROL Configuration Manager closes the dialog box and removes the selected object (RuleSet or folder) and any other subordinate objects such as folders, RuleSets, and rules.

This 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 99.
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.
Chapter 3
89
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.
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:
s s
BEST1_HOMEan environment variable /UNIX_OS/PERFORM_HOMEa PATROL Configuration Database variable
(pconfig)
90
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 99.
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 DcmCol.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.
Chapter 3
91
Configuring the PATROL KM for Log Management
5. PATROL checks for the BEST1 directory under the current directory and its subdirectories. 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.
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.
For details about using the PARTOL KM for Log Management, see the PATROL for Log Management User Guide.
92
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:
s
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.
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.
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

s
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
Chapter 3
93
Configuring Recovery Actions
NothingPATROL continues monitoring the log file but does not attempt to
reduce its size.

s
DeletePATROL reduces the log file to 0 MB by deleting all the messages in the
log file when the file reaches the size limit.

s
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).

This 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.
94
If you dont 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. Table 12 PATROL for UNIX and Linux Recovery Actions
Parameter FILESYSTEM\FSCapacity Auto Run? Requires Configuration You must reboot to run this command.
Recovery Action & Description 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.
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.
Chapter 3
95
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 13. Table 13
Purpose
Selecting a Recovery Action Instance

Recovery Action to Select
FilesystemCleanup 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.
4 From the Edit Recovery Action dialog box, choose from the settings described in
Table 14. Table 14
Setting 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. Run Attended
Recovery Action Configuration Options

Description PATROL runs the recovery action automatically, without prompting you. Configuration Result This recovery action applies to all FILESYSTEM instances.
PATROL prompts you before running the recovery action.
This recovery action applies to all FILESYSTEM instances. This mode is the default setting.
Do Not Execute
PATROL does not perform the recovery action.
96
NOTE
For more information about the recovery action and its configuration options, click the Help button.
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..
Chapter 3
97
98
Appendix

A
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Accessing KM Commands and InfoBoxes

Table 15 provides information about how to access KM commands and InfoBoxes from the various PATROL consoles. Table 15
Console PATROL Console for Microsoft Windows Servers
Accessing KM Commands and InfoBoxes (Part 1 of 2)

To access menu commands 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 the work area, right-click a computer or application icon to display a pop-up menu that contains KM-specific commands. To access InfoBoxes In either the Desktop tree tab or the work area, right-click an application class or parameter icon and choose InfoBox from the popup menu. With the middle mouse button, click an application class or parameter icon.
PATROL Console for UNIX
Appendix A
99
Accessing Online Help
Table 15
Console
Accessing KM Commands and InfoBoxes (Part 2 of 2)

To access menu commands To access InfoBoxes
PATROL Central Operator Windows Edition
In the navigation pane, right-click a In the navigation pane, right-click a PATROL object and choose managed system or application InfoBox from the pop-up menu. icon and choose Knowledge Module Commands from the popup menu. In the tree view area, right-click an In the tree view area, right-click a PATROL object and choose application icon and choose Infobox from the pop-up menu. Knowledge Module Commands from the pop-up menu.
PATROL Central Operator - Web Edition

This section provides instructions about accessing online Help from your PATROL console. Table 16 on page 101 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.
100
Table 16
Console

To access product help
s
To access application class help 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.
To access parameter help

s
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.
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.
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 In the tree view, right-click In the tree view, right-click an application class and a parameter and choose PATROL Central, click Help. Help and choose PATROL choose Help. KM Help.
Appendix A
101
102
Appendix
Troubleshooting PATROL for UNIX and Linux Problems

B
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 . . . . . . . . . . . . . . . . . . . . . . 103 Error Messages in the $BEST1_HOME/bgs/monitor/log/bgscollect_portnumber.log . . . . . . . . . . 105
Troubleshooting PATROL KM for UNIX Problems

The following sections describe some common problems you may encounter while running PATROL KM 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.
NOTE
The installation program prompts you for the root password, regardless of the target platform.
On HP-UX, you will not lose process data unless DCM/bgscollect is disabled.
Appendix B Troubleshooting PATROL for UNIX and Linux Problems 103
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 ./agent_configure.sh. (see Table 17 for possible parameters) 3 Type ./b1config7140.sh.
Table 17
-d -a -s
Parameters for ./agent_configure.sh

sets the ownership and permission of files in the installation to setuid root, and configures the policy files in the /etc/patrol.d sets the ownership and permission of files in the installation to setuid root configures the policy files in the /etc/patrol.d
Parameter Description
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.40.
104
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:
s s s
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.
Appendix B
Troubleshooting PATROL for UNIX and Linux Problems
105
106
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 52 %PATROL_CACHE% 52 migrating 54 migrating manually 58 customized PSL migrating 59
A
accounts local partition requirements 25 permissions needed for PATROL 25 requirements, customizations 25 root access requirements 25 umask settings 25 agent installing a KM to 36 AIX operating system 38, 39 shared memory and semaphores 32 Apply RuleSets 83
D
data collection specifying method 89 troubleshooting 103 DCM collection method 89 deleting old version 56 Digital UNIX 38, 39 directory PATROL installation default 42 documentation library 20 documentation, related 19
B
backing up current installation before migrating 55 BMC Software, contacting 2 Bourne shell 63 browsers installing PATROL without one 42, 45 uninstalling without one 66
E
environment variables LANG 63 PATH 63 PATROL_BROWSER 64 PATROL_HOME 52 setting for Help browser 63 setting for the browser 63 eXceed 63 exportfs command 38
C
C shell 63 collection method changing 89 determining type used 90 specifying 89 colormap option 63 console installing a KM to 35 console systems overview 35, 36 Create Rule 81 custom installation option 41 custom processes, migrating 7273 customer support 3 customizations
F
features, product 14 first-time installation 41 typical installation option 40 format variable name 82
H
HP Tru64 (Compaq Tru64 UNIX) systems shared memory and semaphores 32
Index
107
HPUX 38, 39 shared memory and semaphores 32
N
naming conventions pconfig variable 82 Netscape Navigator 62 new PATROL user easy install option 40 installing for the first time 41 NFS Mount a CD-ROM 38, 39
I
installable images creating for each platform 34 installation backing up before migrating 55 choosing a target machine 35 clearing cache 56 creating vendor-specific installation images 34 custom option 41 default PATROL directory 42 for the first time 41 password troubleshooting 103 preparing for 33 -serveronly option 42, 45 system requirements 22, 23 typical option 40 upgrading from an earlier version 50 verifying requirements 22 without a browser 42, 45
O
online Help installing 36 operations 82
P
password supplying for installation 103 troubleshooting 103 PATH environment variable 63 PATROL default installation directory 42 PATROL account requirements customizations 25 PATROL accounts local partition requirements 25 permissions needed 25 root access requirements 25 umask settings 25 PATROL Agent installing a KM to 36 port number default 41 starting manually 74 PATROL Agent for Unix 15 PATROL Central Operator - Web Edition installing 36 PATROL Configuration Manager migrating customized processes 73 rules 80 RuleSets 80 PATROL Console and Netscape Navigator 62 installing a KM to 35 PATROL KM for Event Management 17 PATROL KM for History Loader 18 PATROL KM for Log Management 1617 PATROL KM for UNIX 16 PATROL Perform Data Collector 18 PATROL Security 18 PATROL security overview of levels 39 PATROL_BROWSER environment variable 64
K
KM customizations migrating manually 58 KMs determining if migratable 51 installing individual 41 upgrading from an earlier version 50 Korn shell 63
L
LANG environment variable 63
M
managed systems overview 36 managing rules 80 manual migration of KM customizations 58 manually starting a PATROL Agent 74 migrating backing up current installation before 55 customizations 54 customized PSL 59 determining if KM is migratable 51 from an earlier version of the KM 50 KM customizations manually 58 mounting the CD-ROM 39
108
PATROL_CACHE 52, 56 PATROL_HOME 52 PCM migrating customized processes 73 rules 80 RuleSets 80 pconfig utility migrating customized processes 73 Perform collector, existing 90 planning for installation 33 platforms creating vendor-specific installable images 34 pop-up blocking software 33 port number default for PATROL Agent 41 preparing for installation 33 product components PATROL Agent for Unix 15 PATROL KM for UNIX 16 product features 14 product support 3 products uninstalling in Unix environments 65 PSL collection method 89 migrating 59 AIX operating system 32 Digital UNIX (HP Tru64) systems 32 HP Tru64 systems 32 HPUX 32 Solaris systems 28 shells Bourne 63 C 63 Korn 63 Solaris 38, 39 shared memory and semaphores 28 starting PATROL Agent, manually 74 support, customer 3 system requirements 22, 23 system roles console systems 35, 36 managed systems 36 overview of target machines 35
T
target machines overview 35 technical support 3 troubleshooting data collection failures 103 passwords for installation 103 typical installation option 40
R
recovery actions built-in 15 file system clean-up 15 remote installation creating vendor-specific images 34 Remove RuleSets 88 requirements overview 22 privileges 38, 39 system 22, 23 RuleSets 81
U
umask setting, PATROL account 25 uninstalling products in Unix environments 65 without a browser 66 upgrading 50 backing up current installation before 55 choosing a procedure 52 from an earlier version of the KM 50 user account 63
S
security overview of levels 39 selecting a collection method 89 semaphores and shared memory segments 28 -serveronly command uninstalling 66 -serveronly option for installation 42, 45 setting environment variables for Help browser 63 share command 38 shared memory and semaphores
V
values 82 variable name format 82
Index
109
110
Notes
*70819* *70819* *70819* *70819*

*70819*

PATROL Getting Started

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PATROL Getting Started

Uploaded by

Copyright:

Available Formats

PATROL Getting Started

for UNIX and Linux

Contacting BMC Software

United States and Canada

Outside United States and Canada

Restricted rights legend

Support by telephone or e-mail

Before contacting BMC

PATROL Getting Started for UNIX and Linux

PATROL Getting Started for UNIX and Linux

Accessing Menu Commands, InfoBoxes, and Online Help

PATROL Getting Started for UNIX and Linux

PATROL Getting Started for UNIX and Linux

PATROL Getting Started for UNIX and Linux

PATROL for UNIX and Linux Components and Capabilities

PATROL for UNIX and Linux Features

PATROL for UNIX and Linux Components and Capabilities

PATROL for UNIX and Linux Features

Product features include:

PATROL Getting Started for UNIX and Linux

PATROL for UNIX and Linux Components

Built-in Recovery Actions

PATROL for UNIX and Linux Components

PATROL for UNIX and Linux Components and Capabilities

PATROL for UNIX and Linux Components

PATROL KM for UNIX

PATROL KM for Log Management

PATROL Getting Started for UNIX and Linux

PATROL for UNIX and Linux Components

PATROL KM for Event Management

PATROL for UNIX and Linux Components and Capabilities

PATROL for UNIX and Linux Components

PATROL KM for History Loader

PATROL Perform Data Collector for UNIX

PATROL Getting Started for UNIX and Linux

PATROL for UNIX and Linux Components and Capabilities

For additional information about PATROL, see the following documentation:

PATROL Getting Started for UNIX and Linux

Installing and Migrating PATROL for UNIX and Linux

Verifying Installation Requirements

Verifying Installation Requirements

PATROL Getting Started for UNIX and Linux

Verifying Installation Requirements

System Requirements for PATROL KM for UNIX

System Requirements for PATROL KM for UNIX (Part 1 of 2)

without components and KMs without components and KMs NA

less than 2-MB for PATROL KM for UNIX NA

screen resolution should be set to at least 600 x 800 pixels NA

Installing and Migrating PATROL for UNIX and Linux

Verifying Installation Requirements

System Requirements for PATROL KM for UNIX (Part 2 of 2)

random access memory (RAM) PATROL Perform Collector security levels

PATROL Security Levels on page 39

dedicated PATROL account

See Accounts on page 24 for information about user account requirements.

PATROL Getting Started for UNIX and Linux

Verifying Installation Requirements

PATROL KM for UNIX User Account Requirements

account file customizations

IBM AIX computers root account

setuid root permissions

Components that Require setuid Permissions

PATROL Foundation Components PATROL Console PATROL Agent

Installing and Migrating PATROL for UNIX and Linux