webes 61 install

Web Based Enterprise Services 6.1Installation, Configuration, and Usage Guide

HP Part Number: 5900-1104Published: 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.211 and 12.212, CommercialComputer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government undervendor'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 expresswarranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shallnot 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.....................................................................................91 Intended Audience...............................................................................................................................92 Publishing History................................................................................................................................93 Typographic Conventions......................................................................................................................94 Related Documents...............................................................................................................................9

1 General Information..................................................................................111.1 What is WEBES?.............................................................................................................................111.2 What is the System Event Analyzer?...................................................................................................111.3 What is the Director?.......................................................................................................................11

1.3.1 SEA and the Director................................................................................................................111.4 ELMC.............................................................................................................................................12

1.4.1 ELMC Version in WEBES...........................................................................................................121.5 WEBES Hardware Requirements........................................................................................................121.6 WEBES Operating System Requirements.............................................................................................121.7 What is New in this Release?............................................................................................................13

1.7.1 Kauai Support..........................................................................................................................131.7.2 ELMC No Longer Seen as a Separate Package............................................................................131.7.3 PostgreSQL 8.4.1 Included in WEBES 6.1....................................................................................13

1.8 Installation Kit.................................................................................................................................131.9 Upgrades.......................................................................................................................................13

2 Installing on Windows..............................................................................152.1 Pre-Installation.................................................................................................................................15

2.1.1 WEBES System Requirements......................................................................................................152.1.2 SEA System Requirements..........................................................................................................162.1.3 Permissions..............................................................................................................................172.1.4 Archiving and Cleaning the Windows Event Log..........................................................................172.1.5 Installing on Terminal Servers.....................................................................................................17

2.2 Installing WEBES.............................................................................................................................182.3 Upgrading WEBES..........................................................................................................................242.4 Downgrading WEBES......................................................................................................................252.5 Uninstalling WEBES.........................................................................................................................25

2.5.1 Uninstalling on Terminal Servers................................................................................................252.6 Removing SQL Server......................................................................................................................25

2.6.1 Remove WEBESDB SQL Server Only (Recommended)...................................................................252.6.2 Remove Entire SQL Server (Not Recommended)...........................................................................25

3 WEBES User Interface...............................................................................273.1 Accessing the System Event Analyzer..................................................................................................273.2 Using The WEBES User Interface.......................................................................................................27

3.2.1 Toolbar..................................................................................................................................283.2.2 Navigation.............................................................................................................................29

3.2.2.1 Navigation Tree Hierarchy................................................................................................293.2.2.2 Features of the Navigation Tree.........................................................................................303.2.2.3 Navigation Tree Icons......................................................................................................313.2.2.4 Navigation Tree active links..............................................................................................33

3.2.2.4.1 SEA link.................................................................................................................333.2.2.4.2 Group link.............................................................................................................333.2.2.4.3 Entity link...............................................................................................................343.2.2.4.4 System Log.............................................................................................................343.2.2.4.5 Real Time Monitoring..............................................................................................34

Table of Contents 3

3.2.2.4.6 Full View................................................................................................................353.2.2.4.7 Other Logs.............................................................................................................363.2.2.4.8 Other Logs file........................................................................................................363.2.2.4.9 WBEM..................................................................................................................37

3.2.3 Applet Messages....................................................................................................................383.3 Customizing the Navigation Tree.......................................................................................................38

3.3.1 Groups...................................................................................................................................383.3.1.1 Adding Groups................................................................................................................383.3.1.2 Removing Groups.............................................................................................................39

3.3.2 Nodes...................................................................................................................................403.3.2.1 Adding Nodes................................................................................................................403.3.2.2 Removing Nodes.............................................................................................................413.3.2.3 Activating Nodes............................................................................................................42

3.3.3 Categories.............................................................................................................................433.3.3.1 Adding Categories..........................................................................................................433.3.3.2 Removing Categories.......................................................................................................44

3.3.4 Event Sources.........................................................................................................................443.3.4.1 System Log.....................................................................................................................453.3.4.2 WBEM..........................................................................................................................453.3.4.3 Other Logs.....................................................................................................................45

3.4 Processing Events............................................................................................................................473.4.1 Additional Toolbar Functions.....................................................................................................503.4.2 Processing Status....................................................................................................................50

3.4.2.1 Navigation Tree..............................................................................................................503.4.2.2 Progress Window...........................................................................................................51

3.4.3 Working With Results..............................................................................................................523.4.3.1 Problem Reports..............................................................................................................523.4.3.2 Summary.......................................................................................................................533.4.3.3 Sub Type Tallied Summaries and Event Listings....................................................................533.4.3.4 Events............................................................................................................................543.4.3.5 Sorting Results................................................................................................................553.4.3.6 Displaying Details...........................................................................................................55

3.5 Managed Protocols.........................................................................................................................563.5.1 Add New Protocol...................................................................................................................56

3.6 Managed Entities............................................................................................................................583.6.1 Adding a Managed Entity........................................................................................................603.6.2 Exporting Managed Entity Information.......................................................................................61

3.7 Getting Help..................................................................................................................................623.7.1 Usage Tips..............................................................................................................................623.7.2 WEBES Documentation............................................................................................................62

3.8 WEBES User Interface - Advanced Functions.......................................................................................62

4 Automatic Notifications.............................................................................634.1 When Are Notifications Sent?...........................................................................................................634.2 Web Interface Notification Settings Page...........................................................................................634.3 Web Interface Notification Status and Dispatch Page...........................................................................644.4 Service Events vs. Info Events............................................................................................................65

4.4.1 Service Events.........................................................................................................................654.5 Informational Events........................................................................................................................654.6 Sending Notifications to Email Addresses...........................................................................................65

4.6.1 Settings..................................................................................................................................654.6.1.1 Web Interface Email Settings Page.....................................................................................66

4 Table of Contents

List of Figures2-1 Configuration Wizard - SNMP Question.............................................................................................182-2 Configuration Wizard - User Information............................................................................................192-3 Configuration Wizard - Profile and Notification Details........................................................................202-4 Configuration Wizard - Configure WEBES..........................................................................................212-5 WEBES Service Obligation Validation...............................................................................................222-6 Clean Binary Error Log....................................................................................................................232-7 WEBES Installation Execution............................................................................................................232-8 WEBES Install Complete...................................................................................................................243-1 Logon Window...............................................................................................................................273-2 Main Screen..................................................................................................................................273-3 Toolbar..........................................................................................................................................283-4 Navigation Tree - Hierarchy..............................................................................................................303-5 Navigation Tree - Collapsed.............................................................................................................303-6 Navigation Tree - Expanded.............................................................................................................313-7 Add Group....................................................................................................................................393-8 Remove Group................................................................................................................................403-9 Add Node.....................................................................................................................................413-10 Remove Node..............................................................................................................................423-11 Activating Node...........................................................................................................................423-12 Activating Node Message..............................................................................................................423-13 Unable to Activate Node Message..................................................................................................433-14 Add Category..............................................................................................................................433-15 Remove Category.........................................................................................................................443-16 Add Log Files Tab.........................................................................................................................463-17 Remove Log File Tab......................................................................................................................473-18 Analysis Failed Message................................................................................................................503-19 Status Icons..................................................................................................................................513-20 Progress Window.........................................................................................................................513-21 Additional Entries Navigation.........................................................................................................523-22 Problem Report Tab.......................................................................................................................523-23 Summary Tab...............................................................................................................................533-24 Summary of Sub-Types...................................................................................................................543-25 Sub-Type Listing............................................................................................................................543-26 Events Tab...................................................................................................................................553-27 Navigation Buttons—Problem Reports..............................................................................................563-28 Navigation Buttons—Events............................................................................................................563-29 Protocol Details: Binary Event Log...................................................................................................573-30 Protocol Details: CommandView EVA..............................................................................................583-31 Protocol Details: SNMP..................................................................................................................583-32 Protocol Details: WMI for Windows................................................................................................583-33 Managed Entities..........................................................................................................................593-34 Managed Entity Detail...................................................................................................................603-35 Managed Entities..........................................................................................................................613-36 Export Managed Entities popup......................................................................................................624-1 Web Interface Notification Settings Page...........................................................................................634-2 Web Notifications...........................................................................................................................644-3 WEBES Notification Dispatch...........................................................................................................644-4 E-mail Settings................................................................................................................................66

