Monitor Description | Configuration Files
Monitor Description
The Itanium Memory Monitor, memory_ia64, is designed to monitor the operation of all system memory on Itanium-based systems only. Diagmond launches the daemon called diaglogd to receive information about various kinds of errors on the system. If diaglogd receives any Corrected Platform Errors (CPE) information, the daemon will send them to the Itanium Memory Monitor. The Itanium Memory Monitor will analyze the data to determine if a hardware problem with the system memory 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 Itanium Memory Monitor employs asynchronous event-driven event detection by continuously watching for Corrected Platform Errors on the system memory reported by the diaglogd daemon. The Itanium Memory Monitor then analyzes the data returned to determine if a hardware problem with the system memory has occurred. If an error has occurred that warrants notification, an event is generated immediately.
The Itanium Memory Monitor and the diaglogd daemon 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
July 2003 Release (HP-UX 11.23): DEV_ID tags support
August 2002 Release (HP-UX 11.22): Initial releaseSupported Products
All Itanium-based systems (except Model rx4610, rx9610)
Special Requirements
HP-UX 11.22 or later.
Diaglogd must be up and running in order for the Itanium Memory Monitor to fully monitor the operation of all system memory on Itanium-based systems only.
Resource Path
Event Monitoring: /system/events/memory_ia64
State Monitoring: NoneState Monitoring: None
Monitor Name
/usr/sbin/stm/uut/bin/tools/monitor/memory_ia64
PSM State Control
The monitor does not support automatic state control.
Memory Error Log File and Event History File
Keeps memory error information and event history in files. If the Itanium Memory Monitor is started or rebooted and the memory configuration has changed, the Itanium Memory Monitor clears the memory error information and event history files. (This is not the default behavior for other monitors.)
Configuration Files
Startup Configuration File (.sapcfg)
File name: /var/stm/config/tools/monitor/memory_ia64.sapcfg
Default Entries: The monitor uses the standard default monitor request entries.
Monitor Configuration File (.cfg)
File name: /var/stm/config/tools/monitor/memory_ia64.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).
Default settings:
Setting Name Settings POLL_INTERVAL 60 minutes REPEAT_FREQUENCY Replaced by "Suppression Time" in the .clcfg file. SEVERITY_ACTION See the .clcfg file for specific event info. Default Client Configuration File (.clcfg)
File name: /var/stm/config/tools/monitor/default_memory_ia64.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_memory_ia64.clcfg applies to messages sent to all targets. Specific .clcfg files (for example, predictive_memory_ia64.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 for that HOST_ID tag will appear in the event message.
For the list of HOST_ID tags that are available for this monitor, please see the HOST_IDs for all monitors as 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 for that DEV_ID tag will appear in the event message.
The following is the list of DEV_ID tags that are available for this monitor:
DEV_ID Tag Default Description Text Label dev_dimm_slot On DIMM Physical Location DIMM Location dev_serial_num On DIMM Serial Number Serial Number dev_part_num On DIMM Part Number Part Number
Top of Page / Diagnostics HOME