NIC 小組NIC Teaming

適用於:Windows Server(以每年次管道)、Windows Server 2016Applies To: Windows Server (Semi-Annual Channel), Windows Server 2016

本主題提供 Windows Server 2016 中的 [網路介面卡 (NIC) Teaming 的概觀。This topic provides an overview of Network Interface Card (NIC) Teaming in Windows Server 2016.

NIC 小組概觀NIC Teaming Overview

NIC 小組可讓您一個和通知三十的兩個實體乙太網路介面卡之間一或多個軟體 virtual 網路介面卡插入群組。NIC Teaming allows you to group between one and thirty-two physical Ethernet network adapters into one or more software-based virtual network adapters. 這些 virtual 網路介面卡提供快的效能與網路介面卡失敗容錯。These virtual network adapters provide fast performance and fault tolerance in the event of a network adapter failure.

NIC 小組成員網路介面卡必須所有安裝在相同的實體主機電腦處於團隊。NIC Team member network adapters must all be installed in the same physical host computer to be placed in a team.

注意

NIC 團隊,其中包含一個網路介面卡不能提供負載平衡和容錯移轉。不過一個網路介面卡,您可以使用 NIC 小組的網路流量之分開時也會使用區域網路 (Vlan)。A NIC team that contains only one network adapter cannot provide load balancing and failover; however with one network adapter, you can use NIC Teaming for separation of network traffic when you are also using virtual Local Area Networks (VLANs).

當您設定網路介面卡插入 NIC 團隊時,這些連接到 NIC 小組方案常見核心,會再顯示一或多個 virtual 介面卡(也稱為小組 Nic [tNICs] 或小組介面)作業系統。When you configure network adapters into a NIC team, they are connected into the NIC teaming solution common core, which then presents one or more virtual adapters (also called team NICs [tNICs] or team interfaces) to the operating system. Windows Server 2016 支援最多 32 個小組介面每個小組。Windows Server 2016 supports up to 32 team interfaces per team. 有各種不同的輸出的流量(載入)Nic 之間的演算法。There are a variety of algorithms that distribute outbound traffic (load) between the NICs.

下圖描述使用多個 tNICs NIC 團隊。The following illustration depicts a NIC Team with multiple tNICs.

使用多個 tNICs NIC 小組

此外,您可以在同一個開關切換至或切換不同連接您小組的 Nic。In addition, you can connect your teamed NICs to the same switch or to different switches. 如果您將 Nic 連接至不同的參數,這兩個參數必須在相同的子網路上。If you connect NICs to different switches, both switches must be on the same subnet.

NIC 小組可用性NIC Teaming Availability

NIC 小組已在 Windows Server 2016 的所有版本。NIC Teaming is available in all versions of Windows Server 2016. 此外,您可以使用 Windows PowerShell 命令、遠端桌面與遠端伺服器管理工具來管理 NIC 小組的電腦正在執行的工具的支援 client 作業系統。In addition, you can use Windows PowerShell commands, Remote Desktop, and Remote Server Administration Tools to manage NIC Teaming from computers that are running a client operating system upon which the tools are supported.

適用於 NIC 小組的支援並不支援 NicSupported and Unsupported NICs for NIC Teaming

您可以使用任何乙太網路 NIC 已在 Windows Server 2016 NIC 小組通過(WHQL 測試)的 Windows 硬體資格和商標測試。You can use any Ethernet NIC that has passed the Windows Hardware Qualification and Logo test (WHQL tests) in a NIC Team in Windows Server 2016.

下列 Nic 無法放在 NIC 團隊。The following NICs cannot be placed in a NIC team.

  • HYPER-V Virtual 切換為 Nic 公開主機磁碟分割中的連接埠 HYPER-V virtual 網路介面卡。Hyper-V virtual network adapters that are Hyper-V Virtual Switch ports exposed as NICs in the host partition.

    重要

    HYPER-V virtual Nic 主機磁碟分割 (vNICs) 中公開必須不放在團隊。Hyper-V virtual NICs that are exposed in the host partition (vNICs) must not be placed in a team. 在 [所有設定] 或 [組合不支援小組的磁碟分割主機在 vNICs。Teaming of vNICs inside of the host partition is not supported in any configuration or combination. 嘗試小組 vNICs 網路問題發生,可能會導致完全遺失的通訊。Attempts to team vNICs might cause a complete loss of communication if network failures occur.

  • 核心偵錯網路介面卡 (KDNIC)。The kernel debug network adapter (KDNIC).

  • Nic 所使用的網路開機。NICs that are being used for network boot.

  • 使用技術乙太網路,例如 WWAN、WLAN 日 Wi ‑ Fi、藍牙、和 Infiniband,包括網際網路通訊協定 (IPoIB) Infiniband Nic 透過以外的 Nic。NICs that use technologies other than Ethernet, such as WWAN, WLAN/Wi-Fi, Bluetooth, and Infiniband, including Internet Protocol over Infiniband (IPoIB) NICs.

NIC 小組的相容性NIC Teaming Compatibility

NIC 小組適用於所有網路技術在 Windows Server 2016 例外如下。NIC teaming is compatible with all networking technologies in Windows Server 2016 with the following exceptions.

  • 單根 I/O 模擬 (SR IOV)Single-root I/O virtualization (SR-IOV). SR-IOV 的資料是直接傳送到而不需要它通過堆疊網路(以主機作業系統,在模擬)。For SR-IOV, data is delivered directly to the NIC without passing it through the networking stack (in the host operating system, in the case of virtualization). 因此,不可能 NIC 團隊車載或重新導向至其他路徑小組中的資料。Therefore, it is not possible for the NIC team to inspect or redirect the data to another path in the team.

  • 原生主機品質服務 (QoS)Native host Quality of Service (QoS). 當 QoS 原則設定在原生或主機系統和那些原則叫用頻寬下限限制時,會 NIC 團隊的整體輸送量小於就地頻寬原則不會。When QoS policies are set on a native or host system and those policies invoke minimum bandwidth limitations, the overall throughput for a NIC team will be less than it would be without the bandwidth policies in place.

  • TCP ChimneyTCP Chimney. 不支援 TCP Chimney NIC 小組因為 TCP Chimney 卸載整個網路堆疊直接 NICTCP Chimney is not supported with NIC teaming because TCP Chimney offloads the entire networking stack directly to the NIC.

  • 802.1 x 驗證802.1X Authentication. 802.1 不應該使用 X 驗證 NIC 小組的。802.1X Authentication should not be used with NIC Teaming. 有些參數不允許 802.1 X 驗證和 NIC 相同的連接埠的聯合的設定。Some switches do not permit the configuration of both 802.1X Authentication and NIC Teaming on the same port.

若要了解如何使用 NIC 小組中虛擬電腦 (Vm) HYPER-V 主機上執行,請查看NIC 小組中虛擬電腦與 #40;Vm 和 #41;.To learn about using NIC Teaming within virtual machines (VMs) that are running on a Hyper-V host, see NIC Teaming in Virtual Machines (VMs).

NIC 小組與一樣佇列 (VMQs)NIC Teaming and Virtual Machine Queues (VMQs)

VMQ 和 NIC 小組合作。應該支援 VMQ,隨時可以 HYPER-V。VMQ and NIC Teaming work well together; VMQ should be enabled anytime Hyper-V is enabled. 根據切換設定模式,載入 distribution 演算法 NIC 小組將會顯示 VMQ 功能 HYPER-V 開關切換至顯示佇列提供給支援小組(分鐘-佇列模式)中的任何介面卡佇列數最小的數字或總數佇列可用的所有團隊成員(的佇列總和-模式)。Depending on the switch configuration mode and the load distribution algorithm, NIC teaming will either present VMQ capabilities to the Hyper-V switch that show the number of queues available to be the smallest number of queues supported by any adapter in the team (Min-queues mode) or the total number of queues available across all team members (Sum-of-Queues mode).

具體而言,如果小組中切換獨立模式和載入 Distribution 的聯合設定為 [HYPER-V 連接埠模式或動態模式,則報告佇列數目的所有可用的小組成員(的佇列總和-模式); 佇列總和否則佇列回報的是最小數目佇列支援任何(分鐘-佇列模式)小組的成員。Specifically, if the team is in Switch-Independent teaming mode and the Load Distribution is set to Hyper-V Port mode or Dynamic mode, then the number of queues reported is the sum of all the queues available from the team members (Sum-of-Queues mode); otherwise the number of queues reported is the smallest number of queues supported by any member of the team (Min-Queues mode).

原因如下:Here's why:

  • HYPER-V 連接埠模式」或「動態模式開關切換至獨立小組時輸入的流量的 HYPER-V 切換連接埠 (VM) 將永遠抵達上相同的小組成員。When the switch independent team is in Hyper-V Port mode or Dynamic mode the inbound traffic for a Hyper-V switch port (VM) will always arrive on the same team member. 主機可預測日控制的成員會接收流量特定 vm 這樣可以在特定的小組成員配置哪些 VMQ 佇列有關更重視 NIC 小組。The host can predict/control which member will receive the traffic for a particular VM so NIC Teaming can be more thoughtful about which VMQ Queues to allocate on a particular team member. NIC 小組,使用 HYPER-V 切換,將 vm VMQ 設定一個小組成員,然後輸入的流量會叫用佇列。NIC Teaming, working with the Hyper-V switch, will set the VMQ for a VM on exactly one team member and know that inbound traffic will hit that queue.

  • 小組處於(靜態小組或 LACP 小組)任何切換相關模式小組已連接到切換控制輸入的流量分配。When the team is in any switch dependent mode (static teaming or LACP teaming), the switch that the team is connected to controls the inbound traffic distribution. 主機 NIC 小組的軟體不能預測的小組成員將會取得輸入的流量 VM 並有可能,開關切換至分散的資料傳輸 vm 所有小組的成員。The host's NIC Teaming software can't predict which team member will get the inbound traffic for a VM and it may be that the switch distributes the traffic for a VM across all team members. 為 NIC 小組軟體,使用 HYPER-V 開關切換至,會在每個小組成員 vm 程式佇列,而不只是其中一個小組成員。As a result the NIC Teaming software, working with the Hyper-V switch, programs a queue for the VM on every team member, not just one team member.

  • 當您切換獨立模式中的小組,並使用位址 hash 載入 distribution 演算法時,輸入的流量永遠進上所有的上一個小組成員一個 NIC(主要小組成員-)。When the team is in switch-independent mode and is using an address hash load distribution algorithm, the inbound traffic will always come in on one NIC (the primary team member) - all of it on just one team member. 因為它們取得的設計用輸入流量處理其他小組成員不相同佇列做為主要的成員,如果主要成員失敗任何其他團隊成員可以用來輸入流量挑選並佇列已經的地方。Since other team members aren't dealing with inbound traffic they get programmed with the same queues as the primary member so that if the primary member fails any other team member can be used to pick up the inbound traffic and the queues are already in place.

大多數 Nic 有可用於收到側邊縮放比例 (RSS) 或 VMQ,但不是能同時在此同時,佇列。Most NICs have queues that can be used for either Receive Side Scaling (RSS) or VMQ, but not both at the same time. 部分 VMQ 設定看起來似乎 RSS 佇列設定,但其實是設定 RSS 和 VMQ 使用根據的功能目前正在使用中的一般佇列。Some VMQ settings appear to be settings for RSS queues but are really settings on the generic queues that both RSS and VMQ use depending on which feature is presently in use. 每個 NIC 有中有進階屬性,值 * RssBaseProcNumber 和 *MaxRssProcessors。Each NIC has, in its advanced properties, values for *RssBaseProcNumber and *MaxRssProcessors. 以下是一些 VMQ 設定,以提供更好的系統效能。Following are a few VMQ settings that provide better system performance.

  • 每個 NIC 應該會有理想 * RssBaseProcNumber 為偶數字超過或等於兩個(2)。Ideally each NIC should have the *RssBaseProcNumber set to an even number greater than or equal to two (2). 這是因為的第一個實體處理器核心 0(邏輯處理器 0 和 1),通常會大部分的系統處理,因此應該會網路處理 steered 原位這個實體處理器。This is because the first physical processor, Core 0 (logical processors 0 and 1), typically does most of the system processing so the network processing should be steered away from this physical processor. (此電腦的基底處理器應大於或等於 1 讓某些電腦架構不需要兩個的邏輯處理器每個實體處理器。(Some machine architectures don't have two logical processors per physical processor so for such machines the base processor should be greater than or equal to 1. 如果有疑問取得您的主機使用每個實體處理器架構 2 邏輯處理器。)If in doubt assume your host is using a 2 logical processor per physical processor architecture.)

  • 如果小組的佇列總和-模式中的小組成員處理器應該,範圍實際,不重疊。If the team is in Sum-of-Queues mode the team members' processors should be, to the extent practical, non-overlapping. 例如的團隊的 2 10Gbps Nic 4 核心主機(8 邏輯處理器),您可以設定使用 2 的基底處理器並使用 4 核心; 的第一個第二個會設定為使用 [基本處理器 6 並使用 2 核心。For example, in a 4-core host (8 logical processors) with a team of 2 10Gbps NICs, you could set the first one to use base processor of 2 and to use 4 cores; the second would be set to use base processor 6 and use 2 cores.

  • 如果最小值-佇列模式中的小組所使用的小組成員處理器集必須是相同。If the team is in Min-Queues mode the processor sets used by the team members must be identical.

NIC 小組與 HYPER-V 網路模擬 (HNV)NIC Teaming and Hyper-V Network Virtualization (HNV)

NIC 小組已完全相容的 HYPER-V 網路模擬 (HNV)。NIC Teaming is fully compatible with Hyper-V Network Virtualization (HNV). HNV 管理系統提供的資訊,可將最適合 HNV 資料傳輸方式中的載入的聯合 NIC NIC 小組驅動程式。The HNV management system provides information to the NIC Teaming driver that allows NIC Teaming to distribute the load in a way that is optimized for the HNV traffic.

NIC 小組與即時移轉NIC Teaming and Live Migration

NIC 小組,在 Vm 中不會影響 Live 移轉。NIC Teaming in VMs does not affect Live Migration. Live 移轉 NIC 小組已在 VM 中有相同的規則。The same rules exist for Live Migration whether or not NIC Teaming is configured in the VM.

也了See Also

NIC 小組中虛擬電腦與 #40;Vm 和 #41;NIC Teaming in Virtual Machines (VMs)