JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Sun Fire X4640 Server Diagnostics Guide     Sun Fire X4640 Server Documentation Library
search filter icon
search icon

Document Information

Using This Documentation

Product Downloads

About This Documentation (PDF and HTML)

We Welcome Your Comments

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 Inspect the Outside of the Server

How to Inspect the Inside of the Server

Troubleshooting DIMM Problems

DIMM Fault LEDs

DIMM Population Rules

How to Isolate and Correct DIMM ECC Errors

Identifying Correctable DIMM Errors (CEs)

Identifying BIOS DIMM Error Messages

Using the ILOM to Monitor the Host

Viewing the ILOM Sensor Readings

Viewing the ILOM System Event Log

Clearing the Faults from the System Event Log

Interpreting Event Log Time Stamps

Using SunVTS Diagnostics Software

Introduction to SunVTS Diagnostic Test Suite

SunVTS Documentation

How to Diagnose Server Problems With the Bootable Diagnostics CD

Creating a Data Collector Snapshot

How To Create a Snapshot With the ILOM Web Interface

How To Create a Snapshot With the ILOM Command-Line Interface

Resetting the SP

How to Reset the ILOM SP Using the Web Interface

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

Index

How to Gather Service Visit Information

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, in order 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 before you add a new device.
  5. Check for version dependencies, especially with third-party software.