m.miller@hp.com August, 2002 - PowerPoint PPT Presentation

About This Presentation
Title:

m.miller@hp.com August, 2002

Description:

... An Availability Monitoring Infrastructure For NonStop Servers Engineered specifically for NonStop Server Architecture ... architectural enhancements to ... – PowerPoint PPT presentation

Number of Views:110
Avg rating:3.0/5.0
Slides: 40
Provided by: MikeM112
Category:

less

Transcript and Presenter's Notes

Title: m.miller@hp.com August, 2002


1
ASAP 2.2 Update
Availability What is ASAP DOTs API OEM 2.x
Update EDL Directions
m.miller_at_hp.com
ITUG Summit 2002 2731 October San Jose,
California EM-08-HP
  • m.miller_at_hp.comAugust, 2002

Presentation contains animation sequences that
are best viewed in slide show mode. A colon
character at the end of a slide bullet indicates
when to click the mouse button to advance
animation
2
Overview
Contents
  • ASAP Resources
  • Internet - http//NonStopAsap.Com
  • Manuals - TIM Independent Products CD
  • Training - Technical Update Training CD 30
  • Presentation Provides Overview of
  • Availability concepts
  • What is ASAP?
  • Release 2.0, 2.1, 2.2 update examples
  • Before discussing ASAP
  • Its important to understand, why monitor
    availability?
  • Its because monitoring increases actual
    availability.
  • To understand why, first discuss availability
    concepts.

3
Dependencies
Availability
  • Scenario - Person needs Taxi
  • Has No Cash... so needs ATM
  • Assumes ATM will be Available
  • Availability has many dependencies

Right Card.. Valid Pin.. Remember Pin.. No Line..
Atm Up.. Network Up.. Routers Up.. Server Up..
Application running.. Account valid.. Balance
OK.. Atm ?
4
Is a Relative Notion
Availability
  • Scenario - Person in hurry - Has 2 minutes to
    catch Taxi
  • If there is a long line, for example Q10
  • Even though ATM is Operational
  • For User at end of the line
  • ATM is NOT Available

5
Service Level Objectives
Availability
  • People define Availability according to their
    objectives.
  • Formal notion is called - Service Level
    ObjectivesEasy to remember, if SLO not met...
    things slow down.
  • ATM Service Level Objectives - Taxi fare
  • Status Up
  • Queue 0
  • Cash 20

6
Varies with Usage
Availability
  • User definition of Availability varies with
    usage.
  • Definition of ATM Availability is different for
    20 Taxi fare versus 300 Air fare
  • Goal ATM
  • Status Up
  • Queue 0
  • Cash 20

7
Depends on Application
Availability
  • Availability depends on how you intend to use
    object.
  • People define Availability based on their own
    criteria.
  • Goal Air Fare
  • Status Up
  • Queue 0
  • Cash 300
  • What if Air Fare were 800?
  • Would ATM be available?
  • Depends on Policy, not Hardware.

8
Review
Availability
  • Availability
  • Has many Dependencies
  • Is a relative Notion
  • Depends on Usage or Application
  • Can be defined with Service Level Objectives
  • To provide true High Availability Enterprise
  • Cannot just Monitor Hardware Operating System
  • But must also Monitor Availability of Application
    Domains
  • External Monitoring inadequate Apps Hang, Loop,
    Deadlock
  • External Monitoring cant know about internal
    domains values
  • If Application Domain Service Levels are not
    monitored, its impossible to know when an
    enterprise becomes unavailable.

9
Availability Monitoring Infrastructure
WhatisASAP?
  • An Availability Monitoring Infrastructure
  • For NonStop Servers
  • Engineered specifically for NonStop Server
    Architecture
  • Provides NonStop Server Agents, Process-Pairs,
    Fault-Tolerant DB,and published API for
    applications.
  • Automatically Restarts/Reconfigures when Cpus
    and/or Devices go up/down.

10
Not an Enterprise Management Framework
WhatASAP is NOT
  • ASAP is not an enterprise management framework
    such as Unicenter, NetView, OpenView, ...
  • ASAP is availability monitoring infrastructure
    for NSK
  • Engineered specifically for NonStop servers
  • Includes deep system and subsystem agents
  • Includes massively-parallel shared-segment API
  • Includes patented provider interface 6301557
  • Provides wide-variety of public interfaces

