SPR - Softdoc T0402H03\OUTLEN 80 SOFTWARE RELEASE DOCUMENT Product Name: ASAP SERVER SPR ID: T0402H03 DATE: 15APR2008 Copyright Notice: HP CONFIDENTIAL: NEED TO KNOW ONLY Copyright 2008 Hewlett-Packard Development Company, L.P. Protected as an unpublished work. The computer program listings, specifications and documentation herein are the property of Compaq Computer Corporation and successor entities such as Hewlett-Packard Development Company, L.P., or a third party supplier and shall not be reproduced, copied, disclosed, or used in whole or in part for any reason without the prior express written permission of Hewlett-Packard Development Company, L.P. Summary: ASAP 3.0 core server now includes TCP/IP subsystem monitoring. TCP/IP includes 19 TCP/IP and Telserv entities, and over 1000 new attributes. New SWAP entity provides in-depth virtual memory statistics allowing ASAP to set thresholds, alert, and take actions on KMSF statistics. New CPU memory statistics include swap, free, locked memory, etc, and allows thresholds, alerts, and actions to be taken on memory usage. ASAP can now host one or more real-time local/proxy websites. ASAP can optionally integrate with the HP Systems Insight Manager (SIM). New HTML entity-attribute grid-graph reports can be sent via website, email, or phone. ASAP Reports now support SIM level 1 integration. New notify control panel has 15 new notify content controls. New ASAP database structures support relative files to greatly reduce I/O overhead given large-record high-volume entities, such as the TCP/IP entity. ASAP 3.0 is now a licensed product. Run SYSINFO on each system to be licensed and E-mail the SYSINFO output for each system to License.Manager@HP.Com. Several minor problems have been fixed. The following SGP's have had corrections made to them: CPU, DISK, FILE, PROCESS, RDF, TAPE, SPOOLER, TCP, and TMF. Also there were corrections to custom events, goals, and the ASAP Monitor. Refer to the problems corrected section for further information. T0402V03 for S-series/K-series processors is equivalent to T0402H03 for Itanium Integrity NonStop servers. Required Hardware: HP Integrity NonStop servers Required Firmware: NONE Required Software: T9050H01 NONSTOP KERNEL T9550H01 SOCKET LIBRARY T9552H01 TCP/IP FTP Microsoft Windows Vista, Microsoft Windows XP, Microsoft Windows 2000, Microsoft Windows ME, or Windows NT 4.0 or later. Microsoft TCP/IP stack and FTP client Manuals: 425263-005 ASAP Client Manual 429917-005 ASAP Messages Manual 522303-008 ASAP Server Manual 545871-001 ASAP QuickStart Manual Migration Considerations: ASAP TCPIP is now included in the ASAP core products T0402V03 and T0402H03. TCPIP is no longer an optional plug-in product. In addition the TCP/IP SGP has been completely re-worked for ASAP 3. It now supports 19 TCP/IP and TELSERV entities and over 1,000 new attributes. Improved ASAP database performance in high volume large record environments by allowing the user to define the ASAP collector to use a Relative database file. HTML entity attribute grid and graph reports that can notify an ASAP user on the overall state of their NonStop environment. Reports can be integrated with HP's Systems Insight Manager (SIM). Additional CPU memory statistics have been introduced in this SPR. Virtual memory support reports on virtual memory per processor and monitors and reports on all the configured swap files for each CPU. Several minor problems have been corrected. Installation Considerations: * When using DSM/SCM to install this SPR: - RECEIVE the SPR from disk or tape. - COPY the SPR to a new revision of the software configuration you want to update. - BUILD and APPLY the configuration revision. - Perform the pre-installation steps shown below. - Run ZPHIRNM to perform the RENAME step. - If not using H01.00 onward, VOLUME to the new/updated SYSnn, and run VTILT to determine if Shared Runtime Library conflicts must be resolved before loading the system. - Perform these pre-installation steps. 1. Ensure that requirements for using this product are met (see Section the Required Hardware and Required Software sections above). 2. Ensure that prerequisites for the installation utility and any product-specific installation requirements are met (see Section D 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. If you are using the ASAP Extension make a copy of the file $SYSTEM.SYSTEM.ASAPUSER. FUP - VOLUME $SYSTEM.SYSTEM - DUP ASAPUSER, ASAPSAVE.*, SAVEALL 6. If you are upgrading from ASAP 2.8 or an earlier release to ASAP 3.0 then this SPR 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. 7. If you are upgrading from an earlier version of ASAP please read the following steps. If you have any ASAP3* files, save the ASAP CI and all EDL files. If you have archived data with the old version of ASAP that you would like to view later, you must save the following files: FUP - VOLUME $SYSTEM.SYSTEM - DUP ASAP, ASAPSAVE.*, SAVEALL - DUP ASAP3EDL, ASAPSAVE.*, SAVEALL - DUP ASAP3SYS, ASAPSAVE.*, SAVEALL - DUP ASAP3APP, ASAPSAVE.*, SAVEALL 8. 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. 9. Follow the post-installation instructions in Section B below, if any, after using IPSetup to place and install this product. - Perform these post-installation steps. 1. Invoke the INSTALL^TEMPLATES TACL macro to install this SPR's EMS template file(s) in the running system. The macro can be found in $.ZINSAIDS.TACLMACS or Support Note S92067B. For instructions, LOAD the macro and type: INSTALL^TEMPLATES /OUT / HELP 2. Run ASAP setup to update the ASAP subsystem with the following commands: a) VOLUME $.ZASAP b) 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 old database files before starting the new ASAP environment. FUP PURGE $..DB*! 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. 6. Please ignore the "Unknown ASAP config option" message from ASAP Extension if you are using an earlier version of ASAPX with ASAP 3.0. The message does not affect the operation of ASAPX. New Features: 1. [H03] The ASAP server now requires a license per node in order for ASAP to run. To obtain a valid license, run SYSINFO on each system to be licensed and E-mail the SYSINFO output along with the type of license and number of CPUs to license.manager@hp.com. (No SOLN) 2. [H03] ASAP TCPIP is now included in the ASAP core products T0402V03 and T0402H03. TCP/IP supports v4, v6 in all modes, ICMP, IP, Process, QIO, RTE and UDP, ARP, IGMP, LOOP, MONGQ, SOCK ICMP6, IP6, SubNet, Route and Port stats. Support for TELSERV process, Service and Window stats are also included in ASAP core products. This results in 19 new TCP/IP and TELSERV entities and more than 1000 attributes. (No SOLN) 3. [H03] Virtual memory (Swap SGP) support has been added. ASAP 3.0 Reports on virtual memory (KMSF) per processor and monitors and reports on all the configured swap files for each CPU. Some of the statistics maintained by the Swap SGP are percent full for all configured swap files, percent full for each individual swap file, reserved pages which is the total memory pages allocated for the CPU, and also displays the number of pages allocated for each swap file. See the ASAP Server manual for all of Swap SGP statistics and threshold support, or mouseover the SWAP entity attributes in ASAP client for an explanation of each SWAP attribute. (No SOLN) 4. [H03] CPU memory statistics have been added. New attributes include memory size, swappable memory, free memory, locked memory, maximum locked memory, and highest locked memory. (No SOLN) 5. [H03] There is new notify control panel that includes 15 new notify content controls and other new checkboxes for setting up ASAP's notification capabilities. Refer to the ASAP Client Manual for further detail. (No SOLN) 6. [H03] New HTML entity attribute grid and graph reports that can notify ASAP users about the overall state of their NonStop servers. Reports can be sent to Email addresses, or wireless phones, or to a customers websites. Reports can also be integrated with HP Systems Insight Manager (SIM). (No SOLN) 7. [H03] ASAP database performance can be greatly improved in high-volume large-record environments. A new SET option allows you to configure the ASAP database to use a Relative database file. The new set option allows ASAP users to control which entity should be configured to use relation files. One possible indication that a relative file DB is needed is when the ASAP Log has a high volume of missed sample log records. To achieve higher ASAP database performance the user simply configures an ASAP collector to create a Relative file by using the new SET PARTITION option. (No SOLN) 8. [H03] The count of unique batch jobs has been added to the Spooler SGP. A new attribute, UBatch, counts the number of unique batch jobs in a Spooler subsystem. (SOLN 10-061201-0829) 9. [H03] RDF domain name parsing and support has been strengthened, so that MONITOR commands cannot be issued against RDF subdomains. (SOLN 10-061219-1264) Problems Corrected: 1. [H03] SYMPTOMS: Expand SGP abends when thr MONITOR EXPAND,LIST command is entered from the ASAP CI. CONDITIONS: The ASAP command Monitor Expand, list is entered. LIKELIHOOD: Likely. (SOLN 10-080405-2151) 2. [H03] SYMPTOMS: Disk SGP could abend when volumes are deleted from the configuration. CONDITIONS: When a large number of disk volumes are deleted from the nodes configuration. LIKELIHOOD: Unlikely. (SOLN 10-071211-9389) 3. [H03] SYMPTOMS: Cannot start ASAP collector if the system is a different node than the system where ASAP collector is to be started. CONDITIONS: ASAP database name is not resolved correctly when defaults are fully qualified and the node number is greater than 96. LIKELIHOOD: Likely. (SOLN 10-070122-4463) 4. [H03] SYMPTOMS: False CPU alert notifications being sent and displayed by the ASAP Client. CONDITIONS: When the monitor sends a request to an SGP and the request times out. The timeout occurs because a CPU SGP is busy. 15:51 \FIELD ASAP ERR Send to SGP $AAA error: 40 LIKELIHOOD: Unlikely. (SOLN 10-070927-7807) 5. [H03] SYMPTOMS: ASAP monitor not allowing sufficient time for SGP's to shutdown. SGP processes may be running after the monitor shuts down. CONDITIONS: When an SGP is busy the ASAP monitor does not allow sufficient time for the SGP to shutdown. LIKELIHOOD: Unlikely. (SOLN 10-080405-2152) 6. [H03] SYMPTOMS: Disk Error 3402 generated when volume is configured for different groups. CONDITIONS: $VOL-P configured group 1 $VOL-M configured group 2. LIKELIHOOD: Likely. (SOLN 10-070626-5827) 7. [H03] SYMPTOMS: Running in a mixed ASAP version down rev CPU records could have incorrect values for Chits and discs. CONDITIONS: ASAP 2.7 CPU SGP sending records to an ASAP 2.8 collector or later collector. LIKELIHOOD: Likely. (SOLN 10-070927-7807) 8. [H03] SYMPTOMS: ASAP could stop a process not started by ASAP after issuing the shutdown command. CONDITIONS: When the ASAP ID is $ZOO and there is a process by the name of $ZOO8 the CPU SGP $ZOO8 fails to start in CPU 8. During shutdown ASAP could stop the process $zoo8 if the permissions were correct. LIKELIHOOD: Unlikely. (SOLN 10-080405-2153) 9. [H03] SYMPTOMS: Disk SGP reporting error 3402 when using -B path. CONDITIONS: Disk drive is using the -B path and using the Y Fabric. LIKELIHOOD: Likely. (SOLN 10-070626-5827) 10. [H03] SYMPTOMS: Multiple records could be displayed for the same disk volume when an object was running and then deleted. CONDITIONS: Disk objects auto-discovered are deleted from the nodes configuration. LIKELIHOOD: Unlikely. (SOLN 10-071211-9389) 11. [H03] SYMPTOMS: TMF mounts show as a warning in ASAP Client after they have been removed. CONDITIONS: When SHOW REMOVED OBJECTS is set on in ASAP Client. LIKELIHOOD: Unlikely. (SOLN 10-080226-0821) 12. [H03] SYMPTOMS: TMF Mounttime UP events are not generated when a mount is rejected. CONDITIONS: When a tape mount is rejected. LIKELIHOOD: Unlikely. (SOLN 10-071218-9539) 13. [H03] SYMPTOMS: Monitoring processes by their object filename is too resource consumptive. CONDITIONS: When monitoring many processes using their object filename. LIKELIHOOD: Likely. (SOLN 10-070717-6304) 14. [H03] SYMPTOMS: TCP SGP consumes too much virtual memory. CONDITIONS: When TCP max domains settings are too high. LIKELIHOOD: Unlikely. (SOLN 10-070703-5998) 15. [H03] SYMPTOMS: Some forms of TCP sub-entity names and/or abbreviations cause ASAP CI to abend. CONDITIONS: When exotic TCP commands are entered. LIKELIHOOD: Unlikely. (SOLN 10-070624-5781) 16. [H03] SYMPTOMS: Goals could be applied incorrectly to TCP ICMP, IP, QIO, RTE and UDP entity domains. CONDITIONS: When goals are defined against TCP stack sub-entities. LIKELIHOOD: Likely. (SOLN 10-070619-5686) 17. [H03] SYMPTOMS: GOAL/RANK SERVICE , LIST commands could fail when issued from ASAP Client. CONDITIONS: When Service names were too long. LIKELIHOOD: Unlikely. (SOLN 10-070615-5597) 18. [H03] SYMPTOMS: Updater UP events are not always generated for the RDF entity. CONDITIONS: When RDF uses an old version of the ASAP infrastructure SGP_RANKVALUE_ procedure. LIKELIHOOD: Unlikely. (SOLN 10-070605-5272) 19. [H03] SYMPTOMS: ASAPFIL, ASAPPRO and ASAPTCP SGPs can abend if MaxDomains is exceeded. CONDITIONS: When more then the maximum number of domains are found. LIKELIHOOD: Unlikely. (SOLN 10-070507-4628) 20. [H03] SYMPTOMS: Custom event numbers are not generated when used with CPU entity domains. CONDITIONS: When custom event numbers are defined for CPU objectives on subdomains. LIKELIHOOD: Likely. (SOLN 10-070420-4291) 21. [H03] SYMPTOMS: Custom event numbers are not generated when used with TMF entity domains. CONDITIONS: When custom event numbers are defined for TMF objectives on subdomains. LIKELIHOOD: Likely. (SOLN 10-070420-4290) 22. [H03] SYMPTOMS: Objectives (goals) could mistakenly be applied to the wrong domain. CONDITIONS: When a domain matched the objective domain name for the length of the objective domain name. LIKELIHOOD: Unlikely. (SOLN 10-070323-3526) 23. [H03] SYMPTOMS: File SGP gives error message 'NoFile' when a large fileset is added to ASAP and when files are continuously deleted from the fileset. CONDITIONS: When files are deleted after the name is resolved by ASAP but before ASAP has gathered stats on the file. LIKELIHOOD: Unlikely. (SOLN 10-070319-3363) Known Problems Remaining: NONE