Why need EBB? Inter-DC traffic growth is much faster than internet egress traffic and WAN technology evolution.
What needed for the new EBB?
- Incremental deployment of software features. 不是一步到位,而且可以roll back.
- NO RSVP-TE, because of inefficiency and complexity. 嗯,锤!
- Use MPLS SR so network state lean. 这倒是真的,SR分离CP和Local segment management.
- Use DC network ideas
- Small routing table - on the order of K routes
- 4 planes.
- 3 Steps:
- IGP + full-mesh iBGP for packet forwarding
- TE + controller
- OPEN/R to replace IGP
- Components:
- 3 server-side:
- SFlow - read
- BGP route injector - write
- Controller - think
- 2 device-side:
- Open/R = IGP
- SR = forwarding
- 还有clean fault domain splitting, 这是咋做的?
- Hybrid approach: centralized controller + SR, best way
- path computation is at central level with global view
- network failure is handled at distributed level.
- Open/R
- how to open/R on arista devices?
- Traffic estimator:
- SFlow, need src/dst pair
- what is the sample rate? 1 of 1000? how accurate
- LSP agent:
- With thrift-based API (eapi on eos) to program hw
- In future? need failure detection and fails over within hundreds of msec.
Next step:
- per-service model
- scheduler for bulk transfer
No comments:
Post a Comment