| Asset ID: |
1-71-1448379.1 |
| Update Date: | 2012-05-21 |
| Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1448379.1
:
/SP/console Appears Dead and/or Shows a Black Screen
| Related Items |
- Sun Fire X4150 Server
- Sun Blade X6450 Server Module
- Sun Fire X4540 Server
- Sun Netra X4200 M2 Server
- Sun Fire X4440 Server
- Sun Blade X6240 Server Module
- Sun Fire X4250 Server
- Sun Fire X4200 Server
- Sun Netra X4450 Server
- Sun Blade X6220 Server Module
- Sun Fire X4275 Server
- Sun Netra X4270 Server
- Sun Fire X4200 M2 Server
- Sun Blade X6270 Server Module
- Sun Netra X6270 M2 Server Module
- Sun Blade X6440 Server Module
- Sun Fire X4240 Server
- Sun Fire X4600 M2 Server
- Sun Fire X2270 Server
- Sun Server X2-8
- Sun Fire X4470 Server
- Sun Fire X4140 Server
- Sun Blade X6275 Server Module
- Sun Blade X6250 Server Module
- Sun Blade X6275 M2 Server Module
- Sun Fire X4170 Server
- Sun Fire X2250 Server
- Sun Fire X4270 M2 Server
- Sun Fire X4100 M2 Server
- Sun Blade X6420 Server Module
- Sun Fire X4600 Server
- Sun Fire X2270 M2 Server
- Sun Blade X6270 M2 Server Module
- Sun Fire X4640 Server
- Sun Fire X4100 Server
- Sun Netra X4250 Server
- Sun Fire X4270 Server
- Sun Server X2-4
- Sun Fire X4800 Server
- Sun Fire X4450 Server
- Sun Fire X4500 Server
- Sun Fire X4170 M2 Server
|
| Related Categories |
- PLA-Support>Sun Systems>x64>Server>SN-x64: MISC-SERVER
- .Old GCS Categories>Sun Microsystems>Servers>x64 Servers
|
In this Document
Applies to:
Sun Fire X2270 Server - Version Not Applicable and later
Sun Fire X4200 M2 Server - Version Not Applicable and later
Sun Fire X4250 Server - Version Not Applicable and later
Sun Blade X6420 Server Module - Version Not Applicable and later
Sun Fire X4800 M2 - Version Not Applicable and later
Information in this document applies to any platform.
Goal
How to troubleshoot the /SP/console when it appears inoperative.
Fix
To troubleshoot /SP/console it is usually helpful to start the /SP/console and the VGA console (via web Graphical User Interface (GUI) remote console redirection) both at the same time and watch both console screens during POST and up through the Operating System (O/S) launch process.
1. Start with the host off.
2. Next, ssh to the Service Processor (SP) and start the /SP/console
ssh xxx.xxx.xxx.xxx -l root
Using username "root".
Using keyboard-interactive authentication.
Password:
Sun(TM) Integrated Lights Out Manager
Version 2.0.2.5
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
>
> start /SP/console
Are you sure you want to start /SP/console (y/n)? y
3. Now, start a browser session to the SP and click on either "Launch Redirection" or "Launch Remote Console". The example below is ILOM 3.0:
4. When both console screens are active, power on the host and wait for the host to start Power On Self Test (POST).
From both console screens, you should see the system begin POST and if necessary you can interact with the system Basic Input / Output System (BIOS) from either screen:
After POST, you will see the beginning stage of O/S launch. For example the Grand Unified Bootloader (GRUB):
Very soon after the O/S launches one of the console screens usually will stop working depending on the console output setting of your O/S.
For example with Solaris, the eeprom setting dictates which console is active:
# eeprom | grep console
console=ttya
If console = 'ttya' then the serial console (/SP/console) will be active.
This is usually the case if the O/S was originally installed over the serial (non-GUI) port:
# eeprom | grep console
console=text
If console = 'text' then the VGA port (i.e., the redirected remote console) will be active.
This is usually the case if the O/S was originally installed via the GUI interface.
If you change the eeprom console setting, an O/S reboot will be needed.
Attachments
This solution has no attachment
