ASAP Release 2 0 ASAP Overview Architecture New

ASAP Release 2. 0 ASAP Overview Architecture New Features DOTs EDL Mike Miller Software Architect Nonstop Enterprise Division May 18, 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:

Contents Overview § Presentation Provides Overview of – Availability Monitoring Concepts – ASAP Features, its Architecture – Release 2. 0 Functions § ASAP Resources – White Paper & Migration Guide on TUT CD – Manuals on TIM Independent Products CD – Intra. Net http: //spg. web. tandem. com/ASAP – Inter. Net http: //nonstop. compaq. com/view. asp? PAGE=Ops. Mgmt_ASAP § Before discussing ASAP – It’s important to understand, Why Monitor Availability? – It’s because monitoring increases actual Availability. – To understand why, first discuss Availability concepts. 2

Availability Dependencies § Scenario - Person needs Taxi – Has No Cash. . . so needs ATM – Assumes ATM will be Available: – Availability has many dependencies: Network? Pin? Up? Line? Card? Right Card. . Valid Pin. . Remember Pin. . No Line. . Atm Up. . Network Up. . Routers Up. . Server Up. . Application running. . Account valid. . Balance OK. . Atm $ ? 3

Availability Is a Relative Notion § Scenario - Person in hurry - Has 2 minutes to catch Taxi – If there is a long line, for example Q=10: – Even though ATM is Operational – For User at end of the line: – ATM is NOT Available Q=0 Q=10 4

Availability Service Level Objectives § Users need to define “Availability” according to their own criteria. § Notion is called - Service Level Objectives If “SLO” not met. . . things “slow” down. § ATM Service Level Objectives - Taxi fare: – Status = Up – Queue = 0 – Cash = $20 5

Availability Varies with Usage § 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 6

Availability Depends on Application § Availability depends on how you intend to use object. § Users define “Availability” based on their own criteria. § Goal ATM – Air Fare: : – Status = Up – Queue = 0 – Cash = $300 ü What if Air Fare were $800? ü Would ATM be available? ü Not dependent on Hardware. 7

Availability Review § 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 can’t know about internal domains & values § If Application Domain Service Levels are not monitored, it’s impossible to know when Application Domains are unavailable. 8

ASAP Overview Introduction Monitors • Status • Performance Reports • Results Objectifies • Information into Object-State DB Object • Status • Performance Analyzes • Service Level Objectives • Determines Availability 9

ASAP 2. 0 Features DOTs - Discrete Object Thresholds § ASAP DOTs – Allow Discrete Object Thresholds: – Rank Atm ZeistNorth, Cash > 5000, Bad. Pins < 5 – Rank Process $My. App, PCpu=0, Priority=150 – Rank Cpu 7, Busy < 60, Queue < 1. 5, Swaps < 6 – Rank File $Data. Master. Accounts, Full < 80 Critical – Rank Disk $Data, Busy < 40 Info, Full < 90 Critical § Allow Dynamic Inclusion-Exclusion of Domains – Monitor Disk $Data 1, ON – Monitor Disk $Data 2, OFF – Monitor File $Data. Master. Accounts, ON – Monitor Process $Test, OFF 10

ASAP Overview Monitoring § ASAP Monitors the 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, Process, Rdf, Tmf, … § Application Domains are Object • Status • Performance – Abstract Domains of Service, such as AccountsPayable, Funds, Sales, . . . 11

ASAP Overview Objectification § ASAP Objectifies: – Status and performance information into normalized object-state data base ATM WARNING Cash $150 § Objectification provides basis: – For Analysis and Visualization of whether objects meet their Service Level Objectives. Object • Status • Performance 12

ASAP Overview Analysis ATM WARNING Cash $150 Availability Analysis § ASAP Analyzes Object – Status and Performance: – Compares Service Objectives: – Determines Object Availability: ATM Cash $150 Object • Status • Performance 13

ASAP Overview Reporting § ASAP Reports Object – Availability Information. – Information is Mapped to a Tree Graph Grid Uniform State Model – Visualized in the form of: § Tree § Graph § Grid Views – Context sensitive: § Popup menus can be displayed on any object – Analysis Includes § § Color synchronized Graph elements Grid elements State icons 14

ASAP Overview State Propagation § ASAP Provides a Uniform – Browsing paradigm for access to 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 collapsed: Example - Newyork 15

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

