Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2117758.1
Update Date:2017-02-21
Keywords:

Solution Type  Technical Instruction Sure

Solution  2117758.1 :   How to configure the ILOM serial console on Exalytics systems  


Related Items
  • Exalytics In-Memory Machine X2-4
  •  
  • Exalytics In-Memory Machine X3-4
  •  
  • Exalytics In-Memory Machine X4-4
  •  
  • Exalytics In-Memory Machine X5-4
  •  
Related Categories
  • PLA-Support>Sun Systems>x86>Engineered Systems HW>SN-x64: EXALYTICS
  •  




Applies to:

Exalytics In-Memory Machine X4-4 - Version All Versions to All Versions [Release All Releases]
Exalytics In-Memory Machine X5-4 - Version All Versions to All Versions [Release All Releases]
Exalytics In-Memory Machine X3-4 - Version All Versions to All Versions [Release All Releases]
Exalytics In-Memory Machine X2-4 - Version All Versions to All Versions [Release All Releases]
x86 64 bit

Goal

How to configure the ILOM serial console on Exalytics systems

Solution

Note- this document covers "BareMetal" installations and does not cover "Virtualized" installations

For Exalytics systems if you want the ILOM console to receive normal console messages and to allow logins the following steps should be followed. Setting this up will allow access to the host and it's console messages from the ILOM cli using the "start /SP/console" command. Setting the system to send console output to the ILOM serial console will have the added benefit of capturing any console messages and boot information in the console log kept by the ILOM which can be helpful when troubleshooting issues.

The OS and the ILOM settings for the serial port speed need to match, start by checking the serial port speed setting in the ILOM. The default is normally set to 9600

From the WebGUI this can be checked by navigating to the ILOM Administration - Connectivity section, select the Serial Port tab and check the setting for the Host Serial Port.

From the ILOM cli this can be checked with the command "show /SP/serial/host"

-> show /SP/serial/host

/SP/serial/host
Targets:

Properties:
commitpending = (Cannot show property)
flowcontrol = none
pendingflowcontrol = none
pendingspeed = 9600
speed = 9600

For an Exalytics system you should also check the BIOS setup to ensure it's Serial Console setting also matches.
Enter the BIOS setup and navigate to "Advanced" -> "Serial Port Console Redirection" make sure "Console Redirection" is Enabled and check the "bits per second" value it should default to 9600.

Note - for these examples the default speed of 9600 is used but the speed may be set to a higher setting if needed. The requirement is that all the speed settings match so if it is changed in one location make sure the setting is changed similarly in the other locations configured in these directions.

After you have confirmed the serial port speed settings (or set them as desired) the OS needs to be configured. There are two pieces to setting up the serial console:
1 - setting the system to send the console messages to the serial console and
2 - configuring the OS to start a getty program so that a login process is invoked so that the host can be logged into.

To get the console messages sent to the serial console you need to edit the /boot/grub/grub.conf file. In this file you need to add "console=ttyS0,9600n8 console=tty1" to the end of the lines that begin with kernel.

For example:

# 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/mapper/VolGroup00-LogVol00
# initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Oracle Linux Server Unbreakable Enterprise Kernel (2.6.39-400.277.1.el6uek.x86_64)
        root (hd0,0)
        kernel /vmlinuz-2.6.39-400.277.1.el6uek.x86_64 ro root=/dev/mapper/VolGroup00-LogVol00 pci=nomsi rd_NO_LUKS LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_LVM_LV=VolGroup00/LogVol01 rd_LVM_LV=VolGroup00/LogVol00 KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM console=ttyS0,9600n8 console=tty1
        initrd /initramfs-2.6.39-400.277.1.el6uek.x86_64.img
title Oracle Linux Server Red Hat Compatible Kernel (2.6.32-504.el6.x86_64)
        root (hd0,0)
        kernel /vmlinuz-2.6.32-504.el6.x86_64 ro root=/dev/mapper/VolGroup00-LogVol00 pci=nomsi rd_NO_LUKS LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_LVM_LV=VolGroup00/LogVol01 rd_LVM_LV=VolGroup00/LogVol00 KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM console=ttyS0,9600n8 console=tty1
        initrd /initramfs-2.6.32-504.el6.x86_64.img

 

