Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

Static Default Routes won't Load Balance

I am trying to staticly load balance between two ISP's. One connection is Ethernet the other DSL. My route statements are as follows

ip route 0.0.0.0 0.0.0.0 dialer 0

ip route 0.0.0.0 0.0.0.0 63.45.61.161

show ip route 0.0.0.0

Routing entry for 0.0.0.0/0, supernet

Known via "static", distance 1, metric 0 (connected), candidate default path

Routing Descriptor Blocks:

* 63.45.61.161

Route metric is 0, traffic share count is 1

directly connected, via Dialer0

Route metric is 0, traffic share count is 1

Internal network traffic always uses the 63.45.61.161 route but internally generated router traffic will load balance. If the interface connected to 63.45.61.161 fails, all traffic will use the Dialer 0. Without administrative distance modification, I would expect the dialer to be the prefered route as it is a static route to an interface (i.e. connected route).

While experimenting I've tried raising the A.D. of both routes to 5. I've tried "ip route 0.0.0.0 0.0.0.0 fastethernet 0/0 63.45.61.161." I've disabled CEF and set "no ip route-cache" but I can't get internal traffic to load balance.

Does the fact that a Dialer interface is "Spoofed." have any impact on the route?

Any ideas would be greatly appreciated?

5 REPLIES
Hall of Fame Super Gold

Re: Static Default Routes won't Load Balance

Marc

The fact that the Dialer is spoofed should have no impact on the routes. Could you post the output of show ip route from this router?

HTH

Rick

Community Member

Re: Static Default Routes won't Load Balance

Gateway of last resort is 63.45.61.161 to network 0.0.0.0

63.0.0.0/29 is subnetted, 1 subnets

C 63.45.61.160 is directly connected, FastEthernet0/0

192.168.10.0/32 is subnetted, 2 subnets

C 192.168.10.251 is directly connected, Dialer0

10.0.0.0/24 is subnetted, 5 subnets

C 10.10.10.0 is directly connected, FastEthernet0/1

S 10.10.20.0 [1/0] via 10.10.10.1

74.0.0.0/32 is subnetted, 1 subnets

C 74.1.176.102 is directly connected, Dialer0

S* 0.0.0.0/0 [1/0] via 63.45.61.161

is directly connected, Dialer0

Hall of Fame Super Gold

Re: Static Default Routes won't Load Balance

Marc

This is certainly not what I expected. These lines:

S* 0.0.0.0/0 [1/0] via 63.45.61.161

is directly connected, Dialer0

seem to associate address 63.45.61.161 with interface dialer0 and not with FastEthernet0/0. Can you post the output of show interface FastEthernet0/0 and also the output of show ip interface brief?

HTH

Rick

Community Member

Re: Static Default Routes won't Load Balance

You may have been confused by the fact that this website removes extra spaces. Please view the route to 0.0.0.0 as ...

S* 0.0.0.0/0 [1/0] via 63.45.61.161

-------------is directly connected, Dialer0

You will notice my original post shows the configured 0.0.0.0 routing entries (including the one to the dialer interface) and a the output of "show ip route 0.0.0.0."

The routing table looks good to me. Unfortunately, traffic received on an interface NEVER takes the dialer interface unless the 63.45.61.161 interface goes down.

The problem appears to be related to PPPoE, virtual-templates, the dialer interface, or something the dsl provider is configuring via my "ip address negotiated" interface.

1841#show ip int br

Interface IP-Address OK? Method Status Prot

ocol

FastEthernet0/0 63.45.61.161 YES manual up up

...

NVI0 unassigned YES unset up up

Virtual-Access1 unassigned YES unset down down

Virtual-Access2 unassigned YES unset up up

Virtual-Template2 74.1.176.102 YES TFTP down down

Dialer0 74.1.176.102 YES IPCP up up

Hall of Fame Super Gold

Re: Static Default Routes won't Load Balance

Marc

Yes you are correct that I mis-interpreted the truncated spaces. (which is the second time today that I have misunderstood formatting of posted information) Thanks for clarifying.

I am surprised to see that the address specified in the static default route seems to be the address of the FastEthernet interface itself:

FastEthernet0/0 63.45.61.161 YES manual up up

I would expect this kind of static route to normally specify the next hop address. I am not clear what the impact is of using the interface address. I would have thought it would not work (since effectively we do not know how to forward past the interface) but wonder if in some perverse way it makes it more attractive?

Also at the risk of being a bit dense again, I wonder if there is significance in seeing the address 74.1.176.102 associated with both Virtual-Template2 (where it is down down) and with Dialer0 where it is up up.

Perhaps we might get more of a handle on the issue if you would post the config of the router.

HTH

Rick

150
Views
0
Helpful
5
Replies
CreatePlease to create content