Sun Fire[TM] v1280, 3800, 4800, 4810, 6800, E2900, E4900, E6900, and Netra[TM] 1280, and 1290 systems: Incoming versus Outgoing errors. (Doc ID 1002710.1)

Last updated on FEBRUARY 23, 2016

Applies to:

Sun Netra 1290 Server - Version Not Applicable and later
Sun Fire E6900 Server - Version Not Applicable and later
Sun Fire E4900 Server - Version Not Applicable and later
Sun Fire 4810 Server - Version Not Applicable and later
Sun Fire V1280 Server - Version Not Applicable and later
All Platforms

Goal

Description
This document applies to Sun Fire[TM] v1280, 3800, 4800, 4810, 6800, E2900, E4900, E6900, and Netra[TM] 1280, and 1290 systems.

This document relates to the diagnosis of error events that get logged to a file called the error buffer on the System Controller (SC) on the systems shown above.

The error buffer log file data is collected by the command showerrorbuffer when running an Explorer using the scextended or 1280extended option.

Alternatively, a user can display this information directly on the System Controller by executing the command as follows (This example is from the lomprompt on an E2900 server):

lom> showerrorbuffer
 
 ErrorData[0]
 Date: Sat Aug 18 09:50:39 EDT 2007
 Device: /SB0/dx3
 ErrorID: 0x33071ff3
 Port: 3
 Syndrome: 0xd(CE bit 41)
 Direction: outgoing read
 TargetAid: 0x3
 Transid: 0x1
 ErrorData[1]
 Date: Sat Aug 18 09:50:39 EDT 2007
 Device: /SB2/dx3
 ErrorID: 0x33071ff3
 Port: 3
 Syndrome: 0xd(CE bit 41)
 Direction: incoming read
 First error: true
 TargetAid: 0x3
 Transid: 0x1

The error example above will be used in the remainder of this article to explain the relation of Incoming to Outgoing as it relates to error message diagnosis.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms