traffic-engineering (MPLS)

When an MPLS-enabled device receives an IS-IS TE LSP, it stores the traffic engineering information in its Traffic Engineering database (TED). The device uses information in the TED when performing calculations to determine a path for an LSP. The user can configure the device to send out IS-IS TE LSPs for all of its MPLS-enabled interfaces.

Syntax

traffic-engineering { [ isis [ level-1| level-2 ] ] | [ ospf [ area [ area_id | all ] ] ] }

no traffic-engineering { [ isis [ level-1| level-2 ] ] | [ ospf [ area [ area_id | all ] ] ] }

Command Default

By default, the device does not send out IS-IS LSPs with TE extensions for its MPLS-enabled interfaces.

Parameters

isis

Advertise by way of ISIS.

level-1: Traffic-engineering for level-1.
level-2: Traffic-engineering for level-2.

ospf

Advertise by way of OSPF.

area

designate OSPF area.

area_id: Specifies OSPF area ID in IP address format.

all: Advertise in all OSPF areas.

Modes

MPLS policy mode

Usage Guidelines

The no for of the command disables the configuration.

The user must enable the device to send out IS-IS LSPs with TE extensions when the user wants CSPF to perform constraint-based path selection because information in the TED is used to make path selections using CSPF, and information in the TED comes from IS-IS LSPs with TE extensions.

MPLS is supported on the Extreme 8820, SLX 9740, SLX 9640, and SLX 9540 devices only.

Examples

The following example configures the device to send out IS-IS TE LSPs to the level-1 MPLS-enabled interface.

device# configure
device(config)# router mpls
device(config-router-mpls)# policy
device(config-router-mpls-policy)# traffic-engineering isis level-1