HP Tru64 UNIX and TruCluster Server Version 5.1B-5 Patch Summary and Release Notes (March 2009)

3.2.1.12 envmond Daemon Modified to Use EVM Events
The envmond daemon has been modified to allow it to use EVM events instead of the
hwmgr command to determine the environmental status of the system. On systems
with many sensors, this improvement may reduce or eliminate previously seen
performance problems.
By default, envmond is configured to use the hwmgr command (the poll method) for
environmental monitoring. To configure envmond to use EVM events, set the
envconfig ENVMON_MODE variable to event as follows:
# envconfig -c ENVMON_MODE=event
Because threshold values in event mode cannot be set to individual sensor, EVM events
are generated only when existing hardware thresholds are exceeded. If you need to
monitor individual sensors at thresholds different from the hardware thresholds, use
the new envconfig ENVMON_POLL_SENSORS variable in conjunction with the hwmgr.
For example:
# envconfig -c ENVMON_POLL_SENSORS="58:59"
To then set the warning threshold for the sensor with ID 58, to 50.0 degrees Celsius,
enter the following command:
# /sbin/hwmgr -set attr -id 58 -a warning_threshold=500
To set the fault action for the sensor with ID 58 to noshutdown:
# /sbin/hwmgr -set attr -id 58 -a fault_action=noshutdown
By specifying this set of commands, envmond uses the poll method for sensors 58 and
59 and the EVM event method for the rest of the sensors.
For more information, see the revised envconfig(8) reference page that is installed with
this kit.
3.2.1.13 aha_chim Driver Problem Corrected
This kit corrects the following problems found in the aha_chim driver:
• The driver would fail to issue a “Bus Reset” instruction when a Bus Device Reset
fails to complete for any reason other than a Bus Reset. With the installation of
this kit, when a Bus Device Reset fails, a Bus Reset will be issued in order to clear
and reset the target.
• The driver would fail to report the correct event identifier in the error entry of the
binary error log when the error condition was caused by the target using an invalid
tag ID, thereby resulting in an incorrect diagnosis of the problem. For example,
an entry of the following type:
Event information: Adapter requested initialization, caller ID = 10
should have been:
Event information: Adapter requested initialization, caller ID = 74.
3.2 Prior Release Notes 45