IBM HS40 - BladeCenter - 8839 User manual

BladeCenter
Serial over LAN Setup Guide


BladeCenter
Serial over LAN Setup Guide


Note: Before using this information and the product it supports, read the general information in Appendix A, “Getting help
and technical assistance,” on page 51 and Appendix B, “Notices,” on page 53.
Twelfth Edition (November 2009)
© Copyright IBM Corporation 2009.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.

Contents
Chapter 1. Introduction ........1
Hardware and firmware requirements ......2
Hardware requirements..........2
Firmware requirements ..........3
Checking firmware versions ........4
Starting the BladeCenter management-module Web
interface ................5
Chapter 2. General configuration ....7
Configuring the global SOL settings for the
BladeCenter unit .............7
Configuring the management module ......9
Installing and configuring SSH for SOL .....11
Enabling SOL for blade servers ........12
Updating and configuring the blade server BIOS . . 13
Chapter 3. Operating system
configuration ............15
Linux configuration ...........15
Red Hat Enterprise Linux ES 2.1 configuration . 15
SUSE SLES 8.0 configuration .......19
Installing the Ethernet controller device driver for
Linux operating systems .........21
Microsoft Windows 2003 Standard Edition
configuration ..............22
Chapter 4. Special component
requirements ............25
Configuring the BladeCenter HS22 Type 7870 blade
server ................25
Configuring the BladeCenter HS20 Type 8832 and
HS20 Type 8843 blade servers ........27
HS20 Type 8832 SOL jumper placement ....28
Updating the integrated systems management
processor firmware ...........28
Updating the Broadcom Ethernet controller
firmware ..............29
Configuring the BladeCenter HS40 Type 8839 blade
server ................29
Updating the Baseboard Management Controller
firmware ..............29
Updating and configuring the BIOS .....30
Configuring the BladeCenter JS20 Type 8842 blade
server ................30
Updating the open firmware (BIOS) .....31
Updating the integrated systems management
processor firmware ...........31
Updating the Broadcom Ethernet controller
firmware ..............32
Configuring the IBM 4-Port Gb Ethernet Switch
Module for BladeCenter ..........32
Configuring the Nortel Networks Layer 2-7 GbE
Switch Module for IBM BladeCenter ......33
Configuring the Cisco Systems Intelligent Gigabit
Ethernet Switch Module for the IBM BladeCenter . 34
Connecting an Intelligent Copper Pass-thru Module 35
Chapter 5. Using SOL ........37
Starting an SOL session ..........37
Starting a command-line Telnet connection . . . 38
Establishing a serial connection.......38
Starting a command-line Secure Shell (SSH)
connection..............39
Starting an SOL session from the command-line
interface ..............39
Ending an SOL session ..........40
Monitoring SOL session status ........41
Restarting a blade server through SOL .....43
Mounting and unmounting media for Linux
operating systems ............44
Chapter 6. Troubleshooting SOL....45
Management module indicates that blade server
does not support SOL ...........45
Blade server shows SOL status of Not Ready . . . 46
SOL session opens and drops ........47
Trouble entering SOL commands or receiving
double prompts .............48
Garbage characters in an SOL session......48
Appendix A. Getting help and technical
assistance .............51
Before you call .............51
Using the documentation ..........51
Getting help and information from the World Wide
Web.................52
Software service and support ........52
Hardware service and support ........52
IBM Taiwan product service .........52
Appendix B. Notices .........53
Trademarks ..............53
Important notes .............53
Index ...............55
© Copyright IBM Corp. 2009 iii

iv BladeCenter: Serial over LAN Setup Guide

Chapter 1. Introduction
Serial over LAN (SOL) provides a means to manage servers remotely by using a
command-line interface (CLI) over a Telnet or Secure Shell (SSH) connection. SOL
is required to manage servers that do not have keyboard/video/mouse (KVM)
support, such as the JS20 Type 8842 blade server.
SOL provides console redirection for both BIOS and the blade server operating
system. The SOL feature redirects server serial-connection data over a LAN
without the need for special cabling. The SOL connection enables blade servers to
be managed from any remote location with network access. The advantages of SOL
include:
vRemote administration without keyboard, video, or mouse (headless servers)
vReduced cabling and no need for a serial concentrator
vStandard Telnet interface that eliminates the need for special client software
The IBM®BladeCenter®management module command-line interfaces provide
access to the text-console command prompt on each blade server through a SOL
connection, enabling the blade servers to be managed from a remote location. This
document explains how to update and configure BladeCenter components for SOL
operation using the BladeCenter management-module Web interface. You can also
perform many configuration procedures using the management-module
command-line interface or the simple network management protocol (SNMP). See
the BladeCenter Management Module Command-Line Interface Reference Guide for
information about the management-module command-line interface and
instructions about how to use it. All BladeCenter unit types, including the
BladeCenter T unit, are referred to throughout this document as the BladeCenter
unit. Unless stated otherwise, all descriptions and instructions in this document
apply to all BladeCenter unit configurations.
In the BladeCenter environment, the integrated system management processor
(ISMP) and network interface controller (NIC) on each blade server routes the
serial data from the blade server serial communications port to the network
infrastructure of the BladeCenter unit, including an Ethernet-compatible I/O
module that supports SOL communication. BladeCenter components are
configured for SOL operation through the BladeCenter management module. The
management module also acts as a proxy in the network infrastructure to couple a
client running a Telnet session with the management module to an SOL session
running on a blade server, enabling the Telnet client to interact with the serial port
of the blade server over the network. Because all SOL traffic is controlled by and
routed through the management module, administrators can segregate the
management traffic for the BladeCenter unit from the data traffic of the blade
servers.
To start an SOL connection with a blade server, you must first start a Telnet
command-line interface session with the management module. When this Telnet
command-line interface session is running, you can start a remote-console SOL
session with any blade server in the BladeCenter unit that is set up and enabled
for SOL operation. You can establish up to 20 separate Web interface, Telnet, serial
(advanced management module only), or SSH sessions with a BladeCenter
management module. For a BladeCenter unit, this enables you to have 14
simultaneous SOL sessions active (one for each of up to 14 blade servers) with 6
additional command-line interface sessions available for BladeCenter unit
© Copyright IBM Corp. 2009 1

