We're planning to implement a stretched datacenter between our two sites. The connectivity between them is a single 100mbit QinQ connection. We have about 500 users at site A and 200 users at site B. There is a very low amount of traffic being generated on the link.
Disclaimer: I won't go through the replication, as it's a different story. We have SAN replication ready in a few months. L3 routing etc is also not an issue, as we know how to do this.
The network plan (right now) is the following:
- VLAN 300: Site A+B - 172.16.0.0/24 - management (switches, routers, vsphere etc)
- VLAN 310: Site A+B - 10.50.0.0/24 - shared servers for clients at either site
- VLAN 311: Site A(+B) - 10.51.0.0/24 - servers for clients at site A
- VLAN 312: Site B(+A) - 10.52.0.0/24 - servers for clients at site B
- VLAN 320: Site A - 192.168.0.0/24 - clients in the site A building
- VLAN 321: Site B - 192.168.10.0/24 - clients in the site B building
The general idea here is that services with HA/site awareness (AD, DFS, Exchange, Lync and so on) lives in VLAN 311 for site A and VLAN 312 for site B. This is simply to ensure that all clients are using the services closest to them, to prevent a bad user experience if the L2 link between the sites should go down. We will be using a single AD domain.
Servers that do not have any kind of HA built in should be put in VLAN 310, wich is active at both sites simultaneously. This way we can do a SAN replica failover of a specific LUN and bring up the VM's at the opposite site in case of disaster.
- Should I stop over-engineering stuff and rather do a completely flat design, with 3 VLAN's (one mgmt, one server and one client)? I'll lose site awareness, but it'll simplify the setup and management a great deal
- Will vSphere break my heart if I try to implement two different clusters on the same logical network?
- Will anything else break my heart? What are major gotchas/cons/prons?