Filter
Top Products
5 Teaming (AFT/ALB/SFT/Static Link Aggregation) 71
E
5.4 Event Log
When using AFT/ALB/SFT/static link aggregation, the following event logs appear (Source: i
ANSMiniport).
Notes
• Even when the teaming operation is started correctly, ID=6, 7, 8 event logs are stored at the system
boot. These can be ignored as they are not a problem.
• When teaming is configured, multiple logs, such as ID=11, 13, and 22 warning logs and ID=15
event log, may be stored in the event viewer system log at the system boot. These can be ignored
as they are not a problem. If the [Wait for Link] is selected in the [Advanced (Advanced Adapter
Settings)], ID=11, 13, and 22 warning logs and ID=15 event log may not be stored.
• Even when the onboard LAN remote management function is not used, the ID=42 event log will
be stored. This can be ignored as it is not a problem when the remote management function is not
used.
• Even when the teaming operation has started correctly, ID=3 error log will be stored at the system
boot. This can be ignored as it is not a problem.
ID Type Message
3 Error Could not read the required registry parameter. Remove the adapter team and
configure a new team.
6 Information Primary adapter is initialized: (adapter name)
7 Information Adapter is initialized: (adapter name)
8 Information (team name): Team is initialized.
10 Information Current primary adapter is switched from the following adapter: (adapter
name)
11 Warning The following adapter link is not connected: (adapter name)
12 Information Secondary adapter takes priority: (adapter name)
13 Warning (adapter name) is disabled in the team.
14 Information Secondary adapter is added to the team again: (adapter name)
15 Information The following adapter link is connected: (adapter name)
16 Warning (team name): The last adapter lost link. Network connection is lost.
17 Information (team name): Adapter reestablished link. Network connection is recovered.
18 Information The following preferred primary adapter is detected: (adapter name)
19 Information The following preferred secondary adapter is detected: (adapter name)
20 Information The following preferred primary adapter takes priority: (adapter name)
21 Information The following preferred secondary adapter takes priority: (adapter name)
22 Warning Primary adapter could not detect the following probe: (adapter name) Cause:
A team may be divided.
35 Warning (team name) missing one adapter is initialized. Check that all adapters exist.
38 Information (adapter name) is removed from the team.
42 Warning (adapter name) is not set correctly.
Adapter cannot process remote management function and be in a network
team at the same time.