Load balancing Multiple T1's on multihomed cisco 7206

[intelwizrd]

I am trying to set up my router to load balance 4 T1's (agragate bandwidth of 6Mbps) but only route a specific network outbound on the T1's.
I have the following:
multi-homed cisco 7206 router (ios 12 i believe)
-DS3 connection to Sprint
-4 T1 lines to QWest
a /24 from QWest
a /22 from Sprint

I want to route internal traffic from the /24 outbound through the T1's (per-packet load balancing) and to route the /22 out the DS3. (also want to be able to have fail over redundancy)

I am running BGP to QWest and Sprint.
I currently have a route-map set up that sets the default interface of the /24 to the four T1's.
route-map QWEST permit 10
match ip address 10
set default interface serial2/7:0 serial 2/6:0 serial2/5:0 serial2/4:0

This route-map is applied to the FastEthernet interface that is acting
as the gateway for the network. The route map is working but all traffic is going out serial2/7:0.
I have turned off route cacheing on the fastethernet and 4 serial interfaces and still no load balanceing. I also tried enableing CEF and adding "ip load-sharring per-packet" to the interfaces, still no luck.

Any ideas?

other info:
*setting false metrics on network broadcasts to sprint and qwest to "force" inbound traffic for the different networks through their respective pipes
*receiving only default routes from neighbors

 

[baddos]

How do you get your routes? Do you get full routes, partials, default routes?

 

[intelwizrd]

i get believe i only get default routes. I can have this changed if need be.

 

[baddos]

Ok... So do you have two default routes or 5? If you have only one from each provider, it should be pretty easy.

 

[intelwizrd]

I am receiving 0.0.0.0 from sprint (that is all)
I am receiving 0.0.0.0 and 192.5.88.0(showing as incomplete) from qwest

 

[baddos]

Do you have a route to the network that qwest sent you? I.E. If their default route points to router x.x.x.a, can you route to that route through the quest t1 lines? If not, make 4 static routes to that subnet via your 4 t1 line routers.

Example:

ser0 ip 1.1.1.1/30 qwest's ip 1.1.1.2/30
ser1 ip 2.2.2.1/30 qwest's ip 2.2.2.2/30
ser2 ip 3.3.3.1/30 qwest's ip 3.3.3.2/30
ser3 ip 4.4.4.1/30 qwest's ip 4.4.4.2/30
Their default route points to 5.5.5.1.

Now you would have 4 equal cost static routes to your default gateway. Turning on ip cef and ip loadsharing per-packet will loadbalance to that default route.

Now you would just do a route-map that would set the next hop based on the source address.

ip route 5.5.5.1 255.255.255.255 1.1.1.2
ip route 5.5.5.1 255.255.255.255 2.2.2.2
ip route 5.5.5.1 255.255.255.255 3.3.3.2
ip route 5.5.5.1 255.255.255.255 4.4.4.2
!
ip prefix-list internal description Internal Network
ip prefix-list internal seq 5 permit xxx.xxx.xxx.0/24
!
route-map myroute permit 10
match ip address prefix-list internal
set ip next-hop 5.5.5.1
!Sets the default route for internal traffic to use qwest
!
route-map myroute permit 20
set ip next-hop xxx.xxx.xxx.xxx
!Sets the default route for all other routes to Sprint's route
!
interface ethernet0/0
ip load-sharing per-packet
ip policy route-map myroute
end
copy running-config startup-config

 

[intelwizrd]

baddos,
I tried this configuration and all traffic was being sent out the T3 interface to sprint. looking at what you suggested, this should work. I think that there is something else in my configuration that is preventing this from working. I am posting the relavent portion of the configuration for review. thanks to anyone who can help and for your help baddos.

