IBM BladeCenter T Type 8720 User Manual
Page 103
Table
6.
Troubleshooting
charts
(continued)
Device
Suggested
action
CD-ROM
drive
is
not
recognized
after
being
switched
back
to
blade
server
running
on
Windows
2000
Advanced
Server
with
SP3
applied.
When
the
CD-ROM
drive
is
owned
by
blade
server
x,
is
switched
to
another
blade
server,
then
is
switched
back
to
blade
server
x,
the
operating
system
in
blade
server
x
no
longer
recognizes
the
CD-ROM
drive.
This
happens
when
you
have
not
safely
stopped
the
drives
before
switching
ownership
of
the
CD-ROM
drive
and
USB
ports
(media
tray).
Note:
Because
the
BladeCenter
T
unit
uses
a
USB
bus
to
communicate
with
the
media
tray
devices,
switching
ownership
of
the
media
tray
to
another
blade
server
is
the
same
as
unplugging
a
USB
device.
Before
switching
ownership
of
the
CD-ROM
drive
(media
tray)
to
another
blade
server,
safely
stop
the
media
tray
devices
on
the
blade
server
that
currently
owns
the
media
tray,
as
follows:
1.
Double-click
the
Unplug
or
Eject
Hardware
icon
in
the
Windows
taskbar
at
the
bottom
right
of
the
screen.
2.
Select
USB
Mass
Storage
Device
and
click
Stop.
3.
Click
Close.
You
can
now
safely
switch
ownership
of
the
media
tray
to
another
blade
server.
CD-ROM
problem.
Replace
the
CD-ROM
drive.
Ethernet
controller
problems
Operating
systems
number
Ethernet
controllers
differently.
Enumeration
of
the
Ethernet
controllers
in
a
blade
server
is
operating-system
dependent.
In
the
blade
server
Configuration/Setup
Utility
program,
the
Ethernet
port
designated
as
Planar
Ethernet
1
is
routed
to
Ethernet
switch
module
2
and
the
Ethernet
port
designated
as
Planar
Ethernet
2
is
routed
to
Ethernet
switch
module
1.
Verify
the
designations
through
your
operating
system
settings
or
by
testing:
1.
Install
only
one
switch
module,
in
switch
bay
1.
2.
Enable
only
one
of
the
Ethernet
controllers
on
the
blade
server.
Make
note
of
the
designation
the
blade
server
operating
system
has
for
the
controller.
3.
Ping
an
external
computer
on
the
network
connected
to
the
switch
module.
If
you
can
ping
the
external
computer,
the
Ethernet
controller
you
enabled
is
the
upper
controller
in
the
blade
server
and
is
associated
with
Ethernet
switch
1.
Ethernet
switch
module
problems
First
ping
from
Ethernet
switch
module
through
Telnet
reports
failure.
When
you
use
the
Ethernet
switch
module
Telnet
interface
to
request
the
switch
module
to
ping
something,
the
first
ping
response
reports
a
failure,
although
the
other
repetitions
might
report
success.
This
occurs
regardless
of
whether
the
switch
module
port
the
pinged
object
is
connected
to
is
internal
or
external,
and
applies
to
pinging
blade
servers
but
not
to
pinging
the
management
module
or
objects
connected
to
its
external
Ethernet
port,
such
as
the
network
management
station.
To
get
accurate
results,
always
specify
multiple
repetitions
(>1)
in
the
ping
request,
and
ignore
the
first
ping
response
from
that
request.
See
the
IBM
4-Port
Gb
Ethernet
Switch
Module
for
BladeCenter
T
Installation
Guide
for
instructions
on
how
to
ping
through
the
Telnet
interface.
Ethernet
switch-module
firmware
graphics
shows
a
blank
panel
when
the
blade
server
is
present
but
powered
off.
If
the
Wake-on-LAN
(WOL)
feature
is
disabled
on
a
blade
server,
and
the
blade
server
is
turned
off,
the
switch
module
internal
port
link
to
that
blade
is
down.
This
is
not
an
error,
but
the
graphic
of
the
BladeCenter
T
unit
might
show
a
blank
panel
instead
of
a
blade
server
in
that
bay.
Note:
You
can
enable
or
disable
the
WOL
feature
on
a
blade
server
through
the
management-module
Web
interface
or
through
the
IBM
Director
console.
Do
not
rely
on
the
BladeCenter
T
graphic
in
the
Ethernet
switch-module
firmware
Web
interface
to
determine
the
presence
or
absence
of
blade
servers
in
the
BladeCenter
T
unit.
Ethernet
switch-module
log
reports
elapsed
time,
not
time
of
day.
The
timestamp
on
entries
in
the
Ethernet
switch
module
log
uses
elapsed
time
(since
last
switch
restart).
The
timestamp
on
entries
restarts
from
0
each
time
the
switch
is
restarted,
although
the
entries
do
remain
in
order
of
occurrence.
Chapter
6.
Symptom-to-FRU
index
93