OSPF Single-Area Configuration

Configuring a dynamic routing protocol is a fundamental skill for any network engineer, and mastering Open Shortest Path First (OSPF) is especially critical for the CCNA and real-world enterprise networks. OSPF's efficiency, scalability, and widespread adoption make it the go-to Interior Gateway Protocol (IGP). This guide moves beyond theory to provide a thorough, practical walkthrough for configuring and verifying a single-area OSPF network on Cisco routers, ensuring you can build a functional, optimized routing domain.

OSPF Core Concepts and Operation

Before entering any commands, you must understand what OSPF is doing behind the scenes. OSPF is a link-state routing protocol, meaning each router constructs a complete map of the network topology. It does this by flooding Link-State Advertisements (LSAs) throughout an area. Every router receives these LSAs and uses them to build an identical Link-State Database (LSDB).

To calculate the best paths, each router independently runs the Dijkstra algorithm (Shortest Path First algorithm) on its LSDB. This algorithm determines the shortest path tree, with the router itself as the root, to every known network. The "shortest" path is determined by a cumulative cost metric, which is inversely derived from the interface bandwidth by default. A critical concept for stable operation is the Router ID (RID), a 32-bit number that uniquely identifies each router in the OSPF domain. The RID is selected in this order: 1) a manually configured OSPF router-id, 2) the highest loopback interface IP address, or 3) the highest active physical interface IP address.

Configuring Single-Area OSPF on Cisco IOS

A single-area OSPF design, where all routers reside in Area 0 (the backbone area), is the foundation for more complex multi-area deployments. The configuration involves two primary steps: enabling OSPF on the router and specifying which interfaces will participate.

The global command router ospf [process-id] enters OSPF configuration mode. The process-id is locally significant and does not need to match on neighboring routers. The core configuration is done using the network command under the OSPF router configuration. This command uses a wildcard mask (the inverse of a subnet mask) to match interface IP addresses and places those interfaces into a specified OSPF area. For a clean and predictable configuration best practice, use the ip ospf [process-id] area [area-id] interface configuration command instead. This method explicitly enables OSPF per interface.

Example Configuration:

Router(config)# router ospf 1
Router(config-router)# router-id 1.1.1.1
Router(config-router)# passive-interface GigabitEthernet0/0 (Optional: prevents unwanted neighbor adjacencies on this interface)
Router(config)# interface GigabitEthernet0/1
Router(config-if)# ip ospf 1 area 0
Router(config-if)# interface Serial0/0/0
Router(config-if)# ip ospf 1 area 0

Verifying OSPF Operation and Routing Tables

After configuration, verification is crucial. Start by checking neighbor relationships with show ip ospf neighbor. This command displays the state of adjacency with neighboring OSPF routers. The state should be "FULL" for routers sharing a common network segment, indicating they have successfully exchanged their full LSDBs. If you see states like "INIT," "2-WAY," or "EXSTART," the adjacency is still forming or has an issue.

Next, examine the LSDB with show ip ospf database. This shows the list of LSAs the router has received, providing a view of the network topology as OSPF sees it. Finally, verify that OSPF has successfully installed routes in the routing table using show ip route ospf. These routes will be marked with an "O" (for OSPF intra-area routes). For detailed information about a specific OSPF-learned route, such as its cost and next-hop, use show ip route [network].

Understanding and Manipulating the OSPF Cost Metric

OSPF uses cost to determine the best path. The default formula on Cisco routers is $Cost=\frac{10^8}{Bandwidth(inbps)}$. Therefore, a higher bandwidth results in a lower, more preferred cost. You can view an interface's OSPF cost with show ip ospf interface [interface-id].

You can influence path selection by manually configuring the cost. This is essential when the default cost does not reflect your desired traffic flow. The cost can be set in two ways:

1. Under the interface configuration: ip ospf cost [1-65535]
2. By changing the reference bandwidth globally with auto-cost reference-bandwidth [Mbps] (recommended in high-speed networks to differentiate between, for example, 10Gig and 1Gig links).

Troubleshooting Common OSPF Issues

Even with correct configuration, issues can arise. A systematic approach is key.

1. Missing or Stuck Neighbor Adjacencies: This is the most common problem. Use show ip ospf neighbor to identify the state. Common causes include:

• Mismatched MTU: Interfaces on the same subnet must have matching MTU sizes for OSPF adjacency to form. Check with show interface.
• Mismatched OSPF Parameters: Area ID, Hello/Dead intervals, and network type must match on both sides of a link. Verify with show ip ospf interface.
• Access List or Firewall Blocking OSPF: OSPF uses multicast addresses 224.0.0.5 (All OSPF Routers) and 224.0.0.6 (All OSPF DRs). Ensure these are not blocked.

1. Routes Missing from the Routing Table: If neighbors are FULL but routes are missing, check the LSDB (show ip ospf database) to confirm the LSA for the network exists. The issue may be on an adjacent router advertising the route. Also, verify that the router-id is unique; duplicates cause severe LSDB corruption.

1. Suboptimal Path Selection: If traffic is taking a slower path, verify the cumulative cost for each potential path using show ip ospf interface to see per-interface costs and traceroute to see the actual path. Remember, OSPF chooses the path with the lowest cumulative cost.

Common Pitfalls

• Incorrect Wildcard Mask in Network Statements: A common error is using a subnet mask instead of a wildcard mask in the network command (e.g., network 10.0.0.0 255.255.255.0 area 0). The correct syntax would be network 10.0.0.0 0.0.0.255 area 0. Using the interface-specific ip ospf area command avoids this pitfall entirely.
• Overlooking Passive Interfaces: Failing to configure passive-interface on LAN segments facing end-users (where no OSPF neighbors exist) wastes router CPU cycles and creates unnecessary multicast traffic on the network.
• Ignoring Duplicate Router IDs: A duplicate Router ID prevents proper LSA flooding and can lead to incomplete routing tables. Always ensure RIDs are unique, preferably by manually setting them with the router-id command.
• Misunderstanding the OSPF Network Type on WAN Links: The default OSPF network type for serial links configured with HDLC or PPP is "POINTTOPOINT," which works automatically. However, for Frame Relay or complex Ethernet WANs, you may need to explicitly configure the network type (e.g., ip ospf network point-to-multipoint) for proper neighbor discovery and adjacency.

Summary

• OSPF is a link-state protocol that uses LSAs and the Dijkstra algorithm to build a loop-free topology map and calculate the shortest path based on cost.
• The Router ID is a critical, unique identifier chosen from a manual setting, a loopback IP, or the highest physical interface IP.
• Single-area OSPF configuration is best done using the ip ospf [process-id] area [area-id] command directly on each interface for precision and clarity.
• Verification is a three-step process: check neighbor adjacency (show ip ospf neighbor), examine the topology database (show ip ospf database), and confirm routes are in the table (show ip route ospf).
• The OSPF cost is derived from bandwidth by default ($Cost=10^8/Bandwidth$) and can be manually tuned to influence path selection.
• The majority of OSPF troubleshooting revolves around failed neighbor adjacencies, typically caused by mismatched parameters, MTU, ACLs, or duplicate Router IDs.