[c-nsp] eBGP no-export

shariq qamar shariq.qam at gmail.com
Sat Jan 24 08:12:22 EST 2009


Hi steve ,

if you dont want your prefix should be advertise by your peering neighbour
or you dont want him to act as a transit AS for the ip addresses advertise
by you ,
then you are doing the right configuartion by setting the no-export
community on the advertise route ,also  your peering partner should put the
additive command on the community what ever comunity  he is using to tag
your traffic

supose he is tagging your traffic or prefixes  with community yyyy:xxxx then
he
also required to  permit your no-export community which is possible by
adding additive command or if he is not taging your prefix with any
community ..then only additive is enough in set clause of route-map .


route-map on peering partner router
route-map FRM-IBCTECH permit 10
match ip address IBC-IN
set community xxxx:yyyy additive

or

 route-map FRM-IBCTECH permit 10
match ip address IBC-IN
set community additive


or If peering partner wants then he can also tag comunity no-export on the
learn routes .

 route-map FRM-IBCTECH permit 10
match ip address IBC-IN
set community no-export


Hopes it clears ur query

-- 
Regards,
Shariq Qamar,


More information about the cisco-nsp mailing list