      F **********************************************************************F **                                                                  **F ** TEXT FILE LIMITATIONS:                                           **F **                                                                  **F ** The text extract for this document does not capture tables very  **F ** well, mainly because of the 75-column, monospaced character      **F ** limitation. Be aware that large data tables probably will not    **F ** wrap properly in this text file.                                 **F **                                                                  **F ** In addition, the text extract cannot capture figure images.      **F ** You can see only placeholders (captions) for the figures.        **F **                                                                  **F ** You may see references to italic or bold fonts that are visible  **F ** in the original document but not in this text extract.           **F **                                                                  **F **********************************************************************      J =========================================================================      Compaq Analyze     User Guide  J -------------------------------------------------------------------------   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 K analyze events stored in the system's binary event log file and events from  other sources.    H The Compaq Analyze User Guide provides information about the features of9 Compaq Analyze and explains how to operate the software.     Rev. 5/23/01-A      Operating System:  >                      Microsoft Windows NT 4.0 and Windows 2000;                      Compaq Tru64 UNIX versions 4.0E to 5.1 N                      Compaq OpenVMS Alpha versions 7.1-2, 7.2, 7.2-1, 7.2-1H1,                      and 7.3    Software Version:  (                      Compaq Analyze 4.0         	 May 2001    + Copyright 2001 Compaq Computer Corporation    J Compaq and the Compaq logo Registered in U.S. Patent and Trademark Office.J Tru64 and OpenVMS are trademarks of Compaq Information Technologies Group,J L.P. in the United States and other countries. Microsoft, Windows, WindowsK NT, and MS-DOS are trademarks of Microsoft Corporation in the United States L and other countries. Intel is a trademark of Intel Corporation in the UnitedH States and other countries. UNIX is a trademark of The Open Group in theK United States and other countries. All other product names mentioned herein 1 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,L Commercial Computer Software, Computer Software Documentation, and TechnicalL 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 F contained herein. The information in this document is provided "as is"I without warranty of any kind and is subject to change without notice. The L warranties for Compaq products are set forth in the express limited warrantyL statements accompanying such products. Nothing herein should be construed as% constituting an additional warranty.    H This service tool software is the property of, and contains confidentialL technology of Compaq. Possession and use of this software is authorized onlyJ pursuant to the Proprietary Service Tool Software License contained in the6 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. Service customer is hereby licensed to use the software only H for activities directly relating to the delivery of, and only during theF term of, the applicable services delivered by Compaq or its authorizedH service provider. Customer may not modify or reverse engineer, remove orH transfer the software or make the software or any resultant diagnosis orI system management data available to other parties without Compaq's or its H authorized service provider's consent. Upon termination of the services,G customer will, at Compaq's or its service provider's option, destroy or D return the software and associated documentation in its possession.    Printed in U.S.A.   J =========================================================================    ***Contents***    	  Preface            Overview       Intended Audience        Documentation Conventions        Further Information          1 Introduction     '      1.1 Description of Compaq Analyze        1.2 Compaq Service Tools       1.3 Supported Products %      1.4 Supported Operating Systems  ,      1.5 WEBES and Compaq Analyze Processes            1.5.1 Director  -           1.5.2 Command Line Interface (CLI)             1.5.3 Web Interface /           1.5.4 Director/Interface Interaction        1.6 Starting the Director        1.7 Stopping the Director  $      1.8 Monitoring WEBES Processes       1.9 Log Files             1.9.1 Location             1.9.2 Logging Level       1.10 Service Obligations       1.11 Environment Setup #      1.12 Nomenclature Differences           2 Command Line Interface (CLI)           2.1 Overview            2.1.1 Standalone CLI             2.1.2 Conventions       2.2 Command Syntax +           2.2.1 Setting the Default Syntax  +           2.2.2 Showing the Default Syntax        2.3 Command Verbs  !           2.3.1 CA Command Verbs             2.3.2 DESTA Commands        2.4 Command Parameters       2.5 Analysis             2.5.1 Manual Analysis 2                2.5.1.1 Performing Manual Analysis .                2.5.1.2 Specifying Input Files /                2.5.1.3 Saving Output to a File  #           2.5.2 Automatic Analysis  :                2.5.2.1 Viewing Automatic Analysis Reports :                2.5.2.2 Logging Automatic Analysis Reports             2.5.3 Analysis Output       2.6 Translation  '           2.6.1 Performing Translation  '           2.6.2 Specifying Input Files  (           2.6.3 Saving Output to a File $           2.6.4 Filtering Log Files            2.6.5 Output Type #           2.6.6 Translation Output        2.7 Summary of Events  '           2.7.1 Specifying Input Files  $           2.7.2 Filtering Log Files            2.7.3 Indexed Output             2.7.4 Example Output  -      2.8 Creating New Binary Event Log Files  '           2.8.1 Specifying Input Files  (           2.8.2 Saving Output to a File $           2.8.3 Filtering Log Files       2.9 Modifying Commands            2.9.1 Input Files            2.9.2 Output Files             2.9.3 Filtering       2.10 Knowledge Rulesets        2.11 Configuration       2.12 Notification        2.13 Service Obligations            2.13.1 Show            2.13.2 Override       2.14 Getting Help          3 Web Interface            3.1 Description             3.1.1 Translation            3.1.2 Analysis  !                3.1.2.1 Automatic                  3.1.2.2 Manual            3.1.3 Notification  +           3.1.4 Create New Binary Log File  %      3.2 Accessing the Web Interface  '           3.2.1 Supported Web Browsers             3.2.2 Browser Setup /           3.2.3 Browsers and the Web Interface  +           3.2.4 Starting the Web Interface        3.3 Toolbar        3.4 Navigation )      3.5 Customizing the Navigation Tree             3.5.1 Groups  %                3.5.1.1 Adding Groups  '                3.5.1.2 Removing Groups             3.5.2 Nodes $                3.5.2.1 Adding Nodes &                3.5.2.2 Removing Nodes #                3.5.2.3 Node Status             3.5.3 Categories  )                3.5.3.1 Adding Categories  +                3.5.3.2 Removing Categories             3.5.4 Log Files "                3.5.4.1 System Log "                3.5.4.2 Other Logs       3.6 Analysis Information ,           3.6.1 Automatic Analysis Features )           3.6.2 Manual Analysis Features  ,           3.6.3 Manual Translation Features #           3.6.4 Displaying Details              3.6.5 Problem Reports            3.6.6 Summary            3.6.7 Events ,            3.6.8 Sorting Results       3.7 Processing Status              3.7.1 Navigation Tree             3.7.2 Progress Window        3.8 Creating New Log Files       3.9 Applying Filters       3.10 Settings             3.10.1 User Settings  (                3.10.1.1 General Options                  3.10.1.2 Filters 6                     3.10.1.2.1 Adjust Filter Template /                     3.10.1.2.2 Default Filters  2                     3.10.1.2.3 Deleting Templates &                3.10.1.3 Event Columns #           3.10.2 Director Settings e1                3.10.2.1 Compaq Analyze Log Files e      3.11 Getting Help  (           3.11.1 Context Sensitive Help $           3.11.2 On-Line User Guide       3.12 Log Off       3.13 Lost Connection       3.14 Service Obligation =$      3.15 Disabling the Web Service         4 Event Translation            4.1 Translation Defaults       4.2 Automatic Translation -      4.3 Manual Translation )      4.4 Viewing Translation Information e.      4.5 Interpreting Translation Information            4.5.1 Overall            4.5.2 Frame            4.5.3 Field 4      4.6 Typical Frame of a Translated Binary Event         5 Event Analysis           5.1 Analysis Rules       5.2 Instance Files       5.3 Managing Rule Sets )           5.3.1 Viewing Registered Rules f                5.3.1.1 CLI f%                5.3.1.2 Web Interface e8           5.3.2 Registering and Unregistering Rule Sets                 5.3.2.1 CLI M%                5.3.2.2 Web Interface 0      5.4 Automatic Analysis       5.5 Manual Analysis  (      5.6 Resource Usage During Analysis &      5.7 Viewing Analysis Information +      5.8 Interpreting Analysis Information             5.8.1 Managed Entity C#           5.8.2 Service Obligation  "           5.8.3 Brief Description            5.8.4 Callout ID e           5.8.5 Severity U           5.8.6 Reporting Node  !           5.8.7 Full Description             5.8.8 FRU List g           5.8.9 Evidence t        6 Configuration r    #      6.1 Getting the Configuration  $      6.2 Changing the Configuration            6.2.1 CLI            6.2.2 Web Interface )      6.3 Global Configuration Attributes  (           6.3.1 Changing the Attributes            6.3.2 Changing Ports u)           6.3.3 Changing the Report Type .,      6.4 Component Configuration Attributes "           6.4.1 Common Attributes $           6.4.2 Extended Attributes       6.5 Profiles 2      6.6 Creating and Resetting the Configuration         7 Notification            7.1 Automatic Notification ,      7.2 Configuring SMTP Mail Notification       7.3 Customer Profile File a&           7.3.1 Profile File Contents            7.3.2 Path Setup c2      7.4 Enabling and Disabling SICL Notification '      7.5 Configuring CRSS Notification i9           7.5.1 Enabling and Disabling QSAP Notification  #           7.5.2 Event Log Settings        7.6 Indictment API         A Sample Outputs     C      A.1 Sample Configuration Entry page A-5Sample Analysis Output a(      A.2 Sample Translated Event Output            A.2.1 Full u           A.2.2 Brief $      A.3 Sample Configuration Entry       $  B Known Messages in Compaq Analyze     $      B.1 Configuration File Created ;      B.2 Start-up Errors in DUReader, Binlog, and Scavenge n       B.3 JIT Compiler Not Found        B.4 Two Director Processes       B.5 File Not Found       B.6 Indictment CCAT Error t  	 Glossary p   Index       J =========================================================================    ***List of Figures***   A      1-1 Compaq Analyze Running on a UNIX and a Windows Machine. d      3-1 Logon Window       3-2 The Web Interface e      3-3 Toolbar e      3-4 Collapsed Tree       3-5 Navigation Tree e      3-6 Add Group o      3-7 Remove Group       3-8 Add Node       3-9 Remove Node r      3-10 Activate Node "      3-11 Activating Node Message *      3-12 Unable to Activate Node Message       3-13 Add Category l      3-14 Remove Category       3-15 Add Log File Tab d      3-16 Remove Log File Tab #      3-17 Analysis Started Message m"      3-18 Analysis Failed Message       3-19 Clear Button y      3-20 Reprocess Button        3-21 Analyze Button        3-22 Navigation Buttons U      3-23 Problem Report Tab =      3-24 Summary Tab       3-25 Events Tab =      3-26 Status Icons        3-27 Progress Window        3-28 New Binary Log Screen       3-29 Filter Templates Bar        3-30 Filter Description        3-31 User Settings       3-32 Filter Preferences y      3-33 Adjust Filter       3-34 Filtering Criteria P      3-35 Filtering Operators       3-36 Applied Filter W      3-37 Event Columns       3-38 Director Settings       3-39 WEBES Logs  "      3-40 Lost Connection Message       5-1 Rules Files c      6-1 Settings       6-2 Selecting an Service       6-3 Attribute Display t'      7-1 Event Log Settings Dialog Box        J =========================================================================    ***List of Tables*** n        User Guide Contents b      2-1 Syntax Conventions       2-2 Syntax Designators       2-3 Default Syntax .      2-4 Command Verbs - ca (multiple syntax) ,      2-5 Command Verbs - ca (single syntax)       2-6 Command Verbs - desta 2"      2-7 Manual Analysis Commands       2-8 Translation Commands       2-9 Summary Commands '      2-10 Create New Log File Commands  #      2-11 Specifying an Input File  $      2-12 Specifying an Output File "      2-13 General Filtering Rules       2-14 Filtering Statements a      2-15 Event Type Keywords "      3-1 Web Interface Components #      3-2 Toolbar - Default Buttons  !      5-1 Problem Severity Levels p      6-1 Ports        J =========================================================================    ***Preface***   I Compaq Analyze is a rules-based hardware fault management diagnostic toolsC that provides error event analysis and translation. The multi-eventaI correlation analysis feature of Compaq Analyze provides the capability totG analyze events from a variety of sources, including those stored in thep  system's binary event log file.   	 Overview    J The Compaq Analyze User Guide describes the features of Compaq Analyze and% explains how to use the application.    1 The organization of the guide is described here. p  /                            User Guide Contents  	  Chapter    ----- c              Contents               ----- O  Chapter 1 l2              Introduces Compaq Analyze and WEBES.   Chapter 2 aD              Provides information about the Command Line Interface.   Chapter 3  D              Provides detailed information about the web interface.   Chapter 4 i9              Describes the translation of system events. 1  Chapter 5  *              Explains the analysis rules.   Chapter 6 WB              Discusses the Compaq Analyze configuration settings.   Chapter 7  @              Describes how to configure automatic notification.   Appendix A (              Shows sample output files.   Appendix B 0              Describes Compaq Analyze messages.          Intended Audience   I The Compaq Analyze User Guide is intended for system managers and service./ personnel who use the Compaq Analyze software. .   Documentation Conventions   3 The following conventions are used in this manual: C    User entries L                  Information that should be entered exactly as it appears in0                  the document is shown in bold.   Variables oN                  Information that will vary depending on your computer or user.                  profile is shown in italics.   System Output iK                  Responses from the system are shown in a monospaced font. v
  Directories  J                  Directory paths do not include the installation directoryD                  path. Thus, if you installed WEBES in the following                  directory:e3                  C:\Program Files\compaq\svctools\  @                  A reference to the ca directory would indicate:7                  C:\Program Files\compaq\svctools\ca\. .         Further Information   L Compaq Analyze is a member of the Web-Based Enterprise Service (WEBES) suiteL of products. For more information on the other WEBES applications, visit the' support web site at the following URL: r  ' http://www.support.compaq.com/svctools U  K For information about the supported products and limitations of the current.4 release, refer to the Compaq Analyze Release Notes.   K Information about the supported operating systems is contained in the WEBES D Install Guide along with detailed installation instructions for each operating system.       J =========================================================================    1    ***Introduction***    C This chapter describes Compaq Analyze, the supported platforms, the K post-installation setup procedures, the WEBES and Compaq Analyze processes, J the procedures used to start and stop the Director, the locations of WEBES6 Director log files, and the nomenclature differences.   #    - Description of Compaq Analyze      - Compaq Service Tools     - Supported Products !    - Supported Operating Systems  (    - WEBES and Compaq Analyze Processes     - Starting the Director      - Stopping the Director r     - Monitoring WEBES Processes     - Log Files      - Service Obligations      - Environment Setup      - Nomenclature Differences   " 1.1 Description of Compaq Analyze   K Compaq Analyze is a fault analysis utility designed to provide analysis for J single error/fault events, as well as multiple event and complex analysis.H Compaq Analyze provides system analysis that uses other error/fault data9 sources in addition to the traditional binary error log. g  G Compaq Analyze provides background automatic analysis by monitoring thenJ active binary error log and processing events as they occur. The events inK the binary error log file are checked against the analysis rules. If one or D more of the events in the binary error log file meets the conditionsG specified in the rules, the analysis engine collects the error data and.H creates a problem report containing a description of the problem and anyF corrective actions required. Once the problem report is created, it isH distributed in accordance with the customer's notification preferences.    1.2 Compaq Service Tools A  K Compaq has implemented a common Application Programming Interface (API) forrJ many of its service tools called Web-Based Enterprise Service (WEBES). The1 tools included in the current WEBES release are:        - Compaq Analyze '    - Compaq Crash Analysis Tool (CCAT) r1    - Revision and Configuration Management (RCM) t  F Compaq Analyze utilizes the common components of WEBES and adds it ownH functionality. The other WEBES service tools can be installed along with7 Compaq Analyze and utilize the same common components. N   1.3 Supported Products i  ? The following list shows the products Compaq Analyze supports. Q  =    - Analysis and Bit-To-Text Translation for the following: 6  ;         - Compaq AlphaServer DS10 (Tru64 UNIX and OpenVMS)  <         - Compaq AlphaServer DS10L (Tru64 UNIX and OpenVMS) <         - Compaq AlphaServer DS20e (Tru64 UNIX and OpenVMS) ;         - Compaq AlphaServer DS20 (Tru64 UNIX and OpenVMS)  ;         - Compaq AlphaServer ES40 (Tru64 UNIX and OpenVMS) aG         - Compaq AlphaServer GS80/GS160/GS320 (Tru64 UNIX and OpenVMS) v<         - Memory Channel II (Compaq Tru64 UNIX and OpenVMS)       - I/O - Analysis   F         - Disk Storage based on SCSI specification (Compaq Tru64 UNIX,            OpenVMS, and Windows) 4         - EZ4X/EZ6X (Compaq Tru64 UNIX and OpenVMS) 4         - EZ5X/EZ7X (Compaq Tru64 UNIX and OpenVMS) <         - HSG60/HSG80/HSZXX (Compaq Tru64 UNIX and OpenVMS)           - HSG60/HSG80 (Windows)   #    - I/O - Bit-To-Text Translation             - RA3000 r4         - KZPSC/KZPAC/KZPBA/KZPCM/KZPSA/KZPCC/KSPEA 3         - KGPSA-CA (Compaq Tru64 UNIX and OpenVMS) c         - CCMAB-AA 1         - CIPCA-BA s    1.4 Supported Operating Systems   K Compaq Sustaining Engineering maintains a schedule of support for the Tru64dH UNIX and OpenVMS operating systems. Compaq does not commit to supportingI WEBES when installed on an operating system version that has exceeded its , end-of-support date. See the following URL:   < http://www.compaq.com/services/software/ss_pvs_se_amap.html   ' 1.5 WEBES and Compaq Analyze Processes 2  K Each WEBES-based service tool adds functionality to the Director, a process I (or set of processes) that executes continuously. Compaq Analyze providesDJ the Director with the capability to capture and interpret hardware events.E Event analysis can be performed automatically or at the request of ann outside process. 3  L Compaq Analyze includes a web browser interface that enables you to interactI with the Director. Although only one Director can run on a machine at anylD time, many web browser connections can be active simultaneously, all" connected to the single Director.   0                                      ***Note*** F WEBES (Web-Based Enterprise Service) and DESTA (Distributed EnterpriseA Service Tools Architecture) refer to the same common components.     1.5.1 Director i  L The Director manages its own host (either a machine, or a node in a cluster)E and communicates to Directors on other hosts through TCP/IP sockets. s  I The Director captures, translates, and analyzes events as well as routing K messages for the Compaq Analyze system. The Director is idle except for the2 following circumstances: e  (    - Events are received for processing D    - Messages arrive from other Compaq Analyze processes on the same
      machine y8    - Messages arrive from a Director on another machine ?    - Another WEBES tool within the Director, performs any task    K The Director is automatically started along with the machine and should not=G require any intervention. See Sections 1.6 and 1.7 for more informationa. regarding starting and stopping the Director.   # 1.5.2 Command Line Interface (CLI) a  J Many Compaq Analyze operations can be performed from the command prompt by; issuing commands beginning with desta and ca. For example: s  C    - ca report - shows all the current problem reports from ongoingv)      automatic analysis of this machine. eC    - ca analyze myBinary.errlog - analyzes the binary events in thepL      provided event log file and displays problem reports resulting from any
      errors.    I Each CLI command starts a process. Some CLI processes (such as ca report) L connect to the Director on the same machine to perform tasks. However, otherG CLI processes (such as ca analyze) perform all tasks themselves withoute connecting to a Director.   J CLI commands typically support many options, enabling you to specify input* and output files, and filtering criteria.   I Chapter 2 of this guide describes how to use the command line interface.     1.5.3 Web Interface   L Using a web browser, such as Netscape Communicator or Internet Explorer, you
 can connect: s  C    - directly to the URL of the Director on the same machine as theS
      browser p=    - directly to the URL of the Director on a remote machine  G    - indirectly to a remote Director through a direct connection to thes0      Director on the local or a remote machine.   F The web interface can monitor multiple nodes by communicating with theI Directors on other machines. You can establish a direct connection to the I Director on any machine reachable by its TCP/IP socket port, and, through F that connection, view the Compaq Analyze processes on other nodes (viaL Director-to-Director communication). You do not need to have WEBES installedK or running on the web browser's machine to connect directly to the DirectorR on a remote machine. m  @ Chapter 3 of this guide describes how to use the web interface.   % 1.5.4 Director/Interface Interaction l  B Figure 1-1 shows an example of two machines running Compaq Analyze processes. i  H      Figure 1-1 Compaq Analyze Running on a UNIX and a Windows Machine.   K In the example, a UNIX machine and a Windows machine, each running a single 6 Director, communicate with each other over a network.   G Web interface #1 is a web browser running on the UNIX machine, directly L connected to the local Director on the same machine (http://localhost:7902).L It can also communicate with the Director on the Windows machine through theE UNIX Director. This enables you to view the output produced by eitheruA machine (such as analysis results) using the same web interface.    J Web interface #2 is also a web browser running on the UNIX machine, but it= has directly connected to the Director on the Windows machinedH (http://thatPC.mydomain.com:7902). Using this web interface, you can, ifI desired, connect back to the UNIX Director as well, but the UNIX Director  need not be running at all.   H A telnet session initiated from the Windows machine has logged on to theG UNIX machine, and the user has issued the Compaq Analyze CLI command ca L report (to view the results of automatic analysis). The CLI process connectsL to the UNIX machine's Director, which returns the current report data to theK CLI process. The report text is then displayed to the user. Note that it istJ not necessary to have the Director running on the Windows machine for this type of remote connection. p  L The CLI command ca analyze thisBinary.errlog (which performs manual analysisH on the binary log file named thisBinary.errlog) is issued from a commandL prompt on the Windows machine. In the example, the file thisBinary.errlog isG assumed to be a log file from a UNIX machine that was transfered to the I Windows machine using FTP. The Director is not required to perform manualm< analysis and therefore, the local Director is not required.   J Finally, web interface #3 is a web browser running on the Windows machine.F This interface is directly connected to the local Director on the sameL machine (http://localhost:7902), the same way that Web interface #1 connects to its local UNIX Director.    1.6 Starting the Director   I The Director is automatically started during system startup. Under normal J operation, you should not need to manually start the Director. However, ifJ circumstances require it, you can manually start the Director by following, the instructions for your operating system.    Tru64 UNIX c  J Enter /usr/sbin/desta start at a shell prompt. The "root" superuser shouldK restart the Director, since only the superuser has privileges to access theA2 system binary error log (/var/adm/binary.errlog).    OpenVMS   6 Enter desta start at the OpenVMS command line prompt.   I The user that restarts the Director must have all privileges set. Without)J the necessary privileges, the Director will not be able to read the system, binary error log (SYS$ERRORLOG:ERRLOG.SYS).    Windows   G Select Programs | Compaq Service Tools | Web-Based Enterprise Service |q$ Start Director from the Start menu.    or t  E Enter net start DESTA_Service in a Command Prompt window to start the J DESTA_Service Windows service that starts the Director. You also can start> DESTA_Service from the Services utility in the Control Panel.    1.7 Stopping the Director   J Under normal operation, you should not need to stop the Director. However,J if circumstances require you to stop the director, follow the instructions for your operating system.     Tru64 UNIX v  C Enter /usr/sbin/desta stop at a shell prompt. Any user can stop theS
 Director.    OpenVMS   > Enter desta stop at a prompt. Any user can stop the Director.    Windows   G Select Programs | Compaq Service Tools | Web-Based Enterprise Service |(K Stop Director from the Start menu. A Stop Director icon appears in the TaskmA Bar, then disappears when the Director's shutdown has completed. X  D You can also stop the Director by stopping the DESTA_Service WindowsI service. To stop the service, enter net stop DESTA_Service at the commandn9 prompt or use the Services utility in the Control Panel. /   1.8 Monitoring WEBES Processes -  H You can monitor the WEBES Director process using the following command:   
 desta status r  J This command generates a brief message describing the current state of theH DESTA Director process. The states that may be reported are given here:   4    - The Director's status could not be determined. "    - The Director is NOT running. H    - The Director's status file indicates it is running, but the process?      ID was not found, so the Director process is NOT running. p    - The Director is running. "    - The Director is starting up. $    - The Director is shutting down.   J If the status is undetermined, or you want more detailed information aboutH sub-processes, you may want to use the monitoring procedures specific to your operating system. r  0                                      ***Note*** J With UNIX and Windows, the WEBES processes are listed using the name java.K Other applications running on your system may also be listed using the namecJ java. Therefore, when using the procedures described here, it is importantA to make sure that the processes in question are WEBES processes.     Tru64 UNIX *  F All WEBES processes are Java-based, using the Java Runtime EnvironmentJ bundled with WEBES. All WEBES processes run under the java executable. The? processes currently running can be displayed with the command:    3 ps ugxww | grep com.compaq.svctools | grep -v grep    E This searches for a command parameter included in every WEBES processeG command, instead of searching for java which could show other non-WEBESC! Java-based applications as well. i   Example output is shown here:   K root      17671  0.3  0.2 2.09M 392K ttyp1    S N  16:06:57     0:00.04 kshi' /usr/opt/compaq/svctools/bin/desta exec 1 com.compaq.svctools.ca.cli.CLIInterpreter analyze : /usr/opt/compaq/svctools/ca/examples/gs320_uce_ivp.errlog G root      17751  0.0  5.0 22.4M  13M ttyp1    I N  16:06:21     0:02.13rA /usr/opt/compaq/svctools/jre/bin/../bin/alpha/native_threads/javanD -DSvctools.Home=/usr/opt/compaq/svctools -DSwcc.Home=/var/adm -Xms8M< -Xmx128M com.compaq.svctools.desta.util.DESTAProcessWrapper G root      18097  0.0 12.0 57.1M  30M ttyp1    S N  16:06:17     0:12.11pA /usr/opt/compaq/svctools/jre/bin/../bin/alpha/native_threads/java:D -DSvctools.Home=/usr/opt/compaq/svctools -DSwcc.Home=/var/adm -Xms8M8 -Xmx128M com.compaq.svctools.desta.core.DESTAController G root      18155 73.4  6.5 33.4M  17M ttyp1    U N  16:06:57     0:03.89eA /usr/opt/compaq/svctools/jre/bin/../bin/alpha/native_threads/java D -DSvctools.Home=/usr/opt/compaq/svctools -DSwcc.Home=/var/adm -Xms8M: -Xmx128M com.compaq.svctools.ca.cli.CLIInterpreter analyze: /usr/opt/compaq/svctools/ca/examples/gs320_uce_ivp.errlog   I In this example, process 18097 is the main Director process, started withrD the DESTAController Java class. Process 17751 is a subprocess of theF Director (subprocesses start with the DESTAProcessWrapper Java class).J Process 18155 and its parent Korn shell script wrapper process 17671 are a, CLI command analyzing an example event log.    OpenVMS   E Use the following command to show the processes running on an OpenVMSL	 machine: e   show system    (or sho sys for short) s   Example output is shown here:   I OpenVMS V7.1-2 on node FIGARO 16-MAR-2001 15:32:50.14 Uptime 14 21:05:23 uL  Pid    Process Name    State  Pri      I/O       CPU       Page flts  Pages  F 00000101 SWAPPER         HIB     16        0   0 00:04:10.34         0      0 tF 00000106 IPCACP          HIB     10       10   0 00:00:00.00        30     23  F 00000107 ERRFMT          HIB      8    33813   0 00:00:10.05       189     61 vF 00000109 OPCOM           HIB      7     1709   0 00:00:00.30       416     41 i ... F 00000797 DESTA Director  HIB      6   110831   0 00:03:14.75    112196	   8192 M  F 0000079A JOHNSON_3       HIB      6    37957   0 00:01:22.05      7612
   1102 MS F 000006B5 THOMAS_1        HIB      4     8967   0 00:00:03.04     11610
   1771 MS   F In the above example, the DESTA Director parent process is shown. ThatE process has also spawned a subprocess named JOHNSON_3, since the userWG JOHNSON started the Director, but the relation is not apparent from the L output. Other WEBES processes, such as Compaq Analyze Command Line InterfaceL commands, appear named after the user that started them, such as THOMAS_1 inE this example, although it is not apparent that the process is a WEBES9	 process. n   Windows   L Use the Windows Task Manager to monitor processes in Windows. Start the TaskL Manager by pressing Ctrl+Alt+Del, and then pressing the Task Manager button.I Once the Task Manager window appears, click the Processes tab to view theb running processes.    F All WEBES processes are Java-based, using the Java Runtime EnvironmentJ bundled with WEBES. All WEBES processes appear in the Task Manager list asH java.exe. However, not all java.exe processes are guaranteed to be WEBESE processes. Other non-WEBES Java-based applications may also appear asfK java.exe. You may be able to distinguish the Director set of processes fromiK other WEBES and non-WEBES Java processes by looking at the Base Priority ofmJ the java.exe processes. The Director processes always run at Low priority,H while all other WEBES processes run at Normal or High priority. However,H other non-WEBES Java processes may also run at Low priority. Because theH Director runs as a Windows service, there is an additional process namedK DESTAService.ex, which wraps the Director's java.exe processes and runs fornJ the lifetime of the Director. The DESTAService.ex process also runs at Low
 priority.   H If the Base Priority column is not shown in the Task Manager list, choseH Select Columns from the View pull-down menu. In the window that appears, click Base Priority, then OK.    1.9 Log Files   E Compaq Analyze processes warnings and informational messages from thee Director in log files. i  0                                      ***Note*** G These warning and informational message files are different from binaryhJ event log files. See Section 1.12 for more information about the different log files. i  H If Compaq Analyze appears to execute incorrectly, or does not respond asE expected, check the Director log files for messages that may help youuJ restart or recover. The files can be copied to new file names so that theyG are not overwritten later, and can be sent to your service provider fort review.   I All WEBES processes log their messages either to files or to the terminaleJ window. For common messages you may encounter, refer to the Compaq Analyze Release Notes or Appendix B. c   1.9.1 Location n  K The format of the log file messages is the same for all platforms, however,e3 the file locations are operating system-dependent. r   Tru64 UNIX    J The Director and web interface log standard output and error messages to:   , /usr/opt/compaq/svctools/logs/desta_dir.log   ? The Director appends to this log file each time it is started.     OpenVMS   J The Director and web interface log standard output and error messages to:   " SVCTOOLS_HOME:[LOGS]DESTA_DIR.LOG   I The Director creates a new log file each time it is started. The previous  log file is saved as:    DESTA_DIR.LOG;n   < Where n is the previous version number of the VMS filename.    Windows   H The locations given here assume that Compaq Analyze was installed in theL default directory; if this is not the case, the location path will match the chosen installation directory. a  G The Director (and web interface) logs its standard output messages to: m  8 C:\Program Files\compaq\svctools\logs\desta_dir_out.txt   6 The Director's standard error messages are logged to:   8 C:\Program Files\compaq\svctools\logs\desta_dir_err.txt   L The Director creates new log files each time it is started. The previous logK files are renamed to desta_dir_err_backup.txt and desta_dir_out_backup.txt,a2 overwriting any previous versions of those files.    1.9.2 Logging Level   K The messages logged by WEBES processes are stored in the Director log filesoI described in Section 1.9.1. The minimum severity level, or logging level,oH indicates the lowest priority message that will be written to the files.K Only messages that meet or exceed the minimum severity level are written toi the Director log files.    1.10 Service Obligations i  G A service obligation specifies your service provider, service agreementeA information, and the duration of your agreement. During the WEBESNJ installation process, you will be prompted to enter the service obligationI information. This information is included with the results of translationp and analysis.   E Although Compaq Analyze continues to function without a valid servicesK obligation, local notification and reporting are disabled. In addition, theiF web interface will no longer operate after your service obligation has	 expired. i  I Refer to Chapters 2 and 3 for information on viewing service obligations.oL Information about temporarily overriding the service obligation is contained in Chapter 2.    1.11 Environment Setup s  E For more information on automatic notification and the Compaq Analyzer8 configuration settings refer to the following sections:   J    - To set up Simple Mail Transfer Protocol (SMTP) E-mail notification of*      problem reports, refer to Chapter 7. E    - To set up Automated Call Handling Service (ACHS) notification ofh*      problem reports, refer to Chapter 7. H    - To enable Qualified Service Access Point (QSAP) for use with Compaq8      Remote Support Service (CRSS), refer to Chapter 7. I    - If you wish to change how the Compaq Analyze components operate, youoJ      can change the system configuration using the web interface. Refer to@      Chapter 6 for more information about system configuration.   ; You can modify the Compaq Analyze environment at any time. a   1.12 Nomenclature Differences   L The term configuration is used in two different contexts in Compaq Analyze:   J    - Hardware Configuration - identifying the Field Replaceable Unit (FRU)>      or hardware components currently installed in a machine. H    - System Configuration - identifying the current software settings ofL      the Compaq Analyze system and each of the services it contains. Most ofF      the settings can be changed using the Compaq Analyze interfaces.   1 Log file is also used in two different contexts: /  I    - A log file containing text errors or information written by a Compaqa&      Analyze or WEBES process, such as?      /usr/opt/compaq/svctools/logs/desta_dir.log on Tru64 UNIX 1G    - An error or event log file containing binary events written by the.H      system event logger, such as /var/adm/binary.errlog, written by theG      binlogd daemon on Tru64 UNIX and translated and analyzed by Compaqr
      Analyze        J =========================================================================    2   # ***Command Line Interface (CLI)*** t  J This chapter describes the Command Line Interface (CLI) for Compaq Analyze' including its usage and functionality. E      - Overview     - Command Syntax     - Command Verbs K    - Analysis     - Translation 6    - Summary of Events l)    - Creating New Binary Event Log Files      - Input Files o    - Output Files     - Filtering n    - Knowledge Rulesets     - Configuration      - Notification     - Service Obligations      - Getting Help   
 2.1 Overview R  K The command line interface (CLI) provides a text-based interface for CompaqPG Analyze and a means to interact with the Director. The CLI enables bothHC automatic and manual analysis (automatic analysis is the default). C  K In automatic mode, Compaq Analyze monitors the binary system event logs forRL new events. When a event is appended to the binary event log, Compaq AnalyzeK translates the event into a readable format. The decomposed event is passed J to the Analyzer for fault analysis. Depending on the analysis of the eventL and the analysis of a history of events, a problem report may be generated.   H Manual mode enables you to specify binary event logs for translation and7 analysis, without interfering with automatic analysis.    0                                      ***Note*** L Most of the examples in this chapter use the Windows directory structure. IfG you are using a different operating system, you will need to modify theE commands accordingly.    2.1.1 Standalone CLI I  K The Director is not required to run all the CLI commands. The following CLIA1 functions can be performed without the Director: h      - Manual Analysis 9    - Translation d    - Summary Report      - Create New Binary Log File   K Since these operations do not use the Director, you must have permission tonH access any log file that you want to process. In addition, messages thatJ would otherwise be written to the Director's log files are included in theH output for the command. The messages shown remain subject to the logging@ level. Refer to Chapter 1 for more information on log messages.    2.1.2 Conventions   E Table 2-1 describes the conventions used to show CLI commands in thise manual.   8                           Table 2-1 Syntax Conventions    Convention   -----                  Meaning                  ----- a  Bold L                Command text. Bold is used for information that must be typedJ                as it appears here. For example, command verbs are shown in                bold. y  Italic F                Variables. Italics are used for information that variesE                depending on your requirements. For example, inputfilenL                indicates that you should enter the name of the file you want                to process. e  [ ] hL                Optional Entries. Information shown in square brackets is notM                required. You may or may not include these optional modifiers.iI                In most cases the optional entries pertain to input files,K4                output files and filtering commands.   | nE                Mutually Exclusive Entries. The bar separates mutually "                exclusive entries.          2.2 Command Syntax m  K You interact with the CLI by issuing commands from the command prompt. Some1L Compaq Analyze operations can be performed using several different commands,) or syntaxes. The supported syntaxes are: o      - Common Syntax  '    - DECevent Emulation (UNIX and VMS)      - New Common Syntax r  E You can enter commands using any of the supported command formats. If 8 desired, you can switch between the different syntaxes.   0                                      ***Note*** C The DECevent emulator is only supported on UNIX and VMS systems. InsL addition, the DECevent emulator only supports some of the commands. Refer toI Table 2-4 for a list of the commands supported by the DECevent emulator. m  L If you are using a command syntax other than the default, you must include aJ syntax designator in the command. Table 2-2 shows the syntax designators.   8                           Table 2-2 Syntax Designators  
  Syntax Name h  ----- r)                        Syntax Designator t                        ----- e>                                               Command Preface 4                                               -----   Common Syntax l                        x rO                                               ca (ca x if the default syntax ispL                                               not set to the common syntax)   DECevent Emulator  (UNIX)                         u e3                                               ca u n  DECevent Emulator  (VMS) i                        v  3                                               ca v t  New Common Syntax                          n t3                                               ca n r        ! 2.2.1 Setting the Default Syntax r  J When Compaq Analyze is installed, the common syntax is the default for theI CLI. As a result, when you enter commands in the common syntax you do notsL need to include a syntax designator. If you want, you can change the defaultH syntax. Any commands that use the default syntax do not require a syntaxD designator. To specify a default syntax, use the following command:    ca syntax syntax_designator   I Where syntax_designator refers to the letter corresponding to the desiredlE default syntax (see Table 2-2 for the designator associated with eachu	 syntax). l  H For example, to set the new common syntax as the default syntax, use the following command: i   ca syntax n   L Once the syntax is set, you can enter commands in your chosen syntax withoutH specifying the syntax designator. Table 2-3 shows how the default syntax setting affects commands.   7                              Table 2-3 Default Syntax  s  Command Syntax   ----- s"                     Default Syntax'                     Translation Commands                     Format i                     ----- F                                                     Not Default SyntaxN                                                     Translation Command Format  :                                                     -----   Common Syntax r                     ca trans n?                                                     ca x trans o	  DECevent   Emulator (UNIX) e                     ca -a <                                                     ca u -a 	  DECeventa  Emulator (VMS)                      ca /tra >                                                     ca v /tra   New Common   Syntax                      ca tra h=                                                     ca n tra a        0                                      ***Note*** H Changes to the default syntax affect all the users on a system. Thus, ifI another user changes the default syntax, your session may not function ashL expected. You can avoid this situation by using a syntax designator with all, the commands that support multiple formats.   ! 2.2.2 Showing the Default Syntax n  ? To show the current default syntax, use the following command: e  
 ca syntax    2.3 Command Verbs   K The CLI supports both Compaq Analyze commands and Director commands. Compaq G Analyze commands use the ca preface and Director commands use the destan	 preface. a  0                                      ***Note*** J If you enter the command ca without any command verb or parameters, CompaqF Analyze defaults to translation. In this case, the system event log is1 translated and the output is sent to the screen. l   2.3.1 CA Command Verbs n  K The Compaq Analyze commands that support multiple syntaxes are formed usingC the following convention:   " ca syntax_designator command_verb   J Where syntax_designator indicates which syntax you are using (if it is notE the default syntax) and command_verb indicates the action you want touL perform. The syntax designator is not necessary if you are using the default syntax.   E Table 2-4 provides an overview of the available ca command verbs that= support multiple syntaxes. =  @                 Table 2-4 Command Verbs - ca (multiple syntax)    Commons  Syntax   ----- t              DECeventc              Emulatory              (UNIX)               ----- E%                              DECevent %                              Emulator #                              (VMS) v#                              ----- t6                                             New Common4                                             Syntax1 2                                             ----- H                                                             Description B                                                             ----- 	  analyze c              ana ."                              /ana 0                                             ana 6                                             (analyze) N                                                             Switches to manualQ                                                             mode and analyzes onemP                                                             or more binary eventE                                                             logs. SeepR                                                             Section 2.5.1 for moreE                                                             details.    trans                -a "                              /tra 0                                             tra 8                                             (translate) N                                                             Switches to manualO                                                             mode and translatesAN                                                             one or more binaryL                                                             event logs. ThisQ                                                             command does not sendsJ                                                             the results toI                                                             analysis. SeefP                                                             Section 2.6 for moreE                                                             details.    summ               -o sum "                              /sum 0                                             sum 8                                             (summarize) P                                                             Returns a summary ofJ                                                             all the eventsQ                                                             contained in a binary J                                                             event log. SeeP                                                             Section 2.7 for moreE                                                             details.    filterlog s              -b "                              /bin 0                                             bin 5                                             (binary) mR                                                             Applies a filter to anQ                                                             existing binary eventaQ                                                             log and creates a newsL                                                             binary event logQ                                                             containing the subsetgN                                                             of events returnedP                                                             after filtering. SeeP                                                             Section 2.8 for moreE                                                             details.    help               hlp e#                              /help u1                                             help  Q                                                             Displays a text-basedtJ                                                             help file. TheO                                                             text-file describestR                                                             the syntaxes supportedM                                                             by your operatingSD                                                             system.       1  G  The new common syntax allows abbreviations. You only need to enter the H  first three letters of a command verb to initiate the command. The full'  command verb is shown in parenthesis. x    L The Compaq Analyze ca commands that only support one syntax are formed using the following convention:    ca command_verb   = Where command_verb indicates the action you want to perform.    J Table 2-5 provides an overview of the available ca command verbs that only support one syntax.   ?                  Table 2-5 Command Verbs - ca (single syntax)     Verb   -----            Description            -----    report E          Displays the active problem reports generated from automatics9          analysis. See Section 2.5.2.1 for more details.    log  M          Toggles the logging of automatically generated problem reports on ort4          off. See Section 2.5.2.2 for more details.   listrk I          List the paths of the knowledge files registered with DeCOR. SeerK          Section 2.10 for syntax information and Chapter 5 for more detailsx          on rule sets. t  regknw M          Registers or unregisters one or more knowledge (*.krs) files for uselI          during automatic and manual event analysis. See Section 2.10 fortI          syntax information and Chapter 5 for more details on rule sets. n  sicl K          Toggles on or off the Compaq Analyze System Initiated Call Logging K          (SICL) feature, which automatically log calls with Compaq ServicesaK          if DSNLink is installed on the system. See Section 2.12 for syntax2=          information and Chapter 7 for more details on SICL.           2.3.2 DESTA Commands    A The Director commands are formed using the following convention:     desta command_verb    = Where command_verb indicates the action you want to perform. x  7 Table 2-6 describes the command verbs used with desta. l  :                          Table 2-6 Command Verbs - desta    Verb   ----- -          Description            -----    msg sD          Changes the Compaq Analyze port configuration settings. See9          Section 2.11 for more details on port settings.    qsap L          Toggles on or off the Compaq Analyze Qualified Service Access PointL          (QSAP) feature, which automatically log calls with Compaq Services.G          See Section 2.12 for syntax information and Chapter 7 for moreh          details on QSAP.   servob K          Overrides your Compaq Analyze service obligation. See Section 2.13o          for more details. t  start fK          Starts the Director if it has been stopped. See Chapter 1 for moren+          details on starting the Director. t  status I          Shows the current status of the Director. See Chapter 1 for moret+          details on the Director's status. n  stop G          Manually stops the Director. See Chapter 1 for more details ono           stopping the Director.          2.4 Command Parameters t  I Parameters are used to specify binary log files for processing, designateeJ output files, and create filters. In most cases, Compaq Analyze allows youG to specify parameters in any order. For example, the following commandsh, using the new common syntax are equivalent:   A ca n tra inp myinput.zpd out myoutput.txt index=(start:10) brief  A ca n brief index=(start:10) out myoutput.txt inp myinput.txt tra a  L Notice that even the placement of the command verb (tra in this case) may be	 changed.    E Be aware of the following exceptions to the order independence rule:    J    - With the common syntax, the command verb must be the first parameter.J    - The parameters of the common syntax filterlog command must be enteredF      in the specified order. See Section 2.8 for more on the filterlog      command. G    - If you are using the new common syntax sum command and you want totI      generate indexed output, the index parameter must immediately followsH      the sum command verb. Otherwise, Compaq Analyze will assume you areI      using the index filter keyword. Refer to Section 2.7 for more on the       sum command.   
 2.5 Analysis    L If the Director is installed, automatic analysis is initiated when you startG your machine. This means that Compaq Analyze automatically analyzes then; default event log file and generates reports as necessary.    D With manual analysis you can select a binary event log for immediate processing.   L For more information on analysis and the default analysis settings, refer to Chapter 5.     2.5.1 Manual Analysis   G Use manual analysis to analyze a binary event log other than the system J event log. To switch to manual mode, analyze binary event logs, and output1 the generated reports, use the analysis command.    G For more information on manual analysis operations and output, refer to  Chapter 5.    # 2.5.1.1 Performing Manual Analysis    D You can manually analyze binary event logs using any command syntax.; Table 2-7 describes the commands used for manual analysis:    ;                        Table 2-7 Manual Analysis Commands     Command Syntax   -----  !                           Format                              -----   Common Syntax  E                           ca x analyze [inputfile] [outtext | outhtml &                           outputfile]   DECevent Emulator  (UNIX) A                           ca u ana [-f inputfile] [> outputfile]    DECevent Emulator  (VMS)  A                           ca v /ana[/out=outputfile] [inputfile] s  New Common Syntax  C                           ca n ana [input inputfile] [out | outhtml &                           outputfile]          2.5.1.2 Specifying Input Files    J By default, manual analysis processes the system event log. If you want toD process a different binary log file, you must specify the input file location and name.    D See Section 2.9.1 for more information on working with input files.     2.5.1.3 Saving Output to a File   F If you would like to save the generated reports to a file, rather thanI display them on the screen, you need to specify the file format, location 
 and name.   E See Section 2.9.2 for more information on working with output files.     2.5.2 Automatic Analysis s  K By default, when the Director is started Compaq Analyze initiates automatic H analysis on the binary system event log. Using the CLI, you can view the@ reports generated by automatic analysis or save them to a file.   L For more information on automatic analysis and the problem reports generated! by analysis, refer to Chapter 5.    + 2.5.2.1 Viewing Automatic Analysis Reports    K To view the active problem reports generated by automatic analysis, use the K report command. Reports can be viewed in the command prompt window or saved  to a file.    1 The syntax for the report command is shown here:    ) ca report [outtext | outhtml outputfile] m  K If you do not include any optional parameters, the reports are shown on thetH screen. See Section 2.9.2 for more information about working with output files. v  + 2.5.2.2 Logging Automatic Analysis Reports    E Compaq Analyze can automatically log generated problem reports in the - prob.log file located in the logs directory.    9 To turn automatic logging on, use the following command: t   ca log prob on    : To turn automatic logging off, use the following command:    ca log prob off   I If the prob.log file already exists, the new data from subsequent loggingeG operations is appended to the existing file. If you delete the prob.log J file, it is automatically recreated during the next logging operation. Log; output is flushed and the file is closed after each entry.     2.5.3 Analysis Output   F Refer to Appendix A for an example of a report generated by analysis.    2.6 Translation   H You can translate, or decompose, the events in a binary event log into aF readable format using the translation command. Translation operates inF manual mode, meaning you must enter the command every time you want to perform translation.    I For more information about translation and its default settings, refer to  Chapter 4.     2.6.1 Performing Translation    J Translation is supported by all the Compaq Analyze syntanxes and Table 2-8- describes the commands used for translation:    9                          Table 2-8 Translation Commands  c  Command Syntax   ----- v                       Format                         -----   Common Syntax pK                       ca x trans [inputfile] [outtext | outhtml outputfile]r@                       [filter "filterstatement"] [brief | full]   DECevent Emulator  (UNIX) M                       ca u -a [-f inputfile] [brief | full] [filter flags] [> "                       outputfile]   DECevent Emulator  (VMS) rN                       ca v /tra[/out=outputfile][/brief | /full][filter flags]"                       [inputfile]   New Common Syntax  A                       ca n tra [input inputfile] [out outputfile] 7                       [filterstatement] [brief | full] r         2.6.2 Specifying Input Files    J By default, manual translation processes the system event log. If you wantG to process a different binary log file, you must specify the input filet location and name. a  D See Section 2.9.1 for more information on working with input files.    2.6.3 Saving Output to a File   F If you would like to save the translated events to a file, rather thanI display them on the screen you need to specify the file format and name. e  E See Section 2.9.2 for more information on working with output files. t   2.6.4 Filtering Log Files   H You can specify the events from a binary event log file that you want toJ translate by defining a filter. For more information on filtering refer to Section 2.9.3. n   2.6.5 Output Type   I You can specify either brief or full output for translation. Full output, L which is the default, presents all the translation information for an event.= Brief output only presents the information used by analysis.     2.6.6 Translation Output -  G Refer to Appendix A for an example of a translated event and to see the * difference between full and brief output.    2.7 Summary of Events   I You can use the CLI to view a summary of the events contained in a binaryn; log file. Table 2-9 describes the command for each syntax. i  7                             Table 2-9 Summary Commands t  Syntax   ----- u"                            Format !                            ----- l  Common Syntax  9                            ca x summ [index] [inputfile] r  DECevent Emulator  (UNIX) E                            ca u -o sum [-f inputfile] [filter flags] A  DECevent Emulator (VMS)  ?                            ca v /sum[filter flags] [inputfile]    New Common Syntax iL                            ca n sum [index] [input inputfile] [out | outhtml9                            outputfile] [filterstatement]           2.7.1 Specifying Input Files t  H By default, the summary command returns information for the system eventJ log. If you want to specify a different log file or multiple log files you can do so.    D See Section 2.9.1 for more information on working with input files.    2.7.2 Filtering Log Files   H You can specify the events from a binary event log file that you want toG view a summary report for by defining a filter. For more information onm" filtering refer to Section 2.9.3.   K Summary report filtering is not supported by the common syntax. If you wantbJ to filter the events in a log file before generating a summary report, use another syntax.    2.7.3 Indexed Output m  J By default, a tallied list of all the events in the binary event log filesI is generated. However, you can generate an indexed list of all the eventst using the index modifier.   @ The indexed output is not available with the DECevent syntaxes.    2.7.4 Example Output    F The results of the summary command are displayed in the command prompt window.   : An example of the standard, tallied output is shown here:   7 Log: /svctools_home/ca/examples/ds20_660_binary.errlog a    Qty    Type  Description 4 ------ ------  ------------------------------------ /      1     302  Tru64 UNIX Panic ASCII Message  2      1     300  Tru64 UNIX Start-up ASCII Message +      1     660  UnCorrectable System Event r$      1     110  Configuration Event .      1     310  Tru64 UNIX Time Stamp Message  Total Entry Count: 5 y/ First Entry Date: Thu Jan 27 09:18:06 MDT 2001  . Last Entry Date: Thu Jan 27 13:00:32 MDT 2001   0 An example of the indexed output is shown here:   7 Log: /SVCTOOLS_HOME/ca/examples/ds20_660_binary.errlog l;  Index   Type Description                        Date/Time  G ------ ------ ---------------------------------- --------------------- nG      1    660 UnCorrectable System Event         05/27/99 09:18:06 MDT eG      2    302 Tru64 UNIX Panic ASCII Message     05/27/99 09:18:08 MDT oG      3    110 Configuration Event                05/27/99 09:19:57 MDT ,G      4    300 Tru64 UNIX Start-up ASCII Message  05/27/99 09:19:57 MDT aG      5    310 Tru64 UNIX Time Stamp Message      05/27/99 13:00:32 MDT    ( 2.8 Creating New Binary Event Log Files   J You can filter the contents of existing binary event logs and create a newK binary event log file containing a subset of the events from the originals. J When you create a new binary log file, Compaq Analyze checks the events inH the original binary event log file against the filter statement. All theL events that meet the criteria specified by the filter statement are added toH the new binary event log file. The new binary event log file can then beH used for analysis, translation, or any other Compaq Analyze process. The> syntax for creating new binary event log files is as follows:   =                     Table 2-10 Create New Log File Commands  F  Command Syntax   ----- l                       Format e                       -----   Common Syntax iN                       ca x filterlog inputfile outputfile ["filterstatement"]   DECevent Emulator  (UNIX) J                       ca u -b outputfile [-f inputfile(s)] [filter_flags]   DECevent Emulator  (VMS) aI                       ca v /bin=outputfile[/filter_flags] [inputfile(s)]    New Common Syntax aB                       ca n bin [input inputfile(s)] out outputfile(                       [filterstatement]          2.8.1 Specifying Input Files t  J By default, the system event log is used as the input file. If you want toH process a different binary log file or files, you must specify the input file location and name.   D See Section 2.9.1 for more information on working with input files.   0                                      ***Note*** L You cannot use multiple input files with the common syntax. If you are usingJ another syntax, you can specify multiple input files and merge them into aJ single binary log file (in this case, filtering occurs for each input fileH before events are written to the new file). Be aware that Compaq Analyze" does not remove duplicate events.    2.8.2 Saving Output to a File   J You must specify a file name and location where the new binary output fileK will be saved. The output file parameter is mandatory when you are creatingl a new binary event log file. e   2.8.3 Filtering Log Files   H You can specify the events from a binary event log file that you want toH include in the new log file by defining a filter. If you do not define aH filter, the new log file will contain all the events in the existing log@ file. For more information on filtering refer to Section 2.9.3.    2.9 Modifying Commands    F By default, the analysis, translation, summary and new binary log fileD commands all process the system event log. The output from analysis,K translation and summary commands is displayed on the screen. You can changenF these defaults in order to process other binary log files and save theG processing results to a file. With some of the commands you can furthertL restrict the events that are processed by filtering the binary log file usedF for input. The following sections describe how to use these features.    2.9.1 Input Files   G Many of the commands used in manual mode enable you to specify an inputnG binary event log file. Table 2-11 describes how to specify a input filea using each syntax. t  ;                       Table 2-11 Specifying an Input File  2  Syntax   ----- o                   Format :                   ----- :                                                   Example 8                                                   -----   Common Syntax o*                   Append the directory and)                   filename of the desiredr*                   input file to the end of                   the command.  >                                                   ca x analyzeG                                                   examples\ds20.errlog D	  DECeventl  Emulator (UNIX)                     -f filename *                   Where filename indicates*                   the name and location of"                   the input file. R                                                   ca u ana -f examples/ds20.errlog  	  DECeventl  Emulator (VMS) *                   Append the directory and)                   filename of the desired *                   input file to the end of                   the command. eR                                                   ca v /ana [.examples]ds20.errlog    New Commonf  Syntax !                   input filename f*                   Where filename indicates*                   the name and location of*                   the input file. If there+                   are multiple input files,f)                   separate the names with                    commas. @                                                   ca n ana inputG                                                   examples\ds20.errlog n        G When you are specifying an input file, the following guidelines apply: f  I    - Specifying an input file is optional. If you do not specify either asJ      directory or a file, Compaq Analyze processes the binary system eventJ      log. An example of a command without any input file criteria is shown      here: o        ca analyze   L      This rule does not apply when you are using the common syntax filterlog9      command. Refer to Section 2.8 for more information. r  I    - You can use the relative directory structure to specify input files.mK      Thus, if you were in the C:\program files\compaq\svctools\ca directorynJ      and you wanted to analyze the ds20.errlog binary event log located inJ      the C:\program files\compaq\svctools\ca\examples directory, you could"      enter the following command:   %      ca analyze examples\ds20.errlog  J    - If you specify a directory but no file name, Compaq Analyze processesK      all the files with a .errlog, .sys, .zpd, or .evt extension located in J      the provided directory. An example of a command that only indicates a      directory is shown here:         ca analyze examples\ H    - Multiple filenames can be specified by separating them with spaces,(      as shown in the following example:   0      ca analyze examples\ds20.errlog hscir1.zpd J    - You can use wildcards to specify multiple files. In the example shownL      here, all the files located in the \examples directory with a name that;      starts with ds and an .errlog extension are analyzed: u  $      ca analyze examples\ds*.errlog    2.9.2 Output Files o  K With many commands, you can save the results of processing to a file ratheriL than viewing the output on the screen. Table 2-12 describes how to specify a output file using each syntax. s  0                                      ***Note*** L These output file guidelines do not apply when you are creating a new binary2 event log. Refer to Section 2.8 for more details.   <                       Table 2-12 Specifying an Output File    Syntax   ----- t                   Format D                   ----- =                                                      Example s;                                                      ----- t  Common Syntax u(                        outtext filename (                        outhtml filename   .                   The outtext option creates a*                   text output file and the/                   outhtml option creates a html3-                   output file. In both cases, (                   filename refers to the.                   directory and filename where/                   you want to save the output. nI                                                      ca x analyze outtextTA                                                      results.txt  I                                                      ca x analyze outhtmlIB                                                      results.html 	  DECevent-	  Emulator-  (UNIX)                    > filename  .                   Where filename indicates the*                   name and location of the.                   output file. The output file/                   must be located at the end of /                   the command. Output files are6/                   always saved in text format. ML                                                      ca u ana > results.txt 	  DECeventa  Emulator (VMS)v                      /out=filename .                   Where filename indicates the*                   name and location of the/                   output file. Output files arey/                   always saved in text format. hO                                                      ca v /ana/out=results.txt n  New Commonv  Syntax $                        out filename (                        outhtml filename   /                   The out option creates a textt-                   output file and the outhtmlo.                   option creates a html output/                   file. In both cases, filename -                   refers to the directory and ,                   filename where you want to#                   save the output.  N                                                      ca n ana out results.txt R                                                      ca n ana outhtml results.html           2.9.3 Filtering   I Some of the CLI commands enable you to filter a binary event log file and G only process a subset of the events. Filtering statements are differentoI depending on the syntax you are using. Table 2-13 shows the general rulesi! each syntax uses with filtering. a  :                        Table 2-13 General Filtering Rules   Syntax   ----- l                      Rules                        ----- f  Common Syntax fL                           Filtering can be used with the trans and filterlog$                           commands. L                           Use the filter keyword before the filter statementA                           when filtering with the trans command. eI                           Filter statements must be enclosed in quotation !                           marks. tM                           You can join multiple filter statements by using ane6                           ampersand (&) between them. H                           Most filter parameters are not case sensitive.>                           Exceptions are given in Table 2-14.   DECevent UNIX tK                           Filtering can be used with the -a, -o sum, and -bg$                           commands. M                           You can include multiple filter statements by usingnL                           more than one filtering flag in a command. In thisA                           case, separate each flag with a space.    DECevent VMS M                           Filtering can be used with the /tra, /sum, and /bin $                           commands. M                           You can include multiple filter statements by usingeK                           more than one filtering flag in a command. You dosA                           not need to put a space between flags. n  New Common Syntax  J                           Filtering can be used with the tra, sum, and bin$                           commands. G                           You can include multiple filter statements byiB                           separating them with comma and a space. L                           You can abbreviate the filter parameters. You onlyN                           need to enter the minimum number of letters requiredN                           to uniquely identify a parameter. For example, index7                           could be abbreviated as ind.          ; Table 2-14 describes filtering statements for each syntax.    :                          Table 2-14 Filtering Statements    Common Syntax    -----  #                            DECevent                              UNIX !                            ----- h7                                           DECevent VMS  0                                           ----- P                                                               New Common Syntax D                                                               ----- 
  dtb=date   (date_time_begin)  
  dte=date   (date_time_end) t$                            -t s:date"                            e:date 4                                           /SIN=date 4                                           /BEF=date I                                                               begin=date  I                                                               since=date  G                                                               end=date gF  Filters based on the time the event occurred. No events that occurredK  before the given start time or after the given end time are processed. ThefB  date can be entered in any format supported by Java (for example,K  dd-mmm-yyyy,hh:mm:ss). You do not need to include the time (hh:mm:ss) with 1  the date. Be aware of the following guidelines:    H       The DECevent UNIX syntax combines the start and end times are in a       single filter statement.  G       The new common syntax begin and since statements are equivalent. :M       You can use the keywords YESTERDAY and TODAY with the DECevent syntaxess!       and the new common syntax. AJ       With the new common syntax begin and since keywords, you can enter aE       negative integer value to process based on a relative date. ForzF       example, entering -3 processes events from the last three days.   rtdb=days    (rel_time_days_begin) i  rtde=days r  (rel_time_days_end) -  rthb=hours   (rel_time_hours_begin)   rthe=hours   (rel_time_hours_end)       L  Filters based on the time the event occurred relative to the time the firstJ  or last event in the log file occurred. Filtering based on days and hoursJ  is supported. For example, using the filter rtdb=3 will processes all theH  events that occurred within three days of the first event in the file.   et=nn f  et!=nn   et<nn o  et>nn e  (entry_type)       C  Filters based on the numeric event type. Be aware of the followingn
  guidelines:    G       With the = and != operators you can enter multiple entry types by #       separating them with commas. cD       Instead of entering entry type numbers, you can use one of theJ       supported keywords. Refer to Table 2-15 for the supported keywords.       &                            -i keyword &                            -x keyword 8                                           /INC(keyword) 8                                           /EXC(keyword) N                                                               include=keyword N                                                               exclude=keyword I  Filters based on the numeric entry type. You must enter a keyword ratherrC  than the actual entry type. Refer to Table 2-15 for information onn  supported keywords.  	  cn=name  
  cn!=name   (computer_name) u#                            -H name n4                                           /NOD=name H                                                               node=name A  Filters based on the node responsible for generating the event.    L       With the common syntax = and != operators you can enter multiple entry,       types by separating them with commas. +       The name argument is case sensitive.    ost=n    ost!=n   (os_type) n      >  Filters based on the operating system type, using the numeric+  representation for each operating system.    L       With the common syntax = and != operators you can enter multiple entry,       types by separating them with commas.   idx=nn 	  idx!=nn a  idx<nn   idx>nn   (event_index) i(                            -e s:nn e:nn ;                                           /ENT=(S:nn,E:nn)  G                                                               index=nn  M                                                               index=(start:nn F                                                               end:nn) 9  Filters based on the event's position in the event log.    L       With the common syntax = and != operators you can enter multiple entry,       types by separating them with commas.   sort=keyword       G  Used with a keyword to organize the output. The following keywords aree  supported:   I       entry - sorts based on entry type from highest entry type number toi
       lowest MK       reventry - sorts based on entry type from lowest entry type number to        highest B       time - sorts based on entry time from most recent to oldest E       revtime - sorts based on entry time from oldest to most recent tI       idx - sorts based on the entry index number from highest to lowest aL       revidx - sorts based on the entry index number from lowest to highest                               -R /                                           /REV fF                                                               reverse L  Processes the events in reverse order according to the event index number.       I                                                               skipconfig  I  Ignores configuration entries when processing a log file. This filter is =  only available when you are creating a new binary log file. o        9                          Table 2-15 Event Type Keywords   	  Keyword u  -----  .                                   Description (                                   ----- L                                                                    SupportedL                                                                    Syntaxes I                                                                    ----- h
  mchk-all <                                   All machine check events. N                                                                         CommonO                                                                         Syntax    mchk <                                   All machine check events. N                                                                         CommonO                                                                         Syntax mR                                                                         New CommonO                                                                         Syntax l
  mchk-sys :                                   All system machine check*                                   events. N                                                                         CommonO                                                                         Syntax r
  mchk-cpu 7                                   All cpu machine check *                                   events. N                                                                         CommonO                                                                         Syntax e
  mchk-env ;                                   All environmental machine 0                                   check events. N                                                                         CommonO                                                                         Syntax n  cam r<                                   All SCSI entries logged by8                                   the CAM logger (199). Q                                                                         DECevent  R                                                                         New CommonO                                                                         Syntax s  configurations >                                   Configuration entries (110).  Q                                                                         DECevent  R                                                                         New CommonO                                                                         Syntax f  control_entries  ;                                   System startup entries ort8                                   new error log creation9                                   entries (32, 35, 300).  Q                                                                         DECevent eR                                                                         New CommonO                                                                         Syntax    cpus ;                                   Machine check entries form2                                   AXP (mchk-cpu). Q                                                                         DECevent    environmental_entries S<                                   Power entries (mchk-env). Q                                                                         DECevent  R                                                                         New CommonO                                                                         Syntax    swxcr e9                                   Entries logged by SWXCRt)                                   (198). oQ                                                                         DECevent dR                                                                         New CommonO                                                                         Syntax i  machine_checks or mchks  >                                   Events with machine checking6                                   information (mchk). Q                                                                         DECevent  R                                                                         New CommonO                                                                         Syntax    operating_system=value or
  os=value 8                                   Events with a specific<                                   operating system type. The;                                   value parameter indicates_:                                   the numeric code for the<                                   desired operating system. Q                                                                         DECevent  R                                                                         New CommonO                                                                         Syntax n  panic  8                                   Crash re-start, system>                                   panic, or user panic entries-                                   (37, 302).  Q                                                                         DECevent  R                                                                         New CommonO                                                                         Syntax    software_informationals or   swi  >                                   Events with lastfail, system4                                   startup, or system;                                   configuration information 8                                   (volume mounts, volume<                                   dismounts, new error logs,=                                   timestamp entries) (32, 35,R:                                   37, 38, 39, 64, 65, 250,2                                   300, 301, 310). Q                                                                         DECevent mR                                                                         New CommonO                                                                         Syntax m  osf_entry a:                                   Events logged on a Tru649                                   UNIX operating system. cQ                                                                         DECevent rR                                                                         New CommonO                                                                         Syntax  
  mchk_sys :                                   All system machine check*                                   events. R                                                                         New CommonO                                                                         Syntax  
  mchk_cpu 7                                   All cpu machine checks*                                   events. R                                                                         New CommonO                                                                         Syntax t
  mchk_env ;                                   All environmental machine 0                                   check events. R                                                                         New CommonO                                                                         Syntax d         Examples - Common Syntax p  A The following examples show sample commands that use filtering. Af: description of what the filter does follows each example.   / ca x trans filter "computer_name=ComputerName"  I ca x filterlog inputfile.zpd outputfile.bin "computer_name=ComputerName" x  < Processes events from the system described by ComputerName.   0 ca x trans filter "computer_name!=ComputerName & date_time_begin=11-Jan-2000" fJ ca x filterlog inputfile.zpd outputfile.bin "computer_name!=ComputerName & date_time_begin=11-Jan-2000" o  K Processes events that did not occur on the system described by ComputerName & that occurred after January 11, 2000.   7 ca x trans filter "date_time_end=31-Jan-2000,20:33:57" f+ ca x filterlog inputfile.zpd outputfile.binu% "date_time_end=31-Jan-2000,20:33:57"    F Processes events that occurred before 8:33:57 PM on January 31, 2000.   * ca x trans filter "rel_time_days_begin=4" D ca x filterlog inputfile.zpd outputfile.bin "rel_time_days_begin=4"   K Processes events that occurred no more than four days after the first event  in the log file.    * ca x trans filter "rel_time_hours_end=35" D ca x filterlog inputfile.zpd outputfile.bin "rel_time_hours_end=35"   J Processes events that occurred no more than 35 hours before the last event in the log file.    ( ca x trans filter "entry_type=mchk-cpu" B ca x filterlog inputfile.zpd outputfile.bin "entry_type=mchk-cpu"   ( Processes all CPU machine check events.   , ca x trans filter "entry_type!=610,620,630" F ca x filterlog inputfile.zpd outputfile.bin "entry_type!=610,620,630"   F Processes all events, except those of type 610, 620, and 630. Only theH common syntax supports filtering based on specific entry types the other syntaxes must use keywords.   # ca x trans filter "entry_type>600"  = ca x filterlog inputfile.zpd outputfile.bin "entry_type>600"    3 Processes all events with a type greater than 600.    / ca x trans filter "entry_type<300 & os_type=3"  I ca x filterlog inputfile.zpd outputfile.bin "entry_type<300 & os_type=3"    I Processes all events with a type less than 300 and an operating system of  type 3.   0 ca x trans filter "os_type!=1,2 & sort=revtime" ; ca x filterlog inputfile.zpd outputfile.bin "os_type!=1,2"    D Processes all events without an operating system type of 1 or 2. TheH translation command presents the output in reverse chronological order.   # ca x trans filter "entry_index>15"  = ca x filterlog inputfile.zpd outputfile.bin "entry_index>15"    D Processes all the events after the fifteenth event in the log file.    Examples - DECevent UNIX m  A The following examples show sample commands that use filtering. A : description of what the filter does follows each example.    ca u -a -H ComputerName  ca u -o sum -H ComputerName 8 ca u -b outputfile.bin -f inputfile.zpd -H ComputerName   < Processes events from the system described by ComputerName.   " ca u -a -t e:31-Jan-2000,20:33:57 & ca u -o sum -t e:31-Jan-2000,20:33:57 B ca u -b outputfile.bin -f inputfile.zpd -t e:31-Jan-2000,20:33:57   F Processes events that occurred before 8:33:57 PM on January 31, 2000.    ca u -a -i cpu   ca u -o sum -i cpu  / ca u -b outputfile.bin -f inputfile.zpd -i cpu E  ( Processes all CPU machine check events.   ! ca u -a -x operating_system=1 -R  " ca u -o sum -x operating_system=1 > ca u -b outputfile.bin -f inputfile.zpd -x operating_system=1   K Processes all events without an operating system type of 1. The translation < command presents the output in reverse chronological order.    ca u -a -e s:15  ca u -o sum -e s:15 0 ca u -b outputfile.bin -f inputfile.zpd -e s:15   D Processes all the events after the fifteenth event in the log file.    Examples - DECevent VMS   K The following examples show sample translation commands that use filtering. < A description of what the filter does follows each example.    ca v /tra/nod=ComputerName   ca v /sum/nod=ComputerName  8 ca v /bin=outputfile.bin/nod=ComputerName inputfile.zpd   < Processes events from the system described by ComputerName.   # ca v /tra/bef=31-Jan-2000,20:33:57  # ca v /sum/bef=31-Jan-2000,20:33:57  # ca v /bin/bef=31-Jan-2000,20:33:57    F Processes events that occurred before 8:33:57 PM on January 31, 2000.    ca v /tra/inc(cpu)   ca v /sum/inc(cpu) e0 ca v /bin=outputfile.bin/inc(cpu) inputfile.zpd   ( Processes all CPU machine check events.   & ca v /tra/EXC(operating_system=1)/rev " ca v /sum/EXC(operating_system=1) ? ca v /bin=outputfile.bin/EXC(operating_system=1) inputfile.zpd    K Processes all events without an operating system type of 1. The translation < command presents the output in reverse chronological order.    ca v /tra/ent=(s:15)   ca v /sum/ent=(s:15)  2 ca v /bin=outputfile.bin/ent=(s:15) inputfile.zpd   D Processes all the events after the fifteenth event in the log file.    Examples - New Common Syntax m  K The following examples show sample translation commands that use filtering. < A description of what the filter does follows each example.    ca n tra node=ComputerName e ca n sum node=ComputerName  B ca n bin input inputfile.zpd out outputfile.bin node=ComputerName   < Processes events from the system described by ComputerName.   " ca n tra end=31-Jan-2000,20:33:57 " ca n sum end=31-Jan-2000,20:33:57 I ca n bin input inputfile.zpd out outputfile.bin end=31-Jan-2000,20:33:57 _  F Processes events that occurred before 8:33:57 PM on January 31, 2000.   , ca n tra include=mchk_cpu, mchk_sys reverse $ ca n sum include=mchk_cpu, mchk_sys K ca n bin input inputfile.zpd out outputfile.bin include=mchk_cpu, mchk_sys    D Processes all CPU machine check and system machine check events. TheH translation command presents the output in reverse chronological order.    ca n tra index=(start:15)  ca n sum index=(start:15) A ca n bin input inputfile.zpd out outputfile.bin index=(start:15)    D Processes all the events after the fifteenth event in the log file.    2.10 Knowledge Rulesets   J Rulesets are used in conjunction with analysis. The events in a binary logL file are compared with rulesets. Depending on the results of this comparisonK problem reports are generated. The following commands are used to work with 
 rulesets.   I ca listrk - lists the registered rulesets used by analysis (see Chapter 5  for more information).    G ca regknw - registers or unregisters the rulesets used by analysis (see ! Chapter 5 for more information).     2.11 Configuration    H The Compaq Analyze configuration settings control port numbers and otherJ features. The following commands can be used to change the configuration.   I desta msg -chgport nnn - changes the socket ports (see Chapter 6 for more  information).   0                                      ***Note*** G There are more configuration settings that can be changed using the web E interface. Refer to Chapter 6 for more information on configuration.     2.12 Notification   F SICL and QSAP are both used for automatic notification. With automaticL notification, the results of analysis are sent to your service provider. TheH following CLI commands can be used to turn automatic notification on and off.    D ca sicl - turns SICL notification on and off (see Chapter 7 for more information).   I desta qsap - turns QSAP on and off (see Chapter 7 for more information).     2.13 Service Obligations    L Your service obligation describes the details of your service agreement. YouI can view an existing service obligation or override an expired obligationmG from the command line. See Chapter 1 for more information about service 
 obligations. h   2.13.1 Show   K To view the service obligation for a machine, enter the following command:     desta servob show   J This displays all the information associated with your service obligation.B The following example depicts the service obligation information:     WEBES Service Obligation Status   -------------------------------   (    Service Obligation:            Valid +    Service Obligation Number:     50036123  +    System Serial Number:          50036123  )    Service Provider Company Name: Compaq     2.13.2 Override   E If you need to view the analysis or translation results on a computer K without a valid service obligation, you can override the service obligationf using the following command: a   desta servob override   J Overriding does not change the service obligation; rather, it enables yourJ service provider to use Compaq Analyze without a valid service obligation.J Overriding the obligation enables you to view Compaq Analyze report output3 for one hour regardless of your obligation status. t  I The following example shows the prompts that appear when you override then. service obligation along with sample answers:   " WEBES Service Obligation Override " ---------------------------------   & Service Provider Company Name? Compaq + Service Provider Employee Name? Jack Smith t, Service Provider Employee ID#? 000000000000  ___. 2= WARNING on March 28, 2000 7:36:01 AM MST (0.037 sec elapsed) o+ Obligation Information Changed as follows: lH Obligation overridden for service provider until Tue Mar 28 08:36:01 MST 2000 bG by Jack Smith (000000000000) of Compaq on Tue Mar 28 07:36:01 MST 2000 h Current Thread[main,5,main]   E The override information is included in the output resulting from anyi. subsequent analysis or translation operation.    2.14 Getting Help   E You can access help from the CLI using the command for your operating  system:   3    - Tru64 UNIX - man ca, man desta, and ca n help t2    - OpenVMS - help ca, help desta, and ca n help     - Windows - ca n help c  L Help is also available through the User Guide. There are four different User$ Guide formats installed by the kit:   J    - Adobe Acrobat Format (located in the \svctools\ca\docs\pdf directory)H    - ASCII Text Format (located in the \svctools\ca\docs\txt directory) H    - HTML Help Format (located in the \svctools\ca\html\help directory) F    - HTML Format (located in the \svctools\ca\html\ns3help directory)   2                                        ***Note*** J      To navigate the HTML formats, use your browser to open the start.htmlL      file. If you are a VMS user and your browser is Netscape 3.03, you willF      need to use the HTML format rather than the HTML Help format. TheI      JavaScript used in the HTML Help format is not supported in Netscapeu      3.03. _      J =========================================================================    3    ***Web Interface***   C This chapter describes how to access and use the Compaq Analyze webt interface.        - Description t!    - Accessing the Web Interface x
    - Toolbar s    - Navigation %    - Customizing the Navigation Tree i    - Analysis Information     - Processing Status x    - Settings     - Getting Help 
    - Log Off      - Service Obligation     - Disabling the Web Service     3.1 Description   J The web interface provides browser-based access to Compaq Analyze. You canL use the web interface to connect to the Director on your local machine or onH remote machines and analyze and translate their binary event log files.    3.1.1 Translation   E Event information in the system event log is stored in binary format.tG Translation is the process of converting this binary data into readable C text. By default, the web interface performs translation as part ofEK analysis, and translation information is shown along with analysis results. H However, it is possible to only perform translation. See Section 3.6 forK more information on how the web interface presents translation information.yD Refer to Chapter 4 for more information on translation, interpreting5 translated events, and default translation settings. u   3.1.2 Analysis    J The information from binary event log files can be used to detect hardwareI failures on the system. When the system writes an event to a binary eventwH log file, Compaq Analyze processes the event according to the registeredG rule sets. The rule sets contain the information necessary to interpretoH events. When an event matches the conditions described in the rule sets,H Compaq Analyze creates a problem report containing information about theD event and proposed resolutions. This process is called analysis. SeeK Section 3.6 for more information on how the web interface presents analysisvH information. Refer to Chapter 5 for more information on analysis and its	 results. a  = The web interface can perform automatic and manual analysis. p   3.1.2.1 Automatic   J When the Director is started, Compaq Analyze initiates automatic analysis.I In automatic mode, Compaq Analyze continuously monitors the binary systemiL event log and processes events as they arrive. Problem reports are generated as necessary.   J For more information about automatic analysis operations and output, refer to Chapter 5.    3.1.2.2 Manual    I Manual analysis also compares the events from log files to the registeredsL rule sets and generates problem reports. However, unlike automatic analysis,I you must manually select each binary event log file you want to process. i  J For more information about manual analysis operations and output, refer to Chapter 5. r   3.1.3 Notification o  J The results of automatic analysis can be sent to remote systems using SMTPB or SICL. Refer to Chapter 7 for more information on notification.   ! 3.1.4 Create New Binary Log File    J You can filter the contents of existing binary event logs and create a newK binary event log file containing a subset of the events from the originals.3J When you create a new binary log file, Compaq Analyze checks the events inB the original binary event log file (input file) against the filterH statement. All the events that meet the criteria specified by the filterK statement are added to the new binary event log file (output file). The newtH binary event log file can then be used for analysis, translation, or anyC other Compaq Analyze process. For more information on using the weblG interface to create a new binary event log file, refer to Section 3.8. e    3.2 Accessing the Web Interface   B The following sections contain information about accessing the web interface. i   3.2.1 Supported Web Browsers r  L The supported browser versions for each operating system are provided here:   J    - Tru64 UNIX - Netscape version 4.x (version 4.5 and later recommended)%    - OpenVMS - No supported browsers nG    - Windows - Netscape version 4.x (version 4.5 and later recommended) '      and Internet Explorer version 5.x s  L Be aware, the web interface may display differently in Netscape and Internet
 Explorer.    3.2.2 Browser Setup   K The setup options that must be configured in order to use the web interfaceh are described here:   F    - Netscape and Internet Explorer - Configure your browser to bypassE      your proxy server when you connect to the Director on your local*      machine. F    - Netscape - Java must be enabled for the web interface to function      properly.    K      To verify that Java is enabled, select Preferences from the Edit menu.AI      Click on the Advanced entry and make sure that the check box next toh      Java is selected.    C    - Internet Explorer - The Microsoft Virtual Machine (VM) must bet;      installed for the web interface to function properly. nJ    - Internet Explorer - The "Use HTTP 1.1" option must be enabled for the)      web interface to function properly. e  L      To enable the option, select Internet Options from the Tools menu. FromL      the Options window, select the Advanced tab and make sure the check box)      next to "Use HTTP 1.1" is selected. d  % 3.2.3 Browsers and the Web Interface C  J Depending on the browser you use, there are several issues that impact how  the web interface is displayed.   F    - Netscape and Internet Explorer - If the web interface is behavingK      erratically, click your browser's Refresh button. This will reload theoF      web interface and display the about screen in the display frame. J    - Netscape and Internet Explorer - During heavy processing, you may seeL      JavaScript errors. You can safely ignore these errors. Depending on the:      error message, respond in one of the following ways:   E         - Click the OK button on the error dialog box to resume usingn           Compaq Analyze. I         - If the dialog box asks if you want to continue running scripts,sA           click the Yes button to continue using Compaq Analyze. o  I    - Internet Explorer - Include the full URL in the address line of yourbG      browser, including http:// (for example, http://14.77.189.23:7902/o&      rather than 14.77.189.23:7902/). F    - Internet Explorer - With version 4.x, the user setting to displayH      error log details in a separate window does not function properly.   ! 3.2.4 Starting the Web Interface v  L It is not necessary to have the Director running on your machine in order toI use Compaq Analyze. In fact, WEBES need not be installed on the browser'saI machine at all. However, WEBES must be installed and the Director must be G running on the target machine in order to connect to its Compaq Analyze3F system. Therefore, before using the web interface, you must ensure theF Director is started on the target machine. There is no need to run the8 Director on your local machine unless it is the target.   7 Chapter 1 describes web interface connections further. i  9 Use the following procedure to access the web interface:    I   1. Start the Director on the machine(s) you want to connect to, if theyaD      have not been started already. Refer to Chapter 1 for details.    2. Start your web browser. a9   3. Enter the URL of a target machine to connect to it. d  .         - To connect to a remote host, enter:   *           http://hostname.domain.com:7902   ?           Substitute the target machine's hostname and domain. t  H         - To connect to the same machine that the web browser is running           on, enter: o              http://localhost:7902   G           In some network configurations, the name localhost may not be\M           recognized. Enter the machine's hostname or its IP address (such asrM           http://14.77.189.23:7902) instead. If you use Internet Explorer, beeH           aware that you must include the http:// for the page to load.   ?   4. Enter the profile name you want to use in the Logon window G      (Figure 3-1) and either click the Logon button or press Enter. SeeJ1      Chapter 6 for more information on profiles. r  8                                 Figure 3-1 Logon Window   6 The web interface main screen is shown in Figure 3-2.   8                            Figure 3-2 The Web Interface   / The value of the URL field appears as follows:    ' http://hostname:7902/&profile=username b  H Where hostname indicates the machine you logged into, username indicates your profile.   L If you need to change profiles while using Compaq Analyze, you can edit yourJ browser's URL field by replacing the old profile name with the new profile name.   H The components of the web interface display are described in Table 3-1.   ;                        Table 3-1 Web Interface Components  e  Component l  ----- i                    Description l                    ----- a  Title Bar fL                    Shows the software version, active profile, and operating                    system. n	  Toolbar tJ                    By default, provides access to the on-line help, systemM                    configuration, processing statistics, and new binary errornH                    log creation. The toolbar is dynamically updated, andM                    additional features are available with some Compaq AnalyzeeB                    screens. See Section 3.3 for more information.   Navigation Tree  E                    Lists the available groups, nodes, and log files. n  Display Frame .H                    Displays interactive screens and system information.   Information Bar  K                    Displays messages from the browser and context sensitiveoL                    help information. See Section 3.11.1 for more informationB                    on the web interface's context sensitive help.         8 Initially, the display frame shows product information.   0                                      ***Note*** J You can use multiple browser windows with Compaq Analyze. If you are usingK the same profile with multiple browser windows, the navigation trees in allf/ the windows will be automatically syncronized. p   3.3 Toolbar   4 Figure 3-3 shows the default web interface toolbar.   3                                 Figure 3-3 Toolbar    D The toolbar buttons are dynamically updated depending on the actionsC performed. Table 3-2 describes the toolbar commands that are alwayss available: h  ;                        Table 3-2 Toolbar - Default Buttons .  Component r  ----- n'                            Description a!                            ----- t
  Help Button ,L                            Opens a new browser window containing the on-lineL                            user guide. See Section 3.11 for more information,                            on getting help.   Settings Button eJ                            Opens the settings screen. See Section 3.10 forF                            more information on changing the settings.   CA Progress Window   Button F                            Opens a new browser window that reports theN                            processing status of log files. See Section 3.7 forB                            more information on processing status.   New Binary Log Button aI                            Opens the New Binary Log screen in the displayiI                            frame. See Section 3.8 for more information one;                            creating a new binary log file. s        F The following buttons may also appear in the toolbar, depending on the feature being used:   C    - Clear - Available when viewing automatic analysis details. Seee)      Section 3.6.1 for more information. ,B    - Refresh - Available when viewing manual analysis details. See)      Section 3.6.2 for more information.  E    - Analyze - Available when viewing manual translation details. Seeh)      Section 3.6.3 for more information. c   3.4 Navigation a  L Compaq Analyze can connect to many different computers and each computer canH have many different binary event log files available for analysis. It isJ possible to monitor numerous binary event log files generated by differentK computers all from a single web interface. In order to simplify the processvI of monitoring these diverse information sources, the web interface uses asL hierarchical navigation tree composed of groups, nodes, and binary event log: files. The entries in the navigation tree are as follows:   F    - Groups - multiple computers that are logically associated. Groups       contain one or more nodes. E    - Nodes - individual computers. Each node has its two types of logw      files. I    - Log Files - system information stored in binary files. Each node has *      two types of binary event log files:   E         - System Log - the binary system event log where the computern%           writes system information.    B              - Real Time Monitoring - automatic analysis results. G              - Full View - manual analysis results for the system evente                log.   D         - Other Logs - any other binary event log files saved on theJ           computer. These can include old files, files from other systems,L           and examples. Optionally, the other logs can be further divided byL           categories (See Section 3.10.1 for information on modifying Compaq&           Analyze to use categories).   E The tree structure can be collapsed to the group level (Figure 3-4). C  7                              Figure 3-4 Collapsed Tree u  H Click on the expansion symbol for an entry to view its contents. Once anH entry is expanded, the expansion symbol changes to a collapse symbol. ToD hide the contents again, click the collapse symbol. An example of an& expanded tree is shown in Figure 3-5.   7                             Figure 3-5 Navigation Tree i  J Each entry in the tree has a name and an icon that indicates its type. ForG example, in Figure 3-5 you can tell that the jarjar.cxo.dec.com node ish inactive because of its icon.   K You can customize the navigation tree by adding and removing groups, nodes,AJ categories, and binary event log files (see Section 3.5). In addition, youL can view the results of automatic analysis and initiate manual analysis from' the navigation tree (see Section 3.6). l  $ 3.5 Customizing the Navigation Tree   K The first time you run the web interface using your profile, only one entryeJ appears in the navigation tree. The machine that you logged into is listed# as a node under the Default Group. l  L You can customize the navigation tree display by creating new groups, adding* nodes to groups, and selecting log files.   0                                      ***Note*** I After you submit changes to the navigation tree, Compaq Analyze refreshes'9 the display. The refresh process may take a few seconds. e  
 3.5.1 Groups    L All the groups are listed in the navigation tree. If a group includes nodes,K an expansion symbol appears next to its name in the tree. To view the nodesiL under a group, click the expansion symbol. From the navigation tree, you can. create new groups and remove existing groups.    3.5.1.1 Adding Groups   / To add new groups use the following procedure: c  I   1. Click the Compaq Analyze link at the top to the navigation tree. Thee<      Group Maintenance screen appears in the display frame. I   2. Select the Add Groups tab at the bottom of the screen (Figure 3-6). a  7                                   Figure 3-6 Add Group d  D   3. Select the location for the new group from the list of groups. I   4. Use the radio buttons to indicate whether you want the group locateda8      before, after, or nested under the selected group. J   5. Enter the group name in the entry box. If you enter a group name thatH      is already in the navigation tree at the same level, Compaq Analyze"      will not create a new group. A   6. Click the Add New Group button. The new group appears in the       navigation tree.   2                                        ***Note*** H      If you do not enter a group name before you click the Add New GroupB      button, Compaq Analyze will create a group named "newGroup".    3.5.1.2 Removing Groups   0                                      ***Note*** J Removing a group removes all the nodes and files contained in the group asC well as all the lower level groups nested under the removed group. n  7 To remove existing groups use the following procedure: h  I   1. Click the Compaq Analyze link at the top to the navigation tree. The/<      Group Maintenance screen appears in the display frame. K   2. Select the Remove Groups tab at the bottom of the screen (Figure 3-7).e  8                                 Figure 3-7 Remove Group   I   3. Select the group name from the list of available groups. If you wantoB      to remove multiple groups, use one of the following methods:   B         - Hold the Ctrl key and click on each desired group name. H         - If the groups you want to remove are listed together, hold theK           Shift key and click on the first and last group to select all ther           groups between them. e  G   4. Click the Remove Selected Group(s) button. The selected groups area'      removed from the navigation tree.     3.5.2 Nodes   K When you expand a group in the navigation tree, the nodes contained in that H group are shown. Every node can be expanded by clicking on the expansionD symbol next to its name. Expanding a node reveals the log file typesL included in that node, the system log and other logs. You can add and remove. nodes from the groups in the navigation tree.   0                                      ***Note*** K Unless the system is accessible through the nameserver, you must use the IPI( address instead of the name of the node.  A For example, the hostname of a Windows machine using Dynamic Host D Configuration Protocol (DHCP) is not listed with the nameserver, andF therefore must be added using its IP address instead of its hostname.    3.5.2.1 Adding Nodes s  C Any computer where the Director is running can be added to your weboD interface navigation tree as a node. To add additional nodes use the following procedure: p  I   1. Determine the group you want to add nodes to, and click the link forwK      that group. The Node Maintenance screen appears in the display frame. eH   2. Select the Add Nodes tab at the bottom of the screen (Figure 3-8).   6                                   Figure 3-8 Add Node   G   3. Select the location for the new node from the list of nodes in them      group. H   4. Use the radio buttons to indicate whether you want the node located(      before or after the selected node. I   5. Enter the node name in the entry box. Be aware that if you enter theHI      name of a node you are already connected to, Compaq Analyze will addiK      the node again. This will overwrite any Other Logs settings associatedo      with the node. $   6. Click the Add New Node button.   2                                        ***Note*** F      If you do not enter a node name before you click the Add New NodeH      button, Compaq Analyze will prompt you to enter a valid node name.   J Adding a node enables you to display the results of automatic analysis for that node's system event log.    3.5.2.2 Removing Nodes S  0                                      ***Note*** K Removing a node removes all the additional binary event log files contained & in the node from the navigation tree.   6 To remove existing nodes use the following procedure:   J   1. Determine the group you want to remove nodes from, and click the linkG      for that group. The Node Maintenance screen appears in the displayo      frame. K   2. Select the Remove Nodes tab at the bottom of the screen (Figure 3-9). i  8                                  Figure 3-9 Remove Node   J   3. Select the node name from the list of available nodes. If you want to>      remove multiple nodes, use one of the following methods:   A         - Hold the Ctrl key and click on each desired node name. 3G         - If the nodes you want to remove are listed together, hold thetJ           Shift key and click on the first and last node to select all the           nodes between them.   /   4. Click the Remove Selected Node(s) button. r  F If a node is contained in multiple groups, removing it from one of the9 groups will not affect its presence in the other groups.     3.5.2.3 Node Status   K Nodes are either active or inactive. By default, when you connect to a nodegK or load a profile that connects to other nodes, all the nodes are active. A K node is only classified as inactive if Compaq Analyze cannot connect to it.iI Inactive nodes appear in the navigation tree with a red "X" through theirp icon.   J If a node is inactive, you can try to connect to it again at a later time.; To connect to a inactive node use the following procedure: s  I   1. Click the expansion icon next to the node. The only available optiont,      is "Activate this node" (Figure 3-10).   9                                Figure 3-10 Activate Node u  *   2. Click the "Activate this node" link.   K      If the director on the remote node is accessible, a message appears in J      the display frame (Figure 3-11) and the navigation tree is updated to      show the new status.   =                          Figure 3-11 Activating Node Message    H      If the director is not accessible, a message appears in the displayA      frame (Figure 3-12) and the navigation tree is not changed. n  A                      Figure 3-12 Unable to Activate Node Message t   3.5.3 Categories e  G Categories provide a method for grouping the log files listed under thecI Other Logs folder. If you use categories, Compaq Analyze provides another K layer of folders under the Other Logs folder. This feature may be useful ifc  you monitor numerous log files.   0                                      ***Note*** K Categories are an optional feature that is disabled by default. If you wantaJ to use categories, you must enable the feature using the User Settings tab+ on the Settings screen (see Section 3.10). r   3.5.3.1 Adding Categories   K Once you have enabled the categories feature, you can add categories to then@ navigation tree. To add categories use the following procedure:   J   1. Determine the node you want to add categories to, and click the OtherI      Logs entry for that node. The Category Maintenance screen appears in.      the display frame. >   2. Select the Add Categories tab at the bottom of the screen      (Figure 3-13).   9                                 Figure 3-13 Add Category y  I   3. Select the location for the new category from the list of the node'st      existing categories. D   4. Use the radio buttons to indicate whether you want the categoryC      located before, after, or nested under the selected category.  I   5. Enter the category name in the entry box. Be aware that if you enteriJ      the name of a existing category, Compaq Analyze will not create a new      category. l(   6. Click the Add New Category button.   2                                        ***Note*** J      If you do not enter a node name before you click the Add New CategoryC      button, Compaq Analyze will create a category named "newCat". e   3.5.3.2 Removing Categories   0                                      ***Note*** K Removing a category removes all the binary event log files contained in theo# category from the navigation tree. s  ; To remove existing categories use the following procedure: s  I   1. Determine the node you want to remove categories from, and click the L      Other Logs entry for that node. The Category Maintenance screen appears      in the display frame. .?   2. Select the Remove Category tab at the bottom of the screena      (Figure 3-14).   :                               Figure 3-14 Remove Category   K   3. Select the category name from the list of available categories. If younK      want to remove multiple categories, use one of the following methods: g  E         - Hold the Ctrl key and click on each desired category name.  H         - If the categories you want to remove are listed together, holdJ           the Shift key and click on the first and last category to select+           all the categories between them.    2   4. Click the Remove Selected Categories button.   J If a log file is contained in multiple categories, removing it from one of; the categories will not affect its presence in the others.     3.5.4 Log Files   J Each node has two types of binary event log files; the binary system eventK log and all other binary event logs. Thus, each node in the navigation treev1 includes two sub-entries, one for each log type. p   3.5.4.1 System Log a  L The system log is the binary event log file where system events are written.G You cannot change this log file. Click the expansion symbol to view thel< analysis options for the system log in the navigation tree.   J    - Real Time Monitoring - shows the results of automatic analysis in the      display frame. I    - Full View - manually analyzes the system event log and processes allt      the events in the file.    = See Sections 3.1.2 and 3.6 for more information on analysis. u   3.5.4.2 Other Logs    G The Other Logs entry in the navigation tree contains entries for binaryuF event log files other than the system event log. These can include theI example binary log files included with Compaq Analyze or any other binaryeG event log file located on the node. Initially, there are no sub-entriesk3 under the Other Logs entry in the navigation tree. i  I If you are using categories, the Other Logs entry contains the categoriesnH you have created and the categories contain entries for binary event log files.    G See Section 3.6 for more information on manually analyzing a log file. a   Adding Other Logs   J If you want to process a binary event log file saved on the node, you must& add it using the following procedure:   0                                      ***Note*** F If you are using categories, click on a category name to add log files" rather than the Other Logs entry.   I   1. Click on the Other Logs entry for the desired node in the navigationiL      tree. Once the Other Logs screen opens in the display frame, select the"      Add Files tab (Figure 3-15).   :                              Figure 3-15 Add Log File Tab   F   2. Enter the path and filename of the desired binary log file in the      Other Log field. ,   3. Click the Add Log File to Tree button. ?   4. Repeat the process until all the desired files are added.    I The binary event log file is added to the navigation tree under the Othere1 Logs entry or appropriate category for the node. r   Removing Other Logs   G You can remove binary event log files from the navigation tree with the  following procedure: a  0                                      ***Note*** I If you are using categories, click on a category name to remove log filesi" rather than the Other Logs entry.   I   1. Click on the Other Logs entry for the desired node in the navigationt9      tree and select the Remove Files tab (Figure 3-16).    <                             Figure 3-16 Remove Log File Tab   K   2. Select the log file name from the list of available files. If you wantrE      to remove multiple log files, use one of the following methods: s  E         - Hold the Ctrl key and click on each desired log file name. oG         - If the files you want to remove are listed together, hold thegJ           Shift key and click on the first and last file to select all the           files between them.   3   3. Click the Remove Selected Log File(s) button. e  I After you remove a file, the navigation tree is refreshed to reflect youri	 changes. r   3.6 Analysis Information a  G Analysis information can be viewed using any of the following methods: d  G    - To view the results of automatic analysis on a node, either select D      System Log or the Real Time Monitoring entry under System Log. B    - To manually analyze a node's system event log and display the:      results, click the Full View entry under System Log. G    - To manually analyze a different binary event log file and view they8      results, click the log file name under Other Logs.   L When analysis is successfully started, the log file's icon is animated and aE status message similar to the following is shown in the display frame  (Figure 3-17). n  ;                       Figure 3-17 Analysis Started Message w  L If the file cannot be processed for any reason, a message similar to the one in Figure 3-18 is shown. a  ;                        Figure 3-18 Analysis Failed Message l  J Once the file is processed, the icon in the toolbar changes to reflect theI status of the log file (see Section 3.7). To view the analysis results insF the display frame, click the log file's entry in the navigation tree.   0                                      ***Note*** K You can view the results of analysis before a file has finished processing.dK Once Compaq Analyze has finished reading a file and has begun analysis, youoI can click on the file to display any problem reports and events that have E been generated so far. Refer to Section 3.7 for information on how to $ determine when analysis has started.  L Be aware that if you view the results before processing is completed, CompaqL Analyze will not automatically update the display when it finishes analyzingI the file. Once analysis completes, you must click the tab you are viewingI again to see the full results.    J Both automatic and manual analysis results are shown in the display frame.7 The information is divided between the following tabs: 2  +    - Problem Reports - results of analysis eJ    - Summary - description of the contents of the log file (only available      with manual analysis) IB    - Events - translation of the events contained in the log file   2                                        ***Note*** D      If you have configured the User Settings so Compaq Analyze onlyK      performs manual translation, rather than translation and analysis, theeJ      Problem Reports tab is empty. See Section 3.10.1 for more information      on User Settings. b  " 3.6.1 Automatic Analysis Features   F When you are performing automatic analysis, the Clear button, shown in% Figure 3-19, appears in the toolbar.    6                              Figure 3-19 Clear Button   J The Clear button removes all the entries (problem reports and events) from the display tabs.    3.6.2 Manual Analysis Features r  H When you are performing manual analysis, the button shown in Figure 3-20 appears in the toolbar.   8                            Figure 3-20 Reprocess Button   G It is used to reprocess binary log files so they reflect changes to therK report type. Refer to Chapter 6 for more information on changing the report  type.   " 3.6.3 Manual Translation Features   G If the User Settings are configured to only perform manual translation,tL rather than translation and analysis, no information is shown on the problemG reports tab (See Section 3.10.1 for more information on User Settings).oK However, an Analyze button appears in the toolbar when you view the details % of manual translation (Figure 3-21). *  7                             Figure 3-21 Analyze Button    K Clicking the Analyze button will perform analysis for the current log file.nH Thus, if you need to perform analysis, it is not necessary to change the& User Settings and reprocess the file.    3.6.4 Displaying Details y  H Compaq Analyze displays the results of analysis in a list in the displayK frame. You can view the details of any entry by clicking on it in the list.eK In order to make viewing events easier, navigation buttons are available at C the top of each detailed entry. The navigation buttons are shown in 
 Figure 3-22. m  9                           Figure 3-22 Navigation Buttons e  J The buttons are used to move between entries in the list, you can view theI details for other events in the list using the Previous and Next buttons.cF Click the Index button to redisplay the list of entries in the displayJ frame. If there is no event in the list for the Next or Previous button toJ display, you will receive an informational message and detailed entry will not change.   0                                      ***Note*** K If your user settings display event details in a separate window, the Index L button will not be available and clicking the Previous and Next buttons willK not open additional new windows. See Section 3.10.1 for more information on  user settings. c   3.6.5 Problem Reports   C The Problem Reports tab displays the reports that were generated bybI analysis. An example of the problem report list is shown in Figure 3-23.    9                           Figure 3-23 Problem Report Tab l  K The filters that affect how problem reports are displayed are listed at thelG top of the screen. Be aware that the screen only shows the filters thatk@ apply to analysis and may not list all the filters you applied.   K To view the details of a specific report, click on its entry in the list of F available problem reports. The report details are shown in the display? frame. Refer to Appendix A for an example of a problem report. e   3.6.6 Summary   0                                      ***Note*** J The Summary tab is only available when you perform manual analysis. Hence,L if you select Real Time Monitoring from the Navigation Tree, the Summary tab is not displayed.   K The Summary tab describes the event types contained in the binary event loghI file. Each event type is listed along with the number of occurrences. The-F time stamps for the first and last events are listed under the summary information. (Figure 3-24).   6                               Figure 3-24 Summary Tab   L The filters that affected the output are listed at the top of the screen. BeF aware that the screen only shows the filters that apply to the summary5 report and may not list all the filters you applied.    
 3.6.7 Events    L The Events tab provides translation information for the events in the binaryK event log file. Depending on the filtering options that were applied duringnB processing, all the events in the log file may or may not be shown (Figure 3-25). o  5                               Figure 3-25 Events Tab e  L The filters that affected the output are listed at the top of the screen. BeJ aware that the screen only shows the filters that apply to translation and* may not list all the filters you applied.   I To view the text of a translated event in the display frame, click on thetH desired entry in the list of events. Compaq Analyze includes informationK about the source of the event and the time it was created at the top of theiL detailed display. Refer to Appendix A for an example of a translated event.   0                                      ***Note*** I You can control the fields that are shown on the events tab from the User ; Settings window. Refer to Section 3.10.1 for more details. i   3.6.8 Sorting Results   J You can sort the results shown on any tab using the field names. Any fieldH name that appears in blue can be used to sort. Simply click on the fieldG name to sort based on that field. An arrow appears next to the field to I indicate the direction of the sorting. The sorting options are applied tonE all the tabs, regardless of which tab was used to specify the sortingi
 criteria.   L Entries can be sorted in either ascending or descending order. To change theH sort order, click on the field name a second time. The arrow next to theI field changes direction to indicate the new sort order. When the arrow istG pointing up, it indicates an ascending sort. When the arrow is pointingC& down, it indicates a descending sort.    3.7 Processing Status   A With large log files, translation and analysis operations are notrE instantaneous. After you have started processing a log file there areiK several ways to check the operations progress. You can check the processingn? status from either the navigation tree or the Progress window. e   3.7.1 Navigation Tree   G You can quickly determine the status of automatic or manual analysis bytH looking at the icons in the navigation tree. Figure 3-26 shows the icons# used to indicate analysis results. n  6                              Figure 3-26 Status Icons   I When automatic analysis generates a problem report exclamation points arelJ added to the icons for the node, system log, and real time monitoring. TheL icon changes remain until the problem reports list is viewed and the tree isC refreshed. If another problem report is generated after the tree is < refreshed, exclamation points are added to the icons again.   K You can also determine the results of manual analysis on a binary event logfL file by checking the icons. Compaq Analyze uses a animated yellow icon whileK a binary log file is being read and an animated green icon during analysis.rB If processing has completed and problem reports were generated, anJ exclamation point is added to the icon. If processing has completed and noI problem reports were generated, a check mark is added to the icon. UnlikedH the icon changes associated with automatic analysis, the manual analysisG icon changes remain visible until you close the web interface session. f  0                                      ***Note*** J If you are only performing translation, when processing completes the iconC will appear with a dash. See Section 3.10.1 for more information ond; configuring the web interface to only perform translation. a  K In addition to the icon-based status indicators, you can also determine the E processing status by positioning the cursor over the file name in thehK navigation tree and reading the status message at the bottom of the window. C Status messages are shown in the information bar (see Figure 3-2). i   3.7.2 Progress Window   J You can open the Progress window by clicking on the Progress Window buttonK in the toolbar (see Figure 3-3). The Progress window opens in a new browser  window (Figure 3-27).   7                            Figure 3-27 Progress Window z  F The Progress window provides statistics for all the log files that areH currently being analyzed by Compaq Analyze. The information includes theJ node where the log file is located, the name and location of the log file,I and the number of events in the file. If you have selected multiple files I for processing, each file's position in the queue is given. You can clickrE the Stop icon to stop processing any of the listed files. When a filee4 finishes processing, it is removed from the window.   L The Progress window is dynamically updated as the processing status changes,I however, if desired, you can manually refresh the display by clicking the , Refresh icon in the upper left hand corner.    3.8 Creating New Log Files s  K To create a binary event log for use with Compaq Analyze, use the followingr procedure: n  J   1. Click the New Binary Log File button in the toolbar (see Figure 3-3).J      The New Binary Log Screen appears in the display area (Figure 3-28).   =                            Figure 3-28 New Binary Log Screen e  J   2. Enter the input file name, including its path, in the Input File text
      box. H   3. Click the Add Input file Button. The file is added to the Currently       Selected Input Files list. G   4. Repeat steps 2 and 3 until all the desired input files are added. e  2                                        ***Note*** I      If you want to remove one of the input files you added, click on theeF      filename in the Currently Selected Input Files list and click theI      Remove Selected Input Files button. You can select multiple files by <      holding the Ctrl key while you click on the filenames.   J   5. Specify the desired filtering options by either creating a new filter'      or applying an existing template. e  J         - To specify filtering criteria, click the Adjust Filter button atJ           the top of the screen and use the Adjust Filter screen to select6           filtering options (see Section 3.10.1.2.1). K         - To apply an existing filter template, select the desired templaten<           from the drop down list at the top of the screen.   B           For more information on filtering, refer to Sections 3.9           and 3.10.1.2.   =   6. Enter the output file name in the Output File text box.    2                                        ***Note*** D      New binary log files are automatically stored in the ca\newlogsK      subdirectory located under the installation directory, hence it is notn;      necessary to include a path with the Output filename. o  I   7. If you have established a filter that excludes configuration entriesbK      and you want to preserve that filtering in the output file, select thea)      Don't add config entries check box.  G   8. If the output file name already exists and you want to replace thebL      existing file, select the Overwrite file if exists check box. If you doI      not select this check box, and enter a filename that already exists,a(      you will receive an error message. H   9. Click the Create New Log File button to process the input files and%      create the new binary log file. a  2                                        ***Note*** G      It is possible to construct a filter that prevents any events from.K      being added to the new log file. If this is the case, no log file will F      be created. However, even if this is the case, when the OverwriteK      option is selected any file with the same name as the output file will       be lost.    3.9 Applying Filters c  I You can apply filters for manual translation and when creating new binarypF log files. You can also use filters to specify how problem reports andL events are sorted. Specify the desired filter using the Filter Templates bar( at the top of the screen (Figure 3-29).   :                          Figure 3-29 Filter Templates Bar   K If you have previously created filter templates, they will be listed in thef  drop-down list. You can either:   G    - Select an existing filter from the drop down list and if necessary D      modify it by clicking the Adjust Filter button and changing the      filtering options. =    - Click the Adjust Filter button and define a new filter. c  2                                        ***Note*** J      Modifying or defining a filter from the Filter Templates bar does notJ      change an existing filter or save a new filter. Your changes are onlyG      used with the current operation. Use the Filters option under Usert>      Settings to create new templates (see Section 3.10.1.2).   L When you use filters in conjunction with analysis and translation the filterJ description will be shown with the results. However, the filtering optionsL you select are only applied to the appropriate output. Thus, if you select aJ filter that only affects event translation, rather than event analysis andJ translation, the filter will be listed with the event details but not withG the analysis details. Figure 3-30 depicts a filter description from thee event details. m  9                           Figure 3-30 Filter Description r  H Refer to Section 3.10.1.2 for more information on creating and modifying	 filters.     3.10 Settings   G The web interface settings enable you to control how the WEBES DirectorsJ functions and modify the web interface to suit your preferences. To accessL the settings, click the settings button in the toolbar. This updates the webL interface, replacing the normal navigation bar with either the User SettingsF navigation bar. The display frame is updated to show the User Settings screen.   9 You can modify both user settings and Director settings. h   3.10.1 User Settings e  K The user settings are used to modify the web interface, configure filteringtG information and determine what translation information is displayed. To K access the User settings, click the Settings button in the toolbar and thene select the User Settings tab.   7                              Figure 3-31 User Settings r  L Use the buttons located at the right side of the screen to navigate the User settings (Figure 3-31).   J    - Settings - Displays the web interface configuration options. Refer to,      Section 3.10.1.1 for more information. J    - Filters - Opens the Filter Preferences screen which is used to defineH      filter templates and set a default filter. See Section 3.10.1.2 for      more information. aF    - Event Columns - Specifies the translation information you want to2      view. See Section 3.10.1.3 for more details. 1    - Exit Settings - Closes the settings screen. o   3.10.1.1 General Options e  4 The general options screen is shown in Figure 3-31.   A The General User Settings screen presents the following options: o  "    - Save File Lists in Other LogsK      Select this option if you want the navigation tree to save a record ofoF      all the log files listed under Other Logs when you log off CompaqJ      Analyze. If this option is selected, the log files will remain in theJ      navigation tree until you manually remove them. If this option is notH      selected, the Other Logs section of the tree will be empty when you      logon. #    - Use Categories With Other LogsdB      Select this option to use categories with log files. Refer to+      Section 3.5.3 for more on categories.  &    - Put Event Details In A New WindowL      Opens a new browser window for the details of a problem report or eventL      selected from the list of entries. The list of entries will remain open      in the original window. n9    - Manually Translate Files Only (Skip Manual Analysis)tK      Prevents Compaq Analyze from performing manual analysis for log files.mI      This affects the output when you select an entry from the Other Logs H      area and when you perform manual analysis on the system event log.     - Log Off TimesK      By default, Compaq Analyze logs your profile off ten minutes after youWJ      close your connection with the Director. You can change the amount ofD      time by entering a new value in the text box. All values are inD      minutes. See Section 3.12 for more information on logging off.   H If you modify the user settings, click the Update button so your changes
 take effect. i   3.10.1.2 Filters l  J Filtering is used when you perform translation or create a new log file inK order to reduce the number of events processed. With large log files, usingrL only a subset of the events can improve processing time and only display the pertinent output.   L With the web interface, filtering is performed by using templates. TemplatesI are pre-defined filtering functions that can be applied to Compaq Analyze 2 functions in order to obtain the desired results.   L You can use the Filtering Preferences screen to create new filter templates,H modify existing filter templates or select default filtering options. ToH access the Filtering Preferences screen, click the Filters button in the User Settings navigation bar.   9                           Figure 3-32 Filter Preferences e  " 3.10.1.2.1 Adjust Filter Template   E To modify a filter template or create a new filter, use the following2 procedure:    H   1. Select the filter you want to modify from the drop-down list in theK      Filter Templates bar. If you want to create a new filter from scratch,C5      you do not need to select an existing template. eH   2. Click the Adjust Filter button located in the Filter Templates bar.L      The Adjust Filter screen appears (Figure 3-33). If you are modifying anE      existing template, the contents of that filter are listed in the %      Currently Applied Filters list.    9                                Figure 3-33 Adjust Filter    D   3. Ensure that all the filter information in the Currently AppliedD      Filters list is correct. Initially, this field will display theL      contents of the filter template you selected. You can delete any filterL      by selecting it and clicking the Remove Selected Filters button. If you2      are creating a new filter the list is blank. J   4. Choose any additional filtering criteria from the drop-down list. The3      drop-down list includes all the event fields. pC   5. Once you have selected an event field, the Filtering screen is I      dynamically updated to include the valid operators (Figure 3-34). BeiL      aware that all the operators are not valid for all filter types. Select@      the radio button that corresponds to the desired operator.            - Not equal to (!=)          - Equal to (=) w         - Greater than (>) i         - Less than (<)   >                                Figure 3-34 Filtering Criteria   J   6. Once you have selected a operator, the screen is updated to include aL      drop-down list of values or a text entry field (Figure 3-35). Select or"      enter the appropriate value.   <                             Figure 3-35 Filtering Operators   I   7. Click the Apply button. The filter is added to the list of Currentlya$      Applied Filters (Figure 3-36).   9                               Figure 3-36 Applied Filter    J   8. Repeat steps 3 to 7 until all the necessary filters have been added. K   9. Click the Adjust Filter button again to close the Adjust Filter screenoF      and return to the Filtering Preferences screen (Figure 3-32). TheL      Filtering Preferences screen describes the contents of the new filter. G  10. Save the new filter as a template by entering a filter name in thehH      Name text box and click the Add New Template button. Compaq AnalyzeH      will update the Filter Templates list and add the new filter to the1      drop-down list in the Filter Templates bar. w  2                                        ***Note*** I      If you are creating a new filter from one of the details tabs rather E      than the User Settings window, you will not be able to save yourn0      filter. Otherwise the process is the same.    3.10.1.2.2 Default Filters t  K You can apply default filtering options to all the analysis and translation H operations performed from the web interface using the Filter Preferences screen (Figure 3-32).   6 To set a default filter, use the following procedure:   G   1. Select the desired templates from the drop-down list in the FiltergJ      Templates bar. It is not necessary to select a template if you do not'      want to use an existing template. aG   2. If necessary, click the Adjust Filter button and modify the filter (      template or create a new template. 6   3. Click the Save Current Filter As Default button.   2                                        ***Note*** I      It is not necessary to save the default filter as a template. If youSI      want to, you can use the Adjust Filter screen to create a filter andlI      then save it as the default filter without saving it as a template. i   3.10.1.2.3 Deleting Templates   C You can delete a filter template from the Filter Preferences screena. (Figure 3-32), using the following procedure.   E   1. Click on the name of the filter you want to delete in the Filter,L      Templates list. You can select multiple filters by holding the Ctrl key'      while you click the filter names. r/   2. Click the Remove Selected Filters button.     3.10.1.3 Event Columns i  H The Event Columns screen is used to specify the information displayed byH translation on the Events tab (see Section 3.6.7 for more information on translation details).   7                              Figure 3-37 Event Columns t  L The Event Columns screen lists the field headings for event translation. YouL can designate which translation information is shown on the Events tab using the following procedures.    Adding Fields    To add fields: p  H   1. Determine which additional translation fields need to be shown. TheL      first list displays all the available translation fields and the second9      list indicates the fields that are currently shown.  J   2. Select the desired field from the first list by clicking on its name.F      You can select multiple entries by holding the Ctrl key while you      select their names. UJ   3. Click the Add button. The selected fields are added to the end of the1      second list and shown under the Events tab. t   Rearranging Fields h  E The order of the fields in the second list indicates the order of ther information on the Events tab.     To rearrange the fields:    K   1. Select the field that needs to be moved by clicking on its name in the       second list. )   2. Move the field to its new location.    E         - Click the Move Up button to move the field up in the list. SI         - Click the Move Down button to move the field down in the list. 1   Removing Fields    To remove a field: s  K   1. Select the field from the second list by clicking on its name. You canpJ      select multiple fields by holding the Ctrl key while you select their      names.    2. Click the Remove button.    3.10.2 Director Settings    H The Director settings are used to modify WEBES components, register ruleK sets and review log files created by Compaq Analyze. To access the DirectoraF settings, click the Settings button in the toolbar and then select the Director Settings tab. u  8                           Figure 3-38 Director Settings   G Use the buttons located at the right side of the window to navigate the  Director settings. h  E    - Settings - Displays the configuration settings for the Director.eK      Refer to Chapter 6 for information on changing the Director settings. IH    - View Compaq Analyze Logs - Displays the log files created by Compaq>      Analyze. Refer to Section 3.10.2.1 for more information. F    - Register Knowledge - Displays the knowledge rule sets that can beH      installed. Refer to Chapter 5 for more information on rule sets and      analysis. f1    - Exit Settings - Closes the settings screen. f  " 3.10.2.1 Compaq Analyze Log Files   0                                      ***Note*** L Informational log files cannot be viewed on OpenVMS systems. Only Tru64 UNIXC and Windows systems display the text-based informational log files. L Therefore, the View Compaq Analyze Logs button is not available when you are logged into a OpenVMS machine. t  I You can view the text-based error/information log files from the SettingsmK screen. Select the Director Settings tab and then click the View WEBES LogsuJ button. The log files are concatenated into one large file for display and* shown in the display frame (Figure 3-39).   5                               Figure 3-39 WEBES Logs o  L You can use the links at the top of the display screen to navigate to any of the available log files. l  J The following examples show some of the log files that may be shown (refer0 to Chapter 1 for information on the log files):    Tru64 UNIX    A All the log files in the /logs directory are shown, for example: t      - webes_delete.log     - webes_install.log r    - setld_error.log a    - wcc_install.log ,    - desta_dir.log t    - ca_delete.log t    - ca_install.log     - ccat_install.log    Windows   L All the log files in the \logs directory are shown; generally, the following) log files are shown for Windows systems: t      - desta_dir_err.txt 2    - desta_dir_err_backup.txt     - desta_dir_out.txt      - desta_dir_out_backup.txt    3.11 Getting Help   H The web interface provides context sensitive help and a link to the user guide. F   3.11.1 Context Sensitive Help   E Position the cursor of your mouse over an element from the toolbar orxL navigation tree to view a brief description of the option in the information) bar at the bottom of the browser window. e   3.11.2 On-Line User Guide   H Click on the Help button from the Compaq Analyze toolbar to view an HTMLI version of the Compaq Analyze User Guide. The help opens in a new browser  window.   
 3.12 Log Off j  L It is not necessary to manually log off Compaq Analyze. Once your connectionI to the Director is closed, Compaq Analyze will automatically log off your K profile after the log off time elapses. By default, the log off time is set J to ten minutes, however, you can configure the time from the User Settings screen (see Section 3.10.1). r  L You can close your connection by exiting your browser or navigating to a web2 site outside of the Compaq Analyze web interface.   I Once you are logged off, all the data associated with your Compaq Analyze H session is lost. However, if you restore your connection to the DirectorK before the log off time elapses, your data will remain intact. This enablestH you to browse other web sites without loosing your Compaq Analyze data.    3.13 Lost Connection a  I If your connection to the Director is lost for any reason, the message in $ Figure 3-40 appears in the toolbar.   ;                        Figure 3-40 Lost Connection Message e   3.14 Service Obligation   K You can view service obligation information by entering the following URL: l    http://hostname:7902/obligation   9 Where hostname refers to the machine name or IP address. u  @ An example of the service obligation information is shown here:    Service Obligation: Valid & Service Obligation Number: NI93202975 ! System Serial Number: NI93202975  & Service Provider Company Name: Compaq   4 Obligation Start Date: Sat May 13 00:00:00 MDT 2000 5 Obligation Ending Date: Sun May 13 00:00:00 MDT 2001 iL Time left on Obligation: 0 years, 355 days, 13 hours, 52 minutes, 57 seconds     History of changes: A   1. Sat May 13 15:46:22 MDT 2000: Installer (unknown) of Compaq hJ Installation settings changed to start Sat May 13 00:00:00 MDT 2000 to SunJ May 13 00:00:00 MDT 2001 (1 years, 0 days, 0 hours, 0 minutes, 0 seconds) F   2. Sat May 13 15:46:11 MDT 2000: WEBES (Web-based Enterprise ServiceF Common Components V3.0 (Build 12), member of WEBES V3.0 (Build 12)) of Compaq  F Set initial obligation: 0 years, 5 days, 0 hours, 0 minutes, 0 seconds$ ending Thu May 18 15:46:10 MDT 2000  Notifications to be sent i5   1. 0 years, 60 days, 0 hours, 0 minutes, 0 seconds l5   2. 0 years, 30 days, 0 hours, 0 minutes, 0 seconds D5   3. 0 years, 15 days, 0 hours, 0 minutes, 0 seconds i4   4. 0 years, 5 days, 0 hours, 0 minutes, 0 seconds 4   5. 0 years, 4 days, 0 hours, 0 minutes, 0 seconds 4   6. 0 years, 3 days, 0 hours, 0 minutes, 0 seconds 4   7. 0 years, 2 days, 0 hours, 0 minutes, 0 seconds 4   8. 0 years, 1 days, 0 hours, 0 minutes, 0 seconds    3.15 Disabling the Web Service e  H The following procedure describes how to turn off the Compaq Analyze web	 service.    E   1. Stop the Director by entering desta stop at the command prompt.  B   2. Edit the ConfigDefaultsCA*.txt file in the config directory.   0         - Tru64 UNIX - edit the following file:   D           /usr/opt/compaq/svctools/config/ConfigDefaultsCADUnix.txt -         - OpenVMS - edit the following file:    <           svctools_home:[config]ConfigDefaultsCAOpenVMS.txt -         - Windows - edit the following file: a  M           c:\Program Files\Compaq\Svctools\Config\ConfigDefaultsCAWindows.txtl  !   3. Put a # in front of the linecJ      com.compaq.svctools.ca.services.web.CAWebService. The contents of the'      file should look similar to this:    #      # ConfigDefaultsCAOpenVMS.txt u      # c@      # Compaq Analyze Default Components, ** OpenVMS Version **       #  J      # Default components of Compaq Analyze, to enroll the first time the H      # DESTA Director process is executed, as fully qualified Java class      names. K      # After DESTA runs the first time, the file Configuration.dat will be n9      # created, and it will be read on startup instead of-      ConfigDefaults*.txt.       # nK      # Duplicates are OK, so let's add the CommonDirector even though it's hD      # also in ConfigDefaultsDESTA.txt, since we can't run the other      services       # without it.        # f3      com.compaq.svctools.desta.core.CommonDirector o:      com.compaq.svctools.ca.services.analysis.EvtAnalyzer ?      com.compaq.svctools.ca.services.decomposers.EvtDecomposer a=      com.compaq.svctools.ca.services.eventreaders.SwccReader i6      com.compaq.svctools.ca.services.web.CAWebService       # c,      # The next line is specific to OpenVMS <      com.compaq.svctools.ca.services.eventreaders.VMSReader       # TL      # Uncomment the next line if operation of the Unanalyzed Event Logging       # service is desired. aE      #com.compaq.svctools.ca.services.analysis.UnanalyzedEventLogger tF      com.compaq.svctools.desta.services.notification.ACHSNotification   E   4. Delete the configuration.dat file from the following directoriest8      (assuming you used the default install directory):   =         - Tru64 UNIX - /usr/opt/compaq/svctools/desta/config e1         - OpenVMS - svctools_home:[desta.config] oB         - Windows - C:\Program Files\Compaq\Svctools\desta\config   G   5. Restart the Director using the procedures described in Chapter 1. b      J =========================================================================    4    ***Event Translation***   H This chapter describes event translation, including automatic and manualL translation, simulation testing of translation, and viewing and interpreting translation information. y      - Translation Defaults     - Automatic Translation h    - Manual Translation %    - Viewing Translation Information t*    - Interpreting Translation Information 0    - Typical Frame of a Translated Binary Event    4.1 Translation Defaults e  A By default some events are not processed. Under normal operation,pK correctable events are not translated. The events that are usually filteredo	 include: o  9    - Correctable System events (entry types 620 and 630) y6    - Correctable Error Throttling Notification events 9    - Miscellaneous events not used by analysis, such as:             - Time Stamp events '         - Volume Mount/Dismount events  7         - Cold Start (System Boot) and Shutdown events r"         - Software-related events    4.2 Automatic Translation   I Automatic translation, which is enabled by default, captures, translates, L and displays events in the web interface as they are generated by the systemI or soon after. As long as the Director is running all the incoming eventsfL are processed without user intervention. Translated events are passed to allI the web interfaces connected to the Director (on any machine). TranslatedeI events are also passed to the Analysis engine to be analyzed according tot& installed rules sets (see Chapter 5).    4.3 Manual Translation n  C You can open a binary event log file and request that the events behF translated. The resulting reports are only sent to your computer. This) activity is known as manual translation. h  K To translate events from a binary event log file, follow the steps outlinedo# in Chapters 2 and 3 of this guide. s  H On supported platforms, Compaq Analyze can read and translate error logsL produced by any of the supported operating systems. For example, you can useJ the web interface running on your PC to connect to a Director running on aI Tru64 UNIX machine to read, translate, and analyze an event file producedg" previously on an OpenVMS machine.   $ 4.4 Viewing Translation Information   L Translation information is available from the the command line interface andE the web interface. Refer to the following chapters for information onr! viewing translation information: x      - CLI - Chapter 2 t    - Web Interface - Chapter 3    ) 4.5 Interpreting Translation Information r  K A translated binary event consists of three layers of information: overall,t frame, and field.    4.5.1 Overall   B The overall binary event contains one or more translated frames ofI information. There are several types of binary events, each identified bytK its class name. In addition to the frames, some other information is storedl at the overall layer, such as: t  I    - The class name of the binary event (passed to Event Analysis but note%      displayed in the web interface) LC    - The event's "match keys," a set of strings used in identifyingnF      analysis rules that may fire for this event (not shown by the web      interface)    4.5.2 Frame   D A frame within an event consists of one or more translated fields ofJ information. There are many types of frames, each identified by its label.L Each frame type contains a defined set of fields. In addition to the fields,> some other information is stored at the frame layer, such as:   +    - The parent binary event of this frame lA    - The frame's label, displayed at the beginning of each frame w   4.5.3 Field   2 A field within a frame consists of the following:   $    - The parent frame of this field @    - The field's label, both as an identifier (not shown) and as      displayable text H    - The field's value (of a type defined by the type of field) which is      displayed in text form   / 4.6 Typical Frame of a Translated Binary Event    A A typical frame of a translated binary event appears as follows: e  
 Event:     2 oH Description: VMS Asychronous Device Attention at Mon Mar 01 20:59:59 MST 2001 f / rom SABL15 2# File:    ./ca/examples/rx_data.zpd  @ ===============================================================   2 OS_Type              2             -- OpenVMS AXP , Hardware_Arch        4             -- Alpha ; CEH_Vendor_ID        3,564         -- Compaq Computer Corp r? Hdwr_Sys_Type        22            -- Unrecognized System Type := Logging_CPU          0             -- CPU Logging this Event 0 CPUs_In_Active_Set   0 tG Entry_Type           128,098       -- VMS Asychronous Device Attention c> DSR_Msg_Num          1,813         -- Compaq AlphaServer ES40   H This frame contains eight fields: OS_Type, Hardware_Arch, CEH_Vendor_ID,L Hdwr_Sys_Type, Logging_CPU, CPUs_In_Active_Set, Entry_Type, and DSR_Msg_Num.- Each field has a single value, such as "22". W      J =========================================================================    5    ***Event Analysis*** q  K This chapter describes event analysis, including analysis rules, installingiI rule sets, automatic and manual analysis, simulation testing of automatic J analysis, viewing analysis information, interpreting analysis information, and configuration of analysis. s      - Analysis Rules     - Instance Files     - Managing Rule Sets     - Automatic Analysis     - Manual Analysis  "    - Viewing Analysis Information '    - Interpreting Analysis Information o   5.1 Analysis Rules a  K Binary events are analyzed by using DeCOR (the analysis engine used by both K Compaq Analyze and its predecessor, DECevent) to apply rules to them. RulesiH are designed to fire when a particular criteria, such as a threshold, isK met. For example, if the number of events within a given time frame exceedse7 the threshold specified in a rule set, the rule fires.    I Depending on the circumstances, a event may or may not fire any rules. IncK addition, a single event can fire multiple rules. When a rule fires, it may:A produce none, one, or multiple reports. A report may be generated I immediately, or may be generated after a gestation time period defined bysF the rule. Each report is stored in a instance file. After the report'sL expiration time period, defined by the rules, the report is removed from the instance file.    K Analysis rules are coded by Compaq serviceability engineers or other domainuJ knowledge specialists. These rules are stored in Knowledge Rule Set files,G typically with the file extension .krs. A KRS file contains one or morerL rules. One or more rule set files can be installed, or "registered," into an@ analysis instance file at the same time. A rule set can later be. "unregistered" if it is no longer applicable.   0                                      ***Note*** I It is possible to run Compaq Analyze without any rule sets registered (ifeJ the rule sets have been unregistered or deleted). However, if there are noH registered rule sets, analysis will not generate meaningful results. TheB problem report generated by analysis will indicate if there are no/ registered rulesets or no applicable rulesets.     5.2 Instance Files s  F Compaq Analyze stores analysis data in instance files that include the following: d  F    - The paths and filenames of the KRS files to be used for analysis A    - Input entry classes, derived from data in the binary events mF    - Intermediate data such as complex storage classes, derived during      analysis .    - Output report classes (analysis results)   J Typically, the input classes are deleted after reports have been generatedI from them. Automatic analysis results (see Section 5.4) are stored in thei following file:    ca/data/decorEvtAuto.ins r  L Manual analysis is separate from automatic analysis (see Section 5.4) in itsG use of data. The file ca/data/decorEvtManual.ins_seed contains only thelL paths and filenames of the KRS files. Before each manual analysis, this fileG is copied to decorEvtManual.ins in the same directory, which is used totJ store all data for this analysis only. Once analysis is complete, the fileI is renamed decorEvtManual.ins_prev-save, overwriting any file of the same K name. In this way, each manual analysis is isolated from the results of alln: other manual analyses as well as from automatic analysis.    Damaged Instance Files    I Compaq Analyze can detect and recover from an automatic analysis instanceAJ file that is damaged. However, if you believe the instance file is damagedJ and want to reset it to its original default state containing only the KRS filenames, do the following:    1   1. Stop all WEBES processes (see Section 1.7). s'   2. Delete the file decorEvtAuto.ins. n-   3. Restart the Director (see Section 1.6). eK   4. Re-register the default rule sets with the command ca regknw rdef (sees      Section 5.3).    E The manual analysis seed instance file decorEvtManual.ins_seed can beeG restored in the same way if it is damaged, although it is never changede6 except when rule sets are registered or unregistered.   K Contact the Compaq Analyze support team for assistance in diagnosing why ane% instance file may have been damaged.     5.3 Managing Rule Sets h  D Compaq Analyze is installed with all rule sets pre-registered in theE automatic and manual analysis instance files. These rule sets are the E installed files with the .krs extension, in the same directory as the  instance files.   8 You can manipulate the rule sets in the following ways:   J    - View the rule sets that are currently registered (see Section 5.3.1).B    - If you receive or create new analysis rule KRS files, you canG      register the new rule sets as needed into both instance files (seen      Section 5.3.2). eI    - Unregister rule sets that are no longer needed (see Section 5.3.2). y@    - Re-register all the default rule sets (see Section 5.3.2).    5.3.1 Viewing Registered Rules a  B Using the CLI or web interface, you can view the rulesets that are( registered for use with Compaq Analyze.    5.3.1.1 CLI   F The listrk command can be used in either automatic or manual mode, andK provides a list of the paths and versions of the knowledge files registeredC6 with DeCOR. The syntax for the command is shown here:   
 ca listrk    Output d  ? An example of the output from a OpenVMS machine is shown here:    % Registered analysis knowledge files:  * Filename: /SVCTOOLS_HOME/ca/data/ds10.krs    Revision: Rev_3_0_A * Filename: /SVCTOOLS_HOME/ca/data/ds20.krs    Revision: Rev_3_0_A * Filename: /SVCTOOLS_HOME/ca/data/es40.krs    Revision: Rev_3_0_A0 t3 Filename: /SVCTOOLS_HOME/ca/data/gs320_ce_rule.krs p   Revision: Rev1_0 f3 Filename: /SVCTOOLS_HOME/ca/data/gs320_se_rule.krs h   Revision: Rev_01 t8 Filename: /SVCTOOLS_HOME/ca/data/gs320_startup_rule.krs    Revision: Rev1_0 t4 Filename: /SVCTOOLS_HOME/ca/data/gs320_uce_rule.krs    Revision: Rev_01 t* Filename: /SVCTOOLS_HOME/ca/data/mcii.krs    Revision: Revison_0 - Filename: /SVCTOOLS_HOME/ca/data/storage.krs o   Revision: Rev_0.2    5.3.1.2 Web Interface    From the web interface:   1   1. Click the Settings button from the toolbar. y'   2. Select the Director Settings tab. tB   3. Click the Register Knowledge button in the navigation frame.   I All the available rule sets are listed with a check box. Rule sets with a # selected check box are registered. v  . 5.3.2 Registering and Unregistering Rule Sets   F You can register a set of rules (stored as KRS files) using the CompaqH Analyze CLI or web interface. Registered files are used by the automaticD analysis instance file decorEvtAuto.ins and the manual analysis seedG instance file decorEvtManual.ins_seed, both of which are located in thei ca\data directory. i  D You can re-register all default rule sets from the command line. ForL example, you may need to do this if you delete either of the instance files, as described in Section 5.2. s   5.3.2.1 CLI   K Use the regknw command to register or unregister knowledge rulesets in bothf) the automatic and manual instance files.    ( Registering and Unregistering Rule Sets   L The syntax for registering and unregistering rule sets is shown here (in allK cases, the first command shown is used to register rule sets and the second * command is used to unregister rule sets):   + ca regknw r knowledgeFileDir knowledgeFile =+ ca regknw u knowledgeFileDir knowledgeFile =  K Where knowledgeFileDir represents the directory where the knowledge file is4C saved and knowledgeFile represents the name or names of the desiredCF knowledge files. Any number of directories and files can be supplied.   4 When registering files, keep the following in mind:   H    - If you do not use any arguments, you will be prompted as to whetherH      you wish to register or unregister the default knowledge files. See-      Default Rule Sets for more information. nJ    - You can use the relative directory structure for the directory, as in      the following examples:    #      ca regknw r \ca\data\ds10.krs d#      ca regknw u \ca\data\ds10.krs  I    - Wildcards can be used to specify multiple filenames, as shown in the=      following examples: y  "      ca regknw r \ca\data\ds*.krs "      ca regknw u \ca\data\ds*.krs H    - If you specify a directory without a filename, all the files with aH      .krs extension in the directory are registered or unregistered. The>      following examples show commands without any file names:         ca regknw r \ca\data\ e      ca regknw u \ca\data\    2                                        ***Note*** E      When you are specifying individual files to unregister, the fileoJ      path(s) entered at the command line must exactly match the DeCOR file=      path. Specifying a relative path is usually sufficient. rH      However, on OpenVMS systems, a relative or absolute path may not beF      translated into a format compatible with DeCOR. Use the ca listrk4      command to determine the proper path argument.    Default Rule Sets   F The set of *.krs files located in the ca\data directory constitute theL default rule sets. You can register all of the default rule sets with either of the following commands:     ca regknw r  ca regknw rdef p  3 The rdef command does not prompt for confirmation.    L You can unregister all of the default rule sets with either of the following
 commands:    ca regknw u  ca regknw udef o  3 The udef command does not prompt for confirmation.    C If you attempt to register a rule set that is already registered ordJ unregister a rule set that is not registered, error messages will result.   F If you want to restore the automatic or manual instance files to theirJ initial state, follow the procedures for damaged instance files, described in Section 5.2.    5.3.2.2 Web Interface   H To register or unregister a set of rules using the web interface, do the following: e  2   1. Click on the Settings button in the toolbar. B   2. Click the Director Settings tab at the bottom of the window. @   3. Click the Register Knowledge button in the navigation frame      (Figure 5-1). e  8                                  Figure 5-1 Rules Files   J      All the available rule sets are listed with a check box. If the checkD      box is selected the rule set is registered, otherwise it is not      registered.    5   4. Register or unregister the necessary rule sets. n  I         - To register a rule set that is not registered, select the checks            box next to its name. I         - To unregister a rule set that is currently registered, deselectm*           the check box next to its name.   J   5. Click the Update Knowledge Regestration button to save your changes.    5.4 Automatic Analysis ,  F Automatic analysis is the immediate analysis of an event that has beenK captured and decomposed by Compaq Analyze as soon as the event is generated L by the system (or shortly thereafter). No user intervention is required, andH as long as the Director is running, Compaq Analyze analyzes any incomingL events, regardless of any interfaces that may be running. Automatic analysisI is always enabled. Be aware that automatic analysis does not use the timetK stamp information associated with events, rather events are assumed to haveO) occured when the Director receives them. m  L Problem reports resulting from automatic analysis are sent to all interfacesG and to all recipients that are set up to be notified. See Chapter 7 fora4 information about setting up notification services.   	 Scavenge n  D Automatic analysis processes events as they occur. However, when theL Director is stopped, Compaq Analyze creates a marker that indicates the lastE event from the binary log file that was processed. When the system isaJ restarted, Compaq Analyze processes all the events that occurred after theD marker was created. This operation is referred to as scavenging. TheE scavenge operation finds events that are still pending processing anddI ensures that no events are missed, even when the system is restarted. The K first time scavenge occurs, it processes the entire event log. Once this iseH complete, new events are processed as they occur. The scavenge operationL always occurs four minutes after the Director is started. If the Director is= started and stopped within four minutes, no scavenge occurs. e  J Initially, the entire system event log is read to find any events that canG be analyzed. A filter is then applied to the analyzable events. All thelJ events that occurred within a week of the most recent analyzable event are processed. o  K If there are no analyzable events, the scavenge feature becomes dormant andlH a marker representing an unsupported system is added to the scavmark.datH file. As long as the scavmark.dat file containing the unsupported systemK marker is present on the system, no scavenging occurs. If there is at leastbJ one recognized event, scavenging occurs every time the Director is stopped
 and started. g  0                                      ***Note*** L If you set the logging level to Info, you can view a count of recognized and unrecognized events. r   5.5 Manual Analysis   F A user can open a binary event log file and request that the events beH translated and analyzed, returning any problem reports to the requestingG user. This activity is known as manual translation and analysis. UnlikelH automatic analysis, manual analysis relies on the time stamp information> included with each event to determine when an event occurred.   F Manual analysis can be performed from all the interfaces. Refer to the7 following chapters for information on manual analysis: _      - CLI - Chapter 2 _    - Web Interface - Chapter 3 n  J Regardless of the platform it is installed on, Compaq Analyze can read andF translate binary event logs produced by any of the supported operating	 systems. i  # 5.6 Resource Usage During Analysis _  E Whenever Compaq Analyze starts, and when you run manual analysis, thesF 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. n  E Compaq Analyze always relinquishes processor cycles to other programs L whenever they need them. In other words, the program uses whatever resources are available. n  G At startup Compaq Analyze needs the available capacity for the scavengetJ process. Depending on the system, and the size and content of the log, theK initial startup pass can take many minutes or even hours to complete. AfteraK completing the scavenge process, Compaq Analyze drops into idle mode, where - resource usage hovers at only a few percent. s  K If you run Compaq Analyze in manual mode, large amounts of system resourcesaF and processor cycles might also get used. As in the case of startup inL automatic mode, the condition is directly related to the size and content ofJ 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 does.D not grow indefinitely. When you are using manual analysis, it may beK beneficial to filter large log files in order to improve processing times.    ! 5.7 Viewing Analysis Information y  A You can use any of the Compaq Analyze interfaces to view analysislJ information from system generated events and binary event log files. ReferL to the following chapters for more details on viewing analysis information:       - CLI - Chapter 2 n    - Web Interface - Chapter 3 e  & 5.8 Interpreting Analysis Information   H A report consists of a set of String and Value Pairs (SVP). A SVP can be short, for example:   
 Entity Type: w CPU   K A SVP also can be extensive, such as the Full Description or Evidence SVPs,gI which can contain many lines of information (see Appendix A for an outputsL example). A problem report resulting from event analysis always contains the@ following Strings, with Values describing the analysis results.    5.8.1 Managed Entity c  H The Managed Entity designator provides service information regarding theI system on which the problem was found. This includes the system host namewG (typically the computer name for networking purposes), type of computerlJ system, and the error event identification. The error event identificationK information uses new common event header Event_ID_Prefix and Event_ID_CounteK components. The Event_ID_Prefix refers to an OS-specific identification forrK this event type. The Event_ID_Count indicates the number of this event typea that occurred. i   5.8.2 Service Obligation r  H The Service Obligation designator provides information about the service0 provider and the state of the service contract.    5.8.3 Brief Description   I The Brief Description designator provides a high level description of thehH event. This typically includes whether the error event is related to theC CPU, the system (PCI or Storage, for example), or the environmental & subsystem within this managed entity.    5.8.4 Callout ID U  K The Callout ID designator provides information about the analysis rule set.lI The last 12 characters can be used to determine the revision level of thesJ current analysis rule set. All other characters within this designator are, used for Compaq-specific reserved purposes.    5.8.5 Severity g  K The Severity designator provides the service relevance of the occurrence ofnI the problem found. The current severity hierarchy is shown in Table 5-1. s  :                        Table 5-1 Problem Severity Levels  	  Severityf  Level m  -----                     Servicer                   Relevance                    ----- 0                                        Comments -                                        ----- m  1 o                   Critical eN                                        This level is not currently used due toK                                        system operation required for Compaq :                                        Analyze diagnosis.   2 i                   Major J                                        Fatal event that typically requiresL                                        service if not already administered.   3 i                   Minor P                                        Non-Fatal or Redundant warning event thatL                                        typically requires future service butG                                        system still operates normally. r  4 g                   Information M                                        System service event such as enclosure P                                        PCI or Fan door is open and only requires<                                        system door closure.   5 e                   Unknown I                                        This level is not used currently. s         5.8.6 Reporting Node h  L The Reporting Node designator is the node from which the error was reported.I It is synonymous with the Managed Entity host name when Compaq Analyze isrK used for system diagnosis for the system on which it is running. For futurenJ implementations, this may reflect a system server reporting about a clientE for which Compaq Analyze is performing diagnosis within an enterpriser computing environment.     5.8.7 Full Description m  I The full description designator provides detailed error information aboutuA the event. This can include the detected fault or error condition C description, specific address or data bit where this fault or errore1 occurred, and other service related information. o   5.8.8 FRU List u  I The Field Replaceable Units (FRU) List designator lists the most probableeF defective FRUs. This list indicates that qualified service needs to beE administered to one or more of these FRUs. This information typicallyrF provides the FRU probability, manufacturer, system device type, systemJ physical location, part number, serial number, and firmware revision level (if applicable to the FRU).    5.8.9 Evidence    K The Evidence designator provides the error event information that triggered K the indictment. The evidence shown depends on the system that generated theeL error log and the registered rules. As a result the contents of the evidence field may vary.       J =========================================================================    6    ***Configuration***   H This chapter describes configuration, including getting and changing theJ configuration, global and component configuration attributes, and creating! and resetting the configuration. l      - Getting the Configuration h     - Changing the Configuration %    - Global Configuration Attributes t(    - Component Configuration Attributes     - Profiles .    - Creating and Resetting the Configuration    6.1 Getting the Configuration   L You can view the configuration settings for your local Director from the web interface. p  8 To view the configuration, use the following procedure:   2   1. Select the Settings button from the toolbar. F   2. Select the Director Settings tab. The Director Settings window isI      shown in the display frame (see Figure 6-1). By default the Settingsv      button is selected. c  6                                   Figure 6-1 Settings   F   3. To view the details of a specific Global configuration attribute,L      click on the attribute name. The details are shown on the right side of      the window. sF   4. To view the attributes of a different service, click on the WEBESK      Services drop-down menu. A list of services appears (see Figure 6-2). t  <                             Figure 6-2 Selecting an Service   G   5. Choose one of the services currently enrolled into the system (seepJ      Figure 6-3). The attributes associated with service are listed on the      left side of the window.   5      The CAWebService was selected for this example. z  :                              Figure 6-3 Attribute Display   H   6. To view the current value of an attribute, click on its name on theL      left side of the window (see Figure 6-3). The attribute's full name andG      current and default values, are displayed on the right side of thee7      window along with a description of the attribute. i  L      The automatic start component (autoStart) was selected in this example.   6.2 Changing the Configuration v  J You can modify the attribute configuration settings from the web interface or the CLI.   C Normally, it is not necessary to change the attribute settings. ThetL following list describes the attributes that most often need changed, and an8 example of circumstances which might call for a change.   I    - commSocketListenerPort (Communications, Socket Listener Port Number)oD    - under Global Attributes. Used to change the communications portI      number. Do not change the commSocket ListenerPort attribute from theaK      web interface, see Section 6.3.2 for information on configuring ports.oL      You may need to change the port number if there is another, conflicting      application. I    - commConnectionTimeout (Communications, Connection Handshake Timeout)bH    - under Global Attributes. Used to change the amount of time that can(      elapse before the system times out.L      You may want to change the Timeout setting if your network is very slowH      and you want to allow more time for connections before timing out. F    - Report Type - under Global Attributes. Used to change the problem+      report display from detailed to brief.mL      Unless you specifically need the full report output, you should use theI      brief report. See Section 6.3.3 for more information on changing thea      Report Type. G    - autoMode (Automatic Mode) - under the Reader attributes (DUReader,oH      VMSReader, or NTReader depending on your operating system). Used toK      enable or disable automatic processing of the binary system event log.sK      You may want to change the autoMode setting if there are event entriesoH      for hardware that is not supported by automatic hardware analysis. G    - HTTPServerPort - under CAWebService Attributes. Used to change thesB      port used for http communications. See Section 6.3.2 for more&      information on configuring ports.J      You may need to change the port number if there is a usage conflict.   
 6.2.1 CLI   - The CLI has limited configuration abilities. n  
 Socket Ports s  E The socket ports can only be modified from the command line. Refer too1 Section 6.3.2 for details on changing the ports.     6.2.2 Web Interface   I Using the web interface, you can change attributes from the ConfigurationcK Settings window (see Figure 6-1). Attributes that can be changed have a NewuL Setting field and three buttons in the System Configuration window. You must7 select an attribute to determine if it can be changed. t  K To change the value of an attribute, enter the new value in the New SettingeJ field. Depending on the attribute that you want to change, you may be ableC to select the new attribute value from a drop-down list or change aiG check-box setting. After changing attributes you have several choices. n  @    - Click the Change button to apply the changes to the current      attribute. I    - Click the Reset button to change the values of the current attributea'      back to their last applied value.  A    - Click the Default button to change the values of the currenta(      attribute to their default values.   J If you leave the Configuration Settings window without clicking the Change) button, your modifications will be lost. h  $ 6.3 Global Configuration Attributes   I The attributes listed under "Global Attributes" affect every component in D the Compaq Analyze system on the current machine, whether or not the2 component has been enrolled in the configuration.    6.3.1 Changing the Attributes   C Changes to the Logging attributes (prefaced with "log") take effect 
 immediately. -  F Changes to the Communications and Controller attributes (prefaced withL "comm" and "ctrlr," respectively) take effect only when a new Compaq AnalyzeL process is started (such as the Director or another process that connects to the Director). e  D Be aware that changing a global configuration attribute affects both interfaces.    6.3.2 Changing Ports    J Table 6-1 describes the ports used by Compaq Analyze and indicates whether or not they can be configured.    2                                   Table 6-1 Ports 
  Port Number    ----- v                 Used For                   ----- R                                                                      Configurable K                                                                      -----    7901 -                 Connections to the director. nI                                                                      Yes d  7902 2                 Web service (http communications) I                                                                      Yes    7903 2                 Web service (http communications) H                                                                      No   7904 =                 EVM connection to the Director. (Although EVMh<                 is a UNIX tool, the Director listens to this2                 socket on all operating systems.) H                                                                      No   1998                   Service Cockpit H                                                                      No   8944 >                 QSAP (see Chapter 7 for more details on QSAP) I                                                                      Yes d  25 <                 SMTP mail. This is the standard port used by?                 TCP/IP systems for SMTP (see Chapter 7 for more..                 details on configuring SMTP). H                                                                      No         J If a port is configurable, you can change the port number used. Most portsL are configured using the web interface, however, the commSocketListenerPort,L which is used for connections to the director, can only be modified from the CLI.     Connections to the Director   E The commSocketListenerPort defines the TCP/IP socket port used by theeL Director to communicate with other processes on the same machine or on other1 machines on the network (Port 7901, by default). n  0                                      ***Note*** J Do not change the commSocketListenerPort attribute with the web interface.G If you do, the Director cannot be stopped from that point on. After thesI socket port is changed, only a service that is already connected can stopg& the Director running on the old port.   K To change the TCP/IP socket port attribute on all operating systems use theg+ following command from the command prompt. g   desta msg -chgport nnn! Where nnn is the new port number e  H This command changes the port number and then stops the Director and allK connected processes. After the Director has finished shutting down, you canu# safely restart it on the new port. o  L The Director can only communicate with Directors on other machines that haveC the same TCP/IP socket port number defined in their configuration. S   6.3.3 Changing the Report Type e  K When you change between the Full Report Type and the Brief Report Type, the G changes will not be visible in binary event logs that have already been G processed using the web interface. When you change the report type, thecF output from manual and automatic analysis is cached using the previousL report type. To view the analysis results with the new report type, you will' need to reprocess the binary log file. c  D    - To reprocess the system event log file, select Full View in theK      navigation frame and click the Reprocess button located in the displaye      frame. F    - To reprocess any other log file, select its entry under the OtherH      Logs heading in the navigation frame and click the Reprocess button#      located in the display frame.    L Refer to Chapter 3 for more information on manual analysis and the Reprocess button.   ' 6.4 Component Configuration Attributes c  L Attributes for all components fall into two categories (indistinguishable inC the web interface): common attributes and extended attributes. (FordL additional information about configuration attributes, refer to Chapter 5.)    6.4.1 Common Attributes   F Attributes that each component contains by default are known as commonE attributes. They are still owned by their component, so the autoStarteJ attribute for one component is independent from the autoStart attribute of another component. e   6.4.2 Extended Attributes   C Attributes specific to a particular component are known as extended I attributes. For example, the "watchFlags" attributes of the "EvtAnalyzer"eL component do not exist in any other components, since they only apply to the Event Analysis service.   
 6.5 Profiles h  K When you are using the web interface, your changes to the configuration arerJ saved in a profile. The profile for the current session is saved using the@ login name you entered (see Chapter 3). To restore your previousK configuration settings when you restart the web interface, simply enter theo same login name. t  K Your profile is saved on the machine where you logged on; if you logon to anH different machine the it will use the default settings. To customize theK settings you will need to create a new profile and change the configuration E settings. Thus, if you want to use the same configuration settings on I several different machines, you will need to have a profile on each one.    0                                      ***Note*** L Profile names are case sensitive. Changing between upper case and lower caseL letters will create additional profiles. To access a profile, you must enter, the profile name exactly as it was created.   - 6.6 Creating and Resetting the Configuration d  E The first time that Compaq Analyze is started on a machine, a warning L similar to the following is written to the Director log file. (See the WEBESG Installation Guide and Chapter 1 of this guide for more on log files.) r   ___.  @ WARNING on February 1, 2001 11:23:35 AM MST (0.023 sec elapsed) J Configuration file /usr/opt/compaq/svctools/desta/config/Configuration.dat not found, creating it.  Current Thread[main,5,main]   K This warning is expected and correct. The Configuration.dat file is createdmL based on the contents of the ConfigDefaults*.txt file in the svctools/configF directory. (The warning example shown is for a Tru64 UNIX system.) The> classes named in those files will "enroll themselves" into theK configuration, which is then saved as Configuration.dat, a binary file thatcL should not be edited directly. Changes made from the web interface are savedJ in this file by the Director. This warning should not appear on subsequent starts of the Director.   J If the configuration becomes damaged, or you wish to return to the defaultG configuration state when Analyze was first started, make sure no CompaqhL Analyze or WEBES processes are running (including the Director process), andL delete the Configuration.dat file. When you restart Compaq Analyze, the fileK will be recreated with the standard defaults, using ConfigDefaults*.txt then7 same way as the first time Compaq Analyze was started. t      J =========================================================================    7    ***Notification*** b  E This chapter describes how to configure Simple Mail Transfer ProtocolgG (SMTP), System Initiated Call Logging (SICL), and Compaq Remote Support C Service (CRSS) for automatic notification as well as how to disableh automatic notification.   (    - Configuring SMTP Mail Notification     - Customer Profile File r.    - Enabling and Disabling SICL Notification #    - Configuring CRSS Notification e    - Indictment API    7.1 Automatic Notification o  L Automatic notification enables you to distribute problem reports over e-mailG without manual intervention. Be aware that problem reports generated by D manual analysis are not sent out for notification. Only reports from! automatic analysis are sent out. t  I The following sections describe how to configure automatic notification. a  ' 7.2 Configuring SMTP Mail Notification s  I Automatic notification provides the capability to send problem reports tog& recipients through the SMTP protocol.   0                                      ***Note*** J If you want to use SMTP (e-mail) automatic notification, your machine mustL either have connectivity to another SMTP server on the TCP/IP network, or itJ must have its own SMTP server. For further information on configuring yourH machine as a SMTP server, refer to your operating system documentation.   J To set up SMTP (E-mail) notification of problem reports, you must edit theK NotifyCA.txt file. You may have already entered the appropriate information H during installation. If so, you will find the information stored in this file.   G Use any text editor to open the file and specify what server to use for J sending E-mail notification and the users to whom messages should be sent.F The NotifyCA.txt file is in the following locations, depending on your operating system:   1    - Tru64 UNIX: /usr/opt/compaq/svctools/config t%    - OpenVMS: svctools_home:[config] a'    - Windows: install directory\config  I      where install directory indicates the directory where Compaq Analyze       was installed    1 The basic format of the text file is as follows: e   SERVER=servername  FROM=username1@server.xxx.com : TO=username1@mailaddress1.com; username2@mailaddress2.com  CC=username3@mailaddress3.com   H The servername must be either a machine currently running an SMTP serverK process, or localhost if the machine running Compaq Analyze is also an SMTPeJ server. The users you identify in the TO and CC fields of the NotifyCA.txtJ file are automatically sent problem reports. Extraneous spaces are ignoredG and the semicolon can be used as a recipient separator in the TO and CClI fields. The CC field is optional. For changes in the NotifyCA.txt file toe: take effect, you must stop the Director, then restart it.   4                                 ***Note for UNIX*** G If your environment does not allow for SMTP forwarding using the normaliB protocol, you can add the following line to the NotifyCA.txt file: CMD=mailx -s '%s' %t pJ The mailx command can be replaced with any other command for sending mail.K The %s is substituted for the subject line of the problem report. The %t iscJ substituted with a space-separated list of the mail addresses specified on( the TO= lines of the NotifyCA.txt file.   ) Disabling and Enabling SMTP Notification d  I The SMTP Notification service is enabled by default, but will not perform E any notification until the configuration procedures described in thisrK section are performed (unless the necessary information was provided during J installation). To disable any notification of problem reports, use the webG interface to deselect the "autoStart" checkbox in the SMTP Notification.L service's configuration attributes. The next time the Director is restarted,J the Notification service will not be started, and no mail will be sent forL problem reports. See Chapter 6 for more information regarding configuration.  I To re-enable the service, select the "autoStart" checkbox and restart theh
 Director.    7.3 Customer Profile File   K You will need a customer profile file in order to automatically notify youreI Compaq qualified service provider of problems detected by Compaq Analyze.cE The profile file provides contact and system information used by yours service provider.   I Normally, the customer profile file is named profile.txt and depending on D your operating system, the file's location defaults to the following directory: V  /    - Tru64 UNIX: /usr/opt/compaq/svctools/data r#    - OpenVMS: svctools_home:[data]  5    - Windows: install directory\compaq\svctools\data eI      where install directory indicates the directory where Compaq Analyze       was installed u  K You can change the name and location of the profile file, however, you willmF need to modify the path to reflect those changes (see Section 7.3.2).    7.3.1 Profile File Contents   H The installation process creates a profile file for you, however, if youL need to change the file you can do so using a text editor. The file includesB contact information, company information, and system information.   E If you modify the profile file, you should maintain the format of thed@ information and save your changes in the appropriate directory.    7.3.2 Path Setup    J In order to use a profile file, you must specify the fully qualified path.I Specify the path in the install directory\svctools\desta\config\desta.regsH file (install directory refers to the directory where Compaq Analyze was: installed). Add the following line to the desta.reg file:    CA.ACHSProfile=filename   F Where filename is the path and name of the profile file. Be aware thatB backslash characters must be duplicated in order to be interpreted correctly. o  J For example, on a Windows system using the default file name and location,, the path statement would appear as follows:   F CA.ACHSProfile=C:\\Program Files\\compaq\\svctools\\data\\profile.txt   - 7.4 Enabling and Disabling SICL Notification n  K SICL enables the Compaq Analyze software to log service calls with a CompaqgK Customer Support Center. Before you enable SICL notification make sure thate you have DSNLink installed.   F SICL notification is enabled and disabled from the command prompt. The syntax is given below: o   Enable - ca sicl on    Disable - ca sicl off   H Once you have entered the command to enable or disable SICL, you will beK prompted to verify the action. To complete the process, answer the prompt. n  D If you don't want to view the prompts, you can disable SICL with the following command:     ca sicl off silent    F After enabling or disabling SICL, stop and restart the Director so theF changes take effect. For more information on stopping and starting the Director, refer to Chapter 1.   " 7.5 Configuring CRSS Notification   0                                      ***Note*** I CRSS is only used with Windows Intel systems with the CRSS kit installed.2L Refer to Section 7.4 for information on configuring SICL for systems without the CRSS kit.   E CRSS provides automatic notification for Windows systems. For CRSS toa6 function properly, you need to configure your system.   / 7.5.1 Enabling and Disabling QSAP Notification    F Before you can use CRSS, you will need to enable communications with a, Qualified Service Access Point (QSAP) node.   6 QSAP is enabled and disabled from the command prompt:    Enable - desta qsap on ,   Disable - desta qsap off g  D When you disable QSAP, you will be prompted to verify the action. To) complete the process, answer the prompt. t  C To disable QSAP without being prompted, use the following command:     desta qsap off silent    7.5.2 Event Log Settings s  J If your event log is completely full no more events can be logged and CRSSK will not be able to perform automatic notification. In order to ensure thatnC the log does not fill, you should make sure the event log is set todH automatically remove old events. Change the event log settings using the following procedure.    .   1. Open the Start menu and select Programs |K      Administrative Tools (Common) | Event Viewer. The Event Viewer opens. =C   2. Select Log Settings from the Log pull-down menu. The Event Log*-      Settings dialog box opens (Figure 7-1). i  @                        Figure 7-1 Event Log Settings Dialog Box   J   3. Select the Application Log using the drop-down list at the top of the      dialog box. i9   4. Use the following settings for the Application Log: a  ,         - Maximum Log Size - 2048 Kilobytes -         - Overwrite Events Older than 2 Days    0   5. Click the OK button to apply your changes.    7.6 Indictment API    0                                      ***Note*** H Indictment API only operates on GS80, GS160, and GS320 platforms runningI Tru64 UNIX version 5.1 and newer. If both conditions are true, the threadtG running Indictment API will automatically start, otherwise it cannot be 	 started. w  H Component indictment describes the process of analyzing specific failureA patterns, either independently or over a given time interval, and L recommending a component's removal. Normally, a service request is initiated  to replace indicted components.   K The Indictment API provides a common mechanism for Compaq Analyze to notify,I the operating system that a component is faulty and needs to be replaced.TI The Hardware Component Module receives the indictment notification, marksnJ the component as indicted, places the indicted state in a permanent store,A and posts an indictment event to the Event Management Subsystem. e  , The indictment event can then be passed to:   H    - SMS - notifies the administrator that a component has been indictedI      by changing the graphical representation of the indicted component.  A    - EVM - notifies the adminstrator about the indictment via itse'      configurable forwarding facility. o      J =========================================================================    A    ***Sample Outputs***    G This appendix provides examples of translated event output and analysisS output.   6    - Sample Configuration EntrySample Analysis Output $    - Sample Translated Event Output   5 A.1 Sample Configuration EntrySample Analysis Output d  L Problem Found: Memory Channel Link Transmit Error at Mon Apr 17 12:20:43 EDT   2000 n   Managed Entity:   " ------ Product Information ------     Computer Name:         sabl28    Record Number: Prefix: xB7EA r   Service Obligation Data:    Service Obligation: Valid v$  Service Obligation Number: CSC1369 "  System Serial Number: A123456789 '  Service Provider Company Name: Compaq     Brief Description:    $  Memory Channel Link Transmit Error    Callout ID:     TPE03x0018x1011-08   
 Severity:     2     Reporting Node:     sabl28    Full Description:   <  ----- Standard HUB Error Description and FRU Callout ----- E  This reporting Adapter detected an error in the transmit FIFO path. eC  ----------------------------------------------------------------- f  Most Probable Cause: #   This reporting CCMAB-AA Adapter. e  Next Most Probable Cause: d3   The CCMLB-AA Linecard connected to this Adapter. a  
 FRU List:     Standard Hub FRU List: <   Highest Probability:      This Reporting CCMAB-AA Adapter #   Manufacturer:             Compaq h7   Description:              PCI Memory Channel Adapter p0   Location:                 PCI Slot: x00000009 (   Part Number:              54-24962-01 -   ------------------------------------------ h$  Next Highest Probability: CCMLB-AA #   Manufacturer:             Compaq n>   Description:              Memory Channel Linecard Interface (   Part Number:              54-24966-01 B   This Adapter is connected to the Linecard in slot 0 of the HUB.   
 Evidence:   5  Local Time of Event: Thu, 8 Jan 2001 15:45:38 -0400  -  Link Control and Status Register: x0000C07B o*  Memory Channel Error Register: x12020258   # A.2 Sample Translated Event Output h  C The following samples show both full and brief translation output. r   A.2.1 Full t  
 Event:     2 fH Description: VMS Asychronous Device Attention at Mon Mar 01 20:59:59 MST 2001 f e rom SABL15 c# File:    ./ca/examples/rx_data.zpd  @ ===============================================================   2 OS_Type              2             -- OpenVMS AXP , Hardware_Arch        4             -- Alpha ; CEH_Vendor_ID        3,564         -- Compaq Computer Corp t? Hdwr_Sys_Type        22            -- Unrecognized System Type  = Logging_CPU          0             -- CPU Logging this Event o CPUs_In_Active_Set   0 fG Entry_Type           128,098       -- VMS Asychronous Device Attention :> DSR_Msg_Num          1,813         -- Compaq AlphaServer ES40 >                                    .... CPU Slots: 1 (500Mhz) 6                                    .... PCI Slots: 10 =                                    .... MMB Slots: 8 (DIMMs) n0 Chip_Type            8             -- EV6 21264  CEH_Device           49  CEH_Device_ID_0     x0000 0000 e CEH_Device_ID_1     x0000 0000 l CEH_Device_ID_2     x0000 0000 i Unique_ID_Count      93  Unique_ID_Prefix     2  - TLV_DSR_String       Compaq AlphaServer ES40 s TLV_DDR_String .  TLV_Sys_Serial_Num   NI73702WH1 4 TLV_Time_as_Local    Mon, 1 Mar 2001 20:59:59 -0700  TLV_OS_Version       X6O1-SSB  TLV_Computer_Name    SABL15  emb_ertcnt          x0000 0016 y. emb_class            128            Bus Class 3 emb_type             49             Memory Channel o emb_bcnt             0 q emb_errcnt           1 h emb_func             0 e ucb_name_len         10   ucb_name             SABL15$MCA  ucb_dtname_len       0 r ucb_dtname q" Revision_Information   x0000 0001 " Family_ID              x0000 0016 " Member_MC_ID           x0000 0007 " MC_PCI_Bus_Number      x0000 003D " MC_PCI_Slot_Number     x0000 0003 " MC_PCI_Frame_Size      x0000 00A4  Vendor_ID              x1011 r Device_ID_MC           x0018 i Bus_Cmd                x0146 f Bus_Status             x0400 h Rev_ID                  176  RegProg                x00 P Sub_Class              x80 s Base_Class             x02 n Cache_Line_Size        x00 i Latency_Timer          x10 e Header_Type            x00 o BIST                   x00 g Window_Cntl            x08 f  PCITbar                x78 0000 " Base_Addr_1            x7800 0008 " Base_Addr_2            x0000 0000 " Base_Addr_3            x0000 0000 " Base_Addr_4            x0000 0000 " Base_Addr_5            x7800 0008 " Cardbus_CIS            x0000 0000  Sys_Vendor_ID          x0000 s Subsystem_ID           x0000 d" Expansion_ROM_Base_Addrx07C0 0000  Interrupt_Line          12 . Interrupt_Pin           1  Min_Gnt                 0  Max_Lat                 0 " PCT_Data               x0000 0000 " MCLcsr                 x0000 C07A     RPE[1]               x1 o    Rx_Err_Ena[3]       x1     Tx_Err_Ena[4]       x1     MC_Int_Ena[5]       x1     Port_Change_Ena[6]  x1     Port_Change_Int[14] x1     INT_Summary[15]     x1   " PCIRbar                xF800 0000 " MCError                x1202 0202     Rx_Err_on_Data[1]   x1     Cntl_Packet_History[9]x1     Heartbeat_Ena[17]   x1     Sum_Rx_Err[25]      x1     Sum_Tx_Err[28]       x1 i  " MCPort                 x5642 0000     Line_Card_Slot[21:16]x02     Hub_Type[24:22]     x1     Rsvd_1[25]          x1     Heartbeat_Timeout_Sel[26]x1 i    Adapter_OK[28]      x1     Hub_OK[30]          x1   " Config                 x0000 001F " Port_Online            x0000 0000 " Cluser_Status_Low      x0000 0002 " Cluser_Status_High     x0000 0000 " Node_0_Low             x0000 0000 " Node_0_High            x0000 0000 " Node_1_Low             x0000 0000 " Node_1_High            x0000 0000 " Node_2_Low             x0000 0009 " Node_2_High            x0000 0000 " Node_3_Low             x0000 0000 " Node_3_High            x0000 0000 " Node_4_Low             x0000 0009 " Node_4_High            x0000 0000 " Node_5_Low             x0000 0000 " Node_5_High            x0000 0000 " Node_6_Low             x0000 0000 " Node_6_High            x0000 0000 " Node_7_Low             x0000 0000 " Node_7_High            x0000 0000    A.2.2 Brief   
 Event:     2 .H Description: VMS Asychronous Device Attention at Mon Mar 01 20:59:59 MST 2001 f m rom SABL15 V$ File:     ./ca/examples/rx_data.zpd @ ===============================================================   1 OS_Type              2            -- OpenVMS AXP  + Hardware_Arch        4            -- Alpha n: CEH_Vendor_ID        3,564        -- Compaq Computer Corp > Hdwr_Sys_Type        22           -- Unrecognized System Type < Logging_CPU          0            -- CPU Logging this Event  CPUs_In_Active_Set   0 iF Entry_Type           128,098      -- VMS Asychronous Device Attention = DSR_Msg_Num          1,813        -- Compaq AlphaServer ES40  =                                   .... CPU Slots: 1 (500Mhz) I5                                   .... PCI Slots: 10 i<                                   .... MMB Slots: 8 (DIMMs) 0 Chip_Type            8            -- EV6  21264  CEH_Device           49  CEH_Device_ID_0     x0000 0000 p CEH_Device_ID_1     x0000 0000 o CEH_Device_ID_2     x0000 0000 e Unique_ID_Count      93  Unique_ID_Prefix     2 m- TLV_DSR_String       Compaq AlphaServer ES40 m TLV_DDR_String    TLV_Sys_Serial_Num   NI73702WH1 4 TLV_Time_as_Local    Mon, 1 Mar 2001 20:59:59 -0700  TLV_OS_Version       X6O1-SSB  TLV_Computer_Name    SABL15 . emb_class            128            Bus Class  emb_type             49    A.3 Sample Configuration Entry t   COMMON EVENT HEADER (CEH) V2.0  *  OS_Type            1       -- Tru64 UNIX %  Hardware_Arch      4       -- Alpha t4  CEH_Vendor_ID      3,564   -- Compaq Computer Corp 6  Hdwr_Sys_Type      35      -- GS40/80/160/320 Series 6  Logging_CPU        0       -- CPU Logging this Event   CPUs_In_Active_Set 1 3  Entry_Type         110     -- Configuration Event e8  DSR_Msg_Num        1,968   -- Compaq AlphaServer GS160 +  Chip_Type          11      -- EV67 21264A o  CEH_Device         54    CEH_Device_ID_0    x0000 03FF =  CEH_Device_ID_1    x0000 0007 =  CEH_Device_ID_2    x0000 0007 t  Unique_ID_Count    0   Unique_ID_Prefix   32,640 e     TLV Section of CEH i9  TLV_Time_as_Local       Tue, 21 Mar 2000 07:11:16 -0700 s   TLV_Computer_Name       wfsi21 8  TLV_DSR_String          Compaq AlphaServer GS160 6/731 8  TLV_OS_Version          Digital UNIX V4.0G (Rev. 1511) $  TLV_Sys_Serial_Num      PROTO-WF21      Configuration Entry   NOTE 8   -  CONFIGURATION ENTRY encountered in Event Log File. 9   -  A Decomposed Configuration Tree Report is available a:        for this event, and may be selected seperately for &        display in certain user modes.       J =========================================================================    B   ' ***Known Messages in Compaq Analyze*** u  L This appendix describes known messages sent by Compaq Analyze to its messageL logs (see Chapter 1 of this guide for more information on the message logs).J Though they may appear to indicate problems, they are known and expected.        - Configuration File Created 7    - Start-up Errors in DUReader, Binlog, and Scavenge e    - JIT Compiler Not Found     - Two Director Processes     - File Not Found    B.1 Configuration File Created i   ___. .@ WARNING on February 1, 2001 11:23:35 AM MST (0.023 sec elapsed)          Configuration fileK /usr/opt/compaq/svctools/desta/config/Configuration.dat not found, creating  it. $         Current Thread[main,5,main]   F This warning is expected and correct the first time the Compaq AnalyzeG Director is executed on a machine. See Chapter 6 of this guide for moreb
 information.    6 B.2 Start-up Errors in DUReader, Binlog, and Scavenge    ___.  L RECOVERED FROM ERROR on February 2, 2001 4:09:51 PM MST (1.263 sec elapsed) K <local>:16063208187:com.compaq.svctools.ca.services.eventreaders.DUReader:2e( Error during connected read of Mailbox:  Current Thread[Thread-10:o9 com.compaq.svctools.ca.services.eventreaders.DUWaiter foro@ com.compaq.svctools.ca.services.eventreaders.DUReader:2,5,main] K EXCEPTION com.compaq.svctools.desta.core.DESTAException: binlog not open at K com.compaq.svctools.ca.services.eventreaders.Binlogd.read(Compiled Code) atnL com.compaq.svctools.ca.services.eventreaders.DUReader.connect(Compiled Code)L at com.compaq.svctools.ca.services.eventreaders.DUWaiter.run(Compiled Code)  ___.  L RECOVERED FROM ERROR on February 2, 2001 4:10:01 PM MST (11.296 sec elapsed)        Scavenge didn't start: ! Current Thread[Thread-11,5,main] tC EXCEPTION com.compaq.svctools.desta.core.DESTAException: timed out o atK com.compaq.svctools.ca.services.eventreaders.EvtReader.scavengeLog(Compiled  Code) H at com.compaq.svctools.ca.services.eventreaders.EvtReader$1.run(Compiled Code)   K These messages appear if a user without privileges to read the system error K log file attempts to start the Director. The Director continues to execute, I but events written to the system error log are not captured. The previous)G messages show examples for Tru64 UNIX. Other operating systems may show  similar error messages.   L If the user starting the Director does have superuser privileges, then theseK messages may appear if the binlogd daemon is not running. If the command psmE -ef | grep binlogd does not show a binlogd process running, it can beH= restarted by a superuser with the command /usr/sbin/binlogd. S   B.3 JIT Compiler Not Found o  A dlopen: Cannot map library libsuncompiler.so (libsuncompiler.so)  E Warning: JIT compiler "suncompiler" not found. Will use interpreter.    H This message only appears on Tru64 UNIX systems when the standalone JavaK Runtime Environment (JRE) is installed instead of the full Java Development L Kit (JDK). It is generated by the Java Virtual Machine when any Java code isI started using the jre command and displays when the desta or ca script isPD used to start a Compaq Analyze process. It is expected and correct.    B.4 Two Director Processes    = Refer to Section 1.5 for information on the WEBES processes.     On Tru64 UNIX and Windows   J With all WEBES products installed, desta start starts two instances of theG java executable (java on UNIX, java.exe on Windows). The first instancenL contains the DESTA Director and all WEBES services except the Crash AnalyzerE service (CCAT). The Director spawns this crash analyzer as the secondf1 instance, which is a subprocess of the Director.    K Because the DeCOR analysis engine (a C++ library) does not support multiplexI simultaneous databases and is not re-entrant, each service that wishes to0K use DeCOR separately must run in a separate process. There are two servicesuH that use the DeCOR library - Compaq Analyze's event analyzer, and CCAT'sL crash analyzer. The Compaq Analyze service runs in the main process with theJ Director, and CCAT's analyzer is spawned in a separate process at startup.L All services started by the Director continue to run for the lifetime of theG java processes. If CCAT is not installed, there is no second instance. e   On OpenVMS    J There may be two WEBES processes, but they are labelled differently in theL SHOW SYSTEM output. The first process is labelled DESTA DIRECTOR. The secondI is normally SYSTEM_1 for example, if the SYSTEM user starts the Director. K The numeric suffix may vary. WEBES processes are labelled USERNAME_n, where I USERNAME is the user that started it, and n is the nth process started by  that user. H   B.5 File Not Found ]  / Could not find file: CAApplet403BeanInfo.class    F This message appears in the Director's log file the first time the webJ interface is activated. It does not affect proper operation of any part of# Compaq Analyze and can be ignored. 0   B.6 Indictment CCAT Error    __. L RECOVERED FROM ERROR on March 31, 2001 1:52:29 AM JST (109.722 sec elapsed) D Could not format/send a com.compaq.svctools.desta.messages.services. ProblemReportMessage@800a504  G Current Thread[Thread-39: com.compaq.svctools.ca.services.notification.   IndictmentNotification ,5,main] + EXCEPTION java.lang.ClassNotFoundException:H" com.compaq.svctools.ccat.analyzer.4 CCATAnalysisReport_DefaultRole_Indictment_Formatter  B C at java.net.URLClassLoader$1.run (URLClassLoader.java:202) (pc 69) 0. at java.security.AccessController.doPrivilegedL (java.security.PrivilegedExceptionAction,java.security.AccessControlContext)  G at java.net.URLClassLoader.findClass (URLClassLoader.java:191) (pc 13) =< at java.lang.ClassLoader.loadClass(java.lang.String,boolean) (ClassLoader.java:300) (pc 42)  J at sun.misc.Launcher$AppClassLoader.loadClass (Launcher.java:285) (pc 36) K at java.lang.ClassLoader.loadClass(java.lang.String) (ClassLoader.java:257)e (pc 3) T at java.lang.Class.forName0 E at java.lang.Class.forName(java.lang.String) (Class.java:124) (pc 5) y3 at com.compaq.svctools.desta.services.notification.tB NotificationRole.getFormatter (NotificationRole.java:42) (pc 102) 3 at com.compaq.svctools.desta.services.notification.sK Notification.processMessage(com.compaq.svctools.desta.messages.DataMessage)   (Notification.java:143) (pc 81) : at com.compaq.svctools.desta.messages.DataMessage.handleMe (DataMessage.java:163) (pc 2) 3 at com.compaq.svctools.desta.services.notification._: Notification.handleMessage (Notification.java:68) (pc 83) 1 at com.compaq.svctools.desta.core.DESTAComponent.S7 startProcessingData (DESTAComponent.java:277) (pc 158)  4 at com.compaq.svctools.desta.core.DESTAComponent.run" (DESTAComponent.java:204) (pc 31) 2 at java.lang.Thread.run (Thread.java:479) (pc 11)   4 This message may be added to the Director's log fileK (/usr/opt/compaq/svctools/logs/desta_dir.log) for every CCAT problem reportTG generated. This only occurs if CCAT is installed on an AlphaServer GSxxrI running Tru64 UNIX version 5.1 or later. This message does not indicate at= problem with CCAT or the Director and can be safely ignored.        J =========================================================================    ***Glossary***     A    ACHS i  F Automatic Call Handling System. Within the service provider's customerG service center, ACHS accepts incoming event analysis messages that were  initiated by SICL. 0  	 analysis C  I The process of interpreting events from a binary event log and generatingCK problem reports that describe any problems and possible corrective actions._J There are two modes of analysis supported by Compaq Analyze, automatic and manual.   
 attribute   J A component of a service. Some attributes can be configured by the user to, modify how Compaq Analyze services operate.     Automated Call Handling Service   
 See ACHS.   
 automatic   I One of the analysis modes supported by Compaq Analyze. In automatic mode,eI Compaq Analyze monitors the binary system event log, analyzes events, andl- generates reports without user intervention.     B    binary event log =  K A log file containing system data saved in binary format. Binary error logs D are processed by Compaq Analyze and the results of this analysis are presented in problem reports.    Bit To Text   	 See BTT.     BTT   K Bit to Text. The process used to translate the events contained in a binaryo9 log file and produce text output. See also, translation. F   C    CCAT    E Compaq Crash Analysis Tool. CCAT is a remote operating system failure ( analysis tool and is a WEBES component.    CEH   D Common Event Header. The header format used for binary event logs onJ supported products. See the Compaq Analyze Release Notes for a list of the supported products.    CLI   J Command Line Interface. The Compaq Analyze interface that uses the commandI prompt to interact with the system. The CLI processes commands entered athI the command prompt and returns information and results as text, either tog5 the terminal window or to designated output file(s). n   Command Line Interface e  	 See CLI.     common attributes   K Standard configuration settings available for all Compaq Analyze services. o   Common Event Header   	 See CEH. a   Compaq Analyze r  F Compaq Analyze is a remote system event monitoring tool and is a WEBES component. .   Compaq Crash Analysis Tool e  
 See CCAT.    Compaq Remote Support Service   
 See CRSS.    CRSS    I Compaq Remote Support Service. CRSS is the next generation of SICL and is ? capable of operating effectively in a distributed environment. l   D    DeCOR   K The rules-based analysis engine used by DECevent, Compaq Analyze, and CCAT.cE Compaq Analyze uses DeCOR to apply rules to binary events and produce G analysis results. Different rules are supplied with DECevent and CCAT.     DESTA   D Distributed Enterprise Service Tools Architecture. DESTA is Compaq's8 high-availability system fault management architecture.    DHCP o  L Dynamic Host Configuration Protocol. DHCP is a protocol for automatic TCP/IPE configuration that provides dynamic and static address allocation and. management.   	 Director s  H The WEBES component responsible for managing a machine and communicating with other machines. t  2 Distributed Enterprise Service Tools Architecture    See DESTA. n   DSNLink   F Automatic notification tool that sends the results of analysis to your service provider.   $ Dynamic Host Configuration Protocol   
 See DHCP.    E    event   - System data written to the binary event log.     extended attributes   B Configuration settings unique to a single Compaq Analyze service.    F    field   E Component of a frame containing a label and its corresponding value. s   Field Replaceable Unit i  	 See FRU.     frame   L Part of an event consisting of one or more translated fields of information.   FRU   D Field Replaceable Unit. A hardware component installed on a system.    G    global attribute e  = An attribute that affects all the Compaq Analyze interfaces. o   group   H Multiple nodes associated in the navigation frame of the web interface.    H    HTML a  J Hypertext Markup Language. The tagging language used to format and display information on the web.    Hypertext Markup Language   
 See HTML.    I    instance file   I A file used by Compaq Analyze to store analysis data including, the pathsrG and filenames of the KRS files to be used for analysis, the input entrylG classes, the intermediate data such as complex storage classes, and thee analysis results.    J    Java n  < Platform-independent, object-oriented programming language.    K    Knowledge Rule Set    	 See KRS. r   KRS   J Knowledge Rule Set. Files that define what conditions must be met in orderA to trigger automatic analysis. Also known as rules or rule sets. s   L   	 log file a  G Either a binary file containing system events or a text file containingt= error and informational messages written by WEBES processes. n   M    manual s  J One of the modes of operation supported by Compaq Analyze. In manual mode,G the binary log files and events to be analyzed must be specified by then user.    N    node t  / A remote system accessed through its Director. e  
 notification    F Procedure for relaying analysis information to the interested parties.J Compaq Analyze supports automatic notification via e-mail, SICL, or CRSS.    P    problem report    J The output generated by analysis. Reports contain information about errors" and suggested corrective actions.    profile   L Configuration information that is associated with a log on name. The profileL contains information about Director settings and navigation frame appearance+ that can be propagated to future sessions. s   Q    QSAP    K Qualified Service Access Point. The QSAP acts as a gateway for CRSS managed + servers to connect with the outside world. a   Qualified Service Access Point    
 See QSAP.    R    RCM   K Revision and Configuration Management. RCM is a remote system configurationa tool and is a WEBES component. n  	 register 0  > The process of installing or activating a knowledge rule set.   & Revision and Configuration Management   	 See RCM. l   rule and rule set   	 See KRS. o   S    service   A A component responsible for providing a Compaq Analyze function.     service obligation s  D An agreement with Compaq for the use of the WEBES tools. The serviceD obligation defines the terms of your support agreement with Compaq.    SICL s  J System Initiated Call Logging. SICL refers to the concept of automaticallyE sending fault and failure messages to the service provider's customer.K service center. The messages are then received by ACHS, analyzed, and actedn upon as appropriate. .   Simple Mail Transfer Protocol   
 See SMTP.    SMTP c  I Simple Mail Transfer Protocol. SMTP is a TCP/IP protocol governing e-mailo transmission and reception.    String and Value Pairs a  	 See SVP.     SVP   K String and Value Pairs. The format used to present information in generatedsG reports. The string describes the type of information presented and theC1 value indicates the system specific information.     system configuration o  I The software settings for Compaq Analyze. The system configuration can beR% changed using any of the interfaces. v   System Initiated Call Logging   
 See SICL.    T    TCP/IP (  @ Transmission Control Protocol/Internet Protocol. TCP/IP providesI communication between computers across interconnected networks, even when K the computers have different hardware architectures and operating systems. a   translation   J The process of converting binary event logs into readable output. See also BTT. .  0 Transmission Control Protocol/Internet Protocol    See TCP/IP.    U   
 UniCensus    The Tru64 UNIX version of RCM. t   unregister p  > The process of removing or deactivating a knowledge rule set.    W    WBEM h  F Web-Based Enterprise Management. WBEM is distributed, web-based system management.    WCC   I WEBES Common Components. The WCC are the portions of WEBES that allow theaJ tool suite to function as an integrated installation. The WCC are separateL from the individual tools in the WEBES suite (Compaq Analyze, CCAT, and RCM)! and are transparent to the user. =    Web-Based Enterprise Management   
 See WBEM.    Web-Based Enterprise Service     See WEBES.     WEBES   G Web-Based Enterprise Service. WEBES is an integrated set of web-enabledrF service tools that include: Compaq Analyze, Compaq Crash Analysis ToolH (CCAT), and Revision Configuration Manager (RCM). See also DESTA, WBEM.    WEBES Common Components   	 See WCC. t   web interface   D The Compaq Analyze interface accessed through a web browser. The webH interface uses graphical displays to present information and relies on aG combination of mouse and keyboard actions to interact with the system.        J =========================================================================    ***Index***     F **********************************************************************F **                                                                  **F ** A NOTE ABOUT THE INDEX:                                          **F **                                                                  **F ** Because of different font spacing and layout, the page count and **F ** configuration of this text extract varies from the original      **F ** print version of the document. This process also prevents the    **F ** text extract from accurately mapping the page numbers shown in   **F ** the original index to the desired page in the text extract.      **F **                                                                  **F ** To find information in this text file, open the file in a text   **F ** editor and use a search command to find the desired word. (In    **F ** fact, this technique generally provides a more thorough series   **F ** of hits than the author's original index.)                       **F **                                                                  **F **********************************************************************      