JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Sun Server X2-8 (formerly Sun Fire X4800 M2) Diagnostics Guide     Sun Server X2-8 (formerly Sun Fire X4800 M2) Documentation Library
search filter icon
search icon

Document Information

Using This Documentation

Sun Server X2-8 Name Change

Product Downloads

Documentation and Feedback

About This Documentation

Change History

Overview of the Diagnostics Guide

Introduction to System Diagnostics

Troubleshooting Options

Diagnostic Tools

Troubleshooting the Server

How to Gather Service Visit Information

How to Troubleshoot Power Problems

How to Externally Inspect the Server

How to Internally Inspect the Server

Troubleshooting DIMM Problems

How to Isolate and Replace Faulty DIMM Pairs

How to Isolate and Correct Persistent DIMM Errors

Additional Tests

How to Detect DIMM Errors Using BIOS POST and the Oracle ILOM SEL

How to Detect DIMM Errors Using the CE Log

DIMM Hardware

BIOS POST

Default BIOS Power-On Self-Test (POST) Events

BIOS POST Errors

Using Oracle ILOM to Monitor the Host

Viewing the Oracle ILOM Sensor Readings

Viewing Fault Status

Clearing Faults

Viewing the Oracle ILOM System Event Log

Clearing the System Event Log

Interpreting Event Log Time Stamps

Resetting the SP

Creating a Data Collector Snapshot

How to Create a Snapshot With the Oracle ILOM Web Interface

How to Create a Snapshot With the Oracle ILOM Command-Line Interface

Using SunVTS Diagnostics Software

Introduction to SunVTS Diagnostic Test Suite

SunVTS Log Files

SunVTS Documentation

How to Diagnose Server Problems With the Bootable Diagnostics CD

Performing Pc-Check Diagnostic Tests

Pc-Check Diagnostics Overview

How to Run Pc-Check Diagnostics

Pc-Check Main Menu

System Information Menu

Advanced Diagnostics

Burn-In Testing

Viewing the Pc-Check Results

U-Boot Diagnostic Start-Up Tests

U-Boot Test Options

Running the U-Boot Diagnostic Tests and Viewing the Results

U-Boot Diagnostic Test Output

Sample SP Environmental Variables Showing U-Boot Test Status

Index

How to Isolate and Correct Persistent DIMM Errors

This task provides instructions for troubleshooting DIMM errors when the problem persists after swapping the faulty DIMMs as described in How to Isolate and Replace Faulty DIMM Pairs.


Caution

Caution - Before handling components, attach an antistatic wrist strap to a chassis ground (any unpainted metal surface). The system’s printed circuit boards and hard drives contain components that are extremely sensitive to static electricity.


Before You Begin

This task requires:

  1. If you have not already done so, shut down the system to standby power mode, remove the CMOD, and remove the cover of the CMOD.

    Refer to Adding, Removing, and Installing a CMOD (CRU) in Sun Server X2-8 (formerly Sun Fire X4800 M2) Service Manual.

  2. Exchange the DIMM pairs between the two CPU slots. Ensure that they are inserted correctly with the ejector latches secured.

    For example, if the faulty pair is DIMM 0 and DIMM 4 on CPU 0:

    1. Remove the DIMMs from CPU0, slots 0 and 4.
    2. Remove the DIMMs from CPU1, slots 0 and 4.
    3. Install the DIMMs from CPU0 into slots 0 and 4 on CPU1.
    4. Install the DIMMs from CPU1 into slots 0 and 4 on CPU0.
  3. Power on the server.
  4. Run the test that reported the error again.
    • If the error follows the DIMMs, replace them.

    • If the error remains in the same location, continue.

  5. Remove both CPUs.

    Refer to Replacing a CPU and Heatsink Assembly (FRU) in Sun Server X2-8 (formerly Sun Fire X4800 M2) Service Manual.

  6. Reinstall each CPUs into the opposite slot.

    In other words, switch the positions of the two CPUs.

  7. Power on the server.
  8. Run the test that reported the original error again.
  9. Review the test results.
    • If the error continues to appear in the same DIMM slot, most likely there is an issue with the DIMM slot. Return the board to the Support Center for replacement.

    • If the error follows the CPU, replace the CPU and confirm that the memory error does not return.

See Also