Dell PowerEdge R830 Integrated Remote Access Controller 8 Version 2.70.70.70 U - Page 114

Using SOL from PuTTY on Windows, Using SOL from OpenSSH or Telnet on Linux

Page 114 highlights

Related tasks Using SOL from PuTTY on Windows Using SOL from OpenSSH or Telnet on Linux Using SOL from PuTTY on Windows NOTE: If required, you can change the default SSH or Telnet time-out at Overview > iDRAC Settings > Network > Services. To start IPMI SOL from PuTTY on a Windows management station: 1. Run the following command to connect to iDRAC putty.exe [-ssh | -telnet] @ NOTE: The port number is optional. It is required only when the port number is reassigned. 2. Run the command console com2 or connect to start SOL and boot the managed system. A SOL session from the management station to the managed system using the SSH or Telnet protocol is opened. To access the iDRAC command-line console, follow the ESC key sequence. Putty and SOL connection behavior: • While accessing the managed system through putty during POST, if the Function keys and keypad option on putty is set to: • VT100+ - F2 passes, but F12 cannot pass. • 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 concepts 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 -l • For Telnet: telnet 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 off, 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 buffer before waiting for input from the keyboard or new characters from the serial port. The default (and maximum) size of the history buffer is 8192 characters. You can set this number to a smaller value using the command: racadm set iDRAC.Serial.HistorySize 4. Quit the SOL session to close an active SOL session. 114 Setting up iDRAC communication

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298

Related tasks
Using SOL from PuTTY on Windows
Using SOL from OpenSSH or Telnet on Linux
Using SOL from PuTTY on Windows
NOTE:
If required, you can change the default SSH or Telnet time-out at Overview > iDRAC Settings > Network >
Services.
To start IPMI SOL from PuTTY on a Windows management station:
1.
Run the following command to connect to iDRAC
putty.exe [-ssh | -telnet] <login name>@<iDRAC-ip-address> <port number>
NOTE:
The port number is optional. It is required only when the port number is reassigned.
2.
Run the command
console com2
or
connect
to start SOL and boot the managed system.
A SOL session from the management station to the managed system using the SSH or Telnet protocol is opened. To access the
iDRAC command-line console, follow the ESC key sequence. Putty and SOL connection behavior:
While accessing the managed system through putty during POST, if the Function keys and keypad option on putty is set to:
VT100+ — F2 passes, but F12 cannot pass.
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 concepts
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 off, 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 buffer before waiting for input from the keyboard or
new characters from the serial port.
The default (and maximum) size of the history buffer 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.
114
Setting up iDRAC communication