Event Monitoring Service Version A Release Notes

Transcription

2 Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained in this document 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. UNIX is a registered trademark of The Open Group. 2

3 1 Event Monitoring Service Version A Release Notes Chapter 1 3

4 Announcement Announcement Event Monitoring Service (EMS) A is being released for use on the Integrity and PA-RISC platforms with the HP-UX 11i v3 operating system. You can use EMS together with one or more EMS monitors to monitor various system resources. The EMS product includes the framework and general monitors. You can configure EMS to monitor system resources through monitoring requests. In the monitoring request, you define how and when you want to be notified about system resource events. EMS can enhance your high availability environment by warning you about a single point of failure before it can make an application unavailable. Monitors that register with the EMS framework are automatically discovered and displayed on the EMS interface. All monitors are bundled with EMS dictionary files and can be found in the /etc/opt/resmon/dictionary directory. Event Monitoring Service (EventMonitoring) version A includes media, license, and manual. 4 Chapter 1

5 Product Overview Product Overview Event Monitoring Service (EMS) is a framework for monitoring system resources which includes configuring, checking resource status, and sending notifications when configured conditions are fulfiled. EMS contains the following components: EMS Framework - The EMS framework provides discovery, configuration, and notification for EMS monitors. Depending on the monitor, EMS may actively poll or it may wait for event messages. It compares the return value with the threshold configured in the request. If it matches, the framework sends notification to the source specified, through a required protocol. EMS Graphical User Interface (GUI) - You can invoke the EMS interface from the Resource Management icon in System Administration Manager (SAM). From the EMS graphical user interface (GUI), you can create, modify, and remove monitoring requests. You can also view the list of available resources that EMS has discovered on your system, and a list of all currently configured monitoring requests. EMS Command Line Interface (CLI) - You can invoke the EMS command-line interface by typing emscli with the appropriate option at the HP-UX command-line prompt. You can use the emscli command-line utility to create, modify, and remove monitoring requests. You can also view the list of available resources that EMS has discovered on your system, and a list of all currently configured monitoring requests. It is also enabled with a help feature, emscli -h, to view the usage of various options supported by emscli. For more information on the command line options supported by emscli, refer to the emscli(1m) manpage. Management Information Base (MIB) Monitors - The following Management Information Base (MIB) monitors are provided with the EMS framework: HA Cluster Monitor checks the status of clusters, nodes, packages, and services of. HA Network Interface Monitor reports the status of LAN interfaces. HA System Resource Monitor checks the number of users, the system load, and the amount of file system space. The resls and resdata EMS utilities. Chapter 1 5

6 Product Overview NOTE If you require the EMS MIB definitions to handle EMS SNMP trap notifications, you can obtain it as part of the EMS Developer s Kit available from EMS templates for HP OpenView ITO/ITO-SE, and EMS SNMP trap templates for HP OpenView NNM are also part of the EMS Developer s Kit. NOTE Textlog notification requests must specify a file in the /var/opt/resmon/log directory. If another directory is specified the default text log file, EMS displays an error message. EMS can be used with HP OpenView,, and any other software that can receive SNMP traps, TCP, or UDP protocol messages. You can write your own monitors using the EMS Developer s Kit. The manual and software can be downloaded free from the Website Select High Availability, and then choose Event Monitoring Service Developers Kit. Further Information Online versions of user guides and white papers for high availability products are available on Hewlett-Packard s HP-UX Documentation Web page at: 6 Chapter 1

7 What s in This Version What s in This Version The following changes have been made in this version: EMS is enhanced to send WBEM (Web Based Enterprise Management) indication. The WBEM indications are in addition to the notifications that EMS already supports. You can view the WBEM indications by using Event Viewer in the HP System Management Homepage (HP SMH). To open Event Viewer, complete the following steps: Step 1. Open a web browser and enter in the address bar. The login page of HP SMH is displayed. Step 2. Login using your user name and password. The home page of HP SMH is displayed. Step 3. Click Logs in the main menu available at the top of the page. The Logs page is displayed. Step 4. Click Event Viewer available in the Evweb box. Event Viewer opens and the list of events are displayed. For more information on HP SMH, see system administration documention available at: For more information on how to use Event Viewer, see the online help in Event Viewer. Chapter 1 7

8 Known Problems and Workarounds Known Problems and Workarounds There are no known problems and workarounds in this version. 8 Chapter 1

9 Compatibility Information and Installation Requirements Compatibility Information and Installation Requirements EMS must be installed on each node that you want to monitor. If you want to monitor the management station, then EMS must be installed on the management station also. Chapter 1 9

