Although it did not resolve the issue, i appreciate for taking the time to answere my concern. It would be impossible for the remote site because it is a large network with various subnets, and also impossible on the local side as well. We are connecting this network thru MPLS. I'm just wondering how other large organization merge their networks without changing their IP addressings . Again thanks for your reply.
With large organisations, public IP addresses are often used for servers and main access devices therefor unique.
also, most of the time end users always connect to these servers, FWs, mail, DNS etc...but hardly directly. so one PC does not talk to another.
when merging is a requirement, MPLS VPN could be used to allow for 2 or more different organizations to use overlapping IPs as long as they communicate through servers with Public addressing. FWs are often the separator, where each VPN, maps to an interface.
Both you and Jon had great answeres regarding the issue. I'm not sure if i'll run on the same problem if just one of the router link on the remote site has an IP conflict with the local link between routers, as shown below. Thanks.
How do organisations merge without changing addressing? basically they don't. When two networks merge, ultimately something will need readressing, it is more how do they manage?
The first bit will probably be opening a VPN tunnel to allow access to the main corporate web server, and jining up email - cross publication of contact info, that sort of thing. At that point it is two totally separate networks that talk to each other.
Ideally major systems would be on public addressing, so that no NAT would be needed.
Actually merging the two networks may or may not actually happen. It is rare that there is actually a merger - normally it is a takeover. What may happen is that office by office, the "minor" company gets migrated to the major companies network. With sensible planning, the email services etc should already be available, and all that happens is a change of network address, and logical position within the network.
MPLY may be an option, as long as datacentre addressing is sortable, with route targets to handle routing, and maybe NAT for source addresses as you hit the datacentre.
I would hate the job of merging two large networks, especially if both used different vendor's kit. Imagine the fun if someone the size of HP running a Cisco network was to merge with someone the size of Sun running Juniper!
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...