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

Ethernet teaming messages, Error code hex

Page 113 highlights

Table 7. NDIS (Windows NT) driver messages for the Ethernet controller (continued) Error code (hex) Description 0x0E Explanation: Could not allocate enough memory for receive queue. Action: 1. From the Windows NT desktop, select Start --> Control Panel --> Networks --> Adapters. 2. Select your IBM Ethernet adapter from the list. 3. Select Properties --> Advanced. 4. Lower the resource values that apply to the receive queue. 0x0F Explanation: Could not allocate enough memory for other structures. Action: 1. From the Windows NT desktop, select Start --> Control Panel --> Networks --> Adapters. 2. Select your IBM Ethernet adapter from the list. 3. Select Properties --> Advanced. 4. Lower the value for the resource named in the message. 0x10 Explanation: Did not find any Ethernet controllers. Action:Using the Configuration/Setup Utility program, make sure that Ethernet is enabled. 0x11 Explanation: Multiple Ethernet controllers found, but none matched the required ID. Action:Using the Configuration/Setup Utility program, make sure that Ethernet is enabled. 0x13 Explanation: Did not find any Ethernet controllers that matched the required subven/subdev. Action:Using the Configuration/Setup Utility program, make sure that Ethernet is enabled. 0x16 Explanation: Single adapter found, but multiple instances tried to load. Action:Using the Configuration/Setup Utility program, make sure that Ethernet is enabled, and that the slot containing the IBM IntelliStation 10/100 Ethernet Adapter or the IBM 10/100 Etherjet PCI adapter is enabled. 0x17 Explanation: Slot parameter not specified in the registry. Action:Remove the adapter driver and reinstall it. If the problem persists, call for service. All other 4-character hexadecimal codes Action:Call for service. Ethernet teaming messages This section displays the messages associated with Ethernet teaming. Table 8. NDIS (Windows NT ) driver teaming messages for the Ethernet controller Event ID Type Description 01 Error Explanation:Team Name and physical adapter name are the same. This is an invalid configuration. Action:Reconfigure the adapter team by double-clicking the PROSeticon in the control panel. 02 Error Explanation:Unable to allocate required resources. Action:Free some memory resources and restart. 03 Error Explanation:Unable to read required registry parameters. Action:Reconfigure the adapter team by double-clicking the PROSeticon in the control panel. 04 Error Explanation:Unable to bind to physical adapter. Action:Reconfigure the adapter team by double-clicking the PROSet icon in the control panel. 05 Error Explanation:Unable to initialize an adapter team. Action:Reconfigure the adapter team by double-clicking the PROSet icon in the control panel. 06 Informational Explanation:Team nn. Primary adapter is initialized. Action:None. 07 Informational Explanation:Team nn. Secondary adapter is initialized. Action:None. 08 Informational Explanation:Team nn. Virtual adapter or Team is initialized. Action:None. Chapter 6. Solving problems 97

  • 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 7. NDIS (Windows NT) driver messages for the Ethernet controller (continued)
Error code (hex)
Description
0x0E
Explanation:
Could not allocate enough memory for receive queue.
Action:
1.
From the Windows NT desktop, selec
t Start --> Control Panel --> Networks --> Adapters
.
2.
Select your IBM Ethernet adapter from the list.
3.
Select
Properties --> Advanced
.
4.
Lower the resource values that apply to the receive queue.
0x0F
Explanation:
Could not allocate enough memory for other structures.
Action:
1.
From the Windows NT desktop, select
Start --> Control Panel --> Networks --> Adapters
.
2.
Select your IBM Ethernet adapter from the list.
3.
Select
Properties --> Advanced
.
4.
Lower the value for the resource named in the message.
0x10
Explanation:
Did not find any Ethernet controllers.
Action:
Using the Configuration/Setup
Utility program, make sure that Ethernet is enabled.
0x11
Explanation:
Multiple Ethernet controllers found, but none matched the required ID.
Action:
Using the Configuration/Setup Utility program, make sure that Ethernet is enabled.
0x13
Explanation:
Did not find any Ethernet controllers that matched the required subven/subdev.
Action:
Using the Configuration/Setup Utility program, make sure that Ethernet is enabled.
0x16
Explanation:
Single adapter found, but multiple instances tried to load.
Action:
Using the
Configuration/Setup Utility program, make sure that Ethernet is enabled, and that the slot
containing the IBM IntelliStation 10/100 Ethernet Adapter or the IBM 10/100 Etherjet PCI
adapter is enabled.
0x17
Explanation:
Slot parameter not specified in the registry.
Action:
Remove the adapter driver and
reinstall it. If the problem persists, call for service.
All other
4-character
hexadecimal
codes
Action:
Call for service.
Ethernet teaming messages
This section displays the messages associated with Ethernet teaming.
Table 8. NDIS (Windows NT ) driver teaming messages for the Ethernet controller
Event ID
Type
Description
01
Error
Explanation:
Team Name and physical adapter name are the same. This is
an invalid configuration.
Action:
Reconfigure the adapter team by
double-clicking the
PROSet
icon in the control panel.
02
Error
Explanation:
Unable to allocate required resources.
Action:
Free some
memory resources and restart.
03
Error
Explanation:
Unable to read required registry parameters.
Action:
Reconfigure the adapter team by double-clicking the
PROSet
icon
in the control panel.
04
Error
Explanation:
Unable to bind to physical adapter.
Action:
Reconfigure the
adapter team by double-clicking the
PROSet
icon in the control panel.
05
Error
Explanation:
Unable to initialize an adapter team.
Action:
Reconfigure the
adapter team by double-clicking the
PROSet
icon in the control panel.
06
Informational
Explanation:
Team
nn
. Primary adapter is initialized.
Action:
None.
07
Informational
Explanation:
Team
nn
. Secondary adapter is initialized.
Action:
None.
08
Informational
Explanation:
Team
nn
. Virtual adapter or Team is initialized.
Action:
None.
Chapter 6. Solving problems
97