IBM HS40 Setup Guide - Page 54

Trouble entering SOL commands or receiving double prompts, Garbage characters in an SOL session

Get IBM HS40 - BladeCenter - 8839 PDF manuals and user guides
UPC - 000435160188
View all IBM HS40 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 54 highlights

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. 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. v The service processor on older blade servers, including the Type 8832 and Type 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. v Make sure that the operating system that is running on the blade server supports SOL. See Chapter 3, "Operating system configuration," on page 15 for instructions. v Make sure that the operating system that is running on the blade server is set up 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. 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 settings specified in the blade server BIOS configuration. Also, make sure that Hardware Flow Control is enabled. v Try setting the remote console text and keyboard emulation to VT100/220, 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. v To correct garbage or missing characters when using Gnome Terminal on a 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. v Try a different terminal emulation program. Several programs are available, such as Telnet, Putty, or Hyperterm. v Update the blade server service processor firmware (BMC or ISMP firmware). Latest firmware is available from http://www.ibm.com/systems/support/. 48 BladeCenter: Serial over LAN Setup Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
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.
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
.
v
The service processor on older blade servers, including the Type 8832 and Type
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.
v
Make sure that the operating system that is running on the blade server
supports SOL. See Chapter 3, “Operating system configuration,” on page 15 for
instructions.
v
Make sure that the operating system that is running on the blade server is set up
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.
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
settings specified in the blade server BIOS configuration. Also, make sure that
Hardware Flow Control is enabled.
v
Try setting the remote console text and keyboard emulation to VT100/220,
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
.
v
To correct garbage or missing characters when using Gnome Terminal on a
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.
v
Try a different terminal emulation program. Several programs are available, such
as Telnet, Putty, or Hyperterm.
v
Update the blade server service processor firmware (BMC or ISMP firmware).
Latest firmware is available from http://www.ibm.com/systems/support/.
48
BladeCenter: Serial over LAN Setup Guide