A network administrator is evaluating an OSPFv2 implementation across a shared Ethernet segment (172.16.1.0/24). Router R1 initialized first on the segment and assumed the Designated Router (DR) role. Routers R2 and R3 joined subsequently. Router R4 was added last, configured with an OSPF interface priority of 200, whereas R1, R2, and R3 retain the default interface priority of 1.
Executing `show ip ospf neighbor` on Router R4 produces the following output:
text
R4# show ip ospf neighbor
Neighbor ID Pri State Dead Time Address Interface
1.1.1.1 1 FULL/DR 00:00:36 172.16.1.1 GigabitEthernet0/1
2.2.2.2 1 FULL/BDR 00:00:34 172.16.1.2 GigabitEthernet0/1
3.3.3.3 1 FULL/DROTHER 00:00:38 172.16.1.3 GigabitEthernet0/1
Based on this output and OSPF operational behavior, why has Router R4 not assumed the Designated Router role despite having a higher interface priority?
- OSPF DR and BDR elections are non-preemptive; once an active DR is elected, a newly connected router will not trigger a election takeover even if configured with a higher priority.Cevap
- BRouter R4 is disqualified from DR election because any interface priority value greater than 100 is automatically treated as priority 0 by OSPFv2.
- CRouter R1 maintains the DR position because its lower numerical Router ID (1.1.1.1) takes precedence over interface priority values during adjacency negotiation.
- DRouter R4 must be configured in point-to-point network mode before high interface priority values are recognized for DR election eligibility.