Monitor Description | Configuration Files
Monitor Description
The System Status Monitor checks whether the target systems being monitored are up and running, and whether they have Online Diagnostic software installed and running. An event is generated if a system crashes, hangs or if the diagnostic software is shut down on any of the systems being monitored.
The monitor is launched automatically when the system is started.
Release HistoryMarch 2001 Release: Multiple-view ("Predictive-enabled") support
June 2000 Release: Resource names changed
December 1999 Release: Initial releaseSupported Products
All systems.
Special Requirements
None
Resource Path
Event monitoring: /system/events/system_status/<target_system>
Status monitoring: /system/status/system_status/<target_system>Prior to the June 2000 release, the resource paths were:
Event monitoring: /system/system_status/events/<target_system>
Status monitoring: /system/system_status/status/<target_system>Monitor Name
/usr/sbin/stm/uut/bin/tools/monitor/sysstat_em
Adding or changing the monitor resources
To add or change a monitored resource you must make the changes directly in the /var/stm/config/tools/monitor/sysstat_em.cfg file. Under the field labeled "These are the systems to be monitored" add/change the resource as desired using the following syntax:
system <systemname>
or
system <IP address>
The monitoring does NOT need to be stopped and restarted for the changes to take affect. After a system name is added/removed from the .cfg file, the monitor will readjust the monitoring requests itself. It might take a couple of POLL_INTERVALs before the change is seen, depending on whether a system was added or removed or both. To verify the resource changes have taken affect, choose "c" (check detailed monitoring status). The resources should all be listed under the /system/events/system_status/........OK field.PSM State Control
Controls its own PSM state with calls to PSM. The resource will be in UP state as long as the diagnostics startup daemon (diagmond) is running on the remote machine, else the resource is set to the DOWN state.
Configuration Files
Startup Configuration File (.sapcfg)File name: /var/stm/config/tools/monitor/sysstat_em.sapcfg
Default Entries: The monitor uses the standard default monitor request entries.
Monitor Configuration File (.cfg)File name: /var/stm/config/tools/monitor/sysstat_em.cfg
The System Status monitor began supporting Multiple-view (Predictive-enabled) in the March 2001 Release. Note the Repeat Frequency and Severity Action are no longer set in the Monitor Configuration file (.cfg) but are now set in the Default Client Configuration file (.clcfg) described below.
Default settings:
Setting Name Before March 2001 March 2001 & After POLL_INTERVAL 15 minutes 15 minutes REPEAT_FREQUENCY 1440 minutes (1 day) Replaced by Suppression Time in the .clcfg file. MIN_PACKET_LOSS 40 (threshold for event 100010) 40 (threshold for event 100010) SEVERITY_ACTION Notify for all levels See the .clcfg file for specific event info. Note: Multiple-view (Predictive-enabled) hardware monitors no longer use the the Monitor Configuration file (.cfg) to set the Repeat Frequency and Severity Action. These settings are made instead in the the Client Configuration files (.clcfg) described below.
Default Client Configuration File (.clcfg)
File name: /var/stm/config/tools/monitor/default_sysstat_em.clcfg
If a monitor is Multiple-view (Predictive-enabled), it uses a client-configuration file (*.clcfg) to control the text sent in text messages to specific targets (for example, to Predictive Support). The default_sysstat_em.clcfg applies to messages sent to all targets. Specific .clcfg files (for example, predictive_sysstat_em.clcfg) are used to control the text sent to specific targets (in this example, to Predictive Support).
HOST_ID tags in the .clcfg files control the System Information, which is reported under the "Additional System Data" label in the event messages. If a HOST_ID tag is enabled in the *.clcfg file, then the corresponding information will appear in the event message.
HOST_IDs available for all monitors are described in the Generic Monitor Data Sheet.
DEV_ID tags in the .clcfg files control the Monitor-specific information, which is reported under the "Component Data" label in the event messages. If a DEV_ID tag is enabled in the *.clcfg file, then the corresponding information will appear in the event message. DEV_IDs available for this monitor include:
DEV_ID tag Default Text label dev_host_id On Host ID (fully qualified name of the system being monitored) dev_host_ip On Host IP Address PSM Configuration File (.psmcfg)
File name: /var/stm/config/tools/monitor/sysstat_em.psmcfg
Default settings:
MONITOR_RESOURCE_NAME /system/events/system_status PSM_RESOURCE_NAME /system/system_status/status/<target_system> MONITOR_STATE_HANDLING ALL_STATE_CONTROL DOWN_SEVERITY_THRESHOLD Serious and Critical map to DOWN