5

List of Tables1-1 ELMC Versions Packaged in WEBES..................................................................................................122-1 Windows Browser Requirements........................................................................................................162-2 WEBES Information Requested During Installation................................................................................192-3 WEBES Information Requested During Installation................................................................................202-4 WEBES Information Requested During Installation................................................................................212-5 WEBES Information Requested During Installation................................................................................223-1 Web Interface Components..............................................................................................................283-2 Toolbar – Default Buttons.................................................................................................................283-3 Toolbar – Dynamic Buttons...............................................................................................................293-4 Navigation Tree - Hierarchy..............................................................................................................303-5 Navigation Tree - Features................................................................................................................313-6 Navigation Tree Icons......................................................................................................................313-7 Applet Messages............................................................................................................................383-8 Additional Toolbar Functions............................................................................................................503-9 Event Type Color Codes...................................................................................................................53

7

About This Document1 Intended Audience

This document is for WEBES standalone users who install the Web-Based Enterprise Services (WEBES) productwithout Insight Remote Support Advanced or Insight Remote Support Standard.

2 Publishing HistoryDescriptionRevision

Created initial copy for WEBES 5.1 using WEBES 5.0 baselinecopy

29-June-2007

Updated for WEBES 5.1July 2007 - Jan 2008

Updated for WEBES 5.2May 2008

Updated for WEBES 5.4January 2009

Updated for WEBES 5.5April 2009

Updated for WEBES 5.6September 2009

Updated for WEBES 6.0March 2010

Updated for WEBES 6.1August 2010

3 Typographic Conventionsfind(1) HP-UX manpage. In this example, “find” is the manpage name and “1” is the

manpage section.Book Title Title of a book or other document.Linked Title Title that is a hyperlink to a book or other document.http://www.hp.com A Web site address that is a hyperlink to the site.Command Command name or qualified command phrase.user input Commands and other text that you type.computer output Text displayed by the computer.Enter 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 labeledCtrl while pressing the A key.

term Defined use of an important word or phrase.variable The name of an environment variable, for example PATH or errno.value A value that you may replace in a command or function, or information in a display

that represents several possible values.<element> An element used in a markup language.attrib= An attribute used in a markup language.

4 Related Documents▲ WEBES Reference Guide

This document provides further information about using and troubleshooting WEBES.

1 Intended Audience 9

#xidi.fm.conventions.citetitle.url

http://www.hp.com

1 General InformationThis 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 supportedoperating 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 operatingsystems 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 servicesto 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 heterogeneousplatforms

• Set of notification mechanisms

The WEBES Service Event Analyzer tool uses these common components to minimize the tool-specificfunctionality 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 singleerror/fault events, as well as multiple event correlation and complex analysis. In addition to the traditionalbinary 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 processingevents as they occur. The events are checked against the analysis rules. If one or more of the events meetsthe conditions specified in the rules, the analysis engine uses the relevant event data to create a problemreport containing a description of the problem and any corrective actions required. Once the problem reportis 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 continuouslyrunning process called the Director, and can perform a variety of tasks from a remotely connected webbrowser. In addition, a set of command line interface (CLI) tools enable diagnosis of binary event logs withoutconnecting 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 astandalone system or a node in a cluster, on behalf of WEBES and executes the functionality of individualWEBES tools.

1.3.1 SEA and the DirectorSEA enables the Director to capture and interpret hardware events, either automatically or at the request ofan outside process. The Director captures, translates, and analyzes the events, and routes messages for theSEA 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 runon a system at any time, many web browser connections can be simultaneously active and all connected toa single Director. See Chapter 3 “WEBES User Interface” for user interface details.

1.1 What is WEBES? 11

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 ELMCELMC is a daemon process that runs continuously. ELMC contains functions that allow WEBES to interactwith the operating system, other WEBES agent processes, and the Director. The Director will not performcorrectly without the WCCProxy service.ELMC automatically starts along with the system and normally does not require additional attention. SeeWEBES 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 nowcontains the WCCProxy service. Where you see ELMC in this document, the term is referring to the collectivecomponents of the ELMC kit, and where you see WCCProxy in this document, the term is referring to theWCCProxy service itself.

1.4.1 ELMC Version in WEBESThe following table shows the ELMC versions that have been packaged in WEBES up to this version.Table 1-1 ELMC Versions Packaged in WEBES

ELMC Version IncludedProduct

WCCProxy 6.1WEBES 6.1





1.5 WEBES Hardware RequirementsWEBES can be installed on the following hardware platforms:

• 32-bit Intel® based systems manufactured by HP, such as the ProLiant or the HP OpenView StorageManagement 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 doesnot 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 forthe 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 unsupportedplatform, the following error message will appear:"This installation package is not supported by this processor type. Contactyour product vendor."

To avoid receiving these errors, please ensure that you obtain the correct kit before installing WEBES.

12 General Information

http://h18023.www1.hp.com/support/svctools/webes/index.html


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 operatingsystem, the Itanium WEBES kit may install and operate correctly, but the Pentium WEBES kit can notbe installed.

See “WEBES Hardware Requirements” for the hardware that WEBES supports. Although WEBES can beinstalled on any of these hardware and operating system combinations, SEA only supports event bit-to-texttranslation 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 editionof this guide was published.

1.7.1 Kauai SupportKauai has the concept of multiple blades making up a system, known as co-joined blades. For entitlementof Kauai, there will be a clip on pipe attached to the front of the blade system and this is where the serialnumber will be located. All blades will use this serial number. There will only be one pipe no matter howmany blades there are.

1.7.2 ELMC No Longer Seen as a Separate PackageELMC 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.1PostgreSQL is an object-relational database management system. PostgreSQL 8.4.1 is embedded within theWEBES 6.1 installation kit. In WEBES 6.1 Postgres runs as a subprocess within WEBES and does not needany 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 orearlier versions and Postgres 8.3.7 installed with WEBES 5.6. These programs may have been installed onyour system during installation of a previous versions of WEBES, or by another application or user. See“Removing SQL Server” for details.

1.8 Installation KitThe WEBES Installation Kit is available at the HP Service Tools Website:http://www.hp.com/services/webes

1.9 UpgradesUpgrades can include anything from a major WEBES release to a minor kit with only rule updates or smallfunctional improvements. When upgrading you do not need to uninstall WEBES if your existing WEBESversion is within two releases. For example, when upgrading to WEBES 6.1 you do not need to uninstallyour 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

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

• 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 anexisting 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 andfunctioning in order to successfully migrate Managed Entity data.

14 General Information



2 Installing on Windows2.1 Pre-Installation2.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 productsuch as Norton SystemWorks. As such, only platforms manufactured by HP, such as the ProLiant, areofficially supported.Engineering normally expects that WEBES will operate correctly on any industry standard system basedon the Intel x86, EM64T, or an AMD architecture. However, because HP does not qualify WEBES onthird-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 andSettings\{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%\ProgramFiles\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 whenmapping 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, usagestays 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 extremelylarge log file is processed. Even then, the memory usage may remain significantly below the maximumvalue. The virtual memory requirement is intended to set a threshold for the absolute maximum amountof memory that will ever be needed. If the threshold is exceeded, the Director terminates without-of-memory error.Virtual memory for a process is stored in RAM and the page file on your disk. The space allocated mustbe 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 arefree 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/893803You can check the Windows Installer version by entering msiexec at the command prompt. (Ignorethe message about incorrect command line parameters.)

• TCP/IP services must be installed and running.

2.1 Pre-Installation 15

http://support.microsoft.com/kb/893803

2.1.2 SEA System RequirementsIn addition to the common WEBES prerequisites, your system must meet the following requirements toaccomodate 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 Advancedinstallation. This is for entitlement purposes, even though successful entitlement of the server is notnecessary to enable the separately entitled storage support.

• Web browser – Table 2-1 “Windows Browser Requirements” describes the browser prerequisites forSEA according to the following categories:Table 2-1 Windows Browser Requirements

BrowserCategory

Internet Explorer 7.0 and 8.0 (32-bit version only)Firefox 3.x

Supported (fully tested)

Internet Explorer 5.5As-Is (not officially tested but may work reasonably well)

Internet Explorer (any 64-bit edition)Internet Explorer earlier than 5.5Netscape earlier than 7.0Firefox earlier than 1.0

Unsupported (known not to work)

Web browsers can use different Java runtime environments, but the SEA User Interface requires certainversions 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 andolder.No Java is included in Internet Explorer on Windows Server 2003 and 2008, and Microsoft nolonger 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 mustdownload and install a Sun JRE.

A version may already be installed for your web browser. You can check the version by selectingTools → Web Development → Java Console. The Java version is given on the first line of the JavaConsole window.

NOTE: Install any desired web browsers before installing the Sun JRE. The JRE installation then findsand 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 enoughfor WEBES to process them in situations where large streams of events occur over a short period oftime. To do this, set the size of your Application Event Log to at least 4MB, in the Windows Event Viewerproperties 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 EventLogs. On x86 (Pentium) and x64 systems, SEA analyzes only the Application Event Log. This initial

16 Installing on Windows

http://java.sun.com/getjava

http://java.sun.com/getjava

analysis can result in high CPU usage over an extended period. To control this operation, you havetwo options:

• Archive and clean the Windows Event Log as described in “Archiving and Cleaning the WindowsEvent Log” before installing. This reduces the size of the log.

• Choose to delay the initial scan when prompted during installation. As a result SEA automaticanalysis 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 → InternetOptions → 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 PermissionsIn 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, ifyour user ID is a Domain Admin, and you have added Domain Admins to the Administrators group onthe local machine, then you have the necessary permissions.

To add Domain Admins to the local Administrator group, use the procedure for your operating system, forexample.Windows Server 2003: From a login account with administrator privileges, locate the user managementfunction under My Computer → Manage → Computer Management (Local) → System Tools → LocalUsers and Groups → Groups. Double click the Administrators Group, and press the Add button. HighlightDomain 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 youclean the log, stop the Director process before proceeding (see the WEBES Reference Guide for informationon 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. Open the event viewer.

Windows Server 2003 – Start → Programs → Administrative Tools → Event Viewer

2. For events analyzed by SEA:

▲ Right-click on the Application Log link in the left pane of the event viewer window.

3. Clear all events. Note that you are given the option to save the existing events to another file beforeclearing. (Saved logs can be analyzed at a later time.)

4. Close the event viewer.If WEBES was installed when you cleaned the log and you stopped the Director, you can now restart it usingthe procedure described in the WEBES Reference Guide.

2.1.5 Installing on Terminal ServersTerminal 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 consoleby 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. Youcan send clients a message about the time and duration of the installation and then disable all connectionsbefore 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. Log on to the Terminal server as an administrator and close all applications.2. Copy the WEBES kit to a local drive on the Terminal server.3. Install the program on a local NTFS formatted drive as with any other Windows WEBES installation.4. 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 EnvironmentVariables, 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 nowset for any command prompt windows opened after performing this workaround.

2.2 Installing WEBESThe 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 itwith the official final kit build of the same version, you must uninstall the existing WEBES installation beforeinstalling the final kit. Do not attempt to install the later kit without first uninstalling the earlier kit. Upgradesfrom one WEBES version to another version within two version numbers are supported, but you cannotupgrade from one build to another build of the same WEBES version. Do not save configuration data if youare going back to an earlier WEBES version, for example 5.2 to 5.1. The stored configuration data maynot be compatible with an earlier version.

After all Pre-Installation requirements are met, follow these steps to install WEBES:1. Log on using an account with administrator privileges.2. 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 beinstalled on x86 and x64 Pentium systems, but not an Itanium edition of Windows. See “WEBESOperating 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 notchoose 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. Read the license agreement, click the appropriate radio button if you accept it, and then click Next.5. Follow the on screen instructions.

a. Upgrading – If a WEBES version within two previous releases is present, the installer alerts youabout the other version and prompts you to upgrade. If this is a fresh WEBES installation, you willnot see this message. See “Upgrading WEBES” for details.

b. Installation Directory Path Selection – You can change the default directory path for your installationby clicking the Change button and browsing to an alternative installation directory. However, ifyou do this take note of your installation directory for future reference.

6. Enter WEBES user information.


Figure 2-2 Configuration Wizard - User Information

Table 2-2 WEBES Information Requested During Installation

NotesExampleQuestion

User Information

The primary user of WEBES on this system, or theperson that HP support should contact regarding issuesreported by WEBES.

Chris GreenUser Name

The company employing the primary WEBES user.XYZ CompanyCompany Name

The telephone voice contact number for the primaryWEBES user.

123-456-7890Phone Number

The e-mail address of the primary WEBES [email protected]

The server that handles SMTP e-mail at your site.mailsys.xyzcompany.comSMTP Mail Server

The serial number of the system upon which WEBES isbeing installed.

A01234567890System Serial Number

7. Enter profile and notification details

2.2 Installing WEBES 19

Figure 2-3 Configuration Wizard - Profile and Notification Details



Profile and Notification Information

The following information will be sent in WEBES problem report notifications.

The company using WEBES as a customer of HP. Bydefault, the Company name entered is entered in theUser Information window.

XYZ CompanyCustomer

The address of the primary WEBES user, or of thecompany site.

123, Main Street, Metropolis, VA 22222Address, City, ...

The primary contact person at the customer company'ssite for the system running WEBES. By default, the UserName is entered in the User Information window.

Chris GreenPrimary Contact

The person to contact at the customer company's site,if the Primary Contact person is unavailable.

Pat BrownSecondary Contact

The telephone voice contact number for the primarycontact. By default, the Phone Number is entered in theUser Information window.

123-456-7890Phone Number

Add details that will be useful to your service provider."Check with customer prior to dispatchingservices. Prior notification to security isnecessary for service access to site."

Special Instructions

8. Enter configuration details


Figure 2-4 Configuration Wizard - Configure WEBES



Configuration Information:


The product description, product number, or modelnumber of the system hardware unit on which WEBESwill be installed.

EVA5000System Type

The serial number of the system hardware unit.A01234567890System Serial Number

The TCP/IP hostname and fully qualified domain nameof the system on which WEBES will be installed. If thesystem has no hostname, the dotted decimal IP addressmay be entered.

server1.xyzcompany.comSystem name

Select Fixed for static IP addresses, or DHCP Served ifthe IP address of the system is assigned when the systemconnects to a DHCP server, usually on startup.

Fixed or DHCP ServerSystem IP Address

9. Validate the service obligation number of the system/subsystem


Figure 2-5 WEBES Service Obligation Validation



Service Obligation Validation:


The serial number of the system hardware unit. Bydefault, the System Serial Number is entered in theConfiguration window.

A01234567890System/Subsystem SerialNumber

Normally, the same as the serial number. Contact yourHP customer support representative to obtain yourservice obligation number as defined by your servicecontract.

A01234567890Service Obligation Number

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”.


Figure 2-6 Clean Binary Error Log

11. Click Install to begin the installation.

Figure 2-7 WEBES Installation Execution

12. You will know that the WEBES installation is completed when you see the following window:


Figure 2-8 WEBES Install Complete

When you click Finish, the window may not disappear for up to a minute (approx). WEBES is finishinginstallation tasks during this time and will close the window when the tasks are completed. ClickingFinish 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 Cleaningthe Windows Event Log”.

This section is applicable when you are upgrading to WEBES 6.1 from an existing version of WEBES thatis within 2 releases (versions) of this version of WEBES. For example, you can upgrade to WEBES 6.1 wheneither WEBES 6.0 or WEBES 5.6 is installed, but not if 5.5 or earlier is installed. If an upgrade is attemptedon a version of WEBES that is too old, you are told to uninstall the existing version, and the upgrade doesnot 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 olderversion of WEBES and installs the newer version—the upgrade does not simply patch or replace certainfiles, 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 informsyou that the older version was detected and prompts you about upgrading.If you answer Yes, the kit does the following:1. Saves configuration and state data to %SystemDrive%:\WebesBackup, where %SystemDrive%

is the drive where Windows (not necessarily WEBES) was installed.2. Uninstalls the existing installation.3. Installs this version with the same components such as SEA that were present before.


4. Restores the saved data.5. 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 uninstallthe existing WEBES copy yourself, but then not all data will be migrated upon installing the newer versionas described in “Installing WEBES”.

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

2.5 Uninstalling WEBESYou 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 completelyclose any WEBES components that are running.

2.5.1 Uninstalling on Terminal ServersFrom Console – Terminal Server system uninstallations should be performed from the Terminal Server consoleby 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. Youcan send clients a message about the time and duration of the uninstallation and then disable all connectionsbefore 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. Log on to the Terminal server as an administrator and close all applications.2. Uninstall the program as with any other Windows WEBES uninstallation.

2.6 Removing SQL ServerWEBES 6.1 does not require the use of Microsoft SQL Server 2005 or Postgres 8.3.7. This program mayhave been installed on your system during installation of a previous version of WEBES, or by anotherapplication or user. Neither the WEBES 5.6 uninstallation process nor the WEBES 6.1 upgrade processautomatically removes SQL Server, since other applications might be sharing this service. You can manuallyremove the WEBES-related part only, or you can manually remove all of the SQL-Server-related software inorder 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 theWEBESDB SQL Server instance (WEBESDB Database Engine). This instance may be removed without affectingother applications. It can be removed while WEBES 6.1 is running.1. From Windows Control Panel, run Add/Remove Programs.2. From the list of programs select Microsoft SQL Server 2005 and click the Remove button. (This does

not immediately remove SQL Server).3. Follow the prompts. Select WEBESDB: Database Engine for removal.4. 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 ofthis 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 removeSQL Server completely.1. From Windows Control Panel, run Add/Remove Programs.2. From the list of programs select Microsoft SQL Server 2005 and click the Change button. (This does

not immediately remove SQL Server).3. Follow the prompts. Select Remove SQL Server.4. 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 thisdata unless you are certain that it will never be needed. Even then, before deleting such data, it isrecommended to make a backup copy. By default, SQL Server data is located in the “Microsoft SQLServer” folder under the “Program Files” folder.


3WEBES User InterfaceThe WEBES user interface provides browser-based access to the Service Event Analyzer (SEA) functionalityof WEBES. You can use the WEBES user interface to connect to the Director on your local system or onremote 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 AnalyzerIt is not necessary to have the Director running on your system in order to use SEA. In fact, WEBES need notbe installed on the browser's system at all. However, WEBES must be installed and the Director must berunning 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: If you are logging into SEA from another system open a web browser and enter the followingURL:https://hostname where director is running:7906. Use the fully qualified host name orthe 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 tolog 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 InterfaceAfter 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 yourusername, 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 replacingthe 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

DescriptionComponent

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

By default, provides access to the online help, system configuration, processing statistics, WEBESmanaged entities configuration, WEBES notification settings and new binary error log creation. Thetoolbar is dynamically updated, and additional features are available with select SEA screens.

Toolbar

Displays any browser connectivity errors and any current WEBES configuration warnings. It willtypically indicate which aspects of configuration should be addressed first.

Applet Message Frame

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

Displays interactive screens and system information. When SEA loads, the display frame showsproduct information.

Display Frame

Displays messages from the browser and usage tips.Information Bar

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

3.2.1 ToolbarFigure 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 groupedby 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 areconfiguration 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


Opens a new browser window that reports the processing status of log files.Progress Window

Opens the New Binary Log screen in the display frame.New Binary Error Log Creation

Displays notification status.WEBES Notification Status

28 WEBES User Interface


Opens the RSC settings screen for configuring enterprise wide information for the Remote SupportClient.

NOTE: This icon and option only exists for customers who have also installed Insight RemoteSupport Standard.

Configure RSC Settings

Opens the SEA settings screen.Configure SEA Settings

Allows you to configure WEBES Managed Entities.Configure Managed Entities

Allows you to configure WEBES Managed ProtocolsConfigure Managed Protocols

Allows you to manage WEBES Managed sites.Configure WEBES ManagedSites

Allows you to configure WEBES Managed contacts.Configure WEBES ManagedContacts

Allows you to configure WEBES notifications including WEBES e-mail settings.Configure WEBES NotificationSettings

Opens a new browser window containing the online user guide.Help

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


Available when viewing automatic analysis details.Clear Results Button

Available when viewing manual analysis details. See Table 3-8 “Additional Toolbar Functions”,Reprocess File Button for more information.

Reprocess File Button

Available when viewing manual translation details. See Table 3-8 “Additional Toolbar Functions”,Analyze File Button for more information.

Analyze File Button

Available after processing a file with a filter applied. See Table 3-8 “Additional Toolbar Functions”,Analyze Filtered Events Button for more information.

Analyze Filtered Events Button

Available when viewing Real-Time Monitoring of a Tru64 UNIX or OpenVMS Alpha system. SeeTable 3-8 “Additional Toolbar Functions”, Get Current FRU Table Button for more information.

Get Current FRU Table Button

Available when viewing Real-Time Monitoring of a Storage Cell.Generate Storage SpreadsheetButton

Available when viewing Real-Time Monitoring of a Storage Cell. See Table 3-8 “Additional ToolbarFunctions”, Get Current Storage Cell Configuration Button for more information.

Get Current Storage CellConfiguration Button

3.2.2 NavigationUsing SEA, it is possible to monitor the binary event log files generated by a wide variety of computers allfrom 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, categoriesand binary event log files.

3.2.2.1 Navigation Tree HierarchyThe entries in the navigation tree are as follows:

3.2 Using The WEBES User Interface 29

Figure 3-4 Navigation Tree - Hierarchy

Table 3-4 Navigation Tree - Hierarchy

DescriptionFolder

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

Individual computer systems that must also be defined as Managed Entities. Each node has one ormore event sources associated with it, such as System Log, Web-Based Enterprise Management(WBEM), or Other Logs.

Nodes

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

System Log

Automatic analysis results.Real Time Monitoring

Manual analysis results for the system event log.Full View

Any other binary event log files saved on the computer. These can include old files, files from othersystems, and examples. Optionally, the other logs can be further divided by categories

NOTE: Other logs may not appear with the tree when connecting to older versions of WCCProxy.

Other Logs

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

Storage Cells

A WBEM Common Information Model Object Manager (CIMOM) which sends WBEM indicationsto WEBES (when WEBES has successfully registered with the CIMOM). By default a WBEM foldercontains Real Time Monitoring.

WBEM

3.2.2.2 Features of the Navigation TreeFigure 3-5 “Navigation Tree - Collapsed” and Figure 3-6 “Navigation Tree - Expanded” describe the featuresand functions of the navigation tree.

Figure 3-5 Navigation Tree - Collapsed


Figure 3-6 Navigation Tree - Expanded

Table 3-5 Navigation Tree - Features

DescriptionFeature

In most browsers, the currently selected entry in the Navigation Tree is highlighted(Figure 3-5 “Navigation Tree - Collapsed”).

Current Selection is Highlighted

The tree structure can be collapsed to the group level (Figure 3-5 “Navigation Tree - Collapsed”).Collapsing Navigation

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

Expanding Navigation

Each entry in the tree has a name and an icon that indicates its type. For example, inFigure 3-6 “Navigation Tree - Expanded” you can tell that the jarjar.cxo.dec.com node isinactive because of its icon.

Icons

You can customize the navigation tree by adding and removing groups, nodes, categories, andbinary event log files.

NOTE: Storage cells are generated automatically and cannot be customized by the user.

Customizing the NavigationTree

You can view and update the Managed Entity configuration data for a Node in the NavigationTree.

Viewing Managed EntityConfiguration

You can view the results of automatic analysis and initiate manual analysis from the navigation tree.Viewing Results

If you modify the entries in the navigation tree, you may need to refresh the display so your changesappear. To refresh the navigation tree, click the Refresh Tree button.

Refreshing Navigation

3.2.2.3 Navigation Tree IconsTable 3-6 Navigation Tree Icons

DescriptionIcon

SEARoot node of the Navigation Tree

Refresh tree buttonButton 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.


DescriptionIcon

Managed Entity node needs info.Indicates an active Managed Entity that requires user attention – probably needs additionalconfiguration 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, eitherbecause 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


DescriptionIcon

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 linksNodes at most levels of the Navigation tree have active links which display context sensitive information inthe right hand pane when selected. The exception to the rule is an Entity node that is attempting to connectto the designated Managed Entity.

3.2.2.4.1 SEA link

3.2.2.4.2 Group linkThe 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 currentGroup, or removal of Managed Entity Nodes from the current Group, using the tabs at the bottom of thepage.


3.2.2.4.3 Entity linkThe Entity Node level tree node displays the Configuration page for the selected Managed Entity – this isthe 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 highlightedin yellow (or other user selected color) when selected.

3.2.2.4.4 System LogDisplays the same information as Real Time Monitoring.

3.2.2.4.5 Real Time MonitoringWhen selected, the Real Time Monitoring tree node displays the current Problem Reports, raw Events, andconfiguration collections resulting from automatic analysis of the current Managed Entity.


3.2.2.4.6 Full ViewWhen selected, the Full View tree node invokes manual analysis of the system log of the current ManagedEntity. The main pane shows the current status of the manual analysis as it is performed, and the resultingProblem reports, event Summary, and raw Events when complete.


3.2.2.4.7 Other LogsThe Other Logs tree node displays the Log File Maintenance page when selected. This allows for the additionor removal of log files using the tabs at the bottom of the page. These files can then be selected to havemanual analysis run against their contents.

3.2.2.4.8 Other Logs fileThe individual files listed under the Other Logs tree node can be selected to have manual analysis runagainst their contents. The main pane shows the current status of the manual analysis as it is performed, andthe resulting Problem reports, event Summary, and raw Events when complete.


3.2.2.4.9 WBEMDisplays the same as Real Time Monitoring.


3.2.3 Applet MessagesThe Toolbar contains a short message pane which displays messages indicating potential issues with theoperational status of WEBES. Errors are color coded in red while warnings are color coded in amber. Thesemessages are not a definitive statement of the current status, but when present these messages give hintsand guidance as to which aspect of WEBES may need attention.

Table 3-7 Applet Messages

DescriptionMessage

The WUI cannot connect to the Director. Any information displayed in the WUI is likely to be stale.Lost Connection to Director!

An unknown error has occurred which is preventing proper connection to the Director.Connection error!

No Managed Sites are configured. You should normally have at least one Managed Site configured.Warning: No sites configured

No Managed Contacts are configured. You should normally have at least a primary contact foreach Managed Entity that is being monitored.

Warning: No contactsconfigured

No Notifications are configured so WEBES cannot report any problems it may find with a ManagedEntity.

Warning: No notificationsconfigured

One or more Managed Sites need additional configuration information to be entered.Warning: Site needs info

One or more Managed Contacts need additional configuration information to be entered.Warning: Contact needs info

One or more Managed Entities need additional configuration information to be entered.Warning: Entity needs info

Email settings have not been configured correctly.Warning: Email settings notconfigured

Only one message can be displayed at a time. When multiple issues are detected, the applet will displaythe message that is likely to be most important to fix first. When that issue is fixed, the next most importantmessage will be displayed, and so on until there are no outstanding messages to display.

3.3 Customizing the Navigation TreeThe first time you run the web interface using your profile, only the local node and the Default Group appearon the navigation tree.You can customize the navigation tree display by creating new groups, adding nodes to groups, and selectinglog files.After you submit changes to the navigation tree, SEA refreshes the display. The refresh process may take afew seconds.

3.3.1 GroupsFrom the navigation tree, you can create new groups and remove existing groups.

3.3.1.1 Adding GroupsTo 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 thenavigation tree relative to existing groups. By default, new groups are added after the selected group.

2. Select an existing group from the list.3. Select a placement option from the radio buttons.4. Enter the name for the new group in the text field. Be sure to follow these rules for naming groups:

• Group names should be unique. If you enter a group name that is already in the navigation treeat the same level, SEA will not create the new group.

• Group names should not use punctuation characters. These characters can cause JavaScript errorsin the web interface.

• Group names should be descriptive. If you leave this field blank, the group is named "newGroup"by default.

5. Click the Add New Group button.The new group appears in the navigation tree.

3.3.1.2 Removing GroupsRemoving a group removes all the nodes and files contained in the group as well as all of the lower levelgroups nested under it.To remove existing groups, follow these steps:1. Click the System Event Analyzer link at the top to the navigation tree.2. Select the Remove Groups tab at the bottom of the "Group Maintenance..." screen (Figure 3-8 “Remove

Group”).

3.3 Customizing the Navigation Tree 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, pressSHIFT 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 NodesExpanding a group in the navigation tree displays the nodes contained in that group. Nodes can be expandedby clicking on the expansion symbol next to their name to reveal the log file types or storage cells includedin that node. You can add and remove nodes from the groups in the navigation tree.

3.3.2.1 Adding NodesAny computer where the WCCProxy is running can be added to your web interface navigation tree as anode. 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 AddNodes tab is already selected.


Figure 3-9 Add Node

The location and placement options determine where you would like the new node to appear in thenavigation tree relative to existing nodes. By default, new nodes are added after the selected node.

2. Select the existing managed entity from the drop-down list.3. Select where in the tree the new node will be placed.4. Select a placement option using the radio buttons.5. Click the Add New Node button.

The new node appears under its group in the navigation tree.

3.3.2.2 Removing NodesRemoving a node removes all the additional data contained in the node from the navigation tree.To remove existing nodes, follow these steps:1. Select the group you want to remove nodes from in the navigation tree.2. Select the Remove Nodes tab at the bottom of the screen (Figure 3-10 “Remove Node”).


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 SHIFTand 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 NodesA new animated icon is displayed when node activation is in progress. Nodes are either active or inactiveand by default when you connect to a node or load a profile that connects to other nodes, all the nodes areactive. A node is only classified as inactive if SEA cannot connect to it. Inactive nodes appear in the navigationtree with a red "X" through their icon.Node activation is based on successful communication with WCCProxy. If a node is inactive, you can notactivate the node manually.However, while activating the node, the icon will animate in several stages as shown in the following figurewhen the connection and handshaking is in progress:

Figure 3-11 Activating Node

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


If the Director is not accessible, a message appears in the display frame (Figure 3-13 “Unable to ActivateNode Message”) and the navigation tree is not changed.

Figure 3-13 Unable to Activate Node Message

3.3.3 CategoriesCategories are an optional feature that is disabled by default. If you want to use categories, you must enablethe 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 usecategories, SEA provides another layer of folders under the Other Logs folder. This feature may be usefulif you monitor numerous log files.

3.3.3.1 Adding CategoriesOnce you have enabled the categories feature, you can add categories to the navigation tree. To addcategories, 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”). TheAdd 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 thenavigation tree relative to existing categories. By default, new categories are added after the selectedcategory.If no categories currently exist for the group, skip Step 2 and Step 3.

2. Select an existing category from the list.3. Select a placement option from the radio buttons.


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 notcreate the new category.

• Category names should not use punctuation characters. These characters can cause JavaScripterrors 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 CategoriesRemoving a category removes all the binary event log files contained in the category from the navigationtree.To remove existing categories, follow these steps:1. Select the Other Logs folder for the node you want to remove categories from in the navigation tree.2. 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 SourcesEach Entity Node is associated with one source of real time events, and may also be associated with a setof event log files which are available for manual analysis. The source of real time events is dependent onthe type of Managed Entity that the node represents, for example, a WBEM CIMOM is the source of eventinformation (called Indications in relation to WBEM communications) for WBEM servers and the System Logcurrently provides event information for other types of servers."


3.3.4.1 System LogThe 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 ofevents 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'ssystem 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 andmanual 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 beconfused 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 expansionsymbol 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 ofevents 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'ssystem 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 symbolto 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 ofevents 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'ssystem log file that apply to WBEM node.

3.3.4.2 WBEMThe WBEM CIMOM is the source of WBEM Indications (event information) for systems/servers that supportWBEM 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 witha WBEM entry:

▲ Real Time Monitoring – shows the results of automatic analysis in the display frame.

3.3.4.3 Other LogsThe Other Logs folder in the navigation tree contains entries for binary event log files other than the systemevent log. These can include the example binary log files included with SEA, or any other binary event logfile 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 categoryfolders 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. Fora 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 adifferent 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 itssubdirectories, or one of the directories you configured in the CA.WUI.OLDirs key in the DESTAregistry. 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


Files stored in these subdirectories are automatically backed up and saved if you uninstall, reinstall, orupgrade WEBES. For more information on storing user data, see the WEBES Installation, Configuration, andUsage Guide.If you want to store files elsewhere, you can configure WEBES by adding a comma separated list of filepaths 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 theOther Logs list by entering the path and filename of an event log located anywhere in the file system.Adding Other LogsFollow 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 OtherLogs link for the node.The Other Logs screen opens in the display frame (Figure 3-16 “Add Log Files Tab”). The Add Filestab 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. (Optional) If enabled, enter the path and filename in the text field.4. Click the Add button.

The binary event log file is added to the navigation tree under the Other Logs entry or appropriatecategory for the node.

Removing Other LogsTo 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 OtherLogs link for the node.

2. Select the Remove Files tab from the bottom of the screen (Figure 3-17 “Remove Log File Tab”).


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 SHIFTand 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 EventsWEBES continually performs automatic translation and analysis of events for every Managed Entity as abackground activity. You can initiate manual translation and/or analysis of log files, and view the currentstatus and results of automatic and manual analysis jobs for a given Managed Entity by using the followingmethods:

• Selecting System Log, WBEM, or Real Time Monitoring displays the recent results of automatic analysisfor 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 ReplaceableUnits (FRU) are reported by the Logical Unit Number (LUN) to which they belong, in addition to the existinginformation. 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 theconfiguration entry. The number of the partition that logged the configuration entry is accessible when it ispresent 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 CELL #

----------- ------

0 0

1 2, 3

2 1

1 0x4 0 DIMM # Size DIMM # Size

------ ----------- ------ -----------

0A 2048 MB 0B 2048 MB

1A 2048 MB 1B 2048 MB

2A 2048 MB 2B 2048 MB

3A 2048 MB 3B 2048 MB

4A 2048 MB 4B 2048 MB

5A 2048 MB 5B 2048 MB

6A 2048 MB 6B 2048 MB

7A 2048 MB 7B 2048 MB

8A -- 8B --

9A -- 9B --

10A -- 10B --

11A -- 11B --

12A -- 12B --

13A -- 13B --

14A -- 14B --

15A -- 15B --

32 GB Total Memory


------ ----------- ------ -----------

0A 2048 MB 0B 2048 MB

1A 2048 MB 1B 2048 MB

2A 2048 MB 2B 2048 MB

3A 2048 MB 3B 2048 MB

4A 2048 MB 4B 2048 MB

5A 2048 MB 5B 2048 MB

6A 2048 MB 6B 2048 MB

7A 2048 MB 7B 2048 MB

8A -- 8B --

9A -- 9B --

10A -- 10B --

11A -- 11B --

12A -- 12B --

13A -- 13B --

14A -- 14B --

15A -- 15B --

32 GB Total Memory


------ ----------- ------ -----------

0A 2048 MB 0B 2048 MB


1A 2048 MB 1B 2048 MB

2A 2048 MB 2B 2048 MB

3A 2048 MB 3B 2048 MB

4A 2048 MB 4B 2048 MB

5A 2048 MB 5B 2048 MB

6A 2048 MB 6B 2048 MB

7A 2048 MB 7B 2048 MB

8A -- 8B --

9A -- 9B --

10A -- 10B --

11A -- 11B --

12A -- 12B --

13A -- 13B --

14A -- 14B --

15A -- 15B --

32 GB Total Memory


------ ----------- ------ -----------

0A 2048 MB 0B 2048 MB

1A 2048 MB 1B 2048 MB

2A 2048 MB 2B 2048 MB

3A 2048 MB 3B 2048 MB

4A 2048 MB 4B 2048 MB

5A 2048 MB 5B 2048 MB

6A 2048 MB 6B 2048 MB

7A 2048 MB 7B 2048 MB

8A -- 8B --

9A -- 9B --

10A -- 10B --

11A -- 11B --

12A -- 12B --

13A -- 13B --

14A -- 14B --

15A -- 15B --

32 GB Total Memory

Viewing Analysis ProgressYou can view the current status of any automatic or manual analysis job by clicking on the Progress Windowbutton in the toolbar to open a new window that displays all the queued and running analysis jobs, andevent counts for each job.Whenever manual analysis is invoked for a log file, an animated icon is used to reflect the running statusof the manual analysis job; when analysis of the log file is complete, the icon in the navigation tree changesto 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 windowdisplays progress for that file.The data in the progress is not displayed in real time. There may be coupleseconds difference in the actual progress and what is displayed in the progress window.

Viewing ResultsThe results of automatic and manual analysis are shown in the display frame when an appropriate selectionis made in the navigation tree. Some or all of the following information is available, depending on the typeof 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 availablewith manual analysis)