ASAP Architecture Architectural Overview Workstation Object Integration Layer OIL Adapter Open Enterprise Management Gateway ASAP Client Local Node ASAP Server Remote Nodes Enterprise Objects ASAP Server Cpu Disk Expand Process OIL OEM Enterprise Management Framework ASAP Server ASAP Client X Adapter Collector X Enterprise Management Framework Y Enterprise Management Framework . . . Y Adapter Alerts Window ASAP Database App Cpu Disk Expand Process … Analysis & Reports Graphs Grids Trees Enterprise Objects ASAP Extension. . . API Enterprise Objects ASAP. . . …. . . ASAPX. . . …. . . ? Adapter . . . Left side of diagram u Represents Consumer Functions. u Includes Presentation/Analysis Features. u Right side of diagram u Represents Provider functions u Including Smart Agents. u 21

ASAP Architecture Smart Gathering Processes - SGPs Workstation Object Integration Layer OIL Adapter ASAP Client Open Enterprise Management Gateway Local Node ASAP Server Remote Nodes Enterprise Objects ASAP Server Cpu Disk Expand Process OIL OEM Enterprise Management Framework ASAP Client Y Enterprise Management Framework . . . Enterprise Objects X Adapter Y Adapter ASAP Extension Collector X Enterprise Management Framework ASAP Server Alerts Window Analysis & Reports Graphs Grids Trees ASAP Database App Cpu Disk Expand Process … . . . API Enterprise Objects ASAP. . . …. . . ASAPX. . . …. . . ? Adapter . . . Smart Gathering Processes - SGPs u Collect Status & Performance info u Store Stats in ASAP history data base u 22

ASAP Architecture Service Level Objectives Workstation Object Integration Layer OIL Adapter ASAP Client Open Enterprise Management Gateway Local Node ASAP Server OIL ASAP Client OEM Enterprise Management Framework X Adapter Collector X Enterprise Management Framework Y Enterprise Management Framework . . . ASAP Server Y Adapter Analysis & Reports Graphs Grids Trees Alerts Window ASAP Database App Cpu Disk Expand Process … Remote Nodes Enterprise Objects ASAP Server Cpu Disk Expand Process Enterprise Objects ASAP Extension. . . API Enterprise Objects ASAP. . . …. . . ASAPX. . . …. . . ? Adapter . . . SGPs also provide Service Level Objectives. u SGPs inform you when SLOs are not met. u Tell you what objects did not meet objectives. u DB also provides history of failed objectives. u 23

ASAP Architecture Application Program Interface - API Workstation Object Integration Layer OIL Adapter ASAP Client Open Enterprise Management Gateway Local Node ASAP Server Remote Nodes Enterprise Objects ASAP Server Cpu Disk Expand Process OIL ASAP Client OEM Enterprise Management Framework X Adapter Collector X Enterprise Management Framework Y Enterprise Management Framework . . . ASAP Server Y Adapter Analysis & Reports Graphs Grids Trees Alerts Window ASAP Database App Cpu Disk Expand Process … Enterprise Objects ASAP Extension. . . API Enterprise Objects ASAP. . . …. . . ASAPX. . . …. . . ? Adapter . . . ASAP includes published API for application access. u Allows Customer-Third Party access to infrastructure. u Allows you to utilize all ASAP Client/Server functions. u API is a shared-seg, high-performance, architecture. u API calls include ASAP_Register, ASAP_Update. u 24

ASAP Architecture ASAP API - Example ASAP_REGISTER_( domain_name : length , segment_offset ); . . ENDTRANSACTION; ASAP_UPDATE_( segment_offset, error_detail , Data_item, Value, Math ); Shared Memory ASAPX ASAP Data_item - Defined by EDL ASAP Database Value - Defined by application Math = 0 - Add Value to Data_item Math = 1 - Assign Value to Data_item 25

ASAP Architecture ASAP API - BASE 24 Plugin - SLO Alerts 26

