networking:clos
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| networking:clos [2026/04/07 10:45] – [QoS] v1ctor | networking:clos [2026/04/07 13:26] (current) – [ROUTING] v1ctor | ||
|---|---|---|---|
| Line 44: | Line 44: | ||
| - Reduced throughput — TCP's congestion control reacts too late because loss signals are delayed. | - Reduced throughput — TCP's congestion control reacts too late because loss signals are delayed. | ||
| - Jitter — unpredictable queue depths cause variable RTTs. | - Jitter — unpredictable queue depths cause variable RTTs. | ||
| + | |||
| + | |||
| + | ==== ROUTING ==== | ||
| + | |||
| + | There are three main designs: | ||
| + | - iBGP underlay and eBGP overlay | ||
| + | - Spines and Super-spines are in iBGP domain | ||
| + | - Each leaf has its unique ASN assigned | ||
| + | - Leaves establish multi-hop eBGP with each other | ||
| + | - eBGP underlay and iBGP overlay (Juniper way) | ||
| + | - All leaves share the same ASN | ||
| + | - Spines and super-spines are connected using eBGP | ||
| + | - Leaves are connected using iBGP | ||
| + | - eBGP for both | ||
| + | |||
| + | |||
| + | BGP convergence challenges: | ||
| + | - Path hunting | ||
| + | - Over-flooding | ||
| + | |||
| + | Solutions: | ||
| + | - Valley-free routing - make sure leaves are non-transit routers. One of the solutions is to apply outbound AS-path filter allowing only '' | ||
| + | |||
| + | BGP Tuning options: | ||
| + | - MRAI (Min route advertisement interval) | ||
networking/clos.1775558751.txt.gz · Last modified: by v1ctor
