OMEGAMON XE for UNIX User’s Guide,...

User’s GuideOMEGAMON® XE for UNIX

Version 200

GC32-9323-00

May 2002

Candle Corporation201 North Douglas Street

El Segundo, California 90245-9796

2 OMEGAMON XE for UNIX User’s Guide, Version 200

Registered trademarks and service marks of Candle Corporation: AF/OPERATOR, AF/PERFORMER, AF/REMOTE, Availability Command Center, Candle, Candle Command Center, Candle Direct logo, Candle Electronic Customer Support, Candle logo, Candle Management Server, Candle Management Workstation, Candle Technologies, CL/CONFERENCE, CL/SUPERSESSION, CommandWatch, CT, CT/Data Server, CT/DS, DELTAMON, eBA, eBA*ServiceMonitor, eBA*ServiceNetwork, eBusiness Assurance, eBusiness Institute, ETEWatch, IntelliWatch, IntelliWatch Pinnacle, MQSecure, MQView, OMEGACENTER, OMEGAMON, OMEGAMON/e, OMEGAMON II, OMEGAMON Monitoring Agent, OMEGAVIEW, OMEGAVIEW II, PQEdit, Solutions for Networked Applications, Solutions for Networked Businesses, and Transplex.Trademarks and service marks of Candle Corporation: Alert Adapter, Alert Adapter Plus, Alert Emitter, AMS, Amsys, AutoBridge, AUTOMATED FACILITIES, Availability Management Systems, Candle Alert, Candle Business Partner Logo, Candle Command Center/SentinelManager, Candle CommandPro, Candle CIRCUIT, Candle eDelivery, CandleLight, CandleNet, CandleNet 2000, CandleNet Command Center, CandleNet eBP, CandleNet eBP Access, CandleNet eBP Administrator, CandleNet eBP Broker Access, CandleNet eBP Configuration, CandleNet eBP Connector, CandleNet eBP File Transfer, CandleNet eBP Host Connect, CandleNet eBP Object Access, CandleNet eBP Object Browser, CandleNet eBP Secure Access, CandleNet eBP Service Directory, CandleNet eBP Universal Connector, CandleNet eBP Workflow Access, CandleNet eBusiness Assurance, CandleNet eBusiness Exchange, CandleNet eBusiness Platform, CandleNet eBusiness Platform Administrator, CandleNet eBusiness Platform Connector, CandleNet eBusiness Platform Connectors, CandleNet eBusiness Platform Powered by Roma Technology, CandleNet eBusiness Platform Service Directory, CandleNet Portal, CCC, CCP, CEBA, CECS, CICAT, CL/ENGINE, CL/GATEWAY, CL/TECHNOLOGY, CMS, CMW, Command & Control, Connect-Notes, Connect-Two, CSA ANALYZER, CT/ALS, CT/Application Logic Services, CT/DCS, CT/Distributed Computing Services, CT/Engine, CT/Implementation Services, CT/IX, CT/Workbench, CT/Workstation Server, CT/WS, !DB Logo, !DB/DASD, !DB/EXPLAIN, !DB/MIGRATOR, !DB/QUICKCHANGE, !DB/QUICKCOMPARE, !DB/SMU, !DB/Tools, !DB/WORKBENCH, Design Network, DEXAN, e2e, eBAA, eBAAuditor, eBAN, eBANetwork, eBAAPractice, eBP, eBusiness Assurance Network, eBusiness at the speed of light, eBusiness at the speed of light logo, eBusiness Exchange, eBusiness Institute, eBX, End-to-End, ENTERPRISE, Enterprise Candle Command Center, Enterprise Candle Management Workstation, Enterprise Reporter Plus, EPILOG, ER+, ERPNet, ESRA, ETEWatch Customizer, HostBridge, InterFlow, Candle InterFlow, Lava Console, MessageMate, Messaging Mastered, Millennium Management Blueprint, MMNA, MQADMIN, MQEdit, MQEXPERT, MQMON, NBX, NetGlue, NetGlue Extra, NetMirror, NetScheduler, OMA, OMC Gateway, OMC Status Manager, OMEGACENTER Bridge, OMEGACENTER Gateway, OMEGACENTER Status Manager, OMEGAMON Management Center, OSM, PC COMPANION, Performance Pac, PowerQ, PQConfiguration, PQScope, Response Time Network, Roma, Roma Application Manager, Roma Broker, Roma BSP, Roma Connector, Roma Developer, Roma FS/A, Roma FS/Access, RomaNet, Roma Network, Roma Object Access, Roma Secure, Roma WF/Access, Roma Workflow Access, RTA, RTN, SentinelManager, Somerset, Somerset Systems, Status Monitor, The Millennium Alliance, The Millennium Alliance logo, The Millennium Management Network Alliance, TMA2000, Tracer, Unified Directory Services, Volcano and ZCopy.Trademarks and registered trademarks of other companies: AIX, DB2, MQSeries and WebSphere are registered trademarks of International Business Machines Corporation. SAP is a registered trademark and R/3 is a trademark of SAP AG. UNIX is a registered trademark in the U.S. and other countries, licensed exclusively through X/Open Company Ltd. HP-UX is a trademark of Hewlett-Packard Company. SunOS is a trademark of Sun Microsystems, Inc. All other company and product names used herein are trademarks or registered trademarks of their respective companies.

Copyright © May 2002, Candle Corporation, a California corporation. All rights reserved. International rights secured.

Threaded Environment for AS/400, Patent No. 5,504,898; Data Server with Data Probes Employing Predicate Tests in Rule Statements (Event Driven Sampling), Patent No. 5,615,359; MVS/ESA Message Transport System Using the XCF Coupling Facility, Patent No. 5,754,856; Intelligent Remote Agent for Computer Performance Monitoring, Patent No. 5,781,703; Data Server with Event Driven Sampling, Patent No. 5,809,238; Threaded Environment for Computer Systems Without Native Threading Support, Patent No. 5,835,763; Object Procedure Messaging Facility, Patent No. 5,848,234; End-to-End Response Time Measurement for Computer Programs, Patent No. 5,991,705; Communications on a Network, Patent Pending; Improved Message Queuing Based Network Computing Architecture, Patent Pending; User Interface for System Management Applications, Patent Pending.

NOTICE: This documentation is provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions set forth in the applicable license agreement and/or the applicable government rights clause.This documentation contains confidential, proprietary information of Candle Corporation that is licensed for your internal use only. Any unauthorized use, duplication, or disclosure is unlawful.

Contents 3

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Contents of this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Adobe Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . 15Documentation Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 1. Introducing OMEGAMON XE for UNIX . . . . . . . . . . . . . . . . . . 21OMEGAMON XE for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Types of UNIX-related Information . . . . . . . . . . . . . . . . . . . . . . . . . . 25Product-provided Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Chapter 2. Introducing UNIX Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Reports for the OMEGAMON XE for UNIX . . . . . . . . . . . . . . . . . . . . 32Viewing Additional Report Information . . . . . . . . . . . . . . . . . . . . . . . 37Accessing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Report Flag Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Refreshing the Current Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Viewing Additional Report Information . . . . . . . . . . . . . . . . . . . . . . . 43Selecting the Contents of a Report . . . . . . . . . . . . . . . . . . . . . . . . . . 44Sorting Report Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Filtering Report Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 3. Disk Inodes Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49How the UNIX Disk Inodes Report Helps You . . . . . . . . . . . . . . . . . . 50A Typical Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Inside the UNIX Disk Inodes Report . . . . . . . . . . . . . . . . . . . . . . . . . 54

Contents


Chapter 4. Disk Performance Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57How the UNIX Disk Performance Report Helps You . . . . . . . . . . . . . 58A Typical Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Inside the UNIX Disk Performance Report . . . . . . . . . . . . . . . . . . . . . 61

Chapter 5. Disk Utilization Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65How the UNIX Disk Utilization Report Helps You . . . . . . . . . . . . . . . 66Typical Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Inside the UNIX Disk Utilization Report . . . . . . . . . . . . . . . . . . . . . . . 70

Chapter 6. File Information Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73How the UNIX File Information Report Helps You . . . . . . . . . . . . . . 74A Typical Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Inside the UNIX File Information Report . . . . . . . . . . . . . . . . . . . . . . 77

Chapter 7. Network Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81How the UNIX Network Report Helps You . . . . . . . . . . . . . . . . . . . . 82A Typical Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Inside the UNIX Network Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Chapter 8. Network File Server (NFS) Reports. . . . . . . . . . . . . . . . . . . . . . 89How the UNIX NFS Report Helps You . . . . . . . . . . . . . . . . . . . . . . . 90Inside the UNIX NFS Server Activity report . . . . . . . . . . . . . . . . . . . . 93Inside the UNIX NFS Client Activity report . . . . . . . . . . . . . . . . . . . . 96

Chapter 9. Process Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99How the UNIX Process Report Helps You . . . . . . . . . . . . . . . . . . . . 100Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Process Detail Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105A Typical Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Inside the Top CPU Time Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Inside the UNIX Process Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Inside the UNIX Child Process Report . . . . . . . . . . . . . . . . . . . . . . . 119Inside the UNIX Process Group Report . . . . . . . . . . . . . . . . . . . . . . 124Inside the Process Application Report . . . . . . . . . . . . . . . . . . . . . . . 129Inside the Process Command Report. . . . . . . . . . . . . . . . . . . . . . . . 134Inside the Process Resource Report . . . . . . . . . . . . . . . . . . . . . . . . . 137

Contents 5

Chapter 10. Remote Procedure Call (RPC) Report . . . . . . . . . . . . . . . . . . . 141How the UNIX RPC Report Helps You . . . . . . . . . . . . . . . . . . . . . . 142Inside the UNIX RPC Server Activity report . . . . . . . . . . . . . . . . . . . 145Inside the UNIX RPC Client Activity report . . . . . . . . . . . . . . . . . . . 147

Chapter 11. System Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149How the UNIX System Reports Help You . . . . . . . . . . . . . . . . . . . . 150Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155A Typical Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Inside the UNIX System Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Inside the System Cache and Buffers Report . . . . . . . . . . . . . . . . . . 160Inside the System Load Average Report . . . . . . . . . . . . . . . . . . . . . 162Inside the System Workload Report. . . . . . . . . . . . . . . . . . . . . . . . . 165

Chapter 12. System CPU Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169How the UNIX System CPU Reports Help You . . . . . . . . . . . . . . . . 170Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171A Typical Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Inside the System CPU Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178Inside the Solaris System CPU Workload Summary Report . . . . . . . 181Inside the Solaris System CPU Workload Report . . . . . . . . . . . . . . . 184

Chapter 13. System Groups Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187How the UNIX System Groups Report Helps You . . . . . . . . . . . . . . 188A Typical Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190Inside the UNIX System Summary Report . . . . . . . . . . . . . . . . . . . . 191

Chapter 14. System Load Average Report . . . . . . . . . . . . . . . . . . . . . . . . . 195How the UNIX System Load Average Report Helps You . . . . . . . . . 196A Typical Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Inside the UNIX System Load Average Report . . . . . . . . . . . . . . . . 199

Chapter 15. User Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203How the UNIX User Reports Help You . . . . . . . . . . . . . . . . . . . . . . 204A Typical Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206Inside the UNIX Users Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207


Inside the UNIX User Process Report. . . . . . . . . . . . . . . . . . . . . . . . 209

Chapter 16. Virtual Memory Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213How the UNIX Virtual Memory Report Helps You . . . . . . . . . . . . . . 214A Typical Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Inside the UNIX Virtual Memory Report . . . . . . . . . . . . . . . . . . . . . 218

Chapter 17. CandleNet Portal™ Client Interface. . . . . . . . . . . . . . . . . . . . . 221CandleNet Portal Workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222How Workspaces Are Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . 223UNIX System Workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227Disk Usage Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229File Information Workspace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232Network Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234NFS Activity Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237Process Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239RPC Performance Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241System Information Workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Users Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

Appendix A. Guide to Candle Customer Support . . . . . . . . . . . . . . . . . . . . 251Base Maintenance Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252Enhanced Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256Customer Support Contact Information. . . . . . . . . . . . . . . . . . . . . . 258

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

List of Tables 7

Table 1. Contents of this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Table 2. Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Table 3. Symbols in Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Table 4. UNIX Reports and Their Descriptions . . . . . . . . . . . . . . . . . . . . . . . . 33Table 5. UNIX Reports With Additional Views. . . . . . . . . . . . . . . . . . . . . . . . . 38Table 6. UNIX Disk Inodes Report Columns . . . . . . . . . . . . . . . . . . . . . . . . . . 55Table 7. UNIX Disk Performance Report Columns . . . . . . . . . . . . . . . . . . . . . 62Table 8. UNIX Disk Utilization Report Columns . . . . . . . . . . . . . . . . . . . . . . . 70Table 9. UNIX File Information Report Columns. . . . . . . . . . . . . . . . . . . . . . . 77

Table 10. UNIX Network Report Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Table 11. UNIX NFS Server Activity Report Rows. . . . . . . . . . . . . . . . . . . . . . . 93Table 12. UNIX NFS Client Activity Report Rows . . . . . . . . . . . . . . . . . . . . . . . 96Table 13. UNIX Process Top CPU Time Report Columns . . . . . . . . . . . . . . . . 109Table 14. UNIX Process Report Column Headings . . . . . . . . . . . . . . . . . . . . . 114Table 15. UNIX Child Process Report Column Headings . . . . . . . . . . . . . . . . 119Table 16. UNIX Process Group Report Column Headings . . . . . . . . . . . . . . . 124Table 17. Process Application Report Row Titles. . . . . . . . . . . . . . . . . . . . . . . 129Table 18. Process Command Report Row Titles . . . . . . . . . . . . . . . . . . . . . . . 135Table 19. Process Resource Report Row Titles . . . . . . . . . . . . . . . . . . . . . . . . 137Table 20. UNIX RPC Server Activity Report Row Titles. . . . . . . . . . . . . . . . . . 145Table 21. UNIX RPC Client Activity Report Row Titles . . . . . . . . . . . . . . . . . . 147Table 22. UNIX System Report Row Titles . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Table 23. System Cache and Buffers Report Row Titles . . . . . . . . . . . . . . . . . 160Table 24. System Load Average report columns . . . . . . . . . . . . . . . . . . . . . . . 162Table 25. System Workload Report Column Heads . . . . . . . . . . . . . . . . . . . . 165Table 26. UNIX System CPU Report Columns . . . . . . . . . . . . . . . . . . . . . . . . 179Table 27. UNIX Solaris System CPU Workload Summary Report . . . . . . . . . . 181Table 28. UNIX Solaris System CPU Workload Report . . . . . . . . . . . . . . . . . . 184Table 29. UNIX System Summary Report Columns . . . . . . . . . . . . . . . . . . . . 192Table 30. UNIX System Load Average Report Row Titles . . . . . . . . . . . . . . . . 200Table 31. UNIX Users Report Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

List of Tables


Table 32. UNIX User Process Report Columns . . . . . . . . . . . . . . . . . . . . . . . . 209Table 33. UNIX Virtual Memory Report Row Titles . . . . . . . . . . . . . . . . . . . . . 218Table 34. Attributes Used by the Workspaces . . . . . . . . . . . . . . . . . . . . . . . . . 226

Preface 9

Preface

This user’s guide introduces you to the new features of the OMEGAMON XE for UNIX, Version 200, how to use reports, and contains detailed information on each of the reports available in OMEGAMON XE for UNIX. For detailed information on the individual UNIX attributes and attribute groups, refer to the OMEGAMON XE for UNIX Reference Guide.

P

About This Book


About This Book

Who Should Use This GuideThis guide is intended to be used by UNIX system operators and system administrators.

Why You Should Use This GuideThis user’s guide is designed to provide you with a fundamental understanding of how to use the OMEGAMON XE family of products to monitor your UNIX distributed systems. The guide supplements the on-line help for the OMEGAMON XE family of products and the products you installed.

Candle recommends you use this guide as a handy reference whenever you need additional information about your Candle products.

Preface 11

Contents of this Guide


OverviewThis unit describes the contents of each chapter of this guide. Use the table to understand the organization and content of this guide.

Table 1. Contents of this Guide

Chapter name Content

“Introducing OMEGAMON XE for UNIX” on page 21.

This chapter introduces the features in the OMEGAMON XE for UNIX. Use this information to see how OMEGAMON XE for UNIX can enhance the performance of your system.

“Introducing UNIX Reports” on page 31.

This chapter includes a summary of the OMEGAMON XE for UNIX reports and describes how to:� Use the UNIX reports� Access OMEGAMON XE for UNIX reports� Refresh the current OMEGAMON XE for UNIX

report� View additional report information� Select the contents of a report� Sorting report data� Filter report data

“Disk Inodes Report” on page 49.

This chapter introduces you to the UNIX Disk Inodes report, which contains detailed information about when, where, and how each UNIX file system currently uses inodes. You can use the UNIX Disk Inodes report to help you improve the performance of your system and monitor usage of disk inodes.

“Disk Performance Report” on page 57.

This chapter describes the UNIX Disk Performance report, which gives you information you need to help improve the performance of your system.



“Disk Utilization Report” on page 65.

This chapter contains information that helps you use the UNIX Disk Utilization report to identify system performance problems caused by disk space shortage, and uneven distribution of space usage across disks and file systems.

“File Information Report” on page 73.

This chapter describes the UNIX File Information report and shows a sample report along with a description of each of the report columns.The UNIX File Information report contains system information that helps you improve the performance of your system and obtain detailed information such as file path, file attributes, and time data about a specific file.

“Network Report” on page 81.

This chapter contains information about the UNIX Network report. This report contains monitored data that helps you see your overall network performance, and supplies you with information about network interfaces on your monitored UNIX systems.

“Network File Server (NFS) Reports” on page 89.

This chapter describes the UNIX Network File Server (NFS) report. This report contains Statistics attributes you can use to create situations that refer to Network File System call rates and errors.

“Process Reports” on page 99.

This chapter describes the UNIX Process reports, which help you determine the processes that are running on a managed system and how to use these reports to improve process flow throughout your system.

“Remote Procedure Call (RPC) Report” on page 141

This chapter describes the UNIX Remote Procedure Call (RPC) report. This report contains Statistics attributes that allow you to create situations that refer to RPC call rates and errors.

Table 1. Contents of this Guide (continued)


Preface 13


“System Reports” on page 149.

This chapter describes the UNIX System reports, which contain detailed information about your monitored UNIX systems. You can use the UNIX System reports to help you improve system performance and, identify and modify system activity information.This chapter describes the UNIX System report that contains detailed information about your monitored UNIX systems. You can use the UNIX System report to help you improve system performance and identify and modify system activity information.

“System CPU Reports” on page 169.

This chapter includes information about the UNIX System CPU reports, how it helps you improve system CPU performance, and how you can use it to identify and monitor system CPU activity.

“System Groups Report” on page 187.

This chapter provides information about how the UNIX System Groups report helps you get an overview of the conditions occurring on your UNIX systems.

“System Load Average Report” on page 195.

This chapter describes the UNIX System Load Average report, which provides information about the load on a UNIX system and gives an indication of system activity.

“User Reports” on page 203.

This chapter introduces you to the UNIX User reports, which contains detailed information that helps you identify terminals and find time data on each user logged onto your monitored UNIX systems.

“Virtual Memory Report” on page 213.

This chapter describes the UNIX Virtual Memory report and contains detailed information about the availability of and demand for virtual storage on your systems.

Table 1. Contents of this Guide (continued)


Documentation Set


Documentation Set

IntroductionCandle provides a complete set of documentation for OMEGAMON XE for UNIX. Each manual in this documentation set contains a specific type of information to help you use the product.

In addition, most products refer to the OMEGAMON XE family of products general documentation and install guides. Please consult these guides located on the Candle Technical Documentation CD-ROM for information on using your Candle products to your best advantage.

If you plan to collect historical data, please see the Historical Data Collection Guide for OMEGAMON XE and CandleNet Command Center.

We would like to hear from youCandle welcomes your comments and suggestions for changes or additions to the documentation set. A user comment form, located at the back of each manual, provides simple instructions for communicating with the Candle Information Development department.

You can also send email to [email protected]. Please include "OMEGAMON XE for UNIX User’s Guide, Version 200" in the subject line.

Ordering additional product documentationTo order additional product manuals, contact your Candle Support Services representative.

Table 2. Documentation Set

Document Number Title Description

UX54-6501 OMEGAMON XE for UNIX User’s Guide, V200

This manual

UX53-6502 OMEGAMON XE for UNIX Reference Guide, V200

Provides detailed information about the attributes and product-provided solutions for the OMEGAMON XE for UNIX, Version 200.

Preface 15

Adobe Portable Document Format


Printing this bookCandle supplies documentation in the Adobe Portable Document Format (PDF). The Adobe Acrobat Reader will print PDF documents with the fonts, formatting, and graphics in the original document. To print a Candle document, do the following:

1. Specify the print options for your system. From the Acrobat Reader Menu bar, select File > Page Setup… and make your selections. A setting of 300 dpi is highly recommended as is duplex printing if your printer supports this option.

2. To start printing, select File > Print... on the Acrobat Reader Menu bar.

3. On the Print pop-up, select one of the Print Range options for� All� Current page� Pages from: [ ] to: [ ]

4. (Optional). Select the Shrink to Fit option if you need to fit oversize pages to the paper size currently loaded on your printer.

Printing problems?The print quality of your output is ultimately determined by your printer. Sometimes printing problems can occur. If you experience printing problems, potential areas to check are:� settings for your printer and printer driver. (The dpi settings for both your

driver and printer should be the same. A setting of 300 dpi is recommended.)

� the printer driver you are using. (You may need a different printer driver or the Universal Printer driver from Adobe. This free printer driver is available at www.adobe.com.)

� the halftone/graphics color adjustment for printing color on black and white printers (check the printer properties under Start > Settings > Printer). For more information, see the online help for the Acrobat Reader.

� the amount of available memory in your printer. (Insufficient memory can cause a document or graphics to fail to print.)

For additional information on printing problems, refer to the documentation for your printer or contact your printer manufacturer.



Contacting AdobeIf additional information is needed about Adobe Acrobat Reader or printing problems, see the Readme.pdf file that ships with Adobe Acrobat Reader or contact Adobe at www.adobe.com.

http://www.adobe.com



Preface 17

Documentation Conventions


IntroductionCandle documentation adheres to accepted typographical conventions for command syntax. Conventions specific to Candle documentation are discussed in the following sections.

Panels and figuresThe panels and figures in this document are representations. Actual product panels may differ.

Required blanksThe slashed-b (b) character in examples represents a required blank. The following example illustrates the location of two required blanks.

beBA*ServiceMonitorb0990221161551000

Revision barsRevision bars (|) may appear in the left margin to identify new or updated material.

Variables and literalsIn examples of command syntax, uppercase letters are actual values (literals) that the user should type; lowercase letters are used for variables that represent data supplied by the user. Default values are underscored.

LOGON APPLID (cccccccc)

In the above example, you type LOGON APPLID followed by an application identifier (represented by cccccccc) within parentheses.

In ordinary text, variable names appear in italics.



SymbolsThe following symbols may appear in command syntax:

Table 3. Symbols in Command Syntax

Symbol Usage

| The “or” symbol is used to denote a choice. Either the argument on the left or the argument on the right may be used. Example:

YES | NOIn this example, YES or NO may be specified.

[ ] Denotes optional arguments. Those arguments not enclosed in square brackets are required. Example:

APPLDEST DEST [ALTDEST]In this example, DEST is a required argument and ALTDEST is optional.

{ } Some documents use braces to denote required arguments, or to group arguments for clarity. Example:

COMPARE {workload} -REPORT={SUMMARY | HISTOGRAM}

The workload variable is required. The REPORT keyword must be specified with a value of SUMMARY or HISTOGRAM.

_ Default values are underscored. Example:

COPY infile outfile - [COMPRESS={YES | NO}]In this example, the COMPRESS keyword is optional. If specified, the only valid values are YES or NO. If omitted, the default is YES.

What’s New 19

What’s New

Candle Monitoring Agents Have a New NameCandle's intelligent monitoring agents that comprise the OMEGAMON XE suite of products and use the CandleNet Portal user interface have been renamed. You will see the new names in the product help and documentation.

Within the application, some of the panel names do not reflect the new product name. However, all of the intelligent functionality of OMEGAMON XE is available for these agents. The new product names will be added to the applications in a subsequent release.

W


Introducing OMEGAMON XE for UNIX 21

IntroducingOMEGAMON XE for UNIX

IntroductionThis chapter introduces the features in the OMEGAMON XE for UNIX. Use this information to see how OMEGAMON XE for UNIX can enhance the performance of your system.

Chapter ContentsOMEGAMON XE for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Types of UNIX-related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Product-provided Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

1

OMEGAMON XE for UNIX



OverviewSystem administrators face increasing challenges in today's ever-changing technical environment. Candle Corporation developed the OMEGAMON XE family of products and OMEGAMON XE for UNIX to help you meet these challenges and better manage the performance of your system.

Using OMEGAMON XE for UNIX and OMEGAMON XE family of products

As part of the OMEGAMON XE family of products for Distributed Systems, OMEGAMON XE for UNIX, offer a central point of management for UNIX. They provide a comprehensive means for gathering exactly the information you need to detect problems early and help prevent them.

Information is standardized across all systems (AIX, HP-UX, and Solaris) and you can monitor hundreds of servers from a single workstation.

The OMEGAMON XE family of products lets you easily collect and analyze UNIX-specific information, including:

� Operating system and CPU performance

� UNIX disk information and performance analysis

� Process status analysis

� Network performance

The OMEGAMON XE for UNIX are intelligent, remote monitoring agents that reside on managed systems. They assist you in anticipating trouble and warn system administrators when critical events take place on their systems. With OMEGAMON XE for UNIX, system administrators can set threshold levels as desired and flags to alert them when the system reaches these thresholds.



How the OMEGAMON XE for UNIX assists youOMEGAMON Monitoring Agent for UNIX provides several benefits.

OMEGAMON XE for UNIX help you monitor and gather consistent, accurate, and timely information you need to effectively perform your job.

Simplify application and system management

by managing applications, platforms and resources across your system.

Increase profits by providing you with real-time access to reliable, up-to-the-minute data that allows you to make faster, better informed operating decisions.

Scale and port to new platforms

OMEGAMON XE for UNIX now support a wide variety of UNIX platforms.

Enhance system performance

by letting you integrate, monitor, and manage your environment, networks, console, and mission-critical applications. OMEGAMON XE for UNIX alert the Candle Management Workstation (CMW) when conditions in your environment meet threshold-based conditions. These alerts notify your system administrator to limit and control system traffic. You can view data gathered by OMEGAMON XE for UNIX in reports and charts, informing you of the status of your UNIX managed systems.

Enhance efficiency by monitoring diverse platforms and networks. Depending on your OMEGAMON XE configuration, you can collect and monitor data across platforms. OMEGAMON XE for UNIX gather and filter status information at the managed system rather than at the Hub, eliminating unnecessary data transmission and sending only data that is relevant to changes in status conditions.



Advanced monitoring facilitiesOMEGAMON Monitoring Agent for UNIX includes advanced monitoring facilities.

� User-defined, and product-provided situations based on thresholds to raise different types of alerts: critical, warning, and others

� At-a-glance status picture of all database servers

� The capability to simultaneously monitor multiple servers from one or more centralized workstations, including servers on various platforms running either Oracle or Sybase database management systems


Types of UNIX-related Information


OverviewOMEGAMON Monitoring Agent for UNIX provides reports with key performance metrics to give you the widest range of information possible across AIX, HP-UX, and Solaris.

File informationThe UNIX File Report lists file attributes, path, and time information. Attributes include file, path, links, owner, group size, access, type, and last accessed time.

Network informationThe UNIX Network Report identifies network interfaces, determines whether they are operational, and shows the amount of network traffic. Data includes network interface name, interface IP process, maximum transmission unit, interface status, collisions, frames received, frames transmitted, input errors, interface DNS name, interface IP address, and interface status.

User informationThe UNIX User Report shows terminal identification and time data on each user logged into your monitored UNIX systems. Use this report to obtain information on individual users and to check for problems caused by user behavior.

ProcessesThe UNIX Process Report provides detailed information on each currently executing process, including identification, priority, command, and memory data. Attributes include command, process ID, parent process ID, CPU utilization, nice value, priority, event waited on, execution state, flag, time, terminal device, CPU percent, memory percent, user ID and more.



Disk inodes informationThe UNIX Disk Inodes Report can be used to monitor inode usage on each of your file systems. Attributes include inode size, inodes free, inodes used, and inodes used percent.

Disk performance informationThe UNIX Disk Performance Report provides detailed information on the efficiency of I/O operations. This identifies disk performance problems through slow rates of data transfer from disk to memory, and high disk usage. Attributes include transfer rate, busy percent, transferred bytes, average queue, average wait, and average service time.

Disk utilization informationThe UNIX Disk Utilization Report provides information on file system location and disk space usage. It identifies system performance problems caused by disk space shortages and uneven distribution of space usage across disks and file systems.

Attributes include space available, space used, and space used percent, and inodes used and inodes used percent.

System load average informationThe UNIX System Load Average Report provides an overall picture of system activity. This report helps you assess whether the load is improving or worsening. Attributes include system name, up time, and load average.

System virtual memory informationThe UNIX System Virtual Memory Report provides detailed information on swapping and paging activity and helps determine if system performance problems are caused by memory shortages. Attributes include total virtual memory, processes in run queue, processes waiting, page faults and page reclaims, and page ins and page outs.



System CPU informationThe UNIX System CPU report displays percentages of processor activity taking place on each monitored UNIX system. Use this report to check for problems such as processes consuming abnormally large amounts of CPU time, imbalances between user and system CPU demands, and long CPU waits caused by I/O bottlenecks. Attributes include system name, user CPU and system CPU, idle CPU, and wait I/O.

System informationThe UNIX System Report supplies basic identification and system activity information on your monitored UNIX systems. Use this report to identify the configuration of your systems and check their current activity levels. Attributes include system name, system type, system version, total real memory, free memory, total virtual memory, number of users sessions, number of system processes, and net address.

Monitored logs informationThe UNIX Monitored Logs Report provides detailed information about when performance changes occur in UNIX applications.

System Groups informationThe UNIX System Groups Report provides you with a summary overview of distributed UNIX systems, defined in a managed system list. If you are experiencing problems on one or more managed systems, use this report to help pinpoint the problem.

NFS and RPC InformationThe UNIX NFS Report and RPC report provide information about calls from managed systems to NFS and RPC servers. Use these reports to pinpoint problems concerning calls to and from these servers.

Product-provided Solutions



OverviewCandle minimizes your programming requirements by providing you with pre-defined solutions you can use to start monitoring your system immediately. There are three types of product-provided solutions:

� Situations in which monitoring criteria are set for the performance of your systems

� Templates in which managed objects representing various areas of your system are correlated with situations and status states

� Policies to support the automation component of OMEGAMON XE family of products

Using product-provided situations for turn-key performanceCandle provides you with situations tailored to OMEGAMON XE for UNIX that you can employ without first having to create them.

You can activate these situations to solve common UNIX problems.

� UNIX_CPU_Critical—Reports when CPU utilization is greater than or equal to 85%

� UNIX_Disk_Availability—Determines under utilized hard drive space

� UNIX_Network_Collisions_Critical—Reports when a large number of network interface collisions have been detected

� UNIX_Runaway_Process—Checks which user is using a process and reports if a process is utilizing a high percentage of the CPU

� UNIX_System_Capacity_Critical—Monitors system capacity with regard to the number of processes running and the amount of CPU being utilized

You can also modify product-provided situations to suit your specific needs, and you can create new situations as well.



For more information on product-provided situationsCandle offers more than 20 product-provided situations in this release of OMEGAMON XE for UNIX. See the OMEGAMON XE for UNIX Reference Guide for a complete description of the product-provided situations.

For more information on product-provided templatesCandle provides five product-provided templates for UNIX systems. See the OMEGAMON XE for UNIX Reference Guide for a complete description of the product-provided templates for your system.

For more information on product-provided policiesCandle provides three product-provided policies for UNIX systems. See the OMEGAMON XE for UNIX Reference Guide for a complete description of the product-provided policies for your system.



Introducing UNIX Reports 31

Introducing UNIX Reports

IntroductionThis chapter includes a summary of the OMEGAMON XE for UNIX reports and describes how to:

� Use the UNIX reports� Access OMEGAMON XE for UNIX reports� Refresh the current OMEGAMON XE for UNIX report� View additional report information� Select the contents of a report� Sorting report data� Filter report data

Chapter ContentsReports for the OMEGAMON XE for UNIX . . . . . . . . . . . . . . . . . . . . . . . 32Viewing Additional Report Information. . . . . . . . . . . . . . . . . . . . . . . . . . . 37Accessing Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Refreshing the Current Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Viewing Additional Report Information. . . . . . . . . . . . . . . . . . . . . . . . . . . 43Selecting the Contents of a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Sorting Report Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Filtering Report Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

2

Reports for the OMEGAMON XE for UNIX



OverviewThe OMEGAMON XE for UNIX systems product provides reports for viewing information about each UNIX node you monitor. Each report is a data display that provides real time information about all major UNIX system components and their functions, such as:

� CPU

� Processes

� I/O

� Virtual memory

� Inodes

� Network interfaces

� Network File Service/Remote Procedure Calls

Using the reportsYou can use these reports to:

� Analyze the performance of your UNIX systems

� Identify problem areas and bottlenecks in your system

� Get information you need to tune your UNIX system

� Evaluate how your tuning decisions affect the performance of your UNIX system. In addition, you can use reports to profile the performance of each UNIX node over a period of time. This profile helps you:

� Pinpoint the exact locations of system bottlenecks

� Identify and anticipate times of peak usage

� Control the flow of network traffic

� Evaluate the effectiveness of your tuning decisions

� Select optimum threshold values for situation monitoring



Where to find more information about reportsTo find more detailed information about each OMEGAMON XE for UNIX report, you can:

� Refer to the chapter in this guide for the report.

� Select the Open as Help menu item from the menu that appears when you place the cursor over the Reports icon and right-click. The Help for OMEGAMON XE for UNIX reports appears.

Reports and their descriptionsThe table describes the UNIX reports provided with OMEGAMON XE for UNIX.

Table 4. UNIX Reports and Their Descriptions

Report Name Provides information on... Used to identify...

System Groups A summary overview of distributed UNIX systems defined in a managed system list.

The overall performance of your distributed UNIX systems.

Disk Inodes Inode sizes and usage. Inodes are the control blocks of the file system. The Disk Inodes Report provides percentages of inodes used and the total number of inodes in the file system.

Inode shortages.

Disk Performance Efficiency of disk I/O operations. Slow rates of data transfer for the physical disk drive, as well as incidents of high disk usage.

Disk Utilization File system information, such as how large they are (MB), how much data is stored in them, and what percentage of the disk they are using.

Disk space shortages and uneven distribution of space usage across disks and file systems.



File Information Information about files in the UNIX File system, including, but not limited to, file attributes, last time a file was accessed, file name, path, mode bits, file owner, group, size.

Detailed information about specifics files.

Network Network interfaces, such as:� Name of an interface� IP address� DNA name� Maximum transmission unit� Status� Number of frames received at

an interface during the 30-second reporting period

� Number of frames transmitted during the reporting period

� Input errors that occurred during the reporting period

� Output errors that occurred during the reporting period

� Interface collisions� Total number of interfaces

received by an interface� Total number of interfaces

transmitted

Operational status of interfaces, network traffic issues, transmission errors.

Network File Server

Network file service (NFS) interfaces.

Operational status of NFS servers and clients.

Process Process information, such as the name of a process, its priority, its size, and process command data.

Which processes are running, who is using them, which processes are consuming large amounts of CPU time, and process priority issues.

Table 4. UNIX Reports and Their Descriptions (continued)




Remote Procedure Call

Information about the Remote Procedure (RPC) clients and servers.

Operational information on RPC Server and client error rates.

System System identification, system activity and other system information.

System configuration, system activity levels, the type and version of Operating System you are monitoring (for example, AIX 4.1.4 or Sun), the memory size, virtual memory size (paging space), the number of user sessions, the current number of processes that are active and the IP address of the system.

System CPU How the system uses the processor(s), the percentage of all processor(s) activity. Allows you to determine if the system is spending too much time in User state, System state, or Idle state, or if the system is waiting for I/O to complete.

By studying these percentages, you can evaluate your system. If the system spends too much time in any one state, you probably need to look at the Process Report next, to see which processes are running and why the system is stuck in one state.

Processes consuming large amounts of CPU time, long CPU waits caused by I/O bottlenecks.





System Load Average

The system load average (the number of processes that could be executing but are waiting because another process is using the CPU). Overall system activity averaged over time. The columns of this report relate to load average figures, such as the System Information Column, the number of user sessions, the number of processes currently active

System work load issues, such as whether the load average tends to be increasing or decreasing, how busy the system was during the last minute, how busy the system was during the last fifteen minutes.

System Virtual Memory

Current information about real and virtual memory sizes, swapping and paging activity

Memory shortages

Users Users logged onto the system Jobs and job steps with processing problems




Viewing Additional Report Information


Charts and additional report informationSome reports have more than one report or chart available. To view an additional report with more information about a specific row in a report, double-click the row of data to open the additional report.

OMEGAMON XE for UNIX reports receive their data from software agents resident on the nodes of your UNIX network. These agents must be active before OMEGAMON XE for UNIX displays valid report data. If all OMEGAMON XE for UNIX cannot measure a particular attribute, a value of N/A appears in the report.

Additionally, OMEGAMON XE for UNIX provides an historical version of many reports. When you choose an historical report, the Time Span Selection window displays. You can request to view up to 24 hours of historical data for a particular report.

Some OMEGAMON XE for UNIX reports provide a graphical view of the monitored information called a Chart view.



Reports with additional viewsThe table lists all reports and show which reports have additional reports and chart views.

Table 5. UNIX Reports With Additional Views

Report NameAdditional Reports

Historical Report Charts

UNIX Disk Inodes N/A ✔ ✔

UNIX Disk Performance N/A ✔ N/A

UNIX Disk Utilization N/A ✔ ✔

UNIX File Information ✔ N/A

UNIX Network N/A ✔ N/A

UNIX Monitored Logs N/A N/A

UNIX Network File Server ✔ ✔ N/A

UNIX Process ✔ ✔ ✔

UNIX System ✔ ✔ ✔

UNIX Remote Procedure Call

✔ ✔ NA

UNIX System CPU ✔ ✔ ✔

UNIX System Groups ✔ ✔

UNIX System Load Average

N/A ✔ N/A

UNIX System Virtual Memory

N/A ✔ ✔

UNIX User ✔ ✔ N/A


Accessing Reports

Accessing Reports

Prerequisites to accessing a reportThe procedures below make the following assumptions about your CMW.

� You have the CMW Main window open.

� You have all OMEGAMON XE for UNIX installed at your site.

OMEGAMON XE for UNIX reports windowThe illustration shows the UNIX report window with the representative icons for each UNIX report.

Accessing Reports


How to access a reportUse the procedure to access an OMEGAMON XE for UNIX report.

1. From the CMW main window, open the Reports window by double-clicking the Reports icon.Result: The Reports window shows an icon for each OMEGAMON XE for UNIX Report.

2. Open the UNIX Disk Utilization report by double-clicking the UNIX Disk Utilization Report icon.Result: The report opens, showing a list of available managed systems whose report data you can view.

3. Select a managed system by double-clicking that row.Result: The report opens, showing real-time data collected for the managed system you selected.

From the UNIX System — Managed System Selection menusThe mouse right-click menus from the UNIX System — Managed System Selection view and from selected rows within reports differ for OMEGAMON XE for UNIX V200, V140 and V120 agents.

NOTE: UNIX V120 agents display 01.30.00 in the Version column of the managed system menu. The Version 120 agents mistakenly display the value of 01.03.00. This is the purpose of releasing the UNIX Version 140 rather than a Version 130.


Report Flag Values

Report Flag Values

Assignment of the N/A (-1) valueNot all UNIX systems display all UNIX attributes. For example, AIX systems do not display the CPU ID where the process is running on. If your system does not display a value for a certain attribute, you see

N/A

in fields relating to that attribute. N/A stands for Not Available. A value of N/A means that this information is not currently being collected for the UNIX platform on which your system is running. For example, HP-UX and Solaris systems do not display Bus Percent information.

Within historical data collection reports, you see a value of -1 in report columns for systems that do not display a value for a particular attribute.

Assignment of the -2 valueIf a data collector has stopped, a value of -2 is returned in all numeric fields. The -2 value is used to signify that a problem has occurred in data collection and that you should review the agent log.

The value -2 also displays in the historical data collection reports.

Refreshing the Current Report


Refreshing the Current Report

Prerequisites to refreshing a reportThe procedures below make the following assumptions about your CMW.

� You have the CMW Main window open.

� You have the OMEGAMON XE for UNIX installed at your site.

� You have a UNIX report open.

How to refresh a current report

1. From the open UNIX report, select the View menu from the menu line.Result: The View pulldown menu appears.

2. From the View pulldown menu, select the Refresh Now menu item.Result: The report window redisplays current data gathered at the last monitored interval by the UNIX monitoring agent on the managed system whose report you are viewing.




OverviewSome reports have an additional report, chart, or topology view available. OMEGAMON XE for UNIX reports can have more columns than you see when you first open the report. Use the right scroll bar to view additional columns.

How to open a chart viewThe steps in this procedure assume you want to open the UNIX Disk Utilization report.

Use the procedure to open a chart view in any report where one is available.

1. While the UNIX Disk Utilization report is open, right-click a row containing the file system whose disk utilization you want to view as a chart.Result: The pop-up menu appears.

2. Click the Disk Utilization Chart menu item from the pop-up menu.Result: The UNIX Disk Utilization Chart appears for the file system you chose.

Selecting the Contents of a Report



OverviewBy default, all report columns appear when you open a report. This provides you the maximum amount of monitored system data about your monitored systems. However, if this is more report information than you want, you can choose which columns you want to appear in any report,

Choosing which columns you want to appear in a reportYou choose which report columns you want to appear in a report by selecting them from the Columns settings page in the Settings notebook for the specific report you want to change.

Changes to column settings take effect when new views openChanges to column settings are not reflected in the currently open reports view. If you add or remove columns from a report, the changes only take affect when a new view is opened. To view your changes to the report, close the report and then re-open it.



How to choose which columns appear in a reportUse the procedure to choose which columns appear in a report. You can use these steps to customize the columns appearing in any CMW details view.

