Hi Raheel, Can you show how you are applying the policies and also give us a "show route x.x.150/23" so we can if the route is being properly accepted and is a candidate for advertisement? I assume this is an export policy toward your transit provider(s)?
I'm not sure if you know, but there is a policy test utility from the CLI as well, which works well with simple policies (ie - non chained ones) try "test policy xyz 0/0" to see which routes match, or "test policy xyz x.x.150/23" to test the prefix in question. Pete On Tue, Feb 2, 2010 at 11:53 AM, Raheel Muhammad <[email protected]> wrote: > Hi, > > term term-1 { > from { > route-filter x.x.128.0/19 upto /24; > } > then accept; > } > term ios-implicit-deny { > then reject; > } > > This way x.x.150.0/23 is not getting advertised though it fall in between. I > have to add 150.0/23 specifically. But if i am putting this policy > > term term-1 { > from { > route-filter x.x.144.0/20 upto /24; or x.x.152.0/21/24 upto /24; > } > then accept; > } > term ios-implicit-deny { > then reject; > } > > Then x.x.150.0/23 is getting advertised without allowing it specifically. > > > rah...@xxx-m10i# run show route receive-protocol bgp x.x.242.249 > > * x.x.150.0/23 x.x242.249 0 100 xxx22 I > > > I am receiving this prefix from customer. > > Regards > > > Thanks > > On Tue, Feb 2, 2010 at 12:39 PM, Felix SchŸueren < > [email protected]> wrote: > >> Raheel, >> >> >> Raheel Muhammad wrote: >> >>> Hi, >>> >>> It is our customer prefix and we are acting as a transit provider. >>> Configuration is simple >>> >>> term term-1 >>> from >>> route-filter x.x.128.0/19 upto /24 >>> >>> do you have any terminating action within that filter? Please paste the >> full policy in junos syntax. Is the route actually in inet.0? Just having it >> in the RIB-in does not mean it's in the actual RIB. If it is active in the >> RIB (and of protocol BGP), then also paste your export policy. The most >> likely config mistakes are probably: >> >> - you don't have a terminating action ("accept" or "reject") in your import >> policy, causing the route to not be accepted >> >> - you have a non-bgp route for the customer subnet as best active route in >> the RIB, which means the default bgp export policy will not pick it up >> >> anyway, please post detailled config & show output so we don't have to >> guess so much. >> >> Kind regards, >> >> Felix >> >> -- >> Felix Schüren >> Head of Network >> >> ----------------------------------------------------------------------- >> Host Europe GmbH - http://www.hosteurope.de >> Welserstraße 14 - 51149 Köln - Germany >> Telefon: 0800 467 8387 - Fax: +49 180 5 66 3233 (*) >> HRB 28495 Amtsgericht Köln - USt-IdNr.: DE187370678 >> Geschäftsführer: >> Uwe Braun - Alex Collins - Mark Joseph - Patrick Pulvermüller >> >> (*) 0,14 EUR/Min. aus dem dt. Festnetz, Mobilfunkpreise ggf. abweichend >> >> > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