ASAP Architecture API – Service Level Objectives Workstation Object Integration Layer OIL Adapter ASAP Client Open Enterprise Management Gateway Local Node ASAP Server Remote Nodes Enterprise Objects ASAP Server Cpu Disk Expand Process OIL ASAP Client OEM Enterprise Management Framework X Adapter Collector X Enterprise Management Framework Y Enterprise Management Framework . . . ASAP Server Y Adapter Analysis & Reports Graphs Grids Trees Alerts Window ASAP Database App Cpu Disk Expand Process … Enterprise Objects ASAP Extension. . . API Enterprise Objects ASAP. . . …. . . ASAPX. . . …. . . ? Adapter . . . API also monitors Service Level Objectives for Apps u Informs you when Application SLOs are not met. u Tells what Apps did not meet objectives. u DB also provides history of failed App objectives. u 27

ASAP Architecture Data Base Workstation Object Integration Layer OIL Adapter ASAP Client Open Enterprise Management Gateway Local Node ASAP Server OIL ASAP Client OEM Enterprise Management Framework X Adapter Collector X Enterprise Management Framework Y Enterprise Management Framework . . . ASAP Server Y Adapter Analysis & Reports Graphs Grids Trees Alerts Window ASAP Database App Cpu Disk Expand Process … Remote Nodes Enterprise Objects ASAP Server Cpu Disk Expand Process Enterprise Objects ASAP Extension. . . API Enterprise Objects ASAP. . . …. . . ASAPX. . . …. . . ? Adapter . . . ASAP DB contains normalized object info. u DB history is automatically maintained. u Includes Object, State, Performance, & Service Objectives u DB Schema published in TIM, and DDL is on CD. u Allows Customer & Third Party DB access. u 28

ASAP Architecture ASAP Client Workstation Object Integration Layer OIL Adapter Open Enterprise Management Gateway ASAP Client Local Node ASAP Server OIL OEM Enterprise Management Framework ASAP Client X Adapter Collector X Enterprise Management Framework Y Enterprise Management Framework . . . ASAP Server Y Adapter Alerts Window Analysis & Reports Graphs Grids Trees ASAP Database App Cpu Disk Expand Process … Remote Nodes Enterprise Objects ASAP Server Cpu Disk Expand Process Enterprise Objects ASAP Extension. . . API Enterprise Objects ASAP. . . …. . . ASAPX. . . …. . . ? Adapter . . . Asap Client provides analysis & presentation functions. u Allows viewing of Availability, Performance, and SLOs. u Uses standard Windows visualization paradigm. u 29

ASAP Architecture Client as Analysis Tool Workstation Object Integration Layer OIL Adapter Open Enterprise Management Gateway ASAP Client Local Node ASAP Server OIL OEM Enterprise Management Framework ASAP Client ASAP Server X Adapter Collector X Enterprise Management Framework Y Adapter Y Enterprise Management Framework Alerts Window Analysis & Reports Graphs Grids Trees ASAP Database App Cpu Disk Expand Process … ? Adapter . . . Remote Nodes Enterprise Objects ASAP Server Cpu Disk Expand Process Enterprise Objects ASAP Extension. . . API Enterprise Objects ASAP. . . …. . . ASAPX. . . …. . . Client displays analysis using Graph, Grid, Tree, & Report Windows. u Users can select their own sets of Entities, Objects, and Properties. u Users can also specify their own sets of State Propagation Rules. u All graphical objects automatically update in real-time. u 30

ASAP Architecture Client as Object-State Provider Workstation Object Integration Layer OIL Adapter Open Enterprise Management Gateway ASAP Client Local Node ASAP Server Remote Nodes Enterprise Objects ASAP Server Cpu Disk Expand Process OIL OEM Enterprise Management Framework ASAP Client X Adapter Collector X Enterprise Management Framework Y Enterprise Management Framework . . . ASAP Server Y Adapter Alerts Window Analysis & Reports Graphs Grids Trees ASAP Database App Cpu Disk Expand Process … Enterprise Objects ASAP Extension. . . API Enterprise Objects ? Adapter ASAP. . . …. . . ASAPX. . . …. . . ASAP can also act as an Object-State Provider. u Utilizes the OEM Gateway to export Object -State information to EMFs. Utilizes the OEM Gateway to export Object-State information to EMFs. u OEM also provides Alert Windows, with sorted highest-to-lowest state views. u OEM acts as a multi-ported, bi-directional, Enterprise-Management Gateway u 31

OEM Architecture OEM Gateway to EMFs Workstation Object Integration Layer OIL Adapter Open Enterprise Management Gateway ASAP Client Local Node ASAP Server Remote Nodes Enterprise Objects ASAP Server Cpu Disk Expand Process OIL OEM Enterprise Management Framework ASAP Client ASAP Server X Adapter Collector X Enterprise Management Framework Y Adapter Y Enterprise Management Framework Alerts Window Analysis & Reports Graphs Grids Trees ASAP Database App Cpu Disk Expand Process … Enterprise Objects ASAP Extension. . . API Enterprise Objects . . . ASAPX. . . …. . . ? Adapter . . . ASAP. . . … . . . OEM Provides API to EMFs via Adapters u Adapters handle Framework specific APIs u Leverages Enterprise Framework Expertise u Allows integration with different Frameworks u Simplifies Client/Agent API Interface u Minimizes impact on Applications u Application-Agent Interface coded once u Handles Client Object-State arbitration u 32

OEM Architecture OEM Alerts View (No EMF) 34

OEM Architecture OEM Multiple Alert views: : Chicago Alerts Sorted All Node Alerts Sorted & Filtered 35

OEM Architecture OEM Custom Adapters Custom Adapter – Left u OEM Alerts View - Right u OEM Sends Object. States - Adapter Displays Updates: - Clicks callback Oem: u OEM Options Dialog: - Allows you to add Adapter u 36

OEM Architecture OEM EMF Adapter Interface: : 37

ASAP 2. 0 Features ASAP Release 2. 0 – New Features § Release 1. 0 - Focus was on “infrastructure”: – Server-Side API access – Data Base File access – Client-Side API access § Release 2. 0 - Focus is on “extensibility”: – – – – Uniformly Extend features to infrastructure Multi-Entity for Applications New System Entities Custom Icons and Colors Object State Change Monitor Discrete Object Thresholds New EMS Availability Events Extensible Entity Definition Language 41

ASAP 2. 0 Features Multi-Entity Apps § Support for Multi-Entity Applications – Release 1. 0 supported multiple applications §But one record layout was permitted for all. §Metrics were forced into single record model. §Restrictive, and could lead to Nonhomogeneous data. – Release 2. 0 allows separate App entity definitions: §Allows multiple Stats record definitions. §Allows different entity-attribute names. §Allows different service level objectives. §Allows disjoint Applications & Third Parties. §Allows user inclusion/exclusion of App entities. 42

ASAP 2. 0 Features ASAP 1. 0: § App § Cpu § Disk § Expand § Process § System New Entities ASAP 2. 0 Multi-Entity Applications u Cpu u Disk u Expand u File u Process Selected u Process Busy u RDF 1. 3 u Spooler u Tape u TMF u System u 43

ASAP 2. 0 Features DB Enhancements § Release 2. 0 Data Base Enhancements – Six New System Entity Tables – New Service Level Objectives Data Base – Support for Multi-Entity Applications – Support for Format 2 (Big) Files – Maximum Number of Extents now Configurable – Primary/Secondary Extent size now Configurable – Data Base can now be Partitioned – Partitioning on System and/or Domain name 44

ASAP 2. 0 Features Icons & Colors § Release 1. 0 - Fixed set of Icons & Alert Colors § Release 2. 0 - Allows User Defined Icons & Colors – Custom State Icons – Custom Alert Colors – Address Internationalization 46

ASAP 2. 0 Features OSC Monitor § Release 2. 0 – includes Object State Change Monitor – Tells you “What has Occurred” if ASAP is left unattended – Provides History of Object State Changes – Allows you to “Reach Back” in time § OSC View Includes – New State – Previous State – Date…Time of change – Reason for state change – Object or Domain affected by change – Functions to provide state change details 47

ASAP 2. 0 Features OSC View § Displays History of Object State Changes based on user criteria. § Provides Dual View: § Log – State Change log –Detailed History of state changes –Allows Monitoring of history & trends § Matrix – High-Level Summary –Summarizes Object-State Changes –Hyper-Matrix provides instant analysis of state changes. § Example… Click “ 15” in Matrix Locates all “Critical-Cpu” changes in log. 48

ASAP 2. 0 Features OSC Analysis Functions 49

