疑難排解 NIC 小組Troubleshooting NIC Teaming

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

本主題提供資訊疑難排解 NIC 小組,並包含下列區段,描述問題 NIC 小組的可能原因。This topic provides information about troubleshooting NIC Teaming, and contains the following sections, which describe possible causes of issues with NIC Teaming.

硬體不符合規格Hardware that doesn't conform to specification

當規格標準通訊協定實作硬體不符合時,可能會影響 NIC 小組效能。When hardware implementations of standard protocols do not conform to specification, NIC Teaming performance might be affected.

在正常運作,NIC 小組可能會傳送封包從相同的 IP 位址,但有多個不同的來源媒體存取控制 (MAC) 位址。During normal operation, NIC Teaming may send packets from the same IP address, yet with multiple different source media access control (MAC) addresses. 通訊協定標準,根據這些封包接收器必須解析的主機或 VM 的 IP 位址特定的 MAC 位址,而非回應的 MAC 地址,收到一封包。According to protocol standards, the receivers of these packets must resolve the IP address of the host or VM to a specific MAC address rather than responding to the MAC address from which the packet was received. 戶端正確實作地址解析度通訊協定的 IPv4 位址解析度通訊協定 (ARP) 或 IPv6 的鄰居探索通訊協定 (NDP),將會傳送具有正確的目的地的 MAC 位址(VM 或主機的擁有該 IP 位址的 MAC 位址)封包。Clients that correctly implement the address resolution protocols, IPv4's Address Resolution Protocol (ARP) or IPv6's neighbor discovery protocol (NDP), will send packets with the correct destination MAC address (the MAC address of the VM or host that owns that IP address).

不過,有些 embedded 硬體不正確實作的地址解析度通訊協定,並也可能會不明確 IP 位址解析使用 ARP 或 NDP 的 MAC 位址。Some embedded hardware, however, does not correctly implement the address resolution protocols, and also might not explicitly resolve an IP address to a MAC address using ARP or NDP. 存放裝置區域網路(舊)控制器,是裝置的這種方式可以執行的範例。A storage area network (SAN) controller is an example of a device that might perform in this manner. 非符合裝置中收到的封包複製來源所包含的 MAC 位址,並使用它做目的地的相對應的輸出封包 MAC 位址。Non-conforming devices copy the source MAC address that is contained in a received packet and use that as the destination MAC address in the corresponding outgoing packets.

這會傳送到錯誤目的地的 MAC 位址封包。This results in packets being sent to the wrong destination MAC address. 因此,封包所中斷 HYPER-V Virtual 開關切換至因為它們不符合所有已知的目的地。Because of this, the packets are dropped by the Hyper-V Virtual Switch because they don't match any known destination.

如果您有無法連接到舊控制器或其他 embedded 硬體,您應該需要封包擷取判斷是否硬體正確實作 ARP 或 NDP,並連絡您的硬體製造商以尋求支援。If you are having trouble connecting to SAN controllers or other embedded hardware, you should take packet captures and determine whether your hardware is correctly implementing ARP or NDP, and contact your hardware vendor for support.

實體切換安全性功能Physical switch security features

根據設定,NIC 小組可能會傳送封包從相同的 IP 位址的數個不同的來源 MAC 地址。Depending on configuration, NIC Teaming may send packets from the same IP address with multiple different source MAC addresses. 這可以成為了安全性使動態 ARP 檢查或 IP 來源例如實體開關切換至上的功能,尤其是實體切換並不知道的連接埠是小組的成員。This can trip up security features on the physical switch such as dynamic ARP inspection or IP source guard, especially if the physical switch is not aware that the ports are part of a team. 這種情形您設定切換獨立模式中的 [NIC 小組。This can occur if you configure NIC Teaming in Switch Independent mode. 您應該會檢查切換登判斷是否切換安全性功能會造成連接 NIC 小組的問題。You should inspect the switch logs to determine whether switch security features are causing connectivity problems with NIC Teaming.

停用,並讓網路介面卡,使用 Windows PowerShellDisabling and enabling network adapters by using Windows PowerShell

失敗 NIC 小組的一個常見原因是在小組介面停用。A common reason for a NIC Team to fail is that the team interface is disabled. 很多時候,介面會意外停用,執行下列命令 Windows PowerShell 順序時:In many cases, the interface is disabled by accident when the following Windows PowerShell sequence of commands is run:

Disable-NetAdapter *  
Enable-NetAdapter *  

這一系列命令不讓所有停用它 NetAdapters。This sequence of commands does not enable all of the NetAdapters that it disabled.

這是因為停用所有的基礎實體成員 Nic 會導致介面移除,且不會再出現在 Get-NetAdapter NIC 小組。This is because disabling all of the underlying physical member NICs causes the NIC team interface to be removed and no longer show up in Get-NetAdapter. 因此,讓-NetAdapter \ ***命令無法讓 NIC 團隊,因為的介面卡,會被移除。Because of this, the **Enable-NetAdapter \* command does not enable the NIC Team, because that adapter is removed.

讓-NetAdapter \ ***命令,但可以讓成員 Nic,然後(片刻)會重新建立小組介面。The **Enable-NetAdapter \* command does, however, enable the member NICs, which then (after a short time) causes the team interface to be recreated. 在這個情況,小組介面仍會在」已停用「狀態因為它未重新讓。In this circumstance, the team interface is still in a "disabled" state because it has not been re-enabled. 之後,它會重新建立讓小組介面,可讓開始重新排列網路流量。Enabling the team interface after it is recreated will allow network traffic to begin to flow again.

也了See Also

NIC 小組NIC Teaming