Re: Wanted: one more well-known BGP community

Ravi Chandra <rchandra@cisco.com> Wed, 09 August 1995 22:36 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa21237; 9 Aug 95 18:36 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa21233; 9 Aug 95 18:36 EDT
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa21461; 9 Aug 95 18:36 EDT
Received: by interlock.ans.net id AA37010 (InterLock SMTP Gateway 3.0 for iwg-out@ans.net); Wed, 9 Aug 1995 18:17:17 -0400
Message-Id: <199508092217.AA37010@interlock.ans.net>
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-2); Wed, 9 Aug 1995 18:17:17 -0400
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-1); Wed, 9 Aug 1995 18:17:17 -0400
To: Vince Fuller <vaf@valinor.barrnet.net>
Cc: bgp@ans.net
Subject: Re: Wanted: one more well-known BGP community
In-Reply-To: Your message of "Wed, 09 Aug 1995 15:10:27 PDT." <CMM.0.90.2.808006227.vaf@valinor.barrnet.net>
Date: Wed, 09 Aug 1995 15:15:57 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Ravi Chandra <rchandra@cisco.com>

>     	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.


	This should work. The set on the outbound will be done just
before the update is shipped.. Probably there is some bug.. could you
unicast me the 'show ip bg x.x.x.x' of the route and I will look at
it.

--ravi

> 
> 	--Vince