Errpt for Aix

In Aix, errpt is used to report error logs related to system software and hardware.

First, let's take a look at the actual output and simply list all the errors without parameters.

# Errpt
Identifier timestamp T c resource_name description
A2205861 1214144307 p s sysproc excessive interrupt disablement time
F3931284 1213234807 I h ent1 Ethernet network recovery mode
Ec0bccd4 1213234807 t h ent1 Ethernet down
F3931284 1213234807 I h ent1 Ethernet network recovery mode
Ec0bccd4 1213233607 t h ent1 Ethernet down
0873cf9f 1212141207 t s pts/1 ttyhog over-run
0873cf9f 1212141207 t s pts/1 ttyhog over-run
...

Use the-a parameter to View Details

# Errpt-A | more
-------------------------
Label: goent_rcvry_exit
Identifier: f3931284

Date/time: Thu Dec 13 23:48:47 Beist 2007
Sequence Number: 162
Machine ID: 00099476d600
Node ID: db158
Class: H
Type: info
Resource Name: ent1
Resource class: Adapter
Resource Type: 14108902
Location: U787B.001.DNWA74C-P1-T9
VPD:
Product Specific .()....... 2-port 10/100/1000 Base-TX PCI-X
Adapter
Network Address ............. 000d6051a0f6
Rom level. (alterable )....... Dv0210

Description
Ethernet network recovery mode

Recommended actions
Perform problem determination procedures

Detail data
File Name
Line: 204 file: goent_intr.c
PCI Ethernet statistics
0001 ef66 0063 0853 0000 0001 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001
0000 0000 0000 a69d 0000 0000 002c b028 0000 0000 0000 a64b 0000 0000 0000 A597
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0001 0000 0001 0000 0001 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 bb83 08f0 0000 0c00 0068 0000 01a0 0000 0000
0000 0000 0000 0000 0000 c9e1 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000
Device Driver internal state
5555 5555 0000 0000 0000 0000
Source Address
0011 25c0 3bde

Where:
Lable:Event name

Identifier:Event ID

Date/time:Occurrence time

Sequence Number:Event serial number

Machine ID:Machine ID

Node ID:Node ID

Class:Event Source
S-Software
H-hardware
I-Info
U-uncertain

Type:Event Type
Pend-availability loss of devices or components is urgent.
Perf-the performance of a device or component has been reduced to an acceptable level.
Perm-unrecoverable. If the error type is set to this value, it is usually the most serious error, and it is likely that the fault of the hardware device or software module occurs. If the error type is a value other than perm, it usually does not indicate a fault, but these errors are recorded for diagnosis.ProgramAnalyze them.
Temp-the status that is restored after multiple unsuccessful attempts. This type of error can also be used to record information entries, such as the data transmission statistics of DASD devices.
Unkn-the severity of the error cannot be determined.
Info-error log entries are informative and are not the result of an error.

Resource Name:The name of the resource that has been detected. For software errors, this is the name of a software component or executable program. For hardware errors, this is the name of a device or system component. It does not indicate that the component is faulty or needs to be replaced. Instead, it is used to determine the appropriate diagnostic module for error analysis.

Resource class:The general category of the faulty Resource (for example, the device category of the disk ).

Resource Type:The type of the faulty resource.

Location Code:The path of the device. There can be up to four fields: drawer, slot, connector, and port.

VPD:Key product data. The content of this field (if any) may be different. Device error log entries usually return information about the device manufacturer, serial number, Engineering Change level, and read-only storage level.

Description:Error summary.

Probable cause:List of possible error causes.

User causes:List of possible causes of errors caused by user errors. Errors Caused by users may include incorrectly inserted disks and external devices (such as modem and printer) that are not enabled ).

Actions:Description of recommended operations that correct errors caused by users.

Install causes:List of possible causes of errors caused by incorrect installation or configuration. Errors of this type include hardware and software mismatch, incorrect installation of cables, loose of cable connections, and incorrectly configured systems.

Actions:Description of recommended actions to correct errors caused by installation.

Failure Causes:List of possible hardware or software faults.

Actions:Description of recommended operations for fault rectification. For hardware errors, this will cause the diagnosis program to run.

Detailed data:Unique fault data for each error log entry, such as device detection data.

This article is mainly from the IBM test 222 certification guide series, Part 1: problem identification and resolution (I), which is for your reference only.