  G  ********************************************************************** G  **                                                                  ** G  ** TEXT FILE LIMITATIONS:                                           ** G  **                                                                  ** G  ** The text extract for this document does not capture tables very  ** G  ** well, mainly because of the 75-column, monospaced character      ** G  ** limitation. Be aware that large data tables probably will not    ** G  ** wrap properly in this text file.                                 ** G  **                                                                  ** G  ** In addition, the text extract cannot capture figure images.      ** G  ** You can see only placeholders (captions) for the figures.        ** G  **                                                                  ** G  ** You may see references to italic or bold fonts that are visible  ** G  ** in the original document but not in this text extract.           ** G  **                                                                  ** G  **********************************************************************   1                            *** Compaq Analyze ***   0                            *** Release Notes ***  K ***************************************************************************   I Compaq Analyze is a rules-based hardware fault management diagnostic tool C that provides error event analysis and translation. The multi-event I correlation analysis feature of Compaq Analyze provides the capability to J analyze events stored in the system's event log file and the capability to" analyze events from other sources.  H The Compaq Analyze Release Notes provide general release information and+ describe the limitations of Compaq Analyze.    Rev. 3/21/02-A  B       Operating System:  Microsoft Windows NT 4.0 and Windows 2000?                          Compaq Tru64 UNIX versions 4.0E to 5.1 I                          Compaq OpenVMS Alpha versions 7.1-2, 7.2, 7.2-1, )                          7.2-1H1, and 7.3 9       Software Version:  Compaq Analyze 4.0 Service Pak 4   : Copyright 2002 Compaq Information Technologies Group, L.P.  K Compaq and the Compaq logo, StorageWorks, AlphaServer, ProLiant, Prosignia, H VAX, Tru64 and OpenVMS are trademarks of Compaq Information TechnologiesI Group, L.P. in the United States and other countries. Microsoft, Windows, E Windows NT, and MS-DOS are trademarks of Microsoft Corporation in the @ United States and other countries. Intel is a trademark of IntelI Corporation in the United States and other countries. UNIX is a trademark E of The Open Group in the United States and other countries. All other D product names mentioned herein may be trademarks of their respective
 companies.  F Confidential computer software. Valid license from Compaq required forB possession, use or copying. Consistent with FAR 12.211 and 12.212,B Commercial Computer Software, Computer Software Documentation, andG Technical Data for Commercial Items are licensed to the U.S. Government + under vendor's standard commercial license.   I Compaq shall not be liable for technical or editorial errors or omissions I contained herein. The information is provided "as is" without warranty of K any kind and is subject to change without notice. The warranties for Compaq A products are set forth in the express limited warranty statements A accompanying such products. Nothing herein should be construed as $ constituting an additional warranty.  H This service tool software is the property of, and contains confidentialK technology of Compaq Computer Corporation or its affiliates. Possession and K use of this software is authorized only pursuant to the Proprietary Service @ Tool Software License contained in the software or documentation accompanying this software.   H Compaq service tool software, including associated documentation, is theC property of and contains confidential technology of Compaq Computer I Corporation or its affiliates. Service customer is hereby licensed to use J the software only for activities directly relating to the delivery of, andK only during the term of, the applicable services delivered by Compaq or its I authorized service provider. Customer may not modify or reverse engineer, E remove or transfer the software or make the software or any resultant F diagnosis or system management data available to other parties withoutJ Compaq's or its authorized service provider's consent. Upon termination ofJ the services, customer will, at Compaq's or its service provider's option,B destroy or return the software and associated documentation in its possession.   A WorldWire contains encryption features subject to the U.S. Export A Administration Regulations (EAR). The U.S. Department of Commerce D classifies WorldWire as "retail encryption" exportable under LicenseJ Exception ENC in accordance with Section 740.17 of the EAR. By downloadingD the software, you agree that you will comply with those regulations.  I Examples used throughout this document are fictitious. Any resemblance to < actual companies, persons, or events is purely coincidental.   Printed in U.S.A.   K ===========================================================================    *** Contents ***  
 Title Page   Copyright Statement    Preface   
      Overview       Intended Audience      Documentation Conventions      Further Information   1 General Information         1.1 Description      1.2 Functionality      1.3 Supported Products $      1.4 Supported Operating Systems.      1.5 Translation and Analysis Capabilities.           1.5.1 Binary Event Log Decomposition3           1.5.2 Machine Check Error Log Entry Types (           1.5.3 GS Error Log Entry Types   2 General Limitations   $      2.1 Interface Independent Notes)           2.1.1 Time Stamp Interpretation 0           2.1.2 Date Reported By Summary Command6           2.1.3 Event Type Reported By Summary Command9           2.1.4 Serial Number Prevents Rules From Working )           2.1.5 Resource Usage Seems High G           2.1.6 Starting the Director Process Results in High CPU Usage @           2.1.7 Commands Time Out During Scavenge or Heavy Loads3           2.1.8 Configuring the Scavenge Start Time 0           2.1.9 Fragmented Disk Slows ProcessingK           2.1.10 Initializing System Error Log With Director Running Causes            ErrorsH           2.1.11 Changing IP Address Causes Director to Stop Functioning-           2.1.12 Disabling Automatic Analysis K           2.1.13 Bad Translation or Analysis Due to No Knowledge Registered   -           2.1.14 Fields Contain "Unavailable" 7           2.1.15 File Not Found Error In DESTA Log File ,           2.1.16 DSNLink (SICL) Connectivity(           2.1.17 Spurious Error MessagesE           2.1.18 Duplicate Callouts when DECevent and WEBES Installed            Together      2.2 CLI Notes/           2.2.1 Syntax Changes Affect All Users       2.3 Web Notes3           2.3.1 Director Communications Limitations :           2.3.2 Node Name Changes Cause Connection Failure3           2.3.3 Problems Connecting to Remote Nodes -           2.3.4 Internet Explorer Limitations 4                2.3.4.1 Java Virtual Machine Required(                2.3.4.2 HTTP 1.1 Required/                2.3.4.3 Partial URLs Not Allowed 6                2.3.4.4 Navigation Icons Updated Slowly?                2.3.4.5 Icons May Disappear If New Window Opened H                2.3.4.6 Event Details Cannot Be Viewed In Separate Window5                2.3.4.7 Progress Bar Indicates Loading $           2.3.5 Netscape Limitations/                2.3.5.1 Netscape 6 Not Supported +                2.3.5.2 Java Must Be Enabled *                2.3.5.3 Excessive CPU Usage:                2.3.5.4 Overlapping Text in Navigation Tree*           2.3.6 Bookmark May Create ErrorsA           2.3.7 Using the Back Button to Access the Web Interface %           2.3.8 Link Color Inaccurate 4           2.3.9 Group and Category Name Restrictions'           2.3.10 Refreshing the Display $           2.3.11 Null-Pointer Errors"           2.3.12 JavaScript Errors           2.3.13 Timeout Issue%           2.3.14 Logout Time Set to 0 ,           2.3.15 Restricting Remote Machines(           2.3.16 Hostname Not Recognized/           2.3.17 Cannot Activate a Running Node (           2.3.18 Negative Timeout Values  ' 3 Operating System Specific Limitationsu  )      3.1 Notes for Tru64 UNIX and Windowse)           3.1.1 Entering Paths in the CLIa                3.1.1.1 Spacesi                 3.1.1.2 Backslash5           3.1.2 Transferring Event Log Files with FTPi      3.2 Notes for Tru64 UNIX >           3.2.1 Compaq Analyze Now Polls for New Events (UNIX)?           3.2.2 Network Connection to Local IP Address Time Outn           3.2.3 Memory Errors*1           3.2.4 Cannot Load Shared Object Libraryr)           3.2.5 Time Reported Incorrectly       3.3 Notes for OpenVMS            3.3.1 Director Crashes           3.3.2 Startup Errors;           3.3.3 Lengthy Processing Time on Large Error Logse*           3.3.4 Trans Command Unresponsive&           3.3.5 Analyze Command Aborts&           3.3.6 Unsatisfied Link Error4           3.3.7 Stack Overflow and Bugcheck Messages7           3.3.8 Memory Errors (OpenVMS 7.2 and earlier) 7           3.3.9 Memory Errors (OpenVMS 7.2-1 and later)t'           3.3.10 Locked Error Log Files*3           3.3.11 Event Logs May Be Read Incorrectlyq=           3.3.12 Directory Names Unrecognized in CLI Commandst0           3.3.13 Invalid Directory Error Message7           3.3.14 Maximum Character Length Error Message '           3.3.15 Wildcards Not Expanded 5           3.3.16 Scrolling Output in Terminal Displaya4           3.3.17 Preserving File Attributes with FTP2           3.3.18 Web Interface No Longer Supported      3.4 Notes for Windows=           3.4.1 No Response on Systems with Norton Anti-Virus #           3.4.2 Netscape LimitationW4           3.4.3 Director Problems - Uninstall Issues<           3.4.4 Commands With Comma Must Use Quotation Marks3           3.4.5 NullPointerException If No Scavmark1   A Return Codes      K ===========================================================================a   *** Preface ***0  I The Compaq Analyze Release Notes provide general information about Compaq  Analyze.   Overview  I The Compaq Analyze Release Notes provide general information about CompaqnJ Analyze including the functionality and known limitations of the software.   Intended Audience   I The Compaq Analyze Release Notes are intended for anyone who will use thet@ Compaq Analyze software. The audience consists of the following:      * Mission Critical Engineersh  5    * Compaq Customer Support Center Phone Specialistst      * Compaq Customersr  $    * Compaq Serviceability Engineers      * Compaq Product Division  !    * Authorized Service Providerso   Documentation Conventions   2 The following conventions are used in this manual:  E       User entries   Information that should be entered exactly as it >                      appears in the document is shown in bold.J       Variables      Information that will vary depending on your computer9                      or user profile is shown in italics.rH       System Output  Responses from the system are shown in a monospaced                      font.   Further Information   F Compaq Analyze is a member of the Web-Based Enterprise Service (WEBES)H suite of products. For more information on the other WEBES applications,> visit the Service Tools support web site at the following URL:  ' http://www.support.compaq.com/svctools/s  5 The following documents contain relevant information:f      * Compaq Analyze User Guide      * WEBES Install Guide      K ===========================================================================r   1t   *** General Information ***e  G This chapter describes Compaq Analyze and the new features supported in ? this release. In addition, it describes the supported products.i      * Description      * Functionality      * Supported Productsq       * Supported Operating Systems  *    * Translation and Analysis Capabilities   1.1 Descriptiono  F Compaq Analyze is a fault analysis utility included with the Web-BasedC Service Enterprise (WEBES) service tools. It is designed to providehE analysis for single error/fault events, as well as multiple event and I complex analysis. Compaq Analyze provides system analysis that uses othergI error/fault data sources in addition to the traditional binary event log.s  G Compaq Analyze provides background automatic analysis by monitoring thevJ active binary event log and processing events as they occur. The events inK the binary event log file are checked against the analysis rules. If one oroD more of the events in the binary event log file meets the conditionsG specified in the rules, the analysis engine collects the error data andsH creates a problem report containing a description of the problem and anyF corrective actions required. Once the problem report is created, it isG distributed in accordance with the customer's notification preferences.e  K Each WEBES-based service tool adds functionality to the Director, a processsI (or set of processes) that executes continuously. Compaq Analyze provides=J the Director with the capability to capture and interpret hardware events.J The analysis of events can be performed automatically or when requested by an outside process.   K Compaq Analyze supports command line and web browser interfaces that enable J you to interact with the Director. Although only one Director can run on aG machine at any time, many web browser and CLI connections can be activen simultaneously.a  G For a complete list of the new features available in the latest releaseaH refer to the readme details text file installed with the kit. The readme/ files are located in the following directories:e  3 Windows - installed directory\compaq\svctools\docs\t   OpenVMS - SVCTOOLS_HOME:[DOCS]  . Tru64 UNIX - /usr/opt/compaq/svctools/docs/txt   1.2 FunctionalityC  J Compaq Analyze presents information through the following user interfaces:  !    * Command Line Interface (CLI)       * Web Interface  0 Both interfaces support the following functions:  '    * Automatic translation and analysisg  $    * Manual translation and analysis      * Scavenge pending events  8    * Automatically send notification to service provider  K Refer to the Compaq Analyze User Guide for more information about using ther( Compaq Analyze interfaces and functions.   1.3 Supported Products  > The following list shows the products Compaq Analyze supports.  <    * Analysis and Bit-To-Text Translation for the following:  G         * Compaq AlphaServer DS10 (Tru64 UNIX and OpenVMS, refer to theFH           AlphaServer Platforms Support section for support information)  H         * Compaq AlphaServer DS10L (Tru64 UNIX and OpenVMS, refer to theH           AlphaServer Platforms Support section for support information)  H         * Compaq AlphaServer DS20e (Tru64 UNIX and OpenVMS, refer to theH           AlphaServer Platforms Support section for support information)  G         * Compaq AlphaServer DS20 (Tru64 UNIX and OpenVMS, refer to theCH           AlphaServer Platforms Support section for support information)  H         * Compaq AlphaServer ES40/ES45 (Tru64 UNIX and OpenVMS, refer to?           the AlphaServer Platforms Support section for supporto           information)  G         * Compaq AlphaServer GS80/GS160/GS320 (Tru64 UNIX and Open VMS,pH           refer to the AlphaServer Platforms Support section for support           information)  ;         * Memory Channel II (Compaq Tru64 UNIX and OpenVMS)            * TS202C      * I/O - Analysis   F         * Disk Storage based on SCSI specification (Compaq Tru64 UNIX,           OpenVMS, and Windows)3  3         * EZ4X/EZ6X (Compaq Tru64 UNIX and OpenVMS)g  3         * EZ5X/EZ7X (Compaq Tru64 UNIX and OpenVMS)C  ;         * HSG60/HSG80/HSZXX (Compaq Tru64 UNIX and OpenVMS)h           * HSG60/HSG80 (Windows)i      * I/O - BTT           * RA3000  3         * KZPSC/KZPAC/KZPBA/KZPCM/KZPSA/KZPCC/KSPEAR  2         * KGPSA-CA (Compaq Tru64 UNIX and OpenVMS)           * CCMAB-AA           * CIPCA-BA   AlphaServer Platforms Support   D Please refer to the operating system's SPD for information about the= platforms supported by the various operating system versions.   F If you need to update your platform's firmware, refer to either of the+ following locations for the latest version:i  "    * The Alpha Systems Firmware CD  K    * The Alpha Systems Firmware - Firmware Updates web page, located at the1      following URL: 3      http://www.compaq.com/support/files/index.htmle   1.4 Supported Operating Systemst  K Compaq Sustaining Engineering maintains a schedule of support for the Tru64IH UNIX and OpenVMS operating systems. Compaq does not commit to supportingI WEBES when installed on an operating system version that has exceeded itsr+ end-of-support date. See the following URL:   ; http://www.compaq.com/services/software/ss_pvs_se_amap.html   ) 1.5 Translation and Analysis Capabilities.  F The following sections describe the translation capabilities of Compaq( Analyze and the message types supported.  )      1.5.1 Binary Event Log Decompositioni  D Compaq Analyze formats and displays binary event log entries for the
 following:      * Compaq AlphaServer DS10      * Compaq AlphaServer DS10Lr      * Compaq AlphaServer DS20      * Compaq AlphaServer DS20ei      * Compaq AlphaServer ES40      * Compaq AlphaServer ES45      * Compaq AlphaServer GS80      * Compaq AlphaServer GS160       * Compaq AlphaServer GS320r      * Memory Channel II  1    * Common Access Method (CAM) error log entries.      * Logged message entries       * TS202cS  .      1.5.2 Machine Check Error Log Entry Types  = The binary event log entries processed by Compaq Analyze are:t   Machine Check Entriesd       * CPU Correctable Error (630)  "    * CPU Uncorrectable Error (670)  #    * System Correctable Error (620)s  %    * System Uncorrectable Error (660)r      * System Environmental (68x)       * Console Data Log (113)u  4    * Correctable Error Throttling Notification (120)   I/O Error Log Entries       * CAM SCSI Entry Type (199)   Miscellaneous Entry Types=      * Generic Information      * Startup Message      * Shutdown Messagel      * Panic Message      * Time Stampo      * Diagnostic Messager      * Repair Messagey  #      1.5.3 GS Error Log Entry Typesa  C All GS160 Uncorrectable Errors (660/670) for the following hardwarea	 entities:e      * PCI      * PCA      * FE-minilink      * Hosecable      * NE-minilink      * IOP      * CPU      * Memorya      * Global port  ; All GS160 System Faults reported by the following entities:i      * PCA      * FE-minilink      * Hosecable      * NE-minilink      * IOP      * CPU      * Memoryv      * Global port      * Hswitch  	    * Dtagi      * Directory      * QSA      * QSD  # GS160 correctable errors (620/630):l  )    * Memory Correctable Read Errors (620)   *    * Memory Correctable Write Errors (620)  ;    * Added OS Indictment API support memory PFNs and DIMMs.o  ,    * Directory Correctable Read Errors (620)  E    * Uncorrelated correctable errors between GP GPL and HSwitch (620)   E    * Uncorrelated correctable errors between GP HSL and HSwitch (620)o  +    * All Processor Correctable Errors (630)    GS160 System Events (68x/113):       * All PSM, PBM and HPM events      K ===========================================================================t   2n   *** General Limitations ***   F This chapter describes the general limitations for Compaq Analyze that apply to all operating systems.        * Interface Independent Notes      * CLI Notes      * Web Notes   2.1 Interface Independent Notess  2 The following limitations apply to all interfaces.  $      2.1.1 Time Stamp Interpretation  K If an event in a binary log includes a Storage Event Header (SEH) or Common F Event Header (CEH), that information is used to provide the time stampI information for analysis results. If the event only includes a Windows NT 8 header, no time stamp is included with analysis results.  J In addition, when you translate an event that includes a SEH or CEH headerE in addition to a Windows NT header, both time stamps are shown in the H translation results. However, unless the machine responsible for loggingB the event is located in the GMT time zone, the time stamps will be
 different.  I The event time is also displayed in the event description (located at thecJ top of a translated event). Depending on the contents of the event and theH Compaq Analyze interface used to translate it, the translated output may include different information:  J    * If the event includes a SEH or CEH header, the time stamp informationI      from that header is included in the event description. If the headertI      has invalid date information the current date is shown along with ane      error message.e  H    * If you are using the web interface and the event only has a WindowsC      header, no date information is shown in the event description.i  H    * If you are using the CLI to send the translation to the screen or a@      text file and the event only has a Windows header, the dateF      information from the header is included in the event description.  H    * If you are using the CLI to send the translation to a HTML file andI      the event only has a Windows header, no date information is shown inu      the event description.    SEH and CEH Headerso  H SEH and CEH time stamp information is stored as a string and reported inG the TLV_Time_as_Local field of a translated event. It has the followingt format:     Jan 11, 2002 3:06:09 AM GMT-0600  H This indicates the time the event was logged, in the time zone where the5 machine responsible for logging the event is located.l   Windows Headerse  A The Windows NT header stores time stamp information as an integeroJ indicating the number of seconds that have elapsed since epoch (January, 1I 1970 00:00:00 AM GMT). These integers are translated into a date and time.J and reported in the WNT_GMT_Time_Generated and WNT_GMT_Time_Written fields1 of a translated event using the following format:C   Jan 11, 2002 9:06:09 AM GMTo  K Since the Windows NT header does not include any information about the timedJ zone where the logging machine is located, the GMT time zone is used. ThisB does not mean the logging machine is located in the GMT time zone.  +      2.1.2 Date Reported By Summary Commandr  H When you view the summary of a log file's contents (either using the webH interface or the CLI), the Last Entry Time field may display the currentE date and time. This occurs if the last event in the log file containslA invalid data and Compaq Analyze cannot determine the actual date.,  1      2.1.3 Event Type Reported By Summary Commandr  H If an event does not have an CEH or SEH header or does not contain validI data, Compaq Analyze reports the event type as 0. If the event type is 0, J the Summary command (in both the web interface and CLI) indicates that theJ event is Unrecognized/Unsupported. As a result, events that only contain aI Windows header are reported as Unrecognized/Unsupported, even though theyU are translated correctly.h  4      2.1.4 Serial Number Prevents Rules From Working  K The system serial number on some GS80, GS160, and GS320 systems was not setOK correctly. The Compaq Analyze rules will only function if the serial numberp is set correctly.o  
 Workaround  A You can check and correct the serial number from the SRM console:p  4 Check the serial number using the following command:   show sys_serial_num   K The serial number should match the actual system serial number given on theS model/SN tag in the power cab.  B If necessary, change the serial number with the following command:   set sys_serial_num  D You should enter the six-character serial number provided on the tagI located in the power cabinet. The serial number begins with the letter G.   ,                                 *** Note ***  @      If multiple systems were ordered, they may all use the sameB      serial number. As a result, the Compaq Analyze rules will not@      work correctly because they require that each system have a@      unique serial number. If this is the case, when you set theB      serial number, append a -1, -2, or -3 to the serial number to#      uniquely identify each system.v  $      2.1.5 Resource Usage Seems High  E Whenever Compaq Analyze starts, and when you run manual analysis, thelF program appears to use a lot of system resources and processor cycles.J However, Compaq Analyze uses only the capacity that is not being asked for by other programs.  E Compaq Analyze always relinquishes processor cycles to other programs B whenever they need them. In other words, the program uses whatever resources are available.  G At startup Compaq Analyze needs the available capacity for the scavengetE process (see Section 2.1.8 for information on configuring the delay).hI Depending on the system, and the size and content of the log, the initialwC startup pass can take many minutes or even hours to complete. After K completing the scavenge process, Compaq Analyze drops into idle mode, where , resource usage hovers at only a few percent.  K If you run Compaq Analyze in manual mode, large amounts of system resourcesyF and processor cycles might also get used. As in the case of startup inI automatic mode, the condition is directly related to the size and contentaH of the log being processed. Once again by design, Compaq Analyze uses as> many resources as are available until processing is completed.  I You can speed processing by managing the system error log so that it doesrD not grow indefinitely. When you are using manual analysis, it may beJ beneficial to filter large log files in order to improve processing times.  B      2.1.6 Starting the Director Process Results in High CPU Usage  I When the Director process is first started, it analyzes the entire binaryeI event log. Performing this analysis takes time and may result in high CPUlF usage. However, once the Director process has completed processing theH binary event log file, CPU usage is reduced significantly and new eventsJ are processed in real time. Thus, when you first start Compaq Analyze, you4 may notice some impact on your system's performance.  J The initial analysis occurs only once, four minutes after the Director hasJ been started (see Section 2.1.8 for information on configuring the delay).H Subsequent restarts of the Director should not result in significant CPUG usage except for the normal startup tasks, which may take from 10 to 30I seconds.  ;      2.1.7 Commands Time Out During Scavenge or Heavy Loads   J Four minutes after the DESTA Director process starts, a scavenge operationK processes the events from the native binary event log that have not already D been processed (see Section 2.1.8 for information on configuring theK delay). If there are numerous events to process, such as the first time the E scavenge operation occurs, the DESTA Director process may be too busyrI scavenging to respond to other requests from the web interface or the CLI2A before their time-outs expire, thus, causing the request to fail.   H Manual translation or analysis of large binary event logs also may causeH the Director to become too busy to respond to other requests in a timely manner.s  D Resource loading and time-outs will be improved in a future release.  
 Workaround  J Wait for the resource-intensive activity to complete and for the system toD become idle again, then repeat the command or operation that failed.  .      2.1.8 Configuring the Scavenge Start Time  G Normally, the scavenge operation begins 4 minutes after the Director isaF started. Scavenging picks up native events for automatic analysis thatB occurred while the Director was not running. If there are numerousI analyzable events, this operation can consume significant resources untilp
 completed.  D You can configure the scavenger delay time by changing the scavStartH attribute of the reader service in the Web Interface's Director SettingsF screen (refer to the Compaq Analyze User Guide for details on changingJ attributes in the Web Interface). The name of the reader service varies by operating system:l      * Windows - NTReadera      * Tru64 UNIX - DUReader      * OpenVMS - VMSReader.h  J Changes to the scavenger delay time take effect the next time the DirectorE is started. Be aware that because the reader service depends on othertF service having completed their startup tasks, it is not recommended to  lower the value below 2 minutes.  J No live event processing is performed until scavenging has been completed,H but any events that occur during the delay before scavenging starts will7 either be processed during or shortly after scavenging.   +      2.1.9 Fragmented Disk Slows Processingf  I Processing binary event logs manually may be significantly slower becausehI of interaction between virus detection software and a fragmented disk. IniI order to process binary event logs as quickly as possible, make sure that ) your disk has been defragmented recently.n  F      2.1.10 Initializing System Error Log With Director Running Causes      Errors   H If the system error log is re-initialized while the Director is running,E events may be missed or processed incorrectly. To avoid this problem,nK either re-initialize the system error log before the Director is started or 8 stop the Director before modifying the system error log.  C      2.1.11 Changing IP Address Causes Director to Stop Functioningp  G If WEBES is installed on a system without a fixed IP address, such as arH network that assigns IP addresses using DHCP (Dynamic Host ConfigurationB Protocol), and the IP address changes, the Director will no longer	 function.   E Similarly, if you connect to a network, disconnect from a network, or F change the network connection of your machine (for example from LAN toK Modem ISP) after the Director has been started, the IP address will change.iG As a result, the Director will cease to function properly. For example,9K starting a Windows machine with no network connection gives the Director an G IP address of 127.0.0.1 (localhost loopback). If you later connect to afI network, the machine obtains a real IP address, but the Director will not > function because it still assumes the IP address is 127.0.0.1.  J If you know the IP address will change, stop the Director until the changeK is complete, then restart the Director. Be aware that stopping the Directori stops all the WEBES components.t  (      2.1.12 Disabling Automatic Analysis  F By default, Compaq Analyze operates in automatic analysis mode. If theG binary event log contains entries for hardware that is not supported byiG automatic analysis you may want to change the default settings. You canmI disable automatic analysis from the settings window in the web interface.oJ Refer to the Compaq Analyze User Guide for information about modifying the	 settings.c  F      2.1.13 Bad Translation or Analysis Due to No Knowledge Registered  D On some systems, the WEBES installation may not register the defaultB knowledge correctly. This problem may affect the event translation6 knowledge or the analysis rule set knowledge, or both.  H If Compaq Analyze analysis does not produce the expected problem reportsG from a binary event log, determine if there are any knowledge rule setsa5 registered using either the CLI or the web interface.   /    * From the CLI, enter the following command:         ca listrk  I      If there are no knowledge files registered, the following message ish      returned:  -      There are no knowledge files registered.     * From the web interface:K      Click the Settings button in the toolbar, select the Director Settingsr7      tab, and then click the Register Knowledge button.   H      If there are no knowledge files registered, none of the check boxes      will be selected.  C If no knowledge files are registered, register the default analysis  knowledge files.  ;    * From the CLI, use the following procedure to register:   #        1. Stop all WEBES processes.   B        2. Delete the decorEvt*.* files from the ca/data directory.          3. Restart the Director.   C        4. Re-register the default rule sets with the ca regknw rdefa           command.  9    * From the web interface, use the following procedure:eE      Click the check boxes next to the knowledge files in the ca\data G      directory and then click the Update Knowledge Registration button.h  K If Compaq Analyze still does not produce the expected problem reports, viewgD the translated events from the binary event log using either the web" interface or the ca trans command.  C If the translated output resembles the following example, the eventy, translation knowledge may not be registered:  B com.compaq.svctools.desta.services.decomposers.DecompNavException:1 No frame found to continue processing this event.C& 0000: FE FF FF FF C0 00 00 00 ...& 0008: 50 04 00 00 02 00 00 00 P.......& 0010: 01 00 04 00 EC 0D 00 00 .......& 0018: 22 00 00 00 00 00 00 00 ........& 0020: 01 00 00 00 02 00 00 00 ........ ...a  F If this is the case, repeat the procedure for registering the analysisE knowledge and then enter the following command at the command prompt:h   desta bldknw  E This process will re-register the event translation knowledge and the  analysis rule set knowledge.  (      2.1.14 Fields Contain "Unavailable"  G This note applies to DS10/DS10L, DS20/DS20E, ES40, and TS202c products.r  H When a valid configuration tree event is accessible, output will includeJ information in the Part Number, Serial Number, and FW Rev Level fields. IfH a valid configuration tree event could not be accessed, these fields are reported as "Unavailable."  2      2.1.15 File Not Found Error In DESTA Log File  = The following error message may appear in the DESTA log file:o  . Could not find file: CAApplet403BeanInfo.class  K It is safe to ignore this message since it does not impact the performance,f. stability, or functionality of Compaq Analyze.  '      2.1.16 DSNLink (SICL) Connectivitye  E There are known DSNLink issues that may result in problems if you useaK DSNLink to provide SICL functionality, and you connect to DSNLink via modemf or X.25.  
 Workaround  K Configure your DSNLink installation to use TCP/IP instead of modem or X.25,  if your network supports it.  #      2.1.17 Spurious Error Messagess  G When you analyze multiple log files, spurious messages may appear along D with the normal output. This can occur if you use a CLI command that? processes multiple log files. If you process multiple log filesgJ simultaneously with the Web Interface, spurious messages may appear in theD Director log file (desta_dir.log). In general, spurious messages areJ proceeded by a string value enclosed in square brackets. Some examples areB shown here, however, you should be aware that this list is not all
 inclusive.  = [mdgs320_se_rule], clRPT_Errlog, init, Duplicate clRPT_ErrlogeI [mdgs320_uce_rule], %WF660_main, processing errlog entry 23248.1 - 25 Octh 2000 13:20:45 -0600 (config)? [mdgs320_uce_rule], %WF660_main, completed errlog entry 23248.1n+ [mdPrivateer], fnSysCsRd, Invalid Arguments   ) These messages can be safely disregarded.,  I      2.1.18 Duplicate Callouts when DECevent and WEBES Installed Togethera  .                                   *** Note ***  K      This situation is most likely to arise when newer Alpha platforms withiK      WEBES (such as GS160) are connected to clusters containing older AlphafF      platforms with DECevent (such as GS60 Turbolaser), however, other2      circumstances may also have the same effects.  C Running DECevent and WEBES on the same machine results in duplicatemC callouts to the CSC when event notification occurs. To resolve this K problem, you can choose to only start one of the applications at boot time.r  
 Tru64 UNIX  G To prevent DECevent from starting on a UNIX platform, use the followingr
 procedure:  =   1. Edit the startup script, /opt/DIAXXX/sbin/init.d/dia_s_kr.      Where XXX is the DECevent version number:  9   2. On line 64 of the script, remove the following code:D        if [ -f /usr/sbin/dia ]	      thena4   3. Insert the following code in the same location.D      Replace nodename1 with the name of the node that should not runB      DECevent. If there are multiple cluster nodes that need to beG      modified, add a similar bail="true" line for each affected clusterm
      node.  
      bail=1      [ "$HOSTNAME" = "nodename1" ] && bail="true"h*      if [ -z "$bail" -a -f /usr/sbin/dia ]	      thenl  D To prevent WEBES from starting on a UNIX platform, use the following
 procedure:  ,   1. Execute /usr/sbin/webes_install_update.  ,   2. Select menu item 4, Start at Boot Time.  #   3. Answer yes to change the list.n  ;   4. Add the node names of the nodes that should run WEBES.c   OpenVMS   F To prevent DECevent from starting on a VMS platform, use the following
 procedure:  ?   1. Edit the startup script, sys$startup:decevent$startup.com.s  <   2. Insert the following code at the beginning of the file:  .                                   *** Note ***  H           Verify the existance and format of the SYS$NODE logical before$           performing this operation.  '      $ node = F$TRNLNM("SYS$NODE",,,,,) 0      $ IF (node .EQS. "nodename1::") THEN EXIT 1  D      Replace nodename1 with the name of the node that should not runB      DECevent. If there are multiple cluster nodes that need to beD      modified, add a similar IF line for each affected cluster node.  C To prevent WEBES from starting on a VMS platform, use the followingi
 procedure:  <   1. Edit the startup script, sys$startup:desta$startup.com.  <   2. Insert the following code at the beginning of the file:  '      $ node = F$TRNLNM("SYS$NODE",,,,,)r0      $ IF (node .EQS. "nodename1::") THEN EXIT 1  D      Replace nodename1 with the name of the node that should not runB      DECevent. If there are multiple cluster nodes that need to beD      modified, add a similar IF line for each affected cluster node.  
 2.2 CLI Notes   > The following limitations apply to the command line interface:  *      2.2.1 Syntax Changes Affect All Users  I Changing the default syntax affects all the users on the system. Thus, ifoK another user changes the default syntax, it will affect your Compaq AnalyzedF session. To ensure that your commands are interpreted correctly, it isJ recommended that you always include a syntax designator when you are using* a command that supports multiple syntaxes.  
 2.3 Web Notese  5 The following limitations apply to the web interface:   .      2.3.1 Director Communications Limitations  J Different versions of the WEBES Director (including different Service PaksK of the same version) may not communicate correctly. As a result, if you aredB logged into a system and attempt to connect a node that is using aJ different version of WEBES, you may not get the expected analysis results.E If you need to monitor multiple nodes using different versions of thetF Director, open a separate browser window for each Director version and connect to the nodes directly.  J Compaq Analyze version 4.0 for UNIX and VMS is not compatible with versionJ 4.0 for Windows. You must install the latest Service Pak on all UNIX, VMS,@ and Windows systems before they can communicate with each other.  5      2.3.2 Node Name Changes Cause Connection Failureb  K If a system's network name changes, the change must be reflected in the webiD interface. After a node's network name changes, the old network nameI remains in the web interface and the connection to the node is lost. ThisfF occurs even if the name change occurs on the localhost. Thus, for nameJ changes on any node, click on the node's group icon in the navigation treeI and delete the old node name. Then add the node again using the new name.t  .      2.3.3 Problems Connecting to Remote Nodes  I If you use the web interface to add a remote Windows node, you may not be I able to use the Full View option on the remote machine. If the local hosteG is running Windows, full view monitoring will fail unless the operatingiI system is installed in the same place on both machines. If the local host H is running UNIX or VMS, you will not be able to use the Full View option" for any added remote Windows node.  
 Workaround  I Rather than using the Full View feature, add the remote machine's Windows K event log to the Other Logs area. To add the Windows event log to the OthernI Logs area, type the path and name of the event log in the Add File screenh% (by default the Windows' event log ishI C:\WINNT\system32\config\AppEvent.Evt). Once the event log is added underv? the Other Logs area, you can perform manual analysis as normal.r  (      2.3.4 Internet Explorer Limitations  A If you are using Internet Explorer as your browser, the followingn% limitations affect the web interface:g  /           2.3.4.1 Java Virtual Machine Requiredm  K Compaq Analyze requires the Microsoft Java Virtual Machine (VM). If you are I using Internet Explorer version 5.x and have not installed the VM on your.J machine, you may be asked to install it when you attempt to logon. You can install the Java VM by:   C    * Following the instructions when you attempt to logon to Compaq 
      Analyze.   9    * Using your browser to access the following web site:a  '      http://windowsupdate.microsoft.comh  H      From the Windows Update page, select the "Product Updates" link and8      follow the instructions for installing the Java VM.  #           2.3.4.2 HTTP 1.1 RequiredS  K The "Use HTTP 1.1" option must be enabled for the web interface to function F properly. To enable the option, select Internet Options from the ToolsG menu. From the Options window select the Advanced tab and make sure thee- check box next to "Use HTTP 1.1" is selected.e  *           2.3.4.3 Partial URLs Not Allowed  H When you access the web interface, you must preface the URL with http://I (for example, enter http://16.23.132.145:7902/ in the address line rather E than 16.23.132.145:7902/). If you do not enter the full URL, Internetn6 Explorer will stop responding and the system may hang.  1           2.3.4.4 Navigation Icons Updated Slowly   C Internet Explorer does not update the icons in the navigation frameoJ quickly. Thus, if automatic analysis results in a problem report or manualE analysis completes, the icon changes will not be visible immediately.t  :           2.3.4.5 Icons May Disappear If New Window Opened  J If you are using Compaq Analyze and open a new browser window, some of theJ icons in the first browser window may disappear. The icons can be restored( by clicking the browser's Reload button.  C           2.3.4.6 Event Details Cannot Be Viewed In Separate Window   F The web interface user settings can be used to view event details in aJ separate browser window. Version 4.x of Internet Explorer does not display4 event details correctly when this option is enabled.  0           2.3.4.7 Progress Bar Indicates Loading  F The progress bar at the bottom of the window indicates that loading is3 still occurring, even after a page is fully loaded.s  G You can determine when loading has finished by watching the upper rightuH corner of the web interface. The text Loading New Page appears while the9 page is loading and disappears once loading is completed.d        2.3.5 Netscape Limitationst  K If you are using Netscape as your browser, the following limitation applies  to the web interface:*  *           2.3.5.1 Netscape 6 Not Supported  I The web interface does not support Netscape 6. If you want to use the webtJ interface with Netscape, you will need to use an earlier version. Refer toJ the Compaq Analyze User Guide for information on the supported versions of	 Netscape.u  &           2.3.5.2 Java Must Be Enabled  G In order to use the web interface, Java must be enabled in your browsersG settings. To enable Java for Netscape, select Preferences from the EditiJ menu and click on Advanced. Make sure the check box next to Enable Java is	 selected.t  %           2.3.5.3 Excessive CPU Usage   K If you are using Netscape 4.x with Compaq Analyze, you may notice excessive J CPU usage. Some browser requests to Compaq Analyze, may result in NetscapeD using 100% of the local system's CPU. This problem occurs if you areJ browsing with Netscape on the same system where Compaq Analyze is running.A When Netscape is using all of the CPU, Compaq Analyze, which is auG background process, does not respond in a reasonable amount of time. IntI most cases, this issue occurs in conjunction with requests such as addingS files to Other Logs.  H If Netscape is using all of the CPU, the browser will appear to wait forJ Compaq Analyze. Check your system's CPU usage and determine if Netscape is. consuming the majority of the processing time.  
 Workaround  H Wait twenty to thirty seconds and click the Stop button in the browser'sH toolbar. Any necessary updates are shown in the navigation tree, and youJ can continue to use Compaq Analyze normally. If necessary, you can refreshI the display frame by right-clicking on it and selecting Reload Frame frompE the pop-up menu. Do not use the Reload button located in the Netscape  toolbar.  5           2.3.5.4 Overlapping Text in Navigation Treey  K Netscape may not display the contents of the navigation tree correctly. ThetI entries in the tree may not collapse properly and as a result entries may G appear to be overlapping and blank lines appear in the tree. To fix theoJ navigation tree, collapse and expand the parent entry of the entry that is displayed incorrectly.  %      2.3.6 Bookmark May Create Errorse  H Do not bookmark the web interface after logging on under a username. ForH example, bookmarking a URL similar to http://nodename:7902/?profile=userK results in errors. To bookmark the web interface, bookmark the logon screenf (http://nodename:7902).   <      2.3.7 Using the Back Button to Access the Web Interface  J If you leave an active web interface session to visit a different web pageJ and the logout time expires, clicking on the back button to return to yourG web interface session will result in multiple errors. In order to logon H again, return to the root address of the node (http://nodename:7902) and repeat the logon procedure.h         2.3.8 Link Color Inaccurate  G Under normal operation, the color of hyper-text links changes after thesH link is visited. Compaq Analyze presents dynamic data that is frequentlyI updated, however, the links used to access the information do not change.eK As a result of this presentation, the color of links in the navigation treehK may be erratic or incorrect. In most cases, the color of visited links will  not change.w  /      2.3.9 Group and Category Name Restrictionss  I Do not use punctuation in the group or category names that you add to the I navigation tree. If you use punctuation characters, JavaScript errors mayl' occur when the navigation tree reloads.a  H If you see JavaScript errors caused by a group name, you can dismiss theK error message by clicking the OK button. To correct the problem, remove theeJ offending name and replace it with a new name that does not use one of the restricted characters.  "      2.3.10 Refreshing the Display  D If the web interface is not updating correctly, click your browser'sH refresh button. This will reset the display and open the about screen in the display frame.        2.3.11 Null-Pointer Errorst  K If a NullPointerException error occurs while using the web interface, click K your browser's Refresh button. If you continue using Compaq Analyze without G refreshing, you may encounter additional errors or unexpected behavior.a        2.3.12 JavaScript Errorsc  F During heavy processing, you may see JavaScript errors. You can safelyD ignore these errors. Depending on the error dialog box that appears,% respond in one of the following ways:e  1    * Click the OK button on the error dialog box.i  J    * If the dialog box asks if you want to continue running scripts, click      the Yes button.   Netscape 3.x and JavaScriptd  D If you are using Netscape 3.x or later and you attempt to resize theE browser window while using Compaq Analyze, Netscape reloads the page.a  I Due to the JavaScript limitations of Netscape 3.x, anytime the navigationn2 tree is refreshed you may see the following error:  # Javascript Error: xxx..., line 159:p Undefined is not a number.  K This error has no effect on Compaq Analyze's behavior or functionality. Your- can ignore the error and click OK to proceed.r  F When you are selecting tabs in the display window (such as the ProblemH Reports and Events tabs shown for processed event logs), you may see the following error:  # Javascript Error: xxx..., line nnn:./ access disallowed from scripts at http://xxx...e  to documents at another location  H You can ignore this error and click OK to proceed. Compaq Analyze is notK trying to access any location other than the node you are connected to, andeK is functioning correctly. If this error message appears frequently, you may F be able to reduce the occurrences by logging off and then logging into Compaq Analyze again.p  E These Javascript issues have been fixed in Netscape's later releases.y        2.3.13 Timeout Issuey  D If you consistently receive timeout notifications when using the webG interface for a specific function, use the same function in the Command  Line Interface as a workaround.          2.3.14 Logout Time Set to 0  J If you set the logout time to 0, you will be logged out and lose your data in the following situations:  0    * If you click your browser's Refresh button.  E    * If you click on a link that opens a page outside Compaq Analyze.o  '      2.3.15 Restricting Remote Machinesf  F Compaq Analyze can connect to other machine's Directors using a set ofE standard IP port numbers. You can restrict access to your Director bysJ changing the ports to nonstandard numbers and only disclosing the new portJ numbers to people who need access. For more information on configuring the+ ports, refer the Compaq Analyze User Guide.e  #      2.3.16 Hostname Not Recognizedr  H Unless the target system is accessible through your nameserver, you mustJ use the IP address instead of the name of the node for remote connections.  A For example, the hostname of a Windows machine using Dynamic HostoD Configuration Protocol (DHCP) is not listed with the nameserver, andE therefore must be added using its IP address instead of its hostname.t  *      2.3.17 Cannot Activate a Running Node  J If you cannot activate a node that is currently running, continue to clickH on the "Activate Node" entry in the navigation tree intermittently until the node is activated.  #      2.3.18 Negative Timeout Values   J Using the web interface settings window, you can change the timeout valuesH for the EvtAnalyzer component. If you need to change settings, make sureI that the timeout value for the WForDecomp attribute is a positive number.i  D If the timeout value is a negative number, Compaq Analyze will fail.      K ===========================================================================h   3g  - *** Operating System Specific Limitations ***a  J This chapter describes the Compaq Analyze limitations associated with each operating system.i  %    * Notes for Tru64 UNIX and Windowsh      * Notes for Tru64 UNIXc      * Notes for OpenVMS      * Notes for Windows  $ 3.1 Notes for Tru64 UNIX and Windows  ? The following limitations apply to both Tru64 UNIX and Windows.i  $      3.1.1 Entering Paths in the CLI  H When you are entering paths in the CLI you must pay special attention to" any space or backslash characters.             3.1.1.1 Spaces  A If you specify a path that contains spaces, it must be wrapped indJ double-quotes. However, this causes some operating system specific issues.E When using this method to pass path or filename arguments to a non-OSaG program, the Windows and Tru64 UNIX shells do not expand path wildcardsb wrapped with double-quotes.s  J For example, "C:\Program Files\someDirectory\*.zpd" does not expand to allB the *.zpd files in the directory "C:\Program Files\someDirectory".  
 Workaround  G Change to a directory in which you do not have to use double-quotes andmF execute the Compaq Analyze CLI command of choice. For instance, in the$ example, do either of the following:   C:\>cd C:\Program Filesa  C:\>ca trans someDirectory\*.zpd   or  % C:\>cd C:\Program Files\someDirectorye C:\>ca trans *.zpd  	 Exceptionu  H Windows does not require the second double-quote, since it automaticallyF completes the set of quotes. Thus, if you enter the following command:  7 C:\>ca trans "C:\Program Files\someDirectory\hscir1.zpds   Windows interprets it as:h  8 C:\>ca trans "C:\Program Files\someDirectory\hscir1.zpd"        3.1.1.2 Backslash  H Furthermore, with Windows, if a backslash character (\) is placed at theJ end of a double-quoted directory, the double-quote following the backslashI is treated as part of the text passed to the program. This causes WindowsnJ to treat all characters, including spaces, before the end of the line as aC single argument. For example, if you enter the following arguments:a  5 "C:\Program Files\someDirectory\" C:\anotherDirectorye  ; They are interpreted by the Windows command interpreter as:n  5 "C:\Program Files\someDirectory" C:\anotherDirectory"   A The second double-quote is considered part of the literal line oftH characters and the third double-quote is added by Windows. Thus, the twoH arguments are passed to the program as a single argument with a embedded double-quote character:T  3 C:\Program Files\someDirectory" C:\anotherDirectoryr   Workaround:e  ) There are two ways to avoid this problem:   J    * Do not place a trailing backslash character following a double-quoted      directory name.  A    * Place two consecutive backslash characters at the end of the2"      double-quoted directory name.  5 For example, you could replace the following command:   5 "C:\Program Files\someDirectory\" C:\anotherDirectoryt  & With either of the following commands:  4 "C:\Program Files\someDirectory" C:\anotherDirectory6 "C:\Program Files\someDirectory\\" C:\anotherDirectory  0      3.1.2 Transferring Event Log Files with FTP  H If you use FTP to transfer binary event log files between machines, makeG sure that the transfer mode is binary rather than ASCII. Compaq AnalyzeeC does not generate an error message when you process a file that was B transferred in ASCII mode, but it may skip some events and produce unreliable analysis results.   3.2 Notes for Tru64 UNIX  . The following limitations apply to Tru64 UNIX.  9      3.2.1 Compaq Analyze Now Polls for New Events (UNIX)   G Compaq Analyze no longer uses the UNIX binlogd daemon to get new binarytK events for automatic analysis. The binlogd daemon has problems which causeddK the Director to crash in some circumstances. As a result, Compaq Analyze norD longer receives events as they occur. In the current release, CompaqK Analyze polls (re-reads) the native binary event log /var/adm/binary.errlog % every 5 minutes to obtain new events.y  E You can configure the period for polling by changing the new pollTimeoJ attribute of the DUReader service in the Web Interface's Director SettingsF screen (refer to the Compaq Analyze User Guide for details on changing! attributes in the Web Interface).t  ,                                 *** Note ***  A      The new pollTime attribute appears on all platforms but onlyn       affects Tru64 UNIX systems.  :      3.2.2 Network Connection to Local IP Address Time Out  K On a Tru64 UNIX system with PPP as its only non-loopback interface, networkf- connections to the local IP address time out.z  
 Workaround  K Add an entry to the routemap table with the local IP address routed through2: the loopback interface, as shown in the following example:   # ifconfig ppp0o' ppp0: flags=51<UP,POINTTOPOINT,RUNNING>D@   inet 10.0.0.2 --> 10.0.0.1 netmask ffffff00 ipmtu 576 trustgrp	   unknownn # route add 10.0.0.2 127.0.0.1        3.2.3 Memory Errors  G When Compaq Analyze is used with large event logs, processing may abortcJ with an out-of-memory message, a communications error, or a streams error.H If you are using the web interface, these errors are logged in the DESTAJ Director log. If you are using the command line interface, the errors will appear on the screen.p  
 Workaround  F Use the filtering tools to create a new, smaller event log, and try toK process the new log. See the Compaq Analyze User Guide for more informationh on filtering event logs.  F Try increasing the total swap space allocation on your system. See theD WEBES Install Guide for more information on swap space requirements.  G On multiprocessor systems, if you have already tried creating a new logyF file and still receive processing errors, you may be able to eliminateH those errors by forcing the DESTA Director to run on only one processor.I When the DESTA Director runs on only one processor it is less susceptiblelI to internal synchronization problems, and as a side benefit, it uses lessc' memory. However, throughput is reduced.f  3 To set DESTA Director to run on only one processor:l  :   1. Stop the Director (desta stop from the command line).  F   2. Using any text editor, append the following line to the DESTA.REG-      file. (The default path for this file isu,      /usr/opt/compaq/svctools/desta/config.)        desta.CPUAffinity=t  >   3. Restart the Director (desta start from the command line).  K Another workaround is to remove the swap space limitation that the Director H imposes on itself to prevent it from using too much of the system's swapF space. Normally, swap space usage is limited to half of the total swap@ space allocated by the system. Be aware that this workaround canJ potentially allow the Director to hang or crash the machine if it uses allG the available system swap space. The Director process and the availablenH swap space must be monitored during the time this workaround is in placeE (Refer to the Compaq Analyze User Guide for details on monitoring theu
 Director).  B To remove the swap space restriction, use the following procedure:  .   1. Stop the Director (/usr/sbin/desta stop).  I   2. In the file /usr/opt/compaq/svctools/bin/desta, change the followingy
      line:        ulimit -v $ulimitvNEW      to:      ulimit -v $ulimitvOLD  2   3. Restart the Director (/usr/sbin/desta start).  K The change only affects the Director process, not any other WEBES processese( such as command-line analysis processes.  ,      3.2.4 Cannot Load Shared Object Library  D Tru64 UNIX may not correctly open WEBES shared object libraries whenJ running under the default Fast Virtual Machine (VM). Follow these steps ifB WEBES does not behave correctly and the following error appears inG /usr/opt/compaq/svctools/logs/desta_dir.log. The library name in __ cann vary:   = EXCEPTION java.lang.UnsatisfiedLinkError: dlopen: cannot loada' /usr/opt/compaq/svctools/share/lib__.sot  0   1. As the root user, type /usr/sbin/desta stop  H   2. Manually edit the file /usr/opt/compaq/svctools/bin/desta. Look for      the following line:  3      DESTA_CMD_NO_PREFIX="$JAVA_HOME/bin/java -fast=9      -DSvctools.Home=$SVCTOOLS_HOME -DSwcc.Home=/var/adm"n  /   3. Remove the -fast flag and replace it with:d        -ss512K -mx256M  I      This disables the Fast VM and reverts WEBES to the Classic VM, whichuF      does not exhibit this behavior. Be aware that performance will be      slower.  K      You also may see error messages about swap space while executing WEBESaJ      CLI commands. The messages can be safely ignored unless you are trulyK      low on swap space. (Type /usr/sbin/swapon -s to see how much is left.)t      4. Type /usr/sbin/desta setsub     5. Type /usr/sbin/desta start   F   6. Report this problem to product support for further investigation.  $      3.2.5 Time Reported Incorrectly  K Tru64 UNIX v5.1 does not correctly log the time in Common Event Headers and K Storage Event Headers. As a result, the time reported by Compaq Analyze maya% not have the correct offset from GMT.-   3.3 Notes for OpenVMS"  + The following limitations apply to OpenVMS.e        3.3.1 Director Crashesn  K OpenVMS versions 7.1-2 and 7.2 include issues with thread handling that mayiD cause the WEBES Director to crash. These crashes may occur in either automatic or manual mode.d  
 Workaround  F If the Director crashes and does not appear in the SHOW SYSTEM output,K restart the Director and try the operation again. If the Director continues\K to crash, you will need to process the event log on a different platform ort, a system running a newer version of OpenVMS.  E If the Director crashes repeatedly during the scavenge operation that K occurs when Compaq Analyze is started, disable automatic analysis using thee6 procedures described in the Compaq Analyze User Guide.        3.3.2 Startup Errors2  H VMS systems may experience problems during Desta startup if the DirectorJ setting logMinSeverity was set to INFO or DEBUG prior to the last DirectorE shutdown. When this occurs, the desta start command displays an errorcI message stating that the Director may not have started correctly, and thefJ web interface is unable to activate the local node. In addition, the destaA stop command may not successfully stop the Director (and its CCAT ! subprocess if CCAT is installed).w  
 Workaround  F To avoid this problem, if the logMinSeverity setting is set to INFO orI DEBUG make sure that it is reset to WARNING before stopping the Director.e  C To recover should the problem occur, use the stop/id DCL command toeJ manually stop the Director and CCAT processes (for more information on theG naming convention used for WEBES processes, refer to the Compaq Analyze H User Guide). Manually resetting the logMinSeverity setting requires thatC the desta configuration file be deleted with the following command:   8 $ delete svctools_home:[desta.config]configuration.dat;*  ? The Director can then be started using the desta start command.o  6      3.3.3 Lengthy Processing Time on Large Error Logs  J Compaq Analyze may require additional time to process large error logs. ToE improve performance, create a new binary log file containing only they< relevant events and then process the new, smaller error log.  %      3.3.4 Trans Command Unresponsiveh  J You may see instances where translation does not appear to do anything. IfI this occurs, adjust the filtering in order to process a smaller subset ofeE events. Create a smaller, secondary event log file, which can then be I submitted for analysis, translation, or any other Compaq Analyze process.b  !      3.3.5 Analyze Command Aborts   J You may see instances where analysis aborts prematurely. When this occurs,I create a new binary log file containing only the relevant events and thene# process the new, smaller error log.b  G Another alternative is to copy the error log file to a platform runninghJ another operating system such as Windows NT or Tru64 UNIX, and analyze the% OpenVMS error log from there instead.h  !      3.3.6 Unsatisfied Link Errorp  J An error message similar to the following may be returned by a CLI commandE or appear in the Director log file SVCTOOLS_HOME:[LOGS]DESTA_DIR.LOG:i  H RECOVERED FROM ERROR on August 14, 2001 9:52:39 PM GMT+00:00 (26.462 sec elapsed) Can't load DeCOR library Current Thread[Thread-8,5,main]mG EXCEPTION java.lang.UnsatisfiedLinkError: no DeCOR in java.library.pathe  A The name of the library (DeCOR in the previous example) can vary.n  I This message is likely caused by interference from certain DECC logicals.UG This is a WEBES installation issue and the solution is described in thet WEBES Installation Guide.w  /      3.3.7 Stack Overflow and Bugcheck Messagesf  G The WEBES Director process on OpenVMS may crash with stack overflow andtJ bugcheck messages. The symptoms, causes, and corrective actions associated@ with these issues are presented in the WEBES Installation Guide.  K Be aware that corrective steps may include configuring WEBES to run on onlytK one CPU or to run using classic Java 2 technology, both of which can reduce  performance.  2      3.3.8 Memory Errors (OpenVMS 7.2 and earlier)  G When Compaq Analyze is used with large event logs, processing may abortiJ with an out-of-memory message, a communications error, or a streams error.H If you are using the web interface, these errors are logged in the DESTAJ Director log. If you are using the command line interface, the errors will appear on the screen.   
 Workaround  F Use the filtering tools to create a new, smaller event log, and try toD process the new log. Refer to the Compaq Analyze User Guide for more' information on creating new event logs.n  D If you have already tried creating a new log file and still receivedF processing errors, try changing the heap memory allocation for the CLIH command or for the Director process. The default settings for the CompaqF Analyze command's heap memory allocation are stored in the ca.com fileI located in the SVCTOOLS_HOME:[BIN] directory the default settings for thesI Director are stored in the desta.com file, located in the same directory.s  ,                                 *** Note ***  D      Each command executed by the ca.com file contains a DCL sectionD      that sets the value of the SVCTOOLS_HEAP logical. Normally, theF      SVCTOOLS_HEAP logical is set to the maximum heap allocated by theB      JRE for the command with the -mx switch. However, the JRE forF      OpenVMS allocates all of the memory specified with the -mx switchD      as the initial startup heap and does not free this memory until@      the process ends. As a result, increasing this maximum heapF      setting will consume extra resources from the time the command isA      invoked until the process is complete. Therefore, you shouldpC      return the modified settings to their original values once yout2      have finished processing the large event log.  -                               *** Caution ***.  >      It is important that you only set or change the SVCTOOL_*D      logicals in the DCL scripts, rather than from the command line.  D Before increasing JVM memory, determine which process has run out of memory.w  G    * If memory shortage errors appear in the DESTA log file (located atrJ      SVCTOOLS_HOME:[logs]desta_dir.log), then the Director's memory shouldK      be increased. Performing unusually large manual analysis jobs from the:I      web interface will most likely result in the failure of the Directors
      process.h  I    * If errors occur at the command prompt after a Compaq Analyze commandaD      is issued, the memory for that CLI command should be increased.  J If the failure is related to the Director, you can increase the Director's> memory settings by changing the following symbol values in the" SVCTOOLS_HOME:[BIN]desta.com file.      * defaultHeap      * defaultNativeStack       * defaultJavaStacko  K The Director's memory settings can are determined by the following lines innH the desta.com file (the values shown here are examples and may vary from the actual values):A  # $  !DESTA Director memory settings:t $  defaultHeap := "-mx65M"" $  defaultNativeStack := "-ss512k"! $  defaultJavaStack := "-oss400K"l  K If performing manual analysis with the CLI caused the out of memory errors,oE increase the memory settings for CLI analysis command. Search for theaG following lines in the SVCTOOLS_HOME:[BIN]ca.com file (the values showns7 here are examples and may vary from the actual values).e  H $  IF completion_code .EQS. "%X000000C9" ! ANALYZE command = 201 base 10 $  THENY" $   DEFINE SVCTOOLS_HEAP "-mx100M"' $   DEFINE SVCTOOLS_JAVA_STACK "-oss1M"C( $   DEFINE SVCTOOLS_NATIVE_STACK "-ss1M"  ,                                 *** Note ***  F      Depending on the system, continuing to increase the heap size may-      eventually cause disk swapping to occur.   9 Use the following guidelines when adjusting the settings:t  >    * If Java.OutOfMemory errors occur, increase the heap size.  A    * If stack overflow errors occur, increase the stack settings.n   Modifying Memory Settings   I If you need to change the memory settings, open the appropriate .com fileeJ and search for the desired settings. The value for the memory setting uses the following format:1   "-mxnu"r  K Where n refers to the maximum size of the memory allocation pool. The valueaG of n must be greater than or equal to 1000 bytes. u indicates the unitshH associated with the size. By default, the size is measured in bytes. UseI the letter K to indicate kilobytes or the letter M to indicate megabytes.t  G The following example shows the how to specify a size of 256 kilobytes:p  	 "-mx256K"e   Modifying Heap Settingso  H The changes to the heap setting that are required will vary depending onK the system. Use the following procedure to determine the correct heap size.e  ,                                 *** Note ***  C      The procedure here describes how to modify the ca.com file. If2A      you are modifying the desta.com file you should use the samea.      procedure, using smaller size increments.  H   1. Using a text editor, change the value of the SVCTOOLS_HEAP from the&      default of "-mx100M" to "-mx80M".  B   2. Save your changes and attempt to process the error log again.  H   3. If the log still fails to process correctly, determine which of the%      following circumstances applies:c  @         * If processing failed earlier (less of the log file wasI           processed), open the .com file again and increase the heap sizet           to "-mx120M".E  J         * If processing failed later (more of the log file was processed),H           open the .com file again and reduce the heap size to "-mx60M".  E   4. Continue modifying the heap size until the log file is processedi      correctly.d   Modifying Stack Sizese  K If you are increasing the stack sizes, be aware that the JVM stack settingstI (-ss and -oss) work collectively. For the best results, increase both theiI stack sizes. Table 3-1 provides some recommended sizes for increasing the  JVM stack size.t  2                          Table 3-1 JVM Stack SizesA           +-----------------------------------------------------+e  9                    -ss (in kilobytes) -oss (in kilobytes) 0                    ----------         ----------)                    512                400h)                    512                800 )                    800                800 )                    1500               800t*                    1500               1200*                    1500               1600*                    1700               2000  A           +-----------------------------------------------------+r  I As with other memory changes, modify the stack sizes using a text editor.d  2      3.3.9 Memory Errors (OpenVMS 7.2-1 and later)  G When Compaq Analyze is used with large event logs, processing may abortnJ with an out-of-memory message, a communications error, or a streams error.H If you are using the web interface, these errors are logged in the DESTAJ Director log. If you are using the command line interface, the errors will appear on the screen.e  
 Workaround  F Use the filtering tools to create a new, smaller event log, and try toK process the new log. See the Compaq Analyze User Guide for more informationS on filtering event logs.  "      3.3.10 Locked Error Log Files  I OpenVMS 7.2-1 has a file locking limitation that may prevent locked filesbJ from being released. This locking problem may affect error logs, includingE the system error log (sys$errorlog:errlog.sys). If a CLI command thatiK requires access to a locked file is invoked, an error will occur. The errore5 message in the DESTA log is similar to the following:t  E EvtReader cannot read log directory[sub]errorlog.zpd. The file may beG inaccessible.: IOException...f  J Where directory[sub] indicates the directory where the log file is located' and errlog.zpd indicates the file name.e  ; The file locking issue is fixed with the following patches:h      * VMS721_SYS-V0500e      * VMS721_UPDATE-V0100      * VMS721_PCSI-V0100  .      3.3.11 Event Logs May Be Read Incorrectly  K Event logs created on a Tru64 UNIX system and processed with Compaq Analyzen- on an OpenVMS system may be read incorrectly.o  G If you are using a binary event log (binlog) that was created on a DS20tK system, and not renamed or deleted prior to the V4.0E installation of Patch H Kit 1 or Patch Kit 2, the binlog file will contain entries with both theI traditional event header and the Common Event Header (CEH). Processing an K event file of this type with Compaq Analyze on a system running OpenVMS mayi cause a timeout error.  
 Workaround  I To process the binary event log, open it with a file editor. If the value H of the first 4 bytes is not 0xFFFFFFFE, then the log file does not begin with a Common Event Header.g  ,                                 *** Note ***  E      The editor may display the bytes in the order they appear in thecF      log file - least significant byte first - so the value may appear      as EFFF FFFF in the file.  I If the log file does not start with a Common Event Header, delete all thetD data proceeding the first CEH entry and then save the modified file.  8      3.3.12 Directory Names Unrecognized in CLI Commands  F Due to an issue with Java 2, CLI commands that accept a directory as aD parameter do not function correctly. Java 2 incorrectly prepends theK current directory to the directory parameter supplied with the CLI command.e  I For example, if the current directory is USER:[THOMAS] and you attempt toe run the following command:  # ca summ svctools_home:[ca.examples]   I The directory is interpreted as /user/thomas/svctools_home:[ca.examples].o  
 Workaround  % Use one of the following workarounds:   H    * Set the directory to the desired directory, and supply the argument1      "." as the directory parameter. For example:u  *      $ set def svctools_home:[ca.examples]      $ ca summ .  H      Java 2 interprets the "." as the current directory and successfully      executes the command.  C    * Supply the directory name with a UNIX-style path. For example:C  )      $ ca summ /svctools_home/ca/examplesh  J      To convert an absolute VMS path into a UNIX-style path, prepend a "/"J      and convert each contiguous set of colons, brackets, and periods intoC      a "/". Do not include a trailing "/". Since relative paths arerA      difficult to convert to UNIX-style, only use absolute paths.m  +      3.3.13 Invalid Directory Error Messageh  I When you use the analysis or translation commands and specify a directorysF as [...] or [-], the process generates an Invalid directory path error message and quits.  
 Workaround  0 Specify the directory or directories explicitly.  2      3.3.14 Maximum Character Length Error Message  F If you enter a lengthy CLI command, you may exceed the OpenVMS maximumI command character length. As a result, OpenVMS may return a command errorpA message that refuses the number of characters that you have used.t  
 Workaround  J Shorten the parameters in the CLI command. For example, you can substituteH a lengthy absolute file path with a shortened relative path for a file's
 directory.  "      3.3.15 Wildcards Not Expanded  E Filenames containing wildcards are not expanded and result in command=K parsing errors. VMS does not expand wildcards before passing arguments to amG program, and as a result VMS cannot find any files that match the givena	 argument.a  
 Workaround  G To input all files in a directory, just enter the directory path alone,pK without wildcard characters. To specify multiple input files, put them in a0/ comma-separated list after the input parameter.Y  0      3.3.16 Scrolling Output in Terminal Display  K When you enter a CLI command in a command window, the resulting output will , scroll continuously in the terminal display.  
 Workaround  J To set a screen pause after each output page, enter the following command:  9 $PIPE ca trans errlog_filename | TYPE/PAGE=SAVE SYS$INPUTu  G You need to enter the command for all CLI outputs you want to pause. To H simplify the process, you can save this stream to a variable by entering' the following line in the login script:f  ! $ more:==TYPE/PAGE=SAVE SYS$INPUTg  G Once this variable is established in the login script or at the commande> line, you can use the following command to set a screen pause:  % $PIPE ca trans errlog_filename | morei  /      3.3.17 Preserving File Attributes with FTPm  G If you are using FTP to transfer files for use with Compaq Analyze, youtJ must ensure that the correct file attributes are preserved. Compaq AnalyzeG files should be formatted as Streamed_LF with the CR control character.oC This file formatting restriction applies to binary event log files, J knowledge rule sets (*.krs), and all other Compaq Analyze files containing binary (non-text) data.   F When you are using FTP to transfer files to an OpenVMS system, use theB following command to ensure that the attributes are set correctly:  + set file/attr=(rfm:stmlf,rat:cr) filename.*   -      3.3.18 Web Interface No Longer Supportedd  I The most recent browser supported by OpenVMS remains Netscape 3.03, whichcI is not new enough to consistently and reliably operate the web interface. J Although the web GUI is still available, it is not officially supported as of WEBES 4.0 on OpenVMS.  
 Workaround  C Run the CLI on the OpenVMS system, or open the web interface from a 4 non-OpenVMS system (one with a more recent browser).   3.4 Notes for Windowsd  ? The following limitations apply to Windows NT and Windows 2000..  8      3.4.1 No Response on Systems with Norton Anti-Virus  D Compaq Analyze may stop responding on Alpha systems that have NortonI Anti-Virus installed and running. When this happens the system shows 100% 0 CPU usage, and the keyboard may stop responding.  
 Workaround  ) Turn off the Norton Anti-Virus auto mode.o        3.4.2 Netscape Limitation  K Netscape for Windows inserts extra blank lines in saved problem reports. IfsI you use the Save As option to save Compaq Analyze problem reports in HTML.H format, the new HTML file will contain an extra blank line between everyG line of text. As a result, the new file appears double-spaced while the- original appears single-spaced.-  J When Netscape's Save As operation encounters the <PRE> tag in the originalH HTML file, it inserts extra lines into the source of the new file. Thus,F regardless of the browser you use to open the new HTML file, the extra lines are present.  J Since this problem only affects text formatted with the <PRE> tag, it does" not affect most translated events.  
 Workaround  F Right-click the Frame containing the HTML report and select View FrameE Source from the pop-up menu. A text window containing the HTML sourcewI opens. In that window, press Ctrl-a to select all the text and then press G Ctrl-c to copy it to the Clipboard. Paste the contents of the clipboards% into an editor and save it to a file.   /      3.4.3 Director Problems - Uninstall Issuesi  K If you installed a version of WEBES prior to 4.0, and the uninstall was notrG completed correctly you may have problems with general WEBES operation.lE These may include difficulties starting and stopping the Director and I problems with the Director hanging or crashing. If you encounter problemscI with general WEBES operation that are not solved by another Release Note,nK and you installed an earlier version of WEBES, perform these steps to clear H any possible problems associated with the previous WEBES uninstallation:     1. Uninstall WEBES V4.0.     2. Reboot the machine.     3. Re-install WEBES V4.0.$  F The WEBES V4.0 uninstall is more comprehensive than the uninstall fromI previous versions and will remove everything from previous WEBES versionsiF in addition to version 4.0. The reboot enables the operating system toK release file, service, and registry references. WEBES is completely removedt once the system is rebooted.  7      3.4.4 Commands With Comma Must Use Quotation Markst  C CLI commands that contain an argument with a comma must enclose thetG argument in quotation marks. If the argument is not in quotation marks,2H Java will not interpret the comma and you may receive undesired results. This affects all the syntaxes.  K The exact placement of the quotation marks is not critical, and both of thet' following examples show valid commands:o   ca n ana index="s:1, e:1"n ca n ana "index=s:1, e:1"e  .      3.4.5 NullPointerException If No Scavmark  H If you delete the file installed dir\ca\data\scavmark.dat, the followingF error appears in the Director's log file the next time scavenge occurs shortly after Director startup:p   ___.? WARNING on March 21, 2002 11:54:56 AM MST (244.872 sec elapsed)r NTR.findMark scav  Current Thread[Thread-23:n> com.compaq.svctools.ca.services.eventreaders.NTReader ,5,main]( EXCEPTION java.lang.NullPointerExceptionA at com.compaq.svctools.ca.services.eventreaders.NTReader.findMark  (NTReader.java:223)eD at com.compaq.svctools.ca.services.eventreaders.NTReader.scavengeLog (NTReader.java:367)lF at com.compaq.svctools.ca.services.eventreaders.EvtReader.stateMachine (EvtReader.java:541)< at com.compaq.svctools.ca.services.eventreaders.NTReader.run (NTReader.java:104)o( at java.lang.Thread.run(Thread.java:484)  I This message is expected and can be ignored. A new scavmark.dat file wills0 be created and the message will not be repeated.      K ===========================================================================r   As   *** Return Codes ***  E The following return codes are used with Compaq Analyze CLI commands.,   All Commands      * 0 - No errorO  J ca log, ca report, ca sicl, ca listrk, ca regknw, ca msg, desta msg, desta qsap, desta servob  !    * 386 - Insufficient argumentsh      * 10 - Too many arguments.o  &    * 18 - Illegal number of arguments.  ?    * 42 - No default krs files in default directory to process.a      * 50 - Illegal arguments.      * 402 - Unknown option.      * 66 - DESTAException.f      * 74 - Directory not found.  +    * 82 - krs files not found in directory.a      * 354 - File I/O Erroru  &    * 106 - Service obligation expired.  I    * 114 - Bad user specified event log, or no default event logs in user$      specified  G    * 122 - Bad user specified krs file, or no default krs files in usery      specified  0    * 130 - No valid event log file(s) specified.  *    * 138 - No valid krs file(s) specified.  *    * 146 - Illegal output option argument.  3 ca trans, ca analyze, ca filterlog, ca fru, ca summ   &    * 306 - Different argument expected      * 314 - Invalid command      * 322 - Invalid operatora  #    * 330 - Numerical value expectedr      * 338 - Invalid keyword      * 346 - Invalid report type      * 354 - File I/O error.      * 362 - Can not determine OSt      * 370 - Invalid abbreviation       * 378 - Date value expected  !    * 386 - Insufficient argumentst  "    * 394 - Command execution error      * 402 - Unknown optione   desta status       * 1 - Director is not running      * 3 - Director is running       * 5 - Director is starting up  "    * 7 - Director is shutting down  K    * 9 - Director status file indicates that it is running, but the processeK      ID was not found. As a result, the Director is assumed to be no longer3
      running.o  )    * 99 - Director is in an unknown statea   Java VM Related Exit Codes      * 602 - VM errors      * 610 - Unknown argument       * 618 - Unknown class      * 626 - Unknown methodV      * 634 - Missing environment  !    * 386 - Insufficient argumentsd   Installation Related Exit Codesr  7    * 642 - The $SVCTOOLS_HOME directory does not exist.c  @    * 650 - Could not find the Service Tools installed jar files.  +    * 658 - Could not find Java environment.   >    * 666 - Could not execute DESTA <DESTA program> executable.  .                                   *** Note ***  I           On VMS systems each error code has a severity of 2. Thus, an ONtH           ERROR statement can be used in DCL scripts to trap for errors.H           For VMS, a bit-wise OR of the value 0x10000000 is performed onG           the published return code before the actual code is returned,pI           which changes the value in $STATUS. Therefore, to determine theiI           correct value, the leading 1 should be removed. For example, if I           an Insufficient arguments error is returned, an OR is performedaC           with 0x10000000 and 0x00000182 (386 base 10) resulting ineI           0x10000182 or 268435842 base 10. Remove the leading 1 to obtain $           the correct decimal value.    