HP NonStop ASAP QuickStart Guide Abstract HP NonStop™ Availability Statistics and Performance (ASAP) is an availability, state, and performance statistics collection infrastructure for the HP NonStop operating system and application resources. Product Version ASAP SE30V3.0 Supported Release Version Updates (RVUs) This manual supports D42.00 and all subsequent D-series RVUs, G06.00 and all subsequent G-series RVUs, and H06.
Document History Part Number Product Version Published 545871-001 ASAP SE30V3.
Table of Contents HP NonStop ASAP QuickStart Guide.................................................................................. 1 Abstract ........................................................................................................................... 1 Product Version ............................................................................................................... 1 Supported Release Version Updates (RVUs) ..................................................................
List of Figures and Tables Figure 1 - ASAP Client Main Window ................................................................................... 18 Figure 2 - ASAP Client Properties Sheet .............................................................................. 19 Figure 3 - ASAP Properties Sheet Entity Tab ....................................................................... 20 Figure 4 - ASAP Properties Sheet Attribute Tab ...................................................................
What’s New in This Manual New and Changed Information This is the first version of this Manual.
About This Manual This manual provides pointers and tips to quickly get NonStop ASAP installed and functional in a new environment. Audience The manual is intended for first time users of the NonStop ASAP product.
Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS Uppercase letters indicate keywords and reserved words.
[ ] Brackets Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list can be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines.
Punctuation Parentheses, commas, semicolons, and other symbols not previously described must be typed 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 type as shown. For example: "[" repetition-constant-list "]" Item Spacing Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma.
!i,o In procedure calls, the !i,o notation follows an input/output parameter (one that both passes data to the called procedure and returns data to the calling program). For example: error := COMPRESSEDIT ( filenum ) ; !i,o !i:i In procedure calls, the !i:i notation follows an input string parameter that has a corresponding parameter specifying the length of the string in bytes.
lowercase italic letters Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed.
% 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. For example: %005400 %B101111 %H2F P=%p-register E=%e-register Notation for Management Programming Interfaces This list summarizes the notation conventions used in the boxed descriptions of programmatic commands, event messages, and error lists in this manual.
Section 1: Introduction to Availability Statistics and Performance (ASAP) The Availability Statistics and Performance (ASAP) product provides an infrastructure for monitoring the availability and performance of HP NonStop servers and the applications that run on them. Before you start using ASAP you need to understand some of the terminology that ASAP uses. Please read this next section and refer to it when you run across a term that you don’t understand.
DISK The name of the DISK entity and also the command used to display DISK data in the ASAP CI. Domain The name of an object or device within a subsystem. For example $DATA might be the domain name for a disk device. EDL An acronym for the Entity Definition Language, a core set of instructions that tells ASAP how to operate. Entity The way ASAP refers to subsystems that it monitors.
command used to display ProcessBusy data in the ASAP CI. RANK A synonym for the GOAL command. RATE The ASAP rate defines the time interval at which ASAP wakes up to recompute attribute values for each of its entities. By default this value is set to 5 minutes, but it can be as low as 1 minute or as high as 60 minutes. There is a master ASAP Rate which applies to all entities. There is also a specific Rate that can be set on a by-entity basis that overrides the master rate.
Section 2: Installing ASAP When you receive your ASAP package you will receive 2 CDs. The first CD contains the ASAP Server component to be installed on your NonStop server(s) and the second contains the ASAP Client component to be installed on your Microsoft Windows™ workstations. ASAP is licensed separately for each NonStop server, but you can run ASAP Client on as many workstations as you need to without licensing ASAP for each workstation.
ASAP + START COLLECT + START \* Expand network -- to start the ASAP Collector -- to start the ASAP components on all nodes in the Installing and Starting ASAP Client To install ASAP Client do the following: 1. Load the ASAP Client CD into a CD drive on a workstation that can connect to your NonStop server collection node. 2. The Windows Installer application should automatically start. If it does not start, locate and double-click on the Setup.exe file on the CD. 3.
Section 3: Running ASAP Client Figure 1 below shows the main ASAP Client window. This is what you will see when you first start. There are many settings you can choose to customize ASAP Client, so please be sure to read the ASAP Client Manual or use the built-in help feature to learn more about all the settings that are available to you. This section will concentrate on some basic settings to get you started.
window to display the entity you selected. The OIL view becomes even more useful when you can navigate down to domains (objects) within each entity. You turn that capability on using the Properties sheet, which is the main configuration window within ASAP Client. To bring up the Properties sheet, click on the toolbar button pointed to by the bright green arrow or select View->Options from the top window menu. Figure 2 illustrates the Properties sheet.
Figure 3 - ASAP Properties Sheet Entity Tab Next click on the Attribute tab of the Properties sheet. Here things get a little more complicated but this is where you start to configure ASAP Client to exactly match your needs. There are two things you want to do on this tab: first you want to select the attributes you want to display; and second, you want to configure the y-axis of the the 3D graph of attribute values so that ASAP Client will alert at the proper utilization threshold.
graph (upper) portion of the ASAP Client main window. It should also be shown in the grid (lower) portion of the window. This will take some time, and will be an iterative process, but as you gain experience with ASAP Client, use the ASAP Properties sheet’s Attribute tab to tailor the attributes you want to display for each ASAP entity.
Figure 5 - Alerting on the COMM Rate value Figure 6 shows the Properties Sheet’s Attribute tab setting for the COMM Rate attribute. Here you can see that the Show in Graph (or y-axis) value is set to 20.
Figure 6 - COMM Rate Attribute Graphmax setting By typing in a new value of 50 for the Graphmax value (Figure 7) we can eliminate the red spike for that attribute (Figure 8).
Figure 8 - Graph display with Rate Graphmax set to 50 If an attribute is constantly alerting in your graph display(e.g., it’s always a red spike), then select the attribute and change the y-axis value to a more appropriate value for your environment by typing a new value into the field.
Section 4: Monitoring Objects The ASAP installation wizard (ASAPWIZ) helped you configure the startup settings for ASAP server, but that doesn’t mean ASAP is configured to provide you the information you need to manage your environment. It only means that ASAP has been primed so that you can configure it to manage your environment. The first thing you need to decide when using ASAP is the set of objects that you will monitor.
become active. Once you have defined your set of objects to be monitored, you can activate monitoring via a single COMMIT command. + COMMIT At this point ASAP will remove the non-existing CPUs (4-15), and will only report data on the CPUs that you are specifically monitoring, CPUs 0-3. When you enter a MONITOR command against any ASAP entity (subsystem), then you assume responsibility for the configuration for that entity.
Section 5: Setting Goals When you first start ASAP Server and Client and configure the set of objects you are interested in, ASAP will begin monitoring those objects and will display them in the ASAP Client. Optionally, you can also view data using the ASAP CI commands on your NonStop Server. We recommend that you run ASAP for a period of time before moving to this step, so that you better understand the performance profile of your objects.
GOAL CPU, BUSY < 90 This goal states that all CPUs on the system must be less than 90% busy. (Note: the best way to read a goal is to mentally insert the words “must be” before the logical operator. So in the case above, you would read it as “Busy MUST BE < 90”.) When this goal is set ASAP will create an alert on ASAP Client when any CPU reaches 90% busy or greater. It will also generate an EMS event if configured to do so. Goals are hierarchical.
Configuring ASAP Client for Host-Based Goals When you turn on a host-based goal using the GOAL command, you should configure ASAP Client to use that goal for alerting instead of the y-axis value in the graph window. You do this by returning to the ASAP Properties sheet’s Attribute tab, selecting the attribute and then selecting one of the 3 host-based option buttons: “Use Value..Graph Value”, “Use State..Graph Value” or “Use State..Graph State” in State Determination section.
in the graph will always represent the attribute that is alerting when this selected. Please see Figure 9 for an illustration of this setting for the CPU BUSY attribute. Figure 9 - Setting CPU BUSY to Use State..Graph State The next set of illustrations show how changing the State Determination setting will affect the Graph display.
Figure 10 - CPU Busy with the “Use Thresholds” setting Figure 11 below shows the same CPU Busy values using the “Use State…Graph Value” setting. In this case ASAP Client uses the state from ASAP Server to control highlighting but it is graphing the value of the attribute. While this view is accurate, it can be somewhat misleading since it is the low value for CPU 3 Busy that is highlighted because its goal wasn’t met.
Figure 11 - CPU Busy with the "Use State...Graph Value" setting Finally, Figure 12 below shows the same CPU Busy values using the “Use State…Graph State” setting. Here ASAP Client is using the state from ASAP Server to control highlighting and is also graphing the state value. This results in the most severe problem always being the highest bar in the graph.
Figure 12 - CPU Busy with the "Use State...Graph State" setting For ease of use you can select the All button next to “State Determination” to select all the state pair attributes for an entity and then with a single selection change them all to your selected state determination method.
Section 6: Automated Actions The GOAL command can also be used to define automated actions that ASAP will execute to fix a problem that might occur. Automated actions are an advanced topic and do not really belong in this QuickState Guide but are included here to show you that they can be defined. Please read about this capability in the ASAP Server Manual for more information.
Section 7: Getting Help! Hopefully this document has helped you get started with ASAP. However, if you need additional information please consult the ASAP Server manuals. You can also reference the ASAP website at http://www.NonStopASAP.com. There you will find examples, FAQs, presentations and other material that might be helpful. If you need further help please contact your local GMCSC.
