Hi, I scanned the forum for HyperV and the search showed nothing. I need some help. We are using a Mikrotik for our LAB and the challenge is to setup to HyperV servers to host VMs. One NIC on each server will be a “Virtual Switch” for the VMs and on Cisco you configure the relevant ports for 802.1Q (http://blogs.msdn.com/b/adamfazio/archive/2008/11/14/understanding-hyper-v-vlans.aspx)
The problem here is understanding my Mikrotik.
Test One:
Configure bridge “br-hyperv”
Add ether11,ether12 as ports to the bridge (had to remove slave and set master to none)
The manuals let me believe that ether11 and ether12 will now forward traffic between them and this is not happening as expected, because I notice the VLAN-ID=0 and not vlan11 or any other TAG.
Example setup:
/interface bridge add name=br-hyperv protocol-mode=rstp
/interface bridge port add interface=ether11 bridge=br-hyperv
/interface bridge port add interface=ether11 bridge=br-hyperv
Problem: VMs on one server cannot ping VMs on the other server.
Note: Adding vlan interfaces for the IP addresses to route out to the Internet is coming. I just wanted to see if I can get one server’s v-switch to “trunk” through to the other server’s v-switch.
If someone has a basic setup for HyperV or ESX, then please share
Hyper-V does not work with the current ROS 6.xx software.
I do think we have to wait for 7.x because this version maybe is based on Linux kernel 3.4 or higher.
Starting with 3.4 Linux kernel there are native Hyper-V virtual device drivers included. Specially for networking you need those.
I read the TOS6.xx software doesn’t work. In my case I have a rack mounted Cloud Switch. I am not installing anything into a VM. If I don’t TAG the VM Nic, then everything works. Like a normal access port. The trouble starts when I TAG a VM Nic.
Are you saying that my device cannot used to connect a physical server to the network if we need to TAG VLANs? Example:
Internet ↔ MT-RB1 <-physical cable-> HV-server with physical NIC ↔ VSwitch ↔ Virtual network <->VM.
As long as I have one NIC per VLAN (one Ethernet interface per vlan), I can get this to work, but this isn’t a solution. I need to trunk multiple VLANs over a single interface.
Some feedback regarding HyperV and my setup with a Cloud Switch RouterBOARD.
This started as a normal network configuration exercise and turned out to be a nightmare. The problem was two fold:
The manuals and literature available on Mikrotik doesn’t categorise advice or information between running an OS and using hardware with an OS and Switch. Too much is available on using bridges, which only keeps the CPU running high. Very little is available on using the switch and ignoring bridges. To me speed is important and the switch capability delivers speed.
Secondly I had a network card for my POC testing, using desktops, an Inte(R) PRO/100GT Desktop Adapter, which if placed on a VLAN in a custom switch group - refused to see the default gateway on that VLAN. This I only realised two weeks later, after reading everything I could find about VLANs on Mikrotik.
So? This is working:
Use network cards that work on Mikrotik It seems that you may find one that has its own mind.
On Server 2012 - the NIC for HyperV VMs
a. Create a Team - even if you place one NIC in the team.
b. Don’t share that team with the host
c. In HyperV - create a VSwitch and tie it to the team
d. Set your VLAN on the VM Nic in the HyperV settings
On server 2012 - the NIC for managing the host
a. Set it up as a normal server NIC. IP address and so on. Nothing special
b. Don’t use this one in HyperV for anything - it is there to get to the host
In Mikrotik setup
a. Configure your “switch” - VLAN
i. VLAN - create vlan ID and link it to all the valid ports - including master and switch-cpu
ii. VLAN Tagging - tag the ports going out to HyperV master and switch-cpu. Don’t tag any access port if you need one.
iii. In. VLAN Tran. - here you only create ingress rules for edge ports (access ports). No ingress rule for any “vlan trunk”
b. Configure “switch” - Settings.
i. Drop if Invalid VLAN On ports. Add the master for the group and all the ports in that group
c. Configure Switch - Ports
i. Confirm you have network ports and "egress VLAM Mode “unmodified” seems to work.
d. On Interfaces and IP addresses
i. Create your vlan interfaces and attach them to the master port for the HyperV switch group.
ii. Place an IP address on each vlan interface
What you now have is a vlan trunk to hyperV VSwitch on which you can tag vlans and run workloads. No Bridges and Ports required in the bridges. Everything happening at fast wire speed connectivity.
I don’t know if it is supposed to work this way, but the vlans work. I do see however that the FDBs for the traffic show the VLAN ID for the Trunk. A network trace on each VM shows that they only see the traffic in their network. Tagging a VM and using the wrong IP address doesn’t allow the VM to communicate at all. You need to Tag the VM correctly and use the correct IP address in the VM for the network.
It seems that you may find one that has its own mind.