said by HELLFIRE:
Trying to think where a client would run MPLS and MPLS TE.... again, in my albeit limited time in networking,
haven't seen this before (thankfully).
mpls is just another mechanism of transporting packets across a network backbone. the nice thing about it is that it has nice little features that allow mp-bgp bits to be carried/honoured to allow l3vpns, etc.
mpls-te is essential when you've got traffic that needs to have dedicated throughput through points in the network. additionally -- with hooks like mpls-te frr and so -- a link loss via any sort of transport mechanism can achieve fast failover and reroute so there is minimal (if any) noticeable loss.
(edited to add)
additionally -- i strongly disagree with the authors. while all you'll need for mpls is to carry loopbacks and internal links in igp -- and you can accomplish this with 'rip' -- the difference is planning. sure -- you can run eigrp because its what you're familiar with -- but eventually, you're going to want some sort of extensible mpls-te as your cap-ex for upgrades can't keep pace with traffic levels. you're going to want to ensure that you've got te tunnels and frr where important -- at least for $mission_critical traffic. at that point -- you've got to deal with the mongolian cluster-eff that could be an igp migration -- especially as you've got a large customer-base depending on your network for connectivity.
do it right, the first time. after that -- its set and forget and you can do what you need to for years to come.
eigrp is a toy. not a protocol.
(of course, people like johnson liu (»books.google.com/books?id=fzBOZD ··· &f=false
) may have different opinions on that last statement. i'll pick his brain the next time i see him). ;-P
"...if I in my north room dance naked, grotesquely before my mirror waving my shirt round my head and singing softly to myself..."