management. For a BladeCenter T unit, this enables you to have 8 simultaneous
SOL sessions active (one for each of up to 8 blade servers) with 12 additional
command-line interface sessions available for BladeCenter unit management. If
security is a concern, you can use Secure Shell (SSH) sessions, or connections made
through the serial management port that is available on the advanced management
module, to establish secure Telnet command-line interface sessions with the
BladeCenter management module before starting an SOL console redirect session
with a blade server.
The most recent versions of all BladeCenter documentation is available at
http://www.ibm.com/support/.
Hardware and firmware requirements
The BladeCenter unit must be correctly configured before you can use the
command-line interface and SOL. This section describes the hardware and software
that are required for the command-line interface and SOL.
Hardware requirements
All BladeCenter components, except for the BladeCenter HS20 Type 8678 blade
server, are SOL capable. All blade servers must be configured to enable SOL
operation. Some of the older BladeCenter components require additional
configuration to support SOL operation.
To use the SOL feature, the following hardware is required:
vAn SOL-capable blade server.
The BladeCenter HS20 Type 8678 blade server does not support SOL operation.
You can use the console command to control a blade server through SOL only
on blade server types that support SOL functionality that have the required
firmware levels (see Table 1 on page 3).
vAn Ethernet I/O module installed in I/O-module bay 1. For systems using
management channel auto discovery (MCAD), SOL can use I/O modules
installed in other I/O-module bays (see the BladeCenter Advanced Management
Module User's Guide for additional information about MCAD).
The following blade servers have specific requirements for SOL operation:
vFor the BladeCenter HS20 Type 8832 and Type 8843 blade servers, and LS20
Type 8850 blade server:
– SOL uses the first network interface, Ethernet 1 (eth1 or Planar Ethernet 1), of
the blade server to communicate. When this network interface attempts to
boot through PXE or DHCP, the network interface is reset, causing the current
SOL session to be dropped and have a new status of Not Ready. If you
require booting through PXE or DHCP, use the second network interface,
Ethernet 2 (eth2 or Planar Ethernet 2), of the blade server and install an
Ethernet I/O module in I/O-module bay 1.
– For the BladeCenter HS20 Type 8832 blade server, jumper J28 must be
installed in the correct position. See “HS20 Type 8832 SOL jumper placement”
on page 28 for information.
vFor the BladeCenter JS20 Type 8842 blade server, SOL uses the first network
interface, Ethernet 1 (eth1 or Planar Ethernet 1), of the blade server to
communicate. When this network interface attempts to use BOOTP, the network
interface is reset, causing the current SOL session to be dropped and have a new
2BladeCenter: Serial over LAN Setup Guide

status of Not Ready. If you require BOOTP, use the second network interface,
Ethernet 2 (eth2 or Planar Ethernet 2), of the blade server and install an Ethernet
I/O module in I/O-module bay 1.
Firmware requirements
Make sure that you are using the latest versions of device drivers, firmware, and
BIOS for your blade server, management module, and other BladeCenter
components. Go to http://www.ibm.com/support/ for the latest information
about upgrading the device drivers, firmware, and BIOS for BladeCenter
components. The latest instructions are in the documentation that comes with the
updates.
The firmware level of most BladeCenter components supports SOL operation.
Some of the older BladeCenter components must have their firmware upgraded to
support SOL operation. The following table lists the firmware levels that are
required for older BladeCenter components to support SOL operation. If a
component is not listed in the table, all firmware levels for that component support
SOL operation.
Table 1. Firmware levels required for SOL for older BladeCenter components
Component Firmware level
BladeCenter Management Module 1.08 or later
BladeCenter HS20 Type 8678 blade server No SOL support
BladeCenter HS20 Type 8832 blade server
BladeCenter HS20 Type 8832 blade server BIOS 1.03 or later
BladeCenter HS20 Type 8832 blade server diagnostics 1.02 or later
BladeCenter HS20 Type 8832 blade server ISMP 1.03 or later
BladeCenter HS20 Type 8832 blade server Broadcom Ethernet Controller
Boot ROM
3.21 or later
BladeCenter HS20 Type 8832 blade server Broadcom Ethernet Controller
Firmware
2.2 or later
BladeCenter HS20 Type 8832 blade server Broadcom Ethernet Controller
Diagnostic Utility
1.06 or later
BladeCenter HS20 Type 8832 blade server Broadcom Ethernet Controller
Linux Device Driver
7.1.22 or later
IBM 4-Port Gb Ethernet Switch Module for BladeCenter 1.04 or later
Nortel Networks Layer 2-7 GbE Switch Module for IBM BladeCenter (4-port switch) See the IBM Support
Web site 1
Note 1: Go to http://www.ibm.com/support/ for the latest information about firmware levels that support SOL.
Chapter 1. Introduction 3

Checking firmware versions
Complete the following steps to view the firmware levels that are installed in the
BladeCenter components:
1. Start the BladeCenter management-module Web interface (see “Starting the
BladeCenter management-module Web interface” on page 5).
2. In the navigation pane, click Monitors →Firmware VPD.
The Firmware VPD choice identifies the firmware type, build ID, release date, and
revision number for the firmware that is installed in each blade server, I/O
module, and management module in the BladeCenter unit. The vital product data
(VPD) for the firmware in the management modules also includes the file name of
the firmware components. (Selecting the Firmware VPD choice takes up to 30
seconds to refresh and display information.)
Important: To avoid problems and to maintain proper system performance, always
make sure that the blade server firmware code, service processor code, and
diagnostic firmware code levels are consistent for all blade servers within the
BladeCenter unit.
Compare the installed firmware version to the information in Table 1 on page 3
and to the firmware information at http://www.ibm.com/support/. If the
firmware version installed is at or above the version listed in Table 1 on page 3,
your BladeCenter component has the firmware code needed to use the SOL
feature. If installed firmware versions do not meet at least the minimum
requirements, download the latest firmware code from http://www.ibm.com/
support/ and install it following the firmware update instructions in Chapter 4,
“Special component requirements,” on page 25.
4BladeCenter: Serial over LAN Setup Guide

Starting the BladeCenter management-module Web interface
Note: The sample screens that appear in this document might differ slightly from
the screens displayed by your system. Screen content varies based on the type of
BladeCenter unit that you are using and the firmware versions and options that
are installed.
The management-module Web interface is used to perform SOL configuration. The
management-module Web interface supports only configuration and monitoring of
the command-line interface and SOL and cannot be used to start command-line
interface or SOL sessions.
Complete the following steps to start the BladeCenter management-module Web
interface:
1. Open a Web browser. In the address or URL field, type the IP address or host
name that is assigned for the management-module remote connection.
The Enter Network Password window opens.
2. Type your user name and password. If you are logging in to the management
module for the first time, you can obtain your user name and password from
your system administrator. All login attempts are documented in the event log.
The initial user ID and password for the management module are:
vUser ID: USERID (all capital letters)
vPassword: PASSW0RD (note the zero, not O, in PASSW0RD)
3. Follow the instructions on the screen. Be sure to set the timeout value that you
want for your Web session.
The BladeCenter management-module Web interface window opens.
Chapter 1. Introduction 5

6BladeCenter: Serial over LAN Setup Guide

Chapter 2. General configuration
Note: The sample screens that appear in this document might differ slightly from
the screens displayed by your system. Screen content varies based on the type of
BladeCenter unit that you are using and the firmware versions and options that
are installed.
This section provides instructions for configuring the BladeCenter unit to operate
using SOL. You must perform the following procedures:
vMake sure that all BladeCenter components and firmware meet the minimum
SOL requirements (see “Hardware and firmware requirements” on page 2).
vConfigure the BladeCenter unit for SOL operation (see “Configuring the global
SOL settings for the BladeCenter unit”).
vConfigure the management module for SOL operation (see “Configuring the
management module” on page 9).
vIf required, configure BladeCenter components for SOL operation (see Chapter 4,
“Special component requirements,” on page 25).
vUpdate and configure BladeCenter BIOS for SOL operation (see “Updating and
configuring the blade server BIOS” on page 13).
vConfigure the operating system that is installed on each blade server to enable
SOL (see Chapter 3, “Operating system configuration,” on page 15).
vIf secure SOL sessions over a network are required, install and configure SSH for
SOL (see “Installing and configuring SSH for SOL” on page 11).
vEnable the blade servers for SOL operation (see “Enabling SOL for blade
servers” on page 12).
Perform the SOL configuration that is shared by all BladeCenter components using
the management-module Web interface. The management-module Web interface
supports only configuration and monitoring of the command-line interface and
SOL and cannot be used to start command-line interface or SOL sessions.
You can also perform some SOL configuration using the management-module
command-line interface or the Simple Network Management Protocol (SNMP). See
the BladeCenter Management Module Command-Line Interface Reference Guide for
information about the management-module command-line interface and
instructions for using it.
Configuring the global SOL settings for the BladeCenter unit
Complete the following steps to configure the global SOL settings for the
BladeCenter unit:
1. Start the BladeCenter management-module Web interface (see “Starting the
BladeCenter management-module Web interface” on page 5).
2. In the navigation pane, click Blade Tasks →Serial Over LAN.Inthe
management-module information page that opens make sure that the settings
match the following default values or are set to the values that are required by
your network configuration. Unless otherwise noted, the default
management-module SOL settings provide the best overall SOL performance.
(For advanced management modules, click the Serial Over LAN configuration
link to access the SOL settings.)
© Copyright IBM Corp. 2009 7

The following illustration shows SOL settings for management modules other than
an advanced management module.
The following illustration shows SOL settings for an advanced management
module.
Note: For the advanced management module, the SOL VLAN ID and the BSMP
IP address range are set on the Blade Tasks →Configuration page (see the
Advanced Management Module User's Guide for information).
The SOL settings and recommended values are:
vSerial Over Lan: Enabled
Use this field to enable or disable SOL globally for the BladeCenter unit. If SOL
is enabled globally and if SOL is enabled for a blade server, an SOL session can
be established with that blade server. If SOL is disabled globally, no SOL
sessions can be established with any blade servers in the BladeCenter unit.
vSOL VLAN ID (management modules other than the advanced management
module)
8BladeCenter: Serial over LAN Setup Guide

– For all switch modules other than the Cisco Systems Intelligent Gigabit
Ethernet Switch Module for the IBM BladeCenter, the SOL VLAN ID must be
set to 4095 (default value).
– For the Cisco Systems Intelligent Gigabit Ethernet Switch Module for the IBM
BladeCenter the SOL VLAN ID is set as follows:
- For Cisco IOS releases earlier than 12.1(22)EA6a, the SOL VLAN ID can be
set to any value between 3 and 1001: it cannot be set to the default value of
4095.
- For Cisco IOS release 12.1(22)EA6a and later, the SOL VLAN ID is set to a
default value of 4095. If desired, you can still set your own defined VLAN
ID.
Note: If your blade server has a Broadcom Ethernet controller and you
want to use an SOL VLAN ID of 4095 for the Cisco Systems Intelligent
Gigabit Ethernet Switch Module, upgrade to the latest versions of blade
server Broadcom Ethernet Controller firmware (minimum level supported
is 1.20.14).
If you set the SOL VLAN ID to a custom value, write it down for later use
during the configuration process.
vBSMP IP Address Range: x.x.x.x (management modules other than the
advanced management module)
This is a mandatory field where x.x.x.x is the base IP address for blade servers
that is used for internal communication inside the BladeCenter unit. The IP
address that SOL uses to communicate with the blade system management
processor (BSMP) of each blade server is based on the IP address that is set in
this field. For example, if the value that you enter is 10.1.1.1, the blade server in
blade bay 1 will have IP address 10.1.1.1, the blade server in blade bay 2 will
have IP address 10.1.1.2, and so on.
vAccumulate timeout: 25 (default value is 5 for management modules other than
the advanced management module and 150 for the advanced management
module)
vSend threshold: 250
vRetry count: 3
vRetry interval: 2500 (default value is 250)
Do not attempt to enable or disable SOL on any of the blade servers that are listed
in the Serial Over LAN Status section.
Configuring the management module
Before you configure the management module for SOL operation, review the
following information:
vMake sure that the management-module external network interface (eth0)
configuration is valid for your production network. This configuration can be
obtained from a DHCP server or set statically.
vFor management module types other than the advanced management module,
the management-module internal network interface (eth1) and the Ethernet I/O
module configuration can be different from that of the management-module
external network interface (eth0); however, the management-module internal
network interface (eth1) and the Ethernet I/O module configuration must be in
the same subnet. The management-module internal interface (eth1) is exposed to
the external network through the management module, so it must not conflict
Chapter 2. General configuration 9

with any other addresses on your production network. If you use a
configuration for the Ethernet I/O module that is not valid for your production
network, you will not be able to update the firmware or manage your Ethernet
I/O module through a Web interface.
vTelnet sessions with the BladeCenter management module do not have a timeout
value set by default. If no timeout value is set, Telnet sessions will remain active
indefinitely. See the BladeCenter Management Module Command-Line Interface
Reference Guide for information about configuring the Telnet session timeout
value for the management module.
vThe SOL blade system management processor (BSMP) address range can include
any valid IP addresses that do not conflict with any of the IP addresses of the
blade servers. The BSMP address range is used for internal communication
between the blade server and the I/O module and is not exposed to the external
network.
Complete the following steps to update the management-module firmware and
configure the management module to enable SOL:
1. Start the BladeCenter management-module Web interface (see “Starting the
BladeCenter management-module Web interface” on page 5).
2. Complete the following steps to update the BladeCenter management module
firmware:
a. Download the latest management-module firmware from
http://www.ibm.com/support/.
b. Update the management-module firmware, following the instructions that
come with the update file that you downloaded.
3. Start the BladeCenter management-module Web interface (see “Starting the
BladeCenter management-module Web interface” on page 5).
4. Complete the following steps to enable SOL for the management module:
a. For management module types other than the advanced management
module, complete the following steps to configure the internal network
interface (eth1) settings:
1) In the navigation pane, click MM Control →Network Interfaces.
2) Scroll to the Internal Ethernet Interface (eth1) section.
3) Make sure that Interface is set to Enabled.
4) Set the Static IP Configuration fields to the values that are required for
your physical network. The values must be in the following formats:
vIP address: x.x.x.x
vSubnet mask: x.x.x.x
vGateway address: x.x.x.x
The static IP configuration values specify valid IP addresses of the form
x.x.x.x, where each xis a number from 0 to 255.
5) Click Save; then, click OK or Yes to confirm. Do not restart the
management module.
b. Complete the following steps to configure the Ethernet I/O module
network settings:
Note: If you are using management channel auto discovery (MCAD),
replace references to I/O-module bay 1 in the following procedure with the
I/O module bay number that is actually being used (see the BladeCenter
Advanced Management Module User's Guide for additional information about
MCAD).
10 BladeCenter: Serial over LAN Setup Guide