1. From the CMW Reports window, place the mouse cursor over the report icon that represents the report whose columns you want to customize.

2. Right-click to display the pop-up menu.

3. Select Open as Settings from the pop-up menu.Result: The Settings notebook for the report opens.

4. Choose the View tab to open the view settings page.

5. From the View list box, click the view name whose report contains columns you want to customize. If the view name is correct, you can skip this step.

6. From the Selected list box, select a report column you want to remove from the report.Result: The selected report column name is highlighted and the left arrow button is activated.

7. Choose the left arrow to remove the column from the report.Result: The report column title appears in the Available list box.

8. Repeat steps 5 and 6 for each report column you want to remove.

9. (Optional) To add a report column from the Available list box to the Selected list box, select the report column title and then click the right arrow.Result: The selected report column is added to the report.

10. When all your changes are complete, click OK to save and exit the Settings notebook.Result: The report reappears. To view your changes in the current report, close this report and re-open it. Only the columns whose names appear in the Selected column list box appear in the report.

Sorting Report Data


Sorting Report Data

OverviewYou can organize a report according to the value of a specific attribute. This capability lets you quickly identify the report listings that are most meaningful to you.

Procedure to sort report dataUse the procedure to sort a UNIX report. The following steps assume you have opened a report view for the managed system whose data you want to sort.

1. From the open report view, click the View > Settings View. Result: The Settings notebook for the report opens.

2. View the Sort settings sheet by selecting the Sort tab.Result: The Sort settings sheet appears.

3. From the View list box, highlight the view where you want the sort to occur.

4. From the Sort by list box, highlight the column name whose data you want sorted.

5. Choose one of the following sort methods:� Click the Ascending radio button to sort the column values in ascending

order (from lowest to highest).

� Click the Descending radio button to sort the column values in descending order (from highest to lowest).

6. Click OK to save and exit the Settings notebook.Result: The report reappears. You see the report data sorted according to its order in the field you selected.


Filtering Report Data


OverviewSome UNIX reports can be lengthy, making it difficult for you to quickly focus on the information that is most important to you. You can use the Include settings sheet for a report to filter the data. The result of the filtering is the display of only the report data that meets the criteria you specified.

Using the Include settings sheet to filter report dataThis unit shows you how to use the Include settings sheet for the UNIX Disk Utilization Report to filter the report listing to show only managed systems with less than 10,000 kilobytes of available disk space.



How to filter report dataUse the procedure to filter report data. You can use these steps to filter all other CMW reports.

1. From the CMW Reports window, open the report you want to filter by selecting its report icon.

2. From the View menu, select Settings View to open the Settings notebook of the report.Result: The Settings notebook opens and the first settings sheet for the report appears.

3. View the Include settings sheet by selecting the Include tab.Result: The Include settings sheet appears.

4. Specify the Disk Utilization report as the report you want to filter by selecting it from the View list box.

5. From the Field to Compare list box, select the Space Available field.

6. From the Field to Compare list box, select Less than.

7. In the Value field, type in 10000 so that values less than 10,000 kilobytes appear in the report.

8. Click OK to save and exit the Settings notebook.Result: The report reappears. You see only those managed systems whose space available is less than 10,000 kilobytes.

Disk Inodes Report 49

Disk Inodes Report

IntroductionThis chapter introduces you to the UNIX Disk Inodes report, which contains detailed information about when, where, and how each UNIX file system currently uses inodes. You can use the UNIX Disk Inodes report to help you improve the performance of your system and monitor usage of disk inodes.

Chapter ContentsHow the UNIX Disk Inodes Report Helps You . . . . . . . . . . . . . . . . . . . . . 50A Typical Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Inside the UNIX Disk Inodes Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

3

How the UNIX Disk Inodes Report Helps You



OverviewInodes are data structures that contain information about files, such as permissions and pointers to the actual data. Any file that exists on a UNIX file system must have its associated inodes.

The UNIX Disk Inodes report provides:

� the percentage of use of inodes

� the total number of inodes in a file system

Additionally, OMEGAMON XE for UNIX provides an historical version of this report. When you choose an historical report, the Time Span Selection window displays. You can request to view up to 24 hours of historical data for a particular report.

Using the monitored disk inode dataViewing disk inode data as a report helps you see detailed inode information for each file system on your monitored UNIX systems.

The number of inodes on a file system is fixed at the time the file system is created. This number determines how many files can exist.

If the inode count becomes low, the number of new files that you can create is limited. This is true regardless of how much disk space is available. If the inode count on your system becomes low, it indicates you or your system administrator should take corrective action. Possible actions include:

� Backing up the affected file system and rebuilding it with more inodes

� Deleting temporary files

� Identifying and reconfiguring parts of the file system with heavy inode consumption



Using the UNIX Disk Inodes ReportBy viewing the monitored disk inode data collected by OMEGAMON XE for UNIX on remote systems, you can:

� Improve your response time to remote system changes, allowing you to quickly and accurately optimize inode usage on your file system

� Increase system efficiency by providing you real time information about how many inodes are used and how many are free on your monitored UNIX file systems

Sample UNIX Disk Inodes ReportThe illustration shows a representative UNIX Disk Inodes report.



Using the Chart ViewYou can view the monitored disk inode data of any remote UNIX system as a chart by selecting UNIX Disk Inode chart from the View pulldown menu. The UNIX Disk Inode chart shows you at a glance the relationship between free and used inodes on any disk. It provides a quick way of scanning a entire disk at one time to see its inode use. With one glance you can understand and respond efficiently to any inode shortage about to occur.

The chart shows you the number of inodes used and the number of inodes still free each disk. When the number of inodes is high, you have a shortage of inodes and need to take corrective action, including:

� Backing up the affected file system and rebuilding it with more inodes

� Deleting unused files

� Reconfiguring the file system

Sample UNIX Disk Inode chartThe illustration shows a representative UNIX Disk Inode chart.


A Typical Scenario

A Typical Scenario

Viewing real-time performance dataSuppose that while monitoring the UNIX systems in use at your site, you open the UNIX Disk Inodes report to view real time performance data. This data informs you of the current status of disk inode use. When you open the report, current data from remote UNIX managed systems fills the report. In the first column the system name appears. By scanning columns to the right, you see the Inode Used Percent column.

Generally, disk inode space should be a relatively high number, so the percentage of inode space to disk space should also be a high number. If the values for Inodes Free is less than 100, this is a critical condition. Notify your system administrator immediately. If the values in the Inode Used Percent are all above 30 percent, delay taking corrective action.

If the percentage used drops to less than 10 percent, your system administrator must act quickly to avoid a pending crisis. Corrective action may include freeing unneeded space or deleting temporary files.

Inside the UNIX Disk Inodes Report



OverviewThe UNIX Disk Inodes report contains ten columns. Monitored data for each managed system appears in rows in each column. You can use any data appearing in a report as a threshold value in the creation of a situation.

Reminder on sorting and filtering columnsYou can sort or filter information in the columns of the UNIX Disk Inodes report to modify the way in which you view disk inode information.

Refer to “Sorting Report Data” on page 46 and “Filtering Report Data” on page 47 for more information about sorting and filtering data in reports.

Report flag valuesRefer to “Report Flag Values” on page 41 for information on report flag values.



Column heads and their descriptionsThe table contains descriptions of each column heading in the UNIX Disk Inodes report. The column headings are listed in the alphabetical order.

Table 6. UNIX Disk Inodes Report Columns

Column Description

Inodes Free Displays the number of inodes currently available on your filesystem

Inodes Used Displays the number of inodes currently allocated to files. This value equals the Inode_Size value minus the Inodes_Free value

Inodes Used Percent Displays the percentage of inodes currently allocated to files

Mount Point Displays the pathname of the directory to which a file system is mounted

Name Displays the name of the physical disk partition mounted

Size (KBytes) Displays the size of the disk in kilobyte

Space Used (KBytes) Displays the amount of space used on a disk expressed in kilobytes

Space Available (KBytes) Displays the number of kilobytes of unused disk space currently available on a disk

Space Used Percent Displays the percentage of space currently in use on a disk

Timestamp Displays the date and time of the last update to the information collected by UNIX remote agents

Total Inodes Displays the number of inodes allocated to a file system, and the size (in bytes) of a file



Write Time The timestamp taken for the history row when it is written to the history file. This timestamp reflects the location of the history file, which can be stored at the CMS or with the agent. If you had a history file stored with an agent in New York and the CMS was in California, this timestamp would be based on New York time.

Values

The format is MM/DD/YY HH:mm:SS where

MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example

06/27/98 13:00:27indicates that row was written on June 27, 1998 at 1:00:27 p.m.

Note: This column head or row head is only seen in the short-term historical reports.

Table 6. UNIX Disk Inodes Report Columns (continued)

Column Description

Disk Performance Report 57

Disk Performance Report

IntroductionThis chapter describes the UNIX Disk Performance report, which gives you information you need to help improve the performance of your system.

Chapter ContentsHow the UNIX Disk Performance Report Helps You . . . . . . . . . . . . . . . . . 58A Typical Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Inside the UNIX Disk Performance Report . . . . . . . . . . . . . . . . . . . . . . . . 61

4

How the UNIX Disk Performance Report Helps You



OverviewThe Disk Performance report helps you solve disk related problems quickly by providing information on devices with excessive I/O activity and/or long service times. New data includes average disk queue length and average number of processes waiting for service.

Using the UNIX Disk Performance reportBy viewing monitored disk input/output (I/O) data collected by the OMEGAMON XE for UNIX, you can:

� Improve the performance of your UNIX system by quickly and accurately pinpointing how your system transfers data from disk to memory

� Increase your efficiency by keeping you constantly informed of how the disk performs


Monitoring disk performanceYou monitor the performance of disks in your system to make sure they operate smoothly. Disk performance has a major impact on the overall functioning of your UNIX system. If disk performance is poor, it affects jobs that require a large amount of disk I/O, virtual memory functioning, and the time required to run a program.

Use this report to identify disk performance problems caused by slow rates of data transfer from disk to memory, or high disk usage.



Sample UNIX Disk Performance reportThe illustration shows a representative Disk Performance report.

Using the Chart ViewThe Disk Performance report has no chart view.

A Typical Scenario


A Typical Scenario

Viewing real time disk I/O dataYour system administrator might use a product-provided situation to monitor I/O wait. The product-provided situation monitors for a system I/O wait greater than 20 percent. When this occurs, disk performance begins to diminish.

Wait I/O is a percentage. Large Wait I/O values mean the user and system are waiting. If the I/O wait on your system becomes large, it indicates that your system administrator should take corrective action.


Inside the UNIX Disk Performance Report


OverviewThe UNIX Disk Performance report contains seven columns. Information for each disk appears in rows in each column. You can use any data appearing in a report as a threshold value in the creation of a situation.

Reminder about sorting and filtering columnsYou can sort or filter information in the columns of the UNIX Disk Performance report to modify the way in which you view disk performance information. Refer to “Sorting Report Data” on page 46 and “Filtering Report Data” on page 47 for more information about sorting and filtering data in reports.

Report Flag valuesRefer to “Report Flag Values” on page 41 for information on report flag values.

Information about Transfer Rate and Percent Busy statisticsNot all UNIX platforms provide Transfer Rate and Percent Busy statistics. When data is not available, the data values will appear as N/A in the report.



Column heads and their descriptionsThe table contains descriptions of each column heading in the UNIX Disk Performance report.

Table 7. UNIX Disk Performance Report Columns

Column Description

Average Queue The average number of requests outstanding over the sampling period

Average Service Time Displays the average time to service disk requests in milliseconds

Average Wait The average time waiting for disk access in milliseconds

Busy Percent Displays the percentage of time the disk is transferring data. The Busy Percent value lets you check whether a process is I/O bound. Values greater than 30% usually indicate excessive paging out to disk, or that a process is I/O bound. If the Busy Percent value is high (greater than 30%), and CPU utilization is also high (greater than 80%), your system is probably overloaded and experiencing performance degradation.

Disk Name Displays the name of a mounted physical device


Transfer Rate Displays the number of transfers per second during a monitoring interval. The transfer rate is one indicator of how fast your disk is moving data. Transfer Rate does not account for variables such as disk format and efficiency of space usage that also affect the speed of data transfer.

Transferred Bytes (KBytes)

Displays the total number of bytes transferred from disk during the recording interval. The Transferred Bytes count is one indicator of how fast your disk is moving data. It does not account for variables, such as disk format and efficiency of space usage, that also affect the speed of data transfer.




Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example



Table 7. UNIX Disk Performance Report Columns

Column Description



Disk Utilization Report 65

Disk Utilization Report

IntroductionThis chapter contains information that helps you use the UNIX Disk Utilization report to identify system performance problems caused by disk space shortage, and uneven distribution of space usage across disks and file systems.

Chapter ContentsHow the UNIX Disk Utilization Report Helps You . . . . . . . . . . . . . 66Typical Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Inside the UNIX Disk Utilization Report . . . . . . . . . . . . . . . . . . . . . . . . . . 70

5

How the UNIX Disk Utilization Report Helps You



OverviewBy viewing the monitored disk utilization data collected by the OMEGAMON XE for UNIX on remote systems, you can:

� Keep your network running smoothly by helping you identify potential system performance problems before they occur. For example, by monitoring file system information you can determine if a file system is being used to its full potential, or if the ratio of inodes to disk space is balanced.

� Increase system efficiency by keeping you constantly informed of how your system uses disk space


Using the UNIX Disk Utilization reportBy viewing monitored disk utilization data collected by the OMEGAMON XE for UNIX, you can:

� Improve the performance of your UNIX system by pinpointing tasks that are impacting disk utilization.

� Increase your system efficiency by keeping you informed of disk utilization across your network.



Sample UNIX Disk Utilization ReportThe illustration shows a representative Disk Utilization report.

Using the Chart viewYou can view the current space available data of any monitored UNIX system as a chart by selecting UNIX Disk Utilization Chart from the View pulldown menu.

The UNIX Disk Utilization Chart shows you at a glance the relationship between free space available and the amount of disk space used on any disk. It provides a quick way of scanning a complete disk at one time to see its space available. With one glance you can understand and respond efficiently to any space shortage about to occur.



Sample UNIX Disk Utilization chartThe illustration shows you an example of the UNIX Disk Utilization chart.


Typical Scenarios

Typical Scenarios

Viewing the availability of real-time disk spaceWhile monitoring the UNIX systems in use at your site, you open the UNIX Disk Utilization report to view real time space available data. When you open the report, current data from UNIX managed systems fills the report. In the first column the system name appears. By scanning columns to the right, you see the Space Used and Space Available.

Generally, systems perform best when disks have plenty of available disk space. A relatively large amount of space available usually requires no intervention. However, if the used disk space rises above 85% (a warning condition), you should notify your system administrator. The critical condition might be 95%.

In addition, when the amount of space available drops to a low percentage, such as below 10%, notify your system administrator of the situation. Your administrator can then take corrective action, which includes freeing up space used by nonessential files, such as old log files or temporary files.

Determining if a remote file system is mountedAnother scenario involves determining if a system is mounted. This is important when you monitor UNIX systems that reside at remote locations. By viewing the UNIX Disk Utilization report using the Mount Point column, you can easily and quickly determine whether or not a file system is mounted. This information allows you to take appropriate action without waiting for a phone call from people depending on that file system being online.

Inside the UNIX Disk Utilization Report



OverviewThe UNIX Disk Utilization Report contains nine columns and includes a UNIX Disk Utilization chart. Monitored data for each managed system appears in rows in each column. You can use any column appearing in a report to create a situation that monitors system conditions that exceed a threshold value.

Reminder about sorting and filtering columnsYou can sort or filter information in the columns of the Disk Utilization Report to modify the way in which you view information regarding availability of disk space.



Column heads and their descriptionsThe table contains descriptions of each column heading in the UNIX Disk Utilization report.

Table 8. UNIX Disk Utilization Report Columns

Column Description

Inodes Free Displays the number of inodes currently available on your file system

Inodes Used Displays the percentage of inodes currently allocated to files. This value equals the Inode_Size value minus the Inodes_Free value.



Inodes Used Percent Displays the percentage of inode space currently allocated to files

If the Inodes Used Percent value increases to a high level, you have a shortage of inodes and need to notify your system administrator to take corrective action. This might include allocating more space for the file system, deleting unused files, or reconfiguring the file system.

Mount Point Displays the pathname of the directory on which the file system is mounted

Name Displays the name of the physical disk partition where the file system is mounted

Size (KBytes) Displays the total space (in kilobytes) on a file system

Space Available (KBytes)

Displays the amount of unused space currently available to non-superusers on a filesystem, expressed in kilobytes. This disk space does not include any space which is reserved for supersusers. A low value in this column, relative to the disk size, alerts you to critical disk space conditions.

If this value is low for one or more filesystems, relative to the disk size, you may need to evaluate reconfiguring the filesystem to distribute the files more evenly across disks.

Space Used (KBytes) Displays the amount of space (in kilobytes) currently in use on the file system. A high value in this column alerts you to critical disk space conditions.

If this value is low for one or more file systems and high for others, you may need to evaluate reconfiguring the file system to distribute the workload more evenly across disks.

Table 8. UNIX Disk Utilization Report Columns (continued)

Column Description



Space Used Percent Displays the space currently used on the file system, expressed as a percentage of the sum of used and available space. The Space_Used_Percent reflects the percentage of disk space which is available to non-superusers. A high value in this column alerts you to critical disk space conditions.


Total Inodes Displays the number of inodes allocated on a file system. The size (in bytes) of a file.


Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example



Table 8. UNIX Disk Utilization Report Columns (continued)

Column Description

File Information Report 73

File Information Report

IntroductionThis chapter describes the UNIX File Information report and shows a sample report along with a description of each of the report columns.

Chapter ContentsHow the UNIX File Information Report Helps You . . . . . . . . . . . . . . 74A Typical Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Inside the UNIX File Information Report . . . . . . . . . . . . . . . . . . . . . . . . . . 77

6

How the UNIX File Information Report Helps You



OverviewThe UNIX File Information report contains system information that helps you improve the performance of your system and obtain detailed information such as file path, file attributes, and time data about a specific file.

Using the UNIX File Information reportThis report displays directories and files. When you first open the report, it displays the files and directories in the root directory.

By viewing the file information on monitored file systems collected by OMEGAMON XE for UNIX on remote systems, you can:

� Find information about files fast by quickly pinpointing specific information you need

� Increase system productivity by allowing the system administrator to change how files are used, based on the needs of system users



Sample UNIX File Information reportThe illustration shows a representative UNIX File Information report.

Using the Chart ViewThe UNIX File Information report has no chart view.

A Typical Scenario


A Typical Scenario

OverviewSuppose you want to track the size of a particular file that may be taking up too much disk space. You can set a situation to notify the system administrator when a file grows beyond a certain size.

You could then use the UNIX Disk Utilization report to determine how much space is left on the disk.


Inside the UNIX File Information Report


OverviewThe File Information report contains 12 columns. Monitored file data for each file or directory appears as rows in each report. You can use any column appearing in a report to create a situation that monitors system conditions for a threshold value.

Reminder about sorting and filtering columnsYou can sort or filter information in the columns of the File Information report to modify the way in which you view disk inode information.


Column heads and their descriptionsThe table contains descriptions of each column heading in the UNIX File Information report. Column information is listed alphabetically.

Table 9. UNIX File Information Report Columns

Column Description

Access Displays a four-digit octal number representing the access rights associated with a file

File Displays the name of the file or directory. If you want to list the files and subdirectories in a directory, select the row containing the directory and click the mouse button.

Group Displays the logical group to which a file owner belongs

Last Accessed Time Displays the date and time of the last file access

Last Changed Time Displays the date and time of the last change to a file

Link Name Displays the name of the link to this file

Links Displays the number of links associated with a file

Owner Displays the name of the owner of a file



Path Displays the full path containing the selected file or directory

Size The size (in bytes) of the file.


Type Identifies the files as one of the following types:

Dir = Directory

File = File

Link = Link

Sock = Socket

Spec = Special file

Table 9. UNIX File Information Report Columns (continued)

Column Description



More about the access columnThe Access attribute column in the File Information report gives you information about who has permission to access a file, and what type of access each person has. The Access attribute value is a four-digit octal number. From left to right, the digits have the following meanings:

For example, a file with 0751 attribute access can be:

� Read, written to, and executed by the owner

� Read and executed by the group

� Executed by everyone

Another example is the access attribute value of 4711. This file can be:

� Read, written to, and executed by the owner

� Executed by everyone

� After execution, the file will take on the user ID of the owner

For additional informationSee the “ls” command in the manual pages of the UNIX Operating System for additional information.

Digit Placement Meaning

1st Set user ID of file upon execution

2nd Permissions for the file owner

3rd Permissions for the group belonging to the file owner

4th Permissions for other users



Network Report 81

Network Report

IntroductionThis chapter contains information about the UNIX Network report. This report contains monitored data that helps you see your overall network performance, and supplies you with information about network interfaces on your monitored UNIX systems.

Using this real time network information, you can:

� Fine-tune your network by allowing you to pinpoint bottlenecks in network traffic so your system administrator can reroute jobs to avoid them

� Increase system productivity by providing you with the information that lets you determine how network resources can be used more efficiently

Chapter ContentsHow the UNIX Network Report Helps You . . . . . . . . . . . . . . . . . . . . . . . . 82A Typical Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Inside the UNIX Network Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

7

How the UNIX Network Report Helps You



