Re: Wanted: one more well-known BGP community

[Paul Traina <[e-mail]>]

  From: Vince Fuller <[e-mail]>
  Subject: Re: Wanted: one more well-known BGP community
      	The 'no-advertise' community was meant to do what you want..
      why cannot you set the 'no-advertise' for selected entries via the
      outbound route-map (10.3 supports network based filtering for outbound
      route-maps). It should do what you want..
  
  I tried it. When I do something like:
  
      router bgp 200
      neighbor 192.31.48.245 route-map peer-out out
      !
      route-map peer-out permit 10
      match ip as-path 81
      match ip address 150
      set community no-advertise
      !
      route-map peer-out permit 20
      match ip as-path 81
  
  the routes which match as-path access-list 81 and access-list 150 are never
  seen by 192.31.48.245, presumably because "no-advertise" was set on them
  locally and therefore, BGP decided not to advertise them.

No, if that's the case, there's a bug and you should submit a bug report,
please include the usual data,
	show version
	show ip bgp <broken path>
	debug ip bgp update
	write term

and please send it to both [e-mail] and [e-mail].

If the 192.31.48.248 route was not advertised, then that's an implementation
foible on our part,  not a requirement for a new parameter.  I can believe
that that problem occured,  another test is probably necessary for locally
assigned communities at redistribution time.

We now return you to your generic non-cisco discussions.