dcsimg
Read more on "Server Virtualization Spotlight" »

Hyper-V Network Virtual Switch Q&As Page 2

By Nirmal Sharma (Send Email)
Posted September 9, 2013


Hyper-V Network Virtual Switch Q&As

Here are a few questions/answers to help clear up any potential confusion:

Q1: Can VM1 and VM2 communicate with each other?

A1: Yes, they can, as long as they are using the same VLAN ID and the Hyper-V virtual switch is also configured with the same VLAN ID (Access Mode) or configured in the Trunk Mode.

Q2: Can VM3 communicate with VM1 or VM2?

A2: No. VM3 is configured with a VLAN ID 5, but the virtual switch (vSwitch1) can only accept network packets that are tagged with VLAN ID 4. So, to allow communication between all virtual machines (VM1, VM2 and VM3 in this example), vSwitch1 must be configured in the Trunk Mode. In other words, you must uncheck the "Enable VLAN identification for management operating system" setting.

Q3: How can we restrict communication between VM1 and VM3 and at the same time allow VM2 to communicate with a server on an external LAN?

A3: To restrict communication between VM1 and VM3, you must configure VM1 and VM3 with the same VLAN ID and then configure vSwitch1 in Trunk Mode. This configuration will force vSwitch1 to receive all network packets from all the virtual machines connected to it.


Nirmal Sharma is a MCSEx3, MCITP and Microsoft MVP in Directory Services. He has specialized in Microsoft Technologies since 1994 and has followed the progression of Microsoft Operating System and software. In his spare time, he likes to help others and share some of his knowledge by writing tips and articles on various sites and contributing to Solution IDs for www.Dynamic-SpotAction.com. Nirmal can be reached at nirmal_sharma@mvps.org.

Follow ServerWatch on Twitter and on Facebook

Page 2 of 2

Read more on "Server Virtualization Spotlight" »

Comment and Contribute

Your name/nickname

Your email

(Maximum characters: 1200). You have characters left.