WEBES 61 Install

Web Based Enterprise Services 6.
1
Installation, Configuration, and Usage Guide
HP Part Number: 5900-1 104 Published: August, 2010
Copyright 1999 - 2010 Hewlett-Packard Development Company, L.P. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.21 and 12.212, Commercial 1 Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgments Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. UNIX is a registered trademark of The Open Group. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Java is a U.S. trademark of Sun Microsystems, Inc.
Table of Contents
About This Document.....................................................................................9
1 2 3 4 Intended Audience...............................................................................................................................9 Publishing History................................................................................................................................9 Typographic Conventions......................................................................................................................9 Related Documents...............................................................................................................................9
1 General Information..................................................................................11
1.1 What is WEBES?.............................................................................................................................11 1.2 What is the System Event Analyzer?...................................................................................................11 1.3 What is the Director?.......................................................................................................................11 1.3.1 SEA and the Director................................................................................................................11 1.4 ELMC.............................................................................................................................................12 1.4.1 ELMC Version in WEBES...........................................................................................................12 1.5 WEBES Hardware Requirements........................................................................................................12 1.6 WEBES Operating System Requirements.............................................................................................12 1.7 What is New in this Release?............................................................................................................13 1.7.1 Kauai Support..........................................................................................................................13 1.7.2 ELMC No Longer Seen as a Separate Package............................................................................13 1.7.3 PostgreSQL 8.4.1 Included in WEBES 6.1....................................................................................13 1.8 Installation Kit.................................................................................................................................13 1.9 Upgrades.......................................................................................................................................13
2 Installing on Windows..............................................................................15
2.1 Pre-Installation.................................................................................................................................15 2.1.1 WEBES System Requirements......................................................................................................15 2.1.2 SEA System Requirements..........................................................................................................16 2.1.3 Permissions..............................................................................................................................17 2.1.4 Archiving and Cleaning the Windows Event Log..........................................................................17 2.1.5 Installing on Terminal Servers.....................................................................................................17 2.2 Installing WEBES.............................................................................................................................18 2.3 Upgrading WEBES..........................................................................................................................24 2.4 Downgrading WEBES......................................................................................................................25 2.5 Uninstalling WEBES.........................................................................................................................25 2.5.1 Uninstalling on Terminal Servers................................................................................................25 2.6 Removing SQL Server......................................................................................................................25 2.6.1 Remove WEBESDB SQL Server Only (Recommended)...................................................................25 2.6.2 Remove Entire SQL Server (Not Recommended)...........................................................................25
3 WEBES User Interface...............................................................................27

3.1 Accessing the System Event Analyzer..................................................................................................27 3.2 Using The WEBES User Interface.......................................................................................................27 3.2.1 Toolbar..................................................................................................................................28 3.2.2 Navigation.............................................................................................................................29 3.2.2.1 Navigation Tree Hierarchy................................................................................................29 3.2.2.2 Features of the Navigation Tree.........................................................................................30 3.2.2.3 Navigation Tree Icons......................................................................................................31 3.2.2.4 Navigation Tree active links..............................................................................................33 3.2.2.4.1 SEA link.................................................................................................................33 3.2.2.4.2 Group link.............................................................................................................33 3.2.2.4.3 Entity link...............................................................................................................34 3.2.2.4.4 System Log.............................................................................................................34 3.2.2.4.5 Real Time Monitoring..............................................................................................34
Table of Contents 3
3.2.2.4.6 Full View................................................................................................................35 3.2.2.4.7 Other Logs.............................................................................................................36 3.2.2.4.8 Other Logs file........................................................................................................36 3.2.2.4.9 WBEM..................................................................................................................37 3.2.3 Applet Messages....................................................................................................................38 3.3 Customizing the Navigation Tree.......................................................................................................38 3.3.1 Groups...................................................................................................................................38 3.3.1.1 Adding Groups................................................................................................................38 3.3.1.2 Removing Groups.............................................................................................................39 3.3.2 Nodes...................................................................................................................................40 3.3.2.1 Adding Nodes................................................................................................................40 3.3.2.2 Removing Nodes.............................................................................................................41 3.3.2.3 Activating Nodes............................................................................................................42 3.3.3 Categories.............................................................................................................................43 3.3.3.1 Adding Categories..........................................................................................................43 3.3.3.2 Removing Categories.......................................................................................................44 3.3.4 Event Sources.........................................................................................................................44 3.3.4.1 System Log.....................................................................................................................45 3.3.4.2 WBEM..........................................................................................................................45 3.3.4.3 Other Logs.....................................................................................................................45 3.4 Processing Events............................................................................................................................47 3.4.1 Additional Toolbar Functions.....................................................................................................50 3.4.2 Processing Status....................................................................................................................50 3.4.2.1 Navigation Tree..............................................................................................................50 3.4.2.2 Progress Window...........................................................................................................51 3.4.3 Working With Results..............................................................................................................52 3.4.3.1 Problem Reports..............................................................................................................52 3.4.3.2 Summary.......................................................................................................................53 3.4.3.3 Sub Type Tallied Summaries and Event Listings....................................................................53 3.4.3.4 Events............................................................................................................................54 3.4.3.5 Sorting Results................................................................................................................55 3.4.3.6 Displaying Details...........................................................................................................55 3.5 Managed Protocols.........................................................................................................................56 3.5.1 Add New Protocol...................................................................................................................56 3.6 Managed Entities............................................................................................................................58 3.6.1 Adding a Managed Entity........................................................................................................60 3.6.2 Exporting Managed Entity Information.......................................................................................61 3.7 Getting Help..................................................................................................................................62 3.7.1 Usage Tips..............................................................................................................................62 3.7.2 WEBES Documentation............................................................................................................62 3.8 WEBES User Interface - Advanced Functions.......................................................................................62
4 Automatic Notifications.............................................................................63
4.1 When Are Notifications Sent?...........................................................................................................63 4.2 Web Interface Notification Settings Page...........................................................................................63 4.3 Web Interface Notification Status and Dispatch Page...........................................................................64 4.4 Service Events vs. Info Events............................................................................................................65 4.4.1 Service Events.........................................................................................................................65 4.5 Informational Events........................................................................................................................65 4.6 Sending Notifications to Email Addresses...........................................................................................65 4.6.1 Settings..................................................................................................................................65 4.6.1.1 Web Interface Email Settings Page.....................................................................................66
Table of Contents
List of Figures
2-1 2-2 2-3 2-4 2-5 2-6 2-7 2-8 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 3-9 3-10 3-1 1 3-12 3-13 3-14 3-15 3-16 3-17 3-18 3-19 3-20 3-21 3-22 3-23 3-24 3-25 3-26 3-27 3-28 3-29 3-30 3-31 3-32 3-33 3-34 3-35 3-36 4-1 4-2 4-3 4-4 Configuration Wizard - SNMP Question.............................................................................................18 Configuration Wizard - User Information............................................................................................19 Configuration Wizard - Profile and Notification Details........................................................................20 Configuration Wizard - Configure WEBES..........................................................................................21 WEBES Service Obligation Validation...............................................................................................22 Clean Binary Error Log....................................................................................................................23 WEBES Installation Execution............................................................................................................23 WEBES Install Complete...................................................................................................................24 Logon Window...............................................................................................................................27 Main Screen..................................................................................................................................27 Toolbar..........................................................................................................................................28 Navigation Tree - Hierarchy..............................................................................................................30 Navigation Tree - Collapsed.............................................................................................................30 Navigation Tree - Expanded.............................................................................................................31 Add Group....................................................................................................................................39 Remove Group................................................................................................................................40 Add Node.....................................................................................................................................41 Remove Node..............................................................................................................................42 Activating Node...........................................................................................................................42 Activating Node Message..............................................................................................................42 Unable to Activate Node Message..................................................................................................43 Add Category..............................................................................................................................43 Remove Category.........................................................................................................................44 Add Log Files Tab.........................................................................................................................46 Remove Log File Tab......................................................................................................................47 Analysis Failed Message................................................................................................................50 Status Icons..................................................................................................................................51 Progress Window.........................................................................................................................51 Additional Entries Navigation.........................................................................................................52 Problem Report Tab.......................................................................................................................52 Summary Tab...............................................................................................................................53 Summary of Sub-Types...................................................................................................................54 Sub-Type Listing............................................................................................................................54 Events Tab...................................................................................................................................55 Navigation ButtonsProblem Reports..............................................................................................56 Navigation ButtonsEvents............................................................................................................56 Protocol Details: Binary Event Log...................................................................................................57 Protocol Details: CommandView EVA..............................................................................................58 Protocol Details: SNMP..................................................................................................................58 Protocol Details: WMI for Windows................................................................................................58 Managed Entities..........................................................................................................................59 Managed Entity Detail...................................................................................................................60 Managed Entities..........................................................................................................................61 Export Managed Entities popup......................................................................................................62 Web Interface Notification Settings Page...........................................................................................63 Web Notifications...........................................................................................................................64 WEBES Notification Dispatch...........................................................................................................64 E-mail Settings................................................................................................................................66
List of Tables
1-1 2-1 2-2 2-3 2-4 2-5 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 3-9 ELMC Versions Packaged in WEBES..................................................................................................12 Windows Browser Requirements........................................................................................................16 WEBES Information Requested During Installation................................................................................19 WEBES Information Requested During Installation................................................................................20 WEBES Information Requested During Installation................................................................................21 WEBES Information Requested During Installation................................................................................22 Web Interface Components..............................................................................................................28 Toolbar Default Buttons.................................................................................................................28 Toolbar Dynamic Buttons...............................................................................................................29 Navigation Tree - Hierarchy..............................................................................................................30 Navigation Tree - Features................................................................................................................31 Navigation Tree Icons......................................................................................................................31 Applet Messages............................................................................................................................38 Additional Toolbar Functions............................................................................................................50 Event Type Color Codes...................................................................................................................53
About This Document