!
version 12.0
!
ip subnet-zero
ip cef
ip tftp source-interface FastEthernet0/0
ip name-server 208.17.204.16
!
!
!
controller T1 2/0
channel-group 0 timeslots 1-24
!
controller T1 2/1
channel-group 0 timeslots 1-24
!
controller T1 2/2
channel-group 0 timeslots 1-24
!
controller T1 2/3
channel-group 0 timeslots 1-24
!
controller T1 2/4
channel-group 0 timeslots 1-24
!
controller T1 2/5
channel-group 0 timeslots 1-24
!
controller T1 2/6
channel-group 0 timeslots 1-24
!
controller T1 2/7
channel-group 0 timeslots 1-24
!
!
!
!
interface FastEthernet0/0
description 100mbps connection to backbone switch
ip address 208.17.206.1 255.255.255.0 secondary
ip address 208.17.205.1 255.255.255.0 secondary
ip address 208.17.204.1 255.255.255.0
no ip directed-broadcast
full-duplex
!
interface Serial1/0
description T3 connection to Sprint
ip address 144.232.186.22 255.255.255.252
ip access-group 100 in
ip access-group 101 out
no ip directed-broadcast
framing c-bit
cablelength 10
dsu bandwidth 15000
!
interface Serial2/0:0
description Connection to downtown
ip address 204.183.154.6 255.255.255.252
no ip directed-broadcast
encapsulation ppp
fair-queue 64 16 0
!
interface Serial2/1:0
description Connection to (In House)
ip address 204.183.154.18 255.255.255.252
no ip directed-broadcast
no ip route-cache
encapsulation ppp
fair-queue 64 16 0
!
interface Serial2/2:0
description Connection to (In House)
ip address 204.183.154.2 255.255.255.252
no ip directed-broadcast
no ip route-cache
encapsulation ppp
fair-queue 64 16 0
!
interface Serial2/3:0
description T1 to r
ip address 204.183.154.14 255.255.255.252
no ip directed-broadcast
encapsulation ppp
fair-queue 64 16 0
!
interface Serial2/4:0
description Connection to Qwest
ip address 65.122.30.98 255.255.255.252
ip access-group 100 in
ip access-group 101 out
no ip directed-broadcast
no fair-queue
!
interface Serial2/5:0
description Connection to Qwest
ip address 65.118.39.162 255.255.255.252
ip access-group 100 in
ip access-group 101 out
no ip directed-broadcast
no fair-queue
!
interface Serial2/6:0
description Connection to Qwest
ip address 65.118.39.122 255.255.255.252
ip access-group 100 in
ip access-group 101 out
no ip directed-broadcast
no fair-queue
!
interface Serial2/7:0
description Connection to Qwest
ip address 65.114.129.158 255.255.255.252
ip access-group 100 in
ip access-group 101 out
no ip directed-broadcast
no fair-queue
!
interface FastEthernet4/0
description Qwest Backbone Switch 100 Mbps
ip address 65.122.27.1 255.255.255.0
no ip directed-broadcast
ip load-sharing per-packet
ip policy route-map QWEST
full-duplex
!
interface FastEthernet6/0
description LAN Backbone Switch
ip address 208.17.207.1 255.255.255.0
no ip directed-broadcast
full-duplex
!
router bgp 20120
network 65.122.27.0 mask 255.255.255.0
network 65.122.27.0
network 204.183.154.0
network 204.183.155.0
network 208.17.204.0
network 208.17.205.0
network 208.17.206.0
network 208.17.207.0
network 205.171.2.28 mask 255.255.255.255
neighbor 205.171.2.28 remote-as 209
neighbor 205.171.2.28 ebgp-multihop 2
neighbor 205.171.2.28 update-source FastEthernet4/0
neighbor 205.171.2.28 soft-reconfiguration inbound
neighbor 205.171.2.28 route-map setmetricSprint out
neighbor 205.171.2.28 filter-list 1 out
neighbor 144.232.186.21 remote-as 1239
neighbor 144.232.186.21 version 4
neighbor 144.232.186.21 soft-reconfiguration inbound
neighbor 144.232.186.21 route-map setmetricQwest out
no auto-summary
!
ip classless
ip route 0.0.0.0 0.0.0.0 Serial1/0
ip route 204.183.154.0 255.255.255.0 Null0
ip route 204.183.154.8 255.255.255.252 Serial2/0:0
ip route 204.183.155.0 255.255.255.0 Null0

ip route 204.183.155.0 255.255.255.240 Serial2/1:0
ip route 204.183.155.0 255.255.255.240 Serial2/2:0

ip route 204.183.155.16 255.255.255.240 Serial2/1:0
ip route 204.183.155.16 255.255.255.240 Serial2/2:0

