OSPF Data Exchange with DR and BDR
Open Shortest Path First (OSPF) is a link-state routing protocol that synchronizes Link-State Databases (LSDBs) across routers while minimizing network traffic. The protocol's behavior varies significantly based on network topology, with Designated Routers (DR) and Backup Designated Routers (BDR) playing crucial roles in broadcast multi-access environments to optimize update distribution.
OSPF Network Types
OSPF operates differently depending on the underlying network structure:
Point-to-Point Networks
Characteristics:
- Connects exactly two routers (serial links, VPN tunnels, direct Ethernet cables)
- No DR/BDR election required
- Routers form direct Full adjacency
- Updates exchanged directly between neighbors
Use Cases: T1/E1 serial connections, site-to-site VPN tunnels, direct router-to-router links
Broadcast Multi-Access Networks
Characteristics:
- Shared medium where multiple routers coexist (Ethernet with switch)
- DR and BDR elected to reduce flooding overhead
- DROthers (non-DR/BDR routers) synchronize only with DR/BDR
- Significantly reduces update traffic in large networks
Router Roles in OSPF
| Role | Responsibility | Communication |
|---|---|---|
| DR | Primary router for flooding LSAs to all routers | Sends to 224.0.0.5 (AllSPFRouters) |
| BDR | Standby router; promotes to DR if primary fails | Listens to 224.0.0.6 (AllDRouters) |
| DROther | Standard router; synchronizes only with DR/BDR | Sends updates to 224.0.0.6 |
DR/BDR Election Process
- Routers exchange Hello packets containing priority values
- Highest priority router becomes DR (default priority: 1)
- Second-highest priority becomes BDR
- If priorities are equal, highest Router ID wins
- Election is non-preemptive (existing DR/BDR remain unless they fail)
Important: DR/BDR elections only occur on multi-access networks. Point-to-point networks skip this process entirely.
OSPF Multicast Addresses
| Address | Name | Purpose |
|---|---|---|
224.0.0.5 | AllSPFRouters | Hello packets and general LSA flooding to all OSPF routers |
224.0.0.6 | AllDRouters | DROther updates sent exclusively to DR and BDR |
Update Flow in Broadcast Networks
- DROther detects topology change → Sends LSA to
224.0.0.6(DR/BDR only) - DR receives update → Floods to
224.0.0.5(all routers) - BDR listens passively → Maintains synchronized LSDB for failover readiness
- All routers update → LSDBs converge across the network
OSPF Neighbor States
OSPF neighbors progress through multiple states during adjacency formation. Two critical states determine synchronization behavior:
2-Way State
- Routers exchange Hello packets and recognize each other
- No LSDB synchronization occurs
- Typical relationship: DROther ↔ DROther on broadcast networks
- Sufficient for neighbor recognition but not routing
Full State
- LSDBs are completely synchronized
- Required relationship: DROther ↔ DR/BDR on broadcast networks
- All routers on point-to-point networks reach Full state
- Indicates operational adjacency for routing
Key Distinction: On broadcast networks, DROthers remain in 2-Way state with each other but must reach Full state with DR/BDR. This is normal and expected behavior.
Practical Example: Enterprise LAN
Scenario: Six routers (R1-R6) connected to a single Ethernet switch
Configuration:
- R1 elected as DR (highest priority)
- R2 elected as BDR (second-highest priority)
- R3-R6 operate as DROthers
Adjacency Relationships:
| Router Pair | State | Reason |
|---|---|---|
| R3 ↔ R1 (DR) | Full | DROther to DR |
| R3 ↔ R2 (BDR) | Full | DROther to BDR |
| R3 ↔ R4 (DROther) | 2-Way | DROther to DROther |
| R3 ↔ R5 (DROther) | 2-Way | DROther to DROther |
Traffic Optimization:
- Without DR/BDR: 15 adjacencies required (n(n-1)/2 for 6 routers)
- With DR/BDR: 10 Full adjacencies (each DROther to DR/BDR only)
- LSA flooding reduced from O(n²) to O(n) complexity
Workflow When R5 Detects Link Failure:
- R5 generates new LSA describing topology change
- R5 sends LSA to
224.0.0.6(reaches R1 and R2 only) - R1 (DR) floods LSA to
224.0.0.5(all routers receive) - All routers update LSDBs and recalculate routing tables
- R2 (BDR) maintains synchronized LSDB but doesn't flood
Common Misconceptions
Myth: The DR Controls Routing Decisions
Reality: Every router maintains its own independent LSDB and calculates routes using the SPF algorithm. The DR only optimizes LSA distribution—it doesn't make routing decisions for other routers.
Myth: All Neighbors Must Reach Full State
Reality: On broadcast networks, DROther-to-DROther relationships remain in 2-Way state. Only DR/BDR relationships require Full state for proper operation.
Myth: DR/BDR Elections Happen on All Networks
Reality: Elections occur exclusively on multi-access networks (broadcast and NBMA). Point-to-point networks form direct adjacencies without elections.
Myth: Higher Priority Always Wins Elections
Reality: Elections are non-preemptive. If a router with higher priority joins after DR/BDR are established, it won't trigger a new election unless the current DR/BDR fail.
Key Takeaways
- Network type determines behavior: Point-to-point networks use direct adjacencies; broadcast networks use DR/BDR optimization
- Multicast addresses serve specific purposes:
224.0.0.5for all routers,224.0.0.6for DR/BDR only - Adjacency states vary by role: DROthers reach Full with DR/BDR but remain in 2-Way with each other
- DR optimizes flooding, not routing: Each router independently calculates routes from its LSDB
- BDR provides redundancy: Listens passively and promotes to DR upon failure
- Election is non-preemptive: Existing DR/BDR remain until failure, regardless of new routers joining
Learn More
Official Standards:
- RFC 2328: OSPF Version 2 - Complete OSPF specification from IETF
Vendor Documentation:
Additional Resources:
- [Cloudflare Learning Center: OSPF Routing Protocol](https://www.cloudflare.com/learning