Solved

Connecting two physical Hyper-V servers together without seeing production network.

Posted on 2013-06-25
1
484 Views
Last Modified: 2014-11-12
I'm looking to run a test domain on a separate subnet, so only the VM servers can see each other, and not see any other network.

I currently have 2 servers. Both running Windows Server 2012 DataCenter and both have Hyper-V Manager installed.  

I have images of my DC and exchange server. I also created a fresh VM w/ Windows Server 2012(will use for exchange 2010 test migration)
 
Each Server has 1 NIC plugged into the production lan. I have the Hyper-V Virtual switch as external. Once I boot a server up in VM, I can set each one static and they see each other. but if I let dhcp takeover, the server try and move over to the production LAN. I currently don't have any VLANs configured on my physical switches, so I haven't enabled anything on the VM servers.  how do i get the VM servers to default to the test domain? It seems if I use internal/private virtual switches, the VM on each physical server end up losing connectivity between each other.

Each server has 4 physical NICS, so i did try and setup a 2nd physical NIC w/ a static ip of the VM network, but i still couldn't get the VM serves to stay on the VM network.

What's the best way to set this up?

production network:
192.168.0.1
255.255.248.0

VM network:
192.168.100.1
255.255.255.0
0
Comment
Question by:AfternoonShift
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 

Accepted Solution

by:
pchindustries earned 500 total points
ID: 39277247
You have a couple of options.

The simplest option is to create a VLAN on your production switch to segment traffic from your production LAN. If this is not possible then you must create a new virtual switch (leave the current production virtual switch unchanged) on each Hyper-V host and connect that virtual switch to one of your physical nics that is not in use by the production LAN. You then must connect the the NICs for your new virtual switch together by using a crossover cable or a switch that is totally separate from your production switches. Once you do this, connect your VMs to the new virtual switch and they will all be able to see each other.
0

Featured Post

Space-Age Communications Transitions to DevOps

ViaSat, a global provider of satellite and wireless communications, securely connects businesses, governments, and organizations to the Internet. Learn how ViaSat’s Network Solutions Engineer, drove the transition from a traditional network support to a DevOps-centric model.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The following article is comprised of the pearls we have garnered deploying virtualization solutions since Virtual Server 2005 and subsequent 2008 RTM+ Hyper-V in standalone and clustered environments.
Will try to explain how to use the VMware feature TAGs in the VMs and create Veeam Backup Jobs using TAGs. Since this article is too long, I will create second article for the Veeam tasks.
In this Micro Tutorial viewers will learn how to use Boot Corrector from Paragon Rescue Kit Free to identify and fix the boot problems of Windows 7/8/2012R2 etc. As an example is used Windows 2012R2 which lost its active partition flag (often happen…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question