JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Sun Fire X4800 Server Product Documentation
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

DIMM Fault LEDs

About DIMM Fault LEDs

How to Read the DIMM Fault LEDs

Identifying DIMM Error Messages

How BIOS POST Memory Testing Works

How to Interpret DIMM Error Messages in the SEL

Correcting DIMM Errors

How to Isolate and Correct DIMM ECC Errors

BIOS POST

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

BIOS POST Errors

Using the ILOM to Monitor the Host

Viewing the ILOM Sensor Readings

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

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

Viewing Fault Status

How to View Fault Status Using the ILOM Web Interface

How to View Fault Status With the Command-Line Interface

Clearing Faults

How to Clear Faults in the Web Interface

How to Clear Faults Using the Command-Line Interface

Viewing the ILOM System Event Log

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

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

Clearing the System Event Log

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

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

Interpreting Event Log Time Stamps

Resetting the SP

How to Reset the ILOM SP Using the Web Interface

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

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

Using SunVTS Diagnostics Software

Introduction to SunVTS Diagnostic Test Suite

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

Index

How to Diagnose Server Problems With the Bootable Diagnostics CD

SUNVTS.7.0ps8 or later software is preinstalled with Oracle Solaris 10 Operating System on the server. The server is also shipped with the Bootable Diagnostics CD. This CD is designed so that the server boots from the CD. This CD boots the Solaris operating system and starts SunVTS software. Diagnostics tests run and write output to log files that the service technician can use to determine the problem with the server.

Before You Begin

You must have a USB DVD drive, keyboard, and mouse, and as well as a monitor attached to the server for booting over the CD locally. For booting over a Remote Console, see the instructions in the Oracle Integrated Lights Out Manager (ILOM) 3.0 Supplement for the Sun Fire X4800 Server for setting up the remote console.

  1. With the server powered on, insert the Bootable Diagnostics CD into the DVD-ROM drive.
  2. Do one of the following:
    • To run SunVTS one time only, press F8 during the reboot and select the DVD-ROM drive as the boot device.
    • To change the boot device to the DVD-ROM in the BIOS:
      1. Press F2 during the start of the reboot so that you can change the BIOS setting for boot-device priority.
      2. When the BIOS Main menu appears, navigate to the BIOS Boot menu.

        Instructions for navigating within the BIOS screens are available on the BIOS screens.

      3. On the BIOS Boot menu screen, select Boot Device Priority.

        The Boot Device Priority screen appears.

      4. Select the DVD-ROM drive to be the primary boot device.
      5. Save and exit the BIOS screens.
      6. Reboot the server.

        When the server reboots from the CD in the DVD-ROM drive, the Solaris OS boots, and the SunVTS software starts and opens its first GUI window.

  3. Press Enter or click the Start button when you are prompted to start the tests.

    The test suite runs until it encounters an error or the test is completed.


    Note - The CD takes approximately nine minutes to boot.


  4. When the test is completed, review the log files generated during the test.

    SunVTS software provides access to four different log files:

    • SunVTS test error log – Contains time-stamped SunVTS test error messages. The log file path name is /var/sunvts/logs/sunvts.err. This file is not created until a SunVTS test failure occurs.

    • SunVTS kernel error log – Contains time-stamped SunVTS kernel and SunVTS probe errors. SunVTS kernel errors are errors that relate to running SunVTS, and not to testing of devices. The log file path name is /var/sunvts/logs/vtsk.err. This file is not created until SunVTS reports a SunVTS kernel error.

    • SunVTS information log – Contains informative messages that are generated when you start and stop the SunVTS test sessions. The log file path name is /var/sunvts/logs/sunvts.info. This file is not created until a SunVTS test session runs.

    • Solaris system message log – A log of all the general Solaris events logged by syslogd. The path name of this log file is /var/adm/messages.

    To view a log file:

    1. Click the Log button.

      The log file window is displayed.

    2. Specify the log file that you want to view by selecting it from the Log file windows.

      The content of the selected log file is displayed in the windows.

    3. Use the three lower buttons to perform the following actions:
      • Print the log file.

        A dialog box appears for you to specify your printer options and printer name.

      • Delete the log file.

        The file remains displayed, but it will be gone the next time you try to display it.

      • Close the log file window.

        The window closes.


        Note - To save the log files, you must save them to another networked system or a removable media device. When you use the Bootable Diagnostics CD, the server boots from the CD. Therefore, the test log files are not on the server hard disk drive, and they are deleted when you power cycle the server.