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

- **ID:** `networking/ospf-lsa-aging`
- **Domain:** networking
- **Category:** routing
- **Verification:** ai_generated
- **Fix Rate:** 76%

## 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.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| Cisco IOS XE 17.12.1 | active | — | — |
| Juniper Junos 22.3R1 | active | — | — |
| FRRouting 9.1 | active | — | — |
| Quagga 1.2.4 | active | — | — |

## Workarounds

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.** (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.
   ```
2. **Force the router to re-advertise the LSA by clearing the specific OSPF neighbor: `clear ip ospf neighbor 192.168.1.1`** (85% success)
   ```
   Force the router to re-advertise the LSA by clearing the specific OSPF neighbor: `clear ip ospf neighbor 192.168.1.1`
   ```

## Dead Ends

- **** — The MaxAge is fixed at 3600 seconds per OSPF standard; cannot be changed without violating RFC compliance. (100% fail)
- **** — This disrupts all OSPF adjacencies and causes network-wide route flapping, making the problem worse. (85% fail)
- **** — Static routes are not propagated via OSPF LSAs and will not fix the aging issue; they may also cause routing loops. (90% fail)