debug ospf packet hello detail
This command displays the full content of the hello packets exchanged between the peers.
Verify that there are no parameter mismatches. For example, the hello interval and dead
interval must match on both neighbors.
OSPF Neighbor in 2-way state
If the neighbor is in a 2-way state, it is not a cause for concern. On a broadcast network, full
adjacency is maintained only with the DR and the BDR. Other OSPF adjacencies remain in
the 2-way state.
OSPF Neighbor in Exstart or Exchange state
Neighbors exchange DBD packets in this state. MTU mismatch can cause neighbors to get
stuck in this state.
The following debug option can be used to display the DBD packet exchanges:
debug ospf packet dd detail
By default, the Avaya VPN router sends 1500 as the MTU in database description packets.
However,
the Secure Router default tunnel MTU is 1420 bytes. As a result, one of the following
changes is required on the Secure Router OSPF settings:
• Set OSPF MTU to 1500
interface/tunnel toNVR# ip ospf mtu 1500
• Set OSPF to ignore MTU mismatch
interface/tunnel toNVR# ip ospf mtu-ignore
The following table describes the source of some additional OSPF adjacency problems, and
the appropriate command to diagnose the problem.
Reason for OSPF Adjacency Problem Commands to Diagnose
OSPF is not configured on one of the
routers.
show ip ospf
OSPF is not enabled on an interface where
it is needed.
show ip ospf interface
OSPF HELLO or Dead timer interval values
are mismatched.
show ip ospf interface
IP OSPF network-type mismatch on the
adjoining OSPF interfaces.
show ip ospf interface
MTU mismatch between neighboring
interfaces.
show interface <intType>
<intNum>
show system jumbo-mtu-limit
OSPF area-type is stub on one neighbor, but
the
adjoining neighbor in the same area is not
configured for stub.
show running-config
show ip ospf interface
Troubleshooting RIP over GRE/IPIP tunnels
Troubleshooting August 2013 225
To Next Page
Loading...
