Load Balancing to the Utah REP

Xmission's load balancing configuration

Here's my REP connected router config.  The other side is similarly done.

interface Serial0/0
 bandwidth 1544
 ip address 204.228.132.22 255.255.255.252
 no ip directed-broadcast
 ip load-sharing per-packet
!         
interface Serial0/1
 bandwidth 1544
 ip address 204.228.132.50 255.255.255.252
 no ip directed-broadcast
 ip load-sharing per-packet
!         
interface Serial0/2
 bandwidth 1544
 ip address 204.228.132.190 255.255.255.252
 no ip directed-broadcast
 ip load-sharing per-packet
!         
router eigrp 6315
 redistribute connected
 redistribute static
 network 204.228.132.0
 no default-information in
 default-metric 10000 100 255 1 1500
 no auto-summary
!
router bgp 6315
 no synchronization
 neighbor 10.123.123.1 remote-as 6315
 neighbor 10.123.123.1 ebgp-multihop 255
 neighbor 10.123.123.1 update-source Loopback0
(peering deleted)
!
ip route 10.123.123.1 255.255.255.255 204.228.132.21 200
ip route 10.123.123.1 255.255.255.255 204.228.132.49 200
ip route 10.123.123.1 255.255.255.255 204.228.132.189 200

So the peering between my REP router and my main router happens on the
10.123.123.0/30 network.  Each router learns how to get to 10.123.123.0 via
EIGRP which handles the load balancing.  I've heard that having "ip cef"
turned on also helps for per-packet load balancing, but haven't tested this
extensively.

This works well.  I'd rather have one pipe though.


[mrtg] [participants] [status]
Last updated: Tue Feb 26 03:29:21 EST 2002