Sun Fire T2000 Server
 
Sun Fire T1000 Server
 
Sun SPARC Enterprise T2000 Server
 

GCS>Sun Microsystems>Servers>CMT Servers
 

Summary:

This document addresses failures in the Sun Fire [TM] T1000 or T2000 Boot process. The symptoms can be either the system reporting some type of error or a hang where no errors or messages are reported.

Symptoms:

- Boot Fails

- Boot Hangs

- Console goes away

- Can't see the ok prompt

Troubleshooting a boot problem needs to focus on whether the symptom is a failure with some type of message displayed, or if the console just seems to stop or  hang .

1. If there is an error message or if the system powers down and drops the console back to the SC> prompt proceed to step 5 .

2. Verify a functional connection to the proper port. This may be the Net Management port, or the Serial Management port. Reference <Document: 1009721.1>  Establishing a connection to Sun Fire T1000 or T2000 System Controller 

3. If successfully connected to the correct Management port, but unable to access the console environment the user may need to redirect the console to the System Controller. Refer to <Document: 1017958.1>  Redirecting the console to the default setting for Sun Fire T1000/T2000 

4. If the console is responding and there is some type of error message from POST (Power On Self Test) go to Step #5 . If the console is still not responding there might be a deeper problem. For additional support contact My Oracle Support (MOS).

5. Verify That POST diagnostics pass. This is simple enough, simply check the console for error messages, if there were none the banner should be displayed.

6. Verify that the boot device can be seen. Refer to <Document: 1011227.1>   Verify that the Boot devices can be seen for the Sun Fire T1000/T2000 

7. Verify that there are no boot media problems.

-Check to be sure that the user is booting from supported Solaris Media. Refer <Document: 1003034.1>  Flash PROM patches / Minimum Solaris[TM] Operating System revisions for Sun systems . Check and make sure that the media works successfully in another (similar) system, or use a second source of media.

-If booting over the network be sure that the add_install_client was done for a sun4v system. Refer to <Document: 1018938.1>    Jumpstart of UltraSPARC  T1 based system panics with "BAD TRAP: type=10"

At this point, if you have validated that each troubleshooting step above  is true for your environment, and the issue still exists, further troubleshooting is required. Gather console logs, any errors that are seen, and showlogs -v from the system controller. For additional support contact MOS.

This document contains normalized content and is managed by the the Domain Lead
(s) of the respective domains. To notify content owners of a knowledge gap
contained in this document, and/or prior to updating this document, please
contact the domain engineers that are managing this document via the “Document
Feedback” alias(es) listed below:

Domain Lead: [email protected]
Feedback Alias: [email protected]

This solution has no attachment