From: Joseph Brunner (joe@affirmedsystems.com)
Date: Sat Mar 08 2008 - 21:54:20 ARST
Thanks Scott V. for the suggestion to make "remove-private-as" outbound on
RTR1, here is the results... (172.24.1.85 is RTR1)
I tried "remove-private-as" on RTR1
RTR2#sh ip bgp | inc 199.79
*> 198.74.60.0/29 172.24.1.85 0 0 65020 i
* 198.74.60.0 0.0.0.0 32768 i
*> 198.74.60.24/29 172.24.1.85 0 0 65020 i
*> 198.74.60.48/29 172.24.1.85 0 0 65020 i
*> 198.74.60.56/29 172.24.1.85 0 0 65020 i
*> 198.74.60.160/27
So as you can see the 65020 is still in the path and towards RTR3
VPN39B-EXT-INT-01#sh ip bgp nei 172.19.255.165 advertised-routes | inc
199.79
*> 198.74.60.0/29 172.24.1.85 0 0 65020 i
*> 198.74.60.0 172.24.5.17 0 32768 i
*> 198.74.60.24/29 172.24.1.85 0 0 65020 i
*> 198.74.60.48/29 172.24.1.85 0 0 65020 i
*> 198.74.60.56/29 172.24.1.85 0 0 65020 i
*> 198.74.60.160/27
(my AS 65500 will be added once its finally off RTR2, cisco swears they are
still going to fix the "show ip bgp" commands to show you what will be
sent...)
I guess remove-private-as doesn't work on routers running private AS's them
selves... time to get back into my BGP lab...
Sadiq, I tried the bgp inject-map, but I cant get it work when the
Matching route source = locally injected. The /24 is created by a network
Command matching a static route on RTR2. the route-map match route source
Prefix list didn't like 0.0.0.0/32 or the next hop of 172.24.5.17 (RTR1) or
anything else... so I wonder if you can use the inject-map if the route your
matching is LOCALLY created...??!?!
Well, in the end I cleaned it up a bit and went with redis static matching a
route-map that checks with a prefix-list for which static routes to import,
of course, in that route-map I "set origin igp" so everyone doesn't see
routes with a ? as the source!
Thanks for the feedback gentlemen,
-Joe
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Sadiq Yakasai
Sent: Saturday, March 08, 2008 5:31 PM
To: Joseph Brunner
Cc: Cisco certification
Subject: Re: Real world bgp issues
Interesting experience there Joe :)
As for point 1) Yes, you can only remove private AS's on the point or
are interfacing with the non-private AS, if I remember my practice
labs well.
Just out of curiousity, why did you not consider using bgp route
injection on RTR2 to inject the /29 routes since you have a /24
covering these specifics routes in the BGP table, and this would have
65500 as the originating AS number. Or is this part of the rules that
you cannot do?
Sadiq
This archive was generated by hypermail 2.1.4 : Tue Apr 01 2008 - 07:53:52 ART