IBM QS21 Service Guide - Page 97

errors

Page 97 highlights

Table 13. Network boot errors (continued) Code Message E3017 (net) TFTP block size negotiation failed Description TFTP server has sent an acknowledgement to the client without block size information for subsequent TFTP network traffic. E3018 (net) file exceeds maximum TFTP The requested file is too big to transfer size transfer via TFTP. Action The TFTP server may not be working properly. Change the TFTP server configuration to allow block size negotiation. Reboot the blade and/or the TFTP server and try again. Change the TFTP server configuration to increase the block size to a maximum value of 1432 bytes. Note: Be aware that your BladeCenter QS21 has two Ethernet controllers and can be connected to two Ethernet switches. As the blade center performs a network boot from the controller that acquires the IP address first make sure that your Linux configuration supports this. If your Linux environment requires a static IP address for a particular Ethernet port, you must set up your DHCP environment accordingly. SAS boot errors These error messages only appear if you have installed the optional SAS daughter card. Table 14. SAS boot errors Code Message E4303 LSISAS1064 controller initialization failed. Description Action The blade server firmware was not Try following steps in order to fix the able to initialize the controller. This problem: could indicate a hardware, blade server 1. Reboot the blade. firmware, or SAS expansion card firmware problem. 2. Power down then remove and reinstall the blade server in the BladeCenter unit. 3. Remove and reinstall the SAS Expansion Card. 4. Ensure the SAS Expansion Card firmware and blade firmware version are at the correct level. 5. If the error started after a SAS Expansion Card firmware upgrade or a blade server firmware upgrade, consider a rollback to the previous firmware versions. Check with the documentation at http://www.ibm.com/systems/ bladecenter/support/ to verify whether rollback is possible. 6. Plug the SAS expansion card into another blade server. If the problem persists, the SAS Expansion Card may need replacement. 7. Plug a different SAS expansion card into the blade server. If the problem persists, the blade server may need replacement. Chapter 5. Diagnostics and troubleshooting 79

  • 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
13.
Network
boot
errors
(continued)
Code
Message
Description
Action
E3017
(net)
TFTP
block
size
negotiation
failed
TFTP
server
has
sent
an
acknowledgement
to
the
client
without
block
size
information
for
subsequent
TFTP
network
traffic.
The
TFTP
server
may
not
be
working
properly.
Change
the
TFTP
server
configuration
to
allow
block
size
negotiation.
Reboot
the
blade
and/or
the
TFTP
server
and
try
again.
E3018
(net)
file
exceeds
maximum
TFTP
transfer
size
The
requested
file
is
too
big
to
transfer
via
TFTP.
Change
the
TFTP
server
configuration
to
increase
the
block
size
to
a
maximum
value
of
1432
bytes.
Note:
Be
aware
that
your
BladeCenter
QS21
has
two
Ethernet
controllers
and
can
be
connected
to
two
Ethernet
switches.
As
the
blade
center
performs
a
network
boot
from
the
controller
that
acquires
the
IP
address
first
make
sure
that
your
Linux
configuration
supports
this.
If
your
Linux
environment
requires
a
static
IP
address
for
a
particular
Ethernet
port,
you
must
set
up
your
DHCP
environment
accordingly.
SAS
boot
errors
These
error
messages
only
appear
if
you
have
installed
the
optional
SAS
daughter
card.
Table
14.
SAS
boot
errors
Code
Message
Description
Action
E4303
LSISAS1064
controller
initialization
failed.
The
blade
server
firmware
was
not
able
to
initialize
the
controller.
This
could
indicate
a
hardware,
blade
server
firmware,
or
SAS
expansion
card
firmware
problem.
Try
following
steps
in
order
to
fix
the
problem:
1.
Reboot
the
blade.
2.
Power
down
then
remove
and
reinstall
the
blade
server
in
the
BladeCenter
unit.
3.
Remove
and
reinstall
the
SAS
Expansion
Card.
4.
Ensure
the
SAS
Expansion
Card
firmware
and
blade
firmware
version
are
at
the
correct
level.
5.
If
the
error
started
after
a
SAS
Expansion
Card
firmware
upgrade
or
a
blade
server
firmware
upgrade,
consider
a
rollback
to
the
previous
firmware
versions.
Check
with
the
documentation
at
bladecenter/support/
to
verify
whether
rollback
is
possible.
6.
Plug
the
SAS
expansion
card
into
another
blade
server.
If
the
problem
persists,
the
SAS
Expansion
Card
may
need
replacement.
7.
Plug
a
different
SAS
expansion
card
into
the
blade
server.
If
the
problem
persists,
the
blade
server
may
need
replacement.
Chapter
5.
Diagnostics
and
troubleshooting
79