Hi all, we are trying to implement at our school, a virtual network within scvmm 2008 r2 so that the students can have VM's that they can do programming on without affecting the physical PC's they are working on.
We have 2 servers that are identical in spec which sit on our actual physical domain which is all in a 172.16 address range and scvmm appears to working fine. however. We are trying to split the virtual network across the 2 servers for redundancy etc and this is where we are running into issues. We have 1 scvmm host (I will call this scvmm1) which is the master and one that is a scvmm host (scvmm2) acting as secondary server attached to scvvm1 host).
The physical nics on those servers are attached to our domain so that the web console can be used etc.
From there, scvmm1 has one virtual DC (on a 192.168 address range) with the domain called vmm.local and a number of win 7 clients.
scvmm2 also has a DC for the same network (again on the 192.168 address range) as we are trying to split the workload of VM's across both servers.
They both sit within the same Cisco 3650G switch with minimal configuration essentially, the uplink port is trunked and our physical network sits on VLAN2 and that is about it for the switch, then, each of the physical servers have their nic cards teamed to increase bandwidth and are plugged into this switch.
You can get log into the scvmm admin console on either scvmm1 or scvmm2 and see and connect to the VM's, however, the problem we are having is communication across the virtual network. For example, the DC on scvmm1 cannot ping the DC on scvmm2, it just comes up with destination host unreachable and vice versa.
Can anyone tell me if:
a) what I am trying to do can actually work, if not, do each of our VM servers have to operate as independent VM servers?
b) if this can be done, what can I do to get this to communicate?
It appears when you tracert etc that each of the DC's don't appear to get passed their default gateways as it doesn't appear to know where to go which is the same address for both the virtual DC's (192.168.0.1).
Here is a diagram which may help explain.
Any help would be appreciated.
Thanks
David