networking routing ai_generated partial

OSPF: LSA age 3600 seconds reached for 10.0.0.0/24, router 192.168.1.1, flushing

ID: networking/ospf-lsa-aging

Also available as: JSON · Markdown · 中文
76%Fix Rate
84%Confidence
1Evidence
2024-11-05First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
Cisco IOS XE 17.12.1 active — — —
Juniper Junos 22.3R1 active — — —
FRRouting 9.1 active — — —
Quagga 1.2.4 active — — —

Root Cause

An OSPF Link State Advertisement (LSA) has reached its maximum age (MaxAge) of 3600 seconds, causing the originating router to flush it from the link-state database, potentially due to a flapping interface or a router that has gone down without sending a proper LSUpdate.

generic

中文

OSPF链路状态通告（LSA）已达到最大年龄（MaxAge）3600秒，导致原始路由器将其从链路状态数据库中刷新，可能是由于接口抖动或路由器在没有发送正确LSUpdate的情况下宕机。

Official Documentation

https://www.rfc-editor.org/rfc/rfc2328

Workarounds

  1. 80% success Check the interface stability on the originating router: `show ip ospf interface` and look for flapping counters; if found, replace faulty hardware or reconfigure interface parameters. 
    Check the interface stability on the originating router: `show ip ospf interface` and look for flapping counters; if found, replace faulty hardware or reconfigure interface parameters.
  2. 85% success Force the router to re-advertise the LSA by clearing the specific OSPF neighbor: `clear ip ospf neighbor 192.168.1.1` 
    Force the router to re-advertise the LSA by clearing the specific OSPF neighbor: `clear ip ospf neighbor 192.168.1.1`

中文步骤

  1. Check the interface stability on the originating router: `show ip ospf interface` and look for flapping counters; if found, replace faulty hardware or reconfigure interface parameters.
  2. Force the router to re-advertise the LSA by clearing the specific OSPF neighbor: `clear ip ospf neighbor 192.168.1.1`

Dead Ends

Common approaches that don't work:

  1. 100% fail

    The MaxAge is fixed at 3600 seconds per OSPF standard; cannot be changed without violating RFC compliance.

  2. 85% fail

    This disrupts all OSPF adjacencies and causes network-wide route flapping, making the problem worse.

  3. 90% fail

    Static routes are not propagated via OSPF LSAs and will not fix the aging issue; they may also cause routing loops.