Tuesday, August 14, 2018

MPLS VPN Internal Routing Input. RFC6368/4456?

Have a customer with about 100 sites on an AT&T full-mesh layer 3 MPLS.

The routing is a mess, lots of RIP/OSPF redistribution into the BGP and back, tons of unnecessary static routes. They want some better redundancy and traffic planning as well as have a SDWAN transition plan, so Phase 1 is getting rid of AT&T cisco managed routers onsite they're unnecessarily paying a ton for and connect their CPEs direct to the MPLS. All devices are modern Fortinet CPEs.

Looking for input on the MPLS internal routing, I've typically either done an eBGP private AS per site or done a single eBGP AS with AllowAS-in, however I've recently been reading RFC6368 and RFC4456 (iBGP with route reflection) and it seems like a great solution. The equipment is compatible so does anyone have any comments or feedback, or maybe another style that I haven't thought of?

Also aware of potentially doing an SDWAN overlay with the Fortinets but that comes down the road a bit, they have the heebie-jeebies about it after being burned in a pilot implementation by another vendor even though it works fine.



No comments:

Post a Comment