Online Diagnostics (EMS and STM) Administrator's Guide March 2012

to the monitor. The settings defined in the monitor-specific file override the settings defined in
the Global Configuration File.
• Client Configuration File: Multiple-View monitors enable you to create a different Client
Configuration File for each target. Settings defined in the Client Configuration File override
comparable settings defined in either the Global or the Monitor-Specific Configuration File.
NOTE: For Multiple-View monitors, settings not defined in the Client Configuration File, such as
the POLL_INTERVAL, must be defined in either the Global or the Monitor-Specific Configuration
File.
The settings defined in the Monitor-Specific Configuration File are optimized to meet your needs.
You can alter these settings. However, HP recommends that you do not alter the settings unless
you fully understand the implications of doing so.
Monitor-Specific and Global Configuration File Parameters
The Monitor-Specific and Global Configuration files include a set of parameters that you can use
to configure the monitors. Following are the common operating parameters of the Monitor-Specific
and the Global Configuration Files for all non-Multiple-View monitors:
• Polling Interval — Identifies the frequency at which the monitor polls the hardware for status.
This interval is selected to provide current device status without seriously impacting system
performance.
• Repeat Frequency — Indicates how often the same event must be reported. A value of once
a day is used as the default repeat frequency.
• Severity Action — Determines whether the severity level is communicated to EMS for reporting
or ignored
• Event Definition — Identifies each event generated by the monitor, defines its severity level,
and determines what action must be taken. Actions include ignoring the event, sending it to
EMS, or using the default action defined by the Severity Action setting.
NOTE: Changes made to a Monitor-Specific Configuration File are invoked at the next polling
interval or when an event is generated, which ever happens first. In either of these situations, the
monitor reads its configuration file for any change and implements any new settings.
Startup Configuration File
Each monitor has its own Startup Configuration File, which contains the monitoring requests currently
defined for the monitor. The entries in the Startup Configuration File are used to create monitoring
requests for the monitor at startup, after the execution of the IOSCAN utility or when using the
monconfig utility to manage monitoring requests.
Each monitoring request in the Startup Configuration File is applicable to all instances of the
monitor's hardware resources. An identical set of default requests is included in the Startup
Configuration File for each monitor.
You can modify the contents of the Startup Configuration File by using the Hardware Monitoring
Request Manager. When you use the Hardware Monitoring Request Manager to create or to
manage monitoring requests, the result is stored as an entry in the monitor's Startup Configuration
File. If you select the All Monitors option for the request, an entry is logged in the Startup
Configuration File to all the monitors.
NOTE: Changes made to a Startup Configuration File are invoked when the system is restarted,
after the execution of the IOSCAN utility, or when you use the Hardware Monitoring Request
Manager to manage monitoring requests. For example, when you add, delete, or modify a
monitoring request using the Hardware Monitoring Request Manager, the changes to the Startup
Configuration File take effect immediately.
Hardware Monitoring Request Manager 29