Considerations For Modifying The Monitor Configuration File Settings; Monitor Configuration File Settings - HP B6191-90029 User Manual

Ems hardware monitors
Table of Contents

Advertisement

Hardware Monitor Configuration Files
Monitor-Specific and Global Configuration Files
Table 5-1
Monitor Configuration File Entries (Continued)
Setting
REPEAT_FREQUENCY
<frequency>
Considerations for Modifying the Monitor Configuration File Settings
The default configuration settings for each monitor have been carefully selected to provide efficient
monitoring for most systems. However, it may be necessary to modify these settings in specific situations.
Here are some considerations for altering the configuration settings.
NOTE
Settings in the Global.cfg configuration file apply to all monitors, so you should avoid
changing these settings. If you need to change the parameters for a monitor, do so using the
monitor-specific configuration file.
Monitor Configuration File Settings
Event Definition
You may want to alter the event definition in a monitor-specific configuration file to change the severity level
assigned to an event, or to suppress reporting of an event.
NOTE
Be aware that any changes you make to the event definition will impact all instances of the
monitor's hardware resources. You cannot modify the behavior of a specific hardware resource.
For example, if a disk array is repeatedly reporting the same event and you would like to
suppress it, you can do so by changing the event definition. But the change will suppress that
event even if it occurs on a different disk array. This may not be the result you want.
Changing the severity level assigned to an event. If you feel that the severity level assigned to an
event does not reflect its importance in your environment, you can make the event more or less
important. For example, if an event is currently assigned a severity level of MAJOR WARNING but from
experience you feel it represents a CRITICAL condition, you can change the DEFINE_EVENT setting for
the event.
Ignoring an event. By default, all events are reported. If you are getting repeated notification for an
event, you can ignore the event. When the condition that caused the event is corrected, you can once again
set the event for notification.
Severity Action
By default, all severity levels are reported to EMS. This default was selected because even lower level events
such as INFORMATION may provide valuable data for identifying trends that could lead to more serious
conditions. Consequently, it is recommended that you do not suppress the reporting of any events.
102
Values
frequency must be a
positive integer
indicating the number of
minutes to wait before a
repeat event can be
generated
Description
Defines how often
repeat alerts should be
generated for the same
event. Events for a
specific device should
not be reported more
often than the specified
frequency.
Chapter 5

Advertisement

Table of Contents
loading

Table of Contents