From: alsontra@hotmail.com
Date: Sun Mar 07 2004 - 23:37:12 GMT-3
Thank you. I know they were suppose to be reversed. However, in one of my
foolish attempt to try anything, most likely reversed them. Shouldn't have
posted the route-map that way. I did mange to get this to work. ( The
problem was a router not supporting "* soft" refresh). You make a good
point though, I did not combine the task. What a mistake!!!! I ended up
using this:
!
route-map FILTER-20 permit 10
match ip address prefix-list 1
set weight 6000
Thanks for your time Yasser...
----- Original Message -----
From: "Yasser Aly" <blackyeyes00@hotmail.com>
To: <alsontra@hotmail.com>; <ccielab@groupstudy.com>
Sent: Sunday, March 07, 2004 4:22 PM
Subject: RE: Route-map using preifix-list
>
> Hi Alsontra,
>
> I guess your first statment in the route-map is the problem.
> The 1st statement is simply setting weight for anything to 6000, so any
route will be matched by this statmment and no route will reach permit 20
statment to be evaluated.
>
> You need to make it checked before - change its sequesnce from 20 to 5
for example.
>
> Try reversing the logi. If it worked for you but screwed the other task
then you need to set your match/set commands in a way to acheive all your
requirements.
>
> Regards,
> Yasser
>
> >From: <alsontra@hotmail.com>
> >Date: Sun, 7 Mar 2004 18:07:28 -0800
> >
> >Hi Group,
> > I read the sections of the BGP configuration guide
regarding
> >prefix-list and their configuration, but I can't seem to find where I'm
making
> >a mistake. Scenario goes something like this:
> >
> >
> >Requirement: remove all prefixes with a mask longer that 20bits. I
applied
> >the following route-map and prefix to neighbor 54.7.6.254 - direction IN
..
> >
> >
> >
> >ip prefix-list 1 seq 5 permit 0.0.0.0/0 le 20
> >
> >route-map FILTER-20 permit 10 <----- requirement for a previous task
> >disregard, unless this is the problem.
> > set weight 6000
> >
> >route-map FILTER-20 permit 20
> > match ip address prefix-list 1
> >!
> >
> >After "clear ip bgp * soft in | out " the table looks as follows:
> >
> >
> >BGP table version is 14, local router ID is 150.1.6.6
> >Status codes: s suppressed, d damped, h history, * valid, > best, i -
> >internal,
> > r RIB-failure
> >Origin codes: i - IGP, e - EGP, ? - incomplete
> >
> > Network Next Hop Metric LocPrf Weight Path
> >*> 28.119.16.0/24 54.7.6.254 6000 54 i
> >*> 28.119.17.0/24 54.7.6.254 6000 54 i
> >*> 112.0.0.0 54.7.6.254 0 6000 54 50 60 i
> >*> 113.0.0.0 54.7.6.254 0 6000 54 50 60 i
> >*> 114.0.0.0 54.7.6.254 0 6000 54 i
> >*> 115.0.0.0 54.7.6.254 0 6000 54 i
> >*> 116.0.0.0 54.7.6.254 0 6000 54 i
> >*> 117.0.0.0 54.7.6.254 0 6000 54 i
> >*> 118.0.0.0 54.7.6.254 0 6000 54 i
> >*> 119.0.0.0 54.7.6.254 0 6000 54 i
> >*> 205.90.31.0 204.12.7.3 0 200 254 ?
> >*> 220.20.3.0 204.12.7.3 0 200 254 ?
> >*> 222.22.2.0 204.12.7.3 0 200 254 ?
> >
> >Shouldn't 28.119.16.0/24 and 28.119.17.0/24 getremoved from the
routing
> >table?
> >
> >Thanks,
> >Alsontra
> >
> >_______________________________________________________________________
> >Please help support GroupStudy by purchasing your study materials from:
> >http://shop.groupstudy.com
> >
> >Subscription information may be found at:
> >http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Thu Apr 01 2004 - 08:15:16 GMT-3