We have a WAN with about 15 locations, soon to expand to 30. There's an old Metro Ethernet cloud connecting 11 of them, with routers running EIGRP with each other. We want to replace that with two VPLS/Metro Ethernet clouds. This means each location needs two WAN interfaces--kind of tough since most of the routers have only two interfaces, one for LAN and one for WAN.
For a while there I thought I was being very clever with a design that puts the routing on Layer 3 switches, and that's how I set up the first remote location: no router, just a Catalyst 3850 talking to another 3850 back in one of the hubs. Static routes to start with, worked fine.
Now I'm trying to teach the 3850s EIGRP, and they seem fine with it, except they don't want to be anything but stub routers. (Just like it says in the docs.) So if I want my remote locations to switch intelligently between two paths to anything but the next hop, I'm going to have to find another routing protocol. Just when I was actually starting to like EIGRP ....
I'll go read the docs like I should, but does anyone have an opinion/recommendation, like OSPF, BGP, IGRP, or stop futzing around with L3 switches and start buying routers?
Thanks.
For a while there I thought I was being very clever with a design that puts the routing on Layer 3 switches, and that's how I set up the first remote location: no router, just a Catalyst 3850 talking to another 3850 back in one of the hubs. Static routes to start with, worked fine.
Now I'm trying to teach the 3850s EIGRP, and they seem fine with it, except they don't want to be anything but stub routers. (Just like it says in the docs.) So if I want my remote locations to switch intelligently between two paths to anything but the next hop, I'm going to have to find another routing protocol. Just when I was actually starting to like EIGRP ....
I'll go read the docs like I should, but does anyone have an opinion/recommendation, like OSPF, BGP, IGRP, or stop futzing around with L3 switches and start buying routers?
Thanks.