OVNPM 1.5.2 - Performance Agent for NonStop Server Monitoring Guide

ManualsBrandsHP ManualsServerHP NonStop G-Series

HP Performance Agent for NonStop

Server Monitoring Guide

Part

number: 519586-003

Third edition

: 04/2012

Summary of content (115 pages)

PAGE 1
HP Performance Agent for NonStop Server Monitoring Guide Part number: 519586-003 Third edition: 04/2012
PAGE 2
Legal notices Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.
PAGE 3
Contents Preface Before You Begin ........................................................................................................................................ 8 Audience ................................................................................................................................................... 8 Goals of Documentation .............................................................................................................................. 8 Organization................
PAGE 4
3-7-1 3-7-2 3-8 3-8-1 3-8-2 3-9 3-9-1 3-9-2 3-10 3-10-1 3-10-2 3-11 3-11-1 3-11-2 3-12 3-12-1 3-12-2 3-13 3-13-1 3-13-2 3-14 3-14-1 3-14-2 3-15 3-15-1 3-15-2 3-16 3-16-1 3-16-2 3-17 3-17-1 3-17-2 3-18 3-18-1 3-18-2 3-19 3-19-1 3-19-2 3-20 3-20-1 3-20-2 3-21 3-21-1 3-21-2 3-22 3-22-1 3-22-2 3-23 3-23-1 3-23-2 3-24 3-24-1 3-24-2 3-25 3-25-1 DISKFILE Instance Configuration ............................................................................................. 34 DISKFILE Metrics ........................
PAGE 5
4-1-1 4-1-2 Threshold Configuration Macro .............................................................................................. 53 Writing the Threshold Text File ............................................................................................... 54 5 Configuring 5-1 5-2 5-3 5-4 5-5 Loop Detection Introduction .......................................................................................................................... 57 CPU Loop Detection ...............................
PAGE 6
System Alert ...................................................................................................................................... 106 Event Alert......................................................................................................................................... 107 Alert Tokens ...................................................................................................................................... 107 EMS Format ............................................
PAGE 7
Figures Figure 1 Estimation of Database Size ...............................................................................................................
PAGE 8
Preface HP Performance Agent for NonStop (OVNPM), formerly known as HP OpenView NonStop Server Performance Management, is an out-of-the-box solution that provides performance monitoring of HP NonStop servers. The software is a natural extension of HP Operations (formerly known as HP OpenView) and provides you with true end-to-end management of your NonStop environment. The various OVNPM Guides provides information about how to get started and use the product.
PAGE 9
Organization Chapter No. Chapter Name Description Chapter 1. OVNPM Monitoring Overview Provides an overview of the OVNPM monitoring. Chapter 2. OVNPM Monitoring Configuration Provides information on how to configuration monitoring parameters and building the configuration on HP NonStop Server. Chapter 3. OVNPM Entities Details the instance configurations and entity configurations for OVNPM domains. Chapter 4.
PAGE 10
OVNPM Documentation Map HP Performance Agent for NonStop (OVNPM) provides a set of manuals and online help that help you use the product and understand the concepts underlying the product. This section describes what information is available and where you can find it. Electronic Versions of the Manuals All manuals are available as Adobe Portable Document Format (PDF) files in the documentation directory on the OVNPM product CD-ROM. All manuals are also available in the HP web server directory.
PAGE 11
1 OVNPM Monitoring Overview 1-1 Goals OVNPM monitors NonStop server and customers application along with the hardware and system software components. Installation procedure adds most of the information in the OVNPM monitoring configuration. Monitoring user specific applications requires more analysis. This guide provides the information to build a monitoring configuration adapted to the specific need of the production. 1-2 Definitions An instance is a system resource to be measured.
PAGE 12
2 OVNPM Monitoring Configuration 2-1 OVNPM Collect and Database Parameters Installation process defines default values for collect and database parameters. This topic provides information for configuring these parameters after installation. This information is optional and is provided for advanced users. In this topic, configuration means OVNPM monitoring configuration. Most of these tasks can be performed using the VCONF utility. For details, refer Appendix B: VCONF Utility.
PAGE 13
2-1-1-2 Blacklisted Measurements OVNPM can start up to five measurements. When USERDEF and BASE24DEF entities are declared in the monitoring configuration, OVNPM searches in all Measurements where these USERDEF are bumped. This search operation has a cost attached. The CPU and time cost can be reduced by excluding the measurements from the search scope. To achieve this, user edit BLACKLST file located in configuration subvolume.
PAGE 14
System Report: Alphanumeric Data File Time Interval Default Retention Period in Days 32 minutes 7 Report time interval equals Collect interval (30 seconds or 15 Seconds) 3 14
PAGE 15
2-2 Building the OVNPM Configuration on HP NonStop Server The OVNPM installation process creates a default configuration for out-of-the-box use. You will have to modify and build the OVNPM configuration in the following scenarios: • Hardware is added or removed • System Software added, removed or upgraded • User Application added, removed or upgraded • Change the monitoring status of any of the existing entity NOTE: Installation process doesn’t know user applications.
PAGE 16
• PROGRAM • PROCESS • USERDEF • BASE24DEF • TERMINAL • SOCKETS • SQLPROC • SQLSTMT • TCP/IP The USERCFG file needs to be modified manually to change the monitoring parameters for the existing entities or to add user application information. You can edit the USERCFG file to remove units you do not want to monitor, change trend flag status, or add additional units. Use the following guidelines to edit the file: • Entities are stored in the USERCFG file by domain type.
PAGE 17
Refer to Symbolic Path Names for details. You can use the syntax provided above to make the desired changes in the USERCFG file. In the following sample section of the USERCFG file, a new APPLIDEF entity named APPLICATION2 has been added, which will monitor processes $Pra, $PRb and $PRc. - section: APPLIDEF -- Syntax : APPLIDEF [,TREND=] -- =<$Process1>+<$Process2>+.. -- .processes=<$Process3> <$Process4>+..
PAGE 18
2-2-3 Step 3: Building the Configuration Use the following commands to build the OVNPM configuration using the modified USERCFG and USERMT files. 1. 2. Change the subvolume to the OVNPM TACL subvolume. Load the OVNPM environment using the following command. run visload 3. Build the OVNPM configuration. sv_build_config 4. If the USERCFG file contains error, the build configuration fails. Syntax errors are displayed with line number. Also, duplicated instances are not allowed.
PAGE 19
2-3 Symbolic Path Name SPN or the Symbolic Path Name provides OSS pathname support for PROGRAM, FILESIZE, and DISKFILE domains. SPN are declared in the USERCFG file. 2-3-1 Symbolic Path Name Declaration A symbolic pathname ID or the SPNID is a unique identifier that defines and refers an OSSPATH. For example, 0web, my_app, and 2004data are valid SPNIDs. The USERCFG syntax to declare a SPN is: SPN [] Where: is an eight character unique identifier.
PAGE 20
2-3-2 Instance Name Using the SPN Instance name identifies an instance. The instance name length must be lower than 32 bytes. Instance name for in domain DISKFILE, PROGRAM and FILESIZE can use the OSS pathname if only the pathname length is lower than 32 bytes. If length is higher than 32 bytes the SPN must be used. The USERCFG Syntax of an instance using an SPN is: [spnId] [,trend=on|off] Where: domainName is one of FILESIZE, DISKFILE, and PROGRAM domains.
PAGE 21
2-4 Monitoring User Application A user application is a set of instances belong domain PROCESS, PROGRAM, APPLIFILE, APPLIDEF, USERDEF and BASE24DEF. To monitor user application, its components (that is instances) must be found and added in the USERCFG file. In OVNPM version 1.2, this operation must be done manually. • Step 1: Get Instances Related Processes In the first step, we must locate the subvolume or the directory that contains the executable belonging the application.
PAGE 22
ITERATION 0.94 Accum 1 BUSY 0.02 % Busy 0 PROCESSSTATES 0.14 Accum 0 PROCESSSTATES 0.15 Accum 1 To monitor those counters in OVNPM, we must locate and use: The process name in red The counter name in blue The counter index And the counter type to define the OVNPM “unit”. So Meascom output becomes in USERCFG file: userdef $vq0A.iteration.000.nb , TREND=ON userdef $vq0A.iteration.001.nb , TREND=ON userdef $vq0A.busy.000.% , TREND=ON Notice that accum unit “nb” gives value of the counter.
PAGE 23
sv_discover_application This function should be run when most programs from an application are in the same subvolume. The application should be running. Syntax: sv_discover_application