IBM 620410U User Guide - Page 119

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

Page 119 highlights

Ethernet teaming messages This section displays the messages associated with Ethernet teaming. Table 7. NDIS (Windows 2000 or Windows XP) 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. Team is initialized. Action: None. 09 Informational Explanation: Team nn. Virtual adapter is initialized. Action: None. 10 Informational Explanation: Team nn. Primary adapter is switching over. Action: None. 11 Warning Explanation: Team nn. Adapter link down. Action: Make sure the adapter is functioning properly. 12 Informational Explanation: Team nn. Secondary adapter took over. Action: None. 13 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. 14 Informational Explanation: Team nn. Secondary adapter has rejoined the team. Action: None. 15 Informational Explanation: Team nn. Secondary adapter link is working. Action: None. Chapter 6. Solving problems 103

  • 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
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166

Ethernet teaming messages
This section displays the messages associated with Ethernet teaming.
Table 7. NDIS (Windows 2000 or Windows XP) 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
. Team is initialized.
Action:
None.
09
Informational
Explanation:
Team
nn
. Virtual adapter is initialized.
Action:
None.
10
Informational
Explanation:
Team
nn
. Primary adapter is switching over.
Action:
None.
11
Warning
Explanation:
Team
nn
. Adapter link down.
Action:
Make sure the adapter is functioning properly.
12
Informational
Explanation:
Team
nn
. Secondary adapter took over.
Action:
None.
13
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.
14
Informational
Explanation:
Team
nn
. Secondary adapter has rejoined the team.
Action:
None.
15
Informational
Explanation:
Team
nn
. Secondary adapter link is working.
Action:
None.
Chapter 6. Solving problems
103