Lenovo NetVista X40 Quick Reference for NetVista 2179 and 6643 systems (Dutch) - Page 111

Ethernet controller messages, Novell NetWare or IntraNetWare system ODI driver teamingmessages

Get Lenovo NetVista X40 PDF manuals and user guides View all Lenovo NetVista X40 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 111 highlights

Ethernet controller messages The integrated Ethernet controller might display messages from the following device drivers: v Novell NetWare or IntraNetWare system open data-link interface (ODI) v Network driver interface specification (NDIS) adapter for level 4.0 (Windows NT) Novell NetWare or IntraNetWare system ODI driver teaming messages This section provides explanations of the error messages for the Novell NetWare or IntraNetWare system ODI driver, and suggested actions to resolve each problem. Table 6. 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: v Check the system configuration. If the problem persists, contact your network supplier. v 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 device control table Explanation:The bind command was entered prior to loading the device (DCT) addresses in internal table. driver. The device driver must be loaded after loading AFT.NLM, but before Make sure that you have loaded LAN any bind command can be issued. Action:Load the driver for the supported drivers after loading AFT.NLM. 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 system 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. Chapter 6. Solving problems 95

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
Ethernet controller messages
The integrated Ethernet controller might display messages from the following
device drivers:
v
Novell NetWare or IntraNetWare system open data-link interface (ODI)
v
Network driver interface specification (NDIS) adapter for level 4.0 (Windows
NT)
Novell NetWare or IntraNetWare system ODI driver teaming
messages
This section provides explanations of the error messages for the Novell NetWare or
IntraNetWare system ODI driver, and suggested actions to resolve each problem.
Table 6. 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:
v
Check the system configuration. If the problem persists, contact your
network supplier.
v
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 device control table
(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 system 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.
Chapter 6. Solving problems
95