1) In the navigation pane, click I/O Module Tasks →Configuration.
2) Scroll to the Bay 1 (Ethernet SM)* section.
3) Set the values in the New Static IP Configuration fields, if they are not
already correct as listed in the Current IP Configuration section. The
values must be in the following formats:
vIP address: x.x.x.x
vSubnet mask: x.x.x.x
vGateway address: x.x.x.x
The static IP configuration values specify valid IP addresses of the form
x.x.x.x, where each xis a number from 0 to 255.
4) If you changed any values, click Save.
5. Complete the following steps to restart the management module. Restarting the
management module ends the current BladeCenter management-module Web
interface session.
a. In the navigation pane, click MM Control →Restart MM.
b. Click Restart.
c. Click OK to confirm.
d. Click Yes to restart the management module and end the session.
Installing and configuring SSH for SOL
Complete the following steps to install and configure Secure Shell Server (SSH) for
SOL:
1. Start the BladeCenter management-module Web interface (see “Starting the
BladeCenter management-module Web interface” on page 5).
2. If you have not previously installed a security key file, complete the following
steps. Otherwise, go to step 3.
a. In the navigation pane, click MM Control →Security.
b. Download the latest version of the SSH security key file from
http://www.ibm.com/support/. Navigate to the Install SSL/SSH section
and click BladeCenter firmware update.
c. Click Browse and select the file that was downloaded in step 2b.
d. Click Install SSL/SSH.
e. Scroll to the Install SSL/SSH section and click Configure and enable.
3. Complete the following steps to generate the SSH Server Private Key:
a. In the navigation pane, click MM Control →Security.
b. Scroll to the SSH Server Key Management section and click Generate SSH
Server Private Key.
c. Click OK to confirm.
4. Complete the following steps to enable SSH:
a. Scroll to the Secure Shell (SSH) Server section.
b. Select Enabled for the SSH Server option; then, click Save.
c. Click OK to confirm.
5. Complete the following steps to restart the management module. Restarting the
management module ends the current BladeCenter management-module Web
interface session.
a. In the navigation pane, click MM Control →Restart MM.
b. Click Restart.
Chapter 2. General configuration 11

