The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2004-Jan> msg00093



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

TE Metric of a link

  • From: Harish Kumtakar <harish_hsk@yahoo.com>
  • Date: Wed, 28 Jan 2004 21:42:26 -0800 (PST)
  • Resent-Date: Thu, 29 Jan 2004 01:30:58 -0500
  • To: mpls-ops@mplsrc.com

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'?

I would like to hear comments from you ppl.

Thanks, cheers,

-Harish

Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!