Re: BGP weight

what does the command 'sh ip bgp neighbors 10.1.12.2 advertised-routes'
show?

wouldnt it be showing that the R2 address as the next-hop now from R1, which
would not be a legit route for R2 to put into its bgp table right?

i will throw this up in a lab when i get a minute...

--
Garry L. Baker
"There is no 'patch' for stupidity." - www.sqlsecurity.com
On Fri, Nov 19, 2010 at 1:30 PM, Jack Router <pan.router_at_gmail.com> wrote:
> I have a question about BGP weight and how it affects routing on other
> routers. Here is an example:
>
> AS100          AS200
> R1-------------R2
> |              |
> |              |
> |              |
> R4-------------R3
> AS400          AS300
>
> Router R4 advertises network 4.0.0.0
> Rip runs on all routers and advertises links between routers.
>
> R2 sees two paths to 4.0.0.0 :
>
>  Network          Next Hop            Metric LocPrf Weight Path
> *  4.0.0.0          10.1.12.1                              0 100 400 i
> *>                  10.1.23.3                              0 300 400 i
>
> Now, on router R1 I define weight of 50000 for all routes coming from
> AS200:
> # neighbor 10.1.12.2 weight 50000
>
> R2 sees now only one route to 4.0.0.0:
>   Network          Next Hop            Metric LocPrf Weight Path
> *> 4.0.0.0          10.1.23.3                              0 300 400 i
>
> R2 removed path via R1 which is good thing because this would create a
> loop.
> My question is:
> How R2 knows not to use R1 anymore ?
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net