


 **********************************************************************
 **                                                                  **
 ** TEXT FILE LIMITATIONS:                                           **
 **                                                                  **
 ** The text extract for this document does not capture tables very  **
 ** well, mainly because of the 75-column, monospaced character      **
 ** limitation. Be aware that large data tables probably will not    **
 ** wrap properly in this text file.                                 **
 **                                                                  **
 ** In addition, the text extract cannot capture figure images.      **
 ** You can see only placeholders (captions) for the figures.        **
 **                                                                  **
 ** You may see references to italic or bold fonts that are visible  **
 ** in the original document but not in this text extract.           **
 **                                                                  **
 **********************************************************************




      *** WEBES ***


      *** User Guide ***


      ***************************************************************************



      The WEBES User Guide provides information about the features of WEBES, 
      SEA, and CCAT and explains how to operate the software. 
      Web-Based Enterprise Services (WEBES) is a suite of applications developed 
      within HP for system diagnosis of computing platforms and on a variety of 
      connected equipment, such as storage arrays.
      System Event Analyzer (SEA) is a rules-based hardware fault management 
      diagnostic tool that provides error event analysis and translation. 
      Computer Crash Analysis Tool (CCAT) is a software application that enables 
      Hewlett-Packard customer service engineers and system administrators to 
      analyze operating system crashes. 
      To access the latest revision of this document containing updated 
      information, please visit the WEBES Web site: 
      http://www.hp.com/services/webes 
              Operating System: Microsoft(R) Windows 2000, Windows Server 2003 
              and Windows XP 
              HP-UX PA-RISC versions 11.11 or higher 
              HP-UX Integrity Server 11.23 or higher
              Red Hat Enterprise Linux Application Server 3.0 and 4.0
              Red Hat Enterprise Linux Enterprise Server 3.0 and 4.0
              HP OpenVMS Alpha versions 7.3-2, 8.2 or higher
              HP OpenVMS Integrity (Itanium) version 8.2-1 or higher 
              Software Version: WEBES Version 5.0 




      Copyright 2006 Hewlett-Packard Company 
      Microsoft, Windows, and Windows NT are US registered trademarks of 
      Microsoft Corporation. Intel is a US registered trademark of Intel 
      Corporation. UNIX is a registered trademark of The Open Group. Java is a 
      US trademark of Sun Microsystems, Inc. 
      Confidential computer software. Valid license from Hewlett-Packard 
      required for possession, use or copying. Consistent with FAR 12.211 and 
      12.212, Commercial Computer Software, Computer Software Documentation, and 
      Technical Data for Commercial Items are licensed to the U.S. Government 
      under vendor's standard commercial license. 
      Hewlett-Packard shall not be liable for technical or editorial errors or 
      omissions contained herein. The information is provided "as is" without 
      warranty of any kind and is subject to change without notice. The 
      warranties for Hewlett-Packard products are set forth in the express 
      limited warranty statements accompanying such products. Nothing herein 
      should be construed as constituting an additional warranty. 
      This service tool software is the property of, and contains confidential 
      technology of Hewlett-Packard Company or its affiliates. Possession and 
      use of this software is authorized only pursuant to the Proprietary 
      Service Tool Software License contained in the software or documentation 
      accompanying this software. 
      Hewlett-Packard service tool software, including associated documentation, 
      is the property of and contains confidential technology of Hewlett-Packard 
      Company or its affiliates. Service customer is hereby licensed to use the 
      software only for activities directly relating to the delivery of, and 
      only during the term of, the applicable services delivered by 
      Hewlett-Packard or its authorized service provider. Customer may not 
      modify or reverse engineer, remove or transfer the software or make the 
      software or any resultant diagnosis or system management data available to 
      other parties without Hewlett-Packard's or its authorized service 
      provider's consent. Upon termination of the services, customer will, at 
      Hewlett-Packard's or its service provider's option, destroy or return the 
      software and associated documentation in its possession. 
      Examples used throughout this document are fictitious. Any resemblance to 
      actual companies, persons, or events is purely coincidental. 
      The following table summarizes changes to this document: 
        +-----------------------------------------------------+

              Revision 
              ----------
              Description 
              ----------

              20-Dec-2006 
              Initial 4.5.1 copy 





        +-----------------------------------------------------+






      ===========================================================================


      *** Contents *** 
      Title Page 
      Copyright Statement 
      Change Summary 
      List of Figures 
      List of Tables 
      1  Introduction 
        1.1  What is SEA? 

        1.2  WEBES 

        1.3  Hardware Requirements 

        1.4   Operating Systems Requirements 

          1.4.1  Operating System Upgrades to Support Daylight Saving Time Rule 
          Changes 

        1.5  Supported Products 

          1.5.1  Automatic and Manual Analysis, and Bit-To-Text Translation 

          1.5.2  Manual Analysis and Bit-to-Text Translation (No Automatic 
          Analysis) 

          1.5.3  Bit-To-Text Translation only 

        1.6  This Manual 

          1.6.1  Intended Audience 

          1.6.2  Document Conventions 

          1.6.3  Nomenclature 

        1.7  Further Information 

      2  Getting Started 
        2.1  Installation 

        2.2  Account Permission Requirements 

          2.2.1  HP-UX and Linux Permissions 

          2.2.2  OpenVMS Privileges 

          2.2.3  Windows Permissions 

        2.3  Processes 

          2.3.1  The Director 

          2.3.2  The WCCProxy 

        2.4  Process Monitoring 

          2.4.1  Monitoring from the CLI 

          2.4.2  Monitoring from the Operating System 

            2.4.2.1  OpenVMS 

            2.4.2.2  Windows 

        2.5  Log Files 

          2.5.1  HP-UX 

          2.5.2  Linux 

          2.5.3  OpenVMS 

          2.5.4  Windows 

          2.5.5  Logging Level 

        2.6  Service Obligation 

        2.7  Managed Entities, Storage Cells, and EVAs 

          2.7.1  Managed Entities 

          2.7.2  Storage Cells are a Type of Managed Entity 

          2.7.3  EVAs are Types of Storage Cells 

        2.8  Automatic Notification 

        2.9  Command Line Interface 

        2.10  Web Interface 

      3  WEBES Director Processes and DESTA Commands 
        3.1  What is the Director? 

        3.2  SEA and the Director 

        3.3  How Directors Work Monitoring Multiple Systems 

        3.4  Interacting with the Director 

          3.4.1  Permissions 

          3.4.2  Clusters 

          3.4.3  DESTA 

        3.5  Troubleshooting an Unresponsive Director 

          3.5.1  Windows (Unresponsive Director) 

          3.5.2  HP-UX and Linux 

          3.5.3  OpenVMS 

        3.6  DESTA Command Overview 

        3.7  Starting the Director 

        3.8  Stopping the Director 

        3.9  Port Configuration 

        3.10  Automatic Notifications 

          3.10.1  ISEE Notification 

          3.10.2  SMTP Notification 

          3.10.3  OSEM Notification (formerly PRS CSG/QSAP) 

          3.10.4  SICL/ACHS/DSNlink Notification 

          3.10.5  SNMP Notification to HP SIM and OVO 

          3.10.6  DTCS Notification 

          3.10.7  Open VMS Mail Notification 

          3.10.8  WEBES Health Check Report 

            3.10.8.1  Scheduling Health Check Tasks Manually 

        3.11  Priority 

        3.12  Service Obligations 

        3.13   Managed Entities (Command View EVA server, EVA, WBEM Server) 
        Commands 

        3.14  Getting Help 

      4   WCCProxy Processes and WCCProxy Commands 
        4.1  What is the WCCProxy? 

        4.2  Interacting with the WCCProxy 

          4.2.1  Permissions 

          4.2.2  Clusters 

        4.3  WCCProxy Command Overview 

        4.4  Starting the WCCProxy 

        4.5  Stopping the WCCProxy 

        4.6  Killing the WCCProxy 

        4.7  Getting Help 

      5  SEA Command Line Interface 
        5.1  Overview 

          5.1.1  Permissions 

          5.1.2  Clusters 

          5.1.3  The CLI and the Director 

        5.2  Conventions 

        5.3  Command Syntax 

          5.3.1  Showing the Default Syntax 

          5.3.2  Changing the Default Syntax 

        5.4  Command Verbs 

        5.5  Command Parameters 

        5.6  Analysis 

          5.6.1  Automatic Analysis 

            5.6.1.1  Viewing Automatic Analysis Reports 

            5.6.1.2  Logging Automatic Analysis Reports 

            5.6.1.3  Simulating Automatic Analysis 

            5.6.1.4  Resetting Automatic Analysis Results 

            5.6.1.5  Disabling and Enabling Automatic Analysis 

          5.6.2  Manual Analysis 

        5.7  Translation 

        5.8  Summary of Events 

        5.9  Creating New Binary Event Log Files 

        5.10  Modifying Commands 

          5.10.1  Input Files 

          5.10.2  Output Files 

          5.10.3  Filtering 

        5.11  Knowledge Rule Sets 

        5.12  Status Information 

        5.13  Getting Help 

      6  WBEM Command Line Interface (CLI) 
        6.1  Introduction 

        6.2  WBEM CLI 

      7  Web Interface 
        7.1  About the Web Interface 

          7.1.1  About Translation 

          7.1.2  About Analysis 

            7.1.2.1  Automatic Analysis 

            7.1.2.2  Manual Analysis 

          7.1.3  Automatic Notifications 

          7.1.4  Create New Binary Log File 

        7.2  Starting the Web Interface 

        7.3  Using The Web Interface 

          7.3.1  Toolbar 

          7.3.2  Navigation 

            7.3.2.1  Navigation Tree Hierarchy 

            7.3.2.2  Features of the Navigation Tree 

        7.4  Customizing the Navigation Tree 

          7.4.1  Groups 

            7.4.1.1  Adding Groups 

            7.4.1.2  Removing Groups 

          7.4.2  Nodes 

            7.4.2.1  Adding Nodes 

            7.4.2.2  Removing Nodes 

            7.4.2.3  Activating Nodes 

          7.4.3  Categories 

            7.4.3.1  Adding Categories 

            7.4.3.2  Removing Categories 

          7.4.4  Log Files 

            7.4.4.1  System Log 

            7.4.4.2  Other Logs 

        7.5  Processing Log Files 

          7.5.1  Additional Toolbar Functions 

          7.5.2   Processing Status 

            7.5.2.1  Navigation Tree 

            7.5.2.2  Progress Window 

          7.5.3  Working With Results 

            7.5.3.1  Problem Reports 

            7.5.3.2  Summary 

            7.5.3.3  Sub Type Tallied Summaries and Event Listings 

            7.5.3.4  Events 

            7.5.3.5  Sorting Results 

            7.5.3.6  Displaying Details 

        7.6  Creating New Log Files 

        7.7  Creating Storage Cell Spreadsheets 

        7.8  Applying Filters 

        7.9  Modifying Settings 

          7.9.1  User Settings 

            7.9.1.1  General Options 

            7.9.1.2  Filters 

            7.9.1.3  Event Columns 

          7.9.2  Director Settings 

        7.10  Getting Help 

          7.10.1  Usage Tips 

          7.10.2  On-Line User Guide 

        7.11  Logging Off 

        7.12  Service Obligation 

        7.13  Managed Entities 

      8  Translation, Analysis, and Summary 
        8.1  Translation, Analysis and Rules 

        8.2  Manual Translation 

          8.2.1  Translating Events 

          8.2.2  Translation Defaults 

          8.2.3  Translation Report Type 

          8.2.4  Interpreting Translation Information 

            8.2.4.1  Overall 

            8.2.4.2  Frame 

            8.2.4.3  Field 

            8.2.4.4  Typical Frame of a Translated Binary Event 

            8.2.4.5  Unsupported Entries 

        8.3  Automatic Analysis 

          8.3.1  Scavenge 

          8.3.2  Reset 

          8.3.3  Disable 

        8.4  Manual Analysis 

          8.4.1  Resource Usage During Analysis 

        8.5  Interpreting Analysis Information 

          8.5.1  Problem Report Times 

          8.5.2  Managed Entity 

          8.5.3  Service Obligation 

          8.5.4  Brief Description 

          8.5.5  Callout ID 

          8.5.6  Severity 

          8.5.7  Reporting Node 

          8.5.8  Full Description 

          8.5.9  FRU List 

          8.5.10  Evidence 

          8.5.11  Versions 

        8.6  Interpreting Time Stamps 

        8.7  Simulation of Automatic Analysis 

          8.7.1  Bypassing The System Error Log 

        8.8  Interpreting Summary Information 

      9  Rule Sets 
        9.1  Rule Sets 

        9.2  Analysis Data 

        9.3  Managing Rule Sets 

          9.3.1  Viewing Registered Rules 

            9.3.1.1  CLI 

            9.3.1.2  Web Interface 

          9.3.2  Registering and Unregistering Rule Sets 

            9.3.2.1  CLI 

            9.3.2.2  Web Interface 

      10  Configuration 
        10.1  Viewing the Configuration 

        10.2  Component Configuration Attributes 

        10.3  Changing the Configuration 

          10.3.1  CLI 

          10.3.2  Web Interface 

        10.4  Global Configuration Attributes 

          10.4.1  Changing the Attributes 

          10.4.2  Changing Ports 

        10.5  Profiles 

        10.6  Creating and Resetting the Configuration 

        10.7  Editing the Desta Registry 

          10.7.1  Configuring the Message Wait Timeout 

          10.7.2  Configuring Additional Log File Directories 

          10.7.3  Enabling Text Entry in Other Logs Pane 

          10.7.4  Controlling Memory Usage 

            10.7.4.1  Circumstances Requiring Memory Changes 

            10.7.4.2  Changing Memory Settings 

        10.8  Configuring Operating System-Specific Services 

          10.8.1  Indictment 

            10.8.1.1  OpenVMS 

      11  Automatic Notifications 
        11.1  When Are Notifications Sent? 

        11.2  Service Events vs. Info Events 

          11.2.1  Service Events 

          11.2.2  Informational Events 

        11.3  Sending Notifications to Email Addresses 

          11.3.1  Settings 

          11.3.2  Disabling Email Notifications 

          11.3.3  Re-enabling Email Notifications 

          11.3.4  Firewall Telnet Checking May Inhibit SMTP Email 

          11.3.5  Open VMS Mail Notification 

        11.4  Sending Notifications to HP Services 

          11.4.1  System Initiated Call Logging 

          11.4.2  Proactive Remote Service 

          11.4.3  Instant Support Enterprise Edition 

        11.5   Sending Notifications to Other Monitoring Tools 

          11.5.1  Open Service Event Manager 

          11.5.2  Simple Network Management Protocol (SNMP) Notifications to HP 
          SIM or OVO 

            11.5.2.1  Unknown Host Exception in Director Log When Manually 
            Analyzing Files with Notifications 

          11.5.3  Disaster Tolerant Computing Service (DTCS) 

          11.5.4  Microsoft Object Manager (MOM) 

        11.6  The Customer Profile File 

          11.6.1  Number of Profile Files 

          11.6.2  Location of the Profile File 

          11.6.3  Calling the Profile File 

          11.6.4  Profile File Content 

            11.6.4.1  Sample Profile 1--Simple 

            11.6.4.2  Sample Profile 2--MSCS Cluster 

            11.6.4.3  Sample Profile 3--MSCS Cluster with DRM 

          11.6.5  How the Profile File Works 

      12  Computer Crash Analysis Tool 
        12.1  Introduction 

        12.2  Gathering Crash Data 

          12.2.1  Windows 

          12.2.2  OpenVMS 

        12.3  CCAT Functionality 

        12.4  Security and Required Permissions 

          12.4.1  Windows 

          12.4.2  OpenVMS 

        12.5  Intended Audience 

        12.6  Further Information 

        12.7  Running CCAT Automatically 

        12.8  Automatic Mode Process 

        12.9  Configuring CCAT To Run Automatically 

        12.10  Using the CCAT GUI 

        12.11  Verifying the WEBES Director 

          12.11.1  Windows 

          12.11.2  OpenVMS 

        12.12  Starting the GUI 

        12.13  CCAT GUI 

        12.14  Performing a Manual Crash Analysis 

          12.14.1  Crash Data Parameters 

          12.14.2  Entering Parameters 

            12.14.2.1  Selecting And Opening a Crash File 

            12.14.2.2  Typing In Crash Parameters 

          12.14.3  Saving the Results File 

        12.15  Viewing Saved Results Files 

        12.16  Exiting From the CCAT GUI 

      A  Sample Outputs 
        A.1  Sample Analysis Output 

        A.2  Sample Translated Event Output 

          A.2.1  Full 

          A.2.2  Brief 

        A.3  Sample Configuration Entry 

      B  Performance 
        B.1  Performance and Resource Usage 

        B.2  Performance Issues 

        B.3  Enhancing Performance 

          B.3.1  OpenVMS 

      C  Browsers And The Web Interface 
        C.1  Supported Web Browsers 

        C.2  Browser Setup 

        C.3  Browser Usage 

        C.4  Browser Specific Limitations 

          C.4.1  Internet Explorer 

          C.4.2  Netscape Communicator 

          C.4.3  Mozilla and Netscape 7 

      D  Known Messages in SEA 
        D.1  Return Codes 

        D.2  Configuration File Created 

        D.3  Files Not Found 

        D.4  Tracker Message 

      E  Other CLI Syntaxes 
        E.1  Using Other Syntaxes 

        E.2  Conventions 

        E.3  Old Common Syntax 

          E.3.1  Manual Analysis 

          E.3.2  Translation 

          E.3.3  Summary of Events 

          E.3.4  Creating New Binary Event Log Files 

          E.3.5  Modifying Commands 

            E.3.5.1  Input Files 

            E.3.5.2  Output Files 

            E.3.5.3  Filtering 

          E.3.6  Knowledge Rule Sets 

        E.4  DECevent UNIX Syntax 

          E.4.1  Manual Analysis 

          E.4.2  Translation 

          E.4.3  Summary of Events 

          E.4.4  Creating New Binary Event Log Files 

          E.4.5  Modifying Commands 

            E.4.5.1  Input Files 

            E.4.5.2  Output Files 

            E.4.5.3  Filtering 

        E.5  DECevent OpenVMS Syntax 

          E.5.1  Manual Analysis 

          E.5.2  Translation 

          E.5.3  Summary of Events 

          E.5.4  Creating New Binary Event Log Files 

          E.5.5  Modifying Commands 

            E.5.5.1  Input Files 

            E.5.5.2  Output Files 

            E.5.5.3  Filtering 

      Glossary 


           ===========================================================================


      *** List of Figures *** 
        3-1  Interaction Between Two Systems Running SEA 

        7-1  Logon Window 

        7-2  Main Screen 

        7-3  Toolbar 

        7-4  Navigation Tree - Hierarchy 

        7-5  Navigation Tree - Collapsed 

        7-6  Navigation Tree - Expanded 

        7-7  Add Group 

        7-8  Remove Group 

        7-9  Add Node 

        7-10  Remove Node 

        7-11  Activating Node 

        7-12  Activating Node Message 

        7-13  Unable to Activate Node Message 

        7-14  Add Category 

        7-15  Remove Category 

        7-16  Add Log Files Tab 

        7-17  Remove Log File Tab 

        7-18  Analysis Failed Message 

        7-19  Additional Toolbar Functions 

        7-20  Status Icons 

        7-21  Progress Window 

        7-22  Additional Entries Navigation 

        7-23  Problem Report Tab 

        7-24  Summary Tab 

        7-25  Summary of Sub-Types 

        7-26  Sub-Type Listing 

        7-27  Events Tab 

        7-28  Navigation Buttons--Problem Reports 

        7-29  Navigation Buttons--Events 

        7-30  New Binary Log Screen 

        7-31  Storage Cell Icon 

        7-32  Storage Cell Icon in WUI 

        7-33  Filter Templates Bar 

        7-34  Filter Description 

        7-35  User Settings 

        7-36  Filter Preferences 

        7-37  Adjust Filter 

        7-38  Filtering Criteria 

        7-39  Filtering Operators 

        7-40  Applied Filter 

        7-41  Event Columns 

        7-42  Director Settings 

        7-43  Lost Connection Message 

        7-44  Managed Entities 

        7-45  Managed Entity Detail 

        7-46  Managed Entities - No Entities 

        9-1  Rules Files 

        10-1  Settings 

        10-2  Attribute Display 

        10-3  Add Log Files Tab with Text Entry Field Enabled 

        10-4  Text Entry Field 

        12-1  Computer Crash Analysis Tool Window 

        12-2  CCAT Analysis Results 

        12-3  Typical CCAT Analysis Results 

        12-4  Exit CCAT Information Window 



            ===========================================================================


      *** List of Tables *** 
        0-1  Supported Products 

        2-1  Director Status Codes 

        2-2  WCCProxy Status Codes 

        3-1  Command Verbs--desta 

        4-1  Command Verbs--wccproxy 

        5-1  wsea Syntax Designators 

        5-2  Command Verbs--wsea (New Common Syntax) 

        5-3  Command Verbs--wsea (Syntax Independent) 

        5-4  Filtering Statements (New Common Syntax) 

        5-5  Event Type Keywords (New Common Syntax) 

        7-1  Web Interface Components 

        7-2  Toolbar--Default Buttons 

        7-3  Toolbar--Dynamic Buttons 

        7-4  Navigation Tree - Hierarchy 

        7-5  Navigation Tree - Features 

        7-6  User Settings Navigation 

        7-7  General User Settings Options 

        7-8  Director Settings Navigation 

        8-1  Problem Severity Levels 

        10-1  Ports 

        12-1  Windows Crash Data Parameters 

        12-2  Open VMS Alpha Crash Data Parameters 

        C-1  SEA Browser Requirements--Non UNIX 

        C-2  SEA Browser Requirements--UNIX Variants 

        E-1  Syntax Conventions 

        E-2  Command Verbs--wsea (Old Common Syntax) 

        E-3  Filtering Statements (Old Common Syntax) 

        E-4  Event Type Keywords (Old Common Syntax) 

        E-5  Command Verbs--wsea (DECevent UNIX syntax) 

        E-6  Filtering Statements (DECevent UNIX syntax) 

        E-7  Event Type Keywords (DECevent UNIX syntax) 

        E-8  Command Verbs--wsea (DECevent OpenVMS syntax) 

        E-9  Filtering Statements (DECevent OpenVMS syntax) 

        E-10  Event Type Keywords (DECevent OpenVMS syntax) 



            ===========================================================================

      1 
      *** Introduction *** 
      This chapter provides an overview of SEA and this manual. 
        What is SEA?
        WEBES
        Hardware Requirements
        Operating Systems Requirements
        Supported Products
        This Manual
        Further Information
      1.1 What is SEA? 
      SEA is a fault analysis utility designed to provide analysis for single 
      error/fault events, as well as multiple events and complex analysis. In 
      addition to the traditional binary error log, SEA provides system analysis 
      capabilities that use other error/fault data sources. 
      SEA provides background automatic analysis by monitoring the active binary 
      error log and processing events as they occur. The events in the binary 
      error log file are checked against the analysis rules, and if one or more 
      of the events in the binary error log file meets the conditions specified 
      in the rules, the analysis engine collects the error data and creates a 
      problem report containing a description of the problem and any corrective 
      actions required. Once the problem report is created, it is distributed in 
      accordance with the customer's notification preferences. 
      SEA supplies a web-based user interface that connects to a continuously 
      running process called the Director, and can perform a variety of tasks 
      from a remotely connected web browser. In addition, a set of command line 
      interface (CLI) tools enable diagnosis of binary event logs without 
      connecting to the Director. 
      1.2 WEBES 
      HP has implemented a common application programming interface (API) for 
      many of its service tools called Web-Based Enterprise Services (WEBES). 
      The tools included in the current WEBES release are: 
        System Event Analyzer (SEA) 
        Computer Crash Analysis Tool (CCAT)
      SEA uses the common components of WEBES and adds its own functionality. 
      The other WEBES service tools can be installed along with SEA and use the 
      same common components. 
      1.3 Hardware Requirements 
      WEBES can be installed on the following hardware platforms. Do not confuse 
      the supported hardware with the products that SEA can analyze, listed in 
      the WEBES Release Notes. 
        32-bit Intel(R) based systems manufactured by HP, such as the ProLiant 
        or the HP OpenView Storage Management Appliance 
        Note that WEBES usually will operate on any industry standard, 32-bit 
        Intel-based system. However, because HP does not qualify WEBES on 
        third-party products, functionality on such systems is provided on an 
        as-is basis only.
        HP Integrity systems, built on the 64-bit Intel Itanium platform
        Note that WEBES may operate on other non-HP Itanium-based systems. 
        However, because HP does not qualify WEBES on third-party products, 
        functionality on such systems is provided on an as-is basis only.
        HP AlphaServer systems 
        HP 9000 series systems 
        *** Note ***


          HP ProLiant systems based on the x64 architecture, which includes both 
          the 64-bit Intel(R) EM64T-based Xeon systems as well as the AMD 
          systems based on the AMD64 Opteron, Athlon, and Turion 64-bit 
