Troubleshooting Storage Module Problems - IBM BladeCenter S Problem Determination And Service Manual

2. The service processor on older blade servers might block SOL output to a blade
3. Verify that the operating system running on the blade server supports Serial
4. Make sure that the operating system running on the blade server has been set
Characters received or typed are incorrect
Use this procedure when you are having trouble typing or receiving correct
characters in a Serial over LAN session.
Problem
Within a Serial over LAN session, the characters that you type appear differently
on the terminal.
Investigation
Perform these steps to resolve the problem:
1. Verify that the serial port settings in your terminal emulation program match
2. Try a different terminal emulation program, such as Telnet, PuTTY, or
3. Make sure the Ethernet switch in I/O module bay 1 is powered on.
4. Check the external link statistics for the Ethernet switch in I/O module bay 1.
5. Attempt to set up a Serial over LAN session to another blade server in the
6. Restart the blade server. From the advanced management module Web
7. Update the Baseboard Management Controller (BMC) and the Ethernet driver
8. If the blade server supports local KVM, attempt to access the blade server

Troubleshooting storage module problems

Use this information to solve problems with the storage module and hard disk
drives.
70
BladeCenter S Type 7779/8886: Problem Determination and Service Guide
v This is the default for Telnet sessions.
v The terminal application PuTTY has a configuration setting for the Return
key. From the Configuration menu, click Connection →Telnet.
server running Linux. If this occurs, type Ctrl-q in the Serial over LAN session
to clear the keystroke buffer.
over LAN. For more information see the IBM BladeCenter Serial over LAN Setup
Guide.
up correctly for Serial over LAN console access. For more information see the
IBM BladeCenter Serial over LAN Setup Guide.
the settings in the blade server BIOS configuration. In addition, verify that
hardware flow control is enabled.
Hyperterm.
Look for high packet loss and/or high packet error rates.
BladeCenter S chassis. If the problem persists for multiple blade servers,
suspect the advanced management module.
interface, click Blade Tasks > Power/Restart. Click the box next to the blade
server, and then scroll down and select Restart Blade System Mgmt Processor.
a. Make sure the blade server is powered up.
b. Check the status of Serial over LAN.
c. If it is ready, attempt to open an Serial over LAN console.
for the blade server.
using the KVM connection on the advanced management module and type
some characters. If the problem persists, suspect the advanced management
module.