IBM 8649 Hardware Maintenance Manual - Page 41

Ethernet, controller, messages

Page 41 highlights

Table 4. Ethernet troubleshooting chart (continued) Ethernet controller problem FRU/actions The Ethernet controller stopped working when another adapter was added to the server. Check the following: v Make sure that the cable is connected to the Ethernet controller. v Make sure that your PCI system BIOS code is current. v Reseat the adapter. v Determine if the interrupt (IRQ) setting assigned to the Ethernet adapter is also assigned to another device in the system. Use the Configuration/Setup Utility program to determine if this is the case. Although interrupt sharing is allowed for PCI devices, some devices do not function well when they share an interrupt with a dissimilar PCI device. Try changing the IRQ assigned to the Ethernet adapter or the other device. v Reseat or replace the adapter. The Ethernet controller Check the following: stopped working without v Try a different connector on the hub. apparent cause. v Reinstall the device drivers. See your operating-system documentation and the ServerGuide information. v Reseat or replace the adapter. Ethernet controller messages The integrated Ethernet controller might display messages from certain device drivers. The latest information available concerning these messages will be made available at the IBM Support Web site at http://www.ibm.com/support. Chapter 3. Diagnostics 31

  • 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

Table
4.
Ethernet
troubleshooting
chart
(continued)
Ethernet
controller
problem
FRU/actions
The
Ethernet
controller
stopped
working
when
another
adapter
was
added
to
the
server.
Check
the
following:
v
Make
sure
that
the
cable
is
connected
to
the
Ethernet
controller.
v
Make
sure
that
your
PCI
system
BIOS
code
is
current.
v
Reseat
the
adapter.
v
Determine
if
the
interrupt
(IRQ)
setting
assigned
to
the
Ethernet
adapter
is
also
assigned
to
another
device
in
the
system.
Use
the
Configuration/Setup
Utility
program
to
determine
if
this
is
the
case.
Although
interrupt
sharing
is
allowed
for
PCI
devices,
some
devices
do
not
function
well
when
they
share
an
interrupt
with
a
dissimilar
PCI
device.
Try
changing
the
IRQ
assigned
to
the
Ethernet
adapter
or
the
other
device.
v
Reseat
or
replace
the
adapter.
The
Ethernet
controller
stopped
working
without
apparent
cause.
Check
the
following:
v
Try
a
different
connector
on
the
hub.
v
Reinstall
the
device
drivers.
See
your
operating-system
documentation
and
the
ServerGuide
information.
v
Reseat
or
replace
the
adapter.
Ethernet
controller
messages
The
integrated
Ethernet
controller
might
display
messages
from
certain
device
drivers.
The
latest
information
available
concerning
these
messages
will
be
made
available
at
the
IBM
Support
Web
site
at
Chapter
3.
Diagnostics
31