c. Click OK to confirm.
d. Click Yes to restart the management module and end the session.
You can now use an SSH client to start a secure Telnet session with the
management module and secure SOL sessions with the blade servers.
Enabling SOL for blade servers
SOL must be enabled both globally for the BladeCenter unit (see “Configuring the
global SOL settings for the BladeCenter unit” on page 7) and individually for each
blade server where you plan to start an SOL session.
Note: Make sure that console redirection is enabled for your blade server, with
port 2 (COM 2) specified as the remote console port. Remote console configuration
information for the HS20 Type 8832, HS20 Type 8843, and HS40 Type 8839 blade
servers is in Chapter 4, “Special component requirements,” on page 25. See the
Installation and User's Guide for your blade server for information about configuring
blade server BIOS settings such as console redirection.
Complete the following steps to enable SOL for a blade server:
1. Start the BladeCenter management-module Web interface (see “Starting the
BladeCenter management-module Web interface” on page 5).
2. Complete the following steps to enable SOL on the blade servers:
a. In the navigation pane, click Blade Tasks →Serial Over LAN; then, scroll to
the Serial Over LAN Status section.
b. Select each blade server that will have SOL enabled; then, click or select
Enable Serial Over LAN. (For advanced management modules, you will
also need to click Perform Action.) Selecting the check box at the top of the
status table selects all blade servers. The SOL column of the table will show
a status of Enabled for each of the blade servers that was selected. The SOL
Session column of the table indicates a status of Not Ready for each of the
blade servers that was selected.
c. To disable SOL for a blade server, select each blade server that will have
SOL disabled; then, click or select Disable Serial Over LAN. (For advanced
management modules, you will also need to click Perform Action.)
Selecting the check box at the top of the status table selects all blade servers.
The SOL column of the table will show a status of Disabled for each of the
blade servers that was selected.
Note: The blade server SOL status periodically updates itself automatically;
however, you can refresh the window for an immediate display of updated
status.
3. Complete the following steps to power-on or restart the blade servers on which
SOL was enabled:
a. In the navigation pane, click Blade Tasks →Power/Restart.
b. Select each blade server on which SOL was enabled; then, click either
Power On Blade or Restart Blade, depending on the current status of the
blade servers.
c. Click OK twice to confirm.
4. Complete the following steps to check the SOL status of the blade servers (see
“Monitoring SOL session status” on page 41 for more information):
12 BladeCenter: Serial over LAN Setup Guide