OverviewThe UNIX Network report contains numerical attributes that report the changing interface workload throughout each workday.This information allows your system administrator to see the ebb and flow of network traffic.


Using the UNIX Network reportThe UNIX Network report helps you:

� See how much data your network interfaces transmit and receive� Identify network interfaces� Determine whether the interfaces are operational� View the amount of data traffic that flows through interfaces� Justify rerouting network data traffic, if necessary� Measure errors in frame transmission and collisions

Network Report 83


Sample UNIX Network reportThe illustration shows a representative UNIX Network report.

Using the Chart ViewThe UNIX Network report has no chart view.

A Typical Scenario


A Typical Scenario

Viewing the performance of your networkSuppose users are complaining that they are having trouble accessing an Ethernet network that connects to other networks in your system. Use the UNIX Network report to view the gateway or router that connects to Ethernet in question. By viewing data received and transmitted through this gateway or router, you can determine if it is working properly.

If the router is overloaded, you may want to view other routers or gateways to see which ones are available, and re-route data traffic to one with a lighter workload.

You can also view the UNIX Network report to view information about collisions on a particular network interface. If the number of collisions is high, this may indicate that the capacity of the network hardware has been reached.

Network Report 85

Inside the UNIX Network Report


OverviewThe UNIX Network report contains 12 columns. Because of screen width limitations, you need to scroll to the right to view all 12 columns. You can use any columns appearing in the report to specify as a threshold value in the creation of a situation. You can sort or filter information in the Network Report to modify the way in which you view network information.

Use Network attributes to create situations that refer to network characteristics such as received count, sent count, network interface name, and interface status.

Network is a multiple-instance attribute group. You cannot mix these attributes with those of any other multiple-instance group.

Reminder about sorting and filtering columnsYou can sort or filter information in the Network report to modify the way in which you view network information.



Frames vs. PacketsThe Received Count (Frames) and Transmitted Count (Frames) show the raw frame counts for the interface. Frames and packets are not necessarily the same thing.

System administrators may define the interface so that multiple frames are sent or received in a packet. The network report and the network attributes display frame counts.



Column heads and their descriptionsThe table contains descriptions of each column heading in the UNIX Network report. Column information is listed alphabetically.

Table 10. UNIX Network Report Columns

Column Description

Collisions Displays the number of times during the sampling period a frame transmitted by the network interface collided with another frame. This occurs when another interface on the same local network transmits a frame at nearly the same time.

Frames Received Displays the number of frames received by the network interface during the sampling period

Frames Transmitted Displays the number of frames sent by the network interface during the sampling period

Interface DNS Name Displays the Domain Name Service (DNS) entry associated with an interface

Interface IP Process Displays the Internet Protocol (IP) address of an interface

Interface Status Indicates if a network interface is currently in use

Input Errors The number of frames received by the interface with errors during the sampling period

Maximum Transmission Unit

Displays the maximum packet size (in bytes) for the specified network interface. This is a fixed value.

Network Report 87


Network Interface Name

Identifies the network interface adapter.

The Network Interface Name is a string comprised of an "Interface Name, Unit Number" where:� The name is a two-character representation of the

adapter, based on the hardware, operating system, and installation procedure.

� The unit represents the physical adapter number, if more than one adapter of a particular type is installed in your system.

For example, if two Ethernet adapters are installed on your system, their network names are en0 and en1, respectively.

Typical network interface adapters on an AIX system are represented as follows:

en Ethernet

lo Loopback

tr Token Ring

sl SLIP

Other operating systems can refer to the adapter type in a different manner. For example, on SunOS, ethernet adapters are typically represented by le. On HP-UX, you often see ethernet represented as lan. The possible combinations based on hardware, operating systems, and installation options are virtually impossible to list. Ask your System Administrator for assistance in determining specific adapter types installed on your system.

Output Errors Displays the number of frames transmitted by the interface with errors during the sampling period

Received Count (Frames)

Displays the total number of frames received since the interface was configured, or since the system was rebooted



Column Description



Transmitted Count (Frames)

Displays the total number of frames transmitted since the interface was configured, or since the system was rebooted.


Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example




Column Description

Network File Server (NFS) Reports 89

Network FileServer (NFS) Reports

IntroductionThis chapter describes the UNIX Network File Server (NFS) report. This report contains Statistics attributes you can use to create situations that refer to Network File System call rates and errors.

Chapter ContentsHow the UNIX NFS Report Helps You . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Inside the UNIX NFS Server Activity report. . . . . . . . . . . . . . . . . . . . . . . . 93Inside the UNIX NFS Client Activity report . . . . . . . . . . . . . . . . . . . . . . . . 96

8

How the UNIX NFS Report Helps You



OverviewNFS Client attributes report on calls from the managed system to NFS Servers. NFS Server attributes report on NFS calls to the managed system.

You can mix these attributes with those of any other single-instance group.

Additionally, OMEGAMON XE for UNIX provides historical versions of these reports. When you choose an historical report, the Time Span Selection window displays. You can request to view up to 24 hours of historical data for a particular report.

Two report views—NFS Server Activity and NFS Client ActivityThe NFS report has two report views:� The NFS Server Activity report view

� The NFS Client Activity report view

The NFS Server Activity shows information about an NFS Server.

The NFS Client Activity report shows information about an NFS client.



Sample UNIX NFS Server Activity reportThe illustration shows a sample NFS Server Activity report.

Sample UNIX NFS Client Activity reportThe illustration shows a sample NFS Client Activity report.



Procedure for accessing the UNIX NFS reports

1. Double-click the UNIX NFS Activity icon, which is located on the Reports screen.

2. Double-click the name of the system for which you want information.

3. Double-click Report from the row of commands at the top of your screen.A pop-up menu appears, showing two report names: NFS Server Activity report and NFS Client Activity report.

4. Double-click the name of the report for which you want information.Result: The report you want to see appears on your screen.


Inside the UNIX NFS Server Activity report


Reminder on sorting and filtering rowsYou can sort or filter information in the rows of the UNIX NFS reports.


Report Flag ValuesRefer to “Report Flag Values” on page 41 for information on report flag values.

Rows and their descriptionsThe table contains descriptions of each row heading in the UNIX NFS Server Activity report. Row information is listed alphabetically.

Table 11. UNIX NFS Server Activity Report Rows

Row Description

Calls Displays the number of calls rejected by a server, over a specific period of time.

Calls Rejected Displays the number of calls rejected by a server during a monitoring interval

File Creates Displays the number of File Creates calls made to a server during a monitoring interval

File System Statistics Calls The number of file statistics calls made within a monitoring interval

Get Attribute Calls Displays the number of calls made to determine what type of file is being called. For example, a text file, or an executable file.

Link Calls Displays the number of hard link reports made by a server during a pre-defined time interval

Lookups Displays the number of Lookups requests made by an NFS server during a monitoring interval

Make Directory Calls Displays the number of Make Directory calls made to a server during a monitoring interval



Null Calls Displays the number of Null NFS calls made by a client for checking connectivity during a monitoring interval

Read Calls Displays the number of Read Calls made to a server during a monitoring interval

Read Directory Calls Displays the number of Read Directory Calls made to a server during a monitoring interval

Read Link Calls Displays the number of call requests a client made to a server to read a linked file, during a monitoring interval

Rejected Call Percentage Displays the percentage of NFS calls rejected by a server during a monitoring interval

Remove Directory Calls The number of Make Directory calls made to a server during a monitoring interval

Remove File Calls The number of Remove File calls made to a server during a monitoring interval

Rename File Calls Displays the number of Rename File calls made to a server during a monitoring interval

root Calls Displays the number of NFS calls made to server root during a monitoring interval

Set Attribute Calls Displays the number of NFS calls made to set the attributes of a file during a monitoring interval

Symbolic Link Calls Displays the number of Symbolic Link calls made to a server during a monitoring interval

System Name Displays the name of the system


Write Cache Calls Displays the number of Write Cache calls made to a server during a monitoring interval

Writes Displays the number of Writes calls made to a server during a monitoring interval

Table 11. UNIX NFS Server Activity Report Rows (continued)

Row Description




Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example



Table 11. UNIX NFS Server Activity Report Rows (continued)

Row Description

Inside the UNIX NFS Client Activity report



Reminder about sorting and filtering rowsYou can sort or filter information in the rows of the UNIX NFS reports.



Rows and their descriptionsThe table contains descriptions of each row heading in the UNIX NFS Client Activity report. Row information is listed alphabetically.

Table 12. UNIX NFS Client Activity Report Rows

Row Description

Calls Displays the number of calls made to a client over the monitoring interval

Calls Rejected Displays the number of NFS calls rejected by the server during the monitoring interval

File Creates Displays the number of File Creates calls made to a server during a monitoring interval

File System Statistics Calls Displays the number of file statistics calls made within a monitoring interval

Get Attribute Calls Displays the number of calls made to get the attributes of a file (to determine what type of file is being called. For example, a text file or an executable file).

Link Calls Displays the number of Client Link calls made to a server during a monitoring interval



Lookups Displays the number of Lookups requests made by an NFS server during a monitoring interval

Make Directory Calls Displays the number of Make Directory calls made by a client to a server during a monitoring interval

Null Calls Displays the number of null NFS calls generated for checking connectivity to the server during a monitoring interval

Read Calls Displays the number of Read Calls made to a client during a monitoring interval

Read Directory Calls Displays the number of Read Directory Calls made to a client during a monitoring interval

Read Link Calls Displays the number of call requests a client made to a server to read a linked file during a monitoring interval

Rejected Calls Percentage Displays the percentage of NFS calls rejected by a client during a monitoring interval

Remove Directory Calls Displays the number of Remove Directory calls made by a client to a server during a monitoring interval

Remove File Calls Displays the number of Remove File calls made by a client to a server during a monitoring interval

Rename File Calls Displays the number of Rename File calls made by a client to a server during a monitoring interval

root Calls Displays the number of NFS calls made by user root during a pre-defined monitoring interval

Set Attribute Calls Displays the number of NFS calls made to set the attributes of a file during the monitoring interval

Symbolic Link Calls Displays the number of Symbolic Link calls made by a client to a server during a monitoring interval

System Name Displays the name of the system


Table 12. UNIX NFS Client Activity Report Rows (continued)

Row Description



Write Cache Calls Displays the number of Write Cache calls made by a client to a server during a monitoring interval

Writes Displays the number of Writes calls made by a client to a server during a monitoring interval


Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example



Table 12. UNIX NFS Client Activity Report Rows (continued)

Row Description

Process Reports 99

Process Reports

IntroductionThis chapter describes the UNIX Process reports, which help you determine the processes that are running on a managed system and how to use these reports to improve process flow throughout your system.

Chapter ContentsHow the UNIX Process Report Helps You. . . . . . . . . . . . . . . . . . . . . . . . 100Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Process Detail Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105A Typical Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Inside the Top CPU Time Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Inside the UNIX Process Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Inside the UNIX Child Process Report. . . . . . . . . . . . . . . . . . . . . . . . . . . 119Inside the UNIX Process Group Report . . . . . . . . . . . . . . . . . . . . . . . . . . 124Inside the Process Application Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Inside the Process Command Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Inside the Process Resource Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

9

How the UNIX Process Report Helps You



OverviewThe UNIX Process report provides detailed information about all processes owned by each user. You can view this information in the detail report columns.

The UNIX Process reports help you:

� Solve process problems quickly by giving you information you need to pinpoint problem processes and their owners.

� Improve system performance by providing you with real-time information on which users and what processes are using the system.


Monitoring process informationWhen monitoring process information, pay special attention to the following attribute values.

� Large values in the CPU Utilization column indicate a CPU-intensive process. These result in a lower process priority. Small values indicate an I/O intensive process. These result in a higher process priority.

� A value greater than 100 indicates a process is consuming a large amount of the CPU. If this value is high, check the Execution State column to see if the process is running, and the Time column to see how long the process has been running.

Variable value for CPU utilizationThe CPU Utilization value is machine-dependent and also varies according to the version of the UNIX operating system running.

Process Reports 101


Special Information about the Flag Field The Flag field of the UNIX Process reports contains hexadecimal and additive flags. These flags are available for historical purposes only, and contain no information regarding the current status of your monitored process.

Special Notice to Solaris Users

Hexadecimal and additive flags shown in the Flag field of the UNIX Process reports are available for historical purposes only. These fields are not relevant to Solaris systems.

Navigation


Navigation

OverviewOMEGAMON XE for UNIX Version 140 introduces several new process reports. The new reports are:

� Top CPU Time report� Process Detail reports

– Application report

– Resource report

– Command report

– Process Group report

The diagram below shows the navigation to the various reports.

Process Reports 103

Navigation

Sample Top CPU Time reportThe illustration shows a representative UNIX Top CPU Time report.

Sample UNIX Process ReportThe illustration shows a representative UNIX Process report.

Navigation


Sample Process Topology graphic viewThe UNIX Process report has a Process Topology Graphic view that allows you to view the hierarchical relationship between processes. You can zoom in or out on the graphic using the tools in the tool palette.

Process Reports 105

Process Detail Reports


Right-click menu for process detail reportsThe illustration below shows the pop-up menu for selecting process detail reports.

Sample Child Process reportThe illustration below shows a representative Child Process report.



Sample Process Group reportThe illustration below shows a representative Process Group report.

Sample Process Application reportThe illustration below shows a representative Process Application report.

Process Reports 107


Sample Process Command reportThe illustration below shows a representative Process Command report.

Sample Process Resource reportThe illustration below shows a representative Process Resource report.

A Typical Scenario


A Typical Scenario

Monitoring CPU utilizationYou can use a product-provided situation to help you monitor CPU utilization for each process. If the CPU Utilization value is high, and the elapsed Time value is high, then the process is probably CPU-bound, and may need to be removed. If this situation occurs, contact your system administrator immediately.

Process Reports 109

Inside the Top CPU Time Report


OverviewThe UNIX Top CPU report contains 17 columns. This report displays the processes using the most CPU time over the sampling period. Monitored data for each process appears as rows in the report. Because of screen width limitations, you need to scroll to the right to view all 17 columns. You can use data appearing in a report to create a situation that monitors system conditions for a threshold value.

Reminder about sorting and filtering columnsYou can sort and filter information in these columns to change the way in which you view process information. Refer to “Sorting Report Data” on page 46 and “Filtering Report Data” on page 47 for more information about sorting and filtering data in reports.


Column heads and their descriptionsThe table contains descriptions of each column heading in the UNIX Top CPU report. Column information is listed alphabetically.

Table 13. UNIX Process Top CPU Time Report Columns

Column Heading Description

Command The name of the UNIX process and the arguments provided to the command. The command field is limited to 31 characters. An ellipsis (...) indicates that the command has been truncated.

CPU Pct The percentage of CPU used by the process which is collected from the operating system structure. (Not applicable to V120.)



CPU Utilization Displays a numerical value indicating the relative CPU intensity of a process. A large value indicates a CPU intensive process. A small value indicates an I/O intensive process. The CPU Utilization attribute represents the number of times a process uses the CPU over a period of 20 system clock ticks. The system decays this value after each 20 clock-tick period by dividing the number by 2.

Event Waited On Displays the memory address of an event (if any) on which the process is waiting. A process must have this information before it can execute.

When sorting based on this field, the CMW orders the data alphanumerically. In some UNIX operating systems, the value for this field is hexadecimal, which results in a sort order that is not meaningful.

Execution State Displays a one-character code that indicates the process state. The meaning of an execution state code may vary according to the type of UNIX system you are monitoring. Refer to the manual pages of your UNIX system for details.The meanings of the following codes are generally consistent across all UNIX systems:

0 NonexistentA The process is active.I IntermediateO RunningR The process is runnable.S The process is sleeping.T The process is stopped.W WaitingX GrowingZ The process terminated, but has not completed

exiting the system (the process is in a zombie state).



Process Reports 111


Flag A hexadecimal sum of multiple constants. Each constant contributing to the value represents a process characteristic.The meaning of this flag varies according to the type of UNIX system you are monitoring. Refer to the manual pages of your UNIX system for details.

Note: This field does not apply to the Solaris platform.

Mem Pct The percentage of system memory used by this process. (Not applicable to V120.)

Nice Value Displays the nice value, which is the requested execution priority of the process in relation to other processes. The higher the nice value, the lower the priority of the command. The nice value, plus the minimum user process priority level equals the priority of the process. The range of nice values varies among UNIX systems. See the nice UNIX manual page for more information.

Parent Process ID Displays the unique numerical identifier of a parent process. The process that invoked the fork system call is the parent process, and the newly created process is the child process. Every process has one parent process, but a process can have several children. Process 1 is known as init and is the ancestor of every other process in the system.

Priority Displays the current execution Priority value, which is the nice value of the process plus the minimum priority value assigned to all user processes. The higher the priority value, the lower the priority of the command.

Note: For Solaris only

The default priority scheme for Solaris is BSD (pre-SVR4). If the environment variable KUX_Priority_SVR4 is defined, then the SVR4 priority scheme is used for all reports and situations.

The environment variable is set by editing the CandleStartAgent script located in the $CANDLEHOME\bin subdirectory





Process ID A unique numerical identifier that the UNIX operating system kernel assigns to the process.

Size (Kbytes) The resident set size in kilobytes.

StartTime The time the process started.

Terminal Device Displays the number of a terminal device that started a process.

Time Displays the total amount of CPU time that the process has consumed. Format is displayed as DDDdHH:MM:SS.

Should this value become large, it may indicate a runaway or long-running process.

Timestamp Displays the date and time of the last update to the information collected by UNIX remote agents.

User ID Displays the numerical user ID of the owner of the process.



Process Reports 113



Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example





Inside the UNIX Process Report



OverviewThe UNIX Process report contains 17 columns. This report displays all of the processes on the monitored system. On busy systems, this report can require extended time to display. Monitored data for each process appears as a rows in the report. Because of screen width limitations, you need to scroll to the right to view all 17 columns. You can use data appearing in a report to create a situation that monitors system conditions for a threshold value.



Column heads and their descriptionsThe table contains descriptions of each column heading in the UNIX Process report. Column information is listed alphabetically.

Table 14. UNIX Process Report Column Headings




Process Reports 115








Table 14. UNIX Process Report Column Headings (continued)















Process Reports 117



Size (KBytes) The resident set size in kilobytes.






User ID Displays the numerical user ID of the owner of the process






Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example





Process Reports 119

Inside the UNIX Child Process Report


OverviewThe UNIX Child Process report displays processes spawned from the process selected in the UNIX Process report. The report contains the same columns as the UNIX Process report.




Table 15. UNIX Child Process Report Column Headings












Table 15. UNIX Child Process Report Column Headings (continued)


Process Reports 121
















Size (KBytes) The resident set size in kilobytes.


Terminal Device Displays the number of a terminal device that started a process







Process Reports 123



Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example





Inside the UNIX Process Group Report



OverviewThis report is the same as the UNIX Process report but displays all the processes for a selected process group.The report contains the same columns as the UNIX Process report.




Table 16. UNIX Process Group Report Column Headings




Process Reports 125








Table 16. UNIX Process Group Report Column Headings (continued)















Process Reports 127















Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example





Process Reports 129

Inside the Process Application Report


OverviewThe Process Application report displays application related information for a particular process. Information includes detail process ID data, execution state, and the number of threads in this application. This report is not applicable to V120.



Row titles and their descriptionsThe table contains descriptions of each column heading in the UNIX Process Application report. Row information is listed alphabetically.

Table 17. Process Application Report Row Titles

Row Title Description

CPU ID The processor identification number on which the process is running

Effective Group ID The effective group identification number.

Effective User ID The effective user identification number.






0 NonexistentA The process is active.I IntermediateO RunningR The process is runnable.S The process is sleeping.T The process is stopped.W WaitingX GrowingZ The process terminated, but has not

completed exiting the system (the process is in a zombie state).



Table 17. Process Application Report Row Titles (continued)


Process Reports 131








Process Group Leader ID The process group leader identification.


Real Group ID The real group identification number

Scheduling Class The name of the scheduling class.





Session ID The session identification number.


System Name The name of the monitored system.


Thread Count The number of threads in the process.



User Name The name of the user



Process Reports 133



Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example





Inside the Process Command Report



OverviewThe Process Command report displays process commands up to 100 characters in length. Information includes process ID, parent process ID, User ID, and the start time of the process. This report is not applicable to V120.



Process Reports 135


Row titles and their descriptionsThe table contains descriptions of each column heading in the UNIX Process Command report. Row information is listed alphabetically.

Table 18. Process Command Report Row Titles



Process Command Displays the process command up to 100 characters

Process ID Displays the unique numeric identifier of the process







Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example



Table 18. Process Command Report Row Titles (continued)


Process Reports 137

Inside the Process Resource Report


OverviewThe Process Resource report displays resource related information for a particular application. Resource information includes CPU percent, process start time, process elapsed time, resident set size, process CPU percentage, children processes CPU usage, CPU wait time, lock wait time, and major and minor faults. This report is not applicable to V120.



Row titles and their descriptionsThe table contains descriptions of each column heading in the UNIX Process Resource report. Row information is listed alphabetically.

Table 19. Process Resource Report Row Titles


Child System CPU Time The sum of children’s system CPU time spent executing for this process.

Child User CPU Time The sum of children’s user CPU time spent executing for this process.

Context Switches The number of context switches for this process.

CPU Pct The percentage of CPU collected from the operating system structure.



Elapsed Time The time used executing this process.

Heap Size The size of heap in kilobytes.

Involuntary Context Switches

The number of involuntary context switches for this process.

Major Fault The number of page reclaims for this process.

Mem Pct The percentage of system memory used by this process.

Minor Fault The number of page faults needing disk access.

Process ID Displays the unique numeric identifier of the process

Read/Write The number of characters read and written.

Size (KBytes) The resident set size.

Stack Size The size of the stack in kilobytes.


System CPU Time The system CPU time spent executing this process.


Total Child CPU Time The sum of children’s CPU time (user + system time) spent executing for this process.

Total CPU Percent The percentage of CPU used since the process was started.

Total CPU Time The CPU time (user + system time) spent executing for this process.

User CPU Time The user CPU time spent executing this process.

User ID The numerical user ID of the owner of the process.

Virtual Size The virtual process size in kilobytes.

Wait CPU Time The time spent waiting for the CPU.

Wait Lock Time The time spent waiting on locks.

Table 19. Process Resource Report Row Titles (continued)


Process Reports 139



Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example



Table 19. Process Resource Report Row Titles (continued)




Remote Procedure Call (RPC) Report 141

Remote ProcedureCall (RPC) Report

IntroductionThis chapter describes the UNIX Remote Procedure Call (RPC) report. This report contains Statistics attributes that allow you to create situations that refer to RPC call rates and errors.

Chapter ContentsHow the UNIX RPC Report Helps You . . . . . . . . . . . . . . . . . . . . . . . . . . 142Inside the UNIX RPC Server Activity report . . . . . . . . . . . . . . . . . . . . . . 145Inside the UNIX RPC Client Activity report . . . . . . . . . . . . . . . . . . . . . . . 147

10

Using the

Job Repo

How the UNIX RPC Report Helps You



OverviewThe RPC Client attributes report on calls made by the managed system to RPC Servers. The RPC Server attributes report on RPC calls made to the managed system.


Two report views—RPC Server Activity and RPC Client ActivityThe RPC report has two report views:� The RPC Server Activity report view

� The RPC Client report view

Sample UNIX RPC Server Activity reportThe illustration shows a sample UNIX RPC Server Activity report.



Sample UNIX RPC Client Activity reportThe illustration shows a sample RPC Client Activity report.

Procedure for accessing the UNIX RPC reportsUse the procedure to access the UNIX RPC reports.

1. Double-click the UNIX RPC Activity icon, which is located on the Reports screen.

2. Double-click the name of the system for which you want information.

3. Single-click Report from the row of commands at the top of your screen. A pop-up menu appears, showing two report names: RPC Server Activity report and RPC Client Activity report.

4. If you want to view the NFS Server Activity report rather than the NFS Client Activity report, you can double-click the row named NFS Client Activity report.Result: The report you want to see appears on your screen.



Procedure to change the default report settingThe default report setting is the RPC Client Activity Report.

1. If you want to change the default report setting, right-click anywhere in the report. The Edit Custom Report pop-up screen appears.

2. Select Settings. The Settings menu appears.

3. Select the Custom Report tab at the top of the Settings menu. The Custom Report view appears.

4. Click on the down arrow button located to the right of the View dialog box.

5. Select RPC Server Activity Report.

6. Select the Default button.

7. Select the OK button.Result: The default report setting is now the RPC Server Activity report.


Inside the UNIX RPC Server Activity report


Reminder on sorting and filtering rowsYou can sort or filter information in the rows of the UNIX RPC reports.



Rows titles and their descriptionsThe table contains descriptions of each row heading in the UNIX RPC Server Activity report.

Table 20. UNIX RPC Server Activity Report Row Titles

Row Description

Calls Rejected Displays the number of RPC calls rejected by a server, during a monitoring interval

Packets Too Short Displays the number of incomplete RPC packets that were too short in length received by a server during a monitoring interval

Packets With Malformed Header

Displays the number of RPC packets that had malformed headers and were received by the server during a monitoring interval

Times RPC Packet Unavailable

Displays the number of time a server attempted to receive a packet when none was available, during a monitoring interval

Timestamp Displays the date and time of the last update to the information collected by the UNIX remote agents




Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example



Table 20. UNIX RPC Server Activity Report Row Titles (continued)

Row Description


Inside the UNIX RPC Client Activity report


Reminder about sorting and filtering rowsYou can sort or filter information in the rows of the UNIX RPC reports.



Row titles and their descriptionsThe table contains descriptions of each row heading in the UNIX RPC Client Activity report.

Table 21. UNIX RPC Client Activity Report Row Titles

Row Description

Calls Rejected by Server Displays the number of calls rejected by a server during a monitoring interval

Calls Retransmitted Displays the number of RPC packets retransmitted to an RPC server during the monitor interval

Calls Timed Out Displays the number of times the wait for an acknowledgment of calls made by the system, from its server, timed out

Replies Not Matching Calls Displays the number of times the managed system received replies from an RPC server that did not match calls, during a monitoring interval

Times Authentication Refreshed

Displays the number of times the managed system had to resend the authentication information for an RPC call during the monitoring interval



Times Call Wait On Busy Displays the number of times the initial bind for an RPC call from the managed system had to wait because of a busy server

Timestamp Displays the date and time of the last update to the information collected by the UNIX remote agents


Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example



Table 21. UNIX RPC Client Activity Report Row Titles (continued)

Row Description

System Reports 149

System Reports

IntroductionThis chapter describes the UNIX System reports, which contain detailed information about your monitored UNIX systems. You can use the UNIX System reports to help you improve system performance and, identify and modify system activity information.

Chapter ContentsHow the UNIX System Reports Help You . . . . . . . . . . . . . . . . . . . . . . . . 150Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155A Typical Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Inside the UNIX System Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Inside the System Cache and Buffers Report . . . . . . . . . . . . . . . . . . . . . 160Inside the System Load Average Report . . . . . . . . . . . . . . . . . . . . . . . . . 162Inside the System Workload Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

11

How the UNIX System Reports Help You



OverviewThe UNIX System reports supply basic identification and system activity information on your monitored UNIX systems. Use these reports to identify the configuration of your systems and check their current activity levels.

By viewing the monitored system data collected by OMEGAMON XE for UNIX on remote systems, you can:

� Improve system performance by helping you identify the configuration of your systems and check their current activity levels

� View monitored data collected from remote systems either as a report or as a chart.


Monitoring system dataThe UNIX System reports provides information on load averages, network connections, and other types of activity, such as:

� The type and version of Operating System you are monitoring, for example, AIX 4.1.4, HP-UX 10.20, or Solaris 2.5

� The memory size, to virtual memory size (paging space)

� The number of user sessions

� The current number of processes that are active

� The IP address of the system

� The status of certain network connections

System Reports 151


Sample UNIX System reportThe illustration shows a representative UNIX System report.

Using the Chart ViewYou can view the memory data of any remote UNIX system as a chart by selecting UNIX Memory Analysis Chart from the View pulldown menu. The Memory Analysis chart shows you at a glance the amounts of free memory available. With one glance you can understand and respond efficiently to any memory shortage about to occur.



Sample UNIX Memory Analysis chartThe illustration shows a sample of the UNIX Memory Analysis Chart.

System Reports 153


Sample System Cache and Buffers reportThe illustration shows a sample of the UNIX System Cache and Buffers report.

Using the System Load Average report viewThe System screen includes a UNIX System Load Average report view, which gives you load average information. To view this report, select it from the View Menu while the UNIX System report is open.

Sample System Load Average report viewThe illustration shows a representative UNIX System Load Average report for V120 OMEGAMON XE for UNIX.



Sample System Workload reportThe illustration shows a sample of the UNIX System Workload report.

System Reports 155

Navigation

Navigation

Overview Three new reports are presented in OMEGAMON XE for UNIX V140. These reports are:

� System Workload report

� System Cache and Buffers report

� Memory Analysis chart

Managed System report selection menuThe mouse right-click menu from the UNIX System — Managed System Selection view displays the various system reports available.

Right-click menu

Highlight a managed system and right-click the mouse. The following menu is presented to you.

A Typical Scenario


A Typical Scenario

Viewing the performance of your system workloadSuppose that while monitoring the UNIX systems in use at your site, you open the UNIX System report to view the flow of data throughout your monitored UNIX systems.

You can use the UNIX System Load Average report to get information about the number of processes in the run queue of the UNIX kernel during a specified time interval.

If the load average is high and not improving, you can use the UNIX Process report to track down the jobs and users responsible for the load. Load averages provide an overall picture of system activity for your monitored UNIX systems. The load average is one of the first indicators you should examine if system response is poor.

System Reports 157

Inside the UNIX System Report


OverviewThe UNIX System report is a vertical format in Version 140. Monitored data for the selected managed system appears in a column to the right of the attribute title. Any data appearing in a report can be used in the creation of a situation that monitors system conditions for a threshold value.

Reminder about sorting and filtering columnsYou can sort or filter information in the columns of the UNIX System report to modify the way in which you view system status information.


Row titles and their descriptionsThe table lists the row headings in the UNIX System report and their definitions. Row information is listed alphabetically.

Table 22. UNIX System Report Row Titles


Free Memory (KBytes) Displays the number of kilobytes of Random Access Memory (RAM) currently available on the system

Net Address Displays the Internet Protocol (IP) address of the monitored system

Number of System Proc

Displays the total number of processes running on the system, including user and system processes in any state

Number of User Sessions

Displays the total number of interactive user sessions running

System Name The name of the managed system.




Total Real Memory (KBytes)

Displays the total number of kilobytes of physical memory on a system you are currently monitoring

Total Virtual Memory (KBytes)

Displays the total amount of disk space (in kilobytes) available for paging operations on the monitored system

For Solaris Systems, the Total Virtual Memory includes the swap space from all configured swap areas (disk space) and the swap space in the form of physical memory. The swap space in the form of physical memory may vary depending on the system load. Because of this, the Total Virtual Memory for Solaris Systems also may vary among different collection sampling.

Type Indicates the kind of UNIX operating system residing on a monitored host

For example, you may see AIX, HPUX, SUNOS, or OSF1 displayed on your screen.

AIX IBM AIX operating system resides on the monitored host.

HPUX Hewlett Packard HP-UX operating system resides on the monitored host.

SUNOS Sun Microsystems Solaris I or Solaris II operating system resides on the monitored host.

Version Specifies the release number of a UNIX operating system on the network

Table 22. UNIX System Report Row Titles (continued)


System Reports 159



Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example



Table 22. UNIX System Report Row Titles (continued)


Inside the System Cache and Buffers Report



OverviewThe UNIX System Cache and Buffers report provides detailed information on read and writes for blocks, logical blocks, and nonlogical blocks.

Reminder about sorting and filtering columnsYou can sort or filter information in the columns of the System Cache and Buffers report to modify the way in which you view system status information.


Row titles and their descriptionsThe table lists the row headings in the UNIX System Cache and Buffers report and their definitions. Rows are listed alphabetically

Table 23. System Cache and Buffers Report Row Titles

Row Titles Definition

Block Reads The number of physical block read over the sampling interval.

Block Writes The number of physical block writes over the sampling interval.

Logical Block Reads The number of logical block reads over the sampling interval.

Logical Block Writes The number of logical block writes over the sampling interval.

NonBlock Reads The number of raw I/O reads over the sampling interval.

NonBlock Writes The number of raw I/O writes over the sampling interval.


Timestamp The date and time of the last update to the information collected by the UNIX agent.

System Reports 161



Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example



Table 23. System Cache and Buffers Report Row Titles (continued)

Row Titles Definition

Inside the System Load Average Report



OverviewThe System report includes a UNIX System Load Average report view, which gives you load average information. Load average refers to the average number of processes in the UNIX kernel run queue during an interval. Any data appearing in a report can be used in the creation of a situation that monitors system conditions for a threshold value.

Reminder about sorting and filtering columnsYou can sort or filter information in the columns of the System Load Average report to modify the way in which you view system status information.


Column heads and descriptionsThe table lists the column headings in the System Load Average report and their definitions. Column information is listed alphabetically.

Table 24. System Load Average report columns

Column Description

Boot Time The system boot time in the format MM/DD/YY HH:MM:SS.

V140 agents only.

Load Average (1 Min) The average number of processes in the UNIX kernel run queue during the last minute. Acceptable values for load average vary according to your system. Values less than 2 are usually considered normal. Values greater than 2 may indicate increasing degrees of problem severity.

If the 1-minute Load Average value is high, compare it to the 5- and 15-minute values. If the load average values are increasing with time, you may want to take corrective action. If the values are falling, you may want to delay action to see if the problem corrects itself.

System Reports 163


Load Average (5 Min) The average number of processes in the UNIX kernel run queue during the last five minutes. Acceptable values for load average vary according to your system. Values less than 2 are usually considered normal. Values greater than 2 may indicate increasing degrees of problem severity.


Load Average (15 Min) The average number of processes in the UNIX kernel run queue during the last fifteen minutes. Acceptable values for load average vary according to your system. Values less than 2 are usually considered normal. Values greater than 2 may indicate increasing degrees of problem severity.



Timestamp The date and time of the last update to the information collected by UNIX remote agents.

Up Time System up time in the following time format:

DDDdHH:MM:SSV140 agents only.

For V120 agents, the number of seconds that the system has been running since boot time.

Table 24. System Load Average report columns (continued)

Column Description




Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example



Table 24. System Load Average report columns (continued)

Column Description

System Reports 165

Inside the System Workload Report


OverviewThe UNIX System Workload report provides information on system processes. System processes can be in a variety of states. Additional information includes system calls, execs and forks executed, device interrupts, and CPU context switches.

Reminder about sorting and filtering columnsYou can sort or filter information in the columns of the System Workload report to modify the way in which you view system status information.


Column heads and their descriptionsThe table lists the column headings in the System Workload report and their definitions. Columns are listed alphabetically.

Table 25. System Workload Report Column Heads

Column Description

CPU Context Switches The number of CPU context switches over the sampling interval.

Device Interrupts The number of device interrupts (nonclock) over the sampling interval.

Execs Executed The number of execs executed over the sampling interval.

Forks Executed The number of forks executed over the sampling interval.

Number of System Procs The number of system processes running.

Processes Idle The number of processes currently in the idle state.

Processes Runnable The number of processes that can be run



Processes Running The number of processes currently in the running state.

Processes Sleeping The number of processes currently in the sleep state.

Processes Stopped The number of stopped processes

Processes Zombie The number of zombie processes.

System Calls The number of system calls over the sampling interval.


System Read The number of read() and readv() system calls over the sampling interval

System Write The number of write() and writev() system calls over the sampling interval.

Timestamp The date and time of the last update to the information collected by the agent.

Table 25. System Workload Report Column Heads (continued)

Column Description

System Reports 167



Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example



Table 25. System Workload Report Column Heads (continued)

Column Description



System CPU Reports 169

System CPU Reports

IntroductionThis chapter includes information about the UNIX System CPU reports, how it helps you improve system CPU performance, and how you can use it to identify and monitor system CPU activity.

Chapter ContentsHow the UNIX System CPU Reports Help You . . . . . . . . . . . . . . . . . . . . . . . 170Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171A Typical Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Inside the System CPU Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178Inside the Solaris System CPU Workload Summary Report . . . . . . . . . . 181Inside the Solaris System CPU Workload Report . . . . . . . . . . . . . . . . . . 184

12

How the UNIX System CPU Reports Help You


How the UNIX System CPU Reports Help You

OverviewThe UNIX System CPU reports display percentages of processor activity taking place on each monitored UNIX system. The data in this report can help you:

� Improve system CPU performance by helping you identify managed systems that consume large amounts of CPU time

� Increase system throughput by identifying user demands on CPUs, allowing you to allocate these demands among several CPUs on your system

� Identify managed systems with I/O bottlenecks caused by waits for CPU time

� Identify managed systems with CPU bottlenecks caused by high CPU utilization


Monitoring System InformationUse the UNIX System CPU reports to check for problems, such as:

� Managed systems with high CPU utilization

� Imbalances between user and system CPU demands

� Long CPU waits caused by I/O bottlenecks


Navigation

Navigation

OverviewDepending on whether you are connected to V120 or V140 OMEGAMON XE for UNIX, you see a difference in the reports available and the navigation to view the reports.

From the UNIX System — Managed System Selection menusThe mouse right-click menus from the UNIX System — Managed System Selection view and from selected rows within reports differ for OMEGAMON XE for UNIX V140 and V120 agents.

NOTE:UNIX V120 agents display 01.30.00 in the Version column of the managed system menu. The Version 120 agents mistakenly display the value of 01.03.00. This is the purpose of releasing the UNIX Version 140 rather than a Version 130.

The menus are presented below.

Right-click menu—V140 agents� Highlight a V140 managed system and right-click the mouse. The

following menu is presented to you.

Version 120 UNIX agent

Navigation


Right-click menu—V120 agents

Highlight a V120 managed system and right-click the mouse. The following menu is presented to you.

Right-click menu—V140 Solaris systems only

Highlight a managed system that is a Solaris operating system and right-click the mouse. The following menu is presented to you.

Version 120 UNIX agent


Navigation

Sample UNIX System CPU V120 reportThe illustration shows a representative UNIX System CPU V120 report.

Using the Chart ViewThe illustration shows a representative UNIX CPU Analysis V120 chart.

Navigation


Sample UNIX System CPU V140 reportThe illustration shows a representative UNIX System CPU V140 report.

Sample CPU Analysis V140 ChartThe illustration shows a representative UNIX CPU Analysis V140 chart.


Navigation

Sample Solaris System CPU Workload Summary ReportThe illustration shows a representative UNIX Solaris System CPU Workload Summary Report.

Navigation


From the UNIX System CPU reportFrom the UNIX System CPU report, you can either right-click on a row of the report or double-click on the row to display the Solaris System CPU Workload report.

Sample Solaris System CPU Workload reportThe illustration shows a representative Solaris System CPU Workload Report.


A Typical Scenario

A Typical Scenario

Viewing the performance of a system CPUIs the processor spending time in User State, System State, or is it waiting on I/O to complete? The percentages provided allow your system administrator to evaluate your system. If the system is spending too much time in any one state, the system administrator will probably ask what processes are running, and why the system is spending too much time in User, System, Idle, or Wait I/O state. The natural navigation path for the system administrator is to view the UNIX System CPU report, followed by the UNIX Process report.

For example, the Idle Percentage is small (or zero), and the User Percentage is large (greater than 30%) then the system may be in a loop or in a compute-bound mode. Your system administrator can create two situations.

The first situation could monitor Idle Percentage and User Percentage. If the Idle Percentage is less than 5% and the User Percentage is greater than 30%; this is a yellow condition. Check with the system administrator for exact values to be used. But this still leaves the question "Which process is spending too much time in User mode?"

The second situation could monitor UNIX processes. A large value (machine dependent) in the Process CPU Utilization column indicates the process is spending a great deal of time in User mode and may be in a loop. If the value is larger than 100, notify your system administrator.

Inside the System CPU Report



OverviewThe UNIX System CPU report, Version 140, has been modified to select data from the new SMP_CPU attribute group rather than the UNIX_System attribute group. Three new columns have been added to the report. Theses are:

� CPU ID

� CPU Busy

� CPU Status

The report now contains eight columns. Monitored data for each managed system appears in rows in each column. You can use any data appearing in a report to create a situation that monitors system conditions for a threshold value.

For a single processor system, the UNIX System CPU report displays a single row of CPU data.

For multi-processor systems, the UNIX System CPU report displays N+1 rows of CPU data, where N is the number of processors in the system. The first row always contains aggregate attributes value. The subsequent rows contains per processor attributes value, one per each processor.

Reminder about sorting and filtering columnsYou can sort or filter information in the columns of the UNIX System CPU report to modify the way in which you view system status information.





Column heads and their descriptionsThe table contains descriptions of each column in the UNIX System CPU report and their definitions. Column information is listed alphabetically.

Table 26. UNIX System CPU Report Columns

Column Description

CPU Busy The sum of the System and User CPU time in percent. (Not applicable to V120.)

CPU ID The processor ID. (Not applicable to V120.)

CPU Status Displays the status of the CPU. Possible values are:

off-line 0

on-line 1

(Not applicable to V120.)

Idle CPU Displays the percentage of time the CPU is not processing instructions. The Idle CPU value should be low if the system load is heavy, and high if the system load is light. If the system load is heavy and the Idle CPU value is high, an I/O problem may exist.

System CPU Displays the percentage of CPU time devoted to executing UNIX system kernel code. System CPU time includes time spent executing system calls and performing administrative functions.



User CPU Displays the percentage of CPU time devoted to user processes

User CPU time includes time spent executing both user programs and library functions. It does not include CPU time spent executing system calls. The ratio between user and system CPU time varies, depending on the kinds of programs executing. If user CPU is extremely high and is affecting system performance, you may want to determine which user programs are preventing the CPU from functioning at its normal rate.



Wait I/O Displays the percentage of time that the CPU spends waiting for I/O operations. Wait I/O indicates how efficiently the system is using disks. If the Wait I/O value is chronically high, you may have a disk throughput problem.

This value is not available for all UNIX systems.


Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example



Table 26. UNIX System CPU Report Columns (continued)

Column Description


Inside the Solaris System CPU Workload Summary Report


OverviewThe Solaris System CPU Workload Summary report is a new report for OMEGAMON XE for UNIX, Version 140. This report is for Solaris 2.5 and 2.6 systems only.

