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

Document Information

Using This Documentation

Hardware Installation

Operating System Installation

Administration, Diagnostics, and Service

Diagnostics Guide

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

How to Use the Oracle ILOM Web Interface to View the Sensor Readings

How to Use the Oracle ILOM Command-Line Interface to View the Sensor Readings

Viewing Fault Status

How to View Fault Status Using the Oracle ILOM Web Interface

How to View Fault Status Using the Oracle ILOM Command-Line Interface

Clearing Faults

How to Clear Faults Using the Oracle ILOM Web Interface

How to Clear Faults Using the Oracle ILOM Command-Line Interface

Viewing the Oracle ILOM System Event Log

How to View the System Event Log Using the Oracle ILOM Web Interface

How to View the System Event Log With the Oracle ILOM Command-Line Interface

Clearing the System Event Log

How to Clear the System Event Log Using the Oracle ILOM Web Interface

How to Clear the System Event Log Using the Oracle ILOM Command-Line Interface

Interpreting Event Log Time Stamps

Resetting the SP

How to Reset the Oracle ILOM SP Using the Web Interface

How to Reset the Oracle ILOM SP Using the Command-Line Interface

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

Standard Scripts

How to Perform Immediate Burn-In Testing

How to Create and Save Scripts for Deferred Burn-in Testing

Viewing the Pc-Check Results

How to View Pc-Check Files With the Text File Editor

How to View Test Results Using Show Results Summary

How to Print the Results of Diagnostics Tests

U-Boot Diagnostic Start-Up Tests

U-Boot Test Options

Running the U-Boot Diagnostic Tests and Viewing the Results

How to Run the U-Boot Diagnostic Tests

U-Boot Diagnostic Test Output

Sample SP Environmental Variables Showing U-Boot Test Status

Index

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.