SFM Release Notes for HP-UX 11i v3 September 2012 web release

For information about the defect fixes, see Defect fixes.
Supported EMS hardware monitors
SFM is the default monitoring mode. However, you can switch to the OnlineDiag monitoring mode.
For information on how to switch to the OnlineDiag mode, see the SFM Administrator's Guide at
http://www.hp.com/go/hpux-diagnostics-docs
NOTE: OnlineDiag monitoring mode is not supported on HP Integrity BL860c i2, BL870c
i2 & BL890c i2 Server Blades, rx2800 i2, HP Integrity Superdome 2, and
Intel Itanium 9500 Processor Series, . Therefore, switching between modes will not
be available on these HP Integrity Servers.
The Event Monitoring Service (EMS) wrapper provider receives events generated by the EMS
hardware monitors. The following EMS hardware monitors are supported on HP 9000 servers
running the HP-UX 11i v3 operating system:
• LPMC (now CPU) (lpmc_em)
• Memory (dm_memory)
• Core HW (dm_core_hw)
• Chassis Code (dm_chassis)
• IPMI Forward Progress Log Monitor (fpl_em)
The following EMS hardware monitors are supported on HP Integrity servers running the HP-UX
11i v3 operating system:
• Corrected platform error monitor (cpe_em)
• IPMI forward progress log monitor (fpl_em)
• CMC monitor (cmc_em)
• Itanium core hardware monitor (ia64_corehw)
• Itanium memory monitor (memory_ia64)
NOTE: All of EMS hardware monitors are not supported by EMS wrapper provider included in
SFM product. For information on other providers like I/O and Storage, see HP WBEM providers
at http://www.hp.com/go/hpux-wbem-docs
Defect fix
• QXCR1001235166
A critical log message seen in sfm.log due to libIO API call failure.
Problem: On a vPar host, if dedicated guest is running and LIBIO patch PHKL_42903 is not
installed, then SFM will log the following critical message in sfm.log
CPUAL_MODULE 256 CRITICAL 12694 20 LIBIO routine failed. Reason: Error accessing data
because of Internal Error.
Resolution: This problem is fixed. you need to install the LIBIO patch PHKL_42903.
• QXCR1001197605
If db connection times out during a transaction, the transaction model is broken.
Problem: Loss of database connection during certain operations results in inconsistent state
of the database and failure to archive events. The following messages is displayed in the
sfm.log in the event of this failure.
ERROR: duplicate key value violates unique constraint "rawlog_pkey"
4 Contents