Table 3. NetWare driver messages for the Ethernet controller (continued)
Message
Description
Failed to create AFT group.
Make sure that the drivers
for supported adapters are
loaded, primary adapter is
bound to protocols, and
secondary adapter is not
bound to any protocols.
Explanation:
Binding of protocol failed. Protocol is either
not bound to any adapter or is bound to more than one
adapter in the group.
Action:
Ensure that the protocol is
bound to only adapter in an AFT team.
Error identifying slot
numbers for the specified
board names.
Explanation:
The mapping between the board name entered
and the slot number for an adapter could not be
established.
Action:
Check the board name for the adapter
before issuing the bind command.
Can’t unbind specified slot
from AFT group. Make sure
that the slot you specified is
for the primary adapter in an
AFT group.
Explanation:
The number entered in the unbind command
was not the primary adapter in an AFT group.
Action:
Reissue the unbind command and specify the slot number
for the primary adapter.
LAN adapter at slot
nnnn
(Port 0x
aa
) failed to reset.
Check the state of the
adapter.
Explanation:
The adapter that you specified could not be
initialized.
Action:
1.
Load the driver for the supported adapter.
2.
Check that the adapter is seated properly in the slot and
try loading the AFT module again.
AFT is not supported on this
version of NetWare
™
.
Explanation:
The NetWare on your server is not a version
supported by AFT.
Action:
Load and bind AFT only on
supported versions of NetWare (currently version 4.11 and
above).
Failed to allocate resources
tags.
Explanation:
An unknown error has occurred when trying
to allocate needed resources for the AFT module.
Action:
Check server configuration.
Please unload all LAN
drivers before unloading
AFT.NLM.
Explanation:
An attempt was made to unload the AFT.NLM
module before unloading the adapter driver.
Action:
Unload the adapter driver before unloading the AFT
module.
NDIS 4.0 (Windows NT) driver messages
This section contains the error messages for the NDIS 4.0 drivers. The explanation
and recommended action are included with each message.
Table 4. NDIS (Windows NT or Windows 2000) driver messages for the Ethernet controller
Error code
(hex)
Description
0x00
Explanation:
The driver could not register the specified interrupt.
Action:
Using the Configuration/Setup Utility program, make sure that a PCI
interrupt is assigned to your Ethernet card, and that Ethernet is enabled.
0x01
Explanation:
One of the PCI cards did not get the required resources.
Action:
Using the Configuration/Setup Utility program, make sure that a
PCI interrupt is assigned to your Ethernet card, and that Ethernet is
enabled.
0x02
Explanation:
Bad node address (multicast address).
Action:
Make sure the
locally administered address is valid, if one is specified. The address can
not be a multicast address.
Chapter 3. Diagnostics
25
Summary of Contents for xSeries 300
Page 1: ...Hardware Maintenance Manual xSeries 300 ...
Page 2: ......
Page 3: ...Hardware Maintenance Manual xSeries 300 ...
Page 10: ...2 Hardware Maintenance Manual xSeries 300 ...
Page 42: ...34 Hardware Maintenance Manual xSeries 300 ...
Page 93: ...Chapter 9 Related service information 85 ...
Page 94: ...86 Hardware Maintenance Manual xSeries 300 ...
Page 95: ...Chapter 9 Related service information 87 ...
Page 96: ...88 Hardware Maintenance Manual xSeries 300 ...
Page 97: ...Chapter 9 Related service information 89 ...
Page 98: ...90 Hardware Maintenance Manual xSeries 300 ...
Page 99: ...Chapter 9 Related service information 91 ...
Page 100: ...92 Hardware Maintenance Manual xSeries 300 ...
Page 110: ...102 Hardware Maintenance Manual xSeries 300 ...
Page 111: ...Chapter 9 Related service information 103 ...
Page 112: ...104 Hardware Maintenance Manual xSeries 300 ...
Page 119: ......