On Jan 24, 2014, at 12:41 PM, Raymond Burkholder <r...@oneunified.net> wrote:
>> >> Some networks I have worked with took the average latency of each link and >> assigned that (with some constant multiple) as the interface cost. >> >> Of course this all fails miserably if you are using anything like MPLS >> underneath your OSPF. >> > > But then when using MPLS underneath, then MPLS Traffic Engineering can be > used to do some interesting path computations and resiliency configurations. I wasn’t attempting to promote or discourage use of MPLS. I was merely endeavoring to point out that in an MPLS world, OSPF costs are not how you want to manage your traffic. Owen
