🚀 OSPF in DMVPN Phase 3 (Cisco IOS 15.9) – Complete Deployment Guide
📚 Table of Contents
📖 Introduction
Deploying OSPF in DMVPN Phase 3 requires precision. Unlike traditional hub-and-spoke routing, DMVPN Phase 3 introduces dynamic spoke-to-spoke tunnels, making routing decisions more complex.
🌐 DMVPN Phase 3 Explained
DMVPN Phase 3 allows spokes to dynamically build tunnels after initial communication through the hub. This improves latency, bandwidth usage, and scalability.
🔽 Expand: How Phase 3 Works Internally
Phase 3 uses NHRP redirect and shortcut messages. The hub informs spokes about better paths, and spokes establish direct GRE/IPsec tunnels.
📡 Role of OSPF in DMVPN
OSPF distributes routing information across the DMVPN network. Its behavior directly impacts:
- Route propagation
- Next-hop selection
- Convergence speed
⚠️ Why OSPF Network Type Matters
Default: Broadcast
- Triggers DR/BDR elections ❌
- Causes unnecessary adjacency overhead ❌
- Breaks DMVPN next-hop logic ❌
🔽 Expand: DR/BDR Problem Explained
Broadcast networks assume full mesh connectivity, which DMVPN does not provide. This mismatch leads to inefficient routing.
✅ Point-to-Multipoint Advantages
- No DR/BDR election ✔
- Hub-based next-hop ✔
- Simplified routing ✔
- Better scalability ✔
ip ospf network point-to-multipoint in DMVPN Phase 3.
⚙️ Configuration Guide
1. Hub Configuration
interface Tunnel0 ip address 10.0.0.1 255.255.255.0 ip nhrp map multicast dynamic ip nhrp network-id 1 ip nhrp redirect tunnel source GigabitEthernet0/0 tunnel mode gre multipoint tunnel key 100
2. Spoke Configuration
interface Tunnel0 ip address 10.0.0.2 255.255.255.0 ip nhrp map 10.0.0.1 192.168.1.1 ip nhrp shortcut tunnel source GigabitEthernet0/0
3. OSPF Configuration
router ospf 1 network 10.0.0.0 0.0.0.255 area 0 interface Tunnel0 ip ospf network point-to-multipoint
💻 CLI Verification
Code Example
show ip ospf neighbor show ip route ospf
Sample CLI Output
Neighbor ID State Address Interface 1.1.1.1 FULL 10.0.0.1 Tunnel0 O 192.168.2.0/24 [110/2] via 10.0.0.1
🔽 Expand CLI Explanation
Routes show the hub as next-hop, ensuring proper DMVPN behavior before shortcuts occur.
🆕 Cisco IOS 15.9 Enhancements
- Improved NHRP stability
- Better next-hop handling
- Reduced need for route-maps
- Enhanced scalability
🔽 Expand: Old vs New Behavior
Older IOS required manual next-hop fixes. IOS 15.9 aligns OSPF behavior automatically with DMVPN design.
📐 Mathematical Insight: OSPF Cost & Path Selection
Understanding OSPF in DMVPN becomes clearer when we look at the mathematics behind routing decisions. OSPF selects the best path based on cost, which is inversely proportional to bandwidth.
📊 OSPF Cost Formula
The cost of an interface is calculated as:
\[ \text{Cost} = \frac{\text{Reference Bandwidth}}{\text{Interface Bandwidth}} \]
By default, the reference bandwidth is 100 Mbps. For example:
\[ \text{Cost} = \frac{100}{10} = 10 \]
This means a 10 Mbps link has a higher cost than a 100 Mbps link, so OSPF prefers higher bandwidth paths.
🔽 Expand: Why Cost Matters in DMVPN
In DMVPN Phase 3, OSPF initially routes traffic via the hub. The cost calculation ensures that the most efficient path is selected before NHRP redirects create a direct spoke-to-spoke tunnel.
📈 Shortest Path First (SPF) Algorithm
OSPF uses Dijkstra’s algorithm to compute the shortest path:
\[ D(v) = \min \left( D(u) + c(u,v) \right) \]
Where:
- \(D(v)\): shortest distance to node v
- \(c(u,v)\): cost between nodes
This ensures that routing decisions are mathematically optimal.
🎯 Key Takeaways
- DMVPN Phase 3 enables dynamic spoke tunnels
- OSPF must use point-to-multipoint
- Broadcast mode causes inefficiencies
- IOS 15.9 simplifies deployment
📘 Final Thoughts
Correct OSPF configuration is critical in DMVPN Phase 3. Using point-to-multipoint ensures predictable routing, scalability, and efficient tunnel creation.
