Dec Osf/1 Translation; Interpreting System Faults Using Erf And Uerf - DEC 4000 AXP Service Manual

ERF bit-to-text translation highlights all error flags that are set, and other
significant state. These are displayed in capital letters in the third column of the
error log (see in Example 4–1). Otherwise, nothing is shown in the translation
column.
Section 4.4.9 provides a sample ERF-generated error log.

4.3.2 DEC OSF/1 Translation

Error log information is written to /var/adm/binary.errlog. Use the following
command to save the error log information by copying it to another file:
$ cp /var/adm/binary.errlog /tmp/errors_upto_today
To clear the error log file, use the following command:
$ cp /dev/null /var/adm/binary.errlog
To produce a bit-to-text translation of the error log file, use the following
command:
$ uerf -f /tmp/errors_upto_today -R
To view all all error logs in reverse chronological order, use the following
command:
$ uerf -R
For filtering of error logs, see the reference page for UERF on the system you are
currently using:
$ man uerf
Section 4.4.10 provides a sample UERF-generated error log.

4.4 Interpreting System Faults Using ERF and UERF

Use the following steps to determine the failing FRU when a system error is
reported via an error log.
1. Examine the error field of the kernel event frame.
If a system error has been reported, one or more bits may be set for the
low and high quadword and their corresponding bit-to-text definition will be
listed.
2. Using Table 4–2, find the entry that matches the set bit and bit-to-text to
determine the most probable source of the fault listed in the third column.
3. If the table entry lists a note number along with the most probable failing
module, refer to that note following Table 4–2.
Error Log Analysis 4–7