IBM 8479 User Reference - Page 102

Ethernet teaming messages, This describes the messages associated with Ethernet teaming.

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 102 highlights

Table 14. NDIS (Windows NT) driver messages for the Ethernet controller. Error code (hex) Description 0x10 Explanation: Did not find any Ethernet controllers. 0x11 Action: Using the Configuration/Setup Utility program, make sure that Ethernet is enabled. Explanation: Multiple Ethernet controllers found, but none matched the required ID. 0x13 Action: Using the Configuration/Setup Utility program, make sure that Ethernet is enabled. Explanation: Did not find any Ethernet controllers that matched the required subven/subdev. 0x16 Action: Using the Configuration/Setup Utility program, make sure that Ethernet is enabled. Explanation: Single adapter found, but multiple instances tried to load. 0x17 Action: Using the Configuration/Setup Utility program, make sure that Ethernet is enabled, and that the slot containing the IBM xSeries 200 10/100 Ethernet Adapter or the IBM 10/100 Etherjet PCI adapter is enabled. Explanation: Slot parameter not specified in the registry. All other 4character hexadecimal codes Action: Remove the adapter driver and reinstall it. If the problem persists, call for service. Action: Call for service. Ethernet teaming messages This section describes the messages associated with Ethernet teaming. Table 15. NDIS (Windows NT) driver teaming messages for the Ethernet controller. Event ID 01 Type Error Description 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. 88 IBM xSeries 200: User's Reference

  • 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
88
IBM xSeries 200: User’s Reference
Ethernet teaming messages
This section describes the messages associated with Ethernet teaming.
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 xSeries 200 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 14. NDIS (Windows NT) driver messages for the Ethernet controller.
Error code (hex)
Description
Table 15. 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.