ip route 204.183.155.32 255.255.255.240 Serial2/1:0
ip route 204.183.155.32 255.255.255.240 Serial2/2:0

ip route 204.183.155.48 255.255.255.240 Serial2/1:0
ip route 204.183.155.48 255.255.255.240 Serial2/2:0

ip route 204.183.155.64 255.255.255.240 Serial2/0:0
ip route 204.183.155.80 255.255.255.240 Serial2/0:0
ip route 204.183.155.96 255.255.255.240 Serial2/0:0

ip route 204.183.155.112 255.255.255.240 Serial2/1:0
ip route 204.183.155.112 255.255.255.240 Serial2/2:0

ip route 204.183.155.192 255.255.255.240 Serial2/1:0
ip route 204.183.155.192 255.255.255.240 Serial2/2:0

ip route 204.183.155.208 255.255.255.240 Serial2/1:0
ip route 204.183.155.208 255.255.255.240 Serial2/2:0

ip route 205.171.2.28 255.255.255.255 Serial2/4:0
ip route 205.171.2.28 255.255.255.255 Serial2/5:0
ip route 205.171.2.28 255.255.255.255 Serial2/6:0
ip route 205.171.2.28 255.255.255.255 Serial2/7:0

ip route 208.17.206.128 255.255.255.128 Serial2/3:0
no ip http server
ip as-path access-list 1 permit ^$
!
!***ACL 100 and 101 removed
!
!***Prefix List***
ip prefix-list qwestnetblock description QWest IP Address Block
ip prefix-list qwestnetblock seq 5 permit 65.122.27.0/24
!
!***RouteMap ACL***
access-list 10 permit 65.122.27.0 0.0.0.255
access-list 20 permit 208.17.204.0 0.0.0.255
access-list 20 permit 208.17.205.0 0.0.0.255
access-list 20 permit 208.17.206.0 0.0.0.255
access-list 20 permit 208.17.207.0 0.0.0.255
access-list 20 permit 204.183.154.0 0.0.0.255
access-list 20 permit 204.183.155.0 0.0.0.255
!
route-map setmetricQwest permit 10
match ip address 20
set metric 50
!
route-map setmetricSprint permit 10
match ip address 10
set metric 50
!
route-map SPRINT permit 10
match ip address 20
set default interface Serial1/0
!
route-map QWEST permit 10
! match ip address 10
match ip address prefix-list qwestnetblock
set ip next-hop 205.171.2.28
! set default interface Serial2/4:0 Serial2/5:0 Serial2/6:0 Serial2/7:0
!
!***snmp info and vty line info removed
!
end

note that the remarked lines in the QWEST route-map indicate the way i was attempting to handle this before.
the network from qwest is the 65.122.27.0/24
i want this network to be routed out the 4 t1 lines (ser2/4:0 - ser2/7:0) and all other traffic to be routed out of the ser1/0 interface. and here is another catch. i must have failover redundancy.

 

[baddos]

Please post a "show ip route".

 

[intelwizrd]

router#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route

Gateway of last resort is 0.0.0.0 to network 0.0.0.0

B 192.5.88.0/24 [20/10] via 205.171.2.28, 4d08h
204.183.155.0/24 is variably subnetted, 11 subnets, 2 masks
S 204.183.155.192/28 is directly connected
is directly connected, Serial2/1:0
is directly connected, Serial2/2:0
S 204.183.155.208/28 is directly connected
is directly connected, Serial2/1:0
is directly connected, Serial2/2:0
S 204.183.155.96/28 is directly connected
is directly connected, Serial2/0:0
S 204.183.155.112/28 is directly connected
is directly connected, Serial2/1:0
is directly connected, Serial2/2:0
S 204.183.155.64/28 is directly connected
is directly connected, Serial2/0:0
S 204.183.155.80/28 is directly connected
is directly connected, Serial2/0:0
S 204.183.155.32/28 is directly connected
is directly connected, Serial2/1:0
is directly connected, Serial2/2:0
S 204.183.155.48/28 is directly connected
is directly connected, Serial2/1:0
is directly connected, Serial2/2:0
S 204.183.155.0/28 is directly connected
is directly connected, Serial2/1:0
is directly connected, Serial2/2:0
S 204.183.155.0/24 is directly connected, Null0
S 204.183.155.16/28 is directly connected
is directly connected, Serial2/1:0
is directly connected, Serial2/2:0
205.171.2.0/32 is subnetted, 1 subnets
S 205.171.2.28 is directly connected, Serial2/4:0
is directly connected, Serial2/6:0
is directly connected, Serial2/7:0
is directly connected, Serial2/5:0
204.183.154.0/24 is variably subnetted, 10 subnets, 3 masks
C 204.183.154.1/32 is directly connected, Serial2/2:0
C 204.183.154.0/30 is directly connected, Serial2/2:0
S 204.183.154.0/24 is directly connected, Null0
C 204.183.154.5/32 is directly connected, Serial2/0:0
C 204.183.154.4/30 is directly connected, Serial2/0:0
S 204.183.154.8/30 is directly connected
is directly connected, Serial2/0:0
C 204.183.154.13/32 is directly connected, Serial2/3:0
C 204.183.154.12/30 is directly connected, Serial2/3:0
C 204.183.154.17/32 is directly connected, Serial2/1:0
C 204.183.154.16/30 is directly connected, Serial2/1:0
65.0.0.0/8 is variably subnetted, 5 subnets, 2 masks
C 65.122.27.0/24 is directly connected, FastEthernet4/0
C 65.114.129.156/30 is directly connected, Serial2/7:0
C 65.122.30.96/30 is directly connected, Serial2/4:0
C 65.118.39.120/30 is directly connected, Serial2/6:0
C 65.118.39.160/30 is directly connected, Serial2/5:0
144.232.0.0/30 is subnetted, 1 subnets
C 144.232.186.20 is directly connected, Serial1/0
C 208.17.205.0/24 is directly connected, FastEthernet0/0
C 208.17.204.0/24 is directly connected, FastEthernet0/0
C 208.17.207.0/24 is directly connected, FastEthernet6/0
208.17.206.0/24 is variably subnetted, 2 subnets, 2 masks
C 208.17.206.0/24 is directly connected, FastEthernet0/0
S 208.17.206.128/25 is directly connected
is directly connected, Serial2/3:0
S* 0.0.0.0/0 is directly connected, Serial1/0

 

[baddos]

Add this..

ip route 0.0.0.0 0.0.0.0 144.232.186.21

You had no default route from Quest, so the traffic was going down serial1/0

 

[intelwizrd]

do you mean add a static default route for qwest?

my only ip route 0.0.0.0 0.0.0.0 is directed to serial1/0 which is directly connected to 144.232.186.21

do i need to add default routes pointing to 205.171.2.28 or to the 4 serial interfaces?

right now all traffic from 65.122.27.0/24 is going out ser2/4:0 and spilling over into ser2/5:0 then ser2/6:0 then ser2/7:0
all traffic from 208.17.204.0/22 and 204.183.154/23 is going out ser1/0
this is as it should be except i want the 65.122.27.0/24 network to loadbalance across ser2/4:0 ser2/5:0 ser2/6:0 and ser2/7:0.

 

[baddos]

yeah... I'm sorry I thought that was the qwest peer.

Just one more default route to qwest.

 

[intelwizrd]

Just in case anyone read this thread earlier or is having the same problem, here is how i solved it.

I added a high distance metric onto the default route that pointed at my T3.

ip route 0.0.0.0 0.0.0.0 Serial1/0 200
ip route 0.0.0.0 0.0.0.0 Serial2/4:0
ip route 0.0.0.0 0.0.0.0 Serial2/5:0
ip route 0.0.0.0 0.0.0.0 Serial2/6:0
ip route 0.0.0.0 0.0.0.0 Serial2/7:0

This would fool the router into thinking that the best path is through Serial2/4 - Serial2/7 (the T1's) and not Serial1/0 (the T3).

I then added route policies to the ethernet interfaces to set the default interface to the T3 for all networks i wanted to route through the T3 and used a route map to set the next-hop (specified the BGP neighbor address for my connection to QWest) for all traffic that i wanted to route through the T1's.

That was it. I don't know why it took me so long to figure it out. Thanks to all who helped out where they could. If you have any questions about how i solved it, post a reply and i will be notified.

Thanks.