Hyper-V: A Team Bound to a Virtual Switch Should Only Have One Exposed Team Interface - TechNet Articles - United States (English) - TechNet Wiki

Table of Contents

Hyper-V: A Team Bound to a Virtual Switch Should Only Have One Exposed Team Interface



This article is intended to provide more information about a specific issue that can be identified by running a Best Practices Analyzer scan for Hyper-V. It also can be used without running a scan, as general troubleshooting and best practice information to help you configure your server appropriately. If you have troubleshooting steps or information that would improve this article, please add it. For instructions on how to edit a TechNet Wiki article, see Wiki: How to Use the Editor.

For more information about best practices and scans, see Run Best Practices Analyzer Scans and Manage Scan Results.

Operating System

Windows Server 2012

Product/Feature

Hyper-V

Severity

Category

Issue

One or more virtual switches are bound to a team that has multiple team interfaces.

Impact

The following virtual switches might not have access to VLANs and bandwidth used by other team interfaces: <list of virtual machines>

Resolution

Use the Windows PowerShell cmdlet Remove-NetLbfoTeamNic to remove all team interfaces from the team other than the default team interface.