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

SOL using IPMI protocol, SOL using SSH or Telnet protocol

Page 113 highlights

SOL using IPMI protocol The IPMI-based SOL utility and IPMItool uses RMCP+ delivered using UDP datagrams to port 623. The RMCP+ provides improved authentication, data integrity checks, encryption, and the ability to carry multiple types of payloads while using IPMI 2.0. For more information, see http://ipmitool.sourceforge.net/manpage.html. The RMCP+ uses an 40-character hexadecimal string (characters 0-9, a-f, and A-F) encryption key for authentication. The default value is a string of 40 zeros. An RMCP+ connection to iDRAC must be encrypted using the encryption Key (Key Generator (KG)Key). You can configure the encryption key using the iDRAC Web interface or iDRAC Settings utility. To start SOL session using IPMItool from a management station: NOTE: If required, you can change the default SOL time-out at Overview > iDRAC Settings > Network > Services. 1. Install IPMITool from the Dell Systems Management Tools and Documentation DVD. For installation instructions, see the Software Quick Installation Guide. 2. At the command prompt (Windows or Linux), run the following command to start SOL from iDRAC: ipmitool -H -I lanplus -U -P sol activate This command connected the management station to the managed system's serial port. 3. To quit a SOL session from IPMItool, press ~ and then . (period). NOTE: If a SOL session does not terminate, reset iDRAC and allow up to two minutes to complete booting. SOL using SSH or Telnet protocol Secure Shell (SSH) and Telnet are network protocols that are used to perform command-line communications to iDRAC. You can parse remote RACADM and SMCLP commands through either of these interfaces. To provide enhanced security, the 'keyboard interactive authentication' option has been enabled on the iDRAC SSH Server. With this option, most SSH Clients make the user aware of this with various prompts in anticipation of potential requests from the SSH Server. These prompts are opportunistic i.e. the SSH clients do not know if any further authentication dialog will be requested by the server. As such when such prompts are seen their context and applicability needs to understood and ignored if the necessary. This behavior is a characteristic of most SSH Clients that support the 'key-board interactive authentication' option in addition to the normal 'password authentication' and 'public-key authentication'. Also, the wording of the 'dialog prompts' will vary among the various SSH Client implementations. SSH has improved security over Telnet. iDRAC only supports SSH version 2 with password authentication, and is enabled by default. iDRAC supports up to two SSH sessions and two Telnet sessions at a time. It is recommended to use SSH as Telnet is not a secure protocol. You must use Telnet only if you cannot install an SSH client or if your network infrastructure is secure. NOTE: While establishing SSH connection, a security message is displayed 'Further Authentication required', as iDRAC now supports 'Keyboard interactive authentication' for enhanced security. Use open-source programs such as PuTTY or OpenSSH that support SSH and Telnet network protocols on a management station to connect to iDRAC. NOTE: Run OpenSSH from a VT100 or ANSI terminal emulator on Windows. Running OpenSSH at the Windows command prompt does not result in full functionality (that is, some keys do not respond and no graphics are displayed). Before using SSH or Telnet to communicate with iDRAC, make sure to: 1. Configure BIOS to enable Serial Console. 2. Configure SOL in iDRAC. 3. Enable SSH or Telnet using iDRAC Web interface or RACADM. Telnet (port 23)/ SSH (port 22) client WAN connection iDRAC The IPMI-based SOL that uses SSH or Telnet protocol eliminates the need for an additional utility because the serial to network translation happens within iDRAC. The SSH or Telnet console that you use must be able to interpret and respond to the data arriving from the serial port of the managed system. The serial port usually attaches to a shell that emulates an ANSI- or VT100/VT220- terminal. The serial console is automatically redirected to the SSH or Telnet console. Setting up iDRAC communication 113

  • 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

SOL using IPMI protocol
The IPMI-based SOL utility and IPMItool uses RMCP+ delivered using UDP datagrams to port 623. The RMCP+ provides improved
authentication, data integrity checks, encryption, and the ability to carry multiple types of payloads while using IPMI 2.0. For more
information, see
.
The RMCP+ uses an 40-character hexadecimal string (characters 0-9, a-f, and A-F) encryption key for authentication. The default value
is a string of 40 zeros.
An RMCP+ connection to iDRAC must be encrypted using the encryption Key (Key Generator (KG)Key). You can configure the
encryption key using the iDRAC Web interface or iDRAC Settings utility.
To start SOL session using IPMItool from a management station:
NOTE:
If required, you can change the default SOL time-out at Overview > iDRAC Settings > Network > Services.
1.
Install IPMITool from the
Dell Systems Management Tools and Documentation
DVD.
For installation instructions, see the
Software Quick Installation Guide
.
2.
At the command prompt (Windows or Linux), run the following command to start SOL from iDRAC:
ipmitool -H <iDRAC-ip-address> -I lanplus -U <login name> -P <login password> sol activate
This command connected the management station to the managed system's serial port.
3.
To quit a SOL session from IPMItool, press ~ and then . (period).
NOTE:
If a SOL session does not terminate, reset iDRAC and allow up to two minutes to complete booting.
SOL using SSH or Telnet protocol
Secure Shell (SSH) and Telnet are network protocols that are used to perform command-line communications to iDRAC. You can parse
remote RACADM and SMCLP commands through either of these interfaces.
To provide enhanced security, the 'keyboard interactive authentication' option has been enabled on the iDRAC SSH Server. With this
option, most SSH Clients make the user aware of this with various prompts in anticipation of potential requests from the SSH Server.
These prompts are opportunistic i.e. the SSH clients do not know if any further authentication dialog will be requested by the server. As
such when such prompts are seen their context and applicability needs to understood and ignored if the necessary. This behavior is a
characteristic of most SSH Clients that support the 'key-board interactive authentication' option in addition to the normal 'password
authentication' and 'public-key authentication'. Also, the wording of the 'dialog prompts' will vary among the various SSH Client
implementations.
SSH has improved security over Telnet. iDRAC only supports SSH version 2 with password authentication, and is enabled by default.
iDRAC supports up to two SSH sessions and two Telnet sessions at a time. It is recommended to use SSH as Telnet is not a secure
protocol. You must use Telnet only if you cannot install an SSH client or if your network infrastructure is secure.
NOTE:
While establishing SSH connection, a security message is displayed 'Further Authentication required', as iDRAC
now supports 'Keyboard interactive authentication' for enhanced security.
Use open-source programs such as PuTTY or OpenSSH that support SSH and Telnet network protocols on a management station to
connect to iDRAC.
NOTE:
Run
OpenSSH
from a VT100 or ANSI terminal emulator on Windows. Running
OpenSSH
at the Windows command
prompt does not result in full functionality (that is, some keys do not respond and no graphics are displayed).
Before using SSH or Telnet to communicate with iDRAC, make sure to:
1.
Configure BIOS to enable Serial Console.
2.
Configure SOL in iDRAC.
3.
Enable SSH or Telnet using iDRAC Web interface or RACADM.
Telnet (port 23)/ SSH (port 22) client <−−> WAN connection <−−> iDRAC
The IPMI-based SOL that uses SSH or Telnet protocol eliminates the need for an additional utility because the serial to network
translation happens within iDRAC. The SSH or Telnet console that you use must be able to interpret and respond to the data arriving
from the serial port of the managed system. The serial port usually attaches to a shell that emulates an ANSI- or VT100/VT220–
terminal. The serial console is automatically redirected to the SSH or Telnet console.
Setting up iDRAC communication
113