Tripp Lite B098048 Owners Manual for B093- B097- and B098-Series Console Serve - Page 40

Alternately, SSH connections can be configured using the standard SSH port 22. The serial port being

Page 40 highlights

4. Serial Port, Host, Device and User Configuration You can also use standard communications packages like PuTTY to set a direct telnet (or SSH) connection to the serial ports. Note: PuTTY also supports telnet (and SSH). The procedure to set up a telnet session is simple. Enter the console server's IP address as the 'Host Name (or IP address)'. Select Telnet as the protocol and set the TCP port to 2000, plus the physical serial port number (i.e. 2001 to 2048). Click the Open button. You may receive a security alert stating the host's key is not cached. If this is the case, you will need to choose yes to continue. You will then be presented with the login prompt of the remote system connected to the serial port chosen on the console server. You can login as normal and use the host serial console screen. PuTTY can be downloaded at http://www.tucows.com/preview/195286.html Note: In Console Server mode, when you connect to a serial port, you connect via pmshell. To generate a BREAK on the serial port, type the character sequence ~b. If doing this over OpenSSH, type ~~b. SSH It is recommended you use SSH as the protocol where the User or Administrator connects to the console server (or connects through the console server to the attached serial consoles) over the Internet or any other public network. This will provide authenticated SSH communications between the SSH client program on the remote user's computer and the console server, so the user's communication with the serial device attached to the console server is secure. For SSH access to the consoles on devices attached to the console server serial ports, you can use SDT Connector. You configure SDT Connector with the console server as a gateway, then as a host, and you enable SSH service on Port (3000 + serial port #) i.e. 3001-3048. You can also use common communications packages like PuTTY or SSHTerm to SSH connect directly to port address IP Address _ Port (3000 + serial port #) i.e. 3001-3048. Alternately, SSH connections can be configured using the standard SSH port 22. The serial port being accessed is then identified by appending a descriptor to the username. This syntax supports: : : : : For example, in order for a User named "Fred" to access serial port 2, when setting up the SSHTerm or the PuTTY SSH client, instead of typing username = fred and ssh port = 3002, the alternate is to type username = fred:port02 (or username = fred:ttyS1) and ssh port = 22. 40

  • 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

40
You can also use standard communications packages like PuTTY to set a direct telnet (or SSH) connection to the serial ports.
Note:
PuTTY also supports telnet (and SSH). The procedure to set up a telnet session is simple. Enter the console server’s IP address as the
‘Host Name (or IP address)’. Select
Telnet
as the protocol and set the TCP port to
2000, plus the physical serial port number
(i.e. 2001
to 2048).
Click the
Open
button. You may receive a security alert stating the host’s key is not cached. If this is the case, you will need to choose
yes
to continue. You will then be presented with the login prompt of the remote system connected to the serial port chosen on the console
server. You can login as normal and use the host serial console screen.
Note:
In Console Server mode, when you connect to a serial port, you connect via pmshell. To generate a BREAK on the serial port, type the
character sequence ~b. If doing this over OpenSSH, type ~~b.
SSH
It is recommended you use SSH as the protocol where the User or Administrator connects to the console server (or
connects through the console server to the attached serial consoles) over the Internet or any other public network. This
will provide authenticated SSH communications between the SSH client program on the remote user’s computer and
the console server, so the user’s communication with the serial device attached to the console server is secure.
For SSH access to the consoles on devices attached to the console server serial ports, you can use SDT Connector.
You configure SDT Connector with the console server as a gateway, then as a host, and you enable SSH service on Port
(3000 + serial port #) i.e. 3001-3048.
You can also use common communications packages like PuTTY or SSHTerm to SSH connect directly to port address IP
Address _ Port (3000 + serial port #) i.e. 3001–3048.
Alternately, SSH connections can be configured using the standard SSH port 22. The serial port being accessed is then
identified by appending a descriptor to the username. This syntax supports:
<username>:<portXX>
<username>:<port label>
<username>:<ttySX>
<username>:<serial>
For example, in order for a User named “Fred” to access serial port 2, when setting up the SSHTerm or the PuTTY SSH
client, instead of typing
username = fred
and
ssh port = 3002
, the alternate is to type
username = fred:port02
(or
username = fred:ttyS1
) and
ssh port = 22
.
4. Serial Port, Host, Device and User Configuration