Diagnostics Process - Netra SPARC T3-1B Server Module HTML Document Collection

Skip Navigation Links
Exit Print View
	Netra SPARC T3-1B Server Module HTML Document Collection

Oracle Technology Network

Document Information

Using This Documentation

Related Documentation

Support and Accessibility

Planning the Installation

Shipping Kit Inventory List

Preinstalled Software

Front and Rear Panel Components

Server Module Cabling

Plan Communication With the Server Module During Installation

Installing the Server Module

Handling Precautions

ESD Precautions

Tools Needed for Installation

Optional Component Installation

Modular System Chassis Preparation

Insert the Server Module Into the Chassis

Communicating With the Server Module During Startup

Monitor the Diagnostic Messages

Powering On the Server Module for the First Time

Initial Power-On Task Overview

Power On the System for the First Time

Configure the System

Install Oracle Solaris Software From the Network

Oracle Solaris Configuration Settings

Assign a Static IP Address to the Service Processor

Understanding System Administration Resources

Oracle ILOM Overview

Platform-Specific Oracle ILOM Features

Oracle Solaris OS Overview

OpenBoot Overview

Oracle VM Server for SPARC Overview

Multipathing Software

Hardware Management Pack Overview

Source for Downloading Hardware Management Pack Software

Hardware Management Pack Documentation

Accessing the Server

Log In to Oracle ILOM

Log In to the System Console

Display the ok Prompt

Display the Oracle ILOM -> Prompt

Use a Local Graphics Monitor

Oracle ILOM Remote Console

Controlling the Server

Power On the Server

Power Off the Server

Reset the Server From the Oracle Solaris OS

Reset the Server From Oracle ILOM

Reset the SP to Default Values

Configuring Hardware RAID

Hardware RAID Support

Important Hardware RAID Guidelines

Disk Zones for SPARC T3-1 Servers With Sixteen-Disk Backplanes

Displaying Disk Zone Information

Enabling and Disabling Disk Zoning In the Field

Prepare to Use the FCode Utility

FCode Utility Commands

Create a Hardware RAID Volume

Hot Spare Drives in RAID Volumes (LSI)

Determining If a Drive Has Failed

RAID Drive Replacement Strategies

Locate Device Paths

Changing Server Identification Information

Change Customer FRUdata Information

Change System Identifier Information

Configuring Policy Settings

Specify Cooldown Mode

Restore Host Power State at Restart

Specify Host Power State at Restart

Disable or Re-Enable Power-On Delay

Specify Parallel Boot of the SP and Host

Configure Host Behavior With the Keyswitch State

Configuring Network Addresses

SP Network Address Options

Disable or Re-Enable Network Access to the SP

Display the DHCP Server IP Address

Display the Host MAC Address

Using an In-band Connection to the SP

Configuring Boot Mode

Boot Mode Overview

Configure the Host Boot Mode of Oracle VM Server for SPARC

Change the Host Boot Mode Behavior at Reset

Manage the Host Boot Mode Script

Display Host Boot Mode Expiration Date

Override OpenBoot PROM Settings to Reset the Server

Configuring Server Behavior at Restart

Specify Behavior When the Host Resets

Specify Behavior When the Host Stops Running

Set the Boot Timeout Interval

Specify Behavior at Boot Timeout

Specify Behavior if Restart Fails

Specify Maximum Restart Attempts

Configuring Devices

Unconfigure a Device Manually

Reconfigure a Device Manually

Monitoring the Server

Monitoring Faults

Enabling Automatic System Recovery

Display Server Components

Locate the Server

Updating the Firmware

Display the Firmware Version

Update the Firmware

Display OpenBoot Version

Display POST Version

Identifying WWN-Designated SAS2 Devices

World Wide Name Syntax

probe-scsi-all Output Example (SPARC T3-1, Eight-Disk Backplane)

probe-scsi-all Output Example (SPARC T3-1, Sixteen-Disk Backplane)

probe-scsi-all Output Example (SPARC T3-4)

Identify a Disk Slot Using probe-scsi-all (OBP)

Identify a Disk Slot Using prtconf (Oracle Solaris, Onboard Controllers)

Identify a Disk Slot Using prtconf (Oracle Solaris, Single Initiator)

WWN Syntax in an OS Installation on a Specific Device

WWN Syntax in an OS Installation on a RAID Volume

Identifying Components

Front and Rear Panel Components

Illustrated Parts Breakdown

Detecting and Managing Faults

Diagnostics Overview

Diagnostics Process

Diagnostics LEDs

Managing Faults (Oracle ILOM)

Oracle ILOM Troubleshooting Overview

Access the SP (Oracle ILOM)

Display FRU Information (show Command)

Check for Faults (show faulty Command)

Check for Faults (fmadm faulty Command)

Clear Faults (clear_fault_action Property)

Service-Related Oracle ILOM Command Summary

Interpreting Log Files and System Messages

Check the Message Buffer (dmesg Command)

View the System Message Log Files

List FRU Status (prtdiag Command)

Managing Faults (Oracle Solaris PSH)

Oracle Solaris PSH Technology Overview

PSH-Detected Fault Example

Check for PSH-Detected Faults

Clear PSH-Detected Faults

Managing Faults (POST)

Oracle ILOM Properties That Affect POST Behavior

Configure How POST Runs

Run POST With Maximum Testing

Interpret POST Fault Messages

Clear POST-Detected Faults

POST Error Message Syntax

Managing Components (ASR)

