Sol Session Opens And Drops - IBM HS40 - BladeCenter - 8839 Setup Manual

v Restart the blade server system management processor (see the Management
v Disable SOL for the blade server; then, re-enable it (see the Management Module
v Restart the management module (see the Management Module User's Guide or the
v Restart the switch module in I/O-module bay 1 (see the Management Module
v Turn off the blade server, remove it from the BladeCenter unit, reinstall it, and

SOL session opens and drops

If you can open an SOL session with a blade server but it will not remain open,
check the following items:
v Make sure that the session timeout has not expired. The management module
v (For HS20 Type 8832, JS20 Type 8842, HS20 Type 8843, and LS20 Type 8850 blade
v Make sure that the latest Broadcom Ethernet driver is installed on the blade
v Do not type on the keyboard while the blade server is rebooting or the operating
between 1 and 1001 and the Cisco switch needs to be configured for these
setting (see "Configuring the Cisco Systems Intelligent Gigabit Ethernet Switch
Module for the IBM BladeCenter" on page 34). If the BladeCenter I/O module
internal ports are VLAN enabled ('trunked' in Cisco terms), then these ports
must be configured to pass traffic from the SOL VLAN ID.
Module User's Guide or the Management Module Command-line Interface Reference
Guide for instructions). Make sure that the blade server is turned on when
restarting the management processor. After the restart is complete, check the
blade server SOL status; if the status indicates Ready, then try to start an SOL
session.
User's Guide or the Management Module Command-line Interface Reference Guide for
instructions). Make sure that the blade server is turned on when disabling and
re-enabling SOL. After the disable and re-enable is complete, check the blade
server SOL status; if the status indicates Ready, then try to start an SOL session.
Management Module Command-line Interface Reference Guide for instructions). After
the restart is complete, check the blade server SOL status; if the status indicates
Ready, then try to start an SOL session.
User's Guide or the Management Module Command-line Interface Reference Guide for
instructions). After the restart is complete, check the blade server SOL status; if
the status indicates Ready, then try to start an SOL session.
turn it back on. After doing this, check the blade server SOL status; if the status
indicates Ready, then try to start an SOL session.
has a default timeout value of 120 seconds for command-line interface sessions.
This value can be changed to never timeout using the command: telnetcfg –T
system:mm[x] –t 0 (where x is the primary management-module bay number).
See the Management Module Command-line Interface Reference Guide for
instructions.
servers only) SOL traffic shares blade server NIC port 1 with regular Ethernet
traffic. Do not try to use SOL on a blade server while attempting to PXE boot it
through NIC port 1. Traffic from a network install server running through blade
server port 1 can block SOL traffic, which will cause the SOL session to hang.
server, especially for blade servers running a Linux operating system.
system network drivers are loading; this action has been known to cause an SOL
session to drop.
Chapter 6. Troubleshooting SOL
47