Does anyone have any experience with using 2 MPLS carriers for load balancing. We'd like to have a primary MPLS network with ATT and then a backup MPLS network with MCI. But rather than use MCI strictly for backup we'd like to load balance traffic across both networks. Most of our bigger sites will have a connection into both clouds. Anyone have any idea how we'd handle the routing for that?
Your edge CE should be connected to both the clouds. And then its matter of load balancing on 2 equal cost paths. So what ever protocol you use you will have to ensure that both paths are seen as equal cost/best paths.
Apart from that it will be load balanced across both the clouds on its own.
So in short its like have two logical connections to the whole of you network from each edge CE persepctive.
We plan to use BGP and have 2 CE devices (Cisco 3845). Initially we thought we'd have 1 CE connect to 1 MPLS Provider, but don't know how we would we load balance. From reading the this it's an interesting concept (and may be somewhat easier to config) to have 1 CE connect to both MPLS Providers. Thoughts?
I assist in supporting an environment which might almost be identical to that you want to move into.
The first issue you might bump into is the way EBGP will prefer to always use its CE-PE link if it sees otherwise equal paths. Simple solution, divide your traffic to your CEs. We do this either by using GLBP for small sites, or via equal cost paths within the LANs routing topology to the CE routers.
Second issue you might bump into is if the AS topologies are different between the MPLS providers making AS hop counts different between sites. We addressed this issue by defining and maintaining our own logical topology that looks identical between the different MPLS providers.
Both of the prior principally perform static load balancing but if you working with 12.4 or later, you might also want to look at OER. It can dynamically load balance, either with the static techniques, above, or without them.
We also deal with the situation where two sites are not on the same provider's MPLS. (Usually the result of some problem.) For this, we leak routes between the providers at major hubs permitting traffic to transit between the providers for sites that can not be reached on the same provider.
Whatever protocol you want to use as a PE-CE protocol or you want to use 1 or 2 CE's, you may want to stick to one thumb rule, dont make any site a transit for one MPLS SP. If you stick to this rule thing s hsould be pretty much fine and you would be able to achieve your objective positvely.
(Dont create a transit meaning, when you learn routes to site x through SP_1 on CE1 interface 1 dont advertise those routes out of CE2 [or CE1 interface 2 to SP_2]) And for the load balancing out of a site use the default CEF method of per destination throughout your each site. And send the routes down from your CE with equal cost/metric to the core LAN device in each site.
This way redundancy would be maintained for that site and you would have the needed load balancing as well.
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 Engineered...
Internet security is important with the increasing attacks that are happening every day. Many internet and browsing security solutions exist, but some are not very easy to use or maybe the question is how can I enable them?
Cisco Software Manager Server
This document describes the programmatic interfaces, RESTful APIs, which are supported by Cisco Software Manager Server (CSM Server).
CSM Server supports a set of finite RESTful APIs. The fir...