These release notes covers the September 2001 release of the Support Tools (diagnostics) for HP-UX 11i V1.5.
- Overview
- Configuring Hardware Monitoring
- Documentation
- Changes
- Known Problems
- Monitors Provided
- Monitor Dependencies
- Defect Reporting
- SD Product Structure
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 products 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 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. 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 Diagnostics section of Hewlett-Packard's online documentation Web site at:
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.
For the most current information on HP-UX 11i V1.5 diagnostics, see the following Web pages at the Diagnostics site:
- "DIAGNOSTICS.readme for HP-UX 11i V1.5 (September 2001)" at:
http://docs/hp.com/hpux/onlinedocs/diag/st/str_1120b.htm- "Release Notes for STM on HP-UX 11i V1.5 (September 2001)" at:
http://docs/hp.com/hpux/onlinedocs/diag/stm/str_1120b.htm- "Release Notes for EMS Hardware Monitors (HP-UX 11i V1.5, September 2001)" at:
http://docs/hp.com/hpux/onlinedocs/diag/ems/emr_1120b.htmFor 11i V1.5, the EMS hardware monitors use version A.03.30 of the EMS platform. HP-UX 11i V1.5 does not support the full functionality of the EMS platform. However, all EMS functionality required by the hardware monitors is provided.
The notification method "SNMP" that can be configured (in previous releases) for EMS HW Monitors will probably NOT be available to monitors running on HP-UX 11i V1.5 (Check the latest the latest Web page version of the EMS Release Notes for the most current information).
Memory Page Deallocation (MPD) and the memlogd daemon are not implemented on the RX 4610 computer.
Changes in the EMS Hardware Monitors for the the September 2001 release include:
- Changes to Multiple Monitors
- Changes to Individual Monitors
- Changes to Platform and Interface
- Customer-Vi sible 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).
N/A- CMC Monitor (cmc_em).
- Fix monitor to prevent it from going into a loop looking for CMC data, if the dummy data has incorrect sub-record length.
- Fix to prevent monitor from going into loop and logging messages in api.log file if poll interval is zero and diaglogd is down.
- Core Hardware for Itanium (ia64_corehw).
- Added ia64_corehw monitor as receiver of salerrors from diaglogd.
- Fix to prevent monitor from going into loop and logging messages in api.log file if poll interval is zero and diaglogd is down. Although the monitor does NOT register with diaglogd, the code is changed for consistency.
- Made the SEL debug dump optional (and stopped the dump by default to stop using excessive CPU).
- Disk Array FC60 Monitor (fc60mon).
Fixed a customer visible problem:The /var/stm/config/tools/monitor/fc60mon.psmcfg configuration file's format was such that the last line in the file was not read. Therefore, the default psmcfg mapping of severity to DOWN state is used for this monitor and an error is logged in the /etc/opt/resmon/log/client.log file, as indicated below.
Severity threshold keyword #1 did not have matching operator keyword or visa versa in the entry with monitor resource name /storage/events/disk_arrays/FC60. This severity mapping will be skipped.
The file is supposed to configure the monitor resources to only go into the DOWN state if the severity is CRITICAL. Due to the skipped severity mapping, the monitor resources will go into the DOWN state when the severity is SERIOUS or higher.
- Disk Monitor (disk_em).
N/A- Fibre Channel Adapter Model A5158 Monitor (dm_TL_adapter).
N/A- Fibre Channel SCSI Multiplexer (dm_fc_scsi_mux).
N/A- High Availability Disk Array Monitor (ha_disk_array) .
N/A- High Availability Storage System (dm_ses_enclosure)
N/A- Kernel Resource Monitor (krmond)
N/A- Memory (dm_memory_azusa) for RX9610 only (not for RX4610).
- Add new monitor, dm_memory_azusa, for RX9610.
- Peripheral Status Monitor (PSM).
N/A- Remote Monitor (RemoteMonitor).
- Initial submittal of the Remote Monitor for HP-UX 11.20.
- SCSI Disk Monitor (scsi_disk).
- JAGad81201
Fix to generate multiple instances of events 100 (devices added) and 101 (devices removed) from the list of devices to be monitored. Currently, only one instance of the events is generated when multiple devices are added/removed in the system.- JAGad67463
Don't try to get defect logs for devices with non-HP firmware.- Replace text "replace XXX" with "contact HP support representative. .." in the event messages.
- Enhanced info in polling events : the event details will now have the information about CDB data that was used in the polling side of the monitor.
- Fix to prevent monitor from going into loop and logging messages in api.log file if poll interval is zero and diaglogd is down. The fix for this defect was provided in the template.
- SCSI Tape Monitor (dm_stape).
- JAGad64273
- Added and used a "Get_stape_Cache" function in perform_polling, that retrieves Inquiry and Log Sense data from the stape driver cache.
- Updated to the latest HMS version (1.43) ems_layer.c
- System Status Monitor (sysstat_em)
- Fix to prevent monitor from going into loop and logging messages in api.log file if poll interval is zero and diaglogd is down. Although th e monitor does NOT register with diaglogd, the code is changed for cons istency.
- Following the field review of the monitor, events 100009 and 100010 will be generated every hour for the field personnel.
- Fix to remove the .fmt file when event generation is finished.
- Fix to generate multiple instances of events 100 (systems added) and 101 (systems removed) from the list of systems to be monitored. Currently, only one instance of the events is generated when multiple systems are added/removed in the list.
- UPS Monitor (dm_ups).
N/AChanges to Platform and Interface
- Fix psmctd to consider a missing HWE_SHUTDOWN file as monitoring enabled, not disabled. If this file was removed, the monitors and monconfig consider monitoring enabled, but psmctd didn't. So, it would shutdown and log an error indicating monitoring needs to be enabled. This is a customer visible change.
- JAGad68646
This fixes a problem on a few systems where, on system boot, monitors call swlist, and it hangs.Customer-Visible Interface Changes N/A
PROBLEM: Memory Page Deallocation (MPD) is not available on the RX 4610 computer.The Memory Page Deallocation (MPD), which runs on most current HP-UX computer systems, does not work on the RX 4610 computer. If you look in the activity log for memlogd, you will see a message saying, "unsupported device."
MPD cannot be implemented on RX 4610 because of the design of that system. The memlogd daemon cannot run on it.
PROBLEM: dm_fc_hub and dm_fc_sw monitors not functional.In the September 2001 release of 11i V1.5, the Fibre Channel Arbitrated Loop Hub monitor (dm_fc_hub) and the Fibre Channel Switch monitor (dm_fc_sw) are probably not functional, because these monitors depend on SNMP functionality which may not be included in this release (check the latest version of the Web page for the EMS Release Notes for the most current information) .
For the September 2001 release of HP-UX 11i V1.5, the following monitors are scheduled to be available:The following monitors are NOT provided:
- AutoRAID Disk Array (armmon)
- CMC Monitor (cmc_em).
- Core Hardware for Itanium (ia64_corehw)
- Disk (disk_em)
- Disk Array FC60 (fc60mon)
- Fibre Channel Adapter Model A5158 (dm_TL_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)
- Memory (dm_memory_azusa) for RX9610 only (not for RX4610)
- Peripheral Status Monitor (psm)
- Remote Monitor (RemoteMonitor)
- SCSI Disk Monitor (scsi_disk)
- SCSI Tape Devices (dm_stape)
- System Status (sysstat_em)
- UPS (dm_ups)
- dm_core_hw: replaced by ia64_corehw
- dm_FCMS_adapter
- fw_disk_array: hardware not supported on system
- lpmc_em: replaced by cmc_em
- scsi123_em: hardware not supported on system
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.hw_mon.hpux. 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.
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