Filter
Top Products
Chapter 3. Diagnostics 21
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.
Table 5. NetWare driver messages for the Ethernet controller.
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
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 persists, contact your network supplier.
Error locating 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 persists, contact
your 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 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
not match. AFT group is not created.
Explanation: A bind command was entered for an adapter team that is a
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.
Requested number of Secondary
cards are not found.
Explanation: The number of adapters specified in the bind command could
not be located. Action: Verify the numbers and slot locations of the adapters to
be bound. If the problem persists, contact your network supplier.
Failed to create AFT group. Make
sure that the drivers for supported
adapters are loaded, primary adapter
is bound to protocols, and secondary
adapter is not bound to any protocols.
Explanation: Binding of protocol failed. Protocol is either not bound to any
adapter or is bound to more than one adapter in the group. Action: Ensure that
the protocol is bound to only adapter in an AFT team.
Error identifying slot numbers for the
specified board names.
Explanation: The mapping between the board name entered and the slot
number for an adapter could not be established. Action: Check the board name
for the adapter before issuing the bind command. If the problem persists,
contact your network supplier.