Monitor Description | Configuration Files
Monitor Description
The Memory monitor, dm_memory_azusa, is designed to monitor the operation of the Model rx9610 system memory. Diagmond launches the daemon called diaglogd to interrogate for various kinds of errors. If diaglogd finds any memory error information, the daemon sends it to the memory monitor. The memory monitor will analyze the data to determine if a hardware problem has occurred. If an error has occurred that warrants notification, an event is generated immediately whenever a threshold is met and sent to the Event Monitoring Service (EMS). EMS alerts you using the notification methods defined for the monitor. Clear, concise error messages identify the problem, what caused it, and what must be done to correct it.
The Memory monitor employs asynchronous event detection. The monitor continuously watches for any memory errors reported by diaglogd daemon. The monitor then analyzes the data returned to determine if a hardware problem has occurred. If an error has occurred that warrants notification, an event is generated immediately.
The Memory monitor and diaglogd are launched by diagmond (if the OnlineDiag product is installed on the system) automatically when the system is started, ensuring that all system memory is protected from undetected hardware failure.
Release History
August 2001 Release: Initial release
Supported Products
Model rx9610 system memory
Special Requirements
HP-UX 11.20 or later.
Diaglogd must be up and running in order for the memory monitor to fully monitor the operation of model rx9610 system memory.
Resource Path
Event monitoring: /system/events/memory_azusa
Status monitoring: /system/status/memory_azusaMonitor Name
/usr/sbin/stm/uut/bin/tools/monitor/dm_memory_azusa
PSM State Control
The set_fixed utility must be used to return a hardware resource to the UP state following a failure. The monitor does not support automatic state control. (See "Using the set_fixed Utility to Restore Hardware UP State" in the EMS Hardware User's Guide.
Memory Configuration and Information Files
Keeps memory configuration and memory error information in files. If the memory monitor is started or rebooted, memory configuration is saved and checked. When memory configuration is changed, the memory monitor clears the memory error information. (This is not the default behavior for other monitors.)
Configuration Files
Startup Configuration File (.sapcfg)
File name: /var/stm/config/tools/monitor/dm_memory_azusa.sapcfg
Default Entries: The monitor uses the standard default monitor request entries.
Monitor Configuration File (.cfg)
File name: /var/stm/config/tools/monitor/dm_memory_azusa.cfg
As a Multiple-view (Predictive-enabled) hardware monitor, 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 August 2001 & after POLL_INTERVAL 60 minutes REPEAT_FREQUENCY 1440 minutes (1 day) SEVERITY_ACTION Notify for all levels Default Client Configuration File (.clcfg)
File name: /var/stm/config/tools/monitor/default_dm_memory_azusa.clcfg
Monitors containing the client-configuration files (.clcfg) are Multiple-View enabled monitors. Client-configuration files can be used to control the text sent in text messages to specific targets (for example, to Predictive Support.) The default_dm_memory_azusa.clcfg applies to messages sent to all targets. Specific .clcfg files (for example, predictive_dm_memory_azusa.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 Description Text label dev_pdev On Physical Device Path Physical Device Path PSM Configuration File (.psmcfg)
File name: /var/stm/config/tools/monitor/dm_memory_azusa.psmcfg
Default settings:
MONITOR_RESOURCE_NAME /system/events/memory_azusa PSM_RESOURCE_NAME /system/status/memory_azusa MONITOR_STATE_HANDLING NO_UP_CONTROL. UP state will be controlled by the set_fixed(1m) command. DOWN_SEVERITY_THRESHOLD Serious and Critical map to DOWN
Top of Page / Diagnostics HOME
URL: http://docs.hp.com/hpux/onlinedocs/diag/ems/emd_mem_azusa.htm
Last updated: Fri Aug 31 10:59:12 PDT 2001