From: Michael Wong (Michael.Wong@xxxxxxxxxx)
Date: Fri Oct 12 2001 - 01:33:19 GMT-3
Another option would be to use the "network" statement to inject the route into
BGP which will give you an ORIGIN of "i". This would save you from doing a "re
distribute connected" at R8.
Seeing as you are modifying the ORIGIN at R6, R8 would have the 172.168.80.0 ro
ute with an "?" ORIGIN. Maybe this doen't fulfil the requirements of the task a
nd the ORIGIN should be set when redistributing the connected interface using a
route-map?
MW :)
-----Original Message-----
From: Jason Gardiner [mailto:gardiner@sprint.net]
Sent: Friday, 12 October 2001 2:25 am
To: w.schoots@chello.nl
Cc: ccielab@groupstudy.com
Subject: Re: CCIE Lab BootCamp, Lab 8, BGP origin code i (igp)
Yeah, you're right. Don't know what I was thinking. I think my
cerebellum's beginning to fuse :)
Willy Schoots wrote:
>
> Hi,
>
> This should normally work. I just tried a similar scenario on my lab and it
> works fine.
> Make sure that that you fully understand what you are seeing.
> - if possible configure soft-reconfiguration in
> - than compare the received-routes vs the routes from the neighbor
>
> --> This is the end result:
> bb#sh ip bgp
> BGP table version is 8, local router ID is 205.1.1.1
> 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
> *> 10.1.1.0/27 192.168.1.21 44445 500 300 1 i
>
> --> as you can see I received more routes with different attribute values.
>
> bb#sh ip bgp neighbors 192.168.1.21 received-routes
> BGP table version is 8, local router ID is 205.1.1.1
> 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
> * 10.1.1.0/27 192.168.1.21 5500 0 1 ?
> * 10.1.1.32/27 192.168.1.21 5500 0 1 ?
> * 200.1.1.0 192.168.1.21 5500 0 1 ?
>
> Total number of prefixes 3
>
> --> I applied the following route map to get to the result:
>
> router bgp 2
> neighbor 192.168.1.21 remote-as 1
> neighbor 192.168.1.21 soft-reconfiguration inbound
> neighbor 192.168.1.21 route-map origin in
> !
> access-list 1 permit 10.1.1.0 0.0.0.31
> !
> route-map origin permit 10
> match ip address 1
> set metric 44445
> set local-preference 500
> set weight 300
> set origin igp
>
> --> This leads to only accepting 10.1.1.0 route with changed attributes
> including the origin is now set to IGP.
>
> bb#sh ip bgp neighbors 192.168.1.21 routes
> BGP table version is 8, local router ID is 205.1.1.1
> 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
> *> 10.1.1.0/27 192.168.1.21 44445 500 300 1 i
>
> Total number of prefixes 1
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Jason Gardiner
> Sent: Thursday, October 11, 2001 3:24 PM
> To: Brittan Walker
> Cc: ccielab@groupstudy.com
> Subject: Re: CCIE Lab BootCamp, Lab 8, BGP origin code i (igp)
>
> I'll need to check, but I don't think you can set this route to IGP when
> you're obviously hearing it from an EBGP neighbor. You may be able to
> announce it to other ASN 2 routers as IGP.
>
> Brittan Walker wrote:
> >
> > I am able to manipulate the MED (metric), local preference, and weight
> > of incoming (or outgoing) bgp updates. However, I have been unable to
> > set the origin code to i (igp). In the following configuration, all
> > of the bgp attributes take effect except the origin. Am I missing
> > something?
> >
> > router bgp 2
> > no sync
> > neighbor 137.20.86.1 remote-as 1
> > neighbor 137.20.86.1 route-map ORIGIN-i in
> > no auto-summary
> > !
> > access-list 2 permit 172.168.80.0
> > route-map ORIGIN-i permit 10
> > match ip address 2
> > set metric 555
> > set local-preference 555
> > set weight 555
> > set origin igp
> >
> > I also tried "set metric-type internal".
> --
> Thanks,
>
> Jason Gardiner
> Supervisor, Engineering Services
> Sprint E|Solutions
>
> "You can swim all day in the Sea of Knowledge and
> still come out completely dry. Most people do."
>
> - Norton Juster
-- Thanks,Jason Gardiner Supervisor, Engineering Services Sprint E|Solutions
"You can swim all day in the Sea of Knowledge and still come out completely dry. Most people do."
- Norton Juster
This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 22:33:17 GMT-3