ASAP 2. 0 Features DOTs - Discrete Object Thresholds § ASAP DOTs – Allow Discrete Object Thresholds: – Rank Atm ZeistNorth, Cash > 5000, Bad. Pins < 5 – Rank Process $My. App, PCpu=0, Priority=150 – Rank Cpu 7, Busy < 60, Queue < 1. 5, Swaps < 6 – Rank File $Data. Master. Accounts, Full < 80 Critical – Rank Disk $Data, Busy < 40 Info, Full < 90 Critical § Allow Dynamic Inclusion-Exclusion of Domains – Monitor Disk $Data 1, ON – Monitor Disk $Data 2, OFF – Monitor File $Data. Master. Accounts, ON – Monitor Process $Test, OFF 50

ASAP 2. 0 Features EMS Events § Discrete Object Thresholds - Availability Events – EMS Events now optionally Logged when DOTs objectives are not met. – Event Generation Options include §INFO §CRITICAL §REPEAT §DISPLAY § Burst Suppression on EMS events: – Eliminates Event Avalanches – Includes Burst Summary Reports 51

ASAP 2. 0 Features EDL Overview § ASAP R 2 Requirements… § Needed to allow extensible Entity Definitions – Allow Customers to define different Application Entities. – Allow Third Parties & EMFs access to Application Entities. § Needed to provide an entity-attribute Name-Space – Allow DOTs to use entity-attribute Names, instead of metric id#s. – Allow users to customize entity-attribute Names (internationalization) § Needed to reduce Maintenance – Provide Version Independent code (R 2 Client run against R 1 Server) – Reduce Source Code maintenance (Add new Entity w/o code change) 52

ASAP 2. 0 Features EDL Requirements § Needed to Externalize Definition & Customization of – Entity Names – Attribute Names – Help Text – Heading Text – Availability Vectors – Data Integrity Checks – State Determination Rules – Graph Normalization Values – Data Formatting & Alignment – Command required to retrieve data –… – and any other ASAP property that is related to Entity-Attribute definitions. 53

ASAP 2. 0 Features EDL Containers § Result - Entity Definition Language (EDL) File § EDL File provides “Container” for ASAP properties § EDL File allows ASAP properties to be “Portable”. – Provides Portable encapsulation of ASAP Properties. – Entities, attributes, and data can be “moved around”. – You can save/share different ASAP environments. – Client registers the. EDL extension with Windows. § EDL also allows DATA to be included in an EDL File. – Allows Data to be associated with Entity-Attribute definitions. – Entities, Attributes, & Data are encapsulated all together 54

ASAP 2. 0 Features EDL Features § EDL allows encapsulation of entire ASAP environment. § EDL Provides a way to – Have different sets of customized ASAP settings. – Save your current environment for later reference. – Mail your entire ASAP environment (with data) to others. – Share observed behavior with other ASAP users. § EDL also useful for – Problem Reporting - Capture entire environment. – Prototyping – Entity, Attribute, Data definitions. – Version Independence - due to encapsulation. – Education – Demo features of environment. – QA/Testing - Reproducing test scenarios. 55

ASAP 2. 0 Features EDL Summary § EDL Defines how Application Entities and Attributes relate to ASAP features, functions, and infrastructure. § Developers use EDL to define how to Monitor Availability § EDL is not something that ASAP users – Need to see, – Understand, – Or even be aware of… 56

ASAP 2. 0 Summary Availability Summary § Definition of Availability is subjective. It depends on how you intend to use object. § Studies indicate if you monitor Availability Actual object Availability is increased. . . § If Application Service Levels are not monitored, you will not know when Applications become unavailable. § ASAP provides both Availability monitoring, and Service-Level Objectives monitoring. 57

ASAP 2. 0 Summary Feature Summary § ASAP 2. 0 - Uniformly Extends Features to overall ASAP infrastructure § Allows concurrent Customer & 3 rd party access - Multi-Entity Apps § Adds Subsystem Monitoring - RDF, File, Process, Spooler, TMF, . . . § Adds Service-Level-Objectives – For both new & old entities § Adds Service-Level Events - Satisfying EMS Requirements § Adds Custom Icons, Colors, & Namespace - Internationalization § Adds Object State Change View – Allows reaching-back in time § Permits External Entity definitions - Entity Definition Language § Shifts Focus from that of system monitoring Point-Product to an Availability Monitoring Infrastructure for Subsystems and Applications. 58