Line One
asked on
HyperV - virtual networks - multiple separate with same subnet
I am using HyperV on both Windows 2008 and Windows 2012 to create test network scenarios. The idea would be as following:
I have two sets of lab VM's - each set includes a DC, Exchange and a File Server VM. I want both sets to have the same subnet structure so each would be using 192.168.0 addresses. I do not want the two sets to see each other - they are to be completely segregated. And they each must have access to the Internet.
So all the VM's in set one can communicate with each other but can not communicate with the VM's in set two. All the VM's in set two can communicate with each other but can not communicate with the VM's in set one.
I can add as many network cards as I want if that's what is needed for this to work properly.
Please describe for me how I would go about setting up the virtual switch/virtual networks to allow for the above.
I have two sets of lab VM's - each set includes a DC, Exchange and a File Server VM. I want both sets to have the same subnet structure so each would be using 192.168.0 addresses. I do not want the two sets to see each other - they are to be completely segregated. And they each must have access to the Internet.
So all the VM's in set one can communicate with each other but can not communicate with the VM's in set two. All the VM's in set two can communicate with each other but can not communicate with the VM's in set one.
I can add as many network cards as I want if that's what is needed for this to work properly.
Please describe for me how I would go about setting up the virtual switch/virtual networks to allow for the above.
ASKER
Thanks.
I am not clear on this part
"On each network select 1 server and add an additional network adapter using an external switch and set this server as a router"
So on PrivateNetwork1 I select one of the VM's and attach it to a 'real' NIC that is attached to a real switch?
And on PrivateNetwork2 I select one of the VM's and attach it to a different 'real' NIC that is attached to a real switch different from the the one Private Network1 is attached to?
So above and beyond any NIC's being used prior to this I will need at least two physical NIC's for this?
Thanks in advance for further assistance.
I am not clear on this part
"On each network select 1 server and add an additional network adapter using an external switch and set this server as a router"
So on PrivateNetwork1 I select one of the VM's and attach it to a 'real' NIC that is attached to a real switch?
And on PrivateNetwork2 I select one of the VM's and attach it to a different 'real' NIC that is attached to a real switch different from the the one Private Network1 is attached to?
So above and beyond any NIC's being used prior to this I will need at least two physical NIC's for this?
Thanks in advance for further assistance.
We do what David has mentioned.
We set up two private networks (PN).
Lab set 1 vNIC bound to PN 1.
Lab set 2 vNIC bound to PN 2.
We then create an EXTERNAL network that is bound to a physical NIC and plugged in to the production network.
Each private lab gets a VM with to vNICs:
vNIC0: PNx
VNIC1: EXTERNAL
We then install 2008 R2 and the RRAS Role. We set up RRAS in NAT mode between the private and external networks then publish RDP inbound to one of the lab VMs and any services we may need to "publish".
We register public domains that we set up in our on-premises DNS to map the RRAS IP to various services. We use RapidSSL for any SSL requirements.
We set up entire clusters, RDSH Farms, Exchange, SQL, and more in this manner.
I have an EE article on Hyper-V that may be of some assistance: Some Hyper-V Hardware and Software Best Practices.
We set up two private networks (PN).
Lab set 1 vNIC bound to PN 1.
Lab set 2 vNIC bound to PN 2.
We then create an EXTERNAL network that is bound to a physical NIC and plugged in to the production network.
Each private lab gets a VM with to vNICs:
vNIC0: PNx
VNIC1: EXTERNAL
We then install 2008 R2 and the RRAS Role. We set up RRAS in NAT mode between the private and external networks then publish RDP inbound to one of the lab VMs and any services we may need to "publish".
We register public domains that we set up in our on-premises DNS to map the RRAS IP to various services. We use RapidSSL for any SSL requirements.
We set up entire clusters, RDSH Farms, Exchange, SQL, and more in this manner.
I have an EE article on Hyper-V that may be of some assistance: Some Hyper-V Hardware and Software Best Practices.
ASKER
Thanks for the further elaboration.
You write:
"We set up two private networks (PN).
Lab set 1 vNIC bound to PN 1.
Lab set 2 vNIC bound to PN 2."
What exactly do you mean by a private network? A VLAN? What GUI interface/ commands are you using to create it?
You write:
"We set up two private networks (PN).
Lab set 1 vNIC bound to PN 1.
Lab set 2 vNIC bound to PN 2."
What exactly do you mean by a private network? A VLAN? What GUI interface/ commands are you using to create it?
Open Hyper-V Management --> Virtual Switch Manager
There are three options there:
External
Internal
Private
Option 3 is the one. It creates a private, that is not shared with anything, virtual network that the VMs use to communicate with each other.
There are three options there:
External
Internal
Private
Option 3 is the one. It creates a private, that is not shared with anything, virtual network that the VMs use to communicate with each other.
ASKER
Sorry for the long time getting back but I had to study a bit to get the idea of what is being suggested here. I know I said two labs but if I extrapolate a bit and have 6 students let's say then I start having to have a lot of network cards and switches and cables. Is there a way I can do this using only one physical network card?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for this. When you say virtual routers do you mean RRAS?
Yes.
ASKER
Thanks for the guidance.
All machines in network 1 will have 1 adapter set to say PrivateNetwork1
All machines in network 2 will have 1 adapter set to say PrivateNetwork2
Now you have to add a router to see the internet. On each network select 1 server and add an additional network adapter using an external switch and set this server as a router (use this guide http://www.dell.com/support/article/us/en/19/HOW10169/EN )