From: Michael Bausenwein (mikeb55@xxxxxxxx)
Date: Mon Apr 03 2000 - 23:56:33 GMT-3
by default the igrp and eigrp routing processes use only bandwidth and delay
for calculating the best path to a destination. this command is used to
specify what weight the value is use in the calc (ie load, reliabliity and
mtu)
look at page 243 in routing TCP/IP by Jeff doyle. He gets paid to explain
it, so he can do it better than I....
Mike
----- Original Message -----
From: Aaron DuShey <adushey@yahoo.com>
To: CCIE (E-mail) <ccielab@groupstudy.com>
Sent: Sunday, April 02, 2000 10:29 PM
Subject: Metric weights IGRP command
> I have looked at the docs and have read up on this command. Yet, I am
still
> unclear as to where this command would be necessary. It seems to me that
you
> could just adjust the bandwidth and delay on the interfaces to affect its
> routing decisions. Also, I think I understand that this command allows you
> to tell IGRP to use other metrics besides bandwidth and delay when making
> routing decisions, but why then can you manipulate it so drastically- see
> below
>
> r2(config)#router igrp 50
> r2(config-router)#metric weights ?
> <0-8> Type Of Service (Only TOS 0 supported)
>
> r2(config-router)#metric weights 0 ?
> <0-4294967295> K1
>
> r2(config-router)#metric weights 0 1 ?
> <0-4294967295> K2
>
> r2(config-router)#metric weights 0 1 1 ?
> <0-4294967295> K3
>
> r2(config-router)#metric weights 0 1 1 1 ?
> <0-4294967295> K4
>
> r2(config-router)#metric weights 0 1 1 1 1 ?
> <0-4294967295> K5
>
> r2(config-router)#metric weights 0 1 1 1 1 1 ?
> <cr>
>
> r2(config-router)#metric weights 0 1 1 1 1 1
>
> any insights?
> thanks,
>
> Aaron DuShey
>
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:12 GMT-3