From: Jason Gardiner (gardiner@xxxxxxxxxx)
Date: Thu Oct 11 2001 - 10:24:16 GMT-3
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
This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 22:33:17 GMT-3