[f-nsp] What should be a simple route-map...
    Gerald Krause 
    gk at ax.tc
       
    Wed Oct 18 11:36:34 EDT 2006
    
    
  
On Wednesday 18 October 2006 15:43, Tuc at T-B-O-H.NET wrote:
> Hi,
>
> 	What should be a simple route map is kicking my backside this morning.
>
> ip community-list extended as22822-customer seq 5 permit 4...
> ip community-list extended as22822-customer seq 10 permit 5...
>
> ip prefix-list  filter24 seq 5 deny 0.0.0.0/0 ge 25
> ip prefix-list  filter24 seq 10 permit 0.0.0.0/0 le 32
>
> route-map  bgp-from-as22822-primary permit  20
>  match community  as22822-customer
>  set metric 100
>  set local-preference 160
>  set community  35954:1000 35954:1004 35954:10041 additive
> route-map  bgp-from-as22822-primary permit  25
>  match ip address prefix-list filter24
> route-map  bgp-from-as22822-primary permit  30
>  set metric 100
>  set local-preference 110
>  set community  35954:1000 35954:1004 additive
>
>
> 	It seems to not be throwing the route away. (I can't tell, the
> reason I'm implementing is that my max-pref gets triggered constantly.
> I can't take it off since its hitting the max the unit can take).
Maybe this would work in your setup:
!
ip prefix-list  filter24 seq 5 permit 0.0.0.0/0 ge 25
ip prefix-list  filter24 seq 10 deny 0.0.0.0/0 le 32
!
route-map  bgp-from-as22822-primary deny  25
  match ip address prefix-list filter24
!
-- 
Gerald    (ax/tc)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20061018/b3ebc010/attachment.sig>
    
    
More information about the foundry-nsp
mailing list