IBM 8682 - Eserver xSeries 350 Hardware Maintenance Manual page 36

Table 3. Novell NetWare or IntraNetWare ODI driver messages for the Ethernet controller
PCNTNW-NW-026
PCNTNW-NW-054
PCNTNW-NW-058
PCNTNW-NW-066
PCNTNW-NW-071
PCNTNW-NW-072
PCNTNW-NW-073
PCNTNW-NW-074
PCNTNW-NW-075
26
IBM xSeries 350 Type 8682: Hardware Maintenance Manual
The MSM is unable to parse a required custom keyword.
Explanation: The user entered an incorrect parameter keyword.
Action: Reload the driver using the correct keyword.
The adapter did not respond to the initialization command.
Explanation: The adapter did not respond when the driver tried to initialize it.
Action: Verify that the Ethernet controller is enabled. If the Ethernet controller is
enabled, go to "Starting the diagnostic programs" on page 14 to run the diagnostic
programs.
The adapter did not respond to the initialization command.
Explanation: The interrupt request (IRQ) setting might not be valid or the EEPROM
information might be incorrect.
Action: Make sure the IRQ settings are correct in the Configuration/Setup Utility
program. for information on setting the interrupt requests. If the IRQ settings are
correct, go to "Starting the diagnostic programs" on page 14 to run the diagnostic
programs.
The cable might be disconnected from the adapter.
Explanation: The cable might be disconnected from the server Ethernet port.
Action: Verify that a cable is connected to the Ethernet port.
The matching virtual adapter could not be found.
Explanation: You tried to load another instance of the driver with a different I/O
address. This new adapter could not be found.
Action: Verify that you installed an IBM 10/100 Fault Tolerant Adapter and make sure
that the adapter is seated correctly. If the adapter is seated correctly, go to "Starting
the diagnostic programs" on page 14 to run the diagnostic programs.
A resource tag is unavailable.
Explanation: The driver tried to allocate some resources that were not available.
Action: Add more memory, or free some memory resources in the server. Then,
restart the server.
Unable to allocate memory
Explanation: The driver failed to allocate the memory needed for normal operation.
Action: Add more memory, or free some memory resources in the server. Then,
restart the server.
The hardware interrupt cannot be set.
Explanation: An attempt was made to initialize a given hardware interrupt. The
attempt was not successful.
Action: Verify that the Ethernet controller is enabled. If the Ethernet controller is
enabled, go to "Starting the diagnostic programs" on page 14 to run the diagnostic
programs. If you have an Ethernet adapter installed, make sure that the adapter does
not share an IRQ with any other device.
The Multiple Link Interface Driver (MLID) cannot be registered with the Link
Support Layer (LSL).
Explanation: An error occurred while the driver was trying to register with the LSL.
Action: Check the version of the NetWare or IntraNetWare Operating System. Make
sure that this driver is correct for the version of NetWare or IntraNetWare that you are
using. Restart the server.