Skip to main content
Network

NIC Teaming Health

Monitor whether the LBFO NIC teams on your Windows servers are up, degraded, or down.

The NIC Teaming Health check monitors NIC teams set up with Windows' built-in LBFO teaming (Load Balancing/Failover). It reports when a team is degraded or down and shows how many members of each team are active. The check runs on the agent device, on Windows only (x64 and Arm64), every 15 minutes by default; the interval is not user-configurable.

Prerequisites

The check reads LBFO teams only. Assign it only to Windows devices that have LBFO teams — on any other device it permanently reports Warning.

Steps

  1. Open the device.
  2. Go to the Checks tab and click Add Check → NIC Teaming Health.

To roll the check out to many servers, use a config package: Assign checks with config packages.

Settings

The check has no configuration fields. It always checks every LBFO team on the device.

Results

Each team is graded by the status Windows reports for it. The overall result is the worst result across all teams.

Team statusResult
UpOK
DegradedWarning
DownCritical

If the check cannot grade any teams, it reports one of these instead:

MessageResultMeaning
No NIC teams configuredWarningNo LBFO team is set up on the device.
NIC teaming (LBFO) not availableWarningThe Windows commands for LBFO teaming are not available on the device.
Team query failedWarningQuerying the teams stopped with an error. The error message from Windows is shown with it.
Only runs on WindowsWarningThe check was assigned to a device that does not run Windows.

If an unexpected error occurs, the check reports Failure.

Per team, the check collects:

  • Team name
  • Team status (Up, Degraded, or Down)
  • Number of team members and how many of them are active

A member counts as active when Windows reports its operational status as "Active". The result, however, follows the team status, not this count.

Was this helpful?

Still need help? Ask the team