1 Intended Audience
This document is for WEBES standalone users who install the Web-Based Enterprise Services (WEBES) product without Insight Remote Support Advanced or Insight Remote Support Standard.
2 Publishing History
Revision 29-June-2007 July 2007 - Jan 2008 May 2008 January 2009 April 2009 September 2009 March 2010 August 2010 Description Created initial copy for WEBES 5.1 using WEBES 5.0 baseline copy Updated for WEBES 5.1 Updated for WEBES 5.2 Updated for WEBES 5.4 Updated for WEBES 5.5 Updated for WEBES 5.6 Updated for WEBES 6.0 Updated for WEBES 6.1
3 Typographic Conventions
find(1) Book Title Linked Title http://www.hp.com Command user input computer output Enter
HP-UX manpage. In this example, find is the manpage name and 1 is the manpage section. Title of a book or other document. Title that is a hyperlink to a book or other document. A Web site address that is a hyperlink to the site. Command name or qualified command phrase. Commands and other text that you type. Text displayed by the computer. The name of a keyboard key. Note that Return and Enter both refer to the same key. A sequence such as Ctrl+A indicates that you must hold down the key labeled Ctrl while pressing the A key. Defined use of an important word or phrase. The name of an environment variable, for example PATH or errno. A value that you may replace in a command or function, or information in a display that represents several possible values. An element used in a markup language. An attribute used in a markup language.
term variable value <element> attrib=
4 Related Documents
WEBES Reference Guide

This document provides further information about using and troubleshooting WEBES.
1 Intended Audience
10
1 General Information
This chapter provides an overview of the Web Based Enterprise Services (WEBES) suite of tools for Windows. WEBES 6.1 is supported for Windows only. Detailed instructions for installing WEBES on other supported operating systems are provided in the previous versions of WEBES installation guides.
1.1 What is WEBES?

WEBES is a suite of tools that run on Hewlett-Packard customer systems of various Windows operating systems and hardware platforms. These tools are built upon a common set of services included in WEBES, called the WEBES Common Components. WEBES acts upon platform-specific data using common services to present results to users in platform-independent ways. The WEBES Common Components (WCC) are a set of core service tool functionality providing a common: Information repository Data interface to the repository Distributed messaging service for interprocess communication between tool services on heterogeneous platforms Set of notification mechanisms
The WEBES Service Event Analyzer tool uses these common components to minimize the tool-specific functionality and the differences between the tools.
1.2 What is the System Event Analyzer?

The System Event Analyzer (SEA) is a fault analysis utility designed to provide binary event analysis for single error/fault events, as well as multiple event correlation 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 sources and processing events as they occur. The events are checked against the analysis rules. If one or more of the events meets the conditions specified in the rules, the analysis engine uses the relevant event data to create 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 includes a web browser interface (see Chapter 3 WEBES 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.3 What is the Director?

The Director is a set of WEBES processes that run continuously. The Director manages a system, either a standalone system or a node in a cluster, on behalf of WEBES and executes the functionality of individual WEBES tools.
1.3.1 SEA and the Director

SEA enables the Director 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 functionality. The Director is idle except during the following circumstances: Events are received for processing Messages arrive from managed entities on the same system or remotely connected systems 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 simultaneously active and all connected to a single Director. See Chapter 3 WEBES User Interface for user interface details.
1.1 What is WEBES?
1 1
The Director automatically starts along with the system and normally does not require additional attention. See WEBES Reference Guide if you do require information on interacting with the Director.
1.4 ELMC
ELMC is a daemon process that runs continuously. ELMC contains functions that allow WEBES to interact with the operating system, other WEBES agent processes, and the Director. The Director will not perform correctly without the WCCProxy service. ELMC automatically starts along with the system and normally does not require additional attention. See WEBES Reference Guide if you do require information on interacting with ELMC. NOTE: Formerly known as WEBES Common Components Proxy (WCCProxy), ELMC is a kit that now contains the WCCProxy service. Where you see ELMC in this document, the term is referring to the collective components of the ELMC kit, and where you see WCCProxy in this document, the term is referring to the WCCProxy service itself.
1.4.1 ELMC Version in WEBES

The following table shows the ELMC versions that have been packaged in WEBES up to this version. Table 1-1 ELMC Versions Packaged in WEBES
Product WEBES 6.1 WEBES 6.0 WEBES 5.6 WEBES 5.5 WEBES 5.4 ELMC Version Included WCCProxy 6.1 WCCProxy 6.0 WCCProxy 2.6 WCCProxy 2.5 WCCProxy 2.4
1.5 WEBES Hardware Requirements

WEBES can be installed on the following hardware platforms: 32-bit Intel based systems manufactured by HP, such as the ProLiant or the HP OpenView Storage Management Appliance NOTE: 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 is not officially supported. x64-86 based Intel and AMD systems NOTE: x64-86 based systems should not be confused with IA-64 Itanium based systems, for example, HP Integrity systems. WEBES 6.1 should not be installed on these systems. However, WEBES 6.1 does not exclude IA-64 Itanium systems from being monitored as a managed entity.
1.6 WEBES Operating System Requirements

NOTE: If you attempt to install the Windows WEBES Pentium/x86 kit on an unsupported Integrity (Itanium-based) system the following error message will appear: "This WEBES kit supports only 32 bit platforms. Please contact HP support for the WEBES kit for your processor type." If you attempt to install the Windows WEBES Itanium kit on a 32-bit or 64-bit system on an unsupported platform, the following error message will appear: "This installation package is not supported by this processor type. Contact your product vendor." To avoid receiving these errors, please ensure that you obtain the correct kit before installing WEBES.
12 General Information
WEBES 6.1 supports the following operating systems: Microsoft Windows Server 2003 with Service Pack 1 or R2 32-bit: Web Edition, Standard Edition and Enterprise Edition Standard x64 Edition and Enterprise x64 Editions
Microsoft Windows Server 2008 with Service Pack 1, Service Pack 2, or R2
WEBES 6.1 is NOT supported on the following version of Windows: Windows XP Professional 64-bit Itanium Edition. Although WEBES is not yet supported on this operating system, the Itanium WEBES kit may install and operate correctly, but the Pentium WEBES kit can not be installed.
See WEBES Hardware Requirements for the hardware that WEBES supports. 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. See the WEBES Reference Guide for the list of products that SEA supports.
1.7 What is New in this Release?

This section provides a summary of the new functionality that has been added to WEBES since the 5.5 edition of this guide was published.
1.7.1 Kauai Support

Kauai has the concept of multiple blades making up a system, known as co-joined blades. For entitlement of Kauai, there will be a clip on pipe attached to the front of the blade system and this is where the serial number will be located. All blades will use this serial number. There will only be one pipe no matter how many blades there are.
1.7.2 ELMC No Longer Seen as a Separate Package

ELMC will now be installed as part of the WEBES package and will no longer be seen as a separate package.
1.7.3 PostgreSQL 8.4.1 Included in WEBES 6.1

PostgreSQL is an object-relational database management system. PostgreSQL 8.4.1 is embedded within the WEBES 6.1 installation kit. In WEBES 6.1 Postgres runs as a subprocess within WEBES and does not need any role or user account creation in order to install the Postgres service. NOTE: WEBES 6.1 does not require the use of Microsoft SQL Server 2005 installed by WEBES 5.5 or earlier versions and Postgres 8.3.7 installed with WEBES 5.6. These programs may have been installed on your system during installation of a previous versions of WEBES, or by another application or user. See Removing SQL Server for details.
1.8 Installation Kit

The WEBES Installation Kit is available at the HP Service Tools Website: http://www.hp.com/services/webes
1.9 Upgrades
Upgrades can include anything from a major WEBES release to a minor kit with only rule updates or small functional improvements. When upgrading you do not need to uninstall WEBES if your existing WEBES version is within two releases. For example, when upgrading to WEBES 6.1 you do not need to uninstall your current version if it is WEBES 6.0 or 5.6. The WEBES 6.1 kit does the following: Recognizes an existing installation Saves configuration and state data
1.7 What is New in this Release? 13
Uninstalls the existing kit Installs the WEBES 6.1 version Restores the configuration and state data
WEBES upgrades are also available in the form of patches which can be downloaded and installed on an existing WEBES installation. Upgrades/Patches for WEBES are available at the HP Service Tools Website: http://www.hp.com/services/ webes NOTE: Before you attempt to upgrade ensure that the WEBES-related DESTA_service is running and functioning in order to successfully migrate Managed Entity data.
14
General Information
2 Installing on Windows
2.1 Pre-Installation
2.1.1 WEBES System Requirements
The system must meet the following basic requirements before you install WEBES: Processor architecture HP 32-bit Intel systems, HP x64 Intel EM64T or AMD64 systems.
Non-HP Systems: WEBES is a proprietary service tool and is not a fully qualified off-the-shelf product such as Norton SystemWorks. As such, only platforms manufactured by HP, such as the ProLiant, are officially supported.
Engineering normally expects that WEBES will operate correctly on any industry standard system based on the Intel x86, EM64T, or an AMD architecture. However, because HP does not qualify WEBES on third-party products, functionality on such systems is provided on an as-is basis only. Operating system Refer to WEBES Operating System Requirements Service Packs (SPs) HP supports the two most recent SPs for Windows Server 2003 or 2008. Disk space A total of 353MB must be available at install time, as follows: 64MB in a local directory to store the WEBES kit itself 64MB in the %TEMP% directory (typically %SystemDrive%\Documents and Settings\{username}\Local Settings\Temp, where %SystemDrive% is C: by default). Files saved to %TEMP% are removed after installation completes. 100MB on the drive where you will install WEBES (%SystemDrive%\Program Files\HP\svctools by default)
A total of 289MB are used after installation completes, assuming all components are installed. Local kit copy required Copy the WEBES kit to a local drive. The installation results in an error when mapping a drive letter to another system where the kit resides, for example: Internal Error 2755. 3, F:\path to\WEBESV60BL322KIT2_Jan-28-2010_Windows.MSI Virtual memory 400MB of virtual memory is recommended. During standard operation, SEA uses far less memory. For example, when the Director is idle, usage stays generally around 13MB for systems with all the WEBES tools installed. The Director only approaches the maximum value when a high volume of events arrive or an extremely large log file is processed. Even then, the memory usage may remain significantly below the maximum value. The virtual memory requirement is intended to set a threshold for the absolute maximum amount of memory that will ever be needed. If the threshold is exceeded, the Director terminates with out-of-memory error. Virtual memory for a process is stored in RAM and the page file on your disk. The space allocated must be sufficient to run WEBES and all other applications that you want to run simultaneously. If the virtual memory requirement given here is too large or too small for your environment, you are free to make adjustments. You may want to experiment with various settings to find the optimal value. Refer to the WEBES Reference Guide for more information on adjusting the memory settings. Microsoft Windows Installer v3.1 must be installed. For details and download options: http://support.microsoft.com/kb/893803 You can check the Windows Installer version by entering msiexec at the command prompt. (Ignore the message about incorrect command line parameters.) TCP/IP services must be installed and running.
2.1 Pre-Installation
15
2.1.2 SEA System Requirements

In addition to the common WEBES prerequisites, your system must meet the following requirements to accomodate the SEA component: Minimum 31MB free disk space (in addition to the 353MB required for WEBES) You must enter the model and serial number of the server during an Insight Remote Support Advanced installation. This is for entitlement purposes, even though successful entitlement of the server is not necessary to enable the separately entitled storage support. Web browser Table 2-1 Windows Browser Requirements describes the browser prerequisites for SEA according to the following categories: Table 2-1 Windows Browser Requirements
Category Supported (fully tested) Browser Internet Explorer 7.0 and 8.0 (32-bit version only) Firefox 3.x As-Is (not officially tested but may work reasonably well) Unsupported (known not to work) Internet Explorer 5.5 Internet Explorer (any 64-bit edition) Internet Explorer earlier than 5.5 Netscape earlier than 7.0 Firefox earlier than 1.0
Web browsers can use different Java runtime environments, but the SEA User Interface requires certain versions of Java for each web browser. You can obtain the required version from: http://java.sun.com/ getjava Internet Explorer Either the Microsoft Java VM version 1.1.4, or a Sun JRE version 1.6.17 and older. No Java is included in Internet Explorer on Windows Server 2003 and 2008, and Microsoft no longer supplies a Java VM. You must download and install a Sun JRE instead. Firefox Sun JRE version 1.3.1 or higher. Firefox does not include any Java VM. You must download and install a Sun JRE.
A version may already be installed for your web browser. You can check the version by selecting Tools Web Development Java Console. The Java version is given on the first line of the Java Console window. NOTE: Install any desired web browsers before installing the Sun JRE. The JRE installation then finds and updates installed web browsers so that they use the Sun JRE. Windows Event Logs ensure that the binary event log is large enough to hold all events long enough for WEBES to process them in situations where large streams of events occur over a short period of time. To do this, set the size of your Application Event Log to at least 4MB, in the Windows Event Viewer properties of this log (Event Viewer is in Control Panel under Administrative Tools). After WEBES installation, SEA begins analyzing all events currently stored in one of the Windows Event Logs. On x86 (Pentium) and x64 systems, SEA analyzes only the Application Event Log. This initial
16
Installing on Windows
analysis can result in high CPU usage over an extended period. To control this operation, you have two options: Archive and clean the Windows Event Log as described in Archiving and Cleaning the Windows Event Log before installing. This reduces the size of the log. Choose to delay the initial scan when prompted during installation. As a result SEA automatic analysis does not run until after (and starting with) the initial scan.
Make sure that HTTP 1.1 settings are enabled on a supported Web browser. Choose Tools Internet Options Advanced from the pull-down menus. Check both of the following under HTTP 1.1 Settings: Use HTTP 1.1 Use HTTP 1.1 through proxy connection
2.1.3 Permissions
In order to install, remove, or update WEBES your user ID must be one of the following: A member of the Administrators group on the machine A member of a group that is a member of the Administrators group on the machine. For example, if your user ID is a Domain Admin, and you have added Domain Admins to the Administrators group on the local machine, then you have the necessary permissions.
To add Domain Admins to the local Administrator group, use the procedure for your operating system, for example. Windows Server 2003: From a login account with administrator privileges, locate the user management function under My Computer Manage Computer Management (Local) System Tools Local Users and Groups Groups. Double click the Administrators Group, and press the Add button. Highlight Domain Admins and press Add.
2.1.4 Archiving and Cleaning the Windows Event Log

NOTE: Required only when installing the SEA component. If WEBES is installed and running when you clean the log, stop the Director process before proceeding (see the WEBES Reference Guide for information on stopping the Director). Also, do not stop and restart any Windows system processes. To archive and clean the Windows Event Log, use the procedure for your operating system, for example: 1. 2. 3. 4. Open the event viewer. Windows Server 2003 Start Programs Administrative Tools Event Viewer For events analyzed by SEA: Right-click on the Application Log link in the left pane of the event viewer window. Clear all events. Note that you are given the option to save the existing events to another file before clearing. (Saved logs can be analyzed at a later time.) Close the event viewer.
If WEBES was installed when you cleaned the log and you stopped the Director, you can now restart it using the procedure described in the WEBES Reference Guide.
2.1.5 Installing on Terminal Servers

Terminal Server WEBES installation guidelines apply to these operating systems: Windows Server 2003 when Remote Desktop connections are enabled Windows Server 2008 when Remote Desktop connections are enabled
From Console Terminal Server system installations should be performed from the Terminal Server console by an administrator (either the Administrator account or any account in the Administrators group). For the best results, make sure that no clients are logged on to the server during WEBES installation. You can send clients a message about the time and duration of the installation and then disable all connections before starting.
2.1 Pre-Installation 17
Otherwise, the process for installing is the same as any other Windows WEBES installation. From Client Install from a Terminal Services client as follows: 1. 2. 3. 4. Log on to the Terminal server as an administrator and close all applications. Copy the WEBES kit to a local drive on the Terminal server. Install the program on a local NTFS formatted drive as with any other Windows WEBES installation. On the Terminal server, open and close the system PATH environment variable. Opening and closing sets the PATH so that commands such as desta or wsea can work without specifying the full \svctools\common\bin path to the command. Open Start Settings Control Panel System. Click the Advanced tab. In Environment Variables, open the PATH entry (under System Variables) for editing. Do not make any changes; just click OK several times to get out of the System utility. The PATH is now set for any command prompt windows opened after performing this workaround.
2.2 Installing WEBES

The procedure in this section applies when WEBES is already uninstalled or was never previously installed. If you are upgrading to this version of WEBES from a version within past two releases, see section 2.3 Upgrading WEBES. Upgrading lets you preserve your configuration and state data. NOTE: If you have installed any pre-release build of any version of WEBES, and you wish to replace it with the official final kit build of the same version, you must uninstall the existing WEBES installation before installing the final kit. Do not attempt to install the later kit without first uninstalling the earlier kit. Upgrades from one WEBES version to another version within two version numbers are supported, but you cannot upgrade from one build to another build of the same WEBES version. Do not save configuration data if you are going back to an earlier WEBES version, for example 5.2 to 5.1. The stored configuration data may not be compatible with an earlier version. After all Pre-Installation requirements are met, follow these steps to install WEBES: 1. 2. Log on using an account with administrator privileges. Locate and run the WEBES kit executable file, which ends in the .EXE extension. NOTE: The Windows WEBES Pentium kit has the identifier "x86_x64" indicating that this can be installed on x86 and x64 Pentium systems, but not an Itanium edition of Windows. See WEBES Operating System Requirements for the list of Windows editions supported by WEBES. 3. Click Yes to create a dependency for WCCProxy service on the SNMP Trap service. If you do not choose Yes, then WEBES will not process traps, and you will not be able to monitor SNMP devices. Figure 2-1 Configuration Wizard - SNMP Question
4. 5.
Read the license agreement, click the appropriate radio button if you accept it, and then click Next. Follow the on screen instructions. a. Upgrading If a WEBES version within two previous releases is present, the installer alerts you about the other version and prompts you to upgrade. If this is a fresh WEBES installation, you will not see this message. See Upgrading WEBES for details. b. Installation Directory Path Selection You can change the default directory path for your installation by clicking the Change button and browsing to an alternative installation directory. However, if you do this take note of your installation directory for future reference. Enter WEBES user information.
6.
18
Figure 2-2 Configuration Wizard - User Information
Table 2-2 WEBES Information Requested During Installation

Question User Information User Name Chris Green The primary user of WEBES on this system, or the person that HP support should contact regarding issues reported by WEBES. The company employing the primary WEBES user. The telephone voice contact number for the primary WEBES user. The e-mail address of the primary WEBES user. The server that handles SMTP e-mail at your site. The serial number of the system upon which WEBES is being installed. Example Notes
Company Name Phone Number E-mail SMTP Mail Server System Serial Number
XYZ Company 123-456-7890 chris.green@xyzcompany.com mailsys.xyzcompany.com A01234567890
7.
Enter profile and notification details
19
Figure 2-3 Configuration Wizard - Profile and Notification Details

Question Example Notes
Profile and Notification Information The following information will be sent in WEBES problem report notifications. Customer XYZ Company The company using WEBES as a customer of HP. By default, the Company name entered is entered in the User Information window. The address of the primary WEBES user, or of the company site. The primary contact person at the customer company's site for the system running WEBES. By default, the User Name is entered in the User Information window. The person to contact at the customer company's site, if the Primary Contact person is unavailable. The telephone voice contact number for the primary contact. By default, the Phone Number is entered in the User Information window. Add details that will be useful to your service provider.
Address, City, ... Primary Contact
123, Main Street, Metropolis, VA 22222 Chris Green
Secondary Contact Phone Number
Pat Brown 123-456-7890
Special Instructions
"Check with customer prior to dispatching services. Prior notification to security is necessary for service access to site."
8.
Enter configuration details
20
Figure 2-4 Configuration Wizard - Configure WEBES

Question Configuration Information: The following information will be sent in WEBES problem report notifications. System Type EVA5000 The product description, product number, or model number of the system hardware unit on which WEBES will be installed. The serial number of the system hardware unit. The TCP/IP hostname and fully qualified domain name of the system on which WEBES will be installed. If the system has no hostname, the dotted decimal IP address may be entered. Select Fixed for static IP addresses, or DHCP Served if the IP address of the system is assigned when the system connects to a DHCP server, usually on startup. Example Notes
System Serial Number System name
A01234567890 server1.xyzcompany.com
System IP Address
Fixed or DHCP Server
9.
Validate the service obligation number of the system/subsystem
21
Figure 2-5 WEBES Service Obligation Validation

Question Service Obligation Validation: The following information will be sent in WEBES problem report notifications. System/Subsystem Serial Number Service Obligation Number A01234567890 The serial number of the system hardware unit. By default, the System Serial Number is entered in the Configuration window. Normally, the same as the serial number. Contact your HP customer support representative to obtain your service obligation number as defined by your service contract. Example Notes
A01234567890
10. The following information window enables you to choose to have a clean binary log for this installation, for more details see Archiving and Cleaning the Windows Event Log.
22
Figure 2-6 Clean Binary Error Log
1 Click Install to begin the installation. 1. Figure 2-7 WEBES Installation Execution
12. You will know that the WEBES installation is completed when you see the following window:
23
Figure 2-8 WEBES Install Complete
When you click Finish, the window may not disappear for up to a minute (approx). WEBES is finishing installation tasks during this time and will close the window when the tasks are completed. Clicking Finish multiple times will have no further effect.
2.3 Upgrading WEBES

NOTE: Before upgrading WEBES, reinitialize the system error log as described in Archiving and Cleaning the Windows Event Log. This section is applicable when you are upgrading to WEBES 6.1 from an existing version of WEBES that is within 2 releases (versions) of this version of WEBES. For example, you can upgrade to WEBES 6.1 when either WEBES 6.0 or WEBES 5.6 is installed, but not if 5.5 or earlier is installed. If an upgrade is attempted on a version of WEBES that is too old, you are told to uninstall the existing version, and the upgrade does not proceed. If WEBES is already uninstalled or was never installed at all, see Installing WEBES. WARNING! Ensure that the DESTA_service is running and functional, before attempting to upgrade, in order to be able to successfully migrate Managed Entity data. Upgrading lets you preserve your configuration and state data. Be aware that upgrading uninstalls the older version of WEBES and installs the newer versionthe upgrade does not simply patch or replace certain files, as was the case with WEBES Service Packs. Whenever a version of WEBES is already installed that is capable of being upgraded, the WEBES kit informs you that the older version was detected and prompts you about upgrading. If you answer Yes, the kit does the following: 1. 2. 3. Saves configuration and state data to %SystemDrive%:\WebesBackup, where %SystemDrive% is the drive where Windows (not necessarily WEBES) was installed. Uninstalls the existing installation. Installs this version with the same components such as SEA that were present before.
24
4. 5.
Restores the saved data. Deletes the WebesBackup directory and all of its contents.
If you answer No, the kit exits and the existing version of WEBES is not upgraded. If desired, you can uninstall the existing WEBES copy yourself, but then not all data will be migrated upon installing the newer version as described in Installing WEBES.
2.4 Downgrading WEBES

Do not save configuration data if you are going back to an earlier WEBES version, for example 5.6 to 5.4 The stored configuration data may not be compatible with an earlier version.
2.5 Uninstalling WEBES

You can uninstall WEBES through the Add/Remove Programs window of the Control Panel. NOTE: Before uninstalling WEBES, log on using an account with administrator privileges and completely close any WEBES components that are running.
2.5.1 Uninstalling on Terminal Servers

From Console Terminal Server system uninstallations should be performed from the Terminal Server console by an administrator (either the Administrator account or any account in the Administrators group). For the best results, make sure that no clients are logged on to the server during WEBES uninstallation. You can send clients a message about the time and duration of the uninstallation and then disable all connections before starting. Otherwise, the process for uninstalling is the same as any other Windows WEBES uninstallation. From Client Uninstall from a Terminal Services client as follows: 1. 2. Log on to the Terminal server as an administrator and close all applications. Uninstall the program as with any other Windows WEBES uninstallation.
2.6 Removing SQL Server

WEBES 6.1 does not require the use of Microsoft SQL Server 2005 or Postgres 8.3.7. This program may have been installed on your system during installation of a previous version of WEBES, or by another application or user. Neither the WEBES 5.6 uninstallation process nor the WEBES 6.1 upgrade process automatically removes SQL Server, since other applications might be sharing this service. You can manually remove the WEBES-related part only, or you can manually remove all of the SQL-Server-related software in order to conserve resources or to minimize the network connection surface area of your system.
2.6.1 Remove WEBESDB SQL Server Only (Recommended)

If you are not certain whether another application might be using SQL Server, you can remove only the WEBESDB SQL Server instance (WEBESDB Database Engine). This instance may be removed without affecting other applications. It can be removed while WEBES 6.1 is running. 1. 2. 3. 4. From Windows Control Panel, run Add/Remove Programs. From the list of programs select Microsoft SQL Server 2005 and click the Remove button. (This does not immediately remove SQL Server). Follow the prompts. Select WEBESDB: Database Engine for removal. Follow the prompts. The WEBESDB SQL Server instance will be removed. NOTE: Other instances of SQL Server (if any) will remain running. No data is deleted as a result of this action. Only software configuration changes are made.
2.6.2 Remove Entire SQL Server (Not Recommended)

If you are certain that you do not need SQL Server running on your system, it is possible to remove it entirely. Doing this is generally not recommended since it may be difficult for you to determine whether SQL Server
2.4 Downgrading WEBES 25
is in use by another application on which you depend. Nevertheless, it is sometimes appropriate to remove SQL Server completely. 1. 2. 3. 4. From Windows Control Panel, run Add/Remove Programs. From the list of programs select Microsoft SQL Server 2005 and click the Change button. (This does not immediately remove SQL Server). Follow the prompts. Select Remove SQL Server. Follow the prompts. The SQL Server instance will be removed. NOTE: No database data is deleted as a result of this action. It is not recommended to delete this data unless you are certain that it will never be needed. Even then, before deleting such data, it is recommended to make a backup copy. By default, SQL Server data is located in the Microsoft SQL Server folder under the Program Files folder.
26
3 WEBES User Interface

The WEBES user interface provides browser-based access to the Service Event Analyzer (SEA) functionality of WEBES. You can use the WEBES user interface to connect to the Director on your local system or on remote systems, analyze and translate their binary event log files, view or edit the list of managed entities, and change various WEBES configuration settings.
3.1 Accessing the System Event Analyzer

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. 1. To log into the SEA, click Start Programs Hewlett-Packard Service Tools System Event Analyzer System Event Analyzer. NOTE: URL: If you are logging into SEA from another system open a web browser and enter the following
https://hostname where director is running:7906. Use the fully qualified host name or the IP address of the system hosting WEBES. 2. You will be prompted to enter a Profile User Name for your session; this can be any name you choose. Enter the name and click Logon IMPORTANT: It is advised to attach adv to the end of your Profile User Name. This enables you to log on as an advanced user and carry out configuration in WEBES. Figure 3-1 Logon Window
3.
If you are prompted by the browser that the site does not have a signed
3.2 Using The WEBES User Interface

After you log on, the browser displays the web interface main screen (Figure 3-2 Main Screen). Figure 3-2 Main Screen
3.1 Accessing the System Event Analyzer
27
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. https://hostname:7906/?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 3-1 Web Interface Components. Table 3-1 Web Interface Components
Component Title Bar Toolbar Description Shows the software version, active profile, and the operating system running WEBES. By default, provides access to the online help, system configuration, processing statistics, WEBES managed entities configuration, WEBES notification settings and new binary error log creation. The toolbar is dynamically updated, and additional features are available with select SEA screens. Displays any browser connectivity errors and any current WEBES configuration warnings. It will typically indicate which aspects of configuration should be addressed first. Lists the available groups, nodes, storage cells, categories, and log files. Displays interactive screens and system information. When SEA loads, the display frame shows product information. Displays messages from the browser and usage tips.
Applet Message Frame Navigation Tree Display Frame Information Bar
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.
3.2.1 Toolbar
Figure 3-3 Toolbar shows the default web interface toolbar. Figure 3-3 Toolbar
The toolbar buttons update dynamically depending on what you are doing. The toolbar buttons are grouped by function. Those in the left hand group are operational buttons that are related to current analysis activity; they are updated dynamically depending on what you are doing. The buttons in the right hand group are configuration buttons that are always available for changing WEBES operational characteristics. Table 3-2 Toolbar Default Buttons describes the toolbar commands that are always available: Table 3-2 Toolbar Default Buttons
Component Progress Window New Binary Error Log Creation WEBES Notification Status Description Opens a new browser window that reports the processing status of log files. Opens the New Binary Log screen in the display frame. Displays notification status.
28
WEBES User Interface
Component Configure RSC Settings
Description Opens the RSC settings screen for configuring enterprise wide information for the Remote Support Client. NOTE: This icon and option only exists for customers who have also installed Insight Remote Support Standard.
Configure SEA Settings Configure Managed Entities Configure Managed Protocols Configure WEBES Managed Sites Configure WEBES Managed Contacts Configure WEBES Notification Settings Help
Opens the SEA settings screen. Allows you to configure WEBES Managed Entities. Allows you to configure WEBES Managed Protocols Allows you to manage WEBES Managed sites. Allows you to configure WEBES Managed contacts. Allows you to configure WEBES notifications including WEBES e-mail settings. Opens a new browser window containing the online user guide.
The following buttons also may appear in the toolbar, depending on the feature being used: Table 3-3 Toolbar Dynamic Buttons
Component Clear Results Button Reprocess File Button Analyze File Button Analyze Filtered Events Button Get Current FRU Table Button Generate Storage Spreadsheet Button Get Current Storage Cell Configuration Button Description Available when viewing automatic analysis details. Available when viewing manual analysis details. See Table 3-8 Additional Toolbar Functions, Reprocess File Button for more information. Available when viewing manual translation details. See Table 3-8 Additional Toolbar Functions, Analyze File Button for more information. Available after processing a file with a filter applied. See Table 3-8 Additional Toolbar Functions, Analyze Filtered Events Button for more information. Available when viewing Real-Time Monitoring of a Tru64 UNIX or OpenVMS Alpha system. See Table 3-8 Additional Toolbar Functions, Get Current FRU Table Button for more information. Available when viewing Real-Time Monitoring of a Storage Cell. Available when viewing Real-Time Monitoring of a Storage Cell. See Table 3-8 Additional Toolbar Functions, Get Current Storage Cell Configuration Button for more information.
3.2.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.
3.2.2.1 Navigation Tree Hierarchy

The entries in the navigation tree are as follows:
29
Figure 3-4 Navigation Tree - Hierarchy
Table 3-4 Navigation Tree - Hierarchy

Folder Groups Nodes Description Multiple computers that are logically associated. Groups contain one or more nodes. Individual computer systems that must also be defined as Managed Entities. Each node has one or more event sources associated with it, such as System Log, Web-Based Enterprise Management (WBEM), or Other Logs. The binary system event log where the computer writes system information. By default, the System log contains Real Time Monitoring and Full View. Automatic analysis results. Manual analysis results for the system event log. 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 NOTE: Storage Cells Other logs may not appear with the tree when connecting to older versions of WCCProxy.
System Log Real Time Monitoring Full View Other Logs
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. A WBEM Common Information Model Object Manager (CIMOM) which sends WBEM indications to WEBES (when WEBES has successfully registered with the CIMOM). By default a WBEM folder contains Real Time Monitoring.
WBEM
3.2.2.2 Features of the Navigation Tree

Figure 3-5 Navigation Tree - Collapsed and Figure 3-6 Navigation Tree - Expanded describe the features and functions of the navigation tree. Figure 3-5 Navigation Tree - Collapsed
30
Figure 3-6 Navigation Tree - Expanded
Table 3-5 Navigation Tree - Features

Feature Description
Current Selection is Highlighted In most browsers, the currently selected entry in the Navigation Tree is highlighted (Figure 3-5 Navigation Tree - Collapsed). Collapsing Navigation Expanding Navigation The tree structure can be collapsed to the group level (Figure 3-5 Navigation Tree - Collapsed). 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. Each entry in the tree has a name and an icon that indicates its type. For example, in Figure 3-6 Navigation Tree - Expanded you can tell that the jarjar.cxo.dec.com node is inactive because of its icon. You can customize the navigation tree by adding and removing groups, nodes, categories, and binary event log files. NOTE: Viewing Managed Entity Configuration Viewing Results Refreshing Navigation Storage cells are generated automatically and cannot be customized by the user.
Icons
Customizing the Navigation Tree
You can view and update the Managed Entity configuration data for a Node in the Navigation Tree. You can view the results of automatic analysis and initiate manual analysis from the navigation tree. 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.
3.2.2.3 Navigation Tree Icons

Table 3-6 Navigation Tree Icons
Icon Description SEA Root node of the Navigation Tree Refresh tree button Button for manual refresh of the Navigation Tree appears at the top level of the tree. Managed Entity node (active). Indicates an active Managed Entity with no special indications.
31
Icon
Description Managed Entity node needs info. Indicates an active Managed Entity that requires user attention probably needs additional configuration data for monitoring of the node can be implemented properly. Managed Entity node has a problem report. Indicates an active Managed Entity that has some sort of Problem report that needs attention. Managed Entity node (inactive). Indicates an inactive Managed Entity this implies that WEBES cannot connect to the Entity, either because of mis-configuration or because the Entity is inaccessible. Problem group
Problem RTM
Problem system log
Reading Log (animation)
Log file
File read
File done
Event
Real Time Monitoring
System log
Category open
Category closed
Node group
Other logs
Storage system
32
Icon
Description Storage system inactive
Storage file done
Storage file read
Problem storage system
Storage cell
Problem storage cell
Storage cell problem report
3.2.2.4 Navigation Tree active links

Nodes at most levels of the Navigation tree have active links which display context sensitive information in the right hand pane when selected. The exception to the rule is an Entity node that is attempting to connect to the designated Managed Entity.
3.2.2.4.1 SEA link
3.2.2.4.2 Group link

The Group level tree node displays the Node Maintenance page for the selected Group in this context a "Node" must be a Managed Entity. This allows for the addition of Managed Entity Nodes to the current Group, or removal of Managed Entity Nodes from the current Group, using the tabs at the bottom of the page.
33
3.2.2.4.3 Entity link

The Entity Node level tree node displays the Configuration page for the selected Managed Entity this is the equivalent of selecting the Managed Entity from the list of Managed Entities that are displayed when the "Configure Managed Entities" button is clicked. A properly configured Managed Entity will be highlighted in yellow (or other user selected color) when selected.
3.2.2.4.4 System Log

Displays the same information as Real Time Monitoring.
3.2.2.4.5 Real Time Monitoring

When selected, the Real Time Monitoring tree node displays the current Problem Reports, raw Events, and configuration collections resulting from automatic analysis of the current Managed Entity.
34
3.2.2.4.6 Full View

When selected, the Full View tree node invokes manual analysis of the system log of the current Managed Entity. The main pane shows the current status of the manual analysis as it is performed, and the resulting Problem reports, event Summary, and raw Events when complete.
35
3.2.2.4.7 Other Logs

The Other Logs tree node displays the Log File Maintenance page when selected. This allows for the addition or removal of log files using the tabs at the bottom of the page. These files can then be selected to have manual analysis run against their contents.
3.2.2.4.8 Other Logs file

The individual files listed under the Other Logs tree node can be selected to have manual analysis run against their contents. The main pane shows the current status of the manual analysis as it is performed, and the resulting Problem reports, event Summary, and raw Events when complete.
36
3.2.2.4.9 WBEM
Displays the same as Real Time Monitoring.
37
3.2.3 Applet Messages

The Toolbar contains a short message pane which displays messages indicating potential issues with the operational status of WEBES. Errors are color coded in red while warnings are color coded in amber. These messages are not a definitive statement of the current status, but when present these messages give hints and guidance as to which aspect of WEBES may need attention.
Table 3-7 Applet Messages

Message Lost Connection to Director! Connection error! Warning: No sites configured Warning: No contacts configured Warning: No notifications configured Warning: Site needs info Warning: Contact needs info Warning: Entity needs info Warning: Email settings not configured Description The WUI cannot connect to the Director. Any information displayed in the WUI is likely to be stale. An unknown error has occurred which is preventing proper connection to the Director. No Managed Sites are configured. You should normally have at least one Managed Site configured. No Managed Contacts are configured. You should normally have at least a primary contact for each Managed Entity that is being monitored. No Notifications are configured so WEBES cannot report any problems it may find with a Managed Entity. One or more Managed Sites need additional configuration information to be entered. One or more Managed Contacts need additional configuration information to be entered. One or more Managed Entities need additional configuration information to be entered. Email settings have not been configured correctly.
Only one message can be displayed at a time. When multiple issues are detected, the applet will display the message that is likely to be most important to fix first. When that issue is fixed, the next most important message will be displayed, and so on until there are no outstanding messages to display.
3.3 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.
3.3.1 Groups
From the navigation tree, you can create new groups and remove existing groups.
3.3.1.1 Adding Groups

To add new groups follow these steps: 1. 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 3-7 Add Group). The Add Groups tab is already selected.
Figure 3-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. 2. 3. 4. 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: 5. 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.
3.3.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: 1. 2. 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 3-8 Remove Group).
39
Figure 3-8 Remove Group
3.
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.
4.
Click the Remove Selected Group(s) button. The groups disappear from the navigation tree.
3.3.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.
3.3.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: 1. Select the group you want to add nodes to from the navigation tree. The "Node Maintenance" screen appears in the display frame (Figure 3-9 Add Node). The Add Nodes tab is already selected.
40
Figure 3-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. 2. 3. 4. 5. Select the existing managed entity from the drop-down list. Select where in the tree the new node will be placed. Select a placement option using the radio buttons. Click the Add New Node button. The new node appears under its group in the navigation tree.
3.3.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: 1. 2. 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 3-10 Remove Node).
41
Figure 3-10 Remove Node
3.
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.
4.
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.
3.3.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 3-1 Activating Node 1
If the Director on the remote node is accessible, a message appears in the display frame (Figure 3-12 Activating Node Message) and the navigation tree is updated to show the new status. Figure 3-12 Activating Node Message
42
If the Director is not accessible, a message appears in the display frame (Figure 3-13 Unable to Activate Node Message) and the navigation tree is not changed. Figure 3-13 Unable to Activate Node Message
3.3.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. 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.
3.3.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: 1. Select the Other Logs folder for the node you want to have new categories. The Category Maintenance screen appears in the display frame (Figure 3-14 Add Category). The Add Categories tab is already selected. Figure 3-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 Step 2 and Step 3. 2. 3. Select an existing category from the list. Select a placement option from the radio buttons.
43
4.
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.
5.
Click the Add New Category button.
The new category appears in the navigation tree.
3.3.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: 1. 2. 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 3-15 Remove Category). Figure 3-15 Remove Category
3.
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.
4.
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.
3.3.4 Event Sources

