Configuring Metric Type

Extensions to IS-IS traffic engineering enable the use of bigger metrics. You can specify whether your router accepts, generates, or accepts and generates only old-style metrics, only new-style metrics, or both.

metric-style narrow

• Use to specify that the router generates and accepts only old-style TLV tuples.
• Old-style TLVs refers to TLVs having metrics with a narrow (six-bit) field with a value in the range 0–63. New-style TLVs refers to TLVs having metrics with a wider field, as provided for in current extensions to IS-IS traffic engineering.
• Use the transition option to accept old-style and new-style metrics; only old-style metrics are generated.
• Specify whether the command applies to level 1, level 2, or both.
• Example

  host1(config-router)#metric-style narrow level-2

• Use the no version to restore the default, which is to generate and accept only old-style TLVs with narrow (six-bit) metric fields.
• See metric-style narrow

metric-style transition

• Use to specify that the router generates and accepts both old-style and new-style TLV tuples.
• Old style refers to TLVs having metrics with a narrow (six-bit) field with a value in the range 0–63. New style refers to TLVs having metrics with a wider field, as provided for in current extensions to IS-IS traffic engineering.
• Specify whether the command applies to level 1, level 2, or both.
• Example

  host1(config-router)#metric-style transition level-1

• Issuing this command results in more resource usage than issuing the metric-style narrow or metric-style wide commands.
• Use the no version to restore the default, which is to generate and accept only old-style TLVs with narrow (six-bit) metric fields.
• See metric-style transition

metric-style wide

• Use to specify that the router generates and accepts only new-style TLV tuples.
• Old style refers to TLVs having metrics with a narrow (six-bit) field with a value in the range 0–63. New style refers to TLVs having metrics with a wider field, as provided for in current extensions to IS-IS traffic engineering.
• Use the transition option to accept old-style and new-style metrics; only new-style metrics are generated.
• Specify whether the command applies to level 1, level 2, or both.
• Before you set a route tag for an IS-IS interface, you must issue the metric-style wide command to configure the router to generate and accept TLV type 135, which is a new-style tuple that contains the route tag.
• Example

  host1(config-router)#metric-style wide level-1-2

• Use the no version to restore the default, which is to generate and accept only old-style TLVs with narrow (six-bit) metric fields.
• See metric-style wide

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.