Ethernet Controller Messages; Novell Netware Or Intranetware Server Odi Driver; Messages - IBM Netfinity 4500R Type 8656 Hardware Maintenance Manual

Table 1. Ethernet troubleshooting chart.
Ethernet controller problem
The Ethernet controller
stopped working when
another adapter was added
to the server.
The Ethernet controller
stopped working without
apparent cause.

Ethernet controller messages

Novell NetWare or IntraNetWare server ODI driver

messages

Table 2. Novell NetWare or IntraNetWare ODI driver messages for the Ethernet controller.
PCNTNW-NW-026 The MSM is unable to parse a required custom keyword.
Check the following:
• Make sure that the cable is connected to the Ethernet controller.
• Make sure that your PCI system BIOS is current.
• Reseat the adapter.
• Determine if the interrupt (IRQ) setting assigned to the Ethernet adapter is also
assigned to another device in the Configuration/Setup Utility program.
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.
If the problem remains, go to "Starting the diagnostic programs" on page 14 to run the
diagnostic programs.
Check the following:
• Run diagnostics for the Ethernet controller.
• Try a different connector on the hub.
• Reinstall the device drivers. Refer to your operating-system documentation and to
the ServerGuide information.
If the problem remains, go to "Starting the diagnostic programs" on page 14 to run the
diagnostic programs.
The integrated Ethernet controller might display messages from the following device
drivers:
• Novell™ NetWare™ or IntraNetWare Server ODI
• NDIS Adapter for level 2.01 (OS/2)
• NDIS Adapter for level 4.0 (Windows NT)
• SCO™ UNIX LLI
This section provides explanations of the error messages for the Novell NetWare or
IntraNetWare server ODI driver, and suggested actions to resolve each problem.
Explanation: The user entered an incorrect parameter keyword.
Action: Reload the driver using the correct keyword.
Suggested Action
19
Diagnostics