Each Entity Node is associated with one source of real time events, and may also be associated with a set of event log files which are available for manual analysis. The source of real time events is dependent on the type of Managed Entity that the node represents, for example, a WBEM CIMOM is the source of event information (called Indications in relation to WBEM communications) for WBEM servers and the System Log currently provides event information for other types of servers."
3.3.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.
3.3.4.2 WBEM
The WBEM CIMOM is the source of WBEM Indications (event information) for systems/servers that support WBEM services, provided that WEBES has successfully subscribed with the CIMOM for WBEM indications. To view the analysis options for WBEM, in the navigation tree, click the expansion symbol associated with a WBEM entry: Real Time Monitoring shows the results of automatic analysis in the display frame.
3.3.4.3 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.
The best place to store log files (as well as other user data) is in one of the user data subdirectories: svctools\specific\ca\userdata svctools\common\ca\userdata
3.3 Customizing the Navigation Tree 45
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, Configuration, and Usage 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. 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. Adding Other Logs Follow these steps to add other log files: 1. 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 3-16 Add Log Files Tab). The Add Files tab is already selected. Figure 3-16 Add Log Files Tab
2.
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.
3. 4.
(Optional) If enabled, enter the path and filename in the text field. 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: 1. 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. 2. Select the Remove Files tab from the bottom of the screen (Figure 3-17 Remove Log File Tab).
46
Figure 3-17 Remove Log File Tab
3.
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.
4.
Click the Remove Selected Log File(s) button. The navigation tree is refreshed to reflect your changes.
3.4 Processing Events

