Shulou(Shulou.com)06/02 Report--

In AIX, errpt is used to report error log information related to system hardware and software

Let's look at an actual output, with no arguments, simply listing all errors.

#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 0000 BB83 08F0 0068 0C00 0000 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

Of which:

LABLE: Event Name

IDENTIFIER: Event ID

Date/Time: Time of occurrence

Sequence Number: Sequence Number of the event

Machine ID: Machine ID

Node ID: Node ID

Class: Source of the event

S-Software

H-Hardware

I-Information

U-Undecided

Type: Event Type

PEND-Loss of availability of equipment or components is imminent.

PERF-The performance of a device or component has degraded below acceptable levels.

PERM-An irrecoverable condition has occurred. If the error type is this value, it is usually the most severe error and most likely indicates a hardware device or software module failure. If the error type is other than PERM, it usually does not indicate a fault, but these errors are logged so that they can be analyzed using diagnostic programs.

TEMP-The state recovered after several unsuccessful attempts. This error type can also be used to record informational entries, such as data transfer statistics for DASD devices.

UNKN-Unable to determine the severity of the error.

INFO-Error log entries are informational and are not the result of an error.

Resource Name: The name of the resource where the error was detected. For software errors, this is the name of a software component or executable. For hardware errors, the name of a device or system component. It does not indicate that the component has failed 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 resource for which the failure was detected (for example, the device class of the disk).

Resource Type: The type of resource for which the failure was detected.

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

VPD: Critical Product Data. The content of this field, if it exists, may vary. Error log entries for devices typically return information about the device manufacturer, serial number, engineering change level, and read-only storage level.

Description: Summary information of errors.

Probable Cause: A list of possible causes of errors.

User Causes: List of possible causes of errors caused by user errors. User-induced errors may include improperly inserted disks and external devices that fail to turn on, such as modems and printers.

Actions: A description of the recommended action to correct the error caused by the user.

Install Causes: List of possible causes of errors due to incorrect installation or configuration procedures. This type of error includes hardware and software mismatches, incorrect cable installation or loose cable connections, and improperly configured systems.

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

Failure Causes: List of possible hardware or software failures.

Actions: A description of the recommended action to correct the fault. For hardware errors, this causes diagnostics to run.

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

This article is primarily from IBM AIX V5.3 Systems Administration (Test 222) Certification Guide Series, Part 5: Problem Identification and Resolution (Part 1), and is excerpted here for reference only.

From: www.cnblogs.com/snake-hand/archive/2011/04/06/2452305.html

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.