IBM 87302RU Hardware Maintenance Manual - Page 104

Device, Suggested, action, Keyboard, problems

Get IBM 87302RU PDF manuals and user guides View all IBM 87302RU manuals
Add to My Manuals
Save this manual to your list of manuals

Page 104 highlights

Table 6. Troubleshooting charts (continued) Device Suggested action Ethernet disconnect notice will not appear when running Windows 2000. If an Ethernet cable is accidentally removed from the back of the BladeCenter T unit, the small red X (disconnect notice) that normally would appear to indicate that the cable was disconnected will not appear in the bottom right of the screen. The disconnect notice does not appear because the blade server Ethernet controller connects to the Ethernet switch module through integrated circuitry inside the BladeCenter T unit. When troubleshooting Ethernet-related problems, make sure that the Ethernet cables on the back of the BladeCenter T unit are connected properly. The default IP address set by the Ethernet switch module does not match the one assigned by the management module. When troubleshooting Ethernet-related problems, make sure that the Ethernet cables on the back of the BladeCenter T unit are connected properly. Updating the ethernet switch module configuration through the management module does not save the switch NVRAM. When you use the management-module Web interface to update the Ethernet switch module configuration, the management module firmware writes its settings for the switch module only to the management module NVRAM; it does not write its settings for the switch module to the switch-module NVRAM. If the switch module restarts when the management module is not able to apply the IP address it has in NVRAM for the switch module, the switch module will use whatever IP address it has in its own NVRAM. If the two IP addresses are not the same, you might not be able to manage the Ethernet switch module any more. The management module cannot apply the switch IP address from its NVRAM if: v The management module is restarting v The management module has failed v The management module has been removed from the unit. When you use the management-module Web interface to update the Ethernet switch module configuration, the management module firmware writes its settings for the switch module only to the management module NVRAM; it does not write its settings for the switch module to the switch module NVRAM. If the switch module restarts when the management module is not able to apply the IP address it has in NVRAM for the switch module, the switch module will use whatever IP address it has in its own NVRAM. If the two IP addresses are not the same, you might not be able to manage the Ethernet switch module any more. Keyboard problems The keyboard is very slow when using an operating system that does not have USB drivers. The keyboard is very slow when using an operating system that does not have USB drivers. The management module cannot apply the switch IP address from its NVRAM if: v The management module is restarting v The management module has failed v The management module has been removed from the unit. Although the keyboard attached to the BladeCenter T unit is a PS/2-style keyboard, communication with it is through a USB bus. When you are running an operating system that does not have USB drivers, such as in the following instances, the keyboard responds very slowly. 1. Run the blade server integrated diagnostics 2. Run a BIOS update diskette on a blade server 3. Update the diagnostics on a blade server 4. Run the Broadcom firmware CD for a blade server Sometimes when switching ownership of the KVM to a blade server, the video for the blade server appears almost immediately, but it takes up to 10 or 20 seconds for the mouse and keyboard to be usable. No action required. 94 BladeCenter T Type 8720 and 8730: 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
Table
6.
Troubleshooting
charts
(continued)
Device
Suggested
action
Ethernet
disconnect
notice
will
not
appear
when
running
Windows
2000.
If
an
Ethernet
cable
is
accidentally
removed
from
the
back
of
the
BladeCenter
T
unit,
the
small
red
X
(disconnect
notice)
that
normally
would
appear
to
indicate
that
the
cable
was
disconnected
will
not
appear
in
the
bottom
right
of
the
screen.
The
disconnect
notice
does
not
appear
because
the
blade
server
Ethernet
controller
connects
to
the
Ethernet
switch
module
through
integrated
circuitry
inside
the
BladeCenter
T
unit.
When
troubleshooting
Ethernet-related
problems,
make
sure
that
the
Ethernet
cables
on
the
back
of
the
BladeCenter
T
unit
are
connected
properly.
The
default
IP
address
set
by
the
Ethernet
switch
module
does
not
match
the
one
assigned
by
the
management
module.
When
troubleshooting
Ethernet-related
problems,
make
sure
that
the
Ethernet
cables
on
the
back
of
the
BladeCenter
T
unit
are
connected
properly.
Updating
the
ethernet
switch
module
configuration
through
the
management
module
does
not
save
the
switch
NVRAM.
When
you
use
the
management-module
Web
interface
to
update
the
Ethernet
switch
module
configuration,
the
management
module
firmware
writes
its
settings
for
the
switch
module
only
to
the
management
module
NVRAM;
it
does
not
write
its
settings
for
the
switch
module
to
the
switch-module
NVRAM.
If
the
switch
module
restarts
when
the
management
module
is
not
able
to
apply
the
IP
address
it
has
in
NVRAM
for
the
switch
module,
the
switch
module
will
use
whatever
IP
address
it
has
in
its
own
NVRAM.
If
the
two
IP
addresses
are
not
the
same,
you
might
not
be
able
to
manage
the
Ethernet
switch
module
any
more.
The
management
module
cannot
apply
the
switch
IP
address
from
its
NVRAM
if:
v
The
management
module
is
restarting
v
The
management
module
has
failed
v
The
management
module
has
been
removed
from
the
unit.
When
you
use
the
management-module
Web
interface
to
update
the
Ethernet
switch
module
configuration,
the
management
module
firmware
writes
its
settings
for
the
switch
module
only
to
the
management
module
NVRAM;
it
does
not
write
its
settings
for
the
switch
module
to
the
switch
module
NVRAM.
If
the
switch
module
restarts
when
the
management
module
is
not
able
to
apply
the
IP
address
it
has
in
NVRAM
for
the
switch
module,
the
switch
module
will
use
whatever
IP
address
it
has
in
its
own
NVRAM.
If
the
two
IP
addresses
are
not
the
same,
you
might
not
be
able
to
manage
the
Ethernet
switch
module
any
more.
The
management
module
cannot
apply
the
switch
IP
address
from
its
NVRAM
if:
v
The
management
module
is
restarting
v
The
management
module
has
failed
v
The
management
module
has
been
removed
from
the
unit.
Keyboard
problems
The
keyboard
is
very
slow
when
using
an
operating
system
that
does
not
have
USB
drivers.
Although
the
keyboard
attached
to
the
BladeCenter
T
unit
is
a
PS/2-style
keyboard,
communication
with
it
is
through
a
USB
bus.
When
you
are
running
an
operating
system
that
does
not
have
USB
drivers,
such
as
in
the
following
instances,
the
keyboard
responds
very
slowly.
1.
Run
the
blade
server
integrated
diagnostics
2.
Run
a
BIOS
update
diskette
on
a
blade
server
3.
Update
the
diagnostics
on
a
blade
server
4.
Run
the
Broadcom
firmware
CD
for
a
blade
server
The
keyboard
is
very
slow
when
using
an
operating
system
that
does
not
have
USB
drivers.
Sometimes
when
switching
ownership
of
the
KVM
to
a
blade
server,
the
video
for
the
blade
server
appears
almost
immediately,
but
it
takes
up
to
10
or
20
seconds
for
the
mouse
and
keyboard
to
be
usable.
No
action
required.
94
BladeCenter
T
Type
8720
and
8730:
Hardware
Maintenance
Manual
and
Troubleshooting
Guide