IBM JS20 Hardware Maintenance Manual - Page 28

Using, command-line, interface, Configuring, Gigabit, Ethernet, controller

Page 28 highlights

Note: The BladeCenter unit supports up to four Ethernet switch modules. The SOL feature is accessed through the Management Module Command-Line Interface. For information about using the command-line interface, see "Using the command-line interface" and the IBM BladeCenter and BladeCenter T Eserver Management Module Command Line Interface Reference Guide on the IBM BladeCenter Documentation CD. Using the command-line interface The IBM BladeCenter Management Module Command-Line Interface Eserver provides direct access to BladeCenter management functions as an alternative to using the Web interface. Using the command-line interface, you can issue commands to control the power and configuration of the blade server and other components installed in the BladeCenter unit. The command-line interface also provides access to the text-console command prompt for the blade server through an SOL connection. See the IBM BladeCenter and BladeCenter T Eserver Management Module Command Line Interface Reference Guide on the IBM BladeCenter Documentation CD for information and instructions. Configuring the Gigabit Ethernet controller One dual-port Gigabit Ethernet controller is integrated on the blade server system board. Each controller port provides a 1000-Mbps full-duplex interface for connecting to one of the Ethernet-compatible switch modules in I/O bays 1 and 2, which enables simultaneous transmission and reception of data on the Ethernet local area network (LAN). Each Ethernet controller port on the system board is routed to a different switch module in I/O bay 1 or bay 2. The routing from the Ethernet controller port to the I/O bay will vary based on blade server type and the operating system that is installed. See "Blade server Ethernet controller enumeration" on page 19 for information about how to determine the routing from the Ethernet controller ports to I/O bays for the blade server. Note: Other types of blade servers, such as the BladeCenter HS20 Type 8678, that are installed in the same BladeCenter unit as this BladeCenter JS20 Type 8842 might have different requirements for Ethernet controller routing. See the documentation that comes with the other blade servers for detailed information. You do not need to set any jumpers or configure the controllers for the blade server operating system. However, you must install a device driver to enable the blade server operating system to address the Ethernet controller ports. For device drivers and information about configuring the Ethernet controller ports, see the Ethernet software documentation that comes with the blade server, or contact your reseller or IBM marketing representative. For updated information about configuring the controllers, go to the IBM Support Web site at http://www.ibm.com/support/. The Ethernet controller supports failover, which provides automatic redundancy for the Ethernet controller ports. Without failover you can have only one Ethernet controller port from each server attached to each virtual LAN or subnet. With failover you can configure more than one Ethernet controller port from each server to attach to the same virtual LAN or subnet. Either one of the integrated Ethernet controller ports can be configured as the primary Ethernet controller port. If you have configured the controller ports for failover and the primary link fails, the secondary controller port takes over. When the primary link is restored, the Ethernet 18 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide

  • 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

Note:
The
BladeCenter
unit
supports
up
to
four
Ethernet
switch
modules.
The
SOL
feature
is
accessed
through
the
Management
Module
Command-Line
Interface.
For
information
about
using
the
command-line
interface,
see
“Using
the
command-line
interface”
and
the
IBM
Eserver
BladeCenter
and
BladeCenter
T
Management
Module
Command
Line
Interface
Reference
Guide
on
the
IBM
BladeCenter
Documentation
CD.
Using
the
command-line
interface
The
IBM
Eserver
BladeCenter
Management
Module
Command-Line
Interface
provides
direct
access
to
BladeCenter
management
functions
as
an
alternative
to
using
the
Web
interface.
Using
the
command-line
interface,
you
can
issue
commands
to
control
the
power
and
configuration
of
the
blade
server
and
other
components
installed
in
the
BladeCenter
unit.
The
command-line
interface
also
provides
access
to
the
text-console
command
prompt
for
the
blade
server
through
an
SOL
connection.
See
the
IBM
Eserver
BladeCenter
and
BladeCenter
T
Management
Module
Command
Line
Interface
Reference
Guide
on
the
IBM
BladeCenter
Documentation
CD
for
information
and
instructions.
Configuring
the
Gigabit
Ethernet
controller
One
dual-port
Gigabit
Ethernet
controller
is
integrated
on
the
blade
server
system
board.
Each
controller
port
provides
a
1000-Mbps
full-duplex
interface
for
connecting
to
one
of
the
Ethernet-compatible
switch
modules
in
I/O
bays
1
and
2,
which
enables
simultaneous
transmission
and
reception
of
data
on
the
Ethernet
local
area
network
(LAN).
Each
Ethernet
controller
port
on
the
system
board
is
routed
to
a
different
switch
module
in
I/O
bay
1
or
bay
2.
The
routing
from
the
Ethernet
controller
port
to
the
I/O
bay
will
vary
based
on
blade
server
type
and
the
operating
system
that
is
installed.
See
“Blade
server
Ethernet
controller
enumeration”
on
page
19
for
information
about
how
to
determine
the
routing
from
the
Ethernet
controller
ports
to
I/O
bays
for
the
blade
server.
Note:
Other
types
of
blade
servers,
such
as
the
BladeCenter
HS20
Type
8678,
that
are
installed
in
the
same
BladeCenter
unit
as
this
BladeCenter
JS20
Type
8842
might
have
different
requirements
for
Ethernet
controller
routing.
See
the
documentation
that
comes
with
the
other
blade
servers
for
detailed
information.
You
do
not
need
to
set
any
jumpers
or
configure
the
controllers
for
the
blade
server
operating
system.
However,
you
must
install
a
device
driver
to
enable
the
blade
server
operating
system
to
address
the
Ethernet
controller
ports.
For
device
drivers
and
information
about
configuring
the
Ethernet
controller
ports,
see
the
Ethernet
software
documentation
that
comes
with
the
blade
server,
or
contact
your
reseller
or
IBM
marketing
representative.
For
updated
information
about
configuring
the
controllers,
go
to
the
IBM
Support
Web
site
at
The
Ethernet
controller
supports
failover,
which
provides
automatic
redundancy
for
the
Ethernet
controller
ports.
Without
failover
you
can
have
only
one
Ethernet
controller
port
from
each
server
attached
to
each
virtual
LAN
or
subnet.
With
failover
you
can
configure
more
than
one
Ethernet
controller
port
from
each
server
to
attach
to
the
same
virtual
LAN
or
subnet.
Either
one
of
the
integrated
Ethernet
controller
ports
can
be
configured
as
the
primary
Ethernet
controller
port.
If
you
have
configured
the
controller
ports
for
failover
and
the
primary
link
fails,
the
secondary
controller
port
takes
over.
When
the
primary
link
is
restored,
the
Ethernet
18
BladeCenter
JS20
Type
8842:
Hardware
Maintenance
Manual
and
Troubleshooting
Guide