DTAG parity error Troubleshooting and Analysis (Doc ID 1010407.1)

Last updated on MARCH 29, 2017

Applies to:

Sun Enterprise 3000 Server
Sun Enterprise 3500 Server
Sun Enterprise 4000 Server
Sun Enterprise 4500 Server
Sun Enterprise 5000 Server
All Platforms

Goal

Description:

This document describes how to perform analysis of DTAG parity error events on Sun Enterprise 3x00/4x00/5x00/6x00 (aka Classic) Servers and determine if a replacement action is necessary.

Examples:

A DTAG Parity Error event is often only visible on the system console (sometimes called the console log since this is often logged on a console server) and is usually seen within Fatal Reset output.

An example from console log data is below:

17-OCT-2001 17:07:55.17 LBC5   Fatal Reset 
17-OCT-2001 17:07:56.69 LBC5 0,0>FATAL ERROR
17-OCT-2001 17:07:57.15 LBC5 0,0> At time of error: System software was running.
17-OCT-2001 17:07:57.37 LBC5 0,0> Diagnosis: Board 2, Dtag B (UPA Port1),AC
17-OCT-2001 17:07:57.37 LBC5 0,0>Log Date: Oct 17 21:17:19 GMT 2001 17-OCT-2001 17:07:57.37 LBC5 0,0>
17-OCT-2001 17:07:57.58 LBC5 0,0>RESET INFO for CPU/Memory board in slot 2
17-OCT-2001 17:07:57.58 LBC5 0,0> AC ESR 00000010.00000000 DT_PERRB
17-OCT-2001 17:07:57.59 LBC5 0,0> DC[0] 00
17-OCT-2001 17:07:57.59 LBC5 0,0> DC[1] 00
17-OCT-2001 17:07:57.59 LBC5 0,0> DC[2] 00
17-OCT-2001 17:07:57.59 LBC5 0,0> DC[3] 00
17-OCT-2001 17:07:57.59 LBC5 0,0> DC[4] 00
17-OCT-2001 17:07:57.59 LBC5 0,0> DC[5] 00
17-OCT-2001 17:07:57.59 LBC5 0,0> DC[6] 00
17-OCT-2001 17:07:57.80 LBC5 0,0> DC[7] 00
17-OCT-2001 17:07:57.80 LBC5 0,0> FHC CSR 00050030 LOC_FATAL SYNC BRD_LED_M BRD_LED_R
17-OCT-2001 17:07:57.80 LBC5 0,0> FHC RCSR 02000000 FATAL
17-OCT-2001 17:07:57.80 LBC5 0,0> Config policy change
17-OCT-2001 17:07:57.80 LBC5 0,0>
17-OCT-2001 17:07:57.80 LBC5 0,0>@(#) POST 3.9.28 2000/12/20 12:29
17-OCT-2001 17:07:58.02 LBC5 0,0>Copyright 2000 Sun Microsystems, Inc. All rights reserved.

In the example above the DTAG parity error occurred on System Board 2. 

NOTE that the port can also be Port A.

The FIX section of this article will explain further details of this event.

A DTAG event may also be seen in prtdiag output (in the section called Analysis of most recent Fatal Hardware Watchdog).  This is about the only type of Fatal Error event that can be diagnosed from prtdiag output alone. 

A DTAG error looks like the following in prtdiag:
     AC: UPA Port B Dtag Parity Error
NOTE that the port can also be Port A for example:

     AC: UPA Port A Dtag Parity Error

Once you have determined that your event matches what has been described above, proceed to the FIX section of this article to resolve the event.

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