Professional Documents
Culture Documents
1
Installation, Configuration, and Usage Guide
Copyright 1999 - 2010 Hewlett-Packard Development Company, L.P. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.21 and 12.212, Commercial 1 Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgments Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. UNIX is a registered trademark of The Open Group. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Java is a U.S. trademark of Sun Microsystems, Inc.
Table of Contents
About This Document.....................................................................................9
1 2 3 4 Intended Audience...............................................................................................................................9 Publishing History................................................................................................................................9 Typographic Conventions......................................................................................................................9 Related Documents...............................................................................................................................9
1 General Information..................................................................................11
1.1 What is WEBES?.............................................................................................................................11 1.2 What is the System Event Analyzer?...................................................................................................11 1.3 What is the Director?.......................................................................................................................11 1.3.1 SEA and the Director................................................................................................................11 1.4 ELMC.............................................................................................................................................12 1.4.1 ELMC Version in WEBES...........................................................................................................12 1.5 WEBES Hardware Requirements........................................................................................................12 1.6 WEBES Operating System Requirements.............................................................................................12 1.7 What is New in this Release?............................................................................................................13 1.7.1 Kauai Support..........................................................................................................................13 1.7.2 ELMC No Longer Seen as a Separate Package............................................................................13 1.7.3 PostgreSQL 8.4.1 Included in WEBES 6.1....................................................................................13 1.8 Installation Kit.................................................................................................................................13 1.9 Upgrades.......................................................................................................................................13
2 Installing on Windows..............................................................................15
2.1 Pre-Installation.................................................................................................................................15 2.1.1 WEBES System Requirements......................................................................................................15 2.1.2 SEA System Requirements..........................................................................................................16 2.1.3 Permissions..............................................................................................................................17 2.1.4 Archiving and Cleaning the Windows Event Log..........................................................................17 2.1.5 Installing on Terminal Servers.....................................................................................................17 2.2 Installing WEBES.............................................................................................................................18 2.3 Upgrading WEBES..........................................................................................................................24 2.4 Downgrading WEBES......................................................................................................................25 2.5 Uninstalling WEBES.........................................................................................................................25 2.5.1 Uninstalling on Terminal Servers................................................................................................25 2.6 Removing SQL Server......................................................................................................................25 2.6.1 Remove WEBESDB SQL Server Only (Recommended)...................................................................25 2.6.2 Remove Entire SQL Server (Not Recommended)...........................................................................25
3.2.2.4.6 Full View................................................................................................................35 3.2.2.4.7 Other Logs.............................................................................................................36 3.2.2.4.8 Other Logs file........................................................................................................36 3.2.2.4.9 WBEM..................................................................................................................37 3.2.3 Applet Messages....................................................................................................................38 3.3 Customizing the Navigation Tree.......................................................................................................38 3.3.1 Groups...................................................................................................................................38 3.3.1.1 Adding Groups................................................................................................................38 3.3.1.2 Removing Groups.............................................................................................................39 3.3.2 Nodes...................................................................................................................................40 3.3.2.1 Adding Nodes................................................................................................................40 3.3.2.2 Removing Nodes.............................................................................................................41 3.3.2.3 Activating Nodes............................................................................................................42 3.3.3 Categories.............................................................................................................................43 3.3.3.1 Adding Categories..........................................................................................................43 3.3.3.2 Removing Categories.......................................................................................................44 3.3.4 Event Sources.........................................................................................................................44 3.3.4.1 System Log.....................................................................................................................45 3.3.4.2 WBEM..........................................................................................................................45 3.3.4.3 Other Logs.....................................................................................................................45 3.4 Processing Events............................................................................................................................47 3.4.1 Additional Toolbar Functions.....................................................................................................50 3.4.2 Processing Status....................................................................................................................50 3.4.2.1 Navigation Tree..............................................................................................................50 3.4.2.2 Progress Window...........................................................................................................51 3.4.3 Working With Results..............................................................................................................52 3.4.3.1 Problem Reports..............................................................................................................52 3.4.3.2 Summary.......................................................................................................................53 3.4.3.3 Sub Type Tallied Summaries and Event Listings....................................................................53 3.4.3.4 Events............................................................................................................................54 3.4.3.5 Sorting Results................................................................................................................55 3.4.3.6 Displaying Details...........................................................................................................55 3.5 Managed Protocols.........................................................................................................................56 3.5.1 Add New Protocol...................................................................................................................56 3.6 Managed Entities............................................................................................................................58 3.6.1 Adding a Managed Entity........................................................................................................60 3.6.2 Exporting Managed Entity Information.......................................................................................61 3.7 Getting Help..................................................................................................................................62 3.7.1 Usage Tips..............................................................................................................................62 3.7.2 WEBES Documentation............................................................................................................62 3.8 WEBES User Interface - Advanced Functions.......................................................................................62
4 Automatic Notifications.............................................................................63
4.1 When Are Notifications Sent?...........................................................................................................63 4.2 Web Interface Notification Settings Page...........................................................................................63 4.3 Web Interface Notification Status and Dispatch Page...........................................................................64 4.4 Service Events vs. Info Events............................................................................................................65 4.4.1 Service Events.........................................................................................................................65 4.5 Informational Events........................................................................................................................65 4.6 Sending Notifications to Email Addresses...........................................................................................65 4.6.1 Settings..................................................................................................................................65 4.6.1.1 Web Interface Email Settings Page.....................................................................................66
Table of Contents
List of Figures
2-1 2-2 2-3 2-4 2-5 2-6 2-7 2-8 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 3-9 3-10 3-1 1 3-12 3-13 3-14 3-15 3-16 3-17 3-18 3-19 3-20 3-21 3-22 3-23 3-24 3-25 3-26 3-27 3-28 3-29 3-30 3-31 3-32 3-33 3-34 3-35 3-36 4-1 4-2 4-3 4-4 Configuration Wizard - SNMP Question.............................................................................................18 Configuration Wizard - User Information............................................................................................19 Configuration Wizard - Profile and Notification Details........................................................................20 Configuration Wizard - Configure WEBES..........................................................................................21 WEBES Service Obligation Validation...............................................................................................22 Clean Binary Error Log....................................................................................................................23 WEBES Installation Execution............................................................................................................23 WEBES Install Complete...................................................................................................................24 Logon Window...............................................................................................................................27 Main Screen..................................................................................................................................27 Toolbar..........................................................................................................................................28 Navigation Tree - Hierarchy..............................................................................................................30 Navigation Tree - Collapsed.............................................................................................................30 Navigation Tree - Expanded.............................................................................................................31 Add Group....................................................................................................................................39 Remove Group................................................................................................................................40 Add Node.....................................................................................................................................41 Remove Node..............................................................................................................................42 Activating Node...........................................................................................................................42 Activating Node Message..............................................................................................................42 Unable to Activate Node Message..................................................................................................43 Add Category..............................................................................................................................43 Remove Category.........................................................................................................................44 Add Log Files Tab.........................................................................................................................46 Remove Log File Tab......................................................................................................................47 Analysis Failed Message................................................................................................................50 Status Icons..................................................................................................................................51 Progress Window.........................................................................................................................51 Additional Entries Navigation.........................................................................................................52 Problem Report Tab.......................................................................................................................52 Summary Tab...............................................................................................................................53 Summary of Sub-Types...................................................................................................................54 Sub-Type Listing............................................................................................................................54 Events Tab...................................................................................................................................55 Navigation ButtonsProblem Reports..............................................................................................56 Navigation ButtonsEvents............................................................................................................56 Protocol Details: Binary Event Log...................................................................................................57 Protocol Details: CommandView EVA..............................................................................................58 Protocol Details: SNMP..................................................................................................................58 Protocol Details: WMI for Windows................................................................................................58 Managed Entities..........................................................................................................................59 Managed Entity Detail...................................................................................................................60 Managed Entities..........................................................................................................................61 Export Managed Entities popup......................................................................................................62 Web Interface Notification Settings Page...........................................................................................63 Web Notifications...........................................................................................................................64 WEBES Notification Dispatch...........................................................................................................64 E-mail Settings................................................................................................................................66
List of Tables
1-1 2-1 2-2 2-3 2-4 2-5 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 3-9 ELMC Versions Packaged in WEBES..................................................................................................12 Windows Browser Requirements........................................................................................................16 WEBES Information Requested During Installation................................................................................19 WEBES Information Requested During Installation................................................................................20 WEBES Information Requested During Installation................................................................................21 WEBES Information Requested During Installation................................................................................22 Web Interface Components..............................................................................................................28 Toolbar Default Buttons.................................................................................................................28 Toolbar Dynamic Buttons...............................................................................................................29 Navigation Tree - Hierarchy..............................................................................................................30 Navigation Tree - Features................................................................................................................31 Navigation Tree Icons......................................................................................................................31 Applet Messages............................................................................................................................38 Additional Toolbar Functions............................................................................................................50 Event Type Color Codes...................................................................................................................53
2 Publishing History
Revision 29-June-2007 July 2007 - Jan 2008 May 2008 January 2009 April 2009 September 2009 March 2010 August 2010 Description Created initial copy for WEBES 5.1 using WEBES 5.0 baseline copy Updated for WEBES 5.1 Updated for WEBES 5.2 Updated for WEBES 5.4 Updated for WEBES 5.5 Updated for WEBES 5.6 Updated for WEBES 6.0 Updated for WEBES 6.1
3 Typographic Conventions
find(1) Book Title Linked Title http://www.hp.com Command user input computer output Enter
HP-UX manpage. In this example, find is the manpage name and 1 is the manpage section. Title of a book or other document. Title that is a hyperlink to a book or other document. A Web site address that is a hyperlink to the site. Command name or qualified command phrase. Commands and other text that you type. Text displayed by the computer. The name of a keyboard key. Note that Return and Enter both refer to the same key. A sequence such as Ctrl+A indicates that you must hold down the key labeled Ctrl while pressing the A key. Defined use of an important word or phrase. The name of an environment variable, for example PATH or errno. A value that you may replace in a command or function, or information in a display that represents several possible values. An element used in a markup language. An attribute used in a markup language.
4 Related Documents
1 Intended Audience
10
1 General Information
This chapter provides an overview of the Web Based Enterprise Services (WEBES) suite of tools for Windows. WEBES 6.1 is supported for Windows only. Detailed instructions for installing WEBES on other supported operating systems are provided in the previous versions of WEBES installation guides.
The WEBES Service Event Analyzer tool uses these common components to minimize the tool-specific functionality and the differences between the tools.
SEA includes a web browser interface that interacts with the Director. Although only one Director can run on a system at any time, many web browser connections can be simultaneously active and all connected to a single Director. See Chapter 3 WEBES User Interface for user interface details.
1 1
The Director automatically starts along with the system and normally does not require additional attention. See WEBES Reference Guide if you do require information on interacting with the Director.
1.4 ELMC
ELMC is a daemon process that runs continuously. ELMC contains functions that allow WEBES to interact with the operating system, other WEBES agent processes, and the Director. The Director will not perform correctly without the WCCProxy service. ELMC automatically starts along with the system and normally does not require additional attention. See WEBES Reference Guide if you do require information on interacting with ELMC. NOTE: Formerly known as WEBES Common Components Proxy (WCCProxy), ELMC is a kit that now contains the WCCProxy service. Where you see ELMC in this document, the term is referring to the collective components of the ELMC kit, and where you see WCCProxy in this document, the term is referring to the WCCProxy service itself.
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
WEBES 6.1 is NOT supported on the following version of Windows: Windows XP Professional 64-bit Itanium Edition. Although WEBES is not yet supported on this operating system, the Itanium WEBES kit may install and operate correctly, but the Pentium WEBES kit can not be installed.
See WEBES Hardware Requirements for the hardware that WEBES supports. Although WEBES can be installed on any of these hardware and operating system combinations, SEA only supports event bit-to-text translation and event analysis on a certain set of HP product. See the WEBES Reference Guide for the list of products that SEA supports.
1.9 Upgrades
Upgrades can include anything from a major WEBES release to a minor kit with only rule updates or small functional improvements. When upgrading you do not need to uninstall WEBES if your existing WEBES version is within two releases. For example, when upgrading to WEBES 6.1 you do not need to uninstall your current version if it is WEBES 6.0 or 5.6. The WEBES 6.1 kit does the following: Recognizes an existing installation Saves configuration and state data
1.7 What is New in this Release? 13
Uninstalls the existing kit Installs the WEBES 6.1 version Restores the configuration and state data
WEBES upgrades are also available in the form of patches which can be downloaded and installed on an existing WEBES installation. Upgrades/Patches for WEBES are available at the HP Service Tools Website: http://www.hp.com/services/ webes NOTE: Before you attempt to upgrade ensure that the WEBES-related DESTA_service is running and functioning in order to successfully migrate Managed Entity data.
14
General Information
2 Installing on Windows
2.1 Pre-Installation
2.1.1 WEBES System Requirements
The system must meet the following basic requirements before you install WEBES: Processor architecture HP 32-bit Intel systems, HP x64 Intel EM64T or AMD64 systems.
Non-HP Systems: WEBES is a proprietary service tool and is not a fully qualified off-the-shelf product such as Norton SystemWorks. As such, only platforms manufactured by HP, such as the ProLiant, are officially supported.
Engineering normally expects that WEBES will operate correctly on any industry standard system based on the Intel x86, EM64T, or an AMD architecture. However, because HP does not qualify WEBES on third-party products, functionality on such systems is provided on an as-is basis only. Operating system Refer to WEBES Operating System Requirements Service Packs (SPs) HP supports the two most recent SPs for Windows Server 2003 or 2008. Disk space A total of 353MB must be available at install time, as follows: 64MB in a local directory to store the WEBES kit itself 64MB in the %TEMP% directory (typically %SystemDrive%\Documents and Settings\{username}\Local Settings\Temp, where %SystemDrive% is C: by default). Files saved to %TEMP% are removed after installation completes. 100MB on the drive where you will install WEBES (%SystemDrive%\Program Files\HP\svctools by default)
A total of 289MB are used after installation completes, assuming all components are installed. Local kit copy required Copy the WEBES kit to a local drive. The installation results in an error when mapping a drive letter to another system where the kit resides, for example: Internal Error 2755. 3, F:\path to\WEBESV60BL322KIT2_Jan-28-2010_Windows.MSI Virtual memory 400MB of virtual memory is recommended. During standard operation, SEA uses far less memory. For example, when the Director is idle, usage stays generally around 13MB for systems with all the WEBES tools installed. The Director only approaches the maximum value when a high volume of events arrive or an extremely large log file is processed. Even then, the memory usage may remain significantly below the maximum value. The virtual memory requirement is intended to set a threshold for the absolute maximum amount of memory that will ever be needed. If the threshold is exceeded, the Director terminates with out-of-memory error. Virtual memory for a process is stored in RAM and the page file on your disk. The space allocated must be sufficient to run WEBES and all other applications that you want to run simultaneously. If the virtual memory requirement given here is too large or too small for your environment, you are free to make adjustments. You may want to experiment with various settings to find the optimal value. Refer to the WEBES Reference Guide for more information on adjusting the memory settings. Microsoft Windows Installer v3.1 must be installed. For details and download options: http://support.microsoft.com/kb/893803 You can check the Windows Installer version by entering msiexec at the command prompt. (Ignore the message about incorrect command line parameters.) TCP/IP services must be installed and running.
2.1 Pre-Installation
15
Web browsers can use different Java runtime environments, but the SEA User Interface requires certain versions of Java for each web browser. You can obtain the required version from: http://java.sun.com/ getjava Internet Explorer Either the Microsoft Java VM version 1.1.4, or a Sun JRE version 1.6.17 and older. No Java is included in Internet Explorer on Windows Server 2003 and 2008, and Microsoft no longer supplies a Java VM. You must download and install a Sun JRE instead. Firefox Sun JRE version 1.3.1 or higher. Firefox does not include any Java VM. You must download and install a Sun JRE.
A version may already be installed for your web browser. You can check the version by selecting Tools Web Development Java Console. The Java version is given on the first line of the Java Console window. NOTE: Install any desired web browsers before installing the Sun JRE. The JRE installation then finds and updates installed web browsers so that they use the Sun JRE. Windows Event Logs ensure that the binary event log is large enough to hold all events long enough for WEBES to process them in situations where large streams of events occur over a short period of time. To do this, set the size of your Application Event Log to at least 4MB, in the Windows Event Viewer properties of this log (Event Viewer is in Control Panel under Administrative Tools). After WEBES installation, SEA begins analyzing all events currently stored in one of the Windows Event Logs. On x86 (Pentium) and x64 systems, SEA analyzes only the Application Event Log. This initial
16
Installing on Windows
analysis can result in high CPU usage over an extended period. To control this operation, you have two options: Archive and clean the Windows Event Log as described in Archiving and Cleaning the Windows Event Log before installing. This reduces the size of the log. Choose to delay the initial scan when prompted during installation. As a result SEA automatic analysis does not run until after (and starting with) the initial scan.
Make sure that HTTP 1.1 settings are enabled on a supported Web browser. Choose Tools Internet Options Advanced from the pull-down menus. Check both of the following under HTTP 1.1 Settings: Use HTTP 1.1 Use HTTP 1.1 through proxy connection
2.1.3 Permissions
In order to install, remove, or update WEBES your user ID must be one of the following: A member of the Administrators group on the machine A member of a group that is a member of the Administrators group on the machine. For example, if your user ID is a Domain Admin, and you have added Domain Admins to the Administrators group on the local machine, then you have the necessary permissions.
To add Domain Admins to the local Administrator group, use the procedure for your operating system, for example. Windows Server 2003: From a login account with administrator privileges, locate the user management function under My Computer Manage Computer Management (Local) System Tools Local Users and Groups Groups. Double click the Administrators Group, and press the Add button. Highlight Domain Admins and press Add.
If WEBES was installed when you cleaned the log and you stopped the Director, you can now restart it using the procedure described in the WEBES Reference Guide.
From Console Terminal Server system installations should be performed from the Terminal Server console by an administrator (either the Administrator account or any account in the Administrators group). For the best results, make sure that no clients are logged on to the server during WEBES installation. You can send clients a message about the time and duration of the installation and then disable all connections before starting.
2.1 Pre-Installation 17
Otherwise, the process for installing is the same as any other Windows WEBES installation. From Client Install from a Terminal Services client as follows: 1. 2. 3. 4. Log on to the Terminal server as an administrator and close all applications. Copy the WEBES kit to a local drive on the Terminal server. Install the program on a local NTFS formatted drive as with any other Windows WEBES installation. On the Terminal server, open and close the system PATH environment variable. Opening and closing sets the PATH so that commands such as desta or wsea can work without specifying the full \svctools\common\bin path to the command. Open Start Settings Control Panel System. Click the Advanced tab. In Environment Variables, open the PATH entry (under System Variables) for editing. Do not make any changes; just click OK several times to get out of the System utility. The PATH is now set for any command prompt windows opened after performing this workaround.
4. 5.
Read the license agreement, click the appropriate radio button if you accept it, and then click Next. Follow the on screen instructions. a. Upgrading If a WEBES version within two previous releases is present, the installer alerts you about the other version and prompts you to upgrade. If this is a fresh WEBES installation, you will not see this message. See Upgrading WEBES for details. b. Installation Directory Path Selection You can change the default directory path for your installation by clicking the Change button and browsing to an alternative installation directory. However, if you do this take note of your installation directory for future reference. Enter WEBES user information.
6.
18
Installing on Windows
Company Name Phone Number E-mail SMTP Mail Server System Serial Number
7.
19
Profile and Notification Information The following information will be sent in WEBES problem report notifications. Customer XYZ Company The company using WEBES as a customer of HP. By default, the Company name entered is entered in the User Information window. The address of the primary WEBES user, or of the company site. The primary contact person at the customer company's site for the system running WEBES. By default, the User Name is entered in the User Information window. The person to contact at the customer company's site, if the Primary Contact person is unavailable. The telephone voice contact number for the primary contact. By default, the Phone Number is entered in the User Information window. Add details that will be useful to your service provider.
Special Instructions
"Check with customer prior to dispatching services. Prior notification to security is necessary for service access to site."
8.
20
Installing on Windows
A01234567890 server1.xyzcompany.com
System IP Address
9.
21
A01234567890
10. The following information window enables you to choose to have a clean binary log for this installation, for more details see Archiving and Cleaning the Windows Event Log.
22
Installing on Windows
1 Click Install to begin the installation. 1. Figure 2-7 WEBES Installation Execution
12. You will know that the WEBES installation is completed when you see the following window:
23
When you click Finish, the window may not disappear for up to a minute (approx). WEBES is finishing installation tasks during this time and will close the window when the tasks are completed. Clicking Finish multiple times will have no further effect.
24
Installing on Windows
4. 5.
Restores the saved data. Deletes the WebesBackup directory and all of its contents.
If you answer No, the kit exits and the existing version of WEBES is not upgraded. If desired, you can uninstall the existing WEBES copy yourself, but then not all data will be migrated upon installing the newer version as described in Installing WEBES.
is in use by another application on which you depend. Nevertheless, it is sometimes appropriate to remove SQL Server completely. 1. 2. 3. 4. From Windows Control Panel, run Add/Remove Programs. From the list of programs select Microsoft SQL Server 2005 and click the Change button. (This does not immediately remove SQL Server). Follow the prompts. Select Remove SQL Server. Follow the prompts. The SQL Server instance will be removed. NOTE: No database data is deleted as a result of this action. It is not recommended to delete this data unless you are certain that it will never be needed. Even then, before deleting such data, it is recommended to make a backup copy. By default, SQL Server data is located in the Microsoft SQL Server folder under the Program Files folder.
26
Installing on Windows
https://hostname where director is running:7906. Use the fully qualified host name or the IP address of the system hosting WEBES. 2. You will be prompted to enter a Profile User Name for your session; this can be any name you choose. Enter the name and click Logon IMPORTANT: It is advised to attach adv to the end of your Profile User Name. This enables you to log on as an advanced user and carry out configuration in WEBES. Figure 3-1 Logon Window
3.
If you are prompted by the browser that the site does not have a signed
27
Note that the value of the URL field includes the hostname for the system you logged into, as well as your username, indicating the current profile. https://hostname:7906/?profile=username TIP: If you need to change profiles while using SEA, you can edit your browser's URL field by replacing the current profile username with a different one. The components of the web interface display are described in Table 3-1 Web Interface Components. Table 3-1 Web Interface Components
Component Title Bar Toolbar Description Shows the software version, active profile, and the operating system running WEBES. By default, provides access to the online help, system configuration, processing statistics, WEBES managed entities configuration, WEBES notification settings and new binary error log creation. The toolbar is dynamically updated, and additional features are available with select SEA screens. Displays any browser connectivity errors and any current WEBES configuration warnings. It will typically indicate which aspects of configuration should be addressed first. Lists the available groups, nodes, storage cells, categories, and log files. Displays interactive screens and system information. When SEA loads, the display frame shows product information. Displays messages from the browser and usage tips.
NOTE: SEA allows you to work in multiple browser windows. If you are using the same profile, the navigation trees in all the windows will automatically synchronize.
3.2.1 Toolbar
Figure 3-3 Toolbar shows the default web interface toolbar. Figure 3-3 Toolbar
The toolbar buttons update dynamically depending on what you are doing. The toolbar buttons are grouped by function. Those in the left hand group are operational buttons that are related to current analysis activity; they are updated dynamically depending on what you are doing. The buttons in the right hand group are configuration buttons that are always available for changing WEBES operational characteristics. Table 3-2 Toolbar Default Buttons describes the toolbar commands that are always available: Table 3-2 Toolbar Default Buttons
Component Progress Window New Binary Error Log Creation WEBES Notification Status Description Opens a new browser window that reports the processing status of log files. Opens the New Binary Log screen in the display frame. Displays notification status.
28
Description Opens the RSC settings screen for configuring enterprise wide information for the Remote Support Client. NOTE: This icon and option only exists for customers who have also installed Insight Remote Support Standard.
Configure SEA Settings Configure Managed Entities Configure Managed Protocols Configure WEBES Managed Sites Configure WEBES Managed Contacts Configure WEBES Notification Settings Help
Opens the SEA settings screen. Allows you to configure WEBES Managed Entities. Allows you to configure WEBES Managed Protocols Allows you to manage WEBES Managed sites. Allows you to configure WEBES Managed contacts. Allows you to configure WEBES notifications including WEBES e-mail settings. Opens a new browser window containing the online user guide.
The following buttons also may appear in the toolbar, depending on the feature being used: Table 3-3 Toolbar Dynamic Buttons
Component Clear Results Button Reprocess File Button Analyze File Button Analyze Filtered Events Button Get Current FRU Table Button Generate Storage Spreadsheet Button Get Current Storage Cell Configuration Button Description Available when viewing automatic analysis details. Available when viewing manual analysis details. See Table 3-8 Additional Toolbar Functions, Reprocess File Button for more information. Available when viewing manual translation details. See Table 3-8 Additional Toolbar Functions, Analyze File Button for more information. Available after processing a file with a filter applied. See Table 3-8 Additional Toolbar Functions, Analyze Filtered Events Button for more information. Available when viewing Real-Time Monitoring of a Tru64 UNIX or OpenVMS Alpha system. See Table 3-8 Additional Toolbar Functions, Get Current FRU Table Button for more information. Available when viewing Real-Time Monitoring of a Storage Cell. Available when viewing Real-Time Monitoring of a Storage Cell. See Table 3-8 Additional Toolbar Functions, Get Current Storage Cell Configuration Button for more information.
3.2.2 Navigation
Using SEA, it is possible to monitor the binary event log files generated by a wide variety of computers all from a single web interface. In order to simplify the process of monitoring these diverse information sources, the web interface uses a hierarchical navigation tree composed of groups, nodes, storage cells, categories and binary event log files.
29
Refreshes tree with current list of storage cells detected by Command View EVA when Clicked. The list is also refreshed when a Storage Configuration Event (type 910) is logged to the system's binary event log and processed by SEA automatic analysis. A WBEM Common Information Model Object Manager (CIMOM) which sends WBEM indications to WEBES (when WEBES has successfully registered with the CIMOM). By default a WBEM folder contains Real Time Monitoring.
WBEM
30
Current Selection is Highlighted In most browsers, the currently selected entry in the Navigation Tree is highlighted (Figure 3-5 Navigation Tree - Collapsed). Collapsing Navigation Expanding Navigation The tree structure can be collapsed to the group level (Figure 3-5 Navigation Tree - Collapsed). Click on the expansion symbol for an entry to view its contents. Once an entry is expanded, the expansion symbol changes to a collapse symbol. To hide the contents again, click the collapse symbol. Each entry in the tree has a name and an icon that indicates its type. For example, in Figure 3-6 Navigation Tree - Expanded you can tell that the jarjar.cxo.dec.com node is inactive because of its icon. You can customize the navigation tree by adding and removing groups, nodes, categories, and binary event log files. NOTE: Viewing Managed Entity Configuration Viewing Results Refreshing Navigation Storage cells are generated automatically and cannot be customized by the user.
Icons
You can view and update the Managed Entity configuration data for a Node in the Navigation Tree. You can view the results of automatic analysis and initiate manual analysis from the navigation tree. If you modify the entries in the navigation tree, you may need to refresh the display so your changes appear. To refresh the navigation tree, click the Refresh Tree button.
31
Icon
Description Managed Entity node needs info. Indicates an active Managed Entity that requires user attention probably needs additional configuration data for monitoring of the node can be implemented properly. Managed Entity node has a problem report. Indicates an active Managed Entity that has some sort of Problem report that needs attention. Managed Entity node (inactive). Indicates an inactive Managed Entity this implies that WEBES cannot connect to the Entity, either because of mis-configuration or because the Entity is inaccessible. Problem group
Problem RTM
Log file
File read
File done
Event
System log
Category open
Category closed
Node group
Other logs
Storage system
32
Icon
Storage cell
33
34
35
36
3.2.2.4.9 WBEM
Displays the same as Real Time Monitoring.
37
Only one message can be displayed at a time. When multiple issues are detected, the applet will display the message that is likely to be most important to fix first. When that issue is fixed, the next most important message will be displayed, and so on until there are no outstanding messages to display.
3.3.1 Groups
From the navigation tree, you can create new groups and remove existing groups.
The location and placement options determine where you would like the new group to appear in the navigation tree relative to existing groups. By default, new groups are added after the selected group. 2. 3. 4. Select an existing group from the list. Select a placement option from the radio buttons. Enter the name for the new group in the text field. Be sure to follow these rules for naming groups: 5. Group names should be unique. If you enter a group name that is already in the navigation tree at the same level, SEA will not create the new group. Group names should not use punctuation characters. These characters can cause JavaScript errors in the web interface. Group names should be descriptive. If you leave this field blank, the group is named "newGroup" by default.
Click the Add New Group button. The new group appears in the navigation tree.
39
3.
Select the group name or names you want to remove from the list. To select multiple groups, press CTRL and click on each group. If the groups are consecutive, press SHIFT and click on the first and last group names.
4.
Click the Remove Selected Group(s) button. The groups disappear from the navigation tree.
3.3.2 Nodes
Expanding a group in the navigation tree displays the nodes contained in that group. Nodes can be expanded by clicking on the expansion symbol next to their name to reveal the log file types or storage cells included in that node. You can add and remove nodes from the groups in the navigation tree.
40
The location and placement options determine where you would like the new node to appear in the navigation tree relative to existing nodes. By default, new nodes are added after the selected node. 2. 3. 4. 5. Select the existing managed entity from the drop-down list. Select where in the tree the new node will be placed. Select a placement option using the radio buttons. Click the Add New Node button. The new node appears under its group in the navigation tree.
41
3.
Select the node name or names from the list. To select multiple nodes, press CTRL and click on each node. If the nodes are consecutive, press SHIFT and click on the first and last node names.
4.
Click the Remove Selected Node(s) button. The nodes disappear from the navigation tree. If the selected node is contained in multiple groups, removing it from one group will not affect its presence in other groups.
If the Director on the remote node is accessible, a message appears in the display frame (Figure 3-12 Activating Node Message) and the navigation tree is updated to show the new status. Figure 3-12 Activating Node Message
42
If the Director is not accessible, a message appears in the display frame (Figure 3-13 Unable to Activate Node Message) and the navigation tree is not changed. Figure 3-13 Unable to Activate Node Message
3.3.3 Categories
Categories are an optional feature that is disabled by default. If you want to use categories, you must enable the feature using the User Settings tab on the Settings screen. Categories provide a method for grouping the log files listed under the Other Logs folder. If you use categories, SEA provides another layer of folders under the Other Logs folder. This feature may be useful if you monitor numerous log files.
The location and placement options determine where you would like the new category to appear in the navigation tree relative to existing categories. By default, new categories are added after the selected category. If no categories currently exist for the group, skip Step 2 and Step 3. 2. 3. Select an existing category from the list. Select a placement option from the radio buttons.
43
4.
Enter the name for the new category in the text field. Be sure to follow these rules for naming categories: Category names should be unique. If you enter the name of an existing category, SEA will not create the new category. Category names should not use punctuation characters. These characters can cause JavaScript errors in the web interface. Category names should be descriptive. If you leave this field blank, the category is named "newCat" by default.
5.
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.
NOTE: On Windows, the system log file is the Windows Application Event Log, located at %SystemRoot%\system32\config\AppEvent.Evt. The terminology "system" log file should not be confused with the Windows System Event Log, located at %SystemRoot%\system32\config\SysEvent.Evt, which SEA does NOT read as of this release. If the node contains storage cells, another pair of icons are listed under each storage cell. Click the expansion symbol to view the analysis options for the storage cell's system log in the navigation tree. Real Time Monitoring shows the results of automatic analysis in the display frame, for the subset of events from the node's system log file that apply to the storage cell. Full View manually analyzes the system event log and processes the subset of events from the node's system log file that apply to the storage cell.
If the node is a WBEM node, another pair of icons are listed under WBEM node. Click the expansion symbol to view the analysis options for the WBEM node's system log in the navigation tree. Real Time Monitoring shows the results of automatic analysis in the display frame, for the subset of events from the node's system log file that apply to WBEM node. Full View manually analyzes the system event log and processes the subset of events from the node's system log file that apply to WBEM node.
3.3.4.2 WBEM
The WBEM CIMOM is the source of WBEM Indications (event information) for systems/servers that support WBEM services, provided that WEBES has successfully subscribed with the CIMOM for WBEM indications. To view the analysis options for WBEM, in the navigation tree, click the expansion symbol associated with a WBEM entry: Real Time Monitoring shows the results of automatic analysis in the display frame.
The best place to store log files (as well as other user data) is in one of the user data subdirectories: svctools\specific\ca\userdata svctools\common\ca\userdata
3.3 Customizing the Navigation Tree 45
Files stored in these subdirectories are automatically backed up and saved if you uninstall, reinstall, or upgrade WEBES. For more information on storing user data, see the WEBES Installation, Configuration, and Usage Guide. If you want to store files elsewhere, you can configure WEBES by adding a comma separated list of file paths to the CA.WUI.OLDirs key in the DESTA registry. You also can enable a text entry field for specific users. The text field allows users to add log files to the Other Logs list by entering the path and filename of an event log located anywhere in the file system. Adding Other Logs Follow these steps to add other log files: 1. Open the Other Logs screen in the display frame. If you are using categories, click on the category name for the node. Otherwise, click on the Other Logs link for the node. The Other Logs screen opens in the display frame (Figure 3-16 Add Log Files Tab). The Add Files tab is already selected. Figure 3-16 Add Log Files Tab
2.
Select the desired binary event log files: Click the Select All button to select all the listed log files. Click the check box for each file. You can select multiple check boxes. Click the Clear All button or uncheck a selected check box to deselect files.
3. 4.
(Optional) If enabled, enter the path and filename in the text field. Click the Add button. The binary event log file is added to the navigation tree under the Other Logs entry or appropriate category for the node.
Removing Other Logs To remove binary event log files from the navigation tree, follow these steps: 1. Open the Other Logs screen in the display frame. If you are using categories, click on the category name for the node. Otherwise, click on the Other Logs link for the node. 2. Select the Remove Files tab from the bottom of the screen (Figure 3-17 Remove Log File Tab).
46
3.
Select the log file name you want to remove from the list. To select multiple files, press CTRL and click on each file name. If the files are consecutive, press SHIFT and click on the first and last file names.
4.
Click the Remove Selected Log File(s) button. The navigation tree is refreshed to reflect your changes.
The IPF configuration reports include information from cell based systems. In particular, Field Replaceable Units (FRU) are reported by the Logical Unit Number (LUN) to which they belong, in addition to the existing information. Information about memory dimm sizes is accessible when it is present in the configuration entry. Information about partitions and the cells that belong to those partitions is provided when it is present in the configuration entry. The number of the partition that logged the configuration entry is accessible when it is present in the configuration entry. An extract of the sample configuration entry is shown below:
Event: 1 Description: Configuration SDR FRU
File: 8620_par0_config.sys@bagend ======================================================================== OpenVMS IPMI configuration report Hostname: BILBO 3.4 Processing Events 47
TimeStamp: Thu 24 Mar 2005 15:01:18 GMT-07:00 DSR Type: HP rx8620 (1.30GHz/3.0MB) Serial #: 1111111111 OEM Property List LUN ID Cell Description ------ ------ ------ ----------------------------------------0 0x0 0 Configuration collected from the running Partition #: 0 0 0x9 0 Partition ----------0 1 2 CELL # -----0 2, 3 1 DIMM # -----0B 1B 2B 3B 4B 5B 6B 7B 8B 9B 10B 11B 12B 13B 14B 15B Size ----------2048 MB 2048 MB 2048 MB 2048 MB 2048 MB 2048 MB 2048 MB 2048 MB ---------
0x4
DIMM # Size ------ ----------0A 2048 MB 1A 2048 MB 2A 2048 MB 3A 2048 MB 4A 2048 MB 5A 2048 MB 6A 2048 MB 7A 2048 MB 8A -9A -10A -11A -12A -13A -14A -15A -32 GB Total Memory DIMM # Size ------ ----------0A 2048 MB 1A 2048 MB 2A 2048 MB 3A 2048 MB 4A 2048 MB 5A 2048 MB 6A 2048 MB 7A 2048 MB 8A -9A -10A -11A -12A -13A -14A -15A -32 GB Total Memory
0x5
Size ----------2048 MB 2048 MB 2048 MB 2048 MB 2048 MB 2048 MB 2048 MB 2048 MB ---------
0x6
DIMM # Size DIMM # Size ------ ----------- ------ ----------0A 2048 MB 0B 2048 MB
48
1A 2048 2A 2048 3A 2048 4A 2048 5A 2048 6A 2048 7A 2048 8A -9A -10A -11A -12A -13A -14A -15A -32 GB Total 1 0x7 3
MB MB MB MB MB MB MB
MB MB MB MB MB MB MB
Memory DIMM # -----0B 1B 2B 3B 4B 5B 6B 7B 8B 9B 10B 11B 12B 13B 14B 15B Size ----------2048 MB 2048 MB 2048 MB 2048 MB 2048 MB 2048 MB 2048 MB 2048 MB ---------
DIMM # Size ------ ----------0A 2048 MB 1A 2048 MB 2A 2048 MB 3A 2048 MB 4A 2048 MB 5A 2048 MB 6A 2048 MB 7A 2048 MB 8A -9A -10A -11A -12A -13A -14A -15A -32 GB Total Memory
Viewing Analysis Progress You can view the current status of any automatic or manual analysis job by clicking on the Progress Window button in the toolbar to open a new window that displays all the queued and running analysis jobs, and event counts for each job. Whenever manual analysis is invoked for a log file, an animated icon is used to reflect the running status of the manual analysis job; when analysis of the log file is complete, the icon in the navigation tree changes to reflect the results of the manual analysis, and the results are shown in the display pane. NOTE: After clicking on the file for manual analysis there may be a delay before the progress window displays progress for that file.The data in the progress is not displayed in real time. There may be couple seconds difference in the actual progress and what is displayed in the progress window. Viewing Results The results of automatic and manual analysis are shown in the display frame when an appropriate selection is made in the navigation tree. Some or all of the following information is available, depending on the type of Managed Entity and the type of analysis involved: Problem Reports results of analysis Summary a count of the number of each type of event found in an analyzed log file (only available with manual analysis)
3.4 Processing Events 49
Events chronological list of events received from an event source Configuration Entries lFRU configuration events received from the event source
NOTE: If you have configured the User Settings so SEA only performs manual translation, rather than translation and analysis, the Problem Reports tab is empty. Analysis Failed If the file cannot be processed for any reason, a message similar to the one in Figure 3-18 Analysis Failed Message is shown. Figure 3-18 Analysis Failed Message
When the User Settings are configured Clicking the Analyze button will perform to perform only manual translation by analysis for the current log file. Thus, if default. you need to perform analysis, it is not necessary to change the User Settings and reprocess the file. When you use a filter for processing a Clicking the Analyze Filtered event log file. button allows you to repeat the analysis using only the events that met the filter criteria. When you are performing or viewing Automatic Analysis on a Tru64 UNIX or OpenVMS Alpha node. Clicking the FRU button reads the current Field Replaceable Unit (FRU) hardware configuration table from the node's in-memory table and adds the table as an entry to the Configuration Entries tab. The Get Current Storage Cell Configuration button adds an entry to the Configuration Entries tab for the selected storage cell, detailing the hardware configuration of the storage cell.
50
When automatic analysis generates a problem report, exclamation points are added to the icons for the node, system log, and real time monitoring. The icon remains changed until problem report details are viewed and the tree is refreshed. If another problem report is generated after the tree is refreshed, exclamation points are added to the icons again. You also can determine the results of manual analysis on a binary event log file by checking the icons. SEA uses a animated yellow icon when a binary log file is being read and an animated green icon during analysis. If processing has completed and problem reports were generated, an exclamation point is added to the icon. Otherwise a check mark is added to the icon. Unlike the icon changes associated with automatic analysis, the manual analysis icon changes remain visible until you close the web interface session. NOTE: dash. If you are only performing translation, when processing completes the icon will appear with a
51
The Progress window provides statistics for all the log files that are currently being analyzed by SEA, including automatic and manual analysis jobs. The information in the Progress window includes: The origin of the log file The number of events in the file
NOTE: After clicking on a file for manual analysis there may be a delay before the progress window displays progress for that file.The data in the progress is not displayed in real time. There may be couple seconds difference in the actual progress and what is displayed in the progress window. The position of each job in the queue is displayed, and information is dynamically updated as the processing changes. When a job finishes processing, it is removed from the window. When monitoring the progress of a job, you can refresh the display manually by clicking the refresh icon in the upper left hand corner. To stop processing an active manual job, click on the Stop icon.
When there are many entries, you can use the navigation options to page through the results. Use the Previous and Next links to move between entry screens. Enter a number in the entry field and click Go to display a specific entry. You can control the number of entries shown in a tab with the options in the User Settings window.
NOTE:
52
The filters used when generating the problem reports are listed at the top of the screen. However, the display only shows the filters that apply to problem reports and may not list all the filters you selected. When working with problem reports, these options are available: To sort the entries in the report list select the column headers. To view the contents of a report, click on its entry in the list of available problem reports.
The problem reports generated by the web interface are the same as those generated by the CLI.
3.4.3.2 Summary
The Summary tab is only available when you perform manual analysis. If you select Real Time Monitoring from the Navigation Tree, for example, the Summary tab is not displayed. When performing manual analysis, the Summary tab describes the event types contained in the binary event log file (Figure 3-23 Summary Tab). Figure 3-23 Summary Tab
Each event type is listed along with the number of occurrences. The time stamps for the first and last events are listed under the summary information. The filters that were applied are listed at the top of the screen. Be aware that the screen only shows the filters that apply to the summary report and may not list all the filters you selected.
To view the Sub Type event summary information, select the summary tab in the Web interface for any binary event log. This will show you the classification of the event types. If the event summary has event type 14009 or 199, click 14009 link or 199 link to view the Sub Type event summary.
3.4 Processing Events 53
Following screen shows the summary of Sub Type event 14009: Figure 3-24 Summary of Sub-Types
To view the Sub Type listing information, click Sub-Type Listing link shown in the above screen. The following screen shows the listing of all the Sub Type events of event type 14009: Figure 3-25 Sub-Type Listing
3.4.3.4 Events
The Events tab shows a list of the events contained in the binary event log file. Depending on the filtering options that were applied during processing, all the events in the log file may or may not be shown (Figure 3-26 Events Tab).
54
NOTE:
You can control the fields that are shown on the events tab from the User Settings window.
The filters that affected the output are listed at the top of the screen. Be aware that the screen only shows the filters that apply to events and may not list all the filters you applied. When working with events, these options are available: To sort the events list, use the column headers. To view the translation of an event, click on its entry in the list.
The translated events shown by the Web interface are the same as those shown by the CLI.
Sorting with a Filter Using a filter to sort entries impacts all the output generated by processing a log file, regardless of how many screens are required to show all the entries.
The buttons are used to move between entries in the list. You can view the details for other events in the list using the Previous and Next buttons. When paging between entries, the column heading sort order always reverts back to the Index column in ascending order. Filter sorts, however, still apply. Click the Index button to redisplay the list of entries. If you select Put Event Details In A New Window in your User Settings, the Index button is not available. Clicking the Previous and Next buttons displays all entries in the new window. The Event Details tab includes a drop down list that can be used to change the report type.
2.
Click the New button to create a new protocol. The Managed Protocol Type screen will open.
56
3.
Enter a name for your protocol and select the protocol type from the drop-down list. You can create as many protocols as you have varied credentials for you managed entities. If each of your managed entities has unique usernames and passwords, then create a protocol for each set of credentials appropriate to the communication method used by that managed entity. The following Managed Protocol types can be created: Binary Event Log Command View EVA Non-stop WBEM SNMP SANIQ WS-MAN Used for Superdome 2 devices. UNIX WBEM WMI WBEM (Windows) SSH TELNET
4.
Click Apply Changes. The Managed Protocol Details screen will open. The following examples show protocol details for various protocol types. Provide the credential information for the protocol type you are configuring. Figure 3-29 Protocol Details: Binary Event Log
57
5.
Click Apply Changes when you are finished configuring your protocol details.
58
IMPORTANT: Remember to edit, create, and manage your Webes Managed Protocols BEFORE you add, create, or edit your Webes Managed Entities. The protocols will be applied to the entities, so it is important to create the protocols first. Figure 3-33 Managed Entities
Any managed entity that is not fully configured is highlighted with an orange background, and has an asterisk indicating that further configuration information is required. To remove the managed devices, check the device name and click the Delete button. Click Select All and then click Delete to delete all the managed devices. To view the details of a managed entity, click on the particular managed entity (for example, Command View EVA Server) which lists out the managed entity details as shown in Figure 3-34 Managed Entity Detail.
59
Specific fields may vary according to the type of managed entity the example shows the detailed fields for a Command View EVA Server. NOTE: WEBES requires a fully qualified domain name (FQDN) or an IP address to be provided in the following Managed Entities page fields: User-Definable Entity Name Entity Name on Network
You can choose from the existing contact names for Primary Contact, Out of Hours Contact, and HP Contact or enter new contact names by clicking Go To Contacts button and filling the required information. The Refresh List button updates the new contact names (added) along with the existing contact names, if any. If you have created protocols that are appropriate to your managed entity type, those options will be displayed on the Managed Entity Detail screen. You can enable and disable protocols for each Managed Entity by using the corresponding drop-down list.
1. 2.
Click the New button on the Managed Entities screen. Enter the Fully Qualified Host Name for your managed entity in the text box, and make sure the Discover Protocols check box is marked.
3.
To export WEBES configuration information for managed entities (except for access credentials), contact details, and site information associated with a WEBES node, click the Export button. A popup Export Managed Entities page provides details of the information that has been exported (see Figure 3-36 Export Managed Entities popup) and details of where the XML files have been saved.
61
To import previously exported WEBES information, click the Import button. WEBES checks for relevant XML files in particular folders and a popup Import Managed Entities page is displayed that displays details of the entities, contacts, and sites that may have been imported. Access details for each imported entity must then be manually configured.
NOTE:
62
4 Automatic Notifications
This chapter describes how SEA can automatically notify you or HP Services whenever automatic analysis has detected an event.
You can enable or disable any of the listed notifications by changing the appropriate pull-down menu (on or off). To view or update additional settings, where available, you can click the link from the Setting column to display a specific notification configure page. Notifications that have been enabled are shown in green. Certain notifications only make sense to enable if the corresponding partner software is installed. In this example, the user has enabled notification of problem reports from WEBES to HP SIM, but the HP SIM software product has not been installed on the same system that WEBES is installed on. In this case, HP SIM notification is still enabled, but that row is colored red to indicate a problem. To write a test binary event to the system's event log, click the Test Event button. This is a good way to verify that notifications are working as expected, because the test event will be recognized, analyzed, and notifications sent for all enabled notification types. Clicking the Test Event button is equivalent to issuing the CLI command "wsea test".
63
The initial screen shows the Status of all notifications sent. In this example, one SEATEST event callout (problem report) was successfully delivered to the SMTP (email) and LOG (prob.log file) notifications in January and February, but the one in February was not able to be delivered to HP SIM, and is still in transit (notification being attempted and retried) to Microsoft Operations Manager (MOM). You can click the link under the ID column to view the problem report, regardless of which notifications succeeded or failed. Also regardless of which notifications succeeded or failed, you can choose to explicitly and immediately dispatch any problem report to any desired notification type, even if you have not enabled that notification type. To dispatch a problem report, click the Dispatch tab at the bottom of this page. The page will look similar to this example: Figure 4-3 WEBES Notification Dispatch
64
Automatic Notifications
To dispatch one or more problem reports, click on the problem reports shown in the Step 1 list, using the standard Shift-click and Ctrl-click for multiple selections. Then, to dispatch these problem reports to one or more notification types, click on the types shown in the Step 2 list, using the standard Shift-click and Ctrl-click for multiple selections. Click the Send Notifications button to send the selected problem reports to the selected notifications. Another feature of this page is to remove problem reports from the list shown in the Status tab (the previous screen). Using the standard Shift-click and Ctrl-click for multiple selections, select the problem reports you wish to remove, in the Step 1 list, and click the Remove Problem Reports From Notification History button. You will no longer be able to see the notification status, the content of the problem report, or dispatch it to a notification type, after you click this button.
4.6.1 Settings
During installation, WEBES prompts for the following: SMTP server address Sender's e-mail address List of e-mail addresses that you want to send reports to
Without valid addresses, SEA cannot send email notifications. After installation, you can change these settings using the Command Line Interface or the Web Interface. A "valid" address depends on what the SMTP server decides is valid. Some servers check the validity of the username or the domain, or both. Some servers return errors where others silently discard the email if it does not consider an address valid. WEBES does not check nor constrain the format or validity of addresses.
4.4 Service Events vs. Info Events 65
Check the validation policies of the SMTP server you use, if you suspect that WEBES emails are not being delivered. If WEBES is connected to HP SIM, then the SMTP server name and port, and the sender's email address supplied by SIM overrides the local WEBES value for these settings. The email recipients are the union of the HP SIM supplied recipients and the WEBES recipients. If WEBES is not connected to HP SIM, then the local WEBES settings are used. If no email sender's address is specified, then a system generated one is used. This will be in the form: <sysname>.webes@<domain> where <sysname> is the local system name, and <domain> is the part of the SMTP server address following the first period, which is not necessarily the domain of the system on which WEBES is installed. For example, if the SMTP server is "smtpserver1.acme.com" and the local host name is "slater.acmelab.com", then: derived sender's address = slater.webes@acme.com
Multiple email addresses may be entered in the Recipients and CC fieldsuse a semi-colon between each email address.
66
Automatic Notifications
If HP SIM is connected, then the SMTP server name and port, and the "from email address" fields cannot be changed. They automatically revert to the HP SIM supplied values as soon as the Apply Changes button is pressed. The Test Email button generates a test email which is sent using the latest applied email settings. WEBES will attempt to send the test email directly to the nominated SMTP serverit does not rely on WEBES notification and it will not appear in any Problem Report displays. A results page is displayed when the test email has been sent. To validate the SMTP settings, check that all nominated recipients and CC addressees have received the test email. To write a test binary event to the system's event log, click the Test Event button. This is a good way to verify that notifications are working as expected, because the test event will be recognized, analyzed, and notifications sent for all enabled notification types. Using the Test Event button is equivalent to issuing the CLI command wsea test.
67