• 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 thantranslation and analysis, the Problem Reports tab is empty.

Analysis FailedIf the file cannot be processed for any reason, a message similar to the one in Figure 3-18 “Analysis FailedMessage” is shown.

Figure 3-18 Analysis Failed Message

3.4.1 Additional Toolbar FunctionsSEA provides additional functionality depending on the type of processing you are performing.Table 3-8 Additional Toolbar Functions

DescriptionWhen Does It Appear in the Toolbar?NameButton

The Clear button removes all the entries(problem reports and events) from thedisplay tabs.

When you are performing or viewingAutomatic Analysis.

Clear Results Button

The Reprocess button forces SEA todiscard the previous analysis results andreprocess the selected binary log file.

When you are performing ManualAnalysis.

Reprocess File Button

Clicking the Analyze button will performanalysis for the current log file. Thus, ifyou need to perform analysis, it is notnecessary to change the User Settingsand reprocess the file.

When the User Settings are configuredto perform only manual translation bydefault.

Analyze File Button

Clicking the Analyze Filtered eventbutton allows you to repeat the analysisusing only the events that met the filtercriteria.

When you use a filter for processing alog file.

Analyze Filtered Events Button

Clicking the FRU button reads thecurrent Field Replaceable Unit (FRU)hardware configuration table from thenode's in-memory table and adds thetable as an entry to the ConfigurationEntries tab.

