Ethernet controller messagesThe integrated Ethernet controller might display messages from the followingdevice drivers:v Novell NetWare or IntraNetWare system open data-link interface (ODI)v Network driver interface specification (NDIS) adapter for level 4.0 (WindowsNT)Novell NetWare or IntraNetWare system ODI driver teamingmessagesThis section provides explanations of the error messages for the Novell NetWare orIntraNetWare system ODI driver, and suggested actions to resolve each problem.Table 6. NetWare driver messages for the Ethernet controllerMessage DescriptionCouldn’t allocate resources. Explanation:An unknown error has occurred when trying to allocate neededresources for the AFT Module. Action:v Check the system configuration. If the problem persists, contact yournetwork supplier.v Verify that the Ethernet controller is enabled. If the Ethernet controller isenabled, run the diagnostic programs.AFT group for primary adapter inslot nnn already exists.Explanation:An attempt was made to rebind an adapter already in an AFTgroup. Action:Check the AFT slot numbers for existing AFT teams. If theproblem persists, contact your network supplier.Error locating device control table(DCT) addresses in internal table.Make sure that you have loaded LANdrivers after loading AFT.NLM.Explanation:The bind command was entered prior to loading the devicedriver. The device driver must be loaded after loading AFT.NLM, but beforeany bind command can be issued. Action:Load the driver for the supportedadapter and try loading the AFT module again. If the problem persists,contact your network supplier.Insufficient number of argumentsspecified.Explanation:The appropriate or expected number of parameters was notentered in a command. Action:Check the parameters required for the givencommand. If the problem persists, contact your network supplier.Duplicate slot numbers detected. Explanation:An attempt has been made to bind the same slot number morethan once. Action:Check the slot numbers entered during the bind. Adapterslot numbers must be valid and unique. If the problem persists, contact yournetwork supplier.’xxx’ is not supported for AFT team. Explanation:A bind command has been issued for adapters not supportedby AFT.NLM. Action:Make sure that you attempt to bind only adapterssupported by AFT.NLM.Primary and Secondary adapters donot match. AFT group is not created.Explanation:A bind command was entered for an adapter team that is acombination of system and client adapters. An AFT team must be agrouping of the same classification of adapter. Action:Verify that all theadapters bound in a team are of the same classification.Requested number of Secondarycards are not found.Explanation:The number of adapters specified in the bind command couldnot be located. Action:Verify the numbers and slot locations of the adaptersto be bound. If the problem persists, contact your network supplier.Failed to create AFT group. Makesure that the drivers for supportedadapters are loaded, primary adapteris bound to protocols, and secondaryadapter is not bound to anyprotocols.Explanation:Binding of protocol failed. Protocol is either not bound to anyadapter or is bound to more than one adapter in the group. Action:Ensurethat the protocol is bound to only adapter in an AFT team.Chapter 6. Solving problems 95