Might depend more on your size than anything. MPLS in my small network is still great, but does add some complexity when setting up new endpoints and for debugging.
I don't use TE yet, but it works well if you have the right equipment. Could be less work in the long run since you can just open up a VPLS endpoint anywhere you have it implemented and add the port to the subnet. That way you could keep routing to the core and just extend vpls endpoints to the IP routes, and let MPLS handle the layer2 style routing automagically over a straight forward OSPF routed core. -----Original Message----- From: Af [mailto:[email protected]] On Behalf Of Dev Sent: Sunday, February 12, 2017 5:31 PM To: [email protected] Subject: [AFMUG] MPLS for non-redundant paths If I have a hub-and-spokes topology I want to do some traffic engineering on to avoid congestion, is there an advantage to MPLS over just using separate subnets to ease congestion if I don’t have multiple redundant paths that I need to be able to route around? I understand there is advantages if you have multiple paths to the endpoint, but this wouldn’t be the case here. I also would like to move routing out closer to the edge. What are the real benefits of MPLS in either case?
