Supported Platforms
Related Documentation
- ACX, M, PTX, T Series
- Configuring Traffic Engineering for LSPs
- EX Series
- Configuring MPLS on Provider Edge Switches Using IP Over MPLS (CLI Procedure)
traffic-engineering (Protocols MPLS)
Syntax
Hierarchy Level
Release Information
Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.1 for EX Series switches.
Description
Select whether MPLS performs traffic engineering on BGP destinations only or on both BGP and IGP destinations. Affects only LSPs originating from this routing device, not transit or egress LSPs.
Default
bgp
Options
bgp—On BGP destinations only. Ingress routes are installed in the inet.3 routing table.
bgp-igp—On both BGP and IGP destinations. Ingress routes are installed in the inet.0 routing table. If IGP shortcuts are enabled, the shortcut routes are automatically installed in the inet.0 routing table.
bgp-igp-both-ribs—On both BGP and IGP destinations. Ingress routes are installed in the inet.0 and inet.3 routing tables. This option is used to support VPNs.
mpls-forwarding—On both BGP and IGP destinations. Use ingress routes for forwarding only, not for routing.
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related Documentation
- ACX, M, PTX, T Series
- Configuring Traffic Engineering for LSPs
- EX Series
- Configuring MPLS on Provider Edge Switches Using IP Over MPLS (CLI Procedure)
Published: 2013-04-03
Supported Platforms
Related Documentation
- ACX, M, PTX, T Series
- Configuring Traffic Engineering for LSPs
- EX Series
- Configuring MPLS on Provider Edge Switches Using IP Over MPLS (CLI Procedure)