Cisco Certified Network Associate (CCNA) 200-301 · Free study guide

Objective 3.4 — Configure single-area OSPFv2

OSPFv2 distributes IPv4 reachability after routers discover compatible neighbors, form adjacencies, exchange topology information, and calculate paths. Troubleshoot those stages in order.

Process and router ID

The locally chosen OSPF process number does not need to match a neighbor's. The router ID is a 32-bit identifier used inside OSPF and must be unique. A manually configured stable ID is operationally clearer than relying on automatic selection. Changing it may require resetting the process or adjacency according to platform behavior.

The router ID looks like IPv4 dotted decimal but is an identifier; it does not have to be a reachable interface address.

If no router ID is configured, IOS-style selection commonly prefers the highest IPv4 address on an up loopback interface, then the highest IPv4 address on an up non-loopback interface. The interface does not have to be enabled for OSPF. The value is selected when the process starts and does not simply change every time a higher address appears, which is another reason to configure it deliberately.

Enabling interfaces in one area

OSPF can be enabled through network matching statements or interface-oriented configuration. Ensure the intended interfaces participate in the same area for this single-area scope. Passive interfaces advertise their connected prefix but do not form neighbors, which is useful on user-facing LANs and wrong on a required router-to-router adjacency.

Neighbor prerequisites

Neighbors need Layer 3 reachability on the link and agreement on essential OSPF parameters such as area, timers, and compatible network behavior. Unique router IDs are required. MTU issues can let discovery begin but prevent full database exchange. Authentication is outside this objective's adjacency scope, but a real network may use it.

Check interface state and addressing before OSPF details.

IOS command map

One process-oriented lab pattern is router ospf 1, followed by router-id 4.4.4.4 and network 10.44.0.0 0.0.255.255 area 0. An interface-oriented alternative is ip ospf 1 area 0 under the intended routed interface. Use ip ospf network point-to-point only when that interface's OSPF network type should be point-to-point; do not apply it merely to avoid understanding a broadcast election.

Use show ip ospf neighbor to verify neighbor state, show ip ospf interface to check area, timers, network type, cost, and DR or BDR state, and show ip route ospf to confirm installed prefixes. show ip protocols and show ip ospf expose process-level state. Changing a live router ID may require an OSPF process reset and adjacency rebuild, so practice that change only in an authorized lab or controlled window.

Point-to-point and broadcast networks

Point-to-point OSPF links between two routers do not need DR/BDR election. Broadcast Ethernet networks elect a designated router and backup to reduce the number of full adjacencies and coordinate flooding. Priority influences eligibility and election, then router ID breaks ties. Election is generally not preemptive after roles settle simply because a better candidate arrives.

Worked scenario

Two Ethernet neighbors see each other but remain in a partial state. Area and timers match; one interface MTU differs. Correct the underlying MTU design rather than repeatedly restarting OSPF. Once full, verify expected OSPF routes. If the neighbor is full but one LAN is absent, inspect whether that LAN participates or is advertised, not the basic adjacency.

Verification layers

Inspect process parameters and router ID, participating interfaces, area and network type, neighbor state, DR/BDR on broadcast links, the OSPF database when needed, and installed OSPF routes. Finally test selected prefixes and return paths.

Common traps

• Requiring process numbers to match.
• Using duplicate router IDs.
• Expecting DR/BDR on a point-to-point link.
• Calling a passive interface silent in advertisements.
• Troubleshooting route exchange before neighbor state.

Readiness checklist

• I can form and verify a single-area adjacency.
• I distinguish process number from router ID.
• I can explain broadcast election and point-to-point behavior.
• I separate adjacency failure from missing-prefix failure.