I’ve had an interesting discussion with Nicolas who optimized my OSPF neighbor loss EEM applet assuming the OSPF-5-ADJCHG message reports only OSPF neighbor state transitions from DOWN to FULL and from FULL to DOWN. I knew I'd seen stranger messages in my lab and was able to produce these ones after fumbling with OSPF configurations of two routers connected with a serial link:
*19:34:42.765: %OSPF-5-ADJCHG: Process 1, Nbr 10.0.1.1 on Serial1/0 from → EXSTART to DOWN, Neighbor Down: Too many retransmissions *19:35:42.773: %OSPF-5-ADJCHG: Process 1, Nbr 10.0.1.1 on Serial1/0 from → DOWN to DOWN, Neighbor Down: Ignore timer expired
The messages are repeated approximately every three minutes (using the default OSPF timers).
Here's the challenge: what was going on and how was I able to produce these messages?

MTU Mismatch
ReplyDeletedbd packets are being filtered/dropped for some reason such as:
ReplyDeletemtu mismatch.
access-list if you block unicast OSPF between the boxes you'll get exactly the symptoms ...
Hay,
ReplyDeleteToo many retransmissions - buggy line
Neighbor Down: Ignore timer expired - ospf message-digest-key is configured only one side
-jumbo
There is hidden "ignore" timer. If neighbor do something wrong its ignored for period of that timer.
ReplyDeleteHow too reproduce this: on one of two routers connected by Ethernet interfaces filter unicast (but not multicast) packets of ospf protocol in both directions - routers will periodically establish two-way adjacency, but they can't exchange their databases...
MTU mismatch prevent establishing adjacency
ReplyDeletesol
1-(config)#system mtu routing "mtu_value"
or
2-(config-if)#ip ospf mtu ignore
Zico
I don't know how you did it, but I'm trying to work an OSPF relationship between a Juniper and a Cisco Router, and I keep getting the following
ReplyDelete%OSPF-5-ADJCHG: Process 1, Nbr xxx.xxx.xxx.xxx on VlanXXX from EXCHANGE to DOWN, Neighbor Down: Too many retransmissions
%OSPF-5-ADJCHG: Process 1, Nbr xxx.xxx.xxx.xxx on VlanXXX from DOWN to DOWN, Neighbor Down: Ignore timer expired
MTU mismatch ignored & oversized packet lost by one of the routers:
ReplyDeletehttp://blog.ioshints.info/2009/11/ip-ospf-mtu-ignore-is-dangerous-command.html
Thank`s!!!
ReplyDeleteI get the same message even though the MTUs on both sides are the same. What more can be wrong, if the MTU missmatch is not the case???
ReplyDelete