Symptom/Cause | Solution |
---|---|
OSPF not enabled on the interface or the corresponding interface is down. | Use network command to enable ospf on a particular network address. Do “no shutdown” on the corresponding interface. Use these commands: show ip ospf interface show ip ospf show running-config ospf show ip ospf neighbor show ip ospf neighbor detail |
OSPF Interface network address mismatch or subnet mask mismatch | Use these commands to find the output/find the mismatch: show ip ospf interface show ip interface brief show running-config ospf show ip ospf neighbor show ip ospf neighbor detail. |
Hello packet attribute mismatch I.e. interface hello interval or dead interval mismatch | Use these commands to find the output/mismatch: show running-config ospf show ip ospf interface debug ospf nfsm debug ospf packet hello detail |
OSPF interface configured as passive interface. Passive interfaces will not send hello packets. | Use these commands: show ip ospf interface show ip ospf show running ospf |
OSPF option field mismatch i.e. Ospf External Routing Capability mismatch due to stub area mismatch. | Configure same stubby-area. Use these commands: debug ospf packet hello show ip ospf show running ospf |
OSPF gets struck in two-way state when there is no DR/BDR elected i.e. both routers configured with priority 0 | One router should be configured with a priority other than 0. Use these commands: show ip ospf neighbor show running ospf |
OSPF can get stuck in Exstart/exchange state when the maximum transmission unit (MTU) do not match | Use these commands: show ip ospf interface show running ospf show ip ospf neighbor |
OSPF network type mismatch can cause timers (hello-interval) mismatch | Use these commands: show ip ospf interface debug ospf packet hello show running ospf |
Symptom/Cause | Solution |
OSPF same router-id and loopback address | Use these commands: show ip ospf show running-config ospf show ip ospf interface |
OSPF area mismatch for virtual-link | Use these commands: show running-config ospf show ip ospf virtual-link |
OSPF virtual-link router-id mismatch causing virtual-link down | Use these commands: show running-config ospf show ip ospf virtual-link show ip ospf interface show ip ospf neighbor |
OSPF not enabled on the interface or the corresponding interface is down causing vlink down | Use these commands: show ip ospf show running-config ospf show ip ospf virtual-link show ip ospf interface |
Symptom/Cause | Solution |
OSPF Multi-Area Adjacency happens only if the adjacency over the primary link is up. | Use these commands: show ip ospf neighbor show ip ospf interface |
Multi-area configuration mismatch, such as area-id or process-id mismatch. | Use these commands: show running-config show ip ospf multi-area-adjacencies show ip ospf neighbor |
Multi-Area link remains down, if the Router is not an "ABR" | Use these commands: show ip ospf show ip ospf multi-area-adjacency. |
Multi-Area link will be removed if the primary link is down | Use these commands: show running-config show ip ospf interface show ip ospf multi-area-adjacency |
For multi access networks, it is required to specify the neighbor's interface address. Multi-area configuration mismatch such as when the neighbor's address does not match any of the OSPF networks or the neighbor’s address is incorrect. | Use these commands: show running-config ospf show ip ospf multi-area-adjacency |
Multi-area adjacency not applicable for the area on which virtual-link is enabled and vice-versa. | Use this command: show running-config ospf |
Symptom/Cause | Solution |
---|---|
Daemon restarted after maximum router dead interval of all OSPF interfaces on restarting node | Use this command on restarting node: show ip ospf interface |
Capability mismatch between restarting and helper node | Enable capability lls in router node. Use these commands on both nodes: show ip ospf show running-config ospf |
Configurations not saved before restart | Use any one of these commands and check the saved file in /usr/local/etc: write <file_path> write file write memory write terminal |
Two routers on same segment get restarted at same time | Use these commands on restarting node: debug ospf nfsm debug ospf packet hello recv detail show ip ospf neighbor |
Helper router got its LSDB changed while helping | Use these commands on restarting node: debug ospf nfsm debug ospf packet hello recv detail show ip ospf neighbor |
“Resync timeout timer” is not sufficient to sync the whole database | Use these commands on restarting node: debug ospf nfsm show ip ospf neighbor |