NOTE: in some el5 based OS images (Exalytics base image 1.0.0.x) the grub.conf file may also have a line showing something like "serial --unit=0 --speed=9600" If this line is in your grub.conf file then you will also need to edit the "--speed=" value to match the baud rate that is being used. In our examples we want to ensure it is set to 9600 like all of our other entries. But if you are setting the speed to a value other than 9600 make sure this line matches the new speed.

To get the login program running on the serial console we need to setup the system to start the agetty program. The process to do this differs between Linux OSs based on el5 and el6.

For el5 based OS images (Exalytics Image versions up to 1.0.0.7 and 2.0.0.0.el5) this may already be configured so that you just need to check and confirm the needed line is there and correct (make sure the serial settings match those that you checked earlier)

open the /etc/inittab file and look for the console line it should look similar to "co:2345:respawn:/sbin/agetty -h -t 60 ttyS0 9600 vt100-nav" If this line is not present in your inittab file add it to the bottom as shown in this example:

[root@localhost ~]# cat /etc/inittab
#
# inittab This file describes how the INIT process should set up
# the system in a certain run-level.
#
# Author: Miquel van Smoorenburg, <miquels@drinkel.nl.mugnet.org>
# Modified for RHS Linux by Marc Ewing and Donnie Barnes
#

# Default runlevel. The runlevels used by RHS are:
# 0 - halt (Do NOT set initdefault to this)
# 1 - Single user mode
# 2 - Multiuser, without NFS (The same as 3, if you do not have networking)
# 3 - Full multiuser mode
# 4 - unused
# 5 - X11
# 6 - reboot (Do NOT set initdefault to this)
#
id:3:initdefault:

# System initialization.
si::sysinit:/etc/rc.d/rc.sysinit

l0:0:wait:/etc/rc.d/rc 0
l1:1:wait:/etc/rc.d/rc 1
l2:2:wait:/etc/rc.d/rc 2
l3:3:wait:/etc/rc.d/rc 3
l4:4:wait:/etc/rc.d/rc 4
l5:5:wait:/etc/rc.d/rc 5
l6:6:wait:/etc/rc.d/rc 6

# Trap CTRL-ALT-DELETE
ca::ctrlaltdel:/sbin/shutdown -t3 -r now

# When our UPS tells us power has failed, assume we have a few minutes
# of power left. Schedule a shutdown for 2 minutes from now.
# This does, of course, assume you have powerd installed and your
# UPS connected and working correctly.
pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down"

# If power was restored before the shutdown kicked in, cancel it.
pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled"

# Run gettys in standard runlevels
1:2345:respawn:/sbin/mingetty tty1
2:2345:respawn:/sbin/mingetty tty2
3:2345:respawn:/sbin/mingetty tty3
4:2345:respawn:/sbin/mingetty tty4
5:2345:respawn:/sbin/mingetty tty5
6:2345:respawn:/sbin/mingetty tty6

# Run xdm in runlevel 5
x:5:respawn:/etc/X11/prefdm -nodaemon
#
#Added this for remote host connection using ILOM CLI using start /SP/console
co:2345:respawn:/sbin/agetty -h -t 60 ttyS0 9600 vt100-nav

For el6 based OS images (Exalytics Image versions 2.0.0.0.el6 and later) the agetty program for the serial console is started by creating a configuration file in the /etc/init directory.

Create the file /etc/init/ttyS0.conf using vi (or your preferred text editor) with the following contents:
(Or you can download this file: ttyS0.conf and just copy it to /etc/init )

# ttyS0 - agetty
#
# This service maintains an agetty on /dev/ttyS0.
#
stop on runlevel [S016]
start on runlevel [2345] and stopped rc

respawn
exec /sbin/agetty -L 9600 ttyS0

After you have the console entry added to the kernel line of grub.conf and you have configured agetty to start the login program reboot the server. After the system completes it's reboot you should be able to log into the ILOM and start the ILOM serial console, you will now see all console messages output to this connection and be presented with a login to access the host.

-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y

Serial console started. To stop, type ESC (

Oracle Linux Server release 5.8
Kernel 2.6.32-400.11.1.el5uek on an x86_64

exalytics0.localdomain login:

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback