From: Jonathan V Hays (jhays@jtan.com)
Date: Sun Sep 28 2003 - 11:49:21 GMT-3
I was a bit surprised at the results, but I am glad for the knowledge
gained.
Thanks! Good information to know.
Jonathan
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
info@mpauli.de
Sent: Sunday, September 28, 2003 10:20 AM
To: jhays@jtan.com; Ken.Farrington@barclayscapital.com
Cc: ccielab@groupstudy.com
Subject: Re-4: Route-Map Logic (Example from networkers 2000)
Hi Jonathan,
you're right concerning the def. weight. But if the default is in
effect, it is not displayed with sh ip bgp. The point was, to
demonstrate, that after a permit in a route-map, it is checked against
the other entrys. (Your point 2).
Anyway, I've just changed the route-map:
R2#sh ip bgp
BGP table version is 20, local router ID is 133.1.2.2
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*>i1.1.1.0/24 133.1.3.3 300 100 0 5001 65001
253 99 100 i
*>i2.2.2.0/24 133.1.3.3 300 100 0 5001 65001
253 99 100 i
*>i3.3.3.0/24 133.1.3.3 300 100 0 5001 65001
253 99 100 i
*>i4.4.4.0/24 133.1.3.3 300 100 0 5001 65001
253 99 100 i
*>i5.5.5.0/24 133.1.3.3 300 100 0 5001 65001
253 99 100 i
*>i6.6.6.0/24 133.1.3.3 300 100 0 5001 65001
253 99 100 i
*>i10.10.1.0/24 133.1.3.3 300 100 0 5001 65001
253 99 100 i
*>i133.1.253.0/24 133.1.3.3 300 100 0 5001 65001
253 99 100 i
*>i144.10.13.0/24 133.1.3.3 444 100 0 5001 i
* i144.10.31.0/24 133.1.3.3 444 100 0 5001 i
Network Next Hop Metric LocPrf Weight Path
* i144.10.35.0/24 133.1.3.3 444 100 0 5001 i
*>i144.10.111.0/24 133.1.3.3 444 100 0 5001 i
*>i150.100.1.0/24 133.1.3.3 444 100 0 5001 i
*>i192.168.161.0 133.1.3.3 300 100 0 5001 65001
253 99 100 i
*>i192.168.167.0 133.1.3.3 300 100 0 5001 65001
253 99 100 i
*>i192.168.170.0 133.1.3.3 300 100 0 5001 65001
253 99 100 i
*>i197.65.7.0 133.1.3.3 300 100 0 5001 65001
253 99 100 i
*>i198.199.199.0 133.1.3.3 300 100 0 5001 65001
253 99 100 i
*>i199.199.198.0 133.1.3.3 300 100 0 5001 65001
253 99 100 i
*>i199.199.199.0 133.1.3.3 300 100 0 5001 65001
253 99 100 i
*>i201.201.201.0 133.1.3.3 444 100 0 5001 i
Q.E.D. ;-)
Cheers
Marcus
-------- Original Message --------
Subject: RE: Re-2: Route-Map Logic (Example from networkers 2000)
(28-Sep-2003 16:12)
From: jhays@jtan.com
To: info@mpauli.de
> I see some flaws in this test.
>
> 1. You are setting local preference to the default, which is 100. So
it
> is not easy to tell if the route-map has actually done anything. You
> would do better to use a non-default value, such as 111.
>
> 2. Please note that each route is filtered by the route-map
> individually. If there are 10 routes, then the route-map is executed
10
> times. So one route might match on permit 10 while the next route
> matches on permit 20.
>
> To verify that the route-map is exiting on the first match for a given
> route, a better test might be this:
>
> route-map bla01 permit 10
> match as-path 10
> set metric 300
> !
> route-map bla01 permit 20
> match as-path 10
> set metric 444
>
> If the route-map does NOT exit after permit 10 has set the metric to
> 300, then the final metric will be 444.
>
> HTH,
>
> Jonathan
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> info@mpauli.de
> Sent: Sunday, September 28, 2003 8:40 AM
> To: Ken.Farrington@barclayscapital.com
> Cc: ccielab@groupstudy.com
> Subject: Re-2: Route-Map Logic (Example from networkers 2000)
>
>
> Hi Ken,
>
> I've just tested it myself:
> Originating router:
>
> router bgp 1
> bgp router-id 133.1.5.5
> bgp log-neighbor-changes
> neighbor 133.1.2.2 remote-as 1
> neighbor 133.1.2.2 update-source Loopback0
> neighbor 133.1.2.2 route-reflector-client
> neighbor 133.1.2.2 route-map bla01 out
> neighbor 133.1.3.3 remote-as 5001
> neighbor 133.1.3.3 ebgp-multihop 2
> neighbor 133.1.3.3 update-source Loopback0
> neighbor 133.1.6.6 remote-as 1
> neighbor 133.1.6.6 update-source Loopback0
> neighbor 133.1.6.6 route-reflector-client
> !
> ip as-path access-list 10 permit 99
> ip as-path access-list 20 permit ^5001
> !
> !
> route-map bla01 permit 10
> match as-path 10
> set metric 300
> !
> route-map bla01 permit 20
> match as-path 20
> set local-preference 100
>
> The outcome on the destination router looks like this:
>
> R2#sh ip bgp
> BGP table version is 21, local router ID is 133.1.2.2
> Status codes: s suppressed, d damped, h history, * valid, > best, i -
> internal
> Origin codes: i - IGP, e - EGP, ? - incomplete
>
> Network Next Hop Metric LocPrf Weight Path
> *>i1.1.1.0/24 133.1.3.3 300 100 0 5001
65001
> 253 99 100 i
> *>i2.2.2.0/24 133.1.3.3 300 100 0 5001
65001
> 253 99 100 i
> *>i3.3.3.0/24 133.1.3.3 300 100 0 5001
65001
> 253 99 100 i
> *>i4.4.4.0/24 133.1.3.3 300 100 0 5001
65001
> 253 99 100 i
> *>i5.5.5.0/24 133.1.3.3 300 100 0 5001
65001
> 253 99 100 i
> *>i6.6.6.0/24 133.1.3.3 300 100 0 5001
65001
> 253 99 100 i
> *>i10.10.1.0/24 133.1.3.3 300 100 0 5001
65001
> 253 99 100 i
> *>i133.1.253.0/24 133.1.3.3 300 100 0 5001
65001
> 253 99 100 i
> *>i144.10.13.0/24 133.1.3.3 100 0 5001 i
> * i144.10.31.0/24 133.1.3.3 100 0 5001 i
> Network Next Hop Metric LocPrf Weight Path
> *>i144.10.35.0/24 133.1.3.3 100 0 5001 i
> *>i144.10.111.0/24 133.1.3.3 100 0 5001 i
> *>i150.100.1.0/24 133.1.3.3 100 0 5001 i
> *>i192.168.161.0 133.1.3.3 300 100 0 5001
65001
> 253 99 100 i
> *>i192.168.167.0 133.1.3.3 300 100 0 5001
65001
> 253 99 100 i
> *>i192.168.170.0 133.1.3.3 300 100 0 5001
65001
> 253 99 100 i
> *>i197.65.7.0 133.1.3.3 300 100 0 5001
65001
> 253 99 100 i
> *>i198.199.199.0 133.1.3.3 300 100 0 5001
65001
> 253 99 100 i
> *>i199.199.198.0 133.1.3.3 300 100 0 5001
65001
> 253 99 100 i
> *>i199.199.199.0 133.1.3.3 300 100 0 5001
65001
> 253 99 100 i
> *>i201.201.201.0 133.1.3.3 100 0 5001 i
>
> Thus, the process was running through both route-maps. As per your
> statement, it should only be the MED of 300 for all prefixes
containing
> AS 99...
>
> Hope I could help.
>
> Cheers
> Marcus
>
>
> -------- Original Message --------
> Subject: RE: Route-Map Logic (Example from networkers 2000)
(28-Sep-2003
> 14:12)
> From: Ken.Farrington@barclayscapital.com
> To: navaid@rogers.com
>
> > Yes, they are for different routes.
> >
> > I am just confused then, on how the route-maps work, so, if you set
> an
> > attrib on prefix A, lets say, then you cant do anything else with a
> route
> > map to that prefix?
> >
> > ? Im sure there are some "route-map Kings" on this list somewhere?
> >
> > Many thx for the input Navaid :)
> >
> >
> > -----Original Message-----
> > From: navaid@rogers.com [mailto:navaid@rogers.com]
> > Sent: 28 September 2003 12:55
> > To: Ken.Farrington@barclayscapital.com; ccielab@groupstudy.com
> > Cc: kenfarrington@yahoo.com
> > Subject: Re: Route-Map Logic (Example from networkers 2000)
> >
> >
> > Ken,
> > Are you setting community attribute and next-hop for same route.
> > If it is for different routes. I think it will work because
route-map
> is
> > applied for each route one by one.
> >
> > Navaid.
> >
> >
> > >
> > > From: Ken.Farrington@barclayscapital.com
> > > Date: 2003/09/28 Sun AM 06:54:05 EDT
> > > To: ccielab@groupstudy.com
> > > CC: kenfarrington@yahoo.com
> > > Subject: Route-Map Logic (Example from networkers 2000)
> > >
> > > All,
> > >
> > > I am a little confused about the route-map logic that Cisco use.
> > > In their example from networkers 2000, they say (note the first
line
> in
> > the
> > > table)
> > > that if in your route-map, you have a hit on a permit and set an
> > attribute,
> > > the
> > > route-map will exit?
> > >
> > > +--------------------------------------------------------------+
> > > | ROUTE-MAP | MATCH CLAUSE/ | ACCEPT ROUTE and | EXIT |
> > > | STANZA | PREFIX-LIST | SET ATTRIBUTE | ROUTE-MAP |
> > > +-----------+-----------------+--------------------+-----------+
> > > | Permit | Yes/Permit | Yes | Yes |
> > > | | | | |
> > > | Permit | No/Deny | No | No |
> > > | | | | |
> > > | Deny | Yes/Permit | No | Yes |
> > > | | | | |
> > > | Deny | No/Deny | No | No |
> > > +-----------+-----------------+--------------------+-----------+
> > >
> > >
> > >
> > > So I have a route map doing two things for BGP.
> > > 1. Setting the next-hop attrib
> > > 2. Setting the community
> > >
> > > But my route map does not exit after the first hit (permit 10) to
> set the
> > > next hop.
> > > It does continue to go onto 20 and set my community.
> > >
> > > Can someone please clarify this for me.
> > >
> > > ****Will it always go onto the next route-map statment if there is
> one?
> > ****
> > >
> > >
> > >
> > > !
> > > ip prefix-list BGP-COMM-LIST seq 5 permit 1.1.1.0/24
> > > ip prefix-list BGP-COMM-LIST seq 10 permit 2.2.2.0/24
> > > !
> > > ip prefix-list BGP-SNH-LIST seq 5 permit 3.3.3.3/32
> > > ip prefix-list BGP-SNH-LIST seq 10 permit 4.4.4.4/32
> > > !
> > > !
> > > route-map BGP-ATTRIB permit 10
> > > match ip address prefix-list BGP-SNH-LIST
> > > set ip next-hop 142.220.10.1
> > > !
> > > route-map BGP-ATTRIB permit 20
> > > match ip address prefix-list BGP-COMM-LIST
> > > set community local-AS
> > > !
> > > route-map BGP-ATTRIB permit 30
> > > !
> > >
> > >
> > >
> > >
>
------------------------------------------------------------------------
> > > For more information about Barclays Capital, please
> > > visit our web site at http://www.barcap.com.
> > >
> > >
> > > Internet communications are not secure and therefore the Barclays
> > > Group does not accept legal responsibility for the contents of
this
> > > message. Although the Barclays Group operates anti-virus
> programmes,
> > > it does not accept responsibility for any damage whatsoever that
is
> > > caused by viruses being passed. Any views or opinions presented
are
>
> > > solely those of the author and do not necessarily represent those
of
> the
> > > Barclays Group. Replies to this email may be monitored by the
> Barclays
> > > Group for operational or business reasons.
> > >
> > >
>
------------------------------------------------------------------------
> > >
> > > ***Get your CCIE and a FREE vacation: Shop.GroupStudy.com***
> > >
>
This archive was generated by hypermail 2.1.4 : Wed Oct 01 2003 - 07:24:39 GMT-3