Sun Fire[TM] 3800/4800/4810/6800/E2900/E4900/E6900 & Netra[TM] 1280/1290: Troubleshooting Level 2 Check Errors (L2CheckError) (Doc ID 1005476.1)

Last updated on APRIL 05, 2022

Applies to:

Purpose

Description

This document provides the steps required to be followed to troubleshoot Level 2 Check Error events (L2CheckErrors) on Sun Fire[TM] Midrange servers.

Symptoms:

• A system or domain(s) may have been described as having gone down, rebooted unexpectedly, panicked, reset, or similar term.

• The word L2CheckError may be displayed in errors on the System Controller (SC) console or in showlogs .

• It may be reported that one domain was rebooted and another unexpectedly reset, panicked, or similar.

• It may be reported that a System Board (SB), Repeater, I/O Board, CPU(s), Memory DIMMs, or similar component is labeled as faulty or suspect and may be missing or disabled.

• It may be reported that the system or domain booted after the System Controller (SC) was failed over, rebooted, or reset.

System Type and Configuration:

• Sun Fire[TM] 3800, 4800, 4810, 6800 Servers

• Sun Fire[TM] E4900, E6900 Servers

• Sun Fire[TM] v1280, E2900 Servers

• Netra[TM] 1280, 1290 Servers

Notes: The system configuration includes at least System Controller Application (ScApp) 5.15.x. A device called a Repeater (RP) will be implicated by an L2CheckError event.  An RP is a type of board on all systems except for Sun Fire[TM] 3800 where the RPs are located on the system's Backplane/Centerplane.

Assumption:
This document assumes the event encountered is not a repeat event. Collect data as outlined in Step 5 below if this is a repeat event, and let the Sun Support Services engineer perform analysis.

Sun Shared Shell

If you require assistance in collecting the data recommended in this article or require help in diagnosing a system issue, there is a collaborative service tool called Sun Shared Shell which allows Sun Service engineers to remotely view and diagnose customer's systems. Consider using this option to reduce the problem resolution time.

Troubleshooting Steps