BMC Base de Conocimiento Linux

PATROL®Knowledge Module® for Unix

User Guide

Supporting

PATROL for Unix and Linux 9.2

March 2005

Contacting BMC Software

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

United States and Canada

Address BMC SOFTWARE INC2101 CITYWEST BLVDHOUSTON TX 77042-2827 USA

Telephone 713 918 8800 or800 841 2031

Fax 713 918 8000

Outside United States and Canada

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

Copyright 2005 BMC Software, Inc., as an unpublished work. All rights reserved.

BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered trademarks or trademarks of BMC Software, Inc.

IBM is a registered trademark of International Business Machines Corporation.

DB2 is a registered trademark of International Business Machines Corporation.

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

All other trademarks belong to their respective companies.

Product Name technology holds U.S. Patent Number number.

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

Restricted rights legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC SOFTWARE INC, 2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA. Any contract notices should be sent to this address.

http://www.bmc.com

3

Customer support

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

Support website

You can obtain technical support from BMC Software 24 hours a day, 7 days a week at http://www.bmc.com/support_home. From this website, you can

■ read overviews about support services and programs that BMC Software offers■ find the most current information about BMC Software products■ search a database for problems similar to yours and possible solutions■ order or download product documentation■ report a problem or ask a question■ subscribe to receive e-mail notices when new product versions are released■ find worldwide BMC Software support center locations and contact information, including e-mail addresses, fax

numbers, and telephone numbers

Support by telephone or e-mail

In the United States and Canada, if you need technical support and do not have access to the web, call 800 537 1813 or send an e-mail message to [email protected]. Outside the United States and Canada, contact your local support center for assistance.

Before contacting BMC Software

Before you contact BMC Software, have the following information available so that Customer Support can begin working on your problem immediately:

■ product information

— product name— product version (release number)— license number and password (trial or permanent)

■ operating system and environment information

— machine type— operating system type, version, and service pack or other maintenance level such as PUT or PTF— system hardware configuration— serial numbers— related software (database, application, and communication) including type, version, and service pack or

maintenance level

■ sequence of events leading to the problem

■ commands and options that you used

■ messages received (and the time and date that you received them)

— product error messages— messages from the operating system, such as file system full— messages from related software

http://www.bmc.com/support_home

mailto:[email protected]

4 PATROL for Unix User Guide

ContentsChapter 1 Introduction 19

PATROL KM for Unix and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Applications and Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 2 Menu Summary 27

Location of KM Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29PATROL Console for Unix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29PATROL Console for Microsoft Windows Servers . . . . . . . . . . . . . . . . . . . . . . . . . 29

Menu Summary Table Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Computer Instance Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30UNIX OS Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31COLLECTORS Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33COMPOSITES Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33COMPOSITES_COLLECTOR Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33CPU Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34DCM Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34DISK Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34FILESYSTEM Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35HEALTH AT A GLANCE Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36KERNEL Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36MEMORY Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36NETWORK Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37NFS Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38PATROL Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38PATROLAGENT Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39PRINTER Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41PROCESS Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42PROCESS_PRESENCE (PROCCONT) Application Menu . . . . . . . . . . . . . . . . . . . . . . 42PROCPRES Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43SCHEDULER Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44SECURITY Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44SMP Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44SNMPHealth Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45SWAP Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46USERS Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Contents 5

Chapter 3 Parameter Summary 49

Parameter Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Parameter Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Chapter 4 Managing Data Collection 87

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Object Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

COLLECTORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88DCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

DCM Collection Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Data Collection Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Collector Parameters for DCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91-Ctrl and -Coll Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92DCM Collection Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

PSL Collection Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Collector Parameters for COLLECTORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95-Coll Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96PSL Collection Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Managing Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Changing Data Collection Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Activating an Inactive Application Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Activating an Inactive Collector Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Significant Events Related to Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Chapter 5 Monitoring CPU and Kernel 105

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Object Hierarchy for CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106CPU and Multiple CPUs (SMP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Viewing CPU Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Viewing CPU Statistics on Interrupts, Switches, and Waits . . . . . . . . . . . . . . . . . 109Viewing Statistics on CPU Run Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Viewing Statistics on Multiple CPUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Object Hierarchy for KERNEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111KERNEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Viewing the Kernel Build Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Viewing Kernel Memory Allocation Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Viewing Kernel I-node Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Viewing Kernel System Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Chapter 6 Using Composite Parameters 117

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Object Hierarchy for COMPOSITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Working with Composite Parameter Expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Examples of Composite Parameter Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Syntax Rules for Composite Parameter Expressions . . . . . . . . . . . . . . . . . . . . . . . 120Setting the Status of a Composite Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Creating Composite Parameter Expressions Using the Wizard . . . . . . . . . . . . . . 121

6 PATROL Knowledge Module for Unix User Guide

Creating Composite Parameter Expressions Manually . . . . . . . . . . . . . . . . . . . . . 124Editing Composite Parameter Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Deleting Composite Parameter Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Chapter 7 Monitoring Disks 127

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Disks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Excluding a Single Disk from Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Selecting Disks to Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Resuming Monitoring Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Chapter 8 Monitoring and Managing File Systems 135

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Monitoring File Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Excluding a Single File System from Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . 138Selecting File Systems to Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Automating File System Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Running Recovery Actions Only with Operator Confirmation . . . . . . . . . . . . . . 143Preventing File Systems from Being Monitored . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Working with File System Types and File System Classes . . . . . . . . . . . . . . . . . . 145

Managing File Systems Using PATROL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Mounting a File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Unmounting a File System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Synchronizing File System Cache and Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Searching for Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Removing Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Chapter 9 Monitoring Overall System Health 157

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158HEALTH AT A GLANCE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Viewing the Overall CPU, File System, and Swap Usage . . . . . . . . . . . . . . . . . . . 159Viewing the Overall Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Chapter 10 Monitoring and Managing Memory 161

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Object Hierarchy for MEMORY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Shared Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Viewing Shared-Memory Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Deleting a Shared-Memory Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Semaphores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Viewing Semaphore Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Deleting a Semaphore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Object Hierarchy for SWAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Contents 7

Virtual Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Viewing the Amount of Swap Space. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Viewing the Swap Partition Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Viewing the Percentage of Used Swap Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Chapter 11 Monitoring and Managing Networks 173

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Network Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Activating the NETWORK Application Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Deactivating the NETWORK Application Class . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Network Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Viewing a Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178Discovering the Name of the Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 179Establishing Behavior When Unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Viewing Memory Buffer Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Network Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Viewing Network Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Listing Host and IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Network Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Listing Protocols Running on the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Viewing Protocol Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Determining the Network Internet Protocol Address . . . . . . . . . . . . . . . . . . . . . . 191

Network Traffic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Viewing the Routing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Determining the Number of Packets Entering and Exiting the Network . . . . . . 194Determining the Number of Packet Errors Entering and Exiting the Network . 194

Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Listing TCP/IP Services Running on the Network. . . . . . . . . . . . . . . . . . . . . . . . . 196Listing Trusted Hosts on the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Copying or Transferring Files by Using FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Checking for a Network Resource by Using ping. . . . . . . . . . . . . . . . . . . . . . . . . . 199Logging In Remotely by Using rlogin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Querying the Name Server for the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Address Resolution Protocol (ARP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Viewing the Address Resolution Protocol (ARP) Cache . . . . . . . . . . . . . . . . . . . . 202Deleting a Host from the ARP Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203Adding a Host to the ARP Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Unix to Unix Communication Protocol (UUCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206Checking for UUCP Support Files and Directories. . . . . . . . . . . . . . . . . . . . . . . . . 206Cleaning Up UUCP Files in the Spool Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . 207Copying Files Using UUCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Listing All UUCP Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Viewing the UUCP Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Viewing UUCP Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Chapter 12 Monitoring Network File Systems 213

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214


Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Network File System (NFS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Viewing Network File System (NFS) Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Resetting Network File System Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Network Information System (NIS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Viewing Network Information System Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . 218Viewing Network Information System Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Viewing Network Information System Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Chapter 13 Monitoring and Managing Printers 223

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224Printer Activation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Activating the PRINTER Application Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225Deactivating the PRINTER Application Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Printers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226Excluding a Printer from Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227Selecting Printers to Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227Viewing the Number of Print Jobs in a Printer’s Queue . . . . . . . . . . . . . . . . . . . . 228Stopping a Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228Starting a Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Print Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231Viewing All Print Jobs Assigned to a Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231Viewing All Print Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232Deleting a Print Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233Deleting All Print Jobs from a Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234Moving a Print Job to Another Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235Moving All Print Jobs to Another Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Print Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237Stopping a Print Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Starting a Print Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Chapter 14 Monitoring Processes 241

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Configuring Multiple Instances of a Process for Monitoring . . . . . . . . . . . . . . . . 247Configuring a Process to Alarm When the Number of Running Instances Exceeds

a Set Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250Configuring a Process to Alarm When the Number of Running Instances Falls

Below a Set Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253Configuring a Process to Restart When PATROL Detects It Has Stopped. . . . . 256Configuring a Process to Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259Configuring a Process to Alarm When Its Parent Process ID (PPID) is Not 1 . . 262Configuring a Process to Alarm When It is Owned by an Unauthorized User . 265Configuring a Process to Suspend Its Alert for N Cycles if Patrol Detects It is

Not Running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268Modifying the Configuration of a Monitored Process . . . . . . . . . . . . . . . . . . . . . . 270

Contents 9

Monitoring Process Presence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274Deleting a Monitored Process from the Monitoring Queue . . . . . . . . . . . . . . . . . 278Specifying a Flag File Directory for Process Presence Blackout Periods . . . . . . . 278Suspending Process Monitoring for a Process Instance . . . . . . . . . . . . . . . . . . . . . 280Resuming Process Monitoring for a Process Instance . . . . . . . . . . . . . . . . . . . . . . 280Reporting on a Selected Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Process Host Groups in a Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282Rules for Creating Process Host Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282Creating a Host Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283Configuring Communication Attributes for a Process Host Group. . . . . . . . . . . 284Modifying Host Attributes within a Process Group. . . . . . . . . . . . . . . . . . . . . . . . 285Removing a Host from a Host Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286Querying a Selected Host within a Process Host Group . . . . . . . . . . . . . . . . . . . . 286Synchronizing the Local Host’s List to a Selected Host’s List for a Process

Host Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288Synchronizing a Selected Host’s List to the Local Host List for a Process

Host Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288Viewing the Process List for a Selected Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289Synchronizing the Local Process’s List with a Selected Process's List . . . . . . . . . 289Synchronizing a Selected Process's List with the Local Process's List . . . . . . . . . 290Viewing the Process Presence List for a Selected Process . . . . . . . . . . . . . . . . . . . 291

Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292Viewing the Number of Zombie Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292Viewing Zombie Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293Viewing the Total Number of Processes Running . . . . . . . . . . . . . . . . . . . . . . . . . 295Viewing Processes that Use Excessive CPU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295Viewing the Number of Processes Waiting on Resources . . . . . . . . . . . . . . . . . . . 298Viewing the Total Number of User Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298Viewing the Average Number of User Processes . . . . . . . . . . . . . . . . . . . . . . . . . . 299

Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299Reprioritizing a Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300Reprioritizing All Processes in a Process Group . . . . . . . . . . . . . . . . . . . . . . . . . . . 301Reprioritizing All Processes Owned by a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

Using the PATROL Configuration Manager to Configure the PATROL KM for Unix and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304Plug-in Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304Configuring the Process KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307

Chapter 15 Scheduling Tasks 311

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Scheduling a Task for Execution via the Operating System Command Line Processor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Scheduling a Task for Execution Using a PATROL Command Processor . . . . . 315Scheduling a PSL Task for Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318Modifying an Existing Scheduled Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321Removing a Scheduled Task from the Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321Collecting Debug Data for the Scheduler Application . . . . . . . . . . . . . . . . . . . . . . 322


Blackouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326Specifying a Default Directory for Blackout Scripts. . . . . . . . . . . . . . . . . . . . . . . . 326Creating a Monitoring Blackout Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327Viewing Information about a Blackout Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330Modifying an Existing Blackout Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331Deleting a Blackout Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334Scheduling a Blackout Script for Execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335Canceling a Scheduled Blackout Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

Chapter 16 Reviewing Security 339

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341

Viewing Files with SUID or SGID Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . 341Viewing Files with Global Write Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

User Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345Viewing Users that Failed to Execute su/msu Commands . . . . . . . . . . . . . . . . . 345Viewing Users without Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346Viewing Users with Multiple Sessions Running . . . . . . . . . . . . . . . . . . . . . . . . . . 348

Chapter 17 Monitoring the Health of SNMP 351

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352PATROL SNMP System Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353Role of Each Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

SNMP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354Changing SNMP Query Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355Listing Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356Viewing PATROL SNMP MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

Status of SNMP Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360Starting the SNMP Master Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361Starting the SNMP Subagent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362Stopping the SNMP Subagent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

Tests SNMP Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364Testing the SNMP Master Agent’s Ability to Receive Traps . . . . . . . . . . . . . . . . 364Generating Manual SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365Querying the PATROL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366Querying the SNMP PATROL platform.km . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367Determining if Any SNMP Managers are Listening . . . . . . . . . . . . . . . . . . . . . . . 369Testing PATROL Event Manager’s Automated SNMP Traps . . . . . . . . . . . . . . . 370

Chapter 18 Monitoring Users 373

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375

Viewing Print Jobs that Belong to a User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375

Contents 11

Viewing Processes that Belong to a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376Viewing the Amount of Disk Space Consumed by a User . . . . . . . . . . . . . . . . . . 377

Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378Viewing the Number of Users on the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379Viewing the Number of Sessions Running on the System . . . . . . . . . . . . . . . . . . 380

Appendix A Debugging and Running Diagnostics 381

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382Unix Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382

Capturing DUMP Information for Selected Components . . . . . . . . . . . . . . . . . . . 383Viewing Installation Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385Capturing Log File Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386

Collector Debug Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388Debugging FILESYSTEM Data Collection (DFColl) . . . . . . . . . . . . . . . . . . . . . . . . 388Debugging NETWORK Data Collection (NETColl) . . . . . . . . . . . . . . . . . . . . . . . . 389Debugging NFS Data Collection (NFSColl) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390Debugging PRINTER Data Collection (PRINTERColl) . . . . . . . . . . . . . . . . . . . . . 391Debugging PROCESS Data Collection (PSColl) . . . . . . . . . . . . . . . . . . . . . . . . . . . 392Debugging USER and PROCESS Data Collection (USRPROCColl). . . . . . . . . . . 392Debugging CPU, MEMORY, and KERNAL Data Collection (VMColl) . . . . . . . 393Debugging DCM Data Collection (DCMColl) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394

Application Discovery Debug Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395Debugging DISK Discovery Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396Debugging FILESYSTEM Discovery Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396Debugging NETWORK Discovery Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397Debugging PRINTER Discovery Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398Debugging SMP Discovery Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398Debugging SWAP Discovery Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

Application Class Debug Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400Debugging the SCHEDULER Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400

Appendix B Loading, Unloading, and Navigating KMs in the PATROL Consoles 401

Accessing KM Commands and InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402Accessing Online Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402Using the Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404

Using the Mouse to Perform Tasks in PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . 405

Appendix C Regular Expressions 407

Components that Use Regular Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410Conventions for Using Regular Expressions with PATROL Objects . . . . . . . . . . . . . 411

Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

Appendix D Inclusion and Exclusion Lists 413

Using Exclusion and Inclusion Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414


Methods for Creating Exclusion and Inclusion Lists . . . . . . . . . . . . . . . . . . . . . . . 414Storage Location of Exclusion and Inclusion Lists . . . . . . . . . . . . . . . . . . . . . . . . . 415

Benefits and Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415Benefits of Creating Exclusion Lists Using Menu Commands . . . . . . . . . . . . . . . 415Inclusion List Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416

Index 417

Contents 13

FiguresPATROL KM for Unix Application Class Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . 21COLLECTORS Application Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88DCM Application Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Data Collection Architecture Using PATROL Perform Collector . . . . . . . . . . . . . . . . 91PSL Collection Confirmation Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99CPU Application Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107KERNEL Application Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111KERNEL InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112COMPOSITE Application Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119COMPOSITES_COLLECTOR Application Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119COMPOSITES Parameters Container Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120DISK Application Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129DISK Exclusion List Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131FILESYSTEM Application Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137FILESYSTEM Exclusion List Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Edit Recovery Action Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Run Recovery Action Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Automatic Mount Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Manual Mount Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Automatic Unmount Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Manual Unmount Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Find Files Like Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Remove Files Like Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154HEALTH AT A GLANCE Application Object Hierarchy . . . . . . . . . . . . . . . . . . . . . 158MEMORY Application Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Remove Shared Memory Segment Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Remove Shared Memory Segment Confirmation Dialog Box . . . . . . . . . . . . . . . . . . 166Remove Semaphores Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Remove Semaphores Confirmation Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169SWAP Application Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170NETWORK Application Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175NETWORK InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Ping Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Rlogin Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Delete Host from Cache Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Delete Host From Cache Confirmation Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Add Host To Cache Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205UUCP Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208NFS Application Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215NFS User Name Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Figures 15

PRINTERS Application Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224Delete Print Job Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233Delete All Jobs Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234Move Job to Another Printer Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235Move Jobs To Another Printer Confirmation Dialog Box . . . . . . . . . . . . . . . . . . . . . . 236Move All Jobs to Another Printer Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236Move Jobs To Another Printer Confirmation Dialog Box . . . . . . . . . . . . . . . . . . . . . . 237PROCESS Application Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245PROCESS InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293CPU Hogs Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296Renice Process Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300Renice Process Confirmation Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301SCHEDULER Application Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312SECURITY Application Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340SECURITY User Name and Password Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341Find SUID/SGID Files Like Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342SNMPHealth Application Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352PATROL SNMP System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353Change SNMP Query Port Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355Walk PATROL SNMP MIB Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358SNMP Query PATROL Master Agent Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367SNMP Query PATROL Platform.km Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368State Change Messages Based on Automated Traps . . . . . . . . . . . . . . . . . . . . . . . . . . 371USERS Application Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374List Print Jobs Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375USERS InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379Select Categories of Diagnostics Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383%DUMP Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384Select Log Files to Collect Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387Mouse Button Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404


TablesPATROL KM for Unix and Linux Applications, Icons, and Descriptions . . . . . . . . . 22Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Menu Summary Table Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Computer Instance Menu Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30UNIX_OS Application Menu Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31COLLECTORS Application Menu Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Composites Application Menu Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34DCM Application Menu Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34DISK Application Menu Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34FILESYSTEM Application Menu Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35MEMORY Application Menu Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36NETWORK Application Menu Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37NFS Application Menu Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38PATROL Application Menu Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38PATROLAGENT Application Menu Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39PRINTER Application Menu Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41PROCESS Application Menu Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42PROCESS_PRESENCE Application Menu Summary . . . . . . . . . . . . . . . . . . . . . . . . . . 42PROCPRES Application Menu Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43SCHEDULER Application Menu Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44SECURITY Application Menu Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44SNMPHealth Application Menu Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45USERS Application Menu Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47PATROL KM for Unix and Linux Parameter Summary . . . . . . . . . . . . . . . . . . . . . . . . 50PATROL KM for Unix and Linux Parameter Defaults . . . . . . . . . . . . . . . . . . . . . . . . . 80Data Collection Methods and Associated Application Classes . . . . . . . . . . . . . . . . . . 88Collection Parameters Used By the DCM Collection Method . . . . . . . . . . . . . . . . . . . 92DCM Deactivated Parameters and their Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Collection Parameters Used By the PSL Collection Method . . . . . . . . . . . . . . . . . . . . 95Collector Deactivated Parameters and their Platforms . . . . . . . . . . . . . . . . . . . . . . . . . 96Find Files Like Command Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Remove Files Like Command Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156List of Shared-Segment Command Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 165List Network Interface Command Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 179List Memory Buffer Command Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183List Network Addresses Command Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . 185List Hosts Command Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188List Protocols Command Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190List Routing Table Command Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193List Services Command Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Tables 17

Show ARP Cache Command Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203List of NIS Accounts Command Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219List of NIS Groups Command Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220List of NIS Groups Command Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221View All Print Jobs Command Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233Variables for Monitoring Process Presence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275List Zombie Process Command Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294CPU Hogs Command Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297PROCTopProcs Text Parameter Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298New Instance Dialog Boxes and Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305Process tab properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307Start/Restart tab properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308Alert and Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309Find Files Like Command Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343List Files With Global Write Command Output Format . . . . . . . . . . . . . . . . . . . . . . . 344List Failed su/msu logins Command Output Format . . . . . . . . . . . . . . . . . . . . . . . . . 346List Users Without Passwords Command Output Format . . . . . . . . . . . . . . . . . . . . . 347List Duplicate User ID Entries Command Output Format . . . . . . . . . . . . . . . . . . . . . 349PATROL SNMP Component Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354Walk PATROL SNMP MIB Command Output Format . . . . . . . . . . . . . . . . . . . . . . . . 360Process List Command Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377Disk Space Command Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378Capture Unix Diagnostics %DUMP Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384Select Log Files to Collect Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387Accessing KM Commands and InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403Regular Expression Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409


C h a p t e r 1
1 Introduction
This chapter provides you with a brief overview of the PATROL Knowledge Module for Unix and Linux (also referred to as the PATROL KM for Unix) component.

The following topics are discussed:

PATROL KM for Unix and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Applications and Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 1 Introduction 19

PATROL KM for Unix and Linux

PATROL KM for Unix and LinuxThe PATROL Knowledge Module (KM) for Unix component is a set of files that contains knowledge in the form of command descriptions, applications, parameters, and recovery actions that analyze and manage PATROL events. The PATROL KM for Unix and Linux parameters provide a detailed view of all system activity over time so that you can detect problems, optimize systems, analyze trends, plan capacity, and manage multiple hosts simultaneously.

Supported Platforms

For a list of operating system platforms that are supported by the PATROL KM for Unix, see the PATROL for Unix and Linux Release Notes. See the PATROL for Unix and Linux Getting Started guide additional system requirements and platform information.

For a list of PATROL for Unix components and PATROL architecture components that are compatible with the PATROL KM for Unix, see the compatibility matrix in the PATROL for Unix and Linux Release Notes.

Object HierarchyThe PATROL products are organized hierarchically. At the top level of the hierarchy is the computer instance. Beneath it is the Unix operating system object. All the Unix product application classes are subordinate to the Unix object. Many of the application classes contain instances, but not all application classes have instances or parameters.

Figure 1 on page 21 illustrates the basic hierarchy. It does not necessarily display all the application classes in the product.


Object Hierarchy

Figure 1 PATROL KM for Unix Application Class Hierarchy


Object Hierarchy

Applications and Icons

Table 1 contains information on each application in the PATROL KM for Unix and Linux. For information on parameter icons, refer to the documentation for your console.

Table 1 PATROL KM for Unix and Linux Applications, Icons, and Descriptions (Part 1 of 4)

Icon Definition

agent host

represents a computer instance that corresponds to the host computer that you are monitoring

Opening a computer instance icon displays the application classes that are active for that system.

COLLECTORS

represents the COLLECTOR application, which maintains collector parameters

COMPOSITES_COLLECTOR

represents the application that you can use to construct a new composite parameter that consists of one or more parameters in a logical relationship that evaluates to true or false

You can use this application to set a warning or alarm condition based on the logical condition and not just on the parameter value. For more information, see Chapter 6, “Using Composite Parameters”

COMPOSITES

represents the application that displays instances of the composite parameters that you construct with the COMPOSITES_COLLECTOR application

CPU

represents the CPU application, which monitors CPU usage

This application also contains the SMP application on machines with multiple processors.

DCM

represents the Data Collection Manager (DCM) application, which controls data collection from PATROL Perform collector to the Data Collection Manager and to associated PATROL parameters

DISK

represents the DISK application, which monitors and provides information about disks and disk usage


Object Hierarchy

FILESYSTEM

represents the FILESYSTEM application, which monitors and provides information about file system resources

HEALTH_AT_A GLANCE

represents the HEALTH AT A GLANCE (HAAG) application, which monitors the general health and well-being of the system by providing an overall view of the system’s CPU, file system, and virtual memory usage

KERNEL

represents the KERNEL application, which monitors system kernel processes and provides kernel resource-usage information, including i-nodes, the file table, and the process table

MEMORY

represents the MEMORY application, which monitors memory activity, including paging, I/O caching, and swapping

NETWORK

represents the NETWORK application, which monitors network activity

NFS

represents the NFS application, which monitors RPC (Remote Procedure Call) and NFS (Network File System) activities

PATROL

represents the PATROL application, which shows the number of PATROL Consoles currently running

PATROLAGENT

represents the PATROLAGENT application, which monitors and manages the agent


Icon Definition


Object Hierarchy

PRINTER

represents the PRINTER application, which monitors the print queue and printer activity and with which you can perform printer administration activities

PROCESS

represents the PROCESS application, which displays statistics on active and zombie processes

PROCESS_PRESENCE

represents the application that holds PROCCONT instances

You can use this application to specify which processes you want to monitor.

name

represents the PROCPRES application, which monitors specified processes running on your system

This application is a child application of the PROCESS and PROCESS_PRESENCE (PROCCONT) applications and resides in the PROCESS_PRESENCE application’s container window.

SCHEDULER

represents the SCHEDULER application, which provides menu commands that enable you to perform tasks or run jobs once or at regular intervals.

The task or jobs are written by you and stored as script files.

SECURITY

represents the SECURITY application, which provides security-related menu commands

SMP

represents the SMP application

This application displays information for each processor on multiprocessor machines. The prefix for SMP parameters is SMP. SMP parameters appear under SMP instances in the CPU container window for machines that have multiple processors.

SNMPHealth

represents the SNMPHealth application

This application displays information on the status of the PATROL SNMP subsystem. It also provides the ability to test various aspects of the system.


Icon Definition


Help

HelpHelp describes the function of the currently displayed window or dialog box and the use of its elements. The tasks in this section describe how to access KM Help topics and context-sensitive Help from the PATROL consoles.

Accessing Online Help

Table 2 on page 26 provides information about how to access online Help on each console.

SWAP

represents the SWAP application, which monitors and provides information about utilization of system swap files

SWAP parameters appear under SWAP instance icons.

The SWAP application may return different results on different platforms.

UNIX_OS

represents the UNIX_OS application class

This application is a container for all other Unix operating system applications. It does not possess any parameters. It does provide menu commands to set debugging for various collectors and to exclude application instances from being monitored.

USERS

represents the USERS application, which monitors and provides information about user sessions and processes

NOTE If you are trying to access Help from a Unix console, you may want to refer to the PATROL Installation Guide for specific instructions on how to install and set up a browser in the Unix environment.


Icon Definition


Help

Table 2 Accessing Online Help

ConsoleTo access product help

To access application class help

To access parameter help

PATROL Console for Microsoft Windows

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

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

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

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

Double-click the parameter in the KM tab of the console; then click the Help tab and Show Help in the properties dialog box.

PATROL Console for Unix

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

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

Right-click the parameter icon, and click Help On.

PATROL Central - Microsoft Windows Edition

From the console menu bar, choose Help => Help Topics. Then double-click the name of your KM.

From the Operator tab of the console, expand or collapse the list to find the application class. Click the What’s this? Help button and then

click the application class name.

Double-click the parameter icon to open its display window. Click the Help button.

PATROL Central - Web Edition

Click the Help link, and then click the link for your KM.

Click the link for the application class, and then click the Page Help link.

Click the link for the parameter, and then click the Page Help link.


C h a p t e r 2
2 Menu Summary
This chapter summarizes the application menus and menu commands for the PATROL Knowledge Module for Unix and Linux component. The application menu content is provided in a table for each of the application classes.

This chapter describes Knowlege Module (KM) menu commands only. The KM help system provides further details about these menu commands. For descriptions of PATROL Console menu commands, see the appropriate PATROL user guide for your console.

The following topics are discussed in this chapter:

Location of KM Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29PATROL Console for Unix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29PATROL Console for Microsoft Windows Servers . . . . . . . . . . . . . . . . . . . . . . . . . 29

Menu Summary Table Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Computer Instance Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30UNIX OS Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31COLLECTORS Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33COMPOSITES Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33COMPOSITES_COLLECTOR Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33CPU Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34DCM Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34DISK Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34FILESYSTEM Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35HEALTH AT A GLANCE Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36KERNEL Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36MEMORY Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36NETWORK Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37NFS Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38PATROL Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38PATROLAGENT Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39PRINTER Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41PROCESS Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42PROCESS_PRESENCE (PROCCONT) Application Menu . . . . . . . . . . . . . . . . . . . . . . 42PROCPRES Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43


SCHEDULER Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44SECURITY Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44SMP Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44SNMPHealth Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45SWAP Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46USERS Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47


Location of KM Menu Commands

Location of KM Menu CommandsWhen a KM)is loaded, its associated menu commands are added to the KM area of a menu. Each PATROL Console presents them in a slightly different manner.


The KM area of a menu is below the menu’s horizontal line. Menu commands above the line belong to the PATROL Console.

PATROL Console for Microsoft Windows Servers

KM menu commands appear as submenus under the KM Commands menu command.

Menu Summary Table FormatThe tables in this chapter use the format described in the following table:

Table 3 Menu Summary Table Format

Menu Item Action

First-level menu Description

Second-level menu Description

Third-level menu Description

Fourth-level menu Description


Computer Instance Menu

Computer Instance MenuAccess the Computer Instance menu as described in “Accessing KM Commands and InfoBoxes” on page 402. The Computer Instance menu has the following menu commands:

Table 4 Computer Instance Menu Summary (Part 1 of 2)

Menu Command Action

OS Command displays a dialog box prompting you for an operating system command and executes the specified command

The output is displayed in the PATROL Console window.

OS Task displays a dialog box prompting you for an operating system command and executes the specified command

A task icon appears.

PSL Command displays a dialog box prompting you for a PATROL Script Language (PSL) command and executes the specified command

The output is displayed in the PATROL Console window.

PSL Task displays a dialog box prompting you for a PSL command and executes the specified command

A task icon appears.

Utilities runs PATROL, process, and file system utilities

Patrol refreshes the process cache, force discover, or reinitialize the agent

Refresh Process Cache forces the PATROL Agent to reload its process cache from the kernel process list

Force Discovery forces application discovery

Reinitialize Agent forces the PATROL Agent to restart

Process provides process-related commands

Kill Process kills a process

File System searches for and to mount and unmount file systems

Mount mounts file systems that PATROL has detected as offline or that have not been discovered

Unmount unmounts a file system that PATROL detects as mounted or that have not been discovered

Find Files Like lists all file system files whose names match the specified expression

Remove Files Like removes all file system files whose names match the specified expression


UNIX OS Application Menu

UNIX OS Application MenuAccess the UNIX_OS application menu as described in “Accessing KM Commands and InfoBoxes” on page 402. The UNIX OS application menu has the following menu commands:

:

Refresh Parameters forces an update of the application parameter values

Agent Quick Config displays a menu item to save your current selection of PATROL KMs so that your KMs automatically load the next time you start the PATROL Agent

Make Current KM Preloaded saves your current selection of PATROL KMs so that the KMs automatically load the next time you start the PATROL Agent

Start SNMP Agent starts the SNMP Master Agent on Unix platforms only

Login opens an xterm window for logging into a remote host or performing other system functions

Configure Recovery Actions accesses and edit registered recovery actions

Table 5 UNIX_OS Application Menu Summary (Part 1 of 3)

Menu Command Action


Knowledge Module Admin provides access to KM administration commands

Toggle PSL/DCM Collection selects the collection method for the PATROL KM for Unix

Specify PERFORM Home Directory

allows you to point the DCM application class to the location of the PERFORM Home directory if it is different than the location that PATROL expects, which is $PATROL_HOME/<platform_target>/ BEST1

DISK Application displays commands for the DISK application

Edit DISK Exclusion List specifies DISK instances that PATROL should ignore

Clear DISK Exclusion List removes all DISK instances from the DISK exclusion list

FILESYSTEM Application displays commands for the FILESYSTEM application

Edit FILESYSTEM Exclusion List

specifies FILESYSTEM instances that PATROL should ignore

Clear FILESYSTEM Exclusion List

removes all FILESYSTEM instances from the FILESYSTEM exclusion list

PRINTER Application displays commands for the PRINTER application

Edit PRINTER Exclusion List

specifies PRINTER instances that PATROL should ignore

Table 4 Computer Instance Menu Summary (Part 2 of 2)

Menu Command Action


UNIX OS Application Menu

Clear PRINTER Exclusion List

removes all PRINTER instances from the PRINTER exclusion list

Activate Monitoring activates monitoring all PRINTER instances that are not in the PRINTER exclusion list (monitoring is inactive by default)

Deactivate Monitoring stops monitoring of all PRINTER instances (monitoring is inactive by default)

NETWORK Application displays commands for the NETWORK application

Activate Monitoring activates monitoring all NETWORK instances

Deactivate Monitoring stops monitoring of all NETWORK instances

SNMPHealth displays commands for monitoring SNMPHealth

Activate Monitoring activates monitoring of SNMPHealth

Deactivate Monitoring stops monitoring of SNMPHealth (default setting)

Debug and Diagnostics provides access to a diagnostic report and debug controls for various collectors

Capture Unix Diagnostics gathers basic installation information such as the computer’s OS version, PATROL target, Perform target, PATROL Agent version, PATROL Console version, PATROL_HOME location, BEST1_HOME location, and license information

Create Diagnostic Report generates a diagnostic report for Support purposes

DCM Debug Admin displays a dialog box that offers several debug options for the DCM functions and binary executable

DISK Debug Admin displays a dialog box that offers several debug options for the DISK application

FILESYSTEM Debug Admin displays a dialog box that offers several debug options for the FILESYSTEM application

NETWORK Debug Admin displays a dialog box that offers several debug options for the NETWORK application

NFS Debug Admin displays a dialog box that offers several debug options for the NFS application

PRINTER Debug Admin displays a dialog box that offers several debug options for the PRINTER application

SMP Debug Admin displays a dialog box that offers several debug options for Symmetric Multi-Processors (SMP) discovery and data collection

SWAP Debug Admin displays a dialog box that offers several debug options for the SWAP application

PROCESS Debug Admin displays a dialog box that offers several debug options for the PROCESS application


Menu Command Action


COLLECTORS Application Menu

COLLECTORS Application MenuAccess the COLLECTORS application menus described in “Accessing KM Commands and InfoBoxes” on page 402. The COLLECTORS application menu has the following menu commands:

COMPOSITES Application MenuThe COMPOSITES application menu has no KM-specific menu commands. For information on common menu items, see the PATROL Console Online Help.

COMPOSITES_COLLECTOR Application MenuAccess the COMPOSITES_COLLECTOR application menu as described in “Accessing KM Commands and InfoBoxes” on page 402. The Composites application menu has the following menu commands:

IPC Resource Usage Report displays a report containing shared memory usage, semaphores usage, a list of current shared memory segments, and a list of current semaphores for the current host

BGS Command Look runs the BGS Collect Look utility

Table 6 COLLECTORS Application Menu Summary

Menu Command Action


Setup DISK Ping Script sets up the correct access privilege to the utilities for accessing the DISK information using PSL collection methods

Setup PRINTERColl Option displays a dialog box from which you can specify the number of printers to monitor


Menu Command Action


CPU Application Menu

CPU Application MenuThe CPU application menu has no KM-specific menu commands. For information on common menu items, see the PATROL Console Online Help.

DCM Application MenuAccess the DCM application menus described in “Accessing KM Commands and InfoBoxes” on page 402. The DCM application menu has the following menu commands:

DISK Application MenuAccess the DISK application menu as described in “Accessing KM Commands and InfoBoxes” on page 402. The DISK instance application menu has the following menu commands:

Table 7 Composites Application Menu Summary

Menu Command Action

Create Expressions creates a composite parameter using a wizard or by entering the information manually

Edit Expressions edits an existing composite parameter

Delete Expressions deletes an existing composite parameter

Table 8 DCM Application Menu Summary

Menu Command Action


Setup PRINTERCOLL Option

Table 9 DISK Application Menu Summary

Menu Command Action

Stop Monitoring stops monitoring the selected instance

Edit DISK Exclusion List adds a DISK instance to the list of DISKs that PATROL ignores

Clear DISK Exclusion List removes all DISK instances from the DISK exclusion list


FILESYSTEM Application Menu

FILESYSTEM Application MenuAccess the FILESYSTEM application menu as described in “Accessing KM Commands and InfoBoxes” on page 402. The FILESYSTEM application menu has the following menu commands:

Table 10 FILESYSTEM Application Menu Summary

Menu Command Action

Maintenance accesses the Maintenance menu that performs file system activities

Mount mounts file systems that PATROL has detected as offline or that have not been discoveredYou must be root to run this command.

Automatic remounts the selected instance

Manual prompts you to specify the file system to mount

Unmount unmounts a file system that PATROL detects as mounted or that has not been discoveredYou must be root to run this command.

Automatic unmounts the selected instance

Manual prompts you to specify the file system to unmount

Sync flushes all previously written buffers to disk

Find Files Like lists all file system files whose names match the specified expression

Remove Files Like removes all file system files whose names match the specified expression


Edit FILESYSTEM Exclusion List

adds a FILESYSTEM instance to the list of FILESYSTEMs that PATROL ignores

Clear FILESYSTEM Exclusion List

removes all FILESYSTEM instances from the FILESYSTEM exclusion list

Delete from FILESYSTEM Exclusion List

removes the current FILESYSTEM instance from the FILESYSTEM exclusion list


HEALTH AT A GLANCE Application Menu

HEALTH AT A GLANCE Application MenuThe HEALTH AT A GLANCE application menu has no KM-specific menu commands. For information on common menu items, see the PATROL Console Online Help.

KERNEL Application MenuThe KERNEL application menu has no KM-specific menu commands. For information on common menu items, see the PATROL Console Online Help.

MEMORY Application MenuAccess the MEMORY application menu as described in “Accessing KM Commands and InfoBoxes” on page 402. The MEMORY application menu has the following menu commands:

Table 11 MEMORY Application Menu Summary

Menu Command Action

List Shared Memory Segments displays information about the shared memory segments

List Semaphores lists information about the active semaphores

Remove Shared Memory Segments deletes a specified shared memory segment

Remove Semaphores deletes a specified semaphore


NETWORK Application Menu

NETWORK Application MenuTo access the NETWORK application menu as described in “Accessing KM Commands and InfoBoxes” on page 402. The NETWORK application menu has the following menu commands:

Table 12 NETWORK Application Menu Summary (Part 1 of 2)

Menu Command Action

TCP/IP views reports and executes TCP/IP utilities

Reports displays network and NFS activity reports in a task window

List Hosts lists the hosts on the network

List Protocols displays the list of known protocols and protocol numbers

List Services provides a list of available services

List Trusted Hosts lists TCP/IP trusted hosts

Utilities provides access to network utilities

Ftp launches the ftp (file transfer protocol) utility

Ping launches the ping utility on the specified computer

Rlogin launches a remote login to a specified computer

Query Name Server launches the internet query name server program

ARP adds and deletes hosts from the Address Resolution Protocol (ARP) table

Show Arp Cache displays the hosts and addresses in the ARP table

Delete Host From Cache deletes hosts from the ARP table

Add Host To Cache adds hosts to the ARP table

UUCP views reports and executes UUCP utilities

Reports displays UUCP reports in a task window

List Server Name displays the UUCP server name

Show Log displays the UUCP log

Show Statistics displays UUCP statistics

Utilities provides access to UUCP utilitiesYou must be root to run these commands.

UUCP Check performs a UUCP check

UUCP Clean performs a UUCP clean

UUCP displays a command entry dialog box in which you can enter UUCP changes

List Network Interface displays the state of an automatically configured interface

List Memory Buffer displays memory management statistics

List Network Address displays all the network addresses


NFS Application Menu

NFS Application MenuAccess the NFS application menu as described in “Accessing KM Commands and InfoBoxes” on page 402. The NFS application menu has the following menu commands:

PATROL Application MenuAccess the PATROL application menu as described in “Accessing KM Commands and InfoBoxes” on page 402. The PATROL application menu has the following menu commands:

List Routing Table displays the routing table and statistics for the network

Show Protocol Statistics displays the statistics for each protocol layer

Toggle Alarm/Destroy if Down destroys the network icon or sets an alarm if the network interface is down

Table 13 NFS Application Menu Summary

Menu Command Action

NFS displays NFS options

Reports displays report options

List Servers lists all the NFS servers for the system in a task window

Zero NFS Counters resets the NFS counters to zeroYou must be root to run this command.

NIS displays NIS options

Reports displays report options

List Accounts displays a list of all NIS accounts in a task window

List Groups displays a list of all NIS groups in a task window

List Servers displays a list of all NIS servers in a task window

Table 14 PATROL Application Menu Summary

Menu Command Action

Refresh Parameters forces an update of the application parameters

Table 12 NETWORK Application Menu Summary (Part 2 of 2)

Menu Command Action


PATROLAGENT Application Menu

PATROLAGENT Application MenuTo access the PATROLAGENT application menu as described in “Accessing KM Commands and InfoBoxes” on page 402. The PATROLAGENT application menu has the following menu commands:

Table 15 PATROLAGENT Application Menu Summary (Part 1 of 2)

Menu Command Action

View Agent Log displays the contents of the agent logs

Tune Agent fine-tunes the agent's performance

Show Tuning Variables displays the current setting of the agent tuning variables

Set Agent Variables sets agent tuning variables

Set Get Processes Cycle (appl)

sets the interval for the system to refresh the process cache

Set Appl Check Cycle sets both simple and PSL discovery poll times

Set Priority sets agent, user, and process cache priority as well as schedule process cache priority

Agent sets the priority for the PATROL Agent.

Process Cache sets the priority that the process cache has for gathering process information

Process Cache Schedule sets the priority of the agent run queue

User sets the priority for user commands

Set Run Queue controls agent execution

Delta sets the length of time, in seconds, between successive agent executions

Delta Increment sets the time interval (increment) to be used in scheduling parameter execution

Maximum Delta sets the maximum value that the process scheduling delta can be set

Schedule Policy sets up the scheduling for agent connection using the following scheduling submenus

Schedule From End The next scheduled execution will occur at the current execution end time.

Schedule From Prev The next scheduled execution will occur at the prior execution end time.

Schedule Automatic The next scheduled execution will be automatically determined by the agent to execute at the optimal time.

Schedule Force Delta The next scheduled execution will occur at the prior execution start time.

Reset Agent to Default Setting

resets the agent’s variables to their default settings


PATROLAGENT Application Menu

List Agent Information displays information about the processes running on the agent

Runable Processes displays all process information that is in the run queue

Running Processes displays all processes that are currently running

Executing Task Commands displays all the task information that is currently in the queue

Registered Applications displays all the applications that are registered by PATROL

Discovered App Instances displays the applications that have been discovered by PATROL

Registered Parameters displays all the parameters registered by PATROL

Error Backtrace displays a backward trace of the agent's error log

List Agent Tuning Variables displays the current setting of the agent tuning variables

Search Agent Process Cache searches the agent's process cache

Trigger Agent Activities executes a refresh of the parameters and process cache and performs application discovery

Perform Application Discovery

causes the agent to execute all application discovery scripts

Refresh Process Cache forces the PATROL Agent to reload its process cache from the kernel process


Table 15 PATROLAGENT Application Menu Summary (Part 2 of 2)

Menu Command Action


PRINTER Application Menu

PRINTER Application MenuAccess the PRINTER application menu as described in “Accessing KM Commands and InfoBoxes” on page 402. The PRINTER application menu has the following menu commands:

Table 16 PRINTER Application Menu Summary

Menu Command Action

List Print Jobs lists all the print jobs for the selected printer

List All Print Jobs lists all the print jobs for all monitored printers

Delete Job deletes the specified print job

Delete All Jobs deletes all the print jobs for the selected printer

Stop Printer disables the selected printer

Start Printer enables the selected printer

Stop Queue disables the selected print queue

Start Queue enables the selected print queue

Move Job To Another Printer moves the specified print job to the specified printer

Move All Jobs to Another Printer

moves all the print jobs from the selected PRINTER to a specified printer


Edit PRINTER Exclusion List adds a PRINTER instance to the list of PRINTER instances that PATROL ignores

Clear PRINTER Exclusion List removes all PRINTER instances from the PRINTER exclusion list


PROCESS Application Menu

PROCESS Application MenuAccess the PROCESS application menu as described in “Accessing KM Commands and InfoBoxes” on page 402. The PROCCONT application menu has the following menu commands:

For more information about monitoring processes, see Chapter 14, “Monitoring Processes.”

PROCESS_PRESENCE (PROCCONT) Application Menu

Access the PROCESS_PRESENCE application menus described in “Accessing KM Commands and InfoBoxes” on page 402. The PROCCONT application menu has the following menu commands:

Table 17 PROCESS Application Menu Summary

Menu Command Action

List Zombie Process displays information about the zombie processes that persist on the system

CPU Hogs displays processes that use the CPU excessively

Renice Process decreases the execution priority of the specified process

Renice Group decreases the execution priority of all processes in the specified PROCESS group

Renice User decreases the execution priority for all processes that the specified USER launches


Table 18 PROCESS_PRESENCE Application Menu Summary (Part 1 of 2)

Menu Command Action

Manage List of Monitored Processes

use to add, modify, and report on monitored processes in your environment

Manage Host Group use to add, modify, and report on watched hosts in your environment

Synchronize use to synchronize group lists and process lists

Group List synchronizes settings between hosts within a group. Also, specifies group communications (such as timeout settings, and whether to accept or send changes made on one host to the rest of the group).

Process List synchronizes the list of monitored processes for hosts within a group


PROCPRES Application Menu

PROCPRES Application MenuAccess the PROCPRES application menu commands as described in “Accessing KM Commands and InfoBoxes” on page 402. The PROCPRES application menu has the following menu commands:

ProcSpring Migration Tools

accesses the menu options that allow you to use and configure the ProcSpring Migration Tools

About ProcSpring Migration Tools

provides information about the ProcSpring Migration Tools other ProcSpring menu commands

Migrate ProcSpring provides options for full or partial migration of ProcSpring log entries

Deactivate ProcSpring w/o Migrating

removes all related ProcSpring pconfig entries and deactivates ProcSpring

Reactivate ProcSpring restores previous ProcSpring settings and reactivates ProcSpring

Identify Flag Directory specifies a directory where PATROL will look for process presence flag files

Table 19 PROCPRES Application Menu Summary

Menu Command Action

Display Included Processes displays all the individual processes currently being monitored for process presence

Table 18 PROCESS_PRESENCE Application Menu Summary (Part 2 of 2)

Menu Command Action


SCHEDULER Application Menu

SCHEDULER Application MenuAccess the SCHEDULER application menu as described in “Accessing KM Commands and InfoBoxes” on page 402. The SCHEDULER application menu has the following menu commands:

SECURITY Application MenuAccess the SECURITY application menu as described in “Accessing KM Commands and InfoBoxes” on page 402. The SECURITY application menu has the following menu commands:

SMP Application MenuThe SMP application has no KM-specific menu commands. For information on common menu items, see the PATROL Console Online Help.

Table 20 SCHEDULER Application Menu Summary

Menu Command Action

Schedule Tasks schedules a task to run at once or at regular intervals

Schedule Blackout suspends monitoring of applications during routine maintenance or other activities that generate false alarms

Set Default Blackout Script Directory

establishes in which directory the KM is stores blackout scripts

Scheduling Debug writes debug information to the system output window

Table 21 SECURITY Application Menu Summary

Menu Command Action

Administration provides listings of the group and password files and shows the failed logins

List SUID and SGID Files displays all of the files that have the suid or the sgid (guid) bit set

List Failed su/msu Logins displays information about each user who tries and fails to execute an su or msu command

List Users Without Password displays all users who do not have a password

List Duplicate User Id Entry displays all users who have multiple sessions active

List Files With Global Write displays all files that can be written to by any user


SNMPHealth Application Menu

SNMPHealth Application MenuAccess the SNMPHealth application menu as described in “Accessing KM Commands and InfoBoxes” on page 402. The SNMPHealth application menu has the following menu commands:

:

Table 22 SNMPHealth Application Menu Summary (Part 1 of 2)

Menu Command Action

SNMP Configuration provides a way to discover the SNMP configuration of PATROL

Change SNMP Query Port changes the SNMP Query Port, which is used by external processes to make SNMP queries against the PATROL Agent

List Configuration Information

displays SNMP-related information that includes PATROL Agent namespace variables relating to SNMP, statuses of the master agent and subagent, and port numbers

Start/Stop SNMP Agent provides a way to manually start and stop components of the PATROL SNMP system

Start SNMP Master Agent starts the SNMP Master AgentWhen the PATROL Agent starts, the computer application’s SNMPStart parameter automatically starts the SNMP Master Agent. This command is used to restart the master agent after it has been intentionally or unintentionally stopped.

Start SNMP sub-agent starts the SNMP subagentThe SNMPHEALTH application class’s snmp_subagent_start parameter attempts to start the subagent if it is not running. This command is used to restart the subagent between the snmp_subagent_start’s scheduled poll time.

Stop SNMP sub-agent stops the SNMP subagentThis command changes the state of the SNMPHEALTH application class’s snmp_subagent_monitor parameter to ALARM.

Test PATROL SNMP System provides several ways to test your PATROL SNMP system

Listen for SNMP Traps listens for SNMP traps on the port specified in the agent configuration variable /snmp/trap_port, whose default value is 162If port 162 is in use and you do not change the configuration variable, this command does not function properly.

Generate Manual SNMP Trap

displays a dialog box that sends a customized trap in which you define the trap’s host, port, community, and four strings

SNMP Query PATROL Master Agent

displays a dialog box that queries the PATROL Agent

SNMP Query PATROL platform.km

displays a dialog box that queries your computer’s platform knowledge module


SWAP Application Menu

SWAP Application MenuThe SWAP application menu has no KM-specific menu commands. For information on common menu items, see the PATROL Console Online Help.

SNMP Query Using snmp_h_get

displays a dialog box that enters a host name and object ID (OID) and runs the PSL function snmp_h_get( )

If no SNMP Managers are listening on port 161, the command times out.

Walk PATROL SNMP Mib displays a dialog box that uses BMC system’s object ID to view the PATROL Agent SNMP management information base (MIB) if the PATROL Agent is listening on the designated port

Test PATROL SNMP System

provides a means to test whether automatic SNMP traps are generated when PATROL issues an event and changes an object’s state

Set SNMPH_testparm OK

changes the state of the SNMPHEALTH application class’s testparm parameter to OK and issues a trap if the SNMP system is set up

Set SNMPH_testparm WARN

changes the state of the SNMPHEALTH application class’s testparm parameter to WARN and issues a trap if the SNMP system is set up

Set SNMPH_testparm ALARM

changes the state of the SNMPHEALTH application class’s testparm parameter to ALARM and issues a trap if the SNMP system is set up

Table 22 SNMPHealth Application Menu Summary (Part 2 of 2)

Menu Command Action


USERS Application Menu

USERS Application MenuAccess the USERS application menu as described in “Accessing KM Commands and InfoBoxes” on page 402. The USERS application menu has the following menu commands:

Table 23 USERS Application Menu Summary

Menu Command Action

List Print Jobs displays all the print jobs that belong to the specified user

Process List displays all the processes that belong to the specified user

Disk Space displays the amount of disk space used by the specified user

List Current Users displays a list of users that are currently active on the host


USERS Application Menu


C h a p t e r 3
3 Parameter Summary
This chapter provides a summary of parameters for the PATROL KM for Unix and Linux. Refer to the PATROL user guide for your console for additional information about the different types of parameters and their functions. See the PATROL KM for Unix and Linux online Help system for details about KM-specific parameters. The following topics are discussed:

Parameter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Parameter Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80


Parameter Summary

Parameter SummaryThe PATROL KM for Unix and Linux has various parameters that provide statistical information about resources, operating status, and performance. Table 24 lists each application class and its associated parameters. The table also provides information that you can use when selecting or reviewing the appropriate parameters used in monitoring the PATROL KM.

Table 24 PATROL KM for Unix and Linux Parameter Summary (Part 1 of 30)

Parameter Description See Also

ALL_COMPUTERS Application

BlockSize converts OS memory to 1-KB blocks

Platforms: Solaris, HP, OSF1, RS6000, SINIX, Linux

page 81

BootTime holds a time stamp of the last time the system was rebooted


page 80

DFBlockSize converts OS disk block values to 1-KB blocks

Platforms: Solaris, HP, RS6000, SINIX, Linux

page 81

Get_700_nproc determines the hardware model (700/800) and HP-UX version on pre-HP-UX 10 model 700 machines

Platforms: HP

page 81

KernelInfo collects information about the kernel, such as when it was last built


page 81

LPSpoolDirectory maintains a list of possible locations for print queues

This parameter is used by PRINTER discovery to limit instance creation to printers that have locally defined queues.


page 82

MaxConfigValLen contains the maximum number of characters permitted in the value of a variable stored in the agent configuration database and is used for edit checking


page 82

OSName collects information about the operating system


page 84

PageSize converts OS page units into 1-KB page units


page 84


Parameter Summary

SetupClearText clears the screen for a parameter that generates text output


page 85

SNMPStart starts the SNMP Master Agent

Platforms: Windows, Solaris, HP, OSF1, RS6000, SINIX, Linux

page 86

TerminalEmulator sets the terminal emulator that PATROL should use; an xterm window is the default on most platforms


page 86

COLLECTORS

CollectorStatus generates an alert if the pconfig variable DCMStatusText exists and saves its contents in the CollectorStatusText parameter

page 80

CollectorStatusText receives the contents of the pconfig variable DCMStatusText page 80

DFColl executes the df command, collects the output, and then sets the values of the FILESYSTEM parameters

page 81

HAAGColl collects data for the HEALTH_AT_A_GLANCE application classes

page 81

NETColl executes the netstat command to collect information about incoming packets, outgoing packets, and errors and sets NETWORK parameters

page 83

NFSColl executes the nfsstat command to collect information about NFS and sets the values of the various NFS parameters

page 83

PRINTERColl executes the lpstat -t command, determines the status of each queue, and displays information about all the local and remote printers you are monitoring

page 84

PROCColl collects kernel information on the Linux platform and sets KERFileUsedPercent and KERINodeUsedPercent

page 84

PSColl calculates the top 10 processes that use the most cpu resources and sets the PROCTopProcs parameter

page 85

SARColl executes the sar command and sets various parameters

Platforms: AIX, HP-UX

Note: On AIX systems, the account that executes the sar command must belong to the adm group.

page 85

SMPColl executes the mpstat command and collects information about each individual CPU on the system

This collector is different from the SARColl and VMColl because these parameter look at multiple CPUs as a whole and report a single value. The SMPColl collector then sets the values of the SMP parameters.

Platforms: HP-UX, Solaris

page 85




Parameter Summary

UPTColl executes the uptime command and sets the CPULoad parameter

page 86

USRPROCColl collects information to set USERS parameters page 86

VMColl gathers operating system information related to memory by executing the vmstat command and sets various parameters

page 86

COMPOSITES_COLLECTOR Application

CPARMCollector collects information for the defined composite parameters page 80

COMPOSITES Application

CPARMResult displays the results of the composite parameter calculation for the specified composite parameter

Collector: CPARMCollector

page 80

CPARMExpression displays the composite parameter definition


page 80

CPARMGeneratedCodeText displays the PSL that was generated by the Composites expression generator and used to determine the composite parameter value


page 80

CPU Application Class

CPUCpuUtil displays the percentage of time the CPU was being used page 80

CPUIdleTime displays the percentage of time that the CPU was idle page 80

CPUInt displays the number of non-VME device interrupts

A non-VME interrupt is an interrupt that does not originate from the backplane.

Collector: VMColl

Note: When using DCM collection, PATROL deactivates this parameter on all platforms. When using PSL collection, PATROL deactivates this parameter on AIX.

page 80

CPULoad displays the 1-minute load average from the uptime command

Collector: UPTColl

page 80

CPUProcSwch displays the total number of CPU context switches per second

Collector: SARColl or VMColl

Note: When using DCM collection, PATROL deactivates this parameter on all platforms.

page 80

CPURunQSize displays the number of processes in the run queue (RunQ) page 81




Parameter Summary

CPUSysTime displays the percentage of CPU time spent in system mode doing system tasks, including the time consumed by calls to kernel routines

Collector: DCMColl, SARColl or VMColl

page 81

CPUUserTime displays the percentage of CPU time currently being spent in user mode executing commands and performing user tasks

page 81

CPUWio displays the percentage of CPU time spent waiting for input and output operations

Platforms: All except Linux

Note: When using PSL collection, PATROL deactivates this parameter on Compaq Tru64 (Digital Unix, OSF/1) and Solaris.

page 81

DCM Application Class

PATROL creates this application class only if the PATROL KM for Unix is using the DCM collection method.

CPUCollStatus indicates whether the CPU data is collected by the DCM or PSL page 80

CPUCtrl controls the poll time and status (active or inactive) for DCM collection of CPU application parameter data

page 80

DCMColl passes data from the Data Collection Manager binary program (DCM) to many parameters

page 81

DCMMessages displays status messages for the DCM process

Anytime the DCM_Alert parameter goes into alarm, PATROL documents the problem in this parameter. It also records start/stop/restart events for the DCM process.

This parameter manages the number of lines in the text so that it keeps the last 'N' messages where 'N' is determined as follows:

■ If the agent namespace variable /DCM/DCM/DCMStatus/maxLength is set, then that value is used.

■ Otherwise, the parameter uses the PCONFIG variable /DCM/DCM/DCMStatus/maxLength if it is available.

■ Otherwise, the parameter will default to 40 lines.

Once the max number of lines is reached, the parameter uses a FIFO mechanism so that the oldest messages are removed to make room for the newest messages.

page 81




Parameter Summary

DCMMonitor monitors the status of the DCM process and the global channel used by the KM to communicate with the DCM process

When it detects a problem, it logs a message to the DCMStatus parameter and closes the channel. Once the channel is closed, the DCMColl parameter exits. The agent reschedules DCMColl. On its next execution, the DCMColl parameter restarts the DCM process.

page 81

DCMStatus displays the health of the DCM process page 81

DCMUpdateCount displays the number of parameter values sent to the PATROL Agent from the DCM process

It provides one measure of the performance of the PATROL Agent/DCM interface.

The number parameter values varies based on the characteristics of your system (for example, number of hard disks) and the configuration of the DCM application class. Both the polling rate and the active/inactive state of the DCM control parameters have an effect on how many parameters values are updated at any one time. DCMUpdateTime is set each time DCMUpdateCount is set.

page 81

DCMUpdateTime displays the number of seconds spent by PATROL Agent processing a data update from the DCM process

It provides one measure of the performance of the PATROL Agent/DCM interface.

The time varies depending on the number of data values included in one update and the other factors on your system. Particularly, the configuration of the UNIX KM and the PATROL Agent with respect to the parameter history file. Anytime the PATROL Agent writes or flushes a significant amount of data to disk, it is possible that this parameter will record an update time that is much longer than normal.

page 81

DFColl executes the df command and collects the output. Then, it then sets the values of the FILESYSTEM parameter.

page 81

DiskCollStatus indicates whether the disk data is collected by the DCM or PSL page 81

DISKCtrl controls the poll time and status (active or inactive) for DCM collection of DISK application parameter data

page 81

HAAGColl gathers data on the system’s overall CPU, File System, and Swap file usage

page 81

KernelCollStatus indicates whether kernel data is collected by the DCM or PSL page 81

KERNELCtrl controls the poll time and status (active or inactive) for DCM collection of KERNEL application parameter data

page 82

MemCollStatus indicates whether memory data is collected by the DCM or PSL page 82




Parameter Summary

MEMORYCtrl controls the poll time and status (active or inactive) for DCM collection of MEMORY application parameter data

page 82

NETColl executes the netstat command to collect information about incoming packets, outgoing packets, and errors and sets NETWORK parameters

page 83

NFSColl executes the nfsstat command to collect information about NFS and sets the values of the various NFS parameters

page 83

PRINTERColl executes the lpstat -t command, determines the status of each queue, and displays information about all the local and remote printers you are monitoring

page 84

PROCColl collects kernel information on the Linux platform and sets KERFileUsedPercent and KERINodeUsedPercent

page 84

ProcessCollStatus indicates whether process data is collected by the DCM or PSL. Issues an alarm if the method of collecting data automatically changes from DCM to PSL. This indicates that the Perform collector is not collecting data from consumer parameters.

page 84

PROCESSCtrl controls the poll time and status (active or inactive) for DCM collection of PROCESS application parameter data

page 84

PSColl calculates the top 10 processes that use the most CPU resources and sets the PROCTopProcs parameter

page 85

SARColl executes the sar command and collects the output. Then, it parses the output and performs the necessary data conversions, such as converting page size to a standard 1-K page. Finally, this collector sets the values of the appropriate PATROL parameters

page 85

SMPColl executes the mpstat command and collects information about each individual CPU on the system. The SMPColl collector then sets the values of the SMP parameters

page 85

SwapCollStatus indicates whether swap data is collected by the DCM or PSL page 86

SWAPCtrl controls the poll time and status (active or inactive) for DCM collection of SWAP application parameter data

page 86

UPTColl executes the uptime command page 86

UserCollStatus indicates whether user data is collected by the DCM or PSL page 86

USERSCtrl controls the poll time and status (active or inactive) for DCM collection of USERS application parameter data

page 86

USRPROColl collects operating system information relating to users.

The UserProcess collector calculates the following information:

■ the number of users currently on the system■ the number of user sessions■ the total number of user processes on the system■ the average number of user processes

page 86




Parameter Summary

VMColl gathers operating system information related to system memory and executes the vmstat command and collects the output. Then, it parses the output and performs the necessary data conversions, such as converting page size to a standard 1-K page

page 86

DISK Application Class

ChangeDiskLabel changes the label for a DISK instance from "sdNN" to "sdNN (cNNtNNdNN)." For example, changes the disk label from “sd3” to “sd31 (c1t1d0).”

This parameter makes the disk label more user-friendly by showing both valid label names for a given disk.

page 80

DSKAvgQueue average number of requests in the queue

Collector: DMColl

Platforms: All except AIX and Linux

Note: When using PSL collection, PATROL deactivates this parameter on Compaq Tru64 (Digital Unix, OSF/1).

page 81

DSKAvgServ displays the average service time, in milliseconds, for the device to complete transfer requests

For a disk, it includes seek time, rotational latency, and transfer time.

Collector: DMColl


Note: When using PSL collection, PATROL deactivates this parameter on AIX and Compaq Tru64 (Digital Unix, OSF/1).

page 81

DSKAvgWait displays the average time that transfer requests wait in the queue for the device

Collector: VMColl


page 81

DSKBps displays the number of 1-KB blocks read from or written to the device per second

Collector: DCMColl

page 81

DSKMsps displays the average disk seek time for the device and indicates the speed of the device

Collector: VMColl

page 81




Parameter Summary

DSKPercentBusy displays the percentage of time that the device is busy servicing a transfer request

Collector: DCMColl



page 81

DSKRead displays the number of kilobytes read from disk per second

Collector: DCMColl

Platforms: AIX, Solaris, Linux

Note: When using PSL collection, PATROL deactivates this parameter on Solaris.

page 81

DSKReadWrite displays the number of read and write pages made to/from the device per second

Collector: DCMColl


page 81

DSKSps displays the number of disk seeks per second

Collector: DCMColl

Platforms: Compaq Tru64 (Digital Unix, OSF/1), HP-UX


page 81

DSKTps displays the number of disk transfers per second

Collector: DCMColl

Platforms: AIX, Compaq Tru64 (Digital Unix, OSF/1), HP-UX, Solaris

page 81

DSKWrite displays the number of kilobytes written to disk per second

Collector: DCMColl

Platforms: AIX, Linux, Solaris

Note: When using PSL collection, PATROL deactivates this parameter on Solaris.

page 81




Parameter Summary

FILESYSTEM Application Class

FSAvailableSpace displays the amount of space available for this file system instance

Collector: DFColl

page 81

FSAvailableSpaceMB displays the amount of space available in megabytes for this file system instance

Collector: DFColl

page 81

FSCapacity displays the percentage of the file system storage that is currently in use

Collector: DFColl

page 81

FSFreeInodes displays the number of unused i-nodes on the local file system

Collector: DFColl

page 81

FSInodeUsedPercent displays the percentage of i-nodes used

Collector: DFColl

page 81

FSMountStatus displays the mount status of the file system

Collector: DFColl

page 81

FSUsedSpace displays the amount of used space for the file system instance

Collector: DFColl

page 81

HEALTH AT A GLANCE Application Class

HAAGCPUUsage displays whether or not the system’s overall CPU usage is satisfactory

Collector: HAAGColl

page 81

HAAGFilesystemUsage displays whether or not the system’s overall File System usage is satisfactory.

Collector: HAAGColl

page 81

HAAGHealthSummary reports on the system's overall health based on the other HAAG parameters: HAAGCPUUsage, HAAGFilesystemUsage, HAAGSwapUsage

Collector: HAAGColl

page 81

HAAGSwapUsage displays whether or not the system’s overall swap file usage is satisfactory

Collector: HAAGColl

page 81




Parameter Summary

KERNEL Application Class

KERDirBlk displays the number of directory-block reads issued per second

Collector: SARColl



page 81

KERFileUsedPercent displays the percentage of kernel file slots being used

This parameter monitors file table use.

Collector: DCMColl or SARColl

Platforms: AIX, HP-UX, Linux

Note: When using DCM collection, PATROL deactivates this parameter on all platforms except HP-UX. When using PSL collection, PATROL deactivates this parameter on Compaq Tru64 (Digital Unix, OSF/1).

page 81

KERIGet displays the number of files located by an i-node entry

Collector: SARColl



page 82

KERINodeUsedPercent displays the percentage of kernel i-node slots being used


Platforms: All except HP, AIX, Linux, and Solaris

Note: When using DCM collection, PATROL deactivates this parameter on all platforms except Compaq Tru64 (Digital Unix, OSF/1) and HP-UX. When using PSL collection, PATROL deactivates this parameter on Compaq Tru64 (Digital Unix, OSF/1).

page 82

KERLgAlloc displays the number of bytes allocated for large memory requests

Collector: SARColl

page 82

KERLgFail displays the number of large memory pool requests that were not satisfied

Collector: SARColl

page 82




Parameter Summary

KERLgMem displays the amount of memory in bytes available in the KERNEL Memory Allocation (KMA) large memory request pool

Collector: SARColl

page 82

KERLockUsedPercent displays the percentage of kernel lock slots being used

Collector: SARColl

page 82

KERMsg displays the number of message operations performed per second

You can use this parameter to monitor applications that use message operations to communicate with other processes.


Platforms: All except Compaq Tru64 (Digital Unix, OSF/1) and Linux

Note: When using DCM collection, PATROL deactivates this parameter on all platforms except AIX and Compaq Tru64 (Digital Unix, OSF/1). When using PSL collection, PATROL deactivates this parameter on Solaris.

page 82

KERMsgNumQueUsedPercent

displays the percentage of the total number of available message queues being used system-wide

Collector: DCMColl

Platforms: all except AIX and Compaq Tru64 (Digital Unix, OSF/1)

page 82

KERMsgNumUsedPercent displays the percentage of the total number of available kernel messages that are being used system-wide

Collector: DCMColl

Platforms: all except AIX

page 82

KERNameI displays the number system pathname searches being performed

Collector: SARColl

Platforms: HP-UX


page 82




Parameter Summary

KEROvzAlloc displays the amount of memory dynamically allocated for oversized requests

Collector: SARColl

page 82

KEROvzFail displays the number of requests for oversized memory that could not be satisfied

Collector: SARColl

page 82

KERProcUsedPercent displays the percentage of kernel process slot used. This parameter monitors the process table utilization


Platforms: All except AIX and Linux

Note: When using DCM collection, PATROL deactivates this parameter on all platforms except Compaq Tru64 (Digital Unix, OSF/1) and HP-UX. When using PSL collection, PATROL deactivates this parameter on Solaris.

page 82

KERSemNumUsedPercent displays the percentage of the total number of available semaphores used system-wide

Collector: DCMColl

Platforms: All except AIX and Compaq Tru64 (Digital Unix)

page 82

KERSemNumSetUsedPercent displays the percentage of the total number of available semaphore sets that are being used system-wide

Collector: DCMColl

page 82

KERSemOps displays the number of semaphore operations per second and monitors applications that use semaphore operations to communicate with other processes



Note: When using DCM collection, PATROL deactivates this parameter on all platforms except AIX, Compaq Tru64 (Digital Unix, OSF/1), and Solaris. When using PSL collection, PATROL deactivates this parameter on Solaris.

page 82

KERShmNumUsedPercent displays the percentage of the total number of available shared memory segments that are being used system-wide

Collector: DCMColl

page 82




Parameter Summary

KERSmlAlloc displays the amount of memory in bytes allocated to the small memory request pool by KERNEL Memory Allocation.

Collector: SARColl

page 82

KERSmlFail displays the number of small memory requests that failed

Collector: SARColl

page 82

KERSmlMem displays the amount of memory in bytes that is available in the small memory request pool allocated by KERNEL Memory Allocation

Collector: SARColl

page 82

KERSysCall displays the number of system calls made per second

This number is the total of all read, write, fork, and exec system calls.

page 82

MEMORY Application Class

MEMActiveVirPage displays the number of active virtual pages

Collector: VMColl

Note: When using DCM collection, PATROL deactivates this parameter on all platforms. When using PSL collection, PATROL deactivates this parameter on AIX (32 bit).

page 82

MEMAddrTransFault displays the number of pages that were not in physical memory when accessed

Collector: SARColl; VMColl for OSF/1

Platforms: Compaq Tru64 (Digital Unix, OSF/1)


page 82

MEMBRead displays the number of physical reads per second from the disk to the buffer cache

Collector: SARColl

Platforms: AIX


page 82




Parameter Summary

MEMBWrt displays the number of physical writes per second from the disk to the system buffer cache

Collector: SARColl

Platforms: AIX


page 82

MEMCow displays the number of page write faults that have occurred

Collector: VMColl



page 82

MEMFreeMem displays the number of pages of memory available

Collector: DCMColl, SARColl or VMColl

Note: When using PSL collection, PATROL deactivates this parameter on AIX (32-bit) and Solaris.

page 82

MEMLRead displays the number of logical blocks read per second from the system buffer




page 82

MEMLWrt displays the number of writes per second to the system buffer




page 82

MEMPageAnticipated displays the anticipated short-term memory shortfall in memory pages

Collector: VMColl



page 82




Parameter Summary

MEMPageFreed displays the number of pages that were added to the free list by the page-stealing daemon

Collector: VMColl or SARColl


Note: When using DCM collection, PATROL deactivates this parameter on all platforms. When using PSL collection, PATROL deactivates this parameter on AIX (32-bit).

page 82

MEMPageIn displays the number of pages that have been swapped in from secondary memory


Note: When using PSL collection, PATROL deactivates this parameter on AIX (32-bit).

page 82

MEMPageOut displays the number of pages swapped out of main memory to secondary memory


Note: When using PSL collection, PATROL deactivates this parameter on AIX (32-bit).

page 82

MEMPageScanned displays the number of pages scanned per second by the page-stealing daemon to find more memory



page 82

MEMPFault displays the number of page protection faults that caused pages to be copied

Note: When using PSL collection, PATROL deactivates this parameter on AIX, Compaq Tru64 (Digital Unix, OSF/1), HP-UX, and Solaris.

page 82

MEMPgFil displays the number of page faults that have been reclaimed by bringing the pages in from the file system

Collector: SARColl

page 82




Parameter Summary

MEMPRead displays the number of raw reads per second from character device (TTYs)



page 82

MEMPWrt displays the number of raw writes per second to character devices (TTYs)



page 83

MEMRCache displays the percentage of read misses in the buffer cache

Collector: SARColl



page 83

MEMWCache displays the percentage of logical blocks written in the buffer cache

Indicates the effectiveness of system buffering

Collector for group A platforms: DCMColl

Collector for group B platforms: SARColl


Note: When using PSL collection, PATROL deactivates this parameter on Compaq Tru64 (Digital Unix, OSF/1) , AIX, and Solaris.

page 83

MEMWire displays the number of 1-KB memory pages that cannot be paged out of main memory

This parameter shows locked memory.

Collector: VMColl



page 83




Parameter Summary

MEMZero This parameter displays the number of memory pages that are zero-filled on demand.

Collector: VMColl



page 83

NETWORK Application Class

NETCollisionPrc displays the percentage of network send collisions

Collector: NETColl

page 83

NETInErrPrc displays the number of incoming data packets containing errors per second

Collector: NETColl

page 83

NETOutErrPrc displays the number of outgoing data packets containing errors per second

Collector: NETColl

page 83

NETPacketsIn displays the total number of incoming packets per second

Collector: NETColl

page 83

NETPacketsOut displays the total number of outgoing packets per second

Collector: NETColl

page 83

NETPseudoAddresses displays the virtual address assigned to a network interface

Collector: NETWORK Discovery


page 83

NFS Application Class

NFSCBadCall displays the percentage of all NFS client calls that failed (since the last sample)

Collector: NFSColl

page 83

NFSCCall displays the total number of NFS client calls made (since the last sample)

Collector: NFSColl

page 83

NFSCCreate displays the percentage of all NFS client calls made to create a new file (since the last sample)

Collector: NFSColl

page 83




Parameter Summary

NFSCFsStat displays the percentage of all NFS client calls made to retrieve file attributes or files statistics (since the last sample)

Collector: NFSColl

page 83

NFSCGetAttr displays the percentage of all NFS client calls that are requests to get file attributes (since the last sample)

Collector: NFSColl

page 83

NFSCLink displays the percentage of all NFS client calls made to create hard links (since the last sample)

Collector: NFSColl

page 83

NFSCLookUp displays the percentage of all NFS client calls made to look up directory paths (since the last sample)

Collector: NFSColl

page 83

NFSCMkDir displays the percentage of all NFS client calls that are calls made to create directories (since the last sample)

Collector: NFSColl

page 83

NFSCNclGet displays the number of times that the client had to request a new client handle for an NFS call (since the last sample)

Collector: NFSColl

page 83

NFSCNclSleep displays the number of times that the kernel had to wait to obtain client structure information (since the last sample)

Collector: NFSColl

Platforms: All except Linux and Solaris

page 83

NFSCNull displays the percentage of NFS client calls that request no action other than acknowledgement (since the last sample)

Collector: NFSColl

page 83

NFSCRead displays the number of all NFS client calls that are calls to read data from files (since the last sample)

Collector: NFSColl

page 83

NFSCReadDir displays the percentage of all NFS client calls made to read directories (since the last sample)

Collector: NFSColl

page 83

NFSCReadLink displays the percentage of NFS client calls made to read symbolic links (since the last sample)

Collector: NFSColl

page 83




Parameter Summary

NFSCRemove displays the percentage of all NFS client calls made to remove files (since the last sample)

Collector: NFSColl

page 83

NFSCRename displays the percentage of all NFS client calls made to rename files (since the last sample)

Collector: NFSColl

page 83

NFSCRmDir displays the percentage of all NFS client calls made to remove directories (since the last sample)

Collector: NFSColl

page 83

NFSCRpcBadCall displays the percentage of all NFS client RPC calls that returned an error other than time-outs or interruptions (since the last sample)

Collector: NFSColl

page 83

NFSCRpcBadXid displays the percentage of client RPC calls for which multiple responses were received (since the last sample)

Collector: NFSColl

page 83

NFSCRpcCall displays the total number of NFS client RPC calls made to the selected server by all clients (since the last sample)

Collector: NFSColl

page 83

NFSCRpcNewCred displays the number of client RPC calls that are calls made to refresh authentication information (since the last sample)

Collector: NFSColl


page 83

NFSCRpcNullRecv displays the number of empty messages received from TCP or LAN (since the last sample)

Collector: NFSColl

page 83

NFSCRpcRetrans displays the number of NFS client RPC requests that had to be retransmitted (since the last sample)

Collector: NFSColl

page 83

NFSCRpcTimeOut displays the percentage of all client RPC calls that timed out because no client handles were available (since the last sample)

Collector: NFSColl

page 83




Parameter Summary

NFSCRpcWait displays the number of times that a client request had to wait because a client handle was unavailable (since the last sample)

Collector: NFSColl


page 83

NFSCSetAttr displays the percentage of all NFS client calls made to store file attributes (since the last sample)

Collector: NFSColl

page 83

NFSCSymLink displays the percentage of all NFS client calls made to create symbolic links (since the last sample)

Collector: NFSColl

page 83

NFSCWrite displays the number of all NFS client calls made to write files (since the last sample)

Collector: NFSColl

page 83

NFSSBadCall displays the percentage of all NFS server calls that failed (since the last sample)

Collector: NFSColl

page 83

NFSSCall displays the total number of NFS server calls made (since the last sample)

Collector: NFSColl

page 84

NFSSCreate displays the percentage of all NFS server calls made to create a new file (since the last sample)

Collector: NFSColl

page 84

NFSSFsStat displays the percentage of all NFS server calls made to retrieve file attributes or files statistics (since the last sample)

Collector: NFSColl

page 84

NFSSGetAttr displays the percentage of all NFS server calls that are requests to get file attributes (since the last sample)

Collector: NFSColl

page 84

NFSSLink displays the percentage of all NFS server calls made to create hard links (since the last sample)

Collector: NFSColl

page 84

NFSSLookUp displays the percentage of all NFS server calls made to look up directory paths (since the last sample)

Collector: NFSColl

page 84




Parameter Summary

NFSSMkDir displays the percentage of all NFS server calls made to create directories (since the last sample)

Collector: NFSColl

page 84

NFSSNull displays the percentage of NFS server calls that request no action other than acknowledgment (since the last sample)

Collector: NFSColl

page 84

NFSSRead displays the percentage of all NFS server calls made to read data from files (since the last sample)

Collector: NFSColl

page 84

NFSSReadDir displays the percentage of all NFS server calls made to read data directories (since the last sample)

Collector: NFSColl

page 84

NFSSReadLink displays the percentage of all NFS server calls made to read symbolic links (since the last sample)

Collector: NFSColl

page 84

NFSSRemove displays the percentage of NFS server calls made to remove files (since the last sample)

Collector: NFSColl

page 84

NFSSRename displays the percentage of all NFS server calls made to rename files (since the last sample)

Collector: NFSColl

page 84

NFSSRmDir displays the percentage of all NFS server calls made to remove directories (since the last sample)

Collector: NFSColl

page 84

NFSSRpcBadCall displays the percentage of all NFS RPC server requests rejected by the server RPC facility before the request could be passed to the kernel NFS service routines (since the last sample)

Collector: NFSColl

page 84

NFSSRpcBadLen displays the total number of server RPC calls that are truncated and have an invalid length (since the last sample)

Collector: NFSColl

page 84

NFSSRpcCall displays the total number of NFS server RPC calls (since the last sample)

Collector: NFSColl

page 84




Parameter Summary

NFSSRpcNullRecv displays the number of null RPC calls that the server received (since the last sample)

Collector: NFSColl

page 84

NFSSRpcXdrCall displays the total number of NFS server RPC calls whose headers could not be XDR-decoded (since the last sample)

This network problem occurs mostly on wide area networks (WANs).

Collector: NFSColl

page 84

NFSSSetAttr displays the percentage of all NFS server calls made to store file attributes (since the last sample)

Collector: NFSColl

page 84

NFSSSymLink displays the percentage of all NFS server calls made to create symbolic links (since the last sample)

Collector: NFSColl

page 84

NFSSWrite displays the percentage of all NFS server calls made to write files (since the last sample)

Collector: NFSColl

page 84

PATROLAGENT Application Class

PADeltaBetweenExecSecs displays the number of seconds between executions. This value is the RUNQ_DELTA variable

page 84

PAHistoryIndexSize displays the size of the PatrolAgent history index file in bytes page 84

PAOutstandingJobs displays the number of currently executing jobs on the PATROL Agent and the time that they were started

page 84

PATotalErrors displays the total number of errors detected by the PATROL Agent

page 84

PAUserErrors displays the total number of errors detected by the PATROL Agent

page 84

PAWorkRateExecsMin displays the number of instruction executions performed per minute by the PATROL Agent

page 84

PRINTER Application Class

PRNQLength displays the number of print jobs waiting in the print queue

Collector: PrinterColl

page 84

PROCCONT Application Class

groupMonitorDaemon collects data that is gathered and analyzed by the PROCPPStatus parameter

page 81

PROCPPStatus lists the status of monitored processes and host groups

Collector: groupMonitorDaemon

page 85




Parameter Summary

PROCESS Application Class

PROCAvgUsrProc displays the average number of processes per nonroot user

Collector: DCMColl or USRPROCColl

page 84

PROCExec displays the number of exec system calls per second

Collector: SARColl



page 84

PROCNoZombies displays the total number of zombie processes


page 84

PROCNumProcs displays the total number of active processes on the system


page 84

PROCProcWait displays the number of processes that are currently waiting for resources

Collector: DCMColl or VMColl

Platforms: AIX, Compaq Tru64 (Digital Unix, OSF/1), HP-UX, Solaris

Note: When using PSL collection, PATROL deactivates this parameter on AIX (32-bit) and Compaq Tru64 (Digital Unix, OSF/1).

page 85

PROCProcWaitInt displays the number of processes in an interruptible wait state

Collector: VMColl



page 85

PROCProcWaitUnint displays the number of processes in an uninterruptible wait state

Collector: VMColl



page 85




Parameter Summary

PROCTopProcs displays the processes (up to ten) using the highest percentage of CPU time during the sample period

Machines with multiple CPUs may show more than 100% utilization for a given process.

Collector: DCMColl or PSColl

Note: When using PSL collection, PATROL deactivates this parameter on AIX.

page 85

PROCUserProcs displays the total number of nonroot user processes


page 85

PROCPRES Application Class

PROCPPCPUPerc displays the percentage of CPU used by the selected process (calculated on the number of active CPUs in the system.

Collector: DCMColl

page 84

PROCPPCount displays the number of processes started with the same command-line string as the selected process

Collector: DCMColl

page 84

PROCPPCountCheck indicates whether the process count is within the acceptable range specified by the user

Collector: discovery

page 84

PROCPPMem displays the amount of virtual memory that the process is using

Collector: DCMColl

page 85

PROCPPOwnerCheck displays the results of a verification that a process is owned by an authorized user name

PATROL issues an alert if it discovers that the process is owned by an unauthorized user name.


page 85

PROCPPParentPID1 displays the results of a verification that the parent process ID (PPID) for a designated process is 1

Processes with a PPID of 1 are owned by the Unix scheduler, or init.


page 85




Parameter Summary

SCHEDULER Application Class

scheduler_daemon gathers the information that is displayed in the PATROL Scheduling Report

You can access the PATROL Scheduling Report by viewing the scheduler parameter.

page 85

scheduler displays the PATROL Scheduling Report

This report provides information about items in the schedule queue.

Collector: scheduler_daemon

page 85

SMP Application Class

SMPContextSwitch displays the number of CPU context switches

Collector: SMPColl

Platforms: Solaris


page 85

SMPCrossCalls displays the number of interprocessor cross-calls

Collector: SMPColl

Platforms: Solaris


page 85

SMPIdlePercent displays the percentage of time the CPU was idle

Collector: DCMColl

Platforms: All except Reliant and Sequent DYNIX/ptx

page 85

SMPInterrupts displays the number of processor interrupts

Collector: SMPColl

Platforms: Solaris


page 85




Parameter Summary

SMPIntThread displays the number of interrupts as threads, excluding clock interrupts

Collector: SMPColl

Platforms: Solaris


page 85

SMPInvContSwitch displays the number of processor involuntary context switches

Collector: SMPColl

Platforms: Solaris


page 85

SMPMajorFaults displays the number of major faults

Collector: SMPColl

Platforms: Solaris


page 85

SMPMinorFaults displays the number of minor faults

Collector: SMPColl

Platforms: Solaris


page 85

SMPRunQLen1Min displays the average number of processes in the CPU's run queue during the last minute

Collector: SMP discovery

Platforms: HP-UX


page 85




Parameter Summary

SMPRunQLen5Min displays the average number of processes in the CPU's run queue during the last 5 minutes


Platforms: HP-UX


page 85

SMPRunQLen15Min displays the average number of processes in the CPU's run queue during the last 15 minutes


Platforms: HP-UX


page 85

SMPSpinMutex displays the number of spins on mutexes, or locks that were not acquired on the first try

Collector: SMPColl

Platforms: Solaris


page 85

SMPSpinRdWr displays the number of reader and writer locks that were not acquired on the first try

Collector: SMPColl

Platforms: Solaris


page 85

SMPSystemCalls displays the number of system calls

Collector: SMPColl

Platforms: Solaris


page 86

SMPSystemPrcnt displays the amount of processor time spent on system activities

Collector: DCMColl

page 86




Parameter Summary

SMPThMigration displays the number of thread migrations to another processor

Collector: SMPColl

Platforms: Solaris


page 86

SMPUserPercent displays the amount of processor time spent on user-requested activities

Collector: DCMColl

page 86

SMPWaitPercent displays the percentage of time the processor spent waiting

Collector: DCMColl

page 86

SNMPHealth Application Class

SNMPH_diagnostics gathers and displays diagnostic information relating to the PATROL SNMP system

In addition to being displayed in the text parameter window, the diagnostic information is also written to the file, SNMPHealth.log in $PATROL_HOME/log.

page 86

SNMPH_monitorSubAgent monitors the subagent's status

If the subagent is running, PATROL sets its value to OK. If the subagent is not running, PATROL sets the value to ALARM.

page 86

SNMPH_startSubAgent uses the output of snmp_agent_config to determine whether the SNMP subagent is running

If the subagent is not running, PATROL issues the PSL command snmp_agent_start() to start the subagent.

page 86

SNMPH_testparm performs diagnostics on the PATROL SNMP system

Use it to test the automatic SNMP traps that are issued through the event management system when an event is generated. This parameter's test uses Standard Event 11, which is triggered in PATROL when a parameter's value falls within an alarm range. It uses Standard Event 9 when the parameter's value falls within the OK range after having been in the alarm range.

Collector: menu command

page 86




Parameter Summary

SWAP Application Class

SWPnPageSizeAvailSWP32PageSizeAvailSWP64PageSizeAvailSWP128PageSizeAvailSWP256PageSizeAvailSWP512PageSizeAvailSWP1024PageSizeAvailSWP2048PageSizeAvail

displays the number of swap pages available on the swap device

The page size is represented by the n in the parameter name and is measured in kilobytes (32, 64, 128, 256, 512, 1024, and 2048).

Collector: SWAP Discovery

page 86

SWPSwapFreeSpace displays the size of the available swap space




page 86

SWPSwapSize displays the size of a particular swap area




page 86

SWPSwapUsedPercent displays the percentage of swap space used for a particular swap area




page 86

SWPTotSwapFreeSpace displays the total amount of free swap space

Appears under the Summary instance only.

Collector: DCMColl, SWAP Discovery or SARColl

page 86

SWPTotSwapSize displays the size of the entire swap space

(On Solaris, this value includes the space used in /tmp.) Appears under the Summary instance only.

Collector: DCMColl or SWAP Discovery

page 86




Parameter Summary

SWPTotSwapUsedPercent displays the percentage of the total system-wide swap space in use of active user sessions on this machine (including root sessions)

Appears under the Summary instance only.

Collector: DCMColl, SWAPCtrl, or SWAP Discovery

page 86

USERS Application Class

USRNoSession displays the number of active user sessions on this machine (including root sessions)

Collector: DCMColl

page 86

USRNoUser displays the number of unique users that are currently logged on to the system, NOT the number of user sessions

Collector: DCMColl

page 86




Parameter Defaults

Parameter DefaultsTable 25 lists default values for parameters. Interpret the column headings as follows. Depending on the type of parameter, some information is not applicable.

Parameter specifies the parameter name

Active? specifies whether the parameter is active or inactive when discovered

Typespecifies whether the parameter is a Standard, Consumer, or Collector parameter

Alarm 1

specifies the thresholds for the first alarm

This information is not applicable to Collectors.

Alarm 2

specifies the thresholds for the second alarm

This information is not applicable to Collectors.

Scheduling specifies the time interval in the poll cycle

Icon specifies whether the icon is a graph, gauge, or text box

Unitsspecifies the type of unit in which the parameter output is expressed, such as a percentage, a number, or bytes

History Level specifies the length of time that history is retained

See Also Pagespecifies other pages in this chapter where you can find more information about the parameter

Table 25 PATROL KM for Unix and Linux Parameter Defaults (Part 1 of 7)

Parameter Act

ive?

Type

Ala

rm1

Ala

rm2

Sche

dulin

g

Icon

Uni

ts

See

Als

oBlockSize y standard und. und. 0 none NA page 50

BootTime y standard und. und. 23:59:59 none NA page 50

ChangeDiskLabel y collector und. und. 10 min none NA page 56

CollectorStatus y collector 1 to 1 2 to 2 1 min none NA page 51

CollectorStatusText y collector und. und. NA none NA page 51

CPARMCollector y collector und. und. 30 sec none NA page 52

CPARMResult y consumer 1 2 NA stoplight NA page 52

CPARMExpression y consumer und. und. NA text NA page 52

CPARMGeneratedCodeText y consumer und. und. NA text NA page 52

CPUCollStatus y consumer und. und. 3 min graph DCM or PSL page 53

CPUCtrl y standard und. und. 1 min none NA page 53

CPUCpuUtil y consumer 90 to 95 95 to 100 NA graph percent page 52

CPUIdleTime y consumer und. und. NA graph percent page 52

CPUInt y consumer und. und. NA graph interrupts page 52

CPULoad y consumer und. und. NA graph load page 52

CPUProcSwch y consumer und. und. NA graph switches page 52


Parameter Defaults

CPURunQSize y consumer und. und. NA graph processes page 52

CPUSysTime y consumer 90 to 95 95 to 100 NA graph percent page 53

CPUUserTime y consumer 90 to 95 95 to 100 NA graph percent page 53

CPUWio y consumer und. und. NA graph percent page 53

DCMColl y collector und. und. 1 min none NA page 53

DCMMessages y consumer und. und. 3 min text none page 53

DCMMonitor y collector NA NA 1 min none NA page 54

DCMStatus y consumer und. und. NA graph NA page 54

DCMUpdateCount y consumer und. und. NA graph values sent page 54

DCMUpdateTime y consumer und. und. NA graph seconds page 54

DFBlockSize y standard und. und. 0 none NA page 50

DFColl y collector und. und. 2 min none NA page 54

DiskCollStatus y consumer und. und. 3 min graph DCM or PSL page 54

DISKCtrl y standard NA NA 1 min none NA page 54

DSKAvgQueue y consumer und. und. NA graph requests page 56

DSKAvgServ y consumer und. und. NA graph milliseconds page 56

DSKAvgWait y consumer und. und. none graph milliseconds page 56

DSKBps y consumer und. und. none graph 1-KB blocks page 56

DSKMsps y consumer und. und. none graph milliseconds page 56

DSKPercentBusy y consumer und. und. none gauge percent page 57

DSKRead y consumer und. und. none graph kilobytes page 57

DSKReadWrite y consumer und. und. none graph pages per second

page 57

DSKSps y consumer und. und. none graph seeks page 57

DSKTps y consumer und. und. none graph transfers page 57

DSKWrite y consumer und. und. none graph kilobytes page 57

FSAvailableSpace y consumer und. und. none graph kilobytes page 58

FSAvailableSpaceMB y consumer und. und. none graph megabytes page 58

FSCapacity y consumer 0 to 0 0 to 0 none graph percent page 58

FSFreeInodes y consumer und. und. none graph i-nodes page 58

FSInodeUsedPercent y consumer und. und. none graph percent page 58

FSMountStatus y consumer 1 to 1 2 to 2 2 min boolean mount status page 58

FSUsedSpace y consumer und. und. none graph megabytes page 58

Get_700_nproc y standard und. und. none text NA page 50

groupMonitorDaemon y collector NA NA 10 min none NA page 71

HAAGColl y collector NA NA 1 min none NA page 51

HAAGCPUUsage y consumer und. und. none stoplight NA page 58

HAAGFilesystemUsage y consumer und. und. none stoplight NA page 58

HAAGHealthSummary y consumer und. und. none text NA page 58

HAAGSwapUsage y consumer und. und. none stoplight NA page 58

KernelCollStatus y consumer und. und. 3 min graph DCM or PSL page 54

KernelInfo y standard und. und. 23:59:59 none NA page 50

KERDirBlk y consumer und. und. none graph reads page 59

KERFileUsedPercent y consumer 90 to 95 95 to 100 none graph percent page 59


Parameter Act

ive?

Type

Ala

rm1

Ala

rm2

Sche

dulin

g

Icon

Uni

ts

See

Als

o


Parameter Defaults

KERIGet y consumer und. und. none graph files page 59

KERINodeUsedPercent y consumer 90 to 100 und. none graph percent page 59

KERLgAlloc y consumer und. und. none graph kilobytes page 59

KERLgFail y consumer und. und. none graph requests page 59

KERLgMem y consumer und. und. none graph kilobytes page 60

KERLockUsedPercent y consumer 90 to 95 95 to 100 none gauge percent page 60

KERMsg y consumer und. und. none graph messages page 60

KERMsgNumQueUsedPercent y consumer 90 to 95 95 to 100 none graph percent page 60

KERMsgNumUsedPercent y consumer 90 to 95 95 to 100 none graph percent page 60

KERNameI y consumer und. und. none graph conversion page 60

KERNELCtrl y standard und. und. 1 min none NA page 54

KEROvzAlloc y consumer und. und. none graph kilobytes page 61

KEROvzFail y consumer und. und. none graph requests page 61

KERProcUsedPercent y consumer 90 to 95 95 to 100 none graph percent page 61

KERSemNumSetUsedPercent y consumer 90 to 95 95 to 100 none graph percent page 61

KERSemNumUsedPercent y consumer 90 to 95 95 to 100 none graph percent page 61

KERSemOps y consumer 80 to 100 und. none graph sem. ops. page 61

KERShmNumUsedPercent y consumer 90 to 95 95 to 100 none graph percent page 61

KERSmlAlloc y consumer und. und. none graph kilobytes page 62

KERSmlFail y consumer und. und. none graph requests page 62

KERSmlMem y consumer und. und. none graph kilobytes page 62

KERSysCall y consumer und. und. none graph sys calls page 62

LPSpoolDirectory y standard und. und. 23:59:59 none NA page 50

MaxConfigValLen y standard und. und. 10 min (one time)

none NA page 50

MEMActiveVirPage y consumer und. und. none graph pages page 62

MEMAddrTransFault y consumer und. und. none graph pages page 62

MEMBRead y consumer und. und. none graph reads/sec page 62

MEMBWrt y consumer und. und. none graph writes/sec page 63

MemCollStatus y consumer und. und. 3 min graph DCM or PSL page 54

MEMCow y consumer und. und. none graph number of 1-Kb pages

page 63

MEMFreeMem y consumer 0 to 100 100 to 200 none graph kilobytes page 63

MEMLRead y consumer und. und. none graph reads page 63

MEMLWrt y consumer und. und. none graph writes/sec page 63

MEMORYCtrl y standard und. und. 1 min none NA page 55

MEMPageAnticipated y consumer und. und. none graph number of 1-Kb pages

page 63

MEMPageFreed y consumer 5 to 25 25 to 100 none graph pages page 64

MEMPageIn y consumer und. und. none graph pages page 64

MEMPageOut y consumer 10 to 15 15 to 100 none graph pages page 64

MEMPageScanned y consumer und. und. none graph pages page 64

MEMPFault y consumer und. und. none graph page faults page 64

MEMPgFill y consumer und. und. none graph pages page 64

MEMPRead y consumer und. und. none graph reads/sec page 65


Parameter Act

ive?

Type

Ala

rm1

Ala

rm2

Sche

dulin

g

Icon

Uni

ts

See

Als

o


Parameter Defaults

MEMPWrt y consumer und. und. none graph writes/sec page 65

MEMRCache y consumer 1 to 10 10 to 20 none graph percent page 65

MEMWCache y consumer 1 to 10 10 to 20 none graph percent page 65

MEMWire y consumer und. und. none graph number of 1-KB pages

page 65

MEMZero y consumer und. und. none graph number of 1-KB pages

page 66

NETColl n collector und. und. 5 min none NA page 55

NETCollisionPrc y consumer und. und. none graph percent page 66

NETInErrPrc y consumer und. und. none graph percent page 66

NETOutErrPrc y consumer und. und. none graph percent page 66

NETPacketsIn y consumer und. und. none graph packets page 66

NETPacketsOut y consumer und. und. none graph packets page 66

NETPseudoAddresses n consumer und. und. none text NA page 66

NFSCBadCall y consumer und. und. none graph percent page 66

NFSCCall y consumer und. und. none graph calls page 66

NFSCCreate y consumer 25 to 50 50 to 100 none graph percent page 66

NFSCFsStat y consumer und. und. none graph percent page 67

NFSCGetAttr y consumer und. und. none graph percent page 67

NFSCLink y consumer und. und. none graph percent page 67

NFSCLookUp y consumer 50 to 60 60 to 100 none graph percent page 67

NFSCMkDir y consumer und. und. none graph percent page 67

NFSCNclGet y consumer und. und. none graph nfs call page 67

NFSCNclSleep y consumer und. und. none graph calls page 67

NFSCNull y consumer 2 to 50 50 to 100 none graph percent page 67

NFSColl y collector und. und. 3 min none NA page 51

NFSCRead y consumer und. und. none graph calls page 67

NFSCReadDir y consumer 18 to 30 30 to 100 none graph percent page 67

NFSCReadLink y consumer und. und. none graph percent page 67

NFSCRemove y consumer 25 to 50 50 to 100 none graph percent page 68

NFSCRename y consumer und. und. none graph percent page 68

NFSCRmDir y consumer und. und. none graph percent page 68

NFSCRpcBadCall y consumer 40 to 50 50 to 100 none graph percent page 68

NFSCRpcBadXid y consumer und. und. none graph percent page 68

NFSCRpcCall y consumer und. und. none graph calls page 68

NFSCRpcNewCred y consumer und. und. none graph calls page 68

NFSCRpcNullRecv y consumer und. und. none graph messages page 68

NFSCRpcRetrans y consumer und. und. none graph calls page 68

NFSCRpcTimeOut y consumer 20 to 50 50 to 100 none graph percent page 68

NFSCRpcWait y consumer und. und. none graph calls page 69

NFSCSetAttr y consumer und. und. none graph percent page 69

NFSCSymLink y consumer 11 to 50 50 to 100 none graph percent page 69

NFSCWrite y consumer 50 to 75 75 to 100 none graph calls page 69

NFSSBadCall y consumer 40 to 50 50 to 100 none graph percent page 69


Parameter Act

ive?

Type

Ala

rm1

Ala

rm2

Sche

dulin

g

Icon

Uni

ts

See

Als

o


Parameter Defaults

NFSSCreate y consumer 25 to 50 50 to 100 none graph percent page 69

NFSSFsStat y consumer 50 to 75 75 to 100 none graph percent page 69

NFSSGetAttr y consumer 75 to 100 und. none graph percent page 69

NFSSCall y consumer und. und. none graph calls page 69

NFSSLink y consumer und. und. none graph percent page 69

NFSSLookUp y consumer 50 to 60 60 to 100 none graph percent page 69

NFSSMkDir y consumer und. und. none graph percent page 70

NFSSNull y consumer 2 to 50 50 to 100 none graph percent page 70

NFSSRead y consumer und. und. none graph percent page 70

NFSSReadDir y consumer 18 to 30 30 to 100 none graph percent page 70

NFSSReadLink y consumer 40 to 50 50 to 100 none graph percent page 70

NFSSRemove y consumer 25 to 50 50 to 100 none graph percent page 70

NFSSRename y consumer und. und. none graph percent page 70

NFSSRmDir y consumer und. und. none graph percent page 70

NFSSRpcBadCall y consumer 40 to 50 50 to 100 none graph percent page 70

NFSSRpcBadLen y consumer und. und. none graph calls page 70

NFSSRpcCall y consumer und. und. none graph calls page 70

NFSSRpcNullRecv y consumer und. und. none graph calls page 71

NFSSRpcXdrCall y consumer und. und. none graph calls page 71

NFSSSetAttr y consumer und. und. none graph percent page 71

NFSSSymLink y consumer 25 to 50 50 to 100 none graph percent page 71

NFSSWrite y consumer 50 to 75 75 to 100 none graph percent page 71

OSName y standard und. und. 23:59:59 none NA page 50

PADeltaBetweenExecSecs y standard und und. 15 min graph seconds page 71

PageSize y standard und. und. 0 none NA page 50

PAHistoryIndexSize y standard 900000 to 950000

950000 to 999999

10 min graph NA page 71

PAOutstandingJobs y standard und. und. 5 min graph jobs page 71

PATotalErrors y standard und. und. 45 min gauge errors page 71

PAUserErrors y standard und. und. 30 min gauge errors page 71

PAWorkRateExecMin y standard 20 to 25 25 to 60 2 min graph execs page 71

PrinterColl n collector und. und. 2 min none NA page 51

PRNQLength y consumer 30 to 100 und. none gauge jobs page 71

PROCAvgUsrProc y consumer und. und. none graph processes page 72

PROCColl y collector und. und. 5 min none NA page 51

ProcessCollStatus y consumer 1 to 2 und. 3 min graph DCM or PSL page 55

PROCExec y consumer und. und. none gauge calls page 72

PROCESSCtrl y standard und. und. 1 min none NA page 55

PROCNoZombies y consumer und. und. none graph processes page 72

PROCNumProcs y consumer und. und. none graph processes page 72

PROCPPCount y consumer und. und. NA graph number of processes

page 73

PROCPPCountCheck y consumer 1 to 1 2 to 2 NA stoplight NA page 73

PROCPPCPUPerc y consumer und. und. NA graph percentage page 73


Parameter Act

ive?

Type

Ala

rm1

Ala

rm2

Sche

dulin

g

Icon

Uni

ts

See

Als

o


Parameter Defaults

PROCPPMem y consumer und. und. NA graph kilobytes page 73

PROCPPOwnerCheck y consumer 1-1 2-2 NA stoplight NA page 73

PROCPPParentPID1 y consumer 1-1 2-2 NA stoplight NA page 73

PROCPPStatus y consumer und. und. none text NA page 71

PROCProcWait y consumer und. und. none graph processes page 72

PROCProcWaitInt y consumer und. und. none graph processes page 72

PROCProcWaitUnint y consumer und. und. none graph processes page 72

PROCTopProcs y consumer und. und. none text NA page 73

PROCUserProcs y consumer und. und. none graph processes page 73

PSColl y collector und. und. 1 min none NA page 51

SARColl y collector und. und. 1 min none NA page 51

SetupClearText y standard und. und. 10 min (once)

none NA page 51

scheduler y consumer und. und. none text NA page 74

scheduler_daemon y collector und. und. 1 hrs none NA page 74

SMPColl y collector und. und. 10 min none NA page 51

SMPContextSwitch y consumer und. und. none graph number of switches per second

page 74

SMPCrossCalls y consumer und. und. none graph number of events per second

page 74

SMPIdlePercent y consumer und. und. none gauge percent page 74

SMPInterrupts y consumer und. und. none graph number of interrupts per second

page 74

SMPIntThread y consumer und. und. none graph number of interrupts per second

page 75

SMPInvContSwitch y consumer und. und. none graph number of switches per second

page 75

SMPMajorFaults y consumer und. und. none graph number of major faults per second

page 75

SMPMinorFaults y consumer und. und. none graph number of minor faults per second

page 75

SMPRunQLen1Min y consumer und. und. none graph number of processes per minute

page 75

SMPRunQLen5Min y consumer und. und. none graph number of processes per 5 minutes

page 76

SMPRunQLen15Min y consumer und. und. none graph number of processes per 15 minutes

page 76

SMPSpinMutex y consumer und. und. none graph number of events per second

page 76

SMPSpinRdWr y consumer und. und. none graph number of events per second

page 76


Parameter Act

ive?

Type

Ala

rm1

Ala

rm2

Sche

dulin

g

Icon

Uni

ts

See

Als

o


Parameter Defaults

SMPSystemCalls y consumer und. und. none graph number of system calls per second

page 76

SMPSystemPrcnt y consumer und. und. none gauge percent page 76

SMPThMigration y consumer und. und. none graph number of migrations per second

page 77

SMPUserPercent y consumer und. und. none gauge percent page 77

SMPWaitPercent n consumer und. und. none gauge percent page 77

SNMPH_diagnostics y standard und. und. 10 min text NA page 77

SNMPH_monitorSubAgen y standard 0 to 0 und. 1 min stoplight NA page 77

SNMPH_startSubAgent y standard und. und. 1 min none NA page 77

SNMPH_testparm y consumer 1 to 1 2 to 2 none stoplight NA page 77

SNMPStart y standard und. und. 30 min none NA page 51

SwapCollStatus y consumer und. und. 1 min graph DCM or PSL page 55

SWAPCtrl y standard und. und. 1 min none NA page 55

SWP1024PageSizeAvail y consumer und. und. none graph pages page 78







SWPSwapFreeSpace y consumer und. und. none graph number of 1-KB blocks

page 78

SWPSwapSize y consumer und. und. none graph number of 1-KB blocks

page 78

SWPSwapUsedPercent y consumer und. und. none gauge percent page 78

SWPTotSwapFreeSpace y consumer und. und. none graph 1-KB blocks page 78

SWPTotSwapSize y consumer und. und. none graph 1-KB blocks page 78

SWPTotSwapUsedPercent y consumer 90 to 95 95 to 100 none gauge percent page 79

TerminalEmulator y standard und. und. NA none NA page 51

UPTColl y collector und. und. 1 min none NA page 52

UserCollStatus y consumer und. und. 3 min graph DCM or PSL page 55

USERSCtrl y standard und. und. 1 min none NA page 55

USRNoSession y consumer und. und. none graph sessions page 79

USRNoUser y consumer und. und. none graph users page 79

USRPROCColl y collector und. und. 5 min none NA page 52

VMColl y collector und. und. 45 sec none NA page 52


Parameter Act

ive?

Type

Ala

rm1

Ala

rm2

Sche

dulin

g

Icon

Uni

ts

See

Als

o


C h a p t e r 4
4 Managing Data Collection
On some platforms, the PATROL Knowledge Module for Unix and Linux product gives you the ability to select the method PATROL uses to gather data for the PATROL KM for Unix and Linux. The following sections appear in this chapter.

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Object Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

COLLECTORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88DCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

DCM Collection Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Data Collection Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Collector Parameters for DCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91-Ctrl and -Coll Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92DCM Collection Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

PSL Collection Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Collector Parameters for COLLECTORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95-Coll Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96PSL Collection Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Managing Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Changing Data Collection Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Activating an Inactive Application Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Activating an Inactive Collector Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Significant Events Related to Data Collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101


Introduction

IntroductionTwo data collection methods are available to the PATROL Knowledge Module for Unix and Linux. The two methods use separate data collection mechanisms and are controlled by separate application classes. Table 26 lists the collection methods and their application classes.

Object HierarchiesIn PATROL, collector parameters are not visually represented by icons. However, the collector application classes are. When their respective data collection methods are employed, PATROL displays the following application class object hierarchies.

COLLECTORS

The COLLECTORS application class governs the PSL data collection method. It does not contain any consumer parameters. When the PSL Collection method is employed, PATROL creates the application class in the UNIX OS container (Figure 2).

Figure 2 COLLECTORS Application Object Hierarchy

Table 26 Data Collection Methods and Associated Application Classes

Method Application Class

DCM Collection Method DCM Application Class

PSL Collection Method COLLECTORS Application Class

OS container

Application class

COLLECTORS

UNIX OS


Object Hierarchies

DCM

The DCM application class governs the DCM data collection method. The DCM application class contains several parameters that monitor the status of the DCM process as shown in the application class hierarchy represented by Figure 3.

Figure 3 DCM Application Object Hierarchy


DCM Collection Method

DCM Collection MethodThe DCM collection method uses the PATROL Perform collection model for gathering and presenting application information. In this model, the Perform Agent makes calls to the operating system to collect information about the system and stores that information in its own data structures. Special standard parameters, designated by -Ctrl suffix, retrieve the data from the Perform data structures and transform it into the PATROL format. Consumer parameters, written in PATROL Script Language (PSL), retrieve the transformed information from these parameters and present this information in a variety of formats (text, gauges, graphs, and so on) to the PATROL Console.

PATROL also uses certain PSL collector parameters, designated by -Coll suffix, to gather information that the Perform Agent does not provide.

This section describes

■ which parameters (-Ctrl and -Coll) are active during DCM data collection■ which parameters supply information to which application classes■ which parameters are not supported by the DCM data collection method



Data Collection Architecture

PATROL for Unix uses two types of data collection:

■ data collectors that use standard Unix utilities■ data collectors that read from the kernel

Data collection that uses standard Unix utilities is called PATROL Script Language (PSL) data collection. Data collection that reads directly from the kernel is gathered by the PATROL Perform Agent kernel-reading data collector as shown in Figure 4.

The PATROL Perform Agent is not available on all platforms. See the PATROL for Unix Getting Started guide for a list of platforms that support the PATROL Perform Agent.

Figure 4 Data Collection Architecture Using PATROL Perform Collector

Figure 4 depicts how the PATROL Perform collector fits into the data collection architecture of PATROL. The PATROL Perform collector collects the data and writes it to shared memory. The Data Collection Manager (DCM) of the PATROL KM for Unix and Linux is the control point and data interface between the PATROL Perform collector and the PATROL Agent.

Collector Parameters for DCM

When the DCM Collection Method is selected, PATROL instantiates the following parameters under the DCM application class. Use this information to customize your PATROL installation to gather only the data you need.

PATROL Agent

PSL KM

SharedMemory

Data CollectionManager(DCM)

Unix-Named Pipe

Data Path

PSL popen() control pipe

PATROL PerformCollector

(FIFO)



-Ctrl and -Coll Parameters

The DCM data collection method gathers data using both the Perform Agent and the PATROL PSL collectors. Ultimately, consumer parameters display the information gathered by both types of collection. However, understanding how each type of collector gathers data and which type of collector feeds a consumer helps to understand apparent discrepancies in system statistics. These discrepancies may be due to poorly managed discovery cycles or other performance-tuning issues.

-Ctrl Suffix

Parameters with -Ctrl suffix are standard parameters that interact with the Perform Agent through the DCM application. These parameters control the poll time and status (active or inactive) for data collection of application parameter data.

-Coll Suffix

Parameters with the -Coll suffix are collector parameters that interact directly with Unix utilities. This type of parameter issues the system calls and receives the data without having to interact with another data-gathering application.

Table 27 Collection Parameters Used By the DCM Collection Method

Collector PSL / Perform Active / Inactive Consumer Application See Also

CPUCtrl Perform Active CPU, SMP 53

DCMColl PSL Active DCM 53

DFColl PSL Active FILESYSTEM 51

DISKCtrl Perform Active DISK 54

HAAGColl PSL Active HEALTH_AT_A_GLANCE 51

KERNELCtrl Perform Active KERNEL 54

MEMORYCtrl Perform Active MEMORY 55

NETColl PSL Inactive NETWORK 55

NFSColl PSL Active NFS 55

PRINTERColl PSL Inactive PRINTER 55

PROCESSCtrl Perform Active PROCESS 55

SWAPCtrl Perform Active SWAP 55

UPTColl PSL Active CPU 55

USERSCtrl Perform Active USERS 55



DCM Collection Exceptions

When you use the DCM data collection method, PATROL deactivates the parameters listed below on the specified platforms. When a parameter is deactivated, PATROL does one of two things:

■ does not create the parameter

■ does not update the parameter (if the parameter was created by using the PSL collection method).

Restarting PATROL after changing the collection method ensures that parameters that are not updated by the DCM collection method are destroyed.

Table 28 DCM Deactivated Parameters and their Platforms (Part 1 of 2)

Deactivated Parameters Platforms

CPU

CPUInt All

CPUProcSwch All

KERNEL

KERFileUsedPercent All except HP-UX

KERInodeUsedPercent All except Compaq Tru64 and HP-UX

KERProcUsedPercent All except Compaq Tru64 and HP-UX

KERMsg All except AIX and Compaq Tru64

KERSemOps All except AIX and Compaq Tru64

KERDirBlk All

KERNameI All

KERIGet All

MEMORY

MEMActiveVirPage All

MEMAddrTransFault All

MEMBRead All

MEMBWrt All

MEMCow All

MEMPageAnticipated All

MEMPageFreed All

MEMRCache All

MEMWire All

MEMZero All



PROCESS

PROCExec All

PROCProcWaitInt All

PROCProcWaitUnint All

SMP

SMPContextSwitch All

SMPCrossCalls All

SMPInterrupts All

SMPIntThread All

SMPInvContSwitch All

SMPMajorFaults All

SMPMinorFaults All

SMPRunQLen1Min All

SMPRunQLen5Min All

SMPRunQLen15Min All

SMPSpinMutex All

SMPSpinRdWr All

SMPSystemCalls All

SMPThMigration All

SWAP

SWPSwapFreeSpace All

SWPSwapSize All

SWPSwapUsedPercent All

Table 28 DCM Deactivated Parameters and their Platforms (Part 2 of 2)



PSL Collection Method

PSL Collection MethodThe PSL collection method uses the PATROL consumer-collector model for gathering and presenting application information. In this model, collector parameters, written in PSL, make calls to Unix utilities to collect information about the system. Consumer parameters, also written in PSL, retrieve the information from the collector parameters and present this information in a variety of formats (text, gauges, graphs, and so on) to the PATROL Console.

This section describes

■ which collector parameters are active during PSL data collection■ which collector parameters supply information to which application classes■ which parameters are not supported by the PSL data collection method

Collector Parameters for COLLECTORS

When the PSL Collection Method is selected, PATROL instantiates the following parameters under the COLLECTORS application class. Use this information to customize your PATROL installation to gather only the data you need.

Table 29 Collection Parameters Used By the PSL Collection Method

Collector Active / Inactive Consumer Application See Also

CollectorStatus Active COLLECTORS 51

CollectorStatusText Active COLLECTORS 51

DFColl Active FILESYSTEM 51

HAAGColl Active HEALTH_AT_A_GLANCE 51

NETColl Inactive NETWORK 51

NFSColl Active NFS 51

PRINTERColl Inactive PRINTER 51

PROCColl Active PROCESS 51

PSColl Active PROCESS 51

SARColl Active CPU, KERNEL, MEMORY, PROCESS, SWAP 51

SMPColl Active SMP 51

UPTColl Active CPU 52

USRPROCColl Active PROCESS, USER 52

VMColl Active CPU, KERNEL, MEMORY, PROCESS 52



-Coll Parameters

The PSL data collection method gathers data using only the PATROL PSL collector parameters. The parameters with -Coll suffix are collector parameters that interact directly with Unix utilities. This type of parameter issues the system calls and receives the data without having to interact with another data-gathering application.

PSL Collection Exceptions

When you use the PSL collection method, PATROL deactivates the parameters listed below on the specified platforms. When a parameter is deactivated, PATROL does one of two things:

■ does not create the parameter

■ does not update the parameter (if the parameter was created by using the DCM collection method)

Restarting PATROL after changing the collection method ensures that parameters that are not updated by the PSL collection method are deleted.

Table 30 Collector Deactivated Parameters and their Platforms (Part 1 of 2)


CPU

CPUInt AIX

CPUWio Compaq Tru64 and Solaris

DISK

DISKDSKAvgQueue Compaq Tru64

DSKAvgServ AIX and Compaq Tru64

DSKPercentBusy Compaq Tru64

DSKRead Solaris

DSKReadWrite Compaq Tru64

DSKSps Compaq Tru64

DSKWrite Solaris

KERNEL

KERFileUsedPercent Compaq Tru64

KERInodeUsedPercent Compaq Tru64

KERMsg Solaris

KERProcUsedPercent Solaris



KERSemOps Solaris

MEMORY

MEMActiveVirPage AIX (32-bit)

MEMFreeMem AIX (32-bit) and Solaris

MEMLRead Compaq Tru64 and Solaris

MEMLWrt Compaq Tru64 and Solaris

MEMPageFreed AIX (32-bit)

MEMPageIn AIX (32-bit)

MEMPageOut AIX (32-bit)

MEMPageScanned Compaq Tru64

MEMPFault AIX, Compaq Tru64, HP-UX, Solaris

MEMPRead Compaq Tru64 and Solaris

MEMPWrt Compaq Tru64 and Solaris

MEMWCache Compaq Tru64 and Solaris

PROCESS

PROCProcWait AIX (32-bit) and Compaq Tru64

PROCTopProcs AIX

Table 30 Collector Deactivated Parameters and their Platforms (Part 2 of 2)



Managing Collection

Managing CollectionThe DCM application class and its components and the COLLECTORS application class are both installed in a standard PATROL installation. By default, PATROL attempts to use the DCM data collection method associated with the DCM KM. If DCM is either not available or not supported on the managed system’s platform, PATROL uses the PSL collection method associated with the COLLECTORS KM.

The data collection management tasks are described in detail on the following pages:

Changing Data Collection Methods

This task describes how to change the data collection method for the PATROL KM for Unix and Linux. See the PATROL for Unix Getting Started guide for more information about the data collection methods that are supported on each platform.

Before You Begin

Determine the collection method that you are currently using by opening the UNIX OS container. If the DCM icon is visible, PATROL is using the DCM data collection method. If the COLLECTORS icon is visible, PATROL is using the PSL data collection method.

To Change the Data Collection Method

To change the collection method, perform the following procedure:

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

2 Select Knowledge Module Admin => Toggle PSL/DCM Collection.

PATROL displays a confirmation dialog box (Figure 5 on page 99).

Task Page

“Changing Data Collection Methods” 98

“Activating an Inactive Application Class” 100

“Activating an Inactive Collector Parameter” 100

“Significant Events Related to Data Collection” 101


Managing Collection

Figure 5 PSL Collection Confirmation Dialog Box

3 Click Yes to confirm.

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

4 Access the Computer application menu as described in “Accessing KM Commands and InfoBoxes” on page 402.

5 Select Update Connection.

PATROL reconnects to the Agent and displays the parameters supported by the chosen data collection method.

NOTE Neither collection method gathers data for every parameter available in the KM. For a list of parameters that are deactivated for a specific collection method, see “DCM Collection Exceptions” on page 93 or “PSL Collection Exceptions” on page 96.

NOTE Steps 4 and 5 are optional. PATROL will automatically reconnect to the Agent. However, due to various discovery intervals, impatient users can reconnect faster by using the menu command than by using the automated procedure.


Managing Collection

Activating an Inactive Application Class

This task describes how to turn on the data collection mechanism for an application class. It is necessary because some application classes are installed in an inactive state. To collect data for those application classes, you must activate the application class and its corresponding collector parameters.

Before You Begin

You must activate the collector parameter and its parent application class. For information on how to activate a collector parameter, see “Activating an Inactive Collector Parameter” on page 100.

To Start Collecting Data for an Application Class

1 Access the application class properties as described in “Accessing KM Commands and InfoBoxes” on page 402.

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.

Activating an Inactive Collector Parameter

This task describes how to turn on a collector parameter. It is necessary because some application classes are installed in an inactive state. To collect data for those application classes, you must activate the application class and its corresponding collector parameters.

Before You Begin

You must activate the application class and collector parameter. For information on how to activate an application class, “Activating an Inactive Application Class” on page 100.


Managing Collection

To Start a Collector Parameter

1 Access the application class properties as described in “Accessing KM Commands and InfoBoxes” on page 402.

2 Check the Active checkbox.

3 Click OK.

PATROL closes the dialog box, runs discovery for this parameter, and gathers the associated data.

Significant Events Related to Data Collection

PATROL for Unix uses the DCM collector as the default means to gather information for application classes and collector processes.

The following events are generated by conditions that affect a change in data collection. Note that when PATROL for Unix switches to PSL data collection, Process Presence functionality does not exist. Look for these events to alert you to a change in data collection methods and the fact that the agent may not be collecting the type of data you want.

Switch to Manual PCM Data Collection

The following event is logged when you manually switch to PSL data collection.

Type of Event INFORMATION

Severity 3

Event Class UNIXToggleCollection

Description This agent is now using classic PSL methods to collect data. This change was initiated from a Console in developer mode by @developer.


Managing Collection

Toggle the DCM/PSL Collection Menu Command to DCM

The following event is logged when you select the DCM/PSL toggle command to switch to DCM data collection.

DCM Binary Dies

One of the following events will be logged when the DCM binary dies.

DCM Fails over to PSL

The following event is logged when DCM fails over to PSL data collection.


Severity 3

Event Class UNIXToggleCollection

Description This agent is now using the PERFORM collector to collect data. This change was initiated from a Console in developer mode by @developer.

Type of Event WARNING

Severity 3

Event Class 41

Description DcmCol.psl: dcm died 1 times.

Type of Event ALARM

Severity 4

Event Class 11

Description Alarm #2 of global parameter 'DCMStatus' triggered on 'DCM.DCM'. 2 <= 2.00 <= 2.

Type of Event WARNING

Severity 3

Event Class 41

Description DcmCol.psl: Switching to PSL data collection. DcmCol.psl: Event text: DcmCol.psl: Reason for switch to PSL: DCM terminated count exceeds maximum allowed.


Managing Collection

Deactivate SMP Application on a Single-CPU System

The following event is logged when the SMP application is deactivated on a single-CPU system. (This event only seems to occur when PSL collection is in effect.)

Toggle PSL/DCM Collection and Reinitialize the Patrol Agent

The following event is logged after using the PSL/DCM toggle command and reinitializing the PATROL agent.

Defined Process Presence Instance Does Not Exist for pconfig Variable

If the pconfig variable, /PUK/PROCPRES/attach_ps_list", exists and is set to TRUE, the following event is generated when the defined process presence instance does not exist. (This condition is based on a recovery action defined for PROCPPCountCheck parameter.) The following event is logged after using the PSL/DCM toggle and re initializing the PATROL agent.


Severity 3

Event Class 41

Description SMP: Single CPU system, deactivating.


Severity 3

Event Class 0

Description Event (0,StartStop) not found in catalog: snowcap 1 0.


Severity 3

Event Class 41

Description This event contains a list of top ten processes and monitored processes. It is generated by the recovery action of the PPROCPCountCheck parameter due to an alert condition.


Managing Collection


C h a p t e r 5
5 Monitoring CPU and Kernel
The PATROL Knowledge Module for Unix and Linux gives you the ability to monitor the CPU and kernel of a system. The following sections appear in this chapter.

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Object Hierarchy for CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106CPU and Multiple CPUs (SMP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Viewing CPU Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Viewing CPU Statistics on Interrupts, Switches, and Waits . . . . . . . . . . . . . . . . . 109Viewing Statistics on CPU Run Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Viewing Statistics on Multiple CPUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Object Hierarchy for KERNEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111KERNEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Viewing the Kernel Build Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Viewing Kernel Memory Allocation Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Viewing Kernel I-node Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Viewing Kernel System Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115


Introduction

IntroductionThe PATROL Knowledge Module for Unix and Linux monitors processors through two applications: CPU and SMP. It monitors the kernel through one: KERNEL.

■ The CPU application monitors such processor statistics as

— percentage of overall CPU utilization— percentage of CPU idle time— percentage of CPU time spent on user activities— percentage of CPU time spent on system activities— percentage of time spent waiting on input and output— number of context switches per second— number of non-VME device interrupts— number of pages in and out per second— number of pages scanned per second— number of processes in the run queue

■ The SMP application provides basic CPU utilization statistics for multiple processors on a machine.

■ The KERNEL application provides information such as

— Kernel Memory Allocation (KMA) statistics for small, large, and oversized memory requests

— i-node usage— kernel usage of system resources

Object Hierarchy for CPUThe CPU application class contains parameters on requests made to the CPU, the size of the CPU run queue, the amount of time the CPU is idle, CPU time consumed by the system, CPU time consumed per user, and other statistics. If the system has multiple CPUs, PATROL creates an SMP application instance for each processor. Each instance contains parameters on processor usage.

Figure 6 on page 107 illustrates the basic hierarchy but does not necessarily display all instances and parameters.


Object Hierarchy for CPU

Figure 6 CPU Application Object Hierarchy

OS container

Application class

Parameters

Application class

Parameters

Instances

UNIX OS


CPU and Multiple CPUs (SMP)

CPU and Multiple CPUs (SMP)The CPU application class monitors various aspects of the CPU. This application class does not provide any menu commands because it automatically detects and monitors the CPU or multiple CPUs. It does gather and store a number of vital statistics in the CPU parameters.

The CPU tasks on how to access information stored in parameters are described in detail on the following pages:

Viewing CPU Utilization

This task describes how to view what percentage of the CPU is being consumed across the system, is in user mode, and is idle.

To View the CPU Utilization Statistics

1 Access the CPU application class so that you can view its parameters.

2 Open the parameters that track the type of CPU utilization that you want to view:

PATROL displays a graph that shows the amount of CPU utilization over time.

Task Page

“Viewing CPU Utilization” 108

“Viewing CPU Statistics on Interrupts, Switches, and Waits” 109

“Viewing Statistics on CPU Run Queue” 109

“Viewing Statistics on Multiple CPUs” 110

Parameter Description

CPUCpuUtil displays the percentage of CPU utilization, which is calculated by subtracting CPU idle time from 100

CPUIdleTime displays the percentage of CPU time that is spent idle

CPUSysTime displays the percentage of CPU time that is spent in system mode doing system tasks, including the CPU resources consumed by calls to kernel routines

CPUUserTime displays the percentage of CPU time that is spent on user mode commands and tasks initiated by users



Viewing CPU Statistics on Interrupts, Switches, and Waits

This task describes how to view information about activities that retard the performance of the CPU. These activities include CPU interrupts, context switches, and waits on input and output operations.

To View Statistics on Activities That Interfere with the CPU


2 Open the parameters that track the type of CPU information that you want to view:

PATROL displays a graph that shows the requested information over time.

Viewing Statistics on CPU Run Queue

This task describes how to view specific information about the CPU run queue.

To View the CPU Run Queue Statistics


2 Open the parameters that track and display the run queue information in the form that you want to view:



CPUInt displays the number of non-VME device interrupts

CPUWio displays the percentage of time that the CPU spends waiting for input and output operations

CPUProcSwch displays the total number of CPU context switches per second.


CPULoad displays the 1-minute load average from the uptime command. Load average is the average number of processes in the kernel’s run queue during an interval (1 minute in this case).

CPURunQSize displays the number of processes in the run queue (RunQ)



Viewing Statistics on Multiple CPUs

This task describes how to view basic CPU utilization information for multiple processors running on the same machine.

To View CPU Utilization Statistics for Multiple Processors

1 Access the CPU application class so that you can view its parameters and the SMP application class.

2 Open the SMP application class so that you can view its instances (one for each processor).

3 Open an SMP instance so that you can view its parameters.

4 Open the parameters that display the basic CPU utilization statistics that you want to view:



SMPIdlePercent displays the percentage of time that the CPU was idle

SMPSystemPrcnt displays the amount of processor time that is spent on system activities

SMPWaitPercent displays the amount of processor time that is spent waiting

SMPUserPercent displays the amount of processor time that is spent on user-requested activities

NOTE The SMP application class creates four parameters on all the platforms that it monitors. On some platforms such as HP and Solaris, SMP also creates some platform-specific parameters. For more information on these parameters, see the PATROL KM for Unix and Linux Help.


Object Hierarchy for KERNEL

Object Hierarchy for KERNELThe KERNEL application class contains parameters on kernel messages, semaphore operations, and system calls as well as other information.

Figure 7 illustrates the basic hierarchy but does not necessarily display all instances and parameters.

Figure 7 KERNEL Application Object Hierarchy

OS container

Application class

Parameters


KERNEL

KERNELThe KERNEL application class monitors various aspects of the kernel. This application class does not provide any menu commands because it automatically detects and monitors the kernel. It does gather and store a number of vital statistics in the KERNEL parameters.

The KERNEL tasks on how to access information stored in parameters are described in detail on the following pages:

Viewing the Kernel Build Information

This task describes how to view the build date of the kernel running on your system.

To View the Build Date of the Kernel

Access the KERNEL application InfoBox as described in “Accessing KM Commands and InfoBoxes” on page 402. PATROL displays the KERNEL InfoBox, which provides the build date of the kernel.

Figure 8 KERNEL InfoBox

Task Page

“Viewing the Kernel Build Information” 112

“Viewing Kernel Memory Allocation Statistics” 113

“Viewing Kernel I-node Usage” 114

“Viewing Kernel System Usage” 115


KERNEL

Viewing Kernel Memory Allocation Statistics

This task describes how to view kernel memory allocation (KMA) information.

Before You Begin

Memory requests are divided into three categories:

■ Small memory request—a request for less than 256 bytes of memory

■ Large memory request—a request from 512 bytes to 4 KB of memory

■ Oversized memory request—a request for more than 4 KB of memory that is allocated dynamically

To View the KMA Statistics

1 Access the KERNEL application class so that you can view its parameters.

2 Open the parameter that records the type of Kernel Memory Allocation information that you want to view:



KERLgAlloc displays the amount of memory in bytes that is allocated for large memory requests by KERNEL Memory Allocation (KMA) in the large memory request pool

KERLgFail displays the number of large memory pool requests that failed

KERLgMem displays the amount of memory in bytes that is available in the KERNEL Memory Allocation (KMA) large memory request pool

KERSmlAlloc displays the amount of memory in bytes that is allocated to the small memory request pool by KERNEL Memory Allocation (KMA)

KERSmlFail displays the number of small memory requests that failed

KERSmlMem displays the amount of memory in bytes that is available in the small memory request pool allocated by KERNEL Memory Allocation (KMA)

KEROvzAlloc displays the amount of memory that is dynamically allocated for oversized requests

KEROvzFail displays the number of requests for oversized memory that could not be satisfied


KERNEL

Viewing Kernel I-node Usage

This task describes how to view information about i-node slots, entries, and tables.

Before You Begin

An i-node is normally used to store active files, directories, and file information. It is also used for other services such as pipes, clone drivers, and, on some systems, semaphores.

To View the I-node Statistics


2 Open the parameters that records the i-node information that you want to view:



KERIGet displays the number of files that are located by an i-node entry

KERINodeUsedPercent displays the percentage of kernel i-node slots that are used

KERNameI displays the number of file system pathname searches, which are the conversion of filenames to i-nodes


KERNEL

Viewing Kernel System Usage

This task describes how to view information about the kernel slot usage (for files, locks, and processes), total number of system calls, directory block reads per second, and message operations performed per second.

To View the Kernel System Statistics


2 Open the parameter that records the type of kernel system information that you want to view:



KERDirBlk displays the number of directory block reads that are issued per second

KERFileUsedPercent displays the percentage of the kernel file slots that are used in the file table

KERLockUsedPercent displays the percentage of used kernel lock slots

KERMsg displays the number of message operations that are performed per second

KERProcUsedPercent displays the percentage of used kernel process slots and monitors the process table utilization

Each table entry represents an active process; the number of entries available depends on the number of terminal lines available and the number of processes spawned by each user.

KERSemOps displays the number of semaphore operations performed each second

KERSysCall displays the total number of system calls, which consists of all read, write, fork, and exec system calls, made per second


KERNEL


C h a p t e r 6
6 Using Composite Parameters
The PATROL Knowledge Module for Unix and Linux provides the ability to create an aggregate parameter. This aggregate parameter consists of two or more existing parameters. PATROL evaluates the values of these designated parameters and then determines, based on user-defined criteria, whether the cumulative effect of these parameters’ states warrants a warning or an alarm. The following sections appear in this chapter.

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Object Hierarchy for COMPOSITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Working with Composite Parameter Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Examples of Composite Parameter Expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . 120Syntax Rules for Composite Parameter Expressions . . . . . . . . . . . . . . . . . . . . . . . 120Setting the Status of a Composite Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Creating Composite Parameter Expressions Using the Wizard. . . . . . . . . . . . . . 121Creating Composite Parameter Expressions Manually . . . . . . . . . . . . . . . . . . . . . 124Editing Composite Parameter Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Deleting Composite Parameter Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126


Introduction

IntroductionComposite parameters are parameters whose values are dependent on one or more existing PATROL parameters. You can assign PATROL alarm settings and recovery actions on the newly created parameters in the same way that you use alarm settings and recovery actions on other parameters.

A composite parameter expression consists of one or more relational clauses joined by Boolean (logical) operators. A relational clause can have one of the following forms:

■ parameter (relational operator) constant or string■ constant or string (relational operator) parameter■ parameter (relational operator) parameter

A relational operator can be any of the standard PSL relational operators (that is, <, >, ==, <=, >=).

Relational clauses can be combined using the logical operators AND (&&) and OR (||).

The result of a composite parameter expression is a PATROL parameter condition, such as “alarm when true,” or “warn when false.”

For example, you can build a composite parameter that triggers a PATROL alarm indicating low memory conditions only when both of the following conditions are true:

■ CPUWio > 40■ MEMPFault > 15

See “Examples of Composite Parameter Expressions” on page 120 for detailed examples.

Object Hierarchy for COMPOSITEThe COMPOSITE application class contains instances for each composite parameter that you have designed. Each instance contains three parameters associated with the existing composite parameter. One parameter contains the logical expression that defines the composite parameter’s threshold, one contains the PATROL-generated PSL code that constitutes your parameter, and one contains the results of the composite parameter over time.



Working with Composite Parameter Expressions

Figure 9 COMPOSITE Application Object Hierarchy


You can enter composite parameter expressions manually or by using the expression entry wizard. Even if you use the expression entry wizard, you may need to edit the expression manually for complex expressions.

You can create, edit, and delete composite parameter expressions using COMPOSITES_COLLECTOR with the application icon shown in Figure 10.

Figure 10 COMPOSITES_COLLECTOR Application Icon

After you create a composite parameter, the icon for the composite parameter appears in the COMPOSITES container (see Figure 11 on page 120) after the next scheduled update of the parameter.

OS container

Application class

Parameters

Instances

UNIX OS



Figure 11 COMPOSITES Parameters Container Icon

Examples of Composite Parameter Expressions

Example 1

CPU System Time for CPU 0 is greater than 91 percent

Example 2

CPUWio is greater than 40 AND MEMPFault is greater than 15

Example 3

DSKAvgQueue is greater than or equal to 20 OR DSKBps is greater than 85 and MEMPFault is greater than 15

Syntax Rules for Composite Parameter Expressions

The following syntax rules apply when you create a composite parameter expression:

1. A valid composite parameter name consists of alphanumeric characters. It cannot contain a space character or any special characters, such as _, /, * or # .

2. All parameters in the expression must be valid PATROL parameters. The parameter name must specify the application class, the application instance, and the parameter name.

’/CPU/CPU_0/CPUSysTime’ > 91

’/CPU/CPU_0/CPUWio’ > 40 && ’/MEMORY/MEMORY/MEMPFault’ > 15

’/DISK/c0t1d0/DSKAvgQueue’ >= 20 || ’/DISK/c0t3d0/DSKBps’ > 85 && ’/MEMORY/MEMORY/MEMPFault’ > 15



3. Although the expression entry wizard displays all parameters within an application class, including collector parameters, the application cannot use collector parameters in calculations.

4. Expressions cannot contain arithmetic operators.

5. String terms must be enclosed in double quotes (").

6. You can enclose a double quote (") in a string by “escaping” it using a backslash, \. A string with an enclosed double quote looks like

"this \"string\""

You cannot use the backslash to escape any other special characters.

7. Although the expression entry wizard does not enable you to enter parentheses in an expression, you can enter parentheses manually to control the order of the expression evaluation. If parentheses are not used, expression evaluation is strictly left to right, with the relational operators having higher precedence than the Boolean operators.

Setting the Status of a Composite Parameter

The state of the composite parameter does not affect the state of the PATROL parameters used to define the composite parameter. For example, if you can make the composite parameter inactive, the parameters used in the expression can remain active.

If the parameters used in a composite parameter expression are inactive, the composite parameter is not calculated.

Creating Composite Parameter Expressions Using the Wizard

This task describes how to create composite parameters using the expression entry wizard.

Before You Begin

You must be using a PATROL Console in developer mode.



To Create a Composite Parameter Expression Using the Expression Entry Wizard

1 From the COMPOSITES_COLLECTOR menu, choose KM Commands => Create Expressions.

PATROL displays the Create Expression dialog box.

2 Type a name for the new expression.

A valid composite parameter name consists of alphanumeric characters. It cannot contain a space character or any special characters, such as _, /, * or # .

3 Click Create.

PATROL displays the Edit Expression dialog box.

A If you do not want the composite parameter to be active when you finish defining it, deselect the Active checkbox.

B Select the Warning state or the Alarm state button to indicate the parameter state that PATROL sets when the condition specified by the expression occurs.

C Select the True or False button to indicate whether PATROL should set the condition when the expression is true or false.

4 To start the expression entry wizard, click Wizard.

PATROL displays the Select Expression Term Type dialog box.

5 Select the term type that you want to use:

■ If you select PATROL KM Parameter and then click Continue, PATROL displays the Select PATROL application dialog box. Go to Step 6 to continue.

■ If you select Constant value and then click Continue, PATROL displays the Enter Constant Value dialog box. Go to step 8 on page 123 to continue.

NOTE To return to the previous dialog box or redisplay the Create Expressions dialog box, you can click Cancel at any time while you are using the expression entry wizard.

NOTE The active state for the composite parameter does not affect the active state for the parameters used in the definition of the composite parameter.



6 Select the application class that contains the parameter that you want to use in the expression and then click Continue.

The parameters associated with the selected application class are displayed in the parameter list box.

7 Select the application parameter that you want to use in the expression.

A If there is more than one instance of the application, select the instance you want to use in the definition and then click Continue.

B If the application has only one instance, select the PATROL application parameter you want to use in the expression and then click Continue.

PATROL displays the Select Relational Operator dialog box. Go to step 10 to continue.

8 Enter the constant you want to use in the composite parameter expression.

The constant can be either an integer value or a string expression. See “Syntax Rules for Composite Parameter Expressions” on page 120 for information about string expressions.

9 Click Continue to continue entering the expression.

PATROL displays the Select Relational Operator dialog box.

10 Select the relational operator you want to use in the relational clause and then click Continue.

After you complete entry of the second term, PATROL displays the Expression Complete dialog box.

■ If you do not want to add another relational clause to the expression, click Done. PATROL displays the Save or Discard dialog box. The procedure continues with step 12 on page 124.

■ If you want to add another relational clause to the expression, click More. PATROL displays the Select Boolean Operator dialog box. The procedure continues with step 11 on page 124.

NOTE Although collector parameters are listed in the dialog box, they cannot be used in composite parameter calculations.



11 Select the Boolean operator you want to use to join relational clauses.

PATROL displays the Select Expression Term Type dialog box. Return to step 5 on page 122 to add another relational clause to the expression.

12 Click Save to save the composite parameter expression.

After you click Save, the KM analyzes the expression to make sure that all terms are valid.

■ If the KM detects no errors, the new composite parameter appears in the COMPOSITES container after the next collection cycle.

■ If the KM detects errors in the expression, the Syntax Errors dialog box appears, which contains text identifying the error. Click OK to display the Edit Expression dialog box and correct the error.

Creating Composite Parameter Expressions Manually

This task describes how to create composite parameter expressions manually.

Before You Begin

Before you enter a composite parameter expression manually, you should be familiar with the syntax rules on page 120.


To Create a Composite Parameter Expression Manually

1 From the COMPOSITES_COLLECTOR menu, choose KM Commands => Create Expressions.

PATROL displays the Create Expressions dialog box.

2 Enter the parameter expression in the text entry box.

3 Select Done when you have completed your entry.

PATROL displays the Save or Discard dialog box.

4 Click Save to save the composite parameter expression. The KM analyzes your entry to make sure that all terms are valid.



■ If the KM detects no errors, the new composite parameter appears in the COMPOSITES container after the next collection cycle.

■ If the KM detects errors in the expression, the Syntax Errors dialog box appears, which contains text identifying the error. Click OK to display the Edit Expression dialog box and correct the error.

Editing Composite Parameter Expressions

This task describes how to edit a composite parameter expression.

Before You Begin


Understand the syntax rules for composite parameter expressions. For more information, see “Syntax Rules for Composite Parameter Expressions” on page 120.

To Edit a Composite Parameter Expression

1 Choose KM Commands => Edit Expressions from the Composites menu located on the Composites application icon.

PATROL displays the Edit Expressions dialog box.

2 Select the name of the composite parameter you want to edit and click Edit.

3 Edit the expression as follows:

■ To change the relational clause, edit the expression in the text entry dialog box manually. For more information, see “Syntax Rules for Composite Parameter Expressions” on page 120.

■ To add a relational clause to the expression, click Wizard. You are then prompted to select a Boolean operator to join the clauses.

4 Click Done to complete the changes.

PATROL displays the Save or Discard dialog box.

5 Click Save to save the changes.

The PATROL KM validates the expression after you click Save and displays any problems.



Deleting Composite Parameter Expressions

This task describes how to delete composite parameter expressions.

Before You Begin


At least one composite parameter expression must exist.

To Delete a Composite Parameter Expression

1 Choose KM Commands => Delete Expressions from the Composites menu located on the Composites application icon.

PATROL displays the Delete Expressions dialog box.

2 Select the name of the composite parameter you want to delete and click Delete.

PATROL removes the expression from the dialog box and deletes the application instance and its associated parameters.


C h a p t e r 7
7 Monitoring Disks
The PATROL Knowledge Module for Unix and Linux gives you the ability to monitor all disk drives mounted on a system. The following sections appear in this chapter.

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Disks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Excluding a Single Disk from Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Selecting Disks to Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Resuming Monitoring Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133


Introduction

IntroductionThe DISK application monitors the disk drives that are mounted on a system for information such as

■ average number of requests in the queue■ average service time■ number of blocks transferred per second■ percentage of time the device was busy servicing a transfer request■ number of kilobytes read from disk per second■ number of read and write pages per second■ number of disk transfers per second■ number of kilobytes written to disk per second

By default, the DISK application class discovers and monitors all the disks mounted on the system. You use menu commands to select which drives are monitored and which are not.

Object HierarchyThe DISK application class contains an instance for each disk that is being monitored. Each disk instance contains parameters on queued requests, service time, block transfer rate, and read and write speeds.



Object Hierarchy

Figure 12 DISK Application Object Hierarchy

OS container

Application class

Parameters

Instances

UNIX OS


Disks

DisksThe DISK application class enables you to select which disks PATROL monitors. With this feature, you can exclude from monitoring test disks and other disks that are not vital to your company’s day-to-day activities.

The DISK tasks are described in detail on the following pages:

Excluding a Single Disk from Monitoring

This task describes how to stop monitoring a single disk.

Before You Begin

To perform this task, you must be in developer mode. If you attempt to stop monitoring a disk when in operator mode, PATROL displays the following error message in the system output window.

To Stop Monitoring a Disk

On the disk that you do not want to monitor, perform the following steps.

1 Access the DISK application menu as described in “Accessing KM Commands and InfoBoxes” on page 402.

2 Select Stop Monitoring.

PATROL removes the disk icon from the PATROL Object Hierarchy and stops monitoring the selected disk. To resume monitoring of the disk, see “Selecting Disks to Monitor” on page 131.

Task Page

“Excluding a Single Disk from Monitoring” 130

“Selecting Disks to Monitor” 131

“Resuming Monitoring Disks” 132

DISK: Only Development Console can filter an instance


Disks

Selecting Disks to Monitor

By default, PATROL monitors all disks. This task describes how to determine which disks PATROL excludes from monitoring and how to resume monitoring disks that have been excluded.

Before You Begin

■ The exclusion list feature supports regular expressions. To stop monitoring large numbers of disks that have uniform names, use regular expressions.

■ To perform this task, you must be in developer mode. If you attempt to stop monitoring a disk when in operator mode, PATROL displays the following error message in the system output window.

To Stop Monitoring Disks

On any disk, perform the following steps.


2 Select Edit DISK Exclusion List.

PATROL opens the DISK Exclusion List dialog box (Figure 13), which contains two list boxes: Monitored Disks and Excluded Disks.

Figure 13 DISK Exclusion List Dialog Box



Disks

3 In the Monitored Disks list box, select the disk that you want to exclude from monitoring.

4 Click Apply.

PATROL adds the disk to the list of excluded disks and then removes the disk icon from the PATROL Object Hierarchy.

5 Repeat step 1 through step 4 for each disk that you want to exclude.

Resuming Monitoring Disks

This task describes how to resume monitoring a single disk or all disks.

Before You Begin

To perform this task, you must be in developer mode. If you attempt to resume monitoring a disk when in operator mode, PATROL displays the following error message in the system output window.

To Resume Monitoring a Disk

On any disk, perform the following steps.


2 Select Edit DISK Exclusion List.

PATROL opens the DISK Exclusion List dialog box (Figure 13 on page 131), which contains two list boxes: Monitored Disks and Excluded Disks.

3 In the Excluded Disks list box, select the disk that you want to resume monitoring.

4 Click Apply.

PATROL places the disk in the Monitored Disks list box, discovers the disk instance during the next discovery cycle, and resumes monitoring it.



Disk Space

To Resume Monitoring All Disks


2 Select Clear DISK Exclusion List.

PATROL opens the Confirmation dialog box, which asks whether you want to clear the DISK exclusion list.

3 Click Yes.

PATROL discovers all the disk instances during the next discovery cycle and resumes monitoring them.

Disk SpaceWith PATROL, you can monitor disk space by user. For more information, see Chapter 18, “Monitoring Users.”


Disk Space


C h a p t e r 8
8 Monitoring and Managing File Systems
The PATROL Knowledge Module for Unix and Linux gives you the ability to monitor all file systems in a network. The following sections appear in this chapter.

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Monitoring File Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Excluding a Single File System from Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . 138Selecting File Systems to Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Automating File System Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Running Recovery Actions Only with Operator Confirmation . . . . . . . . . . . . . . 143Preventing File Systems from Being Monitored . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Working with File System Types and File System Classes . . . . . . . . . . . . . . . . . . 145

Managing File Systems Using PATROL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Mounting a File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Unmounting a File System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Synchronizing File System Cache and Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Searching for Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Removing Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153


Introduction

IntroductionThe FILESYSTEM application monitors the file systems mounted on a system for information such as

■ disk space

— number of kilobytes available — number of kilobytes used— percentage of space used

■ i-nodes

— percentage of i-nodes used— number of i-nodes available

The application also lets you manage a monitored file system within PATROL. Some of the tasks that you can perform are

■ mount and unmount file systems■ synchronize information stored in the file system cache and disk■ search for and remove files

By default, the FILESYSTEM application discovers and monitors all the disks mounted on the system. You can use menu commands to select which file systems are monitored and which are not.


Object Hierarchy

Object HierarchyThe FILESYSTEM application class contains an instance for each file system that is being monitored. Each file system instance contains parameters on free and used space, free and used i-nodes, and system capacity.

Figure 14 illustrates the basic hierarchy but does not necessarily display all and parameters.

Figure 14 FILESYSTEM Application Object Hierarchy

OS container

Application class

Parameters

Instances

UNIX OS


Monitoring File Systems

Monitoring File SystemsThe FILESYSTEM application class enables you to select which file systems PATROL monitors. With this feature, you can exclude from monitoring test systems and other file systems that are not vital to your company’s day-to-day activities.

The FILESYSTEM tasks are described in detail on the following pages:

Excluding a Single File System from Monitoring

This task describes how to stop monitoring a single file system.

Before You Begin

To perform this task, you must be in developer mode. If you attempt to stop monitoring a file system when in operator mode, PATROL displays the following error message in the system output window.

To Stop Monitoring a Single File System

On the file system that you do not want to monitor, perform the following steps.

1 Access the FILESYSTEM application menu as described in “Accessing KM Commands and InfoBoxes” on page 402.


PATROL removes the icon for the file system from the PATROL Object Hierarchy and stops monitoring the selected system. To resume monitoring of the file system, see “Selecting File Systems to Monitor” on page 139.

Task Page

“Excluding a Single File System from Monitoring” 138

“Selecting File Systems to Monitor” 139

“Automating File System Cleanup” 141

“Running Recovery Actions Only with Operator Confirmation” 143

“Preventing File Systems from Being Monitored” 143

FILESYSTEM: Only Development Console can filter an instance



Selecting File Systems to Monitor

By default, PATROL monitors all file systems. This task describes how to determine which file systems PATROL excludes from monitoring and how to resume monitoring file systems that have been excluded.

Before You Begin

■ The exclusion list feature supports regular expressions. To stop monitoring large numbers of file systems that have uniform names, use regular expressions.

■ The exclusion list feature excludes file systems by type. You can stop monitoring all NFS systems, CD-ROM systems, and process control (proc) subsystems.

■ To perform this task, you must be in developer mode. If you attempt to stop monitoring a file system when in operator mode, PATROL displays the following error message in the system output window.

To Stop Monitoring File Systems

On any file system, perform the following steps.


2 Select Edit FILESYSTEM Exclusion List.

PATROL opens the FILESYSTEM Exclusion List dialog box (Figure 15 on page 140), which contains two list boxes: Monitored Filesystems and Excluded Filesystems.


NOTE If the FILESYSTEM application instance has more than 250 instances, the KM displays a message in the system output window (SOW) similar to the following, 20040616162441 PatrolAgent-W-EUSER: Discovery/ pre discovery proc “FILESYSTEM” may be in an infinite loop - executed 500029 instructions.” To prevent this situation, increase the maximum PSL instruction limit from the 500000 default setting to 5000000 or higher.



Figure 15 FILESYSTEM Exclusion List Dialog Box

3 Either in the Excluded Filesystems list box, select the file system that you want to monitor or in the Monitored Filesystems list box, select the file system that you want to exclude from monitoring.

4 If you want to stop monitoring one of the following file system types, select the corresponding check box.

Ignore Filesystem Type Description

NFS excludes all NFS file systems, which means that the PATROL Agent running on this managed system monitors only file systems that reside on the managed system; this option does not exclude SAMBA or AFS shares (types include NFS and CACHEFS)

CD-ROM excludes mounted CD-ROMs (types include CDFS, HSFS, and ISO9660)

proc excludes file systems that provide access to the image of each active process in the system (types include PROC, USBDEVFS, and DEVPTS)

Custom excludes file systems that you designate (possible types include VFS, SYSV, and UMSDOS)



5 Click Apply.

Based on your selections in step 3 and step 4, PATROL adds the file systems to the respective list box and then either removes or inserts the file system icons from the PATROL Object Hierarchy.

6 Repeat step 3 through step 5 for each file system that you want to exclude. Then click Done.

Automating File System Cleanup

This task describes how to set up the Filesystem Cleanup recovery action, which removes files once the percentage of the file system currently in use, measured by the FSCapacity parameter, exceeds the threshold established in either Alarm1 or Alarm2. This recovery action attempts to remove core dump files, and if the file system /tmp, or /tmp is mounted off this file system, the action attempts to remove from /tmp files that are 30 days or older.

Before You Begin

■ You must be root to run this command.

■ For a given FILESYSTEM instance, the FSCapacity parameter must be active.

■ This recovery action applies to all file system types except NFS, CD-ROM, and proc.

To Set Up Automatic File System Cleanup

1 Access the Computer application menu as described in “Accessing KM Commands and InfoBoxes” on page 402.

2 Select Configure Recovery Actions.

PATROL displays the Register Recovery Actions dialog box, which lists all available recovery actions.



3 Select the FilesystemCleanup recovery action and click Accept.

PATROL displays the Recovery Actions Instance dialog box. This recovery action applies to all FILESYSTEM instances.

4 Select the only item in the list and click Edit.

PATROL displays the Edit Recovery Action dialog box (Figure 16).

Figure 16 Edit Recovery Action Dialog Box

5 Select the mode of the recovery action by clicking the corresponding radio button.

■ Run Unattended—runs the recovery action automatically, without prompting you

■ Run Attended—prompts you before running the recovery action, and does nothing if you do not respond within the user-defined time-out period

■ Do Not Execute—does not perform the recovery action; this mode is the default setting

6 Click ACCEPT.

PATROL closes the Edit Recovery Actions dialog box and displays the Recovery Action Instances dialog box.

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



7 Click Close.

PATROL closes the Recovery Action Instances dialog box and displays the Registered Recovery Actions dialog box.

8 Click Close.

PATROL closes the Registered Recovery Actions dialog box and enables the recovery action based on the options that you chose.

Running Recovery Actions Only with Operator Confirmation

This task describes how to manage a recovery action when it is set to run only with operator confirmation. With this feature, you can turn off the operator confirmation check so that the recovery action will run without user input.

Before You Begin

You must have set up a recovery action as described in “Automating File System Cleanup” on page 141.

To Run Recovery Actions in Attend Mode

When the value of the FSCapacity parameter exceeds the file system percentage used amount established in thresholds, PATROL displays the Run Recovery Action dialog box (Figure 17).

Figure 17 Run Recovery Action Dialog Box



Click Acknowledge to run the recovery action.

If you want to disable the recovery action or run the recovery action in the future without user input, select the appropriate option.

■ Do not ask me again—switches the recovery action to unattended mode, which runs the recovery action without any user interaction

■ Disable—prevents the recovery action from attempting to run and from producing this dialog box

If you click Cancel, PATROL does not run the recovery action or save any of the options that you selected.

Preventing File Systems from Being Monitored

The PATROL KM for Unix and Linux automatically discovers the presence of mounted file systems and also issues an alert on the FSMountStatus parameter if a discovered file system is later unmounted. This feature is not optional and cannot be turned off.

In some situations, however, you may want to unmount a discovered file system and cancel any alerts that the PATROL KM for Unix and Linux would subsequently issue, or you may want to exclude a file system from being monitored in the first place. In such cases, you can use one of the following options prevent a file system from being monitored.

■ Use the Stop Monitoring command to add the name of the file system to the FILESYSTEM exclusion list. This command will prevent monitoring of the file system without regard to whether the file system is mounted.

■ Edit the /PUK/FILESYSTEM/moniList variable, which established file system persistence, to remove the file system name from the variable. This option only applies to previously discovered file systems that are no longer available.



Working with File System Types and File System Classes

The PATROL Knowledge Module for Unix and Linux uses the FILESYSTEM.km to report file system information. In turn, the FILESYSTEM.km uses the output from the Unix mount command to determine which types of file systems are mounted. The FILESYSTEM.km discovery logic looks at the type field to determine file system type.

There are four classes of file systems based on type. You can use these classes to exclude certain types of file systems from monitoring. The following table identifies these classes and the Agent configuration variables that you can use to monitor them.

You can edit the appropriate Token in the agent configuration variable to add, delete, or modify file system types for any of these classes. For example, you can add AUTOFS to the variable defining NFS file system types: /UNIX/FILESYSTEM/NFSTokens. This would cause the FILESYSTEM.km to treat file systems with type=AUTOFS as an NFS file system, which, in turn, would result in inclusion or exclusion based upon the NFS file system exclusion rule.

Files System Class Files System Type Agent Configuration Variable

NFS NFS The Agent Configuration variable, /UNIX/FILESYSTEM/NFSTokens designates which file system types are considered NFS file systems. By default, this variable is populated with NFS CACHEFS NFS3 NFSV3.

CDFS CD The Agent Configuration variable, /UNIX/FILESYSTEM/CDFSTokens designates which file system types are considered CDFS file systems. By default, this variable is populated with CDFS HSFS ISO9660 CDRFS.

PROC PROC The Agent Configuration variable, /UNIX/FILESYSTEM/PROCTokens designates which file system types are considered PROC file systems. By default, this variable is populated with PROC USBDEVFS DEVPTS PROCFS.

CUST CUSTOM The Agent Configuration variable, /UNIX/FILESYSTEM/CUSTTokens designates which file system types are defined as CUST file systems. By default, this variable is blank.


Managing File Systems Using PATROL

Managing File Systems Using PATROLThe FILESYSTEM application class enables you to manage file systems from within PATROL. With this feature, you can mount and unmount systems either automatically or manually. It also gives you the ability to synchronize file system tables and find and remove files.

The FILESYSTEM tasks related to managing file systems are described in detail on the following pages:

Mounting a File System

This task describes how to mount a file system that PATROL has detected as offline or that has not been discovered.

Before You Begin


■ To perform this task, you must be in developer mode. If you attempt to mount a file system when in operator mode, PATROL displays the following error message in the system output window.

To Mount a File System


Task Page

“Mounting a File System” 146

“Unmounting a File System” 148

“Synchronizing File System Cache and Disk” 149

“Searching for Files” 150

“Removing Files” 153





2 Select Maintenance => Mount => Automatic or Manual.

Automatic

PATROL uses the file system table to determine where to mount the file system. It prompts you for the password for the root account (shown in Figure 18). This option is available only if the file system has been unmounted.

Figure 18 Automatic Mount Dialog Box

Manual

PATROL prompts you for the device name, where it should enter the file system, and whether or not it should update the file system table (Figure 19).

Figure 19 Manual Mount Dialog Box

NOTE This menu command is only available when the filesystem is offline, when the filesystem is online, it is grayed out. The Manual option is only available on Linux, RS6000, OSF1, and HP platforms only. The Manual mount option is not available on the Solaris platform.

NOTE You can manually mount a file system on Linux, RS6000, OSF1, and HP platforms only. The manual mount option is not available on the Solaris platform.



■ Enter Device Name—the location (absolute path) of the file system (machine_name:/path)

■ Enter Mounted On—the path to be assigned to the file system once it is mounted

■ Update Filesystem Table—determine whether or not to make a record of this mount in the file system table; a record in the file system table ensures that the file system will be automatically mounted when the managed system is rebooted

3 Supply the required information for the type of mount that you are performing and click on Apply.

PATROL mounts the file system to your network and writes the result to the system output window.

Unmounting a File System

This task describes how to unmount a file system that PATROL detects mounted.

Before You Begin


■ To perform this task, you must be in developer mode. If you attempt to unmount a file system when in operator mode, PATROL displays the following error message in the system output window.

To Unmount a File System



2 Select Maintenance => Unmount => Automatic or Manual.

Automatic

PATROL prompts you for the password for the root account (Figure 20 on page 149).




Figure 20 Automatic Unmount Dialog Box

Manual

PATROL prompts you for the mount location (Figure 21), which is the path assigned to a file system once it has been mounted.

Figure 21 Manual Unmount Dialog Box

3 Supply the required information for the type of dismount that you are performing and click Apply.

PATROL unmounts the file system from your network and writes the result to the system output window.

Synchronizing File System Cache and Disk

This task describes how to write the information stored in the file system memory buffer (cache) to the disk immediately rather than waiting for the system to write it at a specified interval. This action synchronizes the information in the file system cache with the information stored on the disk.

To Write Information in the File System Memory to Disk

On the file system for which you want to search for files, perform the following steps.


2 Select Maintenance => Sync.

PATROL writes the memory buffer to disk.



Searching for Files

This task describes how to find files based upon different file characteristics. With this FILESYSTEM application command, you determine where the search begins in the file system and to define search criteria. It then builds the search expression. This command returns the search expression and a list of all the files that match the expression.

Before You Begin

■ You can search for files using a different user name and password from the one under which PATROL is running.

■ You can search for files based upon

— naming convention— owner— group— change date

■ You can restrict searches to

— one or multiple physical disks— a location or directory within a file system

To Search for Files

On the file system for which you want to search for files, perform the following steps.


2 Select Maintenance => Find Files Like.

PATROL prompts you for the user name and password of an account that can read the files that match the criteria.

3 Type the user name and password and click OK. If you want to use the account under which the PATROL Agent is currently running, leave both fields blank.

PATROL displays the Find Files Like dialog box (Figure 22 on page 151).



Figure 22 Find Files Like Dialog Box

4 Define the search criteria. The search is a logical AND operation that returns only files that match all the criteria defined by the following fields.

5 Click Find.

PATROL builds a search expression, searches the file system for files that match the criteria, and writes the results to a PATROL task object (Find Files Like) in the FILESYSTEM container.

Field Description

File Name the regular expression pattern for one or more files

For more information, see “CRegular Expressions” on page 407. Leave this field blank to search for any file name.

File Owner the owner of the file(s)File Group the group to which the owner of the file(s) belongsFile Updated in Last ‘n’ Days the period in days between the change date and the

current dateLimit to one physical disk restrict the operation to the disk drive on which the file

system is mounted



6 Access the Find Files Like task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

Output Format

The output has the following format. Table 31 defines each expression.

Begin: find /home/Begin: find /home/3Supvr/patrol_console_cache -name disc* -xdev -exec ls -ld {} \;

-rw-r--r-- 1 Begin: find /home/3Supvr/patrol_console_cache -name disc* -xdev -exec ls -ld {} \;



-rw-r--r-- 1 3Supvr dev 927 May 4 14:39 /home/3Supvr/patrol_console_cache/disc-1.idx

-rw-r--r-- 1 3Supvr dev 648 May 4 14:39 /home/3Supvr/patrol_console_cache/disc-1.dat

-rw-r--r-- 1 3Supvr dev 829 May 3 13:54 /home/3Supvr/patrol_console_cache/disc_idx-1.idx

-rw-r--r-- 1 3Supvr dev 0 May 3 13:54 /home/3Supvr/patrol_console_cache/disc_idx-1.dat

-rw-r--r-- 1 3Supvr dev 12 May 3 13:55 /home/3Supvr/patrol_console_cache/disc_idx-1

Begin: find /path -name <text*?> -xdev/-mount -exec <ls> -ld {} \;

-rw-r--r-- # <username> <group> ### MMM DD hh:mm <path>/<file_name.ext>

-------------------- >>>>> DONE <<<<< --------------------

Table 31 Find Files Like Command Output Format

Output Description

Search Expression

Begin: find find command

/path starting point for search

- name <text?*> file name pattern

- xdev/-mount search for files that reside only on the same file system as path; xdev works only on Solaris and some BSD systems

-exec ls list the contents of the specified directory

-ld options for the ls command: -l long format listing, -d list only the directory names and not its contents

{ } argument that substitutes current file



Removing Files

This task describes how to delete files based upon different file characteristics. With this FILESYSTEM application command, you specify where the file is located in the file system and to define file search criteria. It then builds the search and delete expression. This command returns the search and remove expression.

Before You Begin

■ You can search for files using a different user name and password from the one under which PATROL is running.

■ You can search for and remove files based upon

— naming convention— owner— group— change date

■ You can restrict search and remove operations to

— one or multiple physical disks— a location/directory within a file system

List of Files

-rw-r--r-- file permissions

# number of links to the file

username owner of the file

dev group of owner

### size in bytes

MMM DD hh:mm date-time stamp

location path and file name

-- >>> DONE <<< -- end of file list


Output Description



To Remove Files

On the file system for which you want to remove files, perform the following steps.


2 Select Maintenance => Remove Files Like.

PATROL prompts you for the user name and password of an account that can read and write to the files that match the criteria.

3 Type the user name and password and click OK. If you want to use the account under which the PATROL Agent is currently running, leave both fields blank.

PATROL displays the Remove Files Like dialog box (Figure 23).

Figure 23 Remove Files Like Dialog Box



4 Define the search and remove criteria. The search and remove feature is a logical AND operation that returns only files that match all the criteria defined by the following fields.

5 Click Find.

PATROL builds a search and remove expression, searches the file system for files that match the criteria, removes the files, and writes the search and remove expression to a PATROL task object (Remove Files Like) in the FILESYSTEM container.

6 Access the Remove Files Like task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the expression. Your result should resemble this example:

Field Name Description

File Name the regular expression pattern for one or more files

For more information, see “CRegular Expressions” on page 407. Leave this field blank to search for any file name.

File Owner the owner of the file(s)File Group the group to which the owner of the file(s) belongsFile Updated in Last ‘n’ Days the period in days between the change date and the

current dateLimit to one physical disk restrict the search to the disk drive on which the file

system is mounted

Begin: find /oracle/bin -name Payroll_2000* -xdev -exec rm {} \;

-------------------- >>>>> DONE <<<<< --------------------



Output Format

The output has the following format. Table 32 defines each expression.

Begin: find </path> -name <text?*> -xdev -exec rm {} \;

-------------------- >>>>> DONE <<<<< --------------------

Table 32 Remove Files Like Command Output Format

Output Description

Search Expression




- xdev/-mount search for files that reside only on the same file system as path; xdev works only on Solaris and some BSD systems

-exec rm run the Unix OS command remove



-- >>> DONE <<< -- end of search and remove output


C h a p t e r 9
9 Monitoring Overall System Health
The PATROL Knowledge Module for Unix and Linux gives you the ability to monitor the overall health of the system. It provides immediate yes-or-no style answers to questions about overall CPU, file system, and swap space usage. The following sections appear in this chapter.

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158HEALTH AT A GLANCE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Viewing the Overall CPU, File System, and Swap Usage . . . . . . . . . . . . . . . . . . . 159Viewing the Overall Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160


Introduction

IntroductionThe HEALTH AT A GLANCE application monitors the

■ overall CPU usage of the system■ overall file system usage of the system■ overall virtual memory of the system

Object HierarchyThe HEALTH AT A GLANCE application class contains parameters on system-wide CPU, file system, and virtual memory usage.


Figure 24 HEALTH AT A GLANCE Application Object Hierarchy

OS container

Application class

Parameters

UNIX OS


HEALTH AT A GLANCE

HEALTH AT A GLANCEThe HEALTH AT A GLANCE application class enables you to monitor the overall health of the system. By reviewing the information provided by the HAAG parameters, you should be able to determine if your system is healthy or not.

The HEALTH AT A GLANCE tasks are described in detail on the following pages:

Viewing the Overall CPU, File System, and Swap Usage

This task describes how to view the system’s overall statistics on CPU, file system and swap space usage and determine if the system is generally healthy.

To View the System’s Overall CPU, File System, and Swap Usage

1 Access the HEALTH AT A GLANCE application class so that you can view its parameters.

2 Open the parameter that records the type of system information you want to view.


Task Page

“Viewing the Overall CPU, File System, and Swap Usage” 159

“Viewing the Overall Health” 160

Field Name Description

HAAGCpuUsage displays whether or not the system’s overall CPU usage is satisfactory

HAAGFileSystemUsage displays whether or not the system’s overall file system usage is satisfactory

HAAGSwapUsage displays whether or not the system’s overall swap space usage is satisfactory


HEALTH AT A GLANCE

Viewing the Overall Health

This task describes how to view a textual summary of the system’s general health.

To View the System’s Overall Health

1 Access the HEALTH AT A GLANCE application class so that you can view its parameters.

2 Open the HAAGHealthSummary parameter.

PATROL displays the information in a text parameter. Your result should resemble this example:

Day Mon DD HH:MM:SS CCYY

CPU Utilization

Total CPU Utilization OK

User Percentage OK

System Percentage OK

Filesystem Usage

proc Used Space Percentage OK

home/dd Used Space Percentage OK

apps/ Used Space Percentage WARN

fs13 Used Space Percentage ALARM

Swap Usage

Summary Swap Percentage Used OK


C h a p t e r 10
10 Monitoring and Managing Memory
The PATROL Knowledge Module for Unix and Linux gives you the ability to monitor and manage memory on a system. The following sections appear in this chapter.

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Object Hierarchy for MEMORY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Shared Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Viewing Shared-Memory Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Deleting a Shared-Memory Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Semaphores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Viewing Semaphore Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Deleting a Semaphore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Object Hierarchy for SWAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Virtual Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Viewing the Amount of Swap Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Viewing the Swap Partition Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Viewing the Percentage of Used Swap Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172


Introduction

IntroductionThe PATROL Knowledge Module for Unix and Linux monitors and manages memory through two applications: MEMORY and SWAP.

■ The MEMORY application monitors such memory activity as

— number of active virtual pages— number of pages anticipated— number of pages freed per second— number of pages in and out per second— number of pages scanned per second

■ The MEMORY application also manages shared-memory segments and semaphores.

■ The SWAP application monitors virtual memory. It provides the following information for the entire system and for each swap area.

— amount of disk space reserved for swap— amount of swap space used— percentage of swap space used


Object Hierarchy for MEMORY

Object Hierarchy for MEMORYThe MEMORY application class contains several parameters with information about memory usage and management.


Figure 25 MEMORY Application Object Hierarchy

Shared MemoryThe MEMORY application class enables you to manage shared-memory segments. With this feature, you can view which segments are shared and who owns them. You can also delete shared segments.

The tasks related to shared memory are described in detail on the following pages:

Task Page

“Viewing Shared-Memory Segments” 164

“Deleting a Shared-Memory Segment” 166

OS container

Application class

Parameters

UNIX OS


Shared Memory

Viewing Shared-Memory Segments

This task describes how to view information about the shared-memory segments. The PATROL KM for Unix lists the type of memory, permissions, owner, and group.

To View Shared-Memory Segments

1 Access the MEMORY application menu as described in “Accessing KM Commands and InfoBoxes” on page 402.

2 Select List Shared Memory Segments.

PATROL writes the information to a PATROL task object (List Shared Memory Segments) in the MEMORY container.

3 Access the List Shared Memory Segments task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

Output Format

The output has the following format. Table 33 on page 165 defines each expression.

IPC status from <running system> as of Tue May 8 HH:MM:SS CDT CCYYT ID KEY MODE OWNER GROUPShared Memory:m 101 0x1038f476 --rw-rw-rw- 3supr adminm 102 0x4130f478 --rw-rw-rw- Night1 shiftm 7703 0x4140f47b --rw-rw-rw- bsmith HR_VAm 104 0x4109f479 --rw-rw-rw- ljohns ACCTGm 205 0x4111f37a --rw-rw-rw- vpatel IS_TXm 106 0x4122f52c --rw-rw-rw- vpatel IS_TXm 207 0x4103f47e --rw-rw-rw- jocruz adminm 908 0x4777f47f --rw-rw-rw- odella DISTB-------------------- >>>>> DONE <<<<< --------------------

IPC status from <running system> as of Tue May 8 HH:MM:SS CDT CCYYT ID KEY MODE OWNER GROUPShared Memory:m 101 0x1038f476 --rw-rw-rw- uname gname-------------------- >>>>> DONE <<<<< --------------------


Shared Memory

Table 33 List of Shared-Segment Command Output Format

Field Description

T type of facility

q—message queue

m—shared-memory segment

s—semaphore

ID the facility entry identifier

KEY the key that is used as an argument by various functions [msgget( ), semget( ), and shmget( )] to create the facility entry

MODE the facility accesses modes and flags

It consists of 11 characters.

The first 2 characters are

R—a process is waiting on msgrc(2)

S—a process is waiting on a msgsnd(2)

D—the shared-memory segment is scheduled to be removed (it will disappear when the last process attached to it detaches)

C—shared-memory segment is cleared when the first attach is executed

- —flag not set

The next 9 characters are Unix permissions: owner (first 3), group (second 3), other (third 3). Permissions are

r—read

w—write

a—alter

- —no permission granted

OWNER the login name of the owner of the facility entry

This name identifies the owner of the process that allocated the shared-memory segment.

GROUP the group name of the owner


Shared Memory

Deleting a Shared-Memory Segment

This task describes how to delete a specified shared-memory segment based on its numeric ID, which can be discovered through the task, “Viewing Shared-Memory Segments” on page 164.

Before You Begin

To delete a shared-memory segment, you must own the segment or have an account with privileges to delete it. If you attempt to remove a segment that you do not own, PATROL issues a permission-denied error message.

To Delete Shared-memory Segments


2 Select Remove Shared Memory Segments.

PATROL displays the Remove Shared Memory Segment dialog box (Figure 26).

Figure 26 Remove Shared Memory Segment Dialog Box

3 Type the numeric ID in the Memory Segment ID field and click either Apply or Apply To Selected.

PATROL prompts you for a user name and password (Figure 27).

Figure 27 Remove Shared Memory Segment Confirmation Dialog Box


Semaphores

4 Enter the user name and password of the owner of the shared segment or an account with privileges to delete it and click OK.

PATROL writes a confirmation message to a task window.

SemaphoresThe MEMORY application class enables you to manage semaphores in the same way you manage shared-memory segments. With this feature, you can view which semaphores have been created and who owns them. You can also delete semaphores.

The semaphore management tasks are described in detail on the following pages:

Viewing Semaphore Information

This task describes how to view information about the semaphores. The task lists type of memory, permissions, owner, and group.

To View Semaphores


2 Select List Semaphores.

PATROL writes the information to a PATROL task object (List Semaphores) in the MEMORY container.

Remove shared memory segments

--------------- >>>>> DONE <<<<< ---------------

Task Page

“Viewing Semaphore Information” 167

“Deleting a Semaphore” 168


Semaphores

3 Access the List Semaphores task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

Output Format

The output has the following format. For a description of the content, see Table 33 on page 165.

Deleting a Semaphore

This task describes how to delete a specified semaphore based on its numeric ID, which can be discovered through the task, “Viewing Semaphore Information” on page 167.

Before You Begin

To delete a semaphore, you must own the segment or have an account with privileges to delete it. If you attempt to remove a segment that you do not own, PATROL issues a permission-denied error message.

IPC status from <running system> as of DAY MON DD HH:MM:SS CDT CCYYT KEY MODE OWNER GROUPSemaphores:s 0x1038f476 --ra-ra-ra- 3supr admins 0x4130f478 --ra-ra-ra- Night1 shifts 0x4140f47b --ra-ra-ra- bsmith HR_VAs 0x4109f479 --ra-ra-ra- ljohns ACCTGs 0x4111f37a --ra-ra-ra- vpatel IS_TXs 0x4122f52c --ra-ra-ra- vpatel IS_TXs 0x4103f47e --ra-ra-ra- jocruz admins 0x4777f47f --ra-ra-ra- odella DISTB-------------------- >>>>> DONE <<<<< --------------------

IPC status from <running system> as of DAY MON DD HH:MM:SS CDT CCYYT KEY MODE OWNER GROUPSemaphores:s 0x1038f476 --ra-ra-ra- uname gname-------------------- >>>>> DONE <<<<< --------------------


Semaphores

To Delete Semaphores


2 Select Remove Semaphores.

PATROL displays the Remove Semaphores dialog box (Figure 28).

Figure 28 Remove Semaphores Dialog Box

3 Type the numeric ID in the Semaphore ID field and click either Apply or Apply To Selected.


Figure 29 Remove Semaphores Confirmation Dialog Box

4 Enter the user name and password of the owner of the semaphore or an account with privileges to delete it and click OK.

PATROL writes a confirmation message to a task window.

Remove semaphores

--------------- >>>>> DONE <<<<< ---------------


Object Hierarchy for SWAP

Object Hierarchy for SWAPThe SWAP application class contains several parameters with information about partition size, free swap space available for the entire system, and the percentage of swap space used.


Figure 30 SWAP Application Object Hierarchy


Virtual Memory

Virtual MemoryThe SWAP application class enables you to monitor virtual memory. With this feature, you can view how much disk space is available for swapping and how much is currently used for swapping.

The SWAP tasks are described in detail on the following pages:

Viewing the Amount of Swap Space

This task describes how to discover how much swap space is available for either a swap area or an entire system.

To View the Amount of Swap Space in a Swap Area

1 Access the swap area instance in the SWAP application class so that you can view its parameters.

2 Open the SWPSwapFreeSpace parameter.

PATROL displays a graph that shows the amount of available swap space in the designated swap area over time.

To View the Amount of Total Swap Space on the System

1 Access the Summary instance in the SWAP application class so that you can view its parameters.

2 Open the SWPToTSwapFreeSpace parameter.

PATROL displays a graph that shows the total amount of available swap space on the system over time.

Task Page

“Viewing the Amount of Swap Space” 171

“Viewing the Swap Partition Size” 172

“Viewing the Percentage of Used Swap Space” 172


Virtual Memory

Viewing the Swap Partition Size

This task describes how to discover the current size of the swap partition for a swap area.

To View the Swap Partition Size in a Swap Area


2 Open the SWPSwapSize parameter.

PATROL displays a graph that shows the amount of available swap space in the designated swap area over time.

Viewing the Percentage of Used Swap Space

This task describes how to discover the current amount of swap space being used as a percentage of the total amount available for either the entire system or a particular swap area.

To View the Percentage of Swap Space Used in a Swap Area


2 Open the SWPSwapUsedPercen parameter.

PATROL displays a gauge that shows the amount of swap space currently being used as a percentage of the total swap space available in the designated swap area.

To View the Percentage of the Total Swap Space Used on the System

1 Access the Summary instance in the SWAP application class so that you can view its parameters.

2 Open the SWPToTSwapUsedPercen parameter.

PATROL displays a gauge that shows the total amount of available swap space currently being used as a percentage of the total swap space available on the system.


C h a p t e r 11
11 Monitoring and Managing Networks
The PATROL Knowledge Module for Unix and Linux gives you the ability to monitor the Unix network. The following sections appear in this chapter.

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Network Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Activating the NETWORK Application Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Deactivating the NETWORK Application Class. . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Viewing a Network Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178Discovering the Name of the Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 179Establishing Behavior When Unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Viewing Memory Buffer Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Network Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Viewing Network Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Listing Host and IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Network Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Listing Protocols Running on the Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Viewing Protocol Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Determining the Network Internet Protocol Address . . . . . . . . . . . . . . . . . . . . . . 191

Network Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Viewing the Routing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Determining the Number of Packets Entering and Exiting the Network . . . . . . 194Determining the Number of Packet Errors Entering and Exiting the Network. 194

Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Listing TCP/IP Services Running on the Network . . . . . . . . . . . . . . . . . . . . . . . . 196Listing Trusted Hosts on the Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Copying or Transferring Files by Using FTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Checking for a Network Resource by Using ping . . . . . . . . . . . . . . . . . . . . . . . . . 199

NOTE At installation, the NETWORK application class is set to inactive. To enable it to collect data for its parameters, see “Activating the NETWORK Application Class” on page 176.


Introduction

Logging In Remotely by Using rlogin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Querying the Name Server for the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Address Resolution Protocol (ARP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Viewing the Address Resolution Protocol (ARP) Cache . . . . . . . . . . . . . . . . . . . . 202Deleting a Host from the ARP Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203Adding a Host to the ARP Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Unix to Unix Communication Protocol (UUCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206Checking for UUCP Support Files and Directories. . . . . . . . . . . . . . . . . . . . . . . . . 206Cleaning Up UUCP Files in the Spool Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . 207Copying Files Using UUCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Listing All UUCP Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Viewing the UUCP Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Viewing UUCP Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

IntroductionThe NETWORK application monitors the network for information on

■ interfaces— names of all or individual networks— memory buffer

■ addresses— local and remote addresses— host name and corresponding IP Address

■ protocols— available protocols— protocol statistics

■ traffic— routing tables— number of incoming and outgoing packets — percentage of incoming and outgoing packets with errors

This application also lets you manage the network by providing you with some standard network utilities, which are accessible from within PATROL. Such management tasks include

■ copying or transferring files using either ftp or UUCP■ logging into remote machines using rlogin■ checking the availability of network resources using ping■ querying the network name server■ adding and deleting hosts from the Address Resolution Protocol cache


Object Hierarchy

Object HierarchyThe NETWORK application class contains the instances for networks that are being monitored. Each network instance contains parameters that gather information on packet traffic in and out of the network, on collisions, and on the percentage of errors in and out of the network.


Figure 31 NETWORK Application Object Hierarchy

OS container

Application class

Parameters

Instances

UNIX OS


Network Activation

Network ActivationThe NETWORK application and its corresponding collector, NETColl, are installed in an inactive state. They do not automatically gather information when loaded.

The NETWORK tasks related to activating and deactivating the NETWORK application class and NETColl collector parameter are described in detail on the following pages:

Activating the NETWORK Application Class

This task describes how activate the NETWORK application class and the NETColl collector parameter. This action causes PATROL to begin gathering information about the network and enables its network monitoring and managing features.

To Activate the NETWORK Application Class


2 Select Knowledge Module Admin => NETWORK Application => Activate Monitoring.

PATROL begins collecting data for the NETWORK application class.

Task Page

“Activating the NETWORK Application Class” 176

“Deactivating the NETWORK Application Class” 177

WARNING Use the same method to activate and deactivate application classes and their respective collectors.

For example, if you use another method to deactivate the NETWORK application class (such as customizing it with a PATROL Console in developer mode), attempting to activate it with the menu command, Knowledge Module Admin => NETWORK Application => Activate Monitoring, will fail.


Network Interface

Deactivating the NETWORK Application Class

This task describes how deactivate the NETWORK application class and the NETColl collector parameter. This action causes PATROL to quit gathering information about the network and disables its network monitoring and managing features.

To Deactivate the NETWORK Application Class


2 Select Knowledge Module Admin => NETWORK Application => Deactivate Monitoring.

PATROL quits collecting data for the NETWORK application class.

Network InterfaceThe NETWORK application class enables you to view a list of network interfaces available to you, discover the name of individual network interfaces, and get a report on the network’s memory buffer. You also can define the behavior of PATROL when a network interface is unavailable.

The NETWORK tasks related to the network interface are described in detail on the following pages:

Task Page

“Viewing a Network Interface” 178

“Discovering the Name of the Network Interface” 179

“Establishing Behavior When Unavailable” 180

“Viewing Memory Buffer Information” 181


Network Interface

Viewing a Network Interface

This task describes how to view the state of an automatically configured interface in a task window.

To View a Network Interface

1 Access the NETWORK application instance menu as described in “Accessing KM Commands and InfoBoxes” on page 402.

2 Select List Network Interface.

PATROL writes the results to a PATROL task object, List Network Interface, in the NETWORK container.

3 Access the List Network Interface task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

# PSL Serial No.: ##########

<NOT INTERACTIVE>

List network interface

Name Mtu Net/Dest Address Ipkts Ierrs Opkts Oerrs Collis Queuelo0 8232 loop localhost 73190 0 73190 0 0 0

hme0 1500 xyz.com xyz.com 386019 5200 14659 0 1810 0

-------------------- >>>>> DONE <<<<< --------------------


Network Interface

Output Format

The output has the following format. Table 34 defines each field.

Discovering the Name of the Network Interface

This task describes how to determine the name of the network interface.

To Discover the Name of the Network Interface

Access the NETWORK application instance InfoBox as described in “Accessing KM Commands and InfoBoxes” on page 402.

PATROL displays the NETWORK InfoBox (Figure 32 on page 180), which provides the name of the network interface in the Network Interface field.

Name Mtu Net/Dest Address Ipkts Ierrs Opkts Oerrs Collis Queue

-------------------- >>>>> DONE <<<<< --------------------

Table 34 List Network Interface Command Output Format

Field Description

Name name of the interface

Mtu maximum transmission unit also known as the maximum packet size

Net/Dest network to which the interface is attachedFor Point-to-Point interfaces, this is the address on the other side of the link.

Address address for each interface

Ipkts number of incoming packets

Ierrs number of incoming packets with errors

Opkts number of outgoing packets

Oerrs number of outgoing packets with errors

Collis number of collisions

Queue length of the queue


Network Interface

Figure 32 NETWORK InfoBox

Establishing Behavior When Unavailable

This task describes how to define the behavior of PATROL when the network goes down. You can instruct PATROL to place the NETWORK instance into a state of alarm or to destroy the icon of the NETWORK instance when the network interface goes down.


Network Interface

To Establish Network Interface Behavior


2 Select Toggle Alarm/Destroy if Down.

PATROL writes the results to the PATROL standard output window. Depending upon the NETWORK instances current setting, PATROL writes one of the following messages:

Set Alarm

Destroy the Instance and Remove the Icon

Viewing Memory Buffer Information

This task describes how to display memory management statistics in a task window. This information includes the current, maximum, and total amounts for streams, queues, mblk, dblk, linkblk, strevent, synq, and qband. It also provides the number of allocation failures for each category.

To View Memory Buffer Information


2 Select List Memory Buffer.

PATROL writes the results to a PATROL task object (List Memory Buffer) in the NETWORK container.

Set Alarm if the network is down

Destroy the network instance if the network is down

NOTE To reset the NETWORK to its previous behavior, repeat this procedure.


Network Interface

3 Access the List Memory Buffer task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

# PSL Serial No.: ##########<NOT INTERACTIVE>List network memory buffer streams allocation: current maximum cumulative

totalallocationfailures

streams 291 320 333447 0queues 824 858 869663 0mblk 1725 3683 448272 0dblk 1722 3760 74204701 0linkblk 12 169 55 0strevent 10 169 554502 0syncq 25 50 745 0qband 2 127 2 0

1439 Kbytes allocated for streams data-------------------- >>>>> DONE <<<<< --------------------


Network Interface

Output Format


streams 291 320 333447 0queues 824 858 869663 0mblk 1725 3683 448272 0dblk 1722 3760 74204701 0linkblk 12 169 55 0strevent 10 169 554502 0syncq 25 50 745 0qband 2 127 2 0-------------------- >>>>> DONE <<<<< --------------------

Table 35 List Memory Buffer Command Output Format

Field Description

streams streams

queues queues

mblk allocated streams message block headers

dblk data blocks

linkblk link blocks structures

strevent stream events

syncq number of messages

qband number of streams queue flow control information structures


Network Addresses

Network AddressesThe NETWORK application class enables you to view both the local and remote addresses for networked resources. It also provides a list of host names for each resource and its corresponding IP address.

The NETWORK tasks related to network addresses are described in detail on the following pages:

Viewing Network Addresses

This task describes how to view all the network addresses. Along with the local address, it provides the protocol version in use, the remote address, the sizes of the send window and send queue, the sizes of the receive window and receive queue, and the internal state of the address.

To View Network Addresses


2 Select List Network Addresses.

PATROL writes the results to a PATROL task object, List Network Addresses, in the NETWORK container.

Task Page

“Viewing Network Addresses” 184

“Listing Host and IP Address” 187


Network Addresses

3 Access the List Network Addresses task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

Output Format


# PSL Serial No.: ##########

<NOT INTERACTIVE>

List network address

TCP: IPv4

Local Address Remote Address Swind Send-Q Rwind Recv-Q State

-------------------- -------------------- ----- ------ ----- ------ -------

172.19.203.130.32785 172.19.203.130.32774 32768 0 32768 0 CLOSE_WAIT

127.0.0.1.32788 127.0.0.1.32783 32768 0 32768 0 ESTABLISHED

127.0.0.1.32783 127.0.0.1.32788 32768 0 32768 0 ESTABLISHED

127.0.0.1.32791 127.0.0.1.32790 32768 0 32768 0 ESTABLISHED

Active UNIX domain sockets

Address Type Vnode Conn Local Addr Remote Addr

30000b8fa08 stream-ord 30000a3d6e8 00000000 /tmp/.X11-unix/X0

30000b8fba8 stream-ord 00000000 00000000

30000b8fd48 stream-ord 30000b5a7f8 00000000 /tmp/jd_sockV6

TCP: IPv4

Local Address Remote Address Swind Send-Q Rwind Recv-Q State

...

Active UNIX domain sockets

Address Type Vnode Conn Local Addr Remote Addr

Table 36 List Network Addresses Command Output Format (Part 1 of 3)

Field Description

TCP the version of TCP/IP

Local Address local address expressed as a number

Remote Address remote address expressed as a number

Swind size of the send window in bytes

Send-Q the count of bytes not acknowledged by the remote host

Rwind size of the receive window in bytes

Recv-Q the count of bytes not copied by the user program connected to this socket


Network Addresses

State internal state of the socket

ESTABLISHED—established connection

SYN_SENT—actively attempting to establish a connection

SYN_RECV—being initialized.

FIN_WAIT1—closed, and the connection is shutting down

FIN_WAIT2—closed, and the socket is waiting for a shutdown from the remote end

TIME_WAIT—waiting after close for remote shutdown retransmission

CLOSED—not being used

CLOSE_WAIT—the remote end has shut down, waiting for the socket to close

LAST_ACK—the remote end shut down, the socket is closed, and waiting for acknowledgement

LISTEN—listening for incoming connections

CLOSING—both sockets are shut down but all the data sent has not been sent

UNKNOWN—state is unknown

Active Unix Domain Sockets

Address address of the socket


Field Description


Network Addresses

Listing Host and IP Address

This task describes how to view the name of a host and its corresponding IP address in the network.

To List Host and IP Addresses


2 Select TCP/IP => Reports => List Hosts.

PATROL writes the results to a PATROL task object (List Hosts) in the NETWORK container.

Type types of socket (values vary based on platform for instance stream may be represented as SOCKET_STREAM on Linux and Stream_ord on Solaris)

■ dgram—the socket is used in Datagram (connectionless) mode

■ stream—a stream (connection) socket■ raw—a raw socket■ rdm—serves reliably-delivered messages■ seqpacket—a sequential packet socket■ packet—a RAW interface access socket■ unknown—unable to identify socket type

Vnode virtual node

Conn connection type

Local Addr the local hostname and port number of the socket

Remote Addr remote address


Field Description


Network Addresses

3 Access the List Hosts task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

Output Format


# PSL Serial No.: #########

dyn2280234 1D IN A 172.19.89.227

dyn2280235 1D IN A 172.19.89.228

dyn2280236 1D IN A 172.19.89.229

dyn2280237 1D IN A 172.19.89.230

dyn2280238 1D IN A 172.19.89.231

--------------- >>>>> DONE <<<<< ---------------

hostname 1D IN A IP Address

-------------------- >>>>> DONE <<<<< --------------------

Table 37 List Hosts Command Output Format

Field Description

hostname the host’s alias

1D IN A information from the NIS map

IP Address ip address


Network Protocol

Network ProtocolThe NETWORK application class enables you to discover which protocols are currently running on the network and view protocol-specific statistics, such as the number of incoming datagrams for UDP, the number of failed attempts for TCP, and incoming deliveries for IPV4. It also provides you the ability to view the IP Address of an individual host.

The NETWORK tasks related to network protocols are described in detail on the following pages:

Listing Protocols Running on the Network

This task describes how to list which network protocols are running on the network.

To List Network Protocols


2 Select TCP/IP => Reports => List Protocols.

PATROL writes the results to a PATROL task object (List Protocols) in the NETWORK container.

Task Page

“Listing Protocols Running on the Network” 189

“Viewing Protocol Statistics” 191

“Determining the Network Internet Protocol Address” 191


Network Protocol

3 Access the List Protocols task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

Output Format


# PSL Serial No.: ##########<NOT INTERACTIVE>List TCP/IP protocols

NIS is detectedrdp 27 RDP # "reliable datagram" protocolxns-idp 22 XNS-IDP # Xerox NS IDPhmp 20 HMP # host monitoring protocoludp 17 UDP # user datagram protocolpup 12 PUP # PARC universal packet protocolegp 8 EGP # exterior gateway protocoltcp 6 TCP # transmission control protocolggp 3 GGP # gateway-gateway protocoligmp 2 IGMP # internet group management protocolicmp 1 ICMP # internet control message protocolip 0 IP # internet protocol, pseudo protocol number

-------------------- >>>>> DONE <<<<< --------------------

pt port PT comment

-------------------- >>>>> DONE <<<<< --------------------

Table 38 List Protocols Command Output Format

Field Description

pt protocol

port the port number on which the protocol is running

PT protocol

comment description of the protocol


Network Protocol

Viewing Protocol Statistics

This task displays the statistics for each protocol layer.

To View Protocol Statistics


2 Select Show Protocol Statistics.

PATROL writes the results to a PATROL task object (Show Protocol Statistics) in the NETWORK container.

3 Access the Show Protocol Statistics task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should list each protocol (RAWIP, UDP, TCP, IPV4, and so on) and provide per-protocol statistics.

Determining the Network Internet Protocol Address

This task describes how to determine the Network IP address.

To Determine the Network IP Address


PATROL displays the NETWORK InfoBox (Figure 32 on page 180), which provides the name to the network interface protocol address in the IP Address field.


Network Traffic

Network TrafficThe NETWORK application class enables you to view the network routing table. It also provides statistics on the volume of packet traffic going into and coming out of the network and gives the percentage of those packets that contain errors.

The NETWORK tasks related to network traffic are described in detail on the following pages:

Viewing the Routing Table

This task displays the routing table and statistics for the network. The information provided by the table includes a list of destination networks, the gateway for each, the router status and route designation, the number of active uses per route, the number of packets sent per route, and the network interface used by the route.

To View Routing Table Information


2 Select List Routing Table.

PATROL writes the results to a PATROL task object (List Routing Table) in the NETWORK container.

Task Page

“Viewing the Routing Table” 192

“Determining the Number of Packets Entering and Exiting the Network” 194

“Determining the Number of Packet Errors Entering and Exiting the Network”

194


Network Traffic

3 Access the List Routing Table task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

Output Format


# PSL Serial No.: ##########<NOT INTERACTIVE>List network routing table

Routing Table: IPv4

Destination Gateway Flags Ref Use Interfacebmt_r_and_s spyro U 1 1386 hme0BASE-ADDRESS.MCAST.NET

spyro U 1 0 hme0

default gate19 UG 1 1523localhost localhost UH 27 125281 lo0

-------------------- >>>>> DONE <<<<< --------------------

Routing Table: IPv4

Destination Gateway Flags Ref Use Interface

------------------ ----------------- ----- ---- ----- ---------

###.###.###.### xyz.com UGH 11 11 hme0

-------------------- >>>>> DONE <<<<< --------------------

Table 39 List Routing Table Command Output Format

Field Description

Destination the destination network

Gateway the router through which packets are forwarded

Flags U—the router is upG—the route is to a gatewayH—the destination is a host rather than a network

Ref number of active uses per route

Use number of packets sent per route

Interface the network interface that the route uses


Network Traffic

Determining the Number of Packets Entering and Exiting the Network

This task describes how to view the total number of packets going into and coming out of the network. These statistics reflect all packet traffic since the system was last rebooted.

To View the Number of Packets at the Moment


PATROL displays the NETWORK InfoBox (Figure 32 on page 180), which provides the statistics of incoming and outgoing packets in the Total Packets In and Total Packets Out fields.

To View the Number of Packets Over Time

1 Access a NETWORK application instance so that you can view its parameters.

2 Open the parameter that records the type of packet information that you want to view.


Determining the Number of Packet Errors Entering and Exiting the Network

This task describes how to view the percentage of packets that contain errors. The information is separated into packets coming into and going out of the network. These statistics reflect all packet traffic errors since the system was last rebooted.


NETPacketsIn displays the total number of incoming packets during the sample interval

NETPacketsOut displays the total number of outgoing packets during the sample interval


Network Traffic

To View the Number of Packet Errors at the Moment


PATROL displays the NETWORK InfoBox (Figure 32 on page 180), which provides the statistics of incoming and outgoing packets in the Total Outgoing Errors and Total Incoming Errors fields.

To View the Number of Packet Errors Over Time

1 Access a NETWORK application instance so that you can view its parameters.

2 Open the parameter that records the type of packet information that you want to view.



NETInErrPrc displays the percentage of incoming data packets that contain packet format errors

NETOutErrPrc displays the percentage of outgoing data packets that contain packet format errors


Network Management

Network ManagementThe NETWORK application class enables you to review some TCP/IP services running on the network, determine which hosts are trusted, and perform some standard network management tasks from within PATROL. These tasks include copying files to remote hosts, checking the availability of resources using ping, logging in remotely, and querying the network’s name server.

The NETWORK tasks related to network management are described in detail on the following pages:

Listing TCP/IP Services Running on the Network

This task describes how to create a list of all TCP/IP Services currently running on the network. It provides the name of the service, the port and protocol that the service uses, and any comments that were added when the service was registered.

To List Services Running on the Network


2 Select TCP/IP => Reports => List Services.

PATROL writes the results to a PATROL task object (List Services) in the NETWORK container.

Task Page

“Listing TCP/IP Services Running on the Network” 196

“Listing Trusted Hosts on the Network” 198

“Copying or Transferring Files by Using FTP” 198

“Checking for a Network Resource by Using ping” 199

“Logging In Remotely by Using rlogin” 200

“Querying the Name Server for the Network” 201


Network Management

3 Access the List Services task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

Output Format


# PSL Serial No.: ##########<NOT INTERACTIVE>List TCP/IP services

NIS is detected

example 2010/tcp # test port, Frank Ginacnbiff 1950/udpqip_qdhcp 1097/tcp #QIP DHCP Lease Update daemonDAServer 987/tcp # SQL distributed accesspmdmgr 696/tcp # OpenView Postmaster Managernew-rwho 550/udpnntp 119/tcp readnews untp # Network News Transfer Protocollink 87/tcp ttylinkftp 21/tcp # File Transfer Protocol (Control)uucp 540/tcp uucpd # uucp daemonname 42/tcp nameserver

-------------------- >>>>> DONE <<<<< --------------------

service port/prtcl # comments-------------------- >>>>> DONE <<<<< --------------------

Table 40 List Services Command Output Format

Field Description

service the name of the service

port/prtcl the assigned port number and communication protocol, which is either UDP or TCP

comment a description of the service or a reference to the individual or group that registered the service


Network Management

Listing Trusted Hosts on the Network

This task describes how to create a list of all trusted hosts currently running on the network. A trusted host is defined as a computer system that cannot be accessed illegally. These criteria are established by the National Computer Security Center (NCSC).

To List Services Running on the Network


2 Select TCP/IP => Reports => List Trusted Hosts.

PATROL writes the results to a PATROL task object (List Trusted Hosts) in the NETWORK container.

3 Access the List Trusted Hosts task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results.

Copying or Transferring Files by Using FTP

This task describes how to use the File Transfer Protocol utility to copy files from one system to another within PATROL.

Before You Begin

PATROL supports the following FTP commands, which are grouped by type.

FTP Command Description

open, close connect to and disconnect from a remote computer

quit, bye log off

help list all the supported ftp functions

bin, ASCII binary and ASCII transfer formats

get, mget retrieve one or multiple files from the remote system

put, mput place one or multiple files on the remote system

ls, dir list file names only or with file property information

cd, lcd change directories within the network or only locally

mkdir, rmdir make or remove directory

pwd print working directory


Network Management

To Transfer Files to a Remote Computer


2 Select TCP/IP => Utilities => Ftp.

PATROL opens the PATROL Ftp dialog box, which provides a command prompt.

3 Type open hostname to connect to a remote host.

The ftp utility prompts you for a username and password.

4 Set the data transfer format by typing either ASCII or bin.

5 Navigate to the desired directory (cd, pwd, ls) and transfer files to (put, mput) or from (get, mget) the remote computer.

The ftp utility provides feedback on the success of each command that you enter.

6 When you are done, type close to disconnect, and then type bye or quit to log off.

PATROL closes the PATROL Ftp dialog box.

Checking for a Network Resource by Using ping

This task describes how to use the ping utility to check if a network resource is available.

To Ping a Remote Computer on the Network


2 Select TCP/IP => Utilities => Ping.

PATROL displays the Ping dialog box (Figure 33).

Figure 33 Ping Dialog Box


Network Management

3 Type the computer name in the Enter machine name field and click Apply.

PATROL writes the results to a PATROL task object (Ping) in the NETWORK container.

4 Access the Ping task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

Logging In Remotely by Using rlogin

This task describes how to use the rlogin utility within PATROL to logon a remote computer.

To Logon a Remote Computer on the Network


2 Select TCP/IP => Utilities => Rlogin.

PATROL displays the Rlogin dialog box (Figure 34).

Figure 34 Rlogin Dialog Box

3 Type the computer name in the Enter machine name field and click Apply.

PATROL writes the results to a PATROL task object (Rlogin) in the NETWORK container.

4 Access the Rlogin task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results.

Ping to Paris_database_server Paris_database_server is alive-------------------- >>>>> DONE <<<<< --------------------


Address Resolution Protocol (ARP)

Querying the Name Server for the Network

This task describes how to query the name server from within PATROL.

To Query the Name Server for the Network


2 Select TCP/IP => Utilities => Query Name Server.

PATROL displays the PATROL Query Name Server dialog box with a command prompt.

Address Resolution Protocol (ARP)The Address Resolution Protocol (ARP) is a TCP/IP protocol that is used to obtain a network node’s physical address. ARP operates at layers 2 (Data Link) and 3 (Network) of the Open Systems Interconnection (OSI) model. The physical address, also referred to as the Machine Access Control (MAC) address, is the unique serial number that identifies one network card from another.

The network maintains a list of devices, IP addresses, and physical addresses in the ARP cache. With the NETWORK KM, you can view the ARP cache and add or delete resources (computers, printers, routers, anything with a network card) from it.

The NETWORK tasks related to Address Resolution Protocol (ARP) are described in detail on the following pages:

Task Page

“Viewing the Address Resolution Protocol (ARP) Cache” 202

“Deleting a Host from the ARP Cache” 203

“Adding a Host to the ARP Cache” 205



Viewing the Address Resolution Protocol (ARP) Cache

This task describes how to view the Address Resolution Protocol (ARP) cache, which consists of the Internet-to-Ethernet address translation tables. ARP is a TCP/IP protocol used to obtain a network node’s physical address (the Machine Access Control address). The ARP cache is a list of each network device, its IP address, mask, and physical address.

To View the ARP Cache


2 Select TCP/IP => Utilities => ARP => Show ARP cache.

PATROL writes the results to a PATROL task object (Show ARP Cache) in the NETWORK container.

3 Access the Show ARP Cache task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

# PSL Serial No.: ##########<NOT INTERACTIVE>Net to Media Table: IPv4

Device IP Address Mask Flags Phys Addrhme0 starbelly01 255.255.255.255 00:10:4b:39:a5:d3hme0 catnhat05 255.255.255.255 00:06:5b:ee:23:c8hme0 sneetch 255.255.255.255 00:03:47:06:dd:1fhme0 spot 255.255.255.255 02:60:6d:21:12:8chme0 javaweb 255.255.255.255 00:50:8b:f4:fd:66hme0 gate19 255.255.255.255 00:00:0c:07:ac:13hme0 bluefish 255.255.255.255 08:00:20:a2:90:68hme0 redfish 255.255.255.255 00:10:4b:39:40:77hme0 greenegg 255.255.255.255 00:d0:b7:b1:21:59hme0 BASE-ADDRESS.MCAST.NET 240.0.0.0 SM 01:00:5e:00:00:00

-------------------- >>>>> DONE <<<<< --------------------



Output Format


Deleting a Host from the ARP Cache

This task describes how to delete a host (resource) from the Address Resolution Protocol (ARP) cache.

Before You Begin

You must be root to run this command.

Device IP Address Mask Flags Phys Addr

----- -------------------- --------------- ----- ---------------

hme0 meridian.xyz.com 255.255.255.255 p 01:00:b2:83:8c:5b

Table 41 Show ARP Cache Command Output Format

Field Description

Device device name assigned to the physical address

IPAddress the numerical address or its text string alias

Mask subnet mask

Flags P—publish, includes IP address for the machine and the addresses that have been explicitly added using the Add Host to Cache (arp -s) option

S—static, not learned for the ARP protocol

U—unresolved, waiting for ARP response

M—mapping, only used for multicast entry for 224.0.0.0

Phys Address the physical address, also known as the Machine Access Control (MAC) address



To Delete a Host from the ARP Cache


2 Select TCP/IP => Utilities => ARP => Delete Host From Cache.

PATROL displays the Delete Host From Cache dialog box (Figure 35).

Figure 35 Delete Host from Cache Dialog Box

3 Type the computer name in the Enter host name field and click Apply.

PATROL prompts you for the password for the root account (Figure 36).

Figure 36 Delete Host From Cache Confirmation Dialog Box

4 Type the root password and click OK.

PATROL writes the results to the PATROL standard output window. Your results should resemble this example:

CCYYMMDDHHMMSS Dallas_email_server (255.255.255.255) deleted



Adding a Host to the ARP Cache

This task describes how to add a host (resource) to the Address Resolution Protocol (ARP) cache.

To Add a Host to the ARP Cache


2 Select TCP/IP => Utilities => ARP => Add Host To Cache.

PATROL displays the Add Host From Cache dialog box (Figure 37).

Figure 37 Add Host To Cache Dialog Box

3 Type the computer name in the Enter host name field and click Apply.

PATROL writes the results to the PATROL standard output window. Your results should resemble this example:

CCYYMMDDHHMMSS Add Dallas_email_server to ARP Cache


Unix to Unix Communication Protocol (UUCP)

Unix to Unix Communication Protocol (UUCP)Unix to Unix Communication Protocol (UUCP) is a Unix utility that copies a file from one computer to another. Unlike TCP/IP, which is a routable communications protocol, UUCP provides a point-to-point transmission where a user at one Unix computer dials up and establishes a session with another Unix computer.

UUCP can be used to send e-mail using a bang path, which specifies the entire route to the destination computer and uses exclamation points (!), also known as bangs, as delimiters. The bang path format is generally: host_n!host_2!host_1!user_account.

The NETWORK tasks related to UUCP are described in detail on the following pages:

Checking for UUCP Support Files and Directories

This task describes how to verify the presence of the files and directories that UUCP requires.

Before You Begin


To Check for UUCP Support Files and Directories


2 Select UUCP => Utilities => UUCP Check.

PATROL prompts you for the password for the root account.

Task Page

“Checking for UUCP Support Files and Directories” 206

“Cleaning Up UUCP Files in the Spool Directory” 207

“Copying Files Using UUCP” 208

“Listing All UUCP Servers” 210

“Viewing the UUCP Log File” 210

“Viewing UUCP Statistics” 211




PATROL writes the results to a PATROL task object (UUCP Check) in the NETWORK container.

4 Access the UUCP Check task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results.

Cleaning Up UUCP Files in the Spool Directory

This task describes how to delete all the files in the spool directory.

Before You Begin


To Delete Files in the Spool Directory


2 Select UUCP => Utilities => UUCP Clean.



PATROL writes the results to a PATROL task object (UUCP Clean) in the NETWORK container.

4 Access the UUCP Clean task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results.

NOTE This task is not supported on SOLARIS systems.



Copying Files Using UUCP

This task describes how to copy files using UUCP.

Before You Begin


To Copy Files


2 Select UUCP => Utilities => UUCP.

PATROL displays the UUCP dialog box (Figure 38).

Figure 38 UUCP Dialog Box

3 Specify what file you want to copy, how you want it copied, and where you want it copied.

Enter options—the copy options control how the copy/transfer is performed, provide for user notification via mail, and provide job statistics as well as debug information

Options Description

-c do not copy local file to the spool directory for transfer to a remote machine (default)

-C copy local file to spool directory for transfer

-d make all necessary directories for the file copy (default)

-f do not make intermediate directories for the file copy



Enter source—the full pathname of the file to be copied

Enter destination—the full pathname to where you want the file copied; it can be a file or a directory

4 Click Apply.



PATROL writes the results to a PATROL task object (UUCP) in the NETWORK container.

6 Access the UUCP task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results.

-gx assign a service grade, x, which is the priority of the data transfer

You must use the uuglist command to determine the appropriate format (single letter, number, or alphanumeric string) for the service grade

-j print the uucp job identification string on standard output

-m notify, via mail, the user who initiated the transfer that it is complete

-nuser notify, via mail, user when the file transfer is complete

-r place the job in the file transfer queue but do not start the transfer

-sfile send transfer status to file (full pathname)

-xn set debug level n (0-9); the higher the number the more detail debug information is provided

Options Description



Listing All UUCP Servers

This task describes how to generate a list of all the hosts known to UUCP.

To List All UUCP Servers


2 Select UUCP => Reports => List Server Name.

PATROL writes the results to a PATROL task object (List Server Name) in the NETWORK container.

3 Access the List Server Name task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results.

Viewing the UUCP Log File

This task describes how to view the UUCP log file.

To Display the UUCP Log File


2 Select UUCP => Reports => Show Log.

PATROL writes the results to a PATROL task object (Show Log) in the NETWORK container.

3 Access the Show Log task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results.



Viewing UUCP Statistics

This task describes how to display information about the UUCP requests.

To Display UUCP Statistics


2 Select UUCP => Reports => Show Statistics.

PATROL writes the results to a PATROL task object (Show Statistics) in the NETWORK container.

3 Access the Show Statistics task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results.


C h a p t e r 12
12 Monitoring Network File Systems
The PATROL Knowledge Module for Unix and Linux gives you the ability to monitor various network components. The Network File System (NFS) provides you with an abstract view of the entire file system, regardless of the various systems’ architectures and operating systems. With the Network Information Service (NIS), you can look up resources distributed throughout the network. The following sections appear in this chapter.

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Network File System (NFS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Viewing Network File System (NFS) Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Resetting Network File System Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Network Information System (NIS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Viewing Network Information System Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . 218Viewing Network Information System Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Viewing Network Information System Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . 220


Introduction

IntroductionTogether with TCP/IP, the Network File System (NFS) and the Network Information Service (NIS) construct the network on Unix.

■ In a heterogeneous environment, with NFS you can bind various file systems together, regardless of architecture and operating system. It presents the file system to the network as a uniform file hierarchy.

■ Formerly known as Yellow Pages, NIS provides a distributed lookup service that you can use to locate resources anywhere in the network.

The NFS application class monitors these services and provides a means to gather information about which resources (servers, users, and groups) use or are used by these networking components.

Object HierarchyThe NFS application class contains several parameters with information about network file system activity.



Object Hierarchy

Figure 39 NFS Application Object Hierarchy


Network File System (NFS)

Network File System (NFS)NFS works by imposing an abstract model of a file system on all file systems. For each operating system, the NFS model is translated into the local file system commands. For example, a list directory contents command, ls, issued from a Unix machine with a DOS file system mounted on it, is translated to a dir command on the DOS node.

With the NFS application class, you can monitor which servers are shared and can be mounted by other machines. You also can manage the NFS counters, resetting them to zero when necessary.

The NFS tasks that relate to the network file system are described in detail on the following pages:

Viewing Network File System (NFS) Servers

This task describes how to list which servers are Network File System servers. An NFS server is a server that makes its resources available for mounting by remote machines.

To View NFS Servers

1 Access the NFS application menu as described in “Accessing KM Commands and InfoBoxes” on page 402.

2 Select NFS => Reports => List Servers.

PATROL writes the list of servers to a PATROL task object, List Servers NFS.

3 Access the List Servers NFS task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

Task Page

“Viewing Network File System (NFS) Servers” 216

“Resetting Network File System Counters” 217

List NFS Server Houston_ivFlorida_iii--------------- >>>>> DONE <<<<< ---------------


Network File System (NFS)

Resetting Network File System Counters

This task describes how to reset or “zero out” the Network File System counters.

Before You Begin


To View NFS Servers


2 Select NFS => Zero NFS Counters.


Figure 40 NFS User Name Dialog Box

3 Supply the required information and click OK.

PATROL resets the NFS counters and issues an nfs_stat command. It writes the command’s output to the PATROL task object, Zero NFS Counters.

4 Access the Zero NFS Counters task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results.


Network Information System (NIS)

Network Information System (NIS)The Network Information System (NIS) works by distributing administrative databases, referred to as maps, throughout a network. Each domain has at least one map. These maps identify resources throughout the network and establish the resources’ level of accessibility.

With the NFS application class, you can determine which servers store NIS maps. You also can view which users and groups are available via NIS.

The NFS tasks that relate to NIS are described in detail on the following pages:

Viewing Network Information System Accounts

This task describes how to list Network Information System accounts.

To View NIS Accounts


2 Select NIS => Reports => List Accounts.

PATROL writes the list of accounts to the PATROL task object, List Accounts.

3 Access the List Accounts task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

Task Page

“Viewing Network Information System Accounts” 218

“Viewing Network Information System Groups” 219

“Viewing Network Information System Servers” 220

tjsmith:X7kxaNoUE5vlc:25507:180:T. John Smith,Krakow, Request by Tammy Rea,TERMINATED:/home/trea:/bin/falsepsellars:H0zXwymSHE4gQ:58196:501:Peter Sellars, Full, paris, NO_EMPNUM:/home/award:/bin/kshlpaulson:DcLKu6HBnjBi.:44444:111:Linus Paulson, , , :/home/lpaulson:/bin/kshedgas:YmlBKzznaP82s:2005:105:Edgar Gas,,:/home/edgas:/bin/ksh--------------- >>>>> DONE <<<<< ---------------



Output Format


Viewing Network Information System Groups

This task describes how to list Network Information System groups.

To View NIS Groups


2 Select NIS => Reports => List Groups.

PATROL writes the list of accounts to the PATROL task object, List Groups.

3 Access the List Groups task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results, which should resemble this example:

user name:password:accountid:seq:comments-------------------- >>>>> DONE <<<<< --------------------

Table 42 List of NIS Accounts Command Output Format

Field Description

user name the login name of the user

password encrypted password

accountid the account identifier, which has a maximum length of eight characters

seq the index of the account id in the group of valid accounts for the usernameZero (0) indicates that the account id is the default account for the user.

comments text comments added during the account creation process

houston:*:212:aabaal,mhartma

dallas:*:709:ccu,wfictes

portland:*:4001:bwinsier,jguaglia

montreal:*:1717:attack9,nmelcamp,vware,sgd,bbucca,package,skrishna

katmandu:*:111:cstevens

bayport:*:222:bayport

singapore:*:333:njudd,lvandros,jdean,spamar

paris:*:4444:oppp,mduchamp,mmarceau

--------------- >>>>> DONE <<<<< ---------------



Output Format


Viewing Network Information System Servers

This task describes how to list Network Information System servers, which is a server that maintains a set of NIS Maps for other servers to query.

To View NIS Servers


2 Select NIS => Reports => List Servers.

PATROL writes the list of accounts to the PATROL task object, List Servers.

3 Access the List Servers task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

group_name:password:###:member_1,member_2,member_X

-------------------- >>>>> DONE <<<<< --------------------

Table 43 List of NIS Groups Command Output Format

Field Description

group_name name of the NIS group

password encrypted passwordThe field is represented by an asterisk (*) and is usually left blank.

### numeric group ID (gid)

member_X list of user names of the members granted the privilege of groupMembers are separated by a comma (,).


<NOT INTERACTIVE>

Print NIS servers

zenith zenith

titan titan

xanadu xanadu

patois patois

--------------- >>>>> DONE <<<<< ---------------



Output Format


server_name NIS_map_key

-------------------- >>>>> DONE <<<<< --------------------

Table 44 List of NIS Groups Command Output Format

Field Description

server_name name of the NIS master server or NIS slave server

NIS_map_key the keys for those maps in which the values are null or the key is not part of the value


C h a p t e r 13
13 Monitoring and Managing Printers
The PATROL Knowledge Module for Unix and Linux gives you the ability to monitor and manage printers, print queues, and print jobs. The following sections appear in this chapter.

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224Printer Activation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Activating the PRINTER Application Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225Deactivating the PRINTER Application Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Printers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226Excluding a Printer from Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227Selecting Printers to Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227Viewing the Number of Print Jobs in a Printer’s Queue . . . . . . . . . . . . . . . . . . . . 228Stopping a Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228Starting a Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Print Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231Viewing All Print Jobs Assigned to a Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231Viewing All Print Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232Deleting a Print Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233Deleting All Print Jobs from a Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234Moving a Print Job to Another Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235Moving All Print Jobs to Another Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Print Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237Stopping a Print Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Starting a Print Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

NOTE At installation, the PRINTER application class is set to inactive. To activate the PRINTER application class and collect data for its parameters, see “Activating the PRINTER Application Class” on page 225.


Introduction

IntroductionThe PRINTER application monitors the printers on the system to determine how many jobs are waiting to be processed.

It also lets you manage printing functions from within PATROL. Some of the tasks that you can perform are

■ moving print jobs■ deleting print jobs■ starting and stopping printers■ starting and stopping print queues

Object HierarchyThe PRINTER application class contains an instance for each printer that is being monitored. Each printer instance contains a parameter that monitors the length of its respective print queue.


Figure 41 PRINTERS Application Object Hierarchy


Printer Activation

Printer ActivationThe PRINTER application and its corresponding collector, PRINTERColl, are installed in an inactive state. They do not automatically gather information when loaded.

The PRINTER tasks related to activating and deactivating the PRINTER application class and PRINTERColl collector parameter are described in detail on the following pages:

Activating the PRINTER Application Class

This task describes how to activate the PRINTER application class and the PRINTERColl collector parameter. This action causes PATROL to begin gathering information about the network and enables its network monitoring and managing features.

To Activate the PRINTER Application Class


2 Select Knowledge Module Admin => PRINTER Application => Activate Monitoring.

PATROL begins collecting data for the PRINTER application class.

Task Page

“Activating the PRINTER Application Class” 225

“Deactivating the PRINTER Application Class” 226

WARNING Use the same method to activate and deactivate application classes and their respective collectors.

For example, if you use another method to deactivate the PRINTER application class (such as customizing it with a PATROL Console in developer mode), attempting to activate it with the menu command, Knowledge Module Admin => PRINTER Application => Activate Monitoring, will fail.


Printers

Deactivating the PRINTER Application Class

This task describes how to deactivate the PRINTER application class and the PRINTERColl collector parameter. This action causes PATROL to quit gathering information about the network and disables its network monitoring and managing features.

To Deactivate the PRINTER Application Class


2 Select Knowledge Module Admin => PRINTER Application => Deactivate Monitoring.

PATROL quits collecting data for the PRINTER application class.

PrintersThe PRINTER application class enables you to monitor and manage individual printers. By default, PATROL monitors all printers on the system.

The PRINTER tasks related to printers are described in detail on the following pages:

Task Page

“Excluding a Printer from Monitoring” 227

“Selecting Printers to Monitor” 227

“Viewing the Number of Print Jobs in a Printer’s Queue” 228

“Stopping a Printer” 228

“Starting a Printer” 229


Printers

Excluding a Printer from Monitoring

This task describes how to stop monitoring a single printer.

Before You Begin

To perform this task, you must be in developer mode. If you attempt to stop monitoring a printer when in operator mode, PATROL displays the following error message in the system output window.

To Stop Monitoring a Printer

On the printer that you do not want to monitor, perform the following steps.

1 Access the PRINTER application menu as described in “Accessing KM Commands and InfoBoxes” on page 402.


PATROL removes the printer icon from the PATROL Object Hierarchy and stops monitoring the selected printer. To resume monitoring of the printer, see “Selecting Printers to Monitor” on page 227.

Selecting Printers to Monitor

This task describes how to determine which printers PATROL excludes from monitoring and how to resume monitoring printers that have been excluded from monitoring.

Before You Begin

■ By default, the PRINTER application class is inactive. Once you activate the PRINTER application class and collector, PATROL monitors all printers.

■ The exclusion list feature supports regular expressions. To stop monitoring large numbers of printers that have uniform names, use regular expressions.

■ To perform this task, you must be in developer mode. If you attempt to stop monitoring a printer when in operator mode, PATROL displays the following error message in the system output window.

PRINTER: Only Development Console can filter an instance



Printers

To Stop Monitoring Printers

On any printer instance, perform the following steps.


2 Select Edit PRINTER Exclusion List.

PATROL opens the PRINTER Exclusion List dialog box, which displays a list of monitored printers and a list of excluded printers.

3 In the Monitored Printers list box, select the name of the printer that you want to exclude from monitoring.

4 Click the right arrow to move the printer into the Exclued Printers list box

5 Click Apply.

PATROL adds the printer to the list of excluded printers and then removes the printer icon from the PATROL Object Hierarchy.

6 Repeat step 3 through step 5 for each printer that you want to exclude.

Viewing the Number of Print Jobs in a Printer’s Queue

This task describes how to view the total number of print jobs in a printer’s queue on the system.

To View the Total Number of Print Jobs in a Printer Queue

1 Access the PRINTER application so that you can view its parameters.

2 Open the PRNQLength parameter.

PATROL displays a gauge that shows the number of print jobs assigned to the printer’s queue.

Stopping a Printer

This task describes how to disable a selected printer so that the printer cannot process print jobs.


Printers

Before You Begin


■ Because the print manager will continue to add print jobs to the print queue while the printer is unavailable, use this command only if the printer will be unavailable for a short time. If the printer will be unavailable for long periods of time, stop the printer’s queue. For more information on this task, see “Stopping a Print Queue” on page 238 command.

To Stop a Printer

On the printer that you want to stop so that it cannot process any more print jobs, perform the following steps.


2 Select Stop Printer.


3 Type the password and click OK.

■ If the print queue is enabled when you stop the printer, PATROL changes the state of the PRINTER instance to ALARM.

■ If the print queue is disabled or stopped when you stop the printer, PATROL changes the state of the PRINTER instance to OFFLINE.

PATROL changes the printer icon to OFFLINE. To restart the printer from within PATROL, see “Starting a Printer” on page 229.

Starting a Printer

This task describes how to enable a selected printer so that the printer can process print jobs.

Before You Begin

■ You must be root to run this command.■ Make sure that the print queue associated with this printer is running.


Printers

To Start a Printer

On the printer that you want to start, perform the following steps.


2 Select Start Printer.



■ If the print queue is enabled or started when you start the printer, PATROL changes the state of the PRINTER instance to OK.

■ If the print queue is disabled or stopped when you start the printer, PATROL changes the state of the PRINTER instance to WARN.

PATROL changes the printer icon to OK and the printer begins processing any jobs that have collected in its queue. To stop the printer from within PATROL, see “Stopping a Printer” on page 228.


Print Jobs

Print JobsThe PRINTER application class enables you to monitor and manage print jobs. With this feature, you can delete and move print jobs from busy or out-of-service printers.

The tasks related to print jobs are described in detail on the following pages:

Viewing All Print Jobs Assigned to a Printer

This task describes how to view a list of all the print jobs assigned to a specific printer.

Before You Begin

■ To view a list of all print jobs owned by a particular user, see “Viewing Print Jobs that Belong to a User” on page 375.

■ To view a list of all print jobs assigned to a printer, see “Viewing All Print Jobs” on page 232

To View a List of Print Jobs Assigned to a Specific Printer

On the printer of whose jobs you want a list, perform the following steps.


2 Select List Print Jobs.

PATROL writes the information to a PATROL task object (List Print Jobs) in the UNIX OS container.

3 Access the List Print Jobs task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results.

Task Page

“Viewing All Print Jobs Assigned to a Printer” 231

“Viewing All Print Jobs” 232

“Deleting a Print Job” 233

“Deleting All Print Jobs from a Printer” 234

“Moving a Print Job to Another Printer” 235

“Moving All Print Jobs to Another Printer” 236


Print Jobs

Viewing All Print Jobs

This task describes how to view a list of all the print jobs on the system.

Before You Begin

■ To view a list of all print jobs owned by a particular user, see “Accessing KM Commands and InfoBoxes” on page 402.

■ To view a list of all print jobs assigned to a printer, see “Viewing All Print Jobs Assigned to a Printer” on page 231

To View a List of All Print Jobs

On any of the printers, perform the following steps.


2 Select List All Print Jobs.

PATROL writes the information to a PATROL task object (List All Print Jobs) in the UNIX OS container.

3 Access the List All Print Jobs task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

Output Format

The output has the following format. Table 45 on page 233 defines each field.

Display printer job list for all printer(s) lp4-0 lysander!root 182 MMM DD MM:SSlp4-3 wenchell!tmavis 4182 MMM DD MM:SSEpson2-1 logger!dpatel 3750 MMM DD MM:SSEpson2-3 sandhill!whill 005 MMM DD MM:SSEpson3-5 hp-dev!jjjones 7431 MMM DD MM:SS--------------------- >>>>> DONE <<<<< ---------------------

printer-# system_name!user job_# MMM DD MM:SS -------------------- >>>>> DONE <<<<< --------------------


Print Jobs

Deleting a Print Job

This task describes how to delete a print job from a print queue.

Before You Begin


■ To perform this task, you must be in developer mode. If you attempt to stop monitoring a printer when in operator mode, PATROL displays the following error message in the system output window.

To Delete a Print Job from a Printer

On the printer whose queue contains the print job that you want to delete, perform the following steps.


2 Select Delete Job.

PATROL displays the Delete Print Job dialog box (Figure 42).

Figure 42 Delete Print Job Dialog Box

Table 45 View All Print Jobs Command Output Format

Field Description

printer-# the printer to which the job is assigned and its position in the print queue

system_name!user the name of the system from which the print job originated and the user who created itThe exclamation point (!) is a delimiter.

job_# the print job ID number

MMM DD MM:SS the time at which the print job was created



Print Jobs

3 Type the print job number in the Enter Job ID field and click on Apply. To learn the number of a print job, see “Viewing All Print Jobs” on page 232.



PATROL deletes the print job.

Deleting All Print Jobs from a Printer

This task describes how to delete all print jobs from a printer’s queue.

Before You Begin


To Delete All Print Jobs from a Printer

On the printer from which you want to delete all jobs, perform the following steps.


2 Select Delete All Jobs.


Figure 43 Delete All Jobs Dialog Box


PATROL deletes all print jobs.


Print Jobs

Moving a Print Job to Another Printer

This task describes how to move a print job from one printer to another. This feature is useful when a printer is busy and you have a job that needs to run immediately.

Before You Begin


To Move a Print Job from One Printer to Another

On the printer whose queue contains the print job that you want to move, perform the following steps.


2 Select Move Job to Another Printer.

PATROL displays the Move Job to Another Printer dialog box (Figure 44).

Figure 44 Move Job to Another Printer Dialog Box

3 Type the print job number in the Enter Job Id field. To learn the number of a print job, see “Viewing All Print Jobs” on page 232.


Print Jobs

4 Type the name of the printer to which you want to move the job and click Apply.


Figure 45 Move Jobs To Another Printer Confirmation Dialog Box


PATROL moves the print job from the current printer to the designated printer.

Moving All Print Jobs to Another Printer

This task describes how to move all print jobs assigned to one printer to another printer. This feature is useful when a printer is offline.

Before You Begin


To Move All Print Jobs from One Printer to Another

On the printer whose jobs you want to move, perform the following steps.


2 Select Move All Jobs to Another Printer.

PATROL displays the Move All Jobs to Another Printer dialog box (Figure 46).

Figure 46 Move All Jobs to Another Printer Dialog Box


Print Queues

3 Type in the Enter New Destination field the name of the printer to which you want to move the job and click Apply.


Figure 47 Move Jobs To Another Printer Confirmation Dialog Box


PATROL moves all print jobs from the current printer to the designated printer.

Print QueuesThe PRINTER application class enables you to monitor and manage print queues. With this feature, you can start and stop queues so that the system print manager will not assign print jobs to printers that are down.

The PRINTER tasks related to print queues are described in detail on the following pages:

Task Page

“Stopping a Print Queue” 238

“Starting a Print Queue” 239


Print Queues

Stopping a Print Queue

This task describes how to disable a selected print queue so that the print manager does not assign any more jobs to it.

Before You Begin


■ Use this command if the printer will be unavailable for long periods of time. If the printer will only be unavailable for a short period of time, stop the printer. For more information on this task, see “Stopping a Printer” on page 228 command.

■ You can also disable spooling to this printer.

To Stop a Print Queue

On the printer whose queue you want to stop, perform the following steps.


2 Select Stop Queue.


3 Type the password and click on OK.

■ If the printer is enabled or online when you stop the print queue, PATROL changes the state of the PRINTER instance to WARN.

■ If the printer is disabled or stopped when you stop the print queue, PATROL changes the state of the PRINTER instance to OFFLINE.

To restart the print queue from within PATROL, see “Starting a Print Queue” on page 239.


Print Queues

Starting a Print Queue

This task describes how to enable a selected print queue so that the print manager can assign print jobs to it.

Before You Begin


To Start a Print Queue

On the printer whose queue you want to start, perform the following steps.


2 Select Start Queue.


3 Type the password and click on OK.

■ If the printer is enabled or online when you start the print queue, PATROL changes the state of the PRINTER instance to OK.

■ If the printer is disabled or stopped when you start the print queue, PATROL changes the state of the PRINTER instance to ALARM.

To stop a print queue from within PATROL, see “Stopping a Print Queue” on page 238.


Print Queues


C h a p t e r 14
14 Monitoring Processes
The PATROL Knowledge Module for Unix and Linux gives you the ability to monitor and manage processes on a system. The following sections appear in this chapter.

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Configuring Multiple Instances of a Process for Monitoring . . . . . . . . . . . . . . . . 247Configuring a Process to Alarm When the Number of Running Instances Exceeds

a Set Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250Configuring a Process to Alarm When the Number of Running Instances Falls

Below a Set Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253Configuring a Process to Restart When PATROL Detects It Has Stopped. . . . . 256Configuring a Process to Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259Configuring a Process to Alarm When Its Parent Process ID (PPID) is Not 1 . . 262Configuring a Process to Alarm When It is Owned by an Unauthorized User . 265Configuring a Process to Suspend Its Alert for N Cycles if Patrol Detects It is Not

Running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268Modifying the Configuration of a Monitored Process . . . . . . . . . . . . . . . . . . . . . . 270Monitoring Process Presence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274Deleting a Monitored Process from the Monitoring Queue . . . . . . . . . . . . . . . . . 278Specifying a Flag File Directory for Process Presence Blackout Periods. . . . . . . 278Suspending Process Monitoring for a Process Instance . . . . . . . . . . . . . . . . . . . . 280Resuming Process Monitoring for a Process Instance . . . . . . . . . . . . . . . . . . . . . . 280Reporting on a Selected Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Process Host Groups in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282Rules for Creating Process Host Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282Creating a Host Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283Configuring Communication Attributes for a Process Host Group . . . . . . . . . . 284Modifying Host Attributes within a Process Group . . . . . . . . . . . . . . . . . . . . . . . 285Removing a Host from a Host Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286Querying a Selected Host within a Process Host Group . . . . . . . . . . . . . . . . . . . . 286Synchronizing the Local Host’s List to a Selected Host’s List for a Process Host

Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288Synchronizing a Selected Host’s List to the Local Host List for a Process Host

Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288Viewing the Process List for a Selected Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289


Synchronizing the Local Process’s List with a Selected Process's List . . . . . . . . . 289Synchronizing a Selected Process's List with the Local Process's List . . . . . . . . . 290Viewing the Process Presence List for a Selected Process . . . . . . . . . . . . . . . . . . . 291

Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292Viewing the Number of Zombie Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292Viewing Zombie Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293Viewing the Total Number of Processes Running . . . . . . . . . . . . . . . . . . . . . . . . . 295Viewing Processes that Use Excessive CPU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295Viewing the Number of Processes Waiting on Resources . . . . . . . . . . . . . . . . . . . 298Viewing the Total Number of User Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298Viewing the Average Number of User Processes . . . . . . . . . . . . . . . . . . . . . . . . . . 299

Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299Reprioritizing a Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300Reprioritizing All Processes in a Process Group . . . . . . . . . . . . . . . . . . . . . . . . . . . 301Reprioritizing All Processes Owned by a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

Using the PATROL Configuration Manager to Configure the PATROL KM for Unix and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304Plug-in Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304Configuring the Process KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307


Introduction

IntroductionThe PATROL Knowledge Module for Unix and Linux monitors and manages processes through the PROCESS and PROCESS_PRESENCE applications and the Process KM Configuration Plug-in for the PATROL Configuration Manager (PCM).

With these application classes, you can

■ designate specific processes for monitoring■ review the overall status of processes on the system such as

— total number of processes— total number of zombie processes— list of all zombie processes— list of all processes consuming excessive CPU— total number of processes waiting for resources— total number of user (nonroot) processes— average number of processes per user

■ reprioritize process by— individual process— user ownership— process group membership

You can use the PROCESS_PRESENCE application class to monitor

■ a single process on a single computer

■ a local process across multiple computers within a process host group (this feature is helpful when you are monitoring processes in a clustered environment)

■ several running instances of a process on a single computer

■ several running instances of a process across multiple computers within a process host group (this feature is helpful when you are monitoring processes in a clustered environment)

You can manage a process by way of its PROCESS_PRESENCE instance to

■ restart a process that has stopped

■ stop a process

■ alarm when an unauthorized User ID owns a process

■ alarm when the number of processes running in a host group drops below a specified minimum number


Object Hierarchy

■ alarm when the number of processes running in a host group exceeds a specified maximum number

■ alarm when a process does not have a parent process ID (PPID) of 1 (a PPID of 1 indicates that a process is owned by init)

You can use the plug-in for PCM to configure process monitoring without using a console. See “Using the PATROL Configuration Manager to Configure the PATROL KM for Unix and Linux” on page 304 for details.

Object HierarchyThe PROCESS application class contains the PROCESS_PRESENCE application class and process parameters. The PROCESS_PRESENCE application class contains instances for individual processes that are being monitored at your request. Each instance contains parameters with information on the individual process’s memory and CPU usage.



Object Hierarchy

Figure 48 PROCESS Application Object Hierarchy

OS container

Application class

Parameters

PROCESS_PRESENCE classand

PROCESS_PRESENCE

PROCESS_PRESENCE

Instances

Parameters

UNIX OS


Processes

ProcessesThe PROCESS application class monitors processes on the operating system level by default and provides general information, such as averages and totals, for all processes running on a managed system. This feature enables you to designate specific processes for monitoring.

The PROCESS tasks that relate to individual processes are described in detail on the following pages:

Task Page

“Configuring Multiple Instances of a Process for Monitoring” 247

“Configuring a Process to Alarm When the Number of Running Instances Exceeds a Set Limit”

250

“Configuring a Process to Alarm When the Number of Running Instances Falls Below a Set Limit”

253

“Configuring a Process to Restart When PATROL Detects It Has Stopped” 256

“Configuring a Process to Stop” 259

“Configuring a Process to Alarm When Its Parent Process ID (PPID) is Not 1” 262

“Configuring a Process to Alarm When It is Owned by an Unauthorized User”

265

“Configuring a Process to Suspend Its Alert for N Cycles if Patrol Detects It is Not Running”

268

“Modifying the Configuration of a Monitored Process” 270

“Monitoring Process Presence” 274

“Deleting a Monitored Process from the Monitoring Queue” 278

“Specifying a Flag File Directory for Process Presence Blackout Periods” 278

“Suspending Process Monitoring for a Process Instance” 280

“Resuming Process Monitoring for a Process Instance” 280

“Reporting on a Selected Process” 280


Processes

Configuring Multiple Instances of a Process for Monitoring

This task describes how to configure PATROL to monitor multiple instances of a process.

1 Double-click the PROCESS application container.

2 Access the PROCESS_PRESENCE application menu as described in “Accessing KM Commands and InfoBoxes” on page 402.

3 Select Manage List of Monitored Processes from the pop-up menu.

The Manage List of Monitored Processes dialog box is displayed.

4 In the Actions group box, select Add New Process, and click OK.

The Add New Process dialog box is displayed.

5 In the Process Instance Label field, type a name for the monitored process icon.

6 In the Monitored Process String field, type the command or a unique command string for the process that is being monitored.

7 In the Minimum Count field, type a value to set the minimum number of process instances that must be running on the local computer or in the host group. To monitor multiple instances of the same process, this value must be set to 2 or above. If the number of running process instances falls below the value set in this field, PATROL will issue an alert.

8 In the Maximum Count field, type a value to set the maximum number of process instances that may be running on the local computer or in the host group. If the number of running process instances exceeds this value, PATROL will issue an alert. The value of the Maximum Count field must be greater than the value of the Minimum Count field.

NOTE ■ PATROL monitors all processes that match the string you type in this field.

When you enter text in this field, you may end up monitoring multiple processes. For example, if you type vi in this field, PATROL will monitor processes named vi, view, and previous.

■ You must specify a single process if you want to use the PATROL feature that allows you to restart a process automatically.


Processes

step 9 through step 18 are optional when you are configuring multiple instances of a process for monitoring. If you do not want to set values for the fields as indicated in these steps, you do not have to.

9 In the Acceptable Process Owners field, type the user IDs for the accounts that may own the process. Separate multiple user IDs with spaces.

10 Select the Parent Process ID Must Be 1 option button if the parent process ID (PPID) must be 1. A process with a PPID of 1 is owned by init, or the Unix scheduler.

11 Select the Restart Automatically option button if you want the KM to automatically restart a process when it detects that the process count is less than the set minimum.

If you select this option button, the KM will attempt to restart the process when it detects that the process instance count has fallen below the specified minimum threshold. The KM uses the value in the Command Execution Attempts field to determine how many times it will try to restart a process.

12 In the Execution Attempts field, type a value set the number of times the host will attempt to run a Start Process or Stop Process command before it stops trying to run the command.

13 In the Start Command field, type the command string that will start the process instance.

14 In the Stop Command field, type the command string that will stop the process instance.

15 In the Command Execution User Name field, type the user ID under which the command will be executed.

NOTE You must specify a start command and a command execution user name in the appropriate fields on this dialog box if you want PATROL to automatically restart a process.

NOTE You must specify a command execution user account and password if you want to use the Start command.



Processes

16 In the Command Execution Password field, type the password for the user ID under which the command will be executed. You can leave this field blank. The KM will accept a NULL value.

17 In the Alert Delay Count field, type a value to set the number of collection intervals that this host will defer an alert while it waits for the process count to be reestablished on a host or across a group of hosts.

If you delay the alert, the system has time to detect that a process has died and restart it automatically before PATROL issues an alarm.

18 Click the drop-down list button in the Alert State field and select the state change that will occur when the process count either falls below the minimum threshold or exceeds the maximum threshold and the alert delay count reaches 0. The state change will apply to the following parameters:

■ PROCPPCountCheck ■ PROCPPOwnerCheck ■ PROCPPParentID1

19 Select one of the following option buttons to indicate whether PATROL should monitor the process on one host computer, or across a group of hosts:

20 Click OK.

The dialog box closes, and the Manage List of Monitored Processes dialog box is displayed. The process that you just added to the monitored queue is listed in the Process List group box.

NOTE You must specify a command execution user account and password if you want to use the Start and Stop commands.


Option Description

Monitor Only On This Host

PATROL will only monitor the process on the selected local host computer.

Monitor Across Host Group

PATROL will monitor the process across a group of host computers. Select this option if you want to monitor a process in a clustered environment.


Processes

Configuring a Process to Alarm When the Number of Running Instances Exceeds a Set Limit

This task describes how to configure PATROL to alarm when the number of running instances for a process exceeds a set limit.







5 In the Blackout field, enter a blackout beginning and ending time (use 24-hour time).



8 In the Minimum Count field, type a value to set the minimum number of process instances that must be running on the local computer or in the host group. This field is optional.

9 In the Maximum Count field, type a value to set the maximum number of process instances that may be running on the local computer or in the host group. You must type a value of 1 or greater in this field in order for PATROL to alarm when the process instance count is exceeded. When the number of running process instances exceeds the value you type in this field, PATROL will issue an alert. The value of the Maximum Count field must be greater than the value of the Minimum Count field.

NOTE PATROL monitors all processes that match the string you type in this field. When you enter text in this field, you may end up monitoring multiple processes. For example, if you type vi in this field, PATROL will monitor processes named vi, view, and previous.


Processes

step 10 through step 19 are optional when you are configuring a process to alarm if the number of running instances exceeds a set limit. If you do not want to set values for the fields as indicated in these steps, you do not have to.

10 In the Acceptable Process Owners field, type the user IDs for the accounts that can own the process. Separate multiple user IDs with spaces.


12 Select the Restart Automatically option button if you want the KM to automatically restart a process when it detects that the process count is less than the set minimum threshold. The KM uses the value in the Command Execution Attempts field to determine how many times it will try to restart a process.

13 In the Execution Attempts field, type a value to set the number of times the host will attempt to run a Start Process or Stop Process command before it stops trying to run the command.




NOTE You must specify a start command and a command execution user name in this dialog box for PATROL to automatically restart a process.


NOTE You must specify a command execution user account and password if you want to use the Stop command.


Processes






20 Select one of the following option buttons to indicate whether PATROL should monitor the process on one host computer or across a group of hosts:

21 Click OK.




Option Description






Processes

Configuring a Process to Alarm When the Number of Running Instances Falls Below a Set Limit

This task describes how to configure PATROL to alarm when the number of running instances for a process falls below a set limit.









7 In the Minimum Count field, type a value to set the minimum number of process instances that must be running on the local computer or in the host group. If the number of running process instances falls below the value set in this field, PATROL will issue an alert.

step 8 through step 18 are optional if you are configuring a process to alarm when the number of running instances falls below a set limit. If you do not want to set values for the fields as indicated in these steps, you do not have to.





Processes













Processes








20 Click OK.



Option Description






Processes


Configuring a Process to Restart When PATROL Detects It Has Stopped

This task describes how to configure a process to restart if PATROL detects that it has stopped.









step 7 through step 10 are optional when you are configuring PATROL to restart a process. If you do not want to set values for the fields as indicated in these steps, you do not have to.





Processes









14 In the Stop Command field, type the command string that will stop the process instance. This field is optional if you are configuring PATROL to restart a process that has stopped.




Processes







20 Click OK.




Option Description






Processes

Configuring a Process to Stop

This task describes how to configure PATROL to stop a process. If the PATROL KM for Unix detects that the number of running process instances exceeds the value set in the Maximum Count field, and you have provided a command to stop the process in the Stop Command field, the KM will attempt to stop process instances until the number of running instances falls within the set threshold.









step 7 through step 13 are optional when you are configuring PATROL to stop a process. If you do not want to set values for the fields as indicated in these steps, you do not have to.






Processes







13 Leave the Start Command field blank.







Processes

step 17 and step 18 are optional if you are configuring PATROL to stop a process. If you do not want to set values for the fields as indicated in these steps, you do not have to.






20 Click OK.



Option Description






Processes

Configuring a Process to Alarm When Its Parent Process ID (PPID) is Not 1

This task describes how to configure PATROL to alarm when the parent process ID (PPID) for a process is not 1. A parent process ID of 1 indicates that a process is owned by init, or the Unix scheduler.









step 7 through step 9 are optional when you are configuring PATROL to alarm when the PPID for a process is not 1. If you do not want to set values for the fields as indicated in these steps, you do not have to.






Processes



10 Select the Parent Process ID Must Be 1 option button.

Step 11 through step 18 are optional when you are configuring PATROL to alarm when the PPID for a process is not 1. If you do not want to set values for the fields as indicated in these steps, you do not have to.










Processes







20 Click OK.



Option Description






Processes

Configuring a Process to Alarm When It is Owned by an Unauthorized User

This task describes how to configure PATROL to alarm when a process is owned by an unauthorized user.









step 7 and step 8 are optional when you are configuring PATROL to alarm when a process is owned by an unauthorized user. If you do not want to set values for the fields as indicated in these steps, you do not have to.






Processes




Step 11 through step 18 are optional when you are configuring PATROL to alarm when a process is owned by an unauthorized user. If you do not want to set values for the fields as indicated in these steps, you do not have to.









Processes







20 Click OK.




Option Description






Processes

Configuring a Process to Suspend Its Alert for N Cycles if Patrol Detects It is Not Running

This task describes how to configure a process to suspend its alert for a designated number of cycles when PATROL detects that the process is not running. This feature gives the system time to detect that a process has died and restart the process before PATROL issues an alarm. Delaying an alert also helps by giving the host group time to restart a process that died on an alternate host.









step 7 through step 17 are optional when you are configuring PATROL to delay an alert for a process that has died. If you do not want to set values for the fields as indicated in these steps, you do not have to.






Processes














Processes





20 Click OK.


Modifying the Configuration of a Monitored Process

This task describes how to modify the configuration of a monitored process.




Option Description






Processes



4 In the Process List group box, select the process you want to modify.

5 In the Actions group box, select Modify Selected Process, and click OK.

The Modify Selected Process dialog box is displayed.

Use the instructions in step 6 through step 19 to modify the monitoring attributes you would like to change.



8 In the Minimum Count field, type a value to set the minimum number of process instances that must be running on the local computer or in the host group. For example, if you want at least three instances of the process to run at all times, type 3 in this field. If the number of running process instances falls below this value, PATROL will issue an alert.








Processes













Processes





20 From the Monitoring Scope drop-down list, select whether you want PATROL to monitor the process on one host computer or across a group of hosts:

21 In the Blackout Period fields, enter a beginning and ending blackout time (use 24-hour clock).

22 Click OK.



Option Description

Only On This Host PATROL will only monitor the process on the selected local host computer.

Across Host Group PATROL will monitor the process across a group of host computers. Select this option if you want to monitor a process in a clustered environment.


Processes

Monitoring Process Presence

Process Presence monitoring is only available when using the Data Collection Manager (DCM) application and Perform Kernel Collector data collection.

To define Process Presence entries for PATROL for Unix and Linux

1 Drill down into the PROCESS container instance.

2 Select the PROCESS_PRESENCE icon and right-click to open its menu.

3 Select Manage List of Monitored Processes from the menu.

Using Regular Expressions to Monitor Process Presence

You can use regular expressions defined by the REGEXP standard (REGEX API) to monitor process presence. However, because regular expression matching requires significant overhead, you should minimize its use. For example, if you want to match CRM80DM without getting CRM89DMO, use CRM89DM[^O] for the definition.

NOTE If the DCM collector is in use, it can take a while to create the PROCESS instance after which there may be another wait for the PROCESS_PRESENCE container instance to be created. If the PATROL Script Language (PSL) data collector is in use, the PROCESS_PRESENCE container will not be created.


Processes

Agent Configuration Variables for Process Presence Monitoring

Table 46 contains descriptions of the variables used to monitor Process Presence.

Table 46 Variables for Monitoring Process Presence (Part 1 of 2)

Variable Description

/PUK/PROCCONT/daemonObjectList Created automatically. If deleted, it will be automatically recreated

Internal use only. PCM configuration is not recommended.

/PUK/PROCPRES/INSTANCE/info Defines individual processes to be monitored. The following instances are created by default: ==> amd, defined by the REGEXP standard (REGEX, bind, cron, sendmail, and ypbind. Mirrors all hosts in the host group if the monitoring scope is across all hosts.

When a new instance definition is discovered, a new PROCPRES instance is created and monitoring begins. Before using PCM to apply a configuration change to an existing definition, restart the Patrol Agent to reflect the change.

One per instance. PCM configuration is allowed.

PUK/Process/Default/Created Created automatically.


/UNIX/PROCCONT/processStamp Automatically created when you add a new process using the Manage List of Monitored Processes menu. If deleted, it is not recreated until the next use of Manage List of Monitored Processes to add another new process.



Processes

Using the /PUK/PROCPRES/INSTANCE/info Variable

Field definitions for the /PUK/PROCPRES/INSTANCE/info variable are closely aligned with the Add New Process dialog of Manage List of Monitored Processes menu option.

/UNIX/PROCCONT/nodeList Use of this option involves synchronization of several hosts and incorporates an encrypted password.

Created when

■ you choose the Manage Host Group menu option. Defines list of hosts in host group.

■ a host group is established and mirrored on all hosts added to the host group. Must be consistent across all hosts in the Group Host List. If this variable is deleted from one or more of the hosts:

— It is not automatically recreated.

— The host will not respond to requests from any of the other hosts in the host group.

— Attempts to use Synchronize=>Host Group will result in No Response.

— When a new process is added to one of the other nodes in the Group Host List that has Monitoring Scope set to Across All Hosts, the process definition is mirrored on the host. However, the group host list is not automatically mirrored.

PCM configuration is not recommended.

/UNIX/PROCCONT/nodeStamp Created when the Manage Host Group menu option is used to define a host group.

Internal use only. PCM configuration not recommended.

Process Instance Label label

Monitored Process String command string

Minimum Count 1

Table 46 Variables for Monitoring Process Presence (Part 2 of 2)

Variable Description


Processes

You can apply the following example ruleset can by using Patrol Configuration Manager or pconfig to define two processes (newproc1 and newproc2).

The field separator is CTRL-B. On a Unix system, use the vi editor to enter the CTRL-B character.

Be careful when you manually edit configuration entries. You may want to start with a configuration that was generated by KMs with Process Presence for PATROL for Unix. For example, use a ruleset captured from an existing configuration generated by using Process Presence to monitor KMs.

Using the /UNIX/PROCCONT/nodeList Variable

These are the field definitions for /UNIX/PROCCONT/nodeList variable. Do not use PCM or pconfig to apply this variable.

The node list consists of one or more nodes separated by the @ character. Each node specification consists of the hostname, port, username, and password fields separated by an * asterisk.

Maximum Count 1

Acceptable Process Owners blank

Parent Process ID Must Be 1 NO (YES = 1, NO = 2)

Restart Automatically NO (YES = 1, NO = 2)

Command Execution Attempts 5

Start Command blank

Stop Command blank

Command Execution User Name

blank

Command Execution Password blank

Alert Delay Count 1

Alert State ALARM (WARN = 1, ALARM = 2)

Monitoring Scope Only on This Host (Only on This Host = 1, Across Host Group = 2)

Blackout Period start 0 (Hours) 0 (Minutes)

Blackout Period end 0 (Hours) 0 (Minutes)

PATROL_CONFIG"/PUK/PROCPRES/newproc1/info" = { REPLACE = "newproc1^Bnewproc1^B1^B1^B^B2^B2^B5^B^B^B^B^B1^B2^B1^B0^B0^B0^B0" },"/PUK/PROCPRES/newproc2/info" = { REPLACE = "newproc2^Bnewproc2^B1^B1^B^B2^B2^B5^B^B^B^B^B1^B2^B1^B0^B0^B0^B0" }


Processes

The host1 value must be the local host which runs the Patrol Agent.

Deleting a Monitored Process from the Monitoring Queue

This task describes how to stop monitoring a process.





4 In the Process List group box, select the process you want to delete.

5 In the Actions group box, select Delete Selected Process, and click OK.

A confirmation message appears.

6 Click Yes to close the confirmation message.

The Manage List of Monitored Processes dialog box refreshes, and the process is removed from the list of monitored processes.

Specifying a Flag File Directory for Process Presence Blackout Periods

This task describes how to specify the directory that contains process presence flag files, and how to use those files as a resource external to the PATROL Agent for disabling the generation of state change alerts for the following parameters: PROCPPCountCheck, PROCPPOwnerCheck, PROCPParentPID1.

host1*portnumber*username*password@host2*portnumber*username*password@host3*portnumber*username*pasword@.


Processes

You can use flag files to create the equivalent of a PATROL “blackout” for specific process presence instances, suspending warnings and alarms during regular system maintenance. To create a “blackout period” for a process presence instance, move a flag file for the process presence instance into the designated flag file directory. When PATROL finds a flag file in the specified directory, it will ignore any alarms or warnings generated for the process.

Before You Begin

Before you identify the directory location, ensure that the following requirements are met for the flag file directory and the flag files.

The flag file directory must conform to the following standards:

■ the directory must exist on the system■ the PATROL Agent must have read permissions on the flag directory

Flag files must conform to the following standards:

■ flag files must reside in the designated flag file directory■ flag files must be named ignore_ProcessName, where ProcessName is the name

assigned to the monitored process

To Specify a Flag File Directory



3 Select Identify Flag Directory from the pop-up menu.

4 Type the full path of the flag file directory in the Enter Full Path field.

5 Click Apply.

NOTE Flag files do not expire after a specified time period. You must manually remove flag files from the specified flag file directory before PATROL will resume monitoring for a process presence instance.

NOTE Do not store flag files in the /tmp directory; many Unix systems automatically clear this directory upon system reboot.


Processes

Suspending Process Monitoring for a Process Instance

This task describes how to suspend process monitoring for a process instance.

Create a file ignore_ProcessName and copy it to the designated flag file directory.

Flag files must be named ignore_ProcessName, where ProcessName is the monitored process name. When the flag file is found in the designated directory, PATROL ignores alerts and events that are generated for the monitored process.

Resuming Process Monitoring for a Process Instance

This task describes how to resume monitoring of a process instance after process monitoring has been suspended.

To start monitoring the process again, remove the ignore_ProcessName file from the flag file directory.

Reporting on a Selected Process

This task describes how to run a report on a selected process.

To Report on a Selected Process





4 In the Process List group box, highlight the process for which you want to run a report.

NOTE Flag files do not expire after a specified time period. You must manually remove flag files from the specified flag file directory before PATROL will resume monitoring for a process presence instance.


Processes

5 In the Actions group box, select the Report on Selected Process option button, and click OK.

The Report on Process Name dialog box is displayed. This dialog box displays the monitoring attributes that were set for the process. In addition, the dialog box displays the number of process instances running on the local host, and the total number of process instances running within the host group.

6 Click Close.

The Report on Process Name dialog box closes, and the Manage List of Monitored Processes dialog box is displayed.


Process Host Groups in a Cluster

Process Host Groups in a ClusterThe PROCESS application class monitors processes in a clustered environment. PATROL allows you to define each cluster as a process host group. This feature enables you to monitor and manage a specific process within a group. For information on how to define a process host group, see “Rules for Creating Process Host Groups” on page 282.

The PROCESS tasks that relate to creating and managing Process Host Groups are described in detail on the following pages:

Rules for Creating Process Host Groups

You must follow these rules when you create a process host group:

■ The local host from which you are creating the group must be the first host added to the group. In other words, the PATROL Agent for the local host computer must be the first PATROL Agent added to the group.

■ Hosts may only be added to the group by a member of the host group. Any host within the group can add another member; you do not have to add all hosts from the original host.

■ A host computer may only belong to one group at a time.

Task Page

“Creating a Host Group” 283

“Configuring Communication Attributes for a Process Host Group” 284

“Modifying Host Attributes within a Process Group” 285

“Removing a Host from a Host Group” 286

“Querying a Selected Host within a Process Host Group” 286

“Synchronizing the Local Host’s List to a Selected Host’s List for a Process Host Group”

288

“Synchronizing a Selected Host’s List to the Local Host List for a Process Host Group”

288

“Viewing the Process List for a Selected Host” 289

“Synchronizing the Local Process’s List with a Selected Process's List” 289

“Synchronizing a Selected Process's List with the Local Process's List” 290

“Viewing the Process Presence List for a Selected Process” 291



Creating a Host Group

This task describes how to create a process host group.

Before You Begin

You must comply with the rules for creating process host groups.

To Create a Process Host Group



3 Select Manage Host Group from the pop-up menu.

The Manage Host Group dialog box is displayed.

4 In the Actions group box, select the Add option button and click OK.

The Add Host to Watched Hosts dialog box is displayed.

5 In the Host Name field, type the name of the host on which the PATROL Agent is installed and running.

6 In the Agent Port field, type the port number of the PATROL Agent that is installed on the host.

7 In the User Name field, type the user name for the PATROL Agent account that is installed on the host.

8 In the Password field, type the password for the PATROL Agent that is installed on the host.

9 Click Add.

The dialog box closes, and the Manage Host Group dialog box is displayed. The new host is listed in the Host Group Members group box.

10 Click Close to close the Manage Host Group dialog box.



Configuring Communication Attributes for a Process Host Group

This task describes how to configure the communication attributes for a process host group.



3 Select Synchronize => Group List from the pop-up menu.

The Synchronize Host List dialog box is displayed.

4 In the Summary of Group Lists group box, highlight a host.

5 Click the Configure Group Communication Options for host option button, and click OK.

The Group Process Monitor Configuration dialog box is displayed.

6 In the Timeout Group Communications After ___ Seconds field, type a value in the field to specify the number of seconds that the local host will wait for a response from a remote host. The valid range for this field is 1-60 seconds. The default value is 10 seconds.

7 In the Check Response of Group Every ___ Intervals field, type a value in the field to indicate the number of polling cycles that this host will allow to lapse between attempts to contact the PATROL Agent for each host within the group.

The valid range for this field is 0-99 intervals. The default value for this field is 0, which means that the host is not performing the check.

8 Select the Send Local Process Changes to Group option button to allow the PATROL Agent to propagate process presence instance changes for the local host to hosts within the group that are set up to receive local host changes from other members of the group.

NOTE In larger host groups, this check can consume a significant amount of system resources. Do not turn this feature on unless you need to use it.



9 Select the Accept Local Process Changes from Group option button to allow the PATROL Agent to receive process presence instance changes marked “local” from other hosts within the group that are set up to propagate changes to members of the host group.

10 Click OK.

The dialog box closes, and the communication setting for the group are changed.

Modifying Host Attributes within a Process Group

This task describes how to modify a host that is part of a process group.

Before You Begin

■ You can modify the following information about a host:

— Agent port number— User name— Password

■ You must comply with the rules for creating process host groups.

To Modify a Host within a Process Group





4 In the Host Group Members group box, highlight the host you want to modify.

5 In the Actions group box, select the Modify Selected Host option button and click OK.

The Modify Watched Hosts List dialog box is displayed.

6 In the Agent Port field, type the port number of the PATROL Agent that is installed on the host.



7 In the User Name field, type the user name for the PATROL Agent account that is installed on the host.

8 In the Password field, type the password for the PATROL Agent that is installed on the host.

9 Click Modify.

The dialog box closes, and the Manage Host Group dialog box is displayed. Changes to the PATROL Agent port number and account user name are displayed in the Host Group Members group box. PATROL does not display the password for the PATROL Agent.

10 Click Close to close the Manage Host Group dialog box.

Removing a Host from a Host Group

This task describes how to delete a host from a process host group.

To Delete a Host from a Process Group





4 In the Host Group Members group box, highlight the host you want to delete.

5 In the Actions group box, select the Delete Selected Host option button and click OK.

The dialog box refreshes, and the selected host is deleted from the Host Group Members group box.

Querying a Selected Host within a Process Host Group

This task describes how to run a query on a selected host within a process group.



To Query a Host within a Process Host Group





4 In the Host Group Members group box, highlight the host you want to query.

5 In the Actions group box, select the Query Selected Host option button and click OK.

The Status group box will display the following information:

■ local host name■ the last host that sent an update within the group■ the date and time that the last update was sent to the group■ whether or not the selected host responded when PATROL tried to query it■ the following diagnostic messages

— No session—displays when the host was unable to open a session on the remote PATROL Agent

— Event failed—displays when the session was opened on the remote PATROL Agent, but sending an event to the remote PATROL Agent failed

— No response—displays when the PATROL Agent timed out while waiting for a response to the event that was sent to the remote PATROL Agent

— Bad return data—displays when the message that is received seems to be from a PATROL Agent other than the one with which the session was opened

— Unknown OS type—displays when the PATROL Agent did not return a known OS type string

— Non-UNIX OS—displays when the remote PATROL Agent is not running on a supported Unix operating system

— OK—displays when the PATROL Agent responded correctly



Synchronizing the Local Host’s List to a Selected Host’s List for a Process Host Group

This task describes how to replace the local host list with the host list from the selected host. You can use this option to copy host group settings from the selected host to your local host.






5 Select the Replace Local Host List with Selected option button and click OK.

The dialog box refreshes, and the local host list is replaced with the information from the selected host list.

Synchronizing a Selected Host’s List to the Local Host List for a Process Host Group

This task describes how to replace the selected host list with the host list from the local host. You can use this option to copy host group settings from the local host to the selected host.






5 Select the Replace Selected Host List with Local option button and click OK.



The dialog box refreshes, and the selected host list is replaced with the information from the local host list.

Viewing the Process List for a Selected Host

This task describes how to view the list of hosts that are part of a selected host group.






5 Select the View Host List from Selected Host option button and click OK.

The Process Presence Host List for Host dialog box is displayed.

6 Click Close.

Synchronizing the Local Process’s List with a Selected Process's List

This task describes how to replace the process list for a local host with the process list on the selected host.

Before You Begin

If you want to receive changes that are marked as local and group, you must set up the local host to accept local process changes from members of the host group.



3 Select Synchronize => Process List from the pop-up menu.



The Synchronize Process List dialog box is displayed.

4 In the Summary of Process Lists group box, select a host name.

5 Click the Replace Local Process List with Selected option button and click OK.

The dialog box refreshes, and the process list for the local host is replaced by the process list for the selected host.

Synchronizing a Selected Process's List with the Local Process's List

This task describes how to replace the process list for a selected host with the process list on the selected host.

Before You Begin

If you want to receive changes that are marked as local and group, you must set up the selected host to accept local process changes from the group.




The Synchronize Process List dialog box is displayed.

4 In the Summary of Process Lists group box, select a host name.

5 Click the Replace Selected Process List with Local option button and click OK.

The dialog box refreshes, and the process list for the local host is replaced by the process list for the selected host.



Viewing the Process Presence List for a Selected Process

This task describes how to view the list of processes that are being monitored on a host group.





4 In the Summary of Process Lists group box, highlight a host.

5 Select the View Process List from Selected Host option button and click OK.

The Process Presence Process List for Host dialog box is displayed.

6 Click Close.


Status

StatusThe PROCESS application class enables you to monitor processes based on their status. This feature allows you to view which and how many processes are running on the system. It also enables you to view processes based on characteristics such as state and CPU usage.

The PROCESS tasks related to status are described in detail on the following pages:

Viewing the Number of Zombie Processes

This task describes how to view the total number of processes in Zombie state on the system at the present time or in the last couple of hours. PATROL identifies a zombie process as an ended process whose entry remains in the process table but is not assigned to a user or kernel space and does not consume any other resources. Processes in this state are also referred to as defunct processes.

To View the Number of Processes Now in Zombie Mode

Access the PROCESS application InfoBox as described in “Accessing KM Commands and InfoBoxes” on page 402.

PATROL displays the PROCESS InfoBox (Figure 49 on page 293), which provides the Number of processes in a Zombie state.

Task Page

“Viewing the Number of Zombie Processes” 292

“Viewing Zombie Processes” 293

“Viewing the Total Number of Processes Running” 295

“Viewing Processes that Use Excessive CPU” 295

“Viewing the Number of Processes Waiting on Resources” 298

“Viewing the Total Number of User Processes” 298

“Viewing the Average Number of User Processes” 299


Status

Figure 49 PROCESS InfoBox

To View the Number of Processes Recently in Zombie Mode

1 Access the PROCESS application class so that you can view its parameters.

2 Open the PROCNoZombies parameter.

PATROL displays a graph that shows the number of Zombie processes that occurred over the last couple of hours.

Viewing Zombie Processes

This task displays information about the zombie processes that persist on the system. PATROL identifies a zombie process as an ended process whose entry remains in the process table but is not assigned to a user or kernel space and does not consume any other resources. Processes in this state are also referred to as defunct processes.

To View Zombie Processes

1 Access the PROCESS application menu as described in “Accessing KM Commands and InfoBoxes” on page 402.

2 Select List Zombie Processes.

PATROL writes the information to a PATROL task object, List Zombie Processes, in the UNIX OS container.


Status

3 Access the List Zombie Processes task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

Output Format


# PSL Serial No.: #########<NOT INTERACTIVE> List zombie process 6933 6932 3Supvr Z 0 0 <defunct> ???---------------- >>>>> DONE <<<<< ----------------

pidppiduserssizecputcmd namecmd line

Table 47 List Zombie Process Command Output Format

Field Description

pid the process ID of the process

ppid the process ID of the parent process

user the name of the user that owns the process

s the status of the process

I—intermediate0—nonexistentR—runningS—sleepingT—stoppedW—waitingX—growingZ—zombie, terminated

size the total size of the process in virtual memory, in blocks

cmd name the first word of the command line that started the process

cmd line the complete command line (command and arguments up to 80 characters) that started the process; note that the command line can be modified during the process execution


Status

Viewing the Total Number of Processes Running

This task describes how to view the total number of processes running on the system at the present time or in the last couple of hours.

To View the Total Number of Processes Now Running

Access the PROCESS application InfoBox as described in “Accessing KM Commands and InfoBoxes” on page 402.

PATROL displays the PROCESS InfoBox, which provides the total number of processes running on the system at the present time.

To View the Total Number of Processes Recently Running


2 Open the PROCNumProcs parameter.

PATROL displays a graph that shows the total number of processes running on the system over the last couple of hours.

Viewing Processes that Use Excessive CPU

This task describes how to view the processes that use the most CPU. These processes are often referred to as CPU hogs. PATROL provides two methods to obtain this information.

Before You Begin

PATROL allows you to discover these CPU hogs by using a menu command or a parameter.

■ The menu command allows you to define “excessive CPU utilization” through a dialog box when you execute the command.

■ The parameter compares each processes’ CPU utilization against the other processes and lists the processes that consume the most CPU.

■ The cputhreshold value has a default value of 80 percent.


Status

To View the Processes that Use Excessive CPU as Defined by You


2 Select CPU Hogs.

PATROL displays the CPU Hogs dialog box (Figure 50).

Figure 50 CPU Hogs Dialog Box

3 Select the threshold by moving the slider bar to the right (maximum value of 100) or the left (minimum value of 0) and click Accept.

PATROL surveys the system for 30 seconds and then writes the information to a PATROL task object, CPU Hogs Process, in the UNIX OS container.

4 Access the CPU Hogs Process task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

# PSL Serial No.: #########<NOT INTERACTIVE> CPU Hogs collecting data for apprx. 30 seconds...Processes consuming at least 50% of CPU during this interval (30 sec.):PID CPU% USER CMD29111 73 3Suprv audit_script -I i18nInstance -MCPU Hogs complete---------------- >>>>> DONE <<<<< ----------------


Status

Output Format


To View the Processes that Consume the Most CPU

This parameter displays the 10 processes that consume the most CPU.


2 Open the PROCTopProcs parameter.

PATROL displays the information in a text parameter. Your result should resemble this example:

pid cpu% user cmd line

Table 48 CPU Hogs Command Output Format

Field Description


cpu% the percentage of CPU that the process consumed during the survey interval



# PSL Serial No.: #########%TIME PID PPID TOT SECS SIZE UID COMMAND0.00 0 0 18 0 root sched0.00 1 0 1 96 root /etc/init -0.00 2 0 0 0 root pageout0.00 3 0 588 0 root fsflush0.00 315 1 0 217 root /usr/lib/saf/sac

Last update: Thu Jun 14 12:50:27 CCYY Sample Period: 30 secs.


Status

Text Parameter Format


Viewing the Number of Processes Waiting on Resources

This task describes how to view the total number of processes on the system waiting for resources.

To View the Number of Processes Waiting for Resources


2 Open the PROCProcWait parameter.

PATROL displays a graph that shows the number of processes that are currently waiting for resources and have been over the last couple of hours.

Viewing the Total Number of User Processes

This task describes how to view the total number of user (non-root) processes running on the system.

%time pid ppid tot secs size uid command

Table 49 PROCTopProcs Text Parameter Format

Field Description

%time the percentage of cpu time that the process consumes



tot secs the total number of seconds the process consumed CPU resources


uid command the complete command line (command and arguments up to 80 characters) that started the process; note that the command line can be modified during the process execution


Priority

To View the Total Number of User (non-root) Processes Running on the System


2 Open the PROCUserProcs parameter.

PATROL displays a graph that shows the number of user (non-root) processes that are running on the system.

Viewing the Average Number of User Processes

This task describes how to view the average number of user (non-root) processes running on the system.

To View the Average Number of Processes Per User


2 Open the PROCAvgUsrProcs parameter.

PATROL displays a graph that shows the average number of processes running on the system per user.

PriorityThe PROCESS application class enables you to manage process execution priority based on the individual process, the owner of the process, and the group to which the process belongs. From within PATROL, it enables you to decrease a process’s priority.

The PROCESS tasks are described in detail on the following pages:

Task Page

“Reprioritizing a Process” 300

“Reprioritizing All Processes in a Process Group” 301

“Reprioritizing All Processes Owned by a User” 302


Priority

Reprioritizing a Process

This task describes how to reprioritize an individual process. Reprioritizing a process’s execution is commonly referred to as renicing. Priorities, or nice values, range from -20 (highest) to 20 (lowest: process will run when no other process attempts to run). To lower a process’s priority, you must raise its nice value. To raise a process’s priority you must lower its nice value.

Before You Begin

■ At a Unix command prompt, use the Unix list active processes command with the long option (ps -l) to find the process ID and current priority of the process whose execution priority you want to change. The execution priority, also referred to as the nice value, is stored in the NI column.

■ Only privilege users can decrease the nice value. Other users can only increase the nice value within the range 0 to 20.

To Reprioritize a Process


2 Select Renice Process.

PATROL displays the Renice Process dialog box (Figure 51).

Figure 51 Renice Process Dialog Box

3 Type the Process ID number in the Enter Process ID field.

4 Type an integer value for the amount you want to lower or raise the priority in the Enter Priority field of the dialog box. Negative values are valid.

The larger the number that you enter is, the lower the resulting priority of the process; the smaller the number is, the higher the priority.

EXAMPLE To raise the priority from 8 to 6, type a value of -2 in the Enter Priority field.


Priority

5 Click Apply.


Figure 52 Renice Process Confirmation Dialog Box

6 Enter the user name and password of the owner of the process or an account with privileges to reprioritize it, and click OK.

PATROL writes a confirmation message to the system output window. Your result should resemble this example:

Reprioritizing All Processes in a Process Group

This task describes how to reprioritize all processes that belong to a process group. Reprioritizing a process’s execution is commonly referred to as renicing. Priorities, or nice values, range from -20 (highest) to 20 (lowest: process will run when no other process attempts to run). To lower a process group’s priority, you must raise its nice value. To raise a process group’s priority you must lower its nice value.

Before You Begin

■ At a Unix command prompt, use the Unix list active processes command with the long j option (ps -lj) to find the group process ID and current priorities of the processes that belong to the group. The group ID is stored in the PGID column. The execution priority, also referred to as the nice value, is stored in the NI column.

■ Only privileged users can decrease the nice value. Other users can only increase the nice value within the range 0 to 20.

CCYY0614153103 PROCESS: Renice process 333 to priority: 6


Priority



2 Select Renice Group.

PATROL displays the Renice Group dialog box.

3 Type the Group ID number in the Enter Group ID field.



5 Click Apply.

PATROL prompts you for a user name and password.

6 Enter the user name and password of the owner of the group or an account with privileges to reprioritize it, and click OK.


Reprioritizing All Processes Owned by a User

This task describes how to reprioritize all processes that belong to a specific user. This task only decreases the execution priority of these processes. Reprioritizing a process’s execution is commonly referred to as renicing. Priorities, or nice values, range from -20 (highest) to 20 (lowest: process will run when no other process attempts to run). To lower a user’s process priority, you must raise its nice value. To raise a user’s process priority you must lower its nice value.

EXAMPLE To lower the priority from 8 to 10, type a value of 2 in the Enter Priority field.

CCYY0614153103 PROCESS: Renice group suprvizr to priority: 10


Priority

Before You Begin

■ At a Unix command prompt, use the Unix list active processes command with the long option (ps -l) to find the processes that belong to a specific user, indicated by user ID, and the current priorities of the processes that belong to the user. The user ID is stored in the UID column. The execution priority, also referred to as the nice value, is stored in the NI column.

■ Only privileged users can decrease the nice value. Other users can only increase the nice value within the range 0 to 20.



2 Select Renice User.

PATROL displays the Renice User dialog box.

3 Type the user ID number in the Enter User ID field.



5 Click Apply.

PATROL prompts you for a user name and password.

6 Enter the user name and password of the user or an account with privileges to reprioritize the process owned by the user, and click OK.


EXAMPLE To lower the priority from 10 to 15, type a value of 5 in the Enter Priority field.

CCYY0614153103 PROCESS: Renice user 3Supvr to priority: 15


Using the PATROL Configuration Manager to Configure the PATROL KM for Unix and Linux


The PATROL Configuration Manager includes the Process KM Configuration Plug-in that allows you to configure the Process KM to monitor specific processes. The plug-in provides three tabs. Each tab enables you to specify certain monitoring criteria.

■ The Process tab designates a process or processes to be monitored by the PATROL Knowledge Module for Unix.

■ The Start/Restart Options tab controls the number of instances of a process that is being monitored. You can configure the knowledge module to automatically stop an instance of a monitored process if it exceeds the maximum process count or automatically start a process if the number of process instances falls below the minimum count.

■ The Alert and Monitor Options tab specifies what type of alert is generated by the knowledge module and the time frame in which the alert is generated when the monitored process falls below the minimum count or rises above the maximum.

Plug-in Actions

The plug-ins interact with PATROL Configuration Manager based upon the task that you are performing. When adding rulesets to establish and configure monitoring, you use the Agent tree view pane. When updating or deleting rulesets, you use the RuleSets tree view pane.

Adding Object Instances to Monitor

Configuring PATROL to monitor some aspect of an application involves creating an instance for the object being monitored such as a process and establishing a ruleset. This procedure is initiated in the Agent tree view pane.

To Add an Object Instance

1 In the Agent tree view pane, select an agent by clicking on it.

2 Right-click the agent and select the plug-in and its option such as either Process KM Configuration => Processes.

The configuration manager displays a configuration dialog box.



3 Click Add.

The plug-in displays a dialog box for creating instances.

4 Type the required information in the appropriate fields, which are described in Table 50.

5 Click OK.

6 Select each tab and provide the relevant information in the configuration dialog box.

For more information about the Process KM Configuration dialog box, see “Configuring the Process KM” on page 307.

7 Click either Apply to save your changes and leave the dialog box open or OK to save the changes and close the dialog box.

Updating Monitored Object Instances

Changing how PATROL monitors some aspects of an application involves editing a ruleset. This procedure is initiated in the RuleSet tree view pane.

1 In the RuleSet tree view pane, expand the RuleSet folder.

2 Navigate to the backup ruleset of the agent whose object instance monitoring you want to update. Expand PCM => backup => backup_container => agent=> ccyymmdd-hhmmss_ruleset.

3 Right-click the ruleset and select the plug-in and its option such as either Process KM Configuration => Processes.

Table 50 New Instance Dialog Boxes and Fields

Fields Description

Process Instance

New Instance Label Type the name of the process as you want it to appear in PATROL

Monitored Process Type the process command of the process that you want to monitor

NOTE If no object instances have been added for monitoring, the menu command will be inactive. For more information about adding an object instance for monitoring, see “Adding Object Instances to Monitor” on page 304.




4 Select one instance from the instance list and click Update.

5 Select the appropriate tab and edit the relevant information in the configuration dialog box.

For more information about the Process KM Configuration dialog box, see “Configuring the Process KM” on page 307.

6 Click either Apply to save your changes and leave the dialog box open or OK to save the changes and close the dialog box.

Deleting Monitored Object Instances

Stopping PATROL from monitoring some aspects of an application involves deleting a ruleset. This procedure is initiated in the RuleSet tree view pane.

1 In the RuleSet tree view pane, expand the RuleSet folder.

2 Navigate to the backup ruleset of the agent whose object instance monitoring that you want to update. Expand PCM => backup => backup_container => agent=> ccyymmdd-hhmmss_ruleset.

3 Right-click the ruleset and select the plug-in and its option such as either Process KM Configuration => Processes.


4 Select one instance from the instance list.

5 Click Delete.

6 Click either Apply to save the deletion and leave the dialog box open or OK to save the deletion and close the dialog box.

NOTE If no object instances have been added for monitoring, the menu command will be inactive. For more information about adding an object instance for monitoring, see “Adding Object Instances to Monitor” on page 304.



Configuring the Process KM

Before You Begin

You must have setup a PATROL object to monitor a process.

To Configure Process Monitoring from PATROL Configuration Manager

1 Add a new PATROL object instance to monitor a process as described in “Adding Object Instances to Monitor” on page 304 or select a ruleset created to monitor a process as described in “Updating Monitored Object Instances” on page 305.

2 Select an Instance from the Process Instance List.

3 Select the Process tab and specify how many process instances should run simultaneously and who can own the process. Table 51 describes the process properties used to define the criteria.

Table 51 Process tab properties (Part 1 of 2)

Field Description

Process Instance List Lists the processes being monitored; provides both the process name and the user-defined label by which PATROL applications refer to it

Process Instance Label Type a name for the monitored process instance icon in this field.

Monitored Process String Type the command or unique command string for the process that is being monitored

PATROL monitors all processes that match the string you type in this field. When you enter text in this field, you may end up monitoring multiple processes. For example, if you type vi in this field, PATROL will monitor processes named vi, view, and previous.

Minimum Count Use the spinner buttons, or type a value in this field to set the minimum number of process instances that may be running on the local computer or in the host group.

Maximum Count Use the spinner buttons, or type a value in this field to set the maximum number of process instances that may be running on the local computer or in the host group.

The value in the Maximum Count field must be equal to or greater than the value in the Minimum Count field.



4 Select the Start/Restart Options tab and specify if a process should be restarted automatically, commands for starting and stopping a process, and credentials for accounts to start and stop passwords. Table 52 describes the process properties used to define the criteria.

Acceptable Process Owners Type the user IDs of all acceptable process owners in this field; separate multiple user IDs with spaces.

Parent Process ID Must Be 1 From the drop list, select one of the following options:

Yes - indicates that the parent process ID (PPID) for the process must be 1. (Processes with a PPID of 1 are owned by init, or the Unix scheduler).

No – indicates that the parent process ID can be a number other than 1.

Table 52 Start/Restart tab properties (Part 1 of 2)

Field Description

Restart Automatically From the drop list, select one of the following options:

Yes—indicates that the process will be restarted automatically if PATROL detects it has stopped.

If you select this option, the PATROL KM for Unix will attempt to restart the process when it detects that the process instance count has fallen below the specified minimum threshold. The KM uses the value in the Command Execution Attempts field to determine how many times it will try to restart a process. Note: To restart a process automatically, you must provide a start command and a command execution account user name and password in the appropriate fields on this dialog box.

No—indicates that the process must be restarted manually if it stops.

Command Execution Attempts

Type a value in this field to set the number of times the host will attempt to run a Start Process or Stop Process command before it stops trying to run the command.

The value that you enter in this field must be a 1 or greater.

Start Command Type the command string that will start the process instance.

You must specify a command execution user account and password if you want to use the Start command.

Table 51 Process tab properties (Part 2 of 2)

Field Description



5 Select the Alert and Monitor Options tab and specify the location of the processes running and the conditions under which an alert is issued. Table 53 describes the process properties used to define the criteria.

Stop Command Type the command string that will stop the process instance.

You must specify a command execution user account and password if you want to use the Stop command.

Command Execution User Name

Type the user ID under which the command will be executed.

You must specify a command execution user account and password if you want to use the Start and Stop commands.

Command Execution Password

Type the password for the user ID under which the command will be executed. You can leave this field blank; the KM will accept a null password.

You must specify a command execution user account and password if you want to use the Start and Stop commands.

Table 53 Alert and Monitor (Part 1 of 2)

Field Description

Alert Delay Count Select a value in this field to set the number of collection intervals that this computer will defer an alert while it waits for the process count to be reestablished across the host or group.

Delaying the initial alert allows the system to correct a situation without generating an event to notify you that there is a problem.

Alert State From the drop list select a state (ALARM or WARNING) change for the following parameters:

PROCPPCountCheckPROCPPCountCheck_parameterPROCPPOwnerCheckPROCPPOwnerCheck_parameterPROCPPParentPID1PROCPPParentPID1_parameter

PATROL sets these parameter to the selected state when the Action Deferral Count reaches zero and the process count across the range is out of range.

Table 52 Start/Restart tab properties (Part 2 of 2)

Field Description



6 Click Apply to save the settings.

7 Click OK.

PATROL Configuration Manager saves your changes and closes the dialog box.

8 Apply the configuration changes.

■ If you are adding a new object instance for monitoring (working in the Agent tree view pane), click the Apply button to apply the ruleset and begin monitoring.

■ If you are updating an object instance for monitoring, (working in the RuleSet tree view pane) assign the updated rulesets to the desired agent(s), and then click the Apply button to apply the ruleset and begin monitoring with the new settings.

Scope From the drop list, select one of the following options to specify whether the process should be monitored on one computer or across a computer host group:

Only on this Host—indicates that PATROL should only monitor the process on the local host computer

Across Host Group—indicates that PATROL should monitor the process across the entire host group

Blackout Period You have the option of setting a blackout period during which you do not want to monitor the selected process.

To set the blackout period:

In the Start drop boxes, enter the time (in 24-hour clock format) to begin the blackout period in hours (first drop list) and minutes (second drop list).

In the End drop boxes, enter the time that you want the blackout period to end in hours (first drop list) and minutes (second drop list).

For example, if you wanted the blackout period to occur between 11:00 PM and 5:00 AM, in the Start fields you would enter 23 and 00. In the End fields you would enter 05 and 00.

Table 53 Alert and Monitor (Part 2 of 2)

Field Description


C h a p t e r 15
15 Scheduling Tasks
The PATROL Knowledge Module for Unix and Linux gives you the ability to schedule processes and to schedule monitoring blackout periods in your environment.The following sections appear in this chapter.

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Scheduling a Task for Execution via the Operating System Command Line Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Scheduling a Task for Execution Using a PATROL Command Processor . . . . . 315Scheduling a PSL Task for Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318Modifying an Existing Scheduled Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321Removing a Scheduled Task from the Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321Collecting Debug Data for the Scheduler Application . . . . . . . . . . . . . . . . . . . . . 322

Blackouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326Specifying a Default Directory for Blackout Scripts. . . . . . . . . . . . . . . . . . . . . . . . 326Creating a Monitoring Blackout Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327Viewing Information about a Blackout Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330Modifying an Existing Blackout Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331Deleting a Blackout Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334Scheduling a Blackout Script for Execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335Canceling a Scheduled Blackout Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337


Introduction

IntroductionThe PATROL Knowledge Module for Unix and Linux schedules processes and establishes monitoring blackout periods in your environment through the SCHEDULER application.

With this application class, you can

■ write a script to perform a task or job and then schedule that task to run at once or at regular intervals

■ suspend monitoring of applications during routine maintenance or other activities that generate false alarms

Object HierarchyThe SCHEDULER application class contains SCHEDULER parameters. You can use the SCHEDULER application class to schedule processes and programs to run at specified times. In addition, you can use the SCHEDULER application class to suspend PATROL event generation during specified time periods.


Figure 53 SCHEDULER Application Object Hierarchy

NOTE You can change settings in the PATROL SCHEDULER application class using the PATROL Operator Console. Set up access control lists (ACLs) to prevent users from making changes to SCHEDULER settings through a PATROL Operator Console.

OS container

Application class

Parameter


Tasks

TasksThe SCHEDULER application class gives you the ability to write a script to perform a task or job and then schedule that task to run at regular intervals. This feature enables you to designate which script runs when.

The SCHEDULER tasks that relate to scheduling scripts are described in detail on the following pages:

Scheduling a Task for Execution via the Operating System Command Line Processor

This task describes how to schedule a script for execution via the operating system command line.

Before You Begin

Ensure that the following requirements are met:

■ The PATROL Agent must have read and execute permissions for the script that is being scheduled for execution.

■ The PATROL Agent must have write permissions for the output file, if you are creating a script with an output file.

To Schedule a Task for Execution Using the Command Line Processor

1 Access the SCHEDULER application menu as described in “Accessing KM Commands and InfoBoxes” on page 402.

2 Select Schedule Tasks from the pop-up menu.

Task Page

“Scheduling a Task for Execution via the Operating System Command Line Processor”

313

“Scheduling a Task for Execution Using a PATROL Command Processor” 315

“Scheduling a PSL Task for Execution” 318

“Modifying an Existing Scheduled Script” 321

“Removing a Scheduled Task from the Queue” 321

“Collecting Debug Data for the Scheduler Application” 322


Tasks

The Schedule Tasks dialog box is displayed.

3 In the Actions group box, select Schedule New Task and click Accept.

The Schedule New Task dialog box is displayed.

4 Select the Schedule an Operating System Script option button and click Accept.

The Schedule an Operating Script dialog box is displayed.

5 In the Execute Script at: group box, use the spinner buttons or type a value in the following fields to schedule the script:

6 If you want to set the script to occur at regularly scheduled intervals, use the spinner buttons or type values in the following fields of the Repeat Execution: group box:

7 Select the Execute Once Immediately option button if you want the script to execute now.

Field Description

Month indicate the month in which the script should execute

Day indicate the date on which the script should execute

Year indicate the year in which the script should execute

hh indicate at which hour of the day the script should execute

Enter hours in military time. For example, if you want to schedule a script to execute at 4 P.M., enter 16 in this field.

mm indicate at which minute the script should execute

ss indicate at which second the script should execute

Field Description

Days indicate the number of days that should pass between script executions

hh indicate the number of hours that should pass between script executions

mm indicate the number of minutes that should pass between script executions

ss indicate the number of seconds that should pass between script executions


Tasks

8 In the Script File Name field, type the full path and file name for the script.

9 In the Execution Instance field, type the name of the PATROL instance against which the command should be executed. This field is optional.

10 In the Write Output To field, type the full path and file name for the output file. This field is optional.

11 Click Accept.

The dialog box closes, and PATROL schedules the script for execution.

Scheduling a Task for Execution Using a PATROL Command Processor

This task describes how to schedule a task for execution using a command interpreter. You can schedule an existing script for execution, or schedule a script that does not yet exist for execution.

Before You Begin



NOTE If you do not select this option and you are scheduling a script that was supposed to run in the past, it will not run again until the repeated execution runtime. For example, if you have a backup script that is supposed to run every Sunday evening, but you fill out this dialog box on a Monday morning, PATROL will not run the script until the next scheduled execution. You must toggle the Execute Once Immediately button on to run the script now.

NOTE The PATROL Agent account must have read and execute permissions for the script. The PATROL Agent account must also have read permissions for the directory in which the script resides.

NOTE If you specify an output file name in this field, the PATROL Agent must have write permissions for the output file.


Tasks

■ The PATROL Agent must have write permissions for the output file, if you are creating a script with an output file.

To Schedule a Task for Execution Via an Interpreter






4 Select the Schedule a PATROL Command Processor Script option button.

The Schedule a PATROL Command Processor Script dialog box is displayed.

5 In the Execute Script at: group box, use the spinner buttons or type a value in the following fields to schedule the blackout script:

6 If you want to set the script to occur at regularly scheduled intervals, use the spinner buttons or type values in the following fields of the Repeat Execution: group box:

WARNING If you schedule a script with incorrect information (for example, a non-existent script, or one that resides in a directory that is different from the one you specified) for execution, PATROL will attempt to execute it at the scheduled time. However, the execution will fail, and the script will not run.

Field Description









Tasks


8 In the PATROL Command Processor field, type the name of the program that should be used to interpret the script you have written.

The command processor must be one that is defined to the PATROL Agent on which you are running the script before you can use it. For more information on defining command interpreters to the PATROL Agent, look up the PSL built-in function named execute() in the PATROL Script Language Reference Manual Volume 2—PSL Functions.


10 In the Execution Instance field, type the name of the PATROL instance against which the command should be executed. This field is optional.

11 In the Write Output To field, type the full path and file name for the output file. This field is optional.

Field Description






NOTE The PATROL Agent account must have read and execute permissions for the script. The PATROL Agent account must also have read permissions for the directory in which the script resides.


Tasks

12 Click Accept.

In the Script File Name field, type the full name and file path for the script and click Accept.

If you entered the correct full path and file name correctly, the script is scheduled for execution.

Scheduling a PSL Task for Execution

This task describes how to schedule a script for execution via PATROL PSL. You can schedule an existing script for execution, or schedule a script that does not yet exist for execution.

Before You Begin



■ The PATROL Agent must have write permissions for all output files, if you are creating a script with output files.

NOTE If you specify an output file name in this field, the PATROL Agent must have write permissions for the output file.

NOTE If you entered an incorrect full path and file name for the script, the PATROL Scheduler File Name dialog box is displayed. Use the following procedure to correctly fill out the dialog box.

WARNING If you schedule a script with incorrect information (for example, a non-existent script, or one that resides in a directory that is different from the one you specified) for execution, PATROL will attempt to execute it at the scheduled time. However, the execution will fail, and the script will not run.


Tasks

To Schedule a PSL Script for Execution






4 Select the Schedule a PATROL PSL Script option button and click Accept.

5 In the Execute Script at group box, use the spinner buttons or type a value in the following fields to schedule the script:

6 If you want to set the script to occur at regularly scheduled intervals, use the spinner buttons or type values in the following fields of the Repeat Execution group box:


Field Description








Field Description






Tasks

8 In the Internal PSL Process Name field, type the name of the PSL process that will be run with the script.

For more information on PSL process names, look up the PslEexecute() function in the PATROL Script Language Reference Manual Volume 2—PSL Functions.


10 In the Write Compile Errors To field, type the full path and file name for the error output file. This field is optional.

11 In the Write Compile Warnings To field, type the full path and file name for the warning output file. This field is optional.

12 Click Accept.

The dialog box closes, and PATROL schedules the script for execution.


NOTE If you enter an incorrect file name and path, the PATROL Scheduler File Name dialog box will display when you click Accept. This dialog box prompts you to correct the file name and path, or schedule the task as-is. If you schedule a script with incorrect information (for example, a non-existent script, or one that resides in a directory that is different from the one you specified) for execution, PATROL will attempt to execute it at the scheduled time. However, the execution will fail, and the script will not run.

NOTE If you specify an error output file name in this field, the PATROL Agent must have write permissions for the output file.

NOTE If you specify a warning output file name in this field, the PATROL Agent must have write permissions for the output file.


Tasks

Modifying an Existing Scheduled Script

This task describes how to modify an existing script for execution.

Before You Begin



■ The PATROL Agent must have write permissions for all output files, if you are creating a script with output files.

To Modify an Existing Task




3 In the Scheduled Tasks group box, highlight the task you want to modify.

4 In the Actions group box, select Modify Selected Task and click OK.

The Select Function to Execute Script dialog box is displayed.

5 Finish the task by performing one of the following actions:

Removing a Scheduled Task from the Queue

This topic provides information about removing a scheduled task from the queue.

To Modify and Schedule this Type of Script Follow this Procedure Page

operating system “Scheduling a Task for Execution via the Operating System Command Line Processor”, step 5 through step 11

313

PATROL PSL “Scheduling a PSL Task for Execution”, step 5 through step 12 318

PATROL Command Processor

“Scheduling a Task for Execution Using a PATROL Command Processor”, step 5 through step 12

315


Tasks

To Remove a Scheduled Task from the Queue




3 In the Scheduled Tasks group box, highlight the task you want to modify.

4 In the Actions group box, select Remove Selected Task and click OK.

5 Click OK.

PATROL removes the scheduled task from the queue and refreshes the dialog box.

Collecting Debug Data for the Scheduler Application

This topic provides information about scheduling PSL debugger data collection. You can use this feature to turn PSL debugger data collection on and off for different parts of the Scheduler application. For more information on PSL debugger data, see the PATROL Script Language Reference Manual Volume I-PSL Essentials.

To Collect PSL Debugger Data for the Scheduler Application


2 Select Scheduling Debug from the pop-up menu.

The PATROL Scheduler PSL Debugger dialog box is displayed.

3 In the Scheduling Debug dialog box, select the check box next to each selection that you want to turn on. Debug data will be collected for that option.

4 For the Scheduler Daemon Debugger group box item, select the check box next to each selection that you want to turn on for run-time checks and traces. When a debugging selection is turned on, debug data is collected for that option.


Tasks

Check Box Description

Run-Time Checks

Arithmetic operations with NULL strings

checks to ensure that numeric variables are explicitly initialized to 0, instead of defaulting to a NULL string.

Arithmetic operations with non-numeric operands

checks for arithmetic operations that involve non-numeric operands

An expression that attempted to numerically add "mary" + "john" would generate this warning.

Illegal or undefined arithmetic operands

checks for illegal or undefined arithmetic operations

An operation that attempted to divide by zero would generate this warning.

Uninitialized variables checks for variables that were not explicitly initialized

If you attempt to use a variable before explicitly equating it to a value, this warning is generated.

PSL Version 2.0 built-in functions

allows you to suppress warning messages that were not suppressible in PSL Version 2.0


allows you to perform an error check of built-in functions that were not in PATROL Version 2.0

This option detects the following errors:■ passing non-numeric arguments when a numeric value

is required■ passing a bad argument■ passing the wrong number of arguments to a printf()

function

Note: BMC Software recommends enabling PSL Version 2.0 and PSL Version 3.0 built in functions.

Traces

Function call tracing reports which functions are called, but does not return information about the arguments. Function call tracing captures both user-defined and built-in functions.

Function argument tracing

reports the arguments passed to all user-defined or built-in functions

Function call tracing must also be enabled if you want to use this debugger option.

Function return value tracing

reports the value returned by calls to all user-defined or built-in functions

Variable assignment tracing

reports the variable name (if available), and the value assigned to it


Tasks

5 For the Scheduler Facility Debugger group box item, select the check box next to each selection that you want to turn on for run-time checks and traces. When a debugging selection is turned on, debug data is collected for that option.

PSL errno tracking reports any nonzero values stored in the PSL errno variable

PSL lock tracing reports the interprocess actions that occur during lock() and unlock() function processing

This option reports back the granting, denying, and releasing of locks.


Run-Time Checks

Arithmetic operations with NULL strings

checks to ensure that numeric variables are explicitly initialized to 0, instead of defaulting to a NULL string.

Arithmetic operations with non-numeric operands

checks for arithmetic operations that involve non-numeric operands

An expression that attempted to numerically add "mary" + "john" would generate this warning.

Illegal or undefined arithmetic operands

checks for illegal or undefined arithmetic operations

An operation that attempted to divide by zero would generate this warning.

Uninitialized variables checks for variables that were not explicitly initialized

If you attempt to use a variable before explicitly equating it to a value, this warning is generated.


allows you to suppress warning messages that were not suppressible in PSL Version 2.0


allows you to perform an error check of built-in functions that were not in PATROL Version 2.0

This option detects the following errors:■ passing non-numeric arguments when a numeric value

is required■ passing a bad argument■ passing the wrong number of arguments to a printf()

function

Note: BMC Software recommends enabling PSL Version 2.0 and PSL Version 3.0 built in functions.



Tasks

6 To complete the PATROL Scheduler PSL Debugger dialog box, choose one of the following options:

■ Click Accept to toggle the debugger data collection on for the items that you selected.

■ Click Cancel to close the dialog box without saving your changes.

Traces

Function call tracing reports which functions are called, but does not return information about the arguments. Function call tracing captures both user-defined and built-in functions.

Function argument tracing

reports the arguments passed to all user-defined or built-in functions

Function call tracing must also be enabled if you want to use this debugger option.

Function return value tracing

reports the value returned by calls to all user-defined or built-in functions

Variable assignment tracing

reports the variable name (if available), and the value assigned to it

PSL errno tracking reports any nonzero values stored in the PSL errno variable

PSL lock tracing reports the interprocess actions that occur during lock() and unlock() function processing

This option reports back the granting, denying, and releasing of locks.

NOTE ■ The left side of the dialog box controls debug options for the scheduler daemon.

The right side of the dialog box controls debug options for the graphical user interface (GUI).

■ Debug information is only sent to the PATROL Agent Console window when the area being debugged is active. The PATROL KM for Unix does not generate debug data when the scheduler daemon is sleeping, or the GUI is not being used.

■ In the left side PATROL begins collecting debug data for the options that you selected. Debug information is displayed in the System Output Window.



Blackouts

BlackoutsThe SCHEDULER application class gives you the ability to suspend monitoring of applications, which is also known as blacking out PATROL objects. This feature enables you to designate which instances are blacked out or hidden from monitoring and when they are.

The SCHEDULER tasks that relate to blacking out instances from monitoring are described in detail on the following pages:

Specifying a Default Directory for Blackout Scripts

This task describes how to specify a directory in which blackout scripts will be saved when the supplied path is a relative path name (a path name that does not begin with a slash “/” character).

Before You Begin

Before you identify the directory location, ensure that the blackout script directory meets the following requirements:

■ The blackout script directory must exist on the system.

■ The PATROL default account must have read and execute permissions for the blackout script directory.

Task Page

“Specifying a Default Directory for Blackout Scripts” 326

“Creating a Monitoring Blackout Script” 327

“Viewing Information about a Blackout Script” 330

“Modifying an Existing Blackout Script” 331

“Deleting a Blackout Script” 334

“Scheduling a Blackout Script for Execution” 335

“Canceling a Scheduled Blackout Script” 337

NOTE If you do not specify a default directory for blackout scripts, blackout scripts will be saved in the PATROL_HOME directory (the directory specified in the PATROL Agent /home variable).


Blackouts

To Specify the Blackout Script Directory


2 Select Set Default Blackout Script Directory from the pop-up menu.

The Identify Default Blackout Script Directory dialog box is displayed.

3 Type the full path of the blackout script directory in the Enter Full Path field and click Apply.

Creating a Monitoring Blackout Script

This task describes how to create a blackout script that suspends propagation of state changes (for example, alarms and warnings) on selected application classes and instances.

Before You Begin

The PATROL KM for Unix will create the blackout script for you; you do not have to write the script before you begin this procedure. However, you must ensure that the default PATROL account has read and execute permissions on the directory in which the blackout script resides.

To Create a Blackout Script for Immediate Execution


2 Select Schedule Blackouts from the SCHEDULER application menu.

The Schedule Blackouts dialog box is displayed.

3 Select Add New Blackout Script and click OK.

The Blackout Script File Name dialog box is displayed.

NOTE Do not store blackout script files in the /tmp directory; many Unix systems automatically clear this directory upon system reboot.


Blackouts

4 Type a file name (and path, if desired) in the Blackout Script Full File Path field and click OK.

The Blackout Instance Selection dialog box is displayed.

5 Use the following table to perform the actions necessary to select application instances for a blackout period.

6 Click Done.

The Add New Blackout Script dialog box is displayed.

NOTE The PATROL default account must have read and execute permissions on the directory in which the script is stored.

To Achieve this Result Perform the Following Action(s)

suspend monitoring for all application class instances on a computer

Click the Select All Instances option button and click Select.

suspend monitoring for all application instances within selected application classes

1. In the Application List group box, select all the application classes for which you want to suspend monitoring.

2. Click the Select All Instances in the Highlighted Classes option button and click Select.

suspend monitoring for selected application instances

1. In the Application List group box, select the application class for which you want to suspend monitoring.

2. Click the Select Only the Highlighted Instances option button and click Select. The application class expands to list all instances within the application class.

3. Highlight the instances for which you want to suspend monitoring and click Select.

clear all of your instance selection choices and start over

Click the Clear All Selections option button and click Select.

NOTE If you want to remove an application class or instance from the script, highlight it in the Selected Instances group box and click Select.


Blackouts

7 Use the spinner buttons or type a value in the following fields:

8 Perform one of the following actions to set monitoring blackout periods:

A If you want to set the same blackout period for all instances in the blackout script, click the Apply period to all remaining instances button.

B If you want to set different blackout periods for each application instances, do not select the Apply period to all remaining instances button. If this button is not selected, the Blackout Period dialog box will display for each instance in the script, allowing you to set different blackout time periods for each instance.

9 Click Apply.

The Add New Blackout Script Name Summary dialog box is displayed.

10 Click Continue.

A confirmation dialog box displays, asking if you want to schedule the script for execution now.

11 Perform one of the following actions:

A Click Yes if you want to schedule the blackout script for execution now.

B Click No if you do not want to schedule the blackout script for execution now. If you click No, you must perform the steps in “Scheduling a Blackout Script for Execution” on page 335 before the blackout script will execute.

If you clicked Yes, the Schedule PATROL PslExecute() Action dialog box is displayed. Proceed to step 14.

NOTE The Blackout Script Status dialog box is also displayed. This dialog box provides information about the status of the blackout script; you cannot enter data into it.

Field Description

Days indicate how many days the blackout period should last

Hrs indicate how many hours the blackout period should last

Mins indicate how many minutes the blackout period should last


Blackouts


13 If you want to set the blackout script to occur at regularly scheduled intervals, use the spinner buttons or type values in the following fields of the Repeat Execution: group box:

14 Click Accept.

The dialog box closes, and PATROL schedules the blackout script for execution.

Viewing Information about a Blackout Script

This task describes how to view information about a blackout script.



3 Select a blackout script from the Blackout Script Files group box.

Field Description

Month indicate the month in which the blackout script should execute

Day indicate the date on which the blackout script should execute

Year indicate the year in which the blackout script should execute

hh indicate at which hour of the day the blackout script should execute


mm indicate at which minute the blackout script should execute

ss indicate at which second the blackout script should execute

Field Description

Days number of days that should pass between blackout script executions

hh number of hours that should pass between blackout script executions

mm number of minutes that should pass between blackout script executions

ss number of seconds that should pass between blackout script executions


Blackouts

4 Select View Selected Script from the Actions group box and click OK.

The View Selected Script dialog box is displayed. This dialog box provides the following information about the selected blackout script:

■ full path and file name of the blackout script■ date and time that the blackout script was last modified■ instances that are included in the blackout script, and their scheduled blackout

times

5 Click Done.

The dialog box closes.

Modifying an Existing Blackout Script

This task describes how to modify an existing blackout script.

Before You Begin

You can only use this procedure to modify blackout scripts that you created using the Scheduling Blackouts command. If you created a blackout script outside of PATROL, you cannot modify it using this procedure.

To Modify an Existing Blackout Script



The PATROL Blackout Scheduler dialog box is displayed.


4 Select Modify Selected Script from the Actions group box and click OK.

The Blackout Instance Selection dialog box is displayed.


Blackouts

5 Use the following table to perform the actions necessary to select application instances for a blackout period.

6 Click Done.

The Add New Blackout Script dialog box is displayed.

7 Use the spinner buttons or type a value in the following fields:

To Achieve this Result Perform the Following Action(s)

suspend monitoring for all application class instances on a computer

Click the Select All Instances option button and click Select.

suspend monitoring for all application instances within selected application classes

1. In the Application List group box, select all the application classes for which you want to suspend monitoring.

2. Click the Select All Instances in the Highlighted Classes option button and click Select.

suspend monitoring for selected application instances

1. In the Application List group box, select the application class for which you want to suspend monitoring.

2. Click the Select Only the Highlighted Instances option button and click Select. The application class expands to list all instances within the application class.

3. Highlight the instances for which you want to suspend monitoring and click Select.

clear all of your instance selection choices and start over

Click the Clear All Selections option button and click Select.

NOTE If you want to remove an application class or instance from the script, highlight it in the Selected Instances group box and click Select.

Field Description

Days indicate how many days the blackout period should last

Hrs indicate how many hours the blackout period should last

Mins indicate how many minutes the blackout period should last


Blackouts

8 Perform one of the following actions to set monitoring blackout periods:

A If you want to set the same blackout period for all instances in the blackout script, click the Apply period to all remaining instances button.

B If you want to set different blackout periods for each application instances, do not select the Apply period to all remaining instances button. If this button is not selected, the Blackout Period dialog box will display for each instance in the script, allowing you to set different blackout time periods for each instance.

9 Click Apply.

The Add New Blackout Script Name Summary dialog box is displayed.

10 Click Continue.

A confirmation dialog box displays, asking if you want to schedule the script for execution now.

11 Perform one of the following actions:

A Click Yes if you want to schedule the blackout script for execution now.

B Click No if you do not want to schedule the blackout script for execution now. If you click No, you must perform the steps in Scheduling a Blackout Script for Execution before the blackout script will execute.

If you clicked Yes, the Schedule PATROL PslExecute() Action dialog box is displayed. Proceed to step 15.


Field Description









Blackouts



15 Click Accept.


Deleting a Blackout Script

This task describes how to delete a blackout script. When you perform this task, PATROL removes the blackout script from the designated blackout script directory. If the blackout script is scheduled for execution, instances of the task are also removed from the SCHEDULER.

Before You Begin

Field Description





NOTE If you do not select this option and you are scheduling a script that was supposed to run in the past, it will not run again until the repeated execution runtime. For example, if you have a blackout script that is supposed to run every Sunday evening, but you fill out this dialog box on a Monday morning, PATROL will not run the script until the next scheduled execution. You must toggle the Execute Once Immediately button on to run the script now.

WARNING Deleting a blackout script does not end blackouts that are currently in effect. To end a blackout that is current in effect, perform the procedure that is documented in “Canceling a Scheduled Blackout Script” on page 337.


Blackouts

To Delete a Blackout Script




4 Select Delete Selected Script from the Action group box and click OK.

The blackout script is deleted.

Scheduling a Blackout Script for Execution

This task describes how to schedule a blackout script for execution. You can only use this procedure to schedule blackout scripts that were created using the PATROL for Unix blackout scheduling features.

Before You Begin

The blackout script must be one that was created using the blackout scheduling features provided by PATROL for Unix. See Creating a Monitoring Blackout Script for instructions about using PATROL to create a blackout script.

To Schedule an Existing Blackout Script for Execution


2 Select Scheduling Blackouts from the SCHEDULER application menu.

The PATROL Blackout Scheduler dialog box is displayed.

3 Highlight a script in the Blackout Script Files group box.

4 Select Schedule Selected Script from the Action group box and click OK.

The Schedule PATROL PslExecute() Action dialog box is displayed.

WARNING If you have created other blackout scripts outside of PATROL, you must use the procedure documented in Scheduling a Task for Execution via the Operating System Command Line Processor to schedule them for execution.


Blackouts




8 Click Accept.


Field Description








Field Description





NOTE If you do not select this option and you are scheduling a script that was supposed to run in the past, it will not run again until the repeated execution runtime. For example, if you have a blackout script that is supposed to run every Sunday evening, but you fill out this dialog box on a Monday morning, PATROL will not run the script until the next scheduled execution. You must toggle the Execute Once Immediately button on to run the script now.


Blackouts

Canceling a Scheduled Blackout Script

This task describes how to cancel the blackout period for a script. When you perform this task, PATROL resumes propagating state changes (for example, alarms and warnings) for the instances that were part of the blackout script. PATROL does not delete the blackout script from its designated location.

To Cancel an Existing Blackout Script




4 Select Cancel Existing Blackout (Selected Script) from the Actions group box and click OK.

The blackout period is canceled, and PATROL resumes propagating state changes for the instances that were part of the script.


Blackouts


C h a p t e r 16
16 Reviewing Security
The PATROL Knowledge Module for Unix and Linux gives you the ability to monitor various aspects of the Unix operating system security. With it, you determine which files were created by super users, which files have global write permissions, and which users have no passwords or have multiple user accounts. The following sections appear in this chapter.

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341

Viewing Files with SUID or SGID Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . 341Viewing Files with Global Write Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

User Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345Viewing Users that Failed to Execute su/msu Commands . . . . . . . . . . . . . . . . . 345Viewing Users without Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346Viewing Users with Multiple Sessions Running . . . . . . . . . . . . . . . . . . . . . . . . . . 348


Introduction

IntroductionPATROL Knowledge Module for Unix and Linux monitors various aspects of the operating system that affect its security. The KM monitors characteristics of files such as whether or not the file has

■ set user or group permissions■ global write access

The KM also monitors characteristics of user accounts and user activity that pose a potential threat to security such as which users

■ failed to execute a set user (su or msu) command■ have no or blank passwords■ are running multiple sessions

Object HierarchyThe SECURITY application class does not possess any instances or contain any parameters. Figure 54 illustrates the basic hierarchy.

Figure 54 SECURITY Application Object Hierarchy

NOTE This chapter discusses how PATROL monitors the Unix operating system. It does not discuss the security features employed by PATROL. For that information, see the getting started guide for your product and the PATROL Security User Guide.

OS container

Application class

UNIX OS

OS container

UNIX OS


Files

FilesThe SECURITY application class enables you to monitor files with potentially dangerous permissions and privileges. With this feature, you can determine if a file has set user or group permissions and if a file can be written to by any user.

The SECURITY tasks related to files are described in detail on the following pages:

Viewing Files with SUID or SGID Permissions

This task describes how to view a list of files that have the set user ID (SUID) or set group ID (SGID) permission set. With this permission, the file can set its own user ID or group ID, respectively, regardless of the owner or group to which the owner belongs.

Before You Begin

To perform this task, you must provide a user account and password. It does not have to be the root account.

To View a List of Files with SUID and/or SGID Permissions

1 Access the SECURITY application menu as described in “Accessing KM Commands and InfoBoxes” on page 402.

2 Select Administration => List SUID and SGID Files

PATROL prompts you for a user account and password (Figure 55).

Figure 55 SECURITY User Name and Password Dialog Box

Task Page

“Viewing Files with SUID or SGID Permissions” 341

“Viewing Files with Global Write Privileges” 344


Files

3 Type the appropriate user name and password and click OK.

PATROL displays the Find SUID/SGID Files Like dialog box (Figure 56).

Figure 56 Find SUID/SGID Files Like Dialog Box

4 Define the search criteria. The search is a logical AND operation that returns only files that match all the criteria defined by the following fields.

5 Click Find.

PATROL builds a search expression, searches the system for files that match the criteria, and writes the results to a PATROL task object (List SUID and SGID Files) in the UNIX OS container.

Field Description

Start find at the directory structure from which to begin the search. The default is root (/).

File Name the regular expression pattern for one or more files. For more information, see “CRegular Expressions” on page 407. Leave this field blank to search for any file name.

File Owner the owner of the file(s)

File Group the group to which the owner of the file(s) belongs

File Updated in ‘n’ days ago

the period in days between the change date and the current date

Limit to one physical disk restricts the operation to the disk drive on which the directory defined in the Start find at field resides


Files

6 Access the List SUID and SGID Files task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

Output Format

The output has the following format. Table 54 describes each expression.


<NOT INTERACTIVE>

List SUID and SGID Files

Begin: find /oracle/empdata/payroll $ -perm -004000 -o -perm -002000 $ -exec ls -ld {} \;

-rwsr-sr-x 1 3Supvr admin 129 Jun 20 14:38 /oracle/empdata/payroll/may_2001

-------------------- >>>>> DONE <<<<< --------------------

Begin: find /path -name <text> $ -perm -004000 -o -perm -002000 $ -exec <ls> -ld {} \;

-rwsr-sr-- # <username> <group> ### MMM DD hh:mm <path>/<file_name.ext>

-------------------- >>>>> DONE <<<<< --------------------


Search Expression




- perm -00400 -o -perm -002000

defines the permissions of files that the find command looks for

-exec ls lists the contents of the specified directory



List of Files

-rwsr-sr-- file permissions

# number of links to the file

username owner of the file

dev group of owner

### size in bytes

MMM DD hh:mm date-time stamp

location path and file name


Files

Viewing Files with Global Write Privileges

This task describes how to view all files that can be written to by any user on the system.

Before You Begin


To View a List of Files that Any User Can Write To


2 Select Administration => List Files With Global Write.

PATROL prompts you for a user account and password.


PATROL writes the results to a PATROL task object (List Files with Global Write) in the UNIX OS container.

4 Access the List Files with Global Write task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

Output Format

The output has the following format. Table 55 describes each field.


/usr/openwin/lib/locale/libs

/var/ntb/tmp

/var/ntb/appcnfg/appmngr/System_Admin

/etc/PERL

/dev/stty

directory/filename

-------------------- >>>>> DONE <<<<< --------------------

Table 55 List Files With Global Write Command Output Format

Field Description

directory/filename path and filename of file or directory with global write permissions


User Activity

User ActivityThe SECURITY application class enables you to monitor user activity that could compromise your system’s security. With this feature, you can determine which users have no or blank passwords, which users are running multiple sessions, and which users attempted to perform a set user command and failed.

The SECURITY tasks related to users are described in detail on the following pages:

Viewing Users that Failed to Execute su/msu Commands

This task describes how to view a list of users who attempted and failed to execute a set user (su) or (msu) command.

Before You Begin


To View a List of Users that Failed to Execute su/msu Commands


2 Select Administration => List Failed su/msu logins.



PATROL writes the information to a PATROL task object (List Failed su/msu logins) in the UNIX OS container.

Task Page

“Viewing Users that Failed to Execute su/msu Commands” 345

“Viewing Users without Passwords” 346

“Viewing Users with Multiple Sessions Running” 348


User Activity

4 Access the List Failed su/msu logins task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

Output Format


Viewing Users without Passwords

This task describes how to view a list of users who either do not have a password or have a blank password.

Before You Begin



<NOT INTERACTIVE>

List Failed su/msu logins

SU 01/02 15:56 - pts/8 dpallet-ssp

SU 01/17 09:39 - pts/8 rabby-root

SU 01/18 17:45 - pts/17 mmoulin-root

SU 01/23 15:13 - pts/13 nedned-root

cmd mm/dd hh:mm - pts/# acct_from-acct_to

Table 56 List Failed su/msu logins Command Output Format

Field Description

cmd the unsuccessful commandsu—become super user (root) or other usermsu—a variant of su that is no longer supported by platforms on which PATROL KM for Unix and Linux runs

mm/dd month and date on which the failed login attempt occurred

hh:mm time at which the failed login attempt occurred

pts/# pseudo tty subsystem slave terminal name

acct_from the user account from which the command was executed

acct_to the user account to which the acct_from user attempted to switch


User Activity

To View a List of Users that Do Not Have a Password or Have a Blank Password


2 Select Administration => List Users Without Passwords.



PATROL writes the information to a PATROL task object (List Users Without Password) in the UNIX OS container.

4 Access the List Users Without Password task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results.Your results should resemble this example:

Output Format



<NOT INTERACTIVE>

List users with-out password

------------------ >>>>> NIS LIST <<<<< ------------------

guest2

admin_request

larryking

ADMIN-NEW

------------------ >>>>> LOCAL LIST <<<<< ----------------

-------------------- >>>>> DONE <<<<< --------------------

------------------ >>>>> LIST SEPARATOR <<<<< ------------------

username

Table 57 List Users Without Passwords Command Output Format

Field Description

list separator a line that separates and categorizes the accounts based on their location in the systemNIS—NIS accounts without passwordsLOCAL—accounts on the local machine without passwords

username the user name of an account that either does not have a password or has a blank password


User Activity

Viewing Users with Multiple Sessions Running

This task describes how to view a list of users who have duplicate user ID entries, a condition that results from running multiple sessions.

Before You Begin


To View a List of Users with Multiple Sessions Running


2 Select Administration => List Duplicate User ID Entry.



PATROL writes the information to a PATROL task object (List Duplicate User ID Entry) in the UNIX OS container.

4 Access the List Duplicate User ID Entry task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:


<NOT INTERACTIVE>

List users with duplicate user id

user id: 9351 -- vdolor, tg1_a, tg1_b, tg2_a, tg1_b, pdolor,

user id: 4262 -- mhartman, ldap,

user id: 923 -- 3Supvr, 4Supvr,

user id: 1092 -- r45, r46,

user id: 2784 -- nots, yesman,

-------------------- >>>>> DONE <<<<< --------------------


User Activity

Output Format


user id: 4262 -- <username_#>, <username_#+1>,

Table 58 List Duplicate User ID Entries Command Output Format

Field Description

user id: #### the user ID

<username_#> the user name under which an additional session is run


User Activity


C h a p t e r 17
17 Monitoring the Health of SNMP
The PATROL Knowledge Module for Unix and Linux gives you the ability to monitor the PATROL SNMP system. Simple Network Management Protocol (SNMP) support is built into the PATROL Agent. The application class checks to see if the SNMP Master Agent and subagent are running, lists configuration information, and provides diagnostic tests with which you can troubleshoot problems. The following sections appear in this chapter:

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352PATROL SNMP System Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353Role of Each Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

SNMP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354Changing SNMP Query Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355Listing Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356Viewing PATROL SNMP MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

Status of SNMP Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360Starting the SNMP Master Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361Starting the SNMP Subagent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362Stopping the SNMP Subagent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

Tests SNMP Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364Testing the SNMP Master Agent’s Ability to Receive Traps . . . . . . . . . . . . . . . . 364Generating Manual SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365Querying the PATROL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366Querying the SNMP PATROL platform.km . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367Determining if Any SNMP Managers are Listening . . . . . . . . . . . . . . . . . . . . . . . 369Testing PATROL Event Manager’s Automated SNMP Traps . . . . . . . . . . . . . . . 370


Introduction

IntroductionThe SNMPHealth application monitors the PATROL SNMP system. This application class also provides the ability to

■ change the SNMP query port■ list PATROL SNMP system configuration information■ view PATROL SNMP MIB database information■ start SNMP Master Agent■ start and stop SNMP subagent■ test SNMP functionality

For information on how to configure the PATROL SNMP system, see the chapters on SNMP in the PATROL Agent Reference Manual.

Object HierarchyThe SNMPHealth application class contains parameters with information on the PATROL SNMP system configuration, status of the SNMP subagent, and results from test run against the system.


Figure 57 SNMPHealth Application Object Hierarchy

OS container

Application class

Parameters

UNIX OS


PATROL SNMP System Architecture

PATROL SNMP System ArchitectureThe PATROL SNMP architecture comprises an SNMP subagent that is part of the PATROL Agent and an SNMP Master Agent that is a separate, external process.

Architecture

Figure 58 shows the relationships between the PATROL SNMP Master Agent, the PATROL Agent, PATROL SNMP subagents, SNMP subagents, and the SNMP manager. It also lists their default port numbers.

Figure 58 PATROL SNMP System Architecture

Table 59 describes the role that each component plays in the PATROL SNMP architecture.

NOTE Port 161 is an industry standard, while port 8161 is a PATROL standard. By running on port 8161, you can avoid possible conflicts with operating system vendors who are already using port 161 for an SNMP agent.

PATROL EventManager

SNMPManager

PATROL Agent

SNMP Subagent

PA

Requester is an SNMPManager and has nothingto do with PATROL

PATROL SNMPMaster Agent

Third-PartySNMP Subagents

Port 8161—PATROL standard portPort 161—industry standard port

resides on each

Makes PATROL KMs

remote machine

available via SNMPand sends traps toSNMP managers

1. generates/sends requests to master or subagent2. listens for traps

looks at requests and dispatches information

Port 199

PATROL Agent sendstraps to SNMP Manager


SNMP Configuration

Role of Each Component

Table 59 lists each component in the PATROL SNMP system and describes its role.

SNMP ConfigurationThe SNMPHealth application class enables you to review the PATROL SNMP system settings and change the most crucial setting, the query port number. With this application, you can also examine the information stored in the SNMP Management Information Base (MIB) by the PATROL Agent.

SNMP configuration tasks are described in detail on the following pages:

Table 59 PATROL SNMP Component Definitions

Component SNMP Role

PATROL Agent generates traps

PATROL SNMP Master Agent

provides SNMP information to SNMP managers in the form of responses to SNMP queries

PATROL SNMP Subagent responds to SNMP queries by going into internal data structures and sending information back

SNMP subagents can also generate or send PATROL traps directly to the SNMP Manager.

PATROL SNMP Manager Functionality

(PSL Functions)

receives traps and issues queries to an SNMP agent

The manager controls the agent by making SNMP requests of the agent and by setting variables in the agent’s management information base (MIB).

Task Page

“Changing SNMP Query Port” 355

“Listing Configuration Information” 356

“Viewing PATROL SNMP MIB” 357


SNMP Configuration

Changing SNMP Query Port

This task describes how to change SNMP Query Port. External processes send queries to the PATROL Agent through its SNMP Query Port.

This port is defined in $PATROL_HOME/log/snmpmagt.cfg. The default value of the SNMP Query Port is 8161, which is registered to BMC Software, Inc. Change this port setting if some other process already uses this port. The PATROL SNMP Master Agent will not start if the port designated as the SNMP Query Port is used by another process.

Before You Begin

Make sure the port that you want to use is available.

To Change the SNMP Query Port

1 Access the SNMPHealth application menu as described in “Accessing KM Commands and InfoBoxes” on page 402.

2 Select SNMP Configuration => Change SNMP Query Port.

PATROL displays the Change SNMP Query Port dialog box (Figure 59).

Figure 59 Change SNMP Query Port Dialog Box

NOTE For the change to take effect, you must stop and restart the PATROL SNMP Master Agent.


SNMP Configuration

3 Delete the existing port number and type in a new one.

4 Click Accept.

PATROL closes the dialog box and changes the value in the snmpmagt.cfg file. To force the PATROL SNMP Master Agent to use the new port, you must stop and restart the snmpmagt process. For information on starting and stopping the master agent, see “Starting the SNMP Master Agent” on page 361.

Listing Configuration Information

This task describes how to display your PATROL SNMP system configuration information. The command lists

■ the PATROL SNMP variables and their values stored in the PATROL Agent configuration database

■ the status of the SNMPStart parameter

■ the status of the snmpmagt Query Port

■ the status of the snmpmagt process

■ the status of the SNMP subagent

■ the contents of the configuration file, snmpmagt.cfg

For additional information on the PATROL SNMP system, see the PATROL Agent Reference Manual.

To View Configuration Information


2 Select SNMP Configuration => List Configuration Information.

PATROL writes the information to a PATROL task object (List Configuration Information) in the UNIX OS container.


SNMP Configuration

3 Access the List Configuration Information task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

To Save Configuration Information to an ASCII File

Perform step 1 through step 3 in “To View Configuration Information” on page 356, and then perform the following steps:

1 Select File => Save As.

PATROL displays the Save Script File dialog box.

2 Enter the filename and location where you want to save this information.

3 Click OK.

PATROL writes the configuration information to the designated file and location. For additional information on specific configuration settings, see the PATROL Agent Reference Manual.

Viewing PATROL SNMP MIB

This task describes how to check the SNMP information stored in a MIB. The dialog defaults to the PATROL Agent MIB. However, if you know the computer name, listening port, community string, and OID (object identifier) of another process that uses SNMP, you can walk that process’s MIBs.

This feature is primarily used to test that the PATROL SNMP Master Agent is populating its MIB.

# PSL Serial No.: ######### SNMPHealth Configuration Information collected for host <host> at Tue Aug 28 16:47:34 CCYY SNMPHealth Configuration Info computer class: SOLARISSNMPHealth Configuration Info... /snmp/agent_auto_start: "yes"SNMPHealth Configuration Info... /snmp/agent_r_community: "public"SNMPHealth Configuration Info... /snmp/agent_w_community: "private"<continued>


SNMP Configuration

Before You Begin

For detailed information on the PATROL SNMP MIB, see the appendix, “PATROL SNMP MIB,” in the PATROL Agent Reference Manual.

To View the SNMP Management Information Base for PATROL


2 Select Test PATROL SNMP System => Walk PATROL SNMP MIB.

PATROL displays the Walk PATROL SNMP MIB dialog box (Figure 60).

Figure 60 Walk PATROL SNMP MIB Dialog Box

3 Define the portion of the PATROL SNMP MIB that you want to view.

Field Description

Host to Query the machine whose SNMP MIB you want to viewListening Port the port on which the master agent is listeningCommunity the SNMP community string defines the relationship between an

SNMP server system and the client systems and acts like a password to control the clients' access to the server

Timeout the amount of time PATROL waits before exiting; the default is set in the PATROL Agent Configuration variable /SNMP/default_timeout


SNMP Configuration

4 Click OK.

PATROL writes the information to a PATROL task object (Walk PATROL SNMP MIB) in the UNIX OS container.

5 Access the Walk PATROL SNMP MIB task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

Retries the number of times PATROL attempts to access the host’s MIB; the default is set in the PATROL Agent Configuration variable /SNMP/default_timeout

OID the object ID

snmp_get returned: 2.1.2.1.2.1.2121.1.1.1.2.0 1 string /2.1.2.1.2.1.2121.1.1.1.3.1.1.8.80.82.79.67.67.79.78.84 8 string PROCCONT2.1.2.1.2.1.2121.1.1.1.3.1.1.6.75.69.82.78.69.76 6 string KERNEL2.1.2.1.2.1.2121.1.1.1.3.1.1.3.76.79.71 3 string LOG2.1.2.1.2.1.2121.1.1.1.3.1.1.9.66.108.111.99.107.83.105.122.101 9 string BlockSize2.1.2.1.2.1.2121.1.1.1.3.1.1.14.83.101.116.117.112.67.108.101.97.114.84.101.120.116 14 string SetupClearText2.1.2.1.2.1.2121.1.1.1.3.1.1.10.67.79.77.80.79.83.73.84.69.83 10 string COMPOSITES2.1.2.1.2.1.2121.1.1.1.3.1.1.9.78.84.95.72.69.65.76.84.72 9 string NT_HEALTH2.1.2.1.2.1.2121.1.1.1.3.1.1.8.80.82.79.67.80.82.69.83 8 string PROCPRES2.1.2.1.2.1.2121.1.1.1.3.1.1.10.70.73.76.69.83.89.83.84.69.77 10 string FILESYSTEM2.1.2.1.2.1.2121.1.1.1.3.1.1.4.68.73.83.75 4 string DISK2.1.2.1.2.1.2121.1.1.1.3.1.1.6.76.79.71.77.79.78 6 string LOGMON2.1.2.1.2.1.2121.1.1.1.3.1.1.11.68.70.66.108.111.99.107.83.105.122.101 11 string DFBlockSize2.1.2.1.2.1.2121.1.1.1.3.1.1.8.83.69.67.85.82.73.84.89 8 string SECURITY2.1.2.1.2.1.2121.1.1.1.3.1.1.9.83.78.77.80.83.116.97.114.116 9 string SNMPStart2.1.2.1.2.1.2121.1.1.1.3.1.1.3.83.77.80 3 string SMP<continued>

Field Description


Status of SNMP Agents

Output Format

The output has the following format. Table 60 describes each expression.

Status of SNMP AgentsThe SNMPHealth application class enables you to control the status of the PATROL SNMP system. With the application, you can start the master agent and start and stop the subagent.

The SNMPHealth start and stop tasks are described in detail on the following pages:

name type length value

Table 60 Walk PATROL SNMP MIB Command Output Format

Field Description

name name of an SNMP MIB variable represented by its numeric object ID (OID)

type the data type of the valueValid data types include:

stringinteger

length length of the value if its data type is “string”If the data type is integer, this field is empty.

value the value of the variableIf the variable does not have a value, this field is empty.

NOTE The PATROL KM for Unix and Linux does not provide the ability to stop the SNMP Master Agent. This action requires root access.

Task Page

“Starting the SNMP Master Agent” 361

“Starting the SNMP Subagent” 362

“Stopping the SNMP Subagent” 363



Starting the SNMP Master Agent

This task describes how to start the PATROL SNMP Master Agent.

Before You Begin

■ Check to see that the master agent has stopped running. You can verify the agent’s status by using one of the following methods:

— view the SNMPHealth capture diagnostic text parameter— run the SNMP List Configuration menu command— search the process table for the snmpmagt process

■ This command will fail if the SMUX port (tcp port 199) or the SNMP query port (defined in PATROL_HOME/lib/snmpmagt.cfg) is used by some other process.

To Start the Master Agent


2 Select Start/Stop SNMP Agent => Start SNMP Master Agent.

After attempting to start the SNMP Master Agent, PATROL refreshes the process cache, sleeps for 60 seconds, and then stops and restarts the PATROL SNMP subagent.

PATROL writes its progress to the system output window. Your results should resemble this example:

CCYYMMDDHHMMSS Start SNMP Master Agent... snmpmagtCCYYMMDDHHMMSS Start SNMP Master Agent... Executing Start command: /apps/patrol/CCYYMMDDHHMMSS Refresh Process cache and then sleep 60 secondsCCYYMMDDHHMMSS Start SNMP Master Agent... Patrol SNMP sub-agent stoppedCCYYMMDDHHMMSS Start SNMP Master Agent... Patrol SNMP sub-agent stopped



Starting the SNMP Subagent

This task describes how to start the SNMP subagent. Generally, this task is performed when the SNMP master agent is running but the SNMP subagent is not.

The SNMPHealth application class uses a parameter without an icon, snmp_subagent_start, to ensure that PATROL attempts to start the subagent if it is not started. The parameter checks the status of the subagent every 60 seconds. Perform this task if either the parameter cannot restart the subagent or you do not want to wait for the next restart attempt.

Before You Begin

This command will fail if the SNMP Master Agent is not running.

To Start the subagent


2 Select Start/Stop SNMP Agent => Start SNMP Sub-agent.

PATROL starts the subagent. If the subagent is already running, PATROL stops the subagent and restarts it.

PATROL writes its progress to the system output window. Your results should resemble this example:

CCYYMMDDHHMMSS SNMPHealth Start SNMP sub-agent: SNMP sub-agent is already active.

CCYYMMDDHHMMSS SNMPHealth Start SNMP sub-agent: Stopping SNMP sub-agent.

CCYYMMDDHHMMSS SNMPHealth Start SNMP sub-agent: Starting SNMP sub-agent.

CCYYMMDDHHMMSS SNMPHealth Start SNMP sub-agent: SNMP sub-agent is active.



Stopping the SNMP Subagent

This task describes how to stop the SNMP subagent. This task is used primarily for testing the snmp_subagent_monitor and snmp_subagent_start parameters.

Before You Begin

The consequences of stopping the subagent with this menu command include

■ the PATROL SNMP system will not function properly until the SNMP subagent is restarted

■ PATROL changes the snmp_subagent_monitor parameter state to ALARM

■ the snmp_subagent_start parameter attempts to restart the subagent within 60 seconds

To Stop the Subagent


2 Select Start/Stop SNMP Agent => Stop SNMP Sub-agent.

PATROL stops the subagent. If the subagent is not running, PATROL recognizes that it is inactive and ignores the command.

PATROL writes its progress to the system output window.Your results should resemble this example:

NOTE If you want to stop the SNMP subagent for an extended period of time (more than 60 seconds), you must disable the snmp_subagent_start parameter.

CCYYMMDDHHMMSS SNMPHealth Diagnostics: SNMP sub-agent is active.

CCYYMMDDHHMMSS SNMPHealth Diagnostics: Stopping SNMP sub-agent.

CCYYMMDDHHMMSS SNMPHealth Diagnostics: SNMP sub-agent is not active.


Tests SNMP Functionality

Tests SNMP FunctionalityThe SNMPHealth application class serves as a diagnostic utility. It provides a number of menu commands with which you can test SNMP functionality to identify potential problems and isolate the cause.

The SNMPHealth tests are described in detail on the following pages:

Testing the SNMP Master Agent’s Ability to Receive Traps

This task describes how to test if the SNMP Master Agent is listening for SNMP traps.

Before You Begin

■ The trap port is stored in the agent configuration variable /snmp/trap_port. The default value is 162. You might need to change this port setting if some other process already uses this port. This task will fail if the port is used by another process.

■ This task should be performed in conjunction with the task, “Generating Manual SNMP Traps” on page 365. This task provides a mechanism (a PATROL task object) with which to view the manually generated traps.

To Test the Master Agent’s Ability to Receive Traps


2 Select Test PATROL SNMP System => Listen for SNMP Traps.

PATROL writes the information to a PATROL task object (Listen for SNMP Traps) in the UNIX OS container.

Task Page

“Testing the SNMP Master Agent’s Ability to Receive Traps” 364

“Generating Manual SNMP Traps” 365

“Querying the PATROL Agent” 366

“Querying the SNMP PATROL platform.km” 367

“Determining if Any SNMP Managers are Listening” 369

“Testing PATROL Event Manager’s Automated SNMP Traps” 370



3 Access the Listen for SNMP Traps task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

Generating Manual SNMP Traps

This task describes how to manually create SNMP traps.

The trap port is stored in the agent configuration variable /snmp/trap_port. The default value is 162. You might need to change this port setting if some other process already uses this port. This task will fail if the port is used by another process.

Before You Begin

This task should be performed in conjunction with the task, “Testing the SNMP Master Agent’s Ability to Receive Traps” on page 364. This task sends traps to the port on which PATROL is listening for traps.

To Generate Manual Traps


2 Select Test PATROL SNMP System => Generate Manual SNMP Trap.

PATROL displays the Generate a Manual SNMP Trap dialog box.

SNMP Listen Running...

NOTE While the task object is executing, it displays any SNMP traps received at the trap port.



3 Edit the Target host/port/community information to correspond to your PATROL SNMP system configuration. If you do not provide a community string, PATROL uses the one stored in the agent configuration variable /SNMP/default_r_community.

4 Click OK.

PATROL closes the dialog box and sends the trap to the SNMP listening process started in step 2.

5 Access the Listen for SNMP Traps task object. Your results should resemble this example:

Querying the PATROL Agent

This task describes how to determine if the PATROL Agent can make SNMP queries. It demonstrates that PATROL can make SNMP requests of the PATROL SNMP Master Agent.

To Test the Master Agent’s Ability to Receive Traps


2 Select Test PATROL SNMP System => SNMP Query PATROL Master Agent.

PATROL displays the SNMP Query PATROL Master Agent dialog box.


From: 27.137.19.172 (2.1.2.1.2.1.2121) Enterprise Specific (1) Uptime: 2 day(s) 4:22:11 (1)

2.1.2.1.2.1.2121.1 6 string test 1

2.1.2.1.2.1.2121.2 6 string test 2

2.1.2.1.2.1.2121.2 6 string test 2

2.1.2.1.2.1.2121.2 6 string test 2



Figure 61 SNMP Query PATROL Master Agent Dialog Box

3 Click OK.

PATROL writes the information to a PATROL task object (SNMP Query PATROL Master Agent) in the UNIX OS container.

4 Access the SNMP Query PATROL Master Agent task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

Querying the SNMP PATROL platform.km

This task describes how to determine if the PATROL Agent application class can receive SNMP queries. It demonstrates that PATROL can make SNMP requests inside the PATROL Agent and access the platform.km, which is automatically loaded by the agent.

host: <accounting_db_3>listening_port: <1161>community: <public>timeout: <>retries: <>oid: <.1.3.6.1.2.1.1.1.0> SNMP Query Master Agent:errno: 0snmp_get returned: 1.3.6.1.2.1.1.1.0 111 string



To Test the Ability of the Platform.km to Receive Traps


2 Select Test PATROL SNMP System => SNMP Query PATROL platform.km.

PATROL displays the SNMP Query platform.km dialog box.

Figure 62 SNMP Query PATROL Platform.km Dialog Box

3 Click OK.

PATROL writes the information to a PATROL task object (SNMP Query PATROL platform.km) in the UNIX OS container.



4 Access the SNMP Query PATROL platform.km task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

Determining if Any SNMP Managers are Listening

This task describes how to determine if any SNMP Managers are configured in either the agent configuration variable /snmp/piV1m_list or in the SNMP configuration file, snmpmagt.cfg, or both and are listening on the default port. It demonstrates that PATROL can make SNMP queries to the industry standard SNMP query port, 161.

Before You Begin

This task uses the PSL command, Snmp_h_get( ), which automatically uses the port number defined in the agent configuration variable /snmp/default_port.

To determine if any SNMP managers are listening


2 Select Test PATROL SNMP System => SNMP Query Using snmp_h_get( ).

PATROL displays the SNMP Query Using snmp_h_get( ) dialog box.

3 Click OK.

host: <accounting_db_4>listening_port: <1161>community: <public>timeout: <>retries: <>oid: <.2.1.2.1.2.1.2121.1.1.1.6.1.1.0> SNMP Query PATROL <platform>.km:errno: 0snmp_get returned: 2.1.2.1.2.1.2121.1.1.1.6.1.1.0 4 string UNIX



PATROL writes the information to a PATROL task object [SNMP Query Using snmp_h_get( )] in the UNIX OS container.

4 Access the SNMP Query Using snmp_h_get( ) task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

Testing PATROL Event Manager’s Automated SNMP Traps

This task describes how to test whether automatic SNMP traps (that is those based on the PATROL event manager system) are generated by PATROL when a parameter changes state. They demonstrate that certain PATROL Events have the send trap option turned on.

Before You Begin

To generate automatic SNMP traps, at least one SNMP Manager must be registered to receive traps. A list of SNMP Managers are stored in the agent configuration variable /snmp/piV1m_list. The format is host/port/community, where the port and community string default to 162 and public, respectively.

To Test the Event Manager’s Automated SNMP Traps


2 Select Test PATROL SNMP System => Test SNMP Traps from PEM.

PATROL creates a task object entitled Test SNMP Traps from PEM.

PATROL writes the information to a PATROL task object (Test SNMP Traps from PEM) in the UNIX OS container.

host: <inventory_db_dallas>oid: <.1.3.6.1.2.1.1.1.0> SNMP Query using snmp_h_get()... UDP port 161:

NOTE If an SNMP manager is not listening on port 161, PATROL times out and returns an error (errorno=95).



3 Access the Listen for SNMP Traps task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

4 Select one of the following tests: Test PATROL SNMP System =>

■ Set testparm Parameter OK—test PATROL standard event class 9■ Set testparm Parameter Alarm—test PATROL standard event class 11■ Set testparm Parameter Warn—test PATROL standard event class 11

PATROL changes the state of testparm in the SNMPHealth application. PATROL also sends a message to the message area.

Figure 63 State Change Messages Based on Automated Traps

5 Access the Listen for SNMP Traps task object. Your results should resemble this example, a trap for Set testparm parameter to Warn command:


NOTE If you attempt to run a test and the testparm is already in that state (for example, select Set testparm Parameter OK when testparm is already in the OK state), PATROL recognizes this fact and does not send a message to the message area.

From: 27.137.19.172 (2.1.2.1.2.1.2121.1.1.2) Enterprise Specific (4) Uptime: 0 day(s) 20:17:29 (7304900)2.1.2.1.2.1.2121.1.1.2.1.0 93 string Alarm #1 of global parameter 'testparm' triggered on 'SNMPHealth.SNMPHealth'. 1 <= 1.00 <= 12.1.2.1.2.1.2121.1.1.2.2.0 31 string /SNMPHealth/SNMPHealth/testparm2.1.2.1.2.1.2121.1.1.2.3.0 0 string


C h a p t e r 18
18 Monitoring Users
The PATROL Knowledge Module for Unix and Linux gives you the ability to monitor resource consumption by individual users. With it, you can also track the number of users and sessions running on the system. The following sections appear in this chapter.

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375

Viewing Print Jobs that Belong to a User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375Viewing Processes that Belong to a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376Viewing the Amount of Disk Space Consumed by a User . . . . . . . . . . . . . . . . . . 377

Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378Viewing the Number of Users on the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379Viewing the Number of Sessions Running on the System . . . . . . . . . . . . . . . . . . 380


Introduction

IntroductionThe PATROL Knowledge Module for Unix and Linux monitors the resource consumption of individual users as well as the number of users and sessions that run on the system.

For individual users, it monitors

■ the number of print jobs issued by a user■ the amount of disk space consumed by a user■ the number of processes owned by a user

For the systems, it monitors

■ the number of users logged on■ the number of sessions running

Object HierarchyThe USERS application class contains several parameters with information about the number of users logged onto the system and the number of sessions running.


Figure 64 USERS Application Object Hierarchy

OS container

Application class

Parameters

UNIX OS


Resources

ResourcesThe USERS application class enables you to monitor an individual user’s resource consumption. With this feature, you can discover how many resources (CPU, disk space, printer) an individual user is consuming.

The USERS tasks are described in detail on the following pages:

Viewing Print Jobs that Belong to a User

This task describes how to view all print jobs that were requested by a specific user.

Before You Begin

PATROL can list print jobs by user and by printer. This task lists all print jobs owned by a single user. For information on how to view print jobs on a specific printer, see “Viewing All Print Jobs Assigned to a Printer” on page 231.

To List a User’s Print Jobs

1 Access the USERS application menu as described in “Accessing KM Commands and InfoBoxes” on page 402.

2 Select List Print Jobs.

PATROL displays the List Print Jobs dialog box.

Figure 65 List Print Jobs Dialog Box

Task Page

“Viewing Print Jobs that Belong to a User” 375

“Viewing Processes that Belong to a User” 376

“Viewing the Amount of Disk Space Consumed by a User” 377


Resources

3 Type the user name and click Apply.

PATROL writes the results to a PATROL task object (List Print Jobs Users) in the UNIX OS container.

4 Access the List Print Jobs Users task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results.

Viewing Processes that Belong to a User

This task describes how to view all processes that were started by a specific user.

To List a User’s Processes


2 Select Process List.

PATROL displays the Process List dialog box.


PATROL writes the results to a PATROL task object (Process List Users) in the UNIX OS container.

4 Access the Process List Users task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

# PSL Serial No.: #########<NOT INTERACTIVE> List processes for user: 3Suprv 2335 2334 3Suprv S 1768 0 ksh -ksh2450 1 3Suprv S 12168 2 Patrol Patrol dev2463 4747 3Suprv S 1760 0 ksh bin/ksh2334 142 3Suprv S 3728 0 xterm usr/openwin/bin/xterm

-ls -sb -cr -white -display 172.19.137.27:0 -name weights---------------- >>>>> DONE <<<<< ----------------


Resources

Output Format


Viewing the Amount of Disk Space Consumed by a User

This task describes how to view how much disk space a specific user is using.

To List the Amount of Disk Space Consumed by a User


2 Select Disk Space.

PATROL displays the Disk Space dialog box.


PATROL writes the results to a PATROL task object (Disk Space Users) in the UNIX OS container.

pid ppid user s size cput cmd name cmd line

Table 61 Process List Command Output Format

Field Description




s the status of the processI—intermediate0—nonexistentR—runningS—sleepingT—stoppedW—waitingX—growingZ—zombie, terminated


cmd name the first word of the command line that started the process



Numbers

4 Access the Disk Space Users task object as described in “Accessing KM Commands and InfoBoxes” on page 402 and view the results. Your results should resemble this example:

Output Format


NumbersThe USERS application class enables you to monitor the amount of usage in terms of users and sessions. With this feature, you can discover how many users are on the system and how many sessions are running. You can view the information for the present moment in time or in the recent past.

The USERS tasks are described in detail on the following pages:

# PSL Serial No.: #########<NOT INTERACTIVE> show user: 3Suprv disk space information Processing, this might take a while, please wait ...NIS is detected, get information from NIS databaseDisk usage for user: 3Suprv20 /home/3Suprv/pcache/tmp68 /home/3Suprv/pcache/knowledge16 /home/3Suprv/pcache/psl16 /home/3Suprv/nsmail---------------- >>>>> DONE <<<<< ----------------

size /path/

Table 62 Disk Space Command Output Format

Field Description

size the amount of space allocated to a fileFile size is written in 512-byte units, rounded up to the next 512-byte unit. For example, a 513-byte file is reported as using 2 units, 1024 bytes.

/path/ the directory path in which files owned by the user are stored

Task Page

“Viewing the Number of Users on the System” 379

“Viewing the Number of Sessions Running on the System” 380


Numbers

Viewing the Number of Users on the System

This task describes how to view the total number of users on the system at the present time or in the last couple of hours.

To View the Total Number of Users Now on the System

Access the USERS application InfoBox as described in “Accessing KM Commands and InfoBoxes” on page 402.

PATROL displays the USERS InfoBox, which provides the number of users.

Figure 66 USERS InfoBox

To View the Total Number of Users Recently on the System

1 Access the USERS application so that you can view its parameters.

2 Open the USRNoUser parameter.

PATROL displays a graph that shows the number of users on the system over time.


Numbers

Viewing the Number of Sessions Running on the System

This task describes how to view the total number of sessions running on the system at the present time or in the last couple of hours.

To View the Total Number of Session Now Running on the System

Access the USERS application InfoBox as described in “Accessing KM Commands and InfoBoxes” on page 402.

PATROL displays the USERS InfoBox, which provides the number of sessions.

To View the Total Number of Sessions Recently Running on the System

1 Access the USERS application so that you can view its parameters.

2 Open the USRNoSessions parameter.

PATROL displays a graph that shows the number of sessions running on the system over time.


A p p e n d i x A
A Debugging and Running Diagnostics
The PATROL Knowledge Module for Unix and Linux comes equipped with diagnostic and debugging utilities. The following sections appear in this chapter.

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382Unix Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382

Capturing DUMP Information for Selected Components. . . . . . . . . . . . . . . . . . . 383Viewing Installation Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385Capturing Log File Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386

Collector Debug Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388Debugging FILESYSTEM Data Collection (DFColl). . . . . . . . . . . . . . . . . . . . . . . . 388Debugging NETWORK Data Collection (NETColl). . . . . . . . . . . . . . . . . . . . . . . . 389Debugging NFS Data Collection (NFSColl). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390Debugging PRINTER Data Collection (PRINTERColl) . . . . . . . . . . . . . . . . . . . . . 391Debugging PROCESS Data Collection (PSColl) . . . . . . . . . . . . . . . . . . . . . . . . . . . 392Debugging USER and PROCESS Data Collection (USRPROCColl) . . . . . . . . . . 392Debugging CPU, MEMORY, and KERNAL Data Collection (VMColl) . . . . . . . 393Debugging DCM Data Collection (DCMColl) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394

Application Discovery Debug Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395Debugging DISK Discovery Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396Debugging FILESYSTEM Discovery Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396Debugging NETWORK Discovery Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397Debugging PRINTER Discovery Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398Debugging SMP Discovery Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398Debugging SWAP Discovery Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

Application Class Debug Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400Debugging the SCHEDULER Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400


Introduction

IntroductionThe PATROL Knowledge Module for Unix and Linux provides diagnostic and debugging utilities to help pinpoint errors if and when they occur. The capabilities include

■ Viewing installation statistics■ Capturing

— DUMP information for selected components— Log file diagnostics

■ Debugging Collectors for the following application classes:— CPU— FILESYSTEM— KERNEL— MEMORY— NETWORK— NFS— PRINTER— PROCESS— USERS

■ Debugging Discovery for the following application classes:— DISK— FILESYSTEM— NETWORK— PRINTER— SMP— SWAP

Unix DiagnosticsThis PATROL Knowledge Module for Unix and Linux gathers installation and configuration information as well as monitor important operating system log files.

The UNIX OS tasks related to the diagnostic procedures are described in detail on the following pages:

Task Page

“Capturing DUMP Information for Selected Components” 383


Unix Diagnostics

Capturing DUMP Information for Selected Components

This task describes how to gather basic system information. With it, you can gather system information as well as to review the current state of various aspects of PATROL such as which KMs are loaded, how many PSL errors have occurred since the agent started, and which tasks are currently being performed.

To Capture Unix Diagnostic Information

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

2 Select Debug and Diagnostics => Capture Unix Diagnostics.

PATROL displays the Select Categories of Diagnostics dialog box (Figure 67).

Figure 67 Select Categories of Diagnostics Dialog Box

3 Select the %DUMP Options check box.

4 Place the cursor in the Output File for Diagnostics field and type the path and filename to which you want the diagnostic information written.

“Viewing Installation Diagnostics” 385

“Capturing Log File Diagnostics” 386

Task Page


Unix Diagnostics

5 Click Accept.

PATROL displays the DUMP Options dialog box (Figure 68 on page 384).

Figure 68 %DUMP Options Dialog Box

6 Select the check boxes of the components for which you want PATROL to provide information. Table 63 lists the options in alphabetic order.

Table 63 Capture Unix Diagnostics %DUMP Options

Options Description

ALL information about PATROL Agent data structure

APP_INSTS information about each application instances

APPS list of applications

CHANNELS list of open PSL global file channels and open process channels

CONSOLES list of connected consoles

ERRORS list of PSL errors that have occurred since the last reboot

GLOBALS list of global channels

KM_LIST list of loaded KMs

LIBRARIES list of loaded libraries

PARAMS list of PATROL Agent parameters

RTLIST information about processes in the PATROL Agent run-time queue


Unix Diagnostics

7 Click Accept.

PATROL writes the information to the file that you specified in step 4 and to a task object (Capture Unix Diagnostics) in the UNIX OS container.

Viewing Installation Diagnostics

This task describes how to gather PATROL installation information. It writes some general information to a task object and writes the remainder of the information to a log file that you specify.

To Capture Installation Diagnostic Information



PATROL displays the Select Categories of Diagnostics dialog box. To view an example, see Figure 67 on page 383.

3 Select the Installation Diagnostics check box.


5 Click Accept.

PATROL writes the information to a task object (Capture Unix Diagnostics) in the UNIX OS container. Your results should resemble this example:

RUNQ list of items scheduled in the run queue

TASKS provides a list of current tasks

%PSLPS provides a list of current PSL processes


<NOT INTERACTIVE>

The remaining diagnostics will be written to the diagnostic log file but will

not be displayed in the task window.

Table 63 Capture Unix Diagnostics %DUMP Options

Options Description


Unix Diagnostics

Capturing Log File Diagnostics

This task describes how to gather basic system information. With it, you can gather system information as well as to generate debug information for different components of the PATROL Knowledge Module for Unix and Linux.

To Capture Unix Diagnostic Information



PATROL displays the Select Categories of Diagnostics dialog box. To view an example, see Figure 67 on page 383.

3 Select the Log Files check box.


5 Click Accept.

PATROL displays the Select Log Files to Collect dialog box (Figure 69 on page 387).

Capturing Agent Configuration Variables.

Capturing Default Agent Configuration Variables.

Capturing Non-Default/Overridden Agent Configuration Variables.

Capturing diagnostics related to the PATROL installation and environment.

Capturing list of symbolic links under PATROL installation.

Capturing setuid and setgid files that exist under PATROL installation.

Capturing information about apidll, dcm, and bgscollect.

BEST1_HOME directory = /local/Patrol35/Solaris-2-8-sparc-64/best1

Capturing setuid and setgid files that exist under BEST1_HOME installation.

Capturing license details for PATROL installation.

Capturing df -k.

Capturing ls -ld on all directores under /local/Patrol35.

Capturing ls -lRu /local/Patrol35.

Capturing ls -lR /local/Patrol35.

Closing OutputDiagFile: /tmp/PDiag.log


Unix Diagnostics

Figure 69 Select Log Files to Collect Dialog Box

6 Select the check boxes of the log files that you want PATROL to capture. Table 64 lists the options in the order that they appear in the dialog box.

7 Click Accept.

PATROL writes some of the information to a task object (Capture Unix Diagnostics) in the UNIX OS container. PATROL writes the entire contents of all the log files that you selected to the .tar file that you specified.

Table 64 Select Log Files to Collect Options

Options Description

All Logs Contained in $PATROL_HOME/log

gathers log information from all the log files stored in the PATROL log directory

Agent Error Log gathers log information the PATROL Agent

DCM Debug Log gathers log information from the Data Collection Manager executable used in the DCM collection method

apidll Log gathers log information from the C library loaded by the PATROL Agent during runtime so that it can read and write to FIFO

bgscollect Log gathers log information from the bgscollect executable, which accesses the kernel, retrieves the requested data, and writes it to the shared memory segment

MrConsumer Log gathers log information from the MrConsumer library, which is used by DCM to read the data from the shared memory segment written by bgscollect executable


Collector Debug Information

Collector Debug InformationThis PATROL Knowledge Module for Unix and Linux gathers debug information for application collectors. This debugging information is available only for collectors that employ the PSL collection method.

The UNIX OS tasks related to the debugging collectors for various application classes are described in detail on the following pages:

Debugging FILESYSTEM Data Collection (DFColl)

This task describes how to turn the debugging feature on and off for the DFColl parameter, which gathers information for the FILESYSTEM application class.

Task Page

“Debugging FILESYSTEM Data Collection (DFColl)” 388

“Debugging NETWORK Data Collection (NETColl)” 389

“Debugging NFS Data Collection (NFSColl)” 390

“Debugging PRINTER Data Collection (PRINTERColl)” 391

“Debugging PROCESS Data Collection (PSColl)” 392

“Debugging USER and PROCESS Data Collection (USRPROCColl)” 392

“Debugging CPU, MEMORY, and KERNAL Data Collection (VMColl)” 393

“Debugging DCM Data Collection (DCMColl)” 394



Before You Begin

This debug command provides the following information for each monitored file system instance

■ rule state of all instances■ the debug command used to collect information■ the information returned by the command for each instance

— file system blocks— file system block size— file system blocks available— total blocks— available blocks— used blocks— file system block capacity represented as an integer and a decimal— number of files in the file system— number of used i-nodes— file system i-node capacity represented as an integer and a decimal

To Turn Debugging On/Off for DFColl


2 Select Debug and Diagnostics => Toggle DFColl Debug.

Depending upon the collector’s current debug state, PATROL writes one of the following messages to the system output window. TRUE means that debug is turned on. FALSE means that debug is turned off.

When the debug feature is turned on, PATROL writes the debug information to the system output window when the collector runs.

Debugging NETWORK Data Collection (NETColl)

This task describes how to turn the debugging feature on and off for the NETColl parameter, which gathers information for the NETWORK application class.

CCYY0621151414 DFColl debug set to TRUE

CCYY0621151414 DFColl debug set to FALSE



To Turn Debugging On/Off for NETColl


2 Select Debug and Diagnostics => Toggle NETColl Debug.



Debugging NFS Data Collection (NFSColl)

This task describes how to turn the debugging feature on and off for the NFSColl parameter, which gathers information for the NFS (network file system) application class.

Before You Begin

This debug command provides the following information for the network file system.

■ call information for — server rpc: connectionless and connection-oriented— server nfs: versions 2 and 3— server nfs_acl: versions 2 and 3— client rpc: connectionless and connection-oriented— server nfs_acl: version 2 and 3

■ values of the last nfs_stat command ■ cross-reference list between file systems■ delta data■ values of the current nfs_stat command

CCYY0621151414 NETColl debug set to TRUE

CCYY0621151414 NETColl debug set to FALSE



To Turn Debugging On/Off for NFSColl


2 Select Debug and Diagnostics => Toggle NFSColl Debug.



Debugging PRINTER Data Collection (PRINTERColl)

This task describes how to turn the debugging feature on and off for the PRINTERColl parameter, which gathers information for the PRINTER application class.

To Turn Debugging On/Off for PRINTERColl


2 Select Debug and Diagnostics => Toggle PRINTERColl Debug.



CCYY0621151414 NFSColl debug set to TRUE

CCYY0621151414 NFSColl debug set to FALSE

CCYY0621151414 PRINTERColl debug set to TRUE

CCYY0621151414 PRINTERColl debug set to FALSE



Debugging PROCESS Data Collection (PSColl)

This task describes how to turn the debugging feature on and off for the PSColl parameter, which gathers information for the PROCESS application class.

Before You Begin

This debug command provides the following information for the processes running on the system.

■ machine type and operating system level■ the Unix list active processes (ps) command output■ results from previous Unix active process command■ list of process by process ID■ size of the processes■ runtime of the processes■ number of total processes■ number of shared processes

To Turn Debugging On/Off for PSColl


2 Select Debug and Diagnostics => Toggle PSColl Debug.



Debugging USER and PROCESS Data Collection (USRPROCColl)

This task describes how to turn the debugging feature on and off for the USRPROCColl parameter, which gathers information for the PROCES and USER application classes.

CCYY0621151414 PSColl debug set to TRUE

CCYY0621151414 PSColl debug set to FALSE



Before You Begin

This debug command provides the following information for users and the processes that they are running on the system.

■ nonroot logins■ nonroot users with processes■ user process statistics

— number of user processes— average number of processes per user— total number of processes— number of zombie processes

To Turn Debugging On/Off for USRPROCColl


2 Select Debug and Diagnostics => Toggle USRPROCColl Debug.



Debugging CPU, MEMORY, and KERNAL Data Collection (VMColl)

This task describes how to turn the debugging feature on and off for the VMColl parameter, which gathers information for the CPU, MEMORY, and KERNEL application classes.

CCYY0621151414 USRPROCColl debug set to TRUE

CCYY0621151414 USRPROCColl debug set to FALSE



Before You Begin

This debug command provides the following information for the system’s cpu, memory, and kernel using the vmstat command.

■ the number of running, blocked, and waiting processes■ swap and free memory sizes■ paging statistics■ disk statistics■ faults statistics■ cpu statistics

To Turn Debugging On/Off for VMColl


2 Select Debug and Diagnostics => Toggle VMColl Debug.



Debugging DCM Data Collection (DCMColl)

This task describes how to turn the debugging feature on and off for the DCMColl parameter.

20010621151414 VMColl debug set to TRUE

20010621151414 VMColl debug set to FALSE

NOTE This task does not provide debugging information for the DCM collection method. Rather, it provides debugging information for the PSL collector that monitors the DCM collection method and that populates the DCM parameters.


Application Discovery Debug Information

Before You Begin

The command is a toggle, which means that when you select it, PATROL sets the collectors debug state to the opposite of its current state. If debug is on, selecting this command turns it off. If debug is off, selecting this command turns it on.

To Turn Debugging On/Off for DCMColl


2 Select Debug and Diagnostics => Toggle DCMColl Debug.


Application Discovery Debug InformationThis PATROL Knowledge Module for Unix and Linux gathers debug information for application discovery. This debugging information is available only for a subset of the application classes that employ the PSL collection method.

The UNIX OS tasks related to the debugging discovery for various applications are described in detail on the following pages:

CCYY0621151414 DCMColl debug set to TRUE

CCYY0621151414 DCMColl debug set to FALSE

Task Page

“Debugging DISK Discovery Process” 396

“Debugging FILESYSTEM Discovery Process” 396

“Debugging NETWORK Discovery Process” 397

“Debugging PRINTER Discovery Process” 398

“Debugging SMP Discovery Process” 398

“Debugging SWAP Discovery Process” 399



Debugging DISK Discovery Process

This task describes how to turn the debugging feature on and off for the DISK application discovery process.

Before You Begin

This debug command provides the following information about the DISK discovery process.

■ access rates— reads per second— writes per second

■ amount of data processed— kilobytes read per second— kilobytes written per second

■ transactions service— average number of transactions waiting for service— average number of transactions actively being serviced— average service time in milliseconds

To Turn Debugging On/Off for DISK Discovery


2 Select Knowledge Module Admin => DISK Application => Toggle DISK Disc. Debug.

Depending upon the current debug state, PATROL writes one of the following messages to the system output window. TRUE means that debug is turned on. FALSE means that debug is turned off.

Debugging FILESYSTEM Discovery Process

This task describes how to turn the debugging feature on and off for the FILESYSTEM application discovery process.

CCYY0621151414 DISK debug set to TRUE

CCYY0621151414 DISK debug set to FALSE



Before You Begin

This debug command provides the following information about the FILESYSTEM discovery process.

■ mounted systems■ file system instances

— name— PATROL object labels— PATROL object rule state— file system type— machine type— options

To Turn Debugging On/Off for FILESYSTEM Discovery


2 Select Knowledge Module Admin => FILESYSTEM Application => Toggle FILESYSTEM Disc. Debug.


Debugging NETWORK Discovery Process

This task describes how to turn the debugging feature on and off for the NETWORK application discovery process.

To Turn Debugging On/Off for NETWORK Discovery


2 Select Knowledge Module Admin => NETWORK Application => Toggle NETWORK Disc. Debug.

CCYY0621151414 FILESYSTEM debug set to TRUE

CCYY0621151414 FILESYSTEM debug set to FALSE




Debugging PRINTER Discovery Process

This task describes how to turn the debugging feature on and off for the PRINTER application discovery process.

To Turn Debugging On/Off for PRINTER Discovery


2 Select Knowledge Module Admin => PRINTER Application => Toggle PRINTER Disc. Debug.


Debugging SMP Discovery Process

This task describes how to turn the debugging feature on and off for the SMP application discovery process.

To Turn Debugging On/Off for SMP Discovery


2 Select Knowledge Module Admin => SMP Application => Toggle SMP Disc. Debug.

CCYY0621151414 NETWORK debug set to TRUE

CCYY0621151414 NETWORK debug set to FALSE

CCYY0621151414 PRINTER debug set to TRUE

CCYY0621151414 PRINTER debug set to FALSE




Debugging SWAP Discovery Process

This task describes how to turn the debugging feature on and off for the SWAP application discovery process.

To Turn Debugging On/Off for SWAP Discovery


2 Select Knowledge Module Admin => SWAP Application => Toggle SWAP Disc. Debug.


CCYY0621151414 SMP debug set to TRUE

CCYY0621151414 SMP debug set to FALSE

CCYY0621151414 SWAP debug set to TRUE

CCYY0621151414 SWAP debug set to FALSE


Application Class Debug Information

Application Class Debug InformationThis PATROL Knowledge Module for Unix and Linux gathers debug information for some application classes. This debugging information is available only for a subset of the application classes.

The tasks related to debugging various applications are described in detail on the following pages:

Debugging the SCHEDULER Application

This task provides information about how to collect PSL debugger data for the SCHEDULER application. For more information about PSL debugger information, see the PATROL Script Language Reference Manual Volume 1—PSL Essentials, or the PATROL Scheduler PSL Debugger dialog box online Help topic.

To Collect PSL Debugger Data for the SCHEDULER Application


2 Select Scheduling Debug from the pop-up menu.

The PATROL Scheduler PSL Debugger dialog box is displayed.

3 Select the check boxes for the PSL debug options that you want to turn on, and click Accept.

The left side PATROL begins collecting debug data for the options that you selected. Debug information is displayed in the System Output Window.

Task Page

“Debugging the SCHEDULER Application” 400

NOTE The left side of the dialog box controls debug options for the scheduler daemon. The right side of the dialog box controls debug options for the graphical user interface (GUI). Debug information is only sent to the PATROL Agent Console window when the area being debugged is active. The PATROL KM for Unix does not generate debug data when the scheduler daemon is sleeping, or the GUI is not being used.


A p p e n d i x B
B Loading, Unloading, and Navigating KMs in the PATROL Consoles
BMC Software, Inc. offers several PATROL consoles from which you can view a PATROL Knowledge Module (KM). Due to the environments in which these consoles run, each one uses different methods to display and access information in the KM. This appendix provides instructions on how to access the KM menu commands and InfoBoxes, and how to access the online Help for the KM using each of the PATROL consoles.

Accessing KM Commands and InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402Using the Mouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404

Using the Mouse to Perform Tasks in PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . 405


Accessing KM Commands and InfoBoxes

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

Accessing Online HelpTable 66 on page 403 provides information about how to access Help on each console.

Table 65 Accessing KM Commands and InfoBoxes

ConsoleTo access menu commands

To accessInfoBoxes


Right-click the application icon and choose KM Commands.

Right-click the application icon to display its pop-up menu and then choose InfoBox.

PATROL Console for Unix Right-click the application icon. Click MB2 on the instance icon.


From an application’s page, click KM Commands.

In either Tree View or Work Area, right-click a PATROL object and choose InfoBox from the pop-up menu.

PATROL Central - Web Edition Right-click the application icon and choose Knowledge Module Commands.

From the Monitored Systems page, click the system that you want, and click the Infobox tab to view the InfoBox for that system.

To view the InfoBox for an application, drill down into a Monitored System until you can click the application instance that you want, and click the Infobox tab.

NOTE If you are trying to access Help from a Unix console, you may want to refer to the PATROL Installation Guide for specific instructions on how to install and setup a browser in the Unix environment.


Accessing Online Help

Table 66 Accessing Online Help (Part 1 of 2)





Right-click the PATROL for Unix and Linux application icon and choose KM Commands => Product Help.

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

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

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

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

Double-click the parameter in the KM tab of the console; then click the Help tab and Show Help in the properties dialog box.


■ Right-click the PATROL for Unix and Linux application icon 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. Then click Show Help in the Application Definition dialog box.

Right-click the parameter icon, and click Help On.


Using the Mouse

Using the MousePATROL assumes that you are using a two-button mouse. On some workstations that have a three-button mouse, clicking the middle mouse button is equivalent to clicking both buttons of a two-button mouse simultaneously.

The instructions in this book are written from a right-hand mouse perspective. If you have a left-hand mouse, or have reconfigured your mouse, you will need to make the appropriate substitutions when you are following the instructions in this book. Figure 70 illustrates the typical right- and left-handed mouse configurations.

Figure 70 Mouse Button Configuration


From the console menu bar, choose Help => Help Topics. Then double-click the name of your KM.

From the Operator tab of the console, expand or collapse the list to find the application class. Click the What’s this? Help button and then

click the application class name.

Double-click the parameter icon to open its display window. Click the Help button.

PATROL Central - Web Edition

Click the Help link, and then click the link for your KM.

Click the link for the application class, and then click the Page Help link.

Click the link for the parameter, and then click the Page Help link.

Table 66 Accessing Online Help (Part 2 of 2)





Using the Mouse

Using the Mouse to Perform Tasks in PATROL

You can use the mouse to perform various tasks within the PATROL KM for Unix. The following list provides information about which mouse button(s) should be used to perform several common tasks.

■ Push-buttons are activated by clicking the left mouse button (MB1).

■ InfoBoxes are displayed by clicking the left and right mouse buttons simultaneously, or by clicking the middle mouse button (MB2) on a three-button mouse.

■ Menus are activated by clicking the right mouse button (MB3).

NOTE PATROL creates menus dynamically, so there may be a delay when you access menus. Click and hold down MB3 until the pop-up menu is displayed.


Using the Mouse


A p p e n d i x C
C Regular Expressions
This appendix describes how to use regular expressions in the context of the PATROL Knowledge Module for Unix and Linux. Not all components of the PATROL KM for Unix and Linux support regular expressions. This appendix lists the components that support regular expressions, defines the regular expression character set for PATROL KM for Unix and Linux, and provides some examples. The following sections appear in this appendix.

Components that Use Regular Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409

Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410Conventions for Using Regular Expressions with PATROL Objects . . . . . . . . . . . . . 411

Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410


Components that Use Regular Expressions

Components that Use Regular ExpressionsThe following components of the PATROL KM for Unix and Linux use regular expressions.

■ PRINTER— exclusion list

■ SECURITY— List SUID and SGID Permission

■ File Name field■ File Owner field■ File Group field


Characters

CharactersYou can use the following special characters when creating a regular expression.

NOTE In PATROL KM for Unix and Linux, the parenthesis ( ) and pipe | characters are paired with a backslash \. This pairing varies from the standard regular expression character set.

Table 67 Regular Expression Characters

Character Description

. (period) matches any single character

* (asterisk) matches zero or more instances of the previous pattern item

+ (plus sign) matches one or more instances of the previous pattern item

? (question mark) matches zero or one instances of the previous pattern item

\(\ ) (backslash and parenthesis)

groups a sub-pattern

The repetition and alternation operators apply to the whole proceeding subpattern.

\| (backslash and vertical bar or pipe)

provides an alternative

This character functions similarly to a logical OR.

[ ] (brackets) delimits a set of characters

Ranges are specified as [x-y]. If the first character in the set is ^, then there is a match if the remaining characters in the set are not present.

^ (caret) anchor the pattern to the beginning of the string

This character applies only when first.

$ (dollar sign) anchor the pattern to the end of the string

This character applies only when last.


Characters

Examples

The following examples illustrate how to use regular expressions.

any two-character string

..—matches any two characters

upper and lower case

[Ww]arning—matches Warning or warning.

exclusion

[^a-zA-Z]—matches anything except uppercase and lowercase letters.

a character followed by zero or more occurrences of a character

st*—matches a string that contains an s followed by zero or more t’s.

repeated sequences

$st$+—matches a string that has one or more sequences of st.

anything

.*—matches anything.

word regardless of case

warning\|Warning—matches warning or Warning.

space or tabs that precede a string

^[ \t]+—matches any string that begins with spaces or tabs.


Conventions for Using Regular Expressions with PATROL Objects


In regular expressions, when specifying PATROL objects (/computer:/application/instance/parameter) or pathnames (/directory/subdirectory/subdirectory/file), remove the initial slash and substitute dashes for the remaining slashes.

Format

For a file, the format for a regular expression is

For a PATROL object, such as a parameter, the format for a regular expression is

Examples

The following examples illustrate how to use regular expressions with PATROL objects and pathnames.

a directory or object

tmp—matches tmp directory

directories or objects with a similar name

usr[1-9].*—matches usr1 through usr9

directory-subdirectory-subdirectory-file

computer:-application-instance-parameter

EXAMPLE The file system /app/oracle/usr would be represented as app-oracle-usr in a regular expression.



subdirectories

etc-test—matches directory or file system /etc/test

objects with similar names in object hierarchies

nerd:-DISK-sb[0-9].*—matches any disk with a prefix of sb0 through sb9 on the computer nerd

PRINTER-.*[Hh]ouston.*—matches any printer with the word Houston, capitalized or in all lowercase, in its name


A p p e n d i x D
D Inclusion and Exclusion Lists
The PATROL Knowledge Module for Unix and Linux gives you the ability to determine which instance PATROL monitors for the DISK, FILESYSTEM, and PRINTER applications. The following sections appear in this chapter.

Using Exclusion and Inclusion Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414Methods for Creating Exclusion and Inclusion Lists . . . . . . . . . . . . . . . . . . . . . . . 414Storage Location of Exclusion and Inclusion Lists . . . . . . . . . . . . . . . . . . . . . . . . . 415

Benefits and Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415Benefits of Creating Exclusion Lists Using Menu Commands . . . . . . . . . . . . . . . 415Inclusion List Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416


Using Exclusion and Inclusion Lists

Using Exclusion and Inclusion ListsPATROL is designed to monitor all the instances that it discovers. However, some application classes, such as DISKS, FILESYSTEMS, and PRINTERS, allow the user to select which instances PATROL monitors. PATROL provides this feature through exclusion and inclusion lists.

The exclusion list is a mechanism for ignoring a small number of instances. If you want PATROL to ignore a majority of instances, you can create an inclusion list, which forces PATROL to ignore all but the instances that you specify.

Methods for Creating Exclusion and Inclusion Lists

PATROL provides three different ways to create exclusion and inclusion lists and subsequently create and populate the associated configuration variables. You can create the list by using

■ the Stop Monitoring menu command from DISK, FILESYSTEM, or PRINTER instances (exclusion list only)

■ the Edit <application> Exclusion List menu command from DISK, FILESYSTEM, or PRINTER instances (exclusion list only)

■ pconfig tool

NOTE When using xpconfig or wpconfig to create an exclusion list, add both entries (pathname-instance and /pathname/instance) for each instance that you intend to exclude. For more information, see “Benefits of Creating Exclusion Lists Using Menu Commands” on page 415.


Benefits and Limitations

Storage Location of Exclusion and Inclusion Lists

PATROL uses variables in the PATROL configuration database to store information about exclusion and inclusion lists. The two variables are

■ /AgentSetup/application.filterList—contains the list of instances to include or exclude depending upon the value of application.filterType

The format is a comma-separated list of instances or regular expressions. The variable has a limit of 1024 characters. Regular Expressions can be used to alleviate this limitation. The error:

Exclusion list too long. Please use regular expression exclusion.

is generated when a filter exceeds the maximum size allowed for an Agent configuration variable.

■ /AgentSetup/application.filterType—determines whether the list is an exclusion or inclusion

If application.filterType does not exist, the list defaults to exclude. Valid values are

— exclude— include

Benefits and LimitationsThe exclusion list feature is designed for ignoring a small number of instances. If you want PATROL to ignore a majority of instances, you can create an inclusion list, which forces PATROL to ignore all but the instances that you specify. However, monitoring by inclusion has a few limitations.

Benefits of Creating Exclusion Lists Using Menu Commands

BMC Software recommends that you use the menu options Stop Monitoring and Edit <application> Exclusion List to exclude application instances. These menu options are accessed from the pop-up menu of the instances.


Benefits and Limitations

The menu commands add two entries into the /AgentSetup/application.filterList for each instance excluded.

■ The first entry is in the form pathname-instance, where slashes are replaced by dashes and the initial slash is omitted.

This entry is used by the collector in setting the consumer variables.

■ The second entry is in the form /pathname/instance.

This entry is used to display the instance in the <application> Exclusions dialog box. If you omit this entry, the instance will not appear in the dialog box.

Inclusion List Limitations

Monitoring application instances by using an inclusion list disables some of the instance’s features and requires the user to perform additional tasks.

■ PATROL will not automatically monitor any new instances.

■ The Stop Monitoring menu command on an application will not work. Initially, the instance will disappear from the list of monitored instances. However, the instance reappears during the next discovery cycle.

EXAMPLE mnt-hpserv-users indicates the file system /mnt/hpserv/users.

EXAMPLE /mnt/hpserv/users indicates the file system /mnt/hpser/users.

NOTE The user assumes full responsibility for maintaining this list.


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/snmp/default_port variable 369/SNMP/default_r_community variable 366/snmp/piV1m_list variable 369, 370/snmp/trap_port variable

default value 364

Aaccessing

InfoBoxes 405menu commands 405push-buttons 405

accountsNetwork Information System (NIS), listing 218

activatingapplication classes 100parameters 100PRINTER application class 225

Address Resolution Protocol (ARP)cache, adding hosts 205cache, deleting hosts 203cache, viewing 202

addresseshost, listing 187host, output format 188internal state 184IP, listing 187IP, output format 188Network IP, determining 191network, output format 185network, viewing 184remote, viewing 184

ALL_COMPUTERS application classparameters 50

application classesactivating 100COMPOSITE, hierarchy 118description 22HEALTH AT A GLANCE 158icons 22NFS 214PRINTER, activating 225PRINTER, object hierarchy 224PROCESS, object hierarchy 244PROCESS_PRESENCE, object hierarchy 244SCHEDULER, object hierarchy 312SECURITY, object hierarchy 340SNMPHealth, object hierarchy 352

application menus

COLLECTOR 33COMPOSITES 33COMPOSITES_COLLECTOR 33Computer Instance 30CPU 34DCM 34DISK 34FILESYTEM 35HEALTH AT A GLANCE 36KERNEL 36MEMORY 36NETWORK 37NFS 38PATROL 38PATROLAGENT 39PRINTER 41PROCCONT 42PROCESS_PRESENCE (PROCCONT) 42PROCPRES 43SMP 44SNMPHealth 45SWAP 46UNIX OS 31USERS 47

Bbang path, Unix to Unix Communication Protocol (UUCP)

206blackout

cancelling a scheduled script 337creating a script 327deleting a script 334modifying a script 331specifying a script default directory 326viewing a script 330

BMC Software, contacting 2build date

viewing, kernel 112

Ccache

Address Resolution Protocol (ARP), adding hosts 205Address Resolution Protocol (ARP), deleting hosts

203Address Resolution Protocol (ARP), viewing 202

CD-ROM systemsexclusion from file system monitoring 140

collectingPSL debug data 322–325

COLLECTORS application classdata collection methods 88icons 22menus 33

Index 417


object hierarchy 88parameters 51

commandsFile Transfer Protocol (ftp), supported by PATROL

198msu attempts, listing failed 345Ping, using in PATROL 199rlogin 200set user (su) attempts, listing failed 345Stop Monitoring 144

COMPOSITE application classobject hierarchy 118

composite parameterscreating 118creating expressions 119creating expressions manually 124creating expressions with the wizard 121expressions, deleting 126expressions, editing 125expressions, examples 120expressions, syntax rules 120icon 119instances 118object hierarchy 118relational operators 118setting the status 121

COMPOSITES application classmenus 33object hierarchy 118parameters 52

COMPOSITES_COLLECTOR application classicons 22menus 33parameter icons 22parameters 52

Computer Instance application classicons 22menus 30

computer systemstrusted 198

configurationmouse 404PATROL SNMP, listing 356PATROL SNMP, saving in ASCII file 357

configuringactivating application classes 100activating parameters 100

context switches, CPU statistics 109counters, resetting for NFS servers 217CPU

detection 108hogs, list output format 297hogs, viewing 295multi-processor, viewing statistics 110processes using excessive amounts, viewing 295viewing, top ten processes using 297

CPU application class

418 PATROL® Knowledge Module® for Unix User Guid

icons 22menus 34object hierarchy 106parameters 52

CPU usagemonitoring, overall system usage 159

CPU utilizationidle time, viewing 108interrupts, viewing data 109monitoring 106monitoring, detection 108multi-processor, statistics 110percentage used 108run queue, viewing 109switches, viewing 109system mode, viewing 108user time, viewing 108viewing 108waits, viewing 109

cross-platform monitoring 216customer support 3

DData Collection Manager (DCM)

data collection methods 91data collection methods

application classes 88changing 98COLLECTORS application class 88Data Collection Manager (DCM) 91DCM 90, 92DCM application class 89DCM, parameters 91determining which is used 98kernel-level data 91managing 98object hierarchies 88PATROL Perform Collection 91PATROL Perform collector 91PATROL PSL 95PSL parameters, activated 95Unix utilities 92, 95

dblk statistics, viewing 181DCM

collection method 90DCM application class

data collection methods 89icons 22menus 34object hierarchy 89parameters 53

DCM collection methodgathering data 92

DCM data collectiondeactivated parameters 93

e


parameters 91selecting 98

deactivated parametersDCM data collection 93PSL data collection 95

debug data 322deleting

files, by characteristics 153files, by date updated 155files, by group 155files, by name 155files, by owner 155files, on single physical disk 155files, output format 156semaphores 168shared-memory segments 166

destination networks, listing 192device names, file system mounting 148devices

network, obtaining information 202directories

Unix to Unix Communication Protocol (UUCP) 206discovery

mounted disks 128network interface, name 179

DISK application classicons 22menus 34object hierarchy 128parameters 56

disk monitoringexcluding 130exclusion list 414inclusion list 414resuming 132resuming monitoring 131resuming on all disks 133selecting disks 131

disksdiscovery 128files, removing on single disk 155synchronizing file system cache 149

Eentries

viewing statistics 114exclusion list 414

file systems 138exclusion lists

disks, monitoring 130expressions

composite parameter wizard 121composite parameters, creating 119composite parameters, editing 125composite parameters, examples 120

composite parameters, syntax 120composite parameters, syntax rules 120creating manually, composite parameters 124deleting, composite parameters 126regular, disk monitoring 131regular, file searches 151regular, file system monitoring 139

Ffile system capacity

managing 141file system cleanup

automating 141recovery actions, attended mode 143

file system monitoringCD-ROM exclusion 140exclusion by type 140exclusion list 414exclusion lists 138inclusion 139inclusion list 414NFS systems, excluding 140process control systems, exclusion 140regular expressions 139

file system searchesoutput format 152

File Systemsexclude from being monitored 144monitoring 144

file systemscache, synchronizing to disk 149device names, mounting 148monitoring, overall usage 159mounting 146mounting, automatic 147mounting, manual 147mounting, paths 148NFS servers, listing 216NFS, resetting counters 217searching 150searching, on single physical disk 151unmounting 148unmounting, automatically 148unmounting, manually 149

File Transfer Protocol (ftp)commands, supported by PATROL 198using with PATROL 198

filescopying, File Transfer Protocol (ftp) 198copying, Unix to Unix Communication Protocol

(UUCP) 208deleting based on characteristics 153deleting, based on name 155deleting, by date updated 155deleting, by group 155

Index 419


deleting, by owner 155deleting, on single physical disk 155global-write privilege, viewing 344locating 150locating, by date updated 151locating, by file name 151locating, by group 151locating, by owner 151locating, on single physical disk 151locating, output format 152locating, SGID-protected 341locating, SUID-protected 341removing, output format 156SGID-protected, listed output format 343SGID-protected, listing 341SUID-protected, listed output format 343SUID-protected, listing 341transferring, File Transfer Protocol (ftp) 198Unix to Unix Communication Protocol (UUCP) 206Unix to Unix Communication Protocol (UUCP) log,

viewing 210Unix to Unix Communication Protocol (UUCP),

deleting 207FILESYSTEM application class


filesystem table, recording mounts 148

Gglobal write privilege files, listing 344group process ID

listing nice value of processes 301groups

Network Information System (NIS), list output 220Network Information System (NIS), listing 219

HHEALTH AT A GLANCE application class 158


helpaccessing in a PATROL Console for Windows 26accessing in PATROL Central - Web Edition 26accessing in PATROL Central - Windows Edition 26accessing in PATROL Console for Unix 26online 25

host addresseslisting 187output format 188


hostsadding to Address Resolution Protocol (ARP) cache

205deleting from Address Resolution Protocol (ARP)

cache 203trusted, listing 198Unix to Unix Communication Protocol (UUCP),

listing 210

II/O operations

CPU statistics, waiting 109icons

application classes 22composite parameter instance 119

inclusion list 414InfoBoxes

accessing with the mouse 405i-nodes

entries, viewing files located 114slots, viewing used 114slots,viewing statistics 114viewing conversions 114

interrupts, CPU statistics 109IP address

obtaining 202IP addresses

determining 191listing 187output format 188

IPV4 protocol, viewing statistics 191

Jjob

modifying a scheduled script 321removing a scheduled script 321scheduling a command interpreter script 315scheduling a PSL script 318scheduling an operating system command script 313

jobsprint, viewing for one printer 231printer, deleting all from a print queue 234printer, moving all jobs 236printer, moving one job 235printers, listing for system 232

Kkernel

build date, viewing 112dynamically allocated memory 113memory allocation, viewing 113memory requests 113

e


monitoring resources 106monitoring, detection 112viewing system usage 115

KERNEL application classicons 23menus 36object hierarchy 111parameters 59

kernel dataactive semaphores 115directory block reads 115message operations per second 115percentage of file slots used 115percentage of used lock slots 115percentage of used process slots 115system calls 115

kernel memory allocation (KMA), viewing 113kernel-level data

collection methods 91km

plug-in 304knowledge module

plug-in 304

Llarge memory requests

viewing allocated amounts 113viewing available amounts 113viewing failed amounts 113

linkblk statistics, viewing 181locating

files, by date updated 151files, by group 151files, by owner 151files, on single physical disk 151files, search output format 152

locating, files 150log files

Unix to Unix Communication Protocol (UUCP), viewing 210

loginsremote, using with PATROL 200

MMachine Access Control (MAC)

obtaining 202Management Information Base (MIB)

checking SNMP information 357managing

data collection 98file system capacity 141semaphores 167

mblk statistics, viewing 181

memorySee also virtual memorysemaphores, viewing statistics 167

MEMORY application classicons 23menus 36object hierarchy 163parameters 62

memory bufferallocation failures, viewing 181

memory buffersstatistics, output format 183statistics, viewing 181

memory requestscategories 113large, viewing allocated amount 113large, viewing available amount 113large, viewing failed amounts 113oversized, viewing allocated amounts 113small, viewing allocated amounts 113small, viewing available amounts 113small, viewing failed amounts 113viewing failed amounts 113

menu commandsaccessing with the mouse 405

menusCOLLECTOR application 33COMPOSITES application 33COMPOSITES_COLLECTOR application 33Computer Instance application 30CPU application 34DCM application 34DISK application 34FILESYTEM application 35HEALTH AT A GLANCE application 36KERNEL application 36location of KM commands 29MEMORY application 36NETWORK application 37NFS application 38PATROL application 38PATROLAGENT application 39PRINTER application 41PROCCONT application 42PROCESS_PRESENCE (PROCCONT) application 42PROCPRES application 43SECURITY application 44SMP application 44SNMPHealth application 45SWAP application 46UNIX OS application 31USERS application 47

modifyinga scheduled task defined by a script 321

monitoringblackout

cancelling a scheduled script 337

Index 421


creating a script 327deleting a script 334modifying a script 331specifying a default directory for scripts 326viewing a script 330

CPU usage, overall for system 159CPU utilization 106CPU utilization, viewing statistics 108cross-platform 216disks, excluding 130disks, resuming for all 133disks, selecting 131file system usage, overall for system 159file systems, excluding 138file systems, selecting 139kernel resources 106kernel, detection 112network data, activating 176overall system health 158poll time, parameters 92printers, excluding 227printers, including 227printers, jobs in queue 228processes waiting on resources 298processes, configuring a process to alarm when its

PPID is not 1 262processes, configuring a process to alarm when its

PPID is owned by unauthorized user 265processes, configuring a process to alarm when

number exceeds set limit 250processes, configuring a process to alarm when

number falls below set limit 253processes, configuring a process to stop 259processes, configuring a process to suspend alert for n

cycles if not running 268processes, configuring communication for a process

host group 284processes, configuring multiple instances of 247processes, configuring to restart a process when it

dies 256processes, creating a host group 283processes, deleting a process from the monitoring

queue 278processes, modifying host attributes in a process host

group 285processes, modifying the configuration of a process

270processes, non-root 298processes, querying a host within a process host

group 286processes, removing a host from a process host group

286processes, reporting on monitored processes 280processes, resuming monitoring for a suspended

process 280processes, specifying a flag file directory 279processes, suspending monitoring for a process 280


processes, synchronizing a local host’s list to a selected host’s list for a process host group 288

processes, synchronizing a local process’s list with a selected process’s list 289

processes, synchronizing a selected host’s list to a local host’s list for a process host group 288

processes, synchronizing a selected process’s list with the local process’s list 290

processes, using most CPU 295processes, viewing the process list for a selected host

289processes, viewing the process presence list for a

selected process 291resuming for a single disk 132status, parameters 92suspend

cancelling a scheduled blackout script 337creating a blackout script 327deleting a blackout script 334modifying a blackout script 331specifying a default directory for blackout scripts

326viewing a blackout script 330

swap space usage, overall for system 159total processes running 295zombie processes, viewing total on system 292

mounting file systems 146automatically 147device names 148filesystem table 148manually 147

mouse usage 404accessing InfoBoxes 405accessing menu commands 405accessing push-buttons 405

msu commandfailed execution, list of users 345

multiple sessionsrunning, listing users 348

multi-processor CPUs, viewing statistics 110

Nname server, querying 201NETWORK application class

activating 176icons 23menus 37object hierarchy 175parameters 66

Network File System (NFS)application class 214counters, resetting 217object hierarchy 215servers, listing 216


e


accounts, listing 218accounts, output format 219groups, list output 220groups, listing 219servers, list output format 221servers, listing 220

network instancedestroying when unavailable 181

network instancesalarming when unavailable 181PATROL behavior when unavailable 180

network interfacesname discovery 179output format 179viewing 178

Network IP addresses, determining 191networks

active uses per route 192addresses, internal state 184addresses, output format 185addresses, viewing 184dblk statistics, viewing 181destination, listing 192devices, obtaining information 202gateways, listing 192interface used 192IP address, obtaining 202linkblk statistics, viewing 181listing trusted hosts 198mblk statistics, viewing 181node, physical address 202packets sent per route 192packets, errors 194packets, statistics 194protocol version, viewing 184protocol, viewing 191protocols, listing 189protocols, output format 190qband statistics, viewing 181querying name server 201queue statistics, viewing 181receive queue size, viewing 184receive window size, viewing 184remote address, viewing 184route designation, viewing 192router status, viewing 192send queue size, viewing 184send window size, viewing 184sockets, viewing data 184, 185statistics, viewing 192stream statistics, viewing 181strevent statistics, viewing 181subnet mask, obtaining 202synq statistics, viewing 181

NFS application classicons 23menus 38

parameters 66NFS systems

exclusion from file monitoring 140nice values

changing for a process 300node

physical address, obtaining 202non-VME device interrupts, viewing 109

Ooversized memory requests

viewing allocated amounts 113viewing failed amounts 113

Ppackets

errors, monitoring 194network, viewing sent 192statistics 194

parametersactivating 100COLLECTORS application class 51composite, creating 118COMPOSITES application class 52COMPOSITES_COLLECTOR application class 52COMPUTERS application class 50CPU application class 52DCM application class 53DCM collection method 91deactivated, DCM collection method 93deactivated, DCM data collection 93deactivated, PSL data collection 95default settings 80–86DISK application class 56FILESYSTEM application class 58HEALTH AT A GLANCE application class 58KERNEL application class 59MEMORY application class 62NETWORK application class 66NFS application class 66PATROLAGENT application class 71PRINTER application class 71PROCCONT application class 71PROCESS application class 72PROCPRES application class 73PSL data collection 95SCHEDULER application class 74SMP application class 74SNMPHealth application class 77SWAP application class 78USERS application class 79

partitions, swap area size 172passwords

Index 423


listing users without a password 346paths

file system mounting 148PATROL

File Transfer Protocol (ftp), supported commands 198mouse usage 404ping, supported commands 199rlogin, supported commands 200SNMP architecture 353

PATROL Agentport number, default 353querying 366receiving SNMP queries, testing 367SNMP queries, testing 366system role 354

PATROL application classicons 23menus 38

PATROL Console for Microsoft Windowsmenu command location 29

PATROL Console for Unixmenu command location 29

PATROL Event Managerautomated SNMP traps, testing 370

PATROL Perform Agent-Ctrl parameters 92data collection methods 91

PATROL PSL collectors-Coll parameters 92

PATROL SNMPconfiguration information, listing 356configuration, saving in ASCII file 357

PATROL SNMP Managersystem role 354

PATROL SNMP Master Agentport number, default 353starting 361system role 354

PATROL SNMP Sub-agentsystem roles 354

PATROLAGENT application classicons 23menus 39parameters 71

permissionssemaphores, viewing 167

pingusing with PATROL 199

plug-insknowledge module 304

poll time monitoringparameters 92

port numbersPATROL Agent, default 353PATROL SNMP Master Agent, default 353

portsSNMP Query, changing 355


print jobsdeleting

jobsprint, deleting 233

deleting all jobs in queue 234listing for entire system 232listing, output 232moving all jobs 236moving single job 235output format 232

print queuesspooling, disabling 238starting 239stopping 238viewing number of jobs 228

PRINTER application classactivating 225icons 24menus 41object hierarchy 224parameters 71

printer monitoringexclusion list 414inclusion list 414

printersdeleting all jobs 234deleting jobs 233excluding one from monitoring 227jobs, moving all jobs 236listing all jobs in system 232monitoring, including 227moving one job 235queues, starting 239queues, stopping 238spooling, disabling 238starting 229stopping 228viewing assigned jobs 231

PROCCONT application classmenus 42parameters 71

PROCESS application classicon 24object hierarchy 244parameters 72

process control subsystemsexcluding from monitoring 140

process groupsrenicing processes within 301

Process KM 304PROCESS_PRESENCE application class

icons 24menus 42object hierarchy 244

processes See also zombie processesactive, listing 300

e


active, listing with group process ID 301listing, by user ID 303monitoring, configuring a process to alarm when its

PPID is not 1 262monitoring, configuring a process to alarm when its

PPID is owned by unauthorized user 265monitoring, configuring a process to alarm when

number exceeds set limit 250monitoring, configuring a process to alarm when

number falls below set limit 253monitoring, configuring a process to stop 259monitoring, configuring a process to suspend alert for

n cycles if not running 268monitoring, configuring communication for a process

host group 284monitoring, configuring multiple instances of a

process 247monitoring, configuring to restart a process when it

dies 256monitoring, creating a host group 283monitoring, deleting a process from the monitoring

queue 278monitoring, modifying host attributes in a process

host group 285monitoring, modifying the configuration of a process

270monitoring, querying a host within a process host

group 286monitoring, removing a host from a process host

group 286monitoring, reporting on monitored processes 280monitoring, resuming monitoring for a suspended

process 280monitoring, specifying a flag file directory 279monitoring, suspending monitoring for a process 280monitoring, synchronizing a local host’s list to a

selected host’s list for a process host group 288monitoring, synchronizing a local process’s list with a

selected process’s list 289monitoring, synchronizing a selected host’s list to a

local host’s list for a process host group 288monitoring, synchronizing a selected process’s list

with the local process’s list 290monitoring, viewing the process list for a selected

host 289monitoring, viewing the process presence list for a

selected process 291non-root, viewing average 299non-root, viewing average number 299renicing 300reprioritizing 300reprioritizing all within a process group 301reprioritizing by owner 302using excessive CPU, output format 297using excessive CPU, viewing 295viewing, processes waiting on resources 298viewing, top ten consumers of CPU 297

viewing, total non-root processes running 298viewing, total running on system 295viewing, total user processes running 298

PROCPRES application classicons 24parameters 73

PROCTopProcs parameter, output 298product support 3protocol version, viewing 184protocols

network, listing 189network, output format 190statistics, viewing 191TCP/IP services, listing 196

PSL data collection-Coll parameters 96exceptions 96selecting 98

PSL data collectionparameters, deactivated by platform 97

PSL data collectionparameters, deactivated by platform 96

push-buttons, selecting 405

Qqband statistics, viewing 181queues

deleting all jobs for single printer 234printer, deleting a print job 233printer, starting 239printer, stopping 238printer, viewing all jobs on a system 232printer, viewing jobs 228printer, viewing jobs for single printer 231receive 184send, size 184statistics, viewing 181

RRAWIP protocol, viewing statistics 191receive queue size, viewing 184receive window size, viewing 184recovery actions

attended mode 143file system cleanup 141

regular expressionsdisk monitoring 131file system monitoring 139file systems, searching 151

relational clauses, composite parameters 118relational operators, composite parameters 118remote addresses

viewing 184

Index 425


removinga scheduled task defined by a script 321files by characteristics 153files, by date updated 155files, by group 155files, by name 155files, by owner 155files, on single physical disk 155files, output format 156semaphores 168shared memory segments 166

renicingprocesses 300processes for a process group 301processes, by owner 302single process 300

requirementscomposite parameters, expression syntax 120file systems, unmounting 148mounting file systems 146

rloginusing with PATROL 200

route designationviewing 192

router status, viewing 192routing table

output format 193viewing 192

run queue, viewing 109

SSCHEDULER application class


schedulingtask defined by a command interpreter script 315task defined by a PSL script 318task defined by an operating system command script

313security

files with global write privilege, viewing 344files, listing SUID-protected files 341listing failed msu command attempts 345listing failed set user (su) command attempts 345listing SGID-protected files 341listing users with multiple running sessions 348listing users without a password 346

SECURITY application classicons 24menus 44object hierarchy 340

semaphoresdeleting 168


displaying active 115group, viewing 167managing 167memory types, viewing 167numeric ID, viewing 167owner, viewing 167permissions, viewing 167statistics, output format 168statistics, viewing 167

send queue sizeviewing 184

send window size, viewing 184server

name, querying 201servers

Network File System (NFS), listing 216Network Information System (NIS), list output format

221Network Information System (NIS), listing 220

servicesTCP/IP, listing 196Unix to Unix Communication Protocol (UUCP),

listing 210sessions

multiple, listing users 348set user (su) command

failed execution, list of users 345SGID-protected files, listing 341shared memory segments

statistics, output format 164viewing statistics 164

shared memory segments, deleting 166small memory requests

viewing allocated amounts 113viewing available amounts 113viewing failed amounts 113

SMP application classicons 24menus 44parameters 74

SNMParchitecture, PATROL 353configuration tasks 354listening for traps, testing 364viewing information in a Management Information

Base (MIB) 357SNMP Managers

determining whether listening 369SNMP Master Agent

PATROL, starting 361traps, ability to receive 364

SNMP queriesreceived by PATROL Agent, testing 367

SNMP Query Portchanging 355

SNMP sub-agentstarting 362

e


stopping 363SNMP traps

manual, generating 365PATROL Event Manager, testing 370

SNMPHealth application classicons 24menus 45object hierarchy 352parameters 77

socketsnetwork, viewing data 184, 185

Solaris systemsUnix to Unix Communication Protocol (UUCP) 207

spooling, disabling for a printer 238statistics

active semaphores 115CPU interrupts, viewing 109CPU run queue, viewing 109CPU switches, viewing 109CPU utilization 106CPU utilization, viewing 108CPU waits, viewing 109CPU, viewing for multi-processors 110dblk, viewing 181kernel resources 106linkblk, viewing 181mblk, viewing 181memory buffer 181network packets 194network protocol 191network, viewing 192overall CPU usage 159overall file system usage 159overall swap usage 159packets with errors 194qband, viewing 181semaphores 167semaphores, viewing 167shared memory segments 164strevent, viewing 181swap partition size, viewing 172swap partition space 172swap space 171swap space used, viewing 172swap space, in a swap area 171swap space, total 171synq, viewing 181system calls 115viewing entries 114viewing kernel system usage 115viewing tables 114viewing, i-node slots 114virtual memory, viewing 171

statusmonitoring, parameters 92setting for composite parameters 121

streams, statistics 181

strevent statistics, viewing 181subnet mask, obtaining 202SUID-protected files, listing 341support, customer 3suspend

monitoringcancelling a scheduled blackout script 337creating a blackout script 327deleting a blackout script 334modifying a blackout script 331specifying a default directory for blackout scripts

326viewing a blackout script 330

SWAP application classicons 25menus 46object hierarchy 170parameters 78

swap partition, size 172swap space

overall usage, monitoring 159percentage used, swap area 172percentage used, total 172percentage used, viewing 172viewing 171viewing, for a swap area 171viewing, total swap space 171

swap space sizeswap area, viewing 172

switches, CPU statistics 109synchronizing, file system cache and disk 149synq statistics, viewing 181syntax rules

composite parameter expressions 120system calls

kernel data 115system health

monitoring 158overall, viewing 160

system rolesPATROL Agent 354PATROL SNMP Manager 354PATROL SNMP Master Agent 354PATROL SNMP Sub-agent 354

system settingsports, SNMP Query 355

system usageviewing kernel data 115

systemscopying files, File Transfer Protocol (ftp) 198transferring files, File Transfer Protocol (ftp) 198

Ttables

routing, viewing 192

Index 427


viewing statistics 114task

collecting debug data 322modifying a scheduled script 321removing a scheduled script 321scheduling a command interpreter script 315scheduling a PSL script 318scheduling an operating system command script 313

TCP protocol, viewing statistics 191TCP/IP

name, listing 196port, listing 196protocol, listing 196services, listing 196services, output format 197

technical support 3testing

SNMP Master Agent, receiving traps 364traps

listening for SNMP, testing 364manual, generating 365PATROL Event Manager SNMP, testing 370

UUDP protocol, viewing statistics 191Unix to Unix Communication Protocol (UUCP)

bang path emails 206copying files 208copying files, specifying source 209deleting files, Solaris systems 207directories 206files, copying options 208files, specifying destination 209hosts, listing 210log file, viewing 210services, listing 210verifying support files 206

Unix utilitiesdata collection 92data collection methods 95

UNIX_OS application classicons 25menus 31

unmountingfile systems, automatically 148file systems, manually 149

userslisting duplicate user ID entries 348without passwords, listing 346

USERS application classicons 25menus 47parameters 79


Vvariables

/PUK/FILESYSTEM/moniList 144/snmp/default_port 369/SNMP/default_r_community 366/snmp/piV1m_list 369, 370/snmp/trap_port 364

viewing 108files, with global write privilege 344non-root processes, average 299PATROL SNMP configuration 356processes waiting on resources 298processes, non-root 298processes, using excessive CPU 295PROCTopProcs parameter, output format 298SGID-protected files 341SUID-protected files 341system health, overall 160top ten CPU hogs 297top ten CPU hogs, output format 298users without passwords 346zombie processes on system 293

virtual memorymonitoring 171percentage used, swap area 172percentage used, viewing 172swap area, viewing 171, 172swap partition size, viewing 172swap space, total 172total swap space, viewing 171viewing 171

Wwaits, CPU statistics 109

Zzombie processes

listing 293viewing total on system 292viewing, output format 294

e

*54130**54130**54130**54130*

*54130*

BMC Base de Conocimiento Linux

Documents

Transcript of BMC Base de Conocimiento Linux