Trouble Entering Sol Commands Or Receiving Double Prompts; Garbage Characters In An Sol Session - IBM HS40 - BladeCenter - 8839 Setup Manual

Serial over lan
Hide thumbs Also See for HS40 - BladeCenter - 8839:
Table of Contents

Advertisement

Trouble entering SOL commands or receiving double prompts

If you are having trouble entering commands in an SOL session or are receiving
double prompts, check the following items:
v Check the keyboard Return key settings for your terminal emulation program.
v The service processor on older blade servers, including the Type 8832 and Type
v Make sure that the operating system that is running on the blade server
v Make sure that the operating system that is running on the blade server is set up

Garbage characters in an SOL session

The default character encoding in Linux does not translate many of the characters
sent over an SOL session, which might corrupt the BIOS screens display. If you are
getting garbage characters while viewing or typing in an SOL session, check the
following items:
v Make sure the serial port settings in your terminal emulation program match the
v Try setting the remote console text and keyboard emulation to VT100/220,
v To correct garbage or missing characters when using Gnome Terminal on a
v Try a different terminal emulation program. Several programs are available, such
v Update the blade server service processor firmware (BMC or ISMP firmware).
48
BladeCenter: Serial over LAN Setup Guide
Make sure that only a line-feed character is sent whenever the Return key is
pressed (Telnet works this way by default). The Putty terminal application has a
configuration setting for the Return key under Configuration → Connection →
Telnet.
8842 blade servers, might block SOL output to a blade server that is running
Linux. If this happens, enter Ctrl+q in the SOL session to clear the keystroke
buffer.
supports SOL. See Chapter 3, "Operating system configuration," on page 15 for
instructions.
correctly for SOL console access (see Chapter 3, "Operating system
configuration," on page 15 for instructions). For example, you must enable the
Windows Emergency Management System (EMS) for Windows Server 2003 and
redirect it to the COM2 serial port.
settings specified in the blade server BIOS configuration. Also, make sure that
Hardware Flow Control is enabled.
instead of ANSI, in blade server BIOS. This might improve character display in
SOL sessions. These setting are found in the blade server BIOS, under Devices
and I/O Ports → Remote Console Redirection.
remote computer, complete the following steps:
1.
From the Gnome Terminal menu, select Terminal → Set Character Encoding
→ Add or Remove.
2. From the list of available encodings that displays, select Western IBM850;
then, click on the right-arrow button to add this encoding to the list of
encodings shown in the menu and click OK.
3. From the Gnome Terminal menu, select Terminal → Set Character Encoding →
Western (IBM850).
Using these settings for the Gnome Terminal should greatly reduce the amount
of garbage or missing characters.
as Telnet, Putty, or Hyperterm.
Latest firmware is available from http://www.ibm.com/systems/support/.

Advertisement

Table of Contents
loading

Table of Contents