Download
asap 2 0 discrete object thresholds dots n.
Skip this Video
Loading SlideShow in 5 Seconds..
ASAP 2.0 Discrete Object Thresholds (DOTs) PowerPoint Presentation
Download Presentation
ASAP 2.0 Discrete Object Thresholds (DOTs)

ASAP 2.0 Discrete Object Thresholds (DOTs)

152 Vues Download Presentation
Télécharger la présentation

ASAP 2.0 Discrete Object Thresholds (DOTs)

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. ASAP 2.0 Discrete Object Thresholds (DOTs) September 17, 2001 Joe.Davis@hp.cm

  2. ASAP 2.0 DOTs • Monitored Domains • Objectives • Events

  3. Controlling Monitored Domains • ASAP auto-configuration • All objects • CPU, DISK, PROCESSBUSY, RDF, TAPE, TMF • Selected objects • FILE - ASAPMON • PROCESS - $<ASAP-id>M • SPOOLER - $SPLS • DOTs lets you control the domains (objects) that ASAP monitors • Monitored objects support is encapsulated in the ASAP MONITOR command

  4. Taking Ownership • When you add an object (domain) to be monitored, you are assuming control of the ASAP configuration for that entity • MONITOR DISK $DATA • Only $DATA will be monitored • MONITOR DISK $DATA, OFF • No “ON” records, but records do exist • No disks will be monitored • MONITOR DISK $DATA, DELETE • ASAP auto-configures all disks again

  5. Commit Processing • MONITOR (and RANK) commands add records to the Objectives database, not to a running copy of ASAP • Database is read at ASAP startup time • Database is re-read online by a running ASAP component when it receives a COMMIT request • Two ways to commit monitored objects • MONITOR <entity>, COMMIT • COMMIT

  6. The Objectives Database • To set the objectives database file name • SET OBJECTIVESDB • To turn on auditing of the objectives database • SET OBJECTIVESAUDIT • MONITOR (RANK) commands ask ASAPMON for the Objectives database file name • To change to database from ASAP CI, change the ASAP ID, not OBJECTIVESDB • Only if ASAPMON is not running or does not respond is the file specified in the SET OBJECTIVESDB used

  7. The Objectives Database SET ID $SG SET OBJECTIVESAUDIT ON SET OBJECTIVESDB $mm.joedb.testme +m expand Opened ObjectivesDB: \Centdiv.$Mm.Joedb.Testme Expand \Centdiv On - $Abc +set objectivesdb $system.zasap.dbobjs +m expand Expand \Centdiv On - $Abc + ASAPMON $SGM returned this name New database is not opened !

  8. The Objectives Database SET ObjectivesDB $mm.joedb.testme +m expand Opened ObjectivesDB: \Centdiv.$Mm.Joedb.Testme Expand \Centdiv On - $Abc +set id $zoo +m expand Opened ObjectivesDB: \Centdiv.$System.Zasap.Dbobjs Expand \Centdiv On - $Lhchi On - $Lhcomm On - $Lhdome On - $Lheast + New database is opened !

  9. The Objectives Database • The Objectives database is distributed, it resides on each node monitored by ASAP • The database on a node contains information for objects on its node +m process $abc Opened ObjectivesDB: \Centdiv.$Mm.Joedb.Testme Process \Centdiv.$Abc, On +m process \dome.$abc Opened ObjectivesDB: \Dome.$Mm.Joedb.Testme Process \Dome.$Abc, On +

  10. MONITOR Command MONITOR [<entity>|*][\<node>] ,COMMIT [[.| ][<domain>]],ADD [,OFF ] ,ON ,OFF ,DELETE ,INFO [,DETAIL ] [,OBEYFORM] ,DETAIL ,OBEYFORM ,LIST [,DETAIL ] ,REMOVE [,FORCE ]

  11. Domain name space NODE is not supported • CPU <cpu-number> • DISK $<disk-device-name> • EXPAND [Path\|Line\]$<line-name> • FILE $<subvolume-name>|$<file-name> • PROCESS $<process-name> • PROCESSBUSY <cpu-number> • RDF <node1><node2> (no backslashes) • SPOOLER $<supervisor-name> • SYSTEM n/a • TAPE $<tape-device-name> • TMF AUDITDUMP | AUDITTRAIL | TMF | TRANSACTION

  12. MONITOR Command • ADD [, OFF] • Adds an object to the Objectives database • Automatically turns object ON (unless OFF) • The default when a domain name is specified without wildcards • ON • Turns an object in the database ON • OFF • Turns an object in the database OFF • COMMIT • Commits database changes to a running copy of ASAP

  13. MONITOR Command • DELETE • Deletes a domain from the Objectives database • Commands must be entered twice to delete non-specific domains • INFO [, DETAIL | OBEYFORM ] • Displays information about domains in the database • DETAIL • Displays ADD, ON and OFF times for domain(s) • OBEYFORM • Outputs domains in Obey format for replay

  14. MONITOR Command • LIST [, DETAIL] • Returns information about domains directly from running ASAP components • DETAIL returns subsystem-specific detailed information about domains • Also supported for user-defined entities • REMOVE [, FORCE] • For user-defined entities only • Removes DOWN domains from ASAPX • FORCE forces removal of a domain regardless of its state

  15. MONITOR Examples • MONITOR CPU 2 • MONITOR DISK $DATA • M EXPAND $EX23 • M FILE $SYSTEM.SYSTEM, ADD, OFF • M PROCESS \REMOTE.$ZTC0 • M PROCESSBUSY \REMOTE.2 • M RDF CHICAGODENVER • M SPOOLER $S2LS • M SYSTEM • M TAPE \REMOTE.$TAPE3 • M TMF AUDITTRAIL

  16. MONITOR Examples • MONITOR CPU *,INFO • MONITOR ATM, LIST, DETAIL • MONITOR ATM CHICAGO\TEST\ATM24, REMOVE • M EXPAND \REMOTE • M FILE \REMOTE.*, OFF • M PROCESS \REMOTE.CPU *,DELETE • M PROCESS \REMOTE.CPU *,DELETE (enter twice)

  17. Objectives • DOTs provides the ability to set up to 6 discrete objectives on any system or user-defined attribute where StatePair is YES in EDL, and where the attribute is not the StateIsOp attribute • The attribute must be immediately followed by an associated state attribute in the EDL file • Objectives processing is encapsulated in the ASAP RANK command

  18. RANK Command • Use the RANK command to establish discrete objectives • RANK DISK, BUSY < 35 • Sets a global objective for all disks • Disks must be less than 35 percent busy • RANK DISK $BR, BUSY < 50 • Sets a specific objective on $BR • $BR must be less than 50 percent busy

  19. RANK Command +ra disk,busy < 35 Disk \Centdiv Busy < 35 WARNING - Use COMMIT to place database changes into production use. +ra disk $br, busy < 50 Disk \Centdiv.$Br Busy < 50 +co Disk \Centdiv objective(s) committed. +

  20. RANK Command RANK [<entity>|*][\<node>] ,COMMIT [.| ]][<domain>]],<rankspec> [,<rankspec>,...] ,LIKE <domain> ,ACTIVATE ,DEACTIVATE ,DELETE ,INFO [,OBEYFORM ] ,OBEYFORM ,LIST

  21. RANK Command • <rankspec>, <rankspec>, ... <attr> <oper> [<val>] [,INFO | CRITICAL [,REPEAT] [,NODISPLAY]] STATUS [,INFO | CRITICAL [,REPEAT] [,NODISPLAY]] STATUS [,NOEMS] • <attr> • The name of an attribute name as defined in ASAP EDL for the entity. The attribute must be defined with StatePair Yes and it cannot be the StateIsOp attribute. • <oper> • One of the 6 operators, >, <, =, <>, >=, <=. • <val> • The objective value • Depends on the attribute data type

  22. RANK Command • STATUS • The StateIsOp attribute as defined in EDL. • Can only be used with EMS control keywords. • Cannot be used to set objectives on the value of Status. • RANK CPU, STATUS = “UP” is invalid! • Is used to change the default behavior for event generation for status changes of system domains. • Is used to turn on and define event generation for status changes in user-defined domains.

  23. RANK Command • INFO • Generate an Info event if the objective is not met • CRITICAL • Generate a Critical event • REPEAT • Repeat the event for each interval the alert persists. • NODISPLAY • Suppress event display on the console. • NOEMS • Used only with the STATUS attribute. • Stops display of Status events for System entities.

  24. RANK Command • ACTIVATE • Activates a domain(s) which was previously deactivated • COMMIT • Commits database changes to a running ASAP • DEACTIVATE • Deactivates a domain (DOTs returns OEM State 1) • DELETE • Deletes a record from the Objectives database • Commands must be entered twice to delete non-specific domains

  25. RANK Command • INFO [, OBEYFORM] • Displays objectives information from the database • LIKE <domain> • Adds ranking for a domain like <domain> • Specific ranks follow LIKE • LIST • Lists actual in-use objectives for a domain from a running ASAP component(s) • Fully qualified domain names only • OBEYFORM • Outputs information is Obey file format for replay

  26. RANK Examples • RANK CPU, BUSY > 10, BUSY < 90 • RANK FILE $SYSTEM.SYSTEM.USERID, RWEP = “OOOO” • RANK PROCESS $ABC, PSTATE = RUNNABLE • RANK SPOOLER $SPLS\COLL\$S,FULLPCT < 80 • RANK TMF • RANK TMF, STATUS NOEMS • RANK SPOOLER, STATUS CRITICAL REPEAT • RANK ATM CHICAGO\$ATM2, STATUS CRITICAL REPEAT • RANK DISK $DATA, LIST

  27. Objectives - Thresholding • Out-of-box defaults are UseThreshold • GraphMax and Threshold sliders determine alerting

  28. Discrete Objectives • Must turn OFF “Use Thresholds” • Must turn ON “Use State - Graph State” or “Use State - Graph Value” • May use the State Determination ALL button

  29. Objectives - Standard Ranking

  30. 0-5% 6-14% 15-24% 35-44% 25-34% > 44% Objectives - Percent Ranking

  31. Objectives - Historical Ranking • Uses Percent method and the last state reported • Minor problems increase in alerts levels over time if they persist

  32. Events • By default DOTs will generate an EMS CRITICAL event for any System object for Status changes, IF • events are turned on • SET OBJECTIVESEVENT ON • Default is OFF due to richness of ASAP Client displays • the operational state is greater or equal to event state • SET OBJECTIVESEVENTSTATE <state> • Default is CRITICAL (state 7) resulting in CRITICAL and DOWN Status events • maximum events haven’t already been written • SET OBJECTIVESEVENTMAX <n> • Default is 1

  33. Events • DOTs will generate an EMS INFO or CRITICAL event when an attribute fails to meet an objective, IF • events are turned on • SET OBJECTIVESEVENT ON • the state is greater or equal to event state • SET OBJECTIVESEVENTSTATE <state> • maximum events haven’t already been written • SET OBJECTIVESEVENTMAX <n> • the objective was specified using event keywords • RANK DISK $DATA, BUSY < 40CRITICAL • the event wasn’t already written in a prior interval • INFO | CRITICAL [ REPEAT ]

  34. Events - Other Controls • To generate UP events for repaired attributes • SET OBJECTIVESEVENTUP ON • Default is OFF • To suppress display of DOWN events on the console • SET OBJECTIVESEVENTCONSOLE OFF • Default is ON • To suppress display of UP events on the console • SET OBJECTIVESEVENTCONSOLEUP OFF • Default is ON

  35. Events Examples • ASAPCONF file • SET OBJECTIVESEVENT ON • SET OBJECTIVESEVENTUP ON • SET OBJECTIVESEVENTMAX 2 • SET OBJECTIVESEVENTSTATE WARNING • RANK Examples • RANK CPU, BUSY < 99 CRITICAL REPEAT • RANK CPU, STATUS CRITICAL REPEAT • RANK CPU, QUEUE < 2 INFO • RANK PROCESS $XYZ, STATUS NOEMS