Projects › RIP to OSPF Migration Inside a Change Window
RIP to OSPF Migration Inside a Change Window
A manufacturer still runs RIPv2 between its data centre and three plants. Hop count is sending Plant 3's production traffic over a 1.544 Mb/s T1 because it is one hop, while a gigabit path through Plant 2 sits idle. The MES system the plants depend on cannot take an outage during the shift. Migrate to OSPF in a change window: overlay OSPF while RIP still runs, let administrative distance make OSPF preferred, move Plant 3 onto the gigabit path, keep the T1 as a backup, then remove RIP, without the continuous ping between the plants and the MES server losing more than one probe.
Difficulty: expert · Time: about 90 minutes
Why it matters
Migrations under an outage budget are what senior network engineers are trusted with. The technique (overlay, prefer, verify, remove) applies to every IGP or WAN migration, and "how did you make sure nothing dropped?" is the question that separates a plan from a change.
Technologies
- OSPFv2
- RIP
- Administrative Distance
- IGP Migration
- OSPF Cost
- Change Management
- Passive Interfaces
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