Quantcast
Channel: Hyper-V forum
Viewing all articles
Browse latest Browse all 8743

VLAN Tagging

$
0
0

I have a 3 node hyper-v setup in cluster on Windows 2012 R2.

My network team created 5 VLANs for each of the network traffic types for this implementation.

We have a dedicated NIC for each traffic type.

I found out that the Network team setup the Switches to do untagged traffic since they have each port setup for only 1 VLAN.

What I discovered is that when I create the external switch on the VM prod NIC and create a VM on it, it works fine so long as I leave the VLAN off on the vNIC in the VM. Once I put the VLAN number on it, I lose connectivity.

So the question is, do I need the VLAN tag on or not? What is Hyper-V Requirement around VLANs.

I am basically just extending our corporate network with our VM machines, they will all have access to all corporate network resources.

Should I request the network team to change the VLAN model on the switch or is it ok to leave as is and leave vlan blank on production VM NIC, live migration NIC, cluster NIC.

All this networking stuff is very new to me so everyday I am learning something new.


Nick


Viewing all articles
Browse latest Browse all 8743

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>