# OSPF：邻居10.0.0.2卡在EXSTART状态

- **ID:** `networking/ospf-neighbor-stuck-in-exstart`
- **领域:** networking
- **类别:** network_error
- **验证级别:** ai_generated
- **修复率:** 80%

## 根因

OSPF邻居无法交换数据库描述（DBD）数据包，原因包括MTU不匹配、接口双工模式不匹配或OSPF网络类型配置错误，导致邻接关系无法从EXSTART阶段继续。

## 版本兼容性

| 版本 | 状态 | 引入 | 弃用 |
|------|------|------|------|
| Cisco IOS 15.7 | active | — | — |
| FRRouting 8.4 | active | — | — |
| Quagga 1.2.4 | active | — | — |

## 解决方案

1. ```
   Verify and set the same MTU on both interfaces: `ip mtu 1500` on both ends, or enable IP fragmentation for OSPF with `ip ospf mtu-ignore`.
   ```
2. ```
   Ensure both interfaces have the same OSPF network type: `ip ospf network point-to-point` on both sides (common fix for frame relay or Ethernet).
   ```
3. ```
   Check for duplex mismatch: use `show interfaces` to confirm both are full duplex; set with `duplex full` if needed.
   ```

## 无效尝试

- **** — This restarts the adjacency but the same issue will reoccur because the root cause (e.g., MTU mismatch) is not addressed. (90% 失败率)
- **** — The EXSTART state is not timer-dependent; it is a protocol handshake issue. Changing timers only delays the failure. (70% 失败率)
- **** — Router ID does not affect the DBD exchange process; the adjacency will still get stuck in EXSTART. (85% 失败率)