The MPLS-OPS Archive

[Jean Philippe Vasseur <jvasseur@cisco.com>]

Hi,

At 09:42 PM 1/28/2004 -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'?

The fact that you can make use of either the IGP or the TE metric during
CSPF allows you to determine the constrained path criteria on a per LSP
basis. You then choose the characteristic that the metric represents.
Hope this clarifies your question.

JP.

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