Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1010752.1
Update Date:2009-02-18
Keywords:

Solution Type  Technical Instruction Sure

Solution  1010752.1 :   Sun Fire [TM] E2900 Server: Power On Takes a Long Time  


Related Items
  • Sun Fire E2900 Server
  •  
Related Categories
  • GCS>Sun Microsystems>Servers>Midrange Servers
  •  

PreviouslyPublishedAs
214844


Description
Customers have reported that the Sun Fire[TM] E2900 Server takes a long time to power on. A considerable time passes before the LEDs indicate that the platform is powered on.


Steps to Follow
1) Power on the Sun Fire Server.

The system controller runs SCPOST.   If the system controller SCPOST level is set

to max, this process takes approximately 20 minutes.  While SCPOST is running,

there are no LEDs lit on the front panel.  It is the responsibility of  ScApp to light

these LEDs, and ScApp does not load until SCPOST finishes running.  It is

particularly confusing that The  Source A & B  LEDs do not light until ScApp is

loaded.

2) After powering on the platform, do the following:

a) Open the front doors, and you'll see the green LEDS flashing on the four PSUs.

b) Look at Fan 3, which is spinning to provide cooling to the system controller.

3) Monitor the progress of SCPOST by establishing a connection to Serial Port A

on the back of the server.

When the lom shell prompt appears, the  System Active  and   Source A & B  LEDs on the front panel are lit.



Product
Sun Fire E2900 Server

Internal Comments
The SCPOST takes longer to run on a Sun Fire E2900 Server than on a Sun Fire[TM] V1280 because the Sun Fire E2900 ships with a version 2 system controller. This version has four times as much memory as the original system controller:



System Controller, Version 2 = 128 MB memory


System Controller, Version 1 = 32 MB memory


The bulk of the 20 minutes to run a max level SCPOST on a system
controller, version 2, is taken up by the memory tests:


Hardware Reset...


@(#) SYSTEM CONTROLLER(SC) POST 38 2003/11/18 21:21


PSR = 0x044010e5


PCR = 0x04004000


Memory size = 128MB


SelfTest running at DiagLevel:0x40


.


.


.


Memory    Test


        Memory Address
                 Test


        MemBankAddrTest:
start address = 0x00010000


        MemBankAddrTest:
start address = 0x04000000


        MemBankAddrTest:
start address = 0x08000000


        MemBankAddrTest:
start address = 0x0c000000


        Memory Walking
one Word         Test


        WalkingBankTest:
start address = 0x00010000


        WalkingBankTest:
start address = 0x04000000


        WalkingBankTest:
start address = 0x08000000


        WalkingBankTest:
start address = 0x0c000000


        Memory Walking
zero Word        Test


        WalkingBankTest:
start address = 0x00010000


        WalkingBankTest:
start address = 0x04000000


        WalkingBankTest:
start address = 0x08000000


.


.


.


POST Complete.


Although, you set SCPOST to the max level after replacing an
IB/SSC assembly, use the lom shell command setupsc to set it to
min.


lom>
setupsc


System Controller Configuration


-------------------------------


SC POST diag Level [max]: min


Host Watchdog [enabled]:


Rocker Switch [enabled]:


Secure Mode [off]:


lom>


 


The SCPOST level min takes approximately 2 minutes to run.


E2900, power, on, SCPOST, level, max
Previously Published As
76426

Change History
Date: 2004-05-26
User Name: c8840
Action: Approved
Comment: I edited this document, and then submitted it for publication.
Version: 0
Date: 2004-05-24
User Name: c8840
Action: Accepted
Comment:
Version: 0

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback