Courseiva
DebugPrivileged EXEC

debug ip ospf events

Enables real-time debugging of OSPF event messages to troubleshoot neighbor adjacency issues, route propagation problems, or OSPF state changes.

Syntax·Privileged EXEC
debug ip ospf events

When to Use This Command

  • Diagnosing why an OSPF neighbor is stuck in INIT state
  • Investigating frequent OSPF adjacency flaps on a link
  • Troubleshooting missing OSPF routes after a network change
  • Verifying OSPF hello/dead timer mismatches between neighbors

Command Examples

Basic OSPF Event Debug Output

debug ip ospf events
OSPF: Rcv hello from 10.0.0.2 area 0 from FastEthernet0/0 192.168.1.2
OSPF: End of hello processing
OSPF: Rcv DBD from 10.0.0.2 seq 0x1D opt 0x52 flag 0x7 len 32 mtu 1500 state INIT
OSPF: First DBD and we are not SLAVE
OSPF: Rcv DBD from 10.0.0.2 seq 0x1D opt 0x52 flag 0x2 len 132 mtu 1500 state EXSTART
OSPF: NBR negotiation done
OSPF: We are the SLAVE
OSPF: Rcv DBD from 10.0.0.2 seq 0x1E opt 0x52 flag 0x1 len 132 mtu 1500 state EXCHANGE
OSPF: Exchange Done with 10.0.0.2
OSPF: Synchronized with 10.0.0.2, state FULL
OSPF: Build router LSA for area 0, router ID 10.0.0.1, seq 0x80000004

Rcv hello: Received hello from neighbor 10.0.0.2 on interface Fa0/0. End of hello processing: Hello processed successfully. Rcv DBD: Database Description packets exchanged during adjacency formation. First DBD: Indicates initial DBD received. NBR negotiation done: Master/slave role determined. We are the SLAVE: This router is slave. Exchange Done: All LSAs exchanged. Synchronized: Adjacency reached FULL state. Build router LSA: Router generates its own LSA.

Debug with Neighbor State Changes

debug ip ospf events
OSPF: Rcv hello from 192.168.1.1 area 0 from Serial0/0 10.0.0.1
OSPF: 2 Way Communication to 192.168.1.1 on Serial0/0, state 2WAY
OSPF: Send DBD to 192.168.1.1 on Serial0/0 seq 0x1A opt 0x52 flag 0x7 len 32
OSPF: Rcv DBD from 192.168.1.1 on Serial0/0 seq 0x1A opt 0x52 flag 0x2 len 132 mtu 1500 state EXSTART
OSPF: NBR negotiation done
OSPF: We are the SLAVE
OSPF: Rcv DBD from 192.168.1.1 on Serial0/0 seq 0x1B opt 0x52 flag 0x1 len 132 mtu 1500 state EXCHANGE
OSPF: Exchange Done with 192.168.1.1
OSPF: Synchronized with 192.168.1.1, state FULL
OSPF: Neighbor change event on interface Serial0/0
OSPF: DR/BDR election on Serial0/0
OSPF: We are the DR on Serial0/0

2 Way Communication: Bidirectional communication established. Send DBD: Router sends its DBD. Rcv DBD: Receives DBD from neighbor. NBR negotiation done: Master/slave resolved. We are the SLAVE: This router is slave. Exchange Done: LSA exchange complete. Synchronized: FULL state reached. Neighbor change event: A change in neighbor state triggers DR/BDR election. DR/BDR election: Election process begins. We are the DR: This router becomes Designated Router.

Understanding the Output

The debug ip ospf events output shows real-time OSPF protocol events. Key messages include 'Rcv hello' indicating receipt of hello packets, '2 Way Communication' confirming bidirectional adjacency, and state transitions like INIT, EXSTART, EXCHANGE, LOADING, and FULL. 'NBR negotiation done' means master/slave election completed. 'Exchange Done' and 'Synchronized' indicate successful LSA exchange and FULL state. 'Build router LSA' shows LSA generation. 'Neighbor change event' and 'DR/BDR election' indicate topology changes. Watch for repeated 'Rcv hello' without state progression, which may indicate timer mismatches. Messages like 'Retransmitting DBD' or 'Bad checksum' indicate errors. A healthy adjacency should quickly reach FULL state.

CCNA Exam Tips

1.

CCNA exam may ask which debug command to use for OSPF neighbor issues; 'debug ip ospf events' is the correct answer.

2.

Remember that debug commands are CPU-intensive; always use 'undebug all' or 'no debug ip ospf events' to disable.

3.

The exam might test that 'debug ip ospf events' shows hello and DBD exchanges but not LSA flooding details.

4.

Be aware that 'debug ip ospf events' does not show routing table changes; use 'debug ip routing' for that.

Common Mistakes

Leaving debug enabled on a production router, causing high CPU usage and potential crashes.

Confusing 'debug ip ospf events' with 'debug ip ospf packet' which shows packet-level details.

Not using 'terminal monitor' when debugging via Telnet/SSH, resulting in no output displayed.

Related Commands

show ip ospf interface

Displays OSPF interface parameters and status, used to verify OSPF configuration and troubleshoot neighbor relationships.

show ip ospf neighbor

Displays OSPF neighbor information to verify adjacency formation and troubleshoot OSPF neighbor relationships.

Practice for the CCNA 200-301

Test your knowledge with hundreds of CCNA practice questions covering all exam domains.

Practice CCNA Questions