WEBES continually performs automatic translation and analysis of events for every Managed Entity as a background activity. You can initiate manual translation and/or analysis of log files, and view the current status and results of automatic and manual analysis jobs for a given Managed Entity by using the following methods: Selecting System Log, WBEM, or Real Time Monitoring displays the recent results of automatic analysis for the node. Clicking Full View initiates manual analysis of a node's system event log and displays the results. Clicking a Log File name under Other Logs runs a manual analysis on the file and displays the results.
The IPF configuration reports 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 3.4 Processing Events 47
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 ----------0 1 2 CELL # -----0 2, 3 1 DIMM # -----0B 1B 2B 3B 4B 5B 6B 7B 8B 9B 10B 11B 12B 13B 14B 15B Size ----------2048 MB 2048 MB 2048 MB 2048 MB 2048 MB 2048 MB 2048 MB 2048 MB ---------
0x4
DIMM # Size ------ ----------0A 2048 MB 1A 2048 MB 2A 2048 MB 3A 2048 MB 4A 2048 MB 5A 2048 MB 6A 2048 MB 7A 2048 MB 8A -9A -10A -11A -12A -13A -14A -15A -32 GB Total Memory DIMM # Size ------ ----------0A 2048 MB 1A 2048 MB 2A 2048 MB 3A 2048 MB 4A 2048 MB 5A 2048 MB 6A 2048 MB 7A 2048 MB 8A -9A -10A -11A -12A -13A -14A -15A -32 GB Total Memory
0x5
DIMM # -----0B 1B 2B 3B 4B 5B 6B 7B 8B 9B 10B 11B 12B 13B 14B 15B
Size ----------2048 MB 2048 MB 2048 MB 2048 MB 2048 MB 2048 MB 2048 MB 2048 MB ---------
0x6
DIMM # Size DIMM # Size ------ ----------- ------ ----------0A 2048 MB 0B 2048 MB
48
1A 2048 2A 2048 3A 2048 4A 2048 5A 2048 6A 2048 7A 2048 8A -9A -10A -11A -12A -13A -14A -15A -32 GB Total 1 0x7 3
MB MB MB MB MB MB MB
1B 2B 3B 4B 5B 6B 7B 8B 9B 10B 11B 12B 13B 14B 15B
2048 2048 2048 2048 2048 2048 2048 ---------
MB MB MB MB MB MB MB
Memory DIMM # -----0B 1B 2B 3B 4B 5B 6B 7B 8B 9B 10B 11B 12B 13B 14B 15B Size ----------2048 MB 2048 MB 2048 MB 2048 MB 2048 MB 2048 MB 2048 MB 2048 MB ---------
DIMM # Size ------ ----------0A 2048 MB 1A 2048 MB 2A 2048 MB 3A 2048 MB 4A 2048 MB 5A 2048 MB 6A 2048 MB 7A 2048 MB 8A -9A -10A -11A -12A -13A -14A -15A -32 GB Total Memory
Viewing Analysis Progress You can view the current status of any automatic or manual analysis job by clicking on the Progress Window button in the toolbar to open a new window that displays all the queued and running analysis jobs, and event counts for each job. Whenever manual analysis is invoked for a log file, an animated icon is used to reflect the running status of the manual analysis job; when analysis of the log file is complete, the icon in the navigation tree changes to reflect the results of the manual analysis, and the results are shown in the display pane. NOTE: After clicking on the file for manual analysis there may be a delay before the progress window displays progress for that file.The data in the progress is not displayed in real time. There may be couple seconds difference in the actual progress and what is displayed in the progress window. Viewing Results The results of automatic and manual analysis are shown in the display frame when an appropriate selection is made in the navigation tree. Some or all of the following information is available, depending on the type of Managed Entity and the type of analysis involved: Problem Reports results of analysis Summary a count of the number of each type of event found in an analyzed log file (only available with manual analysis)
3.4 Processing Events 49
Events chronological list of events received from an event source Configuration Entries lFRU configuration events received from the event source
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. Analysis Failed If the file cannot be processed for any reason, a message similar to the one in Figure 3-18 Analysis Failed Message is shown. Figure 3-18 Analysis Failed Message
3.4.1 Additional Toolbar Functions

