BLAZEPOINT
asked on
Hyper-V R2 Host and VM networking
Hi
Wonder if anyone could kindly help me.
I have built a 16GB ML110 Server with 2 x NIC cards, running Hyper-V R2, linked to Hyper-V console via Windows 7 PC.
I have a Production Domain and about to create a VM Domain hosting a few Domain controllers, Exchange, SQL and MS CRM) for training and testing purposes.
I have a spare ADSL line I could link the test domain onto for internet access, I would like to still control the VM machines via the Windows 7 PC from my Production Domain but mainly the VM domain needs to be isolated from the Production Domain.
So would I, put simply, do this:
1) Retain NIC 1 (Physical NIC) plugged into the switch serving the Production Domain / Network.
2) Create External Virtual Network under Hyper-V --> NIC2 (Physical NIC)--> Spare ADSL (but allow management OS to share this adaptor)
Would I still to in addition to above, Create an External Virtual Network under Hyper-V for NIC1?
Many Thanks
Wil
Wonder if anyone could kindly help me.
I have built a 16GB ML110 Server with 2 x NIC cards, running Hyper-V R2, linked to Hyper-V console via Windows 7 PC.
I have a Production Domain and about to create a VM Domain hosting a few Domain controllers, Exchange, SQL and MS CRM) for training and testing purposes.
I have a spare ADSL line I could link the test domain onto for internet access, I would like to still control the VM machines via the Windows 7 PC from my Production Domain but mainly the VM domain needs to be isolated from the Production Domain.
So would I, put simply, do this:
1) Retain NIC 1 (Physical NIC) plugged into the switch serving the Production Domain / Network.
2) Create External Virtual Network under Hyper-V --> NIC2 (Physical NIC)--> Spare ADSL (but allow management OS to share this adaptor)
Would I still to in addition to above, Create an External Virtual Network under Hyper-V for NIC1?
Many Thanks
Wil
kevinhsieh
Since you want to keep the VM environment completely separate from a networking standpoint NIC 1 should not have a virtual network associated with it, and the external virtual network attached to NIC 2 should NOT be shared with the management OS.
ASKER
Thank you kevin;
So from your advice:
1) Retain NIC 1 (Physical NIC) plugged into the switch serving the Production Domain / Network. (but do not create a Virtual Network for it under Hyper-V)
2) Create External Virtual Network under Hyper-V --> NIC2 (Physical NIC)--> Spare ADSL (do not allow management OS to share this adaptor)
Would this setup then allow me to isolate the VM Domain from the Production Domian, but allow me to control my VM machines on my Windows 7 PC (which is located in the Production Domain) via the Hyper-V console?
Thank you
Wil
So from your advice:
1) Retain NIC 1 (Physical NIC) plugged into the switch serving the Production Domain / Network. (but do not create a Virtual Network for it under Hyper-V)
2) Create External Virtual Network under Hyper-V --> NIC2 (Physical NIC)--> Spare ADSL (do not allow management OS to share this adaptor)
Would this setup then allow me to isolate the VM Domain from the Production Domian, but allow me to control my VM machines on my Windows 7 PC (which is located in the Production Domain) via the Hyper-V console?
Thank you
Wil
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Kevin;
Thank you for your help and quick concise answers. Points well deserved !
Wil
Thank you for your help and quick concise answers. Points well deserved !
Wil