What Does Backup Designated Router Mean?

Imagine you are in a large office building with many rooms, and everyone needs to know what is happening in all the other rooms. Instead of each person running to every single room to ask for news, you elect one person to be the news collector. That person sits in the center, and everyone sends their updates to them. That person is the Designated Router (DR). Now, what happens if that person goes on vacation or gets sick? Suddenly, no one knows who to send updates to, and the whole news system breaks down.

To prevent this problem, the group also elects a Backup Designated Router (BDR). The BDR does the same job as the DR in one key way: they also listen to all the news and updates. However, the BDR does not send out the collected news to everyone else. The BDR just quietly listens and waits. The BDR only starts sending out the news if the DR stops responding. At that moment, the BDR instantly takes over the DR role.

Think of it like a classroom project. The teacher picks one student to be the group leader who collects all the answers. That is the DR. But the teacher also picks a backup leader who gets a copy of every answer as it comes in. If the main leader has to leave, the backup leader already has all the answers and can immediately become the new leader. The rest of the students do not have to start from scratch.

In technical terms, OSPF is a routing protocol that helps routers find the best path to send data across a network. On a shared network segment like an Ethernet cable or a Wi-Fi network, having every router talk to every other router would be chaotic and slow. That is why OSPF uses the DR and BDR. The BDR forms a full neighbor relationship with the DR and with every other router on that segment. This way, the BDR has a complete copy of the network topology. If the DR fails, the BDR already has all the information needed to become the new DR immediately. The transition happens without any additional database synchronization, so the network barely notices the change.

The BDR concept is critical because it makes OSPF networks more reliable. Without a BDR, OSPF would have to hold a new election and then the new DR would have to rebuild its database from scratch. That takes time and creates a temporary blind spot where routers might not know the best path. The BDR eliminates that delay. It is a simple but powerful idea: always have a prepared backup ready to step in without missing a beat.

The Backup Designated Router (BDR) is a fundamental concept within the Open Shortest Path First (OSPF) routing protocol, specifically defined in RFC 2328 (OSPF Version 2). OSPF is a link-state routing protocol that builds a complete topological map of the network by exchanging Link State Advertisements (LSAs) between routers. On broadcast multi-access networks, such as Ethernet segments with multiple routers, OSPF uses a mechanism to optimize the flooding of LSAs and reduce the number of adjacencies formed. Without this mechanism, every router on the segment would need to form a full adjacency with every other router, resulting in n*(n-1)/2 adjacencies, which becomes inefficient in larger networks.

The DR and BDR election process occurs on the multi-access segment. The BDR is elected as part of the same OSPF Hello protocol exchange. Routers send Hello packets that contain the Router ID (RID) and the priority value. The default priority is 1, but it can be set from 0 to 255. A router with priority 0 is never elected as DR or BDR. The router with the highest priority becomes the DR, and the router with the second highest priority becomes the BDR. If there is a tie in priority, the router with the highest RID wins. The RID is typically the highest IP address on a loopback interface, or the highest IP address on an active interface.

The BDR forms a full adjacency with the DR and with every other router (called DROther routers) on the segment. DROther routers form only a two-way neighbor state with each other, not a full adjacency. They do not exchange LSAs directly with each other. Instead, DROther routers send their LSAs to the DR and BDR using the multicast address 224.0.0.6 (AllDRouters). The DR then floods those LSAs to all other routers on the segment using the multicast address 224.0.0.5 (AllSPFRouters). The BDR listens to all these exchanges and maintains an identical link-state database as the DR, but it does not forward LSAs itself during normal operation. This ensures that the BDR always has an up-to-date copy of the network topology.

If the DR fails, the BDR immediately transitions to the DR role. This is detected by the expiration of the Router Dead Interval (typically 40 seconds, four times the Hello Interval of 10 seconds). The BDR then begins performing the DR functions, which includes flooding LSAs to all other routers. A new BDR election is then triggered for the segment. The new BDR is elected from the remaining DROther routers. Importantly, the OSPF database synchronization does not need to be redone because the BDR already had the full database. This makes the failover very fast, limited only by the time it takes for the DR failure to be detected.

The DR and BDR are elected based on the priority and RID, but the election is not preemptive. Once a router becomes DR or BDR, it retains that role even if a higher priority router joins the network later. The only way to force a new election is to reset the OSPF process on the DR or BDR, or shut down the interface. This is known as the "non-preemptive" nature of OSPF elections.

In a multi-access OSPF network, the DR and BDR are critical for scalability and stability. Without them, the number of full adjacencies would grow quadratically, consuming CPU and memory resources. The BDR specifically improves reliability by providing a hot standby. The failover time is predictable and minimal. For network engineers, understanding the BDR role is essential for designing resilient OSPF networks and for troubleshooting issues related to OSPF neighbor states and database synchronization.

In the context of IPv6, OSPFv3 (RFC 5340) uses the same DR/BDR concept, with the same election mechanism. The BDR exists in OSPFv3 as well, for the same reason: to provide redundancy on broadcast networks. The use of multicast addresses differs slightly, but the role of the BDR is identical.

The Backup Designated Router matters because it ensures network reliability and stability in OSPF environments. In real-world IT networks, especially in large enterprise and service provider environments, link failures and router crashes are not uncommon. Without a BDR, the failure of the Designated Router would cause a period of instability. All DROther routers would detect the DR's absence, a new election would be held, and the new DR would need to form full adjacencies with every other router and synchronize its link-state database from scratch. This process can take tens of seconds, during which time routing information may be incomplete, leading to routing loops or black holes.

