Event Monitoring Service Version A.04.20.11.01, A.04.20.23.01, and A.04.20.31.01 Release Notes

from the HP Software Depot web site at https://h20392.www2.hp.com/portal/swdepot/
try.do?productNumber=EventMonitoring. Such fixes will be included in the EMS product on
the AR/OEUR media at a minimum of once each year.
In the support mode the following is applicable:
• No new EMS Monitors will be developed. Customers are encouraged to develop WBEM
provider based monitors using the SysFaultMgmt framework rather than developing EMS
monitors.
• Monitoring for new platforms will be accomplished through WBEM based monitoring only
using the SysFaultMgmt Product.
• EMS Developers Kit will no longer be shipped with HP-UX 11i v3.
For HP-UX 11i v3 you can download the latest templates from the HP Software Depot web
site at http://www.hp.com/go/softwaredepot. In the main page of the Software Depot, select
High Availability under Product Category. In the High Availability page that opens, select
Event Monitoring Service (EMS) Developer's Kit. The templates are listed in the
Developer’s Kit page. Instructions are provided with the templates. To download the
templates, click the Receive for Free button at the top or the bottom of the page. Select
HP-UX 11.23 version A.04.20 when you select the product Specifications.
For more information about EMS Future Strategy, see the 05/08 Event Monitoring Service (EMS)
Release Support Model news update available at http://www.hp.com/softwarereleases/
releases-media2/proginfo/EMS_Future_Direction_0408.pdf
Fixes in this Version
The following defects are fixed in this release:
• QXCR1000576454 - EMS registrar process can run into a tight loop thus using 100% CPU
time when an EMS monitor does not read from a named pipe that is used to communicate
with EMS registrar.
The fix restricts the number of rewrite attempts to 5 before declaring the attempt to write
to the pipe as failed.
• QXCR1000580508 – many registrar processes after running stress tests. When a system is
heavily stressed, the responses from registrar are delayed and the clients waiting on the
response time-out . In this case, the client assumes registrar is not responding and opens a
new connection with the registrar, without closing the earlier connection. This causes the
registrar process buildup.
• QXCR1000587084 – core file from cimprovider found after 1131.0709 IC310 update. During
an update the cimserver is stopped and the cimprovider command is in an inconsistent
state. Any calls to cimprovider command causes it to dump core.
EMS scripts now check whether cimserver is running, before calling cimprovider command.
• QXCR1000794678 – Serviceguard (SG) should be able to register Monitoring Request with
64-bit EMS monitors. The path to the SG library which contained the notification function
called by EMS, was hardcoded to a 32 bit path. When SG tries to register a request for a
resource, which is monitored by a 64 bit monitor, the registrar attempts to locate a 64 bit SG
library in the 32 bit path.
This is resolved to lookup the correct library in the latest EMS framework bits.
12 Event Monitoring Service Version A.04.20.11.01, A.04.20.23.01, and A.04.20.31.01 Release Notes