We need at least three NICs to get our cluster up and running. As we understand things, the cluster can be configured on a 2 NIC setup, but this is not optimal.
- NIC 1: Internal IP address for management.
- NIC 2: Cluster communication.
- NIC 3+: Dedicated to VMs.
Here are some screenshots of our configuration.
Gigabit Ethernet Switch Module 1:
Note that VLAN designated 99 will be for cluster communication and remain internal only (TBD). We still are not 100% clear on whether we need a physical switch for this part yet.
Ethernet Ports 1 through 10, which are the external ports, are mapped to VLAN 1. The management and VM NICs 2 through 4 are mapped to them.
Gigabit Ethernet Switch 2:
All available internal ports for NICs 3 and 4 are mapped to the external ports.
Now, the Hyper-V Server 2008 R2 OS has not necessarily picked up the NIC mapping as we would expect:
Note that Node 3 has not had the cluster subnet assigned to it yet as the IP is still 169.254.96.93.
Once we have all of the IPs in place, we will domain join the three Nodes.
From there, we have the Failover Cluster Management (TechNet article on Server 2008 clustering A+) feature installed on the separate 1U that we will use to run the Validate a Configuration Wizard.
Then we will hopefully discover where in our configuration we are lacking the proper configuration structures.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book