40 likes | 191 Views
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
E N D
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.
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.
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.
Next Step • Last call for an informational RFC?