Escolar Documentos
Profissional Documentos
Cultura Documentos
Discussion
This recipe is similar to Recipe 9.4, but here we have split the functions acros
s two routers to ensure that you can sustain a link failure or a router failure
without losing your Internet connection. Figure 9-2 shows the new network topolo
gy.
Figure 9-2. Using two ISPs
The main difference is that we have had to configure an eBGP link from each rout
er to its ISP, as well as an iBGP link between the two routers. Note that we hav
e included the same AS Path filter on both routers to ensure that our network do
esn't allow transit routing from one ISP to the other.
However, just as in the single router example, you have to decide how you want t
o deal with the problem of the excessive number of routes that you will receive
from both of these ISPs.
Notice we have included the next-hop-self option for the iBGP peers on both rout
ers:
Router1(config)#router bgp 65500
Router1(config-router)#neighbor 172.18.5.3 remote-as 65500
Router1(config-router)#neighbor 172.18.5.3 next-hop-self
Without this option, the next hop IP address for prefixes learned through Router
1 will be the ISP connected to Router1. But even in this simple network, Router2
will not have a route to this next hop address. We could also get around this p
roblem by including static routes on both routers. We discuss the next-hop-self
option in more detail in Recipe 9.3.
In this example, we only have two routers inside our AS. You could add more, usi
ng exactly the same configuration commands that we used here. However, you need
to remember to create a full mesh of iBGP peer relationships between all of thes
e routers. Every BGP router must have a neighbor statement connecting to every o
ther BGP router in the same AS.