When you are performing or viewingAutomatic Analysis on a Tru64 UNIXor OpenVMS Alpha node.

Get Current FRU Table Button

The Get Current Storage CellConfiguration button adds an entry tothe Configuration Entries tab for theselected storage cell, detailing thehardware configuration of the storagecell.

When you are performing AutomaticAnalysis of a Storage Cell.

Get Current Storage Cell ConfigurationButton

3.4.2 Processing StatusWith large log files, translation and analysis operations are not instantaneous. After you have startedprocessing a log file there are several ways to check the operations progress. You can check the processingstatus from either the navigation tree or the Progress window.

3.4.2.1 Navigation TreeYou can quickly determine the status of automatic or manual analysis by looking at the icons in the navigationtree. Figure 3-19 “Status Icons” shows the icons used to indicate analysis results.


Figure 3-19 Status Icons

When automatic analysis generates a problem report, exclamation points are added to the icons for thenode, system log, and real time monitoring. The icon remains changed until problem report details areviewed and the tree is refreshed. If another problem report is generated after the tree is refreshed, exclamationpoints 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. SEAuses a animated yellow icon when a binary log file is being read and an animated green icon duringanalysis. If processing has completed and problem reports were generated, an exclamation point is addedto the icon. Otherwise a check mark is added to the icon. Unlike the icon changes associated with automaticanalysis, the manual analysis icon changes remain visible until you close the web interface session.

