Release Notes for EMS Hardware Monitors (June 2001)

Overview

Configuring Hardware Mo nitoring

Documentation

Changes

Changes to Multiple Monitors

Changes to Individual Monitors

Changes to Platform and Interface

Customer-Visible Interface Changes

Known Problems

Monitors Provided

Monitor Dependenc ies

Defect Reporting

SD Product Structure

These release notes cover the June 2001 release of Support Plus for HP-UX 11i/11.00/10.20 running on S800/S700 systems.
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 (HP-UX 11i, 110.00 and 10.20).

Overview

Included 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, 11.00, or 10.20 (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:

Written to /var/adm/syslog/syslog.log

Sent to EMAIL address root

All events will be stored in /var/opt/resmon/log/event.log.
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

Documentation

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

Changes in the EMS Hardware Monitors for the the June 2001 release include:

Changes to Multiple Monitors

Changes to Individual Monitors

Changes to Platform and Interface

Customer-Vi sible Interface Changes

Changes to Multiple Monitors
JAGab67905.
Fixed a problem whereby monitors would leave the file /var/tmp/MONITOR_NAME.fmt after generating an event. Each time, a monitor would use the same filename so there was no threat of filling up the filesystem.
JAGad44671
Enhanced the monitors so that the event text will report "not set" for System Serial Number, if serial number should be available for the platform, but it hasn't been set:
System Serial Number............: not set
If the platform does not have a serial number that is available programmatically, it will continue to say "unavailable" as it now does.
System Serial Number............: unavailable
Changes to Individual Monitors

For this release, three new monitors were added:

Chassis Code Monitor (dm_chassis)

CMC Monitor (cmc_em)

Core Hardware for Itanium (ia64_corehw).

Two existing monitors were converted to be multiple-view (Predictive-enabled):

High Availability Storage System (dm_ses_enclosure),

Fibre Channel SCSI Multiplexer (dm_fc_scsi_mux).

Changes to each monitor are described below. (Monitors are listed in alphabetical order.)
AutoRAID Disk Array (armmon).
N/A

Chassis Code Monitor (dm_chassis).
New monitor. The Chassis Code Monitor supports Superdome family systems on HP-UX 11i. Each chassis code delivered to the GSP is read by the chassis code monitor, which looks the chassis code up in an internal table built from a chassis code database. If the chassis code warrants an event, it generates an EMS event with summary, event/keyword description, and details text.

CMC Monitor (cmc_em).
New monitor. The CMC Monitor monitors Corrected Machine Checks (CMCs) on Itanium-based systems. CMCs are the equivalent of LPMCs on PA-RISC systems.

Core Hardware Monitor (dm_core_hw)

Added support for hp server rp8400 (9000/800/S16K-A): A6093A ("Keystone W+ and W2", hversion 0x5d7 and 0x5e4)

Enhanced dm_core_hw to monitor AC power sources and to monitor links between crossbar controllers which may have been discovered to be bad during system power-on and routed around. If this had happened, a chassis code would have been generated at complex power-on only, and may not have been noticed. Previously, the core hardware monitor used to just check the links which were in use, so it would not have noticed when links that are expected to be present for a given cabinet configuration were not active.
A physical location will now be displayed in the Details section of events 26, 27, 28, 29, 30, 31, 32 and 36.

Core Hardware for Itanium (ia64_corehw).
New monitor. This Core Hardware monitor runs on Itanium-based systems and monitors hardware errors logged by various sensors on the system to the System Event Log (SEL). The monitor will report the following errors from the SEL:

Temperature problems

Fan failures / performance problems

Power Supply problems

Power Unit problems

Memory errors

Disk Array FC60 Monitor (fc60mon).
N/A

Disk Monitor (disk_em).

JAGad51565.
Fixed a problem with the asynchronous events (the events generated by the library tldecmon.sl). Previously, the details may have had incorrect or missing sense data information.

JAGab67905.
Fixed a problem whereby the Disk Monitor leaves the file /var/tmp/MONITOR_NAME.fmt after generating an event.

Fibre Channel Adapters (dm_FCMS_adapter).
N/A
Fibre Channel Adapter Model A5158 Monitor (dm_TL_adapter).
(HP-UX 11.00) Fixed a problem, whereby the following message was logged to /var/opt/resmon/api.log when the monitor was started:
-------------------Start Event--------------------
User event occurred at Thu Feb  8 09:28:15.787199 2001
Process ID: 20127 (/usr/sbin/stm/uut/bin/.../dm_TL_adapter)   
Log Level: Error
The FCMS Adapter decoder/monitor was passed a log record with a 
product qualifier of (fcp).  It does not support such a log record.
-------------------End Event----------------------
  
Added support for HP-UX 10.20 (the monitor now runs on HP-UX 11.00 and 11i).
Fibre Channel SCSI Multiplexer (dm_fc_scsi_mux).

Enhanced dm_fc_scsi_mux to be multiple-view (Predictive-enabled).

JAGac39723
Minor text changes in multiple events for clarity and consistency.

JAGac40525, JAGac39725
Enhanced dm_fc_scsi_mux to do a quick inquiry on all available FC paths at every polling interval.
There are only two possible paths to the MUX now: the two FC paths. Previously, the MUX monitor kept track of every path to the attached SCSI devices. It no longer does that. The MUX monitor now keeps one list called alternate. It does not use the identical list anymore. Basically, if both FCs are connected you can get the same event info from the MUX from either path, but the monitor now keeps track of which FC path(s) are up and which are down.

Previously, the monitor polled just one of the alternate paths unless it failed. Then it tried another of the alternate paths. The monitor therefore did not generate a "NOT RESPONDING" event if a path other than the one it polled fails.

As of the June 2001 release, dm_fc_scsi_mux was modified to do a quick inquiry on all available FC paths at every polling interval. If the MUX does not respond on that path, the NO RESPONSE event is generated for that path and the alternate path takes over if an alternate is available. If a path that was not responding before is now responding, a RESPONDING event is generated for that path. The code also now controls its own state, and sets PSM state to UP or DOWN for each FC path. The code was also changed to eliminate counting the number of times the MUX did not respond before logging a no response. The monitor will now log a NO RESPONSE event the first time the MUX does not respond on an FC port.

High Availability Disk Array Monitor (ha_disk_array) .
N/A

High Availability Storage System (dm_ses_enclosure)

Enhanced dm_ses_enclosure to be multiple-view (Predictive-enabled).

JAGad09315
Enhanced the text in event messages 302-305 and 601-605 to be more accurate and complete.

Kernel Resource Monitor (krmond)
Updated to version A.11.00.04 on HP-UX 11.00 (A.11.11.04 on HP-UX 11i) to fix a problem which can occur when the kernel is reconfigured and the nflock or ncallout monitors are enabled. Errors were reported through EMS. The workaround has been to run swconfig to reconfigure the EMS-KRMonitor package.

LPMC Monitor (lpmc_em).

Added support for:

hp server rp8400 (9000/800/S16K-A): A6093A ("Keystone W+ and W2", hversion 0x5d7 and 0x5e4)

B2600 workstation: A6070A and A6069A ("Piccolo")

Other computer systems using the PA-8700 chip ("Piranha")

JAGab67905.
Fixed a problem whereby the LPMC Monitor leaves the file /var/tmp/MONITOR_NAME.fmt after generating an event.

JAGad57295
Updated the default client config file, so that Events 100 and 101 are supported. Previously, the client config file did not contain entries that described the default behaviour for these events. Without these entries, the events would be generated with severity set by the monitor. Having this entries in the default client config file will allow the user to change the severity as well as the other parameters.
Memory Monitor (dm_memory).
Fixed a problem which sometimes occurred when a single memory address had many single-bit errors. The Memory Monitor would stop functioning and would report errors in the api.log ( /var/opt/resmon/api.log ) such as:
The system call accept() failed with an unexpected error.
The system call failed with an unexpected error, errno (0).
low_level:  The memory monitor was trying to accept the connection 
            from memlogd or was trying to read from the socket.


The system call read() failed with an unexpected error.
low_level:  The memory monitor was trying to accept the connection 
            from memlogd or was trying to read from the socket.
This error could occur on all machines on all OSs, but has only been reported infrequently.
Peripheral Status Monitor (PSM).
JAGad49489.
Fixed a problem whereby requests for the Peripheral Status Monitor (PSM) on many systems will disappear when the system is rebooted. The configuration parameter BOOT_WAIT was changed to 240 from 0 because monitors were not ready to respond to psmctd requests and were returning ERRORS. These errors were forwarded to psmmon, which would respond to p_client with errors. The upshot of all this is that if there were monitoring requests made in the EMS GUI for any PSM resources, they would get removed by p_client because psmmon would return errors.

Remote Monitor (RemoteMonitor).

Added event 199 to the RemoteMonitor event set. Event was added to address device to host connection failures.

JAGab67905.
Fixed a problem whereby the Remote Monitor leaves the file /var/tmp/MONITOR_NAME.fmt after generating an event.

(11i only). Made two enhancements for 11i that have already been made on 11.00:

Added support for DEV_IDs in the client config file.

Force RemoteMonitor shutdown if all entries in RemoteMonitor.cfg are defined as DISABLE.
SCSI Card Monitor (scsi123_em).
JAGab67905.
Fixed a problem whereby the SCSI Card Monitor leaves the file /var/tmp/MONITOR_NAME.fmt after generating an event.
Changed threshholds, suppression, and severity levels for many events in response to feedback from service personnel:
  T=Threshold Su=Suppression Se=Severity (only if changed)
Event 101014 : T=3/day Su=1 day Se=Major Warning
Event 101015 : T=3/day Su=1 day Se=Major Warning
Event 101021, 101024 : T=Any Su=1 day 
Event 101025 : T=3/day Su=1 day Se=Major Warning
Event 101027, 101028, 101029 : T=10/day Su=1 day Se=Major Warning
Event 101031 : T=3/day Su=1 day Se=Major Warning
Event 101033 : T=10/hr Su=1 day Se=Major Warning
Event 101034 : T=2/2 hrs Su=1 day Se=Major Warning
Event 101035 : T=Never Se=Warning
Event 101036 : T=2/hr Su=1 day Se=Minor Warning
Event 101037 : T=Any Su=1 day
Event 101038, 40, 42, 44, 46, 47, 49, 50, 51 : 
  T=3/day Su=1 day Se=Major Warning
Event 101061 : T=Never Se=Minor Warning
Event 101062  :    T=Never
Event 101063, 64, 65, 66, 67, 68, 76, 77, 78, 79 : 
  T=3/day Su=1 day Se=Major Warning
Event 101081 : T=Never Se=Minor Warning
Event 101094, 103, 109, 113, 114, 115, 117, 121 : 
  T=3/day Su=1 day Se=Major Warning
Event 101124 : T=2/hr Su=1 day
Event 101125 : T=2/4 hrs Su=1 day Se=Major Warning
Event 101126, 127, 128, 131 : T=3/day Su=1 day Se=Major Warning
Event 102002 : T=3/day Su=1 day Se=Major Warning
Event 102003, 007, 009, 012 : T=Any Su=1 day
Event 102013 : T=2/hr Su=1 day Se=Major Warning
Event 102014 : T=Any Su=1 day
Event 102015 : T=3/day Su=1 day Se=Major Warning
Event 102016, 017, 018, 019, 020, 022 : T=2/hr Su=1 day
Event 102023, 026, 027, 028, 029 : T=Any Su=1 day 
Event 103003, 004 : T=Any Su=1 day 
Event 103012 : T=Any Su=1 day Se=Major Warning
Event 103013, 014, 015, 016 : T=Any Su=1 day 
Event 103017, 024 : T=Never Se=Warning 
Event 103027, 029 : T=Any Su=1 day 
Event 103031, 032 : .  T=Never Se=Warning
Event 103033, 034 : T=3/day Su=1 day Se=Major Warning
Event 103035, 036 : T=5/day Su=1 week Se=Major Warning
Event 103037 : T=3/day Su=1 day Se=Major Warning
Event 103038 : T=Never Se=Warning
Event 103045, 046, 047, 048, 049, 051, 056, 057 : 
   T=3/day Su=1 day Se=Major Warning
Event 103059, 62 : T=Any Su=1 day 
Event 103068 : T=Never Se=Minor Warning
Event 103075, 079, 080, 081, 085 : T=3/day Su=1 day Se=Major Warning
Event 103086 : T=Any Su=1 day 
Event 103087 : T=3/day Su=1 week Se=Warning
Event 103088 : T=3/day Su=1 day Se=Major Warning
Event 103089, 090, 091 : T=Any Su=1 day 
Event 103092 : T=3/day Su=1 day Se=Major Warning
Event 103093, 094, 095 : T=Any Su=1 day 
Event 103097 : T=3/day Su=1 week Se=Major Warning
Event 103100 : T=Never Se=Informational
Event 103101 : T=Any Su=1 day 
Event 103102 : T=3/day Su=1 week Se=Major Warning
Event 103103, 104 : T=Any Su=1 day 
Event 103106 : T=3/day Su=1 week Se=Major Warning
Event 103107 : T=3/day Su=1 day Se=Major Warning
Event 103112, 113 : T=Any Su=1 day 
Event 103115 : T=3/day Su=1 day Se=Major Warning
Event 103117, 118 : T=Any Su=1 day 
Event 103119 : T=40/day Su=1 week Se=Warning
SCSI Tape Monitor (dm_stape).
Fixed a problem, whereby if POLL_INTERVAL is set to zero, the monitor is disabled from sending SCSI commands or logging events.

System Status Monitor (sysstat_em).

Fixed a problem, whereby the resource name used to set the PSM state was incorrect.

Added entry for DEV_ID in the .clcfg file, so that group name will be included in the event details.
UPS Monitor (dm_ups).
JAGad57809
Changed the cause/action text for event 42 to provide a solution to the indicated problem:
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 one of the
following patches:
HPUX 10.20/s800 : PHCO_23830
HPUX 11.00      : PHCO_23831
HPUX 11.11      : PHCO_23832
This problem will occur and event 42 will be generated on most systems with a UPS when the June 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_19031 (HP-UX 10.20) or PHCO_19040 (HP-UX 11.00) installed.
The ups monitoring daemon (ups_mond) will no longer be delivered as part of the Support Plus Media beginning in the June 2001 release. A patch will be provided to install the version of ups_mond that supports EMS monitoring. The UPS Monitor (dm_ups) cannot function without the version of ups_mond that will be supplied on the patch. If the monitor is run without the supported version of ups_mond, it will generate event 42 which defines the patch number to load in order to get the proper version of ups_mond. (See previous entry.) In future releases, the correct version of ups_mond will be supplied as part of the Hardware Enablement patch bundle.

JAGad55320
Fixed the UPS Monitor to respond to a problem initially reported as "ups_mond shuts down system when getting a one second power spike." This change was necessary due to a modification to the UPS monitoring daemon (ups_mond). This daemon sends all UPS information to the monitor. When detecting a status change from the UPS, ups_mond would send more commands to the UPS in order to get inquiry data. The daemon was changed so it now will only get inquiry data in the event of certain status codes. For those status codes that DO NOT result in inquiry date, there will be no Inquiry Data in the Detailed Information section (events 1, 2, 3, 4, 7, 8, 9).
Changes to Platform and Interface
Fixed a problem whereby a process running on the system might be mistakenly killed. When a monitor tries to unregister itself with diaglogd, it sends a request to diaglogd using its PID. If diaglogd is not running or its PID cannot be obtained, the monitor (in previous releases) tried to send the request to a random process, and the process might have been killed.

Fixed a problem whereby monitors don't log an error, and behave poorly when boot time is not available. Now, when boot time is not available, a message will be logged in api.log file.
Enhanced the handling of monitor configuration files. Previously, embedded spaces within configuration-verb's values were not allowed -- now they are. The string is expected to be within quotes. For example:
    # COMMAND "ls -f *.foo"
(10.20 and 11.00 only; problem was previously fixed on 11i). Fixed a problem, whereby monitors would abort with a SIGSEGV signal The problem occurred when rebooting a system when the CPU or System Information tool had not been previously run, and the system is rebooted. The monitors would SIGSEGV when they attempt to run those tools using the PG library routines.
JAGad54303
Updated monconfig.help, monconfig manpage, and disabled_instances file comments to describe more clearly how to disable monitor instances. The functionality for disabling instances was added in the Sept 00 release (IPR 0009). Text added to each file is listed below:
disabled_instances file

#
# The user can specify that specific instances not have monitoring requests
# created by monconfig by adding those instances to the this file.
# Monitoring requests created by monconfig apply to ALL instances
# associated with that monitor, except those listed in this file.
#
# In order to monitor some but not all instances associated with a monitor,
# the user would perform the following set of tasks:
# 1: add those instances associated with the monitor that should NOT be
# monitored to this file
# 2: create a monitoring request for the monitor using monconfig
# OR
# 2: enable monitoring to cause monconfig to read the new
# version of this file and apply the new set of disabled instances
# to the current monitoring requests

AND

# For example:
# To not have monitor requests created for a disk at hardware
# path 52/8.5.0, currently monitored by the disk_em monitor the following
# entry would be added to this file:
# /storage/events/disks/default/52_8.5.0
#
# To not have monitor requests created for any disks currently
# monitored by the disk_em monitor, the following entry would be added
# to this file:
# /storage/events/disks/default/*

monconfig.help
The user can specify that specific instances not have monitoring requests
created by monconfig by adding those instances to the this file.
Monitoring requests created by monconfig apply to ALL instances
associated with that monitor, except those listed in this file.

In order to monitor some but not all instances associated with a monitor,
the user would perform the following set of tasks:
1: add those instances associated with the monitor that should NOT be
monitored to this file
2: create a monitoring request for the monitor using monconfig
OR
2: enable monitoring to cause monconfig to read the new
version of this file and apply the new set of disabled instances
to the current monitoring requests

monconfig.1m
FILES
   /var/stm/data/tools/monitor/disabled_instances - file that lists
   instances (devices) for which monitoring requests should NOT be created
   by monconfig
(HP-UX 11i only. Changes have already been made to 10.20 and 11.00) Enhanced the psmctd daemon to not allow a monitor to set the state of a resource instance to UP if that resource instances is one that was removed from the system. The set_fixed command was previously modified to not allow the user to set the state to UP. This change is an enhancement to ensure that monitors that control their own state, rather than depending on the set_fixed command, behave in the same way.

(HP-UX 11i only. Changes have already been made to 10.20 and 11.00) Fixed the psmctd daemon to leave a resource instance that was removed from the system marked as an instance, so when it is added back in, it is still considered an instance. If a resource instance was removed, psmctd would mark it DOWN and indicate it no longer exists and clear the instance flag. At this point, the instance would no longer be displayed in set_fixed -l. When the instance was restored, psmctd would mark the instance as existing on the system, but failed to set the flag indicating it was an instance, so it still would not be displayed in set_fixed -l, and thus could not be set to the UP state.

(HP-UX 11i only. Changes have already been made to 10.20 and 11.00) Previously, startmon_client removed all the EMS HW Monitor monitoring requests and then re-created the new set. This left a window in which a monitor could generate an event, but the event would not be forwarded on to the user. The code was modified to leave the old monitoring requests active, while it created new ones and then remove any monitoring requests that were not re-created.

(HP-UX 11i only. Changes have already been made to 10.20 and 11.00) Some of the error messages generated for communication problems with EMS were unclear and some were completely wrong. These error messages were corrected. For details, see "Customer-Visible Interface Changes" below.

(HP-UX 11i only. Changes have already been made to 10.20 and 11.00) startmon_client used to create monitoring requests for the dummy entries which were added to the sapcfg files by monconfig as placeholders when all monitoring requests were removed. startmon_client was modified to ignore these dummy entries. For details, see "Customer-Visible Interface Changes" below.
Customer-Visible Interface Changes

This section reports changes to the customer-visible interface in this release. This information is provided for the benefit of customers using scripts to drive hardware support tools to look at the output of hardware support tools.
The following error messages, that could be logged into /etc/opt/resmon/log/api.log were modified:
BEFORE:
monitor 'XXX; times out waiting for resource list reply: No such file or
directory:
AFTER:
Timed out waiting for resource list reply for monitor XXXX

BEFORE:
Error in get_first_config function: No such file or directory
AFTER:
Error in get_first_config function.

BEFORE:
Error in send_monitor_request function: No such file or directory
AFTER:
Error in send_monitor_request function.

BEFORE:
Error in receive_monitor_reply function: No such file or directory
AFTER:
Error in receive_monitor_reply function for instance XXXX.

BEFORE:
Error in set_monitor_request function: No such file or directory
AFTER:
Error in set_monitor_request function.

BEFORE:
monitor timed out waiting for monitor reply
AFTER:
Timed out waiting for monitor reply.

NEW ERROR MESSAGE:
Error in rm_get RmRequestID for monitor reply: XXXXX
Previously, when all the monitoring requests for a monitor were removed using monconfig, it would add a dummy entry. This entry would be displayed when the "C)heck monitoring requests" command is performed:
 Events <= 1 (INFORMATION) Goto TEXTLOG; file=//dev///null
This dummy entry is no longer displayed. Thus when all the monitoring requests are removed for a monitor, the following will be displayed when the "C)heck monitoring requests" command is performed:
 There are no monitoring requests.
The event text reported by monitors will now report "not set" for System Serial Number, if serial number should be available for the platform, but it hasn't been set:
System Serial Number............: not set
If the platform does not have a serial number that is available programmatically, it will continue to say "unavailable" as it now does:
System Serial Number............: unavailable
Known Problems

CAUTION: UPS Monitor May Need a Patch
In some cases, the UPS monitor (dm_ups) will not function and will instead generate 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 one of the
following patches:
HPUX 10.20/s800 : PHCO_23830
HPUX 11.00      : PHCO_23831
HPUX 11.11      : PHCO_23832
To fix the problem, load the indicated patch.
This problem will affect most systems with a UPS when the June 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_19031 (HP-UX 10.20) or PHCO_19040 (HP-UX 11.00) installed.

CAUTION: Monitoring Changes for disc30, sdisk and disk array devices
As 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, pharaymon_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, sdisk_exec.cfg, and haraymon_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.03
Support Tools and the EMS hardware monitors are not affected. For complete information, see EMS Incompatibility Problem.

Monitors Provided

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)

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 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)

Kernel Resource (krmond)

LPMC (lpmc_em)

Memory (dm_memory)

Remote (RemoteMonitor)

SCSI Card (scsi123_em)

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/ .

Monitor Dependencies

Several of the monitors have special requirements, such as patches or certain versions of firmware. In particular:

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.

For a list of the current required patches, see the DIAGNOSTIC.readme file for this release.
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".

Defect Reporting

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.

SD Product Structure

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

Top of Page

/ Diagnostics HOME

URL: http://docs.hp.com/hpux/onlinedocs/diag/ems/emr_0106.htm
Last updated: Thu Jan 3 10:58:05 PDT 2002