Configuring Single-Area OSPF on Cisco Routers

The Three Core Steps of OSPF Configuration

Configuring single-area OSPF involves three primary steps, which we'll build upon using the topology below as our guide.

The fundamental steps are:

1. Enable the OSPF process on the router.
2. Establish a unique Router ID (RID) for identification.
3. Specify which interfaces will participate in OSPF and in which area.

Let's break down each step.

Step 1: Enable the OSPF Process

First, you need to "turn on" OSPF on the router. This is done from global configuration mode.

R1> enable
R1# configure terminal
R1(config)# router ospf <process-id>
R1(config-router)#

The router ospf <process-id> command initiates the OSPF routing process.

• The Process ID is a number from 1 to 65,535.
• This ID is locally significant, meaning it does not have to match on neighboring routers for them to form an adjacency. It's used by the router to distinguish between multiple OSPF processes if you were running them (which is rare). A common practice is to use the same process ID across your network for consistency.

The video below from Practical Networking demonstrates this first simple step.

Step 2: Establish the Router ID (RID)

As we learned in the last lesson, the RID is a unique 32-bit number in IP address format that identifies a router within the OSPF domain. It's crucial for functions like the DR/BDR election. A router determines its RID using the following priority order:

1. The value configured explicitly with the router-id <A.B.C.D> command. (Highest Priority - Best Practice)
2. The highest IP address of any configured loopback interfaces that are "up". (Good Practice)
3. The highest IP address of any other active, non-loopback interfaces. (Lowest Priority - Least predictable)

For a stable network, you should never leave the RID selection to chance. Best practice is to set it manually. The following reading and video demonstrate the two best ways to do this.

The following video from Jeremy's IT Lab provides a practical demonstration of using loopback interfaces to set the RID. This is a very common and effective method.

Step 3: Enable OSPF on Interfaces

This is the most critical step, where you tell the router which of its networks should be advertised and which interfaces should start sending Hello packets. There are two popular methods to achieve this.

Method 1: The network Command (Traditional)

The traditional way is using the network command within the OSPF router configuration mode.

R1(config-router)# network <ip-address> <wildcard-mask> area <area-id>

A common point of confusion is that this command does not advertise a network. Instead, it finds any interface on the router whose IP address matches the ip-address and wildcard-mask combination and enables OSPF on that interface. The network and mask configured on the interface itself are what get advertised.

• Wildcard Mask: An inverted subnet mask. A 0 means the corresponding bit in the IP address must match, and a 1 means it can be anything. For example, 0.0.0.255 means the first three octets must match. A mask of 0.0.0.0 requires an exact IP address match.

The following resources provide excellent explanations of this command.

Method 2: The Interface Command (Modern)

A more direct and often preferred method is to enable OSPF directly on the interface itself.

R1(config)# interface <interface-name>
R1(config-if)# ip ospf <process-id> area <area-id>

This command explicitly enables OSPF on the interface, assigning it to the specified process and area. It is less prone to error than wildcard masks, especially in complex networks.

The "OSPF Configuration & Show Commands" video demonstrates this method clearly.

Key Point: If you configure both methods for the same interface, the direct interface-level command (ip ospf...) takes precedence over the network command.

Let's Configure!

Now, let's apply these steps to our reference topology. We will configure R1 together, and then you can try configuring R2 and R3.

Configuration for R1:
We'll use a loopback for the RID and the traditional network command.

! Enter global configuration mode
R1# configure terminal

! Configure loopback for a stable Router ID
R1(config)# interface Loopback0
R1(config-if)# ip address 1.1.1.1 255.255.255.255
R1(config-if)# exit

! Enable OSPF process 1
R1(config)# router ospf 1

! Enable OSPF on interfaces in the 192.168.12.0/24 and 192.168.13.0/24 subnets
R1(config-router)# network 192.168.12.0 0.0.0.255 area 0
R1(config-router)# network 192.168.13.0 0.0.0.255 area 0
R1(config-router)# end

Now, try to write the configurations for R2 and R3. Use these details:

• R2: Use RID 2.2.2.2 (via a loopback) and the ip ospf 1 area 0 command on its two active interfaces.
• R3: Use RID 3.3.3.3 (via a loopback) and network commands with 0.0.0.0 wildcard masks for its two interfaces.

After applying the configurations, the routers will start sending Hello packets, form neighbor adjacencies, and exchange routes. We can quickly verify this.

Conclusion

In this lesson, we bridged the gap from theory to practice, configuring a live single-area OSPF network. You now have the essential commands to build the routing foundation for your project.

Key Takeaways:

• OSPF Configuration is a 3-step process: Enable the process (router ospf), set a stable Router ID (best done with router-id or a loopback), and enable OSPF on interfaces.
• Two methods exist for enabling interfaces:
  • The traditional network <ip> <wildcard> area <id> command, which matches interfaces based on a range.
  • The modern ip ospf <pid> area <id> interface command, which is more explicit and often preferred.
• Configuration is just the first half: Verification using commands like show ip ospf neighbor and show ip route is essential to confirm that your network is operating as intended.

In our next lesson, we will perform a deep dive into verifying OSPF configurations. We'll explore a full suite of show commands that allow you to inspect every aspect of the OSPF process, from neighbor states and database tables to interface-specific settings, giving you the skills to troubleshoot and confirm your network's health.