NIC teaming is a valuable feature for creating redundant NIC connections to critical resources.
When it comes to configuring a Hyper-V cluster utilizing individual nodes with connection to a SAN or SANs having no single point of failure is critical.
With the advent of v15 of Intel’s PROSet we can now create the needed NIC teams to allow for redundancy for the various Hyper-V host network connections.
- Intel Support: Network Connectivity: How do I configure advanced features in Windows Server 2008* core installations?
Intel Modular Server
When it comes to the Intel Modular Server network configuration for a Hyper-V cluster we will need to make a few structural changes to our initial NIC set up as we did not have teaming available to us then.
This is a screenshot of the IMS rear from Modular Server Control:
For each node configured in the cluster we will need to team a pair of NICs with each NIC in the pair connected to a separate switch module.
- Hyper-V Node
- Team 1
- NIC 0 (SWM 1)
- NIC 0 (SWM 2)
- Team 2
- NIC 1 (SWM 1)
- NIC 1 (SWM 2)
Once we had our two teams set up we would configure things using the Intel PROSet utility as follows:
- Team 1
- Management IP – Default VLAN
- Heartbeat IP – Create and set VLAN 99
- Team 2
- Bind Hyper-V vSwitch with no host access.
Finally, once we had all of our configuration steps above completed, we would set the correct NIC binding order:
- Blog How To: NIC Binding Order On Server Core or Hyper-V Server 2008 RTM/R2
- Blog: NIC Binding Order On Server Core – Error 0x000013AB – A cluster network is not available for this operation
- This post has the correct binding order posted.
Once we have run through the configuration steps a few times, if necessary we will post a how-to step-by-step here.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book