Projects › Post-Merger Routing Integration: OSPF and EIGRP
Post-Merger Routing Integration: OSPF and EIGRP
The company (OSPF area 0) has acquired a firm that runs EIGRP AS 100. Two new border routers, BDR-1 and BDR-2, are cabled and addressed between HQ-CORE and ACQ-CORE. Each side already has an external route of its own: HQ reaches a partner network by a static route redistributed into OSPF, and the acquired firm reaches its legacy ERP by a static route redistributed into EIGRP. Join the two routing domains through both border routers without loops, detours or a single point of failure.
Difficulty: expert · Time: about 90 minutes
Why it matters
Mergers are where two-point mutual redistribution happens in real networks, and it is the routing topic CCNP ENARSI spends the most time on because it fails quietly: an EIGRP external (distance 170) comes back to the other border router as an OSPF external (distance 110) and wins, so traffic takes a detour, and routes are redistributed back into the domain they came from. Route tags and filtering on those tags is the standard fix, and being able to show the result in the routing table is the job.
Technologies
- OSPFv2
- EIGRP
- Route Redistribution
- Route Tags
- Route Maps
- Distribute Lists
Related projects
- Multi-Area OSPFv2 Network with Area 0 Backbone & Stub Routing
- Branch-to-Cloud WAN Fabric Deployment via Cisco SD-WAN
- Route-Based Site-to-Site VPN: Tunnel Interface and eBGP, with IKEv2 Design
- WAN-Edge QoS for Voice and Video: Classify, Queue, Apply
- Cisco SD-WAN Direct Internet Access (DIA) with Enterprise Firewall
- Dual-Circuit Branch: Floating Static Failover with a Pinned Probe Route
- DMVPN Phase 3: Hub-and-Spoke with On-Demand Spoke-to-Spoke Tunnels
- EIGRP for a Three-Store Retailer: Authenticated Peering and Stub Branches