Ethernet controller messages
The integrated Ethernet controller might display messages from the following device drivers:
•Novell™ NetWare™ or IntraNetWare Server ODI
•NDIS Adapter for level 4.0 (Windows NT)
Novell NetWare or IntraNetWare server ODI driver teaming messages
This section provides explanations of the error messages for the Novell NetWare or IntraNetWare server ODI driver, and suggested actions to resolve each problem.
Message | Description | |
|
| |
Couldn’t allocate resources | Explanation: An unknown error has occurred when trying to allocate needed | |
| resources for the AFT Module. | |
| Action: | |
| • | Check the server configuration. If the problem persists, contact your |
|
| network supplier. |
| • | Verify that the Ethernet controller is enabled. If the Ethernet controller is |
|
| enabled, run the diagnostic programs. |
|
| |
AFT group for primary adapter in slot | Explanation: An attempt was made to rebind an adapter already in an AFT | |
nnn already exists. | group. | |
| Action: Check the AFT slot numbers for existing AFT teams. If the problem | |
| persists, contact your network supplier. | |
|
| |
Error locating DCT addresses in | Explanation: The bind command was entered prior to loading the device | |
internal table. Make sure that you | driver. The device driver must be loaded after loading AFT.NLM but before | |
have loaded LAN drivers after | any bind command can be issued. | |
loading AFT.NLM. | Action: Load the driver for the supported adapter and try loading the AFT | |
| module again. If the problem persists, contact your network supplier. | |
|
| |
Insufficient number of arguments | Explanation: The appropriate or expected number of parameters was not | |
specified. | entered in a command. | |
| Action: Check the parameters required for the given command. If the problem | |
| persists, contact your 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 persists, contact your network | |
| supplier. | |
|
| |
’Xxx’ is not supported for AFT team. | Explanation: A bind command has been issued for adapters not supported by | |
| AFT.NLM. | |
| Action: Make sure that you attempt to bind only adapters supported by | |
| AFT.NLM. | |
|
| |
Primary and Secondary adapters do | Explanation: A bind command was entered for an adapter team that is a | |
not match. AFT group is not created. | combination of server and client adapters. An AFT team must be a grouping of | |
| the same classification of adapter. | |
| Action: Verify that all the adapters bound in a team are of the same | |
| classification. | |
|
|
|
