IBM 867282X Maintenance Manual - Page 35

Ethernet teaming messages:, Event ID, Description, Explanation, Action

Get IBM 867282X - Eserver xSeries 300 PDF manuals and user guides
UPC - 087944650966
View all IBM 867282X manuals
Add to My Manuals
Save this manual to your list of manuals

Page 35 highlights

Ethernet teaming messages: This section displays the messages associated with Ethernet teaming. Table 5. 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. 12 Warning Explanation: Team nn. Secondary adapter is deactivated from the Team. Action: Make sure the secondary adapter is functioning properly and that the adapter cable is securely connected to the LAN. 13 Informational Explanation: Team nn. Secondary adapter has rejoined the Team. Action: None. 14 Informational Explanation: Team nn. Secondary adapter link is up. Action: None. 15 Error Explanation: Team nn. The last adapter has lost its link. Network connection has been lost. Action: Shut down the server and replace the adapters; then, restart the server to reestablish the connection. 16 Informational Explanation: Team nn. An adapter has reestablished the link. Network connection has been restored. Action: None. 17 Informational Explanation: Team nn. Preferred primary adapter has been detected. Action: None. Chapter 3. Diagnostics 27

  • 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
Ethernet teaming messages:
This section displays the messages associated with Ethernet teaming.
Table 5. 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.
12
Warning
Explanation:
Team
nn
. Secondary adapter is deactivated
from the Team.
Action:
Make sure the secondary
adapter is functioning properly and that the adapter
cable is securely connected to the LAN.
13
Informational
Explanation:
Team
nn
. Secondary adapter has rejoined
the Team.
Action:
None.
14
Informational
Explanation:
Team
nn
. Secondary adapter link is up.
Action:
None.
15
Error
Explanation:
Team
nn
. The last adapter has lost its link.
Network connection has been lost.
Action:
Shut down
the server and replace the adapters; then, restart the
server to reestablish the connection.
16
Informational
Explanation:
Team
nn
. An adapter has reestablished the
link. Network connection has been restored.
Action:
None.
17
Informational
Explanation:
Team
nn
. Preferred primary adapter has
been detected.
Action:
None.
Chapter 3. Diagnostics
27