If you can open an SOL session with a blade server but it will not
remain open, check the following items:
- Make sure that the session timeout has not expired. The management module
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.
- (For HS20 Type 8832, JS20 Type 8842, HS20 Type 8843, and LS20 Type 8850
blade 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.
- Make sure that the latest Broadcom Ethernet driver is installed on the
blade server, especially for blade servers running a Linux operating system.
- Do not type on the keyboard while the blade server is rebooting or the
operating system network drivers are loading; this action has been known to
cause an SOL session to drop.