You need to use debug commands to troubleshoot an OSPF issue.
Enable OSPF debug:
debug ospf all
Clear the interface, connect/disconnect a link, or simply wait for 60 seconds. It depends on what you want to monitor.
undebug osfp allFIREWALL-A->
get dbuf stream
Review the logs.
Before you start detailed troubleshooting, look for these common sources of errors:
Checking physical connectivity
Matching network and netmask (see Recipe 16.1)
Matching MTU (see Recipe 16.1)
Compatible link type (see Recipe 16.1)
Matching area ID (see Recipe 16.4)
Check authentication and security measures (see Recipe 16.15)
Matching timers (see Recipe 16.14)
First, you need to ensure that you have physical connectivity to the neighbor. An easy way to check this is with
get interface and
ping, to see whether the interface is physically and administratively up and has connectivity to its neighbor. You may have to enable
ping on an interface with
set interface e0/0 manage ping to be able to ping. On broadcast and NBMA, every device on the segment should be able to ping any other device on the same segment. On point-to-multipoint networks, only hubs may be able to ping the spoke (and vice versa, but spokes may not be able to ping each other), and on point-to-point networks, devices may not be able to ping each other at all. Addressing on point-to-point links is optional with ...