NOTE: If you are only performing translation, when processing completes the icon will appear with adash.

3.4.2.2 Progress WindowYou can open the Progress window by clicking on the Progress Window button in the toolbar (seeFigure 3-3 “Toolbar”).The Progress window opens in a new browser window (Figure 3-20 “Progress Window”).

Figure 3-20 Progress Window


The Progress window provides statistics for all the log files that are currently being analyzed by SEA, includingautomatic 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 windowdisplays progress for that file.The data in the progress is not displayed in real time. There may be coupleseconds 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 processingchanges. 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 iconin the upper left hand corner. To stop processing an active manual job, click on the Stop icon.

3.4.3 Working With ResultsAfter processing, the results of analysis are shown on the tabs in the display frame (Figure 3-21 “AdditionalEntries 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.

NOTE: You can control the number of entries shown in a tab with the options in the User Settings window.

3.4.3.1 Problem ReportsThe Problem Reports tab displays a list of the reports that were generated by analysis. An example of theproblem report list is shown in Figure 3-22 “Problem Report Tab”.

Figure 3-22 Problem Report Tab


The filters used when generating the problem reports are listed at the top of the screen. However, the displayonly 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 SummaryThe Summary tab is only available when you perform manual analysis. If you select Real Time Monitoringfrom 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 eventlog 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 eventsare 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 filtersthat apply to the summary report and may not list all the filters you selected.

3.4.3.3 Sub Type Tallied Summaries and Event ListingsCertain types of events have subtypes which can be further summarized and listed by Sub Type. As of theWEBES 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 classifiedbased on the nature of the event. As of the WEBES 4.5 release, there is no color classification for the SubType events of event type 199 (CAM events). All the Sub Type events of event type 199 will appear in graycolor. The colors of the event description signify the following about their nature.Table 3-9 Event Type Color Codes

Nature of the EventColor

Significant eventsRed

Configuration events, and return to normal status from a previous failureGreen

EVA Reboot/Resync/Restart etcBlue

Data Availability, CA, Customer attention neededDark Orange

Drive firmware update eventsMagenta

Threshold eventsPurple

To view the Sub Type event summary information, select the summary tab in the Web interface for any binaryevent log. This will show you the classification of the event types. If the event summary has event type 14009or 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. Thefollowing screen shows the listing of all the Sub Type events of event type 14009:

Figure 3-25 Sub-Type Listing

3.4.3.4 EventsThe Events tab shows a list of the events contained in the binary event log file. Depending on the filteringoptions that were applied during processing, all the events in the log file may or may not be shown(Figure 3-26 “Events Tab”).


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 showsthe 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 ResultsYou can sort the results of analysis using either the column headings on the tabs in the display frame, or byusing a filter.Sorting with Column Headings

• Sorting with the column headings only impacts the entries currently shown. Therefore, if there are toomany entries to be listed on a tab, the column headings will only sort the entries that are displayedrather than all the output produced by processing the log file. In most cases, this limitation only impactsthe Events tab.

• You can sort the results shown on any tab using the field names that appear in blue (i.e., as hypertextlinks). Click on the field name to sort based on that field. An arrow appears next to the field to indicatethe direction of the sorting. The sorting options are applied to all the tabs, regardless of which tab wasused to specify the sorting criteria.

• Entries can be sorted in either ascending or descending order. To change the sort order, click on thefield 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, itindicates 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 howmany screens are required to show all the entries.

3.4.3.6 Displaying DetailsThe Problem Reports tab lists the reports generated by analysis and the Events tab lists the events in thebinary log. You can view the details of a problem report or the translated text of an event by clicking on anentry in the list. Depending on the User Settings selected, the details will either be shown in the displaywindow 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 “NavigationButtons—Problem Reports” and Figure 3-28 “Navigation Buttons—Events”.


Figure 3-27 Navigation Buttons—Problem Reports

Figure 3-28 Navigation Buttons—Events

The buttons are used to move between entries in the list.

• You can view the details for other events in the list using the Previous and Next buttons.When paging between entries, the column heading sort order always reverts back to the Index columnin 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 notavailable. 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 ProtocolsThis 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 toaccess and retrieve event data from your managed entities. After the appropriate protocol information isconfigured, you can then apply those protocols to each managed entity as needed.

3.5.1 Add New ProtocolTo 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: To edit the credential information for an existing or default protocol, just click the protocolname.

2. Click the New button to create a new protocol. The Managed Protocol Type screen will open.


3. Enter a name for your protocol and select the protocol type from the drop-down list. You can create asmany protocols as you have varied credentials for you managed entities. If each of your managedentities has unique usernames and passwords, then create a protocol for each set of credentialsappropriate to the communication method used by that managed entity. The following Managed Protocoltypes 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 examplesshow protocol details for various protocol types. Provide the credential information for the protocol typeyou 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 EntitiesThis 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 Entitypage. Figure 3-33 “Managed Entities” shows the list of all the devices managed by this node. Some WEBESnodes may manage many devices, some of which require configuration information. To view only thosedevices, click the View filtered list button.


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 importantto 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 anasterisk indicating that further configuration information is required.To remove the managed devices, check the device name and click the Delete button. Click Select All andthen click Delete to delete all the managed devices.To view the details of a managed entity, click on the particular managed entity (for example, CommandView EVA Server) which lists out the managed entity details as shown in Figure 3-34 “Managed EntityDetail”.

3.6 Managed Entities 59

Figure 3-34 Managed Entity Detail

Specific fields may vary according to the type of managed entity – the example shows the detailed fieldsfor a Command View EVA Server.

NOTE: WEBES requires a fully qualified domain name (FQDN) or an IP address to be provided in thefollowing 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 Contactor enter new contact names by clicking Go To Contacts button and filling the required information. TheRefresh 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 displayedon the Managed Entity Detail screen. You can enable and disable protocols for each Managed Entity byusing the corresponding drop-down list.

3.6.1 Adding a Managed EntityIf you need to add a managed entity:


1. Click the New button on the Managed Entities screen.2. 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 InformationTwo additional buttons are available to advanced users in the web-based interface at the bottom of theManaged Entities page. The Export button allows you to export details for a WEBES system's managedentities, contacts, and sites to an XML file that can be subsequently imported by another (or the same) WEBESsystem 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), contactdetails, and site information associated with a WEBES node, click the Export button. A popup ExportManaged Entities page provides details of the information that has been exported (see Figure 3-36 “ExportManaged Entities popup”) and details of where the XML files have been saved.

3.6 Managed Entities 61

Figure 3-36 Export Managed Entities popup

To import previously exported WEBES information, click the Import button. WEBES checks for relevant XMLfiles in particular folders and a popup Import Managed Entities page is displayed that displays details ofthe entities, contacts, and sites that may have been imported. Access details for each imported entity mustthen be manually configured.

3.7 Getting HelpThe WEBES user interface provides usage tips and a link to documentation

3.7.1 Usage TipsPosition the cursor of your mouse over an element from the toolbar or navigation tree to view a brief descriptionof the option in the information bar at the bottom of the browser.

3.7.2 WEBES DocumentationClick on the Help button from the toolbar to view the current WEBES documentation which is located athttp://h18023.www1.hp.com/support/svctools/webes/index.html

3.8 WEBES User Interface - Advanced FunctionsThe following advanced functions are described in detail in the WEBES Reference Guide.

• Creating New Log Files

• Applying Filters

• Modifying Settings

• Logging Off

• Service Obligation

NOTE: Not every user will need to utilize these functions when working with WEBES.



4 Automatic NotificationsThis chapter describes how SEA can automatically notify you or HP Services whenever automatic analysishas 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 beenautomatically detected on the system.Problem reports generated by manual analysis do not trigger any kind of automatic notification.

4.2 Web Interface Notification Settings PageOn the Web interface main screen, you can navigate to the Notification Settings page by clicking on itstoolbar 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 (onor off). To view or update additional settings, where available, you can click the link from the Setting columnto 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 thisexample, the user has enabled notification of problem reports from WEBES to HP SIM, but the HP SIMsoftware product has not been installed on the same system that WEBES is installed on. In this case, HP SIMnotification 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 toverify that notifications are working as expected, because the test event will be recognized, analyzed, andnotifications sent for all enabled notification types. Clicking the Test Event button is equivalent to issuingthe CLI command "wsea test".

4.1 When Are Notifications Sent? 63

4.3 Web Interface Notification Status and Dispatch PageOn the Web interface main screen, you can navigate to the Notification Status and Dispatch page by clickingon its toolbar button (yellow triangle with a red question mark, within the icon that also contains a displayand 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 (problemreport) was successfully delivered to the SMTP (email) and LOG (prob.log file) notifications in Januaryand February, but the one in February was not able to be delivered to HP SIM, and is still in transit (notificationbeing 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 notificationssucceeded or failed.Also regardless of which notifications succeeded or failed, you can choose to explicitly and immediatelydispatch any problem report to any desired notification type, even if you have not enabled that notificationtype.To dispatch a problem report, click the Dispatch tab at the bottom of this page. The page will look similarto 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 thestandard 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 theStep 2 list, using the standard Shift-click and Ctrl-click for multiple selections. Click the Send Notificationsbutton 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 previousscreen). Using the standard Shift-click and Ctrl-click for multiple selections, select the problem reports youwish to remove, in the Step 1 list, and click the Remove Problem Reports From Notification Historybutton. You will no longer be able to see the notification status, the content of the problem report, or dispatchit to a notification type, after you click this button.

4.4 Service Events vs. Info EventsSEA automatic analysis detects and reports on two kinds of events:

4.4.1 Service EventsService Events usually require the attention of HP Services, such as when an FRU has failed and must bereplaced.Provided that you have both types of notification enabled, SEA always sends service event problem reportsboth as emails to you and as secure transmissions to HP Services.

4.5 Informational EventsInfo events generally require the attention of the local system administrator, such as when a disk is runningout 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 serviceoffering enabled.Even though SEA does not log a call to HP Services, you may decide to place your own customer-initiatedcall 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 AddressesSEA notifies you about events by automatically sending SMTP email copies of problem reports to the addressesyou specify. Although there are no restrictions on what addresses you can list, you probably do not want tosend 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 beyondthe scope of this manual, so see the given operating system documentation if you need help in this area.

4.6.1 SettingsDuring 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 theusername or the domain, or both. Some servers return errors where others silently discard the email if it doesnot 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 beingdelivered.If WEBES is connected to HP SIM, then the SMTP server name and port, and the sender's email addresssupplied by SIM overrides the local WEBES value for these settings. The email recipients are the union ofthe 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 thedomain 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 = [email protected]

4.6.1.1 Web Interface Email Settings PageThe 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 NotificationSettings Page”) and then click the Email notification link to display the WEBES Email Settings page (seeFigure 4-4 “E-mail Settings”).

Figure 4-4 E-mail Settings

Multiple email addresses may be entered in the Recipients and CC fields—use a semi-colon between eachemail address.

66 Automatic Notifications

If HP SIM is connected, then the SMTP server name and port, and the "from email address" fields cannotbe changed. They automatically revert to the HP SIM supplied values as soon as the Apply Changes buttonis pressed.The Test Email button generates a test email which is sent using the latest applied email settings. WEBESwill attempt to send the test email directly to the nominated SMTP server—it does not rely on WEBESnotification and it will not appear in any Problem Report displays. A results page is displayed when the testemail has been sent. To validate the SMTP settings, check that all nominated recipients and CC addresseeshave 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 toverify that notifications are working as expected, because the test event will be recognized, analyzed, andnotifications sent for all enabled notification types. Using the Test Event button is equivalent to issuing theCLI command wsea test.

4.6 Sending Notifications to Email Addresses 67