BGP load sharing, dual-homed to one SP

[LEFT][CODE]http://evilrouters.net/2009/03/22/bgp-load-sharing-dual-homed-to-one-sp/[/CODE]
Here’s another lab that I just made up using [URL="http://www.ipflow.utc.fr/index.php/Cisco_7200_Simulator"]dynamips[/URL]/[URL="http://dynagen.org/"]dynagen[/URL]. There is a download link to the .net file I used (modify it as needed) at the bottom of this post.
[B]NOTE: See the video demonstration below![/B]
For this lab, here’s the topology we’re working with:
[IMG]http://evilrouters.net/wp-content/uploads/2009/03/bgp-load-sharing-dual-homed-one-isp.png[/IMG]
Our scenario here is pretty basic. We are AS 65065 and are dual-homed to our service provider, AS 65001. We have two T-1 connections: R1 to R2 and R1 to R3. We’re running [URL="http://evilrouters.net/tag/bgp/"]BGP[/URL] with our service provider and we would like to load share our outgoing traffic over these two T-1 connections. Fortunately, [URL="http://www.cisco.com/"]Cisco[/URL] provides us with an easy way to do this.
As you may already know, BGP will, by default, only install the one best path into the routing table. In our case, that means that we would only be utilizing one connection at a given time. That’s not exactly the best use of our available bandwidth. The [I]“maximum-paths”[/I] command is our friend.
From the Cisco IOS IP Command Reference:[INDENT]“To configure the maximum number of parallel routes that an IP routing protocol will install into the routing table, use the maximum-paths command in router configuration or address family configuration mode. To restore the default value, use the no form of this command.”[/INDENT]Here are our starting configurations for R2 and R3

[B]R2[/B]
[CODE]interface fastethernet 0/0
ip address 172.16.23.2 255.255.255.0
no shutdown
interface serial 1/1
ip address 172.16.12.2 255.255.255.0
no shutdown
router bgp 65001
network 172.16.12.0 mask 255.255.255.0
network 172.16.23.0 mask 255.255.255.0
neighbor 172.16.12.1 remote-as 65065
neighbor 172.16.23.3 remote-as 65001
neighbor 172.16.23.3 next-hop-self
[/CODE][B]
R3[/B]
[CODE]interface fastethernet 0/0
ip address 172.16.23.3 255.255.255.0
no shutdown
interface serial 1/0
ip address 172.16.13.3 255.255.255.0
no shutdown
router bgp 65001
network 172.16.13.0 mask 255.255.255.0
network 172.16.23.0 mask 255.255.255.0
neighbor 172.16.13.1 remote-as 65065
neighbor 172.16.23.2 remote-as 65001
neighbor 172.16.23.2 next-hop-self
end[/CODE]The interface configuration for R1 is pretty standard and simple, with perhaps one exception

[CODE]interface serial 1/0
ip address 172.16.13.1 255.255.255.0
ip load-sharing per-packet
no shutdown
interface serial 1/1
ip address 172.16.12.1 255.255.255.0
ip load-sharing per-packet
no shutdown[/CODE]Note the use of [I]“ip load-sharing per-packet”[/I]. Cisco’s default is to use per-destination load sharing. You’ll want to evaluate your network to decide which is best for you.
Now, let’s configure BGP on R1 and we’re practically done

[CODE]router bgp 65065
maximum-paths 2
neighbor 172.16.12.2 remote-as 65001
neighbor 172.16.13.3 remote-as 65001[/CODE]
[/LEFT]