Table of Contents
Advertisement
Figure 41. Example of an Open Link Error
The example also shows that, during any six hour period, no more than three errors of
this type are sent to the error log. If other types of error occur for this device, or errors
occur for another device, they are sent immediately to the error log. The actual
threshold values that are used for any given error type are regularly reviewed, and
might change with any new version of the device driver. They always permit, however,
enough errors to be logged to ensure that the error log analysis produces an SRN
when any service action is required.
Error Log Analysis
Summary
The error log is analyzed automatically every 24 hours. This automatic error log
analysis is started by the run_ssa_ela cron job. If the results of the analysis show that
any service activity is needed, the automatic error log analysis:
1. Sends an operator message (OPMSG) to the error log.
2. Displays an error message on /dev/console.
3. Sends a mail message to ssa_adm. The name ssa_adm is an alias (alternative)
address that is set up in /etc/aliases. By default, ssa_adm is set to root. You can,
however, change this alias to any valid mail address for your using system. See
your using-system documentation for information about how to change alias
addresses.
Error log analysis also runs automatically each time that diagnostics run in Problem
Determination mode. In this mode, the error log analysis runs before any diagnostic test
is run to the SSA devices. Diagnostics in Problem Determination mode, therefore,
generate an SRN if any SSA error logs show that service activity is needed.
If you run the ssa_ela command from the command line, you can also run error log
analysis to all SSA devices that are attached to a system.
Chapter 11. SSA Error Logs
229
Advertisement
Table of Contents
