Re: BGP Metric

From: Mingzhou Nie (mnie@xxxxxxxxx)
Date: Tue Aug 20 2002 - 23:13:53 GMT-3


   
I don't see any reason why it chose 172.16.20.2 over 192.68.6.1 as best
route, unless you can post more configs, show outputs.

--- Ademola Osindero <osindero@lagos.sns.slb.com> wrote:
> Group,
>
> I thought MED is meant to take preference over internal or external
> routes
> but i can't see it happen in the case below. R6 prefers 172.16.20.2
> to
> 192.68.6.1 to reach network 172.16.10.0 despite the fact that the
> latter as
> a lower metric of 0.
>
> Can anyone explain this?
>
> r6#sh ip bgp
> BGP table version is 7, local router ID is 192.168.11.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
> *> 172.16.1.0/24 172.16.20.2 100 0 3 i
> * i 192.68.6.1 50 100 0 3 i
> *> 172.16.10.0/24 172.16.20.2 100 0 3 i
> * i 192.68.6.1 0 100 0 3 i
>
> r6#sh ip bgp 172.16.10.0
> BGP routing table entry for 172.16.10.0/24, version 7
> Paths: (2 available, best #1, table Default-IP-Routing-Table)
> Advertised to non peer-group peers:
> 192.68.6.1
> 3
> 172.16.20.2 from 172.16.20.2 (172.16.220.1)
> Origin IGP, metric 100, localpref 100, valid, external, best
> 3
> 192.68.6.1 from 192.68.6.1 (192.68.10.2)
> Origin IGP, metric 0, localpref 100, valid, internal
>
>
> Osindero Ademola
> Schlumberger Network Solutions
> Tel: 234 1 261 0446 Ext 5427
> Fax 234 1 262 1034
> email:osindero@lagos.sns.slb.com



This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:48:31 GMT-3