1 Hyper-V server, 2 NICs, 3 VMs, 2 different subnets

Hello to all

- Hyper-V server Windows 2012 R2 which has 2 NICs installed
- 3 VMs are also up and running

The question is,
Can we connect the 2 VMs and the physical machine to one subnet and the 3rd VM to a different subnet?

If the answer is positive, please point me to the right direction
LVL 13
AlexiosAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Anand PandyaCommented:
As per me yes, you can do it and you need to create a vlan.
You can go through below links:
http://social.technet.microsoft.com/wiki/contents/articles/1306.hyper-v-configure-vlans-and-vlan-tagging.aspx
http://www.aidanfinn.com/?p=10164

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Separate subnet is via separate switch or VLAN?
AlexiosAuthor Commented:
Yes Philip it is via a seperate switch, for DMZ.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Okay, I suggest plugging in an Intel i350-T2 NIC, creating a team on that NIC, then a dedicated vSwitch, and finally plugging it in to the dedicated switch.

From there you can bind the required vSwitch to the VMs.

We usually have two dual or quad port NICs installed. We then team across physical NICs to create some redundancy. That's what we'd do here.
AlexiosAuthor Commented:
Thank you Philip for your detailed answer but the thing is that the solution has to be found without extra modules, only with the two NICs that already exist.

I will try Anand's solution to check if it's do-able
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Remove the existing vSwitch from VMs.
Delete vSwitch.
Delete team if exists.
Create vSwitch 0 on Port 0
Create vSwitch 1 on Port 1
Bind production network VMs to vSwitch 0 and keep that port connected to production.
Bind separate subnet vSwitch 1 to VMs requiring and plug port into separate switch.
Done.
AlexiosAuthor Commented:
Sorry for the delay guys but still haven't tried it.
I will come back to you as soon as I do
AlexiosAuthor Commented:
I never tried it.

Thank you for your help
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.