SEA provides additional functionality depending on the type of processing you are performing. Table 3-8 Additional Toolbar Functions
Button Name Clear Results Button When Does It Appear in the Toolbar? When you are performing or viewing Automatic Analysis. When you are performing Manual Analysis. Description The Clear button removes all the entries (problem reports and events) from the display tabs. The Reprocess button forces SEA to discard the previous analysis results and reprocess the selected binary log file.
Reprocess File Button
Analyze File Button
When the User Settings are configured Clicking the Analyze button will perform to perform only manual translation by analysis for the current log file. Thus, if default. you need to perform analysis, it is not necessary to change the User Settings and reprocess the file. When you use a filter for processing a Clicking the Analyze Filtered event log file. button allows you to repeat the analysis using only the events that met the filter criteria. When you are performing or viewing Automatic Analysis on a Tru64 UNIX or OpenVMS Alpha node. Clicking the FRU button reads the current Field Replaceable Unit (FRU) hardware configuration table from the node's in-memory table and adds the table as an entry to the Configuration Entries tab. The Get Current Storage Cell Configuration button adds an entry to the Configuration Entries tab for the selected storage cell, detailing the hardware configuration of the storage cell.
Analyze Filtered Events Button
Get Current FRU Table Button
Get Current Storage Cell Configuration Button
When you are performing Automatic Analysis of a Storage Cell.
3.4.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.
3.4.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 3-19 Status Icons shows the icons used to indicate analysis results.
50
Figure 3-19 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: dash. If you are only performing translation, when processing completes the icon will appear with a
3.4.2.2 Progress Window

