I have 2 lines to MPLS cloud as following : CE1--PE1
I want to aggregate the BW on both routers , which is best way to do that , Is it better to terminate both lines on same PE routter or keep them on deferent PE router for redundancy ? and if i keep it on deferents PE's routers Is posible to do 2 TE's for load balance ?
what is the underlying issue, which leads to your request?
If you want load balancing from your site to the MPLS cloud, then normal IP routing can be used. We would need some more informations about your topology though (HSRP between CE1 and CE2, or other routers present, how many segments, etc.)
Be aware, that there is no MPLS TE on CE routers, because there is typically no MPLS but only IP (with some exceptions like CsC).
So "aggregating the BW" is an IP task from the CE side and has nothing to do with MPLS.
In an IP solution you can use existing routing protocols (which one?) to distribute traffic onto both links. Load sharing from the MPLS cloud into your site has to be implemented by your SP. You should check with the SP which options exist.
You also could use Multilink PPP between two routers (one PE and one CE), but this removes hardware redundancy.
Thanks Martin , yes in CE side I will use GLBP or MHSRP there is no issue but my concern when we get to MPLS cloud there is 2 PE routers , so if the traffic from both CE routers reach the PE routers and each PE routers get deferent route to destination and one path is faster than the other , then at the destination point it will aggregate the 2 paths with 2 deferent speed, i think this degrade the quality
the way you setup load balancing from the CEs to the MPLS cloud prevents this. As one PC will have one CE as default gateway, all the traffic from one PC will go through one path only. Thus no packet reordering will take place and no degradation should be experienced. If a PE has two pathes to a certain destination it depends on the PE load balancing implementation. With Cisco PEs the default behaviour is determined through CEF. Factory default is per destination load balancing. This also means no reordering and attached degradation issues.
Bottom line: unless the SP messes up things there should be no such issues, which you are afraid of.
This document is an early notification of a behaviour change that will be introduced in IOS XR release 6.5.
IOS XR configuration principles relevant for this article are:
On router platforms all interfaces must be by defaul...
With XR 4.2.0 the ASR9000 is releasing a new line of hardware models. This amongst others is the RSP440, the next generation RSP with faster switch fabric along with Typhoon based Linecards, the next generation network processor.
The Cisco EPN system incorporates a network architecture designed to consolidate multiples services on a single Multiprotocol Label Switching (MPLS) transport network. This network is designed primarily based on Application ...