You were happy. You were in your cubicle, working with that fancy new management tool that was going make those dynamic maps you’d always dreamed of. Your phone rings, an annoyance at the best of times, but more so since you were just about done with that sweet core map that was coming out even better than you’d imagined it. You answer, and you boss summons you to conference room X.
When you arrive, your boss, his boss, the CTO, and few other folks you aren’t sure you recognize but who all seem dressed above your pay grade, ask you to sit. They swear you to secrecy, and then share some fateful words. “We’re merging with another company, and we need you to figure out how to get the networks connected.”
That ends your sunny day of productivity, but it’s just the beginning for this edition of the Packet Pushers podcast. This is the first in a series we’re calling “Design & Build,” where we talk through some common network challenges you might face in your network career.
Today, talk about network mergers, where the network you know and love needs to work with a network that you don’t. We’re going to hear from some folks who’ve dealt with this sort of project before. We’ll share wisdom and experience, from deep within the trenches.
What We Discuss
- Mergers are going to happen.
- There’s a people component.
- Time is an important consideration.
- An interim strategy for quick connectivity.
- Specific technical challenges.
Our External Resources
- Daniel Brown — http://vlan50.com
- Quentin Demmon — https://packetpushers.net/author/qdemmon/
- Eugene Khabarov — http://betep.wpl.ru/