# OSPF: LSDB overload detected, max LSA limit (10000) reached on area 0.0.0.0, dropping new LSAs

- **ID:** `networking/ospf-lsdb-overload`
- **Domain:** networking
- **Category:** routing
- **Verification:** ai_generated
- **Fix Rate:** 88%

## Root Cause

The OSPF Link State Database (LSDB) has exceeded the configured maximum number of Link State Advertisements (LSAs) due to route flapping or a misconfigured router injecting excessive routes, causing the router to drop new LSAs and potentially corrupt the routing table.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| Cisco IOS 15.9(3)M | active | — | — |
| Juniper Junos 22.2R2 | active | — | — |
| FRRouting 8.4 | active | — | — |

## Workarounds

1. **Identify the source of excessive LSAs using 'show ip ospf database' and 'show ip route ospf' to find flapping routes, then configure route summarization or set a route filter to limit the number of redistributed routes.** (90% success)
   ```
   Identify the source of excessive LSAs using 'show ip ospf database' and 'show ip route ospf' to find flapping routes, then configure route summarization or set a route filter to limit the number of redistributed routes.
   ```
2. **Configure OSPF stub area or totally stubby area on the affected area to reduce LSA flooding: area 0.0.0.0 stub no-summary** (85% success)
   ```
   Configure OSPF stub area or totally stubby area on the affected area to reduce LSA flooding: area 0.0.0.0 stub no-summary
   ```
3. **Temporarily increase the max LSA limit to 15000 while investigating: router ospf 1; max-lsa 15000; then set a timer to revert after 24 hours.** (75% success)
   ```
   Temporarily increase the max LSA limit to 15000 while investigating: router ospf 1; max-lsa 15000; then set a timer to revert after 24 hours.
   ```

## Dead Ends

- **** — This only masks the problem; if the LSA flood is due to a misconfiguration or attack, the LSDB will eventually exceed the new limit and cause memory exhaustion. (80% fail)
- **** — The LSDB will be rebuilt from neighbors after reboot; if the underlying issue (e.g., route flapping) is not fixed, the overload will recur quickly. (85% fail)
- **** — This causes a complete network outage and does not address the LSA source; the overload will return once OSPF is re-enabled. (90% fail)