The report contains 14 columns. Monitored data for each managed system appears in rows in each column. You can use any data appearing in a report to create a situation that monitors system conditions for a threshold value.



Column heads and their descriptions.The table contains descriptions of each column in the UNIX Solaris System CPU Workload Summary report and their definitions. Column information is listed alphabetically.

Table 27. UNIX Solaris System CPU Workload Summary Report

Column Headings Description

Context Switches CPU context switches rate per second over the sampling interval.

CPU ID Processor identification number.


off-line 0

on-line 1

Cross Calls Inter-processor cross-calls rate per second over the sampling interval.



Interrupt as Threads Interrupts as thread (not counting interrupts) rate per second over the sampling interval.

Interrupts Interrupts rate per second over the sampling interval.


Involuntary context switches rate per second over the sampling interval.

Major Faults Major faults rate per second over the sampling interval.

Minor Faults Minor faults rate per second over the sampling interval.

Spins on Mutexes Spins on mutexes (locks not acquired on try) rate per second over the sampling interval.

Spins on RW Locks Spins on reader/writer locks (locks not acquired on first try) rate per second over the sampling interval.

System Calls System calls rate per second over the sampling interval.


Thread Migrations Thread migrations to anther processor rate per second over the sampling interval.

Timestamp The date and time of the last update to the information collected by the UNIX remote agents

Table 27. UNIX Solaris System CPU Workload Summary Report (continued)





Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example



Table 27. UNIX Solaris System CPU Workload Summary Report (continued)


Inside the Solaris System CPU Workload Report



OverviewThe Solaris System CPU Workload report is a new report for OMEGAMON XE for UNIX, Version 140. This report is for Solaris 2.5 and above systems only.

The report now contains eight columns. Monitored data for each managed system appears in rows in each column. You can use any data appearing in a report to create a situation that monitors system conditions for a threshold value.



Column heads and their descriptions.The table contains descriptions of each column in the UNIX Solaris System CPU Workload Summary report and their definitions. Column information is listed alphabetically.

Table 28. UNIX Solaris System CPU Workload Report


Context Switches CPU context switches rate per second over the sampling interval.

CPU ID Processor identification number.


off-line 0

on-line 1

Cross Calls Inter-processor cross-calls rate per second over the sampling interval.



Interrupt as Threads Interrupts as thread (not counting interrupts) rate per second over the sampling interval.

Interrupts Interrupts rate per second over the sampling interval.


Involuntary context switches rate per second over the sampling interval.

Major Faults Major faults rate per second over the sampling interval.

Minor Faults Minor faults rate per second over the sampling interval.

Spins on Mutexes Spins on mutexes (locks not acquired on try) rate per second over the sampling interval.

Spins on RW Locks Spins on reader/writer locks (locks not acquired on first try) rate per second over the sampling interval.

System Calls System calls rate per second over the sampling interval.

Thread Migrations Thread migrations to anther processor rate per second over the sampling interval.

Timestamp The date and time of the last update to the information collected by the UNIX remote agents

Table 28. UNIX Solaris System CPU Workload Report (continued)





Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example



Table 28. UNIX Solaris System CPU Workload Report (continued)


System Groups Report 187

System Groups Report

IntroductionThis chapter provides information about how the UNIX System Groups report helps you get an overview of the conditions occurring on your UNIX systems.

The UNIX System Groups Report helps you monitor the performance of your distributed UNIX systems from a single display screen.

Chapter ContentsHow the UNIX System Groups Report Helps You . . . . . . . . . . . . . . . . . . . . . 188A Typical Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190Inside the UNIX System Summary Report . . . . . . . . . . . . . . . . . . . . . . . 191

13

How the UNIX System Groups Report Helps You



OverviewUse the UNIX System Groups report to get a summary overview of distributed UNIX systems defined in a managed system list. From the UNIX System Summary report you can open other detailed reports for a selected managed system.

If you are experiencing problems on one or more systems, use this report to help pinpoint the problem.

Sample UNIX System Groups reportThe illustration is an example of the UNIX System Groups report on a Windows NT CMW.



Using the UNIX System Groups Chart ViewThe UNIX System Groups report has no chart view.

Procedure for accessing the UNIX System Groups reportUse the procedure to access the UNIX System Groups report.

1. Double-click the UNIX System Groups icon in the Reports window. The Managed UNIX System Groups selection view appears.

2. Double-click the managed system list for which you want information.Result: The UNIX System Summary report appears.

A Typical Scenario


A Typical Scenario

OverviewThe UNIX System Summary report contains a summary overview of all the nodes defined in a selected managed system list.

The System Summary report allows you to open any other UNIX report for a managed system list member when a problem arises or when a situation triggers an event.

Accessing additional reports from the UNIX System Summary reportUse the procedure to access additional reports from the UNIX System Summary report.

1. Double-click the UNIX System Groups icon in the Reports window. The Managed UNIX System Groups selection view appears.

2. Click on the managed system for which you want another report.

3. Right-click and select a report from the pop-up menu.Result: The selected report for the managed system opens.


Inside the UNIX System Summary Report


OverviewThe UNIX System Summary report contains eleven columns; each column has the name of an attribute as its heading. An attribute is a system element, for example, System CPU, you monitor using a situation. Because of screen width limitations, you need to scroll to the right to view all table columns.

The values for data in a UNIX System Summary Report may be up to 3 minutes old due to the collection interval for the agent. You can use any data appearing in a report as a threshold value in the creation of a situation.

Reminder about sorting and filtering columnsYou can sort or filter information in the columns of the System Groups report to modify the way in which you view information.





Column heads and their descriptionsThe table contains descriptions of each column heading in the UNIX System Summary report. The column headings are listed alphabetically.

Table 29. UNIX System Summary Report Columns

Column Description

Idle CPU (Percent) Displays the percentage of time the CPU is not processing instructions. The Idle CPU value should be low if the system load is heavy, and high if the system load is light. If the system load is heavy and the Idle CPU is high, an I/O problem may exist.

Free Memory (KBytes) Displays the amount of memory, in kilobytes, not being used on the monitored system

Load Average (1 Min.) Displays the average number of processes in the UNIX kernel run queue during the last minute. Acceptable values for load average vary according to your system. Values less than 2 are usually considered normal. Values greater than 2 may indicate increasing degrees of problem severity.

Load Average (5 Min.) Displays the average number of processes in the UNIX kernel run queue during the last five minutes. Acceptable values for load average vary according to your system. Values less than 2 are usually considered normal. Values greater than 2 may indicate increasing degrees of problem severity.

System Name Identifies the name of the system for which you are viewing information.

System CPU (Percent) Displays the percentage of CPU time devoted to executing UNIX system kernel code. System CPU time includes time spent executing system calls and performing administrative functions.


Total Real Memory (KBytes)

Displays the total amount of kilobytes of physical memory on the monitored system.




Displays the total amount of disk space (in kilobytes) available for paging operations on the monitored system

User CPU (Percent) Displays the percentage of CPU time devoted to user processes.

User CPU time includes time spent executing both user programs and library functions. It does not include CPU time spent executing system calls.

The ratio between user and system CPU time varies, depending on the kinds of programs executing. If user CPU is extremely high and adversely affecting system performance, you may want to determine which user programs are preventing the CPU from functioning at its normal speed.

Wait I/O (Percent) Displays the percentage of time that the CPU spends waiting for I/O operations. Wait I/O indicates how efficiently the system is using disks. If the Wait I/O value is chronically high, you may have a disk throughput problem.

This value is not available on all UNIX systems.

Table 29. UNIX System Summary Report Columns (continued)

Column Description



System Load Average Report 195

System Load Average Report

IntroductionThis chapter describes the UNIX System Load Average report, which provides information about the load on a UNIX system and gives an indication of system activity.

Chapter ContentsHow the UNIX System Load Average Report Helps You . . . . . . . . . . . . 196A Typical Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Inside the UNIX System Load Average Report . . . . . . . . . . . . . . . . . . . . 199

14

How the UNIX System Load Average Report Helps You



OverviewLoad Average is defined as the number of processes that could be running (executing) but are waiting because another process is using the CPU. The UNIX System Load Average provides an overall picture of system activity for your monitored UNIX systems. It is one of the first reports you should examine if system response is poor.

The one-minute average tells you how busy the system was during the last minute. The five-minute and 15-minute averages help provide a trend.

You can use the UNIX System Load Average report to:

� Optimize system performance by providing information you need to evaluate the overall load on your system.

� Forecast future needs of your network by supplying data that helps you determine whether the load increases or decreases over a specified fifteen-minute time period. You can then chart when these load fluctuations occur, and analyze the charts to see if the fluctuations occur at certain times throughout the workday. If they do, your system administrator can plan for these fluctuations and tune the system accordingly.


Monitoring system load average dataUse the UNIX System Load Average report to check the overall load on your system, and determine whether the load is increasing or decreasing within a fifteen minute time period. If the load average is high and not improving, use the UNIX Process Report to track down the jobs and users responsible for the load.



Sample UNIX System Load Average ReportThe illustration shows a representative UNIX System Load Average report.

Using the Chart ViewThe System Load Average report has no chart view.

A Typical Scenario


A Typical Scenario

Monitoring load average dataSuppose users are calling you with complaints that the system is really slow, and print jobs are

taking a long time to process. You decide to investigate by selecting the UNIX System Load Average report.

If the load average is greater than 3 during the last minute, you should consider this a critical condition. Check with your system administrator for exact values to use.

A load average of 3 for the last minute is one indicator of a busy system. If the value of this attribute continues to climb, you should notify your system administrator. The OMEGAMON XE for UNIX also provide 5 minute and 15 minute load average attributes, which you can use to give an indication of short-term trends.


Inside the UNIX System Load Average Report


OverviewThe UNIX System Load Average report contains five columns. Load average data for a managed system appears in the rows displayed. Any column appearing in a report can be used to create a situation that monitors system conditions for a threshold value.

ReminderYou can sort and filter information in the columns of the UNIX System Load Average report to modify the way you view system load data.




Row titles and their descriptionsThe table contains descriptions of each row title in the UNIX System Load Average report. The row titles are listed alphabetically.

Table 30. UNIX System Load Average Report Row Titles

Row Title DescriptionBoot Time The system boot time. Version 140 only.Load Average (1 Min) This column displays the average number of processes in

the UNIX kernel run queue during the last minute. Acceptable values for load average vary according to your system. Values less than 1 are generally considered normal. Values greater than 1 may indicate increasing degrees of problem severity. If the 1-minute Load Average value is high, compare it to the 5- and 15- minute values. If the load average values are increasing with time, you may want to take corrective action. If the values are falling, you may want to delay action and see if the problem corrects itself.

Load Average (5 Min) This column displays the average number of processes in the UNIX kernel run queue during the last five minutes. Acceptable values for load average vary according to your system. Values less than 2 are generally considered normal. Values greater than 2 may indicate increasing degrees of problem severity. If the 5-minute Load Average value is high, compare it to the 1 and 15 minute values. If the load average values are increasing with time, you may want to take corrective action.

Load Average (15 Min) This column displays the average number of processes in the UNIX kernel run queue during the last 15 minutes. Acceptable values for load average vary according to your system.

System Name The name of the system.Timestamp Displays the date and time of the last update to the

information collected by UNIX remote agents.Up Time Displays the system up time in the format

DDDd:HH:MM:SS. Version 140 only.

For V120 agents, the number of seconds that the system has been running since boot time.




Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example



Table 30. UNIX System Load Average Report Row Titles (continued)




User Reports 203

User Reports

IntroductionThis chapter introduces you to the UNIX User reports, which contains detailed information that helps you identify terminals and find time data on each user logged onto your monitored UNIX systems.

Chapter ContentsHow the UNIX User Reports Help You . . . . . . . . . . . . . . . . . . . . . . . . . . 204A Typical Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206Inside the UNIX Users Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Inside the UNIX User Process Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

15

How the UNIX User Reports Help You



OverviewBy viewing the monitored user data collected by OMEGAMON XE for UNIX on remote systems, you can:

� Troubleshoot problems and solve them quickly using reliable, real-time information about users and the programs they use.

� Use this information to pinpoint problem processes, and the user(s) responsible for them. Your system administrator can then eliminate the process, contact the user responsible for the problem, and take corrective action.


Monitoring user dataYou can use this report to obtain information on individual users and the processes they use, and check for problems caused by user activity.

How to monitor an individual userUse the procedure to monitor an individual user.

1. Select the row of data containing the user whose processes you want to view.

2. Activate the pop-up menu using mouse button 2.

3. Select Open as User Process from the menu.Result: A detailed report for the user you selected appears.

User Reports 205


Sample UNIX Users reportThe illustration shows a representative UNIX Users report.

Using the Chart ViewThe UNIX Users report has no chart view.

A Typical Scenario


A Typical Scenario

Monitoring user activityYou can use this report to check for problems caused by user activity. For example, a high Idle_Time value for a remote user can indicate a security problem. You may want to notify your system administrator to call the user and find out why he or she needs to stay logged on to the system.

User Reports 207

Inside the UNIX Users Report


OverviewThe UNIX Users report contains seven columns. Monitored data for logged-on user appears as rows in the report. Because of screen width limitations, you need to scroll to the right to view all seven columns. You can use any data appearing in a report as a threshold value in the creation of a situation.

Reminder about sorting and filtering columnsYou can sort or filter information in the columns of the UNIX Users report to modify the way in which you view user information.


Column heads and their descriptionsThe table contains descriptions of each column heading in the UNIX Users report. Column information is listed alphabetically.

Table 31. UNIX Users Report Columns

Column Description

Idle Time (Minutes) Displays the number of minutes that have passed since a user last entered a command. You may want to take action if the Idle Time is high for remote users, since this may not be an economical use of system resources.

Location Displays information about how to contact a user. This information may not be available for all users or for all UNIX systems.

Login Name Displays the name recognized by the system that permits a user to log into the system.

Login Time Displays the date and time that the user logged into the system.

Name Displays the full name of the user.



Terminal Displays the identification code of the physical terminal at which the user is logged in.


User ID Displays the numeric identification of the user.


Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example



Table 31. UNIX Users Report Columns (continued)

Column Description

User Reports 209

Inside the UNIX User Process Report


OverviewThe UNIX User Process report lets you check the status of all processes owned by a single user.

Use this report to determine whether problems are caused by a program or programs executed by a particular user. This may be a useful report to display anytime you suspect that the types of programs being run by a specific user have impacted system performance.

Reminder about sorting and filtering columnsYou can sort or filter information in the columns of the UNIX Users report to modify the way in which you view user information.


Column heads and their descriptionsThe table contains descriptions of each column heading in the UNIX User Process report. Column information is listed alphabetically.

Table 32. UNIX User Process Report Columns

Column Description









0 NonexistentA The process is active.I IntermediateO RunningR The process is runnable.S The process is sleeping.T The process is stopped.W WaitingX GrowingZ The process terminated, but has not completed exiting

the system (the process is in a zombie state).

Table 32. UNIX User Process Report Columns (continued)

Column Description

User Reports 211













Column Description










Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example




Column Description

Virtual Memory Report 213

Virtual Memory Report

IntroductionThis chapter introduces you to the UNIX Virtual Memory report, contains detailed information about the availability of and demand for virtual storage on your systems.

Chapter ContentsHow the UNIX Virtual Memory Report Helps You . . . . . . . . . . . . . . . 214A Typical Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Inside the UNIX Virtual Memory Report . . . . . . . . . . . . . . . . . . . . . . . . . 218

16

How the UNIX Virtual Memory Report Helps You



OverviewMemory shortages can cause system performance problems. If system performance is poor, excessive page-outs and swapping activity can indicate memory problems.

By viewing the monitored virtual memory data collected by the OMEGAMON XE for UNIX on a remote system, you can:

� Determine whether performance degradation is caused by a lack of virtual memory.

� View monitored data collected from remote systems either as a report or a chart.


Monitoring virtual memory dataThe UNIX Virtual Memory report provides detailed information on swapping and paging activity on your monitored UNIX systems. Use this report to help determine if memory shortages are causing performance degradation.



Sample UNIX Virtual Memory reportThe illustration shows a representative UNIX System Virtual Memory report.

Sample UNIX Virtual Memory ChartThe illustration shows a sample of the UNIX Virtual Memory Analysis Chart.

A Typical Scenario


A Typical Scenario

Monitoring Virtual MemoryOn UNIX systems, Active Virtual Memory closely matches how much paging space is being used. When UNIX systems use all the paging space, the operating system terminates processes asking for more space. Use the UNIX Virtual Memory Report and compute 90% and 95% of the Total Virtual Memory. When the Active Virtual Memory is equal to 90% of the Total Virtual Memory, this is a warning condition. When the Active Virtual Memory is equal to 95% of the Total Virtual Memory, this is a critical condition. Talk to your system administrator and see if the percentages should be increased or lowered.

Generally, a system should have a virtual memory pool equal to about 2 times the total physical memory size, but this varies depending on the programs being executed. If the site has a lot of small programs and they run to completion quickly, then maybe only one times the total memory size is required. Should the site execute large programs that run for hours or days at a time, then more paging space is required.


A Typical Scenario

✍Note for Solaris UNIX users

Any situations written using the System.Page_Faults attribute for OMAs for UNIX Version 120 agents must be rewritten for OMEGAMON XE for UNIX Version 200 agents.

The Version 120 OMAs for UNIX agent uses the System.Page_Faults attribute to store page scan rate. Version 200 OMEGAMON XE for UNIX added a new attribute System.Page_Scan_Rate to store page scan rate.

System.Page_Faults now stores the page fault rate. In order to have Version 120 situations the use page scan rate work correctly on Version 200, modify these situations to use System.Page_Scan_Rate.

Inside the UNIX Virtual Memory Report



OverviewThe UNIX Virtual Memory report, Version 140, contains 16 rows. Monitored data for each managed system appears in a column to the right of the row titles. You can use any attribute in the report when specifying a threshold value in the creation of a situation. The Version 120 report displays only 10 rows and is also displayed vertically.

Reminder about sorting and filtering columnsYou can sort or filter information in the rows of the UNIX Virtual Memory Report to modify the way in which you view disk inode information.


Row Titles and their descriptionsThe table contains descriptions of each column heading in the UNIX Virtual Memory report. Column information is listed alphabetically.

Table 33. UNIX Virtual Memory Report Row Titles


Active Virtual Memory (Kbytes)

The amount of system memory currently in use, in kilobytes.

Free Memory (Kbytes) The amount of system memory currently available, in kilobytes.

Page Ins (Per Sec) The average number of page-in requests per second over the sampling period. A page-in request may include multiple pages and gives an indication of the I/O rate on the paging file.(Not applicable to V120.)

Page Faults (Per Sec) The average number of page faults per second over the sampling period.

Page Outs (Per Sec) The average number of page-out requests per second over the sampling period. A page-out request may include multiple pages and gives an indication of the I/O rate on the paging file.(Not applicable to V120.)



Page Reclaims (Per Sec)

Displays the number of times (during the recording interval) that a page was taken off the queue to be written to disk and used by another process.

Page Scan Rate (Per Sec)

Displays the average number of pages examined per second during the recording interval. (Not applicable to V120.)

This field does not apply to AIX, HP-UX and Sun UNIX.

See “Note for Solaris UNIX users” on page 217.

Pages Paged In (Per Sec)

Displays the actual number of pages that were paged-in from disk to system memory during the recording interval.

A high Pages Paged-In value may or may not indicate a system problem. Page-ins may increase during normal activity, such as the start of several new jobs. When this occurs, the system pages in the executable image and data of the new jobs.

When the number of page-ins remains high instead of dropping off, the page-in value may indicate a memory shortage problem.

Pages Paged Out (Per Sec)

Displays the actual number of pages paged-out from system memory to disk, during a recording interval.

A high page-out count can indicate a shortage of memory. An occasional increase in page-out activity during times of peak demand is normal. If the number of page-outs remains high, available memory may be insufficient to handle the number and size of jobs running on the system.

Processes/Threads in Run Queue

Displays the total number of runnable processes (or threads in AIX 4.1 and above and Digital UNIX) waiting for execution by the CPU. This number does not include processes waiting for I/O or some external event, or processes in a sleeping state.

Processes/Threads Waiting

Displays the number of processes (or threads in AIX 4.1 and above and Digital UNIX) waiting for page operations.

System Name The name of the system.







The total amount of disk space, in kilobytes, available for paging operations on the monitored system.

Virtual Memory Percent Available

The percent of virtual memory available. (Not applicable to V120.)

Virtual Memory Percent Used

The percent of virtual memory used. (Not applicable to V120.)


Values


MM Month

DD Day of the week

YY Year

HH Hours

mm Minutes

SS Seconds

Example





CandleNet Portal™ Client Interface 221

CandleNet Portal™Client Interface

IntroductionThis chapter contains information about the CandleNet Portal™ client interface. This includes client workspaces that allow you to access agent activity in both report and graphic formats.

For additional information on the using the Candlenet Portal client, refer to Administering OMEGAMON Products: CandleNet Portal.

Chapter ContentsCandleNet Portal Workspaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222How Workspaces Are Organized. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223UNIX System Workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227Disk Usage Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229File Information Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232Network Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234NFS Activity Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237Process Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239RPC Performance Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241System Information Workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Users Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

17

CandleNet Portal Workspaces


CandleNet Portal Workspaces

OverviewOMEGAMON XE for UNIX for CandleNet Portal has predefined workspaces that show general system performance of servers and networks in your UNIX environment. For example, you can see information on hardware configuration, software activity, and performance statistics.

