Best practices for integrating recent acquistion into existing IP network

[Steve Coady]

Hello

IS there a Phased approach guide/outline of considerations and practices, with examples, of integrating a new acquisition with possible same/similar internal ip addresses into my existing WAN/LAN infrastructure.

[paul driver]

Hello
Can you be more specific?

Res
Paul


Sent from Cisco Technical Support Android App

[Steve Coady]

I have an existing IP network over AT&T AVPN. I have 8 sites currently across the Nation. Recently we aquired an interest in a company that has (5) sites around the country and are on a L2 network. We are going to put them on our AVPN design. I wanto to "bring them into the fold" as if they are like any 1 of the orther existin 8 sites.

I belive they may have internal ip shecmes that will conflict with my current IP scheme.

I know this has been doen b4 and am looking for a proven guide that will will walk me through the process step-by-step to make this integration  as seemeless and error free as possible.

[paul driver]

Hello
For a short fix term i would suggest nat.

And for a long term i suppose would depend how large this new company is - possible ip readdressing !

Res
Paul

Sent from Cisco Technical Support Android App

[Steve Coady]

Thankyou for the response. I am really looking for more of an indepth study or outlined project task lsits. The Integration has other steps to consider.

For one, the company acquired company is well known, so we will not be changing their name to ours. How would that affect Domains and Active directory?

I am looking for a project template with proven steps to guide me through this design.

[paul driver]

Hello Steve

Regards this merger, the network IP address merger via nat is one thing but then considering merging AD domains/forests it a whole new ball game

As you have to worry about email/smtp user accounts / ldap etc... if I remember from a 10000 ft perspective, there is a ADMT migration tool which can be used. But thats way down the line of things to define before you are even near ready to attempt to merge AD domains

I think you have your work cut out on this project but suggest you seek advice from a Microsoft forum as to the exact procedure for AD merger.

As for the remote access between your two company's then as stated previously implementing NAT should a relative painless procedure

Res
Paul

Sent from Cisco Technical Support iPad App

[Steve Coady]

Sorry I have not responded recently.

We have several overlapping Ip subnets. However, the new company stated they would
possibly re-ip some of those. So that is good.

The new company currently uses ENLAN Ip backbone for Layer 2 between the (5) sites.

We will be adding each of the 5 sites as a Layer endpoint, to match how we have ALL our other endpoints.
Circuits and routers have been ordered.

I understand natting in firewall/asa and I am wondering how to approach the design in that each site may need
to have some of there subnets natted due to the importance they have (Server farms, VoIP etc...)

So if each of the new sites needs 1 or 2 subnets natted, what is the best practice approach to that?
Is this done at a local firewall for each site? currently, I think they simply have the 1 asa at Primary site

Are the nats done in the new L3 routers?

If you know of any video's about this, that would be nice to view.