1 / 4

Simplified Virtual Aggregation Configuration for Efficient Routing

This system simplifies VA router configurations by focusing on APRs and partial ASBRs. It allows easy VP changes without altering all routers, distinguishing VP-range from VP-list. Pop-prefix-list configures on partial ASBRs, streamlining FIB installation. Configure ASBRs connected to peer or provider ASes, leveraging VP-range concept for efficient addressing. Tag routes selectively within VP-range, ensuring APRs handle sub-prefixes efficiently, while non-APRs exclude suppressed tags. Applies to all routers for comprehensive, effective routing setup. Consider an informational RFC for further understanding.

chiquita-clayton
Télécharger la présentation

Simplified Virtual Aggregation Configuration for Efficient Routing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. VA-auto • Goal: make the VA configuration simpler • Don’t need to make configures on all VA routers. • Only APRs and partial ASBRs. • Don’t need to change the configurations on all VA routers when the VPs change. (e.g., VP add/del/split/merge). • VP-range vs VP-list • Don’t need to make much configuration on all VA routers. • Configure pop-prefix-list on partial ASBRs.

  2. How to know what to FIB-install? • Configure ASBRs which are connected to peer ASes or provider ASes with “VP-range” • VP-range: ranges of addresses covered by all configured VPs, eventually a single 0/0 entry. • Those ASBR tag routes within VP-range with “can suppress” tag • Non-transitive Extended Community Attribute. • Exception: VP routes are never tagged. • May also not tag other routes according to policy, for instance customer routes, high-volume routes.

  3. Selective FIB Installation • APRs must FIB-install sub-prefixes within their own corresponding VPs regardless of the “can-suppress” tag. • Non-APRs don’t need to FIB-install the sub-prefixes with “can-suppress” tag. • All routers need to FIB-install the prefixes without the “can-suppress” tag as normal. • Including VP routes, popular-prefix routes and those routes for prefixes which are not covered by the VPs.

  4. Next Step • Last call for an informational RFC?

More Related