Users Guide

• ESC[n~ — F12 passes, but F2 cannot pass.

• In Windows, if the Emergency Management System (EMS) console is opened immediately after a host reboot, the Special Admin

Console (SAC) terminal may get corrupted. Quit the SOL session, close the terminal, open another terminal, and start the SOL

session using the same command.

Related link

Disconnecting SOL session in iDRAC command line console

Using SOL from OpenSSH or Telnet on Linux

To start SOL from OpenSSH or Telnet on a Linux management station:

NOTE: If required, you can change the default SSH or Telnet session time-out at Overview > iDRAC Settings > Network >

Services.

1 Start a shell.

2 Connect to iDRAC using the following command:

• For SSH: ssh <iDRAC-ip-address> -l <login name>

• For Telnet: telnet <iDRAC-ip-address>

NOTE: If you have changed the port number for the Telnet service from the default (port 23), add the port number to

the end of the Telnet command.

3 Enter one of the following commands at the command prompt to start SOL:

• connect

• console com2

This connects iDRAC to the managed system’s SOL port. Once a SOL session is established, iDRAC command line console is not

available. Follow the escape sequence correctly to open the iDRAC command line console. The escape sequence is also printed on the

screen as soon as a SOL session is connected. When the managed system is o, it takes sometime to establish the SOL session.

NOTE

: You can use console com1 or console com2 to start SOL. Reboot the server to establish the connection.

The console -h com2 command displays the contents of the serial history buer before waiting for input from the keyboard or

new characters from the serial port.

The default (and maximum) size of the history buer is 8192 characters. You can set this number to a smaller value using the

command:

racadm set iDRAC.Serial.HistorySize <number>

4 Quit the SOL session to close an active SOL session.