Well, route-reflectors and route-reflector-clients have an iBGP relationship with each other, yet the route-reflector-clients need not be part of the full mesh.
iBGP speakers tell each other about locally injected routes, routes learned from ebgp neighbors, and routes learned from ibgp route-reflector-clients. Additionally, iBGP speakers announce all bgp routes to route-reflector-clients. Of course, the above is subject to applied routing policies. Route-reflection (and confederations), in my experience, are best used when physical (or administrative) hierarchy promote a matching routing hierarchy. For instance, say a site has 2 core routers connected to core routers at other sites, and 2 distribution routers connected to the two local core routers, and each other. It would make sense to make the core routers part of the full ibgp mesh, and then make the distribution routers route-reflector-clients of both core routers at that site. In large networks, a combination of confederations and route-reflectors can really cut down on the overhead involved in managing huge router configs. Regards, --phil On Sat, Aug 03, 2002 at 05:06:18AM +0000, Chuck wrote: only the iBGP speakers must be in a full mesh - not necessarily the entire network. ""Robert D. Cluett"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Group, > > In reading the BSCN book, I have stumbled across something confusing when it > is discussing "route reflectors". The books states that the use of route > reflectors eliminates the need to run BGP in a full mesh environment. Based > on this statement I have assumed that BGP therefore must be configured only > on a network that is fully meshed (unless route reflectors are used). Is > this true? > > Robert D. Cluett, CCNA -- Regards, --phil Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=50577&t=50573 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
