The Lazy Networker

Establishing OSPF neighbor relationships is a critical step before routers can exchange routing information. Understanding the process and troubleshooting steps ensures a stable OSPF network.

---

1. OSPF Neighborship Process

OSPF routers must go through specific steps to establish and maintain adjacency. The process involves 7 states:

OSPF Neighbor States

State	Description
Down	No Hello packets received. This is the starting state.
Init	Hello packet received, but the router’s own Router ID is NOT listed in the neighbor’s Hello.
2-Way	Router ID is seen in the received Hello, indicating bidirectional communication. DR/BDR election occurs here in broadcast/multi-access networks.
ExStart	Routers exchange DBD (Database Description) packets to negotiate the master/slave roles for database exchange.
Exchange	Routers exchange LSA headers to identify missing or outdated information.
Loading	Routers request and exchange missing LSAs using Link-State Request (LSR) and Link-State Update (LSU) packets.
Full	Full adjacency is achieved. The routers’ LSDBs are fully synchronized.

---

2. Key OSPF Packet Types

• Hello (Type 1): Establishes and maintains neighbor relationships.
• DBD (Type 2): Summarizes LSDB information during the Exchange state.
• LSR (Type 3): Requests missing LSAs.
• LSU (Type 4): Sends updated LSAs.
• LSAck (Type 5): Acknowledges receipt of LSAs.

---

3. OSPF Neighborship Requirements (Hello Packet Parameters)

To successfully form an OSPF neighbor relationship, these parameters must match:

✅ Area ID — Must be identical on both routers.
✅ Subnet Mask — Must match on the connecting interfaces.
✅ Hello and Dead Timers — Must match (default: 10 sec Hello, 40 sec Dead on broadcast networks).
✅ Authentication — Must match if configured.
✅ Stub Area Flag — Must match for routers within a stub area.
✅ MTU (Maximum Transmission Unit) — Should match to avoid DBD exchange issues.
✅ Router IDs — Each router must have a unique Router ID.

---

4. OSPF Troubleshooting Steps

If OSPF neighbors fail to establish, follow these steps:

🔎 Step 1: Check Interface Status

• Use show ip ospf interface to confirm the interface is up and participating in OSPF.

🔎 Step 2: Verify OSPF Configuration

• Use show running-config | section router ospf to review OSPF settings.
• Ensure correct:
  • Router ID
  • Network statements
  • Area assignments

🔎 Step 3: Check Hello and Dead Timers

• Use show ip ospf interface <interface> to confirm matching timers.

🔎 Step 4: Examine OSPF Neighbor State

• Use show ip ospf neighbor to identify the current state.
• Common issues based on state:
  • Stuck in INIT/2-WAY: Mismatched Hello parameters.
  • Stuck in EXSTART/EXCHANGE: MTU mismatch or corrupted DBD packets.
  • Stuck in LOADING: Missing or incomplete LSAs.

🔎 Step 5: Verify Area and Subnet Configuration

• Use show ip ospf database to check for mismatches in the Area ID or Subnet Mask.

🔎 Step 6: Inspect Authentication

• Use show ip ospf interface to confirm authentication settings if configured.

🔎 Step 7: Investigate Network Layer Issues

• Ensure IP connectivity using ping and traceroute.

---

5. Common OSPF Issues and Solutions

Issue	Solution
Stuck in DOWN state	Check IP connectivity and interface status.
Stuck in INIT state	Verify Hello timer, area ID, and network type.
Stuck in 2-WAY state	DR/BDR election issue; verify priority settings.
Stuck in EXSTART state	Check for MTU mismatch on both routers.
Stuck in LOADING state	Inspect LSDB using show ip ospf database.
Router ID Conflict	Ensure each router has a unique Router ID.

---

6. Useful OSPF Commands for Troubleshooting

✅ show ip ospf neighbor — Displays OSPF neighbor status.
✅ show ip ospf interface — Shows OSPF parameters like timers, priority, etc.
✅ show ip ospf database — Displays LSDB details.
✅ debug ip ospf hello — Useful for diagnosing Hello packet issues.
✅ debug ip ospf adj — Monitors the OSPF adjacency process.

---

7. Example Scenario (Common Issue – MTU Mismatch)

Symptom: OSPF stuck in EXSTART state.
Solution:

1. Use show ip ospf interface to check MTU values.
2. If there’s a mismatch, adjust the MTU value on one of the routers:

Router(config-if)# ip mtu 1500