.jpg "Opportunities, Appliacation, Openings"){kind=small}
.jpg "Hand Job, Blow Job, Job Search, Monster Job"){kind=small}
.jpg "pusat resume, daftar kerja, cari kerja"){kind=small}
.jpg "Project Manager, SOftware Engineer, SAP Consultant"){kind=small}
No-Advertise & No-Export
No-export of course!
Using no-advertise will prevent prefixes received from AS10 to be advertized to R3 iBGP peers as well which are undesirable here.
Sent from my iPhone
On 13/01/2009, at 6:28 AM, CCIE To Be wrote:
Dear Group,
I have a confusion regarding usage of no-advertise and no-export communities. I know that no-advertise means NOT TO ADVERTISE to any bgp peer ( iBGP & eBGP ) whereas no-export says NOT TO ADVERTISE to any eBGP peer means don’t advertise outside this AS. Consider the following topology,
R1(AS 10) ——–R2(AS 10)————R3(AS 30)
Let say AS 10 is advertising a prefix to AS 30 and requirement is that AS 30 should not forward this prefix further to any other AS. Now we have option to use either no-advertise or no-export on R2 towards R3. Both will give the desired result , what should be the recommended approach here ??
HTH
Blogs and organic groups at http://www.ccie.net
