You are on page 1of 7

9/9/2014

Document

/SP/console Appears Dead and/or Shows a Black Screen (Doc ID 1448379.1)


In this Document
Goal
Solution

APPLIES TO:
Sun Blade X6275 M2 Server Module - Version Not Applicable and later
Sun Netra X4270 Server - Version Not Applicable and later
Sun Fire X4270 M2 Server - Version Not Applicable and later
Sun Blade X6240 Server Module - Version Not Applicable and later
Sun Fire X4100 M2 Server - Version Not Applicable and later
Information in this document applies to any platform.
***Checked for relevance on 18-Nov-2013***

GOAL
To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or
start a discussion in the My Oracle Support Community - Sun x86 Systems

How to troubleshoot the /SP/console when it appears inoperative.

SOLUTION
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

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=sy6rj54ur_94

1/7

9/9/2014

Document

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:

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=sy6rj54ur_94

2/7

9/9/2014

Document

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=sy6rj54ur_94

3/7

9/9/2014

Document

After POST, you will see the beginning stage of O/S launch on both, for example the Grand Unified Bootloader
(GRUB):

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=sy6rj54ur_94

4/7

9/9/2014

Document

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=sy6rj54ur_94

5/7

9/9/2014

Document

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.
For Linux:
# dmesg | grep console
https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=sy6rj54ur_94

6/7

9/9/2014

console [ttyS0] enabled


console [tty0] enabled

Document

--> Serial port


--> VGA port

Edit grub config:


/boot/grub/grub.conf
Change from:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
#
all kernel and initrd paths are relative to /boot/, eg.
#
root (hd0,0)
#
kernel /vmlinuz-version ro root=/dev/sda3
#
initrd /initrd-version.img
#boot=/dev/sda
default=1
timeout=5
title Oracle Linux Server (2.6.18-164.el5xen)
root (hd0,0)
kernel /xen.gz-2.6.18-164.el5
module /vmlinuz-2.6.18-164.el5xen ro root=LABEL=/
module /initrd-2.6.18-164.el5xen.img
title Oracle Linux Server-base (2.6.18-164.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-164.el5 ro root=LABEL=/
initrd /initrd-2.6.18-164.el5.img

to:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
#
all kernel and initrd paths are relative to /boot/, eg.
#
root (hd0,0)
#
kernel /vmlinuz-version ro root=/dev/sda3
#
initrd /initrd-version.img
#boot=/dev/sda
default=1
timeout=5
serial --unit=0 --speed=9600
terminal --timeout=5 serial console
title Oracle Linux Server (2.6.18-164.el5xen)
root (hd0,0)
kernel /xen.gz-2.6.18-164.el5 com1=9600 console=com1
module /vmlinuz-2.6.18-164.el5xen ro root=LABEL=/ console=ttyS0,9600
module /initrd-2.6.18-164.el5xen.img
title Oracle Linux Server-base (2.6.18-164.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-164.el5 ro root=LABEL=/ earlylprintk=ttyS0,9600
console=ttyS0,9600
initrd /initrd-2.6.18-164.el5.img

# reboot

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=sy6rj54ur_94

7/7