11
Interfaces
ASAPInterfaces
  • ASAP Public interfaces
  • Tandem EMS Events
  • SNMP Agent Traps
  • Provider/Consumer API
  • Plug-in 3rd party Entities
  • Published Database
  • Batch Query Interface
  • Conversational Interface
  • Graphical User Interface
  • Web Viewpoint interface
  • Optional EMF interfaces

02-09-17 114201 TANDEM.ASAP.V02 ASAP
ALERT Atm Chicago\Atm Status Cash 150 02-09-17
114201 TANDEM.ASAP.V02 ASAP ALERT File
Data.App.Cash RWEP nnnn 02-09-17 114202
TANDEM.ASAP.V02 ASAP ALERT Process App2
Status Down 02-09-17 114902 TANDEM.ASAP.V02
ASAP ALERT Funds\Transfer Status Lost
Trans 02-09-17 114902 TANDEM.ASAP.V02
ASAP ALERT Expand Lhny Status
Connecting 02-09-17 114902 TANDEM.ASAP.V02
ASAP ALERT Disk Data Full gt 95
12
How does ASAP work?
HowASAPWorks
  • Monitors
  • Status
  • Performance
  • Objectifies
  • Information into Object-State DB
  • Reports
  • Results
  • Analyzes
  • Service Level Objectives
  • Determines Availability

13
Monitoring
ASAPMonitoring
  • ASAP Monitors both Status and Performance of
    System objects and Application domains
  • Status refers to
  • Qualitative Attributes, such as Up, Down,
    Warning...
  • Performance refers to
  • Quantitative Attributes, such as Busy, Queue,
    Rate, ...
  • System Objects are
  • Subsystems or components, such as File, Rdf,
    Spooler, Tmf,
  • Application Domains are
  • Abstract Domains of Service, such as
    Accounts\Payable, Funds, Sales, ...

14
Objectification
ASAPObjectification
ATM Cash 150
  • ASAP Objectifies
  • Status and performance information into
    normalized object-state data base
  • Objectification provides basis
  • For Analysis and Visualizationof whether objects
    meet their Service Level Objectives.

15
Analysis
ASAPAnalysis
  • ASAP Analyzes Object
  • Status and Performance
  • Compares Service Objectives
  • Determines Object Availability

ATM WARNING Cash 150
Analysis
Availability
Availability
ATM Cash 150
16
Reporting
ASAPReporting
  • ASAP Reports Availability Info
  • Many different ways...EMS, Traps, DB, CI, WebVpt
  • Information is mapped onto a Uniform State Model
  • Also includes Analysis GUI
  • Tree
  • Graph
  • Grid Views
  • Context sensitive
  • Popup menus can be displayed on any object
  • Analysis Includes
  • Color synchronized
  • Graph elements
  • Grid elements
  • State icons

TreeGraphGrid
17
State Propagation
ASAPStatePropagation
  • ASAP Provides a uniform
  • Browsing paradigm for access to monitored objects
  • Tree View
  • Allows object navigation
  • Access to many objects
  • Drives Graph/Grid views
  • State Information
  • Propagated upward in tree
  • Provides guide to state of nodes, entities, and
    objects
  • State info always visible even if tree is
    collapsedExample - Newyork

18
Availability Vectors
ASAPAvailabilityVectors
  • Easy to assume ASAP just
  • Graphs Data Colors Elements.
  • Easy to Underestimate Content.
  • Includes Analysis Engine.
  • Determines Availability
  • Based on user defined rules.
  • Each PropertyAvailability Vector
  • Allows Availability Graphs/Icons
  • Result, Visual Display combines
  • Alpha, Numeric, Status,
  • Performance, SLOs all
  • Together in uniform paradigm
  • 3D, Color-Coded, Graphical display
  • Human mind good at patterns...
  • Faces, Buildings, Automobiles...

19
DOTs - Discrete Object Thresholds
ASAPService-Level Objectives
  • ASAP DOTs Hierarchical Service-Level
    Objectives
  • Rank Atm, Cash gt 1500
  • Rank Atm Zeist, Cash gt 3000
  • Rank Atm Zeist\North, Cash gt 4500
  • Rank Cpu 7, Busy lt 60, Queue lt 3, Swaps lt 6
  • Rank File Data.Master.Accounts, Full lt 80
  • Rank File System.System.Userid RWEP oooo
  • Dynamic Inclusion-Exclusion
  • Monitor Cpu, ON
  • Monitor Cpu 7, OFF
  • Monitor Disk, ON
  • Monitor Disk Data2, OFF
  • Monitor Process App5, ON
  • Monitor File System.System.Userid

20
Massively-Parallel Shared-Segment API
ASAP MPS2 Architecture
  • ASAPs Massively-Parallel Shared-Segment API
    Architecture
  • Allows deep application domain API integration
  • Engineered for NonStop server MP architecture
  • Ultra-fast, non-blocking, interface - Apps never
    wait
  • Efficient stats collection, aggregation,
    objective alerts

21
ASAP Extension API
ASAPXAPI
Data_item - Defined by EDL Value - Defined
by application Math 0 - Add Value to
Data_itemMath 1 - Assign Value to
Data_itemMath 2 - Assign Text to Data_item
22
ASAP API Example TeleBanking Web Server
ASAPXAPI
23
ASAP API Example - BASE24 plugin
ASAPXAPI
24
ASAP API Example TCPIP plugin
ASAPXAPI
25
What is Open Enterprise Management gateway
WhatisOEM?
  • OEM is not an enterprise management framework
    such as Unicenter, NetView, OpenView, ...
  • OEM is an Object-State gateway to EMFs
  • Reports Application domain Object-States
  • Reports System Subsystem Object-States
  • Optionally forwards object-state info to EMFs
  • Uses patented OEM provider API 6301557
  • OEM API published in TIM protects investment.
  • Allows change from one Enterprise Management
    solution to another without changing apps or
    agents.

26
ASAP OEM - Custom Adapter view
ASAPOEM
  • Consumer Adapter Left
  • OEM Provider - Right
  • Adapter Consumes Object-State information..
  • - Displays Updates
  • - Calls Back on Query
  • OEM Options Dialog- Allows adding Adapters

27
ASAP HP OpenView Operations
ASAPOEM
  • ASAP OpenView Operations agent integrates ASAP
  • Object-States
  • Availability
  • Performance
  • Service Levels
  • Objects Types
  • System objects
  • Subsystem objects
  • App domains
  • Also includes OVO Web interface 8

28
ASAP OEM - Standard Alerts view
ASAPOEM
29
ASAP 2.x Update
ASAPStatus Update
  • New features and fixes during last year
  • Release 2.0 June 2001
  • Discrete Object Thresholds Add service level
    objective monitoring
  • 6 New System Entities All old entities
    reworked for DOTs EMS
  • Entity Definition Language Provide extensible
    environment
  • Custom Namespace, Icons, and Colors Addressed
    I18N
  • Release 2.1 Nov 2001
  • Availability Events EMS, Web ViewPoint,
    OpenView Traps
  • EMS availability events - Extended to include
    object status
  • 37 new features and minor bug fixes Extreme
    reliability
  • Release 2.2 June 2002
  • EDL compiler performance improved 403 -
    Ansi?Unicode
  • Support for regional language locales -
    internationalization
  • 12 New plug-in entities - total entities number
    in 100s

30
New Entities
ASAPStatus Update
Plug-ins
31
DOTs Feature Summary
ASAPStatus Update
  • Provides uniform Service Level Objectives for all
    entity types
  • Uniform Object-State model now applies to all
    object types
  • All Objects Objectives can be changed on the
    fly
  • Dynamic re/definition of Service Level Objectives
  • Support instant, massive SLO reconfiguration
  • Dynamic addition and/or removal of Objects
  • Tokenized EMS events

32
EMS Events
ASAP Status Update
  • DOTs - Service Level Objective - Availability
    Events
  • EMS Events now Logged when DOTs SLO objectives
    are not met.
  • Event Generation Options include
  • INFO
  • CRITICAL
  • REPEAT
  • DISPLAY
  • Burst Suppression on EMS events
  • Eliminates Event Avalanches
  • Includes Burst Summary Reports

