IBM eServer xSeries 335 Type 8676, Hardware Maintenance Manual And Troubleshooting Manual

Page: 43 / 178

Table 4. Ethernet troubleshooting chart (continued)
Ethernet controller
problem FRU/actions
The Ethernet controller
stopped working without
apparent cause. Check the following:
v
Run diagnostics for the Ethernet controller.
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 information in this section might be helpful. The latest information
available concerning these messages will be made available at the IBM Support
Web site at http://www.ibm.com/pc/support.
Note: Although the term
″
adapter
″
is used in these messages, the messages might
also apply to the integrated Ethernet controller on the system board.
Novell NetWare or IntraNetWare system ODI driver messages
This section explains the error messages for the Novell NetWare or IntraNetWare
system ODI driver, and suggested actions to resolve each problem.
Table 5. NetWare or IntraNetWare system ODI driver teaming messages for the Ethernet controller
Message Description
Could not allocate resources. Explanation: An unknown error has occurred when trying to allocate needed
resources for the AFT Module.
Action:
v Check the system configuration. If the problem remains, contact the
network supplier.
v Verify that the Ethernet controller is enabled. If the Ethernet controller is
enabled, run the diagnostic programs.
AFT group for primary adapter in slot
nnn already exists.
Explanation: An attempt was made to rebind an adapter already in an AFT
group.
Action: Check the AFT slot numbers for existing AFT teams. If the problem
remains, contact the network supplier.
Error locating device control table
(DCT) addresses in internal table.
Make sure that you have loaded LAN
drivers after loading AFT.NLM. Explanation: The bind command was entered prior to loading the device
driver. The device driver must be loaded after loading AFT.NLM, but before
any bind command can be issued.
Action: Load the driver for the supported adapter and try loading the AFT
module again. If the problem remains, contact the network supplier.
Insufficient number of arguments
specified. Explanation: The appropriate or expected number of parameters was not
entered in a command.
Action: Check the parameters required for the given command. If the
problem remains, contact the network supplier.
Duplicate slot numbers detected. Explanation: An attempt has been made to bind the same slot number more
than once.
Action: Check the slot numbers entered during the bind. Adapter slot
numbers must be valid and unique. If the problem remains, contact the
network supplier.
Chapter 3. Diagnostics
33