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 | Explanation: An attempt was made to rebind an adapter |
adapter in slot nnn already | already in an AFT group. |
exists. | Action: Check the AFT slot numbers for existing AFT teams. |
| If the problem persists, contact your network supplier. |
|
|
Error locating device control | Explanation: The bind command was entered prior to |
table (DCT) addresses in | loading the device driver. The device driver must be loaded |
internal table. Make sure that | after loading AFT.NLM, but before any bind command can be |
you have loaded LAN | issued. |
drivers after loading | Action: Load the driver for the supported adapter and try |
AFT.NLM. | loading the AFT module again. If the problem persists, |
| contact your network supplier. |
|
|
Insufficient number of | Explanation: The appropriate or expected number of |
arguments specified. | 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 | Explanation: An attempt has been made to bind the same slot |
detected. | 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 | Explanation: A bind command has been issued for adapters |
AFT team. | not supported by AFT.NLM. |
| Action: Make sure that you attempt to bind only adapters |
| supported by AFT.NLM. |
|
|
Primary and Secondary | Explanation: A bind command was entered for an adapter |
adapters do not match. AFT | team that is a combination of server and client adapters. An |
group is not created. | 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 | Explanation: The number of adapters specified in the bind |
Secondary cards are not | command could not be located. |
found. | 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. | Explanation: Binding of protocol failed. Protocol is either not |
Make sure that the drivers | bound to any adapter or is bound to more than one adapter in |
for supported adapters are | the group. |
loaded, primary adapter is | Action: Ensure that the protocol is bound to only adapter in |
bound to protocols, and | an AFT team. |
secondary adapter is not |
|
bound to any protocols. |
|
|
|