You can open the Progress window by clicking on the Progress Window button in the toolbar (see Figure 3-3 Toolbar). The Progress window opens in a new browser window (Figure 3-20 Progress Window). Figure 3-20 Progress Window
3.4 Processing Events
51
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
NOTE: After clicking on a file for manual analysis there may be a delay before the progress window displays progress for that file.The data in the progress is not displayed in real time. There may be couple seconds difference in the actual progress and what is displayed in the progress window. 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.
3.4.3 Working With Results

After processing, the results of analysis are shown on the tabs in the display frame (Figure 3-21 Additional Entries Navigation). Figure 3-21 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. You can control the number of entries shown in a tab with the options in the User Settings window.
NOTE:
3.4.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 3-22 Problem Report Tab. Figure 3-22 Problem Report Tab
52
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. To view the contents of a report, click on its entry in the list of available problem reports.
The problem reports generated by the web interface are the same as those generated by the CLI.
3.4.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 3-23 Summary Tab). Figure 3-23 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.
3.4.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 gray color. The colors of the event description signify the following about their nature. Table 3-9 Event Type Color Codes
Color Red Green Blue Dark Orange Magenta Purple Nature of the Event Significant events Configuration events, and return to normal status from a previous failure EVA Reboot/Resync/Restart etc Data Availability, CA, Customer attention needed Drive firmware update events 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 3-24 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 3-25 Sub-Type Listing
3.4.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 3-26 Events Tab).
54
NOTE:
You can control the fields that are shown on the events tab from the User Settings window.
Figure 3-26 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. To view the translation of an event, click on its entry in the list.
The translated events shown by the Web interface are the same as those shown by the CLI.
3.4.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). 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.
3.4.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, 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 Figure 3-27 Navigation ButtonsProblem Reports and Figure 3-28 Navigation ButtonsEvents.
Figure 3-27 Navigation ButtonsProblem Reports
Figure 3-28 Navigation ButtonsEvents
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. The Event Details tab includes a drop down list that can be used to change the report type.
3.5 Managed Protocols

This section is limited to topics specific to the Web interface. You can use the Managed Protocols tool to create and edit communication protocols that will be used to access and retrieve event data from your managed entities. After the appropriate protocol information is configured, you can then apply those protocols to each managed entity as needed.
3.5.1 Add New Protocol

To add a new protocol: 1. Click on the Configure Webes Managed Protocols icon on the SEA Tool Bar. The Managed Protocol screen will open in the SEA. NOTE: name. To edit the credential information for an existing or default protocol, just click the protocol
2.
Click the New button to create a new protocol. The Managed Protocol Type screen will open.
56
3.
Enter a name for your protocol and select the protocol type from the drop-down list. You can create as many protocols as you have varied credentials for you managed entities. If each of your managed entities has unique usernames and passwords, then create a protocol for each set of credentials appropriate to the communication method used by that managed entity. The following Managed Protocol types can be created: Binary Event Log Command View EVA Non-stop WBEM SNMP SANIQ WS-MAN Used for Superdome 2 devices. UNIX WBEM WMI WBEM (Windows) SSH TELNET
4.
Click Apply Changes. The Managed Protocol Details screen will open. The following examples show protocol details for various protocol types. Provide the credential information for the protocol type you are configuring. Figure 3-29 Protocol Details: Binary Event Log
3.5 Managed Protocols
57
Figure 3-30 Protocol Details: CommandView EVA
Figure 3-31 Protocol Details: SNMP
Figure 3-32 Protocol Details: WMI for Windows
5.
Click Apply Changes when you are finished configuring your protocol details.
3.6 Managed Entities

This section is limited to topics specific to the Web interface. After adding the required managed devices, you can see the list of managed devices in the Managed Entity page. Figure 3-33 Managed Entities shows the list of all the devices managed by this node. Some WEBES nodes may manage many devices, some of which require configuration information. To view only those devices, click the View filtered list button.
58
IMPORTANT: Remember to edit, create, and manage your Webes Managed Protocols BEFORE you add, create, or edit your Webes Managed Entities. The protocols will be applied to the entities, so it is important to create the protocols first. Figure 3-33 Managed Entities
Any managed entity that is not fully configured is highlighted with an orange background, and has an asterisk indicating that further configuration information is required. To remove the managed devices, check the device name and click the Delete button. Click Select All and then click Delete to delete all the managed devices. 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 3-34 Managed Entity Detail.
59
Figure 3-34 Managed Entity Detail
Specific fields may vary according to the type of managed entity the example shows the detailed fields for a Command View EVA Server. NOTE: WEBES requires a fully qualified domain name (FQDN) or an IP address to be provided in the following Managed Entities page fields: User-Definable Entity Name Entity Name on Network
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 you have created protocols that are appropriate to your managed entity type, those options will be displayed on the Managed Entity Detail screen. You can enable and disable protocols for each Managed Entity by using the corresponding drop-down list.
3.6.1 Adding a Managed Entity

If you need to add a managed entity:
1. 2.
Click the New button on the Managed Entities screen. Enter the Fully Qualified Host Name for your managed entity in the text box, and make sure the Discover Protocols check box is marked.
3.
Click the Apply Changes button to add the Managed Entity.
3.6.2 Exporting Managed Entity Information

Two additional buttons are available to advanced users in the web-based interface at the bottom of the Managed Entities page. The Export button allows you to export details for a WEBES system's managed entities, contacts, and sites to an XML file that can be subsequently imported by another (or the same) WEBES system via the Import button (see Figure 3-35 Managed Entities). Figure 3-35 Managed Entities
To export WEBES configuration information for managed entities (except for access credentials), contact details, and site information associated with a WEBES node, click the Export button. A popup Export Managed Entities page provides details of the information that has been exported (see Figure 3-36 Export Managed Entities popup) and details of where the XML files have been saved.
61
Figure 3-36 Export Managed Entities popup
To import previously exported WEBES information, click the Import button. WEBES checks for relevant XML files in particular folders and a popup Import Managed Entities page is displayed that displays details of the entities, contacts, and sites that may have been imported. Access details for each imported entity must then be manually configured.
3.7 Getting Help

The WEBES user interface provides usage tips and a link to documentation
3.7.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.
3.7.2 WEBES Documentation

