Debugging the Optical Core Router OSFP

Use targeted OSPF debug commands to monitor hello packets, neighbor states, and LSDB changes while verifying interface and area configurations to identify routing issues.

Step 1: Verify OSPF Configuration

Before enabling debug, ensure OSPF is correctly configured on all relevant interfaces:

• Use show ospf interface (Junos) or show ip ospf interface (Cisco) to confirm OSPF is running on the intended interfaces and assigned to the correct areas .
• Check neighbor relationships with show ospf neighbor to ensure each router has the expected adjacencies and that neighbor states reach Full. States like Init, 2-way, or Down indicate potential misconfigurations or connectivity issues .
• Verify the OSPF routing table contains expected entries and that the designated router (DR) and backup DR addresses are correct .

Step 2: Enable Targeted Debugging

Debugging provides real-time visibility into OSPF operations:

• On Cisco, use debug ip ospf hello to monitor hello packet exchanges and detect mismatched parameters such as network masks or timers .
• On FRR or similar platforms, use debug ospf packet hello recv detail and debug ospf event to capture neighbor state transitions and SPF recalculations .
• For Nokia 7210 SAS routers, debug commands can target specific OSPF instances, areas, interfaces, LSDB types, or CSPF calculations . Best Practices:
• Redirect debug output to a log file or buffer to avoid overwhelming the terminal .
• Apply filters or ACLs to limit debug output to specific neighbors or interfaces.
• Disable debugging immediately after capturing the necessary information using no debug ospf all or undebug all .

Step 3: Analyze Debug Output

• Look for mismatched hello parameters, which prevent adjacency formation (e.g., subnet mask or hello/dead interval mismatches), .
• Monitor LSA flooding and SPF recalculation events to detect routing loops or convergence delays .
• Check for link flaps or Layer 2 issues; if proxy ARP is enabled, disable it and clear the ARP cache to prevent OSPF instability .

Step 4: Troubleshoot Common Issues

• Adjacency failures: Ensure interface IPs, area IDs, and hello/dead timers match on both ends .
• Routing table inconsistencies: Verify LSDB synchronization and check for missing or stale LSAs .
• High CPU due to debug: Use selective debugging and avoid running debug commands on production routers without proper logging .

Step 5: Continuous Monitoring

• Use periodic show ospf neighbor and show ospf database commands to monitor OSPF health.
• Consider automated scripts or event managers (e.g., Cisco EEM) to detect and log link flaps or adjacency changes . By following these steps, you can systematically debug OSPF on an optical core router, identify misconfigurations, and ensure stable routing across your network.