adapter for hp ovo

BMC ProactiveNet Adapter forHP OVO Administrator Guide

April 2010

www.bmc.com

Contacting BMC Software

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

United States and Canada

Address BMC SOFTWARE INC2101 CITYWEST BLVDHOUSTON TX 77042-2827 USA

Telephone 1 713 918 8800or1 800 841 2031

Fax 1 713 918 8000

Outside United States and Canada

Telephone +01 713 918 8800 Fax +01 713 918 8000

© Copyright 2010- BMC Software, Inc.BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., areregistered with the U.S. Patent and Trademark Office, and may be registered or pending registration in othercountries. All other BMC trademarks, service marks, and logos may be registered or pending registration inthe U.S. or in other countries. All other trademarks or registered trademarks are the property of theirrespective owners.

IBM, Tivoli, and WebSphere are trademarks or registered trademarks of International Business MachinesCorporation in the United States, other countries, or both.

Oracle is a registered trademark of Oracle Corporation.

The information included in this documentation is the proprietary and confidential information of BMCSoftware, Inc., its affiliates, or licensors. Your use of this information is subject to the terms and conditions ofthe applicable End User License agreement for the product and to the proprietary and restricted rights noticesincluded in the product documentation.

Restricted rights legend

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

http://www.bmc.com

Customer support

Support website

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

■ read overviews about support services and programs that BMC offers

■ find the most current information about BMC products

■ search a database for problems similar to yours and possible solutions

■ order or download product documentation

■ download products and maintenance

■ report a problem or ask a question

■ subscribe to receive proactive e-mail alerts

■ find worldwide BMC support center locations and contact information, including e-mail addresses, fax numbers, andtelephone numbers

Support by telephone or e-mail

In the United States and Canada, if you need technical support and do not have access to the web, call 800 537 1813 or sendan e-mail message to [email protected]. (In the subject line, enter SupID:yourSupportContractID, such as SupID:12345). Outside the United States and Canada, contact your local support center for assistance.

Before contacting BMC

Have the following information available so that Customer Support can begin working on your issue immediately:

■ product information

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

■ operating system and environment information

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

maintenance level

■ sequence of events leading to the problem

■ commands and options that you used

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

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

3

http://www.bmc.com/support

mailto:[email protected]

License key and password information

If you have questions about your license key or password, contact BMC as appropriate for your location:

■ (USA or Canada) Contact the Order Services Password Team at 1 800 841 2031, or send an e-mail message [email protected].

■ (Europe, the Middle East, and Africa) Fax your questions to EMEA Contracts Administration at +31 20 354 8702, or send ane-mail message to [email protected].

■ (Asia-Pacific) Contact your BMC sales representative or your local BMC office.

4 BMC ProactiveNet Adapter for HP OVO Administrator Guide



Contents

Chapter 1 BMC ProactiveNet adapter for HP OVO 7BMC ProactiveNet adapter for HP OVO overview .....................................................7Adding an adapter for HP OVO ....................................................................................9

Adapter for HP OVO prerequisites ...................................................................10Connecting to the HP OVO Proxy server .........................................................11Configuring an environment HP OVO Proxy server .....................................12Importing HP OVO monitor types ....................................................................14Importing HP OVO application classes and creating an adapterinstance ..................................................................................................................15

Modifying the list of monitored attributes ..................................................................16XML files for SPIs ...........................................................................................................17

Provided XML files for SPIs ...............................................................................18XML reference for SPIs ........................................................................................19

Examining Detailed Diagnostics for HP OVO monitors ..........................................22Application diagnostics for the SCOPE SPI .....................................................23Process diagnostics for the SCOPE SPI .............................................................23Transaction diagnostics for the SCOPE SPI .....................................................24Status diagnostics for the CODA SPI ................................................................25Status diagnostics for the SCOPE SPI ...............................................................26

Enabling debug logging for the adapter for HP OVO .............................................27

Contents 5

BMC ProactiveNet adapter for HPOVO

This document provides details for configuring and using the BMC ProactiveNetadapter for HP OpenView Operations Manager (OVO).

BMC ProactiveNet adapter for HP OVOoverview

This section provides an overview of the concepts and procedure for using the BMCProactiveNet adapter for HP OVO.

The BMC ProactiveNet adapter for HP OVO collects numerical system and networkmonitoring performance data from HP OVO, and displays the data in BMCProactiveNet for in-depth and probable-cause analysis. Using the adapter for HPOVO, you can import application classes into BMC ProactiveNet and automaticallysynchronize the performance data collected by these application classes into BMC

1

Chapter 1 BMC ProactiveNet adapter for HP OVO 7

ProactiveNet. Figure 1 on page 8 illustrates the major components of the adapterarchitecture.

Figure 1: Adapter for HP OVO architecture

Configuring and creating an adapter instance starts in the BMC ProactiveNetAdministration Console where you connect to a proxy server, and provide informationto connect to the HP OVO server (not shown in the figure). The adapter queries theHP OVO server for a list of agents that you can select to build a monitoringenvironment. The adapter then loads XML files, which contain HP OVO Smart Plug-In (SPI) specifications, to show the list of monitor types that you can import. Afterimporting the monitor types you can select application classes to monitor.

BMC ProactiveNet adapter for HP OVO overview


After creation of the adapter instance, the proxy server communicates directly with theHP OVO agents. The adapter synchronizes the monitor information with BMCProactiveNet for display in the Operations Console.

BMC ProactiveNet includes several XML files for common SPIs. You can use the XMLfiles as-is, edit the files, or create files for custom-designed SPIs.

Note The HP OVO Proxy server is built on the PATROL Proxy server infrastructure. On-screen BMC ProactiveNet elements sometimes refer to the PATROL Proxy server. Theproxy server is the same, though, for adapters for BMC PATROL, HP OVO, and IBMTivoli.

For more details about BMC ProactiveNet adapters, refer to the BMC ProactiveNetAdministrator Guide.

Use the following table as a guide to find information about configuring and using theBMC ProactiveNet adapter for HP OVO:

Task Reference

(Optional) Edit or create an XML file for use with HPOVO Smart Plug-Ins (SPIs)

See “XML files for SPIs” on page 17

Add the BMC ProactiveNet adapter for HP OVO See “Adding an adapter for HP OVO ” on page 9

Modify the list of monitored attributes See “Modifying the list of monitored attributes” onpage 16

View Detailed Diagnostics and current information(FlashCheck) about the monitored attributes

See “Examining Detailed Diagnostics for HP OVOmonitors” on page 22

Refer to general information about adapters Refer to the BMC ProactiveNet Administrator Guide

Refer to detailed information about the HP attributes Refer to HP OVO documentation

Adding an adapter for HP OVOAdding an adapter for HP OpenView Operations Manager (OVO) involves thefollowing tasks:

Task reference

“Adapter for HP OVO prerequisites” on page 10

“Connecting to the HP OVO Proxy server” on page 11

“Configuring an environment HP OVO Proxy server” on page 12

“Importing HP OVO monitor types” on page 14

Adding an adapter for HP OVO


Task reference

“Importing HP OVO application classes and creating an adapter instance” on page 15

The tasks are linked in one graphic interface, but you can skip tasks depending on yourcurrent environment and requirements. The first time you configure an adapter,though, you need to perform each task, in order.

Adapter for HP OVO prerequisites

Before you configure and use the BMC ProactiveNet adapter for HP OpenViewOperations Manager (OVO), ensure that you have the listed prerequisites.

The BMC ProactiveNet adapter for HP OVO requires the following componentinstallations on the HP OVO Proxy server for successful data collection:

■ An HP OVO agent

— (for Windows) HP Performance Agent 4.7

— (for Solaris) HP Performance Agent C.04.70.000

— (for Linux) HP Performance Agent C.04.71.000

— (for IBM AIX) HP Performance Agent C.04.70.000

— (for all platforms) HP Operations Agent 08.52.006

■ Enable the proxy server during BMC ProactiveNet Server installation. For details,refer to the procedure in the BMC ProactiveNet Installation Guide.

Note During BMC ProactiveNet Server installation, select Enable Patrol\HP OVOProxy to enable the proxy server, or follow the instructions to enable the BMCPATROL Proxy server for a Windows agent. BMC adapters for BMC PATROL,HP OVO, and Tivoli use the same proxy server and you can use a single proxyserver for any combination of the adapters.You no longer need to enable the HPOVO Proxy server separately.

■ Prepare XML files to import HP OVO SPIs (for details, see “XML files for SPIs” onpage 17).



Connecting to the HP OVO Proxy server

Use the following procedure to connect to the HP OVO Proxy server.

Before you begin

Before you begin, verify that your environment satisfies the requirements listed in “Adapter for HP OVO prerequisites” on page 10.

To connect to the HP OVO Proxy server

1 In the Administration Console, select and right-click the Adapters folder, andchoose Import Monitor Types And Add Adapter => HP OpenView.

2 In the Import Monitor Types And Add Adapter dialog box, on the Configurationtab, complete the required information as detailed in the following table:

Table 1: Configuration tab for HP OVO adapter

Input Fields Description or action

Instance Name Type a unique instance name for the HP OVO adapter.You can also select an item from the Insert Macro list to more easilyidentify the adapter instance. For example, enter an instance name andselect HP OVO Proxy Agent Hostname/IP to add the $(DNSIP) macro.The macro retrieves the value from the selected field and displays thevalue during runtime.

Source Agent Select the name or IP address of the BMC ProactiveNet Agent on whichthe monitors are to be deployed.

HP OVO Proxy Agent Hostname/IP

Type or select the name or IP address of the computer where the HPOVO proxy server is running.

Port Type the port on which the proxy server runs. Unless directed otherwiseby BMC Customer Support, use the default port, 3182.

User Name and Password Type the user name and password necessary to log in to the HP OVOProxy server.

Skip Import Select this option to skip importing monitor types. When you clickNext, you can directly add application classes with previously importedmonitor types.The option is disabled if no monitor types are imported.

■ If the Skip Import option is not selected, you can view and modify the agentconfiguration on the HP OVO Proxy server, or import HP OVO monitor typesfrom an existing HP OVO environment. See the following sections for details:



—“Configuring an environment HP OVO Proxy server” on page 12

—“Importing HP OVO monitor types” on page 14

■ If the Skip Import option is selected, you can directly add application classes withpreviously imported monitor types. See “Importing HP OVO application classesand creating an adapter instance” on page 15 for details.

3 Select the Control tab and view or modify the statistics polling options, as detailedin the following table. When you finish, click Next.

Table 2: Control tab for HP OVO adapter

Input Fields Description

Statistics Poll Interval Select the time interval between successive statistical data polls from theHP OVO Proxy server.The default time is 5 minutes.

Statistics Poll Timeout Select the time-out period for each statistical data poll.The default time is 2 minutes.

Configuring an environment HP OVO Proxy server

An environment is a grouping of HP OVO agents that are configured on the HPOVO Proxy server.

Use the following procedure to configure an environment on the HP OVO Proxy server.

To configure an environment on the HP OVO Proxy server

1 After you connect to the HP OVO Proxy server (“Connecting to the HP OVO Proxyserver” on page 11), click Configure HP OpenView Proxy.

2 In the HP OVO Server Configuration dialog box, right-click the HP OpenViewenvironment folder and choose Configure HP OVO environment.

3 In the Import Agents from HP OVO Server dialog box, select the HP OVO platformto monitor. Complete the required information as detailed in the following table,and click Next:

Table 3: HP OVO platform details

Input Fields Action

HP OVO running on Windows (Connect to the WMI service)



Input Fields Action

HP OVO Server Host Name Type the HP OVO server host name.

User Name Type a local user name to connect to the HP OVO server. Do not use adomain user.

Password Type the password to connect to the HP OVO server.

HP OVO running on UNIX/Linux (Connect to the HP OVO database)

HP OVO DB Host Name Type the HP OVO database host name.

DB User Name Type the user name to connect to the HP OVO database.

DB Password Type the password to connect to the HP OVO database.

DB Port Type the HP OVO database port.The default port number for Oracle databases is 1521. The port numbercannot be less than 1024.

DB Name Type the HP OVO database name.

4 Select HP OVO agents from the List of Agents and click Add or Add All to movethem to the Available Agents list.

Available Agents lists agents that will be used to import monitor types onto theHP OVO Proxy server.

The following options are also available:

■ Hold the Ctrl key to select multiple agents.

■ Click Remove or Remove All to remove agents from the Available Agents list.

■ Set the frequency (in minutes) that data is collected from agents.

When you finish, click Next.

5 In the Save HP OVO Agents to Environment screen, select one of the followingoptions:

■ To create a new environment on the HP OVO Proxy server, such as for additionalHP OVO servers, select Create New Environment and enter a uniqueenvironment name.

■ To overwrite an existing environment on the HP OVO Proxy server, select Addto Existing Environment and select the name of an environment from the list.

6 To save the environment settings, click Save Changes.



7 (optional) Click Add More Agents to adjust agent settings in a new or existingenvironment.

Note To add or remove agents later, add a new adapter instance and adjust the HPOVO Proxy server configuration to update the existing environment.

8 Click Finish to complete the environment configuration and return to the HPOVO Server Configuration dialog box.

The configured environments are listed.

9 Click OK to return to the Import Monitor Types and Add Adapter dialog box.

All agents from the configured environments on the HP OVO Proxy server aredisplayed in the dialog box.

See “Importing HP OVO monitor types” on page 14 to continue.

Importing HP OVO monitor types

Monitor types in BMC ProactiveNet correspond to the HP OVO agents. When youimport monitor types, the system creates a template file on the HP OVO Proxy server.You can use this template to import application classes and create adapter instances.

Use the following procedure to import HP OVO monitor types.

To import HP OVO monitor types

1 Connect to the HP OVO Proxy server (“Connecting to the HP OVO Proxy server”on page 11).

2 Configure an environment on the HP OVO Proxy server (“Configuring anenvironment HP OVO Proxy server” on page 12) and click Next.

3 Select the monitor types that you want to use and the ones you want to delete.

■ A green check mark indicates that the monitor type is to be imported.

■ A green check mark with a lock indicates that the monitor type is in use.

■ A red X mark indicates that the monitor type is marked for deletion.



Best practice Import all monitor types; you can then edit a single adapter instance to clear groupsof application classes, or you can filter out monitor types that you do not need. Byimporting all the monitor types, you can edit a single adapter instance later, insteadof creating a new adapter instance.

4 Click Next.

See “Importing HP OVO application classes and creating an adapter instance” onpage 15 to continue.

Target Availability monitor for

A Target Availability monitor type, HP_AGENT_CONN_INFO, is available for everyHP OVO adapter instance.

The monitor provides a built-in attribute that reflects the status of the HP OVO agents.Target Availability is 100% if the HP OVO agent is available; otherwise, the value is0%. For more details about the Target Availability monitor, see the BMCProactiveNet Administrator Guide.

Importing HP OVO application classes and creating an adapterinstance

Use the following procedure to import HP OVO application classes and create anadapter instance.

To import HP OVO application classes and create an adapter instance

1 Connect to the HP OVO Proxy server (“Connecting to the HP OVO Proxy server”on page 11).

2 Configure an environment on the HP OVO Proxy server (“Configuring anenvironment HP OVO Proxy server” on page 12).

3 Import HP OVO monitor types (“Importing HP OVO monitor types” on page 14).

4 Select the application classes that you want to use and clear the ones you do notwant to use. Click Next.

5 (optional) On the Include Filters and Exclude Filters tabs, define filters for devicesand instances to include in, or exclude from, discovery, and then click Next.

For details about defining filters, see the BMC ProactiveNet Administrator Guide.



6 On the Schedule Auto-sync Polls screen, configure the time interval in which BMCProactiveNet runs an automatic synchronization poll (that is, a discovery of HPOVO agents), then click Next.

7 On the Summary Details for Adapter screen, review the details and perform one ofthe following actions:

■ If required, click Back to change the adapter details.

■ Click Finish to trigger an auto-sync poll and create the adapter instance.

Every agent in the configured environment is displayed in the Administration Consoleunder the Device => Server folder. You can expand the agents to see the associatedmonitor types by group.

If you add an agent through the Administration Console, and later remove the agent,the agent name continues to be displayed in the Administration Console. For bettermanagement, right-click the agent name and choose Delete to remove unused agentsfrom the Administration Console.

Modifying the list of monitored attributesThis topic presents instructions for modifying the list of monitored attributes for theBMC adapter for HP OVO.

Through the Administration Console, you can edit the following characteristics of HPOVO adapter instances (see the BMC ProactiveNet Administrator Guide for details):

■ Include and exclude filters

■ Auto-sync schedule

In addition, if you imported all the monitor types of a Smart Plug-In (SPI) when youconfigured the HP OVO adapter instance, you can edit the attributes and groups in thelist of application classes (see “To modify the list of attributes when all monitor typesare imported” on page 16).

If you did not import all the monitor types of an SPI when you configured the HPOVO adapter instance, you can edit the attributes and groups by creating a new adapterinstance (see “To modify the list of attributes when all monitor types are notimported” on page 17).

To modify the list of attributes when all monitor types are imported

If you imported all the HP OVO monitor types during monitor instance creation, thenyou can modify the list of monitored attributes.

Modifying the list of monitored attributes


1 In the Administration Console, expand the Adapters => HP OpenView folder andselect the adapter instance.

2 Right-click the adapter instance and choose Edit.

3 In the Edit HP OpenView dialog box, click Next.

4 Select or clear groups of application classes and click Next.

5 Adjust the include and exclude filters as required and click Next.

6 Adjust the auto-sync schedule as required and click Next.

7 Review the summary details for the adapter. Click Back to adjust details, orFinish to complete editing the adapter instance.

To modify the list of attributes when all monitor types are not imported

If you did not import all the HP OVO monitor types during monitor instance creation,then you can adjust the list of monitor types by adding a new HP OVO adapter instance.

1 In the Administration Console, add a new instance and connect to the HP OVOProxy server as described in the BMC ProactiveNet Administrator Guide.

Verify that the Skip Import check box is clear so that you can import new monitortypes.

2 On the Import HP OpenView Application Classes screen, which lists the monitoredagents, click Next and edit the list of imported monitor types.

Note You cannot remove monitor types that are in use, but you can clear the attributesgroups from the list of application classes so that the attributes are not displayed inthe Operations Console.

XML files for SPIsThis section describes XML files that you can use, edit, or create to import any HPOVO Smart Plug-In (SPI), including custom SPIs.

The BMC ProactiveNet adapter for HP OVO uses an XML file to import and integrateHP OVO SPI groups and attributes. The XML file contains the specifications HPOVO SPIs, including the groups and attributes (also called parameters) to be monitoredin BMC ProactiveNet. The adapter loads the XML files on the proxy server and

XML files for SPIs


synchronizes the monitor information with BMC ProactiveNet for display in theOperations Console.

You can use the provided XML files for common SPIs, or edit the files for your specificrequirements. You can also create an XML file for custom SPIs.

Provided XML files for SPIs

The following table describes the XML files for SPIs that are provided with the BMCProactiveNet installation. The files are located in the proxy server in theinstallDirectory\pw\pproxy\PNS\lib\ovxml directory.

File name SPI Description

ADSPI.xml Microsoft Active Directory

CODA.xml Basic SPI provided with the HP agent

DBSPI_MSS_GRAPH.xml Microsoft SQL Server graph metrics

DBSPI_MSS_REPORT.xml Microsoft SQL Server report metrics

DBSPI_ORA_GRAPH.xml Oracle Database graph metrics

DBSPI_ORA_REPORT.xml Oracle Database report metrics

MOSS_2007.xml Microsoft Office SharePoint Server 2007

MSES_BIZTALKSERVER_2004_INTERVAL.xml Microsoft BizTalk Server

MSES_BIZTALKSERVER_INTERVAL.xml Microsoft BizTalk Server

NET_SPS2003.xml Microsoft Office SharePoint Portal Server 2003

NET_SPS2003_COMMON.xml Microsoft Office SharePoint Portal Server 2003 commonmetrics

OASSPI_METRICS.xml Oracle Application server

OASSPI_RPT_METRICS.xml Oracle Application server report metrics

SCOPE.xml SPI provided with the HP performance agent

WBSSPI_METRICS.xml WebSphere Application server

WBSSPI_RPT_METRICS.xml WebSphere Application server report metrics

WINOSSPI-DNS.xml Microsoft DNS Server

WINOSSPI-IIS.xml Microsoft Internet Information Server

WINOSSPI-Win2k.xml Microsoft Windows 2000 operating system

WINOSSPI-WinOS.xml Microsoft Windows operating system

WINOSSPI-WTS-Win2k.xml Microsoft Windows Terminal Server Windows 2000operating system

XML files for SPIs


File name SPI Description

WLSSPI_METRICS.xml Oracle WebLogic Server

WLSSPI_RPT_ METRICS.xml Oracle WebLogic Server report metrics

XML reference for SPIs

You can create or edit XML files to import HP OVO Smart Plug-Ins (SPIs) into BMCProactiveNet for monitoring and analysis.

This topic describes the XML elements and attributes required to import an SPI intoBMC ProactiveNet.

The following example shows the elements and attributes used in the XML file for SPIs.

Example

<?xml version="1.0" encoding="UTF-8"?><SPI name="WINOSSPI-Win2k" calculation="no"> <GROUP name="WINOSSPI-Win2k" parent="WINOSSPI-Win2k" hasInstances="yes" label="WINOSSPI-Win2k" nameIdentifier="_InstanceName" groupIdentifier="SystemUpTime"> <parameter name="SystemUpTime"> <type>2</type> <description>System Up Time</description> <unit>#</unit> <style>standard</style> <factor>1</factor> </parameter> </GROUP></SPI>

SPI

The <SPI> root element contains the SPI group and parameter details.

The <SPI> element contains the following attributes: name and calculation.

name

The value of the name attribute is the name of the SPI, exactly as it is providedby HP OVO.

calculation

The value of the calculation attribute indicates whether one or moreparameters in the SPI require mathematical manipulation.

XML files for SPIs


■ A yes value indicates that one or more parameters are calculated as adelta value or require a normalization factor.For information about calculating delta values, see the <style> element.For more information about using normalization factors, see the <factor>element.

■ A no value indicates that none of the parameters are calculated as a deltavalue or require a normalization factor.

GROUP

Use one or more <GROUP> elements to define group details and to contain theparameter details of the group. If the SPI does not contain a group, add a groupusing the SPI name as the group name.

The <GROUP> element contains the following attributes: name, parent,hasInstances, label, nameIdentifier, and groupIdentifier.

name

The value of the name attribute is the name of the group, exactly as it isprovided by HP OVO.

parent

The value of the parent attribute is the name of the SPI, exactly as it isprovided by HP OVO. The attribute is reserved for future subgroupfunctionality of the HP OVO adapter.

hasInstances

The value of the hasInstances attribute indicates whether the group ofparameters can have more than one instance.

■ A yes value indicates that the group can have more than one instance,such as for CPUs or disks.

■ A no value indicates that the group has only one instance, such as forGLOBAL parameters.

label

The value of the label attribute is the name of the group that appears in theOperations Console.

nameIdentifier

The value of the nameIdentifier attribute specifies the name of the parameterthat provides the instance name.

XML files for SPIs


If no parameter provides the instance name, leave the nameIdentifierattribute empty. The instance name, in this case, is the same as the groupname.

groupIdentifier

The value of the groupIdentifier attribute specifies the name of a parameterthat uniquely identifies the group.

parameter

Use one or more <parameter> elements to define the name of each parameterand to contain elements with the parameter properties.

Note The adapter for HP OVO can only use numeric parameters for metric analysis.Do not add parameters with string values.

The <parameter> element contains the name attribute.

name

The value of the name attribute specifies the name of the parameter,exactly as it is provided by HP OVO.

type

The content of the <type> element is always 2, indicating a numerical value thatyou can use to generate a graph.

description

Type the content of the <description> element to add a description of theparameter and to identify it in the Operations Console.

unit

Type the contents of the <unit> element to specify the units of the parameter;for example, sec., #, or days, which will cause the units to be displayed withthe parameter in the Operations Console.

style

Type the contents of the <style> element to specify whether the parameterappears at its current value or as the difference since the previous collection.Use one of the following contents for the element:

XML files for SPIs


