From: Nathan Chessin (nchessin@cisco.com)
Date: Thu Oct 24 2002 - 02:06:36 GMT-3
I would guess that the 133 route via 151.51.112.2 is being passed via eBGP.
Meanwhile, the 133 route with the lower metric is not in the IP routing
table, therefore, the route with the lower metric is not a viable option for
BGP selection, so the eBGP route is chosen.
Although, kinda hard to tell from the limited info.
Nate
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> jim.phillipo@guardent.com
> Sent: Wednesday, October 23, 2002 3:43 PM
> To: ccielab@groupstudy.com
> Subject: BGP route selection question
>
>
> Why is BGP choosing the route to 133.133.133.0 via
> 151.51.112.2 when it has
> a higher metric ?
>
>
>
> bb2#sho ip bgp
> BGP table version is 30, local router ID is 202.202.5.111
> 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
> * i121.121.1.0/24 151.51.111.111 0 100 0 i
> *> 0.0.0.0 0 32768 i
> * i121.121.2.0/24 151.51.111.111 0 100 0 i
> *> 0.0.0.0 0 32768 i
> * i121.121.3.0/24 151.51.111.111 0 100 0 i
> *> 0.0.0.0 0 32768 i
> *> 133.133.133.0/24 151.51.112.2 30 0
> 12 8723 4799 i
> * i 151.51.111.1 10 100 0
> 12 8723 4799 i
> *> 144.144.144.0/24 151.51.112.2 0 12 8723 i
> * i 151.51.111.1 100 0 12 8723 i
> *> 155.155.155.0/24 151.51.112.2 0
> 12 8723 4799 i
> * i 151.51.111.1 100 0
> 12 8723 4799 i
> *> 166.166.166.0/24 151.51.112.2 0 12 8723 i
> * i 151.51.111.1 100 0 12 8723 i
> *> 177.177.177.0/24 151.51.112.2 0
> 12 8723 4799 i
> * i 151.51.111.1 100 0
> 12 8723 4799 i
> *> 203.203.1.0 151.51.112.2 0
> 12 8723 4799
> 113 i
> * i 151.51.111.1 100 0
> 12 8723 4799
> 113 i
This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:55 GMT-3