IBM QS21 Service Guide - Page 95

Network, errors

Page 95 highlights

Table 12. System firmware boot errors (continued) Code Message Description E5040 (USB) Device transaction error. Note: indicates the command in progress when the transaction error occurred. This information may not always be available. The drive showed an error during data transfer. Action 1. Verify that the media tray is assigned to the blade server. Note: A reboot of the blade server the to which the media tray was previously assigned is required. 2. Check that the correct media is inserted and that the drawer is closed. 3. Inspect the media to see if there is visible damage. 4. Use another CD or DVD drive to check that the media is readable. 5. Check with other blade servers within the BladeCenter unit to see if they have the problem. If they do, the BladeCenter unit itself may be the cause of the problem. See the Problem Determination and Service Guide for your BladeCenter unit for more information. Network boot errors The following table describes the network boot errors. Table 13. Network boot errors Code Message Description Action E3000 (net) Could not read MAC address. The firmware could not establish a communication socket for booting over the network due to an error while retrieving the MAC address of the network device. Power down then reboot the blade server. If this does not resolve the problem, contact your IBM service representative. E3001 E3002 (net) Could not get IP address. (net) ARP request to TFTP server (x.x.x.x) failed. Note: (x.x.x.x) represents the address of the TFTP server. The DHCP server is not responding, or there could be a MAC address conflict in your network. v Check that your DHCP server is available v Check that an IP addresses has been correctly assigned v check that your MAC address is valid and is unique across your network The MAC address resolution failed 1. Check that the TFTP server is for the TFTP server with IP available and can be reached address (x.x.x.x). over the network. 2. Check that the DHCP server is correctly assigning IP addresses. Chapter 5. Diagnostics and troubleshooting 77

  • 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

Table
12.
System
firmware
boot
errors
(continued)
Code
Message
Description
Action
E5040
(USB)
Device
transaction
error.
<command>
Note:
<command>
indicates
the
command
in
progress
when
the
transaction
error
occurred.
This
information
may
not
always
be
available.
The
drive
showed
an
error
during
data
transfer.
1.
Verify
that
the
media
tray
is
assigned
to
the
blade
server.
Note:
A
reboot
of
the
blade
server
the
to
which
the
media
tray
was
previously
assigned
is
required.
2.
Check
that
the
correct
media
is
inserted
and
that
the
drawer
is
closed.
3.
Inspect
the
media
to
see
if
there
is
visible
damage.
4.
Use
another
CD
or
DVD
drive
to
check
that
the
media
is
readable.
5.
Check
with
other
blade
servers
within
the
BladeCenter
unit
to
see
if
they
have
the
problem.
If
they
do,
the
BladeCenter
unit
itself
may
be
the
cause
of
the
problem.
See
the
Problem
Determination
and
Service
Guide
for
your
BladeCenter
unit
for
more
information.
Network
boot
errors
The
following
table
describes
the
network
boot
errors.
Table
13.
Network
boot
errors
Code
Message
Description
Action
E3000
(net)
Could
not
read
MAC
address.
The
firmware
could
not
establish
a
communication
socket
for
booting
over
the
network
due
to
an
error
while
retrieving
the
MAC
address
of
the
network
device.
Power
down
then
reboot
the
blade
server.
If
this
does
not
resolve
the
problem,
contact
your
IBM
service
representative.
E3001
(net)
Could
not
get
IP
address.
The
DHCP
server
is
not
responding,
or
there
could
be
a
MAC
address
conflict
in
your
network.
v
Check
that
your
DHCP
server
is
available
v
Check
that
an
IP
addresses
has
been
correctly
assigned
v
check
that
your
MAC
address
is
valid
and
is
unique
across
your
network
E3002
(net)
ARP
request
to
TFTP
server
(x.x.x.x)
failed.
Note:
(x.x.x.x)
represents
the
address
of
the
TFTP
server.
The
MAC
address
resolution
failed
for
the
TFTP
server
with
IP
address
(x.x.x.x)
.
1.
Check
that
the
TFTP
server
is
available
and
can
be
reached
over
the
network.
2.
Check
that
the
DHCP
server
is
correctly
assigning
IP
addresses.
Chapter
5.
Diagnostics
and
troubleshooting
77