Routing load balancing problem, Help!

Unanswered Question
Jun 29th, 2007

Hello, I have 3 conections to my ISP. All of them are frame relay (E1), my problem is:

I configure as follow:

interface FastEthernet0/0

ip address

ip route (ISP IP ADDRESS)

when I configure this like that everything works well internet is fast by example the video from are ok.

When I Configure the next ip route and interface as follow

interface FastEthernet0/0

ip address

ip address secondary

ip route

ip route

everything become slowly, I put load-balancing per packect and per destination but it still the same.

Each conection is a E1.

Even when I make a Traceroute in the first case is very fast but when I add the second ip route and third is really slow.

How can I fix this problem? I want to use of all my links making load balancing

By now the only traffic is from my laptop nobody else is using this connections.




I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
mohammedmahmoud Fri, 06/29/2007 - 06:37

Hi Leo,

There is either a typo error, or i can't analyze your situation, how is it that you are doing the default route to "", while your FastEthernet interface is in the same subnet "" and you say that you are connected to the provider via FR links, what is the IPs that you are peering with your provider with, please post the whole configuration if applicable.


Mohammed Mahmoud.

Leonardo A Pena... Fri, 06/29/2007 - 06:43

Ok my example wasn't right, here is my config

interface Ethernet4/1

ip address secondary

ip address

no ip redirects

load-interval 30

interface Serial0/0

description Circuito 8151-0012318

bandwidth 1920

ip address

ip load-sharing per-packet

encapsulation frame-relay IETF

no ip mroute-cache

load-interval 30

serial restart-delay 0


frame-relay interface-dlci 350

frame-relay lmi-type ansi

ip route

It works well but whe I add next ip route fron other valid network it becomes slow


ip route

ip route


Harold Ritter Fri, 06/29/2007 - 07:36

In order to try to isolate the issue, you should you use only as a next hop for the default route. This should tell you if the "slowness" is introduced by the new link/new ISP.


mohammedmahmoud Fri, 06/29/2007 - 12:51


Agree with Harold's suggestion, and please try to get the results of a direct ping with 1500 datagram to all your next-hops to see if there is any source of packet loss or delay on any of the paths.


Mohammed Mahmoud.


This Discussion