+ All Categories
Transcript
Page 1: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

© 2004 Hewlett-Packard Development Company, L.P.The information contained herein is subject to change without notice

ASAP 2.5 TOI

Part 4

ASAP OVO SPI

mailto:[email protected]

Page 2: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 2

IntroductionWelcome to the ASAP 2.5 TOI

ASAP 2.5 TOI Part 1 – ASAP Server Rank, Action, File and Process ASAP 2.5 TOI Part 2 – ASAP Server Enhancements and Comm SGP

ASAP 2.5 TOI Part 3 – ASAP Client

ASAP 2.5 TOI Part 4 – ASAP OVO SPI

Audience• GCSC

• NonStop Analysts

• Other Interested HP Employees

Other Places to Go for Information• NonStopASAP.com

• HP OpenView SPI For ASAP Reference Guide (ships with the SPI)

• HP OpenView SPI For ASAP on-line help (ships with the SPI)

• HP OpenView SPI For ASAP manual in NTL

Page 3: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 3

ContentsWhat’s This About

Introduction topics, audience, other references

Background overview of the SPI

Architecture SPI components and how they fit within ASAP

ASAP Data in OVO ASAP objects, nodes, & messages in OpenView

System Requirements hardware and software necessary to run the SPI

Installation SPI setup, verification, and removal

Configuration configuring ASAP and SPI components

More Information additional resources

Page 4: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 4

•OpenView Smart Plug-In (SPI) for ASAP is a Windows-based component that allows ASAP to integrate with HP OpenView•Permits sharing of ASAP object hierarchy and alerts with an OpenView environment•Includes all objects monitored by ASAP: system, application, and third-party•SPI included as part of base ASAP product•OpenView integration is optional; OpenView is not required to utilize ASAP

ASAP OpenView SPI BackgroundGeneral Information and Capabilities

Page 5: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 5

SPI made up of two components: ASAP OpenView Adapter and ASAP OpenView Policy

ASAP OpenView SPI ArchitectureASAP OVO SPI Components

Page 6: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 6

ASAP OpenView SPI ArchitectureAdapter Details

•Receives ASAP object and state data from ASAP Client via OEM•Adds new objects, nodes, and services to OpenView•Analyzes the state of each object•Maps ASAP states to OpenView states•Generates an alert message for each object that has changed state•Regulates flow of alerts from ASAP to OpenView

Page 7: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 7

ASAP OpenView SPI ArchitecturePolicy Details

•Defines rules for how ASAP messages are handled by OpenView once received•Extracts message fields for display in message browser•Performs auto-acknowledgement of prior messages•Responsible for defining state propagation rules for ASAP objects within OpenView

Page 8: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 8

ASAP Data Within OpenViewOverview

ASAP data appears within OpenView in 4 locations:• All systems monitored by ASAP appear in the node tree

• ASAP object hierarchy appears in the services tree

• ASAP alert messages appear in the OpenView message browser

• ASAP nodes and alert messages accessible via OpenView web interface

•All ASAP data within OpenView can be viewed and acted on in the same way as all other OpenView data•ASAP data is “permanent” within OpenView; the only way to remove an object or message is to delete it via OpenView console

Page 9: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 9

• Nodes listed under “HP NonStop Servers (ASAP)” branch of tree

• Node name annotated to reflect state of the node

• OpenView propagation engine propagates “worst” state of any ASAP object on that system

• Selecting an individual node causes message browser to filter display of messages

ASAP Data Within OpenViewThe Node Tree

OpenView node tree contains a list of all systems monitored by ASAP

Page 10: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 10

ASAP Data Within OpenViewThe Services Tree

OpenView services tree contains a list of all ASAP services/objects

• Listed under “HP NonStop Servers (ASAP)” branch of tree

• Depth of object hierarchy controlled by Client and Adapter settings

• States propagated, and objects/services annotated to reflect state

• Drill-down through hierarchy causes message browser to filter accordingly

Page 11: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 11

ASAP Data Within OpenViewThe Hyberbolic Tree

•ASAP services/objects also displayed in OpenView hyperbolic services tree•Contains same data as standard tree; just a different display paradigm

Page 12: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 12

ASAP Data Within OpenViewMessages

Message browser contains alert messages from ASAP

• Severity reflects the criticality of the message

• Service defines the ASAP entity

• Node defines the node on which the object resides

• Object specifies the name of the object alerting

• Text provides error/state information

Page 13: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 13

ASAP Data Within OpenViewWeb Interface

ASAP data can be accessed from any web browser

ASAP Node List ASAP Messages Filter Criteria Acknowledge, annotate messages

Page 14: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 14

ASAP Data Within OpenViewState Mapping

ASAP and OpenView employ different state models• ASAP/OEM utilizes a 9-state model

• OpenView utilizes a 5-state model

• ASAP OpenView Adapter maps ASAP/OEM states to OpenView states

OEM Numeric State OEM State Description OpenView State

1 Exists, no state information known Normal

2 Up or OK Normal

3 Low Usage Warning

4 Medium Usage Warning

5 High Usage Warning

6 Warning Minor

7 Critical Major

8 Down Critical

9 State Degradation Critical

Page 15: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 15

System RequirementsSPI Hardware and Software Requirements

Hardware• Identical to those for OpenView, since the SPI runs on the

OpenView server system

Software• Microsoft Windows 2000 or 2003 server

• HP OpenView Operations for Windows version 7.x

• ASAP Client, any version

• ASAP Open Enterprise Management Gateway (OEM), any version

Page 16: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 16

InstallationSPI Setup and Deployment

To install the SPI• Run SPIForASAPSetup.exe from the ASAP 2.5 client CD

• Run SPIForASAPSetup.exe from the <program-files>\Tandem\ASAPOpenViewSetup folder

Restrictions• OpenView must be installed prior to installing the SPI

Effects of installation• SPI files placed on system

• SPI classes and objects registered in system registry

• SPI policy uploaded to OpenView

Page 17: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 17

InstallationVerifying the Installation

Verification process explained in detail in HP OpenView SPI for ASAP Reference Guide• Check that all files were installed to required locations

• Confirm that the ASAP OpenView Adapter has been registered correctly

• Ensure that the ASAP OpenView Policy has been uploaded to OpenView

• Ensure that the ASAP OpenView Policy has been deployed on the OpenView server

Page 18: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 18

InstallationRemoving the SPI from a Server

•Use Windows “Add or Remove Programs” control panel •May also manually remove the SPI components• See HP OpenView SPI for ASAP Reference Guide for

details

•ASAP objects, nodes, and messages in OpenView are not deleted if the SPI is removed

Page 19: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 19

Adapter ConfigurationOverview

To enable and configure the ASAP OpenView Adapter, three steps are necessary:• Enable the OEM in the ASAP Client

• Enable the OpenView Adapter in the OEM

• Set Adapter options

Page 20: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 20

Adapter ConfigurationEnable OEM in ASAP Client

OEM must be enabled in order to interface to OpenView• Check “Open Enterprise Management” check box on OEM

tab of ASAP client property sheet

Page 21: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 21

Adapter ConfigurationAdd/Activate OpenView Adapter in OEM

•Bring up OEM property sheet by double-clicking on OEM icon in system tray•Click on “Adapters” tab to view configured adapters•Add the OpenView Adapter if necessary•Activate the OpenView Adapter•Adapter will be started automatically by OEM from now on

Page 22: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 22

Adapter ConfigurationAccessing Adapter Properties

•Select the OpenView Adapter in the OEM Adapters list•Click on the Configure button to display the OpenView Adapter properties

Page 23: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 23

Adapter ConfigurationOVO Options

Control how the Adapter interacts with OpenView

•When services and nodes are added•Level of detail populated in the services tree•Message acknowledgement and flow control•OpenView file locations•Cleanup of work/temporary files

Page 24: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 24

Adapter ConfigurationOVO Service and Node Updates

•Adapter detects new services and nodes•Can send them to OpenView automatically, can prompt (default), or can wait for manual intervention•If “Manual Updates” is chosen, you must click on the “Update Now” button to cause updates to occur•Status fields on OVO property page will tell you if service or node updates are pending•OpenView console caches information, therefore consoles may need to be restarted to pick up new objects•Can manually force a reload by clicking on the “Reload OVO” button

Page 25: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 25

Adapter ConfigurationOVO Service Population Scheme

Three different choices for population• All Services

Populates all levels of objects, including instances; e.g.\Chicago\Disk\$System, \SanFran\CPU\00

• Container Services (default)

Populates only those objects/services that contain subitems; e.g.\Chicago\Disk, \SanFran\CPU

• n Levels of Detail

Populates to a fixed depth, regardless of the actual hierarchy

1 level = \Node only, 2 levels = \Node\Entity, etc.

Note that the population scheme does not affect which messages are logged to OpenView, only how many levels of drill-down are available in the Services tree

Page 26: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 26

Adapter ConfigurationOVO Message Options

•OVO Message Acknowledgement• Auto-acknowledgement of messages causes a new

message for a given object to replace prior message

• With auto-acknowledgement, objects always reflect the state of the latest message (this is the default)

• Without auto-acknowledgement, objects reflect the state of the most critical unacknowledged message

•OVO Message Flow Control• Can limit the number of messages sent by ASAP to OVO

• Prevents flooding of OVO in the case of a serious outage

• Adapter always logs most critical messages first

• Adapter will “catch up” when possible

Page 27: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 27

Adapter ConfigurationOVO Utility Options

•Adapter relies on OpenView utilities for some functions• Ovpmutil is used to perform node and service updates

• Opcmsg is used to log messages

• Typically these utilities should be installed with OpenView and should be on the search path

• If not, the location can be specified here

•Adapter creates temporary work files at startup, and during node and service updates• By default, these are removed immediately

• Files can be useful for debugging; if needed, uncheck the “Cleanup Temporary Files Automatically” check box to preserve the work files

Page 28: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 28

Adapter ConfigurationLogging Options

Manage the Adapter’s logging mechanism

•Enable or disable logging•Logging level can be set to any of 5 levels – critical only, errors, warnings, internal messages, or all messages•Specify the log file location•Can automatically delete the log file when the Adapter shuts down if desired•Log file is in HTML format; can be viewed using any browser

Page 29: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 29

Adapter ConfigurationTracing Options

Control the Adapter’s tracing facility

•Enable or disable tracing•Define items to trace•Specify trace file location•Number of records to trace•Enable or disable wrapping•All data traced in memory; written to disk when trace stopped•Should only be used for debugging!!

Page 30: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 30

Adapter ConfigurationVersion Information

Adapter version information and run-time status

•Version info should be supplied for any problem reports or cases•Statistics can be used as an aid in debugging (object counts, thread counts, exceptions, etc.)

Page 31: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 31

For More Information

Further details on the ASAP OVO SPI• HP OpenView SPI For ASAP Reference Guide (ships with

the SPI)

• HP OpenView SPI For ASAP on-line help (ships with the SPI)

• HP OpenView SPI For ASAP manual in NTL

Further information on ASAP• http://www.NonStopASAP.com

• Email [email protected]

• Email [email protected]

Thanks for attending!!

Page 32: ASAP 2.5 TOI  Part 4 ASAP OVO SPI

2004-08-23 ASAP 2.5 OVO SPI TOI 32


Top Related