SPR - Softdoc T0402H01^AAJ\OUTLEN 80 SOFTWARE RELEASE DOCUMENT Product Name: ASAP SERVER SPR ID: T0402H01^AAJ H-series T0402V02^AAI G-series DATE: 15JAN2007 Copyright Notice: HP CONFIDENTIAL: NEED TO KNOW ONLY Copyright 2006 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 server version 2.8 supports a new optional TCP/IP plug-in which monitors 12 new TCP/IP and Telserv entities, and 600 new attributes. CPU entity now monitors Blade Count, Status, and preferred Count. Expand entity now monitors path/line-handler primary CPU and state. ProcessBusy entity monitors up to 10,000 busiest processes per CPU. DISK entity now monitors up to 1,000 mirrored volumes per node. ASAPMEAS is now distributed as part of ASAP 2.8 server and allows in-depth, on-demand Measurement and analysis of selected objects. APP, FILE, PROCESS, TCP commands now support new AGE option. EDL extended to allow relations to be defined between EDL entities. RELATION and MAP statements have been added to the EDL language. Limit on the EDL Attribute count has been removed (it was 100). Minor corrections to COMM, CPU, DISK, NODE, and the TAPE were made. T0402V02^AAI for S-series/K-series processors is equivalent to T0402H01^AAJ for Itanium Integrity NonStop servers. [H01^AAH] Minor corrections affecting the COMM, DISK, EXPAND, PROCESS SGP's have been corrected. Minor problems with the ASAP CI have been corrected. Note this SPR is equivalent to SPR T0402V02^AAG. [H01] Minor Disk SGP issues have been corrected. ASAP SGP's can no longer abend when EDL MaxObjectives are exceeded. Process SGP creates aggregate record when using wildcard specifier. File command outputs with period characters. ASAP monitor command would no longers accepts 5 domain name levels. ASAP File SGP reports on SQL/MX tables, views and indexes. Obeyform output created for Monitor, OBEY command. CPU SGP reports correct state value for breakpoints attribute. ASAP client now displays correct disk block splits. Spooler SGP no longer formats the #object token incorrectly. Corrective actions no longer fail when the file was monitored using a wild card. Up event generated for TMF SGP when the alert returned to a normal state. Superseded SPRs: T0402H01^AAH Requisite SPRs: T6965H01^AAJ SEEVIEW T6965 The function needed in T6965 is required onlyif you SET ACTION ON. Required Hardware: HP Integrity NonStop servers Required Firmware: NONE Required Software: T9050H01 NONSTOP KERNEL T9550H01 SOCKET LIBRARY T9552H01 TCP/IP FTP 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-004 ASAP Client Manual *429917-004 ASAP Messages Manual *522303-007 ASAP Server Manual * - indicates that the manual is new or its contents have changed in this SPR. Installation Considerations: Subsystem interruption required Installation Instructions: * 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 G05.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.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. 7. 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 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 nvironment. 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. New Features: 1. [H01^AAJ] 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. (No SOLN) 2. [H01^AAJ] 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". (SOLN 10-061114-0500) 3. [H01^AAJ] The ProcessBusy SGP now monitors up to 10,000 processes per Cpu to determine the n-busiest process in the CPU. (SOLN 10-060526-6770) 4. [H01^AAJ] The Disk SGP supports 2,000 physical disk devices on a node. (SOLN 10-060912-8970) 5. [H01^AAJ] 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 (SOLN 10-061114-0499) 6. [H01^AAJ] PROCESS Command and Detail support long abstract names (No SOLN) 7. [H01^AAJ] 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 (No SOLN) 8. [H01^AAJ] 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 ASAP Property sheet. (No SOLN) 9. [H01^AAJ] 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. (No SOLN) 10. [H01^AAJ] Limits on maximum EDL attributes were removed (was 100) (No SOLN) 11. [H01] YOSEMITE SUPPORT (SOLN 10-050113-3563) Problems Corrected: 1. [H01^AAJ] SYMPTOMS: CPU SGP's abending after blade/slice integration CONDITIONS: Occurs during blade re-integration. LIKELIHOOD: Unlikely FIX-INFO: The CPU SGP checks for overflow of the process busy time. (SOLN 10-061201-0839) 2. [H01^AAJ] SYMPTOMS: Missed samples being reported for Expand lines. Could also occur with Disk and Comm SGP's CONDITIONS: Expand rate is set at a higher value than the ASAP rate value. LIKELIHOOD: Unlikely FIX-INFO: The EXPAND, DISK, and COMM SGP's now correctly use the rate value specified by the user. (SOLN 10-061201-0837) 3. [H01^AAJ] SYMPTOMS: The ASAPNCP SGP could loop and did not return end-to-end node statistics. CONDITIONS: When the Expand network topology was configured incorrectly, or when certain OS versions were executing. LIKELIHOOD: Unlikely FIX-INFO: The SGP now recognizes mis-configured network topologies and correctly returns end-to-end node statistics for all NSK versions (SOLN 10-061130-0786) 4. [H01^AAJ] SYMPTOMS: The ASAPTAP SGP would not monitor all virtual tape drives. CONDITIONS: When many, many virtual tape drives were configured. LIKELIHOOD: Unlikely FIX-INFO: The SGP now supports 1,000 virtual tape drives. (SOLN 10-061130-0785) 5. [H01^AAJ] SYMPTOMS: The ASAPTMF SGP could abend at each interval. CONDITIONS: When 16 audittrails were configured in TMF. LIKELIHOOD: Unlikely FIX-INFO: The SGP now supports the maximum size of 16 audittrails. (SOLN 10-060920-9190) 6. [H01^AAJ] SYMPTOMS: The ASAPPRO SGP could abend when monitoring certain nonstop processes. CONDITIONS: When 16 audittrails were configured in TMF. LIKELIHOOD: Unlikely FIX-INFO: The SGP now uses 64-bit floating point math to handle very large values. (SOLN 10-060906-8832) 7. [H01^AAJ] SYMPTOMS: Comm line status attribute not being shown as EMS event. CONDITIONS: Status of a Comm line changes. LIKELIHOOD: Certain FIX-INFO: The correct status is now used. (SOLN 10-061114-0506) 8. [H01^AAJ] SYMPTOMS: CPU Queue counter is not correct. CONDITIONS: None LIKELIHOOD: Certain FIX-INFO: The correct queue value is being calculated by the CPU SGP. (SOLN 10-061114-0504) 9. [H01^AAJ] SYMPTOMS: Disk devices not always displaying the warning state for down paths on the Client. CONDITIONS: Path is down, not shown on the client as a warning state LIKELIHOOD: Certain FIX-INFO: The ASAP CI now updates the ASAP Client with the correct value of down disk paths. (SOLN 10-061115-0530) 10. [H01^AAJ] SYMPTOMS: Disk busy counter not always correct on G and H series nodes. CONDITIONS: Occurs only on very busy volumes. LIKELIHOOD: Likely FIX-INFO: The Disk SGP now uses the correct measure counter on G & H series nodes. (SOLN 10-061114-0498) 11. [H01^AAJ] SYMPTOMS: Disk Device inaccessible messages when using the backup path on the primary volume or MB path on the mirrored volume. CONDITIONS: When using the -B or -MB path LIKELIHOOD: Likely FIX-INFO: The correct servernet value is now used in the call to Measreadactive. (SOLN 10-061009-9642) 12. [H01^AAH] SYMPTOMS: The canned ASAP rule named SECURE failed to properly re-secure disk files. CONDITIONS: When the SECURE rule was used in an action against a disk file. LIKELIHOOD: Certain (SOLN 10-060427-6133) 13. [H01^AAH] SYMPTOMS: The canned ASAP rule named PRIMARY did not work to primary disk paths. CONDITIONS: When the PRIMARY rule was used in an action against a disk path. LIKELIHOOD: Certain (SOLN 10-060427-6132) 14. [H01^AAH] SYMPTOMS: 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 file name from a previous request. CONDITIONS: None LIKELIHOOD: Certain (SOLN 10-060330-5478) 15. [H01^AAH] SYMPTOMS: The PROCESS SGP would sometimes report incorrect MSent, MRecv and PFaults values for the first interval after a monitored process failed. CONDITIONS: When a monitored process failed that was not being measured by Measure. LIKELIHOOD: Certain (SOLN 10-060330-5477) 16. [H01^AAH] SYMPTOMS: The percentage ranking scheme did not work correctly for all ASAP entities when Historical ranking was used. CONDITIONS: When Historical ranking is used and an alert condition exists for more than one ASAP interval. LIKELIHOOD: Certain (SOLN 10-060306-4869) 17. [H01^AAH] SYMPTOMS: 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. CONDITIONS: Pool space is used when wildcard names or object filenames are used in MONITOR commands. LIKELIHOOD: Likely (SOLN 10-050928-1685) 18. [H01^AAH] SYMPTOMS: 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. CONDITIONS: Occurs when the X25 link status was not up. LIKELIHOOD: Certain (SOLN 10-050523-8018) 19. [H01^AAH] SYMPTOMS: The ASAP CI would report an additional comm line from a previous sample whenever that line was no longer being monitored. CONDITIONS: Occurs when a comm line was no longer being monitored. LIKELIHOOD: Certain (SOLN 10-060316-5114) 20. [H01^AAH] SYMPTOMS: The COMM SGP would report comm lines that were added via SCF when auto-discovery was off. CONDITIONS: Occurs when the a new line is configured. LIKELIHOOD: Certain (SOLN 10-060316-5130) 21. [H01^AAH] SYMPTOMS: The COMM SGP would not report on comm lines when the IOP was not started. CONDITIONS: Occurs when the IOP is in a startdown state. LIKELIHOOD: Certain (SOLN 10-060316-5129) 22. [H01^AAH] SYMPTOMS: 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. CONDITIONS: Occurs when the backup path to an unmirrored volume is down. LIKELIHOOD: Likely (SOLN 10-060316-5128) 23. [H01^AAH] SYMPTOMS: The EXPAND SGP could report SPI -8 errors when an Expand line was aborted for a long period of time, or could occur if the $zexp was stopped and restarted during an ASAP sample interval. CONDITIONS: Could occur when the $ZEXP process is stopped and restarted. LIKELIHOOD: Unlikely (SOLN 10-060308-4933) 24. [H01^AAH] SYMPTOMS: The ASAP CI could abend after issuing a startup Monitor command. CONDITIONS: Would occur when the command startup monitor was entered. LIKELIHOOD: Unlikely (SOLN 10-051115-2572) 25. [H01^AAH] SYMPTOMS: The DISK SGP reported device inaccessible on a disk device subtype 53 when the backup path was being used. CONDITIONS: Would occur when the backup path was in use. LIKELIHOOD: Certain (SOLN 10-060308-4930) 26. [H01^AAH] SYMPTOMS: The BUSIEST PROCESS SGP did not display the current priority, but was displaying the intial priority when the process was first started. CONDITIONS: Would occur when a process priority was changed. LIKELIHOOD: Certain (SOLN 10-060308-4928) 27. [H01^AAH] SYMPTOMS: 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. CONDITIONS: Would occur when monitoring comm lines. LIKELIHOOD: Certain (SOLN 10-060316-5127) 28. [H01^AAH] SYMPTOMS: The COMM SGP did not always collect comm line stats when the line was up. CONDITIONS: Occurred on comm lines that did not have traffic. LIKELIHOOD: Certain (SOLN 10-060316-5126) 29. [H01] SYMPTOMS: The EXPAND SGP would report down EMS events in a multiline environment when the Path for the multilines was not configured on the node. CONDITIONS: Occurs when the Path for a multiline Expand configuration is deleted from the node. LIKELIHOOD: Certain (SOLN 10-050503-7367) 30. [H01] SYMPTOMS: The ASAP DISK SGP had the invalid flag set for volumes in the up state. CONDITIONS: Occurs on disk volumes that do not have a mirrored drive configured. LIKELIHOOD: Certain (SOLN 10-050505-7449) 31. [H01] SYMPTOMS: 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. CONDITIONS: When Historical Ranking is being used and an alerting domain passes into a second interval with an alert level higher than its last state plus one. LIKELIHOOD: Likely (SOLN 10-050504-7414) 32. [H01] SYMPTOMS: 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. CONDITIONS: When the FILE command was issued to ASAP CI without the RAW parameter. LIKELIHOOD: Certain (SOLN 10-050322-5834) 33. [H01] SYMPTOMS: 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. CONDITIONS: User monitored processes are added by using a wildcard specifier or object filename when the domain name contained logical prefixes LIKELIHOOD: Certain (SOLN 10-050321-5826) 34. [H01] SYMPTOMS: The ASAP MONITOR command could allow a FILE domain name containing more than 5 levels to be accepted under certain conditions. CONDITIONS: When certain combinations of hierarchical grouping and wildcard names were specified in MONITOR commands. LIKELIHOOD: Likely (SOLN 10-050321-5825) 35. [H01] SYMPTOMS: ASAP did not report that files were SQL/MX tables, views and indexes. CONDITIONS: ASAP file entity is montioring files that are SQL/MX tables, views and indexs. LIKELIHOOD: Certain (SOLN 10-050315-5636) 36. [H01] SYMPTOMS: ASAP would fail to create obeyform output when the M,OB command was entered. CONDITIONS: Occurred when the Monitor,OBEY command was entered from the ASAP CI. LIKELIHOOD: Certain (SOLN 10-050315-56) 37. [H01] SYMPTOMS: The ASAP DISK SGP was not returning correct largest fragment state for a down disk. CONDITIONS: Occurred when a disk is down, and the fragment attibute is enabled on the client grid. LIKELIHOOD: Certain (SOLN 10-050316-5670) 38. [H01] SYMPTOMS: The ASAP CPU SGP was not displaying correct state value for Breakpoints when the CPU is down. CONDITIONS: Occurred against any down CPU on the node. LIKELIHOOD: Certain (SOLN 10-050302-5219) 39. [H01] SYMPTOMS: The ASAP Client was not displaying the correct value for disk block splits. CONDITIONS: Occurred on the client when the user enabled the block split attribute to be displayed in the graph or grid. LIKELIHOOD: Certain (SOLN 10-050302-5217) 40. [H01] SYMPTOMS: The SPOOLER SGP could improperly format the <#OBJECT> token in action strings. CONDITIONS: Occurred when actions are defined against spooler objects using the <#OBJECT> token. LIKELIHOOD: Likely (SOLN 10-050302-5215) 41. [H01] SYMPTOMS: Actions against FILE objects could fail when the file was monitored using a wildcard name. CONDITIONS: Occurred when the user configured ASAP to monitor a file using a wildcard name. LIKELIHOOD: Likely (SOLN 10-050223-4895) 42. [H01] SYMPTOMS: ASAP would fail to generate an UP event when a TMF transaction duration alert had returned to normal. CONDITIONS: Occurred when a TMF transaction duration alert had returned to a normal state. LIKELIHOOD: Certain (SOLN 10-050208-4527) 43. [H01] SYMPTOMS: In certain cases an ASAP SGP could abend if MaxObjectives, as defined in the entity EDL, was exceeded. CONDITIONS: When an SGP reaches its MaxObjectives value. LIKELIHOOD: Unlikely (SOLN 10-041125-2185) 44. [H01] SYMPTOMS: The ASAP DISK SGP could abend CONDITIONS: Occurred when more than 33 volumes are monitored and the ASAP collector did not reply within 3 minutes to an update request. LIKELIHOOD: Unlikely (SOLN 10-050113-3559) 45. [H01] SYMPTOMS: The Discrete Objectives Threshold Engine would abend. CONDITIONS: Occurred when a disk volume was renamed. LIKELIHOOD: Certain (SOLN 10-050112-3532) 46. [H01] SYMPTOMS: The ASAP DISK SGP did not display the correct disk path to the client when the -M path was down, but is reporting that th -MB path was down. CONDITIONS: Occurred on disk devices when the mirror path is down. LIKELIHOOD: Certain (SOLN 10-050113-3558) 47. [H01] SYMPTOMS: The ASAP DISK SGP did not display the correct operational state for a volume that had a configured backup path, and the mirrored disk did not exist. CONDITIONS: Occurred when the backup controller is configured and the mirrored disk is not configured. LIKELIHOOD: Likely (SOLN 10-050113-3556) Known Problems Remaining: NONE