Troubleshooting
Problem
While connected to an HS40 through a Serial Over LAN (SOL) session, pressing the up-arrow key rapidly in the telnet window causes the connection to drop. The HS40 reports a "Not Ready" SOL status.
Resolving The Problem
|
Source
|
|---|
RETAIN tip: H181469
|
Symptom
|
|---|
While connected to an HS40 through a Serial Over LAN (SOL) session, pressing the up-arrow key rapidly in the telnet window causes the connection to drop. The HS40 reports a "Not Ready" SOL status.
|
Affected configurations
|
|---|
The system may be an IBM eServer BladeCenter HS40, type 8839, any model.
The BIOS level affected is:
- version 11
|
Solution
|
|---|
This problem is currently fixed by adjusting system flow control settings. No firmware updates are planned.
|
Workaround
|
|---|
Adjusting the flow control settings for the SOL session improves data handling across network.
|
Additional information
|
|---|
For Red Hat and SUSE ONLY, apply the following:
- The command line in /etc/inittab for agetty should have the option -h added. This turns on CTS/RTS flow-control at the application level.
For example:
7:2345:respawn:/sbin/agetty -h ttyS1 19200 vt102
- In the grub and/or lilo config.
The console Kernel parameter should also have CTS/RTS turned
on with the "r" option.
This will force CTS/RTS on the serial/console line.
For example:
kernel ...options...
console=ttyS1,19200n81r"
- Just to be safe, setserial should be used at startup to force the default baud rate on ttyS1 from 115200 down to 19200(ONLY SUPPORTED RATE).
In Red Hat the file is:
/etc/rc.d/rc.local
In SUSE the file is:
/etc/init.d/setserial
Examples:
Red Hat:
setserial /dev/ttyS1 baud_base 19200
SUSE (just before the "automatic configuration" section):
run_setserial /dev/ttyS1 baud_base 19200
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
29 January 2019
UID
ibm1MIGR-54837