IBM JS20 Hardware Maintenance Manual - Page 43

Running, Serial, session

Get IBM JS20 - BladeCenter - 8842 PDF manuals and user guides
UPC - 000435230263
View all IBM JS20 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 43 highlights

Chapter 6. Running a Serial Over LAN session The IBM BladeCenter management-module command-line interface Eserver provides a convenient method for entering commands that manage and monitor BladeCenter components. The blade server does not support a direct connection to a monitor, keyboard, or mouse. Therefore, to enable communication between the blade server and these devices, you must first configure the SOL feature on the blade server to establish an SOL connection and then start an SOL session as described in this chapter. Note: Detailed information about configuring the SOL feature is described in the BladeCenter JS20 Installation and User's Guide on the IBM BladeCenter Documentation CD. This chapter contains the following information about running an SOL session: v Starting the command-line interface v Establishing a Telnet connection v Establishing a Secure Shell (SSH) connection v Starting an SOL session v Ending an SOL session In the BladeCenter environment, the integrated system management processor (ISMP) and network interface controller (NIC) on each blade server route the serial data from the blade server serial communications port to the network infrastructure of the BladeCenter unit, including an Ethernet compatible I/O module that supports SOL communication. Configuration of BladeCenter components for SOL operation is done through the BladeCenter management module (see the BladeCenter JS20 Installation and User's Guide on the IBM BladeCenter Documentation CD). The management module also acts as a proxy in the network infrastructure to couple a client running a Telnet session with the management module to an SOL session running on a blade server, allowing the Telnet client to interact with the serial port of the blade server over the network. Because all SOL traffic is controlled by and routed through the management module, it is possible for administrators to segregate the management traffic for the BladeCenter unit from the data traffic of the blade servers. To start an SOL connection with a blade server, you must first start a Telnet command-line interface session with the management module. When this Telnet command-line interface session is running, you can start a remote console SOL session with any blade server installed in the BladeCenter unit that is set up and enabled for SOL operation. You can establish as many as 20 separate Telnet sessions with the BladeCenter management module, giving you the ability to have 14 simultaneous SOL sessions active (one for each of up to 14 blade servers) with six additional command-line interface sessions available for BladeCenter unit management. If security is a concern, secure shell (SSH) sessions can be used to establish secure Telnet command-line interface sessions with the BladeCenter management module before starting an SOL console redirect session with a blade server. The most recent versions of all BladeCenter documentation are available from the IBM Web site. Complete the following steps to check for updated BladeCenter documentation and technical updates: 1. Go to http://www.ibm.com/support/. © Copyright IBM Corp. 2003 33

  • 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
Chapter
6.
Running
a
Serial
Over
LAN
session
The
IBM
Eserver
BladeCenter
management-module
command-line
interface
provides
a
convenient
method
for
entering
commands
that
manage
and
monitor
BladeCenter
components.
The
blade
server
does
not
support
a
direct
connection
to
a
monitor,
keyboard,
or
mouse.
Therefore,
to
enable
communication
between
the
blade
server
and
these
devices,
you
must
first
configure
the
SOL
feature
on
the
blade
server
to
establish
an
SOL
connection
and
then
start
an
SOL
session
as
described
in
this
chapter.
Note:
Detailed
information
about
configuring
the
SOL
feature
is
described
in
the
BladeCenter
JS20
Installation
and
User’s
Guide
on
the
IBM
BladeCenter
Documentation
CD.
This
chapter
contains
the
following
information
about
running
an
SOL
session:
v
Starting
the
command-line
interface
v
Establishing
a
Telnet
connection
v
Establishing
a
Secure
Shell
(SSH)
connection
v
Starting
an
SOL
session
v
Ending
an
SOL
session
In
the
BladeCenter
environment,
the
integrated
system
management
processor
(ISMP)
and
network
interface
controller
(NIC)
on
each
blade
server
route
the
serial
data
from
the
blade
server
serial
communications
port
to
the
network
infrastructure
of
the
BladeCenter
unit,
including
an
Ethernet
compatible
I/O
module
that
supports
SOL
communication.
Configuration
of
BladeCenter
components
for
SOL
operation
is
done
through
the
BladeCenter
management
module
(see
the
BladeCenter
JS20
Installation
and
User’s
Guide
on
the
IBM
BladeCenter
Documentation
CD).
The
management
module
also
acts
as
a
proxy
in
the
network
infrastructure
to
couple
a
client
running
a
Telnet
session
with
the
management
module
to
an
SOL
session
running
on
a
blade
server,
allowing
the
Telnet
client
to
interact
with
the
serial
port
of
the
blade
server
over
the
network.
Because
all
SOL
traffic
is
controlled
by
and
routed
through
the
management
module,
it
is
possible
for
administrators
to
segregate
the
management
traffic
for
the
BladeCenter
unit
from
the
data
traffic
of
the
blade
servers.
To
start
an
SOL
connection
with
a
blade
server,
you
must
first
start
a
Telnet
command-line
interface
session
with
the
management
module.
When
this
Telnet
command-line
interface
session
is
running,
you
can
start
a
remote
console
SOL
session
with
any
blade
server
installed
in
the
BladeCenter
unit
that
is
set
up
and
enabled
for
SOL
operation.
You
can
establish
as
many
as
20
separate
Telnet
sessions
with
the
BladeCenter
management
module,
giving
you
the
ability
to
have
14
simultaneous
SOL
sessions
active
(one
for
each
of
up
to
14
blade
servers)
with
six
additional
command-line
interface
sessions
available
for
BladeCenter
unit
management.
If
security
is
a
concern,
secure
shell
(SSH)
sessions
can
be
used
to
establish
secure
Telnet
command-line
interface
sessions
with
the
BladeCenter
management
module
before
starting
an
SOL
console
redirect
session
with
a
blade
server.
The
most
recent
versions
of
all
BladeCenter
documentation
are
available
from
the
IBM
Web
site.
Complete
the
following
steps
to
check
for
updated
BladeCenter
documentation
and
technical
updates:
1.
Go
to
©
Copyright
IBM
Corp.
2003
33