set community no-export

[Sean Donelan <SEAN () SDG DRA COM>]

No that doesn't work very well, unless you make the rash assumption that
all of Sprint's customers are in the same Autonomous System.  We saw all
sorts of goofy problems when I*STAR did this with MCI.  The problems
went away when the customer switched from I*STAR to UUNET/Canada :-)

You need a community that will be announced to "customer" BGP sessions,
but not to "peer" BGP sessions.  Its not hard to do, but it does seem
to be hard to explain to your standard order taker/sales staff.

It also seems to confuse the heck out of the support folks when they
need to troubleshoot things.  It would really be nice if cisco's had
a "show ip bgp neigh xxx out" command that showed what you are telling
your neighbor.  Essentially the inverse of the "show ip bgp neigh xxx
route" command.

> set community no-export?
>
> > It's the other direction that is the problem.  How does he advertise
> > routes to Sprint so that Sprint customers can reach him but without
> > Sprint advertising his routes at exchange points?  That's the other
> > half of what he's asking for, and he can't do it unless Sprint sets
> > up filters to do it for him.
-- 
Sean Donelan, Data Research Associates, Inc, St. Louis, MO
  Affiliation given for identification not representation
- - - - - - - - - - - - - - - - -