OMAs for UNIX provides more than simple "heartbeat" data. Use OMAs for UNIX to:

� monitor system and resource usage

� determine what alerts you want to set

� locate problems that may affect system availability

� integrate with other Candle products for an enterprise-wide view of multiple systems from a single CandleNet Portal console

Use OMEGAMON XE for UNIX workspaces to view, at-a-glance, general system performance of servers and networks in your UNIX environment. Monitored data includes information on hardware configuration, software activity, and performance statistics.

The table and chart views contained in your OMAs for UNIX workspaces provide a snapshot of the most recent monitored data collected by the agent. They do not automatically update while the workspace is open.

When you refresh the workspace, the views are updated with information collected during the latest monitor interval. For example, if the data is collected every 30 seconds and you open the report 2 minutes, 45 seconds after startup, the report data would show the value collected at the 2 minute, 30 second mark.


How Workspaces Are Organized


OverviewThe following list shows how the OMAs for UNIX workspaces are organized. The ➠ indicates that you can link to the workspace. For example, if you right-click on a row in the Top CPU Time Processes view and select Link To, you can link to the Application for Process view.

UNIX� UNIX Summary Workspace (default)

– Top CPU Time (bar chart)– Memory % - Top Ten (bar chart)– Disk Space Used % - Top Ten (bar chart)– Virtual Size - Top Ten (bar chart)– Virtual Memory Availability (bar chart)

� UNIX Detail Workspace– Top CPU Time - Processes (table)– Top Virtual Size (table)– Top Memory % (table)– Top Space Used % (table)– System Virtual Memory (table)

� Enterprise UNIX System Summary Workspace– UNIX System Summary Table– Memory Usage Summary (bar chart)– Load Average Summary (bar chart)– CPU % Summary (bar chart)

Disk Usage� Disk Usage Workspace

– Space Used % - Top Ten (bar chart)– Inodes Used % - Top Ten (bar chart)– Disk Utilization (table)

➠ Disk Utilization– Disk Busy %



� Disk Usage Details Workspace– Disk Utilization

➠ Disk Utilization for Mount Point– Disk Performance– Disk Inodes

File Information� File Information Workspace

– File Information Report➠ Specific File Information

� Specific File Information Workspace– File Information for

➠ Specific File Information

Network� Network Workspace

NFS Activity� NFS Activity Workspace

Process� Process Workspace

– Top CPU Time Processes➠ Child Processes➠ Processes for Group Leader➠ Application for Process➠ Command for Process➠ Resource for Process

� Process Resource Workspace� Top CPU and Memory % Usage Workspace� Child Processes Workspace� Process Group Workspace� Process Resource Workspace

– Resource for Process ID =➠ Child Processes



➠ Processes for Group Leader➠ Application for Process➠ Command for Process

– User Information for User ID =➠ User Processes

� Command Workspace


� Application Workspace


� All Processes Workspace

RPC Performance� RPC Performance Workspace

System Information� System Information Workspace

� System Details Workspace

– System CPU (table)

➠ Solaris System CPU Workload Summary Workspace

� Solaris System CPU Workload Summary Workspace



Users� Users Workspace

– Users Report➠ User Processes

� User Processes Workspace– Processes for User ID =

➠ Process Resource➠ Child Processes➠ Processes for Group Leader➠ Command for Process➠ Application for Process

� Users Report– User Processes

Attributes used by the workspacesIn most cases, a workspace contains data or columns that have the same attributes as their respective attribute group. Report or table column headings refer to the attribute found in the attribute groups.

Table 34. Attributes Used by the Workspaces

Workspace Related Attribute Group

Disk Usage Disk Information

Disk Performance

File Information File Information

Network Network

NFS Activity NFS RPC Statistics

Process Process

SMP CPU

RPC Performance NFS RPC Statistics

System Information System

Users User


UNIX System Workspaces


OverviewThe three illustrations below show the high level UNIX system workspaces.

UNIX Summary Workspace (default)



UNIX Detail Workspace

Enterprise UNIX System Summary Workspace

This workspace requires that the hub and remote CMSs are seeded with the OMAs for UNIX seed data. This workspace displays a summary of all UNIX systems on-line.


Disk Usage Workspace


OverviewThe Disk Usage workspace is comprised of four views and provides an at-a-glance snapshot of your disk condition. The views shown are:

� Space Used % - Top Ten (horizontal bar chart)

� Inodes Used % - Top Ten (horizontal bar chart)

� Disk Utilization Report

� Disk Busy % (horizontal bar chart)

Sample Disk Usage workspace



Space Used % - Top Ten

This chart provides information on the top ten subdirectories using hard drive space.

Inodes Used % - Top Ten

This chart presents a diagramtic view of the percent of inodes used by the top ten drive space components.

Disk Utilization

The Disk Utilization report helps you solve disk related problems quickly by providing information on devices with excessive I/O activity and/or long service times. New data includes average disk queue length and average number of processes waiting for service.

Disk Busy %

This graph shows monitored disk input/output (I/O) data collected by the UNIX agents. With this information you can:

Improve the performance of your UNIX system by quickly and accurately pinpointing how your system transfers data from disk to memory

Increase your efficiency by keeping you constantly informed of how the disk performs

Using the UNIX Disk Performance reportBy viewing monitored disk input/output (I/O) data collected by the UNIX agents, you can:

Improve the performance of your UNIX system by quickly and accurately pinpointing how your system transfers data from disk to memory

Increase your efficiency by keeping you constantly informed of how the disk performs



Monitoring disk performanceYou monitor the performance of disks in your system to make sure they operate smoothly. Disk performance has a major impact on the overall functioning of your UNIX system. If disk performance is poor, it affects jobs that require a large amount of disk I/O, virtual memory functioning, and the time required to run a program.

Use this report to identify disk performance problems caused by slow rates of data transfer from disk to memory, or high disk usage.

File Information Workspace



OverviewThe File Information workspace has two views

� File Size - Top Ten (horizontal bar chart)

� File Information Report

Sample File Information workspace

File Size - Top Ten

This graph allows you to quickly see at a glance the files that are consuming the largest amount of disk space.



File Information Report

The UNIX File Information report contains system information that helps you improve the performance of your system and obtain detailed information such as file path, file attributes, and time data about a specific file.

Using the UNIX File Information reportThis report displays directories and files. When you first open the report, it displays the files and directories in the root directory. By viewing the file information on monitored file systems collected by OMEGAMON XE for UNIX on remote systems, you can:

Find information about files fast by quickly pinpointing specific information you need

Increase system productivity by allowing the system administrator to change how files are used, based on the needs of system users

A typical scenarioSuppose you want to track the size of a particular file that may be taking up too much disk space. You can set a situation to notify the system administrator when a file grows beyond a certain size. You could then use the UNIX Disk Utilization report to determine how much space is left on the disk.

Network Workspace


Network Workspace

OverviewThe Network workspace has three views:

� Errors and Collisions (horizontal bar chart)

� Frames Transfer Data (horizontal bar chart)

� Network Information Report

Sample Network workspace

Errors and Collisions

The bar chart displays network input errors, output errors, and collisions allowing you a quick glance at potentially severe network problems.


Network Workspace

Frames Transfer Data

The Frames Transfer chart displays graphically the frames received and frames transmitted on each network card.

Network Information Report

The Network Info report contains monitored data that helps you see your overall network performance, and supplies you with information about network interfaces on your monitored UNIX systems.

Using this real time network information, you can:

� Fine-tune your network by allowing you to pinpoint bottlenecks in network traffic so your system administrator can reroute jobs to avoid them

� Increase system productivity by providing you with the information that lets you determine how network resources can be used more efficiently

The UNIX Network report contains numerical attributes that report the changing interface workload throughout each workday. This information allows your system administrator to see the ebb and flow of network traffic.

Frames vs. packetsThe Received Count (Frames) and Transmitted Count (Frames) show the raw frame counts for the interface. Frames and packets are not necessarily the same thing.

System administrators may define the interface so that multiple frames are sent or received in a packet. The network report and the network attributes display frame counts.

Using the UNIX Network reportThe UNIX Network report helps you:

� See how much data your network interfaces transmit and receive� Identify network interfaces� Determine whether the interfaces are operational� View the amount of data traffic that flows through interfaces� Justify rerouting network data traffic, if necessary� Measure errors in frame transmission and collisions

Network Workspace


Viewing the performance of your networkSuppose users are complaining that they are having trouble accessing an Ethernet network that connects to other networks in your system. Use the UNIX Network report to view the gateway or router that connects to Ethernet in question. By viewing data received and transmitted through this gateway or router, you can determine if it is working properly.

If the router is overloaded, you may want to view other routers or gateways to see which ones are available, and re-route data traffic to one with a lighter workload.

You can also view the UNIX Network report to view information about collisions on a particular network interface. If the number of collisions is high, this may indicate that the capacity of the network hardware has been reached.


NFS Activity Workspace


OverviewThis workspace is comprised of four views. The views are:

� NFS Server Statistics (vertical bar chart)� NFS Client Statistics (vertical bar chart)� NFS Server Activity Report� NFS Client Activity Report

Sample NFS Activity workspace



NFS Server Statistics

The NFS Server Statistics chart graphically displays the activity for the following attributes:

� NFS Server Calls� NFS Server Calls Rejected� NFS Server Null Calls� NFS Server lookups

NFS Client Statistics

The NFS Client Statistics chart graphically displays the activity for the following attributes:

� NFS Client Calls� NFS Client Calls Rejected� NFS Client Null Calls� NFS Client lookups

NFS Server Activity Report

NFS Server Activity attributes report on NFS calls to the managed system. The agent reports these calls only when the managed system is an NFS server.

NFS Client Activity Report

NFS Client Activity attributes report on calls from the managed system to NFS servers.

NFS RPC Statistics group is a single-instance attribute group. You can mix these attributes with those of any other single-instance group.


Process Workspace

Process Workspace

OverviewThe Process workspace is comprised of four views. The views are:

� Top CPU Time (horizontal bar chart)� Memory % - Top Ten (horizontal bar chart)� Top CPU Time Processes Report� Virtual Size - Top Ten (horizontal bar chart)

Sample Process workspace

Top CPU Time

This chart displays CPU Percent for the processes utilizing the highest CPU time.

Process Workspace


Memory % - Top Ten

This chart displays graphically the Memory Percent attribute for the top ten processes utilizing memory.

Virtual Size - Top Ten

The Top Virtual Memory graph provides information about virtual memory process usage by the top ten processes.

Top CPU Time Processes

The Top CPU Process report provides detailed information about the top CPU processes currently running. You can view this information in the detail report columns.

The Top CPU Process report helps you:

� Solve process problems quickly by giving you information you need to pinpoint problem processes and their owners.

� Improve system performance by providing you with real-time information on which users and what processes are using the system.

Monitoring process informationWhen monitoring process information, pay special attention to the following attribute values.

Large values in the CPU Utilization column indicate a CPU-intensive process. These result in a lower process priority. Small values indicate an I/O intensive process. These result in a higher process priority.

A value greater than 100 indicates a process is consuming a large amount of the CPU. If this value is high, check the Execution State column to see if the process is running, and the Time column to see how long the process has been running.

Variable value for CPU utilizationThe CPU Utilization value is machine-dependent and also varies according to the version of the UNIX operating system running.


RPC Performance Workspace


OverviewThe RPC Performance workspace is comprised of four views. The views represented are:

� RPC Server Statistics (vertical bar chart)� RPC Client Statistics (vertical bar chart)� RPC Server Performance Report� RPC Client Performance Report

Sample RPC Performance workspace



RPC Server Statistics

This chart graphically displays the following attributes:

� RPC Client Calls Rejected by Server� RPC Server Times RPC Packet Unavailable� RPC Server Packets Too Short� RPC Server Packets with Malformed Header

RPC Client Statistics

This chart graphically displays the following attributes:

� RPC Client Calls Rejected by Server� RPC Client Calls Retransmitted� RPC Client Replies Not Matching Calls� RPC Client Calls Timed Out

RPC Server Performance Report

This table contains statistics attributes that refer to Remote Procedure Call (RPC) Server call rates and errors.

The RPC Server attributes report on RPC calls made to the managed system.

RPC Client Performance Report

This table contains statistics attributes that refer to Remote Procedure Call (RPC) Client call rates and errors.

The RPC Client attributes report on calls made by the managed system to RPC Servers.


System Information Workspaces


OverviewThe System Information Group has 3 workspaces that can be displayed. The three workspaces are:

� System Information workspace� System Details workspace� Solaris System CPU Workload Summary workspace

Sample System Information workspaceThe System Information workspace is comprised of five chart views. These charts are

� Virtual Memory Availability (pie chart)� Page Fault Statistics (vertical bar chart)� Total Real and Virtual Memory (vertical bar chart)� CPU % (pie chart)� Load Averages (vertical bar chart)



Virtual Memory Availability

This chart displays the following attributes:

� Virtual Memory Percent Used

� Virtual Memory Percent Available

Memory shortages can cause system performance problems. If system performance is poor, excessive page-outs and swapping activity can indicate memory problems. By viewing the monitored virtual memory data collected by OMA for UNIX on a remote system, you can:

� determine whether performance degradation is caused by a lack of virtual memory.

� view monitored data collected from remote systems either as a report or a chart.

Page Fault Statistics

This chart displays page fault attributes to provide an at-a-glance view of problems with virtual memory faults. The attributes displayed are:

� Page Faults� Page Scan Rate� Page Reclaims� Pages Paged In� Pages Paged Out� Page Ins� Page Outs

Total Real and Virtual Memory

The Total Real and Virtual memory chart graphically displays vital information about system memory. The attributes displayed are:

� Total Real Memory

� Free Memory

� Total Virtual Memory



The System chart gives you operating system and memory information on your UNIX systems. By viewing the monitored system data collected by OMA for UNIX on remote systems, you can:

� Improve system performance by helping you identify the configuration of your systems and check their current activity levels

� View monitored data collected from remote systems either as a report or as a chart.

CPU %

The CPU % pie chart helps you improve system CPU performance by using it to identify and monitor system CPU activity. The CPU % chart displays percentages of processor activity taking place on each monitored UNIX system. Use this chart to check for problems such as:

� improve system CPU performance by helping you identify managed systems that consume large amounts of CPU time

� increase system throughput by identifying user demands on CPUs, allowing you to allocate these demands among several CPUs on your system

� identify managed systems with I/O bottlenecks caused by waits for CPU time

� identify managed systems with CPU bottlenecks caused by high CPU utilization

Load Averages

The Load Average chart gives you load average information on your UNIX systems. Load average refers to the average number of processes in the UNIX kernel run queue during an interval. By viewing the monitored system data collected by OMA for UNIX on remote systems, you can improve system performance by helping you identify the configuration of your systems and check their current activity levels.



Sample System Details workspace

The System Details workspace is comprised of multiple tables that provide detailed information about system statistics. The tables available are:

� System CPU

– This table links to the Solaris System CPU Workload Summary workspace by selecting a row and right-clicking.

� System Virtual Memory

� System (memory information)

� System Load Average

� System Workload

� System Cache and Buffers



Sample Solaris System CPU Workload Summary workspaceThe Solaris System CPU Workload Summary workspace is applicable only to Solaris systems. This workspace is comprised of the Solaris System CPU Workload Summary table and a Take Action view as illustrated below.

Monitoring system informationUse the System Information workspaces to check for problems, such as:

� managed systems with high CPU utilization� imbalances between user and system CPU demands� long CPU waits caused by I/O bottlenecks

Users Workspace


Users Workspace

OverviewThe Users workspace is comprised of three views. The views are:

� Users Report

� Take Action

� User Processes – Right click the user's row in the User's Report to see the processes started by a user.

Sample Users workspace


Users Workspace

Users Report

The Users Report attributes refer to user characteristics such as idle time, user name, location, and login time. By viewing the monitored user data collected by OMA for UNIX on remote systems, you can:

Troubleshoot problems and solve them quickly using reliable, real-time information about users and the programs they use.

Use this information to pinpoint problem processes, and the user(s) responsible for them. Your system administrator can then eliminate the process, contact the user responsible for the problem, and take corrective action.

Take Action

Use the Take Action view to perform a selected action on select system destinations.

User Processes Report

The User Processes report displays information about the processes started/owned by the user selected in the User report.

Monitoring user dataYou can use this report to obtain information on individual users and the processes they use, and check for problems caused by user activity.

Users Workspace


Guide to Candle Customer Support 251

Guide to CandleCustomer Support

IntroductionCandle Corporation is committed to producing top-quality software products and services. To assist you with making effective use of our products in your business environment, Candle is also committed to providing easy-to-use, responsive customer support.

Precision, speed, availability, predictability—these terms describe our products and Customer Support services.

Included in this Guide to Candle Customer Support is information about the following:

Base Maintenance Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252– Telephone Support– eSupport– Description of Severity Levels– Service-level objectives– Recording and monitoring calls for quality purposes– Customer Support Escalations– Above and Beyond

Enhanced Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256– Assigned Support Center Representative (ASCR)– Maintenance Assessment Services (MAS)– Multi-Services Manager (MSM)

Customer Support Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . 258– Link to Worldwide Support Telephone and E-mail information

A

Base Maintenance Plan



OverviewCandle offers a comprehensive Base Maintenance Plan to ensure that you realize the greatest value possible from your Candle software investments. We have more than 200 technicians providing support worldwide, committed to being responsive and to providing expedient resolutions to support requests. Technicians are available worldwide at all times during the local business day. In the event of an after-hours or weekend emergency, our computerized call management and forwarding system will ensure that a technician responds to Severity One situations within one hour. For customers outside of North America, after-hours and weekend support is provided in English language only by Candle Customer Support technicians located in the United States.

Telephone supportCandle provides consistently reliable levels of service—thanks to our worldwide support network of dedicated experts trained for specific products and operating systems. You will always work with a professional who truly understands your problem.

We use an online interactive problem management system to log and track all customer-reported support requests. We give your support request immediate attention by routing the issue to the appropriate technical resource, regardless of geographic location.

Level 0 Support is where your call to Candle Customer Support is first handled. Your support request is recorded in our problem management system, then transferred to the appropriate Level 1 support team. We provide Level 0 manual interaction with our customers because we support more than 170 products. We feel our customers would prefer personal interaction to a complex VRU or IVR selection menu.

Level 1 Support is the service provided for initial support requests. Our Level 1 team offers problem determination assistance, problem analysis, problem resolutions, installation assistance, and preventative and corrective service information. They also provide product usage assistance.



Level 2 Support is engaged if Level 1 cannot provide a resolution to your problem. Our Level 2 technicians are equipped to analyze and reproduce errors or to determine that an error is not reproducible. Problems that cannot be resolved by Level 2 are escalated to Candle’s Level 3 R&D support team.

Level 3 Support is engaged if a problem is identified in Candle product code. At Level 3, efforts are made to provide error correction, circumvention or notification that a correction or circumvention is not available. Level 3 support provides available maintenance modifications and maintenance delivery to correct appropriate documentation or product code errors.

eSupportIn order to facilitate the support process, Candle also provides eSupport, an electronic full-service information and customer support facility, via the World Wide Web at www.candle.com/support/. eSupport allows you to open a new service request and update existing service requests, as well as update information in your customer profile. New and updated service requests are queued to a support technician for immediate action. And we can respond to your request electronically or by telephone—it is your choice.

eSupport also contains a continually expanding knowledge base that customers can tap into at any time for self-service access to product and maintenance information.

The Candle Web Site and eSupport can be accessed 24 hours a day, 7 days a week by using your authorized Candle user ID and password.

Description of Candle severity levelsResponses to customer-reported product issues and usage questions are prioritized within Candle according to Severity Code assignment. Customers set their own Severity Levels when contacting a support center. This ensures that we respond according to your individual business requirements.

Severity 1 Crisis

A crisis affects your ability to conduct business, and no procedural workaround exists. The system or application may be down.

Severity 2High

A high-impact problem indicates significant business effect to you. The program is usable but severely limited.

http://www.candle.com/support/



Candle has established the following service-level objectives:

Severity 3Moderate

A moderate-impact problem involves partial, non-critical functionality loss or a reasonable workaround to the problem. A “fix” may be provided in a future release.

Severity 4Low

A low-impact problem is a “how-to” or an advisory question.

Severity 5Enhancement Request

This is a request for software or documentation enhancement. Our business units review all requests for possible incorporation into a future release of the product.

Call Status Severity 1 Goal

Severity 2 Goal

Severity 3 Goal

Severity 4 Goal

Severity 5Goal

First Call Time to Answer

90% within one minute

Level 1 Response(Normal Business Hours)

90% within 5 minutes

90% within one hour

Level 2 Response

(Normal Business Hours)

Warm Transfer

90% within two hours

90% within eight hours

Scheduled follow-up (status update)

Hourly or as agreed

Daily or as agreed

Weekly or as agreed Notification is made when an enhancement is incorporated into a generally available product.

Notification is made when a fix is incorporated into a generally available product.

The above information is for guideline purposes only. Candle does not guarantee or warrant the above service levels. This information is valid as of October 1999 and is subject to change without prior notice.



Recording and Monitoring Calls for Quality PurposesCandle is committed to customer satisfaction. To ensure that our customers receive high levels of service, quality and professionalism, we'll monitor and possibly record incoming and outgoing Customer Support calls. The information gleaned from these calls will help us serve you better. If you prefer that your telephone call with Candle Customer Support in North America not be monitored or recorded, please advise the representative when you call us at (800) 328-1811 or (310) 535-3636.

