These release notes cover the September 2003 release of Support Plus for HP-UX 11.0/11i running on S800/S700 systems.
- Overview
- Configuring Hardware Monitoring
- Documentation
- Changes
- Known Problems
- Monitors Provided
- Monitor Dependencies
- Defect Reporting
- SD Product Structure
NOTE: As of the September 1999 release, the name of the Diagnostic/IPR Media has been changed to Support Plus. In addition, the format has changed so that there is a separate CD-ROM for each version of the operating system (e.g., HP-UX 11i).
NOTE: The HP Storageworks SDLT 160/320 GB Tape Drive and HP Ultrium 460 External Tape Drive are NOT SUPPORTED by the OnlineDiag product. Even though some STM tools may function with these devices, they are still NOT SUPPORTED. The diagnostic tools and utilities that DO SUPPORT these devices are the HP StorageWorks Library and Tape Tools (L&TT). These tools can be downloaded, free of charge, at:
http://www.hp.com/support/tapetoolsIncluded on the Support Plus CD-ROM 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 products and be alerted immediately if any failure or other unusual event occurs. Hardware event monitoring is available to users running HP-UX 11i and 11.00 (IPR 9902 and later).
Hardware event monitoring provides a high level of protection against system hardware failure. By using hardware event monitoring, you can virtually eliminate 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. Once the monitoring software is installed, monitoring is automatically enabled.
By default, messages regarding major warning, serious and critical events that occur on hardware being monitored will be:
All events will be stored in /var/opt/resmon/log/event.log.
- 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 The Kernel Resource Monitor (krmond) are configured differently. They use the EMS GUI. See: http://docs.hp.com/hpux/onlinedocs/diag/ems/ems_gui.htm
For the latest and most complete information on EMS Hardware Monitors and the Support Tools Manager (STM), see the Web page "Diagnostics":
http://docs.hp.com/hpux/diag/At this site, you will find Overviews, Tutorials, Quick Reference Cards, Frequently Asked Questions (FAQs), and much 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 above site. An electronic copy of this book is also included on the Support Plus CD-ROM in the <mount_point>/DIAGNOSTICS directory.
Changes in the EMS Hardware Monitors for the the September 2003 release include:
- Changes to Multiple Monitors
- Changes to Individual Monitors
- Changes to Platform and Interface
- Customer-Visible Interface Changes
- N/A
Changes to Individual Monitors
Changes to each monitor are described below. (Monitors are listed in alphabetical order.)
- AutoRAID Disk Array (armmon).
- N/A
- Chassis Code Monitor (dm_chassis).
- JAGae76349
The chassis codes have been updated for this release.- CMC Monitor (cmc_em).
- N/A
- Core Hardware Monitor (dm_core_hw)
- N/A
- Core Hardware for Itanium (ia64_corehw).
- JAGae81900
Starting with this release, the ia64_corehw monitor will perform the following additional tasks on PA systems:
- Register with diaglogd to receive PCI card error data
- Receive the data when it is available on the FIFO
- CPU Monitor (lpmc_em).
Note: As of the June 2002 release, the LPMC Monitor (lpmc_em) was renamed to "CPU Monitor". The binary name is still lpmc_em. The name was changed to reflect the monitor's enhancement to check floating-point functionality in the CPU.
- JAGae57006
Fixed a problem with the lpmc_em monitor: on 32-bit systems, the lpmc_em monitor was logging errors related to 64-bit systems.- JAGae63617
lpmc_em did not handle an invalid CPU data file.The cpu_data_file is now recreated, when the entries in the data file are found to be inconsistent with the actual hardware present on the system.
- Events 100601-100604 and 100661-100664 are disabled by default because they are insignificant.
- Disk Array FC60 Monitor (fc60mon).
- N/A
- Fast Wide SCSI Disk Array (fw_disk_array)
- N/A
- Disk Monitor (disk_em).
- N/A
- Fibre Channel Adapters (dm_FCMS_adapter).
- N/A
- Fibre Channel Adapter Model A5158 Monitor (dm_TL_adapter).
- N/A
- Fibre Channel Adapter Model A6826A Monitor (dm_QL_adapter)
- N/A
- Fibre Channel SCSI Multiplexer (dm_fc_scsi_mux).
- N/A
- Fibre Channel Switch (dm_fc_sw).
- N/A
- High Availability Disk Array Monitor (ha_disk_array).
- JAGae79849
ha_disk_array did not generate a disk removal event in HPUX 11.11.- High Availability Storage System (dm_ses_enclosure)
- N/A
- iSCSI Device Adapter (dm_iscsi_adapter)
- N/A
- Kernel Resource Monitor (krmond)
- N/A
- LPMC Monitor (lpmc_em).
As of the June 2002 release, the LPMC Monitor (lpmc_em) was renamed to "CPU Monitor". The binary name is still lpmc_em. The name was changed to reflect the monitor's enhancement to check floating-point functionality in the CPU. For more information, see CPU Monitor (lpmc_em).- Memory Monitor (dm_memory).
- JAGae70912
The entry for event # 6000 in the default_dm_memory.clcfg was incorrect. Whenever the dm_memory monitor tried to generate this event, the following error message was logged in /var/opt/resmon/log/api.log:"event occurred at <date> Process ID: <pid> (/usr/sbin/stm/uut/bin/.../dm_memory) Log Level: Error Neither operator field in the following entry in client configuration file (/var/stm/config/tools/monitor/default_dm_memory.clcfg) are used, one must be used: (EQ:6000:CRITICAL:TRUE:1440:NOT_USED:1:NONE:NO_OP:NO_OP:NONE)"This has now been fixed.- JAGae70887
When memory Single Bit Errors were seen in quick succession, memlogd encountered communication errors, while reporting about them to dm_memory. A message was logged in the memlogd activity log, indicating that the socket communication between memlogd and dm_memory failed. This has now been fixed.- Peripheral Status Monitor (PSM/psmmon).
- JAGae60292
The down severity operators >= and <=, specified in the psmcfg file, were being incorrectly interpreted as = by the code. This problem, which relates to psmctd, has now been fixed.- Remote Monitor (RemoteMonitor).
- JAGae81349
RemoteMonitor is logging a debug message to the registrar. This has been fixed.- JAGae73371
The RemoteMonitor send_test_event fails after the hardware monitors are restarted. This has been fixed.- SCSI Card Monitor (scsi123_em).
- N/A
- SCSI Cascade Monitor (scsi_cascade).
- N/A
- SCSI Disk (scsi_disk).
- N/A
- SCSI Tape Monitor (dm_stape).
- N/A
- System Status Monitor (sysstat_em).
- An enhancement was made to the STM platform, so that systems configured with IPv6 addresses are now supported. Remote connections are allowed only if the connecting IPF system (11.23) is B.40.00 or greater, or the connecting PA system (11.0/11.11) is A.42.00. Otherwise, the connection request will timeout and be refused, since the remote system will get an unrecognized request.
- UPS Monitor (dm_ups).
- N/A
Changes to Platform and Interface
- N/A
Customer-Visible Interface Changes
- N/A
CAUTION: UPS Monitor May Need a PatchIn some cases, the UPS monitor (dm_ups) will not function and will instead generate event 45 (formerly event 42) with the text:
Probable Cause / Recommended Action: The monitor was unable to locate the fifo pipe that should have been created by ups_mond. Therefore, information about the ups cannot be sent to the monitor. You need version (80.1.2.3) of ups_mond or greater. To update your system with the correct version of ups_mond, install the following patch: HPUX 11.11 : PHCO_23832To fix the problem, load the indicated patch or load the HWE patch bundle which contains this patch. For HP-UX 11i, the ups_mond patch PHCO_23832 is also distributed on the Sept 01 OE.This problem will affect most systems with a UPS when the September 2001 diagnostics are installed. The only systems not affected will be those which are being updating from certain versions of the diagnostics (September 2000 through March 2001) and which do not have patch PHCO_19040 (HP-UX 11.00) installed.
CAUTION: Monitoring Changes for disc30, sdisk and disk array devicesAs of IPR 9902 (Feb 99 release), there has been a change to the way that monitoring is done for disc30, sdisk and the HA Disk Array Models 10, 20, and 30FC.
Formerly, the "diaglogd exec" programs (pdisc30_exec and psdisk_exec) handled driver error entries for these devices.
As of IPR 9902, these programs have been deleted and their functionality is now provided by the EMS Hardware Monitors.
If you had customized the configuration files for the diaglogd exec programs (disk30_exec.cfg and sdisk_exec.cfg) you may wish to re-configure the EMS Hardware Monitors to achieve the same results.
CAUTION: Compatibility Problem with EMS-Related Products (ServiceGuard, HA Monitors, etc.)If you install the OnlineDiag bundle (Dec 99 or later) onto a computer running older revisions of EMS-related products, these products may experience compatibility problems. Affected products include MC/ServiceGuard, ServiceGuard OPS Edition and High Availability Monitors. The only critical problems occur with the following versions:
MC/ServiceGuard A.10.10, A.11.01, A.11.03 ServiceGuard OPS Edition A.11.02, A.11.03Support Tools and the EMS hardware monitors are not affected. For complete information, see EMS Incompatibility Problem.
Monitors are provided to support the following:
- AutoRAID Disk Array (armmon)
- Chassis Code Monitor (dm_chassis)
- CMC Monitor (cmc_em).
- Core Hardware (dm_core_hw)
- Core Hardware for Itanium (ia64_corehw)
- CPU (lpmc_em)
- Disk (disk_em)
- Disk Array FC60 (fc60mon)
- Fast Wide SCSI Disk Array (fw_disk_array)
- Fibre Channel Adapters (dm_FCMS_adapter)
- Fibre Channel Adapter Model A5158 (dm_TL_adapter)
- Fibre Channel Adapter Model A6826A Monitor (dm_QL_adapter)
- Fibre Channel Arbitrated Loop Hub (dm_fc_hub)
- Fibre Channel SCSI Multiplexer (dm_fc_scsi_mux)
- Fibre Channel Switch (dm_fc_sw)
- High Availability Disk Array (ha_disk_array)
- High Availability Storage System (dm_ses_enclosure)
- iSCSI Device Adapter (dm_iscsi_adapter)
- Kernel Resource (krmond)
- LPMC (lpmc_em) renamed to "CPU Monitor" as of the June 02 release
- Memory (dm_memory)
- Remote (RemoteMonitor)
- SCSI Card (scsi123_em)
- SCSI Cascade (scsi_cascade)
- SCSI Disk (scsi_disk)
- SCSI Tape Devices (dm_stape)
- System Status (sysstat_em)
- UPS (dm_ups)
In addition, the Peripheral Status Monitor (PSM) is provided to monitor the current status of the products supported by the above list.
For detailed information concerning which products are supported by which monitors and additional dependencies, check the "Diagnostics" section of Hewlett-Packard's online documentation web site: http://docs.hp.com/hpux/diag/ .
Several of the monitors have special requirements, such as patches or certain versions of firmware. In particular:
For a list of the current required patches, see the DIAGNOSTIC.readme file for this release.
- The Fibre Channel Arbitrated Loop Hub Monitor and the Fibre Channel Switch Monitor require special configuration which is described in their data sheets in the "EMS Hardware Monitors User's Guide" (chapter 6). A patch is also required.
- A patch is required if your system includes an HP SureStore E Disk Array FC60. This patch is required to to run the EMS hardware monitor (fc60mon) or STM tools for this device.
Current monitor requirements are described in the "Supported Products" page under "EMS Hardware Monitors" at http://docs.hp.com/hpux/diag . Requirements are also listed in chapter 2 of the manual "EMS Hardware Monitors User's Guide".
Use CHART to report defects in the EMS Hardware monitors. The project name is diag. If you don't have access to CHART, contact an HP representative to enter a defect for you.
The EMS hardware monitors are installed as part of the OnlineDiag bundle (product number B4708AA). In addition, they utilize the EMS framework, product number B7609BA.
Note: EMS Hardware Monitors are installed as part of the STM-UUT-RUN Fileset. However, the EMS Hardware Monitors are dependent on the EMS-Core and EMS-Config products and additional filesets in the Sup-Tool-Mgr Product.
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 Files