Because when you redistribute a routing protocol like BGP into EIGRP, you
must specify a metric.  Metrics in BGP are meaningless in EIGRP.  I mean
if a route has a local pref of 100, a weight of 100, and a AS PATH of 100
200, how is eigrp to deal with that?  EIGRP understand load, reliability,
mtu, etc.  so you must put it into a form EIGRP can understand.

Their is no "automatic" way to convert BGP metrics to EIGRP metrics.  In
some redistribution situations you don't have to worry about specifying a
metric.

You can specify the metric the BGP routes should have within the EIGRP
process on the same line as the "redistribute" line.  Or you can specify a
"default-metric" line which will apply to the redistributed routes.
Either one would be a valid way of doing this.  You don't have to have
"default-metric" instead you could have specified the metric on the
"redistribute" line.

If you redistrbute routes into a distance vector proctocol, and it
doesn't understand the metrics of the foreign protocol, then it assigns
"-1" which is definitly not what you want.

Read a good chapter on route-redistribution, perhaps Routing TCP/IP (an
excellent source on this), and it will clear your mind.

Brian


On Sat, 2 Dec 2000, Frank Wells wrote:

> Just did the Fatkid Basic BGP lab #320.  I am trying to understand why I
> needed the command default-metric 64000 2 225 1 1500 under the eigrp 1
> process on router 4.  I could not advertise the 10.0.0.0 network from
> router4 to the other members of AS 200 until I used it.  I just want to hear
> some explanantions as to why.  What default-metric did this command change ?
>
> Thanks a lot
>
> http://www.fatkid.com/html/320_basic_bgp.html
> _____________________________________________________________________________________
> Get more from the Web.  FREE MSN Explorer download : http://explorer.msn.com
>
> _________________________________
> FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>

-----------------------------------------------
Brian Feeny, CCNP, CCDP       [EMAIL PROTECTED]
Network Administrator
ShreveNet Inc. (ASN 11881)

_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to