a. In the navigation pane, click Blade Tasks →Serial Over LAN; then, scroll to
the Serial Over LAN Status section.
b. Make sure that the SOL Session column of the table shows a status of
Ready. For the BladeCenter HS20 Type 8832 blade server, if the SOL Session
column does not show a status of Ready, make sure that the J28 jumper on
the blade server is in the correct position. See “HS20 Type 8832 SOL jumper
placement” on page 28 for information.
Updating and configuring the blade server BIOS
Note: If you update the blade server BIOS using UpdateXpress, the blade server
will maintain any BIOS settings that might have been set previously using the
Configuration/Setup Utility program; the blade server will not revert to the BIOS
default settings when you use UpdateXpress.
Complete the following steps to update and configure the blade server BIOS to
enable SOL. Some blade servers have special BIOS update and configuration
requirements that are in Chapter 4, “Special component requirements,” on page 25.
1. Complete the following steps to update the blade server BIOS:
a. Download the latest version of BIOS for your blade server type from
http://www.ibm.com/support/.
b. Update the blade server BIOS, following the instructions that come with the
update file that you downloaded.
2. Complete the following steps to configure the blade server BIOS settings:
a. Restart the blade server and press F1 when prompted to start the
Configuration/Setup Utility program.
b. Select Devices and I/O Ports; then, make sure that the values are set as
follows:
vSerial Port A: Auto-configure
vSerial Port B: Auto-configure
c. Select Remote Console Redirection; then, make sure that the values are set
as follows:
vRemote Console Active: Enabled
vRemote Console COM Port: COM 2
vRemote Console Baud Rate: 19200
vRemote Console Data Bits:8
vRemote Console Parity: None
vRemote Console Stop Bits:1
vRemote Console Text Emulation: ANSI
vRemote Console Keyboard Emulation: ANSI
vRemote Console Active After Boot: Enabled
vRemote Console Flow Control: Hardware
d. Press Esc twice to exit the Remote Console Redirection and Devices and
I/O Ports sections of the Configuration/Setup Utility program.
Note: For older blade servers, do not use Planar Ethernet 1 for PXE/DHCP
or BOOTP booting or installation. See “Hardware and firmware
requirements” on page 2 for information.
Chapter 2. General configuration 13

e. If your blade server does not support PXE/BOOTP booting or installation
and SOL on Planar Ethernet 1 at the same time, select Start Options; then,
set the following values:
vPlanar Ethernet PXE/DHCP to Planar Ethernet 2
vRun PXE only on selected Planar NIC to Enabled
f. Press Esc to exit the Start Options section of the Configuration/Setup Utility
program.
g. Select Save Settings; then, press Enter.
h. Press Enter to confirm.
i. Select Exit Setup; then, press Enter.
j. Make sure that Yes, exit the Setup Utility is selected; then, press Enter.
14 BladeCenter: Serial over LAN Setup Guide