Hi,
this looks like an integer overflow and could be a bug. SPF will never
run with minus timer and I wonder which condition will trigger this.
What versions are your running?
I would start with
debug ospf <spf, adj, bfd, error)
show cpu-utilization detail | include ospf
show ip os neighbor
and maybe try and set different timers and then restart the router?
E.g.
router ospf
timers throttle spf 5 1000 90000
Jörg
On 2 Aug 2017, at 16:06, Pave Lunin wrote:
Hi,
Any ideas, what "Next SPF run wait" actually means in the following
output? It is a large negative value which is increasing by absolute
value (will never reach zero).
It looks like it never runs SFP as the box doesn't install new routes.
I see that it learns the LSAs but it never uses them as routes: show
ip routes / show ip ospf routes don't show theses routes, while I see
the corresponding LSAs in the OSPF DB. All the neighbor state
machinery works well. But active routes are never updated even if an
interfaces and a corresponding neighbor fail.
SSH@CER#show ip ospf
OSPF Version Version 2
Router Id 10.x.x.x
ASBR Status No
ABR Status No (0)
Redistribute Ext Routes from
Initial SPF schedule delay 0 (msecs)
Minimum hold time for SPFs 0 (msecs)
Maximum hold time for SPFs 0 (msecs)
**Next SPF run wait (msecs) -177170950**
External LSA Counter 0
External LSA Checksum Sum 00000000
Originate New LSA Counter 89
Rx New LSA Counter 3260
External LSA Limit 14447047
Database Overflow Interval 0
Database Overflow State : NOT OVERFLOWED
RFC 1583 Compatibility : Enabled
NSSA Translator: Enabled
Nonstop Routing: Disabled
Graceful Restart: Disabled, timer 120
Graceful Restart Helper: Enabled
BFD: Enabled
I checked other NetIron boxes (CERs and MLXes) but this line is just
not present in the output.
We saw this behavior on another CERs, fixed this by a reboot.
Unfortunately I don't have "show ip ospf" before the reboot from those
boxes, now this line (Next SFP run wait) is just not present on the
rebooted boxes.
Looks like a bug, but maybe I am missing something. Can't it be
something like SPF throttling and maybe there is a way to clear this
state less disruptively? On the other hand, "clear ip ospf all" did
not help yesterday.
\--
Kind regards,
Pavel
_______________________________________________
foundry-nsp mailing list
[email protected]
http://puck.nether.net/mailman/listinfo/foundry-nsp
