Asset ID:	1-75-1019096.1
Update Date:	2010-08-30
Keywords:

---

Solution Type  Troubleshooting Sure

Solution  1019096.1 :   Sun Fire[TM] V215 and V245 Troubleshooting Tips  


PreviouslyPublishedAs
234761

Description
This document provides some tips and guidelines that can assist the user in troubleshooting the Sun Fire[TM] V215/V245 servers

Steps to Follow
V215 and V245 Troubleshooting Tips
Before replacing systemboard the following actions are recommended:

Many times the system itself will give clues as to what the problem is.  Some of the best sources of this data are the status LEDs and the results of self testing and monitoring of environmental conditions.



1.) Check the status of the LEDs
----------------------------------------------

V215 Sun System Handbook Link:
https://support.oracle.com/handbook_private/General/LEDs/SunFireV215_LEDs.html

V245 Sun System Handbook Link:
https://support.oracle.com/handbook_private/General/LEDs/SunFireV245_LEDs.html

2.) Using POST (Power On Self Tests)
--------------------------------------------------------

a.) See if POST has already failed a component using the "show-post-results" command:
     
       {1} ok show-post-results

       CPU: 0

       Status 0=Pass, Non-Zero=Fail (%o0): ffffffffffffffff

       Message String               (%o1): Motherboard IO-Bridge 1, CPU

       Board Descriptor             (%o2): ffffffdfffffffff
       
b.) Check to see if POST has failed and ASR has marked a component failed. That can be seen  by use of the OBP command ".asr"
          ok .asr
          net0&1        Disabled by
                        FWDIAG OBDIAG failure

c.) Run a Max level POST to test for failures:
     
         
To run a max POST the verbosity and diag-level variable should be set to max. Once done toggle back to ALOM sc> prompt and issue a "reset -y" command. Immediately issue a "console -f" command to switch back to the console to see the POST output.


{1} ok setenv verbosity max
verbosity =             max
{1} ok setenv diag-level max
diag-level =            max
{1} ok sc>    <------- [At this point system was toggled ("#" then ".") to ALOM sc> prompt]
sc> reset -y
SC Alert: SC Request to Reset Host.

SC Alert: Host System has Reset
sc> console -f
Warning: User <auto> currently has write permission to this console and forcibly removing them will terminate any current write actions and all work will be lost.  Would you like to continue? [y/n]y

Enter #. to return to ALOM.

 ******  POST Running ******
 .
 . "REMOVED TEXT FOR BRIEVETY"
 .
 .
 
0> POST Passed all devices.
0>
0> POST: Return to OBP.


3.) Check to see if some environmental problem has been detected
---------------------------------------------------------------------------------------------------

The system will monitor environmental sensors and report problems it finds.  If the problem is severe enough it may power the system down.In such circumstances there are a couple of ways to determine what is happening.The ALOM command "showenvironment" will show all the power and environmental sensor info. Also the ALOM command "showlogs -v" will DISPLAY any problems detected
 
 
4.) Checking For Known Product Issues
---------------------------------------------------------

Often times knowing what the known problems are with a product can save uneeded downtime and troubleshooting efforts. 


Product
Sun Fire V245 Server
Sun Fire V215 Server

Internal Comments
The Product Issues for Seattle can be found at:

    http://panacea/twiki/bin/view/Products/ProdIssuesSFV215V245

V215, V245, troubleshooting tips, systemboard, POST, LED, product issues

Change History
2008-11-18 Volkmar Grote (vg117021)
Made links clickable, so off we go now?




Attachments

This solution has no attachment