ToChangeIT
asked on
Using same IP addresses in two Active/Active DCs connected by stretched layer 2 Interconnect
Hi Experts
I suspect this is not possible, but I thought I would throw it out to you guys as a challenge
Basically I am building two new data centers in active/active configuration with two Metro Ethernet Interconnects (unsure of protocol as yet but it will not be OTV as I have to use Juniper). Pretty much everything is virtualised (5.1) and most OSs are Win 2012. The only replication is synchronous and occurs between the two SANs.
I have a requirement to use the same IP addressing scheme (by that I mean the same IP addresses) in both DCs.
Question 1 - is this possible?
Question 2 - if it is possible, how on earth can it be done?
Any help would be very much appreciated
Yours hopefully
Ben Woods
I suspect this is not possible, but I thought I would throw it out to you guys as a challenge
Basically I am building two new data centers in active/active configuration with two Metro Ethernet Interconnects (unsure of protocol as yet but it will not be OTV as I have to use Juniper). Pretty much everything is virtualised (5.1) and most OSs are Win 2012. The only replication is synchronous and occurs between the two SANs.
I have a requirement to use the same IP addressing scheme (by that I mean the same IP addresses) in both DCs.
Question 1 - is this possible?
Question 2 - if it is possible, how on earth can it be done?
Any help would be very much appreciated
Yours hopefully
Ben Woods
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
not possible if like you said both networks are interconnected. out of curiousity, whats the reason you want to use the same IP ?
ASKER
Thanks for your super-quick reply TG-TIS. I understand the duplicate IP conflict issue, but thought therre may be some clever VMWare or VLAN solution to the problem.
If both locations are connected and considered one network, it's going to be hard to mask that situation. If you make them two seperate networks, your problem goes away.
ASKER
Hi innocentdevil
The key reason is sloppy in-house legacy programmes which use hard-coded IP addresses and FQDNs. I know it is possible to script my way out of this, but a nifty network-based solution would get me a lot of brownie points at work!!!
Ben
The key reason is sloppy in-house legacy programmes which use hard-coded IP addresses and FQDNs. I know it is possible to script my way out of this, but a nifty network-based solution would get me a lot of brownie points at work!!!
Ben
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.