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

Using Telnet virtual console, Configuring backspace key for your Telnet session, Disconnecting SOL

Page 115 highlights

Related tasks Using Telnet virtual console Configuring backspace key for your Telnet session Disconnecting SOL session in iDRAC command line console Using Telnet virtual console Some Telnet clients on the Microsoft operating systems may not display the BIOS setup screen correctly when BIOS Virtual Console is set for VT100/VT220 emulation. If this issue occurs, change the BIOS console to ANSI mode to update the display. To perform this procedure in the BIOS setup menu, select Virtual Console > Remote Terminal Type > ANSI. When you configure the client VT100 emulation window, set the window or application that is displaying the redirected Virtual Console to 25 rows x 80 columns to make sure correct text display. Else, some text screens may be garbled. To use Telnet virtual console: 1. Enable Telnet in Windows Component Services. 2. Connect to the iDRAC using the command telnet : Parameter Description IP address for the iDRAC Telnet port number (if you are using a new port) Configuring backspace key for your Telnet session Depending on the Telnet client, using the Backspace key may produce unexpected results. For example, the session may echo ^h. However, most Microsoft and Linux Telnet clients can be configured to use the Backspace key. To configure a Linux Telnet session to use the key, open a command prompt and type stty erase ^h. At the prompt, type telnet. To configure Microsoft Telnet clients to use the Backspace key: 1. Open a command prompt window (if required). 2. If you are not running a Telnet session, type telnet. If you are running a Telnet session, press Ctrl+]. 3. At the prompt, type set bsasdel. The message Backspace will be sent as delete is displayed. Disconnecting SOL session in iDRAC command line console The commands to disconnect a SOL session are based on the utility. You can exit the utility only when a SOL session is completely terminated. To disconnect a SOL session, terminate the SOL session from the iDRAC command line console. • To quit SOL redirection, press Enter, Esc, T. The SOL session closes. • To quit a SOL session from Telnet on Linux, press and hold Ctrl+]. A Telnet prompt is displayed. Type quit to exit Telnet. If a SOL session is not terminated completely in the utility, other SOL sessions may not be available. To resolve this, terminate the command line console in the Web interface under Overview > iDRAC Settings > Sessions. Communicating with iDRAC using IPMI over LAN You must configure IPMI over LAN for iDRAC to enable or disable IPMI commands over LAN channels to any external systems. If IPMI over LAN is not configured, then external systems cannot communicate with the iDRAC server using IPMI commands. NOTE: From iDRAC v2.30.30.30 or later, IPMI also supports IPv6 address protocol for Linux-based operating systems. Setting up iDRAC communication 115

  • 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 Telnet virtual console
Configuring backspace key for your Telnet session
Disconnecting SOL session in iDRAC command line console
Using Telnet virtual console
Some Telnet clients on the Microsoft operating systems may not display the BIOS setup screen correctly when BIOS Virtual Console is set
for VT100/VT220 emulation. If this issue occurs, change the BIOS console to ANSI mode to update the display. To perform this procedure
in the BIOS setup menu, select
Virtual Console
>
Remote Terminal Type
>
ANSI
.
When you configure the client VT100 emulation window, set the window or application that is displaying the redirected Virtual Console to
25 rows x 80 columns to make sure correct text display. Else, some text screens may be garbled.
To use Telnet virtual console:
1.
Enable
Telnet
in
Windows Component Services.
2.
Connect to the iDRAC using the command
telnet <IP address>:<port number>
Parameter
Description
<IP address>
IP address for the iDRAC
<port number>
Telnet port number (if you are using a new port)
Configuring backspace key for your Telnet session
Depending on the Telnet client, using the Backspace key may produce unexpected results. For example, the session may echo
^h
.
However, most Microsoft and Linux Telnet clients can be configured to use the Backspace key.
To configure a Linux Telnet session to use the <Backspace> key, open a command prompt and type
stty erase ^h
. At the prompt,
type
telnet
.
To configure Microsoft Telnet clients to use the Backspace key:
1.
Open a command prompt window (if required).
2.
If you are not running a Telnet session, type
telnet
. If you are running a Telnet session, press Ctrl+].
3.
At the prompt, type
set bsasdel
.
The message
Backspace will be sent as delete
is displayed.
Disconnecting SOL session in iDRAC command line console
The commands to disconnect a SOL session are based on the utility. You can exit the utility only when a SOL session is completely
terminated.
To disconnect a SOL session, terminate the SOL session from the iDRAC command line console.
To quit SOL redirection, press Enter, Esc, T.
The SOL session closes.
To quit a SOL session from Telnet on Linux, press and hold Ctrl+].
A Telnet prompt is displayed. Type
quit
to exit Telnet.
If a SOL session is not terminated completely in the utility, other SOL sessions may not be available. To resolve this, terminate the
command line console in the Web interface under
Overview
>
iDRAC Settings
>
Sessions
.
Communicating with iDRAC using IPMI over LAN
You must configure IPMI over LAN for iDRAC to enable or disable IPMI commands over LAN channels to any external systems. If IPMI
over LAN is not configured, then external systems cannot communicate with the iDRAC server using IPMI commands.
NOTE:
From iDRAC v2.30.30.30 or later, IPMI also supports IPv6 address protocol for Linux-based operating systems.
Setting up iDRAC communication
115