Okay, that makes sense then. Only routes that originate from a given PE's CEs will be tagged and advertised. Any routes received from other PEs would only be imported into VRFs, never exported.
This especially makes sense with MP-iBGP, which should never re-advertise BGP routes since we're doing iBGP. Is MP-eBGP supported inside a SP MPLS cloud, or is that a major no-no? Thanks for your response, that's exactly what I needed to know. Keller Giacomarro [email protected] On Sun, Dec 18, 2011 at 1:23 AM, Andrey Klyuchka <[email protected]> wrote: > Based on the reading I've done, at this point Customer 1 and Customer 2 > should be able to communicate with Central Services but not with each > other. But that doesn't really make sense to me! Wouldn't central > services *import* routes from Customer 1 with an RT of 1 and then > *export* those > > same routes with an RT of 2? Wouldn't that mean that both Customer 1 and > Customer 2 are receiving each other's routes, with the Central Services PE > acting as a route bridge? > > > Central Services will export routes only redistributed from its CEs over > IGP. > > > Best regards, > Andrey > > -- > Andrey Klyuchka :: CCIE #30274 (Security) > Twitter: http://twitter.com/bitstriker > LinkedIn: http://kz.linkedin.com/in/andreyklyuchka > > _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com http://onlinestudylist.com/mailman/listinfo/ccie_rs