Display System Components

Disable System Components

Enable System Components

Checking if Oracle VTS Software Is Installed

Oracle VTS Overview

Check if Oracle VTS Software Is Installed

Preparing for Service

General Safety Information

Tools Needed for Service

Find the Modular System Serial Number

Find the Server Module Serial Number

Locate the Server Module

Removing the Server Module From the Modular System for Service

Servicing Hard Drives

Drive Hot-Plugging Rules

Replace or Add a Drive

Remove a Drive Filler

Install a Drive Filler

Servicing Memory

Locate a Faulty DIMM (LEDs)

Install a Replacement DIMM

Clear the Fault and Verify the Functionality of the Replacement DIMM

Verify DIMM Functionality

DIMM Configuration Reference

Servicing a REM

Servicing a FEM

Servicing a Service Processor Card

Remove the Service Processor Card

Install the Service Processor Card

Servicing the ID PROM

Remove the ID PROM

Install the ID PROM

Verify the ID PROM

Servicing a USB Flash Drive

Remove a USB Flash Drive

Install a USB Flash Drive

Servicing the Battery

Replace the Battery

Replacing the Server Module Enclosure Assembly

Transfer Components to Another Enclosure Assembly

Returning the Server Module to Operation

Replace the Cover

Install the Server Module Into the Modular System

Start the Server Module Host

Diagnostics Process

The following flowchart illustrates the complementary relationship of the different diagnostic tools and indicates a default sequence of use.

image:Flowchart diagram shows the sequence of diagnostic tasks.

The following table provides brief descriptions of the troubleshooting actions shown in the flowchart. The table also provides links to topics with additional information on each diagnostic action.

Table 7 Diagnostic Flowchart Reference Table

Diagnostic Action	Possible Outcome	Additional Information
Flowchart item 1. Check the Power OK LED.	The Power OK LED is located on the front of the server module. If this LED is not lit, check the power source and ensure that the server module is properly installed in the modular system chassis.	Diagnostics LEDs
Flowchart item 2. Run the Oracle ILOM `show faulty` command to check for faults.	The `show faulty` command displays the following kinds of faults: Environmental and configuration faults PSH-detected faults POST-detected faults Faulty FRUs are identified in fault messages using the FRU name. All Oracle ILOM detected fault messages begin with the characters “SPT”. For additional information on a reported fault, including possible corrective action, go to: http://support.oracle.com Search for the message ID contained in that fault message. Then read the further information about that fault.	Service-Related Oracle ILOM Command Summary Check for Faults (`show` `faulty` Command)
Flowchart item 3. Check the Oracle Solaris log files for fault information.	The Oracle Solaris message buffer and log files record system events, and provide information about faults. If system messages indicate a faulty device, replace the FRU. For more diagnostic information, review the Oracle VTS report (flowchart item 4).	Interpreting Log Files and System Messages
Flowchart item 4. Run Oracle VTS software.	Oracle VTS is an application you can run to exercise and diagnose FRUs. To run Oracle VTS, the server module must be running the Oracle Solaris OS. If Oracle VTS reports a faulty device, replace the FRU. If Oracle VTS does not report a faulty device, run POST (flowchart item 5).	Checking if Oracle VTS Software Is Installed
Flowchart item 5. Run POST.	POST performs basic tests of the server module components and reports faulty FRUs.	Managing Faults (POST) Oracle ILOM Properties That Affect POST Behavior
Flowchart item 6. Check if the fault is environmental.	Determine if the fault is an environmental fault or a configuration fault. If the fault listed by the `show faulty` command displays a temperature or voltage fault, then the fault is an environmental fault. Environmental faults can be caused by faulty FRUs, or by environmental conditions such as when computer room ambient temperature is too high, or airflow is blocked. When the environmental condition is corrected, the fault will automatically clear. For additional information on a reported fault, including possible corrective action, go to: http://support.oracle.com Search for the message ID contained in that fault message. Then read the further information about that fault.	Check for Faults (`show` `faulty` Command)
Flowchart item 7. Determine if the fault was detected by PSH.	If the fault message does not begin with the characters “SPT”, the fault was detected by the PSH feature. For additional information on a reported fault, including possible corrective action, go to: http://support.oracle.com Search for the message ID contained in that fault message. Then read the further information about that fault. After the FRU is replaced, perform the procedure to clear PSH detected faults.	Managing Faults (Oracle Solaris PSH) Clear PSH-Detected Faults
Flowchart item 8. Determine if the fault was detected by POST.	POST performs basic tests of the server module components and reports faulty FRUs. When POST detects a faulty FRU, POST logs the fault and if possible, takes the FRU offline. POST detected FRUs display the following text in the fault message: `Forced fail` `reason` where `reason` is the name of the power-on routine that detected the failure.	Managing Faults (POST) Clear POST-Detected Faults
Flowchart item 9. Contact technical support.	The majority of hardware faults are detected by the server module's diagnostics. In rare cases a problem might require additional troubleshooting. If you are unable to determine the cause of the problem, contact your service representative for support.	Support and Accessibility

Related Information

SPARC T3 Series Servers Administration Guide
Diagnostics Overview
Diagnostics LEDs
Managing Faults (Oracle ILOM)
Interpreting Log Files and System Messages
Managing Faults (Oracle Solaris PSH)
Managing Faults (POST)
Managing Components (ASR)
Checking if Oracle VTS Software Is Installed

Copyright © 2011, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices

Previous

Next