READ THIS FILE COMPLETELY BEFORE BEGINNING PRODUCT INSTALLATION Copyright 2007 HP Product Name: ASAP Server Product ID: HSE30V2.8 H-series SE30V2.8 G-series Component Products: 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 will need Adobe Acrobat Reader to read or print the IPSetup User Guide. Visit Adobe's website to download the latest Adobe Acrobat Reader: http://www.adobe.com 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. This product contains both NonStop Kernel components and workstation components. You must place each component type separately. To restart the installation program after placing the first component type, click SETUP.EXE in the root directory. 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 1. If you are using the ASAP Extension make a copy of the file $SYSTEM.SYSTEM.ASAPUSER. FUP - VOLUME $SYSTEM.SYSTEM - DUP ASAPUSER, ASAPSAVE.*, SAVEALL 2. If you are upgrading from ASAP 2.4 or an earlier release to ASAP 2.7 then this SPR includes a change to the Objectives database file and also includes EDL changes for several entities. All records in any old ASAP databases need to be saved prior to installing this version of ASAP. It is very important that you save the records using the old version of ASAP, then restore them using the new version of ASAP. Please follow these instructions to save your current ASAP databases. From the central ASAP collection node: TACL> ASAP +VOLUME $SYSTEM.ASAPSAVE +MONITOR/OUT ASAPOBEY/, OBEYFORM +RANK/OUT ASAPOBEY/, OBEYFORM +MONITOR/OUT ASAPOBEY/ \, OBEYFORM +RANK/OUT ASAPOBEY/ \,OBEYFORM (preceding commands must be done for each remote node) Once data from all nodes has been saved then shutdown ASAP and purge the ASAP objectives database on each node. The objectives database file location is set with the SET OBJECTIVESDB command, or it defaults to $SYSTEM.ZASAP.DBOBJ. 3. Save ASAP CI and all EDL files if you have archived data with the old version of ASAP that you might want to view later. FUP - VOLUME $SYSTEM.SYSTEM - DUP ASAP, ASAPSAVE.*, SAVEALL - DUP ASAP2EDL, ASAPSAVE.*, SAVEALL - DUP ASAP2SYS, ASAPSAVE.*, SAVEALL - DUP ASAP2APP, ASAPSAVE.*, SAVEALL 4. 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. 5. Follow the post-installation instructions in Section B below, if any, after using IPSetup to place and install this product. 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. f) If you saved ASAP database records prior to the install then reload them now. From the same central node that you saved the data on please enter: ASAP + OBEY $SYSTEM.ASAPSAVE.ASAPOBEY 3. If you are using the ASAP Extension copy the duplicated file from the Pre-Installation instructions Step 1 back to $SYSTEM.SYSTEM. FUP - VOLUME $SYSTEM.ASAPSAVE - DUP ASAPUSER, SYSTEM.*, PURGE, SAVEALL 4. Start the new ASAP version. 5. When looking at ASAP data from earlier ASAP versions please be sure to use the old ASAP CI and EDL files saved to the $SYSTEM.ASAPSAVE subvolume if you performed the save step defined above. IV. Product Requirements Required Hardware: HP Integrity Servers Minimum OS Release: NonStop Kernel release H05 or higher Required Software: T0346H01 If using RDF T6965H01^AAJ (see note) Note: T6965: The function needed in T6965 is required only if you SET ACTION ON. 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: HP NonStop Server Communications controller allowing file transfer from PC to HP NonStop Server 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 HP NonStop Server 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 for this CD: To access the documentation for this product, please see the HP NonStop Technical Library at www.hp.com/go/ntl or your NonStop Technical Library CD/DVD disc VII. CD-ROM Root Directory Contents AUTORUN.INF File containing CD AutoRun commands. AXDIST.EXE Microsoft redistributable library files. 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. WS_SW Subdirectory containing workstation component files (if applicable to this product), including installation utilities if any. SOFTDOCS Subdirectory containing all Initial Product Version / Product Version Update Softdocs. ADDENDUM Overview: The 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 Comm, Cpu, Disk, Expand, File, Process, ProcessBusy, RDF, Spooler, System, Tape, and TMF. The optional TCPIP plug-in monitors 12 new TCP/IP and Telserv entities, and 600 new attributes. Application information can include virtually any user-defined availability statistics. Applications participate in the ASAP environment by using the ASAPX API. New Feature History: ==================== 2.8 ASAP now supports the optional ASAP TCP/IP Plug-in. The TCP/IP SGP monitors 9 new TCP/IP entities and 3 new TELSERV entities. For TCP/IP, the ASAP TCP/IP Plug-in monitors the ICMP, IP, TCP, QIO, RTE and UDP layers of the TCP/IP stack, and also monitors TCP/IP Ports, Routes and Subnets. For TELSERV, the new Plug-in monitors TELSERV Processes, Services and Windows. Taken together the new Plug-in provides a never seen before real-time view of the TCP/IP and TELSERV activity on NonStop Servers. See product SE35V1 for more information on the ASAP TCP/IP Plug-in. 2.8 The CPU SGP reports on the number of Blades that are active and objectives can be set on active Blades count using the GOAL command. For example: GOAL CPU, BLADES = 3 -- Sets objective for TMR system. When the objective is met the client displays Blades as "A B C". When the objective is not met because Blade B is down the client displays Blades as "A C". GOAL CPU, BLADES = 2 -- Sets objective for DMR system. When the objective is not met because Blade A is down the client displays Blades as "B". 2.8 The ProcessBusy SGP now monitors up to 10,000 processes per Cpu to determine the n-busiest process in the CPU. 2.8 The Disk SGP supports 2,000 physical disk devices on a node. 2.8 The Expand SGP allows objectives to be set for the primary Cpu of Expand lines. For Example: GOAL EXPAND, CPU=1 GOAL EXPAND $LHNY, CPU=3 2.8 PROCESS Command and Detail support long abstract names 2.8 A new file ASAPMEAS is now distributed as part of ASAP 2.8 server and beyond. ASAPMEAS provides in-depth Measure and analysis on demand simply by selecting an object in the ASAP client and clicking Show Related Measurement 2.8 APP, FILE, PROCESS, TCPIP, TELSERV commands support new AGE option which allows users (and the ASAP client) to control which objects appear. For example, AGE 15 indicates only objects stats within the last 15 minutes will be displayed. See Also ASAP Client Show Removed Objects checkbox on the General TAB of the 2.8 The EDL language has been enhanced to allow relationships to be defined between entities. This aspect of EDL is often referred to as Relation Definition Language (RDL). RELATION and MAP statements were added to the EDL language. 2.8 Limits on maximum EDL attributes were removed (was 100) 2.7 No New Features 2.6 No New Features Problems Corrected History: =========================== 2.8 [AAJ] The ASAPNCP SGP could loop and did not return end-to-end node statistics. 2.8 [AAJ] CPU SGP's abending after blade/slice integration 2.8 [AAJ] Missed samples being reported for Expand lines. Could also occur with Disk and Comm SGP's 2.8 [AAJ] The ASAPTAP SGP would not monitor all virtual tape drives. 2.8 [AAJ] The ASAPTMF SGP could abend at each interval. 2.8 [AAJ] The ASAPPRO SGP could abend when monitoring certain nonstop processes. 2.8 [AAJ] Comm line status attribute not being shown as EMS event. 2.8 [AAJ] CPU Queue counter is not correct. 2.8 [AAJ] Disk devices not always displaying the warning state for down paths on the Client. 2.8 [AAJ] Disk busy counter not always correct on G and H series nodes. 2.8 [AAJ] Disk Device inaccessible messages when using the backup path on the primary volume or MB path on the mirrored volume. 2.7 [AAH] The canned ASAP rule named SECURE failed to properly re-secure disk files. 2.7 [AAH] The canned ASAP rule named PRIMARY did not work to primary disk paths. 2.7 [AAH] The Process SGP could generate excess activity against the disk process by requesting the program filename at each interval using Process_GetInfoList_ even though it already knew the program filename from a previous request. 2.7 [AAH] The Process SGP would sometimes report incorrect MSent, MRecv and PFaults values for the first interval after a monitored process failed. 2.7 [AAH] The percentage ranking scheme did not work correctly for all ASAP entities when Historical ranking was used. 2.7 [AAH] The MONITOR FILE, LIST, DETAIL and MONITOR PROCESS, LIST, DETAIL commands did not provide useful information about the dynamic object pool size and utilization, and an incorrect default pool size was shown in the help text for HELP SET FILE and HELP SET PROCESS. 2.7 [AAH] The COMM SGP did not report the link level status for X25 lines. The status of the line would be displayed as up when the link status was down or connecting. 2.7 [AAH] The ASAP CI would report an additional comm line from a previous sample whenever a line was no longer being monitored. 2.7 [AAH] The COMM SGP would report Comm lines that were added via SCF when auto-discovery was off. 2.7 [AAH] COMM SGP would not report Comm lines when the IOP was not started. 2.7 [AAH] The DISK SGP would not report the backup path as down for an unmirrored volume when the backup path was downed by the operator or due to a hardware failure. 2.7 [AAH] The EXPAND SGP could report SPI -8 errors when an Expand line is aborted for a long period of time, or could occur if the $zexp is stopped and restarted during an ASAP sample interval. 2.7 [AAH] The ASAP CI could abend after issuing a startup Monitor command. 2.7 [AAH] The DISK SGP reported lines inaccessible on a device subtype 53 when the backup path was being used. 2.7 [AAH] The BUSIEST PROCESS SGP did not display the current priority, but was displaying the intial priority when the process was first started. 2.7 [AAH] The COMM SGP did not display correct rate value, or input/output byte values or input/output data values. Also did not display the correct program object file name for the communication line. Did not always display the correct pin. 2.7 [AAH] The COMM SGP did not always collect line stats when the line was up. 2.6 [H01] ASAP Disk SGP showing invalid flag set for volumes in the up state. 2.6 [H01] ASAP reported last state plus one for an historically ranked domain when an alert continued into the second interval even if the percentage comparison would have produced a higher state. 2.6 [H01] The FILE command would output ordinary filenames with backslash characters instead of period characters and ASAP required the characters to be entered when retrieving information about a specific file. 2.6 [H01] ASAP would fail to automatically create an aggregate-only domain for processes being monitored by a wildcard specifier or object filename if the domain name contained logical prefixes. 2.6 [H01] The ASAP MONITOR command could allow a FILE domain name containing more than 5 levels to be accepted under certain conditions. 2.6 [H01] ASAP did not report that files were SQL/MX tables, views and indexs. 2.6 [H01] ASAP would fail to create obeyform output when the M,OB command was entered. 2.6 [H01] ASAP Disk SGP not returning correct largest fragment state for a down disk. 2.6 [H01] ASAP CPU SGP not displaying correct state value for Breakpoints when the CPU is down. 2.6 [H01] ASAP Client not displaying the correct value for disk block Splits. 2.6 [H01] The SPOOLER SGP could improperly format the <#OBJECT> token in action strings. 2.6 [H01] Actions against FILE objects could fail when the file was monitored using a wildcard name. 2.6 [H01] ASAP would fail to generate an UP event when a TMF transaction duration alert had returned to normal. 2.6 [H01] In certain cases an ASAP SGP could abend if MaxObjectives, as defined in the entity EDL, was exceeded. 2.6 [H01] The ASAP Disk SGP could abend. Occurs when more than 33 volumes are monitored and the collector does not reply within 3 minutes to an update request. 2.6 [H01] The Discrete Objectives Threshold Engine would abend. Would occur when an a disk volume was renamed. 2.6 [H01] The ASAP Disk SGP does not display the correct disk path to the lient when the -M path is down. Reports that the -MB path is down on the client. Occurs when the Mirror path is down. 2.6 [H01] The ASAP Disk SGP does not display the correct Operational state for a volume that has a configured backup path, and the mirrored disk does not exist. Would occur when the backup controller is configured and the mirrored disk is not configured. 2.6 [H01] Expand SGP would report down EMS events in a multiline environment when the Path for the multilines was not configured on the node. Known Problems Remaining: NONE =========================