IBM 8479 User Reference - Page 99

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

Get IBM 8479 - Eserver xSeries 200 PDF manuals and user guides
UPC - 087944653912
View all IBM 8479 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 99 highlights

Table 12. Ethernet troubleshooting chart. Ethernet controller problem The Ethernet controller stopped working without apparent cause. Suggested action Check the following: • Run diagnostics for the Ethernet controller. • Try a different connector on the hub. • Reinstall the device drivers. Refer to your operating system documentation and to the ServerGuide information. If the problem remains, call for service. Ethernet controller messages The integrated Ethernet controller might display messages from the following device drivers: • Novell NetWare or IntraNetWare system open data-link interface (ODI) • 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 13. NetWare driver messages for the Ethernet controller. Message Couldn't allocate resources. Description Explanation: An unknown error has occurred when trying to allocate needed resources for the AFT Module. Action: • Check the system 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 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. your network supplier. 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. Chapter 6. Solving problems 85

  • 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
Chapter 6.
Solving problems
85
Ethernet controller messages
The integrated Ethernet controller might display messages from the following device
drivers:
•
Novell NetWare or IntraNetWare system open data-link interface (ODI)
•
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.
The Ethernet controller
stopped working without
apparent cause.
Check the following:
•
Run diagnostics for the Ethernet controller.
•
Try a different connector on the hub.
•
Reinstall the device drivers. Refer to your operating system documentation and to
the ServerGuide information.
If the problem remains, call for service.
Table 12. Ethernet troubleshooting chart.
Ethernet controller
problem
Suggested action
Table 13. 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 system 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 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. your network supplier.
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.