IBM 8646 Hardware Maintenance Manual - Page 31

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

Get IBM 8646 - Eserver xSeries 220 PDF manuals and user guides View all IBM 8646 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 31 highlights

Table 3. Ethernet troubleshooting chart (continued) Ethernet controller problem Suggested Action The Ethernet controller stopped working when another adapter was added to the server. Check the following: v Make sure that the cable is connected to the Ethernet controller. v Make sure that your PCI system BIOS is current. v Reseat the adapter. v Determine if the interrupt (IRQ) setting assigned to the Ethernet adapter is also assigned to another device in the Configuration/Setup Utility program. Although interrupt sharing is allowed for PCI devices, some devices do not function well when they share an interrupt with a dissimilar PCI device. Try changing the IRQ assigned to the Ethernet adapter or the other device. The Ethernet controller stopped working without apparent cause. Check the following: v Run diagnostics for the Ethernet controller. v Try a different connector on the hub. v Reinstall the device drivers. Refer to your operating-system documentation and to the ServerGuide information. Ethernet controller messages The integrated Ethernet controller might display messages from the following device drivers: v Novell¬ NetWare¬ or IntraNetWare Server ODI v NDIS Adapter for level 4.0 (Microsoft« Windows NT«) 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 4. 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 server 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 Explanation: An attempt was made to rebind an adapter already adapter in slot nnn in an AFT group. Action: Check the AFT slot numbers for existing already exists. 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. Diagnostics 23

  • 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
Table 3. Ethernet troubleshooting chart (continued)
Ethernet
controller
problem
Suggested Action
The Ethernet
controller stopped
working when
another adapter
was added to the
server.
Check the following:
v
Make sure that the cable is connected to the Ethernet controller.
v
Make sure that your PCI system BIOS is current.
v
Reseat the adapter.
v
Determine if the interrupt (IRQ) setting assigned to the Ethernet
adapter is also assigned to another device in the
Configuration/Setup Utility program.
Although interrupt sharing is allowed for PCI devices, some devices
do not function well when they share an interrupt with a dissimilar
PCI device. Try changing the IRQ assigned to the Ethernet adapter
or the other device.
The Ethernet
controller stopped
working without
apparent cause.
Check the following:
v
Run diagnostics for the Ethernet controller.
v
Try a different connector on the hub.
v
Reinstall the device drivers. Refer to your operating-system
documentation and to the ServerGuide information.
Ethernet controller messages
The integrated Ethernet controller might display messages from the following
device drivers:
v
Novell
¬
NetWare
¬
or IntraNetWare Server ODI
v
NDIS Adapter for level 4.0 (Microsoft
«
Windows NT
«
)
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 4. 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 server 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 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.
Diagnostics
23