Unequal Load Balancing Question on two mpls circuit

Unanswered Question
Jul 12th, 2007
User Badges:

hello all,

On our headquarter we have two mpls circuit. one 9mbps atm and 1 t1. Both circuit connects to all of our branch offices. Also both are setup on two different routers. My question is, can I setup load balancing even though both of my circuit are setup on different routers.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Richard Burts Thu, 07/12/2007 - 08:25
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN

Gerald


To really answer that question we would need to know a bit more about the topology of your network. Each of the routers with an MPLS circuit would almost certainly prefer their own connection and not load balance. For other routers in the network it might be possible to configure them to see both routes as equal and to load balance. It wold be difficult to do and if you do it I think that you will not be happy with the results. If you configure both routes to look equal then it will attempt to send equal amounts of traffic over both links. The result will be that your 9mbs circuit will be throttled back to T1 performance.


My suggestion is to configure them for redundancy and fail over but not to attempt load balance.


HTH


Rick

pgrama0124 Thu, 07/12/2007 - 08:36
User Badges:

Thanks Rick,

I would hate to see the t1 circuit not being used but your point do make a lot of sense. for redundancy to work. Do I need to setup both circuit on one router? Or it can be on different router?

Richard Burts Thu, 07/12/2007 - 08:45
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN

Gerald


For redundancy to work they can be on different routers. The details of how to do it would vary depending on whether you are using a dynamic routing protocol (different protocols would have different implementation details) or using static routes. But for redundancy you want each of the routers with the MPLS circuit to be seen as potential ways to get to the remote destinations and you want the route through the higher bandwidth connection to look more favorable.


I understand your point about not wanting the T1 to be un-used. One alternative to consider would be to implement some Policy Based Routing which would identify some type of traffic (perhaps all FTP traffic, or perhaps traffic from a particular subnet, or some other particular identifiable traffic) and route it specifically over the T1. This would give some use of the T1 without getting into the issues of load balancing.


HTH


Rick

pgrama0124 Thu, 07/12/2007 - 13:42
User Badges:

Thanks again Rick, you are giving me a lot of valuable information. I got another newbie question for you. when I do a traceroute from the router that has the t1 to a branch office, it doesn't travel out on the serial connection, instead it goes to the fastethernet and goes to the 9mbs circuit. I believe its because we are running eigrp protocol. Do you have any recommendation on how to make your recommedation work?

Thanks

Richard Burts Thu, 07/12/2007 - 19:12
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN

Gerald


If you are running EIGRP as your dynamic routing protocol then it would logically choose to send all the traffic over the interface with the highest bandwidth. And if it is configured correctly it would choose to use the other interface if the preferred interface became not available.


My suggestion of Policy Based Routing works very well with EIGRP. In essence PBR provides an alternative to the traditional routing decision for certain identified traffic. To implement PBR you would create an access list that identifies the traffic. For example if you decide that you want to send all traffic that is telnet you might create an access list like this:

access-list 123 permit tcp any eq 23 any

access-list 123 permit tcp any any eq 23

Then you create a route map which uses the access list to identify traffic and you set a next hop which will send the identified traffic to a next hop that is different from the normal choice in the routing table. It might look like this:

route-map use-alternate-path permit 10

match ip address 123

set next-hop ip-address w.x.y.z

And then you assign the route map on interfaces where the traffic will be received

interface fastethernet1/1

ip policy route-map use-alternate-path

This link will provide some additional information and should help you get started with this:

http://www.cisco.com/en/US/docs/ios/12_0/qos/configuration/guide/qcpolicy.html


HTH


Rick

Actions

This Discussion