Auto-sync: 2026-04-29 00:02
This commit is contained in:
50
wiki/concepts/Static-Routing.md
Normal file
50
wiki/concepts/Static-Routing.md
Normal file
@@ -0,0 +1,50 @@
|
||||
---
|
||||
title: "Static Routing"
|
||||
type: concept
|
||||
tags: [AWS, Networking, Routing, Transit Gateway]
|
||||
sources: [ctp-topic-18-wide-area-networking-in-aws-cloud]
|
||||
last_updated: 2026-05-07
|
||||
---
|
||||
|
||||
## Static Routing
|
||||
|
||||
静态路由(Static Routing)是指由网络管理员手动配置的固定路由条目,路由路径不随网络拓扑变化而自动更新。与之对应的是使用动态路由协议(如 BGP、OSPF)自动发现和更新路由的动态路由。
|
||||
|
||||
## Definition
|
||||
|
||||
- **配置方式**: 手动在路由器/网关中写入目的网络与下一跳的对应关系
|
||||
- **路由选择**: 固定不变,除非管理员主动修改
|
||||
- **适用场景**: 小型网络、路由路径明确且稳定的环境
|
||||
|
||||
## Limitations in AWS Transit Gateway Context
|
||||
|
||||
在 [[ctp-topic-18-wide-area-networking-in-aws-cloud]] 中描述的问题:
|
||||
|
||||
- **当前状态**: TGW 间的跨区域路由依赖静态前缀列表(Prefix Lists)
|
||||
- **缺乏动态协议**: 没有 BGP 等动态路由协议支持,无法自动感知链路故障或拓扑变化
|
||||
- **DR 场景痛点**: 灾难恢复场景下需要人工干预切换路由,无法自动收敛
|
||||
- **规模局限**: 随着 Landing Zone 数量增长,手动维护静态路由表的复杂度呈指数上升
|
||||
|
||||
## Static vs Dynamic Routing
|
||||
|
||||
| 维度 | 静态路由 | 动态路由(BGP/OSPF) |
|
||||
|------|---------|-------------------|
|
||||
| 配置复杂度 | 低(小型网络) | 高 |
|
||||
| 故障自愈 | ❌ 需人工干预 | ✅ 自动收敛 |
|
||||
| 可扩展性 | 差 | 好 |
|
||||
| 资源开销 | 低 | 高(协议开销) |
|
||||
| 适用规模 | < 10 节点 | 任意规模 |
|
||||
|
||||
## Evolution Path
|
||||
|
||||
静态路由的局限推动了向 [[SD-WAN]] 的演进——SD-WAN 通过软件控制层实现动态路径选择,即使底层 Underlay 网络仍使用静态路由,Overlay 层也能实现智能流量调度。
|
||||
|
||||
## Connections
|
||||
|
||||
- [[ctp-topic-18-wide-area-networking-in-aws-cloud]] ← 痛点 ← [[Static-Routing]]
|
||||
- [[AWS-Transit-Gateway-TGW]] ← 应用于 ← [[Static-Routing]]
|
||||
- [[SD-WAN]] ← 演进目标 ← [[Static-Routing]]
|
||||
|
||||
## Sources
|
||||
|
||||
- [[ctp-topic-18-wide-area-networking-in-aws-cloud]]
|
||||
Reference in New Issue
Block a user