Event Logs - Fujitsu Primergy RX300 S4 User Manual

Chapter 4 Operations after OS Installation
• "Team: (Team Name)"
Upper protocols will be bound with the main virtual adapter.
They cannot be bound with the LAN card included in a Team.
The IP address can be set in the main virtual adapter.

Event logs

When configuring a team, the following event logs will be generated (source: iANSMiniport).
ID Type
3 Error
6 Information
7 Information
8 Information
10 Information
11 Warning
12 Information
13 Warning
14 Information
15 Information
16 Warning
17 Information
18 Information
19 Information
20 Information
21 Information
22 Warning
35 Warning
38 Information
42 Warning
When the teaming function normally starts running, event logs (ID = 6 to 8) are stored at boot of the
system. This is not a problem; no action is required.
Once a Team is setup, plural warning logs (ID = 11, 13, 22) and event logs (ID =15, etc.) may be stored
in the system log of the event viewer at boot of the system. This is not a problem; no action is required.
When enable [Link Standby] in the [Advanced Settings] of the LAN adapter, warning logs (ID = 11, 13,
22) and event logs (ID =15, etc.) may not be stored.
When not using the remote management function on the onboard LAN, event log (ID =42) may be
stored. When not using the remote management function, this is not a problem; no action is required.
When teaming starts operation properly, error log (ID =3) may be stored at system start. This is not a
problem; no action is required.
122
table: Event log messages
The necessary registry parameter could not be read. To resolve this problem, delete the
adapter team, and create a new team.
The primary adapter has been initialized: (Adapter name)
The adapter has been initialized: (Adapter name)
(Team name): The team has been initialized.
The current primary adapter is changed from the next adapter: (Adapter name)
The next adapter link is not connected: (Adapter name)
The secondary adapter has a priority: (Adapter name)
(Adapter name) has been disabled with a team.
The secondary adapter has been added to a team again: (Adapter name)
The next adapter link is connected: (Adapter name)
(Team name): The last adapter has been unlinked. The team network connection has
failed.
(Team name): The adapter has established a link again. The team network connection has
been recovered.
The primary adapter at the next priority level has been detected: (Adapter name)
The secondary adapter at the next priority level has been detected: (Adapter name)
The primary adapter at the next priority level is preferentially handled: (Adapter name)
The secondary adapter at the next priority level is preferentially handled: (Adapter name)
The primary adapter could not detect the next probe: (Adapter name) Cause: The team
may be divided into groups.
(Team name) without one adapter is initialized. Confirm that all adapters exist and
function.
(Adapter name) has been deleted from the team.
(Adapter name) is not specified properly. The adapter cannot process the remote
management function while being a network team.
Message