The BDR eliminates this risk. It maintains a complete, synchronized database at all times. The failover is essentially instantaneous from a database perspective. The only delay is the time it takes to detect the DR failure, which is governed by the Router Dead Interval. This makes OSPF more suitable for mission-critical networks that require fast convergence.

For a network administrator, understanding the BDR is essential for network design. If you have a network segment with multiple routers, you must ensure that the routers with the highest processing power and most stable connections are elected as DR and BDR. This is done by adjusting the OSPF priority setting. Neglecting this can result in a low-end router becoming DR, which could become a bottleneck. Also, if you decommission a router that is the DR, you must know that the BDR will take over, but you should plan for the new BDR election. The BDR concept also helps in troubleshooting. If you see OSPF neighbor states stuck in "2-WAY" on a broadcast network, it is not necessarily an error; it simply means those routers are not DR or BDR. Knowing this saves time in diagnostics.

the BDR is a design choice that trades a small amount of extra CPU and memory on one router for significant gains in network stability and failover speed. It is a core feature of OSPF that any IT professional working with routed networks must understand.

Exam questions about the Backup Designated Router appear in several common patterns. The first pattern is the direct definition question. For example: "Which of the following best describes the role of the Backup Designated Router in OSPF?" The options might include descriptions like "It forwards LSAs to all routers," "It maintains a full topology database but does not forward LSAs," or "It only communicates with DROther routers." The correct answer is the one that states it holds a full database but does not flood LSAs during normal operation.

The second pattern is the election scenario. You are given a table or a diagram showing four routers with their priorities and Router IDs. For example: Router A priority 10, RID 1.1.1.1; Router B priority 10, RID 2.2.2.2; Router C priority 5, RID 3.3.3.3; Router D priority 0, RID 4.4.4.4. The question asks: "Which router will become the BDR?" The answer is the router with the second highest priority that is not the DR. If priorities are equal, the highest RID becomes the DR, and the second highest becomes the BDR. In this example, Router A and B have same priority, so Router B (higher RID) is DR, and Router A is BDR. Routers with priority 0 are ineligible.

The third pattern is neighbor state questions. For example: "An OSPF router on a broadcast network shows a neighbor state of '2-WAY' with another router. What does this indicate?" The answer is that the two routers are not DR or BDR, but have exchanged Hello packets and are ready to become neighbors. They do not form a full adjacency because they will send their LSAs to the DR and BDR instead.

The fourth pattern is failover behavior. A question might say: "The Designated Router on an OSPF broadcast segment fails. Which of the following statements is true?" The correct answer might be: "The BDR immediately becomes the DR and a new BDR is elected." A distracter might say: "All routers re-elect a new DR and BDR, causing a delay." The key is that the BDR already has the database, so there is no need to re-synchronize.

The fifth pattern is configuration based. In the CCNA, you might be asked to configure an interface with a specific priority to ensure a router becomes the BDR. For example: "Which command should be used to set the OSPF priority to 100 on an interface?" The answer is `ip ospf priority 100`. You also need to know that the priority is set in interface configuration mode.

Finally, there are troubleshooting questions. A network administrator notices that the BDR is not forming a full adjacency with the DR. Possible causes include mismatched Hello timers, authentication failure, or the interface is configured as passive. You might be asked to identify the problem from a show command output.

Understanding the Backup Designated Router is not just about passing an exam; it is about designing and troubleshooting resilient networks. In practice, network engineers must carefully plan which routers become the DR and BDR. The default priority of 1 means that the router with the highest Router ID automatically becomes the DR, which may not be ideal. For example, a low-end router with a high Router ID could become the DR, creating a bottleneck because it has to process all the LSA flooding. To avoid this, engineers set a higher priority on more capable routers.

Configuration is straightforward. On Cisco IOS, you set the priority under the interface configuration mode with the command `ip ospf priority` followed by a number from 0 to 255. If you want a specific router to be the BDR, you set its priority to, say, 50, and set another router's priority to 100 to be the DR. This gives you control over the election. Remember, once elected, the roles are non-preemptive. So if you change priorities later, you must restart the OSPF process on the DR/BDR to force a new election. This can be done with `clear ip ospf process` but that is disruptive.

What can go wrong in practice? One common issue is that a router is accidentally configured with priority 0, making it ineligible for election. In a network where you only have two routers, both need to be eligible for DR/BDR. If one is priority 0, the other becomes DR but there is no BDR. If that single DR fails, there is no backup, and all adjacencies must be rebuilt. Another issue is mismatched Hello or Dead timers. If the DR has a different Dead Interval, the BDR might not detect the failure in time. Also, authentication must be consistent between the DR and BDR, or they will not form a full adjacency.

For troubleshooting, use commands like `show ip ospf neighbor` to see the state of neighbors. If a DROther router shows FULL with the DR and BDR, and 2-WAY with other DROther routers, it is correct. If you see FULL with a DROther router that should be 2-WAY, there may be a configuration error. The `show ip ospf interface` command shows the DR, BDR, and priority for that interface. This is useful for verifying who was elected.

Professionals also need to understand the impact on convergence time. The BDR allows sub-second convergence if BFD (Bidirectional Forwarding Detection) is used, but that is an advanced feature. Without BFD, the 40-second Dead Interval is the primary delay. In modern networks, engineers often reduce the Hello and Dead intervals to speed up detection. For example, a Hello of 1 second and Dead of 4 seconds are common for fast convergence. The BDR still works the same way, just faster.

Finally, remember that the DR and BDR concept only applies to broadcast and non-broadcast multi-access networks. On point-to-point links, there is no DR or BDR. So when designing your network, know which segments need this mechanism. The BDR is a simple but critical component of OSPF that ensures reliability through redundancy. Master this concept by practicing configuration and checking neighbor states.