This release notes reflects the changes made to the EMS Hardware Monitors for HP-UX 11.23, Dec 2005 release.
- Overview
- Configuring Hardware Monitoring
- Changes
- Known Problems
- Monitors Provided
- Monitor Dependencies
- Product Documentation
- SD Product Structure
- Reporting Defects
Note: No tape drives are supported by Online Diagnostics on HP-UX. Although some of the Support Tools Manager (STM) tools may function with tape drives, they are not supported. The diagnostic tools and utilities that support these devices are HP StorageWorks Library and Tape Tools (L and TT). These tools are available at http://www.hp.com/support/tapetools.
Included with the OnlineDiag bundle of support tools are the EMS Hardware Monitors - an important tool for maintaining system availability. The EMS Hardware Monitors allow you to monitor the operation of a wide variety of hardware resources and be alerted immediately if any failure or other unusual event occurs.
Hardware event monitoring provides a high level of protection against system hardware failure. By using hardware event monitoring, you can eliminate the most undetected hardware failures that could interrupt system operation or cause data loss.
Configuring Hardware Monitoring
The EMS Hardware Monitors are installed at the same time as the Support Tools Manager (STM). Once the monitoring software is installed, monitoring is automatically enabled.
By default, event messages with severity levels major, warning, serious and critical generated by the monitors will be conveyed in the following ways:
All events will be stored in /var/opt/resmon/log/event.log file.
- Written to /var/adm/syslog/syslog.log
- Sent to EMAIL address root
To configure, enable, or disable hardware event monitoring, run the monitoring request manager: /etc/opt/resmon/lbin/monconfig .
The Peripheral Status Monitor (PSM) and the Kernel Resource Monitor (krmond) are configured differently. They use the Event Monitoring Service (EMS) Graphical User Interface (GUI). See: http://docs.hp.com/en/diag/ems/ems_gui.htm
The following change applies to systems based on PA-RISC platform only:
The following change applies to systems based PA-RISC or Itanium platform:
- JAGaf61014
If there is a mistake in the suppression time of the client configuration file, events are generated every time a monitor starts, irrespective of the flag value.
- JAGaf71186
If the system time is changed to a time that is earlier than the last boot time, all the monitors generate the following errors when the moncheck utility is executed.>/StorageAreaNetwork/events/SAN_Monitor ... NOT READY. >/system/events/cpu/cmc ... NOT READY. >/system/events/cpu_hitachi/cmc ... NOT READY. >/system/events/cpe ... NOT READY. >/storage/events/disks/default ... NOT READY. >/storage/events/disks_hitachi/default ... NOT READY. >/adapters/events/TL_adapter ... NOT READY. >/connectivity/events/hubs/FC_hub ... NOT MONITORING. (Possibly there is no hardware to monitor.) >/connectivity/events/switches/FC_switch ... NOT MONITORING. (Possibly there is no hardware to monitor.) >/adapters/events/iscsi_adapter ... NOT READY. >/system/events/dm_memory_asama ... NOT READY.This is to indicate that monitoring is not possible in such a scenario. The monitors are now enhanced to overcome this limitation. They continue monitoring even if the system time is changed to a time that is earlier than the last boot time.- Memory Page Deallocation (MPD) and the memlogd daemon are not implemented on RX 4610 systems.
- Changes made to the EMS Hardware Monitors for the the Dec 2005 release include the following:
This section describes the changes made to individual monitors. Monitors are listed in alphabetical order.
- Chassis Code Monitor (dm_chassis)
The following changes apply only to systems running on the PA-RISC platform:
- JAGaf69452
The Probable Cause/Recommended Action of Event 1839 is modified.- JAGaf65955
Event Summary of Event 1352 is modified.- JAGaf65955
The Problem Description of Event 1352 is modified. It read "The battery on the SBCH is below the safe threshold. The battery can be replaced online." It now reads "The battery on the SBCH is below the safe threshold".- CMC Monitor (cmc_em)
The following change applies only to systems running on the Itanium platform:
- The cmc_em monitor and tools now support Intel Itanium 2 processors with the Hyper-Threading feature.
- Core Hardware (dm_core_hw)
- N/A
- Core Hardware for Itanium (ia64_corehw)
The following changes apply to systems running on either the Itanium platform or the PA-RISC platform:
- JAGaf46420
The severity of Event 115002 and Event 115003 has been changed to Major Warning and Minor Warning respectively.- JAGaf54242
The ia64_corehw monitor experiences a memory leak on non-cellular systems. This problem is fixed now.- JAGaf61202
Event 104011 is generated when a redundant source of power supply is removed. The Generic Message of this event reads Redundancy regained. This is incorrect. The problem is fixed. The correct Generic Message now reads Redundancy lost.- JAGaf70658
The ia64_corehw monitor now reports events related to temperature on rp3440 and C8000 systems.- JAGaf76908
The ia64_corehw monitor configuration file is modified. It now states that the watchdog timer Power_Down and Power_Cycle settings are not applicable on cellular systems.- Core Hardware Monitor -- Asama (ipfcorehw_asama)
- N/A
- Core Hardware Monitor -- Hitachi (ipfcorehw_hitachi)
- N/A
- CPE Monitor (cpe_em)
The following change applies only to systems running on the Itanium platform:
- The CPE Monitor now supports servers based on the HP sx2000 chipset.
- CPU Monitor (lpmc_em)
The following change applies only to systems running on the PA-RISC platform:
- JAGaf56907
Event Summary of Event 100906 to Event 100910 is modified. The Dynamic Processor Resilience Action Threshold reads 32 instead of 1. This problem is fixed.- CPU Monitor -- Hitachi (cmc_em_hitachi)
- N/A
- Disk Array FC60 Monitor (fc60mon)
The following changes apply only to systems running on the Itanium platform:
- JAGaf69055
The fc60mon monitor is modified to include the -k option during ioscan. This option reduces the time taken to scan devices in the Storage Array Network (SAN).- JAGaf52161
Event 6 is generated even if fc60 is working fine. This problem is fixed. Entry for event 6 in the default_fc60mon.clcfg file is modified to report controller failure events as and when they occur.- JAGaf52955
The fc60mon monitor does not generate an event when a disk fails in a Fibre Channel (FC60) array that is enabled with Global Hotspace (GHS). This problem occurs inspite of fixing the following:This problem is fixed.
- JAGae03024
- JAGae62769
- JAGae87110
The fc60mon monitor exits causing registrar.log messages. This problem is fixed. The monitor now logs correct signals to registrar.log avoiding the creation of spurious logs.- JAGaf74551
The fcmon monitor now alerts users before resetting the controller. Also, a script is provided for resetting the controllers.- Disk Monitor (disk_em)
- N/A
- Fibre Channel Adapter (ql_adapter)
- N/A
- Fibre Channel Adapter Model A5158 Monitor (dm_TL_adapter).
- N/A
- Fibre Channel SCSI Multiplexer (dm_fc_scsi_mux)
- N/A
- Fibre Channel Switch (dm_fc_sw)
- N/A
- Forward Progress Log (FPL) Monitor (fpl_em)
- N/A
- High Availability Disk Array Monitor (ha_disk_array)
- N/A
- High Availability Storage System (dm_ses_enclosure)
- N/A
- iSCSI Driver Subsystem Monitor (dm_iscsi_adapter)
- N/A
- Kernel Resource Monitor (krmond)
- N/A
- Memory (dm_memory)
The following change applies to systems based on PA-RISC platform only:
- JAGaf62382 The dm_memory monitor terminates when the failure of the getsockname() call is accompanied by the errno EINTR. The monitor terminates because the dm_memory process receives a signal when it is in a blocked state. However, the system call can be reinvoked to procure a socket critical for the monitor. A maximum of 5 attempts are allowed.
- Memory IA64 (memory_ia64)
The following changes apply only to systems running on the Itanium platform:
- The memory_ia64 monitor does not run on the HP Virtual Machine guest operating system because the guest operating system does not interact with the physical hardware. As a result, the guest operating system does not require monitoring.
- The memory_ia64 monitor now supports servers based on the HP sx2000 chipset.
- Memory Monitor -- Hitachi (ipfmemory_hitachi)
- N/A
- MSA1000 Storage Disk Array Monitor (msamon)
The following changes apply to systems running on either the Itanium platform or the PA-RISC platform:
- JAGaf48231
The msamon monitor is enhanced to monitor MSA1500 with Active-Active firmware.- JAGaf73262
Event Summary of Event 500 and Event 501 is modified.- Peripheral Status Monitor (psmmon)
- N/A
- RAID Adapter (dm_raid_adapter)
The following change applies to systems running on either the Itanium platform or the PA-RISC platform:
- JAGaf69660
Severity of Event 2 is changed from Critical to Information.- Remote Monitor (RemoteMonitor)
- N/A
- SCSI Disk Monitor (scsi_disk)
- N/A
- System Status Monitor (sysstat_em)
The following change applies to systems running on either the Itanium platform or the PA-RISC platform:
- If the guest operating system is detected, the sysstat_em monitor is disabled.
- UPS Monitor (dm_ups)
- N/A
Changes to Platform and Interface
- N/A
Customer-Viewable Interface Changes
- N/A
- If the System Fault Management product is installed on your system, you must complete the following steps, before and after updating the OnlineDiag product:
- Type the following command to shut down the System Fault Management subsystem:
/sbin/init.d/cimserver stop- Perform the OnlineDiag update.
- Type the following command to restart the System Fault Management subsystem after the update is completed:
/sbin/init.d/cimserver start- If the maxssiz_64bit kernel parameter is set below the default value of 0x800000, it can cause the lpmc_em monitor to abort.
- The Memory Page Deallocation (MPD), which runs on most current HP-UX computer systems, does not work on RX 4610 systems. The activity log for memlogd includes a message that reads unsupported device.
MPD cannot be implemented on the RX 4610 system because the system's design does not allow the memlogd daemon to run on it.
For the Dec 2005 release of HP-UX 11.23, the following monitors are provided:The following monitors are NOT provided:
- CMC Monitor (cmc_em).
- Core Hardware (dm_core_hw)
- Core Hardware for Itanium (ia64_corehw)
- Core Hardware Monitor -- Asama (ipfcorehw_asama)
- Core Hardware Monitor -- Hitachi (ipfcorehw_hitachi)
- CPE Monitor (cpe_em)
- CPU Monitor (lpmc_em)
- CPU Monitor -- Hitachi (cmc_em_hitachi)
- Disk (disk_em)
- Disk Array FC60 (fc60mon)
- Fibre Channel Adapter (ql_adapter)
- Fibre Channel Adapter Model A5158 (dm_TL_adapter)
- Fibre Channel SCSI Multiplexer (dm_fc_scsi_mux)
- Forward Progress Log (FPL) Monitor (fpl_em)
- High Availability Disk Array (ha_disk_array)
- High Availability Storage System (dm_ses_enclosure)
- iSCSI Driver Subsystem Monitor (dm_iscsi_adapter)
- Kernel Resource Monitor (krmond)
- Memory (dm_memory)
- Memory IA64 (memory_ia64)
- Memory Monitor -- Hitachi (ipfmemory_hitachi)
- MSA1000 Storage Disk Array Monitor (msamon)
- Peripheral Status Monitor (psmmon)
- RAID Adapter (dm_raid_adapter)
- Remote Monitor (RemoteMonitor)
- SCSI Disk Monitor (scsi_disk)
- System Status (sysstat_em)
- UPS (dm_ups)
- dm_FCMS_adapter
- fw_disk_array: hardware not supported on the system
- scsi123_em: hardware not supported on the system
For detailed information about the products and the monitors supporting them, and additional dependencies, see the Diagnostics section of Hewlett-Packard's online documentation Web site: http://docs.hp.com/hpux/diag/ .
For a list of the current required patches, see the DIAGNOSTIC.readme file for this release.
Current monitor requirements are described in the Requirements and Supported Products file. Requirements are also listed in Chapter 2 of the EMS Hardware Monitors User's Guide.
For the latest and most complete information on EMS Hardware Monitors and the Support Tools Manager (STM), see the documentation of Online Diagnsotcs at http://docs.hp.com/en/diag/
At this site, you will find Overviews, Tutorials, Quick Reference Cards, Frequently Asked Questions (FAQs), and other material.
For complete information on installing and using EMS Hardware Monitors, as well as a list of supported hardware, refer to the "EMS Hardware Monitors User's Guide" available at the mentioned site.
For the most current information on HP-UX 11.23 diagnostics, see the following Web pages at the Diagnostics site:
- "DIAGNOSTICS.readme for HP-UX 11.23 (Dec 2005)" at:
http://docs.hp.com/en/diag/st/str_0512.htm- "Release Notes for STM on HP-UX 11.23 (Dec 2005)" at:
http://docs.hp.com/en/diag/stm/str_0512_1123.htm- "Release Notes for EMS Hardware Monitors on HP-UX 11.23 (Dec 2005)" at:
http://docs.hp.com/en/diag/ems/emr_0512_1123.htmThe EMS Hardware Monitors are installed as part of the OnlineDiag bundle (product number B4708AA). In addition, they require the EMS framework, product number B7609BA.
For information on the STM product, refer to the STM release notes file /usr/sbin/stm/Rel_NOTES.STM.
SD Bundle: OnlineDiag Description: On-line Diagnostic System (Series 800/700) SD PRODUCT: Sup-Tool-Mgr Description: Support Tools Manager for HP-UX Systems SD SUB-PRODUCT: Manuals Description: Support Tools Manager Manual Pages FILESET: RELEASE_NOTES Description: HPUX STM Release Notes FILESET: STM-MAN Description: HPUX STM Manual Pages SD SUB-PRODUCT: Runtime Description: STM Manual Runtime FILESET: STM-CATALOGS Description: HPUX STM Shared Libraries FILESET: STM-SHLIBS Description: HPUX STM Shared Libraries FILESET: STM-UI-RUN Description: HPUX STM User Interface FILESET: STM-UUT-RUN Description: HPUX STM Unit Under Test Runtime SD PRODUCT: EMS-Config Description: EMS Config FILESET: EMS-GUI Description: Event Monitoring Service Graphical User Interface SD PRODUCT: EMS-Core Description: EMS Core Product FILESET: EMS-CORE Description: Event Monitoring Service Core FilesYou can report defects by filing a request on CHART. The name of the project is diag.hw_mon.hpux. If you do not have access to CHART, contact your local HP representative to file a defect on your behalf.