Supported Platforms
Related Documentation
- ACX, M, MX, PTX, QFX, T Series
- Example: Enabling Wide IS-IS Metrics for Traffic Engineering
- ACX, M, MX, PTX, SRX, T Series
- te-metric
wide-metrics-only
Syntax
Hierarchy Level
Release Information
Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Description
Configure IS-IS to generate metric values greater than 63 on a per IS-IS level basis.
Normally, IS-IS metrics can have values up to 63, and IS-IS generates two type, length, and value (TLV) tuples, one for an IS-IS adjacency and the second for an IP prefix. To allow IS-IS to support traffic engineering, a second pair of TLVs has been added to IS-IS, one for IP prefixes and the second for IS-IS adjacency and traffic engineering information. With these TLVs, IS-IS metrics can have values up to 16,777,215 (224 – 1).
To configure IS-IS to generate only the new pair of TLVs and thus to allow the wider range of metric values, include the wide-metrics-only statement.
Default
By default, Junos OS supports the sending and receiving of wide metrics. Junos OS allows a maximum metric value of 63 and generates both pairs of TLVs.
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related Documentation
- ACX, M, MX, PTX, QFX, T Series
- Example: Enabling Wide IS-IS Metrics for Traffic Engineering
- ACX, M, MX, PTX, SRX, T Series
- te-metric
Published: 2013-08-15
Supported Platforms
Related Documentation
- ACX, M, MX, PTX, QFX, T Series
- Example: Enabling Wide IS-IS Metrics for Traffic Engineering
- ACX, M, MX, PTX, SRX, T Series
- te-metric