Customer Support EscalationsCandle Customer Support is committed to achieving high satisfaction ratings from our customers. However, we realize that you may occasionally have support issues that need to be escalated to Candle management. In those instances, we offer the following simple escalation procedure:

If you experience dissatisfaction with Candle Customer Support at any time, please escalate your concern by calling the Candle support location closest to you. Ask to speak to a Customer Support manager. During standard business hours, a Customer Support manager will be available to talk with you or will return your call. If you elect to hold for a manager, you will be connected with someone as soon as possible. If you wish a return call, please tell the Candle representative coordinating your call when you will be available. After contacting you, the Customer Support manager will develop an action plan to resolve your issue. All escalations or complaints received about support issues are logged and tracked to ensure responsiveness and closure.

Above and BeyondWhat differentiates Candle's support services from our competitors? We go the extra mile by offering the following as part of our Base Maintenance Plan:

� Unlimited multi-language defect, installation and operations support� eSupport using the World Wide Web� Regularly scheduled product updates and maintenance provided at no

additional charge� Over 200 specialized technicians providing expert support for your

Candle products

Enhanced Support Services



OverviewOur Base Maintenance Plan provides a high level of software support in a packaged offering. However, in addition to this plan, we have additional fee-based support services to meet unique customer needs.

The following are some examples of our added-value support services:

� Assigned Support Center Representative Services (ASCR)

– An assigned focal point for managing support escalation needs– Proactive notification of available software fixes– Proactive notification of product version updates– Weekly conference calls with your ASCR to review active problem

records– Monthly performance reviews of Candle Customer Support service

levels– Optional on-site visits (extra charges may apply)

� Maintenance Assessment Service (MAS)

– On-site assessment services– Advice about product maintenance and implementation– Training your staff to develop efficient and focused procedures to

reduce overall cost of ownership of your Candle software products– Analysis of your Candle product environment: versions, updates,

code correction history, incident history and product configurations– Reviews to ensure that purchased Candle products and solutions are

used effectively

� Multi-Services Manager (MSM)

Multi-Services Manager provides highly valued services to customers requiring on-site full time expertise to complement their technical resources.

– Dedicated on-site Candle resource (6 months or one year) at your site to help ensure maximum use and effectiveness of your Candle products



– Liaison for all Candle product support activities, coordination and assistance with implementation of all product updates and maintenance releases

– Works with your staff to understand business needs and systems requirements

– Possesses technical and systems management skills to enhance your staff’s knowledge and expertise

– Other projects as defined in Statement of Work for MSM services

Customer Support Contact Information


Customer Support Contact Information

Link to Worldwide Support Telephone and E-mail informationTo contact Customer Support, the current list of telephone numbers and e-mail addresses can be found on the Candle Web site, www.candle.com/support/.

Select Support Contacts from the list on the left of the page.

http://www.candle.com/support/

Index 259

Index

AAccess 77

additional information 79accessing reports 39

how to 40Active Virtual Memory 218Adobe portable document format 15advanced monitoring facilities 24ASCR

assigned support center representative 256

assigned support center representativeASCR 256

assignment of the -2 value 41assignment of the N/A (-1) value 41Average Queue 62Average Service Time 62Average Wait 62

BBlock Reads 160Block Writes 160Boot Time 162, 200BSD sorting

Priority column 111, 116, 121, 126, 131, 211

Busy Percent 62

CCalls 93, 96Calls Rejected 93, 96, 145Calls Rejected by Server 147Calls Retransmitted 147Calls Timed Out 147CandleNet Portal client 221

workspaces 222CandleStartAgent script

location 111, 116, 121, 126, 131, 211change the default report setting

procedure 144chart view

how to open 43Child System Time 137Child User CPU Time 137Collisions 86Command 109, 114, 119, 124, 209Context Switches 137, 181, 184CPU Busy 179CPU Context Switches 165CPU ID 129, 179, 181, 184CPU Pct 109, 114, 119, 124, 137, 209CPU Status 179, 181, 184CPU Utilization 110, 115, 120, 125, 210CPU utilization

variable value 100Cross Calls 181, 184customer service

telephone support 252Customer Support 14customer support

base maintenance plan 252contact information 258enhanced support services 256eSupport 253severity levels 253

DDevice 165Device Interrupts 165Disk Inodes report 33

using 51Disk Name 62Disk Performance report 33Disk Utilization report 33

E


DiskUsage workspace 229Documentation Set 14

EEffective Group ID 129Effective User ID 129Elapsed Time 138eSupport

customer support 253Event Waited On 110, 115, 120, 125, 130,

210Execs Executed 165Execution State 110, 115, 120, 125, 130,

210

FFile 77File Creates 93, 96File Information report 34File Information workspace 232File System Statistics Calls 93, 96filtering report data 47Flag 111, 116, 121, 126, 130, 211

special notice to Solaris users 101Forks Executed 165Frames Received 86Frames Transmitted 86Frames vs. Packets 85Free Memory 218Free Memory (KBytes) 192Free Memory (Kilobytes) 157

GGet Attribute Calls 93, 96Group 77

HHeap Size 138

IIdle CPU 179, 192

Idle Time 207Include settings sheet 47Inodes Free 55, 70Inodes Used 55, 70Inodes Used Percent 55, 71Input Errors 86Interface DNS Name 86Interface IP Process 86Interface Status 86Interrupt as Threads 182, 185Interrupts 182, 185Involuntary Context Switches 138, 182,

185

LLast Accessed Time 77Last Changed Time 77Link Calls 93, 96Link Name 77Links 77Load Average (1 Min) 162, 200Load Average (1 Min.) 192Load Average (15 Min) 163, 200Load Average (5 Min) 163, 200Load Average (5 Min.) 192Location 207Logical Block Reads 160Logical Block Writes 160Login Name 207Login Time 207Lookups 93, 97

Mmaintenance assessment service

MAS 256Major Fault 138Major Faults 182, 185Make Directory Calls 93, 97Managed System Selection

Version 120 agents display 01.30.00 40, 171

MAS

Index 261

N

maintenance assessment service 256Maximum Transmission Unit 86Mem Pct 111, 116, 121, 126, 138, 211Minor Fault 138Minor Faults 182, 185Monitored Logs report 27monitoring process information 100Mount Point 55, 71MSM

multi-services manager 256multi-services manager

MSM 256

NName 55, 71, 207Net Address 157Network File Server (NFS) report 34Network Information report 25Network Interface Name 87Network report 34Network workspace 234NFS Activity workspace 237NFS Client Activity report view 90NFS Server Activity report view 90Nice Value 111, 116, 121, 126, 131, 211NonBlock Reads 160NonBlock Writes 160Null Calls 94, 97Number of System Processes 157Number of System Procs 165Number of User Sessions 157

OOMEGAMON XE for UNIX 22

assists you 23benefits of 22, 23, 24definition of 22features 28how it assists you 23overview 22types of infomation collected by 22

Output Errors 87Owner 77

PPackets Too Short 145Packets With Malformed Header 145Page Faults 218Page Faults/Scan Rate 219Page Ins 218Page Outs 218Page Reclaims 219Pages Paged In 219Pages Paged Out 219Parent Process ID 111, 116, 121, 126, 131,

135, 211Path 78Percent Busy

information about 61printing problems 15Priority 111, 116, 121, 126, 131, 211

changing sort preference on Solaris 111, 116, 121, 126, 131, 211

Process Application reportCPU ID 129Effective Group ID 129Effective User ID 129Event Waited On 130Execution State 130Flag 130Nice Value 131Parent Process ID 131Priority 131Process Group Leader ID 131Process ID 131Real Group ID 131row descriptions 129Scheduling Class Name 131Session ID 132StartTime 132System Name 132Terminal Device 132Thread Count 132

R


Timestamp 132User ID 132User Name 132

Process Command 135Process Command report

Parent Process ID 135Process Command 135Process ID 135row descriptions 135StartTime 135System Name 135User ID 135

Process Group Leader ID 131Process ID 112, 117, 122, 127, 131, 135,

138, 211Process report 34Process Resource report

Child System Time 137Child User CPU Time 137Context Switches 137CPU Pct 137Elapsed Time 138Heap Size 138Involuntary Context Switches 138Major Fault 138Mem Pct 138Minor Fault 138Process ID 138row descriptions 137Size 138Stack Size 138StartTime 138System CPU Time 138System Name 138Total Child CPU Time 138Total CPU Percent 138Total CPU Time 138User CPU Time 138User ID 138Virtual Size 138Wait CPU Time 138Wait Lock Time 138

Process workspace 239Processes Idle 165Processes Runnable 165Processes Running 166Processes Sleeping 166Processes Stopped 166Processes Zombie 166Processes/Threads in Run Queue 219Processes/Threads Waiting 219product-provided situations

additional information about 28UNIX_CPU_Critical 28UNIX_Disk_Availability 28UNIX_Network_Collisions 28UNIX_Runaway_Process 28UNIX_System_Capacity_Critical 28using for turn-key performance 28

product-provided solutions 28definition of 28

product-provided templates 29

RRead Calls 94, 97Read Directory Calls 94, 97Read Link Calls 94, 97Read/Write 138Real Group ID 131Received Count (Frames) 87Rejected Call Percentage 94Rejected Calls Percentage 97Remote Procedure Call (RPC) report 35Remove Directory Calls 94, 97Remove File Calls 94, 97Rename File Calls 94, 97Replies Not Matching Calls 147reports

accessing 39choosing columns 44descriptions 32Disk Inodes 26, 33, 49Disk Performance 26, 33Disk Utilization 26, 33

Index 263

S

File Information 34filtering data 47how to choose columns 45how to filter data 48Monitored Logs 27Network 34Network File Server (NFS) 34Network Information 25, 26overview 25Process 25, 34Remote Procedure Call (RPC) 35sorting data 46System 35System CPU 27, 35System Groups 27, 33System Information 27System Load Average 26, 36System Virtual Memory 26, 36types of 25UNIX Disk Inodes 49User 25Users 36using 32viewing additional information 37with additional views 38

root Calls 94, 97RPC Client Times Call Wait On Busy 148RPC Performance workspace 241

SScheduling Class Name 131selecting the contents of a report 44Session ID 132Set Attribute Calls 94, 97severity levels

customer support 253Size 55, 71, 78, 112, 117, 122, 127, 138,

212sorting report data 46Space Available 71Space Available (KBytes) 55Space Used 71

Space Used (KBytes) 55Space Used (Percent) 55Space Used Percent 72special Information about the Flag Field 101Spins on Mutexes 182, 185Spins on RW Locks 182, 185Stack Size 138StartTime 112, 117, 122, 127, 132, 135,

138, 212SVR4 priority scheme 111, 116, 121, 126,

131, 211Symbolic Link Calls 94, 97System Calls 166, 182, 185System CPU 179, 192System CPU report 35System CPU Time 138System Groups report 27, 33System Load Average report 36System Name 94, 97, 132, 135, 138, 157,

160, 163, 166, 179, 182, 192, 200, 219

System Read 166System report 35System Virtual Memory report 36System workspace 243System Write 166

Ttelephone support

customer service 252Terminal 208Terminal Device 112, 117, 122, 127, 132,

212Thread Count 132Thread Migrations 182, 185Time 112, 117, 122, 127, 212Times Authentication Refreshed 147Times RPC Packet Unavailable 145Timestamp 55, 62, 72, 78, 87, 94, 97,

112, 117, 122, 127, 132, 145, 148, 157, 160, 163, 166, 179, 182, 185, 192, 200, 208, 212, 220

U


Total Child CPU Time 138Total CPU Percent 138Total CPU Time 138Total Inodes 55, 72Total Real Memory (KBytes) 192Total Real Memory (Kilobytes) 158Total Virtual Memory 158, 220Total Virtual Memory (KBytes) 193Transfer Rate 62

information about 61Transferred Bytes 62Transmitted Count (Frames) 88Type 78, 158types of information

disk inodes 26disk performance 26disk utilization 26file 25monitored logs 27network 25NFS/RPC 27processes 25system 27system CPU 27system groups 27system load average 26system virtual memory 26user 25

UUNIX Child Process report 119

Command 119CPU Utilization 120Event Waited On 120Execution State 120Flag 121Mem Pct 121Nice Value 121Parent Process ID 121Priority 121Process ID 122

Size 122StartTime 122Terminal Device 122Time 122Timestamp 122User ID 122

UNIX Disk Inode chart 52UNIX Disk Inodes report 49–55

Inodes Free 55Inodes Used 55Inodes Used Percent 55Mount Point 55Name 55sample 51Size 55Space Available (KBytes) 55Space Used (KBytes) 55Space Used (Percent) 55Timestamp 55Total Inodes 55using the chart view 52viewing real-time performance data 53

UNIX Disk Performance report 26, 57–62Average Queue 62Average Service Time 62Average Wait 62Busy Percent 62Disk Name 62sample 59Timestamp 62Transfer Rate 62Transferred Bytes 62using 58

UNIX Disk Utilization chart 68UNIX Disk Utilization report 26, 65–72

Inodes Free 70Inodes Used 70Inodes Used Percent 71Mount Point 71Name 71remote file system mounting 69sample 67

Index 265

U

Size 71Space Available 71Space Used 71Space Used Percent 72Timestamp 72Total Inodes 72typical scenario 76using 66viewing real-time disk space 69

UNIX File Information report 73–79Access 77File 77Group 77Last Accessed Time 77Last Changed Time 77Link Name 77Links 77Owner 77Path 78sample 75Size 78Timestamp 78Type 78using 74

UNIX Group Process reportEvent Waited On 125

UNIX Memory Analysis chart 151sample 152

UNIX Monitored Logs report 27UNIX Network File Server (NFS) report 89–

98UNIX Network report 81–86

Collisions 86Frames Received 86Frames Transmitted 86Frames vs. Packets 85Input Errors 86Interface DNS Name 86Interface IP Process 86Interface Status 86Maximum Transmission Unit 86Network Interface Name 87

Output Errors 87Received Count (Frames) 87sample 83Timestamp 87Transmitted Count (Frames) 88typical scenario 84using 82

UNIX NFS Client Activity reportCalls 96Calls Rejected 96File Creates 96File System Statistics Calls 96Get Attribute Calls 96Link Calls 96Lookups 97Make Directory Calls 97Null Calls 97Read Calls 97Read Directory Calls 97Read Link Calls 97Rejected Calls Percentage 97Remove Directory Calls 97Remove File Calls 97Rename File Calls 97root Calls 97sample 91Set Attribute Calls 97Symbolic Link Calls 97System Name 97Timestamp 97Write Cache Calls 98Writes 98

UNIX NFS reportsaccessing 92

UNIX NFS Server Activity reportCalls 93Calls Rejected 93File Creates 93File System Statistics Calls 93Get Attribute Calls 93Link Calls 93Lookups 93

U


Make Directory Calls 93Null Calls 94Read Calls 94Read Directory Calls 94Read Link Calls 94Rejected Call Percentage 94Remove Directory Calls 94Remove File Calls 94Rename File Calls 94root Calls 94sample 91Set Attribute Calls 94Symbolic Link Calls 94System Name 94Timestamp 94Write Cache Calls 94Writes 94

UNIX Process Child reportcolumn descriptions 119

UNIX Process Group reportcolumn descriptions 124Command 124CPU Pct 124CPU Utilization 125Execution State 125Flag 126Mem Pct 126Nice Value 126Parent Process ID 126Priority 126Process ID 127Size 127StartTime 127Terminal Device 127Time 127Timestamp 127User ID 127

UNIX Process reportcolumn descriptions 109, 114Command 114CPU Pct 114CPU Utilization 115

Event Waited On 115Execution State 115features 100Flag 101, 116Mem Pct 116Nice Value 116Parent Process ID 116Priority 116Process ID 117sample 103Size 117StartTime 117Terminal Device 117Time 117Timestamp 117topology view 104typical scenario 108User ID 117

UNIX Process Top CPU Time reportCommand 109CPU Pct 109CPU Utilization 110Event Waited On 110Execution State 110Flag 111Mem Pct 111Nice Value 111Parent Process ID 111Priority 111Process ID 112Size 112StartTime 112Terminal Device 112Time 112Timestamp 112User ID 112

UNIX RPC Client Activity reportCalls Rejected by Server 147Calls Retransmitted 147Calls Timed Out 147Replies Not Matching Calls 147row descriptions 147

Index 267

U

RPC Client Times Call Wait On Busy 148sample 143Times Authentication Refreshed 147Timestamp 148

UNIX RPC reportsaccessing 143

UNIX RPC Server Activity reportCalls Rejected 145Packets Too Short 145Packets with Malformed Header 145row descriptions 145sample 142Times RPC Packet Unavailable 145Timestamp 145

UNIX Solaris System CPU Workload reportcolumn descriptions 184Context Switches 184CPU ID 184CPU Status 184Cross Calls 184Interrupt as Threads 185Interrupts 185Involuntary Context Switches 185Major Faults 185Minor Faults 185Spins on Mutexes 185Spins on RW Locks 185System Calls 185Thread Migrations 185Timestamp 185

UNIX Solaris System CPU Workload Summary report

column descriptions 181Context Switches 181CPU ID 181CPU Status 181Cross Calls 181Interrupt as Threads 182Interrupts 182Involuntary Context Switches 182Major Faults 182Minor Faults 182

Spins on Mutexes 182Spins on RW Locks 182System Calls 182System Name 182Thread Migrations 182Timestamp 182

UNIX System Cache and Buffers reportBlock Reads 160Block Writes 160Logical Block Reads 160Logical Block Writes 160NonBlock Reads 160NonBlock Writes 160System Name 160Timestamp 160

UNIX System CPU report 27column descriptions 179CPU Busy 179CPU ID 179CPU Status 179Idle CPU 179monitoring system information 170sample 173, 174System CPU 179System Name 179Timestamp 179typical scenario 177User CPU 179Wait I/O 180

UNIX System Groups report 27sample 188

UNIX System Load Average report 26Boot Time 162, 200column descriptions 200features 196Load Average (1 Min) 162, 200Load Average (15 Min) 163, 200Load Average (5 Min) 163, 200overview 162, 199sample 153, 197System Name 163, 200Timestamp 163, 200

U


typical scenario 198Up Time 163Uptime 200

UNIX System report 27Free Memory (Kilobytes) 157Net Address 157Number of System Processes 157Number of User Sessions 157sample 151System Name 157Timestamp 157Total Real Memory (Kilobytes) 158Total Virtual Memory 158Type 158typical scenario 156Version 158

UNIX System Summary reportaccessing additional reports 190column descriptions 192Free Memory (Kbytes) 192Idle CPU 192Load Average (1 Min) 192Load Average (5 Min) 192overview 191System CPU 192System Name 192Timestamp 192Total Real Memory (KBytes) 192Total Virtual Memory (KBytes) 193typical scenario 190User CPU 193Wait I/O 193

UNIX System Virtual Memory chart 215UNIX System Virtual Memory report 26UNIX User Process report

Command 209CPU Pct 209CPU Utilization 210Event Waited On 210Execution State 210Flag 211Mem Pct 211

Nice Value 211Parent Process ID 211Priority 211Process ID 211Size 212StartTime 212Terminal Device 212Time 212Timestamp 212

UNIX Users reportcolumn descriptions 207, 209Idle Time 207Location 207Login Name 207Login Time 207monitoring individual users 204Name 207overview 204sample 205Terminal 208Timestamp 208typical scenario 206User ID 208

UNIX Virtual Memory report 213–220Active Virtual Memory 218column descriptions 218Free Memory 218monitoring virtual memory 214Page Faults 218Page Faults/Scan Rate 219Page Ins 218Page Outs 218Page Reclaims 219Pages Paged In 219Pages Paged Out 219Processes/Threads in Run Queue 219Processes/Threads Waiting 219sample 215System Name 219Timestamp 220Total Virtual Memory 220typical scenario 216

Index 269

V

Virtual Memory Percent Available 220Virtual Memory Percent Used 220

UNIX Workload reportCPU Context Switches 165Device Interrupts 165Execs Executed 165Forks Executed 165Number of System Procs 165Processes Idle 165Processes Runnable 165Processes Running 166Processes Sleeping 166Processes Stopped 166Processes Zombie 166System Calls 166System Name 166System Read 166System Write 166Timestamp 166

UNIX_System_Capacity 28Up Time 163Uptime 200User CPU 179, 193User CPU Time 138User ID 112, 117, 122, 127, 132, 135,

138, 208User Name 132user-defined situations 28Users report 36Users workspace 248Using 22using the monitored disk inode data 50

VVersion 158Version 120 agents

display 01.30.00 40, 171Virtual Memory Percent Available 220Virtual Memory Percent Used 220Virtual Size 138

WWait CPU Time 138Wait I/O 180, 193Wait Lock Time 138workspace

Disk Usage 229workspaces

attribute groups used 226File Information 232Network 234NFS Activity 237organization for CandleNet Portal 223Process 239RPC Performance 241System 243Users 248

Write Cache Calls 94, 98Write Time

historical report column 56, 212, 220Writes 94, 98

W


Date post:	14-Sep-2020
Category:	Documents
Upload:	others
View:	2 times
Download:	0 times

OMEGAMON XE for UNIX User’s Guide,...

Documents