doka at lucky
Jul 18, 2011, 4:56 AM
Post #3 of 5
(768 views)
Permalink
|
Erik,
I was trying single "community set" statement like
community set "3254:65535 3254:9100 3254:9111"
with the same result. Since I want to remove all incoming communities, I
use "set" to rewrite entire information.
Actually, this works - because you've seen that particular network
prefix has specific communities. The question is why some of them can't
be used with "show bgp route comm" command.
On 7/18/2011 1:49 PM, Erik Bais wrote:
>
> Hi Doka,
>
> Is there a specific reason why you are using the following syntax for
> the BGP policy to add the communities ?
>
> community set "3254:65535 3254:9100";
> community add "3524:9111";
>
> I’m using the following in my policies :
>
> entry entry-5 {
>
> If {
>
> nlri 123.123.128.0/21 exact ;
>
> }
>
> then {
>
> med set 0;
>
> local-preference 250;
>
> community add "51088:6543" ;
>
> community add "51088:65001" ;
>
> permit ;
>
> }
>
> }
>
> And that works on 12.4.2 , 12.4.3, 12.5.4. (and is currently broken
> in the 12.6.x beta but expected to be fixed before the 12.6 GA version.)
>
> I’m also running X480’s .
>
> Regards,
>
> Erik Bais
>
> *From:*extreme-nsp-bounces [at] puck
> [mailto:extreme-nsp-bounces [at] puck] *On Behalf Of *Volodymyr
> Litovka
> *Sent:* Monday, July 18, 2011 12:35 PM
> *To:* extreme-nsp [at] puck
> *Cc:* yokodzun [at] yokodzun
> *Subject:* [e-nsp] ExOS: "sh bgp routes community" bug?
>
> Hi,
>
> when looking into detailed network info, it shows right communities here:
>
> _eel.35 # sh bgp routes detail network 31.41.120.0/21_
>
> Feasible Routes
> ---------------
> Route: 31.41.120.0/21, Peer 213.133.164.149, BEST, Active
> Origin IGP, Next-Hop 213.133.164.149, LPref 95, MED 100
> Weight 1,
> AS-Path: 13249 9002 8744 48485
> Community: 3254:65535 3254:9100 3524:9111
>
> but when I'm trying to get all routes with selected community, I get
> strange results.
>
> None for 3254:9111 :
>
> _eel.36 # show bgp routes community 3254 : 9111__
> _
> Feasible Routes
> ---------------
> Destination Peer Next-Hop LPref Weight MED AS-Path
>
>
> Unfeasible Routes
> -----------------
> Destination Peer Next-Hop LPref Weight MED AS-Path
>
> while everything is ok for 3254:9100:
>
> _eel.60 # show bgp routes community 3254 : 9100_
>
> Feasible Routes
> ---------------
> Destination Peer Next-Hop LPref Weight
> MED AS-Path
> *>i 1.0.4.0/22 194.44.35.213 194.44.35.213 90
> 1 3255 6939 7545 7545 7545 7545 7545 56203
> i 1.0.4.0/22 213.133.164.149 213.133.164.149 85 1
> 100 13249 6939 7545 7545 7545 7545 7545 56203
> *>i 1.5.0.0/16 194.44.35.213 194.44.35.213 90
> 1 3255 6939 4725
> i 1.5.0.0/16 213.133.164.149 213.133.164.149 85 1
> 100 13249 6939 4725
> *>i 1.8.1.0/24 194.44.35.213 194.44.35.213 90
> 1 3255 3549 6453 4641 38345
> i 1.8.1.0/24 213.133.164.149 213.133.164.149 85 1
> 100 13249 6453 4641 38345
> *>i 1.8.8.0/24 194.44.35.213 194.44.35.213 90
> 1 3255 3549 6453 4641 38345
> i 1.8.8.0/24 213.133.164.149 213.133.164.149 85 1
> 100 13249 6453 4641 38345
>
> Everything rest besides "show" seems to be working.
>
> Incoming policy map is:
>
> entry peer-in-50 {
> if match any {
> as-path "_NNNNN_" ;
> community "XXXX:YYYYY" ;
> }
> then {
> local-preference 95;
> community set "3254:65535 3254:9100";
> community add "3524:9111";
> permit;
> }
> }
>
> Is it bug or feature?
>
> Summit x480
> Image : ExtremeXOS version 12.5.1.6 v1251b6 by release-manager
> on Tue Nov 23 09:49:14 PST 2010
>
> Thank you
>
>
> --
>
> /doka
>
> Vision without Execution is Hallucination. -- Thomas Edison.
> ------------------------------------------------------------------------
>
> No virus found in this message.
> Checked by AVG - www.avg.com <http://www.avg.com>
> Version: 10.0.1390 / Virus Database: 1516/3771 - Release Date: 07/17/11
>
--
/doka
Vision without Execution is Hallucination. -- Thomas Edison.
|
