The MPLS-OPS Archive

[Eric Osborne <eosborne@cisco.com>]

On Wed, Jan 28, 2004 at 09:42:26PM -0800, Harish Kumtakar wrote:
> Hi guys,
>  
> My understanding is that 'TE metric' associated with a link ('administrative-weight' of a link - in CISCO IOS terminology) may be used to represent 'delay' across the link. Usage of 'TE metric' to represent 'delay' is useful (makes sense) in MPLS-TE networks that carry voice traffic or both voice and data traffic. 
> 
> If I have an MPLS-TE network which is deployed to carry only 'data' traffic, is it necessary (required?) to configure 'TE metric' for all links in my network? I think it does not make much sense to use 'TE metric' to indicate 'delay' as 'delay' is not at all an important factor for networks which carry only data. For such networks, is there any other attribute (used by CSPF path calculation) which we can associate with 'TE metric'?
> 

It is not necessary to configure TE metric; the TE metric by default
takes the same value as the IGP metric.  The only time you need to
configure TE metric is if you want to give TE one metric for the link
and IGP another.  For example, if you want to run only some TE tunnels
(not a full mesh) and want them to use delay as a cost metric and bw
reservation as the other part of their path calculation, but you want
IGP to have a single metric that is some combination of cost and
delay, then you'd need to set TE differently from IGP.




eric

> I would like to hear comments from you ppl.
> 
> Thanks, cheers,
> 
> -Harish
> 
> 
> 
> ---------------------------------
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free web site building tool. Try it!

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml