+ All Categories
Home > Documents > ASAP 2.5 TOI Part 4 ASAP OVO SPI


Date post: 17-Jan-2016
Author: kalila
View: 75 times
Download: 0 times
Share this document with a friend
ASAP 2.5 TOI Part 4 ASAP OVO SPI. mailto:[email protected] Introduction Welcome 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 - PowerPoint PPT Presentation
Embed Size (px)
Popular Tags:
of 32 /32
© 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]
  • IntroductionWelcome to the ASAP 2.5 TOIASAP 2.5 TOI Part 1 ASAP Server Rank, Action, File and Process ASAP 2.5 TOI Part 2 ASAP Server Enhancements and Comm SGPASAP 2.5 TOI Part 3 ASAP ClientASAP 2.5 TOI Part 4 ASAP OVO SPIAudienceGCSCNonStop AnalystsOther Interested HP EmployeesOther Places to Go for InformationNonStopASAP.comHP 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

  • ContentsWhats This AboutIntroductiontopics, audience, other referencesBackgroundoverview of the SPIArchitectureSPI components and how they fit within ASAPASAP Data in OVOASAP objects, nodes, & messages in OpenViewSystem Requirementshardware and software necessary to run the SPIInstallationSPI setup, verification, and removalConfigurationconfiguring ASAP and SPI componentsMore Informationadditional resources

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

  • ASAP OpenView SPI ArchitectureASAP OVO SPI ComponentsSPI made up of two components: ASAP OpenView Adapter and ASAP OpenView Policy

  • ASAP OpenView SPI ArchitectureAdapter DetailsReceives ASAP object and state data from ASAP Client via OEMAdds new objects, nodes, and services to OpenViewAnalyzes the state of each objectMaps ASAP states to OpenView statesGenerates an alert message for each object that has changed stateRegulates flow of alerts from ASAP to OpenView

  • ASAP OpenView SPI ArchitecturePolicy DetailsDefines rules for how ASAP messages are handled by OpenView once receivedExtracts message fields for display in message browserPerforms auto-acknowledgement of prior messagesResponsible for defining state propagation rules for ASAP objects within OpenView

  • ASAP Data Within OpenViewOverviewASAP data appears within OpenView in 4 locations:All systems monitored by ASAP appear in the node treeASAP object hierarchy appears in the services treeASAP alert messages appear in the OpenView message browserASAP nodes and alert messages accessible via OpenView web interfaceAll ASAP data within OpenView can be viewed and acted on in the same way as all other OpenView dataASAP data is permanent within OpenView; the only way to remove an object or message is to delete it via OpenView console

  • ASAP Data Within OpenViewThe Node TreeOpenView node tree contains a list of all systems monitored by ASAPNodes listed under HP NonStop Servers (ASAP) branch of treeNode name annotated to reflect state of the nodeOpenView propagation engine propagates worst state of any ASAP object on that systemSelecting an individual node causes message browser to filter display of messages

  • ASAP Data Within OpenViewThe Services TreeOpenView services tree contains a list of all ASAP services/objectsListed under HP NonStop Servers (ASAP) branch of treeDepth of object hierarchy controlled by Client and Adapter settingsStates propagated, and objects/services annotated to reflect stateDrill-down through hierarchy causes message browser to filter accordingly

  • ASAP Data Within OpenViewThe Hyberbolic TreeASAP services/objects also displayed in OpenView hyperbolic services treeContains same data as standard tree; just a different display paradigm

  • ASAP Data Within OpenViewMessagesMessage browser contains alert messages from ASAPSeverity reflects the criticality of the messageService defines the ASAP entityNode defines the node on which the object residesObject specifies the name of the object alertingText provides error/state information

  • ASAP Data Within OpenViewWeb InterfaceASAP data can be accessed from any web browser

    ASAP Node ListASAP MessagesFilter CriteriaAcknowledge, annotate messages

  • ASAP Data Within OpenViewState MappingASAP and OpenView employ different state modelsASAP/OEM utilizes a 9-state modelOpenView utilizes a 5-state modelASAP OpenView Adapter maps ASAP/OEM states to OpenView states

  • System RequirementsSPI Hardware and Software RequirementsHardwareIdentical to those for OpenView, since the SPI runs on the OpenView server systemSoftwareMicrosoft Windows 2000 or 2003 serverHP OpenView Operations for Windows version 7.xASAP Client, any versionASAP Open Enterprise Management Gateway (OEM), any version

  • InstallationSPI Setup and DeploymentTo install the SPIRun SPIForASAPSetup.exe from the ASAP 2.5 client CDRun SPIForASAPSetup.exe from the \Tandem\ASAPOpenViewSetup folderRestrictionsOpenView must be installed prior to installing the SPIEffects of installationSPI files placed on systemSPI classes and objects registered in system registrySPI policy uploaded to OpenView

  • InstallationVerifying the InstallationVerification process explained in detail in HP OpenView SPI for ASAP Reference GuideCheck that all files were installed to required locationsConfirm that the ASAP OpenView Adapter has been registered correctlyEnsure that the ASAP OpenView Policy has been uploaded to OpenViewEnsure that the ASAP OpenView Policy has been deployed on the OpenView server

  • InstallationRemoving the SPI from a ServerUse Windows Add or Remove Programs control panel May also manually remove the SPI componentsSee HP OpenView SPI for ASAP Reference Guide for detailsASAP objects, nodes, and messages in OpenView are not deleted if the SPI is removed

  • Adapter ConfigurationOverviewTo enable and configure the ASAP OpenView Adapter, three steps are necessary:Enable the OEM in the ASAP ClientEnable the OpenView Adapter in the OEMSet Adapter options

  • Adapter ConfigurationEnable OEM in ASAP ClientOEM must be enabled in order to interface to OpenViewCheck Open Enterprise Management check box on OEM tab of ASAP client property sheet

  • Adapter ConfigurationAdd/Activate OpenView Adapter in OEMBring up OEM property sheet by double-clicking on OEM icon in system trayClick on Adapters tab to view configured adaptersAdd the OpenView Adapter if necessaryActivate the OpenView AdapterAdapter will be started automatically by OEM from now on

  • Adapter ConfigurationAccessing Adapter PropertiesSelect the OpenView Adapter in the OEM Adapters listClick on the Configure button to display the OpenView Adapter properties

  • Adapter ConfigurationOVO OptionsControl how the Adapter interacts with OpenViewWhen services and nodes are addedLevel of detail populated in the services treeMessage acknowledgement and flow controlOpenView file locationsCleanup of work/temporary files

  • Adapter ConfigurationOVO Service and Node UpdatesAdapter detects new services and nodesCan send them to OpenView automatically, can prompt (default), or can wait for manual interventionIf Manual Updates is chosen, you must click on the Update Now button to cause updates to occurStatus fields on OVO property page will tell you if service or node updates are pendingOpenView console caches information, therefore consoles may need to be restarted to pick up new objectsCan manually force a reload by clicking on the Reload OVO button

  • Adapter ConfigurationOVO Service Population SchemeThree different choices for populationAll ServicesPopulates all levels of objects, including instances; e.g.\Chicago\Disk\$System, \SanFran\CPU\00Container Services (default)Populates only those objects/services that contain subitems; e.g.\Chicago\Disk, \SanFran\CPUn Levels of DetailPopulates to a fixed depth, regardless of the actual hierarchy1 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

  • Adapter ConfigurationOVO Message OptionsOVO Message AcknowledgementAuto-acknowledgement of messages causes a new message for a given object to replace prior messageWith 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 messageOVO Message Flow ControlCan limit the number of messages sent by ASAP to OVOPrevents flooding of OVO in the case of a serious outageAdapter always logs most critical messages firstAdapter will catch up when possible

  • Adapter ConfigurationOVO Utility OptionsAdapter relies on OpenView utilities for some functionsOvpmutil is used to perform node and service updatesOpcmsg is used to log messagesTypically these utilities should be installed with OpenView and should be on the search pathIf not, the location can be specified hereAdapter creates temporary work files at startup, and during node and service updatesBy default, these are removed immediatelyFiles can be useful for debugging; if needed, uncheck the Cleanup Temporary Files Automatically check box to preserve the work files

  • Adapter ConfigurationLogging OptionsManage the Adapters logging mechanismEnable or disable loggingLogging level can be set to any of 5 levels critical only, errors, warnings, internal messages, or all messagesSpecify the log file locationCan automatically delete the log file when the Adapter shuts down if desiredLog file is in HTML format; can be viewed using any browser

  • Adapter ConfigurationTracing OptionsControl the Adapters tracing facilityEnable or disable tracingDefine items to traceSpecify trace file locationNumber of records to traceEnable or disable wrappingAll data traced in memory; written to disk when trace stoppedShould only be used for debugging!!

  • Adapter ConfigurationVersion InformationAdapter version information and run-time statusVersion info should be supplied for any problem reports or casesStatistics can be used as an aid in debugging (object counts, thread counts, exceptions, etc.)

  • For More InformationFurther details on the ASAP OVO SPIHP 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 NTLFurther information on ASAPhttp://www.NonStopASAP.comEmail [email protected] [email protected]

    Thanks for attending!!