From: fwells12 (fwells12@xxxxxxxxxxx)
Date: Mon Jan 07 2002 - 02:37:13 GMT-3
Weight doesn't have anything to do with how a BGP peer imports its routes.
Weight is a local-router-only attribute to tell only the local router which
route it prefers. It should work for you.
----- Original Message -----
From: "Richard Geiger" <geiger_rich@hotmail.com>
To: <fallow46@yahoo.com>; <ccielab@groupstudy.com>
Sent: Sunday, January 06, 2002 9:23 PM
Subject: Re: BGP Help 2 days untill Lab
> Weight, Local-pref, as-path, are all used to decide what in the BGP table
> will ten be imported into the routing table as the preferred path.
> As R2 and R3 each only have one path to the route in the BGP table they
mean
> nothing. Remember that R2 will not forward the path to R3 because it is
an
> external route learned from a internal neighbor. Now if R2 was also
peered
> with the outside As this would work.
>
> I can route-map with the next hop statement and send it to R2, but the
> problem is that if R2 goes down it will not remove the next hop path,
(i've
> tried a lot of variations of this). I've also tried tagging the route in
> BGP and manipulating it in IGP with a route-map but have had problems with
> the local policy matching everything even if the route is tagged.....
>
> -Rich
>
>
> >From: garry baker <fallow46@yahoo.com>
> >To: Richard Geiger <geiger_rich@hotmail.com>
> >Subject: Re: BGP Help 2 days untill Lab
> >Date: Sun, 6 Jan 2002 21:07:05 -0800 (PST)
> >
> >Richard,
> >
> >weight should work on r3. give the link to r2 a hiher
> >weight and you should be fine. if this doesn't work
> >let me know and i will play when i get home from work
> >and let you know. later on tonight
> >
> >Garry
> >--- Richard Geiger <geiger_rich@hotmail.com> wrote:
> > > The senerio is that you have 1 BGP external router
> > > AS100 connected to an
> > > internal router AS999. You are using the next hop
> > > command because you are
> > > not using IGP for the outside route.
> > >
> > > AS100 lo0 10.10.10.1/24
> > > |
> > > AS999 -R1
> > > / \
> > > AS999-R2 --- As999 -R3
> > >
> > > All three of the internals are peered to each other.
> > > R2 and R3 both show the next hop to 10.10.10.0 to be
> > > the Loopback
> > > on R1
> > >
> > > As there is only one path local-pref,weight, as-path
> > > won't help here.
> > > How do you tell R3 to use a path through R2 to Reach
> > > 10.10.10.1
> > >
> > >
> > >
> > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:18 GMT-3