[c-nsp] BGP Route Reflectors

[Bruce Pinsky]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mikael Abrahamsson wrote:
> On Tue, 11 Jul 2006, Alex Foster wrote:
> 
> May I point you to the publication "ISP Essentials" by Cisco.
> 
> www.ccxx.net/books/Cisco%20ISP%20Essentials.pdf
> 
> It will cover this topic as well. Afaik it's not updated anymore but you 
> have to buy the physical book to get the latest revisions, but the ones on 
> the web cover all the basics.
> 
>> Okay, so separating the physical topology - provided I'm running IGP - I can create iBGP peering between the loopbacks of routers that are not directly connected ??  Throughout any diagrams I looked at I always assumed that a full-mesh iBGP network inferred that a physical connection existed between each and every router (now that I consider that statement - it would seem ludicrous to expect that).
>>
>> So in my scenario we don't need RRs just iBGP full-mesh as such:
>>
>> Router A - iBGP to Loopback of Routers B,C,D
>> Router B - iBGP to Loopback of Routers A,C,D
>> Router C - iBGP to Loopback of Routers A,B,D
>> Router D - iBGP to Loopback of Routers A,B,C
>>
>> Hopefully its as simple as that.
> 
> Remember that the BGP sessions should be loopback to loopback 
> (update-source in cisco).
> 

And that, ideally, your IGP should be limited to only the loopbacks
(/32's).  Alternately, depending on your IGP, you may need to carry some
additional infrastructure routes or because you want management to physical
IP addresses.


- --
=========
bep

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEs+PgE1XcgMgrtyYRAkjiAJ9uKzKO87rvyMcui+B4gvGGbkXoHgCfdQPv
B9PQ0e1j0w7zyoCKld+p0vQ=
=dUqa
-----END PGP SIGNATURE-----