IBM 8654 Hardware Maintenance Manual - Page 31

Explanation, Action, Start -> Control Panel -> Networks -> Adapters

Get IBM 8654 - Eserver xSeries 330 PDF manuals and user guides
UPC - 087944618102
View all IBM 8654 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 31 highlights

Table 6. NDIS (Windows NT or Windows 2000) driver messages for the Ethernet controller. Error code (hex) Description 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, make sure that Ethernet is enabled. 0x11 Explanation: Multiple Ethernet controllers found, but none matched the required ID. Action: Using the Configuration/Setup utility, 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, make sure that Ethernet is enabled. 0x16 Explanation: Single adapter found but multiple instances tried to load. Action: Using the Configuration/Setup utility, make sure that Ethernet is enabled, and that the slot containing the IBM Netfinity 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 4character hexadecimal codes Action: Call for service. Ethernet teaming messages: Table 7. NDIS (Windows NT or Windows 2000) driver teaming messages for the Ethernet controller. Event ID 01 02 03 04 05 06 07 08 09 10 11 Type Error Error Error Error Error Informational Informational Informational Informational Warning Informational Description Explanation: Team Name and physical adapter name are the same. This is an invalid configuration. Action: Reconfigure the adapter team by doubleclicking the PROSet icon in the control panel. Explanation: Unable to allocate required resources. Action: Free some memory resources and restart. Explanation: Unable to read required registry parameters. Action: Reconfigure the adapter team by double-clicking the PROSet icon in the control panel. Explanation: Unable to bind to physical adapter. Action: Reconfigure the adapter team by double-clicking the PROSet icon in the control panel. Explanation: Unable to initialize an adapter team. Action: Reconfigure the adapter team by double-clicking the PROSet icon in the control panel. Explanation: Team nn. Primary adapter is initialized. Action: None. Explanation: Team nn. Secondary adapter is initialized. Action: None. Explanation: Team nn. Virtual adapter or Team is initialized. Action: None. Explanation: Team nn. Primary adapter is switching over. Action: None. Explanation: Team nn. Adapter link down. Action: Make sure the adapter is functioning properly. Explanation: Team nn. Secondary adapter took over. Action: None. Chapter 3. 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
  • 157
  • 158
Chapter 3.
Diagnostics
23
Ethernet teaming messages:
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,
make sure that Ethernet is enabled.
0x11
Explanation:
Multiple Ethernet controllers found, but none matched the required ID.
Action:
Using the Configuration/Setup utility, 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, make sure that Ethernet is enabled.
0x16
Explanation:
Single adapter found but multiple instances tried to load.
Action:
Using the
Configuration/Setup utility, make sure that Ethernet is enabled, and that the slot containing the
IBM Netfinity 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.
Table 7. NDIS (Windows NT or Windows 2000) 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.
09
Informational
Explanation:
Team
nn
.
Primary adapter is switching over.
Action:
None.
10
Warning
Explanation:
Team
nn
.
Adapter link down.
Action:
Make sure the adapter
is functioning properly.
11
Informational
Explanation:
Team
nn
.
Secondary adapter took over.
Action:
None.
Table 6. NDIS (Windows NT or Windows 2000) driver messages for the Ethernet controller.
Error code (hex)
Description