RE: BGP and Metric

From: GOLBERY Irčne (irene.golbery@xxxxxxxx)
Date: Wed Jun 05 2002 - 03:19:18 GMT-3


   
Thanks for your answer and help Nick,Louis and Peter

Workaround is route-map --> OK
The med is the IGP metric in this Case --> OK

The bahavior is now clear for me but however I am so surprised not to find
any documentation about this way of working.

Thanks again.

Irene.

-----Message d'origine-----
De : Nick Shah [mailto:nshah@connect.com.au]
Envoyi : mercredi 5 juin 2002 00:05
@ : GOLBERY Irhne; ccielab@groupstudy.com
Objet : Re: BGP and Metric

BGP Med is generally derived from 2 sources, IGP metric & explicitly
specifying via route-map. If the IGP metric is unacceptable, apply a
route-map to the neighbor, and change the metric to 0 or anything else to
your liking.

The Med is converted/used as metric when the route is put into routing
table, this can be tweaked via table-map command .

So in general

IGP (Metric ) ---->(tweak with route-map)----> BGP med ----> (tweak with
table-map)----> Routing table.

If none of the tweaks are applied, the IGP metric is carried right into the
routing table.

rgds
Nick
-----Original Message-----
From: GOLBERY Irhne <irene.golbery@arche.fr>
To: ccielab@groupstudy.com <ccielab@groupstudy.com>
Date: Tuesday, 4 June 2002 11:08
Subject: BGP and Metric

>Hi all,
>
>I am trying to understand the Metric parameters in the "Show ip bgp"
command
>- see below.
>
>I am "not using MED"(no MED config. nowhere) and however for the same
>network 195.110.250.40 we can see metric 71 and 70.
>
>Can you help me ?
>
>Thanks
>
>Irene.
>
>
>
>ROUTER#sh ip b
>BGP table version is 760, local router ID is 3.3.3.8
>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
>
>* i195.110.250.40/29 3.3.3.9 71 180 0 i
>*> 0.0.0.0 70 32768 i



This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:24 GMT-3