We have an 8-site VPLS WAN we are turning up, and I would like to use BGP to route across it instead of EIGRP which is used on the legacy WAN. I've gathered that this is generally a Good Idea and we've had flapping issues with EIGRP in the past.
However, I'm internally debating whether to use eBGP or iBGP across the VPLS links and I'm soliciting your advice on the subject.
My current thoughts:
- Currently, the routes will be redistributed into EIGRP which runs on the core of each site. However, the long-term plan is to migrate to a primarily BGP solution everywhere mostly for vendor compatibility.
- While building a full iBGP mesh among 8 peers is a bit of work, it's a one-time config and we don't expect any growth in this particular WAN.
- I'm a little concerned that eBGP will increase the latency when a route goes down as each route is advertised by all peers, instead of only the originating peer.
- This WAN serves as a redundant link for an existing VPLS service over which our core EIGRP is extended. The last phase of this turn-up is to migrate the existing VPLS WAN from EIGRP to BGP--so there will be 16 total peers: 2 at each site, 8 on each VPLS circuit. Those two routers at each site will not communicate via BGP (until the "someday" all-BGP project happens) just inject equal-cost routes into EIGRP.
Thanks for whatever ideas, comments, or advice you have.
No comments:
Post a Comment