Click on the Help button from the toolbar to view the current WEBES documentation which is located at http://h18023.www1.hp.com/support/svctools/webes/index.html
3.8 WEBES User Interface - Advanced Functions

The following advanced functions are described in detail in the WEBES Reference Guide. Creating New Log Files Applying Filters Modifying Settings Logging Off Service Obligation Not every user will need to utilize these functions when working with WEBES.
NOTE:
62
4 Automatic Notifications
This chapter describes how SEA can automatically notify you or HP Services whenever automatic analysis has detected an event.
4.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.
4.2 Web Interface Notification Settings Page

On the Web interface main screen, you can navigate to the Notification Settings page by clicking on its toolbar button (yellow triangle with a red question mark). The page will look similar to this example: Figure 4-1 Web Interface Notification Settings Page
You can enable or disable any of the listed notifications by changing the appropriate pull-down menu (on or off). To view or update additional settings, where available, you can click the link from the Setting column to display a specific notification configure page. Notifications that have been enabled are shown in green. Certain notifications only make sense to enable if the corresponding partner software is installed. In this example, the user has enabled notification of problem reports from WEBES to HP SIM, but the HP SIM software product has not been installed on the same system that WEBES is installed on. In this case, HP SIM notification is still enabled, but that row is colored red to indicate a problem. To write a test binary event to the system's event log, click the Test Event button. This is a good way to verify that notifications are working as expected, because the test event will be recognized, analyzed, and notifications sent for all enabled notification types. Clicking the Test Event button is equivalent to issuing the CLI command "wsea test".
4.1 When Are Notifications Sent?
63
4.3 Web Interface Notification Status and Dispatch Page

On the Web interface main screen, you can navigate to the Notification Status and Dispatch page by clicking on its toolbar button (yellow triangle with a red question mark, within the icon that also contains a display and network lines). The page will look similar to this example: Figure 4-2 Web Notifications
The initial screen shows the Status of all notifications sent. In this example, one SEATEST event callout (problem report) was successfully delivered to the SMTP (email) and LOG (prob.log file) notifications in January and February, but the one in February was not able to be delivered to HP SIM, and is still in transit (notification being attempted and retried) to Microsoft Operations Manager (MOM). You can click the link under the ID column to view the problem report, regardless of which notifications succeeded or failed. Also regardless of which notifications succeeded or failed, you can choose to explicitly and immediately dispatch any problem report to any desired notification type, even if you have not enabled that notification type. To dispatch a problem report, click the Dispatch tab at the bottom of this page. The page will look similar to this example: Figure 4-3 WEBES Notification Dispatch
64
Automatic Notifications
To dispatch one or more problem reports, click on the problem reports shown in the Step 1 list, using the standard Shift-click and Ctrl-click for multiple selections. Then, to dispatch these problem reports to one or more notification types, click on the types shown in the Step 2 list, using the standard Shift-click and Ctrl-click for multiple selections. Click the Send Notifications button to send the selected problem reports to the selected notifications. Another feature of this page is to remove problem reports from the list shown in the Status tab (the previous screen). Using the standard Shift-click and Ctrl-click for multiple selections, select the problem reports you wish to remove, in the Step 1 list, and click the Remove Problem Reports From Notification History button. You will no longer be able to see the notification status, the content of the problem report, or dispatch it to a notification type, after you click this button.
4.4 Service Events vs. Info Events

SEA automatic analysis detects and reports on two kinds of events:
4.4.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 and as secure transmissions to HP Services.
4.5 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, 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
4.6 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 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.
4.6.1 Settings
During installation, WEBES prompts for the following: SMTP server address Sender's e-mail address List of e-mail addresses that you want to send reports to
Without valid addresses, SEA cannot send email notifications. After installation, you can change these settings using the Command Line Interface or the Web Interface. A "valid" address depends on what the SMTP server decides is valid. Some servers check the validity of the username or the domain, or both. Some servers return errors where others silently discard the email if it does not consider an address valid. WEBES does not check nor constrain the format or validity of addresses.
4.4 Service Events vs. Info Events 65
Check the validation policies of the SMTP server you use, if you suspect that WEBES emails are not being delivered. If WEBES is connected to HP SIM, then the SMTP server name and port, and the sender's email address supplied by SIM overrides the local WEBES value for these settings. The email recipients are the union of the HP SIM supplied recipients and the WEBES recipients. If WEBES is not connected to HP SIM, then the local WEBES settings are used. If no email sender's address is specified, then a system generated one is used. This will be in the form: <sysname>.webes@<domain> where <sysname> is the local system name, and <domain> is the part of the SMTP server address following the first period, which is not necessarily the domain of the system on which WEBES is installed. For example, if the SMTP server is "smtpserver1.acme.com" and the local host name is "slater.acmelab.com", then: derived sender's address = slater.webes@acme.com
4.6.1.1 Web Interface Email Settings Page

The web interface provides a single page where all the SMTP email settings can be viewed and changed. To access the email notifications page, click the the Configure WEBES Notifications Settings icon ( ) on the toolbar to display the WEBES Notifications Settings page (see Figure 4-1 Web Interface Notification Settings Page) and then click the Email notification link to display the WEBES Email Settings page (see Figure 4-4 E-mail Settings). Figure 4-4 E-mail Settings
Multiple email addresses may be entered in the Recipients and CC fieldsuse a semi-colon between each email address.
66
Automatic Notifications
If HP SIM is connected, then the SMTP server name and port, and the "from email address" fields cannot be changed. They automatically revert to the HP SIM supplied values as soon as the Apply Changes button is pressed. The Test Email button generates a test email which is sent using the latest applied email settings. WEBES will attempt to send the test email directly to the nominated SMTP serverit does not rely on WEBES notification and it will not appear in any Problem Report displays. A results page is displayed when the test email has been sent. To validate the SMTP settings, check that all nominated recipients and CC addressees have received the test email. To write a test binary event to the system's event log, click the Test Event button. This is a good way to verify that notifications are working as expected, because the test event will be recognized, analyzed, and notifications sent for all enabled notification types. Using the Test Event button is equivalent to issuing the CLI command wsea test.
4.6 Sending Notifications to Email Addresses
67

WEBES 61 Install

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WEBES 61 Install

Uploaded by

Copyright:

Available Formats

Web Based Enterprise Services 6.

HP Part Number: 5900-1 104 Published: August, 2010

3 WEBES User Interface...............................................................................27

About This Document

term variable value <element> attrib=

WEBES Reference Guide

1.1 What is WEBES?

1.2 What is the System Event Analyzer?

1.3 What is the Director?

1.3.1 SEA and the Director

1.1 What is WEBES?

1.4.1 ELMC Version in WEBES

1.5 WEBES Hardware Requirements

1.6 WEBES Operating System Requirements

Microsoft Windows Server 2008 with Service Pack 1, Service Pack 2, or R2

1.7 What is New in this Release?

1.7.1 Kauai Support

1.7.2 ELMC No Longer Seen as a Separate Package

1.7.3 PostgreSQL 8.4.1 Included in WEBES 6.1

1.8 Installation Kit

2.1.2 SEA System Requirements

2.1.4 Archiving and Cleaning the Windows Event Log

2.1.5 Installing on Terminal Servers

2.2 Installing WEBES

Figure 2-2 Configuration Wizard - User Information

Table 2-2 WEBES Information Requested During Installation

XYZ Company 123-456-7890 chris.green@xyzcompany.com mailsys.xyzcompany.com A01234567890

Enter profile and notification details

2.2 Installing WEBES

Figure 2-3 Configuration Wizard - Profile and Notification Details

Table 2-3 WEBES Information Requested During Installation

Address, City, ... Primary Contact

123, Main Street, Metropolis, VA 22222 Chris Green

Secondary Contact Phone Number

Pat Brown 123-456-7890

Enter configuration details

Figure 2-4 Configuration Wizard - Configure WEBES

Table 2-4 WEBES Information Requested During Installation

System Serial Number System name

Fixed or DHCP Server

Validate the service obligation number of the system/subsystem

2.2 Installing WEBES

Figure 2-5 WEBES Service Obligation Validation

Table 2-5 WEBES Information Requested During Installation

Figure 2-6 Clean Binary Error Log

2.2 Installing WEBES

Figure 2-8 WEBES Install Complete

2.3 Upgrading WEBES

2.4 Downgrading WEBES

2.5 Uninstalling WEBES

2.5.1 Uninstalling on Terminal Servers

2.6 Removing SQL Server

2.6.1 Remove WEBESDB SQL Server Only (Recommended)

2.6.2 Remove Entire SQL Server (Not Recommended)

3 WEBES User Interface

3.1 Accessing the System Event Analyzer

3.2 Using The WEBES User Interface

3.1 Accessing the System Event Analyzer

Applet Message Frame Navigation Tree Display Frame Information Bar

WEBES User Interface

Component Configure RSC Settings

3.2.2.1 Navigation Tree Hierarchy

3.2 Using The WEBES User Interface