33
EDL Overview
ASAP Status Update
  • ASAP R2 - Design Goals Realized...
  • Provide extensible Entity Definitions
  • Allow Customer Applications to define and add
    Entities.
  • Allow Third Party EMF access to all Entity
    types.
  • Provide entity-attribute Name-Space
  • Allow DOTs to use entity-attribute Names, instead
    of metric ids.
  • Allow users to customize entity-attribute Names
    (internationalization)
  • Provide Version Independent code
  • Support Mixed version code environments and
    entity definitions
  • Eliminate maintenance (R2 Client runs with R1,
    R2, 2.1, 2.2... Servers)
  • Eliminate code changes (can add Entities without
    code changes)
  • Single ASAP thread support of K-series, S-series,
    and Itanium.

34
EDL
ASAP Status Update
  • What is EDL ?
  • A meta-data language file that defines how
    NonStop Server availability domains relate to
    ASAP features and functions.
  • Developers use EDL
  • To define how to monitor Subsystem Availability
  • To define how to monitor Application Availability
  • EDL is not something that ASAP users
  • Need to see,
  • Understand,
  • Or even be aware of

35
Why Care about EDL?
ASAP Status Update
  • EDL was designed to define availability
    properties
  • However EDL resulted in many additional benefits
  • Allows users to have different sets of customized
    ASAP settings.
  • Allows entire environments to be archived for
    later reference.
  • Observed behavior can be shared with other ASAP
    users. 
  • ASAP environments can be mailed to other people.
  • Useful for Application and System reporting.
  • Both Schema and Data can be stored in EDL files
  • Allows an entire ASAP environment to be saved in
    an EDL file.
  • Means you can completely snapshot or capture
    situations.
  • Means you can snapshot your entire system/app
    configuration.
  • EDL Files can be saved, mailed, reviewed, and
    displayed.

36
ASAP EDL Interactive Development Environment
ASAP Status Update
37
ASAP Futures
ASAP Futures
  • ASAP
  • Ongoing massively-parallel architectural
    enhancements to overall infrastructure
  • Performance enhancements always a goal eg
    403 faster EDL compiler v2.2
  • Monitor command enhancements, multiple objects,
    improved advisory messages
  • Process hierarchical-logical-name-grouping of
    Processes and their Aggregates
  • SGP placement, eg Disk, Expand, File, Process,
    Spooler, RDF, TMF, Tape
  • SHOW command display flags rank-able state pair
    attributes
  • Misc Discrete Objective Threshold (DOTs)
    enhancements
  • ASAPX
  • Larger and variable numbers of Data Items
  • In-Memory Detail Record retrieval (cordwood)
  • Java package for simplified access from Java
  • Allow finer Data Item Aggregation Control in
    ASAPX
  • Slot re-use of same domain for temp process names
    (X, Y, Z)

38
ASAP - OpenView Futures
ASAP Futures
  • OpenView will become another strategic interface
    for ASAP
  • ASAP OEM architecture will continue to be
    supported
  • OVO Survey available at http//NonStopAsap.com
  • Requesting input to help define OVO
    alternatives.
  • ASAP integration research for OVO underway
  • Actively Seeking Interested EAP Sites
  • Please Fill Out ASAP - OVO Survey

39
ASAP 2.x Release Summary
ASAP Summary
  • ASAP 2.x - Uniformly Extend Features to overall
    ASAP infrastructure
  • Allow concurrent Customer/Third party access -
    Multi-Entity Apps
  • Add Subsystem Monitoring - File, Process, RDF,
    Spooler, TMF, ...
  • Add Service-Level-Objectives For both new old
    entities
  • Add Service-Level Events - Satisfying EMS
    Requirements
  • Add Custom Namespace, Icons, Colors -
    Internationalization
  • Add Object State Change Views Allows
    reaching-back in time
  • Permit External Entity definitions - Entity
    Definition Language
  • Shift Focus from that of system monitoring
    Point-Product to a Fault-Tolerant Availability
    Monitoring Infrastructure for NonStop Server
    Subsystems and Applications.
Write a Comment
User Comments (0)
About PowerShow.com