Well, we put it on the network statement, which might be the difference?
Could be something that works on network & redist, but not output props?
router bgp 64512
network 192.168.32.0 mask 255.255.224.0 route-map SET-ORIGIN
neighbor 172.26.2.2 remote-as 64513
George
> From cmartin@gnilink.net Tue Oct 17 16:27:12 2000
> From: "Martin, Christian" <cmartin@gnilink.net>
> To: "'George Robbins'" <grr@shandakor.tharsis.com>, andrea.sala@blixer.it,
> cisco-nsp@puck.nether.net, "Martin, Christian" <cmartin@gnilink.net>,
> mpicard@sinc.ca
> Subject: RE: [nsp] [nsp] BGP - set origin
> Date: Tue, 17 Oct 2000 16:22:28 -0400
>
> > > George,
> > >
> > > In my experience in testing, set origin egp <asn> does nothing to =
> > > change the
> > > AS-PATH. Perhaps a bug? Either way, I believe the egp
> > construct is =
> > > there
> > > for legacy purposes and will likely be deprecated in a
> > future release.
> > >
> > > ./chris
> >
> > It really *does* work, what you have to realize is that like prepend,
> > the origin is tacked onto the as-path as part of the output editing
> > process and doesn't show up if you just do a "show ip bgp n.n.n.n".
>
> I tried it in the lab using two private asn's. The receiving neighbor shows
> origin as egp, but the path is the original path...
>
> TEST-GSR2-------TEST-GSR1
>
> TEST-GSR1#sh run | beg router b
> router bgp 64512
> network 192.168.32.0 mask 255.255.224.0
> neighbor 172.26.2.2 remote-as 64513
> neighbor 172.26.2.2 route-map SET-ORIGIN out
> !
> !
> route-map SET-ORIGIN permit 10
> set origin egp 65000
> !
> ip route 192.168.32.0 255.255.224.0 Null0
> !
>
>
> Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
> State/PfxRcd
> 172.26.2.1 4 64512 10028 10022 14 0 0 02:40:14 1
> TEST-GSR2#sh run | beg router bgp
> router bgp 64513
> no synchronization
> neighbor 172.26.2.1 remote-as 64512
> !
> TEST-GSR2#sh ip bgp
> BGP table version is 14, local router ID is 172.27.1.170
> 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
> *> 192.168.32.0/19 172.26.2.1 0 0 64512 e
> TEST-GSR2#
> TEST-GSR2#sh ip bgp 192.168.32.0
> BGP routing table entry for 192.168.32.0/19, version 14
> Paths: (1 available, best #1)
> Not advertised to any peer
> 64512
> 172.26.2.1 from 172.26.2.1 (207.68.6.5)
> Origin EGP, metric 0, localpref 100, valid, external, best
> TEST-GSR2#
>
>
> As you can see here, the ASN doesn't change...
>
> chris
>
>
>
> > It will show up if viewed from the neighbor or if you show routes
> > advertised towards a neighbor...
> >
> > We've used it 11.1CC thru 12.0.12S...hope nobody gets any silly ideas
> > about deprecating it...
>
>
> >
> > George
> >
>
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:19 EDT