Obviously from a cisco track development engineer who does not work with
OSPF :)
Thing is, track is protocol independent and different protocols use
different metrics. They decided that 1 byte was enough precision to
track a route, so they try to fit different protocol metrics into
the 0-255 range.
Some documents state that the RIP factor is "times 17" instead of
1. Luckily, OSPF (and EIGRP/ISIS/BGP/static) support changing the
default with "track resolution ip route ospf xxxx".
-Carlos
Taufik Kurniawan @ 3/08/2010 2:17 -0300 dixit:
> here :
> http://www.cisco.com/E-Learning/bulk/public/cln/qlm/ccnp/QLM-VRRP/Configuring_VRRP_to_Track_an_Interface.htm
>
> it mentions scaling factor :
>
> eigrp 2560
> is-is , static : 10
> ospf, rip : 1
>
> where this number come from ?
>
> anyone care to explain ?
>
> thanks
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
-- Carlos G Mendioroz <tron_at_huapi.ba.ar> LW7 EQI Argentina Blogs and organic groups at http://www.ccie.netReceived on Wed Aug 04 2010 - 10:41:25 ART
This archive was generated by hypermail 2.2.0 : Wed Sep 01 2010 - 11:20:52 ART