10 Compatibility Information and Installation Requirements Compatibility with HP-UX Releases Table 1-1 EMS Hardware and HP-UX Compatibility EMS Version Compatible HP-UX Releases Compatible Hardware EMS A HP-UX HP 9000 Servers EMS A.03.00, A , A.03.10, and A HP-UX HP 9000 Servers EMS A HP-UX 11i v1 HP 9000 Servers EMS A HP-UX 11i v1.6 HP Integrity Server EMS A HP-UX 11i v1 HP 9000 Servers EMS A HP-UX 11i v2 HP Integrity Server EMS A HP-UX 11i v1 HP 9000 Servers EMS A EMS A HP-UX 11i v2 September 2004 (including revisions for HP-UX 11i v2 September 2004 update) HP-UX 11i v2 (includes revision for May 2005 update) HP Integrity Server and HP 9000 Servers HP Integrity Server and HP 9000 Servers EMS A HP-UX 11i v2 HP Integrity Server and HP 9000 Servers EMS A HP-UX 11i v3 HP Integrity Server and HP 9000 Servers Software Requirements 10 Chapter 1

11 Compatibility Information and Installation Requirements If you are a licensed customer using EMS to configure resources as package dependencies, you must have the correct version of installed. Table 1-2 EMS Compatibility EMS Version HP-UX Release Version A HP-UX MC/ServiceGuard A.11.01, A A.03.00, A , A.03.10, and A HP-UX HP-UX MC/LockManager A.11.01, A.11.02, A MC/ServiceGuard A and later MC/LockManager A and later ServiceGuard OPS Edition A and later A HP-UX 11i v1 MC/ServiceGuard A MC/LockManager A OPS Edition A and later A HP-UX 11i Version 1.6 MC/ServiceGuard A Extension for RAC (formerly known as OPS Edition) A Chapter 1 11

12 Compatibility Information and Installation Requirements Table 1-2 EMS Compatibility (Continued) EMS Version HP-UX Release Version A HP-UX 11i v1 A Extension for RAC (formerly known as OPS Edition) A A HP-UX 11i v2 A Extension for RAC (formerly known as OPS Edition) A A HP-UX 11i v1 A Extension for RAC (formerly known as OPS Edition) A A HP-UX 11i v2 (includes revisions for HP-UX 11i v2 September 2004 update) A Extension for RAC (formerly known as OPS Edition) A Chapter 1

13 Compatibility Information and Installation Requirements Table 1-2 EMS Compatibility (Continued) EMS Version A HP-UX Release HP-UX 11i v2 (includes revisions for HP-UX 11i v2 May 2005 update) Version A Extension for RAC (formerly known as OPS Edition) A A HP-UX 11i v2 A Extension for RAC (formerly known as OPS Edition) A A HP-UX 11i v1 A Extension for RAC (formerly known as OPS Edition) A A HP-UX 11i v3 A Extension for RAC (formerly known as OPS Edition) A Chapter 1 13

14 Compatibility Information and Installation Requirements Requirements for HP OpenView Users: You must configure templates in HP OpenView ITO or NNM applications to view EMS events. To configure, download the latest templates from the web site. Select High Availability, and then choose Event Monitoring Service Developers Kit. The templates are listed in the Developer s Kit page. Instructions are provided with the templates. Hardware Requirements EMS version A runs on PA-RISC and HP-UX Integrity server platforms running HP-UX 11i v3. Disk Requirements You will need approximately 8 MB of disk space on your system to install EMS. The following EMS log files require 4 MB of disk space in the /etc/opt directory: api.log registrar.log client.log emsagent.log api.log.old registrar.log.old client.log.old emsagent.log.old An additional 2 MB disk space is required for reslog.html, and reslog.old.html for archiving monitor data. Apart from 6 MB monitor disk space, you may have to reserve additional disk space for EMS monitors logging. Memory Requirements To run EMS, memory space of approximately 3 MB is required on your system. Installing EMS EMS checks the resources for local systems only. EMS is most effective when installed and configured on all systems in your environment. 14 Chapter 1

15 Compatibility Information and Installation Requirements EMS must be installed on each node that you want to monitor. EMS can be installed on a running system in a multi-user mode. NOTE Updated monitors may have new status values that change the meaning of your monitoring requests. When you update a monitor: Check for recent updates of the EMS bundle to ensure compatibility with the new monitor. Review your existing monitoring requests to ensure that they are current and reasonable for the new monitor. The EMS bundle (EventMonitoring) version A contains the following file sets: Table 1-3 EMS Product Filesets Fileset EMS-Core.EMS-CORE EMS-Core.EMS-CORE-COM EMS-Core.EMS-MX EMS-Core.EMS-WRAPPER EMS-Core.EMS-WRAPPER-COM EMS-Config.EMS-GUI EMS-Config.EMS-GUI-COM EMS-MIBMon Description Contains the EMS framework. Contains the EMS framework man pages and catalogs, configuration scripts, start-up scripts, libraries, and EMS Agent. Provides the EMS tool definitions for integrating into ServiceControl Manager. Contains EMSHAWrapperProvider. Contains xml schema and mof files for EMSHAWrapperProvider. Provides SAM s interface to EMS. This fileset also provides the emscli command line utility. Refer to the emscli(1m) manpage for more information. Provides SAM s interface to EMS, and contains EMS GUI help files. Provides MIB (Management Information Base) monitors for cluster, networking interface, and system resources. Chapter 1 15

