OSPF debug commands
OSPF global debug commands
debug ospf packet This debug command can be used to verify
if the two routers are successfully
exchanging OSPF control packets or not. It
helps debugging the OSPF adjacency if it is
failing
due to a mismatch or misconfiguration
of protocol settings at the OSPF endpoint
routers. Sub options of this command can be
used to selectively enable debugging for
some of the OSPF protocol packets.
debug ospf ifsm
and
debug ospf nfsm
Use these debug commands to debug
adjacency related issues. These commands
will display the information about the
interface state machine (ifsm) or neighbor
state machine (nfsm). If adjacencies are
stuck in some state for longer than expected
duration, then these options help to debug
and find the cause.
debug ospf route This debug command can be used to debug
issues in routing calculations. For example:
if the adjacency has reached the Full state,
but an expected route in the router is missing
in the routing table. In this case, the route
calculation can be traced using this option
OSPF interface-level debug command
configure/interface/tunnel <tunnel-name># ip ospf debug packet
This
debug command can be used to enable debugging of OSPF protocol packets on selected
interface. Sub options of this command can be used to selectively enable debugging for some
of the OSPF protocol packets.
Common OSPF problems
The following sections describe some common OSPF routing problems and potential
solutions.
OSPF Neighbor in INIT State
If
two-way communication is not established by the neighbors, the following debug option can
be used to display the hello packet and its contents:
Troubleshooting security
224 Troubleshooting August 2013
Comments? infodev@avaya.com
To Next Page
Loading...
