Hyper-V 2012 r2 - TEAMING - VLANS

Nandoskid

Junior Member
Apr 2, 2015
7
0
16
Problem is i can't get any network connectivity to my VM's. I have just recently done the setup, and here are some steps/feedback I have to help you help me :)

1. I have three NICs. x2 Intels and x1 Realtek.
2. I am using the Realtek on its own so i can have un-interrupted connection to the host.
3. I take the two Intel NICs (Ethernet2 and Ethernet3 for this example) and team them up through "NIC Teaming" window calling the new combine NIC as EtherTeam1. I am using LACP and Dynamic.

MORE INFO ON SETUP: So i want to run 4 vlans, that being 101,102,103 and 104, where VLAN 101 is my server/switch subnet, and the other VLANS are there for testing.

4. I go into "NIC Teaming >> TEAMS >> TEAM INTERFACES" and double click on EtherTeam1 and confirm no VLAN is set as my switch port has 101 as Untagged and 102,103,104 as tagged. I also see that the combined NIC EtherTeam1 on Server Manager is now getting an IP as well as the Realtek.

This is where things start to go down hill.

5. I go to "Hyper-V Manager >> Virtual Switch Manager" and create a new virtual switch called "vSwitch-v101", and in the settings for this switch i make it EXTERNAL, select MICROSOFT NETWORK ADAPTER MULTIPLEXOR DRIVER and tick ALLOW MANAGEMENT OPERATING SYSTEM TO SHARE THIS NETWORK ADAPTOR", and when i click apply and OK, the result i notice is a loss of network connectivity to EtherTeam1 aswell as it getting a 169.x.c.v address and the CMDLET "get-netlbfoteam" command shows the EtherTeam1 as being Status=Down.

Even if i setup VM, and select NIC as "vSwitch-v101", the vm says no network connectivity.

Any ways i hope someone can give me some help or pointers.
 

fleshconsumed

Diamond Member
Feb 21, 2002
6,486
2,363
136
I don't know if this is going to help you or not, but when I was playing with Hyper-V, I had to create Virtual Switch before adding Network Adapter to Virtual Machine. Originally I created VM first, then created Virtual Switch, then pointed VM to the Virtual Switch. Well, apparently VM does not really like that. I ended up having to delete Network Adapter from Virtual Machine, and adding it again while pointing to an already existing Virtual Switch to make it all work. So try making sure Virtual Switch is all setup and working, then delete Ethernet Adapter from the Virtual Machine, and then add it again and point it to your Virtual Switch.
 

Nandoskid

Junior Member
Apr 2, 2015
7
0
16
Hi fleshconsumed and thank you for your reply. I think you misunderstood me, so i will repeat a portion of my comments again as I failed to mention my NAS is on the same subnet which is my isci drive and provides the space where i store my vm's. Here goes:

1. My vm host has the following main NIC of 10.10.10.19 (which is a result of combining the two Intel nics into a LACP Dynamic team)
2. I connect my VM Host to my iscsi drive at 10.10.10.10, and all is well.
3. I then go to make my virtual switch which will connect the VM's to the host adapter. At this point, when i make the vSwitch, i lose all connection to my VM Host Nic. In other words, 10.10.10.19 becomes 169.a.b.c and my iscsi drive fails as it cant reach 10.10.10.10.

So I am not even getting a chance to make a vm, or remake one as the VMHOST can not connect to the iscsi service and load the S: which has all the vhd's etc.
 

imagoon

Diamond Member
Feb 19, 2003
5,199
0
0
Do you have the (physical) switch config you are using? Sounds a lot like you have don't have trunking configured correctly among some other things.

Also iSCSI over LACP -> bad mojo
 

Nandoskid

Junior Member
Apr 2, 2015
7
0
16
Do you have the (physical) switch config you are using? Sounds a lot like you have don't have trunking configured correctly among some other things.

Also iSCSI over LACP -> bad mojo

