HP NIC network teaming under Windows Server 2012 R2
I am in the process of migrating server from Windows Server 2008 to 2012 R2 and I note that the HP NIC teaming configuration utility is no longer supported and that the OS's own NIC teaming software should be used.
Under the HP software, 2 cards were configured against separate switches and set for Network Fault Tolerance only. All inbound and outbound traffic was there received on one card only, which is critical for the network-sensitive software I am running.
This worked fine until the upgrade to Windows 2012 R2. We are now using a configuration of 'Switch Independent | Dynamic', which does not appear to a like-for-like configuration compared to the old HP NFT only setup.
The question is have I selected the correct configuration under Windows 2012 R2 or is there an alternative that fully replicates the HP NFT setup?
Under the HP software, 2 cards were configured against separate switches and set for Network Fault Tolerance only. All inbound and outbound traffic was there received on one card only, which is critical for the network-sensitive software I am running.
This worked fine until the upgrade to Windows 2012 R2. We are now using a configuration of 'Switch Independent | Dynamic', which does not appear to a like-for-like configuration compared to the old HP NFT only setup.
The question is have I selected the correct configuration under Windows 2012 R2 or is there an alternative that fully replicates the HP NFT setup?
strivoli
I have faced same issue and ended up using OS's NIC Teaming. I used to love HP's Teaming feature but it seams they have given up as long as MS started pushing OS's Teaming.
Windows 2012 R2 EOL is October 2023, so IMHO you ought to be planning to get off 2012 R2, not on 2012 R2.
Switch independent teaming provides fault tolerance. You can specify 1 NIC as primary and the other as secondary. That to me matches what you have under 2008 R2.
Switch independent teaming provides fault tolerance. You can specify 1 NIC as primary and the other as secondary. That to me matches what you have under 2008 R2.
ASKER
I will look at the configuration again but I am sure I was still seeing packets being presented to the secondary NIC but not being processed.
The HP NFT configuration was a case of everything to the primary card and no activity at all on the secondary card.
I'll post anything I find.
The HP NFT configuration was a case of everything to the primary card and no activity at all on the secondary card.
I'll post anything I find.
ASKER
I think key to the issue here is that OS teaming uses LBFO, so load balancing is used whatever the configuration.]
There's no option for fault tolerance only.
There's no option for fault tolerance only.
LBFO is the way in 2012 R2 leaving the default algorithm for the team hosting production/management.
HyperVPorts is the algorithm to use for the team hosting the dedicated virtual switch.
If the ports are Broadcom Gigabit then make sure to disable Virtual Machine Queues for _all_ physical ports in the two teams (assuming 4 ports).
Make sure to use all ports.
I have two very thorough EE articles on all things Hyper-V:
Some Hyper-V Hardware and Software Best Practices
Practical Hyper-V Performance Expectations
Some PowerShell Guides:
PowerShell Paradise: Installing & Configuring Visual Studio Code (VS Code) & Git
PowerShell Guide - Standalone Hyper-V Server
PowerShell Guide - New VM PowerShell
PowerShell Guide - New-VM Template: Single VHDX File
PowerShell Guide - New-VM Template: Dual VHDX Files
Here are some focused articles:
Set up PDCe NTP Domain Time in a Virtualized Setting
Slipstream Updates Using DISM and OSCDImg
Protecting a Backup Repository from Malware and Ransomware
Disaster Preparedness: KVM/IP + USB Flash = Recovery. Here’s a Guide
HyperVPorts is the algorithm to use for the team hosting the dedicated virtual switch.
If the ports are Broadcom Gigabit then make sure to disable Virtual Machine Queues for _all_ physical ports in the two teams (assuming 4 ports).
Make sure to use all ports.
I have two very thorough EE articles on all things Hyper-V:
Some Hyper-V Hardware and Software Best Practices
Practical Hyper-V Performance Expectations
Some PowerShell Guides:
PowerShell Paradise: Installing & Configuring Visual Studio Code (VS Code) & Git
PowerShell Guide - Standalone Hyper-V Server
PowerShell Guide - New VM PowerShell
PowerShell Guide - New-VM Template: Single VHDX File
PowerShell Guide - New-VM Template: Dual VHDX Files
Here are some focused articles:
Set up PDCe NTP Domain Time in a Virtualized Setting
Slipstream Updates Using DISM and OSCDImg
Protecting a Backup Repository from Malware and Ransomware
Disaster Preparedness: KVM/IP + USB Flash = Recovery. Here’s a Guide
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.