■ A standard value indicates that the Operations Console shows the currentvalue of the parameter.

■ A delta value indicates that the Operations Console shows the change inthe parameter since the previously collected value.

Note If the content of the <style> element is delta for any parameter in the SPI,ensure that the value of the calculation attribute in the <SPI> root element isyes.

factor

The <factor> element is a non-zero normalizing value.

Depending on your system configuration, the Operations Console mightdisplay some values in the SPI as greater than or less than the defined units bya factor of 10, 100, or 1,000. Adjust the contents of the <factor> element asrequired for your system.

Note If the content of the <factor> element does not equal 1 for any parameter in theSPI, ensure that the value of the calculation attribute in the <SPI> root elementis yes.

Examining Detailed Diagnostics for HP OVOmonitors

Use Detailed Diagnostics for HP OVO monitors to observe the performance of systemand network file systems for CODA and SCOPE Smart Plug-Ins (SPIs).

To view Detailed Diagnostics for HP OVO monitors

1 In the Operations Console, Grid View, click the All Devices folder in the navigationtree.

2 Select the PATROL Proxy server device name.

3 For an HP_AGENT_CONN_INFO monitor type, click Tools => Remote Actions/Diagnostics and select the required Detailed Diagnostics:

Examining Detailed Diagnostics for HP OVO monitors


■ “Application diagnostics for the SCOPE SPI” on page 23

■ “Process diagnostics for the SCOPE SPI” on page 23

■ “Transaction diagnostics for the SCOPE SPI” on page 24

■ “Status diagnostics for the CODA SPI” on page 25

■ “Status diagnostics for the SCOPE SPI” on page 26

Application diagnostics for the SCOPE SPI

The following table lists parameters that appear in the Applications DetailedDiagnostics for the SCOPE SPI.

For parameter details, refer to HP OVO documentation.

The results in the Application Detailed Diagnostics are sorted according to the CPUTotal Utilization value.

Parameter HP OVO parameter

Name APP_NAME

CPU Total Utilization (%) APP_CPU_TOTAL_UTIL

Memory Utilization (KB) APP_MEM_UTIL

Resident Memory (KB) APP_MEM_RES

Virtual Memory (KB) APP_MEM_VIRT

