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

DIMM Hardware


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


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


How to Gather Service Visit Information

The first step in determining the cause of the problem with the server is to gather whatever information you can from the service-call paperwork or the on-site personnel. Use the following general guideline steps when you begin troubleshooting.

  1. Collect information about the following items:
    • Events that occurred prior to the failure

    • Whether any hardware or software was modified or installed

    • Whether the server was recently installed or moved

    • How long the server exhibited symptoms

    • The duration or frequency of the problem

  2. Document the server settings before you make any changes.

    If possible, make one change at a time to isolate potential problems. In this way, you can maintain a controlled environment and reduce the scope of troubleshooting.

  3. Take note of the results of any change you make. Include any errors or informational messages.
  4. Check for potential device conflicts, especially if you have added a new device.
  5. Check for version dependencies, especially with third-party software.