Page 1 of 1

BGP Advice

Posted: Wed Feb 01, 2012 6:10 pm
by syadnom
I am looking to optimise my iBGP setup. Looking for some advice from those who have been using iBGP for a while.

I have a standard tree topology network.

Core>Tower1>Tower2,3,4 and so on

Core 10.0.0.0/24
Tower1 10.0.1.0/24
Tower2 10.0.2.0/24
Tower3 10.0.3.0/24

Core <bgp> Tower1 (tower 1 is a main distribution point to other towers)

Tower1 <bgp> Tower2
Tower1 <bgp> Tower3
Tower1 <bgp> Tower4

My questions are:
Should I continue to use a single ASN for all bgp peers? currently using '1'

At Tower1, should I use a single instance to both connect to Core and to Towers 2,3,4, or should I have an 'upstream' instance and a 'downstream', or even a different instance for each tower I connect to?

For route filters, should I be doing accepts and only allowing specific networks through? Or should I be letting anything through and disguarding certain networks?

Finally, when to use route-reflect. Just at Tower1 so that Towers2,3, and 4 can get those routes?

Thanks for any help in advance.

Re: BGP Advice

Posted: Wed Feb 01, 2012 6:14 pm
by syadnom
just to throw a kink in here, I plan on deploying an HWMP+ mesh on this and giving each tower router a public IP on the mesh and eventually routing clients through the mesh.

When I do that I will have a separate bgp tree on the mesh, but because the mesh is a single layer2 I will just have the core mesh node with route reflect on and the sites as peers, all of which on a separate bgp instance. (unless I am told that is the wrong way to do it.)

Re: BGP Advice

Posted: Thu Feb 02, 2012 9:32 pm
by samsung172
run a main ebgp at core router. Then try confederation with different AS in all ibgp routers. make sure u have a connection between all routers, who will act as multihomed (redundant) links. if stright r1-r2-r3-r4 and no r2-r3and4 its no good use of bgp. Just stight forward routes.

Re: BGP Advice

Posted: Thu Feb 02, 2012 9:46 pm
by syadnom
so in my example:
Core <bgp> Tower1 (tower 1 is a main distribution point to other towers)
Tower1 <bgp> Tower2
Tower1 <bgp> Tower3
Tower1 <bgp> Tower4
I can extend this to say
Tower2 connects to Tower 3, which makes Towers 1,2,3 in a triangle shape.
Tower3 connects to Tower 4, making 1,3,4 a triangle shape.

This means a ton for static routes.

Also, if I have a subnet at the end of this topology Core>Tower1>Tower4>Tower5>CPE, each tower has it's own subnet which means 4 networks, I have 4 static routes to add :( ibgp means 0 static routes.

I was thinking I would use ibgp for this for simplicity, but without route filters I am getting huge route lists and loops etc etc.

Maybe I should be looking at OSPF instead?

Re: BGP Advice

Posted: Thu Feb 02, 2012 11:50 pm
by dasiu
Maybe I should be looking at OSPF instead?
And how many "real" eBGP sessions (on different routers) do you have there?
iBGP's main idea is that the eBGP routers should "discuss" the routes received from their peers and decide, how to route the traffic outside. For routing inside one "real" AS - BGP is too "heavy" and complicated, and THAT'S WHY people invented some better routing protocols - like OSPF! :)