ASAP Migration Guide for NSX and OMF Users Abstract This guide introduces the Availability Statistics and Performance (ASAP) product to users of the Network Statistics Extended (NSX) and Object Monitoring Facility (OMF) products. It compares the features and functions of the three products to help these users prepare for migrating current monitoring configurations to ASAP 2.0. Product Version ASAP 2.0 Supported Releases This manual supports D42.00 and subsequent D-series releases, and G05.
Document History Part Number Product Version Published 520627-001 ASAP 2.0 September 2001 Ordering Information For manual ordering information: domestic U.S. customers, call 1-800-243-6886; international customers, contact your local sales representative. Document Disclaimer Information contained in a manual is subject to change without notice. Please check with your authorized representative to make sure you have the most recent information.
ASAP Migration Guide for NSX and OMF Users Tables What’s New in This Manual v Manual Information v New and Changed Information v About This Guide vii Who Should Read This Guide vii About ASAP Client vii About ASAPX vii Additional Information viii Your Comments Invited viii Notation Conventions viii 1. ASAP 2.0 Overview Supported Entities Comparison 1-1 ASAP 2.0 1-2 ASAP User Interfaces 1-2 Domains 1-3 Discrete Object Thresholds (DOTs) Entity Definition Language (EDL) 1-4 1-4 2.
2. ASAP Installation and Configuration (continued) Contents 2. ASAP Installation and Configuration (continued) Dynamic Configuration 2-4 Batch Configuration 2-5 2-5 Objectives DB 3. DOTs, EMS Events, and Other Features DOTs and EMS Events Sampling Rate 3-1 3-3 ASAPCONF File 3-3 Network Time Synchronization Network Statistics Collection 3-3 Persistence 3-4 3-4 A.
Tables Contents Tables Table 1-1. Supported Entities for OMF, NSX, and ASAP 2.0 1-1 Table 1-2. Domain Names 1-3 Table 2-1. Domain Autodiscovery for ASAP Entities Table B-1. OMFCOM Versus ASAP 2.
Contents ASAP Migration Guide for NSX and OMF Users —520627-001 iv
What’s New in This Manual Manual Information ASAP Migration Guide for NSX and OMF Users Abstract This guide introduces the Availability Statistics and Performance (ASAP) product to users of the Network Statistics Extended (NSX) and Object Monitoring Facility (OMF) products. It compares the features and functions of the three products to help these users prepare for migrating current monitoring configurations to ASAP 2.0. Product Version ASAP 2.0 Supported Releases This manual supports D42.
What’s New in This Manual New and Changed Information ASAP Migration Guide for NSX and OMF Users —520627-001 vi
About This Guide ASAP 2.0 is a new Compaq infrastructure for monitoring the availability of system and application objects. ASAP offers a rich, sophisticated infrastructure that functionally replaces the OMF and NSX products that previously monitored object state and performance. By the end of 2001, both NSX and OMF are officially unsupported and obsolete. Current NSX and OMF customers must transition to ASAP 2.0. This guide concentrates on NSX, OMF, and ASAP 2.
Additional Information About This Guide Additional Information ASAP 2.0 is not a direct replacement for NSX and OMF. ASAP brings a new set of features and capabilities that greatly enhances availability, performance, and state monitoring. Although this guide highlights many ASAP features, it does not provide complete, detailed descriptions of ASAP.
General Syntax Notation About This Guide UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name [ ] Brackets. Brackets enclose optional syntax items. For example: TERM [\system-name.
General Syntax Notation About This Guide Punctuation. Parentheses, commas, semicolons, and other symbols not previously described must be entered as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.#su-name Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must enter as shown. For example: "[" repetition-constant-list "]" Item Spacing.
Notation for Messages About This Guide Notation for Messages This list summarizes the notation conventions for the presentation of displayed messages in this manual: Bold Text. Bold text in an example indicates user input entered at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.00 You must press the Return key after typing the input. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up.
Notation for Management Programming Interfaces About This Guide % Percent Sign. A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number.
1 ASAP 2.0 Overview Topic Page Supported Entities Comparison 1-1 ASAP 2.0 1-2 ASAP User Interfaces 1-2 Domains 1-3 Discrete Object Thresholds (DOTs) 1-4 Entity Definition Language (EDL) 1-4 Supported Entities Comparison ASAP 2.0 and NSX use the term entities to describe classes of objects for which state, performance, and availability statistics are reported. OMF uses the term object types. Table 1-1. Supported Entities for OMF, NSX, and ASAP 2.
ASAP 2.0 ASAP 2.0 Overview ASAP 2.0 ASAP software provides a uniquely integrated, extensible infrastructure for monitoring the availability and performance of system and application objects. Both availability and performance information are integrated to form normalized availability vectors for monitored domains and associated properties. Information integration includes operational status, performance, and availability objectives for NonStop Kernel systems, subsystems, and abstract application domains.
Domains ASAP 2.0 Overview Domains In ASAP 2.0, a domain is a logical concept representing an object or group of objects to monitor. It applies to all entities. A domain can be a CPU number, disk volume, spooler supervisor name, subvolume name, and so on; for example: 03, $data, $spls, $db1.logfiles, respectively. In NSX and OMF, a domain is called an object name. Various entities require different approaches for monitoring and display of domain information.
Discrete Object Thresholds (DOTs) ASAP 2.0 Overview Table 1-2. Domain Names (page 2 of 2) Entity Domain Names— Configuration Domain Name—Display Comments RDF Chicago->NewYork Chicago>NewYork\Extractor\$ext1 Nodes involved with RDF Spooler $Spls $Spls\super\$spls $Spls\coll\$s $Spls\dev\$lpl $Spls\print\$p Supervisor name; subdomain display available System n.a.
2 ASAP Installation and Configuration Topic Page Installation 2-1 Startup and Shutdown 2-1 Configuration 2-2 Installation The ASAP 2.0 Server installation process is conceptually similar to NSX installation. ASAP 2.0 is an Independent Product distributed on two CDs, one containing the ASAP Client, the other containing ASAP Server. The IPSETUP process guides you through steps that transfer the ASAP Server files from the CD to your NonStop Kernel system.
ASAP Installation and Configuration ASAP ID and Suffixes ASAP ID and Suffixes To uniquely identify an ASAP environment, ASAP uses the concept of an ID. NSX also used this concept. All processes running in the same ASAP environment have names that begin with this ID followed by a unique suffix that identifies the component. The default ID is $ZOO. You can change the ID with the ASAP SET ID command. Once the ID is set, processes are automatically named at startup.
ASAP Installation and Configuration Adding or Deleting Domains In ASAP 2.0, for performance and multithreading purposes, most entities have a private SGP process that collects statistics. Before starting ASAP components on a node, you must decide which entities to enable. When you start ASAP, the ASAP Monitor starts the associated entity SGPs. To enable an entity, use the ASAP SET entity ON|OFF command.
ASAP Installation and Configuration Autodiscovery Autodiscovery In NSX, autodiscovery of objects was automatic. You had no control over which objects were monitored. In OMF, if the OMFDB database was not present, autoconfiguration occurred. For most object types, all objects discovered on the system were automatically added to the OMF configuration and monitored. ASAP 2.0 also offers automatic discovery of domains.
Batch Configuration ASAP Installation and Configuration Process \Asap Off - $Funds On - $Xyz + COMMIT The ASAP COMMIT command allows massive reconfiguration of objectives without forcing SGPs to incur overhead for each configuration change in the Objectives DB. When you use COMMIT, the SGPs pick up all your configuration changes at the next sample interval. The next statistics sample reflects those changes. The same dynamic configuration concept applies when you set objectives.
ASAP Installation and Configuration ASAP Migration Guide for NSX and OMF Users —520627-001 2 -6 Objectives DB
3 DOTs, EMS Events, and Other Features Topic Page DOTs and EMS Events 3-1 Sampling Rate 3-3 ASAPCONF File 3-3 Network Time Synchronization 3-3 Network Statistics Collection 3-4 DOTs and EMS Events In NSX, you could set thresholds on only some attributes of the CPU, Disk, Expand, and Process[Busy] entities. In OMF, you could set thresholds on a per-object basis, and decide what type of EMS event message was generated if the threshold was exceeded.
DOTs, EMS Events, and Other Features DOTs and EMS Events Valid Type Et Busy Busystate Queue Queuestate Disp Dispstate more attributes… In this CPU example, any attribute followed by an attribute with the same name plus the word "state" can accept objectives; for example, "Busy" followed by "BusyState". Objectives are set against the attributes, not the state; for example, Busy, Queue, Disp. Adding the state suffix to an attribute does not automatically make it a state pair.
DOTs, EMS Events, and Other Features Sampling Rate Sampling Rate In OMF, you set a sampling interval for each object type. It represented the retrieval frequency, in minutes, of the next set of statistics for each object in this object type. NSX had a concept of global RATE shared by all entities. Some specific entities could override this rate and specify their own. ASAP 2.0 follows the NSX model. A global rate value represents the frequency of the samples, in minutes.
DOTs, EMS Events, and Other Features Network Statistics Collection Network Statistics Collection The ASAP network statistics collection mechanism is similar to NSX. Each SGP sends its statistics to the ASAP Collector, which writes those statistics in the appropriate Enscribe DBentity file. There is one partitionable DB file per entity. Partitioning is a new feature in ASAP 2.0 that can help reduce the workload of specific DB files or store more ASAP statistics.
A ASAP Examples This Appendix presents various examples about how to start, shutdown, and configure ASAP using the command interface: Example Page Running ASAP A-1 Starting a Collector and a Three-Node Network A-1 Monitoring CPU A-2 Monitoring Disk A-3 Monitoring Expand A-5 Monitoring ExpandIP A-6 Monitoring File A-7 Monitoring Process A-8 Monitoring ProcessBusy A-9 Monitoring RDF A-10 Monitoring Spooler A-11 Monitoring System A-12 Monitoring Tape A-13 Monitoring TMF A-14 Run
Monitoring CPU ASAP Examples 3. View which entities are ON or OFF and start the ASAP Monitor on the first node: + SET + START \CHICAGO 4. Start the ASAP Monitor on the second node: + SET DISK OFF + SET SPOOLER ON + START \NEWYORK 5. Start the ASAP Monitor on the third node: + + + + + SET DISK ON, PARAM “RATE 5” SET TAPE ON SET SPOOLER OFF SET FILE OFF START \HOUSTON 6.
Monitoring Disk ASAP Examples On On On - 01 - 02 - 03 6. Display currently configured objectives in the Objectives DB of the local node: + RANK CPU 7. Set a global objective on the CPU BUSY attribute: + RANK CPU, BUSY < 80 8. Set a specific objective on the BUSY attribute for CPU 01, generate a critical EMS event when the objective is not met, and repeat the event at every sampling that the condition persists: + RANK CPU 01, BUSY < 90 CRITICAL REPEAT 9.
Monitoring Disk ASAP Examples 4. Review the list of domains: + MONITOR DISK Disk \Chicago On - $Data On - $System On - $Tools 5. Commit the changes, then see results at the next sample + COMMIT 6. Set global objectives, EMS event only for Qlen: + RANK DISK, FULL < 70, FULL > 10, BUSY < 40, QLEN < 1 INFO 7. Set a specific objective on the FULL attribute for $System, generate a critical EMS event when the objective is not met, and do not repeat the event: + RANK DISK $SYSTEM, FULL < 80 CRITICAL 8.
Monitoring Expand ASAP Examples Monitoring Expand 1. Display currently configured domains in the Objectives DB of the local node: + MONITOR EXPAND Expand \Chicago On - $Ipisld On - $Lhcomm On - $Lhcorp 2. Start monitoring $Lhchi (all Expand domains are automatically monitored by default, so adding them to the Objectives DB is not mandatory): + MONITOR EXPAND $Lhchi 3. Review the list of domains: + MONITOR EXPAND Expand \Chicago On - $Ipisld On - $Lhchi On - $Lhcomm On - $Lhcorp 4.
Monitoring ExpandIP ASAP Examples 10. List the attributes of the EXPAND entity: + SHOW EXPAND You can set objectives on any attribute with a state pair; for example, Pool, Pfail, Nobuf, Bcc, NakSnt, and so on. Monitoring ExpandIP 1. Display currently configured domains in the Objectives DB of the local node (all ExpandIP domains are really Expand domains. ASAP does not require you to know which type of transport the Expand line is using.
Monitoring File ASAP Examples 8. Display currently configured objectives in the Objectives DB of the local node: + RANK EXPAND Expand \Chicago Dframsnt < 1000 Info NoDisplay 9. Commit the changes to see results at the next sample: + COMMIT 10. List the attributes of the EXPANDIP entity: + SHOW EXPANDIP You can set objectives on any attribute with a state pair; for example, Dframsnt, Dframrvd, Dbytesnt, and so on. Monitoring File 1.
Monitoring Process ASAP Examples 7. Set specific objectives and generate EMS events: + RANK REPEAT + RANK + RANK rwep = FILE $System.system.userid, owner = “255,255” CRITICAL FILE $Data.logfiles, files < 50 CRITICAL FILE $Build.sources, owner = “66,50” critical repeat, “nuuu” 8. Display currently configured objectives in the Objectives DB of the local node: + RANK FILE File \Chicago Full <= 85 $Build.Sources Owner = 66,50 Rwep = Nuuu $Data.Logfiles Files < 50 $System.System.
Monitoring ProcessBusy ASAP Examples 5. Stop monitoring $Zip, but keep the domain in the Objectives DB: + MONITOR PROCESS $Zip, OFF + COMMIT 6. Display currently configured objectives in the Objectives DB of the local node: + RANK PROCESS 7. Set specific objectives and generate EMS events: + RANK PROCESS $System, pri = 220 CRITICAL REPEAT + RANK PROCESS $Pr01, pri >= 150 CRITICAL, mpages < 225 INFO REPEAT + RANK PROCESS $Pr01, cpu=1, bcpu=2 8.
Monitoring RDF ASAP Examples 4. Commit the changes to see results at the next sample: + COMMIT 5. Display currently configured objectives in the Objectives DB of the local node: + RANK PROCESSBUSY 6. Set global objectives with no EMS events: + RANK PROCESSBUSY, pages < 50, busy < 90 7. Set a specific objective with no EMS events: + RANK PROCESSBUSY 0, pages < 35 8.
Monitoring Spooler ASAP Examples 5. Display currently configured objectives in the Objectives DB of the local node: + RANK RDF 6. Set global objectives and generate EMS events: + RANK RDF, rtdtime < 2 CRITICAL REPEAT + RANK RDF, pcpu = 2 CRITICAL, bcpu = 3 CRITICAL, priority = 185 INFO REPEAT 7.
Monitoring System ASAP Examples 6. Set global objectives and generate EMS events: + RANK SPOOLER, numlocs < 75 INFO REPEAT, numlocs >= 1 INFO REPEAT + RANK SPOOLER, fullpct <= 80 CRITICAL REPEAT 7. Set specific objectives and generate EMS events: + RANK SPOOLER $spls\coll, holdjobs < 150 CRITICAL REPEAT + RANK SPOOLER $spls\coll, openjobs < 45 INFO REPEAT 8.
Monitoring Tape ASAP Examples 5. Display currently configured objectives in the Objectives DB of the local node: + RANK SYSTEM System \Chicago Queue Chit Disp Tle < < <= <= 10 100 1000 70 Info Info Critical Critical Repeat Repeat Repeat Repeat 6. Commit the changes to see results at the next sample: + COMMIT 7. List the attributes of the SYSTEM entity: + SHOW SYSTEM You can set objectives on any attribute with a state pair; for example, Busy, Queue, Disp, Disk, Chit, and so on. Monitoring Tape 1.
Monitoring TMF ASAP Examples 8. Display currently configured objectives in the Objectives DB of the local node: + RANK TAPE Tape \Chicago Mountreq < Mounttime < $Dat Mounttime < 1 5 Critical Repeat Critical Repeat 2 Critical Repeat 9. Commit the changes to see results at the next sample: + COMMIT 10. List the attributes of the TAPE entity: + SHOW TAPE You can set objectives on any attribute with a state pair; for example, Pcpu, Bcpu, Mountreq, Mounttime, and so on. Monitoring TMF 1.
Monitoring TMF ASAP Examples 7. Set specific objectives and generate EMS events: + RANK TMF TRANSACTIONS, duration < 30 CRITICAL REPEAT 8. Display currently configured objectives in the Objectives DB of the local node: + RANK TMF Tmf \Chicago Ovflw Hung Trans Transactions Duration = No = No <= 100 Critical Repeat Critical Repeat Info Repeat < Critical Repeat 30 9. Commit the changes to see results at the next sample: + COMMIT 10.
Monitoring TMF ASAP Examples ASAP Migration Guide for NSX and OMF Users —520627-001 A -16
B OMFCOM Versus ASAP 2.0 Commands This Appendix provides a guide to understand how the old OMFCOM commands can now be achieved in ASAP 2.0 command interpreter: • • Only entities supported by OMF are listed. ASAP 2.0 supports other entities that are not in this table. Additional functions in ASAP 2.0 that are not related to any OMFCOM commands are not in this table. Table B-1. OMFCOM Versus ASAP 2.0 Commands (page 1 of 3) Function OMFCOM ASAP 2.
OMFCOM Versus ASAP 2.0 Commands Table B-1. OMFCOM Versus ASAP 2.0 Commands (page 2 of 3) Function OMFCOM ASAP 2.
OMFCOM Versus ASAP 2.0 Commands Table B-1. OMFCOM Versus ASAP 2.0 Commands (page 3 of 3) Function OMFCOM ASAP 2.
OMFCOM Versus ASAP 2.
C Configuring ASAP Similar to OMF This Appendix provides two file samples that let you configure ASAP to match many of OMF default settings: File Description Page OMFOBJS Objectives file C-2 ASAPCONF Global settings file C-3 • • OMFOBJS—Objectives file ASAPCONF—Global Settings file You can modify these two files to your convenience. The samples given below provide a base upon which other settings and/or objectives can be added, modified or deleted. 1.
OMFOBJS Sample File Configuring ASAP Similar to OMF OMFOBJS Sample File !------------------------------------------------------! ASAP Objectives matching many OMF default settings !------------------------------------------------------! CPU Rank CPU, Busy < 90 Critical ! Disk Rank Disk, Full < 90 Critical ! Objectives on disk primary cpu and paths (Listdev) Rank Disk $System, cpu = 1 Critical Rank Disk $System, P = "P" Critical Rank Disk $System, M = "B" Critical ! Add objectives for other disks here
ASAPCONF Sample File Configuring ASAP Similar to OMF ASAPCONF Sample File !-------------------------------------------------------! ASAPCONF Settings matching many OMF default settings !-------------------------------------------------------! Uniquely identify this environment Set ID $ZOO Set DB $System.Zasap.Db Set ObjectivesDB $System.Zasap.DbObjs Set Asaplog $System.System.Asaplog Set EDL $System.System.
Configuring ASAP Similar to OMF ASAPCONF Sample File ASAP Migration Guide for NSX and OMF Users —520627-001 C- 4
