Our previous post on setting up an adapter team:
Once our adapter teams are created the next step for us is to create a dedicated VLAN for our Heartbeat network.
In this case we will have two adapter teams created:
- NIC 0 Switch 1
- NIC 0 Switch 2
- NIC 1 Switch 1
- NIC 1 Switch 2
The above team names are what we are working with on our Intel Modular Server at this point.
So, we need to know what the index number is for each team:
- PROSetCL Team_Enumerate
Now that we know our index numbers, we can go ahead and create the two needed VLANs:
- PROSetCL Team_CreateVLAN 2 untagged Management
- PROSetCL Team_CreateVLAN 2 99 Heartbeat
- PROSetCL Team_EnumerateVLANS 2
The “untagged” VLAN will remain connected to our management network. VLAN 99 will be our exclusive heartbeat network.
Now, in our Hyper-V Server 2008 R2 “console” we can see that we do indeed have 3 NICs to work with:
We will then go ahead and set our heartbeat subnet and bind the Hyper-V virtual switch to the vSwitch team.
Now that our teaming has been configured our node is ready to become a part of our cluster!
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book