chipsets.
          Note that WEBES usually will operate on any industry standard x64 
          system. However, because HP does not qualify WEBES on third-party 
          products, functionality on such systems is provided on an as-is basis 
          only.



      See the WEBES Release Notes (section General WEBES Issues) for related 
      error messages if you install WEBES on non-supported platforms. 
      See the specific operating system chapters for more information about 
      platforms. See the next section "Operating Systems Requirements" for the 
      operating systems that WEBES can be installed upon. Although WEBES can be 
      installed on any of these hardware and operating system combinations, SEA 
      only supports event bit-to-text translation and event analysis on a 
      certain set of HP products. 
      See Section  1.5 "Supported Products" for the list of products that SEA 
      supports. 
      1.4 Operating Systems Requirements 
      WEBES supports systems running the following operating systems: 
        Microsoft(R) Windows
          Windows 2000 (any edition except Datacenter Server)
          Windows Server 2003, with either Service Pack 1 or R2
            32 bit: Web Edition, Standard Edition and Enterprise Edition
            Standard x64 Edition and Enterprise x64 Editions
            Enterprise Edition and Datacenter Edition for 64 bit Itanium based 
            Systems
          Windows Storage Server 2003
          Windows XP Professional
            32 bit Edition
            x64 Edition
        HP OpenVMS Itanium (Integrity) versions 8.2-1 or higher
        HP OpenVMS Alpha versions 7.3-2, 8.2 or higher
        WEBES 4.5 and above require ODS-5 supported disk when installed on VMS
        *** Note ***


          WEBES v4.5 and above will require an ODS-5 disk to install itself 
          onto, regardless of the version of VMS you are running on, regardless 
          of Itanium or Alpha. VMS has several types of hard drive formats, 
          ODS-2 (the old standard) and a newer type ODS-5 that supports more 
          complex filenames (and other features). Because WEBES v4.5.1and above 
          include and use the Java Runtime Environment version 1.5, and the JRE 
          requires ODS-5 to run, WEBES v4.5.1and above requires ODS-5.

          You can install and run WEBES on HP-UX and Linux, but currently it 
          does not analyze native error logs for events occurring on those 
          platforms. 

          You can, however, copy an error log from another system (Windows or 
          OpenVMS) to an HP-UX or Linux system for manual analysis there. 



        HP-UX PA-RISC version 11.11 or higher 
        HP-UX Integrity Server version 11.23
        Red Hat Enterprise Linux Application Server 3.0 and 4.0
        Red Hat Enterprise Linux Enterprise Server 3.0 and 4.0
      See the previous section Hardware Requirements for the types of hardware 
      that WEBES can be installed upon. Although WEBES can be installed on any 
      of these hardware and operating system combinations, SEA only supports 
      event bit-to-text translation and event analysis on a certain set of HP 
      product. 
      This version of WEBES is NOT supported on the following versions of 
      Windows: 
        Windows XP Professional 64 bit Itanium Edition
        Although WEBES is not yet supported on this operating system, the 
        Itanium kit may install and operate correctly but the Pentium kit can 
        not be installed.
        Windows Vista, 32-bit Beta Edition (formerly known as "Longhorn")
      See the section Supported Products and WEBES Release Notes for the list of 
      products that SEA supports. 
        1.4.1 Operating System Upgrades to Support Daylight Saving Time Rule 
        Changes
      Although WEBES v4.5.1 includes the latest Java updates available at the 
      time of its release to support the new rules defined for changes to 
      Daylight Saving Time definitions in various countries that go into effect 
      in 2007, certain operating system patches are also required to fully 
      implement the changes. 
      Refer to the following HP Web page for details: 
      http://h10072.www1.hp.com/dst 
      You can find the same Web page by going to: 
      http://search.hp.com 
      Enter the search phrase "Daylight Saving Time" (not Savings but Saving). 
      1.5 Supported Products 
      Although WEBES can be installed on any of the hardware and operating 
      system combinations shown in Chapter 1, SEA only supports event 
      bit-to-text translation and event analysis on the following set of HP 
      products. The list grows with each subsequent SEA release.The following 
      list includes the products SEA supports. 
      This list also is available in the WEBES Release Notes. In the event of 
      any discrepancy between this list and the WEBES Release Notes, the release 
      notes take precedence. 
      *** Note ***


        Do not confuse the supported products with the systems where WEBES can 
        be installed as explained in the Chapter1 "Introduction".



        WEBES 4.5 includes support for HP-UX 11-23 WBEM notifications on all 
        Itanium servers.
        1.5.1 Automatic and Manual Analysis, and Bit-To-Text Translation
        +-----------------------------------------------------+

              Type
              ----------
              Device
              ----------
              Operating System
              ----------

              HP Integrity Servers 
              rx3600
              Windows 2003 Server Enterprise Edition and OpenVMS 8.3


              rx6600 


              rx7620


              rx7640


              rx8620


              rx8640

              Integrity Superdome
              SD16A
              Windows 2003 Server Enterprise Edition and OpenVMS 8.3


              SD32A


              SD64A


              SD32B


              SD64B

              HP AlphaServer
              DS10/DS10L/DS15/DS20/DS20E/DS25
              OpenVMS


              ES40/ES45


              GS80/GS160/GS320


              TS80/ES47/ES80/GS1280/GS1280 M64


              TS20/TS40


              TS202C

              I/O Devices




              Disk Storage based on SCSI specification (OpenVMS and Windows) 
              OpenVMS and Windows


              EZ4X/EZ6X
              OpenVMS


              EZ5X/EZ7X 
              OpenVMS


              HSG60/HSG80
              Windows


              KGPSA-CA/KGPSA-BC/KGPSA-BY/KGPSA-CB/KGPSA-CX/KGPSA-CY 
              FCA2384/FCA2354/FCA2404/FCA2406



              Smart Array 5304 Controller (OpenVMS)
              OpenVMS


              Modular SAN Array 1000 (OpenVMS)
              OpenVMS


              EMA16000, MA8000/EMA12000, MA6000, RA8000/ESA12000


              Storage Systems




              Supports HP Storage Works EVA4000, EVA6000 and EVA8000 products 
              with XCS v6.100 and older



              Supports HP Storage Works EVA3000 and EVA5000 products with VCS 
              v4.007 and/or v3.110 and older



              Supports HP Storage Works Command View EVA v7.0.0 and older. EVA 
              CV v7 made a change to the logs that are stored into the NT 
              application log. The change is a major improvement that allows 
              WEBES to report more information in a callout report. This also 
              requires WEBES v5 to be installed whenever EVA CV v7 is installed. 
              Older versions of WEBES will not support EVA CV v7.


              Storage System Components



              StorageWorks SAN 1 Gbps Switches: 
              DSGGA-AA 8 port, StorageWorks Fibre Channel switch 
              DSGGA-AB 16 port, StorageWorks Fibre Channel switch 
              DSGGB-AA 8 port, StorageWorks SAN switch 8 
              DSGGB-AB 16 port, StorageWorks SAN switch 16 
              DSGGC-AA 8 port, SAN Switch 8-EL 
              DSGGC-AB 16 port, SAN Switch 16-EL 
              DSGGS SAN Switch Integrated /32 and /64 ports 


              StorageWorks SAN 2 Gbps Switches: 
              DS-DSGGD-AA 16 port, SAN Switch 2/16 
              DS-DSGGD-AB 32 port, SAN Switch 2/32 
              DS-DSGGD-AC 8 port, SAN Switch 2/8-EL 
              DS-DSSGD-AD 16 port, SAN Switch 2/16-EL 
              DS-DSGGD-BB 32 port, SAN Switch 2/32 
              DS-DSGGD-DB 32 port, SAN Switch 2/32 
              DS-DSGGE-xx 64 port, Core Switch 2/64






        +-----------------------------------------------------+




        1.5.2 Manual Analysis and Bit-to-Text Translation (No Automatic 
Analysis)
        Table 0-1 Supported Products
        +-----------------------------------------------------+

              Type
              ----------
              Device
              ----------
              Operating System
              ----------

              HP Integrity Servers 
              rx1600
              Windows Server 2003 Enterprise Edition and OpenVMS v8.2 and later


              rx1620


              rx2600


              rx2620


              rx4640


              rx5670
              Windows Server 2003 Enterprise Edition only


              zx6000


              zx2000





        +-----------------------------------------------------+




        1.5.3 Bit-To-Text Translation only
        +-----------------------------------------------------+

              Type
              ----------
              Device
              ----------
              Operating System
              ----------

              HP AlphaServer 
              DS20L (OpenVMS) 

              OpenVMS

              I/O Devices




              RA3000



              KZPSC/KZPAC/KZPBA/KZPCM/KZPSA/KZPCC/KSPEA



              KGPSA-CA/KGPSA-BC/KGPSA-BY/KGPSA-CB/KGPSA-CX/KGPSA-CY



              FCA2384/FCA2354/FCA2404/FCA2406 
              OpenVMS


              CCMAB-AA



              CIPCA-BA






        +-----------------------------------------------------+




      1.6 This Manual 
      The System Event Analyzer User Guide describes the features of SEA and 
      explains how to use the application: 
              Chapter 1 Introduces SEA and this manual 
              Chapter 2 Explains the basics behind running SEA, including 
              permissions, processes, and log files, as well as pointers to 
              additional details 
              Chapter 3 Describes how to interact with the WEBES Director and 
              the DESTA CLI command 
              Chapter 4 Describes how to interact with the WCCProxy and the 
              WCCPROXY CLI command 
              Chapter 5 Provides details about the WSEA CLI command 
              Chapter 6 Provides details about the WBEM CLI command 
              Chapter 7 Provides detailed information about the web interface 
              Chapter 8 Describes the translation of system events and the 
              analysis of error logs 
              Chapter 9 Explains the analysis rules used by SEA 
              Chapter 10 Discusses the SEA configuration settings 
              Chapter 11 Describes how to configure automatic notification 
              Chapter 12 Introduces CCAT 
              Appendix  Shows sample output files 
              Appendix B Contains information about optimizing the performance 
              of SEA 
              Appendix C Details how to configure and use your browser with the 
              web interface 
              Appendix D Describes SEA messages 
              Appendix E Explains the CLI old common syntax, DECevent UNIX 
              syntax, and DECevent VMS syntax 




      See Also 
         1.6.1 Intended Audience 
         1.6.2 Document Conventions 
         1.6.3 Nomenclature 
        1.6.1 Intended Audience 
      The System Event Analyzer User Guide is intended for system managers and 
      service personnel who run the SEA software to analyze and diagnose events 
      occurring on the products shown in the Supported Products list. 
        1.6.2 Document Conventions 
      This manual uses the following conventions: 
              Bold Used for entries, commands, and GUI tasks where information 
              is typed at the keyboard as it appears in the document 
              Italics Used for information that will vary depending on your 
              system and user profile 
              Fixed-width font Used to recreate the input and output of a 
              terminal session such as when using the CLI 
              CAPITALIZATION Used for special keyboard characters such as the 
              CTRL key 




        1.6.3 Nomenclature 
      There are certain terms that are applied somewhat interchangeably 
      throughout WEBES, so you need to become aware of some subtle differences 
      in meaning. 
      "Configuration" 
        Hardware configuration refers to the field replaceable units (FRUs) or 
        hardware components currently installed in a system. 
        System configuration refers to the current software settings of the SEA 
        system and each of the services it contains. Most of the settings can be 
        changed using the SEA interfaces. 
      "Log file" 
        On Windows, there are at least 3 binary event logs: Application, System, 
        and Security log. As of this release on Windows, the Application log 
        (AppEvent.evt) is the only log processed by SEA. However, in this and 
        other WEBES documents, it is stated that the system event log is read or 
        written by SEA. This is intended to mean generically "the binary event 
        log on the system that SEA processes" on all platforms. On Windows, this 
        should not be confused with the System Event Log (SysEvent.evt), which 
        is never accessed, read or written by SEA.
      "Supported" 
        WEBES can be installed and run on certain operating systems, and is 
        often said to "support" the operating systems even when SEA may not 
        analyze events on those operating systems. See Section 1.4. 
        For informational and troubleshooting purposes, the release notes may 
        specify the exact platforms used for WEBES testing. Despite that, you 
        always can install and run SEA on supported hardware and operating 
        systems even when a particular one was not formally included in the test 
        environment. 
        There is a defined list of supported products that SEA can analyze, 
        regardless of where SEA may be installed. See Section 1.5. 
      1.7 Further Information 
      See the following sources of additional information about SEA: 
        WEBES Release Notes 
        WEBES Installation Guide 
      Kits, updates, documentation for WEBES are available at the following URL: 

      http://www.hp.com/services/webes



            ===========================================================================

      2 
      *** Getting Started *** 
      This chapter describes the permissions, processes, and log files used by 
      SEA. Some key features of SEA are briefly described, and pointers to 
      detailed information are provided. 
        Installation
        Account Permission Requirements
        Processes
        Process Monitoring
        Log Files
        Service Obligation
        Managed Entities, Storage Cells, and EVAs
        Automatic Notification
        Command Line Interface
        Web Interface
      2.1 Installation 
      Always install SEA as part of the process of installing the WEBES suite of 
      tools, even if SEA is the only tool that you choose to install at the 
      time. There is no standalone kit for installing only SEA, and SEA depends 
      on WEBES common components for proper operation. 
      See the WEBES Installation Guide for complete installation requirements 
      and instructions. 
      2.2 Account Permission Requirements 
      For enhanced security, only privileged users of each operating system can 
      access the WEBES directory tree or run commands. 
         2.2.1 HP-UX and Linux Permissions 
         2.2.2 OpenVMS Privileges 
         2.2.3 Windows Permissions 
        2.2.1 HP-UX and Linux Permissions 
      The following actions are restricted to privileged users: 
        Running any WEBES or SEA commands (desta, wccproxy, or wsea commands 
        from the command prompt). 
        Viewing the WEBES directory tree on a system. 
      Only the root user can perform these actions. The /opt/hp/svctools 
      directory is owned by root, and has rwx (read, write, and execute) 
      permissions for root (owner), and no permissions for any other user (group 
      or world). 
        2.2.2 OpenVMS Privileges 
      Commands--To execute any SEA commands (DESTA or WSEA commands), the user 
      needs all of the following OpenVMS privileges. Note that these are a 
      subset of the privileges required to install, upgrade, or uninstall WEBES 
      as described in the WEBES Installation Guide: 
              ALTPRI 
              BUGCHK 
              CMKRNL DIAGNOSE 
              IMPERSONATE 
              NETMBX SYSPRV 
              TMPMBX 




      Files--File access is restricted in the WEBES installed directory tree 
      pointed to by the SVCTOOLS_HOME logical (SYS$COMMON:[HP] by default). To 
      view these files, you must be a member of the System group, your user ID 
      must have all privileges, or you must issue the SET PROCESS /PRIV=ALL 
      command. 
      All directories and files in the SVCTOOLS_HOME tree are owned by the 
      System user, and have System, Owner, and Group permissions of RWED (read, 
      write, execute, and delete). There are no permissions for World. 
        2.2.3 Windows Permissions 
      The following actions are restricted to privileged users: 
        Running any of the WEBES programs from the Start menu (Start | Programs 
        | Hewlett-Packard Service Tools).
        Running any WEBES or SEA commands (desta, wccproxy, or wsea commands 
        from the command prompt). 
        Accessing any files within the WEBES directory tree, C:\Program 
        Files\hp\svctools by default. 
      To perform restricted actions, your user ID must be at least one of the 
      following: 
        A member of the Administrators group on that system. 
        A member of another group that is a member of the Administrators group 
        on that system. 
        For example, if your user ID is a member of the Domain Admin group, and 
        you add Domain Admins to the Administrators group on the local system, 
        you will have the necessary permissions. See your Windows documentation 
        if you need help with configuring groups. 
      2.3 Processes 
      There are WEBES processes that must run all the time and are essential to 
      SEA operation: the Director and the WCCProxy. 
         2.3.1 The Director 
         2.3.2 The WCCProxy 
        2.3.1 The Director 
      The Director is a required WEBES process (or set of processes) that runs 
      continuously. The Director manages a system on behalf of WEBES, and 
      executes functionality added to it by individual WEBES tools. For example, 
      SEA provides the Director with the ability to capture and interpret 
      hardware events, either automatically or at the request of an outside 
      process. 
      The Director automatically starts along with the system and normally does 
      not require additional user interaction. Some operations may require that 
      you stop and restart it, however (see Sections 3.8 and 3.7). 
      See Chapter 3 for more information about the Director. 
        2.3.2 The WCCProxy 
      The WCCProxy is a daemon process that runs all the time, like the 
      Director. After WEBES installation, the WCCProxy appears as a separately 
      installed kit and represents WEBES functionality not developed in the 
      Java(TM) environment. The WCCProxy contains required functions that allow 
      WEBES to interact with the operating system, other WEBES agent processes, 
      and the Director. 
      The WCCProxy also is packaged with the ISEE Client kit and is necessary 
      for sending of notifications through ISEE. 
      The WCCProxy automatically starts along with the system and normally does 
      not require additional user interaction. See Chapter 4 for more 
      information about the WCCProxy. 
      2.4 Process Monitoring 
      You can monitor WEBES processes from the CLI or by using built-in 
      operating system utilities. 
         2.4.1 Monitoring from the CLI 
         2.4.2 Monitoring from the Operating System 
        2.4.1 Monitoring from the CLI 
      Director--Monitor the Director process with the following command (see 
      Table 2-1): 
      desta status 

        Table 2-1 Director Status Codes 
        +-----------------------------------------------------+

              Code 
              ----------
              Description 
              ----------

              1 
              The Director is not running. 

              3 
              The Director is running. 

              5 
              The Director is starting up. 

              7 
              The Director is shutting down. 

              9 
              The Director's status file indicates it is running, but the 
              process ID was not found, so the Director process in fact is not 
              running and has terminated abnormally. 

              99 
              The Director's status could not be determined. 





        +-----------------------------------------------------+




      WCCProxy--Monitor the WCCProxy using the following command (see Table 
      2-2): 
      wccproxy status 

        Table 2-2 WCCProxy Status Codes 
        +-----------------------------------------------------+

              Code 1 
              ----------
              Description 
              ----------

              0 or 4 
              The WCCProxy status could not be determined. 

              1 
              The WCCProxy is running. 

              2 
              The WCCProxy is not running. 

              3 
              The WCCProxy service is not installed. 



               1  In WEBES 4.3.2, the values apply only to Windows. The values 
              will be changed in a future release to values more like the desta 
              status values shown in Table 2-1. 

              On all UNIX platforms, the return code is always zero. This will 
              be corrected in a future release. 

              On OpenVMS, the return code is always %X10010001 (hexadecimal). 
              This will be corrected in a future release. 

        +-----------------------------------------------------+




        2.4.2 Monitoring from the Operating System 
      If the CLI returns an undetermined status, or you want more details about 
      subprocesses, you can use the monitoring procedures specific to your 
      operating system. 
      In UNIX variants and Windows, some WEBES processes are listed under the 
      "Java" name. Be aware, however, that other applications also might use the 
      Java name. Be careful to make sure that the processes you are monitoring 
      really are WEBES processes, as shown in the following examples. 
          2.4.2.1 OpenVMS 
      Use the following command to show the processes running on an OpenVMS 
      system: 
      $ show system 

      Example output is shown here: 
      OpenVMS V7.2-2 on node THIS 15-OCT-2002 15:03:52.59 Uptime 39 05:37:42 
      Pid      Process Name    State  Pri I/O     CPU            Page flts  
      Pages 
      ... 
      0000F68D WCCProxy        LEF    6   353     0 00:00:00.07  504        201 
      0000F68E DESTA Director  HIB    5   198456  0 00:01:10.09  154670     
      12301 M 
      0000F68F SMITH_2         HIB    6   23027   0 00:02:31.40  25089      6285 
      MS 
      0000F691 CA.A.19.54240   HIB    6   341     0 00:00:00.16  422        286 
      0000F695 CA.A.20.54249   LEF    6   248     0 00:00:00.11  465        239 
      0000F698 WCC.A.1200.8989 LEF    6   201     0 00:00:00.10  382        220 
      0000F89C JONES_1         HIB    6   291     0 00:00:00.05  316        133 
      S 
      0000F69E JONES_2         COM    4   2656    0 00:00:07.57  73623      7357 
      MS 
      0000F342 RCM            HIB    7   0      0 00:00:00.00  23        30 

      In the above example, the DESTA Director parent process is shown. That 
      process also has spawned a subprocess named SMITH_2, which only runs when 
      needed, so named because the user SMITH started the Director, but the 
      relation is not apparent from the output. Other WEBES processes, such as 
      SEA CLI commands, appear named after the user that started them, such as 
      JONES_1 and its subprocess JONES_2 in this example, although it is not 
      apparent that they are WEBES processes. The WCCProxy process is a C++ 
      based launcher for WEBES processes that communicates to the main Director 
      process. The CA.A.nn.nnnn and WCC.A.nn.nnnn processes are C++ based 
      processes launched by WCCProxy to send notifications, read the native 
      binary event log, and send events to the main Director process. There may 
      be more than one CA.A.nn.nnnn or WCC.A.nn.nnnn process running at a time, 
      or none. 
          2.4.2.2 Windows 
      On Windows, press CTRL+ALT+DEL, open the Task Manager, and Click the 
      Processes tab to view running processes. WEBES Director processes consist 
      of the following image names: 
        DESTAService.ex (on Windows 2000) or DESTAService.exe (on XP) 
        java.exe 
        WCCProxy.exe 
        CAAgents.exe 
        WCCAgents.exe 
      The main parent Java-based Director process is the DESTAService process, 
      which runs as a Windows service. It spawns a subprocess when needed, which 
      runs under the process name java.exe. The WCCProxy process is a launcher 
      for C++ based WEBES processes that communicates to the main Director 
      process. The CAAgents.exe and WCCAgents.exe processes are C++ based 
      processes launched by WCCProxy to send notifications, read the native 
      binary event log, and send events to the main Director process. There may 
      be more than one CAAgent or WCCAgent process running at any time, or none. 

      All CLI commands run under the process name java.exe. However, not all 
      java.exe processes are guaranteed to be WEBES processes. Java-based 
      applications other than WEBES also may appear as java.exe. 
      You may be able to distinguish the Director set of processes from other 
      WEBES and non-WEBES Java processes by looking at the base priority of the 
      java.exe processes. The Director processes always run at low priority, 
      while all other WEBES processes run at normal priority. However, other 
      Java processes, not associated with WEBES, also may run at low priority. 
      If the Base Priority column is not shown in the Task Manager list: 
        Choose View | Select Columns. 
        Click Base Priority. 
        Click OK. 
      2.5 Log Files 
      WEBES processes log warning or informational messages to special log files 
      or to the terminal window. (These log files are different from the system 
      binary event log files that SEA interprets and analyzes as part of its 
      normal operation.) 
      If SEA is not responding as expected, check the log files for messages 
      that may help you restart or recover. You also can copy the files to new 
      filenames so that they are not overwritten, and you can send files to your 
      service provider for review. 
      For commonly-encountered log messages, see Appendix D or the WEBES Release 
      Notes. The format of each message is the same for all platforms; however, 
      the file locations differ depending on operating system. 
         2.5.1 HP-UX 
         2.5.2 Linux 
         2.5.3 OpenVMS 
         2.5.4 Windows 
         2.5.5 Logging Level 
        2.5.1 HP-UX 
      The Director and web interface log standard output and error messages to: 
      /opt/hp/svctools/specific/webes/logs/desta_dir.log 

      The Director appends to this log file each time it is started. 
      WEBES and the WEBES installer write additional log files containing 
      information that might be useful to WEBES product support personnel when 
      diagnosing a problem with WEBES or any of its component tools. These log 
      files are stored in the following directories: 
      /opt/hp/svctools/specific/ca/logs 
      /opt/hp/svctools/specific/wccproxy/logs 
      /opt/hp/svctools/specific/webes/logs 

        2.5.2 Linux 
      The Director and web interface log standard output and error messages to: 
      /usr/opt/hp/svctools/specific/webes/logs/desta_dir.log 

      The Director appends to this log file each time it is started. 
      WEBES and the WEBES installer write additional log files containing 
      information that might be useful to WEBES product support personnel when 
      diagnosing a problem with WEBES or any of its component tools. These log 
      files are stored in the following directories: 
      /usr/opt/hp/svctools/specific/ca/logs 
      /usr/opt/hp/svctools/specific/wccproxy/logs 
      /usr/opt/hp/svctools/specific/webes/logs 

        2.5.3 OpenVMS 
      The Director and web interface log standard output and error messages to: 
      SVCTOOLS_HOME:[SPECIFIC.WEBES.LOGS]DESTA_DIR.LOG 

      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 OpenVMS filename. 
      WEBES and the WEBES installer write additional log files containing 
      information that might be useful to WEBES product support personnel when 
      diagnosing a problem with WEBES or any of its component tools. These log 
      files are stored in the following directories: 
      SVCTOOLS_HOME:[SPECIFIC.CA.LOGS] 
      SVCTOOLS_HOME:[SPECIFIC.WCCPROXY.LOGS] 
      SVCTOOLS_HOME:[SPECIFIC.WEBES.LOGS] 

        2.5.4 Windows 
      These locations assume that SEA was installed to the default directory; if 
      this is not the case, the path will match the chosen install directory. 
      The Director and web interface log standard output messages to: 
      C:\Program Files\hp\svctools\specific\webes\logs\director_out.txt 

      The Director's standard error messages are logged to: 
      C:\Program Files\hp\svctools\specific\webes\logs\director_err.txt 

      The Director creates new log files each time it is started. The previous 
      log files are renamed to director_err.txt.bck and director_out.txt.bck, 
      overwriting any previous versions of those files. 
      WEBES and the WEBES installer write additional log files containing 
      information that might be useful to WEBES product support personnel when 
      diagnosing a problem with WEBES or any of its component tools. These log 
      files are stored in the following directories: 
      C:\Program Files\hp\svctools\specific\ca\logs 
      C:\Program Files\hp\svctools\specific\desta\logs 
      C:\Program Files\hp\svctools\specific\wccproxy\logs 
      C:\Program Files\hp\svctools\specific\webes\logs 

        2.5.5 Logging Level 
      The warning or informational messages logged by WEBES processes are stored 
      in the Director log files as previously described. A minimum severity 
      level, or logging level, determines the lowest priority of message that 
      will be written to these files. Only messages that meet or exceed the 
      minimum severity level are written to the Director log files. 
      2.6 Service Obligation 
      A system's service obligation specifies your service provider, service 
      agreement information, and the duration of your agreement. During the 
      WEBES installation process, you are prompted to enter the service 
      obligation information, and this information gets included with the 
      results of SEA analysis. 
      Although SEA continues to function without a valid service obligation, 
      local notification and reporting are disabled. In addition, the web 
      interface does not operate if the service obligation has expired. 
      Sections 3.12 and  7.12 explain how to view your service obligation. 
      2.7 Managed Entities, Storage Cells, and EVAs 
        2.7.1 Managed Entities
      SEA monitors the nodes (hosts or machines) that you define. By default, 
      SEA monitors the local host. A node can also monitor and analyze other 
      managed entities. A managed entity is the general term for a hardware 
      device or system that is managed by SEA or other software. The managing 
      software maintains the configuration information of the hardware, allows 
      users to update it, and ensures that real-time events such as errors, 
      status or configuration changes are logged and processed for taking 
      appropriate actions. 
      Note that SEA may not be the managing software of the device or system. 
      Other software may be managing it or it may be managed by SEA in 
      conjunction with the other software. SEA's role may be limited to 
      monitoring or processing data, while the other software performs other 
      management tasks. 
        2.7.2 Storage Cells are a Type of Managed Entity
      As of the current release of SEA, there are four types of managed entities 
      that SEA can monitor and process, which is a Storage Cell. This is the 
      general term for a set of hardware and software that stores information, 
      beyond the simple internal disk storage which is managed by the host 
      operating system. A storage cell may be a network-attached storage server, 
      a Storage Area Network (SAN), a disk array system, or a tape backup 
      system. 
      In the future, SEA may be able to monitor and process other types of 
      managed entities besides storage cells. 
        2.7.3 EVAs are Types of Storage Cells
      As of the current release of SEA, the SEA can monitor and process an HP 
      StorageWorks Enterprise Virtual Array (EVA). HP's Command View EVA program 
      is the software that manages an EVA. As of the current release, SEA 
      supports EVA Storage Cells only on Windows 2000, Windows XP, and Windows 
      2003 on the Intel Pentium platform. Because it must be installed on the 
      same machine as the ISEE Client, it cannot be a Windows XP host. SEA is 
      intended to support managed entities on other operating systems and 
      platforms in the future. 
      SEA can monitor and process events logged by the EVAs to the system's 
      binary event log via Command View EVA. SEA displays the information in the 
      web interface by automatically analyzing events from such entities and by 
      sending notifications when appropriate, much like the functioning of SEA 
      with a node's binary events. SEA can gather configuration information 
      about the EVAs from the Command View. With the configuration data supplied 
      by the user, SEA can fill in the appropriate information to be sent in 
      problem report notification. 
      *** Note ***


        WEBES v4 and later requires Command View EVA (CV EVA) v3.2 to be 
        installed on systems that manage HP StorageWorks Enterprise Virtual 
        Arrays (EVAs). In addition, WEBES v4.5 now supports the gathering of 
        status and error data from the fiber ports associated with EVA storage 
        subsystems. For this feature to work correctly CV EVA v4.1 is required. 
        If you connect to CV EVA of a version earlier than v4.1, WEBES will work 
        but it will not collect fiber port status data. Regardless of this new 
        feature, WEBES recommends installing the latest version of CV EVA to 
        take advantage of the latest improvements and features in CV EVA. 



      During the WEBES installation process, you are prompted to enter 
      configuration information for any managed entities detected on the node 
      where you are installing WEBES. This information is included with the 
      results of SEA analysis. If an entity is not fully configured during WEBES 
      installation or a new entity is detected later, the Web interface prompts 
      for the entity configuration information, when the user logs in. 
      Refer to Section 3.13 "Managed Entities (Command View EVA server, EVA, 
      WBEM Server) Commands" for more information on Managed Entity Command and 
      Section 7.13 "Managed Entities" for more information on Web-based 
      management interface. 
      EVA Storage Systems Status and Events 
      WEBES V4.5 supports the gathering of status and error data from the fiber 
      ports associated with HP StorageWorks Enterprise Virtual Array (EVA) 
      storage subsystems. 
      The EVA status and error data is reported to the EM-Client, which is part 
      of the HP StorageWorks Command View storage management application. 
      The port data that can be collected is related to: 
        Disk drives in the storage array 
        Fiber port controller 
        Enhanced Port Bypass Circuit (E-PBC) 
      By default, WEBES V4.5 polls the EM-Client for fiber port status every 12 
      hours. 
      This new EVA fiber port support allows HP StorageWorks Serviceability 
      Engineering to write rules that present status information and error 
      callouts in the Command View application. These rules will support the 
      following assets: 
        Physical loop map of the fiber port, which changes whenever one of the 
        following occurs: 
          A disk is removed, inserted, or replaced.
          The physical configuration of the loop changes 
        Port stat counters, which become invalid whenever one of the following 
        occurs: 
          An array is powered up.
          A loop circuit is re-synchronized 
          A link is lost 
          A LIP command is invoked. 
          The disk firmware does not meet the minimum revision
      The current port status is kept in memory for 24 hours, after which it is 
      removed. 
      These new EVA fiber port rules will be available as future rules updates 
      to WEBES v4.5. 
      2.8 Automatic Notification 
      Whenever SEA determines that there has been a reportable event on a 
      system, it can automatically notify you via email. You can also configure 
      SEA to perform other forms of notification, such as to HP's OSEM or SIM 
      software products, or appending the notification to a text file on the 
      system. 
      In addition, SEA can automatically notify a customer support center, 
      provided that the system is configured to work with HP Instant Support 
      Enterprise Edition (ISEE), which uses the ISEE Client installed on the 
      system. 
      See Chapter 11 to configure automatic notification. 
      2.9 Command Line Interface 
      You can perform many operations from the command prompt by issuing 
      commands beginning with desta, wccproxy, or wsea. For example: 
      wsea analyze input myBinary.errlog 

      CLI commands typically support many options for specifying input files, 
      output files, and filtering criteria. Each command starts a process. Some 
      CLI processes connect to the Director on the local system, while others 
      perform tasks by themselves without connecting to a Director. 
      See Chapter 3, 4, or  5, respectively, for details about the desta, 
      wccproxy, or wsea commands. 
      2.10 Web Interface 
      A web browser can connect to any of the following: 
        Directly to the URL of the Director on the same system as the browser 
        Directly to the URL of the Director on a remote system 
        Indirectly to a remote WCCProxy, by first opening a direct connection to 
        the Director on the local or a remote system 
      The web interface can monitor multiple nodes by communicating with the 
      WCCProxys on multiple systems. You can establish a direct connection to 
      the Director on any system reachable by its TCP/IP socket port, and, 
      through that connection, view the SEA processes on other nodes via 
      Director-to-WCCProxy communication. 
      You do not need to have WEBES installed or running on the same system as 
      the web browser in order to connect to the Director on a remote system. 
      See Chapter 7 for more details about the web interface and Appendix C for 
      a list of supported web browsers. 


            ===========================================================================

      3 
      *** WEBES Director Processes and DESTA Commands *** 
      This chapter describes the WEBES Director and the DESTA CLI command. 
        What is the Director?
        SEA and the Director
        How Directors Work Monitoring Multiple Systems
        Interacting with the Director
        Troubleshooting an Unresponsive Director
        DESTA Command Overview
        Starting the Director
        Stopping the Director
        Port Configuration
        Automatic Notifications
        Priority
        Service Obligations
        Getting Help
      3.1 What is the Director? 
      The Director is a required WEBES process (or set of processes) that runs 
      continuously. The Director manages a system--either a standalone system or 
      a node in a cluster--on behalf of WEBES, and executes functionality added 
      to it by individual WEBES tools. 
      3.2 SEA and the Director 
      SEA provides the Director with the ability to capture and interpret 
      hardware events, either automatically or at the request of an outside 
      process. The Director captures, translates, and analyzes the events, and 
      routes messages for the SEA system. The Director is idle except for during 
      the following circumstances: 
        Events are received for processing 
        Messages arrive from other WEBES processes on the same system 
        Another WEBES tool within the Director performs any task 
      SEA includes a web browser interface that interacts with the Director. 
      Although only one Director can run on a system at any time, many web 
      browser connections can be active simultaneously, all connected to a 
      single Director. 
      3.3 How Directors Work Monitoring Multiple Systems 
      Figure 3-1 shows an example of two systems running SEA processes, a UNIX 
      system and a Windows system, each running a single Director, and 
      communicating with each other over a network. 
      Figure 3-1 Interaction Between Two Systems Running SEA 
        Web interface #1 is a web browser running on the UNIX system, directly 
        connected to the local Director on the same system 
        (http://localhost:7902). It also can communicate with the WCCProxy on 
        the Windows system through the UNIX Director. This enables you to view 
        the output produced by either system, such as analysis results, using 
        the same web interface. 
        Web interface #2 also is running in a browser on the UNIX system, but it 
        has directly connected to the Director on the Windows system 
        (http://win.sys.name.here:7902). Using this web interface you can, if 
        desired, connect back to the UNIX WCCProxy as well, but the UNIX 
        Director need not be running at all. 
        A telnet session initiated from the Windows system has logged on to the 
        UNIX system, and the user has issued the wsea report command to view the 
        results of automatic analysis. The CLI process connects to the UNIX 
        system's Director, which returns the current report data to the CLI 
        process. The report text is then displayed to the user. Note that it is 
        not necessary to have the Director running on the Windows system for 
        this type of remote connection. 
        A user wants to perform manual analysis on the "thisBinary.errlog" file 
        that was transferred from a UNIX system to the Windows system via FTP. 
        The user issues the wsea analyze input thisBinary.errlog command from 
        the Windows system. The Director is not needed for manual analysis, so 
        there is no interaction with the local Director. 
        Web interface #3 is a web browser running on the Windows system. This 
        interface is directly connected to the local Director on the same system 
        (http://localhost:7902) the same way that web interface #1 connects to 
        its local UNIX Director. 
      3.4 Interacting with the Director 
      The Director automatically starts along with the system and normally does 
      not require additional attention; however, this chapter explains how to 
      interact with it whenever you must affect its operation for some reason. 
      You interact with the Director by sending it commands from the command 
      prompt of the system where WEBES is installed. These commands impact all 
      of WEBES and are not limited to only the SEA tool. The Director commands 
      perform WEBES-level tasks such as configuring port settings, activating 
      automatic notification, or viewing your service obligation. 
         3.4.1 Permissions 
         3.4.2 Clusters 
         3.4.3 DESTA 
        3.4.1 Permissions 
      To run any of the commands described in this chapter, you must be a 
      privileged user as described in Section 2.2. 
        3.4.2 Clusters 
      Even if SEA is installed on a cluster, commands only impact the local 
      node. If you want to modify an entire cluster you must perform the desired 
      operation on each node. 
        3.4.3 DESTA 
      Distributed Enterprise Service Tools Architecture (DESTA) is the 
      engineering code name for the WEBES software suite architecture, central 
      to which is the Director. DESTA has become the name of the command that 
      affects the Director. 
      3.5 Troubleshooting an Unresponsive Director 
      If one of the WEBES components is not responding or giving an error, it 
      may be that the Director process is not responding. To correct this 
      problem, use one of the following procedures. 
         3.5.1 Windows (Unresponsive Director) 
         3.5.2 HP-UX and Linux 
         3.5.3 OpenVMS 
         3.5.3 OpenVMS 
        3.5.1 Windows (Unresponsive Director)
      Stop the Director either from the Start | Programs menu, or by issuing the 
      command: net stop desta_service. Check the Windows Task Manager for the 
      following WEBES processes: 
        CAAgents.exe (may be more than one of these, but they are all part of 
        WEBES) 
        WCCAgents.exe (may be more than one of these, but they are all part of 
        WEBES) 
        DESTAService.ex or DESTAService.exe 
        java.exe (there may be other Java(TM) processes on the systems, see 
        below) 
        WCCProxy.exe 
      If they end within 2 minutes, the Director can be restarted either from 
      the Start | Programs menu, or by issuing the command: net start 
      desta_service and then waiting approximately one minute for WEBES to set 
      up its processes before running a WEBES tool. 
      If there are data transport problems, there is a possibility of 
      accumulating about one megabyte of used disk space per week. 
      If the Director does not stop in approximately two minutes the processes 
      may be hung. Select any suspect WEBES process from the list above and 
      press the End Process button, which should remove the entry. Do not end 
      java.exe processes that are not associated with the WEBES Director. To 
      identify likely WEBES java.exe processes, look for a "Low" base priority 
      in the Task Manager's Process list. If you do not see the Base Priority 
      column, choose View | Select Columns from the Task Manager pull-down menu 
      and check the box for Base Priority. 
      If you are presented with an error message that you do not have privileges 
      to end a process, you must restart the Windows system. Before restarting, 
      follow the post-installation steps in the WEBES Installation Guide to 
      assign yourself the privileges necessary to kill WEBES processes in the 
      future. The Director will be restarted automatically during the restart 
      phase. 
        3.5.2 HP-UX and Linux
      Issue the command: desta stop. If the Director does not stop in 
      approximately two minutes the process may be hung. Look for the WEBES java 
      processes in the ps list: 
      # ps -eflx | grep /opt/hp/svctools | grep -v grep 

      Processes containing any of the following strings may appear, all of which 
      are WEBES processes: 
        CAAgents (may be more than one) 
        WCCAgents (may be more than one) 
        DESTAController 
        DESTAProcessWrapper 
        WCCProxy 
      Then, issue kill commands to stop them. Finally, as the root user, issue 
      the command: desta start and wait approximately one minute for WEBES to 
      set up its processes before running a WEBES component. 
        3.5.3 OpenVMS 
      Issue the command: desta stop. If the Director does not stop in 
      approximately two minutes the process may be hung. Look in the SHOW SYSTEM 
      output for any of the following WEBES processes: 
        CA.N.nn.nnnn (the n values will vary) 
        DESTA Director 
        WCCProxy 
      Issue the STOP PROC /ID= command to kill the process ID associated with 
      those processes. Then issue the command: desta start and wait 
      approximately one minute for WEBES to set up its processes before running 
      a WEBES component. 
      3.6 DESTA Command Overview 
      Director commands follow this convention: 
      desta command_verb 

      Where command_verb indicates the action you want to perform (see Table 
      3-1). 
        Table 3-1 Command Verbs--desta 
        +-----------------------------------------------------+

              Verb 
              ----------
              Description 
              ----------

              dri 
              Controls DESTA registry entries including the amount of memory 
              used by the Director process and subprocesses. See Section 10.7.4. 


              help 
              Displays an overview of the desta command. Entering no command 
              verb also shows the help file. See Section 3.14. 

              isee 
              Turns Instant Support Enterprise Edition (ISEE) automatic 
              notifications to HP on or off if the ISEE Client is installed on 
              the system. See Section 3.10.1 for syntax information and Section 
              11.4.3 for more details. (Not available for WEBES on HP-UX) 

              entity
              Manages the list of managed entities monitored by SEA. See Section 
              3.13 for more details on managed entity commands.

              smtp
              Turns Simple Mail Transfer Protocol (smtp) notifications via email 
              to the user of WEBES on or off. See section 3.10.2 for more 
              details.

              msg 
              Changes the SEA port configuration settings. See Section 3.9 for 
              more details on port settings. 

              priority 
              (UNIX variants and OpenVMS only) Changes the priority of the 
              Director process. Possible priorities are normal (compete with 
              other processes) and low (allow normal processes to use more CPU 
              than the Director). The default is low. See Section 3.11. 

              qsap 
              Turns automatic notifications to HP on or off if the system 
              communicates with OSEM (Open Service Event Manager). See Section 
              3.10.3 for syntax information and Section 11.4.2 for more details. 


              servob 
              Displays the current status of the service obligation. See Section 
              3.12 for more details. 

              sicl 
              Turns System Initiated Call Logging (SICL) automatic notifications 
              to HP on or off if DSNLink is installed on the system. See Section 
              3.10.4 for syntax information and Section 11.4 for more details. 

              start 
              Starts the WEBES Director. Normally this is not necessary, since 
              the Director automatically is started with the system. It may be 
              necessary to run this command if the Director was stopped using 
              the stop command. See Section 3.7. 

              status 
              Displays the current status of the Director process. See Section 
              2.4.1. 

              stop 
              Shuts down the WEBES Director process and all DESTA-connected 
              processes. Be aware that this impacts all WEBES users connected to 
              the system. See Section 3.8. 

              snmp
              Enables SEA to communicate Serviceable Events to HP-SIM and HP 
              OpenView.





        +-----------------------------------------------------+




      3.7 Starting the Director 
      The Director is automatically started during system startup. Under normal 
      operation, you should not need to manually start the Director. However, if 
      circumstances require it, you can manually start the Director by following 
      the instructions for your operating system. 
      *** Wait Before Restarting ***


        After a "desta stop" or "net stop desta_service" command completes, the 
        operating system sometimes requires a few more seconds to stop all 
        WEBES-related processes and release resources (such as sockets). On rare 
        occasions, restarting the Director too soon after stopping it can result 
        in errors in the Director log file, and the Director also may fail to 
        restart. 

        To avoid this issue, wait 10 more seconds before restarting the 
        Director, once the "desta stop" or "net stop desta_service" command 
        completes. 



      HP-UX 
      At a shell prompt, enter: 
      # /usr/sbin/desta start 

      Linux 
      At a shell prompt, enter: 
      # /usr/sbin/desta start 

      OpenVMS 
      At the OpenVMS command line prompt, enter: 
      $ desta start 

      On OpenVMS clusters, you can uses the SYSMAN utility to issue the do desta 
      start command on either all the nodes in the cluster or a specific group 
      of nodes that you choose. 
      Windows 
      To start the Director, start the DESTA_Service using one of the following 
      methods: 
        Choose Start | Programs | Hewlett-Packard Service Tools | Web-Based 
        Enterprise Services | Start Director. 
        In a Command Prompt window, enter the command: 
        C:\>net start desta_service 

        Start the DESTA_Service using the Windows Services Manager utility 
        available within the operating system. 
        *** Caution ***


          The desta start command on Windows is unsupported.The command may 
          start the Director, but it also may cause errors. 

          If you close the command prompt window used to issue the command, or 
          log out of Windows, you forcibly but incompletely stop the Director 
          and leave running processes behind (see the WEBES Release Notes if 
          this situation occurs). 

          Furthermore, any open files may not be saved correctly and may have 
          their data corrupted. 

          At a minimum, text log output from the Director process is only 
          displayed on the screen and will eventually scroll past the buffer. 

          On Windows, the desta start/stop commands are used only for 
          troubleshooting, and if the Director is started with desta start, it 
          must be stopped with desta stop.



      3.8 Stopping the Director 
      Under normal operation, you should not need to stop the Director. However, 
      if circumstances require you to stop the Director, follow the instructions 
      for your operating system. 
      *** Wait Before Restarting ***


        After a "desta stop" or "net stop desta_service" command completes, the 
        operating system sometimes requires a few more seconds to stop all 
        WEBES-related processes and release resources (such as sockets). On rare 
        occasions, restarting the Director too soon after stopping it can result 
        in errors in the Director log file, and the Director also may fail to 
        restart. 

        To avoid this issue, wait 10 more seconds before restarting the 
        Director, once the "desta stop" or "net stop desta_service" command 
        completes. 



      HP-UX 
      At a shell prompt, enter: 
      # /usr/sbin/desta stop 

      Linux 
      At a shell prompt, enter: 
      # /usr/sbin/desta stop 

      OpenVMS 
      At the OpenVMS command line prompt, enter: 
      $ desta stop 

      On OpenVMS clusters, you can uses the SYSMAN utility to issue the do desta 
      stop command on either all the nodes in the cluster or a specific group of 
      nodes that you choose. 
      Windows 
      To stop the Director, stop the DESTA_Service using one of the following 
      methods: 
        Choose Start | Programs | Hewlett-Packard Service Tools | Web-Based 
        Enterprise Services | Stop Director. 
        A Stop Director icon appears in the Task Bar, then disappears when the 
        Director shutdown has completed. 
        In a Command Prompt window, enter the command: 
        C:\>net stop desta_service 

        Stop the DESTA_Service using the Windows Services Manager utility 
        available within the operating system. 
        *** Caution ***


          The desta stop command on Windows is unsupported. The command may 
          eventually stop the Director, but it also may cause errors. 

          The Director may not stop completely, leaving running processes 
          behind. 

          Error messages may appear in either the logs for the Director process 
          or in the desta stop output. 

          The Director may take longer to stop than it normally would using one 
          of the recommended methods, and it may continue to run for a time even 
          after the desta stop process has finished. 

          On Windows, the desta start/stop commands are used only for 
          troubleshooting, and if the Director is started with desta start, it 
          must be stopped with desta stop.



      3.9 Port Configuration 
      You can configure the socket ports used by WEBES with the following 
      command: 
      desta msg -chgport nnn 

      See Section 10.4.2 for more information. 
      You can use the web interface to modify additional configuration settings 
      as explained in Chapter 10. 
      3.10 Automatic Notifications 
      SEA can automatically send problem reports to HP Services for faster 
      problem resolution. With notifications, the results of SEA analysis are 
      automatically sent to your service provider as they occur. 
         3.10.1 ISEE Notification 
         3.10.2 SMTP Notification 
         3.10.3 OSEM Notification (formerly PRS CSG/QSAP) 
         3.10.4 SICL/ACHS/DSNlink Notification
         3.10.5 SNMP Notification to HP SIM and OVO
         3.10.6 DTCS Notification
         3.10.7Open VMS Mail Notification
         3.10.8WEBES Health Check Report
        3.10.1 ISEE Notification
      Instant Support Enterprise Edition (ISEE) can send automatic notifications 
      from WEBES to HP customer support when the ISEE Client is installed on the 
      same system where WEBES is installed. When you install WEBES 4.5, ISEE 
      notification will be enabled by default if the ISEE Client is found to be 
      installed. The desta isee command enables or disables ISEE notifications. 
      desta isee on
      desta isee off

      See Section 11.4.3 "Instant Support Enterprise Edition" for more 
      information. 
        3.10.2 SMTP Notification
      When you install WEBES 4.5, email notification via Simple Mail Transfer 
      Protocol (SMTP) will be enabled by default. SMTP is a method to notify the 
      user of WEBES and typically not a method to notify HP Services. The desta 
      smtp command enables or disables notifications via SMTP email. 
      desta smtp on
      desta smtp off

      See Section 11.3 "Sending Notifications to Email Addresses" for more 
      information. 
        3.10.3 OSEM Notification (formerly PRS CSG/QSAP)
      WEBES can be enabled to send notifications to Open Service Event Manager 
      (OSEM). OSEM has replaced the Customer Service Gateway (CSG, formerly 
      known as Qualified Service Access Point or QSAP) function of Proactive 
      Remote Services (PRS). The PRS product has now retired in favor of HP ISEE 
      (see section  3.10.1) as the remote support tool for notifying HP customer 
      support. OSEM provides local support similar to the remote support 
      previously provided by PRS CSG/QSAP. You can configure WEBES to send 
      notifications to OSEM in the same manner you would have previously 
      configured WEBES to send notifications to PRS CSG/QSAP. 
      The desta qsap command enables or disables OSEM notifications. The command 
      name is still qsap even though the product has changed. WEBES sends 
      notifications to OSEM using the same protocol it sent to CSG/QSAP. 
      desta qsap on
      desta qsap off

      See Section 11.5.1 "Open Service Event Manager" for more information. 
        3.10.4 SICL/ACHS/DSNlink Notification
      The HP DSNlink product has retired and is no longer supported by HP. You 
      may still enable this form of notification, and WEBES will send out 
      notifications using the DSNlink software if it is installed on the system, 
      but the notifications are not likely to arrive at any HP Services call 
      center. Use ISEE (see Section 3.10.1) instead for fully-supported 
      notifications to HP Services. 
      The WEBES Automated Call Handling System (ACHS), also known as 
      System-Initiated Call Logging (SICL), uses HP DSNlink software to securely 
      transmit problem reports to HP Services (before DSNlink's retirement). The 
      desta sicl command enables or disables SICL notifications. 
      desta sicl on
      desta sicl off

      See Section 11.4.1 "System Initiated Call Logging" for more information. 
      *** Note ***


        The SICL command is changed from wsea sicl to desta sicl in an earlier 
        release. Both commands are not supported in WEBES now and may be removed 
        in a future release.



        3.10.5 SNMP Notification to HP SIM and OVO
      The Simple Network Management Protocol (SNMP) Trap output capability from 
      WEBES allows a support notification to be sent to management applications 
      such as HP Systems Insight Manager (HP SIM) and OpenView Operations (OVO). 
      The desta snmp command enables or disables support notification to 
      management applications. 
      desta snmp on
      desta snmp off

      The desta snmp on command on WEBES 4.5 Windows Itanium requests the user 
      to provide both SNMP Trap destination and trap type. The supported trap 
      types are 2 and 3. 
      See Section 11.5.2 "Simple Network Management Protocol (SNMP) 
      Notifications to HP SIM or OVO" for more information. 
        3.10.6 DTCS Notification
      The Disaster Tolerant Computing Service (DTCS) is a notification of all 
      callouts made by WEBES. WEBES sends SEA callouts that are marked for 
      delivery to a new DTCS destination, support provider destination or 
      customer destination. The callouts are delivered in XML over HTTP format 
      to a host and port defined in the desta dtcs on command. This command is 
      disabled by default and the user will have to enable the desta dtcs 
      notification, if desired. 
      DTCS requests a heart beat every minute to verify the connectivity status. 

      desta dtcs on
      desta dtcs off

      See Section 11.5.3 "Disaster Tolerant Computing Service (DTCS)" for more 
      information. 
        3.10.7 Open VMS Mail Notification
      WEBES can be enabled to send notifications to the OpenVMS Mail utility 
      (not to be confused with SMTP email). The following desta vmsmail command 
      enables or disables OpenVMS Mail notification. 
      desta vmsmail on
      desta vmsmail off

      See Section  11.3.5 "Open VMS Mail Notification" for more information. 
        3.10.8 WEBES Health Check Report
      WEBES Health Check Report is a notification sent by email when the 
      Director or WCCProxy is not running. The email notification is sent if the 
      whc SMTP is ON and the results are written to a log file. The notification 
      contains instructions on what corrective action/steps to be taken. 
      WEBES Health Check is supported on Windows Pentium only. 
      The following are the basic WEBES Health Check Commands: 
      Desta whc on/off - Turn all components of webes health check on or off

      After executing whc on/off, check the desta.reg file for the following 3 
      whc entries:
      whc.e2e=t/f
      whc.smtp=t/f
      whc.log=t/f

      Turns each component of health check on or off

      Desta whc smtp on/off turns health check smtp notification on or off
      Desta whc log on/off turns health check logging on or off
      Desta whc e2e on/off turns health check end to end testing on or off

      Desta whc status - Indicates whether the health check is on or off

        3.10.8.1 Scheduling Health Check Tasks Manually
      To schedule the Health Check tasks manually, execute the following CLIs to 
      add/remove scheduled tasks: 
      Adding a scheduled task: at <Time> /every:M, T, W, Th, F, S, Su cmd /c 
      "<INSTALLDIR>\svctools\common\bin\desta.bat launchwhc"

      Removing a scheduled task: at <AtJobNo> /delete /yes 
      3.11 Priority 
      By default the Director process runs at low priority. On UNIX variants and 
      OpenVMS systems, you can change the priority while the Director is running 
      by entering the desta priority command: 
      desta priority compete 
      desta priority low 

      Where compete assigns the Director a normal priority, or low assigns the 
      Director a low priority. 
      On OpenVMS systems, this command issues the SET PROCESS /PRIORITY command. 
      The operating system may change the priority of any process at any time, 
      and may not change the priority when the SET PROCESS /PRIORITY command is 
      issued. Therefore, the desta command may not change the priority of the 
      DESTA Director process. It functions more like a suggestion to the 
      operating system rather than a command. 
      3.12 Service Obligations 
      During the WEBES installation process, the user is asked about the service 
      obligation data for the system on which WEBES in being installed. 
      Your service obligation describes the details of your service agreement. 
      You can view an existing service obligation from the command line. See 
      Section 2.6 for more information about service obligations. 
      WEBES V4.5 now interviews the user for the service obligation data as 
      shown in the following example. As with the earlier versions of WEBES, the 
      default response that is shown in square brackets is chosen if you press 
      `Enter'. Otherwise, the text entered by you is captured. 
      If the you enter `N' when asked if the Service Obligation number is the 
      same as the serial number, you will be prompted for the new Service 
      Obligation number, and that number replaces the default number. 
      To view the service obligation for a system, enter the following command: 
      desta servob show 

      This displays your service obligation as shown in the following example: 
      WEBES Service Obligation Status 
      Service Obligation: Valid
      Service Obligation Number: D133FK31K009
      System Serial Number: D133FK31K009
      Service Provider Company Name: Hewlett-Packard Company


      3.13 Managed Entities (Command View EVA server, EVA, WBEM Server) Commands 

      You can import a new managed entity with the following command: 
      desta entity import [fileroot]

      where fileroot is the path (optional) and root name of the set of CSV 
      (Comma Separated Values)files to be converted into WEBES Managed Entities. 

      Command Usage 
        The template xls file is present in the kit and is available in 
        ..\svctools\common\ca\data 
        In the Entities sheet, fill in the details of managed entities to be 
        added (Note: Serial no and Product no are mandatory fields). Provide 
        username and password for WBEM Server and EVA.
        In the Sites sheet, fill in the details of the sites to be added.
        In the Contact sheet, fill in the details of the contacts to be added.
        Save the Entities sheet as Ents_ent.csv
        Save the Sites sheet as Ents_sit.csv
        Save the Contacts sheet as Ents_con.csv (Note: for non-Windows platform, 
        copy the .CSVs to the respective machines).
        Execute the following command:
        desta entity import Ents 


      The command has been implemented to support managed entities in general, 
      including but not limited to Command View EVA Server, EVAs, and WBEM 
      Server or all future releases. As of the WEBES 4.5 release, you need not 
      issue this command as EVAs are detected automatically by the Command View 
      EVA software. WEBES retrieves the list of EVAs from Command View EVA every 
      12 hours. Any entity that you add with this command will not appear in the 
      list of SEA Web interface - Storage Cells unless it exists as an EVA 
      detected by the Command View EVA. 
      See Sections  7.13 Managed Entities and  7.7 Creating Storage Cell 
      Spreadsheets for more information on the SEA Web interface relating to 
      Managed Entities and Storage Cells. 
      After installing a new EVA, refer to the WEBES Install Guide section 2.3.6 
      "Adding an EVA After Installing WEBES" for the steps to configure the EVA 
      information for SEA and to allow the WEBES Director and SEA to recognize 
      the new Storage Cell immediately. WEBES will recognize the new EVA within 
      12 hours, and send an email using the settings in NotifyCA.txt, (see 
      Section  11.3.1Settings) asking you to configure the new EVA for SEA. 
      As of the WEBES 4.5 release, you need not issue this command for EVAs 
      unless you are removing the EVA hardware. SEA detects new unconfigured 
      EVAs every 12 hours, and at Director startup and other situations. If you 
      remove an EVA from Command View EVA with this command, but do not remove 
      the hardware, SEA will re-detect the EVA within 12 hours or on the next 
      Director startup. SEA will also prompt you for configuration data on your 
      next CLI command or Web interface login. 
      3.14 Getting Help 
      You can access different help for the desta command based on your 
      operating system: 
        UNIX variants--man desta and desta help 
        OpenVMS--help desta and desta help 
      Windows--desta help 


          ===========================================================================

      4 
      *** WCCProxy Processes and WCCProxy Commands *** 
      This chapter describes the WEBES WCCProxy process and the WCCProxy CLI 
      command. 
        What is the WCCProxy?
        Interacting with the WCCProxy
        WCCProxy Command Overview
        Starting the WCCProxy
        Stopping the WCCProxy
        Killing the WCCProxy
        Getting Help
      4.1 What is the WCCProxy? 
      The WCCProxy is a daemon process that runs all the time, like the WEBES 
      Director Processes and DESTA Commands. After WEBES installation, the 
      WCCProxy appears as a separately installed kit and represents WEBES 
      functionality not developed in the Java environment. The WCCProxy contains 
      required functions that allow WEBES to interact properly with the 
      operating system, other WEBES agent processes, and the Director. The 
      Director will not perform correctly without the WCCProxy. 
      The WCCProxy also is packaged with the ISEE Client kit and is necessary 
      for proper sending of notifications through ISEE. 
      Refer to the WEBES Install Guide section 1.1.3, "The WCCProxy", for more 
      information on the interaction between ISEE, WEBES, and the WCCProxy. 
      Refer to the WEBES Release Notes for any current issues regarding the 
      WCCProxy; how it is shared by WEBES and ISEE, and how WEBES and ISEE 
      should be installed or removed for proper functioning of WCCProxy. 
      The WCCProxy process spawns other CAAgent and WCCAgent processes as 
      needed. Refer to section  3.5 "Troubleshooting an Unresponsive Director" 
      for more operating system specific information on these processes. 
      4.2 Interacting with the WCCProxy 
      The WCCProxy automatically starts along with the system and normally does 
      not require additional attention; however, this chapter explains how to 
      interact with it whenever you must affect its operation for some reason. 
      You interact with the WCCProxy by sending it commands from the command 
      prompt of the system where WEBES is installed. These commands impact all 
      of WEBES and are not limited to only the SEA tool. The WCCProxy commands 
      only affect the WCCProxy process and are not useful for activities such as 
      system configuration, automatic notification, and so on. 
         4.2.1 Permissions 
         4.2.2 Clusters 
        4.2.1 Permissions 
      To run any of the commands described in this chapter, you must be a 
      privileged user as described in Section 2.2. 
        4.2.2 Clusters 
      Even if SEA is installed on a cluster, commands only impact the local 
      node. If you want to modify an entire cluster you must perform the desired 
      operation on each node. 
      4.3 WCCProxy Command Overview 
      WCCProxy commands follow this convention: 
      wccproxy command_verb 

      Where command_verb indicates the action you want to perform (see Table 
      4-1). 
        Table 4-1 Command Verbs--wccproxy 
        +-----------------------------------------------------+

              Verb 
              ----------
              Description 
              ----------

              start 
              Starts the WEBES WCCProxy. Normally this is not necessary, since 
              the WCCProxy automatically is started with the system. It may be 
              necessary to run this command if the WCCProxy was stopped using 
              the stop command. See Section 4.4. 

              status 
              Displays the current status of the WCCProxy process. See Section 
              2.4.1. 

              stop 
              Shuts down the WEBES WCCProxy process and all WCCProxy-connected 
              processes. Be aware that this impacts all WEBES users connected to 
              the system. See Section 4.5. 

              To display help, use "wccproxy help". It displays an overview of 
              the wccproxy command. See Section  4.7.





        +-----------------------------------------------------+




      4.4 Starting the WCCProxy 
      The WCCProxy is automatically started during system startup. Under normal 
      operation, you should not need to manually start the WCCProxy. However, if 
      circumstances require it, you can manually start the WCCProxy by following 
      the instructions for your operating system. 
      HP-UX 
      At a shell prompt, enter: 
      # /usr/sbin/wccproxy start 

      Linux 
      At a shell prompt, enter: 
      # /usr/sbin/wccproxy start 

      OpenVMS 
      At the OpenVMS command line prompt, enter: 
      $ wccproxy start 

      On OpenVMS clusters, you can uses the SYSMAN utility to issue the command 
      do wccproxy start on either all the nodes in the cluster or a specific 
      group of nodes that you choose. 
      Windows 
      To start the WCCProxy, start the WCCProxy service using one of the 
      following methods: 
        In a Command Prompt window, enter either equivalent command:
        C:\>net start wccproxy 

        C:\>wccproxy start 

        Start the WCCProxy service using the Windows Services Manager utility 
        available within the operating system. 
      4.5 Stopping the WCCProxy 
      Under normal operation, you should not need to stop the WCCProxy. However, 
      if circumstances require you to stop the WCCProxy, follow the instructions 
      for your operating system. 
      HP-UX 
      At a shell prompt, enter: 
      # /usr/sbin/wccproxy stop 

      Linux 
      At a shell prompt, enter: 
      # /usr/sbin/wccproxy stop 

      OpenVMS 
      At a prompt, enter: 
      $ wccproxy stop 

      On OpenVMS clusters, you can uses the SYSMAN utility to issue the command 
      do wccproxy stop on either all the nodes in the cluster or a specific 
      group of nodes that you choose. 
      Windows 
      Stop the WCCProxy by stopping the WCCProxy Windows service. You can use 
      any of the following methods: 
        In a Command Prompt window, enter either equivalent command:
        C:\>net stop wccproxy 

        C:\>wccproxy stop 

        Stop the WCCProxy service using the Windows Services Manager utility 
        available within the operating system. 
      If any of the processes associated with WCCProxy (see Section 2.4 Process 
      Monitoring) do not stop using any of the methods listed above, you can 
      kill them with the following command: 
      wccproxy kill 

      4.6 Killing the WCCProxy 
      In certain rare situations, stopping the WCCProxy processes using the stop 
      commands in section 4.5 will not stop all WCCProxy, CAAgent, and WCCAgent 
      processes. In those cases, the "wccproxy kill" command can be used to 
      abort those processes. Follow the instructions in section 4.5, replacing 
      the word "stop" with "kill". See also section  3.5 "Troubleshooting an 
      Unresponsive Director" for more operating system specific information on 
      these processes. 
      4.7 Getting Help 
      You can access different help for the wccproxy command based on your 
      operating system: 
        Linux--man wccproxy and wccproxy help 
        OpenVMS--help wccproxy 
        Windows--wccproxy help 


           ===========================================================================

      5 
      *** SEA Command Line Interface *** 
      This chapter describes the WEBES SEA CLI command (WSEA). 
        Overview
        Conventions
        Command Syntax
        Command Verbs
        Command Parameters
        Analysis
        Translation
        Summary of Events
        Creating New Binary Event Log Files
        Modifying Commands
        Knowledge Rule Sets
        Status Information
        Getting Help
      5.1 Overview 
      The WEBES SEA (wsea) CLI command provides a terminal-based interface for 
      interacting with SEA by issuing commands from the command prompt. 
         5.1.1 Permissions 
         5.1.2 Clusters 
         5.1.3 The CLI and the Director 
        5.1.1 Permissions 
      To run any of the commands described in this chapter, you must be a 
      privileged user as described in Section 2.2. 
        5.1.2 Clusters 
      Even if SEA is installed on a cluster, commands only impact the local 
      node. If you want to modify an entire cluster you must perform the desired 
      operation on each node. 
        5.1.3 The CLI and the Director 
      The Director does not need to be running for every CLI command. The 
      following CLI functions are possible without the Director: 
        Manual Analysis 
        Translation 
        Summary Report 
        Create New Binary Log File 
        List Registered Rule Sets 
        Register/Unregister Rule Sets 
        Change or View Syntax 
        Reset the Automatic Analysis Database 
        View the Status Information 
      Since these operations do not use the Director, messages that would 
      otherwise be written to the Director's log files are included in the 
      output for the command. The messages shown remain subject to the logging 
      level. See Section 2.5 for more information on log messages. 
      5.2 Conventions 
      The CLI commands in this manual follow these conventions: 
              Bold Used for entries and commands where information is typed at 
              the keyboard as it appears in the document 
              Italics Information that varies depending on your requirements. 
              For example, inputfile indicates that you should enter the actual 
              name of the file you want to process. 
              [] Optional entries. Values in square brackets are not required 
              and in most cases pertain to input files, output files, and 
              filtering options. 
              | Mutually exclusive entries. A vertical bar separates entries 
              where you only can choose one. 




      5.3 Command Syntax 
      You can perform some of the same SEA operations using more than one 
      command variation, or syntax, and you can switch among the different 
      syntaxes at any time: 
        New common syntax (the default after install) 
        Old common syntax 
        OpenVMS DECevent emulation 
      This chapter describes the new common syntax, which supports all SEA 
      functions and is the default after installation. For reference, the older 
      syntaxes are detailed in Appendix E. 
      To use a syntax other than the current default, you must include a syntax 
      designator in the command (see Table 5-1). 
        Table 5-1 wsea Syntax Designators 
        +-----------------------------------------------------+

              Syntax 
              ----------
              Designator 
              ----------
              Example 
              ----------

              New common syntax 
              n 
              wsea or wsea n1 

              Old common syntax 
              x 
              wsea x 

              DECevent emulator 
              (OpenVMS) 
              v 
              wsea v 



               1  The new common syntax is the default after install, so the "n" 
              is not required unless the default is changed. 

        +-----------------------------------------------------+




         5.3.1 Showing the Default Syntax 
         5.3.2 Changing the Default Syntax 
        5.3.1 Showing the Default Syntax 
      To show the current default syntax, issue the following command: 
      wsea syntax 

        5.3.2 Changing the Default Syntax 
      The new common syntax is the default when SEA is installed, so any new 
      common syntax commands do not initially require the "n" designator. 
      To use another syntax without needing a designator, change the default 
      with the following command plus a designator from Table 5-1: 
      wsea syntax syntax_designator 

      Afterwards, UNIX DECevent emulator commands no longer need the "u" 
      designator, but new common syntax commands now require the "n" designator. 

      Impact on Other Users 
      Changing the default affects all users logged onto a system, so it can 
      impact your session if someone else changes the default without telling 
      you. 
      When there are multiple users logged onto a system, you can play it safe 
      and avoid confusion by always including the designator whenever a command 
      is available in multiple syntaxes (regardless of what you think the 
      current default may be). 
      5.4 Command Verbs 
      Some wsea commands are supported by multiple syntaxes, some only are 
      supported by the new common syntax, and some are syntax independent. 
        Syntax-specific commands follow this convention: 
        wsea syntax_designator command_verb 

        Syntax-independent commands do not use a syntax designator, regardless 
        of what the default syntax is: 
        wsea command_verb 

      Table 5-2 provides an overview of the wsea command verbs available in the 
      new common syntax. 
      If you enter the wsea command without any command verb or parameters, SEA 
      defaults to translating the system event log and sending the output to the 
      screen. 
        Table 5-2 Command Verbs--wsea (New Common Syntax) 
        +-----------------------------------------------------+

              Verb1 
              ----------
              Description 
              ----------

              ana 
              (analyze) 
              Analyzes one or more binary event logs. See Section 5.6.2 for 
              details. 

              aut 
              (autoanalysis) 
              Turns automatic analysis on or off. See Section 5.6.1.5 for 
              details. 

              bin 
              (binary) 
              Applies a filter to an existing binary event log and creates a new 
              binary event log containing the subset of events returned after 
              filtering. The bin command verb also can be used to merge existing 
              binary event logs. See Section 5.9 for details. 

              help 
              Displays a text-based help file for the wsea command. 

              lis 
              (listrk) 
              Lists the registered analysis rule sets. See Section 5.11 for 
              syntax information and Chapter 9 for details on rule sets. 

              reg 
              (regknw) 
              Registers one or more analysis rule sets for use during automatic 
              and manual event analysis. See Section 5.11 for syntax information 
              and Chapter 9 for details on rule sets. 

              res 
              (reset) 
              Resets the automatic analysis database. See Section 5.6.1.4 for 
              syntax information and Chapter 8 for details on analysis. 

              sta 
              (status) 
              Displays system information such as the software version, 
              obligation information, and notification status. See Section 5.12 
              for details. 

              sum 
              (summarize) 
              Returns a summary of all the events contained in a binary event 
              log. See Section 5.8 for details. 

              tes 
              (test) 
              Simulates automatic analysis. See Section 5.6.1.3 for syntax 
              information and Chapter 8 for details on analysis. 

              tra 
              (translate) 
              Translates one or more binary event logs, but does not analyze the 
              events. See Section 5.7 for details. 

              unr 
              (unregknw) 
              Unregisters one or more analysis rule sets so they are no longer 
              considered during automatic and manual event analysis. See Section 
              5.11 for syntax information and Chapter 9 for details on rule 
sets.



               1  The new common syntax allows abbreviations. You only need to 
              enter the minimum number of characters required to uniquely 
              identify the command (generally, the first three letters of a 
              command verb). The full command verb is shown in parenthesis. 

        +-----------------------------------------------------+




      Table 5-3 describes the commands that are syntax independent and do not 
      take a syntax designator, regardless of what the default syntax is. 
        Table 5-3 Command Verbs--wsea (Syntax Independent) 
        +-----------------------------------------------------+

              Verb 
              ----------
              Description 
              ----------

              log 
              Toggles the logging to a file of automatically generated problem 
              reports on or off. See Section 5.6.1.2 for details. 

              report 
              Displays the active problem reports generated from automatic 
              analysis. See Section 5.6.1.1 for details. 

              sicl 
              Toggles on or off the SEA System Initiated Call Logging (SICL) 
              feature, which automatically log calls with HP Services if DSNLink 
              is installed on the system. See Section 3.10.1 for syntax 
              information and Section 11.4 for details. 

              This command is being phased out and replaced by the desta sicl 
              command. 

              syntax 1 
              Shows the current default syntax or changes the default syntax for 
              CLI commands. Once you have changed the default, you no longer 
              need to include a syntax designator for commands that use the 
              chosen syntax. See Section 5.3.2 for details. 



               1  This syntax-independent command sometimes involves a syntax 
              designator, but only because it needs one in order to set the 
              default. In spite of that, the command is not an embedded part of 
              any of the available syntaxes and must still be considered syntax 
              independent. 

        +-----------------------------------------------------+




      5.5 Command Parameters 
      With the new common syntax, command parameters can be abbreviated. You 
      only need to enter the minimum number of characters required to uniquely 
      identify the parameter. For example, input can be abbreviated as inp, and 
      outhtml can be abbreviated as outh. 
      Parameters specify binary log files for processing, designate output 
      files, and create filters. In most cases, SEA allows you to specify 
      parameters in any order (the new common syntax sum command is an 
      exception, see Section 5.8 for details). For example, the following 
      commands using the new common syntax are equivalent: 
      wsea tra inp myinput.zpd out myoutput.txt index=start:10 brief 
      wsea brief index=start:10 out myoutput.txt inp myinput.zpd tra 

      Notice that even the placement of the command verb (tra in this case) may 
      be changed. 
      5.6 Analysis 
      SEA applies rules (see Section 5.11 Knowledge Rule Sets) that interpret 
      error log contents and create meaningful problem reports--reports 
      containing valuable analysis beyond a simple translation of log contents 
      into a readable format. (SEA can perform translation as well, as described 
      in Section 5.7 Translation) 
         5.6.1 Automatic Analysis 
         5.6.2 Manual Analysis 
      For a detailed description of analysis and the problem reports generated 
      by analysis, see Chapter 8. In addition, Appendix  shows an example of a 
      report generated by analysis. 
        5.6.1 Automatic Analysis
      With the Director installed, automatic analysis of the system event log 
      starts whenever you start your system. Because of this, SEA automatically 
      analyzes events in the log file and generates reports as events occur. 
      The wsea command lets you interact with automatic analysis functions, 
      including viewing the reports generated by automatic analysis and saving 
      them to a file. 
         5.6.1.1 Viewing Automatic Analysis Reports 
         5.6.1.2 Logging Automatic Analysis Reports 
         5.6.1.3 Simulating Automatic Analysis 
         5.6.1.4 Resetting Automatic Analysis Results 
         5.6.1.5 Disabling and Enabling Automatic Analysis 
          5.6.1.1 Viewing Automatic Analysis Reports 
      To view the active problem reports generated by automatic analysis, use 
      the report command: 
      wsea report [outtext | outhtml outputfile] 

      Reports can be viewed on screen or saved to a file. If you do not include 
      any output file parameter, the reports appear on screen. See Section 
      5.10.2 for more information about working with output files. 
          5.6.1.2 Logging Automatic Analysis Reports 
      You can tell SEA to automatically log generated problem reports into a 
      \specific\ca\logs\prob.log file with the following command: 
      wsea log prob on | off 

      If a prob.log file already exists, new data from subsequent logging 
      operations gets appended into the existing file. If you delete the 
      prob.log file, SEA creates a new one as of the next logging operation. 
          5.6.1.3 Simulating Automatic Analysis 
      You can simulate automatic analysis with the following command: 
      wsea tes[t]

      The command tests automatic analysis and the system's error logging 
      facilities. See Section 8.7 for more information on simulating automatic 
      analysis. 
          5.6.1.4 Resetting Automatic Analysis Results 
          *** Note ***


            Resetting can significantly impact the results of future analysis. 



      The following command clears the automatic analysis database (only 
      available in the new common syntax): 
      wsea res 

      The command removes any currently active callouts and any stored analysis 
      data such as thresholding information. The FRU configuration data and the 
      marker of the most recently analyzed event are not removed. 
      Section 8.3.2 contains additional detail about resetting the automatic 
      analysis results and the impact that resetting can have on future analysis 
      results. 
          5.6.1.5 Disabling and Enabling Automatic Analysis 
      To enable or disable automatic analysis, use the following command: 
      wsea auto [on | off] 

      The parameter "auto" can be shortened to "aut". 
      If the automatic analysis process is busy when you issue the wsea auto off 
      command, the command will not take effect until the analyzer has finished 
      processing events already in its queue. If desired, you can force the 
      command to take effect immediately by stopping and restarting the Director 
      (see Sections 3.8 and  3.7). 
      The wsea auto on command takes effect immediately. 
      Automatic analysis is enabled by default, but you may want to disable it 
      if SEA is running on a platform such as HP-UX or Linux, where a native 
      error log is not currently analyzed. 
      You can verify that automatic analysis is enabled by issuing the wsea test 
      command and observing the Real Time Monitoring display in the web 
      interface (see Section 7.4.4.1). 
        5.6.2 Manual Analysis 
      Manual analysis is the user-initiated process of selecting a binary event 
      log file for immediate processing using either the CLI command or the web 
      interface (see Chapter 7). 
      The wsea ana command performs manual analysis as well as filtered manual 
      analysis on a binary event log file, which can be the system event log, 
      another log from the same system, or a log from a different system: 
      wsea ana
      [input inputfile]
      [out | outhtml outputfile]
      [notify [OS | CUSTOMER | PROVIDER | WUI | CLI | AUI | VISIBLE | EVERY]]

      Filtered Manual Analysis--It is possible to create a tailored log file 
      using filters (see Section 5.9 Creating New Binary Event Log Files) and 
      then manually analyze the new file; however, be aware that this can result 
      in incomplete or invalid analysis due to missing data that was filtered 
      out. 
      To perform manual analysis with another syntax, see Appendix E. 
      Input Files 
      By default, manual analysis processes the system event log. If you want to 
      process a different binary log file, you must use the input keyword and 
      specify the input file. See Section 5.10.1 for more information on input 
      files. 
      Notify 
      Notification options are defined as follows: 
        OS - Operating System ("Indictment"). 
        As of the current release of WEBES, only Alpha operating systems 
        (OpenVMS Alpha) recognize indictments.
        CUSTOMER - Customer email, pager, etc., as set up during installation. 
        As of the current release of WEBES, SNMP (HP SIM), DTCS, MOM, SMTP 
        notification is included in this type of notification.
        PROVIDER - Service provider's support organization set up during WEBES 
        installation. 
        As of the current release of WEBES, the provider notification types 
        include ISEE, OSEM (formerly PRS CSG/QSAP now retired), SNMP (HP SIM), 
        DTCS, MOM, VMSMAIL and SICL/ACHS/DSNlink (now retired) only. The 
        notification types that are enabled for automatic analysis are the ones 
        that will be used for notification if this channel is specified.
        WUI - Web User Interface (browser).
        CLI - Command Line Interface (user's console - the default if the notify 
        command is not used).
        AUI - All User Interfaces (WUI and CLI).
        VISIBLE - All visible notification channels, that is, every channel 
        except OS.
        EVERY - All notification channels.
      If "notify" is used, one and only one of the above options must be used 
      immediately after it on the command line. 
      Notification options may be abbreviated to uniqueness. For example, "O" 
      may be used instead of "OS"; "CU" may be used instead of "CUSTOMER" etc., 
      Notification and analysis mode information is now displayed in all problem 
      reports. See Appendix A.1 for a sample problem report. The information is 
      positioned above the SEA and WCC Version sections of the report. 
      The command line options correspond to the notification information on the 
      problem report as follows: 
        OS - OS
        CUSTOMER - Customer
        PROVIDER - Support
        WUI - Browser
        CLI - Console
        AUI - AllUserInterfaces
        VISIBLE - Visible
        EVERY - All
      For the CUSTOMER, PROVIDER, VISIBLE, and EVERY flags, a problem report 
      will ONLY be sent to the customer or provider notification types (SMTP, 
      ISEE, QSAP (PRS), and SICL (DSNlink)) that are enabled for automatic 
      analysis. In other words, if the customer has enabled SMTP and ISEE 
      notification, but not QSAP or SICL notification, then CUSTOMER sends 
      notification to SMTP only, PROVIDER sends notification to ISEE only, and 
      VISIBLE and EVERY sends both SMTP and ISEE notifications (among other 
      types of notifications). If the user disables SMTP notifications with the 
      "desta smtp off" command, then the CUSTOMER option will have no effect, 
      and email will not be sent using the VISIBLE or EVERY options either. If 
      the user has no provider notifications enabled (ISEE, QSAP, or SICL), then 
      the PROVIDER option will have no effect, and HP Services will not be 
      notified using the VISIBLE or EVERY options either. 
      For more information on notifications, see Chapter 11 Automatic 
      Notifications. For commands on how to enable/disable notifications, see 
      Section 3.10 Automatic Notifications. 
      Output Files 
      By default, output from manual analysis is displayed on the screen. To 
      save output to a file, use either the out or the outhtml keyword and 
      provide a file name. See Section 5.10.2 for more information on output 
      files. 
      5.7 Translation 
      You can translate, or decompose, the events in a binary event log into a 
      readable format using the translate command. Translation operates in 
      manual mode, meaning you must enter the command every time you want to 
      perform translation: 
      wsea tra [input inputfile] [out | outhtml outputfile] [filterstatement] 
      [brief | full] 

      For a detailed description of translation, see Chapter 8. In addition, 
      Appendix  shows examples of translated events. 
      To perform translation with another syntax, see Appendix E. 
      Input Files 
      By default, translation processes the system event log. If you want to 
      process a different binary log file, you must use the input keyword and 
      specify the input file. See Section 5.10.1 for more information on input 
      files. 
      Output Files 
      By default, output from translation is displayed on the screen. To save 
      output to a file, use either the out or the outhtml keyword and provide a 
      file name. See Section 5.10.2 for more information on output files. 
      Filtering Log Files 
      You can identify a subset of the events from a binary event log file that 
      you want to translate by defining a filter. For more information on 
      filtering, see Section 5.10.3. 
      Report Type 
      You can specify either brief or full output for translation. See Section 
      8.2.3 for more information on the report types. The examples in Appendix  
      show the difference between full and brief output. 
      5.8 Summary of Events 
      The CLI can show you a summary of the events contained in a binary log 
      file: 
      wsea sum [index] [input inputfile] [out | outhtml outputfile] 
      [filterstatement] 

      Correctable events are not shown. Section 8.8 tells how to interpret the 
      summary and describes circumstances that can cause unexpected summary 
      output. 
      To generate a summary with another syntax, see Appendix E. 
      Indexed Output 
      By default, SEA creates a tallied list of all the events in the binary 
      event log files. However, you can generate an indexed list by adding the 
      index parameter. 
      If you want indexed output, the index parameter must immediately follow 
      the sum command verb. Otherwise, SEA assumes you are using an "index" 
      filter keyword instead. 
      Input Files 
      By default, the summary command processes the system event log. If you 
      want to process a different binary log file, you must use the input 
      keyword and specify the input file. See Section 5.10.1 for more 
      information on input files. 
      Output Files 
      By default, output from the summary command is displayed on the screen. To 
      save output to a file, use either the out or the outhtml keyword and 
      provide a file name. See Section 5.10.2 for more information on output 
      files. 
      Filtering Log Files 
      You can identify a subset of the events from a binary event log file that 
      you want to view a summary report for by defining a filter. For more 
      information on filtering see Section 5.10.3. 
      Examples 
      Standard (tallied) output: 
      /opt/hp/svctools/common/ca/examples/gs320_system_events.sys
      Qty Type Description
      ---------------------------------------------------------------
      1 32 VMS Cold Start (i.e. System Boot) Message
      1 65 VMS Volume Dismount Message
      2 64 VMS Volume Mount Message
      1 1096 VMS IDE Disk Event
      1 38 VMS Time Stamp Message
      6 686 Non-Fatal Environmental Event
      1 37 VMS Crash Restart Event
      1 110 Configuration Event
      Total Entry Count: 14
      First Entry Date: Tue 9 May 2000 12:16:17 GMT-05:00
      Last Entry Date: Tue 9 May 2000 12:26:17 GMT-05:00

      Indexed output: 
      /opt/hp/svctools/common/ca/examples/gs320_system_events.sys
      Index Type Description Date/Time
      ------ ------ ------------------------------------------------------ 
      1 110 Configuration Event 05/09/00 12:16:17 -05
      2 65 VMS Volume Dismount Message 05/09/00 11:06:31 -05
      3 37 VMS Crash Restart Event 05/09/00 11:06:49 -05
      20 32 VMS Cold Start (i.e. System Boot) Message 05/09/00 12:15:39 -05
      21 64 VMS Volume Mount Message 05/09/00 12:15:39 -05
      22 1096 VMS IDE Disk Event 05/09/00 12:16:13 -05
      23 64 VMS Volume Mount Message 05/09/00 12:17:35 -05
      24 686 Non-Fatal Environmental Event 05/09/00 12:19:11 -05
      25 686 Non-Fatal Environmental Event 05/09/00 12:19:12 -05
      26 686 Non-Fatal Environmental Event 05/09/00 12:19:44 -05
      27 686 Non-Fatal Environmental Event 05/09/00 12:19:48 -05
      28 686 Non-Fatal Environmental Event 05/09/00 12:19:54 -05
      29 686 Non-Fatal Environmental Event 05/09/00 12:24:39 -05
      30 38 VMS Time Stamp Message 05/09/00 12:26:17 -05

      5.9 Creating New Binary Event Log Files 
      You can filter the contents of existing binary event logs into a new log 
      file containing a subset of the events from the originals. When you create 
      the new log, SEA checks the events in the originals against the filter 
      statement, and only events that pass the filter get added to the new file: 

      wsea bin [input inputfile(s)] out outputfile [filterstatement] 
      [skipconfig] 

      The newly created binary event log file can be used for analysis, 
      translation, or any other SEA operation; however, be aware that analysis 
      may produce incomplete or invalid results due to missing data that was 
      filtered out. 
      To create a new binary event log file with another syntax, see Appendix E. 

      Input Files 
      By default, the system event log is used as the input file. If you want to 
      process a different binary log file or files, you must specify the input 
      file location and name. See Section 5.10.1 for more information on working 
      with input files. 
      Multiple Input Files--You can specify multiple input files to merge into a 
      single binary log (in which case filtering occurs for each input file 
      before the events are written to the new file). If you merge files, 
      however, be aware that SEA does not remove duplicate events. 
      Output Files 
      You must specify a file name and location where the new binary output file 
      will be saved. The output file parameter is mandatory when you are 
      creating a new binary event log file. 
      Filtering Log Files 
      You can identify a subset of the events from a binary event log file that 
      you want to include in the new log file by defining a filter. If you do 
      not define a filter, the new log file will contain all the events in the 
      existing log file. For more information on filtering see Section 5.10.3. 
      Skipping Configuration Entries 
      If you are using the new common syntax, you can keep configuration entries 
      from being automatically inserted by adding the skipconfig parameter to 
      your command. This parameter prevents configuration entries from the 
      original log files that are needed for analysis from being inserted into 
      the new log file if they would normally be filtered out. 
      5.10 Modifying Commands 
      By default, the analysis, translation, summary, and new binary log file 
      commands all process the system event log. In addition, the output from 
      analysis, translation, and summary commands is displayed on screen by 
      default. 
      You can change the defaults in order to process other binary log files or 
      to save the results to a file. When performing translation, summary, 
      analysis, or creating a new binary log file, you can further restrict the 
      events that are processed by filtering the binary log file used for input. 

         5.10.1 Input Files 
         5.10.2 Output Files 
         5.10.3 Filtering 
        5.10.1 Input Files 
      Many commands in manual mode enable you to specify an input binary event 
      log file: 
      input filename 

      Where filename indicates the path and name of the input file. The 
      following guidelines apply: 
        Specifying an input file is optional. If you do not specify either a 
        directory or a file, SEA processes the binary system event log, for 
        example: 
        wsea ana 

        Relative directory paths are allowed. If the current directory is 
        C:\Program Files\hp\svctools\common\ca, and you want to analyze 
        C:\Program 
        Files\hp\svctools\common\ca\examples\memory_channel_adapter.errlog, you 
        can enter: 
        wsea ana input examples\memory_channel_adapter.errlog

        If you specify a directory but no file name, SEA processes all files 
        with .errlog, .sys, .zpd, or .evt extensions in that directory: 
        wsea analyze input examples

        Multiple filenames are allowed when separated by a comma and space: 
        wsea ana input examples\memory_channel_adapter.errlog, 
        examples\disk_read_errors.errlog

        Wildcards are allowed. For example, here all files in the samples 
        directory with a name that starts with "ds" and the .errlog extension 
        are analyzed: 
        wsea ana input samples\ds*.errlog

        5.10.2 Output Files 
      With many commands, you can save the results of processing to a file 
      rather than viewing the output on screen. (These guidelines do not apply 
      when creating a new binary event log as described in Section 5.9. New 
      binary event logs always require an output file name.) 
      To send the output of an operation to a file, use one of the following 
      parameters: 
      out filename 
      outhtml filename 

      The out parameter creates a text output file and the outhtml parameter 
      creates a HTML output file. The filename indicates the path and name where 
      you want to save the output: 
      wsea ana out results.txt 
      wsea ana outhtml results.html 

        5.10.3 Filtering 
      The tra, sum, bin, and ana commands enable you to filter a binary event 
      log file and only process a subset of the events. The following general 
      rules apply when you use filters: 
        Multiple filter statements are allowed when separated by a comma and 
        space. 
        Abbreviations are allowed for filter parameters. You only need the 
        minimum number of letters to uniquely identify a parameter. For example, 
        index could be abbreviated as ind.
        On Windows systems, any argument that includes a comma must be enclosed 
        in quotation marks. This includes arguments that contain a date. 
      Table 5-4 lists the filtering statements available with the new common 
      syntax. 
        Table 5-4 Filtering Statements (New Common Syntax) 
        +-----------------------------------------------------+

              Filter Statement
              ----------
              Description
              ----------

              begin="date" 
              since="date" 
              end="date" 
              Filters based on the time the event occurred. No events that 
              occurred before the given start time or after the given end time 
              are processed. 
              The date can be entered in any format supported by Java (for 
              example, dd-mmm-yyyy,hh:mm:ss). You do not need to include the 
              time (hh:mm:ss) with the date. 
              Be aware of the following additional guidelines:

                The begin and since statements are equivalent. 
                You can use the keywords YESTERDAY and TODAY. 
                With the begin and since keywords, you can enter a negative 
                integer value to process based on a relative date. For example, 
                entering -3 processes events from the last three days. 

              include=keyword 
              exclude=keyword 
              Filters based on the numeric entry type. You must enter a keyword 
              rather than the actual entry type. See Table 5-5 for supported 
              keywords. 

              node=name 
              Filters based on the node responsible for generating the event. 
              The name argument is case sensitive. 

              index=nn 
              index="start:nn, end:nn" 
              Filters based on the event's position in the event log. The first 
              event in the file is event index 1. 

              reverse
              Processes the events in reverse order according to the event index 
              number. 





        +-----------------------------------------------------+




        Table 5-5 Event Type Keywords (New Common Syntax) 
        +-----------------------------------------------------+

              Keyword 
              ----------
              Description 
              ----------

              mchk 
              All machine check events. 

              cam 
              All SCSI entries logged by the CAM logger (199). 

              configurations 
              Configuration entries (110). 

              control_entries 
              System startup entries or new error log creation entries (32, 35, 
              300). 

              environmental_entries 
              Power entries (mchk-env). 

              swxcr 
              Entries logged by SWXCR (198). 

              machine_checks 
              mchks 
              Events with machine checking information (mchk). 

              operating_system=value 
              os=value 
              Events with a specific operating system type. The value parameter 
              indicates the numeric code for the desired operating system. 

              panic
              Crash restart, system panic, or user panic entries (37, 302). 

              software_informationals 
              swi 
              Events with lastfail, system startup, or system configuration 
              information (volume mounts, volume dismounts, new error logs, 
              timestamp entries) (32, 35, 37, 38, 39, 64, 65, 250, 300, 301, 
              310). 

              mchk_sys 
              All system machine check events. 

              mchk_cpu 
              All cpu machine check events. 

              mchk_env 
              All environmental machine check events. 





        +-----------------------------------------------------+




      Examples 
      Only process events from the system ComputerName: 
      wsea tra node=ComputerName 
      wsea sum node=ComputerName 
      wsea bin input inputfile.zpd out outputfile.bin node=ComputerName 

      Only process events that occurred before 8:33:57 PM on January 31, 2000: 
      wsea tra end="31-Jan-2000,20:33:57"
      wsea sum end="31-Jan-2000,20:33:57"
      wsea bin input inputfile.zpd out outputfile.bin end="31-Jan-2000,20:33:57"

      Only process CPU machine check and system machine check events (the 
      translation command presents the output in reverse chronological order): 
      wsea tra include="mchk_cpu, mchk_sys reverse"
      wsea sum include="mchk_cpu, mchk_sys"
      wsea bin input inputfile.zpd out outputfile.bin include="mchk_cpu, 
      mchk_sys"

      Only processes events beginning with the fifteenth event in the log file: 
      wsea tra index=start:15
      wsea sum index=start:15
      wsea bin input inputfile.zpd out outputfile.bin index=start:15

      5.11 Knowledge Rule Sets 
      SEA uses rule sets to create the meaningful output generated by analysis. 
      Events from the binary log file are compared against the rules, and the 
      result of this operation provides the content for any problem reports that 
      must be generated. The following new common syntax commands manage rule 
      sets: 
      wsea lis 

      Lists the registered rule sets used by analysis (see Section 9.3.1 for 
      more information). 
      wsea reg 

      Registers the rule sets used by analysis (see Section 9.3.2 for more 
      information). 
      wsea unr 

      Unregisters the rule sets used by analysis (see Section 9.3.2 for more 
      information). 
      To manage rule sets using the old common syntax, See Appendix E. 
      5.12 Status Information 
      The new common syntax provides a command to show version, service 
      obligation, and notification status: 
      wsea sta 
      System Event Analyzer for Linux V4.4.4 (Build 31)
      Service Tools Home: /usr/opt/hp/svctools
      Service Obligation Start Date: Tue Dec 13 08:44:27 PST 2005
      Service Obligation End Date: Wed Dec 13 08:44:27 PST 2006
      OSEM/CSG/QSAP notification: enabled.
      ISEE notification: disabled.
      MOM notification: disabled.
      SNMP notification: disabled.
      DTCS notification: disabled.
      SMTP notification: enabled.
      LOG notification: enabled.
      VMSMAIL notification: disabled.

      5.13 Getting Help 
      You can access different help for the desta command based on your 
      operating system: 
        UNIX variants--man wsea and wsea help 
        OpenVMS--help wsea and wsea help 
        Windows--wsea help 
      Help also is available through this user guide, which is installed in 
      HTML, Adobe Acrobat PDF, and text formats available from the following 
      directory: 
        HP-UX--/opt/hp/svctools/common/ca/docs 
        Linux--/usr/opt/hp/svctools/common/ca/docs 
        OpenVMS--SVCTOOLS_HOME:[COMMON.CA.DOCS] 
        Windows--C:\Program Files\hp\svctools\common\ca\docs 
        (or Start | Programs | Hewlett-Packard Service Tools | System Event 
        Analyzer | SEA User Guide) 
      The text version does not include graphics and formatting available in the 
      other formats, and usually is used only when the other formats cannot 
      easily by viewed, such as at a terminal prompt. 
      The SEA web interface also includes a link to the HTML version of this 
      user guide as described in Section 7.10. 
      wsea sum [other params] all 



          ===========================================================================

      7 
      *** Web Interface *** 
      This chapter describes how to access and use the SEA web interface. 
        About the Web Interface
        Starting the Web Interface
        Using The Web Interface
        Customizing the Navigation Tree
        Processing Log Files
        Creating New Log Files
        Creating Storage Cell Spreadsheets
        Applying Filters
        Modifying Settings
        Getting Help
        Logging Off
        Service Obligation
        Managed Entities
      7.1 About the Web Interface 
      The web interface provides browser-based access to SEA. You can use the 
      web interface to connect to the Director on your local system or on remote 
      systems and analyze and translate their binary event log files. 
        7.1.1 About Translation
      Event information in the system event log is stored in binary format. 
      Translation is the process of converting this binary data into readable 
      text. The web interface does not automatically perform translation; each 
      event that you want to translate must be manually selected. 
        See Section 7.5 for more information on how the web interface presents 
        translation information.
        See Chapter 8 for more information on translation, interpreting 
        translated events, and default translation settings.
        7.1.2 About Analysis
      Information from a binary event log file can be used to detect hardware 
      failures on the system. The process of reading binary event log files, 
      interpreting events, and creating problem reports with proposed 
      resolutions is called analysis. 
      As the system writes events to the binary event log file, SEA processes 
      each event according to the registered rule sets. The rule sets contain 
      the information necessary to interpret events. Then, when an event matches 
      the conditions described in the rule sets, SEA creates a problem report 
      containing information about the event and proposed resolutions. 
      The web interface can perform both automatic and manual analysis. 
        See Section 7.5 for more information on how the web interface presents 
        analysis information.
        See Chapter 8 for more information on analysis and its results.
          7.1.2.1 Automatic Analysis
      When the Director is started, SEA initiates automatic analysis. In 
      automatic mode, SEA continuously monitors the binary system event log and 
      processes events as they arrive. Problem reports are generated as 
      necessary. 
      For more information about automatic analysis operations and output, see 
      Chapter 8. 
          7.1.2.2 Manual Analysis
      Manual analysis also compares the events from log files to the registered 
      rule sets and generates problem reports. However, unlike automatic 
      analysis, you must manually select each binary event log file you want to 
      process. 
      For more information about manual analysis operations and output, see 
      Chapter 8. 
        7.1.3 Automatic Notifications 
      SEA can send the results of automatic analysis to email addresses or HP 
      Services. See Chapter 11 for more information on automatic notifications. 
        7.1.4 Create New Binary Log File
      You can filter the contents of existing binary event logs and create a new 
      binary event log file containing a subset of the events from the 
      originals. When you create a new binary log file, SEA checks the events in 
      the original binary event log file (input file) against the filter 
      statement. All the events that meet the criteria specified by the filter 
      statement are added to the new binary event log file (output file). The 
      new binary event log file can then be used for analysis, translation, or 
      any other SEA process. 
      For more information on using the web interface to create a new binary 
      event log file, see Section 7.6. 
      7.2 Starting the Web Interface 
      It is not necessary to have the Director running on your system in order 
      to use SEA. In fact, WEBES need not be installed on the browser's system 
      at all. However, WEBES must be installed and the Director must be running 
      on the target system in order to connect to its SEA system. Therefore, 
      before using the web interface, you must ensure the Director is started on 
      the target system. 
      For additional information about supported browsers and configuring your 
      browser for SEA, see Appendix C. 
      Accessing the Web Interface 
        Start the Director on the system you want to connect to, if it has not 
        been started already (see Section 3.7). 
        Start your web browser.
        Enter the URL of the target system to connect to it.
          If you are connecting to a remote host, enter:
          http://target.sys.name.here:7902 

          If you are connecting to the local system, enter:
          http://localhost:7902 

          In some network configurations, the name localhost may not be 
          recognized. Enter the system's hostname or its IP address (such as 
          http://12.34.56.78:7902) instead. 
          If you are using Internet Explorer, be sure to include the http://.
        Enter the profile name you want to use in the Logon window (Figure 7-1) 
        and Click the Logon button or press Enter. See Section 10.5 for more 
        information on profiles.
        Figure 7-1 Logon Window
      Although you must log on to SEA, the logout process is automatic. See 
      Section 7.11 for a description of the automatic logout process. 
      7.3 Using The Web Interface 
      After you log on, the browser displays the web interface main screen 
      (Figure 7-2). 
      Figure 7-2 Main Screen
      Note that the value of the URL field includes the hostname for the system 
      you logged into, as well as your username, indicating the current profile. 

      http://hostname:7902/?profile=username

      *** Tip ***


        If you need to change profiles while using SEA, you can edit your 
        browser's URL field by replacing the current profile username with a 
        different one.



      The components of the web interface display are described in Table 7-1. 
        Table 7-1 Web Interface Components 
        +-----------------------------------------------------+

              Component
              ----------
              Description
              ----------

              Title Bar
              Shows the software version, active profile, and operating system.

              Toolbar
              By default, provides access to the on-line help, system 
              configuration, processing statistics, and new binary error log 
              creation. The toolbar is dynamically updated, and additional 
              features are available with some SEA screens. See Section 7.3.1 
              for more information.

              Navigation Tree
              Lists the available groups, nodes, storage cells, categories, and 
              log files.

              Display Frame
              Displays interactive screens and system information. When SEA 
              loads, the display frame shows product information.

              Information Bar
              Displays messages from the browser and usage tips. See Section 
              7.10.1 for more information on the web interface's usage tips.





        +-----------------------------------------------------+




      *** Note ***


        SEA allows you to work in multiple browser windows. If you are using the 
        same profile, the navigation trees in all the windows will automatically 
        synchronize.



        7.3.1 Toolbar
      Figure 7-3 shows the default web interface toolbar. 
      Figure 7-3 Toolbar
      The toolbar buttons update dynamically depending on what you are doing. 
      Table 7-2 describes the toolbar commands that are always available: 
        Table 7-2 Toolbar--Default Buttons
        +-----------------------------------------------------+

              Component
              ----------
              Description
              ----------

              Help Button
              Opens a new browser window containing the on-line user guide. See 
              Section 7.10 for more information on getting help.

              Settings Button
              Opens the settings screen. See Section 7.9 for more information on 
              changing the settings.

              Progress Window Button
              Opens a new browser window that reports the processing status of 
              log files. See Section 7.5.2 for more information on processing 
              status.

              New Binary Log Button
              Opens the New Binary Log screen in the display frame. See Section 
              7.6 for more information on creating a new binary log file.





        +-----------------------------------------------------+




      The following buttons also may appear in the toolbar, depending on the 
      feature being used: 
        Table 7-3 Toolbar--Dynamic Buttons
        +-----------------------------------------------------+

              Component
              ----------
              Description
              ----------

              Clear Results Button
              Available when viewing automatic analysis details. See Figure 
              7-19, Clear Results Button for more information.

              Reprocess File Button
              Available when viewing manual analysis details. See Figure 7-19, 
              Reprocess File Button for more information.

              Analyze File Button
              Available when viewing manual translation details. See Figure 
              7-19, Analyze File Button for more information.

              Analyze Filtered Events Button
              Available after processing a file with a filter applied. See 
              Figure 7-19, Analyze Filtered Events Button for more information.

              Generate Storage Spreadsheet Button
              Available when viewing Real-Time Monitoring of a Storage Cell. See 
              Figure 7-19, Generate Storage Spreadsheet Button for more 
              information.





        +-----------------------------------------------------+




        7.3.2 Navigation
      Using SEA, it is possible to monitor the binary event log files generated 
      by a wide variety of computers all from a single web interface. In order 
      to simplify the process of monitoring these diverse information sources, 
      the web interface uses a hierarchical navigation tree composed of groups, 
      nodes, storage cells, categories and binary event log files. 
          7.3.2.1 Navigation Tree Hierarchy
      The entries in the navigation tree are as follows: 
      Figure 7-4 Navigation Tree - Hierarchy
        Table 7-4 Navigation Tree - Hierarchy
        +-----------------------------------------------------+

              Folder
              ----------
              Description
              ----------

              Groups
              Multiple computers that are logically associated. Groups contain 
              one or more nodes.

              Nodes
              Individual computers. Each node contains two types of log files: 
              System Log and Other Logs.

              System Log 
              The binary system event log where the computer writes system 
              information. By default, the System log contains Real Time 
              Monitoring and Full View.

              Real Time Monitoring 
              Automatic analysis results.

              Full View
              Manual analysis results for the system event log.

              Other Logs 
              Any other binary event log files saved on the computer. These can 
              include old files, files from other systems, and examples. 
              Optionally, the other logs can be further divided by categories 
              (See Section 7.9.1 for information on modifying SEA to use 
              categories).
              Note: Other logs may not appear with the tree when connecting to 
              older versions of WCCProxy.

              Storage Cells
              Refreshes tree with current list of storage cells detected by 
              Command View EVA when Clicked. The list is also refreshed when a 
              Storage Configuration Event (type 910) is logged to the system's 
              binary event log and processed by SEA automatic analysis.





        +-----------------------------------------------------+




          7.3.2.2 Features of the Navigation Tree
      Figures 7-5 and 7-6 describe the features and functions of the navigation 
      tree. 
      Figure 7-5 Navigation Tree - Collapsed
      Figure 7-6 Navigation Tree - Expanded
        Table 7-5 Navigation Tree - Features
        +-----------------------------------------------------+

              Feature
              ----------
              Description
              ----------

              Current Selection is Highlighted
              In most browsers, the currently selected entry in the Navigation 
              Tree is highlighted (Figure 7-5).

              Collapsing Navigation
              The tree structure can be collapsed to the group level (Figure 
              7-5).

              Expanding Navigation
              Click on the expansion symbol for an entry to view its contents. 
              Once an entry is expanded, the expansion symbol changes to a 
              collapse symbol. To hide the contents again, Click the collapse 
              symbol.

              Icons
              Each entry in the tree has a name and an icon that indicates its 
              type. For example, in Figure 7-6 you can tell that the 
              jarjar.cxo.dec.com node is inactive because of its icon.

              Customizing the Navigation Tree
              You can customize the navigation tree by adding and removing 
              groups, nodes, categories, and binary event log files (see Section 
              7.4). 
              Note: Storage cells are generated automatically and cannot be 
              customized by the user.

              Viewing Results
              You can view the results of automatic analysis and initiate manual 
              analysis from the navigation tree (see Section 7.5).

              Refreshing Navigation
              If you modify the entries in the navigation tree, you may need to 
              refresh the display so your changes appear. To refresh the 
              navigation tree, Click the Refresh Tree button.





        +-----------------------------------------------------+




      7.4 Customizing the Navigation Tree 
      The first time you run the web interface using your profile, only the 
      local node and the Default Group appear on the navigation tree. 
      You can customize the navigation tree display by creating new groups, 
      adding nodes to groups, and selecting log files. 
      After you submit changes to the navigation tree, SEA refreshes the 
      display. The refresh process may take a few seconds. 
        7.4.1 Groups
      From the navigation tree, you can create new groups and remove existing 
      groups. 
          7.4.1.1 Adding Groups
      To add new groups follow these steps: 
        Click the "System Event Analyzer" link at the top of the navigation 
tree.
        The "Group Maintenance For System Event Analyzer" screen appears in the 
        display frame (Figure 7-7). The Add Groups tab is already selected.
        Figure 7-7 Add Group
        The location and placement options determine where you would like the 
        new group to appear in the navigation tree relative to existing groups. 
        By default, new groups are added after the selected group.
        Select an existing group from the list.
        Select a placement option from the radio buttons.
        Enter the name for the new group in the text field. Be sure to follow 
        these rules for naming groups:
          Group names should be unique. If you enter a group name that is 
          already in the navigation tree at the same level, SEA will not create 
          the new group.
          Group names should not use punctuation characters. These characters 
          can cause JavaScript errors in the web interface.
          Group names should be descriptive. If you leave this field blank, the 
          group is named "newGroup" by default.
        Click the Add New Group button.
        The new group appears in the navigation tree.
          7.4.1.2 Removing Groups
      Removing a group removes all the nodes and files contained in the group as 
      well as all of the lower level groups nested under it. 
      To remove existing groups, follow these steps: 
        Click the System Event Analyzer link at the top to the navigation tree.
        Select the Remove Groups tab at the bottom of the "Group Maintenance..." 
        screen (Figure 7-8).
        Figure 7-8 Remove Group
        Select the group name or names you want to remove from the list.
        To select multiple groups, press CTRL and Click on each group. If the 
        groups are consecutive, press SHIFT and Click on the first and last 
        group names.
        Click the Remove Selected Group(s) button.
        The groups disappear from the navigation tree.
        7.4.2 Nodes
      Expanding a group in the navigation tree displays the nodes contained in 
      that group. Nodes can be expanded by Clicking on the expansion symbol next 
      to their name to reveal the log file types or storage cells included in 
      that node. You can add and remove nodes from the groups in the navigation 
      tree. 
          7.4.2.1 Adding Nodes
      Any computer where the WCCProxy is running can be added to your web 
      interface navigation tree as a node. To add additional nodes follow these 
      steps: 
        Select the group you want to add nodes to from the navigation tree.
        The "Node Maintenance" screen appears in the display frame (Figure 7-9). 
        The Add Nodes tab is already selected.
        Figure 7-9 Add Node
        The location and placement options determine where you would like the 
        new node to appear in the navigation tree relative to existing nodes. By 
        default, new nodes are added after the selected node.
        If no nodes currently exist for the group, skip steps 2, 3a or 3b.
        Select an existing node from the list.
        Select a placement option from the radio buttons.
        Select an existing WEBES node or server from the Managed Entities or go 
        to Step 3b.
        Type in the name of the new node if you have not selected an existing 
        Managed Entity in step 3a. Select the node type from the following 
        options and Click Add New Node button.:
          WEBES Node
          Command View EVA Server
          WBEM Server
        Follow these rules to enter the name of the new node:
          Node names should be valid hostnames or IP addresses. Hostnames must 
          be accessible through the nameserver to be valid. For example, the 
          hostname of a Windows system using DHCP is not listed with the 
          nameserver. In this instance, you would need to enter the IP address.
          Node names should be unique. Entering the name of a node you are 
          already connected to will overwrite the existing node and any data 
          associated with it. The overwritten data includes filters, other logs, 
          categories, callouts, and storage cell information. 
          It is recommended to do the managed entity, when appropriate, before 
          doing the Node Maintenance. This helps assure that the same 
          information is entered in both the places.
        Click the Add New Node button.
        The new node appears under its group in the navigation tree.
          7.4.2.2 Removing Nodes
      Removing a node removes all the additional data contained in the node from 
      the navigation tree. 
      To remove existing nodes, follow these steps: 
        Select the group you want to remove nodes from in the navigation tree.
        Select the Remove Nodes tab at the bottom of the screen (Figure 7-10).
        Figure 7-10 Remove Node
        Select the node name or names from the list.
        To select multiple nodes, press CTRL and Click on each node. If the 
        nodes are consecutive, press SHIFT and Click on the first and last node 
        names.
        Click the Remove Selected Node(s) button.
        The nodes disappear from the navigation tree. If the selected node is 
        contained in multiple groups, removing it from one group will not affect 
        its presence in other groups.
          7.4.2.3 Activating Nodes
      A new animated icon is displayed when node activation is in progress. 
      Nodes are either active or inactive and by default when you connect to a 
      node or load a profile that connects to other nodes, all the nodes are 
      active. A node is only classified as inactive if SEA cannot connect to it. 
      Inactive nodes appear in the navigation tree with a red "X" through their 
      icon. 
      Node activation is based on successful communication with WCCProxy. If a 
      node is inactive, you can not activate the node manually. 
      However, while activating the node, the icon will animate in several 
      stages as shown in the following figure when the connection and 
      handshaking is in progress: 
      Figure 7-11 Activating Node
      If the Director on the remote node is accessible, a message appears in the 
      display frame (Figure 7-12) and the navigation tree is updated to show the 
      new status.
      Figure 7-12 Activating Node Message
      If the Director is not accessible, a message appears in the display frame 
      (Figure 7-13) and the navigation tree is not changed.
      Figure 7-13 Unable to Activate Node Message
        7.4.3 Categories
      Categories are an optional feature that is disabled by default. If you 
      want to use categories, you must enable the feature using the User 
      Settings tab on the Settings screen (see Section 7.9). 
      Categories provide a method for grouping the log files listed under the 
      Other Logs folder. If you use categories, SEA provides another layer of 
      folders under the Other Logs folder. This feature may be useful if you 
      monitor numerous log files. 
          7.4.3.1 Adding Categories
      Once you have enabled the categories feature, you can add categories to 
      the navigation tree. To add categories, follow these steps: 
        Select the Other Logs folder for the node you want to have new 
        categories.
        The Category Maintenance screen appears in the display frame (Figure 
        7-14). The Add Categories tab is already selected.
        Figure 7-14 Add Category
        The location and placement options determine where you would like the 
        new category to appear in the navigation tree relative to existing 
        categories. By default, new categories are added after the selected 
        category.
        If no categories currently exist for the group, skip steps 2 and 3.
        Select an existing category from the list. 
        Select a placement option from the radio buttons.
        Enter the name for the new category in the text field. Be sure to follow 
        these rules for naming categories:
          Category names should be unique. If you enter the name of an existing 
          category, SEA will not create the new category.
          Category names should not use punctuation characters. These characters 
          can cause JavaScript errors in the web interface.
          Category names should be descriptive. If you leave this field blank, 
          the category is named "newCat" by default.
        Click the Add New Category button.
        The new category appears in the navigation tree.
          7.4.3.2 Removing Categories
      Removing a category removes all the binary event log files contained in 
      the category from the navigation tree. 
      To remove existing categories, follow these steps: 
        Select the Other Logs folder for the node you want to remove categories 
        from in the navigation tree.
        Select the Remove Category tab at the bottom of the screen (Figure 
7-15).
        Figure 7-15 Remove Category
        Select the category name or names you want to remove from the list.
        To select multiple categories, press CTRL and Click on each category. If 
        the categories are consecutive, press SHIFT and Click on the first and 
        last category names.
        Click the Remove Selected Categories button.
        The categories disappear from the navigation tree. If a log file is 
        contained in multiple categories, removing it from one of the categories 
        will not affect its presence in the others.
        7.4.4 Log Files
      Each node contains binary event log files. Log files are separated into 
      two different types: the binary system event log and all other binary 
      event logs. 
          7.4.4.1 System Log
      The system log is the binary event log file where system events are 
      written. You cannot change this log file. Click the expansion symbol to 
      view the analysis options for the system log in the navigation tree. 
        Real Time Monitoring--shows the results of automatic analysis in the 
        display frame, for the subset of events from the node's system log file 
        that apply to the storage cell.
        Full View--manually analyzes the system event log and processes the 
        subset of events from the node's system log file that apply to the 
        storage cell.
        Storage Cells - shows the list of all the managed entities. Each EVA 
        shows the results of automatic and manual analysis (Real Time Monitoring 
        and Full View) of that particular device.
        *** Note ***


          On Windows, the system log file is the Windows Application Event Log, 
          located at %SystemRoot%\system32\config\AppEvent.Evt. The terminology 
          "system" log file should not be confused with the Windows System Event 
          Log, located at %SystemRoot%\system32\config\SysEvent.Evt, which SEA 
          does NOT read as of this release.



      If the node contains storage cells, another pair of icons are listed under 
      each storage cell. Click the expansion symbol to view the analysis options 
      for the storage cell's system log in the navigation tree. 
        Real Time Monitoring - shows the results of automatic analysis in the 
        display frame, for the subset of events from the node's system log file 
        that apply to the storage cell.
        Full View - manually analyzes the system event log and processes the 
        subset of events from the node's system log file that apply to the 
        storage cell.
      If the node is a WBEM node, another pair of icons are listed under WBEM 
      node. Click the expansion symbol to view the analysis options for the WBEM 
      node's system log in the navigation tree. 
        Real Time Monitoring - shows the results of automatic analysis in the 
        display frame, for the subset of events from the node's system log file 
        that apply to WBEM node.
        Full View - manually analyzes the system event log and processes the 
        subset of events from the node's system log file that apply to WBEM 
node.
          7.4.4.2 Other Logs
      The Other Logs folder in the navigation tree contains entries for binary 
      event log files other than the system event log. These can include the 
      example binary log files included with SEA, or any other binary event log 
      file located on the node. Initially, there are no sub-entries under Other 
      Logs in the navigation tree. 
      If you are using categories, the Other Logs entry contains the categories 
      you have created and the category folders contain entries for binary event 
      log files. 
      In order to add saved log files to the navigation tree, they must be 
      viewable in the Add Log Files list. For a file to be viewable, it must 
      meet both of these criteria: 
        The log file must have a .sys, .evt, .zpd, or .errlog extension. If you 
        wish to add a file with a different extension, you will need to rename 
        the file so it uses an acceptable file extension.
        The log file must be saved in the svctools directory (created during 
        installation), one of its subdirectories, or one of the directories you 
        configured in the CA.WUI.OLDirs key in the DESTA registry. Files that 
        are stored in these locations are automatically displayed in the list. 
        For more information, see Section 10.7.2.
      The best place to store log files (as well as other user data) is in one 
      of the userdata subdirectories: 
      svctools\specific\ca\userdata
      svctools\common\ca\userdata

      Files stored in these subdirectories are automatically backed up and saved 
      if you uninstall, reinstall, or upgrade WEBES. For more information on 
      storing user data, see the WEBES Installation Guide. 
      If you want to store files elsewhere, you can configure WEBES by adding a 
      comma separated list of file paths to the CA.WUI.OLDirs key in the DESTA 
      registry. For more information, see Section 10.7.2. 
      You also can enable a text entry field for specific users. The text field 
      allows users to add log files to the Other Logs list by entering the path 
      and filename of an event log located anywhere in the file system. For more 
      information, see Section 10.7.3. 
      Adding Other Logs 
      Follow these steps to add other log files: 
        Open the Other Logs screen in the display frame.
        If you are using categories, Click on the category name for the node. 
        Otherwise, Click on the Other Logs link for the node.
        The Other Logs screen opens in the display frame (Figure 7-16). The Add 
        Files tab is already selected.
        Figure 7-16 Add Log Files Tab
        Select the desired binary event log files:
          Click the Select All button to select all the listed log files.
          Click the check box for each file. You can select multiple check 
boxes.
          Click the Clear All button or uncheck a selected check box to deselect 
          files.
        (Optional) If enabled, enter the path and filename in the text field 
        (see Section 10.7.3 for more information).
        Click the Add button.
        The binary event log file is added to the navigation tree under the 
        Other Logs entry or appropriate category for the node.
      Removing Other Logs 
      To remove binary event log files from the navigation tree, follow these 
      steps: 
        Open the Other Logs screen in the display frame.
        If you are using categories, Click on the category name for the node. 
        Otherwise, Click on the Other Logs link for the node.
        Select the Remove Files tab from the bottom of the screen (Figure 7-17).
        Figure 7-17 Remove Log File Tab
        Select the log file name you want to remove from the list. 
        To select multiple files, press CTRL and Click on each file name. If the 
        files are consecutive, press SHIFT and Click on the first and last file 
        names.
        Click the Remove Selected Log File(s) button.
        The navigation tree is refreshed to reflect your changes.
      7.5 Processing Log Files 
      You can process a log file, check its status, and view the results using 
      any of the following methods: 
        Selecting System Log or Real Time Monitoring runs automatic analysis on 
        a node.
        Clicking Full View manually analyzes a node's system event log and 
        display the results.
        Clicking a Log File name under Other Logs runs manual analysis on the 
        file and displays the results.
        Clicking a Storage Cell (SMA, EVA, WBEM Server) - Real Time Monitoring 
        runs automatic analysis on the selected device. Clicking a Storage Cell 
        - Full View manually analyzes the selected device's system event log and 
        displays the results.
        *** Note ***


          The problem reports, events, and configuration entries shown in the 
          Real-Time Monitoring and Full View listings apply only to the given 
          storage cell.



      The IPF configuration reports have been updated to include information 
      from cell based systems. In particular, Field Replaceable Units (FRU) are 
      reported by the Logical Unit Number (LUN) to which they belong, in 
      addition to the existing information. Information about memory dimm sizes 
      is accessible when it is present in the configuration entry. Information 
      about partitions and the cells that belong to those partitions is provided 
      when it is present in the configuration entry. The number of the partition 
      that logged the configuration entry is accessible when it is present in 
      the configuration entry. 
      An extract of the sample configuration entry is shown below: 
      Event: 1
      Description: Configuration SDR FRU at Thu 24 Mar 2005 17:01:18 GMT-05:00 
      from FPAR2 
      File: 8620_par0_config.sys@bagend
      ========================================================================
      OpenVMS IPMI configuration report

      Hostname: BILBO
      TimeStamp: Thu 24 Mar 2005 15:01:18 GMT-07:00
      DSR Type: HP rx8620 (1.30GHz/3.0MB)
      Serial #: 1111111111

      OEM Property List

      LUN ID Cell Description 
      ------ ------ ------ -----------------------------------------
      0 0x0 0 Configuration collected from the running Partition #: 0

      0 0x9 0 Partition CELL #
      ----------- ------
      0 0
      1 2, 3
      2 1

      1 0x4 0 DIMM # Size DIMM # Size 
      ------ ----------- ------ -----------
      0A 2048 MB 0B 2048 MB 
      1A 2048 MB 1B 2048 MB 
      2A 2048 MB 2B 2048 MB 
      3A 2048 MB 3B 2048 MB 
      4A 2048 MB 4B 2048 MB 
      5A 2048 MB 5B 2048 MB 
      6A 2048 MB 6B 2048 MB 
      7A 2048 MB 7B 2048 MB 
      8A -- 8B -- 
      9A -- 9B -- 
      10A -- 10B -- 
      11A -- 11B -- 
      12A -- 12B -- 
      13A -- 13B -- 
      14A -- 14B -- 
      15A -- 15B -- 
      32 GB Total Memory


      1 0x5 1 DIMM # Size DIMM # Size 
      ------ ----------- ------ -----------
      0A 2048 MB 0B 2048 MB 
      1A 2048 MB 1B 2048 MB 
      2A 2048 MB 2B 2048 MB 
      3A 2048 MB 3B 2048 MB 
      4A 2048 MB 4B 2048 MB 
      5A 2048 MB 5B 2048 MB 
      6A 2048 MB 6B 2048 MB 
      7A 2048 MB 7B 2048 MB 
      8A -- 8B -- 
      9A -- 9B -- 
      10A -- 10B -- 
      11A -- 11B -- 
      12A -- 12B -- 
      13A -- 13B -- 
      14A -- 14B -- 
      15A -- 15B -- 
      32 GB Total Memory

      1 0x6 2 DIMM # Size DIMM # Size 
      ------ ----------- ------ -----------
      0A 2048 MB 0B 2048 MB 
      1A 2048 MB 1B 2048 MB 
      2A 2048 MB 2B 2048 MB 
      3A 2048 MB 3B 2048 MB 
      4A 2048 MB 4B 2048 MB 
      5A 2048 MB 5B 2048 MB 
      6A 2048 MB 6B 2048 MB 
      7A 2048 MB 7B 2048 MB 
      8A -- 8B -- 
      9A -- 9B -- 
      10A -- 10B -- 
      11A -- 11B -- 
      12A -- 12B -- 
      13A -- 13B -- 
      14A -- 14B -- 
      15A -- 15B -- 
      32 GB Total Memory

      1 0x7 3 DIMM # Size DIMM # Size 
      ------ ----------- ------ -----------
      0A 2048 MB 0B 2048 MB 
      1A 2048 MB 1B 2048 MB 
      2A 2048 MB 2B 2048 MB 
      3A 2048 MB 3B 2048 MB 
      4A 2048 MB 4B 2048 MB 
      5A 2048 MB 5B 2048 MB 
      6A 2048 MB 6B 2048 MB 
      7A 2048 MB 7B 2048 MB 
      8A -- 8B -- 
      9A -- 9B -- 
      10A -- 10B -- 
      11A -- 11B -- 
      12A -- 12B -- 
      13A -- 13B -- 
      14A -- 14B -- 
      15A -- 15B -- 
      32 GB Total Memory


      Viewing Process Status 
      When analysis is successfully started, the log file's icon is animated. 
      Once the file is processed, the icon in the toolbar changes to reflect the 
      status of the log file (see Section 7.5.2) and the results of processing 
      are shown in the display frame. 
      Viewing Results 
      Both automatic and manual analysis results are shown in the display frame. 
      The information is organized under the following tabs: 
        Problem Reports--results of analysis
        Summary--description of the contents of the log file (only available 
        with manual analysis)
        Events--translation of the events contained in the log file
        *** Note ***


          If you have configured the User Settings so SEA only performs manual 
          translation, rather than translation and analysis, the Problem Reports 
          tab is empty. See Section 7.9.1 for more information on User Settings.



      Analysis Failed 
      If the file cannot be processed for any reason, a message similar to the 
      one in Figure 7-18 is shown. 
      Figure 7-18 Analysis Failed Message
        7.5.1 Additional Toolbar Functions
      SEA provides additional functionality depending on the type of processing 
      you are performing. 
        Figure 7-19 Additional Toolbar Functions
        +-----------------------------------------------------+

              Button
              ----------
              Name
              ----------
              When Does It Appear in the Toolbar?
              ----------
              Description
              ----------


              Click for Larger Image 82
              Clear Results Button
              When you are performing or viewing Automatic Analysis.
              The Clear button removes all the entries (problem reports and 
              events) from the display tabs.


              Click for Larger Image 80
              Reprocess File Button
              When you are performing Manual Analysis.
              The Reprocess button forces SEA to discard the previous analysis 
              results and reprocess the selected binary log file.


              Click for Larger Image 80
              Analyze File Button
              When the User Settings are configured to perform only manual 
              translation by default.
              Clicking the Analyze button will perform analysis for the current 
              log file. Thus, if you need to perform analysis, it is not 
              necessary to change the User Settings and reprocess the file. 


              Click for Larger Image 80
              Analyze Filtered Events Button
              When you use a filter for processing a log file. 
              Clicking the Analyze Filtered event button allows you to repeat 
              the analysis using only the events that met the filter criteria.





        +-----------------------------------------------------+




        7.5.2 Processing Status
      With large log files, translation and analysis operations are not 
      instantaneous. After you have started processing a log file there are 
      several ways to check the operations progress. You can check the 
      processing status from either the navigation tree or the Progress window. 
          7.5.2.1 Navigation Tree
      You can quickly determine the status of automatic or manual analysis by 
      looking at the icons in the navigation tree. Figure 7-20 shows the icons 
      used to indicate analysis results. 
      Figure 7-20 Status Icons
      When automatic analysis generates a problem report, exclamation points are 
      added to the icons for the node, system log, and real time monitoring. The 
      icon remains changed until problem report details are viewed and the tree 
      is refreshed. If another problem report is generated after the tree is 
      refreshed, exclamation points are added to the icons again. 
      You also can determine the results of manual analysis on a binary event 
      log file by checking the icons. SEA uses a animated yellow icon when a 
      binary log file is being read and an animated green icon during analysis. 
      If processing has completed and problem reports were generated, an 
      exclamation point is added to the icon. Otherwise a check mark is added to 
      the icon. Unlike the icon changes associated with automatic analysis, the 
      manual analysis icon changes remain visible until you close the web 
      interface session. 
      *** Note ***


        If you are only performing translation, when processing completes the 
        icon will appear with a dash. See Section 7.9.1 for more information on 
        configuring the web interface to only perform translation.



          7.5.2.2 Progress Window
      You can open the Progress window by Clicking on the Progress Window button 
      in the toolbar (see Figure 7-3). 
      The Progress window opens in a new browser window (Figure 7-21). 
      Figure 7-21 Progress Window
      The Progress window provides statistics for all the log files that are 
      currently being analyzed by SEA, including automatic and manual analysis 
      jobs. The information in the Progress window includes: 
        The origin of the log file
        The number of events in the file
      The position of each job in the queue is displayed, and information is 
      dynamically updated as the processing changes. When a job finishes 
      processing, it is removed from the window. 
      When monitoring the progress of a job, you can refresh the display 
      manually by Clicking the refresh icon in the upper left hand corner. To 
      stop processing an active manual job, Click on the Stop icon. 
        7.5.3 Working With Results
      After processing, the results of analysis are shown on the tabs in the 
      display frame (Figure 7-22). 
      Figure 7-22 Additional Entries Navigation
      When there are many entries, you can use the navigation options to page 
      through the results. 
        Use the Previous and Next links to move between entry screens. 
        Enter a number in the entry field and Click Go to display a specific 
        entry.
        *** Note ***


          You can control the number of entries shown in a tab with the options 
          in the User Settings window. See Section 7.9.1 for more details.



          7.5.3.1 Problem Reports
      The Problem Reports tab displays a list of the reports that were generated 
      by analysis. An example of the problem report list is shown in Figure 
      7-23. 
      Figure 7-23 Problem Report Tab
      The filters used when generating the problem reports are listed at the top 
      of the screen. However, the display only shows the filters that apply to 
      problem reports and may not list all the filters you selected. 
      When working with problem reports, these options are available: 
        To sort the entries in the report list select the column headers. See 
        Section 7.5.3.5 for more details on sorting.
        To view the contents of a report, Click on its entry in the list of 
        available problem reports. See Section 7.5.3.6 for information on 
        viewing reports.
      The problem reports generated by the web interface are the same as those 
      generated by the CLI. 
        See Chapter 8 for more information on analysis. 
        See Appendix  for an example of a problem report.
          7.5.3.2 Summary
      The Summary tab is only available when you perform manual analysis. If you 
      select Real Time Monitoring from the Navigation Tree, for example, the 
      Summary tab is not displayed. 
      When performing manual analysis, the Summary tab describes the event types 
      contained in the binary event log file (Figure 7-24). 
      Figure 7-24 Summary Tab
      Each event type is listed along with the number of occurrences. The time 
      stamps for the first and last events are listed under the summary 
      information. 
      The filters that were applied are listed at the top of the screen. Be 
      aware that the screen only shows the filters that apply to the summary 
      report and may not list all the filters you selected. 
      See Section 8.8 for details on the summary information presented. 
          7.5.3.3 Sub Type Tallied Summaries and Event Listings
      Certain types of events have subtypes which can be further summarized and 
      listed by Sub Type. As of the WEBES 4.5 release, binary events of type 199 
      (CAM events) and 14009 (Enterprise Virtual Array events) display this 
      feature. 
      The Sub Type Tallied Summaries screen shows you the list of Sub Type 
      events. The events have been classified based on the nature of the event. 
      As of the WEBES 4.5 release, there is no color classification for the Sub 
      Type events of event type 199 (CAM events). All the Sub Type events of 
      event type 199 will appear in grey color. The colors of the event 
      description signify the following about their nature. 
        +-----------------------------------------------------+

              Color
              ----------
              Nature of the Event
              ----------

              Red
              Significant events

              Green
              Configuration events, and return to normal status from a previous 
              failure

              Blue
              EVA Reboot/Resync/Restart etc

              Dark Orange
              Data Availability, CA, Customer attention needed

              Magenta
              Drive firmware update events

              Purple
              Threshold events





        +-----------------------------------------------------+




      To view the Sub Type event summary information, select the summary tab in 
      the Web interface for any binary event log. This will show you the 
      classification of the event types. If the event summary has event type 
      14009 or 199, Click 14009 link or 199 link to view the Sub Type event 
      summary. 
      Following screen shows the summary of Sub Type event 14009: 
      Figure 7-25 Summary of Sub-Types
      To view the Sub Type listing information, Click Sub-Type Listing link 
      shown in the above screen. The following screen shows the listing of all 
      the Sub Type events of event type 14009: 
      Figure 7-26 Sub-Type Listing
          7.5.3.4 Events
      The Events tab shows a list of the events contained in the binary event 
      log file. Depending on the filtering options that were applied during 
      processing, all the events in the log file may or may not be shown (Figure 
      7-27). 
      *** Note ***


        You can control the fields that are shown on the events tab from the 
        User Settings window. See Section 7.9.1 for more details.



      Figure 7-27 Events Tab
      The filters that affected the output are listed at the top of the screen. 
      Be aware that the screen only shows the filters that apply to events and 
      may not list all the filters you applied. 
      When working with events, these options are available: 
        To sort the events list, use the column headers. See Section 7.5.3.5 for 
        more details on sorting. 
        To view the translation of an event, Click on its entry in the list. See 
        Section 7.5.3.6 for information on viewing translation details. 
      The translated events shown by the Web interface are the same as those 
      shown by the CLI. 
        See Chapter 8 for more information on event translation
        See Appendix  for an example of a translated event.
          7.5.3.5 Sorting Results
      You can sort the results of analysis using either the column headings on 
      the tabs in the display frame, or by using a filter. 
      Sorting with Column Headings 
        Sorting with the column headings only impacts the entries currently 
        shown. Therefore, if there are too many entries to be listed on a tab, 
        the column headings will only sort the entries that are displayed rather 
        than all the output produced by processing the log file. In most cases, 
        this limitation only impacts the Events tab.
        You can sort the results shown on any tab using the field names that 
        appear in blue (i.e., as hypertext links). Simply Click on the field 
        name to sort based on that field. An arrow appears next to the field to 
        indicate the direction of the sorting. The sorting options are applied 
        to all the tabs, regardless of which tab was used to specify the sorting 
        criteria.
        Entries can be sorted in either ascending or descending order. To change 
        the sort order, Click on the field name a second time. The arrow next to 
        the field changes direction to indicate the new sort order. When the 
        arrow is pointing up, it indicates an ascending sort. When the arrow is 
        pointing down, it indicates a descending sort.
        If you are working in multiple windows, sorting only applies to the 
        current window.
      Sorting with a Filter 
        Using a filter to sort entries impacts all the output generated by 
        processing a log file, regardless of how many screens are required to 
        show all the entries. 
        For more information on using a filter to sort output, see the 
        information on applying filters in Section 7.8.
          7.5.3.6 Displaying Details
      The Problem Reports tab lists the reports generated by analysis and the 
      Events tab lists the events in the binary log. You can view the details of 
      a problem report or the translated text of an event by Clicking on an 
      entry in the list. Depending on the User Settings selected (see Section 
      7.9.1), the details will either be shown in the display window or in a new 
      browser window. 
      In order to make viewing details easier, navigation buttons are available 
      at the top of each detailed entry. The navigation buttons for the Problem 
      Reports tab and Events Tab are shown in Figures 7-28 and  7-29. 
      Figure 7-28 Navigation Buttons--Problem Reports 
      Figure 7-29 Navigation Buttons--Events 
      The buttons are used to move between entries in the list. 
        You can view the details for other events in the list using the Previous 
        and Next buttons.
        When paging between entries, the column heading sort order always 
        reverts back to the Index column in ascending order. Filter sorts, 
        however, still apply.
        Click the Index button to redisplay the list of entries.
        If you select "Put Event Details In A New Window" in your User Settings, 
        the Index button is not available. Clicking the Previous and Next 
        buttons displays all entries in the new window. See Section 7.9.1 for 
        more information on user settings.
        The Event Details tab includes a drop down list that can be used to 
        change the report type. See Chapter 8 for more information on 
        translation report types.
      7.6 Creating New Log Files 
      To create a binary event log for use with SEA, follow these steps: 
        Click the New Binary Log File button in the toolbar (see Figure 7-3).
        The New Binary Log Screen appears in the display area (Figure 7-30).
        Figure 7-30 New Binary Log Screen
        Enter the input file name, including its path, in the Input File text 
        box.
        Click the Add Input file Button.
        The file is added to the Currently Selected Input Files list.
        Repeat steps 2 and  3 until all the desired input files are added.
        *** Note ***


          If you want to remove one of the input files you added, Click on the 
          filename in the Currently Selected Input Files list and click the 
          Remove Selected Input Files button. You can select multiple files by 
          holding the Ctrl key while you click on the filenames.



        Specify the desired filtering options by either creating a new filter or 
        applying an existing template. 
          To specify filtering criteria, Click the Adjust Filter button at the 
          top of the screen and use the Adjust Filter screen to select filtering 
          options (see Section ).
          To apply an existing filter template, select the desired template from 
          the drop down list at the top of the screen.
          For more information on filtering, see Sections 7.8 and  7.9.1.2.
        Enter the output file name in the Output File text box.
        *** Note ***


          New binary log files are automatically stored in the 
          specific\ca\userdata subdirectory located under the installation 
          directory, hence it is not necessary to include a path with the Output 
          filename. For more information on storing user data, see the WEBES 
          Installation Guide.



        If you have established a filter that excludes configuration entries and 
        you want to preserve that filtering in the output file, select the "Do 
        not reinsert config entries needed for analysis" check box.
        If the output file name already exists and you want to replace the 
        existing file, select the "Overwrite file if exists" check box. 
        If you do not select this check box, and enter a filename that already 
        exists, you will receive an error message.
        Click the Create New Log File button to process the input files and 
        create the new binary log file.
        *** Note ***


          It is possible to construct a filter that prevents any events from 
          being added to the new log file. If this is the case, no log file will 
          be created. However, even if this is the case, when the Overwrite 
          option is selected any file with the same name as the output file will 
          be lost.



      7.7 Creating Storage Cell Spreadsheets 
      You can create a Microsoft Excel spreadsheet file containing Bit-to-Text 
      translations of all controller events for a given Storage Cell. 
        Select the storage cell name from the navigation tree for which you want 
        to generate a spreadsheet of events.
        From the toolbar, Click the following icon:
        Figure 7-31 Storage Cell Icon
      It appears in the Web interface toolbar as shown in the following figure: 
      Figure 7-32 Storage Cell Icon in WUI
      7.8 Applying Filters 
      You can apply filters when processing existing log files and when creating 
      new binary log files. You also can use filters to specify how problem 
      reports and events are sorted. Specify the desired filter using the Filter 
      Templates bar at the top of the screen (Figure 7-33). 
      Figure 7-33 Filter Templates Bar
      If you have previously created filter templates, they will be listed in 
      the drop-down list. You can either: 
        Select an existing filter from the drop down list and if necessary 
        modify it by Clicking the Adjust Filter button and changing the 
        filtering options. 
        Click the Adjust Filter button and define a new filter.
        *** Note ***


          Modifying or defining a filter from the Filter Templates bar does not 
          change an existing filter or save a new filter. Your changes are only 
          used with the current operation. Use the Filters option under User 
          Settings to create new templates (see Section 7.9.1.2).



      When you use filters in conjunction with analysis and translation the 
      filter description will be shown with the results. However, the filtering 
      options you select are only applied to the appropriate output. Thus, if 
      you select a filter that only affects event translation, rather than 
      problem reports and translation, the filter will be listed with the event 
      details but not with the problem reports details. Figure 7-34 depicts a 
      filter description from the event details. 
      Figure 7-34 Filter Description
      See Section 7.9.1.2 for more information on creating and modifying 
      filters. 
      7.9 Modifying Settings 
      The Web interface settings enable you to control how the WEBES Director 
      functions and modify the Web interface to suit your preferences. To access 
      the settings, Click the settings button in the toolbar. This updates the 
      Web interface, replacing the normal navigation bar with the User Settings 
      navigation bar. The display frame is updated to show the User Settings 
      screen. 
      You can modify both User and Director settings. 
        7.9.1 User Settings
      The user settings are used to modify the Web interface, configure 
      filtering information and determine what translation information is 
      displayed. To access the User settings, Click the Settings button in the 
      toolbar and then select the User Settings tab. 
      Figure 7-35 User Settings
      Use the tabs located at the left side of the screen to navigate the User 
      settings (Figure 7-35). 
        Table 7-6 User Settings Navigation
        +-----------------------------------------------------+

              Option
              ----------
              Description
              ----------

              Settings
              Displays the web interface general configuration options. See 
              Section 7.9.1.1 for more information.

              Filters
              Opens the Filter Preferences screen which is used to define filter 
              templates and set a default filter. See Section 7.9.1.2 for more 
              information.

              Event Columns
              Specifies the translation information you want to view. See 
              Section 7.9.1.3 for more details.

              Exit Settings
              Closes the settings screen.





        +-----------------------------------------------------+




          7.9.1.1 General Options
      The general options screen is shown in Figure 7-35.The General User 
      Settings screen presents the following options: 
        Table 7-7 General User Settings Options
        +-----------------------------------------------------+

              Option
              ----------
              Description
              ----------

              Save File Lists in Other Logs
              Select this option if you want the navigation tree to save a 
              record of all the log files listed under Other Logs when you log 
              off SEA. If this option is selected, the log files will remain in 
              the navigation tree until you manually remove them. If this option 
              is not selected, the Other Logs section of the tree will be empty 
              when you log on.

              Use Categories With Other Logs
              Select this option to use categories with log files. See Section 
              7.4.3 for more on categories.

              Put Event Details In A New Window
              Opens a new browser window for the details of a problem report or 
              event selected from the list of entries. The list of entries will 
              remain open in the original window. 

              Manually Translate Files Only (Skip Manual Analysis)
              Prevents SEA from performing manual analysis for log files. This 
              affects the output when you select an entry from the Other Logs 
              area and when you perform manual analysis on the system event log.

              Event Reporting Level
              Specifies the default level of reporting for translated events. 
              The available report types are brief and full. See Section 8.2.3 
              for more information on report types.

              Tree Selected Color
              Enables you to specify the color used to highlight selected 
              entries in the navigation tree.

              Entries per screen
              Specifies the number of entries displayed at one time on the 
              output tabs. See Section 7.5.3 for more information.

              Log Off Time
              By default, SEA logs your profile off ten minutes after you close 
              your connection with the Director. You can change the amount of 
              time by entering a new value in the text box. All values are in 
              minutes. See Section 7.11 for more information on logging off. 
              (Setting the Log Off time to zero is not recommended. See Section 
              7.11 for more details.) 





        +-----------------------------------------------------+




      Click the Update button to save your changes to the settings. 
          7.9.1.2 Filters
      Filtering is used to reduce the number of events processed when you 
      perform translation or create a new log file. With large log files, using 
      only a subset of the events can improve processing time and enhance output 
      by displaying only the most pertinent information. 
      Within the web interface, filtering is performed using templates. 
      Templates contain pre-defined filtering functions that can be applied to 
      SEA functions. 
      The Filtering Preferences screen allows you to create new filter 
      templates, modify existing filter templates, or select default filtering 
      options. To access the Filtering Preferences screen, Click the Filters 
      button in the User Settings navigation bar. 
      Figure 7-36 Filter Preferences
      Creating and Modifying Filter Templates 
      To modify a filter template or create a new filter, use the following 
      procedure: 
        Select the filter you want to modify from the drop-down list in the 
        Filter Templates bar.
        If you want to create a new filter from scratch, you do not need to 
        select an existing template.
        Click the Adjust Filter button located in the Filter Templates bar. 
        The Adjust Filter screen appears (Figure 7-37). If you are modifying an 
        existing template, the contents of that filter are listed in the 
        Currently Applied Filters list.
        Figure 7-37 Adjust Filter
        Ensure that all the filter information in the Currently Applied Filters 
        list is correct. 
        Initially, this field will display the contents of the filter template 
        you selected. You can delete any filter by selecting it and Clicking the 
        Remove Selected Filters button. If you are creating a new filter the 
        list is blank.
        Choose any additional filtering criteria from the drop-down list. 
        Once you have selected a filter type, the Filtering screen is 
        dynamically updated to include the valid operators (Figure 7-38). Be 
        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 (=)
          Greater than (>)
          Less than (<)
          Figure 7-38 Filtering Criteria
          Once you have selected an operator, the screen is updated to include a 
          drop-down list of values or a text entry field (Figure 7-39). 
        Select or enter the appropriate value.
        Figure 7-39 Filtering Operators
        Click the Apply button. 
        The filter is added to the list of Currently Applied Filters (Figure 
        7-40).
        Figure 7-40 Applied Filter
        Repeat steps 3 to  7 until all the necessary filters have been added.
        Click the Adjust Filter button again to close the Adjust Filter screen 
        and return to the Filtering Preferences screen (Figure 7-36). 
        The Filtering Preferences screen describes the contents of the new 
        filter.
        Save the new filter as a template by entering a filter name in the Name 
        text box and Click the Add New Template button. 
        SEA will update the Filter Templates list and add the new filter to the 
        drop-down list in the Filter Templates bar.
      If you are creating a new filter from one of the details tabs rather than 
      the User Settings window, the filter is saved for that file or automatic 
      node, but not as a template that can be applied elsewhere. Otherwise the 
      process is the same. 
      Default Filters 
      You can apply default filtering options to all the analysis and 
      translation operations performed from the web interface using the Filter 
      Preferences screen (Figure 7-36). 
      To set a default filter, use the following procedure: 
        Select the desired templates from the drop-down list in the Filter 
        Templates bar. 
        It is not necessary to select a template if you do not want to use an 
        existing template.
        If necessary, Click the Adjust Filter button and modify the filter 
        template or create a new template.
        Click the Save Current Filter As Default button.
      It is not necessary to save the default filter as a template. If you want 
      to, you can use the Adjust Filter screen to create a filter and then save 
      it as the default filter without saving it as a template. 
      Deleting Templates 
      You can delete a filter template from the Filter Preferences screen 
      (Figure 7-36), using the following procedure. 
        Click on the name of the filter you want to delete in the Filter 
        Templates list.
        You can select multiple filters by holding the CTRL key while you Click 
        the filter names.
        Click the Remove Selected Filters button.
          7.9.1.3 Event Columns
      The Event Columns screen is used to specify the information displayed by 
      translation on the Events tab (see Section 7.5.3.4 for more information on 
      translation details). 
      Figure 7-41 Event Columns
      The Event Columns screen lists the field headings for event translation. 
      You can designate which translation information is shown on the Events tab 
      using the following procedures. 
      Adding Fields 
      To add fields, determine which additional translation fields need to be 
      shown. The first list displays all the available translation fields and 
      the second list indicates the fields that are currently shown. 
        Select the desired field from the first list by Clicking on its name. 
        You can select multiple entries by holding the Ctrl key while you select 
        their names.
        Click the Add button.
        The selected fields are added to the end of the second list and shown 
        under the Events tab.
      Rearranging Fields 
      The order of the fields in the second list indicates the order of the 
      information on the Events tab. To rearrange the fields: 
        Select the field that needs to be moved by Clicking on its name in the 
        second list.
        Move the field to its new location.
          Click the Move Up button to move the field up in the list.
          Click the Move Down button to move the field down in the list.
      Removing Fields 
      To remove a field: 
        Select the field from the second list by Clicking on its name.
        You can select multiple fields by holding the Ctrl key while you select 
        their names.
        Click the Remove button.
        7.9.2 Director Settings
      The Director settings are used to modify WEBES components, enter 
      entitlement information and register rule sets. To access the Director 
      settings, Click the Settings button in the toolbar and then select the 
      Director Settings tab. 
      Figure 7-42 Director Settings
      Use the buttons located at the right side of the window to navigate the 
      Director settings. 
        Table 7-8 Director Settings Navigation
        +-----------------------------------------------------+

              Option
              ----------
              Description
              ----------

              Settings
              Displays the configuration settings for the Director. See Chapter 
              10 for information on changing the Director settings.

              Register Knowledge
              Displays the knowledge rule sets that can be installed. See 
              Chapter 9 for more information on rule sets and analysis.

              Managed Entities
              Displays the list of Managed Entities (SMAs, EVAs, WBEM Server) 
              allowing you to change their configuration data.

              Exit System Event Analyzer Settings
              Closes the settings screen.





        +-----------------------------------------------------+




      7.10 Getting Help 
      The web interface provides usage tips and a link to the user guide. 
        7.10.1 Usage Tips
      Position the cursor of your mouse over an element from the toolbar or 
      navigation tree to view a brief description of the option in the 
      information bar at the bottom of the browser window. 
        7.10.2 On-Line User Guide
      Click on the Help button from the SEA toolbar to view an HTML version of 
      the System Event Analyzer User Guide. The help opens in a new browser 
      window. 
      7.11 Logging Off 
      It is not necessary to manually log off SEA. Once your connection to the 
      Director is closed, SEA will automatically log off your profile after the 
      log off time elapses. By default, the log off time is set to ten minutes; 
      however, you can configure the time from the User Settings screen (see 
      Section 7.9.1). 
      You can close your connection by exiting your browser or navigating to a 
      web site outside of the SEA web interface. SEA continues to process 
      requests and stores your data after you have closed your connection (as a 
      result, SEA continues to consume memory resources). If you restore your 
      connection to the Director before the log off time elapses, your data will 
      remain intact. This enables you to browse other web sites without losing 
      your SEA data. However, if the connection with the Director is closed, 
      once the log off time elapses, all the data associated with your SEA 
      session is lost and the memory resources used by SEA are released. Thus, 
      if you return to SEA after the log off time has elapsed, you will not be 
      able to view the results of processing. 
      For example, if your log off time is set to 120 minutes and you start 
      processing a log file before switching to another web site, you have two 
      hours during which SEA will continue to process the log file and maintain 
      your data. If you return to SEA before the two hours elapses, processing 
      will continue and all your data will be maintained. If you do not return 
      to SEA within the two hours, processing is terminated and your data will 
      be lost as memory resources are cleaned up. 
      *** Note ***


        If you set the log off time to zero, you will be logged off and lose 
        your data if you click the refresh button in your browser or if you 
        click a link that opens a page outside SEA.



      The following list shows some possible log off times and the time frame 
      they represent: 
        180 = 3 hours
        1440 = 24 hours
        10080 = 1 week
        44640 = 31 days
      Lost Connection 
      If your connection to the Director is lost for any reason, the message in 
      Figure 7-43 appears in the toolbar. 
      Figure 7-43 Lost Connection Message
      7.12 Service Obligation 
      You can view service obligation information by entering the following URL: 

      http://hostname:7902/obligation

      Where hostname refers to the system name or IP address.
      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: Hewlett-Packard

      Obligation Start Date: Sat May 13 00:00:00 MDT 2000
      Obligation Ending Date: Sun May 13 00:00:00 MDT 2001
      Time left on Obligation: 0 years, 355 days, 13 hours, 52 minutes, 57 
      seconds

      History of changes: 
        1. Sat May 13 15:46:22 MDT 2000: Installer (unknown) of Hewlett-Packard
      Installation settings changed to start Sat May 13 00:00:00 MDT 2000 to Sun 
      May 13 00:00:00 MDT 2001 (1 years, 0 days, 0 hours, 0 minutes, 0 seconds) 
        2. Sat May 13 15:46:11 MDT 2000: WEBES (Web-based Enterprise Services 
      Common Components V3.0 (Build 12), member of WEBES V3.0 (Build 12)) of 
      Hewlett-Packard
      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 
        1. 0 years, 60 days, 0 hours, 0 minutes, 0 seconds 
        2. 0 years, 30 days, 0 hours, 0 minutes, 0 seconds 
        3. 0 years, 15 days, 0 hours, 0 minutes, 0 seconds 
        4. 0 years, 5 days, 0 hours, 0 minutes, 0 seconds 
        5. 0 years, 4 days, 0 hours, 0 minutes, 0 seconds 
        6. 0 years, 3 days, 0 hours, 0 minutes, 0 seconds 
        7. 0 years, 2 days, 0 hours, 0 minutes, 0 seconds 
        8. 0 years, 1 days, 0 hours, 0 minutes, 0 seconds 

      7.13 Managed Entities 
      The Managed Entities page lists all the managed entities like EVA, Command 
      View EVA Server, WBEM Server and WBEM Non-stop server. WEBES has the 
      capability to receive WBEM indications from a WBEM Server. 
      After adding the required managed devices, you can see the list of managed 
      devices in the Managed Entity page. Figure  7-44 shows the list of all the 
      devices managed by this node. 
      Figure 7-44 Managed Entities
      To view the details of a managed entity, Click on the particular managed 
      entity (for example, Command View EVA Server) which lists out the managed 
      entity details as shown in Figure  7-45. 
      Figure 7-45 Managed Entity Detail
      The following fields are available in the Managed Entity Detail for EVAs: 
              Choose a Primary Contact
              Refresh List
              Go To Contacts

              Out of Hours Contact
              Refresh List
              Go To Contacts

              HP Contact
              Refresh List
              Go To Contacts





      You can choose from the existing contact names for Primary Contact, Out of 
      Hours Contact, and HP Contact or enter new contact names by clicking Go To 
      Contacts button and filling the required information. The Refresh List 
      button updates the new contact names (added) along with the existing 
      contact names, if any. 
      If the node is not managing any entity, the Managed Entities page does not 
      show any information on this. The following screen is an example of a node 
      that is not managing any entity. 
      Figure 7-46 Managed Entities - No Entities
      You can modify or remove the existing managed devices from the SEA WUI. 
      Enter the required details in the SEA WUI and Click Apply Changes button 
      to modify the existing managed devices. Click Undo Changes button to 
      cancel the modifications. 
      To remove the managed devices, check the device name and Click Delete 
      button. Click Delete All to delete all the managed devices. 
      Refer to section 3.13 "Managed Entities (Command View EVA server, EVA, 
      WBEM Server) Commands" for information on adding an EVA from the Command 
      Line Interface (CLI). 




           ===========================================================================

      8 
      *** Translation, Analysis, and Summary *** 
      This chapter describes event translation and explains how to view and 
      interpret translation information. It also describes log file analysis, 
      including automatic and manual analysis and how to view and interpret 
      analysis information. Procedures for simulating automatic analysis are 
      described as well. Exceptions that impact the results produced by summary 
      operations also are detailed. 
        Translation, Analysis and Rules
        Manual Translation
        Translating Events
        Automatic Analysis
        Manual Analysis
        Resource Usage During Analysis
        Interpreting Analysis Information
        Interpreting Time Stamps
        Simulation of Automatic Analysis
      8.1 Translation, Analysis and Rules 
      The results produced by translation and analysis are dependent on rule 
      sets. The rules sets are developed by Serviceability Engineers and 
      registered with SEA. These rule sets determine what problem reports will 
      be generated in response to the contents of a log file and determine what 
      translated data is presented in SEA. 
      For more information on rule sets, see Chapter 9. 
      8.2 Manual Translation 
      SEA can translate the events in a binary event log and send the results to 
      your computer. This activity is known as manual translation. 
      On supported platforms, SEA can read and translate error logs produced by 
      any of the supported operating systems. For example, you can use the web 
      interface running on your PC to connect to a Director running on a Tru64 
      UNIX system to read, translate, and analyze an event file produced 
      previously on an OpenVMS system. 
        8.2.1 Translating Events
      Translation information is available from the CLI and the web interface. 
      See the following chapters for information on translating events: 
        CLI--Chapter 5 
        Web Interface--Chapter 7 
        8.2.2 Translation Defaults
      By default some events are not processed. Under normal operation, 
      correctable events are not translated. The events that are usually 
      filtered include: 
        Correctable System events (entry types 620 and 630)
        Correctable Error Throttling Notification events
        Miscellaneous events not used by analysis, such as:
          Time Stamp events
          Volume Mount/Dismount events
          Cold Start (System Boot) and Shutdown events
          Software-related events
        8.2.3 Translation Report Type
      When you translate an event, you can choose between brief and full output. 
      The content differences between full and brief output are defined in the 
      rule sets. Brief output generally only contains the most important data 
      items from the event while full output generally includes most of the data 
      items from the event. Since the exact contents of each report type are 
      defined by the rules used to generate the report, the type of information 
      contained in brief and full reports may vary for different events. 
        8.2.4 Interpreting Translation Information
        *** Note ***


          Translated events include a timestamp. For information on interpreting 
          this information see Section 8.6.



      A translated binary event consists of three layers of information: 
      overall, frame, and field. 
          8.2.4.1 Overall
      The overall binary event contains one or more translated frames of 
      information. There are several types of binary events, each identified by 
      its class name. In addition to the frames, some other information is 
      stored at the overall layer, such as: 
        The class name of the binary event (passed to Event Analysis but not 
        displayed in the translated output in the CLI or web interface)
        The "match keys" for the event, a set of strings used in identifying 
        analysis rules that may fire for this event (not displayed in the 
        translated output in the CLI or web interface)
          8.2.4.2 Frame
      A frame within an event consists of one or more translated fields of 
      information. There are many types of frames, each identified by its label. 
      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
        The frame's label, displayed at the beginning of each frame
          8.2.4.3 Field
      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
        The field's value (of a type defined by the type of field) which is 
        displayed in text form
          8.2.4.4 Typical Frame of a Translated Binary Event
      A typical frame of a translated binary event appears as follows: 
      HPM System Event Frame Subpacket - Version X
      HPM_Elapsed_Time_Since_Srm_Boot 947                  Seconds Since Last    
                                                        Console Boot 
      HPM_Event_Info_Block_1          x0040 AB81 0F0F 0010 H-Switch System Event 
                                                           Information 
         HPM_System_Event_Code[7:0]  x10                  HS Temperature in 
                                                           Yellow Zone 
         HPM_Supplementary_Code[15:8] x0                   Supplementary Code 
         Gp0_Valid[16]                x1 
         Gp1_Valid[17]                x1 
         Gp2_Valid[18]                x1 
         Gp3_Valid[19]                x1 
         Hs_P0_Valid[24]              x1 
         Hs_P1_Valid[25]              x1 
         Hs_P2_Valid[26]              x1 
         Hs_P3_Valid[27]              x1 
         Csb_Master_Ena[32]           x1 
         3_3_Dcok_2[42]              x0                   0 = NOT OK if
                                                          Regulator 2 is
                                                           Installed 
         2_5_Dcok_2[44]              x0                   0 = NOT OK if
                                                          Regulator 2 is
                                                           Installed 
         Pll_Dcok_2[46]              x0                   0 = NOT OK if
                                                          Regulator 2 is
                                                           Installed 
         Csb_Address[55:48]           x40 

      This frame contains 17 fields. Each field has a single value, such as 947 
      (decimal) or x10 (hexadecimal, 16 decimal). Some fields are represented as 
      both a Register (HPM_Event_Info_Block_1) containing the complete 
      hexadecimal value, and again as a series of subfields such as 
      HPM_System_Event_Code[7:0]. The [7:0] indicates that bits 0 through 7 of 
      this register comprise this subfield, bit 0 being the least significant 
      bit. 
          8.2.4.5 Unsupported Entries
      Some of the events logged by a system or device are not used by SEA to 
      diagnose hardware failures. The CLI translate command and the event 
      listing in the web interface translate events with many different entry 
      types, including some not used for analysis. However, there are some cases 
      where SEA cannot translate an event: 
        If the event type is not supported.
        If the system or device logged incorrect data for a supported entry 
        type, causing it to be unrecognized.
      If an event that is not supported or recognized is encountered during 
      translation, an unsupported entry dump is shown in the output. The 
      unsupported entry dump at the end of the event shows the entire event in 
      hexadecimal format, from the first header byte to the last byte of the 
      event. 
      *** Note ***


        Each subsequent release of SEA supports the translation of new event 
        types and incorporates better handling of incorrect input data. Events 
        that currently result in a unsupported entry dump may be correctly 
        translated in a future release.



      The following example shows the translated output for an event that was 
      logged incorrectly. The event should have been logged with major class 250 
      and minor class 0, which SEA would have correctly translated. However, the 
      minor class was 18 and the event was unrecognized. As a result, an 
      unsupported entry dump was generated. 
      Event: Unknown Combined Entry Type - UNSUPPORTED ENTRY - Major_Class: 250
      Minor_Class: 18 occurred at Mon, 13 Aug 2001 18:30:36 +0200

      COMMON EVENT HEADER (CEH) V2.0
      OS_Type 1 -- Tru64 UNIX
      Hardware_Arch 4 -- Alpha

      CEH_Vendor_ID 3,564 -- Hewlett-Packard Company

      Hdwr_Sys_Type 35 -- GS40/80/160/320 Series

      Logging_CPU 0 -- CPU Logging this Event
      CPUs_In_Active_Set 24
      -- Unknown Combined Entry Type -
      Entry_Type 18,250 UNSUPPORTED ENTRY -
      Major_Class: 250
      Minor_Class: 18

      DSR_Msg_Num 1,969 -- AlphaServer GS320
      Chip_Type 11 -- EV67 - 21264A
      CEH_Device 255
      CEH_Device_ID_0 x0000 0000
      CEH_Device_ID_1 x0000 0000
      CEH_Device_ID_2 x0000 0000
      Unique_ID_Count 3
      Unique_ID_Prefix 11,248

      TLV Section of CEH
      TLV_DSR_String AlphaServer GS320 6/731
      TLV_OS_Version Tru64 UNIX V5.1 (Rev. 732)
      TLV_Sys_Serial_Num QBB7.AJK01
      TLV_Time_as_Local Mon, 13 Aug 2001 18:30:36 +0200
      TLV_Computer_Name abcd101

      com.compaq.svctools.desta.services.decomposers.DecompDataException:
      EXCEPTION: Entry_Type_Support.java, DUNIX_Entry_Type(), No support for 
this
      DUNIX Entry Type... Major_Class is: 250 Minor_Class is: 18
      0000: FE FF FF FF 0C 01 00 00 ?yyy....
      0008: 48 01 00 00 02 00 00 00 H.......
      0010: 01 00 04 00 EC 0D 00 00 ....i...
      0018: 23 00 00 00 00 00 00 00 ........
      0020: 00 00 00 00 18 00 00 00 ........
      0028: FA 00 12 00 B1 07 00 00 u.......
      0030: FF 00 05 00 02 18 00 00 y.......
      0038: 01 00 00 00 0B 00 00 00 ........
      0040: 00 00 00 00 00 00 00 00 ........
      0048: 00 00 00 00 03 00 F0 2B ......?.
      0050: 00 00 00 00 00 00 00 00 ........
      0058: 00 00 00 00 00 00 00 00 ........
      0060: 00 00 00 00 00 00 00 00 ........
      0068: 00 00 00 00 00 00 00 00 ........
      0070: 00 00 00 00 00 00 00 00 ........
      0078: 05 00 00 00 61 00 1F 00 ....a...
      0080: 43 6F 6D 70 61 71 20 41 Compaq.A
      0088: 6C 70 68 61 53 65 72 76 lphaServ
      0090: 65 72 20 47 53 33 32 30 er.GS320
      0098: 20 36 2F 37 33 31 00 00 .6.731..
      00a0: 81 00 22 00 43 6F 6D 70 ....Comp
      00a8: 61 71 20 54 72 75 36 34 aq.Tru64
      00b0: 20 55 4E 49 58 20 56 35 .UNIX.V5
      00b8: 2E 31 20 28 52 65 76 2E .1..Rev.
      00c0: 20 37 33 32 29 00 00 00 .732....
      00c8: C1 00 0B 00 51 42 42 37 A...QBB7
      00d0: 2E 49 4F 52 30 31 00 00 .AJK01..
      00d8: 41 00 18 00 32 30 30 31 A...2001
      00e0: 30 38 31 33 31 38 33 30 08131830
      00e8: 33 36 2C 30 30 30 30 32 36.00002
      00f0: 30 30 00 00 21 01 14 00 00......
      00f8: 68 73 31 31 30 31 61 00 abcd101.
      0100: 00 00 00 00 00 00 00 00 ........
      0108: 00 00 00 00 FA 00 00 00 ....u...
      0110: 20 00 00 00 6D 63 68 61 ....mcha
      0118: 6E 31 3A 20 20 6E 6F 64 n1...nod
      0120: 65 20 32 20 68 61 73 20 e.2.has.
      0128: 63 6F 6D 65 20 6F 6E 6C come.onl
      0130: 69 6E 65 0A 00 00 00 00 ine.....
      0138: 00 00 00 00 E8 00 00 00 ....e...
      0140: 48 01 00 00 25 7E 3C 5E H.......


      8.3 Automatic Analysis 
      Automatic analysis is the immediate analysis of an event that has been 
      captured and decomposed by SEA as soon as the event is generated by the 
      system (or shortly thereafter), regardless of any interfaces that may be 
      running. No user intervention is required. Automatic analysis is always 
      enabled while the Director is running. The Director is always running 
      unless it is manually stopped or, during installation, you chose not to 
      start the Director when the system is rebooted (HP-UX, Linux, or OpenVMS 
      systems). 
      Problem reports resulting from automatic analysis are sent to all 
      interfaces and to all recipients that are set up to be notified. 
      See Chapter 11 for information about setting up notification services. 
        8.3.1 Scavenge
      Automatic analysis processes events as they occur. However, when the 
      Director is stopped, SEA indicates the last event from the binary log file 
      that was processed in the analysis database. When the system is restarted, 
      SEA checks the database to see which events have been processed and 
      processes all the events that occurred after that point. This operation is 
      referred to as scavenging. The scavenge operation finds events that are 
      still pending processing and ensures that no events are missed, even when 
      the system is restarted. The first time scavenge occurs, it processes the 
      entire event log. Once this is complete, new events are processed as they 
      occur. The scavenge operation occurs four minutes after the Director is 
      started. If the Director is started and stopped within four minutes, no 
      scavenge occurs. 
      Initially, the entire system event log is read to find any events that can 
      be analyzed. A filter is then applied to the analyzable events. All 
      analyzable events that occurred within a week of the current time are 
      processed. 
      If there are no analyzable events, the scavenge feature becomes dormant 
      and a marker representing an unsupported system is stored in the automatic 
      analysis database. As long as the unsupported system marker is present on 
      the system, no scavenging occurs. If there is at least one recognized 
      event, scavenging occurs every time the Director is stopped and started 
      Scavenging and the Web Interface 
      If you connect to the Web Interface before scavenging begins, events that 
      arrive while the Web Interface is running will appear in the Real-Time 
      Monitoring view. All the events that arrive before scavenging starts are 
      processed once scavenging begins and any problem reports that result from 
      scavenging also appear in the Real-Time Monitoring view. However, any 
      events that were added to the event log before the Web Interface was 
      started will not appear in the Real-Time Monitoring view. 
        8.3.2 Reset 
        *** Caution ***


          Resetting the automatic analysis database can significantly impact the 
          results seen from future analysis. 



      In rare cases, you may by asked to reset the automatic analysis database 
      as part of troubleshooting an operational problem with SEA. Be aware that 
      resetting the database erases all active callouts and stored analysis 
      data. After resetting, the database only retains the following: 
        FRU configuration data for the hardware present 
        A scavenging marker indicating the last event read from the system 
        binary event log 
      Follow these steps to reset the automatic analysis database. For the 
      procedure to work, the database must be uncorrupted and functioning 
      properly: 
        Stop the Director (see Section 3.8). 
        Issue the wsea reset command (only available in the new common syntax). 
        Restart the Director (see Section 3.7). 
      Why a Reset Affects Future Analysis 
      A reset clears all active problem reports and storage units. Storage units 
      are records of past events that some rules use for thresholding and 
      multiple event analysis. After a reset, the lack of these records can 
      significantly change analysis results. 
      For example, SEA can accumulate storage units that count toward 
      satisfaction of a threshold filter. When a reset erases the units, problem 
      reports that occur at the threshold may be delayed (because the count 
      started over) or even completely suppressed. 
      The scenario usually involves correctable events. SEA generally reports 
      uncorrectable faults when they occur, but correctable events such as 
      intermittent disk read errors may be subject to threshold filtering. In 
      other words, SEA only sends a problem report when enough correctable 
      events occur within a specified time frame. This allows SEA to signal that 
      a device is suspect even though a hard fault has not happened yet. 
      To reduce the impact of resetting, first review recent events (the minimum 
      recommendation is to review the past 24 hours). During the review, look 
      for recurring events, typically correctable errors, that involve any 
      device that has not already been called out in problem reports. These 
      events can indicate suspect devices. 
        8.3.3 Disable
      If necessary, automatic analysis can be disabled from the CLI as described 
      in Chapter 5. You may want to disable automatic analysis if SEA is running 
      on a platform such as HP-UX or Linux, where a native error log is not 
      currently analyzed. 
      8.4 Manual Analysis 
      You can open a binary event log file and request that the events be 
      translated and analyzed. This activity is known as manual analysis. Unlike 
      automatic analysis, manual analysis relies on the time stamp information 
      included with each event to determine when an event occurred. 
      Manual analysis can be performed from all the interfaces. See the 
      following chapters for information on manual analysis: 
        CLI--Chapter 5 
        Web Interface--Chapter 7 
      Regardless of the platform where it is installed, SEA can read and analyze 
      binary event logs produced by any of the supported operating systems. 
        8.4.1 Resource Usage During Analysis
      Whenever SEA starts, and when you run manual analysis, the program appears 
      to use a lot of system resources and processor cycles. However, SEA uses 
      only the capacity that is not being asked for by other programs. 
      SEA always relinquishes processor cycles to other programs whenever they 
      need them. In other words, the program uses whatever resources are 
      available. 
      At startup SEA needs the available capacity for the scavenge process. 
      Depending on the system, and the size and content of the log, the initial 
      startup pass can take many minutes or even hours to complete. After 
      completing the scavenge process, SEA drops into idle mode, where resource 
      usage hovers at only a few percent. 
      If you run SEA in manual mode, large amounts of system resources and 
      processor cycles also might get used. As in the case of startup in 
      automatic mode, the condition is directly related to the size and content 
      of the log being processed. Once again by design, SEA uses as many 
      resources as are available until processing is completed. 
      You can speed processing by managing the system error log so that it does 
      not grow indefinitely. One way to accomplish this is to periodically 
      archive and reset the current error log by following the guidelines in the 
      WEBES Installation Guide. When you are using manual analysis, it may be 
      beneficial to filter large log files in order to improve processing times. 

      8.5 Interpreting Analysis Information 
      *** Note ***


        Problem reports generated by analysis include a timestamp. For 
        information on interpreting this information see Section 8.6.



      A report consists of a set of String and Value Pairs (SVP). A SVP can be 
      short, for example: 
      Severity:
          MAJOR

      An SVP also can be extensive, such as the Full Description or Evidence 
      SVPs, which can contain many lines of information (see Appendix  for an 
      output example). A problem report resulting from event analysis typically 
      contains the following Strings, with Values describing the analysis 
      results. 
        8.5.1 Problem Report Times
      The Problem Report Times designator indicates the time when SEA generated 
      the Problem Report, and is unrelated to the time of the event or events 
      that caused the problem report. 
        8.5.2 Managed Entity
      The Managed Entity designator provides service information regarding the 
      system on which the problem was found. This includes the system host name 
      (typically the computer name for networking purposes), and the type of 
      computer system. 
        8.5.3 Service Obligation
      The Service Obligation designator provides information about the service 
      provider and the state of the service contract. 
        8.5.4 Brief Description
      The Brief Description designator provides a high level description of the 
      event. This typically includes whether the error event is related to the 
      CPU, the system (PCI or Storage, for example), or the environmental 
      subsystem within this managed entity. 
        8.5.5 Callout ID
      The Callout ID designator provides information about the analysis rule 
      set. Most characters within this designator are used for HP-specific 
      reserved purposes. 
        8.5.6 Severity
      The Severity designator provides the service relevance of the occurrence 
      of the problem found. The current severity hierarchy is shown in Table 
      8-1. 
        Table 8-1 Problem Severity Levels 
        +-----------------------------------------------------+

              Severity Level
              ----------
              Comments
              ----------

              MAJOR 
              Fatal or serious problem that requires immediate service if not 
              already administered.

              MINOR 
              Non-Fatal problem that requires service.

              WARNING 
              A problem that can wait to be fixed at the next scheduled 
              maintenance time.

              INFORMATIONAL 
              A purely informational event, such as an SEATEST report, or else a 
              problem that can be corrected by the customer without the service 
              provider. Example, an enclosure PCI or fan door open.





        +-----------------------------------------------------+




        8.5.7 Reporting Node
      The Reporting Node designator is the node from which the error was 
      reported. It is synonymous with the Managed Entity host name when SEA is 
      used for system diagnosis for the system on which it is running. For 
      future implementations, this may reflect a system server reporting about a 
      client for which SEA is performing diagnosis within an enterprise 
      computing environment. 
        8.5.8 Full Description
      The full description designator provides detailed error information about 
      the event. This can include the detected fault or error condition 
      description, specific address or data bit where this fault or error 
      occurred, and other service related information. 
        8.5.9 FRU List
      The Field Replaceable Units (FRU) List designator lists the most probable 
      defective FRUs. This list indicates that qualified service needs to be 
      administered to one or more of these FRUs. This information typically 
      provides the FRU probability, manufacturer, system device type, system 
      physical location, part number, serial number, and firmware revision level 
      (if applicable to the FRU). 
        8.5.10 Evidence
      The Evidence designator provides the error event information that 
      triggered the SEA Problem Report. The evidence shown depends on the system 
      that generated the error log and the registered rules. As a result the 
      contents of the evidence field may vary. 
      Typically, the evidence includes the following: 
        The time stamp of the event responsible for the callout.
        The event identifier, which is displayed differently depending on the 
        responsible rule set. (In some cases, the event identifier uses new 
        common event header Unique_ID_Prefix and Unique_ID_Count components. 
        Where the Unique_ID_Prefix refers to an OS-specific identification for 
        this event type and the Unique_ID_Count indicates the number of this 
        event type that occurred.)
        The ruleset name and revision number may be included depending on the 
        rule set.
        8.5.11 Versions
      The SEA Version and WCC Version designators provide the versions of SEA 
      and WEBES that created the problem report. 
      8.6 Interpreting Time Stamps 
      If an event in a binary log includes a Storage Event Header (SEH) or 
      Common Event Header (CEH), that information is used to provide the time 
      stamp information for analysis and translation results. If the event only 
      includes a Windows NT(R) header, no time stamp is included with analysis 
      results. 
      In addition, when you translate an event that includes a SEH or CEH header 
      in addition to a Windows NT header, both time stamps are shown in the 
      translation results. However, unless the system responsible for logging 
      the event is located in the GMT time zone, the time stamps will be 
      different. 
      The event time also is displayed in the event description (located at the 
      top of a translated event). Depending on the contents of the event and the 
      SEA interface used to translate it, the translated output may include 
      different information: 
        If the event includes a SEH or CEH header, the time stamp information 
        from that header is included in the event description. If the header has 
        invalid date information the current date is shown along with an error 
        message.
        If you are using the web interface and the event only has a Windows 
        header, no date information is shown in the event description.
        If you are using the CLI to send the translation to the screen or a text 
        file and the event only has a Windows header, the date information from 
        the header is included in the event description.
        If you are using the CLI to send the translation to a HTML file and the 
        event only has a Windows header, no date information is shown in the 
        event description.
      SEH and CEH Headers 
      SEH and CEH time stamps are stored as strings and reported in the 
      TLV_Time_as_Local field of a translated event. This field has the 
      following format: 
      Jan 11, 2002 3:06:09 AM GMT-0600

      This indicates the time the event was logged, in the time zone where the 
      system responsible for logging the event is located. The time zone is 
      shown as an offset, in hours, from GMT. 
      Windows Headers 
      The Windows NT header stores time stamp information as an integer 
      indicating the number of seconds that have elapsed since epoch (January, 1 
      1970 00:00:00 AM GMT). These integers are translated into a date and time 
      and reported in the WNT_GMT_Time_Generated and WNT_GMT_Time_Written fields 
      of a translated event using the following format: 
      Jan 11, 2002 9:06:09 AM GMT

      Since the Windows NT header does not include any information about the 
      time zone where the logging system is located, the GMT time zone is used. 
      This does not mean the logging system is located in the GMT time zone. 
      8.7 Simulation of Automatic Analysis 
      SEA can simulate the occurrence of events and their automatic analysis. 
      The events are translated and analyzed as if they occurred on the local 
      system and events and problem reports from analysis appear as automatic 
      events do. Using the simulation, you can perform and end-to-end test of 
      SEA. 
      *** Note ***


        Problem reports created by simulated automatic analysis are identified 
        as test callouts so that no action is taken by the customer service 
        center. Translation results also indicate that the output was generated 
        by the test command.



      The wsea tes[t] no longer accepts the "inp[ut]" argument. Hence the 
      following command that existed in WEBES versions prior to 4.5 has been 
      replaced with a new command. 
      wsea tes[t] inp[ut]

      This command is now replaced with wsea ana inp[ut] command. See section  
      5.6.2 Manual Analysis for the new syntax. Use the following command to 
      test SEA, from event detection to analysis and notification: 
      wsea test 

      This command sends an event with header fields but no further content to 
      the system's error logging API. The action taken with this event is 
      dependent on the system: 
      HP-UX, Linux, and OpenVMS 
      If the command was run on a supported platform, the system's error logging 
      service takes the event content and wraps it with a Common Event Header 
      (CEH). This is necessary because SEA only recognizes events with a CEH or 
      a Storage Event Header (SEH). After the CEH is created and all its fields 
      are populated, the event is written to the error log where it can be 
      processed by automatic analysis, generate a problem report, and trigger 
      notification. 
      *** Note ***


        The event generated by the test command will be logged with a CEH on the 
        following operating systems and platforms:
        OpenVMS 7.1-2 and 7.2 and above on all platforms



      Windows 
      The error logging service on Windows does not wrap event content with a 
      CEH since that is usually done by the device drivers themselves. So, like 
      a device driver, the test command creates a mock CEH which is used as the 
      event content and passed to the system error logging API. The command does 
      not provide values for all the fields in the mock CEH. Only the fields 
      critical to translation, analysis, and human identification (including 
      time, computer name, OS type and event ID) are given valid values. Most 
      other fields are set to 0 or NULL values and do not affect translation or 
      analysis. After Windows receives the event, it adds a Windows NT header 
      and the event is appended to the system error log. Once in the error log 
      the event is processed by automatic analysis, generates a problem report, 
      and triggers notification. 
        8.7.1 Bypassing The System Error Log
      Use the following command to test SEA without sending an event through the 
      system error log: 
      wsea test nosystem 

      The Director must be running in order to use the test nosystem command. 
      The nosystem option sends an event directly to the SEA event reader, 
      bypassing the system altogether. This command is used to facilitate 
      troubleshooting of a problem and determine if it is caused by SEA. 
      Regardless of the platform, the command creates a mock CEH for the event 
      so that it can be recognized. Since SEA also requires an NT event header 
      when running on Windows platforms, a mock NT header also is created when 
      the command is executed on an Windows system. Only the NT header fields 
      necessary for translation, analysis, and human identification are 
      populated with valid values. Fields set to 0 or NULL do not affect 
      translation or analysis. 
      Since the event created by the nosystem option has a CEH (and for Windows, 
      a NT header as well), it should always be recognized by SEA. However, 
      since the event is never appended to the system error log, it cannot be 
      seen when manually translating or analyzing the system error log. In 
      addition, the problem report immediately expires and, as a result, it will 
      not appear if you subsequently run the wsea report command. The only ways 
      to view the problem report generated by analysis is by using the "Real 
      Time Monitoring" view in the web interface, or the problem report logging 
      functionality (see Section 5.6.1.2). The wsea report command will not show 
      the problem report because it is designed to expire immediately. 
      *** Note ***


        The nosystem option creates an event that can be translated and analyzed 
        for all the supported operating systems, regardless of whether or not 
        the hardware platform is supported. 



      8.8 Interpreting Summary Information 
      If a log file contains invalid data or lacks a recognizable (CEH or SEH) 
      header, the results produced by the summary command will be affected. 
        If the final event in a log file contains invalid data, SEA cannot 
        determine the date information for the Last Entry Time field. In this 
        case, the current date and time are shown in the Last Entry Time field.
        If an event does not include a recognized header, the event type is 
        reported as 0. In this case the summary command indicates that the event 
        is Unrecognized/Unsupported. This applies to events that only contain a 
        Windows header even if they are translated correctly. 
      The new command to simulate automatic analysis using a saved error log 
      file is: 
      wsea ana input eventlog notify



            ===========================================================================

      9 
      *** Rule Sets *** 
      This chapter describes the rule sets and instance files used by SEA. 
      Information on managing rule sets also is given. 
        Rule Sets
        Analysis Data
        Managing Rule Sets
      9.1 Rule Sets 
      Binary events are analyzed by using an analysis engine to apply rules to 
      them. Rules are designed to fire when a particular criteria, such as a 
      threshold, is met. For example, if the number of events within a given 
      time frame exceeds the threshold specified in a rule set, the rule fires. 
      Depending on the circumstances, a event may or may not fire any rules. 
      Alternately, a single event can fire multiple rules. When a rule fires, it 
      may or may not produce reports. In the case where reports are generated, a 
      rule can create one or multiple reports. A report may be generated 
      immediately, or may be generated after a gestation time period defined by 
      the rule. Each report is stored in a instance file. After the report's 
      expiration time period, as defined by the rules, the report is removed 
      from the instance file. 
      Rules also are responsible for determining the output presented for a 
      translated event. 
      Analysis rules are coded by HP serviceability engineers or other domain 
      knowledge specialists. These rule sets are stored in .jar files located in 
      the svctools\common\jars directory. Rule sets pertaining to the supported 
      platforms are located in the .jar files and can be installed, or 
      "registered," for use with SEA. A rule set can later be "unregistered" if 
      it is no longer applicable. 
      *** Note ***


        It is possible to run SEA without any rule sets registered (if the rule 
        sets have been unregistered or deleted). However, if there are no 
        registered rule sets, analysis will not generate meaningful results. The 
        problem report generated by analysis indicates if there are no 
        registered rule sets or no applicable rule sets.



      9.2 Analysis Data 
      SEA stores analysis data in the svctools\common\ca\data directory. These 
      files contain information about: 
        The rule set files to be used for analysis
        Input entry classes, derived from data in the binary events. Typically, 
        the input classes are deleted after reports have been generated from 
        them.
        Intermediate data such as complex storage classes, derived during 
        analysis
        Output report classes (analysis results)
      You can clear this state data using the wsea reset command described in 
      Chapter 8. 
      9.3 Managing Rule Sets 
      SEA is installed with all rule sets pre-registered. You can manipulate the 
      rule sets in the following ways: 
        View the rule sets that are currently registered (see Section 9.3.1).
        If you receive or create new analysis rule files, you can register the 
        new rule sets as needed (see Section 9.3.2). 
        Unregister rule sets that are no longer needed (see Section 9.3.2). 
        Re-register all the default rule sets (see Section 9.3.2).
        *** Note ***


          This section describes how to manage rule sets using the new common 
          syntax. For the equivalent old common syntax commands, see Appendix E.



        9.3.1 Viewing Registered Rules
      Using the CLI or web interface, you can view the rulesets that are 
      registered for use with SEA. 
          9.3.1.1 CLI
      The new common syntax lis command provides a list of the paths and 
      versions of the knowledge files registered with DeCOR. The syntax for the 
      command is shown here: 
      wsea lis

      Output 
      An example of the output is shown here: 
            Ruleset                      Version
      ==================== ===================================
      CATEST               Rules_v1_1
      DS10                 Rev_030509
      DS20                 Rev_030320
      DS25                 Rev_030509
      ES40                 Rev_030512
      ES45                 Rev_030509
      GS1280_EV7           V4_2
      GS1280_IO7           V4_2
      GS1280_RBOX          V4_2
      GS1280_SM            V4_2
      GS1280_ZBOX          V4_2
      GS320_CE             V53_0953
      GS320_SE             V53_0953
      GS320_STARTUP        V53_0953
      GS320_UCE            V53_0953
      MCII                 Rev_1
      Storage              Rev_2.20
      Storage_HSV_DRM      Rev_X1_00
      Storage_HSV_EMU      Rev_X1_00
      Storage_HSV_EXEC     Rev_X1_00
      Storage_HSV_FCS      Rev_X1_00
      Storage_HSV_FM       Rev_X1_00
      Storage_HSV_SCMI     Rev_X1_00
      TS202c               Rev_4_1_A0
      Vstor                Rev_1.00

        9.3.1.2 Web Interface
      From the web interface: 
        Click the Settings button from the toolbar.
        Select the Director Settings tab.
      All the available rule sets are listed with a check box. Rule sets with a 
      selected check box are registered. 
        9.3.2 Registering and Unregistering Rule Sets
      You can register a set of rules using the CLI or the web interface. 
          9.3.2.1 CLI
      The syntax for registering and unregistering rule sets is shown here (the 
      first command shown is used to register rule sets and the second command 
      is used to unregister rule sets). 
      Using the new common syntax: 
      wsea reg [ruleSet] 
      wsea unr [ruleSet] 

      Where ruleSet represents the name or names of the desired knowledge files. 
      If you do not enter any rule set names, all the default rule sets are 
      registered. 
      Wildcards cannot be used to specify multiple rule set names. To register 
      or unregister all rules supplied with WEBES, do not specify any rule set 
      names, as in: 
      wsea reg
      wsea unr

      *** Note ***


        If you are running analysis in the CLI, you will see the changes take 
        effect immediately. However, to run analysis in the web interface, you 
        must stop and restart the Director first (see Sections 3.8 and  3.7). 



        9.3.2.2 Web Interface
      To register or unregister a set of rules using the web interface, do the 
      following: 
        Click on the Settings button in the toolbar.
        Click the Director Settings tab at the bottom of the window.
        Click the Register Knowledge button in the navigation frame (Figure 
9-1).
        Figure 9-1 Rules Files
        All the available rule sets are listed with a check box. If the check 
        box is selected the rule set is registered, otherwise it is not 
        registered. 
        Register or unregister the necessary rule sets.
          To register a rule set that is not registered, select the check box 
          next to its name.
          To unregister a rule set that is currently registered, deselect the 
          check box next to its name.
        Click the Update Knowledge Registration button to save your changes.
        *** Note ***


          Changes will not take effect in the web interface for automatic 
          analysis until the analyzer is restarted. This is done by stopping and 
          restarting the Director. These changes will not affect manual analysis 
          jobs already in progress.



        Stop and restart the Director to apply the changes (see Sections 3.8 and 
         3.7). 


     
      ===========================================================================

      10 
      *** Configuration *** 
      This chapter describes configuration, including getting and changing the 
      configuration, global and component configuration attributes, and creating 
      and resetting the configuration. 
        Viewing the Configuration
        Component Configuration Attributes
        Changing the Configuration
        Global Configuration Attributes
        Profiles
        Creating and Resetting the Configuration
        Editing the Desta Registry
        Configuring Operating System-Specific Services
      10.1 Viewing the Configuration 
      You can view the configuration settings for your local Director from the 
      web interface. 
      To view the configuration, use the following procedure: 
        Select the Settings button from the toolbar. 
        Select the Director Settings tab. 
        The Director Settings window is shown in the display frame (see Figure 
        10-1). By default the Settings button is selected.
        Figure 10-1 Settings
        Select the service whose attributes you want to view from the drop-down 
        list. 
        By default, Global Attributes are shown; however, the drop-down list 
        contains all the services currently enrolled in the system. The 
        SEAWebService was selected in Figure 10-2. 
        Figure 10-2 Attribute Display
        To view the current value of an attribute, Click on its name on the left 
        side of the window (see Figure 10-2). 
        The attribute's full name and current and default values, are displayed 
        on the right side of the window along with a description of the 
        attribute.
        The automatic start attribute (autoStart) was selected in this example.
      10.2 Component Configuration Attributes 
      Attributes for all components fall into two categories (indistinguishable 
      in the web interface): common attributes and extended attributes. 
      Common Attributes 
      Attributes that each component contains by default are known as common 
      attributes. They are still owned by their component, so the autoStart 
      attribute for one component is independent from the autoStart attribute of 
      another component. 
      Extended Attributes 
      Attributes specific to a particular component are known as extended 
      attributes. For example, the "HTTPServerPort" attribute of the 
      "SEAWebService" component does not exist in any other components, since it 
      only applies to the web service. 
      10.3 Changing the Configuration 
      You can modify the attribute configuration settings from the web interface 
      or make limited changes from the CLI. 
      Normally, it is not necessary to change the attribute settings. The 
      following list describes the attributes that most often need changed and 
      the location of the attribute in the web interface. 
        commSocketListenerPort (Communications, Socket Listener Port 
        Number)--under Global Attributes. Used to change the communications port 
        number. Do not change the commSocket ListenerPort attribute from the web 
        interface, see Section 10.4.2 for information on configuring ports.
        You may need to change the port number if there is another, conflicting 
        application.
        commConnectionTimeout (Communications, Connection Handshake 
        Timeout)--under Global Attributes. Used to change the amount of time 
        that can elapse before the system times out.
        You may want to change the Timeout setting if your network is very slow 
        and you want to allow more time for connections before timing out.
        autoMode (Automatic Mode)--under the EvtAnalyzer attribute. Used to 
        enable or disable automatic processing of the binary system event log.
        You may want to change the autoMode setting if there are event entries 
        for unsupported hardware in the event log.
        HTTPServerPort--under the SEAWebService attribute. Used to change the 
        port used for http communications. See Section 10.4.2 for more 
        information on configuring ports.
        You may need to change the port number if there is a usage conflict.
        10.3.1 CLI
      The CLI has limited configuration abilities. 
      Socket Ports 
      The socket ports can only be modified from the command line. See Section 
      10.4.2 for details on changing the ports. 
        10.3.2 Web Interface
      Using the web interface, you can change attributes from the Configuration 
      Settings window (see Figure 10-1). Attributes that can be changed have a 
      changeable field and three buttons in the System Configuration window. You 
      must select an attribute to determine if it can be changed. 
      To change the value of an attribute, enter the new value in the New 
      Setting field. Depending on the attribute that you want to change, you may 
      be able to select the new attribute value from a drop-down list or change 
      a check-box setting. After changing attributes you have several choices. 
        Click the Change button to apply the changes to the current attribute. 
        Click the Reset button to change the values of the current attribute 
        back to their last applied value.
        Click the Default button to change the values of the current attribute 
        to their default values.
      If you leave the Configuration Settings window without clicking the Change 
      button, your modifications will be lost. 
      10.4 Global Configuration Attributes 
      The attributes listed under "Global Attributes" affect every component in 
      the SEA system on the current system, whether or not the component has 
      been enrolled in the configuration. 
        10.4.1 Changing the Attributes
      Changes to the Logging attributes (prefaced with "log") take effect 
      immediately. 
      Changes to the Communications and Controller attributes (prefaced with 
      "comm" and "ctrlr," respectively) take effect only when a new SEA process 
      is started (such as the Director or another process that connects to the 
      Director). 
      Be aware that changing a global configuration attribute affects both 
      interfaces. 
        10.4.2 Changing Ports
      Table 10-1 describes the ports used by SEA and indicates whether or not 
      they can be configured. 
        Table 10-1 Ports 
        +-----------------------------------------------------+

              Port Number
              ----------
              Used For
              ----------
              Configurable
              ----------

              7901
              Director-to-Director communications, and communicating with the 
              Director on the local system through the CLI. 
              Yes

              7902
              Director's Web Interface listener port used by the web browser 
              (e.g., http://target.sys.name.here:7902)
              Yes

              7903
              Communication between SEA's applet (running inside the web 
              browser) and the Director.
              No

              7920
              The WEBES WCCProxy process communicates with the Director on this 
              port.
              No.

              1998
              Service Cockpit
              No

              2069/8941
              CSG/QSAP--the port number for CSG v4.5 and v5.0 is 2069. For v3.1 
              and v3.1B it is 8941. (See Section 11.4.2 for more details on 
              CSG/QSAP.)
              Yes

              25
              SMTP mail. This is the standard port used by TCP/IP systems for 
              SMTP (see Section 11.3 for more details on configuring SMTP).
              No





        +-----------------------------------------------------+




      If a port is configurable, you can change the port number used. Most ports 
      are configured using the web interface; however, the 
      commSocketListenerPort, which is used for connections to the Director, can 
      only be modified from the CLI. 
      Connections to the Director 
      The commSocketListenerPort defines the TCP/IP socket port used by the 
      Director to communicate with other processes on the same system or on 
      other systems on the network (Port 7901, by default). 
      *** Note ***


        Do not change the commSocketListenerPort attribute with the web 
        interface. If you do, the Director cannot be stopped from that point on. 
        After the socket port is changed, only a service that is already 
        connected can stop the Director running on the old port. 



      To change the TCP/IP socket port attribute on all operating systems use 
      the following command from the command prompt. 
      desta msg -chgport nnn

      Where nnn is the new port number
      This command changes the port number and then stops the Director and all 
      connected processes. After the Director has finished shutting down, you 
      can safely restart it on the new port. 
      *** Note ***


        If the process hangs unexpectedly under Windows, kill the command and 
        stop the Director manually. Press CTRL-C to exit the CLI command, and 
        then enter net stop desta_service.



      The Director can only communicate with Directors on other systems that 
      have the same TCP/IP socket port number defined in their configuration. 
      You can restrict access to your Director by changing the ports to 
      nonstandard numbers and only disclosing the new port numbers to people who 
      need access. 
      10.5 Profiles 
      When you are using the web interface, your changes to the configuration 
      are saved in a profile. The profile for the current session is saved using 
      the logon name you entered (see Section 7.2). To restore your previous 
      configuration settings when you restart the web interface, simply enter 
      the same logon name. 
      Your profile is saved on the system where you logged on. If you log on to 
      a different system, then it will use the default settings. To customize 
      the settings for the new system, you will again need to create a new 
      profile and change the configuration settings. This is true for each new 
      system you log onto. 
      *** Note ***


        Profile names are case sensitive. Changing between upper case and lower 
        case letters will create additional profiles. To access a profile, you 
        must enter the profile name exactly as it was created.



      10.6 Creating and Resetting the Configuration 
      The first time that SEA is started on a system, a warning similar to the 
      following is written to the Director log file. (See the WEBES Installation 
      Guide and Section 2.5 of this guide for more information on log files.) 
      WARNING on July 19, 2006 10:08:29 PM MDT (0.047 sec elapsed)
      Configuration file 
      /opt/hp/svctools/specific/desta/config/Configuration.dat not found, 
      creating it.

      This warning is expected and correct. The Configuration.dat file is 
      created based on the contents of the ConfigDefaults*.txt file in the 
      svctools/specific/desta/config directory. (The warning example shown is 
      for a HP-UX system.) The classes named in those files will enroll 
      themselves into the configuration, which is then saved as 
      Configuration.dat, a binary file that should not be edited directly. 
      Changes made from the web interface are saved in this file by the 
      Director. This warning should not appear on subsequent starts of the 
      Director. 
      If the configuration becomes damaged, or you wish to return to the default 
      configuration state (the configuration when SEA was first started), make 
      sure no SEA or WEBES processes are running (including the Director 
      process), and delete the Configuration.dat file. When you restart SEA, the 
      file will be recreated with the standard defaults, using 
      ConfigDefaults*.txt the same way it was first time SEA was started. 
      10.7 Editing the Desta Registry 
      The Desta Registry contains information gathered about the user and the 
      system during the installation process. Additionally, you can configure 
      WEBES and SEA by making changes to the registry using the desta dri 
      commands. 
      *** Note ***


        In Windows, the WEBES registry is stored in the DESTA.REG file in the 
        svctools installed directory tree, and should not be confused with the 
        Windows Registry.



      The desta dri commands allow you to add, view, edit, and remove registry 
      keys. 
      *** Note ***


        In OpenVMS, key names and parameters are always put in quotes in order 
        to preserve mixed-case names and values. For example:
        desta dri get "KeyName"



      Adding a Registry Key 
      The desta dri add command creates the key within the registry. This 
      command does not assign any values to the key, but you must create it 
      before you can edit it. To add a key to the registry, enter the following: 

      desta dri add key_name

      Viewing a Registry Key 
      The desta dri get command displays the current value assigned to a key. If 
      the key returns a value of "null" (for example, CA.WUI.OLMsgWait=null) it 
      does not exist, and you will need to add it before attempting to make any 
      changes. To view a key, use the get command: 
      desta dri get key_name

      Editing a Registry Key 
      The desta dri set command allows you to enter one or more values for an 
      existing registry key. Multiple values can be assigned by entering a 
      comma-separated list in quotation marks. To edit a key, use the set 
      command: 
      desta dri set key_name parameter_value

      When entering a comma-separated list: 
      desta dri set key_name "value1,value2,..."

      Removing a Registry Key 
      The desta dri del command deletes all of the assigned values, and removes 
      the key from the registry. To remove a key, use the del command: 
      desta dri del key_name

        10.7.1 Configuring the Message Wait Timeout
      The CA.WUI.OLMsgWait key allows you to set the message wait timeout value 
      for the web interface. For example, you may be experiencing timeouts when 
      loading the list of log files using the Other Logs link. By default, the 
      value is 45 seconds. To reset the timeout to 90 seconds, add and set the 
      key in the Desta Registry. 
      Windows, HP-UX, and Linux 
        Add the key to the registry if it does not already exist:
        desta dri add CA.WUI.OLMsgWait


        Set the value of the key to 90 seconds:
        desta dri set CA.WUI.OLMsgWait 90


        View the new value of the key:
        desta dri get CA.WUI.OLMsgWait

        The system displays the following:
        CA.WUI.OLMsgWait=90


        Stop and restart the Director to apply the changes (see Sections 3.8 and 
         3.7). 
      OpenVMS 
        Add the key to the registry if it does not already exist:
        desta dri add "CA.WUI.OLMsgWait"


        Set the value of the key to 90 seconds:
        desta dri set "CA.WUI.OLMsgWait" 90


        View the new value of the key:
        desta dri get "CA.WUI.OLMsgWait"

        The system displays the following:
        CA.WUI.OLMsgWait=90


        Stop and restart the Director to apply the changes (see Sections 3.8 and 
         3.7). 
        10.7.2 Configuring Additional Log File Directories
      In order to add saved log files to the web interface's navigation tree, 
      files can be saved under the svctools directory, or in one or more 
      directories you specify by editing the Desta registry. 
      To add log files which are saved in directories outside of the svctools 
      path, you must first add the full path of each directory to the 
      CA.WUI.OLDirs key. Multiple directories are added using a comma separated 
      list. 
      For more information on Log Files, see Section 7.4.4. 
      Windows, HP-UX, and Linux 
      Follow these steps: 
        Add the key to the registry if it does not already exist:
        desta dri add CA.WUI.OLDirs


        Set the new value for the key using the full path of each directory:
        desta dri set CA.WUI.OLDirs "directory1,directory2,..."

        For example, in Windows you would enter:
        desta dri set CA.WUI.OLDirs "c:\morelogs,d:\evenmorelogs"

        View the new values for the key:
        desta dri get CA.WUI.OLDirs

        In Windows, the system displays the following:
        CA.WUI.OLDirs=c:\morelogs,d:\evenmorelogs


        Stop and restart the Director to apply the changes (see Sections 3.8 and 
         3.7). 
      To delete the key and remove all directories from the search list, enter: 
      desta dri del CA.WUI.OLDirs


      OpenVMS 
      Follow these steps: 
        Add the key to the registry if it does not already exist:
        desta dri add "CA.WUI.OLDirs"


        Set the new value for the key using the full path of each directory:
        desta dri set "CA.WUI.OLDirs" "directory1,directory2,..."


        View the new value for the key:
        desta dri get "CA.WUI.OLDirs"


        Stop and restart the Director to apply the changes (see Sections 3.8 and 
         3.7). 
      To delete the key and remove all directories from the search list, enter: 
      desta dri del "CA.WUI.OLDirs"

        10.7.3 Enabling Text Entry in Other Logs Pane
      When enabled, the text entry field in the Add Logs screen allows users to 
      add log files by entering the path and filename for an event log located 
      anywhere in the file system (Figure 10-3. For more information, see 
      Section 7.4.4 and Figure 7-16). 
      Figure 10-3 Add Log Files Tab with Text Entry Field Enabled
      When entering a file name into the text entry field (Figure 10-4), the log 
      file must have a .sys, .evt, .zpd, or .errlog extension. If you wish to 
      add a file with a different extension, you will need to rename the file so 
      it uses an acceptable file extension. 
      Figure 10-4 Text Entry Field
      The text field can only be enabled for users you specify in the 
      CA.WUI.OLText key. It cannot be enabled for all users unless you list each 
      user individually. 
      *** Note ***


        The list of usernames assigned to the CA.WUI.OLText key corresponds to 
        the user profile entered by the user at the SEA Logon screen (see 
        Section 7.2). SEA profiles and usernames are not related to the ID a 
        user enters to log on to a system, and they are not authenticated by SEA 
        during the log on process. It is therefore the responsibility of those 
        with knowledge of text entry enabled user profiles to protect them from 
        unauthorized use (i.e., not allowing open access to event logs anywhere 
        on the system).



      Windows, HP-UX, and Linux 
      Follow these steps: 
        Add the key to the registry if it does not already exist:
        desta dri add CA.WUI.OLText


        Set the values for the key by entering a single username, or a 
        comma-separated list of usernames:
        desta dri set CA.WUI.OLText "username1,username2,..."

        For example, in Windows you would enter:
        desta dri set CA.WUI.OLText "bill,ted"


        View the new values for the key:
        desta dri get CA.WUI.OLText

        In Windows, the system displays the following:
        CA.WUI.OLText=bill,ted


        Stop and restart the Director to apply the changes (see Sections 3.8 and 
         3.7). 
      To delete the key and remove the text field for all users, enter the 
      following: 
      desta dri del CA.WUI.OLText


      OpenVMS 
      Follow these steps: 
        Add the key to the registry if it does not already exist:
        desta dri add "CA.WUI.OLText"


        Set the values for the key by entering a single username, or a 
        comma-separated list of usernames:
        desta dri set "CA.WUI.OLText" "username1,username2,..."


        View the new values for the key:
        desta dri get "CA.WUI.OLText"


        Stop and restart the Director to apply the changes (see Sections 3.8 and 
         3.7). 
      To delete the key and remove the text field for all users, enter the 
      following: 
      desta dri del "CA.WUI.OLText"


        10.7.4 Controlling Memory Usage
      The WEBES Director and Analyzer subprocesses run within a Java environment 
      on all the supported operating systems. WEBES can override the default 
      maximum amount of memory used by the Director process and any Java 
      subprocesses that the Director spawns. 
      WEBES controls the memory usage by setting the following two DESTA 
      registry entries: 
        desta.director.maxHeapSize--Controls the memory used by the Director 
        process.
        desta.subprocess.maxHeapSize--Controls the memory used by WEBES 
        subprocesses.
      In Java, the heap is the main block of memory that is allocated by the 
      process. Setting the maximum size of the heap controls how much memory the 
      process can allocate. 
      The following examples show the registry entries with values set: 
        desta.director.maxHeapSize=300m--This registry limits the maximum memory 
        for the Director process to 300 megabytes.
        desta.subprocess.maxHeapSize=200m--This registry entry limits the 
        maximum memory for the Analyzer subprocess (and any other subprocess) to 
        200 megabytes.
        *** Note ***


          WEBES is installed with default heap settings. It is only necessary to 
          adjust the values if you are having problems with out-of-memory 
errors.



          10.7.4.1 Circumstances Requiring Memory Changes
      If the Director hangs or terminates unexpectedly, check the Director log 
      files (see Section 2.5 for more information on log files). If the log 
      files contain errors mentioning "out of memory" conditions, one of the 
      following conditions may apply: 
        Your system has run out of memory or paging space. 
        The Director process has reached its Java memory limits. These limits 
        are set during WEBES installation, but may be overridden by setting the 
        values on the registry entries described in this section. 
      If the Java memory limits are responsible for the problem, you can raise 
      the memory limits applied to the Director process and its subprocesses. 
      After the limits have been increased, you can restart the Director and 
      perform the actions that caused the out of memory error. The limits can be 
      set as high as necessary, and are only constrained by the memory and 
      paging space available on the system. 
      To determine which registry entry to change, find the "out of memory" 
      message in the Director log file. All messages from the subprocesses start 
      with a ">" character at the beginning of the line. If the "out of memory" 
      messages begin with ">" characters, as in the following example, then the 
      subprocess heap limit needs to be raised. 
      > java.lang.OutOfMemoryError
      > at sun.misc.Resource.getBytes(Resource.java, Compiled Code)
      > at java.net.URLClassLoader.defineClass(URLClassLoader.java, Compiled 
      Code) 
      ... 

      The contents of the error message can vary widely. The important element 
      is the OutOfMemoryError, which can be claimed by Java or other parts of 
      the runtime system. 
      If the messages do not contain ">" characters at the beginning of the 
      line, as in the following example, then the Director heap limit needs to 
      be raised. 
      EXCEPTION java.lang.OutOfMemoryError
      at com.compaq.svctools.ca.services.eventreaders.ReaderContext.readEvent 
      (ReaderContext.java, Compiled Code)
      at com.compaq.svctools.ca.services.eventreaders.ReaderContext.getEvent 
      (ReaderContext.java, Compiled Code)

        10.7.4.2 Changing Memory Settings
      Before you begin changing the memory settings, check the current registry 
      values to establish a baseline for your changes. 
      You can view the current values for the Director heap registry entry with 
      the following commands: 
        Windows, HP-UX, and Linux: 
        desta dri get desta.director.maxHeapSize 

        OpenVMS:
        desta dri get "desta.director.maxHeapSize" 

      You can view the current values for the subprocess heap registry entry 
      with the following commands: 
        Windows, HP-UX, and Linux: 
        desta dri get desta.subprocess.maxHeapSize 

        OpenVMS:
        desta dri get "desta.subprocess.maxHeapSize" 

      Once you have established a baseline value, you can modify the memory 
      settings using the procedure for setting the heap size. The procedure 
      varies slightly depending on your operating system. 
      OpenVMS 
      Java on Windows uses more memory as needed up to the imposed limits. 
      However, on OpenVMS, Java allocates the entire maximum heap size at 
      startup for the lifetime of the process. Besides using the following 
      commands to raise the heap sizes, you also can use them to reduce the heap 
      sizes if the defaults are too resource-intensive for your system. Be aware 
      that reducing the values limits the event processing that the Director can 
      perform, and reducing them too much can cause the Director to fail during 
      normal operation. 
      To designate the maximum heap size for the Director set the value of the 
      registry key: 
        Set the value of the registry key by entering the following command at 
        the command prompt:
        $ desta dri set "desta.director.maxHeapSize" "XXm" 

        Where XX is the desired heap size in megabytes.
        Stop and restart the Director to apply the changes (see Sections 3.8 and 
         3.7). 
      To set the maximum heap size for subprocesses, use the following 
      procedure: 
        Set the value of the registry key by entering the following command at 
        the command prompt:
        $ desta dri set "desta.subprocess.maxHeapSize" "XXm"

        Where XX is the desired heap size in megabytes.
        Delete the subprocess command line registry key by entering the 
        following command at the command prompt:
        $ desta dri del "desta.Subprocess.CommandLine" 


        Stop and restart the Director to apply the changes (see Sections 3.8 and 
         3.7). 
      Windows 
      To set the maximum heap size for the Director process, adjust the value of 
      the registry entry: 
        Set the value of the DESTA registry key with the following command:
        C:\> desta dri set desta.director.maxHeapSize XXm 

        Where XX is the desired heap size in megabytes.
        Stop and restart the Director to apply the changes (see Sections 3.8 and 
         3.7). 
      To set the maximum heap size for subprocesses, use the following 
      procedure: 
        Set the value of the registry key by entering the following command at 
        the command prompt:
        C:\> desta dri set desta.subprocess.maxHeapSize XXm

        Where XX is the desired heap size in megabytes.
        Stop and restart the Director to apply the changes (see Sections 3.8 and 
         3.7). 
      10.8 Configuring Operating System-Specific Services 
      Some WEBES services are only appropriate for certain versions of the 
      supported operating systems. This is usually because the earlier, older 
      versions of the operating system do not provide the necessary support. 
      Normally, WEBES determines which services are supported by the OS during 
      installation and copies the necessary files. However, if you upgrade your 
      system's OS version, you may want to add the version dependent services 
      manually. The following sections describe the services that may need to be 
      manually configured. 
        10.8.1 Indictment
      The Indictment service is supported on systems that meet all of the 
      following conditions: 
        AlphaServers only
        OpenVMS only (because WEBES is not being released for Tru64 UNIX as of 
        this release) that maintain a FRU version 6 configuration tree, which 
        includes the hardware models DS15, DS25, ES45, GS* and later models. It 
        does not include DS10, DS20, DS20e, nor ES40 that maintain version 5 FRU 
        trees.
      Indictment enables the system to automatically detect and shut down 
      failing CPUs and certain PCI boards in order to avoid system crashes. See 
      the operating system documentation for more information on component 
      indictment. The following sections describe how to configure Indictment on 
      OpenVMS systems. 
          10.8.1.1 OpenVMS
      Indictment is supported on OpenVMS V7.3-2 and newer. To configure 
      Indictment on an upgraded system, use the following procedure: 
        Access the SVCTOOLS_HOME:[common.ca.install] directory and locate the 
        enabling configuration file ConfigDefaultsIndictment.txt.
        Copy the enabling configuration file to the 
        SVCTOOLS_HOME:[specific.desta.config] directory.
        Run DESTA ChangeEnrollments command:
        desta exec "com.compaq.svctools.desta.configuration.ChangeEnrollments" 
        "-enroll" "ConfigDefaultsIndictment.txt"

      The next time WEBES is started, the Indictment service will be activated. 


     
      ===========================================================================

      11 
      *** Automatic Notifications *** 
      This chapter describes how SEA can automatically notify you or HP Services 
      whenever automatic analysis has detected an event. 
        When Are Notifications Sent?
        Service Events vs. Info Events
        Sending Notifications to Email Addresses
        Sending Notifications to HP Services
        Sending Notifications to Other Monitoring Tools
        The Customer Profile File
      11.1 When Are Notifications Sent? 
      An automatic notification occurs whenever SEA automatic analysis(including 
      simulated automatic analysis) has formed a problem report based on its 
      analysis of one or more correlated events that have been automatically 
      detected on the system. 
      Problem reports generated by manual analysis do not trigger any kind of 
      automatic notification. 
      11.2 Service Events vs. Info Events 
      Starting with version 4.5, SEA automatic analysis detects and reports on 
      two kinds of events: 
         11.2.1 Service Events 
         11.2.2 Informational Events 
        11.2.1 Service Events
      Service Events usually require the attention of HP Services, such as when 
      an FRU has failed and must be replaced. 
      Provided that you have both types of notification enabled, SEA always 
      sends service event problem reports both as emails to you (see Section 
      11.3 Sending Notifications to Email Addresses) and as secure transmissions 
      to HP Services (see Section 11.4 Sending Notifications to HP Services). 
        11.2.2 Informational Events
      Info events generally require the attention of the local system 
      administrator, such as when a disk is running out of space. An info event 
      always includes "CUST" in the problem report heading: 
      HP SEA: CUST: EVA_1: A controller has begun booting: 5005-08B4-0001-483B 

      SEA sends info event reports only to you (see Section 11.3 Sending 
      Notifications to Email Addresses). HP Services is not notified, even if 
      you have a notification service offering enabled. 
      Even though SEA does not log a call to HP Services, you may decide to 
      place your own customer-initiated call if you want help with system info 
      events. 
      Some examples of these kinds of customer-only notifications are: 
        pulling a disk drive
        pulling a power cord or, any sudden loss of AC power
      11.3 Sending Notifications to Email Addresses 
      SEA notifies you about events by automatically sending SMTP email copies 
      of problem reports to the addresses you specify. Although there are no 
      restrictions on what addresses you can list, you probably do not want to 
      send problem reports across the open Internet to recipients outside your 
      company firewall. For example, to reach HP Services, use one of the secure 
      service offerings described in Section 11.4 Sending Notifications to HP 
      Services instead of sending problem reports to a service representative's 
      email address. 
      For email notifications to work, the system must have connectivity to an 
      SMTP server on the TCP/IP network, or it must be an SMTP server itself. 
      Describing how to configure different systems as SMTP servers is beyond 
      the scope of this manual, so see the given operating system documentation 
      if you need help in this area. 
         11.3.1 Settings 
         11.3.2 Disabling Email Notifications 
         11.3.3 Re-enabling Email Notifications
         11.3.4 Firewall Telnet Checking May Inhibit SMTP Email
         11.3.5 Open VMS Mail Notification
        11.3.1 Settings 
      During installation, WEBES asks for an SMTP server address, and for the 
      email addresses that you want to send reports to. Without valid addresses, 
      SEA cannot send email notifications. 
      After installation, you can change these settings by editing the 
      NotifyCA.txt file in a text editor. The NotifyCA.txt file is stored at the 
      following location, depending on your operating system: 
        HP-UX--/opt/hp/svctools/specific/desta/config 
        Linux--/usr/opt/hp/svctools/specific/desta/config 
        OpenVMS--SVCTOOLS_HOME:[SPECIFIC.DESTA.CONFIG] 
        Windows--install_directory\specific\desta\config 
        where install_directory is the directory where SEA was installed 
      The basic format of the NotifyCA.txt file is as follows: 
      SERVER=smtp.server.xyzcompany.com 
      FROM=sendername@xyzcompany.com 
      TO=username1@mailaddress1.com; username2@mailaddress2.com 
      CC=username3@mailaddress3.com 

        SERVER--Enter the address of a system running an SMTP server process, or 
        localhost if the system running SEA also is an SMTP server. 
        FROM--The domain (the part of an email address following the @ symbol) 
        must be a real, registered one. Some SMTP servers do not deliver email 
        for fake domain names. For sendername, you might choose the system name 
        so that recipients see what node sent the problem report. 
        TO--SEA automatically sends copies of problem reports to all users in 
        the TO field. Use a semicolon to separate additional recipient 
        addresses. Extra spaces are ignored. 
        CC (optional)--SEA automatically sends copies of problem reports to all 
        users in the CC field. Use a semicolon to separate additional recipient 
        addresses. Extra spaces are ignored. 
      For changes to the NotifyCA.txt file to take effect, save the file, and 
      stop and restart the Director (see Sections 3.8 and  3.7). 
      UNIX Configuration Issue 
      If your UNIX environment does not allow for SMTP forwarding using the 
      normal protocol, add the following line to the NotifyCA.txt file: 
      CMD=mailx -s '%s' %t 

      You are free to substitute a different mail-sending command for mailx, if 
      desired. SEA transparently replaces %s with the subject line of the 
      problem report, and %t with all "TO" addresses, when forming the email 
      message. 
      As of this release, using the "mailx" feature may result in multiple 
      duplicate problem reports being sent.Ignore the duplicates.This will be 
      corrected in a future WEBES release. 
        11.3.2 Disabling Email Notifications 
        *** Caution ***


          Events may continue to occur even though you have chosen not to notify 
          anyone. 



      Email notifications are enabled by default, and perform correctly provided 
      that you entered valid SMTP server and email addresses during installation 
      (or when editing NotifyCA.txt after installation). 
      To disable SMTP email notification, enter the following command: 
      desta smtp off

      See Section 3.10.2 "SMTP Notification" for more information. 
        11.3.3 Re-enabling Email Notifications 
      Email notifications are enabled by default, and perform correctly provided 
      that you entered valid SMTP server and email addresses during installation 
      (or when editing NotifyCA.txt after installation). 
      If the email notification is disabled as described in Section 11.3.2 
      "Disabling Email Notifications", enter the following command to re-enable 
      SMTP email notification: 
      desta smtp on

      See Section 3.10.2 "SMTP Notification" for more information. 
        11.3.4 Firewall Telnet Checking May Inhibit SMTP Email
      Certain firewall products, such as those from Symantec or Norton, check 
      for telnet access and disable any such connection attempts. An SMTP 
      connection on standard SMTP socket port 25 made by the DESTA Director to 
      an SMTP email server may be interpreted by such a firewall as a telnet 
      connection attempt, and the email may be blocked. In this case, you may 
      see a message in the Director's log file such as: 
      SMTP< 421 mynode.mysite.com configuration error

      See Section  2.5 "Log Files" for the location of the Director log 
      Workaround 
      As a workaround, disable the telnet checking feature of the firewall. 
        11.3.5 Open VMS Mail Notification
      On OpenVMS systems only, you can use either or both SMTP email (see above) 
      and VMS mail notification described here. The "desta vmsmail on" command 
      prompts for a comma separated list of User names. For example, 
      $ desta vmsmail on
      Enter the distribution list as a comma-separated list of VMS mail 
      addresses. For example, system,node1::m_smith
      Addresses without a nodename assumes the local host.
      Distribution list[System]

      Press "ENTER" to receive the notification mails to the "SYSTEM" account. 
      If you want to receive the notifications tin your account on node <node1>, 
      then specify the nodename and the username in the following format. 
      <node1>::<uname> 
      For example, MAYFLY::USER_X. 
      To receive notifications in both "SYSTEM" and <uname> accounts specify 
      both "SYSTEM" and <node1>::<uname> separating them with commas. 
      To disable VMS mail notification, execute the command: 
      $ desta vmsmail off
      Do you really want to turn off VMS Mail notification [Yes]:

      To change the list of addresses, execute the command "desta vmsmail off" 
      followed by "desta vmsmail on" and re-supply the addresses when prompted. 
      The previously entered addresses will be shown as the default. 
      11.4 Sending Notifications to HP Services 
      In addition to notifying you by email, SEA can automatically send 
      securely-transmitted problem reports to HP Services. There is one 
      supported and two obsolete unsupported service offerings that can perform 
      this function: 
         11.4.1 System Initiated Call Logging (obsolete, unsupported)
         11.4.2 Proactive Remote Service (obsolete, unsupported)
         11.4.3 Instant Support Enterprise Edition (supported)
      SEA does not send "INFO" notifications to your service provider even if 
      you have one of the service provider notification options enabled (see 
      Section 11.2 Service Events vs. Info Events). 
        11.4.1 System Initiated Call Logging 
        *** Note ***


          The HP DSNlink product has retired and is no longer supported by HP. 
          The following information is obsolete. Although the commands still 
          exist in WEBES, notifications are not likely to arrive at any HP 
          Services call center. See Section 3.10.4 "SICL/ACHS/DSNlink 
          Notification" for more information.



      System Initiated Call Logging (SICL) uses HP DSNLink software to securely 
      transmit problem reports to HP Services. You must have DSNLink installed 
      on the same system as SEA before you can enable SICL notifications. 
      The desta sicl [on | off] command (see Chapter 3) enables or disables SICL 
      notifications. 
      *** Note ***


        The SICL command is changed from wsea sicl to desta sicl in an earlier 
        release. Both commands are not supported in WEBES now and may be removed 
        in a future release. 



      When you enable SICL, SEA prompts for an email address so that DSNLink can 
      notify you whenever it logs a call. 
      TCP/IP Network Connection Preferred--Known DSNLink issues may occur if the 
      DSNLink system connects to the network via modem or X.25. For best SICL 
      results, configure DSNLink to use TCP/IP if your network supports it. 
      ACHS--Some people also refer to SICL as Automated Call Handling Services 
      (ACHS), although ACHS more correctly refers to the back-end, receiving 
      systems that handle incoming SICL problem reports at HP. 
        11.4.2 Proactive Remote Service 
        *** Note ***


          The PRS product has now retired. OSEM provides local support similar 
          to the remote support previously provided by PRS CSG/QSAP,see section  
          11.5.1 Open Service Event Manager. The same commands still exist in 
          WEBES to route notifications to either PRS or OSEM, but WEBES only 
          supports routing to OSEM, not PRS anymore. See Section 3.10.3 "OSEM 
          Notification (formerly PRS CSG/QSAP)" for more information. . 



      Proactive Remote Service (PRS) does not require that its own software be 
      installed on the same system as SEA. Instead, PRS gets installed on a 
      designated customer service gateway or CSG. SEA sends problem reports to 
      the customer service gateway for forwarding on to HP. You must have a 
      customer service gateway configured before you can enable PRS 
      notifications. See the PRS documentation for details. 
      QSAP--The customer service gateway was formerly known as the Qualified 
      Service Access Point (QSAP). 
      The desta qsap [on | off] command (see Chapter 3) enables or disables PRS 
      notifications. 
      When you enable PRS, SEA prompts for the customer service gateway address 
      and the port number that it listens on: 
        PRS 4.5 and later use port 2069. 
        PRS versions earlier than 4.5 use port 8941. 
        11.4.3 Instant Support Enterprise Edition 
      HP ISEE automates remote support over the Internet by using electronic 
      notifications similar to those from SICL or PRS. ISEE service providers 
      can use remote diagnostic scripts to analyze supported systems and 
      devices. 
      For ISEE automatic reports, you must install ISEE Client A.03.95 or later 
      on the same system as SEA. See the ISEE documentation for details. 
      The desta isee [on | off] command (see Chapter 3) enables or disables ISEE 
      notifications. 
      Currently, ISEE reports are not available for SEA on HP-UX. 
      11.5 Sending Notifications to Other Monitoring Tools 
      In addition to notifying you by email or directly notifying HP Services, 
      you can configure WEBES to send notifications to other HP-provided 
      software service tools running on the same system or a different system on 
      the network. There are currently three routes you can configure: 
         11.5.1 Open Service Event Manager
         11.5.2 Simple Network Management Protocol (SNMP) Notifications to HP 
        SIM or OVO
         11.5.3 Disaster Tolerant Computing Service (DTCS)
         11.5.4 Microsoft Object Manager (MOM)
        11.5.1 Open Service Event Manager
      WEBES can be enabled to send notifications to Open Service Event Manager 
      (OSEM). OSEM has replaced the Customer Service Gateway (CSG, formerly 
      known as Qualified Service Access Point or QSAP) function of Proactive 
      Remote Services (PRS). The PRS product has now retired in favor of HP ISEE 
      (see section  3.10.1) as the remote support tool for notifying HP customer 
      support. OSEM provides local support similar to the remote support 
      previously provided by PRS CSG/QSAP. You can configure WEBES to send 
      notifications to OSEM in the same manner you would have previously 
      configured WEBES to send notifications to PRS CSG/QSAP. 
      The desta qsap command enables or disables OSEM notifications. The command 
      name is still qsap even though the product has changed. WEBES sends 
      notifications to OSEM using the same protocol it sent to CSG/QSAP. 
      To enable notification to OSEM, issue the command and answer the prompts: 
      desta qsap on
      What is the name of the Open Service Event Manager (OSEM, formerly 
      CSG/QSAP) node [localhost]: mynode.company.com

      What is the port number the OSEM node is listening on [2069]: 

      The name of the OSEM node can be any system running OSEM that is 
      accessible by a "ping", i.e. a fully qualified hostname with dotted 
      domain, or a simple hostname, or an IP address. All supported versions of 
      OSEM use the same default port, 2069. 
      To disable notification to OSEM, issue the command and answer the prompt: 
      desta qsap off
      Do you really want to turn off OSEM (formerly CSG/QSAP) Call Logging 
      [Yes]: 

      See also section  3.10.3 OSEM Notification (formerly PRS CSG/QSAP) 
        11.5.2 Simple Network Management Protocol (SNMP) Notifications to HP SIM 
        or OVO
      HP Systems Insight Manager 4.2 extends existing management capabilities 
      for ProLiant, Integrity, and HP 9000 systems with a HP BladeSystem 
      Integrated Management and support for value added plug-ins, improved rapid 
      deployment, vulnerability and patch management, and virtual machine 
      management and control. 
      HP SIM runs on Port 280 and uses the SNMP service provided by the 
      operating system for monitoring SNMP traps. 
      HP SIM is not required to be installed on the same system as SEA. 
      The desta snmp [on | off] command (see Chapter 3) enables or disables SNMP 
      Notification. 
      The desta snmp on command on WEBES 4.5 Windows Itanium requests the user 
      to provide both SNMP Trap destination and trap type. The supported trap 
      types are 2 and 3. 
      HP SIM Service Notification overview: 
      The HP Services analysis tools, WEBES and OSEM, generate service 
      notifications to HP SIM via a specific SNMP trap type if analysis has 
      determined there are serviceable events. 
      This is supported in Web-Based Enterprise Services (WEBES) v4.4.1 or 
      greater and Open Service Event Manager (OSEM) v1.3 or greater. This 
      capability has been a part of HP SIM since v4.0. 
      To download HP SIM and for more information on HP SIM, go to: 
      http://www.hp.com/go/hpsim 
      HP SIM handling of Service Trap Notifications: 
      Upon receipt of service trap notifications from WEBES, HP SIM handles them 
      in much the same way as any other management event. 
      There are several ways to view these events. One way is to view them under 
      All Events as this will always be done by default. Another way is to view 
      them under Event Lists using the Advanced Search capability. For HP SIM 
      4.x, the user must use Advanced Search and do the following: 
      Search for events where event category name is HP Service Events and type 
      name is any. In HP SIM 5.0, this is done by default by showing HP Service 
      Events under Event Lists, Events by Severity list. 
      The Event Type is shown as `A Service Incident has been reported'. 
      The System Name and Event Time refer to the failing system or subsystem 
      and the time the error was reported. 
      The Severity is shown as MAJOR because the service notification is only 
      sent if analysis has determined that a maintenance action should be 
      performed and also since the service trap contains information in addition 
      to what may be found in the original events such as SNMP traps sent by 
      Insight Management agents. 
      In the case of WEBES, notification is sent based on the operating system 
      event log analysis so there may or may not be other traps sent by 
      management agents. 
      New Service Trap and Service MIB information: 
      HP SIM 5.0 ships with a newer version of the service MIB to support 
      enhanced service traps sent by WEBES v4.5. 
      The new MIB can be compiled into older versions of HP SIM 4.x and will 
      recognize both the old and new versions of service traps. To obtain the 
      latest Service MIB, visit the following link: 
      http://h18023.www1.hp.com/support/svctools/ 
      Select download service MIB under WEBES or OSEM. To register the new 
      service MIB with HP SIM perform the following procedure on the system 
      running HP SIM: 
        +-----------------------------------------------------+

              Open an MS-DOS window or UNIX shell.

              Change to the directory containing the MIBs such as c:\program 
              files\hp\systems insight manager\mibs for Windows or /opt/mx/mibs 
              for Linux.

              Run "mxmib -d cpqservice.mib" to unregister the old service MIB. 

              Delete the old cpqservice.mib and cpqservice.cfg.

              Copy the new cpqservice.mib to the MIBS directory.

              Run "mxmib -a cpqservice.cfg" to install the updated files into HP 
              SIM.





        +-----------------------------------------------------+




          11.5.2.1 Unknown Host Exception in Director Log When Manually 
          Analyzing Files with Notifications
      If you have enabled SNMP service trap notifications using the "desta snmp 
      on" command, then the following commands will cause WARNING messages in 
      the Director log. These messages are expected and ignorable. The Director 
      will attempt to find the IP address of the TLV_Computer_Name in the binary 
      event, to fill in another field of the trap for informational purposes. 
      Since that host name will not exist on the TCP/IP network for the SEA Test 
      Event (and probably not for any of the SEA example binary event logs 
      provided either), the WARNING is logged, but the SNMP trap will still be 
      sent successfully. This is working as designed. 
      The following command: 
      wsea test nosys

      ...causes the following error in the Director log: 
      RECOVERED FROM ERROR on May 3, 2005 7:28:17 AM MDT (2888.161 sec elapsed)
      Error formatting problem report for SNMP
      Current Thread[Thread-79,5,main]
      EXCEPTION java.net.UnknownHostException: *SEATEST*: *SEATEST*
      at java.net.InetAddress.getAllByName0(InetAddress.java:1011)

      The following command: 
      wsea ana input <file> notify [customer|visible|every]

      ...causes the following error in the Director log, where "Computer Name 
      Here" will be the contents of the "Reporting Node" field of the SEA 
      Problem Report: 
      RECOVERED FROM ERROR on May 3, 2005 8:15:54 PM PDT (990.047 sec elapsed)
      Error formatting problem report for SNMP
      Current Thread[Thread-91,5,main]
      EXCEPTION java.net.UnknownHostException: Computer Name Here
      at java.net.InetAddress.getAllByName0(Unknown Source)

        11.5.3 Disaster Tolerant Computing Service (DTCS)
      The DTCS notification is enabled with the following command: 
      desta dtcs on
      hostname is prompted for the DTCS server (default value is localhost).
      Port number is prompted for the DTCS server (default is 6085).

      The desta dtcs on command enables the DTCS notification for the hostname 
      provided (or the default value). An XML report via HTTP is sent to the 
      port number that is provided (or the default value). 
      There should be a file for each heartbeat and each problem report that was 
      sent. The problem report should contain all of the data of the callout. 
      The desta dtcs [on | off] command (see Chapter 3) enables or disables DTCS 
      notification. 
        11.5.4 Microsoft Object Manager (MOM)
      WEBES now supports a new storage interface called Microsoft Object Manager 
      (MOM). MOM is a Microsoft software product to monitor and process events. 
      MOM will specifically catch WEBES Problem Reports sent using MOM 
      interface, and display them in the MOM tool. The MOM interface on WEBES 
      uses the same mechanism as the QSAP/CSG/OSEM interface implemented by the 
      HttpNotification Java classes in DESTA. The output format is XML. MOM is a 
      tool available from Microsoft, but the EVA receiver is available from HP. 
      EVA receiver acts like a plug-in to MOM. If you do not have the EVA 
      receiver installed and running, you will not see anything in the MOM even 
      if the MOM interface is enabled on WEBES. 
      11.6 The Customer Profile File 
      Automatic SEA notifications let you dispatch the appropriate corrective 
      actions at your site. An important part of these notifications includes 
      matching system information to the fault and failure messages from SEA. 
      Your customer profile file is the key to this task. 
         11.6.1 Number of Profile Files
         11.6.2 Location of the Profile File
         11.6.3 Calling the Profile File
         11.6.4 Profile File Content
         11.6.5 How the Profile File Works
        11.6.1 Number of Profile Files 
      A system must have access to at least one profile text file. One suggested 
      setup is to have a profile file on each system. However, in a cluster 
      environment it might be more efficient to create a single profile file and 
      store it in a suitable directory on a common, shared disk that all nodes 
      in the cluster have read access to. 
      Provided that you reference the correct file path (see Section 11.6.3 
      Calling the Profile File), there is no reason you cannot edit, update, and 
      maintain a profile file in a different location than the suggested 
      default. 
        11.6.2 Location of the Profile File 
      Even after installing WEBES, you can manually update the profile file 
      using any text editor. The default name and location for the profile file 
      is as follows: 
        OpenVMS--SVCTOOLS_HOME:[SPECIFIC.DESTA.CONFIG]PROFILE.TXT
        Windows--{WEBES installed 
        directory}\svctools\specific\desta\config\profile.txt
        By default, WEBES is installed to C:\Program Files\Hewlett-Packard.
        HP-UX--/opt/hp/svctools/specific/desta/config/profile.txt
      You can, however, locate and name the profile file as desired, provided 
      that the system always has access to it. 
        11.6.3 Calling the Profile File 
      So that WEBES can detect the profile file, its path is specified in the 
      following file: 
        OpenVMS--SVCTOOLS_HOME:[SPECIFIC.DESTA.CONFIG]DESTA.REG 
        Windows--\hp\svctools\specific\desta\config\desta.reg 
      If you move the profile file from its default location, update the 
      following line in the desta.reg file. You can edit desta.reg with any text 
      editor. 
      CA.ACHSProfile=filename 

      Filename is the path and name of the profile file. 
      In Windows, backslash characters must be doubled for the path be 
      interpreted correctly. For example: 
      CA.ACHSProfile=C:\\Program 
      Files\\hp\\svctools\\specific\\desta\\config\\profile.txt 

        11.6.4 Profile File Content 
      The installation process creates a basic profile file for you, based on 
      your answers to the prompts during WEBES installation. The basic content 
      includes contact, company, and system information that you supplied. 
      However, it often is beneficial to add further detail to the file by 
      editing it with a text editor after installation. 
      Adding storage configuration information to the profile file is very 
      important. For example, when your storage is part of a storage area 
      network (SAN), event detection occurs within the SAN itself, but the event 
      information gets logged to all the hosts attached to the SAN environment. 
      As such, multiple systems may in fact receive event information indicating 
      the same potential failure because of the shared/redundant resource nature 
      of the SAN. 
      Ultimately, this one event may be reported as multiple events. With 
      accompanying configuration information, however, your administrator is 
      able to build a true picture of where the fault is and more accurately 
      direct resources to the physical location of the problem. 
      If your system is well bounded (i.e. all storage is directly attached to 
      SmartArray Controllers on the servers), simpler configuration information 
      usually is enough. 
          11.6.4.1 Sample Profile 1--Simple 
      The following is a simple profile.txt depicting: 
        ProLiant server
        No attached ESA12000/RA8000 Storage Array Subsystem 
        Customer: Acme Stonecutting, Inc.
        System Type: ProLiant Model 5500
        System S/N: V907-BY43-1972 System Name: ARGOSS
        System IP address: 123.4.567.89 Fixed(X) DHCP Served ( )
        Primary Contact: Fred Flintstone
        Secondary Contact: Barney Rubble
        Phone number: (xxx) 555-5555
        Special Instructions: 
        Check with customer prior to dispatching services. Prior notification to 
        security is necessary for service access to site.
        Remote call back to system permissible w/prior notification to customer 
        so that account may be enabled.
        CONFIGURATION INFORMATION:
        Qty 2 - KZPAC array controllers on PCI bus #1 attached to qty 6 
        StorageWorks I shelves w/disks.

          11.6.4.2 Sample Profile 2--MSCS Cluster 
      The following shows configuration information from a profile.txt 
      depicting: 
        2 ProLiant servers 
        Attached to ESA12000/RA8000 Storage Array Subsystem 
        The servers are in an MSCS configuration.
        CONFIGURATION INFORMATION:
        MS Cluster Systems
        SYSTEM: ProLiant Model: 5500
        System S/N: V907-BY43-1972 System Name: SNOBAL
        System IP address: 192.7.100.99 Fixed(X) DHCP Served ( )
        SYSTEM: ProLiant Model: 5500
        System S/N: V903-BW43-1972 System Name: QUEBAL
        System IP address: 192.7.100.98 Fixed(X) DHCP Served ( )
        Compaq FC Switch 16 Serial # 3G944001233
        TCPIP 192.7.100.100
        Compaq FCSwitch 16 Serial # 3G944001235
        TCPIP 192.7.100.101
        ESA12000 Array Controller 
        Subsystem Name: Joiner
        joiner-Top >> HSG80 ZG91416110 Software S056P-0, Hardware E06
        joiner-Bottom>> HSG80 ZG83502157 Software S056P-0, Hardware E03
        ESA12000 Array Controller 
        Subsystem Name: Partnr
        partnr-Top >> HSG80 ZG91516230 Software S056P-0, Hardware E06
        partnr-Bottom>> HSG80 ZG91516231 Software S056P-0, Hardware E03

          11.6.4.3 Sample Profile 3--MSCS Cluster with DRM 
      The following shows configuration information from a profile.txt 
      depicting: 
        Data Replicator Storage Solution 
        Two (initiator and target) sites 
        2 ProLiant servers on each site 
        ESA12000/RA8000 Storage Array Subsystems interconnected by FC Switches 
        between the sites. 
        FC SAN is linked between Initiator/Target sites by Compaq FC Gateway ATM 
        interfaces and a leased ATM circuit. 
        The servers are in an MSCS configuration.
        CONFIGURATION INFORMATION:
        INITIATOR SITE: DENVER
        Denver, CO., US
        1244 E. McGuire Way, Floor 2, Room CR1
        MS Cluster Systems
        SYSTEM: ProLiant Model: 8500
        System S/N: Q762-BHET-AE43-1305 System Name: FSTBAL
        System IP address: 192.7.100.99 Fixed(X) DHCP Served ( )
        SYSTEM: ProLiant Model: 8500
        System S/N: Q761-BHET-AE44-0900 System Name: CRVBAL
        System IP address: 192.7.100.98 Fixed(X) DHCP Served ( )
        ESA12000 Storage ARRAY CONTROLLER 
        Subsystem Name: Denver
        denver-Top >> HSG80 ZG91416110 Software S056P-0, Hardware E06
        denver-Bottom>> HSG80 ZG83502157 Software S056P-0, Hardware E03
        Compaq FC Switch 16 Serial # 3G944001233
        TCPIP 192.7.100.100 Fixed(X) DHCP Served ( )
        Compaq FCSwitch 16 Serial # 3G944001235
        TCPIP 192.7.100.101 Fixed(X) DHCP Served ( )
        FC GATEWAY Serial # 52623434
        TCPIP 192.7.100.102 Fixed(X) DHCP Served ( )
        Dial-in Phone Number to FC Gateway Asynchronous Switch
        Ph. 303-555-xxxx
        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
        TARGET SITE: CHICAGO 
        Chicago, Ill, CO., US
        1245 Times Blvd.
        Floor 7, CR200
        MS Cluster Systems
        SYSTEM: ProLiant Model: 5500
        System S/N: xxxxxxxxxxxx System Name: SNKBAL
        System IP address: 192.7.100.79 Fixed(X) DHCP Served ( )
        SYSTEM: ProLiant Model: 5500
        System S/N: xxxxxxxxxxxx System Name: SLDBAL
        System IP address: 192.7.100.78 Fixed(X) DHCP Served ( )
        ESA12000 Array Controller 
        Subsystem Name: Chicago
        chicago-Top >> HSG80 ZG91416110 Software S056P-0, Hardware E06
        chicago-Bottom>> HSG80 ZG83502157 Software S056P-0, Hardware E03
        Compaq Switch 16 Serial # 3G012000435
        TCPIP 192.7.100.200 Fixed (X) ) DHCP Served ( )
        Compaq Switch 16 Serial # 3G9012000422
        TCPIP 192.7.100.201 Fixed (X) ) DHCP Served ( )
        FC GATEWAY Serial # 526538653
        TCPIP 192.7.100.202 FIXED ) DHCP Served ( )
        Dial-in Phone Number to FC Gateway Asynchronous Switch
        Ph. 312-222-xxxx 

        11.6.5 How the Profile File Works 
      When events are identified by automatic analysis, SEA assembles a problem 
      report and attaches your profile text file to the report. The profile file 
      helps the message accurately identify the following: 
        The department, location, phone number, and contact person 
        The system from which the message originated, including address, 
        physical location, contact person for that system, and so on 
      In instances where the system includes attached Enterprise Array 
      Controllers or SAN storage, the profile file becomes very important in 
      indicating storage configuration, exact FRUs, and physical location of any 
      failing component. 


      