Hands-On Lab: Configuring OSPF on Broadcast Networks

This hands-on lab configures OSPF across an Ethernet segment with three routers, observing DR and BDR election in action and verifying how it differs fundamentally from the point-to-point behavior covered in the previous lab.

OSPF Broadcast Network TypeDR and BDR ElectionOSPF Priority

~3 min read · Updated Sep 22, 2026

Lab Objective

Configure OSPF on an Ethernet segment shared by three routers, observe the DR and BDR election process, manually influence the outcome using OSPF priority, and verify the resulting neighbor states.

Lab Purpose

Unlike the point-to-point network type covered in the previous lab, a broadcast network type (the default on Ethernet interfaces) requires electing a Designated Router and Backup Designated Router to reduce the number of adjacencies needed among multiple routers sharing the same segment.

Lab Topology

R1, R2, R3 all connected to the same
Ethernet segment via Switch1

R1: 192.168.100.1/24
R2: 192.168.100.2/24
R3: 192.168.100.3/24

Task 1: Configure Basic Addressing

Configure all three routers' Ethernet interfaces on the shared segment.

Task 2: Enable OSPF on All Three Routers

Enable OSPF process 1 on all three routers, advertising the shared network into area 0.

Task 3: Verify the Network Type

Confirm the interface is recognized as a broadcast OSPF network type.

Task 4: Observe the Default DR/BDR Election

Identify which router became DR and which became BDR by default, based on Router ID.

Task 5: Influence the Election Using Priority

Set R3's OSPF priority higher than the others, then reset OSPF processes and observe whether R3 becomes the new DR.

Solution and Verification

R1(config)# interface gigabitethernet0/0
R1(config-if)# ip address 192.168.100.1 255.255.255.0
R1(config-if)# no shutdown

R2(config)# interface gigabitethernet0/0
R2(config-if)# ip address 192.168.100.2 255.255.255.0
R2(config-if)# no shutdown

R3(config)# interface gigabitethernet0/0
R3(config-if)# ip address 192.168.100.3 255.255.255.0
R3(config-if)# no shutdown

R1(config)# router ospf 1
R1(config-router)# network 192.168.100.0 0.0.0.255 area 0

R2(config)# router ospf 1
R2(config-router)# network 192.168.100.0 0.0.0.255 area 0

R3(config)# router ospf 1
R3(config-router)# network 192.168.100.0 0.0.0.255 area 0

R1# show ip ospf interface gigabitethernet0/0

GigabitEthernet0/0 is up, line protocol is up
  Internet Address 192.168.100.1/24, Area 0
  Network Type BROADCAST, Cost: 1

R1# show ip ospf neighbor

Neighbor ID     Pri   State           Address         Interface
192.168.100.2   1     FULL/BDR        192.168.100.2   GigabitEthernet0/0
192.168.100.3   1     FULL/DR         192.168.100.3   GigabitEthernet0/0

-- By default, the router with the HIGHEST
-- Router ID wins DR election (here, R3 at
-- 192.168.100.3), with the next-highest
-- becoming BDR (R2) -- R1 sees itself as
-- neither, shown as DROTHER in its own status

-- Attempting priority to force R1 as DR
-- instead, for demonstration:
R1(config)# interface gigabitethernet0/0
R1(config-if)# ip ospf priority 200

R1(config-if)# shutdown
R1(config-if)# no shutdown

R1# show ip ospf neighbor

-- R1's priority change does NOT retroactively
-- displace the existing DR/BDR -- DR/BDR
-- election is non-preemptive, so R3 remains
-- DR even with R1's higher priority, until
-- R3 itself goes down and a genuinely new
-- election occurs

Key Takeaway

OSPF's DR/BDR election is deliberately non-preemptive: once a DR is elected, a newly configured higher-priority router does not automatically take over, even after resetting its own OSPF process — the existing DR only changes if it actually goes down, which is precisely why priority should be configured before a router first joins the segment rather than after a DR is already established.

Written & researched by Dr. Shahin Siami

Related Articles

Hands-On Lab: Configuring Standard Numbered ACLs

This hands-on lab configures a standard numbered ACL to permit traffic from a specific subnet while denying everything else, applies it to the correct interface and direction, and verifies both permitted and denied traffic behave as expected.

Continue

Hands-On Lab: Configuring VRRP

This hands-on lab configures VRRP between two routers as the open-standard alternative to HSRP, using a real interface address as the virtual IP, and verifies Master/Backup roles and automatic failover behavior.

Continue

Hands-On Lab: Configure GLBP Redundancy

This hands-on lab configures GLBP between two routers to achieve load balancing across both routers simultaneously, verifying that different hosts receive different virtual MAC addresses and therefore route through different physical gateways.

Continue

Hands-On Lab: Implementing HSRP

This hands-on lab configures HSRP between two routers sharing a virtual gateway address, sets priority and preempt to control which router is active, and verifies automatic failover when the active router fails.

Continue

Hands-On Lab: Verifying the EIGRP Database

This hands-on lab examines the EIGRP topology table directly, identifying the successor and feasible successor for a destination network, and demonstrates how this underlying data explains what appears in the IP routing table.

Continue

Hands-On Lab: Summarizing Routes with EIGRP

This hands-on lab manually configures interface-level route summarization in EIGRP, advertising a single aggregated route instead of several specific subnets, and verifies the automatically created Null0 discard route that prevents summarization-related loops.

Continue