Debugging OTN Router OSFP

Use OSPF debug commands to monitor neighbor states, packet exchanges, and LSDB updates while checking for mismatched parameters or interface issues.Step 1: Verify Basic ConnectivityBefore debugging OSPF, ensure that interfaces are up and IP addressing is correct. OSPF will not form adjacencies if Layer 3 connectivity is missing. Use commands like show ip interface brief to confirm interface status and IP configuration .Step 2: Check OSPF Neighbor StatesOSPF neighbors progress through states: Down → Init → 2-Way → ExStart → Exchange → Loading → Full. If a neighbor is stuck in any state other than Full (or 2-Way for non-DR/BDR routers), troubleshooting is required. Common causes include mismatched hello/dead intervals, MTU mismatches, or network type mismatches .Step 3: Use Debug CommandsEnable OSPF debugging to capture real-time events:Neighbor state transitions: debug ospf packet hello recv debug ospf eventLSA and SPF events: debug ip ospf lsa debug ip ospf spf Tips for production environments:Redirect debug output to a log file or buffer to avoid overwhelming the terminal .Use ACLs or filters to limit debug output to specific neighbors.Disable debugging immediately after capturing relevant information .Step 4: Analyze Debug OutputLook for common issues in the debug logs:Mismatched hello parameters → check subnet mask, hello/dead intervals .No output at all → indicates connectivity issues or ACL blocking OSPF multicast (224.0.0.5).MTU mismatches → can prevent adjacency; either match MTUs or use mtu-ignore temporarily .Network type mismatches → point-to-point vs broadcast can affect route exchange even if adjacency forms .Step 5: Verify LSDB and Routing TableOnce adjacency is established, confirm that LSAs are installed in the LSDB and routes appear in the routing table:show ip ospf databaseshow ip route ospf This ensures that OSPF is correctly propagating routes across the network .Step 6: Reset OSPF Process if NeededIf misconfigurations persist or changes need to be applied quickly, you can reset the OSPF process:clear ip ospf process (Cisco)exec router clear ospf process (Fortigate) Warning: This deletes all OSPF routes temporarily, so use with caution .SummaryEffective OSPF debugging on OTN routers involves:Confirming interface and IP connectivity.Checking neighbor states and parameter consistency.Using targeted debug commands to capture hello packets, LSAs, and SPF events.Analyzing debug output for mismatches or blocked packets.Verifying LSDB and routing table entries.Resetting the OSPF process if necessary. Following these steps ensures that OSPF adjacencies form correctly and routes are exchanged reliably.