I can't give you the switch config as it is not a CLI switch ... I have HP 1810-24G. I kinda know what i am doing form the switch point of view because i previously had ESXi working, but I can explain what I have done though as I need help :)

I have ports 15 and 16, and under TRUNKS>>TRUNK CONFIGURATION I have made a Team Name of HypV01, and assigned the two ports to it with settings of LACP and Dynamic. I then go to VLANS>>PARTICIPATION/TAGGING, and all the stuff is already setup there as the config is pre-existing from the esxi setup, where v101,102,103,104 are TAGGED. The only alteration I have done is change v101 from TAG to UNTAG and tried that combination as well.

I have done this setup ages ago, and it worked, but it definitely was with different hardware AND I am not sure if it was Hyper-v 2012 or 2012 r2.

Just confirm one thing if you can, all the basic configuration to get things running in a basic level can be done on the GUI correct? Right now I am tryin to read up on setting this up with CMDLETS, to see if there is something extra needed to be done. In about 6 hours or so time if i have no luck i will try installing Hyper-V 2012.



Oh and regarding this comment "Also iSCSI over LACP -> bad mojo" I know it is good to have two NICs, one for san connection and another for main network, but this is my lab and i dont have resources :)
 
Last edited:

Nandoskid

Junior Member
Apr 2, 2015
7
0
16
ATTENTION FORUM ADMINS: Why did this get moved to networking? The core problem is Hyper-V, hence why i applied it to OS's group. If i new my network was an issue I'd paste it in the networking section myself. I can confirm my network is not an issue because my ESXi host server works beautifully when connected to the same ports on the switch, hence why i ruled it out as being a network issue. Please move it back to an OS's related issue, or something more specific to Hyper-V.
 

imagoon

Diamond Member
Feb 19, 2003
5,199
0
0
I can't give you the switch config as it is not a CLI switch ... I have HP 1810-24G. I kinda know what i am doing form the switch point of view because i previously had ESXi working, but I can explain what I have done though as I need help :)

I have ports 15 and 16, and under TRUNKS>>TRUNK CONFIGURATION I have made a Team Name of HypV01, and assigned the two ports to it with settings of LACP and Dynamic. I then go to VLANS>>PARTICIPATION/TAGGING, and all the stuff is already setup there as the config is pre-existing from the esxi setup, where v101,102,103,104 are TAGGED. The only alteration I have done is change v101 from TAG to UNTAG and tried that combination as well.

I have done this setup ages ago, and it worked, but it definitely was with different hardware AND I am not sure if it was Hyper-v 2012 or 2012 r2.

Just confirm one thing if you can, all the basic configuration to get things running in a basic level can be done on the GUI correct? Right now I am tryin to read up on setting this up with CMDLETS, to see if there is something extra needed to be done. In about 6 hours or so time if i have no luck i will try installing Hyper-V 2012.



Oh and regarding this comment "Also iSCSI over LACP -> bad mojo" I know it is good to have two NICs, one for san connection and another for main network, but this is my lab and i dont have resources :)

Fair enough. I wasn't sure it was a lab so I wanted to mention it since it is one of the "classic mistakes" I see in many implementations when later on we are troubleshooting loss of of path issues and performance issues. In labs this isn't relevant.

Also since you verified that the config works with ESXi I would generally agree that the network is working at least on the switch side. I haven't done anything with 2012R2 bonding and vlans since everything I do with it is virtual at the moment so I would deffer that to someone else.

As for the networking thing.... it is the same reason all the NAS / SAN posts end up in here. No one really knows what a network does it seems at times so they think "hey it has an IP and RJ45 port so its a networking issue!"
 
Dec 16, 2009
32
0
0
By chance, have you tried configuring the switch ports as normal trunk ports (no untagged vlans except vlan 1) and setting the Win2012R2 team mode to switch independent? You will loose network connectivity from the time that the team is created until you create a vswitch with the correct management vlan. Once the vswitch is created with the management vlan checked, you should get network connectivity again.

That should help tell you whether it's a problem with LACP negotiation or a problem with your NIC drivers.