Hello.
I have started replicating data from 1 site to another for DR. At the corp office i have a layer 3 switch and have the ability to do vlans on both the firewall and router. At the Dr site - no. Because of this issue whenever I boot up the servers at the DR side I have to change there networking and remove the VLAN tag so that I can boot them via DHCP onto the DR network, adjust dns settings,etc. - then set manually to the remote network side so that they are accessible. Although several changes to the networking and boots to get 'everything' up and working, it's not the best solution or way to do it. For 'safety's sake' I also break the site-2-site connection while I am doing some testing to be sure that the data replicated, is only looking that the data that is there and not 'reaching' back out to the Corp side and making any changes. Make sense?
What I'd like to do is create some type of VLAN or Virtual network, at the DR side, that has the same VLAN-ID associated with it that way I can just 'boot' them up - do the testing I'd like and then power them down. Since they are in, or should be in a 'closed or virtual' network, I don't need Internet access for them if this helps with any routing. I have a machine, at the DR side that I'd like to use RDP to connect to those servers for my testing. Is this something that can be done easily with only 1 network interface at the DR side?
The Corp side has a 172.x network schema, and the DR side has a 10.x network schema.
Any thoughts or suggestions would be appreciated, and I can provide any other info needed.
I have started replicating data from 1 site to another for DR. At the corp office i have a layer 3 switch and have the ability to do vlans on both the firewall and router. At the Dr site - no. Because of this issue whenever I boot up the servers at the DR side I have to change there networking and remove the VLAN tag so that I can boot them via DHCP onto the DR network, adjust dns settings,etc. - then set manually to the remote network side so that they are accessible. Although several changes to the networking and boots to get 'everything' up and working, it's not the best solution or way to do it. For 'safety's sake' I also break the site-2-site connection while I am doing some testing to be sure that the data replicated, is only looking that the data that is there and not 'reaching' back out to the Corp side and making any changes. Make sense?
What I'd like to do is create some type of VLAN or Virtual network, at the DR side, that has the same VLAN-ID associated with it that way I can just 'boot' them up - do the testing I'd like and then power them down. Since they are in, or should be in a 'closed or virtual' network, I don't need Internet access for them if this helps with any routing. I have a machine, at the DR side that I'd like to use RDP to connect to those servers for my testing. Is this something that can be done easily with only 1 network interface at the DR side?
The Corp side has a 172.x network schema, and the DR side has a 10.x network schema.
Any thoughts or suggestions would be appreciated, and I can provide any other info needed.