16 Compatibility Information and Installation Requirements You can install EMS by either using the swinstall command or use the software management tools in SAM. If you have many systems, it may be easier to install over the network from a central location. The steps to install over the network from a central location are given below: 1. Create a network depot according to the instructions in Managing HP-UX Software with SD-UX. 2. rlogin or telnet to the remote host on which you are installing EMS. 3. Install EMS from the depot. Your requests are retained when the monitors are updated, or when you re-install a monitor on top of an existing monitor. This is part of the functionality provided by the persistence client. While installing EMS, the installation process may modify /etc/services, /etc/inittab, or /etc/inetd.conf files. If the files are modified, a copy of the unmodified version is available in the /etc directory. For example, /etc/inittab will be copied to /etc/ems_inittab.old /etc/services will be copied to /etc/services.old /etc/inetd.conf will be copied to /etc/inetd.conf.old Removing EMS You have to use the swremove utility or the Software Management tools in SAM to remove EMS. Note that the monitors are persistent; that is, they are always automatically started if they are stopped. Therefore, the following warning message may be created in your log file: Could not shut down process. The following error message is displayed: File /etc/opt/resmon/lbin/p_client could not be removed. Even if you see these warnings, monitors are removed and any unwanted files are cleaned up on reboot. CAUTION When you remove EMS, all log files are also removed. If you wish to save any of the EMS log files, rename them or store them before you remove EMS. 16 Chapter 1

17 EMS and EMS HA Monitors Patch Strategy EMS and EMS HA Monitors Patch Strategy EMS is provided through releases and patches. EMS patch will contain High Availability (HA) Monitors patch as well. EMS uses PHSS_ prefix for patches. A new release contains new EMS and EMS HA Monitors features as well as fixes for known problems. For a new release of EMS and EMS HA Monitors, the following is guaranteed: Full release testing is performed prior to release. All patches from the previous release are incorporated. The new release continues as the patch stream for the previous release. New releases will be until a newer version of EMS and EMS HA Monitors becomes available on the particular OS version. In order to receive fixes for any defects found in a release after a newer version is released, you need to upgrade to the newer, supported version. A patch for a release is issued in response to a critical business problem found by you. With a patch, the following is guaranteed: Patch-specific release testing is performed prior to posting the patch. Existing functionality will continue to operate without modification. All fixes from the previous patch are incorporated. EMS and EMS HA Monitors Compatibility with HP-UX Releases The following table provides information about HP-UX releases that must be used with the supported versions of EMS and EMS HA Monitors. Only the latest EMS and EMS HA Monitors release on an operating system is continued to be. Table 1-4 EMS and EMS HA Monitors Compatibility with HP-UX Releases EMS / HA Monitors Release A Support Status HP-UX Release Compatibility Chapter 1 17

18 EMS and EMS HA Monitors Patch Strategy Table 1-4 EMS and EMS HA Monitors Compatibility with HP-UX Releases EMS / HA Monitors Release A xx A A A A A A A A A A A A Support Status Current Release HP-UX Release Compatibility i v1 (B.11.11) 11i v1 (B.11.11) 11i v1 (B.11.11) 11i v1.6 (B.11.22) 11i v2 (B.11.23) 11i v2 (B September 2004) 11i v2 (B May 2005) 11i v2 18 Chapter 1

19 EMS and EMS HA Monitors Patch Strategy Table 1-4 EMS and EMS HA Monitors Compatibility with HP-UX Releases EMS / HA Monitors Release A A Support Status Current Release Current Release HP-UX Release Compatibility 11i v1 11i v3 Chapter 1 19

20 Patches and Fixes in this Version Patches and Fixes in this Version Fixes and Changes JAGag42000 was fixed in this version. 20 Chapter 1

21 Software Availability in Native Languages Software Availability in Native Languages EMS version A does not provide native language support. However, separate native language versions of documentation are available as part of bundle EventMonitoring with the following options: ABA: American English ABJ: Japanese Chapter 1 21

22 List of Documents available with the Product List of Documents available with the Product The following documents are available with EMS version A : Event Monitoring Service Release Notes Using the Event Monitoring Service manual These documents are available on 22 Chapter 1