Alive Processes (#) APP_ALIVE_PROC

Active Processes (#) APP_ACTIVE_PROC

Process diagnostics for the SCOPE SPI

The following table lists parameters that appear in the Process Detailed Diagnosticsfor the SCOPE SPI.


The results in the Process Detailed Diagnostics are sorted according to the CPU TotalUtilization value.




Name PROC_PROC_NAME

ID PROC_PROC_ID

Parent ID PROC_PARENT_PROC_ID

User Name PROC_USER_NAME

CPU Total Utilization (%) PROC_CPU_TOTAL_UTIL

Resident Memory (KB) PROC_MEM_RES

Virtual Memory (KB) PROC_MEM_VIRT

Thread Count (#) PROC_THREAD_COUNT

Transaction diagnostics for the SCOPE SPI

The following table lists parameters that appear in the Transactions DetailedDiagnostics for the SCOPE SPI.


The results in the Transactions Detailed Diagnostics are sorted according to the Timevalue.


Name TT_NAME

ID TT_TRAN_ID

Application Name TT_APP_NAME

Application Transaction Name TT_APP_TRAN_NAME

Time (s) TT_WALL_TIME_PER_TRAN

User Name TT_UNAME

User Measurement Max (#) TT_USER_MEASUREMENT_MAX

User Measurement Avg (#) TT_USER_MEASUREMENT_AVG

User Measurement Min (#) TT_USER_MEASUREMENT_MIN



Status diagnostics for the CODA SPI

The following table lists parameters that appear in the Status Detailed Diagnostics forthe CODA SPI.


Parameter Unit

GBL_COLLECTOR not applicable

GBL_INTERVAL seconds

GBL_OSNAME not applicable

GBL_OSVERSION not applicable

GBL_OSRELEASE not applicable

GBL_MACHINE not applicable

GBL_NUM_CPU #

GBL_MEM_PHYS MB

GBL_NUM_DISK #

GBL_NUM_NETWORK #

GBL_MACHINE_MODEL not applicable

GBL_STATTIME date and time (mm/dd/yy hh:mm:ss AM|PM)

GBL_ACTIVE_CPU #

GBL_RUN_QUEUE #

GBL_CPU_SYS_MODE_UTIL %

GBL_CPU_USER_MODE_UTIL %

GBL_CPU_TOTAL_UTIL %

GBL_DISK_PHYS_IO_RATE #

GBL_INTERRUPT_RATE #

GBL_SWAP_SPACE_AVAIL MB

GBL_SWAP_SPACE_UTIL %

GBL_MEM_PAGEIN_RATE #

GBL_MEM_PAGEOUT_RATE #

GBL_MEM_UTIL %

GBL_NET_IN_PACKET_RATE #

GBL_NET_OUT_PACKET_RATE #



Parameter Unit

GBL_NET_ERROR_RATE #

GBL_FS_SPACE_UTIL_PEAK %

Status diagnostics for the SCOPE SPI

The following table lists parameters that appear in the Status Detailed Diagnostics forthe SCOPE SPI.


Parameter Unit

GBL_STATTIME date and time (mm/dd/yy hh:mm:ss AM|PM)

GBL_INTERVAL seconds

GBL_INTERRUPT_RATE #

GBL_ACTIVE_CPU #

GBL_CPU_TOTAL_UTIL %

GBL_CPU_SYS_MODE_UTIL %

GBL_CPU_USER_MODE_UTIL %

GBL_NUM_DISK #

GBL_DISK_PHYS_IO_RATE #

GBL_FS_SPACE_UTIL_PEAK %

GBL_MEM_UTIL %

GBL_SWAP_SPACE_UTIL %

GBL_MEM_PAGEOUT_RATE #

GBL_MEM_PAGEIN_RATE #

GBL_NUM_NETWORK #

GBL_NET_ERROR_RATE #

GBL_NET_IN_PACKET_RATE #

GBL_NET_OUT_PACKET_RATE #

GBL_RUN_QUEUE #



Enabling debug logging for the adapter for HPOVO

To help troubleshoot issues that might arise in the adapter for HP OVO, you can enabledebug logging.

To enable debug loging for the adapter for HP OVO

1 On the proxy server, open the ovconfig.xml file, located in the installDirectory\pw\pproxy\PNS\lib directory.

2 Change the value of the logLevel attribute to DEBUG, that is, logLevel="DEBUG".

3 Save and close the file.

The debugging information is written to the ovadapter.log file with the PID numberat the end of the file name. The file is located in the installDirectory\pw\pproxy\PNS\log directory.

Enabling debug logging for the adapter for HP OVO


Enabling debug logging for the adapter for HP OVO


Index

Aadding adapters

HP OVO 9Application diagnostics for the SCOPE SPI 23

Ddebug log

enabling logging 27description element 21Detailed Diagnostics

Application diagnostics for the SCOPE SPI 23Process diagnostics for the SCOPE SPI 23Status diagnostics for the CODA SPI 25Status diagnostics for the SCOPE SPI 26Transaction diagnostics for the SCOPE SPI 24viewing 22

Eediting monitored attributes 16

Ffactor element 22

GGROUP element 20

HHP OVO Proxy server

configuring environment 12connecting 11

HP OVO, adapter foradding 9creating adapter instances 15importing application classes 15importing monitor types 14overview 7prerequisites 10

HP_AGENT_CONN_INFO 15

IImport Monitor Types And Add Adapter dialog

box 11importing application classes 15importing monitor types 14

Mmonitored attributes

editing list of 16

Oovconfig.xml 27

Pprameter element 21Process diagnostics for the SCOPE SPI 23proxy server

configuring environment for HP OVO 12connecting 11

SSPI element 19

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Index 29

SPIs (Smart Plug-Ins)overview 17provided with BMC ProactiveNet installation

18XML reference 19

Status diagnostics for the CODA SPI 25Status diagnostics for the SCOPE SPI 26style element 21

TTarget Availability monitor

HP OVO 15

Transaction diagnostics for the SCOPE SPI 24type element 21

Uunit element 21

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z


49532*123883*

adapter for hp ovo

Documents