Hello everyone,
Using Hyper-V Server (whether 2008/2012) I've to create this multi subnet network to simulate a real World dispersed network. I plan to have following networks (HQ-10-1-1-x, STATE-192-168-1-x, DISTRICT-172-168-1-x) for which I'll create INTERNAL Hyper-V
virtual switches. Please shed light how routing can be done among these INTERNAL networks.
Hyper-V Host NICs
==============
NIC1 & NIC2 are physical interface connected to DSL modem/router. DSL modem/router's NIC: 131.107.0.254/24.
NIC1: Management NIC
IP: 131.107.0.100/24
DG: 131.107.0.254
NS1:131.107.0.254
As per Microsoft practice NIC1 is only for Hyper-V management.
NIC2: Data NIC
IP: 131.107.0.200/24
DG: 131.107.0.254
NS1:131.107.0.254
NIC2 can be used to connect VMs to physical network but that's not real objective.
Hyper-V Virtual Switches
---------------------------
vSwitch1 :HQ-10-1-1-x
Type: INTERNAL
Hyper-V's vNIC connected to this switch:
IP: 10.1.1.200/24
vSwitch2 :STATE-192-168-1-x
Type: INTERNAL
Hyper-V's vNIC connected to this switch:
IP: 192.168.1.200/24
vSwitch3 :DISTRICT-172-168-1-x
Type: INTERNAL
Hyper-V's vNIC connected to this switch:
IP: 172.168.1.200/24
Organization scenario:
=============+
vOrg has physical presence at these sites, with each site having single network.
HQ Site:
------------
Site will have AD DC/ DNS server. Server has following TCP/IP Settings:
vNIC1: 10.1.1.254/24 connected to vSwitch1 :HQ-10-1-1-x
vNIC2: 131.107.1.254/24 connected to vSwitch2 :STATE-192-168-1-x
vNIC3: 192.168.1.254/24 connected to vSwitch3 :DISTRICT-172-168-1-x
STATE Site:
-----------------
Site will have single member server
vNIC1: 192.168.1.100/24 connected to vSwitch2 :STATE-192-168-1-x
DISTRICT Site:
--------------------
Site will have single member server
vNIC1: 172.
168.1.100/24 connected to vSwitch3 :DISTRICT-172-168-1-x
Objective:
Servers at STATE and DISTRICT sites needs to be able to join domain at HQ site and talk to each other.