READ THIS FILE COMPLETELY BEFORE BEGINNING PRODUCT INSTALLATION Copyright 2001 Compaq Computer Corporation Product Name: ASAP Server Marketing Product ID: SE30V2 Component Products T0402V02 I. Basic Product Installation Instructions 1. Ensure that requirements for using this product are met (see Section IV Product Requirements below). 2. Ensure that prerequisites for the installation utility and any product-specific installation requirements are met (see Section V Installation Prerequisites below). 3. Review the file USRGUIDE.PDF (in the subdirectory NSK_SW on this CD) containing the IPSetup User Guide, which provides instructions for using IPSetup, a utility provided on the CD that enables installation of Independent Products. You need Adobe Acrobat Reader (available on this CD) to read or print the IPSetup User Guide. 4. Decide whether you will use DSM/SCM to move files to Installation Subvolumes (ISVs) after files are placed on the workstation. Using DSM/SCM is optional, but is recommended when DSM/SCM is available. 5. Follow the pre-installation instructions in Section II below, if any, before continuing to Step 6. 6. Run IPSetup to place (move files from the CD to the workstation) and install (move NonStop Kernel files to correct ISVs) this product. If TCP/IP and FTP are unavailable, or if you have problems with automatic file placement, use the instructions in the IPSetup User Guide section "Manual Software Placement Using the IPSetup TACL Program" to manually place NonStop Kernel files. 7. Follow the post-installation instructions in Section III below, if any, after using IPSetup to place and install this product. II. Pre-Installation Instructions None III. Post-Installation Instructions 1) Invoke the INSTALL^TEMPLATES TACL macro to install this NPV's EMS template file(s) in the running system. This TACL macro and instructions for its use are given in Support Note S92067B. The INSTALL^TEMPLATES TACL macro is distributed on the SUT and can be located in the ISV volume: $.ZINSAIDS.TACLMACS. To print the usage notes, LOAD the file containing the macro and, at the TACL prompt, enter: INSTALL^TEMPLATES /OUT /HELP 2) Run ASAP setup to update the ASAP subsystem with the following commands: a) TACL 1 > VOLUME $.ZASAP b) TACL 2 > OBEY INSTALL c) Perform "Full Install on this node" from the central ASAP database node. d) Perform "Remote Monitor Install" for any additional Licensed ASAP nodes that you wish to monitor. See Section 2 of the ASAP manual for detailed information regarding subsystem configuration. e) If you are using the same volume and subvolume location for the ASAP database files, you must delete the ASAP version 1 database files before starting the ASAP Version 2 environment. IV. Product Requirements Required Hardware: NonStop servers Minimum OS Release: NonStop Kernel release D42.00 or higher NonStop Kernel release G05.00 or higher Required Software: T9057D40^ADE or T9057G02^ADY , T9086D40^ACE or T9086G02^ABS , T9117D40^AAW or T9117G02^AAV, T6028D42^AAT Disk Space Requirement: ZASAP subvol 9.0MB $System.system run time files 7.0MB ASAP Dictionary files 1.1MB Refer to the section 2 of the ASAP manual for ASAP database file sizes. Memory Requirement: 16MB per cpu minimum. V. Installation Prerequisites Required Hardware: Tandem NonStop server Communications controller allowing file transfer from PC to Tandem PC with 486 or higher processor and all of the following: CD-ROM drive VGA or higher-resolution video adapter and monitor Microsoft Mouse or similar pointing device Communications controller allowing file transfer from PC to Tandem Required Software: T9550D30 SOCKET LIBRARY or higher version T9552D30 TCP/IP FTP with IPM ABG or superseding IPM (for releases D31.00 to D40.00) T9552D40 TCP/IP FTP with IPM ABJ or superseding IPM (for releases D40.01 and higher) Microsoft Windows 95, or Windows NT 4.0 or later Microsoft TCP/IP stack and FTP client VI. Manuals Included On this CD 422770 ASAP SERVER VII. CD-ROM Root Directory Contents AUTORUN.INF File containing CD AutoRun commands AXDIST.EXE Microsoft redistributable libraries file. IPSETUP.CNT File containing help contents for the CD installation utility IPSetup. IPSETUP.EXE File containing the main executable for IPSetup. IPSETUP.HLP File containing help text for IPSetup. LICENSE.TXT File containing limited-use Software Licensing Agreement with the licensing terms governing this product. README.TXT File containing product and installation information (this file). SETUP.EXE File containing the Launcher executable. NSK_SW Subdirectory containing NonStop Kernel component files, including installation utilities and instructions. CD_DOCS Subdirectory containing product documentation in the following two subdirectories: TIM_COLL Subdirectory of CD_DOCS containing product manuals formatted for the Tandem Information Manager (TIM) viewer. PDF_DOC Subdirectory of CD_DOCS containing: 1. Product manuals in PDF format for viewing with Adobe Acrobat Reader 2. ACROBAT_VIEWERS subdirectory containing Adobe Acrobat Reader for DOS, OS/2, Windows, Windows NT, MacOS, Sun OS, Solaris, HP-UX, IBM AIX, and SGI IRIX. ADDENDUM Overview: Compaq Availability Stats And Performance (ASAP) provides an availability monitoring infrastructure for an entire network of NonStop servers. ASAP monitors the availability and performance of both system and application objects. System information includes the operational status and performance of NonStop Kernel subsystems. Subsystems monitored include Cpu, Disk, Expand, File, Process, ProcessBusy, RDF, Spooler, System, Tape, and TMF. Application information can include virtually any user-defined availability statistics. Applications participate in the ASAP environment by using the ASAPX API. ASAP 2.0 provides numerous additional features. For details, see below. New Feature History: ==================== 2.0 ASAP 2.0 includes many new system entities. This includes: Expand, File, Process, ProcessBusy, RDF, Spooler, TMF, and Tape. For complete descriptions, see new LH, File, Process, ProcessBusy, RDF, Spooler, TMF, and Tape commands. 2.0 ASAP 1.0 System entities such as Cpu, Disk, Expand, ProcessBusy, and System have been enhanced to provide new availability vector information. 2.0 ASAP 2.0 includes a new Entity Definition Language (EDL). EDL provides a mechanism to define abstract application entities and associated property attributes. Note that EDL is used to define both application and system entities. For example all of the system entities are also defined using the new EDL. For more information, see ASAP Client EDL - Interactive Development Environment, and ASAP Client TIM manual. 2.0 ASAP 2.0 EDL allows multiple application entity definitions. This allows multiple applications to have totally different entity schemas, property names, and thresholds. 2.0 Unlike release 1.0, ASAP 2.0 allows you to selectively control which objects or sets of objects are monitored. For Example: MONITOR CPU 0 MONITOR CPU 1 MONITOR DISK $DATA1 MONITOR DISK $DATA2 MONITOR EXPAND $LHCHI MONITOR FILE $SYSTEM.SYSTEM.USERID MONITOR FILE $DATA.SUBVOL MONITOR PROCESS $XYZ MONITOR RDF \CHI->\NYC For more information, see the ASAP command interpreter HELP MONITOR command. 2.0 ASAP 2.0 includes the ability to set complex Discrete Object Thresholds (DOTs) on individual objects, or on subsets of objects. This capability applies to all ASAP entities, and unlike release 1.0 includes both system and application objects. For more information, see ASAP command interpreter HELP MONITOR and HELP RANK commands. 2.0 ASAP 2.0 provides new user controlled "Availability" events on all Discrete Object Thresholds (DOTs). For more information, see HELP RANK command. 2.0 The ASAP database can now be partitioned across multiple volumes on the collection node. New options have also been added to allow user specified primary/secondary extent sizes, and to control the maximum number of extents. For more information, see HELP SET PARTITION. 2.0 Many ASAP 1.0 features that were only available to the APP entity, now also apply to all system entities. As a result, many ASAP 1.0 ASAPX commands have been moved to the ASAP 2.0 command interpreter. 2.0 New Burst suppression features have been added to suppress duplicate ASAPLOG and EMS events. 2.0 Expand now supports the following new Expand transports: ATM, Servernet, and SNA. A new Expand option "IP" was added to display new counters for Expand lines using ATM or TCP/IP as the transport. 2.0 ASAP 1.0 SGP (Stats Gathering Process) data is now supported and automatically remapped into the ASAP 2.0 Database. The Asap 2.0 server can now run in mixed environments with ASAP version 1 and version 2 SGP servers. Note that the ASAP Collector must be version 2.0 in order to run in a mixed environment. 2.0 The ASAP 2.0 CPU SGP now supports 4GB memory modules. Problems Corrected History: =========================== 2.0 ASAP CI corrected a possible formatting problem with data counters rolling over to an adjacent field. 2.0 Corrected Expand multiline IP problems. 2.0 Processbusy corrected to display $disk device name instead of DP2 object "TSYSDP2" 2.0 CPU,RAW,AVG and CPU,AVG,TYPE corrected to display correct cputype and correct CPU state. Known Problems Remaining: ========================= 2.0 Burst suppression report summary does not always report after the suppression interval (Loginterval) has expired. 2.0 The children nodes of a TMF distributed transaction are not displayed. 2.0 Under certain conditions, a duplicate record is written to the ASAP collector at startup in both the File and TMF SGP's. 2.0 Status monitor command can time out when SGP's take too long to report status information. 2.0 Asap 2.0 does not support multiple collector access to the same database.