My Setup with Windows 2012 Hyper-V Virtual Switch of a NIC Team - Correct?
-
Thursday, December 06, 2012 3:28 PM
Hey Guys,
Got a few general questions about my setup and wondering if I did this right. I have a HP Proliant DL360 G7 with 4 NICs running Windows 2012. This server is a hypervisor for two VMs running Win 2008 R2.
I was really excited about trying out NIC Teaming so I created a team called "NicTeam" that uses NIC 1, 2 and 3. The "NicTeam" is assigned Hyper-V Port for Load balancing mode. I left NIC 4 out of the team and it is dedicated to the server itself with a static IP. After "NicTeam" was created, I went ahead and created a Hyper-V virtual Switch called "Hyper-V Team" and selected "NicTeam" as an external physical connection.
I imported my two VMs running Win 2008 R2 and assigned them both to use the same "Hyper-V Team" virtual switch. Started up the VMs and they seem to be running well. Each of the VMs have their own static ips and network performance was as good as before.
The only thing that bothers me is the virtual "Hyper-V Team" switch. It is set right now with dhcp and grabbed some random IP. So looking at my network connections on this Windows 2012 server, I see the static IP I assigned for the server on NIC 4 and a random IP assigned to the virtual switch. Back with my old 2008 R2 hypervisor server, the virtual switches did not have an IP assigned and was actually listed as disabled under network configuration.
So how is my setup? Did I do something wrong? I would love to get rid of the random dhcp ip for the virtual switch.
George
All Replies
-
Friday, December 07, 2012 4:15 PManyone?
-
Friday, December 07, 2012 4:34 PM That does seem correct. In 2012 it looks like the virtual switch will have to be assigned an IP. You should see an enabled adapter (your physical NIC) with the only option enabled as Hyper-V Virtual switch. The virtual switch adapter that is created along with the switch will have all the usual tcp/ip settings, etc enabled. You should be able to set the adapter to a static IP if you want, but it has to have some IP address.
- Proposed As Answer by Jeremy_WuMicrosoft Contingent Staff, Moderator Monday, December 10, 2012 2:09 AM
- Marked As Answer by Jeremy_WuMicrosoft Contingent Staff, Moderator Tuesday, December 11, 2012 5:23 PM
-
Sunday, December 09, 2012 5:26 PMModerator
Hi,
I agree with Dr_Bartholomew_Cheesecake_Esq, your configuration seems correct. And, based on my understanding, the "Hyper-V Team" virtual switch should be assigned an IP address within the same IP range of your NIC 4. In addition, you can also assign static IP configuration with the same IP range. In brief, the "Hyper-V Team" virtual switch has the same basic TCP/IP function of your NIC 4 to your Windows Server 2012.
More information:Hyper-V Virtual Switch Overview
Hope this helps.
Jeremy Wu
TechNet Community Support
- Edited by Jeremy_WuMicrosoft Contingent Staff, Moderator Sunday, December 09, 2012 5:27 PM
- Proposed As Answer by Jeremy_WuMicrosoft Contingent Staff, Moderator Monday, December 10, 2012 2:09 AM
- Marked As Answer by Jeremy_WuMicrosoft Contingent Staff, Moderator Tuesday, December 11, 2012 5:23 PM
.png)
